Related
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.4.2, TWRP 2.7.0.0 recovery
Objective: wipe everything and flash back to a (rooted) stock for device retail
Why I'm screwed: everything is wiped - phone has no OS, recovery, etc. It simply hangs out on the Motorola M at boot and doesn't move. fastboot loads and will flash recovery (seemingly successfully) but rebooting to recovery always gets stuck at the logo
How I got there:
1. Backed up with TWRP, then flashed new recovery CWM (the one here) and backed up again. Saved both folders of nandroid backups to my PC (yay)
2. Flashed back to TWRP (but this time the new one v2.8.0.1 here, which I downloaded and flashed via that fancy new TWRP app [I selected the "ghost" model]) clicked about every type of wipe option I could get my grubby little fingers on, then adb pushed the ROM and kernel/radio combo from here.
3. Attempted to flash the new ROM via TWRP. It failed. something about an "Error executing updater binary in zip". I sighed, said "meh", googled the problem a bit and figured I'd reboot the recovery and try again. This is where things get weird.
4. Phone hangs out at boot logo (that kaleidoscope "M"). Fine, I accidentally did a normal boot, and there's no OS installed. I go into fastboot and boot to recovery. SAME SCREEN. TWRP has apparently disappeared. No matter. I go into fastboot and flash it again, then boot to recovery. SAME SCREEN. Flash back to CWM. SAME SCREEN. Back to TWRP one more time just for giggles? SAME SCREEN.
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot? Restore either my CWM or TWRP nandroid backups without access to the recovery? Any guidance would be appreciated.
Attachments:
a) boot logo I'm stuck on
b) command line log of commands from flashing recoveries
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
VerneVerne said:
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
Click to expand...
Click to collapse
Perhaps I didn't make that clear - that's exactly what I've been doing.
PHP:
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman
Click to expand...
Click to collapse
That is what I have.
gerodive said:
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot?
Click to expand...
Click to collapse
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Wansanta said:
PHP:
That is what I have.
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Click to expand...
Click to collapse
Could you elaborate a little more on this? How do I get the system.img file to flash? I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check? Deleting the system partition was definitely what I did. Also, why mfastboot as opposed to just fastboot?
gerodive said:
Could you elaborate a little more on this? How do I get the system.img file to flash?
Click to expand...
Click to collapse
mfastboot flash system system.img
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
In bootloader mode it will tell you on the second line. 30:B7 is the 4.4.4 bootloader version.
gerodive said:
Deleting the system partition was definitely what I did.
Click to expand...
Click to collapse
As long as you can get into bootloader mode you can flash it back.
gerodive said:
Also, why mfastboot as opposed to just fastboot?
Click to expand...
Click to collapse
because the moto x system images are too large to flash with fastboot, you have to use mfastboot.
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.2.2, TWRP 2.7.0.0 recovery
Click to expand...
Click to collapse
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
4.2.2 or 4.4.2?
nhizzat said:
4.2.2 or 4.4.2?
Click to expand...
Click to collapse
yeah he really needs to check b/c it really matters what version of the bootloader he is on.
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Sorry, meant 4.4.2.
gerodive said:
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Click to expand...
Click to collapse
So glad!! If you are unlocked, as long as you can get into a functioning bootloader mode and have access to the sbf for your version of the OS you haven't bricked.
I about near had a heart attack when I deleted my system, but no biggie to restore it. I think I only paid $35 to unlock b/c I did it straight through tao bao, but it was the best $35 I have spent in a long time. I drop $35 every time I go for sushi, so I can't imagine not paying to unlock if you have the option.
Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks
Segnale007 said:
Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks
Click to expand...
Click to collapse
Do you have TWRP or stock recovery?
cam30era said:
Do you have TWRP or stock recovery?
Click to expand...
Click to collapse
Nope I do not. I don't even have access to the stock recovery. For some reason when I select the stock recovery the recovery menu does not appear. It just comes up a dead android with a question mark and nothing else..
Segnale007 said:
Nope I do not. I don't even have access to the stock recovery.
Click to expand...
Click to collapse
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.
cam30era said:
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.
Click to expand...
Click to collapse
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..
Segnale007 said:
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..
Click to expand...
Click to collapse
You have nothing to loose by contacting them and asking.
What 5.0.1 factory stock file did you flash?
Mega Montana said:
What 5.0.1 factory stock file did you flash?
Click to expand...
Click to collapse
This one right here https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz
Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?
Mega Montana said:
Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?
Click to expand...
Click to collapse
Depends if he had a 5.1 bootloader before or not. Attempts to downgrade the BL from 5.1 will result in a loop.
If it appears when connecting to the PC as qhsusb mode, then it's fixable. If it appears normally as a fastboot device, then it needs repairing.
Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help
Segnale007 said:
Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help
Click to expand...
Click to collapse
How did you do that with a locked bootloader?
cam30era said:
How did you do that with a locked bootloader?
Click to expand...
Click to collapse
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.
Segnale007 said:
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.
Click to expand...
Click to collapse
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
Aahh. That makes sense. I'm still amazed that recovery was this easy.
cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.
Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
Btw I was surprised to see the phone booting with a userdata and cache files from a newer version of android.
Click to expand...
Click to collapse
Most of those who were able to successfully format cache and userdata still had TWRP installed. You are very lucky. Should buy a lotto ticket today.
Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.
Click to expand...
Click to collapse
You can format cache and userdata with a locked bootloader. You cannot flash cache or userdata with a locked bootloader... Unless your bootloader is "bricked" as per the thread you linked to ultimately.
FYI formatting has the exact same result as flashing userdata and cache. So the options are:
1) you formatted which fixed it
2) you were bootloader bricked and had to use a gpt.bin to fix it.
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
worst case just reflash TWRP =]
akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
You can use whatever recovery you would like, the system image does not affect the recovery in any way.
Thanks - flashed your bootloader files which got me out of a never ending boot animation issue
j32olger said:
Thanks - flashed your bootloader files which got me out of a never ending boot animation issue
Click to expand...
Click to collapse
The bootloop have nothing to do with my bootloader files, they are completley stock from the ota file!
If you installing the new bootloader files on older roms you are asking for troubles.
Boot the watch in bootloader mode and flash the files as described and you watch will work.
Af if it bootlooping run a "Fastboot -w" after flashing.
Greetings, Is the newly released OTA compatible with your rom?
drmcatchr said:
Greetings, Is the newly released OTA compatible with your rom?
Click to expand...
Click to collapse
No ota files will only work with stock untouched rom.
bunny0007 said:
No ota files will only work with stock untouched rom.
Click to expand...
Click to collapse
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!
2k4ever said:
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!
Click to expand...
Click to collapse
Have added it today.
I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.
GuiyeC said:
I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.
Click to expand...
Click to collapse
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.
bunny0007 said:
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.
Click to expand...
Click to collapse
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".
GuiyeC said:
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".
Click to expand...
Click to collapse
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??
bunny0007 said:
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??
Click to expand...
Click to collapse
Yes, it had the boot loader unlocked, and I can't try again flashing the aboot because I can't get it to recovery mode or fast boot mode or anything.
Who can I get the images from?
bunny0007 said:
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
Click to expand...
Click to collapse
By people, do you mean 1 person ???
Pretty unfair for other, isn't it ?
I am looking for bootloader files for the G Watch R to flash over what I believe to be a corrupt bootloader on my device. It will only boot when on the charging stand, and so far I have only been able to get it to boot to 5.0.1 successfully. Once the device tries to pull down the OTA update it reboots and proceeds to run the update and then it fails and powers off.
Currently I can access fastboot and I can get it to boot a stock recovery and twrp with the 5.0.1 boot.img flashed to my device.
Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.
fnj00 said:
Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.
Click to expand...
Click to collapse
Hi there ,
Why don't you try this one ??
http://forum.xda-developers.com/g-w...edroid-r-urbane-port-v1-0-0-june-6th-t3128850
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
rvrzl said:
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
Click to expand...
Click to collapse
Can't flash the OTA in TWRP. Have to be completely stock. It is picking up the TWRP recovery build that does not match stock recovery. TWRP is built from AOSP source and dees_troy is one of the devs.
prdog1 said:
Can't flash the OTA in TWRP. Have to be completely stock. It is picking up the TWRP recovery build that does not match stock recovery. TWRP is built from AOSP source and dees_troy is one of the devs.
Click to expand...
Click to collapse
Oh, I thought you could flash it as long as you downloaded and flashed it manually via recovery, instead of letting the OTA do it's thing automatically. Bummer!
There's no way to remove the recovery without doing a full re-flash either, right? It certainly seems like an exploit worthy of my time to patch, but I was trying to avoid the data loss :/
rvrzl said:
Oh, I thought you could flash it as long as you downloaded and flashed it manually via recovery, instead of letting the OTA do it's thing automatically. Bummer!
There's no way to remove the recovery without doing a full re-flash, right? It certainly seems like an exploit worth of my time to patch, but I was trying to avoid the data loss :/
Click to expand...
Click to collapse
You can fastboot flash the corresponding factory images. Skip the userdata data image and will will not wipe data. OTA's are worthless if gonna run root and recovery. Someone may make a TWRP flashable. Would have to search for it.
Awesome, I'll dig around and figure out how to skip certain images while flashing and give that a try (I've never had to do that before). I'm pretty comfortable in the terminal though, so I'm not too worried. Thanks for your help, @prdog1
rvrzl said:
Awesome, I'll dig around and figure out how to skip certain images while flashing and give that a try (I've never had to do that before). I'm pretty comfortable in the terminal though, so I'm not too worried. Thanks for your help, @prdog1
Click to expand...
Click to collapse
If you're running root, fastboot flash the system.img only. If you don't run a custom kernel, you probably should also fastboot flash the boot.img too.
Keep supersu on your sdcard and after flashing system DO NOT boot the rom. Boot straight into TWRP and flash supersu
If you boot rom install-recovery.sh will install stock recovery on first boot. .flashing super su amended this script so that won't happen.
You can also flash the radio.img. Your choice.
rvrzl said:
I have an unlocked & rooted Nexus 6 (T-Mo, I My build number is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP,
Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Click to expand...
Click to collapse
For OTA's the device needs to be unrooted and complete stock. Including 'recovery'. So flashing with TWRP-recovery will not work.
An alternative is to flash only the new system.img with fastboot.
FWIW, recovery flashable updates are here:
http://forum.xda-developers.com/showthread.php?t=3066052
rvrzl said:
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
Click to expand...
Click to collapse
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
snatale1 said:
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
Click to expand...
Click to collapse
Booting to a stock recovery is easy.
"fastboot boot recovery.img"
Then you can adb sideload, as long as your rom is entirely stock and never rooted.
That said, fastboot flashing the system.img would probably be quicker.
snatale1 said:
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
Click to expand...
Click to collapse
You can flash the OTA all day anyway you want but if you are not stock it won't take. Only other way is one of the flashable TWRP versions that were linked to. And right now looks like that thread is down for update.
danarama said:
Booting to a stock recovery is easy.
"fastboot boot recovery.img"
Then you can adb sideload, as long as your rom is entirely stock and never rooted.
That said, fastboot flashing the system.img would probably be quicker.
Click to expand...
Click to collapse
If I am running everything stock apart from the recovery (using TWRP), with an unlocked bootloader and the device is not rooted, can I simply flash the stock recovery.img without losing any of my data? Is it really that simple? Do I have to use a particular recovery.img?
All I want to do is restore the stock recovery so I can OTA the stagefright update. TWRP is preventing me from doing so at the moment, but I don't want to lose all my data.
rvrzl said:
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
!
Click to expand...
Click to collapse
Because of this, I did the update twice; different methods, to see of there are possible differences.
Differences between official OTA and flashing the new system.img only.
Update 1: Flashing only the new system image (1,7 Gb) with fastboot.
Update 2: Return to stock LMY47Z and install official OTA (24,2 Mb)
Both updates have the same results. Data and apps were kept but there were changes:
a. Changes in build.prop gone (DPI, Wifi interval);
b. Standard icons because the DPI value 384 was changed to 560;
c. BGN-launcher replaced. Google Now launcher became white again;
d. Root gone (SuperSu and Busybox);
(Update 2. Of course returning to stock, replaces the custom kernel).
After rerooting the N6 the following actions were needed after both update methods:
- edit the file: system/build.prop to change the dpi and wifi interval;
- reflash/reinstall: BGN-Launcher, SuperSU and Busybox;
- uninstall updates of the Google app to get BGN-launcher working;
- replacing icons from drawer to start screen.
So when you have made changes to the system, like DPI settings, an update will leave your data alone, but not the settings.
Clawz114 said:
If I am running everything stock apart from the recovery (using TWRP), with an unlocked bootloader and the device is not rooted, can I simply flash the stock recovery.img without losing any of my data? Is it really that simple? Do I have to use a particular recovery.img?
All I want to do is restore the stock recovery so I can OTA the stagefright update. TWRP is preventing me from doing so at the moment, but I don't want to lose all my data.
Click to expand...
Click to collapse
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
efrant said:
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
efrant said:
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The OTA doesn't check the recovery version, since it replaces recovery on first boot anyway. Only matters that its stock.
That said, the only reason not to flash the rightbversiin is if the download link.is down or you have a local copy of a different version anyway.
Clawz114 said:
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
Click to expand...
Click to collapse
The exclamation mark isn't an error. That's the stock recovery splash screen. You have to press vol up + power at that screen to get to the menu
How are you trying to flash the OTA?
By unrooted, lets be clear. The rom must never have been rooted. Unrooting a rom won't work
Clawz114 said:
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
Click to expand...
Click to collapse
What is the error?
danarama said:
[snip]
The OTA doesn't check the recovery version, since it replaces recovery on first boot anyway. Only matters that its stock.
Click to expand...
Click to collapse
You are right, the OTA doesn't check the version of the recovery. However, I can tell you for a fact that on older Nexus devices, using a recovery from a different version of Android would not allow an update to flash. (It is possible this has changed since then though.) I remember very clearly, helping many users troubleshoot (particularly given that the only available toolkit at the time would flash only one generic stock recovery, and not a specific version), and it was confirmed that the errors users were having were due to using a wrong version of the stock recovery, so the recovery version did indeed matter (at least on the Galaxy Nexus it did).
danarama said:
The exclamation mark isn't an error. That's the stock recovery splash screen. You have to press vol up + power at that screen to get to the menu
Click to expand...
Click to collapse
I press install update now, let the phone reboot and I get the installation screen with the progress bar. It sits at about 10% filled for about 10 seconds then I get the picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
danarama said:
How are you trying to flash the OTA?
Click to expand...
Click to collapse
The only thing I flashed was a stock recovery.img, to replace TWRP. I am trying to get the latest update the normal way, by getting the notification I have an update available, and pressing install update now.
danarama said:
By unrooted, lets be clear. The rom must never have been rooted. Unrooting a rom won't work
Click to expand...
Click to collapse
I have never rooted the phone. I updated the phone manually a while back and long story short, I flashed TWRP recovery instead of the stock recovery as I intended to. I just want to revert everything back to stock (which it should be now that I have replaced TWRP with stock recovery)
efrant said:
What is the error?
Click to expand...
Click to collapse
As above, it's picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
efrant said:
What is the error?
You are right, the OTA doesn't check the version of the recovery. However, I can tell you for a fact that on older Nexus devices, using a recovery from a different version of Android would not allow an update to flash. (It is possible this has changed since then though.) I remember very clearly, helping many users troubleshoot (particularly given that the only available toolkit at the time would flash only one generic stock recovery, and not a specific version), and it was confirmed that the errors users were having were due to using a wrong version of the stock recovery, so the recovery version did indeed matter (at least on the Galaxy Nexus it did).
Click to expand...
Click to collapse
I believe it changed for lollipop OTA's. I don't think it had changed for kitKat.
---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------
Clawz114 said:
I press install update now, let the phone reboot and I get the installation screen with the progress bar. It sits at about 10% filled for about 10 seconds then I get the picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
The only thing I flashed was a stock recovery.img, to replace TWRP. I am trying to get the latest update the normal way, by getting the notification I have an update available, and pressing install update now.
I have never rooted the phone. I updated the phone manually a while back and long story short, I flashed TWRP recovery instead of the stock recovery as I intended to. I just want to revert everything back to stock (which it should be now that I have replaced TWRP with stock recovery)
As above, it's picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
Click to expand...
Click to collapse
If you're.familiar with fastboot already, why not just download the full factory image and flash system, boot, bootloader, radio and recovery images?
danarama said:
If you're.familiar with fastboot already, why not just download the full factory image and flash system, boot, bootloader, radio and recovery images?
Click to expand...
Click to collapse
I'm going to have to do just that by the looks of it.
I am fully stock since MRA58K came out. I applied the security update today via the factory images but left user data alone. I am now getting the Corrupt Message during Boot. I accidentally booted TWRP 2.8.7.1 from Fastboot but did not flash it. Just selected reboot. Any Ideas on ways to get rid of it without a factory reset?
what's the exact message?
jj14 said:
what's the exact message?
Click to expand...
Click to collapse
Sorry, I thought it was inherently known with the phrase corrupt during boot. But this with the Red Status
https://support.google.com/nexus/answer/6185381?p=verified_boot
GMoGoody said:
Sorry, I thought it was inherently known with the phrase corrupt during boot. But this with the Red Status
https://support.google.com/nexus/answer/6185381?p=verified_boot
Click to expand...
Click to collapse
So your device is still booting ok . That message shows up if your device is rooted or has some other changes (recovery perhaps).
If you want to stay stock, just reflash the factory images using fastboot (all files skip userdata)
jj14 said:
what's the exact message?
Click to expand...
Click to collapse
jj14 said:
So your device is still booting ok . That message shows up if your device is rooted or has some other changes (recovery perhaps).
If you want to stay stock, just reflash the factory images using fastboot (all files skip userdata)
Click to expand...
Click to collapse
Which I have tried three times and I am still getting this message. The second and third time I tried Flashing MRA58N over itself it did not optimize or anything. I guess I will wait for the next security update, or flash back to MRA58K reboot and try flashing MRA58N again
Did you flash everything? bootloader/boot/recovery/system/radio/cache? (reboot bootloader after flashing radio and bootloader)
flash a custom kernel and it should go away
GMoGoody said:
.>....... the Corrupt Message during Boot. I accidentally booted TWRP 2.8.7.1 from Fastboot but did not flash it. Just selected reboot. Any Ideas on ways to get rid of it without a factory reset?
Click to expand...
Click to collapse
Flash a custom kernel like Franco's kernel
jj14 said:
Did you flash everything? bootloader/boot/recovery/system/radio/cache? (reboot bootloader after flashing radio and bootloader)
Click to expand...
Click to collapse
Yes I flashed everything but the userData even though some things like the radio and bootloader didn't change
Strange. Hopefully somebody else will chime in.
NLBeev said:
Flash a custom kernel like Franco's kernel
Click to expand...
Click to collapse
I want to use android Pay. So I am staying stock. I am trying to figure out why this message suddenly started appearing between MRA58K and MRA58N. If Others are seeing it and potentially how to recover from this state with staying stock but not doing a factory reset. Seems like factory reset may be in order
jj14 said:
Strange. Hopefully somebody else will chime in.
Click to expand...
Click to collapse
My thoughts exactly. When I get home from work I will go back to MRA58K , reboot, then reflash MRA58N. Hopefully this fixes the issue. I will report back tonight. In other threads I saw people were having to go all the way back to 5.1.1 when they saw this when first upgrading to MRA58K
Edit:
This worked. I flashed back to MRA58K, Let it optimize, Verified no corrupt message. then Flashed MRA58N and did the same. So far so good. Also note there is an update to platform-tools in the SDK
GMoGoody said:
I want to use android Pay. So I am staying stock. I am trying to figure out why this message suddenly started appearing between MRA58K and MRA58N. If Others are seeing it and potentially how to recover from this state with staying stock but not doing a factory reset. Seems like factory reset may be in order
Click to expand...
Click to collapse
I think it has to do with TWRP. You used it temporary with fastboot, but it is pushed to the phone's memory. You could try to fastboot flash stock recovery.
SOLVED
I'm getting the same as OP. flashed manually bl/reboot/radio/reboot/system/boot/recovery/cache then tried again with a fresh D/L through Wug's NRT. No joy. Maybe there is something different between the OTA and factory image that would require a data wipe with the latter. Is there an OTA in the wild that I could dissect? Also having bluetooth problems after dirty flashing MRA58N as stated above.
EDIT: Flashed back MRA58K, all is better.
Also noted that after flashing MRA58N the cache didn't rebuild. Hmmm.
SOLUTION: Update platform-tools in your SDK. Just updated and manually dirty flashed, no corrupt message and app cache is rebuilding. :good: