Is There Any Way To Remove "Orange State Your Dev.." Message? - Moto E4 Plus Questions & Answers

Hi guys I unlocked my bootloader etc and like everyone else who owns a E4 Plus I get the message "Orange state your device has been unlocked bla blah"
I was wondering is there anyway to remove/hide it? I already searched the forum and most answers were a "no".
But I just wanted to double clarify hence I started this thread.. I know the message only shows up on bootup but like everyone else I would prefer it not to be there..
any replies would be appreciated thanks.
My model is XT1771 Nicklaus
Cheers.

I flashed a bootlogo that covered it. There are several around, pick what you like.

koop1955 said:
I flashed a bootlogo that covered it. There are several around, pick what you like.
Click to expand...
Click to collapse
Could you link me to your boot logo or one similar?
I searched but cant find one specifically hiding the message.
Thanks

koop1955 said:
I flashed a bootlogo that covered it. There are several around, pick what you like.
Click to expand...
Click to collapse
That just apply for the Qualcomm variants, on nicklaus that warning is reported by lk partition on mtk devices, and cant be removed by just changing an custom logo
---------- Post added at 11:20 PM ---------- Previous post was at 11:16 PM ----------
Cobrahaze said:
Could you link me to your boot logo or one similar?
I searched but cant find one specifically hiding the message.
Thanks
Click to expand...
Click to collapse
It cant be removed, at least that you hex patch the lk partition of the device, this message is reported by this partition, it doesn't load an image on boot, it just display this annoying message, and that its why it xant be removed

hetor99 said:
That just apply for the Qualcomm variants, on nicklaus that warning is reported by lk partition on mtk devices, and cant be removed by just changing an custom logo
---------- Post added at 11:20 PM ---------- Previous post was at 11:16 PM ----------
It cant be removed, at least that you hex patch the lk partition of the device, this message is reported by this partition, it doesn't load an image on boot, it just display this annoying message, and that its why it xant be removed
Click to expand...
Click to collapse
Thanks for clearing that up for me.

My apologies for posting incorrect information. The differences between the E4 Plus versions continue to surprise me.

koop1955 said:
My apologies for posting incorrect information. The differences between the E4 Plus versions continue to surprise me.
Click to expand...
Click to collapse
I just got this phone for christmas, There are way too many versions of this phone, so confusion is going be a learning curve, what works on one version doesn't work on another.
So far that's the only downside I have found so far with this phone. Mine is the retail version, xt1775.

Related

...

...
I hope u find this, i've also a bricked x+1
If anyone have this tool I need too!!
Thanks
Can you get into bootloader mode? Charge the phone and see if you can get into bootloader mode.
I'm on the same boat... Just got my Moto X 2014 bricked... Found the tool and files for the original Moto X, but not for Moto X 2014. I don't think they exist (yet).
---------- Post added at 05:08 PM ---------- Previous post was at 05:03 PM ----------
@JulesJam
I am (and I believe eveybody else on this post is) requesting the tool / files because our smartphones are bricked in a way we can't access the bootloader. The tool Junior asked on the OP is to repair / reflash the bootloader, which probably got corrupt, so there's no way to access it and flash anything through Fastboot.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
joker2mbr said:
I am (and I believe eveybody else on this post is) requesting the tool / files because our smartphones are bricked in a way we can't access the bootloader. The tool Junior asked on the OP is to repair / reflash the bootloader, which probably got corrupt, so there's no way to access it and flash anything through Fastboot.
Click to expand...
Click to collapse
Ok, yes, if you corrupted the bootloader than you obviously can't get into bootloader mode. But a lot of times people just don't know how to get into bootloader mode when they have a blank screen. So I was asking.
If your screen is blank when you turn on your device and you know the phone is charged, you can press and hold the power button for about 5 seconds, then immediately press and hold volume down and then press and hold power again and hold both for about 4 seconds then release. I have found I need to press and hold both volume up/down then while still holding press power and keep all 3 held down for 4 seconds and then release. I don't know why but pressing and holding all 3 seems to work better for me.
JulesJam said:
Can you get into bootloader mode? Charge the phone and see if you can get into bootloader mode.
Click to expand...
Click to collapse
The screen is only black and phone doesn't get to the fastboot. I've tried a number of ways.
When I connect to the PC, the device is recognized with the name QHSUSB_DLOAD.
When I connect to the charger, the green led flashes constantly.
Ive already have the .hex files
Junior Passos said:
The screen is only black and phone doesn't get to the fastboot. I've tried a number of ways.
When I connect to the PC, the device is recognized with the name QHSUSB_DLOAD.
When I connect to the charger, the green led flashes constantly.
Click to expand...
Click to collapse
The behavior I see here is quite the same. I tried to use the blankflash tool, but as you already discovered, it needs some device specific files (from the bootloader) and the ones available around just won't work with the Moto X 2014... Install the unsigned device driver on Windows is not difficult. The problem is to find these files, that should come directly from Motorola. Without them, we can't restore the bootloader, that is probably corrupted.
---------- Post added at 11:26 PM ---------- Previous post was at 11:22 PM ----------
dashiell_cano said:
Ive already have the .hex files
Click to expand...
Click to collapse
Did you manage to use the files you've found to fix your bootloader? I thought the needed files were like "singleimage_XXXX.bin"... Please let us know your results.
Thanks a lot!
Junior Passos said:
The screen is only black and phone doesn't get to the fastboot. I've tried a number of ways.
When I connect to the PC, the device is recognized with the name QHSUSB_DLOAD.
When I connect to the charger, the green led flashes constantly.
Click to expand...
Click to collapse
Has anyone looked at this process to see if some variation of it can be used to resurrect your device?
http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602
I am not familiar with the process used here to resurrect a bricked Moto X 2013:
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
However, I have a file emmc_appsboot.mbn for 5.0 for XT1096 (Verizon Moto X 2014) and from scanning the thread above, that may be a useful file.
I can access to the command system, but with the .bin file ive found i receive the "file to large" or "wrong version" message sometimes.
As you said we need the right .bin file.
dashiell_cano said:
I can access to the command system, but with the .bin file ive found i receive the "file to large" or "wrong version" message sometimes.
As you said we need the right .bin file.
Click to expand...
Click to collapse
do you know what emmc_appsboot.mbn is?
JulesJam said:
do you know what emmc_appsboot.mbn is?
Click to expand...
Click to collapse
As i know the mbn file Is the equivalent to the .hex file, am i wrong?
dashiell_cano said:
As i know the mbn file Is the equivalent to the .hex file, am i wrong?
Click to expand...
Click to collapse
Idk, but I have that file and it is for the aboot partition if anyone wants it I can upload it. But it is for the XT1096, I don't know if that matters or not. Do you want it?
Yes please, with your file, mine and the next files to come maybe together we can solve this puzzle
dashiell_cano said:
Yes please, with your file, mine and the next files to come maybe together we can solve this puzzle
Click to expand...
Click to collapse
https://www.dropbox.com/s/5bu79og4b3oqbug/emmc_appsboot.mbn?dl=0
---------- Post added at 05:07 AM ---------- Previous post was at 05:03 AM ----------
dashiell_cano said:
Yes please, with your file, mine and the next files to come maybe together we can solve this puzzle
Click to expand...
Click to collapse
Also read this:
http://forum.xda-developers.com/showpost.php?p=60635306&postcount=431
What is the emmc software flasher tool? Is it this?
http://androidxda.com/download-emmc-dl-tool
JulesJam said:
https://www.dropbox.com/s/5bu79og4b3oqbug/emmc_appsboot.mbn?dl=0
---------- Post added at 05:07 AM ---------- Previous post was at 05:03 AM ----------
Also read this:
http://forum.xda-developers.com/showpost.php?p=60635306&postcount=431
What is the emmc software flasher tool? Is it this?
http://androidxda.com/download-emmc-dl-tool
Click to expand...
Click to collapse
The flasher tool is a program that let you solve the missing recovery with the qualcomm devices instead of use command lines(its something like rsd vs mfastboot), you need 2 files, .hex file ( or mbn) and .bin file (the emergency recovery). You have the mbn (same as my .hex) we just need the .bin one.
dashiell_cano said:
The flasher tool is a program that let you solve the missing recovery with the qualcomm devices instead of use command lines(its something like rsd vs mfastboot), you need 2 files, .hex file ( or mbn) and .bin file (the emergency recovery). You have the mbn (same as my .hex) we just need the .bin one.
Click to expand...
Click to collapse
Is the .bin file something I can pull from a working device? Or is it inaccessible?
... I really dont know
dashiell_cano said:
... I really dont know
Click to expand...
Click to collapse
The Droid Ultra is very similar to the Moto X 2014, do you think any of these files may work?
http://forum.xda-developers.com/droid-ultra/general/droid-ultra-maxx-brick-recovery-t2830806
maybe this:
MPRG8960_MOTO.zip

Phones IMEI changed without even touching it

I have this problem - my G800F changed it's IMEI to 350695200123951. When that happened I had not touched it (no root, no nothing) at evening I still was able to make calls, but later that night it showed 'not registered on network'. I have tried factory reset, reinstalling the firmware using Kies, then I used odin, tried to make EFS backup and restore, but so far I haven't had any success. So I thought that some of you brilliant minds could help me, maybe there is a way to change the IMEI in efs backup file? The only strange thing that happened to my phone couple of days before this happened is that some random number from Ukraine called me, but for obvious reasons I did not answer it nor did I call it back. So now I'm stuck using my fathers old HTC Wildfire S, I really hope that you could help me, because I want my phone back.
SOS
Sorry no answer from me but exactly the same thing with my S5 mini g800F last week (end Sept), with exactly the same false IMEI, and I think I have now tried everything. No luck. Not the Ukraine phone call though!
Cannot get into "engineermode" which may have been a way to fix this. I loaded a new firmware, still nothing. ANY help will be appreciated but please nothing that asks me to add a "secret code" as the phone does not respond to those. I'm not an expert but got desperate enough to try my hand at a terminal emulator, it did not work. Stopped short of using SDK as the download is huge. Firmware now loaded is android 4.4.2 build number KOT49H.G800FXXU1AOG2. Heeeeelp anybody! The vendor is of no use either, just mumbling "this is a very strange thing, where did you get the phone....." (bought from the guy asking!!)
Warranty service restored the original IMEI
KVE123 said:
Sorry no answer from me but exactly the same thing with my S5 mini g800F last week (end Sept), with exactly the same false IMEI, and I think I have now tried everything. No luck. Not the Ukraine phone call though!
Cannot get into "engineermode" which may have been a way to fix this. I loaded a new firmware, still nothing. ANY help will be appreciated but please nothing that asks me to add a "secret code" as the phone does not respond to those. I'm not an expert but got desperate enough to try my hand at a terminal emulator, it did not work. Stopped short of using SDK as the download is huge. Firmware now loaded is android 4.4.2 build number KOT49H.G800FXXU1AOG2. Heeeeelp anybody! The vendor is of no use either, just mumbling "this is a very strange thing, where did you get the phone....." (bought from the guy asking!!)
Click to expand...
Click to collapse
Just couple of days ago got my phone back from warranty and they fixed it (thought they wouldn't since it was rooted), so I would suggest doing the same thing. At the warranty center I had to explain my problem for about 30 minutes, because they believed that phone couldn't change its IMEI. Also you could try other service centers, because some of them said that they could fix this problem for about 30-50 EUR. I believe the only thing that could help otherwise is something like the z3x box, but it would be more expensive as it costs 100+ USD.
If you download the original stock firmware you can flash the IMEI number back to the phone
:S
No solution has been under warranty , the pochaine time to think about backup your EMEI
Yes yes
there is a backup somewhere between all my external hard drives, memory sticks, cloud servers... And i can't find it, too long ago and too many passwords!! But, no use telling me now to make a "pochaine" backup. I will try the reflash to older version suggestion, and see whether that gives me access to the required features. If not, it is the mountain to climb, of getting to the samsung "support" to tinker with the phone. Glad you you are sorted sunciks. A person from xda did contact me, so lets see if that bears fruit.
KVE123 said:
there is a backup somewhere between all my external hard drives, memory sticks, cloud servers... And i can't find it, too long ago and too many passwords!! But, no use telling me now to make a "pochaine" backup. I will try the reflash to older version suggestion, and see whether that gives me access to the required features. If not, it is the mountain to climb, of getting to the samsung "support" to tinker with the phone. Glad you you are sorted sunciks. A person from xda did contact me, so lets see if that bears fruit.
Click to expand...
Click to collapse
A back up of your phone? I would suggest just making a new back up because it's less time consuming.
BUP
irontaco1 said:
A back up of your phone? I would suggest just making a new back up because it's less time consuming.
Click to expand...
Click to collapse
You are going to have to be patient with an old person here. Making a backup of the current situation? Will it not just copy the existing false IMEI and replace on restore? Please be specific, step by step, as you would for a kid. Regards
KVE123 said:
You are going to have to be patient with an old person here. Making a backup of the current situation? Will it not just copy the existing false IMEI and replace on restore? Please be specific, step by step, as you would for a kid. Regards
Click to expand...
Click to collapse
Nope it shouldn't. The IMEI number is installed with the firmware. So if you back it up and factory reset, it should fix it.
---------- Post added at 01:43 PM ---------- Previous post was at 01:39 PM ----------
KVE123 said:
You are going to have to be patient with an old person here. Making a backup of the current situation? Will it not just copy the existing false IMEI and replace on restore? Please be specific, step by step, as you would for a kid. Regards
Click to expand...
Click to collapse
If factory reseting doesn't work, then I suggest flashing the firmware manually.
BUP
OK I have tried this before, but just tried again. Does not work or I'm not doing it correctly.
What's the model number?
Reflash
KVE123 said:
OK I have tried this before, but just tried again. Does not work or I'm not doing it correctly.
Click to expand...
Click to collapse
Meaning tried to backup and factory reset. Now in process of manual flashing (via Kies). Previously found that Kies would download for an hour and then say "unexpected error...." so have not used it in more than two years. Anyway here we go again.
Model is SD-G800F [samsung galaxy s5 mini]
---------- Post added at 04:20 PM ---------- Previous post was at 04:09 PM ----------
KVE123 said:
Meaning tried to backup and factory reset. Now in process of manual flashing (via Kies). Previously found that Kies would download for an hour and then say "unexpected error...." so have not used it in more than two years. Anyway here we go again.
Model is SD-G800F [samsung galaxy s5 mini]
Click to expand...
Click to collapse
Correction = SM-G800F
KVE123 said:
Meaning tried to backup and factory reset. Now in process of manual flashing (via Kies). Previously found that Kies would download for an hour and then say "unexpected error...." so have not used it in more than two years. Anyway here we go again.
Model is SD-G800F [samsung galaxy s5 mini]
---------- Post added at 04:20 PM ---------- Previous post was at 04:09 PM ----------
Correction = SM-G800F
Click to expand...
Click to collapse
So you get an error when backing it up?
kies
irontaco1 said:
So you get an error when backing it up?
Click to expand...
Click to collapse
No, I mean downloading the firmware upgrade. It will download the new files but not install. This was long ago. Right now I get to tools to upgrade and initialise and get the message "does not support initializing" I give up!
No don't give up, just download the firmware and flash it with ODIN. If you need my to explain that, leave me an email and I'll send you the instructions.
irontaco1 said:
No don't give up, just download the firmware and flash it with ODIN. If you need my to explain that, leave me an email and I'll send you the instructions.
Click to expand...
Click to collapse
What you propose was the second thing I did. The first was doing a factory reset with the older version of the firmware (what the phone came out with). Neither steps worked. The firmware I flashed was (Build number) KOT49H.G800FXXU1AOG2. Which btw Kies indicates as the latest version.
Don't use kies
---------- Post added at 05:09 PM ---------- Previous post was at 04:50 PM ----------
The only reason I need an email from you is because XDA won't let me post links. The instructions I'm providing contain links so you can fix your problem.
email
[/COLOR]The only reason I need an email from you is because XDA won't let me post links. The instructions I'm providing contain links so you can fix your problem.[/QUOTE]
Kies does not work anyway
Can do (email) but not on this open forum. Use the private messages
Added edit in wrong place but, given the phone to samsung tech. Will post the outcome somewhere next week
irontaco1 said:
Don't use kies
---------- Post added at 05:09 PM ---------- Previous post was at 04:50 PM ----------
The only reason I need an email from you is because XDA won't let me post links. The instructions I'm providing contain links so you can fix your problem.
Click to expand...
Click to collapse
Can you help me please, i have the same probleme one week ago, without solutions, i pm you, please help me!
same problem here

Bootloader unlock theory 2

I possibly found that the lg g4 can connect a serial console when in fast-boot and android with limited access, and that the boot-loader is based on little kernel
codeaurora.org/blogs/little-kernel-based-android-bootloader
It may be possible to connect uart via serial and map out how the bootrom loads the sbl and (aboot (bootloader))and possibly find a way to unlock the boot-loader
newandroidbook.com/Articles/aboot.html
so far acessing fastboot with a nuked laf partition only specific fastboot commands work. can not get oem-id or reboot/continue via fastboot
console=
/dev/tty
/dev/ttyHS0
/dev/ttyHSL0
/dev/ttyHSL1
gefiltefish1478 said:
I possibly found that the lg g4 can connect a serial console when in fast-boot and android with limited access, and that the boot-loader is based on little kernel
codeaurora.org/blogs/little-kernel-based-android-bootloader
It may be possible to connect uart via serial and map out how the bootrom loads the sbl and (aboot (bootloader))and possibly find a way to unlock the boot-loader
newandroidbook.com/Articles/aboot.html
so far acessing fastboot with a nuked laf partition only specific fastboot commands work. can not get oem-id or reboot/continue via fastboot
console=
/dev/tty
/dev/ttyHS0
/dev/ttyHSL0
/dev/ttyHSL1
Click to expand...
Click to collapse
Try posting this in here: http://forum.xda-developers.com/g4/help/unlock-technical-steps-to-make-unlocked-t3165391
Or even the general G4 forum; the audience appears bigger and you'll probably be able to get more brains taking a look at this!
It's quite interesting.
Dude, I was literally coming here to see if anyone had tried anything like USB serial console the way you'd do with like a raspberry pi or a more recent thin client and found this thread with the search feature.
I'm glad to see that it does, in fact, work. I was about to pitch the theory, but it seems you've not only arrived at the same theory, but have tried it yourself. +thanks for posting the results dude. Much appreciated. Hopefully this will lead to some kind of progress otherwise I'm just going to use an upgrade to get something else and sell my G4. I'm really getting tired of the total lack of ROMs. This isn't 2008 where only a couple carriers have Android phones and the developer base is tiny. What company thinks it's SMART to create only one model that can have the bootloader unlocked and then NOT make that model available on all carriers at the off-contract price?!
I'm guessing there is no way to edit the LK, and implement these changes to re enable fastboot commands without it throwing some type of error due to the fact of it not being signed? -
To selectively enable any fastbootcommand on user/production build, add the command as shown below:
File: bootable/bootloader/lk/app/aboot/aboot.c
Function: void aboot_fastboot_register_commands(void)
structfastboot_cmd_desccmd_list[] = {
/* By default the enabled list is empty. */
{““, NULL},
/* move commands enclosed within the below ifndefto here
* if they need to be enabled in user build.
*/
#ifndefDISABLE_FASTBOOT_CMDS
/* Register the following commands only for non-user builds */
{“flash:”, cmd_flash},
{“erase:”, cmd_erase},
{“boot”, cmd_boot},
{“continue”, cmd_continue},
{“reboot”, cmd_reboot},
{“reboot-bootloader”, cmd_reboot_bootloader},
{“oemunlock”, cmd_oem_unlock},
{“oemlock”, cmd_oem_lock},
{“oemverified”, cmd_oem_verified},
{“oemdevice-info”, cmd_oem_devinfo},
{“oemenable-charger-screen”, cmd_oem_enable_charger_screen},
{“oemdisable-charger-screen”, cmd_oem_disable_charger_screen},
{“oem-select-display-panel”, cmd_oem_select_display_panel},
#endif
};
Can we flash aboot of H811 to LS991 ?
Tctien342 said:
Can we flash aboot of H811 to LS991 ?
Click to expand...
Click to collapse
Nope i already asked that one
bump
TheMadScientist420 said:
bump
Click to expand...
Click to collapse
Any chance this will work? http://www.droidviews.com/unlock-bootloader-twrp-root-lg-v20/
When typed " id" in terminal i got similar results to what is shown in instructions.. Im on ls991zvf..
lowkeyst4tus said:
Any chance this will work? http://www.droidviews.com/unlock-bootloader-twrp-root-lg-v20/
When typed " id" in terminal i got similar results to what is shown in instructions.. Im on ls991zvf..
Click to expand...
Click to collapse
only prob is still oh never mind i do have a twrp lol i forgot kernals wouldnt be same we would need i thing the debug bootloader for ls991 which i actally read the other day on something trying to find us one.
in theory a debug or engineering bl should overite a qfuse in a way kinda thing device model specific but firmware versions usually dont matter or at least the few ive messed with on samsungs.
im in no way a dev but if someone could possibly mod one of the debug bls for us then yes may be possible because if im not mistaken the v20s are locked as tight as ours arent they`
---------- Post added at 04:19 PM ---------- Previous post was at 04:12 PM ----------
lowkeyst4tus said:
Any chance this will work? http://www.droidviews.com/unlock-bootloader-twrp-root-lg-v20/
When typed " id" in terminal i got similar results to what is shown in instructions.. Im on ls991zvf..
Click to expand...
Click to collapse
my g4 may be dying very soon i chucked it pretty hard the other day enough to crack the mother board near the noise cancelling mic and earpiece. destrotyed rear camera. bent the lcd and mother board in a bad kinda way . i might be down tonight to try it with v20s bootloader for the hell of it.
i had a spare lcd with a busted gorilla glass i put back on it lol 4 screen on my g4.
u gonna be around about 8 pm eastern time tonight ima dl most of the files now and when my kids goto bed we can try this with mine of coarse im not out anything if i hard brick and itll give me a reason to find a method to un hardbrick. i got alll thi .bins and firmware extractors if i need to make new boot images. i run cdma workshop qpst dfs all thge good old software i made my own ls991 .dll for old lg flashtool
plus my octobox came in finnaly with jtag
---------- Post added at 04:25 PM ---------- Previous post was at 04:19 PM ----------
im dling the v20 rom and going to attempt to rplace the system and stuff with my rooted zv6 system i got a couple ideas up my sleave on this one
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
---------- Post added at 04:38 PM ---------- Previous post was at 04:29 PM ----------
screw it i aint got nothing goin on now im goin for it
TheMadScientist420 said:
only prob is still oh never mind i do have a twrp lol i forgot kernals wouldnt be same we would need i thing the debug bootloader for ls991 which i actally read the other day on something trying to find us one.
in theory a debug or engineering bl should overite a qfuse in a way kinda thing device model specific but firmware versions usually dont matter or at least the few ive messed with on samsungs.
im in no way a dev but if someone could possibly mod one of the debug bls for us then yes may be possible because if im not mistaken the v20s are locked as tight as ours arent they`
---------- Post added at 04:19 PM ---------- Previous post was at 04:12 PM ----------
my g4 may be dying very soon i chucked it pretty hard the other day enough to crack the mother board near the noise cancelling mic and earpiece. destrotyed rear camera. bent the lcd and mother board in a bad kinda way . i might be down tonight to try it with v20s bootloader for the hell of it.
i had a spare lcd with a busted gorilla glass i put back on it lol 4 screen on my g4.
u gonna be around about 8 pm eastern time tonight ima dl most of the files now and when my kids goto bed we can try this with mine of coarse im not out anything if i hard brick and itll give me a reason to find a method to un hardbrick. i got alll thi .bins and firmware extractors if i need to make new boot images. i run cdma workshop qpst dfs all thge good old software i made my own ls991 .dll for old lg flashtool
plus my octobox came in finnaly with jtag
---------- Post added at 04:25 PM ---------- Previous post was at 04:19 PM ----------
im dling the v20 rom and going to attempt to rplace the system and stuff with my rooted zv6 system i got a couple ideas up my sleave on this one
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
---------- Post added at 04:38 PM ---------- Previous post was at 04:29 PM ----------
screw it i aint got nothing goin on now im goin for it
Click to expand...
Click to collapse
Yes i will be around.. I hope you have success.. I like the sprint variant for alot of reasons.. I think the octobox might do dumps to..
lowkeyst4tus said:
Yes i will be around.. I hope you have success.. I like the sprint variant for alot of reasons.. I think the octobox might do dumps to..
Click to expand...
Click to collapse
i think it does too
---------- Post added at 06:15 PM ---------- Previous post was at 05:50 PM ----------
gefiltefish1478 said:
I possibly found that the lg g4 can connect a serial console when in fast-boot and android with limited access, and that the boot-loader is based on little kernel
codeaurora.org/blogs/little-kernel-based-android-bootloader
It may be possible to connect uart via serial and map out how the bootrom loads the sbl and (aboot (bootloader))and possibly find a way to unlock the boot-loader
newandroidbook.com/Articles/aboot.html
so far acessing fastboot with a nuked laf partition only specific fastboot commands work. can not get oem-id or reboot/continue via fastboot
console=
/dev/tty
/dev/ttyHS0
/dev/ttyHSL0
/dev/ttyHSL1
Click to expand...
Click to collapse
Hey man u still around
I flashed one of the boot images on mine with. Twrp. And of coarse secure boot erroors so i have to restore and retwrp
TheMadScientist420 said:
I flashed one of the boot images on mine with. Twrp. And of coarse secure boot erroors so i have to restore and retwrp
Click to expand...
Click to collapse
Have you tried the octopus box bootloader unlock?
lowkeyst4tus said:
Have you tried the octopus box bootloader unlock?
Click to expand...
Click to collapse
no
i didnt even know it could
Yea after you mentioned you had one, i spent hours looking up what it can do.. It sim unlock, bootloader unlock, repair imei, hardbrick.. Who knows what else.. The cheapest one i found was $100..
lowkeyst4tus said:
Yea after you mentioned you had one, i spent hours looking up what it can do.. It sim unlock, bootloader unlock, repair imei, hardbrick.. Who knows what else.. The cheapest one i found was $100..
Click to expand...
Click to collapse
**** i spent 259. I got it for iemi repairs. And hard brick fix for g4 and a couple old htcs i have.
TheMadScientist420 said:
**** i spent 259. I got it for iemi repairs. And hard brick fix for g4 and a couple old htcs i have.
Click to expand...
Click to collapse
Im working on getting it.. Expensive but worth every penny.. As far as using it to unlock the bootloader, ive seen it done just by clicking the option in the software that should have came with it.. Ive seen it work with 3rd party jtaging software..
---------- Post added at 10:50 AM ---------- Previous post was at 10:19 AM ----------
Im gonna try calling Sprint today and asking for a bootloader unlock..
---------- Post added at 10:56 AM ---------- Previous post was at 10:50 AM ----------
TheMadScientist420 said:
**** i spent 259. I got it for iemi repairs. And hard brick fix for g4 and a couple old htcs i have.
Click to expand...
Click to collapse
Can this work via lg flash tool to convert say a ls991 to h811? Is there any special ools needed like octopus box?
I dont think we can cross flash to811. Ive tried askin that one may be possible with box but doibtfull
And sprint wont unlock bl. Only lg can. They would have to basicly give u the signature to sign ure own images. Unless they offer unlock when nougats released
TheMadScientist420 said:
I dont think we can cross flash to811. Ive tried askin that one may be possible with box but doibtfull
And sprint wont unlock bl. Only lg can. They would have to basicly give u the signature to sign ure own images. Unless they offer unlock when nougats released
Click to expand...
Click to collapse
http://forums.easy-firmware.com/showthread.php?9084-Convert-lg-tot
U gotta pay for the files. And thats the only site claims it can be done tht i see
---------- Post added at 11:43 AM ---------- Previous post was at 11:28 AM ----------
lowkeyst4tus said:
http://forums.easy-firmware.com/showthread.php?9084-Convert-lg-tot
Click to expand...
Click to collapse
Yea i signed up for that site a long time ago. And its a pay site. Cant find that tot any where else and not a garanty

[TOOL] 6T MsmDownloadTool v4.0.59 (OOS v9.0.13)

This tool can be used to revive a bricked OP6T and remove the 'Device is corrupt' error message on boot.
Contains the latest MsmDownloadTool v4.0.59 and OOS v9.0.13 which is compatible with International and McLaren editions.
OOS v9.0.11 can also be used to convert a T-Mobile model into a fully fledged International model, more info here.
Make sure that your phone is switched off.
Open device manager on your Windows PC.
Press and hold the Volume Up & Volume Down buttons then connect to your PC using your data cable.
Once the device is connected to your Windows PC, check if the phone is being recognized (Other > QUSB_BULK or Ports > Qualcomm).
If showing as Other > QUSB_BULK either wait for Windows to install the Qualcomm driver or download one of the drivers below and install.
Run MsmDownloadTool V4.0 and click Start.
NOTE: This will completely wipe your device and relock your bootloader.
Downloads
6T MsmDownloadTool v4.0.59 (OOS v9.0.13)
6T MsmDownloadTool v4.0.58 (OOS v9.0.12)
6T MsmDownloadTool v4.0.58 (OOS v9.0.11)
6T MsmDownloadTool v4.0.58 (OOS v9.0.6)
6T MsmDownloadTool v4.0.58 (OOS v9.0.5)
Driver
Alternative driver
Shameless plugs - OP referral link for any peops that would like $20/£20/€20 discount: OnePlus or PayPal donation link: PayPal.
Wow nice. Now to test this on T-Mobile!! Let the flashing commence
Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.
im tempted to run this today on the tmobile model. how high is the risk of hard brick? will it leave me without fastboot if it doesnt work?
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
dreinulldrei said:
Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.
Click to expand...
Click to collapse
apparently the flash to 9.0.5 in the other thread overwrites the modem anyway. its the criticals that dont overwrite. worst case im within my 14 days still, can alwasy return
dreinulldrei said:
Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.
Click to expand...
Click to collapse
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445
SourPower said:
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445
Click to expand...
Click to collapse
Yep, if a Dev can chime in that I won't be left with a hard brick and will be able to go back to TMobile firm atleastsr I'll jump. The only thing holding me back is that sim unlock and unlock bin. I don't wanna go thru that again if have to exchange.
SourPower said:
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445
Click to expand...
Click to collapse
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
strictlyphat said:
Yep, if a Dev can chime in that I won't be left with a hard brick and will be able to go back to TMobile firm atleastsr I'll jump. The only thing holding me back is that sim unlock and unlock bin. I don't wanna go thru that again if have to exchange.
Click to expand...
Click to collapse
One of three things will happen.
One, it will recognize it as the wrong device and won't flash at all.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.
hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
Click to expand...
Click to collapse
Screw it. I'm gonna do this soon. Will report back
hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
One of three things will happen.
One, it will recognize it as the wrong device and won't flash as at.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.
Click to expand...
Click to collapse
Wanna find out? I'll probably test in a few, lol.
hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
One of three things will happen.
One, it will recognize it as the wrong device and won't flash as at.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.
Click to expand...
Click to collapse
Cuz I'm assuming it's the same as Samsung. One hardware multiple softwares.
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Dark Nightmare said:
Wanna find out? I'll probably test in a few, lol.
Click to expand...
Click to collapse
Dude I will owe you one. Ur much braver than I. If my son falls asleep I'm trying to. PLEASE LET ME KNOW. And please let me buy u a beer lmfao
strictlyphat said:
Screw it. I'm gonna do this soon. Will report back
Click to expand...
Click to collapse
Guess I'll wait on your results...
Dark Nightmare said:
Guess I'll wait on your results...
Click to expand...
Click to collapse
I'm.having doubts man. Lol. What's your input. How likely I hard brick?
strictlyphat said:
I'm.having doubts man. Lol. What's your input. How likely I hard brick?
Click to expand...
Click to collapse
Since this will flash criticals, very likely, don't worry, my download is almost complete, I'll test it since my 6T is my spare device.
Dark Nightmare said:
Since this will flash criticals, very likely, don't worry, my download is almost complete, I'll test it since my 6T is my spare device.
Click to expand...
Click to collapse
Ah u r king. I had a backup iPhone til my daughter destroyed hers.
strictlyphat said:
Ah u r king. I had a backup iPhone til my daughter destroyed hers.
Click to expand...
Click to collapse
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.
Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.[/QUOTE
oof that sucks. thanks again
Click to expand...
Click to collapse
Safe flashing to anyone taking the plunge!
Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.
Click to expand...
Click to collapse
tried it for good measure, same error
iaTa said:
This tool can be used to revive a bricked OP6T and remove the 'Device is corrupt' error message on boot.
Contains the latest MsmDownloadTool v4.0.58 and OOS v9.0.5 and is compatible with the non T-mobile international models (T-mobile compatibility currently unknown).
Make sure that your phone is switched off.
Open device manager on your Windows PC.
Press and hold the Volume Up & Volume Down buttons then connect to your PC using your data cable.
Once the device is connected to your Windows PC, check if the phone is being recognized (Other > QUSB_BULK or Ports > Qualcomm).
If showing as Other > QUSB_BULK either wait for Windows to install the Qualcomm driver or download the driver below and install.
Run MsmDownloadTool V4.0_factory.exe and click Start.
NOTE: This will completely wipe your device and relock your bootloader.
Downloads
MsmDownloadTool: https://androidfilehost.com/?fid=11410963190603846961
Driver: https://androidfilehost.com/?fid=24052804347798730
Shameless plug - my OP referral link for any peops that would like $20/£20/€20 discount: https://www.oneplus.com/invite#EC5BZVULJDUUO22
Click to expand...
Click to collapse
Oh my God you just saved my life brother. Thank you so much.
Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.
Click to expand...
Click to collapse
Sad days... Appreciate the risks you've taken tho!!

TWRP - Need help downloading from Baidu

Can someone download this twrp and upload it to a mirror? It's for the Red Magic 3.
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEw...arentPath=/sharelink781715067-606770439204444
+6281281903288 contact me via whatsapp and i will share to you twrp file
tembokbesi said:
+6281281903288 contact me via whatsapp and i will share to you twrp file
Click to expand...
Click to collapse
OK at this point Ill try anything. I have my cell totally unlocked OEM an Bootloader an still have just a fastboot screen an little else no matter what I try and do.
I use whatsapp. Not sure how to add you or contact you through it?
The only thing i used it for was sending info to my boss
---------- Post added at 01:44 PM ---------- Previous post was at 01:43 PM ----------
Bryceicle1971 said:
OK at this point Ill try anything. I have my cell totally unlocked OEM an Bootloader an still have just a fastboot screen an little else no matter what I try and do.
I use whatsapp. Not sure how to add you or contact you through it?
The only thing i used it for was sending info to my boss
Click to expand...
Click to collapse
Edit: just found out how to add you
I already download twrp wait I share after some time
Any Twrp or EDL rom? Currently stuck in bootloop.

Categories

Resources