Related
First of all I just bought Global Moto G 2014 (XT1063) from US Amazon and that was KXH21.85-23 (not updatable to Lollipop via shared OTA.)
So I did manage to unlocked the bootloader and flashed KXH21.85-17 and tried to flash the "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US" which supposed to flash the Lollipop.
Unfortunately at first it failed to update me because "Printspooler.apk" mismatch the hash check. After attempt to flash (yes, I ignore the abort message and redo the process, It passed.... I don't know why) and stuck at some "xxx.apk" mismatch the hash again. After redo the process and bypass (for unknown reason that redo bypass the mismatch) I stuck at "velvet.apk" mismatch and this time It won't let me bypass and keep going on update to lollipop.
In my theory, Is it possible that I flash KXH21.85-17 from other country? Yes, any XT1063 (latin american, whereever on earth) supposed to flashable, but maybe the different country has slightly different apk. So that's why I failed the hash check.
Can anyone give me a URL or mirror to USA XT1063 for KXH21.85-17 that confirmed updatable to Lollipop? Since SBF-Dev and MotoFirmware is now down I couldn't find any.
I know what I'm saying is sound ridiculous, but I have no other theory that support my conspiracy anymore.
Hi @bankkung, I was facing similar problems. First you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!
Lamech242 said:
Hi @bankkungFirst you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
Click to expand...
Click to collapse
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
Lamech242 said:
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!
Click to expand...
Click to collapse
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?
bankkung said:
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?
Click to expand...
Click to collapse
Yes once you place the backup on your SD card, flash TWRP, reboot into recovery and go to advanced then go to file manager, then finish following the instructions above. Once you place it in the right place then you restore it. As of the stock recovery issue, it wouldn't make much sense to do that unless you followed the first option, where the stock recovery would actually be needed. But if you find a recovery image then yeah. If you do the second method you won't be able to receive updates nor update it manually unless doing the first method.. But the TWRP backup is the latest lollipop so enjoy!
If you still need help you can just flash TWRP recovery, and download this and flash it. http://forum.xda-developers.com/mot...-stock-rom-t2970427/post57438355#post57438355
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.
How to flash Android M, TWRP, & SuperSU with out getting red corrupt triangle @ boot?
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks
I wonder the same thing. I tried to get rid of the red triange but it's impossible. I've tried a full wipe and flash everything from stock but no dice.
Also i'm unable to boot to recovery. It just freezes... Same thing if I flash back the 5.1.1 image. TWRP is working though.
Any ideas?
Does anyone have a solution to get rid of the triangle WITHOUT twrp or root? I flashed TWRP to see if I could install a custom HOSTS file and the message started popping up on boot, but even after reflashing everything from the official M image and wiping data and cache it still pops up. Any suggestions? o_o
Did you flash userdata too? Tried factory reset on top?
pszyman said:
Did you flash userdata too? Tried factory reset on top?
Click to expand...
Click to collapse
I formatted userdata because I have a 64GB device and the userdata image included is for 32GB. this is what I did without the file names because I'm mobile:
Code:
Fastboot flash bootloader mboot.img
Fastboot reboot-bootloader
Fastboot flash mradio.img
Fastboot flash system msystem.img
Fastboot flash boot mboot.img
Fastboot flash recovery mrecovery.img
Fastboot format userdata
Fastboot format cache
And then I booted and got the device corrupt message. I did all of that a few times to make sure I didn't miss anything and I have no idea what it's detecting as modified. I haven't tried factory resetting from the device itself, I figured formatting userdata would be enough but ill try that tomorrow unless anyone has other ideas.
I had this same issue today too after I flashed twrp. The only way to resolve it was to flash stock and unroot using nexus toolkit to a lollipop stock image. In time I'm sure it will be a smoother process to go to android m with twrp and root, but until then, I'm sticking with lollipop.
Sent from my Nexus 6 using Tapatalk
530farm said:
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks
Click to expand...
Click to collapse
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.
Well, the issue is this corrupted message stays even after the full stock reinstall. Some say it went away after the factory reset but returned back after a while later, after spontaneous reboot or so.
thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks
What I've done to get back to stock was - flash clean image and next factory reset. No corrupted message. So far so good.
I believe to get rid of it...you will have to lock and unlock bootloader again...which will factory reset in the process. Hopefully someone finds a workaround for a factory reset...I am going to continue to run it with the error message until someone does. I dont want to factory reset. The message doesnt cause any issues to my knowledge...its just a warning to the user.
dansoh said:
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.
Click to expand...
Click to collapse
kidhudi said:
thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks
Click to expand...
Click to collapse
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
inspiron41 said:
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
Click to expand...
Click to collapse
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.
I flashed the kernel from here http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958 and it went away.
PhantomGamers said:
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.
Click to expand...
Click to collapse
Custom kernels that have the flag edited out will will get rid of the Corrupt message.
djkinetic said:
Custom kernels that have the flag edited out will will get rid of the Corrupt message.
Click to expand...
Click to collapse
I guess I'll have to resort to that if factory resetting doesn't fix it, sucks though cuz I would have been happy with stock.
Phone happily running 7.0.0 (NBD90Z, Oct 2016)
Running system less super su SR3 and Franco #57
Downloaded and fast boot flashed the latest November update from PC.
Only flashed updated bootloader and system image from 7.0.0 (NBD91P, Nov 2016)
Restarted Phone and it loops at boot animation, left for twenty minutes, no progress, so rebooted back to recovery and tried wiping, cache, dalvik and art cache, and restarted again still no difference, looped at boot animation again for twenty minutes.
So rebooted to recovery and restored October backup.
Was anyone else and to fast boot flash latest factory system image and boot their phone without any issues?
Is a full wipe really necessary?
Any one?
Sent from my Shamu using Tapatalk
ben_pyett said:
Phone happily running 7.0.0 (NBD90Z, Oct 2016)
Running system less super su SR3 and Franco #57
Downloaded and fast boot flashed the latest November update from PC.
Only flashed updated bootloader and system image from 7.0.0 (NBD91P, Nov 2016)
Restarted Phone and it loops at boot animation, left for twenty minutes, no progress, so rebooted back to recovery and tried wiping, cache, dalvik and art cache, and restarted again still no difference, looped at boot animation again for twenty minutes.
So rebooted to recovery and restored October backup.
Was anyone else and to fast boot flash latest factory system image and boot their phone without any issues?
Is a full wipe really necessary?
Any one?
Sent from my Shamu using Tapatalk
Click to expand...
Click to collapse
I flashed NBD91P without a full wipe and my phone booted without any issues. However I have not been able to get su SR2 or su SR3 to work with either NBD90Z or NBD91P. SR1 works without any issues.
I flashed bootloader, boot and system without a problem. Also using FK, but have magisk+phh root.
I've seen a few people mentioning having problems with SuperSU 2.78 SR2 and SR3 and the latest update (NBD91P)
"Only flashed updated bootloader and system image"
I'm genuinely puzzled as to why people aren't using the OTA sideload method, which is incredibly simple and leaves your data and settings totally intact.
The quote above makes me think "You did half a job and now wonder why your phone won't work...?"
dahawthorne said:
I'm genuinely puzzled as to why people aren't using the OTA sideload method, which is incredibly simple and leaves your data and settings totally intact.
The quote above makes me think "You did half a job and now wonder why your phone won't work...?"
Click to expand...
Click to collapse
You didn't read the post completely, as my phone is working as I always make the precaution of taking a backup and simply restored to it.
I didn't think ota method was possible if you had custom recovery?
Using the method I've described also leaves data and settings in tact.
I didn't run the flash all scripts.
Thanks
Sent from my Shamu using Tapatalk
No offence intended. I have never (touch wood) had any serious problems with my many upgrades on many devices. As you did, I always have a backup in case it goes wrong. In fact I even have multiple backups on my laptop in case the latest one doesn't work.
I've use the OTA sideload method a dozen times now on all my rooted Nexus devices. All of them as standard have TWRP & root (either doitright's or Chainfire's), and the OTA just slides right in there regardless. No problems at all. When it's installed (which takes about five minutes) I have to reroot - I can't remember if I've had to reinstall TWRP, though on a number of occasions I've just reinstalled it anyway without bothering to check if it was already still there.
So in summary the OTA sideload works for rooted/TWRPed devices, doesn't lose anything, and is far simpler and safer than running separate partition flashes. Give it a go and I guarantee you'll never do it the old way again.
dahawthorne said:
No offence intended. I have never (touch wood) had any serious problems with my many upgrades on many devices. As you did, I always have a backup in case it goes wrong. In fact I even have multiple backups on my laptop in case the latest one doesn't work.
I've use the OTA sideload method a dozen times now on all my rooted Nexus devices. All of them as standard have TWRP & root (either doitright's or Chainfire's), and the OTA just slides right in there regardless. No problems at all. When it's installed (which takes about five minutes) I have to reroot - I can't remember if I've had to reinstall TWRP, though on a number of occasions I've just reinstalled it anyway without bothering to check if it was already still there.
So in summary the OTA sideload works for rooted/TWRPed devices, doesn't lose anything, and is far simpler and safer than running separate partition flashes. Give it a go and I guarantee you'll never do it the old way again.
Click to expand...
Click to collapse
Do you change, or alter you system partition, ie remove application or add some.
I'm asking if an ota will apply over the top of an altered system?
If so I'll try it once I've finished work.
Although will also rule out the version of super su first.
Sent from my Shamu using Tapatalk
I change nothing. My N6 is rooted and TWRPed and I just connect to the computer and use ADB to sideload the OTA. It says "flashing unconditionally" so I'm guessing (I'm just an end-user, not a dev) that the OTA just wipes the old ROM and overwrites it, but doesn't touch the data partition. Since the system partition is replaced, root disappears with it, but I'm not sure if it touches TWRP - as I said, I just reinstall it anyway each time and then use it to flash SuperSU.
Give it a go - you'll like it...
P.S. I understand that the OTA has some sort of internal checksum to verify the package integrity, but I always double-check my download with Checksum Utility:
https://raylin.wordpress.com/downloads/md5-sha-1-checksum-utility/
dahawthorne said:
I change nothing. My N6 is rooted and TWRPed and I just connect to the computer and use ADB to sideload the OTA. It says "flashing unconditionally" so I'm guessing (I'm just an end-user, not a dev) that the OTA just wipes the old ROM and overwrites it, but doesn't touch the data partition. Since the system partition is replaced, root disappears with it, but I'm not sure if it touches TWRP - as I said, I just reinstall it anyway each time and then use it to flash SuperSU.
Give it a go - you'll like it...
P.S. I understand that the OTA has some sort of internal checksum to verify the package integrity, but I always double-check my download with Checksum Utility:
https://raylin.wordpress.com/downloads/md5-sha-1-checksum-utility/
Click to expand...
Click to collapse
So flashed, ota through flash fire, worked as described.
As expected phone booted, with stock kernel, recovery and no root.
So rebooted to bootloader and had to re fast boot flash twrp recovery.
But then flashed systemless super su and Franco kernel, phone no longer boots.
Restored backup as ran out of time.
Will try again tonight with our systemless, which root version and methods are you using?
I'll try just kernel and then just root to see which it is that's causing the problem
Progress.
Although to be honest, I'm still of the opinion that flashing just system partition is a far simpler, process then ota.
This is the first time in a a good few years and multiple nexus/android versions, where I've ever had an issue with this process. (And I've had N4, N5 and N6)
Anyone?
Thanks
Sent from my Shamu using Tapatalk
Maybe you're trying too much all at once? I installed the OTA, TWRP and SuperSU 2.78 R3 with no problems - I have tried a couple of custom kernels but saw no appreciable difference, so decided that I'd avoid the risk of tinkering with stuff I don't understand.
Maybe there's some incompatibility with the Franco kernel? I know that SuperSU performs some processing on the kernel - it shows in the installation dialogue.
The more Google locks down android the harder it will be so people need to make a choice and live with it. Either you want the pointless OTA or you are gonna use a custom set up. Not flashing an update properly and then posting a thread about it only makes developers laugh.
zelendel said:
The more Google locks down android the harder it will be so people need to make a choice and live with it. Either you want the pointless OTA or you are gonna use a custom set up. Not flashing an update properly and then posting a thread about it only makes developers laugh.
Click to expand...
Click to collapse
Why do you say he didn't flash the update properly? I thought the only difference between NBD90Z and NBD91P was the bootloader and system images. There was no new recovery, radio, etc... included in that release. So what's the harm in only updating the bootloader/system partitions?
If you did it the "right way" I guess that would be running the flash-all.bat file in the folder. All that does is flash all the partitions (which is dumb because you're overwriting the same partitions which is completely unnecessary if you already have them) and wipe userdata. With his method userdata would've stayed intact.
Please note I never do this method, I'm a custom ROM man thru and thru. Whether it's Dirty Unicorns, AOSiP, OctOS, etc... I never run factory system images because even though with GravityBox you can get a lot of customization, I still prefer CMTE over Substratum/OMS. No way to get CMTE in stock firmware.
dahawthorne said:
Maybe you're trying too much all at once? I installed the OTA, TWRP and SuperSU 2.78 R3 with no problems - I have tried a couple of custom kernels but saw no appreciable difference, so decided that I'd avoid the risk of tinkering with stuff I don't understand.
Maybe there's some incompatibility with the Franco kernel? I know that SuperSU performs some processing on the kernel - it shows in the installation dialogue.
Click to expand...
Click to collapse
Finally managed it.
Fastboot Flashed system
Fastboot Flashed stock boot
Went in to recovery
Flashed Franco
Booted rom
Went back to recovery
Flashed update-unSU (unsure is this stage is needed, but was taking no chances)
Flashed super su
Was finally able to boot rom
Seems combination of super su and Franco wouldn't work in single flash for me. Needed clean reboot between each.
Although I still believe that fast boot flash system is easiest method rather than ota, as doesn't affect recovery or boot partitions and you stay in control, each to their own.
This is the first time I've encountered any issues with this method.
Comments suggesting I didn't do it properly without highlighting what, if anything I did wrong or without adding any positive feedback are worthless.
Thanks for input and suggestions.
Sent from my Nexus 6 using Tapatalk
I had very similar issues. I've been updating this phone monthly since day 1 without issue but with the NBD91P update, I got the same boot loop even with the stock kernel. My device is also encrypted.
After I booted back to the bootloader I noticed that TWRP was gone. I found that very odd. It was like the system image was trying to write over it. Not sure though, but I do know that I had to re-flash TWRP (I've had the same version, which is also the latest one, for months) after every boot loop.
I kept re-flashing and trying different versions of the systemless versions of SuperSU but none of them worked. Got stuck in the same boot loop everytime.
I finally re-flashed everything except for SuperSU and stock NBD91P booted up fine without root.
I'm also having the same issue. I can't even flash SR1. Any update on this?
I can't not boot the NBD91P factory image if I have any layers installed. Removing that overlay folder via TWRP is the only way to make it boot again.
LordDeath said:
I can't not boot the NBD91P factory image if I have any layers installed. Removing that overlay folder via TWRP is the only way to make it boot again.
Click to expand...
Click to collapse
There is a bug in this update which causes a bootloop if the system is themed. Restore to NBD90Z.
msaitta said:
I had very similar issues. I've been updating this phone monthly since day 1 without issue but with the NBD91P update, I got the same boot loop even with the stock kernel. My device is also encrypted.
After I booted back to the bootloader I noticed that TWRP was gone. I found that very odd. It was like the system image was trying to write over it. Not sure though, but I do know that I had to re-flash TWRP (I've had the same version, which is also the latest one, for months) after every boot loop.
I kept re-flashing and trying different versions of the systemless versions of SuperSU but none of them worked. Got stuck in the same boot loop everytime.
I finally re-flashed everything except for SuperSU and stock NBD91P booted up fine without root.
Click to expand...
Click to collapse
collinjames said:
I'm also having the same issue. I can't even flash SR1. Any update on this?
Click to expand...
Click to collapse
LordDeath said:
I can't not boot the NBD91P factory image if I have any layers installed. Removing that overlay folder via TWRP is the only way to make it boot again.
Click to expand...
Click to collapse
I was able to get over my own original problem using the process listed a few posts above, in my previous comment.
Even though it took several attempts to determine a working sequence. Did you try the process which worked for me on your devices?
Strephon Alkhalikoi said:
There is a bug in this update which causes a bootloop if the system is themed. Restore to NBD90Z.
Click to expand...
Click to collapse
Can't comment as my system wasn't themed.
Does the boot loop occur, if you, remove your themes then upgrade to latest image, reboot it and finally reapply your layers?
Sent from my Nexus 6 using Tapatalk
Dopamin3 said:
Why do you say he didn't flash the update properly? I thought the only difference between NBD90Z and NBD91P was the bootloader and system images. There was no new recovery, radio, etc... included in that release. So what's the harm in only updating the bootloader/system partitions?
Click to expand...
Click to collapse
He said, quote:
Only flashed updated bootloader and system image from 7.0.0 (NBD91P, Nov 2016)
Click to expand...
Click to collapse
Unless you have the diffs from the Android git, you can't decide if flashing boot necessary or not. And even then you can decide wrong.
The whole package is: bootloader, radio, boot, system, (vendor in case of the 6P), recovery, and the clutter.
You should skip data, and shouldn't bother with the cache partition, but it's a good idea clearing it after flashing a new system. You can always check if the bootloader and radio have changed, you can diff them if you don't believe the version numbers.
That leaves boot and system, you should always flash both, even if it goes by the nuisance of re-rooting.
Also if you're unencypted, as I am, then after flashing boot, you should not reboot without flashing a root that deals with it.
(But making an unencrypted and verity-less boot is five minutes tops, by the way)
Strephon Alkhalikoi said:
There is a bug in this update which causes a bootloop if the system is themed. Restore to NBD90Z.
Click to expand...
Click to collapse
Having the lastest security fixes is more important than themes.
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Um, i think ur in the wrong category
thejacer87 said:
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps ...
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is?
Click to expand...
Click to collapse
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Fatal_Scythe said:
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Click to expand...
Click to collapse
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
thejacer87 said:
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Click to expand...
Click to collapse
If you're planning to go back to stock MIUI and locked bootloader, I highly recommend using Mi Flash and flashing the original fastboot MIUI ROM which can be found here https://www.xda-developers.com/download-miui-11-xiaomi-redmi-note-7-pro-poco-f1/amp/. All you gotta to do is extract the ROM file which is .tgz to any folder, and in Mi Flash select that folder click on "clean all and lock" in the bottom right corner, and click flash. This should theoretically make your device "out of the box".
Keep in mind that this method requires a PC with all ADB and fastboot drivers, they can be downloaded from here https://forum.xda-developers.com/showthread.php?t=2588979 .
thejacer87 said:
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
Click to expand...
Click to collapse
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Fatal_Scythe said:
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Click to expand...
Click to collapse
just got gpay to work with the sql fix. thanks for the help