Related
Hey everyone,
Got myself into an interesting situation here. I have the GSM Unlocked Moto X (XT1053) and I'm using it on T-Mobile USA.
I have unlocked the bootloader, installed TWRP (twrp-2.6.3.1-ghost-4.4), SuperSU, Xposed all that jazz. Phone ran wonderfully until I saw the 4.4.2 update zip.
Downloaded the zip, put the phone into fastboot and attempted to flash the stock recovery. I had some trouble finding it and ended up using the one I found here. After doing this the phone started to bootloop, showing the ugly white "WARNING: BOOTLOADER UNLOCKED" screen and then nothing then looped. I put the phone back into fastboot and reflashed TWRP.
Now the phone just bootloops into TWRP. To attempt to remedy this I fixed permissions, wiped cache/Dalvik but to no effect. I can actually successfully boot into Android if I go into fastboot and select the "Factory" option in the menu, however I seem to have lost my service.
So looks like I broke a pretty big rule, don't flash until you know exactly what it was you had- but I got impatient and greedy and now I'm paying the price :victory:.
How can I repair the damage I've done? I don't mind losing data (currently making a backup in Android).
INFO RECAP
XT1053
rooted, bootloader unlocked 30.B2
twrp 2.6.3.1
http://forum.xda-developers.com/showthread.php?t=2477132
[TOOL] Moto X Toolkit v1.3.4 [Backup/Restore,Drivers,Return to stock,Root,Bootani] you could use this to flash back to stock and get a fresh start
Sent from my Nexus 7 using XDA Premium 4 mobile app
sounds like you flashed something that was not a recovery i would return to stock and then follow this guide
http://forum.xda-developers.com/showthread.php?t=2603358
thanks for the replies,
using the toolkit i have more or less fixed everything. however, my stock recovery is borked- it shows no options, just the android recovery background. i am currently downloading the entire firmware here and plan to extract the stock recovery.img to flash with fastboot.
hopefully this will trigger the ota and everything will be as usual from there on.
DarK_MischieF said:
thanks for the replies,
using the toolkit i have more or less fixed everything. however, my stock recovery is borked- it shows no options, just the android recovery background. i am currently downloading the entire firmware here and plan to extract the stock recovery.img to flash with fastboot.
hopefully this will trigger the ota and everything will be as usual from there on.
Click to expand...
Click to collapse
you can't trigger the OTA even if you are root and have a custom recovery you will still get the OTA you just wont be able to install it.
DarK_MischieF said:
thanks for the replies,
using the toolkit i have more or less fixed everything. however, my stock recovery is borked- it shows no options, just the android recovery background. i am currently downloading the entire firmware here and plan to extract the stock recovery.img to flash with fastboot.
hopefully this will trigger the ota and everything will be as usual from there on.
Click to expand...
Click to collapse
Check this video for booting stock recovery it's kinda tricky yours might not be borked http://www.youtube.com/watch?v=kjNXkRtEQlo&list=PL0V3YBytQ2FudO8sUC_EHgdMqUB_tVb8d
jmcdonald58 said:
Check this video for booting stock recovery it's kinda tricky yours might not be borked http://www.youtube.com/watch?v=kjNXkRtEQlo&list=PL0V3YBytQ2FudO8sUC_EHgdMqUB_tVb8d
Click to expand...
Click to collapse
Thanks for the video, you were correct, my recovery is working as intended. To actually activate the options in the stock recovery you need to hold the Volume up button and press the Power button.
4.4.2 sideloaded successfully, nothing noteworthy for my personal use- wasn't there mention of the Google dialer in a Canadian update release notes?
DarK_MischieF said:
Thanks for the video, you were correct, my recovery is working as intended. To actually activate the options in the stock recovery you need to hold the Volume up button and press the Power button.
4.4.2 sideloaded successfully, nothing noteworthy for my personal use- wasn't there mention of the Google dialer in a Canadian update release notes?
Click to expand...
Click to collapse
I am note sure I usually just use the search feature or google now when looking I have a Nexus 5 I rarely use the dialer but it is nice to have seems like it would be available
I recently followed this guide to root my XT1095. All I did was unlock my bootloader and boot the image...I did not (intentionally) alter my recovery, nor did I install a custom ROM. Will I still receive OTA update notifications and, if so, are they safe to apply?
Dan Again said:
I recently followed this guide to root my XT1095. All I did was unlock my bootloader and boot the image...I did not (intentionally) alter my recovery, nor did I install a custom ROM. Will I still receive OTA update notifications and, if so, are they safe to apply?
Click to expand...
Click to collapse
If you are running a custom recovery TWRP for example, I doubt that you will get OTA updates. I believe you need the stock recovery to be able to install OTA updates.
grneyez said:
If you are running a custom recovery TWRP for example, I doubt that you will get OTA updates. I believe you need the stock recovery to be able to install OTA updates.
Click to expand...
Click to collapse
I'm a little confused by your response. As I said in my original question, I did not (intentionally) alter my recovery. Did the method that I used achieve root alter my recovery for me?
If you did not install a custom recovery than you should be able to get OTA updates. Check to see what recovery you have.
Dan Again said:
I'm a little confused by your response. As I said in my original question, I did not (intentionally) alter my recovery. Did the method that I used achieve root alter my recovery for me?
Click to expand...
Click to collapse
As long as you don't make any changes to /system, you *should* be good to go for updates. If you didn't intentionally flash a custom recovery then you still have the stock one.
If you're rooted OTAs won't work. In KitKat and lower they just performed checksums on each file before updating, so the altered root files were left untouched and the update installed. In Lollipop and up (at least for Nexus devices), it does a total checksum and if /system has been altered in any way (including for root) OTA's won't install.
grneyez said:
If you did not install a custom recovery than you should be able to get OTA updates. Check to see what recovery you have.
Click to expand...
Click to collapse
Thanks for all the responses, guys. I booted into recovery and saw this, so I think my recovery is still stock. One quick question: when I boot into fastboot and select "Recovery", I get a dead Android and a "No Command" prompt - I had to follow these steps to actually get there. Why is that?
I'd like to try out Xposed now that it's available for my device, and I see that requires a custom recovery. If I install a custom recovery (TWRP, for instance) and use it to flash Xposed, can I then revert back to stock recovery and continue to receive OTA updates?
Dan Again said:
Thanks for all the responses, guys. I booted into recovery and saw this, so I think my recovery is still stock. One quick question: when I boot into fastboot and select "Recovery", I get a dead Android and a "No Command" prompt - I had to follow these steps to actually get there. Why is that?
I'd like to try out Xposed now that it's available for my device, and I see that requires a custom recovery. If I install a custom recovery (TWRP, for instance) and use it to flash Xposed, can I then revert back to stock recovery and continue to receive OTA updates?
Click to expand...
Click to collapse
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
juliospinoza said:
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
Click to expand...
Click to collapse
Fair enough. So let's say that I install a custom recovery and then Xposed. Will there be a way that I can manually upgrade to new stock OS versions as they come out for my phone?
Dan Again said:
Fair enough. So let's say that I install a custom recovery and then Xposed. Will there be a way that I can manually upgrade to new stock OS versions as they come out for my phone?
Click to expand...
Click to collapse
You can always flash a ROM or custom ROM via fast boot, but you will loss all your settings, apps etc because you are flashing an entire new system... The OTA only patches
The only way back is to flash your stock ROM if you can get a hold of it.
floepie said:
The only way back is to flash your stock ROM if you can get a hold of it.
Click to expand...
Click to collapse
So, funny story - this weekend I accidentally wiped my OS and had to flash stock ROM to get back up and running. See: here. Good resource for others who might be looking for Moto X 2014 stock Lollipop firmware...definitely saved that on my computer
juliospinoza said:
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
Click to expand...
Click to collapse
Isn't there any way to uninstall Xposed, revert back to original recovery and remove root--all in order to install OTA without completely loosing user data and apps installed?
yurkennis said:
Isn't there any way to uninstall Xposed, revert back to original recovery and remove root--all in order to install OTA without completely loosing user data and apps installed?
Click to expand...
Click to collapse
yes
just flash via fastboot
1. recovery (stock)
2. system
if your phone is 5.0 xt1095 and you didn't flash modems you should be able to receive OTA.
Repeat of Question
I'm not sure I completely understand what I need to do to get updated to 5.1. I have an XT1095 that I only rooted, no custom recovery. I downloaded the OTA for 5.1 last night and tried to update. Got an error and it did not update. A quick google search seems to state, as well as earlier in this thread, that I can not update if I am rooted. I would prefer not completely start over on my phone (wipe) and would like to just apply the update. Can I just "unroot" my phone and apply the update or do I have to go back to the beginning (with a stock recovery) before the update will take?
I know enough about all this to have followed the directions to accomplish the root about 7 months ago. Since then not played with any system files! The only reason I rooted was so I could use the full capabilities of Greenify. Any opinions on that would be appreciated as well. Thanks!
jhworth8 said:
I'm not sure I completely understand what I need to do to get updated to 5.1. I have an XT1095 that I only rooted, no custom recovery. I downloaded the OTA for 5.1 last night and tried to update. Got an error and it did not update. A quick google search seems to state, as well as earlier in this thread, that I can not update if I am rooted. I would prefer not completely start over on my phone (wipe) and would like to just apply the update. Can I just "unroot" my phone and apply the update or do I have to go back to the beginning (with a stock recovery) before the update will take?
I know enough about all this to have followed the directions to accomplish the root about 7 months ago. Since then not played with any system files! The only reason I rooted was so I could use the full capabilities of Greenify. Any opinions on that would be appreciated as well. Thanks!
Click to expand...
Click to collapse
Try reading, the post literally before yours tells you what to do, lol.
Sent from my XT1095 using Tapatalk
AGISCI said:
Try reading, the post literally before yours tells you what to do, lol.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I take it that flashing the recovery and the system.img files to the phone will not erase all the apps, photos, music, etc.?
summit15 said:
I take it that flashing the recovery and the system.img files to the phone will not erase all the apps, photos, music, etc.?
Click to expand...
Click to collapse
Correct, it won't erase those things.
Sent from my XT1095 using Tapatalk
so if i am just rooted, and custom recovery, could I unroot (via supersu app) and flash stock recovery and be good to go? or am i missing something?
yamahakid said:
so if i am just rooted, and custom recovery, could I unroot (via supersu app) and flash stock recovery and be good to go? or am i missing something?
Click to expand...
Click to collapse
It's more difficult with Lollipop: updates now "look for" a completely stock unmodified unrooted system. So you'll have to flash a stock image of the current build and then take the OTA.
I am 100% stock.
I did the update using Minimal ABD and Fastboot. Once that was finished, the phone booted up (after optimizing all my apps) and gave me a System UI error and would never get past that (even if I hit OK or Report). I turned it off and then went it came back on, it went straight to the Google Logo. It didn't even vibrate like it usually does when it boots up.
If I hold down all 3 buttons, it will boot to the bootloader screen, but anything I do from there, just goes back to the Google logo and that's it. I had to go to Recovery and get another error, then hit power + volume up, and I did a factory wipe. However, after that, it still does the same thing. Goes to the Google Logo and nothing else. I've wiped it a few times now and no luck.
Any suggestions on what to do?
Which ROM did you flash? There is no 5.1 factory image at the moment. If you are flashing through ADB, try manually erasing then flashing each file first instead of using flash-all. Don't forget to flash userdata.
edit: Didn't realize update file was sent out through OTA. Try flashing factory 5.0.1 then flash the update which is in the cache folder. Extract and save that 5.1 OTA file somewhere else before flashing 5.0.1, if not its gone. Best suggestion is to wait go back to 5.0.1 and wait for 5.1 factory image.
DevilMR said:
Which ROM did you flash? There is no 5.1 factory image at the moment. If you are flashing through ADB, try manually erasing then flashing each file first instead of using flash-all. Don't forget to flash userdata.
Click to expand...
Click to collapse
Sorry, no ROM, just the OTA.zip I tried. I used it from here: (can't link) but AndroidPolice FLASH ALL THINGS post
mikebio said:
Sorry, no ROM, just the OTA.zip I tried. I used it from here: (can't link) but AndroidPolice FLASH ALL THINGS post
Click to expand...
Click to collapse
Most likely going to have to download the 5.0.1 factory image and reflash that if you didn't make a backup before doing the OTA.
I'm assuming you don't have a 3rd party recovery since your title says "STOCK" correct?
meest said:
Most likely going to have to download the 5.0.1 factory image and reflash that if you didn't make a backup before doing the OTA.
I'm assuming you don't have a 3rd party recovery since your title says "STOCK" correct?
Click to expand...
Click to collapse
This is correct. I also can't get my computer to recognize my Nexus anymore. Any tips on that?
OK, i see what you did. Try flashing factory 5.0.1, then flash that 5.1 update. I rather wait for factory 5.1.
DevilMR said:
OK, i see what you did. Try flashing factory 5.0.1, then flash that 5.1 update. I rather wait for factory 5.1.
Click to expand...
Click to collapse
Will do. Do you know the exact USB driver I need for nexus 6? When I plug it into my computer now, it comes up Shamu and I can't get the phone to be recognized by Nexus Root Toolkit or Minimal ADB & Fastboot
Nevermind, got it... I am going to reflash factory image... I tried 5.0.1 and it failed.
mikebio said:
Will do. Do you know the exact USB driver I need for nexus 6? When I plug it into my computer now, it comes up Shamu and I can't get the phone to be recognized by Nexus Root Toolkit or Minimal ADB & Fastboot
Click to expand...
Click to collapse
If I remember right I just downloaded the google driver pack and pointed windows to that directory and it found one.
http://developer.android.com/sdk/win-usb.html
meest said:
If I remember right I just downloaded the google driver pack and pointed windows to that directory and it found one.
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
The issue is, it comes up Fastboot Shamu and it isn't recognized. Only when I put in into Apply update from ADB does it show up Nexus 6 on Windows... Not sure what to do. I can't flash right now because of this.
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.
My nexus 6 is soft bricked I'm assuming, I can't get past the 6.0.1 boot up screen it just keeps on booting . The device is unlocked with TWRP recovery but not rooted as far as I know it's not rooted. The only way I can check MTP is through twrp but it's showing an exclmation point in device mgr. I'm in wugs toolkit now under Advanced Utilities, before I got the boot logo it had the you're device is corrupt. I fixed the corrupt message by putting my device in boot loader mode and in Advanced Utilities under fastboot flash then I clicked Boot [Kernel] I flashed the stock kernel and that got rid of the corrupt device warning screen. I'm gonna try flashing a modified boot img next but I'm having trouble. I just need someone to stick with me for awhile and help me fix this thing because I gotta return it and I don't have long.
Sent from my HTC6600LVW using Tapatalk
Ok now I have the corrupt device message back again.
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
My nexus 6 is soft bricked I'm assuming, I can't get past the 6.0.1 boot up screen it just keeps on booting . The device is unlocked with TWRP recovery but not rooted as far as I know it's not rooted. The only way I can check MTP is through twrp but it's showing an exclmation point in device mgr. I'm in wugs toolkit now under Advanced Utilities, before I got the boot logo it had the you're device is corrupt. I fixed the corrupt message by putting my device in boot loader mode and in Advanced Utilities under fastboot flash then I clicked Boot [Kernel] I flashed the stock kernel and that got rid of the corrupt device warning screen. I'm gonna try flashing a modified boot img next but I'm having trouble. I just need someone to stick with me for awhile and help me fix this thing because I gotta return it and I don't have long.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
If TWRP is installed there's no problem. Just a matter of the pc let recognize the device. Quit the toolkits though!
Do you have google drivers installed? Once they are installed your device should be recognized and you can copy any of the fine roms that can be found here.
Droidphilev said:
If TWRP is installed there's no problem. Just a matter of the pc let recognize the device. Quit the toolkits though!
Do you have google drivers installed? Once they are installed your device should be recognized and you can copy any of the fine roms that can be found here.
Click to expand...
Click to collapse
I need a lot of help installing the drivers.
Sent from my HTC6600LVW using Tapatalk
Like I said I now have the corrupt device message back instead of the 6.0.1 boot logo. I tried flashing the stock img file and the stupid corrupt screen came back. Ok I'm just craps out luck I guess,
Sent from my HTC6600LVW using Tapatalk
Ok I have what says is the latest Google usb drivers which was Aug 2015 downloaded. On my device I'm using I'm gonna transfers the drivers to my pc now, and attempt to install them. I hope this works and fixes my device. I sat in front of my pc yesterday for 7 hrs trying to fix this stupid phone.
Sent from my HTC6600LVW using Tapatalk
the corrupt device message is only there because you have twrp and a stock kernel. flash a custom kernel.
It's fixed, everything is running as it should no boot loops or corrupt screen, now I gotta check to see if recovery is gone. I used wugs to flash stock 6.0.1
Sent from my HTC6600LVW using Tapatalk
I used to have the corrupt message also, but it would go away and boot just fine. Started when I had TWRP. As someone mentioned, if this is a really annoyance, just flash a custom kernel . Though mine went away when I rooted with SuperSU (which patches the kernel I think)
Tower1972 said:
I used to have the corrupt message also, but it would go away and boot just fine. Started when I had TWRP. As someone mentioned, if this is a really annoyance, just flash a custom kernel . Though mine went away when I rooted with SuperSU (which patches the kernel I think)
Click to expand...
Click to collapse
I used wugs toolkit to flash back to complete stock it worked my device is running as normal, but when I power of the device and power it back on the corrupt message then disappears and boots right up. When I boot into boot loader mode and boot recovery it shows the green android robot laying down. After I flashed back to stock 6.0.1 it got rid of twrp and root but I'm still unlocked . The unlocked part I'm not worried about. In order to fix this do I have to 're root and flash twrp all over again or is there an easier way. I need step by step, on how to get rid of the corrupt message. Example, like when someone says flash img to me that's about as clear as mud.....
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I used wugs toolkit to flash back to complete stock it worked my device is running as normal, but when I power of the device and power it back on the corrupt message then disappears and boots right up. When I boot into boot loader mode and boot recovery it shows the green android robot laying down. After I flashed back to stock 6.0.1 it got rid of twrp and root but I'm still unlocked . The unlocked part I'm not worried about. In order to fix this do I have to 're root and flash twrp all over again or is there an easier way. I need step by step, on how to get rid of the corrupt message. Example, like when someone says flash img to me that's about as clear as mud.....
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
flash twrp then when you root, flash a custom kernel as well, that will get rid of the message.
Anybody here?
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
Anybody here?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
me. well not here, but in nyc. here in spirit though
simms22 said:
me. well not here, but in nyc. here in spirit though
Click to expand...
Click to collapse
I'm trying to get my brain working,lol my device is stock unrooted without twrp but the corrupt message still shows up I gotta get this fixxed. It's hard for me to understand what all I need to do. All I need is the corrupt message to go away and I'll be good. At start up it shows the corrupt message, but a few seconds later it goes away and it boots up normally.
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I'm trying to get my brain working,lol my device is stock unrooted without twrp but the corrupt message still shows up I gotta get this fixxed. It's hard for me to understand what all I need to do. All I need is the corrupt message to go away and I'll be good. At start up it shows the corrupt message, but a few seconds later it goes away and it boots up normally.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
i believe that your bootloader is unlocked, thats why its showing up on a non rooted n6. you can lock your bootloader(i wouldnt, you can have problems later) or you can flash twrp recovery, then a custom kernel, and you dont need to root it for that.
simms22 said:
i believe that your bootloader is unlocked, thats why its showing up on a non rooted n6. you can lock your bootloader(i wouldnt, you can have problems later) or you can flash twrp recovery, then a custom kernel, and you dont need to root it for that.
Click to expand...
Click to collapse
If I flash the kernel with twrp it's gotta be a zip? Is there anyway that you can link me to stock 6.0.1 kernel
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
If I flash the kernel with twrp it's gotta be a zip? Is there anyway that you can link me to stock 6.0.1 kernel
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
a stock twrp flashable, then theres no zip version of it available. BUT twrp can also flash .img kernels as well. if you have the factory image available, you can unzip it and just flash the boot.img in twrp(or fastboot). but why the stock kernel?? if you just want stock, id recommend just fastboot flashing the boot.img from the factory image. boot.img is the kernel.
simms22 said:
a stock twrp flashable, then theres no zip version of it available. BUT twrp can also flash .img kernels as well. if you have the factory image available, you can unzip it and just flash the boot.img in twrp(or fastboot). but why the stock kernel?? if you just want stock, id recommend just fastboot flashing the boot.img from the factory image. boot.img is the kernel.
Click to expand...
Click to collapse
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
nope. the kernel is what connects the operating system(software) to the hardware and also serves as the devices main "brain"
---------- Post added at 05:10 PM ---------- Previous post was at 05:08 PM ----------
mwebb34 said:
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
just download the factory image, then grab the boot.img out of it. link to the 6.0.1 factory image https://dl.google.com/dl/android/aosp/shamu-mmb29k-factory-9a76896b.tgz
simms22 said:
nope. the kernel is what connects the operating system(software) to the hardware and also serves as the devices main "brain"
Click to expand...
Click to collapse
Ok, with no twrp recover when I boot into boot loader mode and then boot into recovery mode what should I see come up on the screen?
Sent from my HTC6600LVW using Tapatalk