Database Develop

[Q] CM KFHD 7 was stable 5 months, now stuck at blue "Kindle" logo??

Hey everyone, first time caller, long time listener here. Apologies for the long post but I figured I'd rather provide all the details upfront.
I've had a KFHD 7" for about a year now and have been lurking around the KFHD dev forums ever since, anxiously awaiting ROM's made available for the 7. Finally in July I took the plunge, and using KFFA, downgraded to stock Kindle OS 7.2.3 and followed opensystem's thread here (http://forum.xda-developers.com/showthread.php?t=2347170) on using FireFlash to install kfhd7-Freedom-boot-7.3.0.img as the bootloader and kfhd7-twrp 2.4.4.0-recovery.img as the recovery. Success and all was beautiful!
Since then I've:
* Updated TWRP to version 2.5.0 via Hashcode's ZIP within TWRP
* Updated CM to version 10.2 (8/12/2013 build)
* Reverted CM to version 10.1 (had stability problems)
* Updated TWRP to version 2.6.3.0 via Hashcode's ZIP within TWRP
* Updated CM to version 10.2 (11/15/2013 build)
* Updated TWRP to version 2.6.3.1 via Hashcode's ZIP within TWRP
All this succeeded, and was stable until Thanksgiving Day (go figure). With my tablet acting somewhat laggy, I rebooted it as I have many times before. This time, when the "Kindle" logo went from Orange & White to Blue & White, it froze. I waited 5, 10, 20 minutes and longer, nothing. Wiped Cache, Dalvik, etc via TWRP and tried again... nothing. Reflashed TWRP 2.6.3.0 and CM 10.1 from zips, still freezes. And then it gets really weird when I factory reset it. Here's the sequence of events:
* Restored Kindle OS 7.2.3 via KFFA and fastboot, turned of Amazon updating
* Used FireFlash to install kfhd7-Freedom-boot-7.3.0.img and kfhd7-twrp 2.4.4.0-recovery.img
* Rebooted to TWRP 2.4.4.0 and installed TWRP 2.6.3.1 via Hash's ZIP
* Rebooted to TWRP 2.6.3.1 and installed CM 11.0 (11/25/2013 build)
* Reinstalled applications, etc.
Beautiful again! Worked for several hours with it yesterday, then decided to reboot again and... BAM! Back to the frozen "Kindle" blue & white logo again. Has anyone ever seen this before? Is there some way I can pull up a display of what the bootloader is doing behind the splash screen to see where it is falling over? (BTW, fastboot works, I can still boot into TWRP, and I have a factory cable)
Thanks in advance to all!

Netjerk said:
Hey everyone, first time caller, long time listener here. Apologies for the long post but I figured I'd rather provide all the details upfront.
Thanks in advance to all!
Click to expand...
Click to collapse
Using Freedom Boot with FireFlash does nothing. FireFlash is for images and freedom boot is not an image. You can push it manually no problem. That's why you have to downgrade your firmware to match the Amazon ROM you are about to flash. You may be having a software issue that can't be fixed. Verify your TWRP first. I would do a fresh install of the ROM you choose. Make sure to "swipe" first. Also, how full is your memory? Do you use the Greenify app to keep cpu usage down? Let me know..

LinearEquation said:
Using Freedom Boot with FireFlash does nothing. FireFlash is for images and freedom boot is not an image. You can push it manually no problem.
Click to expand...
Click to collapse
Hey, thanks for the reply. I'm even more confused now than before based on the statement above. Both the seokhun (http://forum.xda-developers.com/showthread.php?t=2271909) and Opensystem (http://forum.xda-developers.com/showthread.php?t=2347170) posts reference using FireFlash to install the kfhd7-Freedom-boot.img. Are you saying I shouldn't install it that way and should instead install via fastboot?
To further clarify, I am doing a full restore of 7.2.3 via Kindle Fire First Aide prior to beginning the procedure. KFFA "pre-roots" the 7.2.3 install and installs the SU app. From there, I'm disabling Amazon OTA updates and then installing ES File Explorer via the Amazon store. ES File Explorer is then used to install the freedom-boot.img as the boot and twrp as the recovery, using the stack override for boot and disabling updates on the recovery. A full reset is done afterwards and before installing CM (cache/dalvik/system wipe). Memory usage should be a non-issue as I haven't yet installed any other applications.
Any thoughts are greatly appreciated!

Opps, wow, I meant you can't flash the bootloader so that's why you downgrade firmware.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------
Netjerk said:
Hey, thanks for the reply. I'm even more confused now than before based on the statement above. Both the seokhun (http://forum.xda-developers.com/showthread.php?t=2271909) and Opensystem (http://forum.xda-developers.com/showthread.php?t=2347170) posts reference using FireFlash to install the kfhd7-Freedom-boot.img. Are you saying I shouldn't install it that way and should instead install via fastboot?
To further clarify, I am doing a full restore of 7.2.3 via Kindle Fire First Aide prior to beginning the procedure. KFFA "pre-roots" the 7.2.3 install and installs the SU app. From there, I'm disabling Amazon OTA updates and then installing ES File Explorer via the Amazon store. ES File Explorer is then used to install the freedom-boot.img as the boot and twrp as the recovery, using the stack override for boot and disabling updates on the recovery. A full reset is done afterwards and before installing CM (cache/dalvik/system wipe). Memory usage should be a non-issue as I haven't yet installed any other applications.
Any thoughts are greatly appreciated!
Click to expand...
Click to collapse
See post above.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers

[Q] How to install TWRP Recovery on KFHD7 with stock rom?

I have a Kindle Fire HD 7 (7.4.6) rooted and I want to know if there's a way that I can install the TWRP Recovery without flashing any rom at the moment and most important without bricking it. I want to have it installed in case that in a future I want to flash a rom. I think it's a must have tool on this device but I'm not quite sure if it's possible and I don't want to try how-to's that I've read in these forums because it's not what I'm looking for and I don't want to mess up the KF . Any help or advice on this will be very appreciated. :angel:

There is a way but you have to do 1 of 2 things outside of what the standard tutorial says. The newer is checks the boot loader for its version to see if it matches with the is version, if it mismatches it will cause a boot loop. So if you tried the default instructions, you would boot loop since you are on a 7.4.6 os, so you have 2 choices, downgrade the is first to the same as the freedom boot image in the tutorial, or download the latest kinology ROM which has a 7.4.6 freedom boot image inside it that for some reason isn't posted by itself last I check. If you download the kinology ROM you don't have to flash it to install that freedom boot image you can just extract it from the ROM and use it in place of the freedom boot the tutorial tells you to use. Take note of one last thing, make sure to check the box in fire flash at the top with red warning text under it about downgrading the boot loader or you will get stuck with a red screen and that requires a fastboot cable to fix. Anyways here's the tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
I suggest reading through it in its entirety to familiarize yourself. You also have a option for the lazier person, you can simply download the kinology ROM onto the device before flashing 2nd boot loader + twrp (because it will bootloop as I previously mentioned) and first make a backup of data and system, then flash the kinology ROM, then restore your backup you just made. In theory I think that will work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
There is a way but you have to do 1 of 2 things outside of what the standard tutorial says. The newer is checks the boot loader for its version to see if it matches with the is version, if it mismatches it will cause a boot loop. So if you tried the default instructions, you would boot loop since you are on a 7.4.6 os, so you have 2 choices, downgrade the is first to the same as the freedom boot image in the tutorial, or download the latest kinology ROM which has a 7.4.6 freedom boot image inside it that for some reason isn't posted by itself last I check. If you download the kinology ROM you don't have to flash it to install that freedom boot image you can just extract it from the ROM and use it in place of the freedom boot the tutorial tells you to use. Take note of one last thing, make sure to check the box in fire flash at the top with red warning text under it about downgrading the boot loader or you will get stuck with a red screen and that requires a fastboot cable to fix. Anyways here's the tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
I suggest reading through it in its entirety to familiarize yourself. You also have a option for the lazier person, you can simply download the kinology ROM onto the device before flashing 2nd boot loader + twrp (because it will bootloop as I previously mentioned) and first make a backup of data and system, then flash the kinology ROM, then restore your backup you just made. In theory I think that will work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for the response, I'm trying that... but before I do this... I want to make sure I'm on the right track. I copied three files on the main kindle directory (fireflash11.apk, kfhd7-freedom-boot-7.4.6.img and kfhd7-twrp-2.6.3.1-recovery.img). I've installed the Fire Flash and now... I'm seeing the interface to flash the boot partition and recovery partition, and the bootloader says the warning thing that the bootloader is not kfhd7-u-boot-prod-7.2.3.bin. That last part is where I'm stuck in... I don't know if checking the box will mess up my kindle... so far, I know that I had to check the "apply stack override", "disable recovery auto update", then unplug cable and hit flash. I'm not sure if I'm still needing the kinology rom since I've downloaded the freedom boot from hashcode.

stunts513 said:
There is a way but you have to do 1 of 2 things outside of what the standard tutorial says. The newer is checks the boot loader for its version to see if it matches with the is version, if it mismatches it will cause a boot loop. So if you tried the default instructions, you would boot loop since you are on a 7.4.6 os, so you have 2 choices, downgrade the is first to the same as the freedom boot image in the tutorial, or download the latest kinology ROM which has a 7.4.6 freedom boot image inside it that for some reason isn't posted by itself last I check. If you download the kinology ROM you don't have to flash it to install that freedom boot image you can just extract it from the ROM and use it in place of the freedom boot the tutorial tells you to use. Take note of one last thing, make sure to check the box in fire flash at the top with red warning text under it about downgrading the boot loader or you will get stuck with a red screen and that requires a fastboot cable to fix. Anyways here's the tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
I suggest reading through it in its entirety to familiarize yourself. You also have a option for the lazier person, you can simply download the kinology ROM onto the device before flashing 2nd boot loader + twrp (because it will bootloop as I previously mentioned) and first make a backup of data and system, then flash the kinology ROM, then restore your backup you just made. In theory I think that will work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Wait, so if you were to install 7.4.6 freedomboot, it would bootloop? Why?

x10knight said:
Wait, so if you were to install 7.4.6 freedomboot, it would bootloop? Why?
Click to expand...
Click to collapse
Because they were running 7.4.6 so the 7.4.6 bootloader is a match. The problem is that the exploit was patched at 7.3.0 so one really should downgrade to 7.2.3 first because sometimes clicking flash 7.2.3 bootloader while using FireFlash app does not work and you get a bootloop anyway. It's best to drag and drop a ROM onto the internal sd card before flashing. If you do bootloop, just go into TWRP and flash the ROM.

x10knight said:
Wait, so if you were to install 7.4.6 freedomboot, it would bootloop? Why?
Click to expand...
Click to collapse
I'm new and a complete noob to this, I'm running 7.4.6, can someone please explain freedom boot and if it would be possible for me to get a custom Rom loaded on my tablet without downgrading to 7.2.3?
Sent from my KFTT using xda premium

Freedom boot if I understand correctly is a patch to the kernel used for second bootloader, I believe it also has version data stored in it that the kindle is checks on boot, if the kernel doesn't match the kindle os version it boot loops into recovery. So yes you can do all without downgrading the os, its just suggested you do because amazon patched the boot loader a while back and downgrading ensures you don't boot loop in case you have an older freedom boot image or you are on 7.4.7. Its probably also flashes the old boot loader too which helps. Never used kffa so not positive about that though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

So how do you suggest I go about flashing my custom Rom, I don't want to downgrade and I want to use fireflash preferable?
Sent from my KFTT using xda premium

I prefer the fire flash method but if you or the program mess up and don't flash the boot loader with the older version first, you will need a fastboot cable to fix it. I haven't ever had a problem with fire flash myself, as long as you check the first box with a bunch of red warning text under it you should be OK.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
I prefer the fire flash method but if you or the program mess up and don't flash the boot loader with the older version first, you will need a fastboot cable to fix it. I haven't ever had a problem with fire flash myself, as long as you check the first box with a bunch of red warning text under it you should be OK.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks figured it out on my own before your post but it's the thought that counts lol your post will help others tho, I was a complete noob it was actually easier than what I thought, I'm running CM11 right now
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app

So... what I should do... run the fire flash app checking that box about the warning of boot loader... and put the files in place and check the "apply stack override" and that's it? I'm getting confused because the post went out of topic...

gracielatf said:
So... what I should do... run the fire flash app checking that box about the warning of boot loader... and put the files in place and check the "apply stack override" and that's it? I'm getting confused because the post went out of topic...
Click to expand...
Click to collapse
First, drag and drop what ever ROM you are going to use onto the root of the internal SD card (CM, Paranoid Android, which ever one). This is important. If you do loop, access TWRP and flash the ROM.
Make sure to put the images in the right place, tick "apply stack override" and also tick "disable recovery auto update" and also chaeck "7.2.3 bootloader."
Here is the original tutorial as well for your reference. http://forum.xda-developers.com/showthread.php?t=2271909
Edit: when you do go to flash the ROM from TWRP you first "swipe" then flash the ROM and then wipe only Dalvic and CACHE.

LinearEquation said:
First, drag and drop what ever ROM you are going to use onto the root of the internal SD card (CM, Paranoid Android, which ever one). This is important. If you do loop, access TWRP and flash the ROM.
Make sure to put the images in the right place, tick "apply stack override" and also tick "disable recovery auto update" and also chaeck "7.2.3 bootloader."
Here is the original tutorial as well for your reference. http://forum.xda-developers.com/showthread.php?t=2271909
Edit: when you do go to flash the ROM from TWRP you first "swipe" then flash the ROM and then wipe only Dalvic and CACHE.
Click to expand...
Click to collapse
Got it, wish me luck! :cyclops:

gracielatf said:
Got it, wish me luck! :cyclops:
Click to expand...
Click to collapse
Good luck!

Well... that was fast. I didn't need the Kinology ROM, but I downloaded and dragged it to the Kindle, just in case it boot loop and so have the rom as backup. Just needed the three fiiles. I'll place the instructions clearly just in case anyone wants to do this and worked perfectly for me.
Download:
fireflash11.apk,
kfhd7-freedom-boot-7.4.6.img and
kfhd7-twrp-2.6.3.1-recovery.img.
Copy or Drag & Drop the three files to Kindle Fire HD 7". Make sure to have ON the "allow installations of applications" options found in drop down window (More+ -> Device). Then install the fireflash11.apk, after installation, open the app, if you got the warning message, check the box on the right, then place the kfhd7-freedom-boot-7.4.6.img in the "boot partition" section and tick "apply stack override", then the kfhd7-twrp-2.6.3.1-recovery.img in the "recovery partition" section and tick "disable recovery auto update". Unplug your KFHD7 from the USB, then hit Flash, and that's it! :victory:
No ROM needed, but in case you want like to go in "safe mode" like I did, download the Kinology ROM found here.

KFHD 7" TWRDP 2.5 and no OS

Rooted my kindle and flashed a custom ROM. Let a friend borrow it and when I got it back i through it in a closet. Recently moved and found my kindle, charged it, and nothing. I can boot into TWRP but that's about it. I've tried to flash new ROM and get an error message saying "error installing from zip". I've downloaded multiple ROMS multiple times and still no go. Is the kindle done for or am I doing something wrong?

Well your version of twrp is kinda outdated(at least according to the thread title, latest is 2.7), I would first try flashing the latest twrp update hashcode just posted, just download the zip, push it to the device with adb, and flash it and reboot into recovery again. Then try a cm 11 flash. What is did it have on it before all this happened?
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Well your version of twrp is kinda outdated(at least according to the thread title, latest is 2.7), I would first try flashing the latest twrp update hashcode just posted, just download the zip, push it to the device with adb, and flash it and reboot into recovery again. Then try a cm 11 flash. What is did it have on it before all this happened?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Not exactly sure. It has been about a year.

MaelstromMonkey said:
Not exactly sure. It has been about a year.
Click to expand...
Click to collapse
Ok, basing it off that it was either amazon os or a cm 10.1 based os. Only reason i ask is because if you tried to install cm 11, and maybe cm 10.2 onto the device at this point it would probably fail with that version of twrp because of lack of selinux support, so i would say go grab latest twrp zip(2.7) for your device, and flash it in recovery, reboot into recovery again, and flash cm 11. Probably should do a factory reset while your at it. I don't think internal storage will need wiping as i doubt it has any selinux xattrib's on it since its more than likely pre-cm10.2ish.

Mismatching build numbers when flashing Stagefright update

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.

Phone won't boot after flashing latest November NBD91P image

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.