Database Users

fastboot for Aussie Razr M 77.176.16.XT905.Telstra.en.AU

Hi all
Just wondering if anyone has a copy of the official Australian Razr M release firmware.
77.176.16.XT905.Telstra.en.AU
Always good to have a fallback system image!
Thanks in advance

wintermute000 said:
Hi all
Just wondering if anyone has a copy of the official Australian Razr M release firmware.
77.176.16.XT905.Telstra.en.AU
Always good to have a fallback system image!
Thanks in advance
Click to expand...
Click to collapse
Hi, I am also looking for the same firmware, managed to root the phone using Motofail2go but unable to use Clockworkmod to backup or load other firmware. Now when I try to Erase the phone I get the AP Fastboot Flash Mode (s) Device is looked Boot Failure. Luckily pressing the power button gets me back to a working phone. I have also unrooted the phone using DoomLord unrooting script but still the same boot up error. I know now the bootloader is locked by Motorola, this is why I need the original Telstra firmware.
I will donate $ 20 by Paypal to anyone that posts a working 77.176.16.XT905.Telstra.en.AU firmware that I can use and fixes the boot issue.

ozsultan said:
Hi, I am also looking for the same firmware, managed to root the phone using Motofail2go but unable to use Clockworkmod to backup or load other firmware. Now when I try to Erase the phone I get the AP Fastboot Flash Mode (s) Device is looked Boot Failure. Luckily pressing the power button gets me back to a working phone. I have also unrooted the phone using DoomLord unrooting script but still the same boot up error. I know now the bootloader is locked by Motorola, this is why I need the original Telstra firmware.
I will donate $ 20 by Paypal to anyone that posts a working 77.176.16.XT905.Telstra.en.AU firmware that I can use and fixes the boot issue.
Click to expand...
Click to collapse
Out of curiosity what CWM did you try to flash?
You do know that you CAN unlock your bootloader right? exact same procedure as Razr I. Yeah the moto website doesn't mention telstra Razr M model blah blah blah it works as confirmed by Ausdroid editor in this thread.
http://forum.xda-developers.com/showthread.php?p=33777574#post33777574

wintermute000 said:
Out of curiosity what CWM did you try to flash?
You do know that you CAN unlock your bootloader right? exact same procedure as Razr I. Yeah the moto website doesn't mention telstra Razr M model blah blah blah it works as confirmed by Ausdroid editor in this thread.
http://forum.xda-developers.com/showthread.php?p=33777574#post33777574
Click to expand...
Click to collapse
Hi I used CWM from Google Play and selected the Motorola Photon Q from CWM, maybe a mistake but no RAZR M was listed.
I registerd on the Motorola site to get the unlock key but there is a quite a process to complete the excersice. Rather just have my stock rom back and forget about rooting for now.

ozsultan said:
Hi I used CWM from Google Play and selected the Motorola Photon Q from CWM, maybe a mistake but no RAZR M was listed.
I registerd on the Motorola site to get the unlock key but there is a quite a process to complete the excersice. Rather just have my stock rom back and forget about rooting for now.
Click to expand...
Click to collapse
I dunno how experienced you are at this so I apologise if I'm getting mixed up here but:
a.) You will NEVER flash ANY RECOVERY aside from stock without unlocking your bootloader, and you don't flash CWM from google play (not even sure what you're referring to!!!). You CAN flash recoveries from rom manager if your bootloader is unlocked and you have root.
b.) The only recovery I've seen around the place confirmed for Razr M (unlocked bootloader) is this one
http://aosp.us/?p=294
If you think the steps in unlocking bootloader is too hard you shouldn't even attempt it. Sorry to say but thats pretty much standard stuff for flashing recoveries etc. !!!! (having drivers installed, using fastboot via command line etc.)

wintermute000 said:
I dunno how experienced you are at this so I apologise if I'm getting mixed up here but:
a.) You will NEVER flash ANY RECOVERY aside from stock without unlocking your bootloader, and you don't flash CWM from google play (not even sure what you're referring to!!!). You CAN flash recoveries from rom manager if your bootloader is unlocked and you have root.
b.) The only recovery I've seen around the place confirmed for Razr M (unlocked bootloader) is this one
If you think the steps in unlocking bootloader is too hard you shouldn't even attempt it. Sorry to say but thats pretty much standard stuff for flashing recoveries etc. !!!! (having drivers installed, using fastboot via command line etc.)
Click to expand...
Click to collapse
Hi Thanks for your help and comments, I have rooted my old HTC Desire using Unrevoked in the past and flashed a Cyanogen mod and a LeeDroid mod without any problems so I thought I would try the RAZR M. Maybe the boot loader was different or not locked. I was able to go into recovery mode and select the cooked zipped roms from the SD card. I can not find any roms for the Aussie RAZR M either, I guess that is what you are looking for and concerned about updating the the JB from for the Verizon version as the radio may be different.
Anyway, the Motorola UI is not so bad and I especially like to start page with the circles. Hopefully JB update will come OTA soon. I hope that the JB update will return my phone to stock and the Bootloader error does not come up anymore. All is fine for now but if I have to wipe my phone and start again I can not do it. Have you ended up using your Motorola unlock code to unlock the boot loader ?
I am not completely a newbie

ozsultan said:
Hi Thanks for your help and comments, I have rooted my old HTC Desire using Unrevoked in the past and flashed a Cyanogen mod and a LeeDroid mod without any problems so I thought I would try the RAZR M. Maybe the boot loader was different or not locked. I was able to go into recovery mode and select the cooked zipped roms from the SD card. I can not find any roms for the Aussie RAZR M either, I guess that is what you are looking for and concerned about updating the the JB from for the Verizon version as the radio may be different.
Anyway, the Motorola UI is not so bad and I especially like to start page with the circles. Hopefully JB update will come OTA soon. I hope that the JB update will return my phone to stock and the Bootloader error does not come up anymore. All is fine for now but if I have to wipe my phone and start again I can not do it. Have you ended up using your Motorola unlock code to unlock the boot loader ?
I am not completely a newbie
Click to expand...
Click to collapse
No waiting for
- backup stock image for obvious reason!
- something to actually flash to appear!
BTW check this thread http://forum.xda-developers.com/showthread.php?p=33789915#post33789915 the comments from apacheo who has confirmed unlock and recovery install (TWRP though not CWM)

wintermute000 said:
No waiting for
- backup stock image for obvious reason!
- something to actually flash to appear!
BTW check this thread http://forum.xda-developers.com/showthread.php?p=33789915#post33789915 the comments from apacheo who has confirmed unlock and recovery install (TWRP though not CWM)
Click to expand...
Click to collapse
Thanks. did you mean now waiting, I guess u could mean either as apacheo has something available ? Looks like apacheo might be getting my $20 via paypal. So with the recommendation from apachio do I still have to unlock the booter. If yes, can this only be done via the Motorola site unlock code?
Will the stock Telstra image from apacheo fix my boot failure issue ? Will I need to have a rooted RAZR M and loader (TWRP) to load the file?
Thanks appreciate your help.

You shouldn't need to unblock bootloader to push the stock image. If its stock you should be able to flash it.
The whole point of unlocking is to be able to push NON OFFICIAL stuff however not having seen that image I can't confirm. e.g. Maybe because he extracted it himself its not signed like an official moto image so you may need to unlock.
If he has extracted a fastboot image it will INCLUDE stock recovery and you flash it via fastboot command line utility. Thats better than a ROM you have to flash with a recovery because it lets you roll back even if you screw your recovery.
All in all, ask him yourself, I'm only speculating based on first principles
BTW android manufacturers have gotten a lot more anal since desire, and yeah back then a lot of stuff was unlocked, now pretty much only Sammy ships unlocked bootloaders. I'd say that back then you could probably unlock the bootloader pretty easily so you don't remember jumping through hoops.

ozsultan said:
Thanks. did you mean now waiting, I guess u could mean either as apacheo has something available ? Looks like apacheo might be getting my $20 via paypal. So with the recommendation from apachio do I still have to unlock the booter. If yes, can this only be done via the Motorola site unlock code?
Will the stock Telstra image from apacheo fix my boot failure issue ? Will I need to have a rooted RAZR M and loader (TWRP) to load the file?
Thanks appreciate your help.
Click to expand...
Click to collapse
The stock recovery img is probably not going to fix your device.. sounds like you probably need the boot image, but how'd you manage to corrupt that?

apacheo said:
The stock recovery img is probably not going to fix your device.. sounds like you probably need the boot image, but how'd you manage to corrupt that?
Click to expand...
Click to collapse
Hi Apacheo, thanks for the reply, my procedure was as per my first post yesterday. Using Clockworkmod Rom Manger app I picked the Motorola Photon Q for Flash Alternate Recovery as this was the only close Motorola phone to the Razr M. (MY BAD) Maybe that was the problem. I tried to back up the existing rom using Clockworkmod but again got the AP Fastboot Flashmode error.
How do I get the boot image and load that? Meanwhile I have unrooted the phone and can use it. Just can't do a factory data reset and start with a new slate if I have to. Just hangs on the AP Fastboot Flashmode (S) black and white Device is locked screen.
Thanks, I was hoping to lose that $20 to u.

Flashing the stock recovery using fastboot is probably the best start.
I'll upload the recovery image and post the URL here. Wait a moment.
Sent from my XT905 using xda app-developers app
---------- Post added at 08:01 PM ---------- Previous post was at 07:56 PM ----------
Here's the stock recovery image:
http://db.tt/A5veTD0u
Sent from my XT905 using xda app-developers app

apacheo said:
Flashing the stock recovery using fastboot is probably the best start.
I'll upload the recovery image and post the URL here. Wait a moment.
Sent from my XT905 using xda app-developers app
---------- Post added at 08:01 PM ---------- Previous post was at 07:56 PM ----------
Here's the stock recovery image:
http://db.tt/A5veTD0u
Sent from my XT905 using xda app-developers app
Click to expand...
Click to collapse
Thanks Apacheo, I assume I can use RSD Lite 5.4.6.4, how to open the 10 MB RAW file ? I know RAW as a picture file from a camera. Does the 10 MB file contain the whole Telstra ROM ?

ozsultan said:
Thanks Apacheo, I assume I can use RSD Lite 5.4.6.4, how to open the 10 MB RAW file ? I know RAW as a picture file from a camera. Does the 10 MB file contain the whole Telstra ROM ?
Click to expand...
Click to collapse
No idea about RSDLite, you use Fastboot to flash that, and it's a raw dump of the Recovery partition. Flash it like this:
fastboot flash recovery recovery-file.raw
The extension is irrelevant, you could equally rename it .img (which is the standard for fastboot files) but it won't make any difference. It's not the whole Telstra ROM, just the recovery partition. The whole ROM would be something like 600 mb, and as I've modified my system partition (i.e. rooted it) you may not want that, and with only 3G internet, I couldn't upload it anyway

apacheo said:
No idea about RSDLite, you use Fastboot to flash that, and it's a raw dump of the Recovery partition. Flash it like this:
fastboot flash recovery recovery-file.raw
The extension is irrelevant, you could equally rename it .img (which is the standard for fastboot files) but it won't make any difference. It's not the whole Telstra ROM, just the recovery partition. The whole ROM would be something like 600 mb, and as I've modified my system partition (i.e. rooted it) you may not want that, and with only 3G internet, I couldn't upload it anyway
Click to expand...
Click to collapse
Hi apache, thanks again, HELP.
OK, I press vol up and vol down and press the power key at the same time. I get the menu boot load selection, availlable boot modes if I pick recovery or AP fastboot I still get back to the AP Fastboot Flashmode (s) screen Device is locked Status Code:0
I assume I get into recovery mode and use your raw file from my SD card to update the recovery partition. What am I doing wrong?

incorrect, you flash via fastboot command line in.... fastboot mode (not recovery mode)

Hey,
I'm hoping to help you guys out. First I have a couple of questions.
1) is your device bootloader unlocked?
2) are you rooted?
If so I have methods to create a backup XML file for you.

jimmydafish said:
Hey,
I'm hoping to help you guys out. First I have a couple of questions.
1) is your device bootloader unlocked?
2) are you rooted?
If so I have methods to create a backup XML file for you.
Click to expand...
Click to collapse
If you have methods to recover an Australian modem IMG (instead of the Verizon-based one) then I'm all ears.. because until I find an AU modem, my phone is now completely unusable.. whoops :/

apacheo said:
If you have methods to recover an Australian modem IMG (instead of the Verizon-based one) then I'm all ears.. because until I find an AU modem, my phone is now completely unusable.. whoops :/
Click to expand...
Click to collapse
We can work on this, do you have access to another AU M? Plus this may be easier via gtalk or email.

jimmydafish said:
We can work on this, do you have access to another AU M? Plus this may be easier via gtalk or email.
Click to expand...
Click to collapse
If I had another, I'd just root it and dd the modem image off and flash it on the broken one.. sadly I don't
I managed to screw it up by flashing the VZW ICS stock, so I could get the JB update on.. I deliberately didn't flash the modem from the VZW ICS stock, and I modified the JB update so it wouldn't apply any changes to the modem... but seemingly, I missed a couple of lines (checking the updater-script, I missed a couple that messed with the modem) so it's completely wrecked. Says the SIM is invalid, and won't detect or connect to any UMTS or GSM carriers here.
If someone else with a rooted Aussie RAZR M is able to step up to assist, it'd be great.
I'll also PM you my details jdf.

[HOW-TO][DEV EDITION ONLY]Root on 4.4 KitKat

https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!

What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app

Jexx11 said:
What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it

alex94kumar said:
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it
Click to expand...
Click to collapse
That's odd, I used the TWRP version in Hashcodes thread, flashed with the Motorola Fastboot. When I went to restart from TWRP it asked me if I wanted to root and I let it. Now I'm rooted.
Sent from my XT1060 using Tapatalk

Stranger things have happened, I guess. Regardless of which method you use, you'll end up with root either way

This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.

chaoslimits said:
This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.
Click to expand...
Click to collapse
same here but i have 85% battery
so i guess we will have to re-flash and push the supersu

The only advice I can give to either of you is to try reflashing TWRP again

Actually i did it again and it worked, guess we can't just skip steps.
Sent from my Nexus 7 using Tapatalk 4

Well im glad it worked out for you in the end

It worked after I charged the phone.
Thanks
Sent from my XT1060 using Tapatalk 2

How do I return my phone to default in order to install OTA
I have already flashed the stock recovery but my phone is still rooted. Do I need to unroot? I tried installing the OTA and it said it failed.

This method should work on any version with with an unlocked bootloader such as Sprint and T-Mobile - not just the dev editions.

alex94kumar said:
https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
Click to expand...
Click to collapse
Anyone knows how to do UNROOT if I used this method to get root?

I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.

1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.

s0nic69 said:
1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.
Click to expand...
Click to collapse
If we're already on 4.4, how do we know if we have the first OTA?
Thanks

chillmeow said:
I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.
Click to expand...
Click to collapse
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
---------- Post added at 03:45 PM ---------- Previous post was at 03:28 PM ----------
doctor_evil said:
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
Click to expand...
Click to collapse
OK I feel like an idiot. I just noticed that in the fastboot screen it shows that it's locked. I thought developer phones were unlocked by default?
ok after unlocking it I was able to install twrp recovery with no problems

Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?

pphi said:
Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?
Click to expand...
Click to collapse
Are you selecting recovery with the power button or the volume up button? Volume up selects. If you use the power button, the phone just boots normally.

T-Mobile OTA URL 5.0.1 LRX22C to 5.1 LMY47M

5.0.1 Build LRX22C OTA to 5.1 Build LMY47M "T-Mobile"
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
Your bootloader MUST be unlocked already, if not, these instructions do not apply to you so don't do them, it won't work.
These are the steps I did that worked for me. No guarantees that it will work for you, or if it wipes or bricks your phone.
Basically, you're downgrading your phone to 5.0.1 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None. Set OEM Unlock in Developer Options on just in case.
2. Reboot phone to bootloader (adb reboot-bootloader), or Power+Vol Down while the phone is off.
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
Green Android with Red Exclamation mark is stock recovery. Press Power + Vol Up to activate the menus. I sometimes have to press them a lot to get it to show.
If your PC does not recognize ADB Sideload mode, unplug your phone and plug it back in, it should work. If not check Device Manager and reload ADB drivers.

nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
Click to expand...
Click to collapse
Thank You! THANK YOU! THANK YOU! lol thanks for sharing

How do i install this again what are the requirements

Looks like I'm reverting back to 5.01 to get this one.

Just installed it. Thank you!

iGoogleNexus said:
Just installed it. Thank you!
Click to expand...
Click to collapse
Good job, mine is still optimizing apps, super slow, 160 of 202.

someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???

simms22 said:
someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???
Click to expand...
Click to collapse
Radio is 95R, it's the same in the D system image.

nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
You must be bootloader unlocked already, if not, these instructions do not apply to you so don't do them.
Basically, you're downgrading your phone to 5.01 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None.
2. Reboot phone to bootloader (adb reboot-bootloader)
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
FYI, Radio is 95R, the E (Verizon build) is 98R
Click to expand...
Click to collapse
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?

the.emilio said:
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?
Click to expand...
Click to collapse
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.

nxt said:
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.
Click to expand...
Click to collapse
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol

Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!

I just finish side loading it......

mr pnut said:
I just finish side loading it......
Click to expand...
Click to collapse
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
the.emilio said:
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol
Click to expand...
Click to collapse
Same not sure. Ended flashimg all the img, 47E

jay661972 said:
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
Same not sure. Ended flashimg all the img, 47E
Click to expand...
Click to collapse
Yes sir.......

Sorry too far OT delete

kaos2569 said:
Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!
Click to expand...
Click to collapse
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?

LGSilva said:
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?
Click to expand...
Click to collapse
What if u already stuch with 5.1 47E bootloader, flash the one from op but when about tonto recovery, got the same woth the other guy, android with the spinning thing and not exclamation.

Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)

lainemac said:
Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)
Click to expand...
Click to collapse
98R and E build is for Verizon phones. The D builds are for all other non Verizon nexus 6 phones. I went back to 95R because 98R was giving me calling issues.

Bricked my LeEco Pro 3 while installing CM13, need some help and advice.

Hi Guys,
Long story short, I bought the LeEco Pro 3 US version due to the awesome Tmobile network support. The modem supports band 12 and WiFi calling and I was happy with it. But eventually notification issues and the horrible EUI got under my skin and I decided to install CM13 keeping the phone as untouched as possible so that I can revert back to stock whenever needed.
I followed below steps:
1. Enabled developer options and enabled USB debugging.
2. Went the Developer Options and enabled OEM Unlocking.
3. Did adb reboot bootloader to get into the bootloader menu.
4. Did fastboot unlock-go command to unlock the bootloader. I noticed that if I did this command and rebooted the phone, the phone reverted back to being locked again. But I could run the command again from bootloader screen and unlock it (as long as the developer options had the OEM unlocking enabled). So I was never permanently unlocked, just unlock at will whenever I wanted.
5. Then I downloaded the twrp.img file and from fastboot screen i did fastboot boot twrp.img, which booted me inot twrp screen. I was able to switch the language to english but i didnt do the permanent system modification. I did not root the phone as well through the menu.
6. Now, I plugged in a USB OTG drive in the phone. Usb OTG drive had CM13 ROM + Gapps on it.
7. Using the TWRP menu, I did a factory data reset and made a backup of all partitions of the LeEco Phone and saved it into USB OTG drive.
8. Then I installed the CM13 rom on the phone. Followed by Gapps and then rebooted the phone. The phone wouldnt boot.
9. I immediately rebooted the phone into the fastboot menu and tried to run the fastboot boot twrp.img, and got an error message that the device is not unlocked. Which is when i noticed that the phone is bricked.
So Long story short, I have a locked bootloader and I want to to retain my modem. I was given a suggestion to boot into the stock recovery and put the x720 update.zip file and install it. But that would flash the CN modem as well. Can I delete the modem file from the CN rom and flash the update.zip? Can someone help me there? All I want is the modem for the US rom and CM13, thats it.
Thank you guys for reading this post, it helps to talk to XDA about such issues, my wife would just kick my butt because I broke a phone, again!

Did you wipe the system using twrp before installing CM?

sunbinyuan said:
Did you wipe the system using twrp before installing CM?
Click to expand...
Click to collapse
No I didn't wipe the system before installing CM13. Usually the ROM installation scripts do system wipes.

This is the reason why I am hesitant to do this thing as there are no clear (step-by-step) procedures and there is no solid benefit (in fact your will lose some features). Can't it be possible to just create a CM or any other ROM that could be downloaded and rename into update.zip and load it directly renaming the X720 ROM? ^_^

Try unlocking bootloader again with fastboot method as you didn't do it the first time. Then try fastboot boot twrp.img

srikanthc said:
Try unlocking bootloader again with fastboot method as you didn't do it the first time. Then try fastboot boot twrp.img
Click to expand...
Click to collapse
He will not be able to unlock again due to the fact that he installed CM13 on an unlocked bootloader. I did read where you can flash the CN bootloader on a locked bootloader. Look at post #44 from the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" thread.
http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
"I finished the setup and run fastboot again and it is good so for anyone having the same issue as I was having of not able to unlock, just run: Fastboot Flash aboot emmc_appsboot.mbn get the file from dr4stic zip file"
Followed by post #47:
"Yeah I can confirm that flashing the aboot worked like dish soap on a squeaky hinge."
If that doesn't work then you will need to install the CN rom using the stock bootloader.

zoid_99 said:
He will not be able to unlock again due to the fact that he installed CM13 on an unlocked bootloader. I did read where you can flash the CN bootloader on a locked bootloader. Look at post #44 from the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" thread.
http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
"I finished the setup and run fastboot again and it is good so for anyone having the same issue as I was having of not able to unlock, just run: Fastboot Flash aboot emmc_appsboot.mbn get the file from dr4stic zip file"
Followed by post #47:
"Yeah I can confirm that flashing the aboot worked like dish soap on a squeaky hinge."
If that doesn't work then you will need to install the CN rom using the stock bootloader.
Click to expand...
Click to collapse
I ended up installing CN ROM as my last resort. I have an unlocked bootloader and twrp installed now, with CM13. Now I need the way to go back to US modem so I can get all the bands.
Sent from my LEX720 using Tapatalk

ceo.mtcl said:
I ended up installing CN ROM as my last resort. I have an unlocked bootloader and twrp installed now, with CM13. Now I need the way to go back to US modem so I can get all the bands.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
1. Download the rom from here: https://www.androidfilehost.com/?fid=601275311581036717
2. Unzip and extract the NON-HLOS.img file.
3. Reboot into fastboot mode.
4. Flash the modem "fastboot flash modem NON-HLOS.img"
You will not notice a change in the modem version in "About Phone" as they both report Baseband version MPSS.2.0.c1.9.1-00010. Who knows, they may be the same.

zoid_99 said:
1. Download the rom from here: https://www.androidfilehost.com/?fid=601275311581036717
2. Unzip and extract the NON-HLOS.img file.
3. Reboot into fastboot mode.
4. Flash the modem "fastboot flash modem NON-HLOS.img"
You will not notice a change in the modem version in "About Phone" as they both report Baseband version MPSS.2.0.c1.9.1-00010. Who knows, they may be the same.
Click to expand...
Click to collapse
Is this NON HLOS.img file from US baseband? Can you please help me in locating where it came from before I flash it. Thanks in advance.
Sent from my LEX720 using Tapatalk

ceo.mtcl said:
Is this NON HLOS.img file from US baseband? Can you please help me in locating where it came from before I flash it. Thanks in advance.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
That is from the US baseband. That rom will convert a CN install back to a US install.

zoid_99 said:
That is from the US baseband. That rom will convert a CN install back to a US install.
Click to expand...
Click to collapse
Thank you, is that from your phone or did you found it in some other post out here that I missed Zoid? I'm just looking for source of the file.
Sent from my LEX720 using Tapatalk

It's from this thread.
http://forum.xda-developers.com/le-pro3/how-to/flashing-guide-roundup-leeco-le-pro-3-t3511901
"
Okay, if you chose to use the long route and installed the Chinese ROM, you can still get back to the full US version, complete with all LTE bands. dr4stic is responsible for this gem, and was my way back to US ROMdom.
To go from Chinese or Custom ROM back to Stock US version:
The file is located in his Android File Host space here: https://www.androidfilehost.com/?fid=601275311581036717
"

ceo.mtcl said:
No I didn't wipe the system before installing CM13. Usually the ROM installation scripts do system wipes.
Click to expand...
Click to collapse
Sorry for the late answer but to add to that, it happened to me that the ROM didn't have a wipe script thus bricking another of my device. I reinstalled it after wiping the system and it worked.

[V29a only] I managed to relock the bootloader without any backups.

While using the v29a ROM, @kessaras said it should be possible to lock the bootloader using "fastboot oem lock", which didn't work for me on any ROM. I decided to give it a try anyways and it actually worked! It wiped my data, and after restoring and all that I rebooted the phone to see if it was actually locked. "fastboot getvar unlocked" gave me a result of "no". Try it out, but beware, your data will be lost. Proof video: https://youtu.be/Tr6E9LaGWRs Before doing this make sure EVERYTHING is stock! This includes custom recoveries. I do not claim any responsibility if anything goes wrong!
Steps (assuming you already have v29 rom installed):
1. Download ADB and fastboot, along with LG drivers (if you don't have them). Connect your phone and start CMD. CD to the folder where your adb and fastboot files are. (pretty obvious isn't it? )
2. Type "adb reboot bootloader".
3. Type "fastboot oem lock". This WILL wipe your data, and I'm NOT responsible for it!
4. Enjoy your locked phone.

Interesting to say the least, is there any drm locked content that you now can use? (not sure if g4 has any)

Tbh you can relock even without loosing data (at least on LL and MM).
Just reflash the misc partition from either a previous backup (recommended) or from a extracted stock kdz partition will do so.
You should backup misc and the persistent partition before doing so just for the case.
Never written it down because I thought its something no one would like to do but that's verified to work...
.
Sent from my LG-H815 using XDA Labs

OsiBasi said:
Interesting to say the least, is there any drm locked content that you now can use? (not sure if g4 has any)
Click to expand...
Click to collapse
I didn't use any drm content while it was unlocked, so I can't tell. Sorry

steadfasterX said:
Tbh you can relock even without loosing data (at least on LL and MM).
Just reflash the misc partition from either a previous backup (recommended) or from a extracted stock kdz partition will do so.
You should backup misc and the persistent partition before doing so just for the case.
Never written it down because I thought its something no one would like to do but that's verified to work...
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes, it's totally possible but this method doesn't need any backups. I understand it might be hard to believe it worked, even for me it was hard to believe having tried this method on previous ROMs to no avail

alex2000robert said:
Yes, it's totally possible but this method doesn't need any backups. I understand it might be hard to believe it worked, even for me it was hard to believe having tried this method on previous ROMs to no avail
Click to expand...
Click to collapse
yes using fastboot command is new (for OUR device) coming with that modified N release.
btw my described method does not necessarily need a backup. you can do even without..
.

steadfasterX said:
yes using fastboot command is new (for OUR device) coming with that modified N release.
btw my described method does not necessarily need a backup. you can do even without..
.
Click to expand...
Click to collapse
Didn't see you mention flashing misc partition. But if I don't remember wrong it gets flashed everytime we install a KDZ with LGUP anyways this method should be somewhat safer as it doesn't involve flashing anything.

alex2000robert said:
Didn't see you mention flashing misc partition. But if I don't remember wrong it gets flashed everytime we install a KDZ with LGUP anyways this method should be somewhat safer as it doesn't involve flashing anything.
Click to expand...
Click to collapse
no - not every partition u see in a KDZ will be flashed.
Especially when you have an unlocked bootloader.
well the fastboot command will erase all data. flashing misc not nvm i don't care about which is better just wanted to add that there is a method which works on LL and MM (fastboot command will not work there).
btw you should consider to add a [N only] or similar in the thread title
.

steadfasterX said:
no - not every partition u see in a KDZ will be flashed.
Especially when you have an unlocked bootloader.
well the fastboot command will erase all data. flashing misc not nvm i don't care about which is better just wanted to add that there is a method which works on LL and MM (fastboot command will not work there).
.
Click to expand...
Click to collapse
I don't care either, now the good thing is that we suddenly got from 1 method involving backups to 3 methods of which 2 don't involve backups. Hurray :highfive:
I just included [V29a only], just in case. Maybe on V30a/b/c from Korea this won't work.

alex2000robert said:
I don't care either, now the good thing is that we suddenly got from 1 method involving backups to 3 methods of which 2 don't involve backups. Hurray :highfive:
I just included [V29a only], just in case. Maybe on V30a/b/c from Korea this won't work.
Click to expand...
Click to collapse
lol yes true so true :highfive: :victory:
title is perfect now

"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
---------- Post added at 02:05 PM ---------- Previous post was at 01:54 PM ----------
Also cant access download mode. So i think this **** ruined my phone lol

pedrogcsb said:
"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
Click to expand...
Click to collapse
Go to my Q&A, Help & Troubleshooting thread ---> https://forum.xda-developers.com/g4/help/help-imei-0-t3660318/page2
All the info you need is there. Your IMEI probably got corrupted.
Edit: Oh I just saw your added post about not being able to boot into the Download mode, I can't help you at the moment. Haven't figured out why some devices refuse to boot into the Download mode...

Mr.FREE_Bird said:
Go to my Q&A, Help & Troubleshooting thread ---> https://forum.xda-developers.com/g4/help/help-imei-0-t3660318/page2
All the info you need is there. Your IMEI probably got corrupted.
Click to expand...
Click to collapse
What do you mean? I can't even turn on my phone, or acces TWRP or Download mode. Nothing is working

alex2000robert said:
While using the v29a ROM, @kessaras said it should be possible to lock the bootloader using "fastboot oem lock", which didn't work for me on any ROM. I decided to give it a try anyways and it actually worked! It wiped my data, and after restoring and all that I rebooted the phone to see if it was actually locked. "fastboot getvar unlocked" gave me a result of "no". Try it out, but beware, your data will be lost. Proof video: https://youtu.be/Tr6E9LaGWRs
Steps (assuming you already have v29 rom installed):
1. Download ADB and fastboot, along with LG drivers (if you don't have them). Connect your phone and start CMD. CD to the folder where your adb and fastboot files are. (pretty obvious isn't it? )
2. Type "adb reboot bootloader".
3. Type "fastboot oem lock". This WILL wipe your data, and I'm NOT responsible for it!
4. Enjoy your locked phone.
Click to expand...
Click to collapse
you should add a big warning that re-locking the bootloader will lock the bootloader
yea I know.. just make it clear that this means:
BEFORE you do so you have to ensure that everything is completely STOCK! Even no TWRP flashed etc.
.

steadfasterX said:
you should add a big warning that re-locking the bootloader will lock the bootloader
yea I know.. just make it clear that this means:
BEFORE you do so you have to ensure that everything is completely STOCK! Even no TWRP flashed etc.
.
Click to expand...
Click to collapse
Thanks, just added that.

pedrogcsb said:
"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
---------- Post added at 02:05 PM ---------- Previous post was at 01:54 PM ----------
Also cant access download mode. So i think this **** ruined my phone lol
Click to expand...
Click to collapse
Sorry, don't know how to help you here. I read about this error snd supposedly after 10 seconds this message should go away by its own... Try to boot it and wait a little. Then unlock back the bootloader with the unlock.bin and flash the stock recovery from the ZIP file of V29a (which should've flashed by itself, did you remove it?) and only then lock the bootloader. Make sure everything is stock.

pedrogcsb said:
What do you mean? I can't even turn on my phone, or acces TWRP or Download mode. Nothing is working
Click to expand...
Click to collapse
Well, I guess you hard bricked your phone. You had modified firmware(TWRP, kernel) and relocked. Not even surprised you're phone is bricked. Only shot would be send it to LG but they will 99% know you messed with firmware
Wysłane z mojego LG-H815 przy użyciu Tapatalka

Hello,
Is it still possible to unlock the boot loader of an LG G4? Their site is not working.

Minto107 said:
Well, I guess you hard bricked your phone. You had modified firmware(TWRP, kernel) and relocked. Not even surprised you're phone is bricked. Only shot would be send it to LG but they will 99% know you messed with firmware
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Click to expand...
Click to collapse
https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853 I think I will try this next in the morning

Did anyone try unlocking the bootloader as well?
Sent from my iPhone using Tapatalk