Database Users

[Q] can't boot into os after ota 6.3 update

My kindle fire is rooted by using BurritoRoot3 method,with firefirefire bootloader and CWR recovery installed.
this morning,my kindle fire automatically rebooted,then stuck at CWR recovery interface,i realized it may related with a new ota update,so i shutdown kindle fire and power on,it reboot into recovery as long as it going into the os.
now i can boot into the recovery but cannot into the os,what should i do ?

puppyguy said:
My kindle fire is rooted by using BurritoRoot3 method,with firefirefire bootloader and CWR recovery installed.
this morning,my kindle fire automatically rebooted,then stuck at CWR recovery interface,i realized it may related with a new ota update,so i shutdown kindle fire and power on,it reboot into recovery as long as it going into the os.
now i can boot into the recovery but cannot into the os,what should i do ?
Click to expand...
Click to collapse
I think I read somewhere that CWM stops the ota from installing so it starts bootlooping. Twrp would let the update go through but if it did, you would lose root anyway. Maybe using CWm you could install the 6.3 pre-rooted stock rom

I was having the same issue with twrp and this upgrade. To get out of the bootloop I used adb:
adb shell
idme bootmode 4000
reboot
It Didn't install the update but got me the kindle back. I then used eldarerathis rooted 6.3 image:
http://forum.xda-developers.com/showthread.php?t=1569298:p

My kindle did the same thing it's because the OTA update doesn't work right with TWRP. Take a look at my thread. Basically you need to download the update, rename it update.zip put it in the root directory of the kindle, and then power up the kindle it will go into TWRP and click on the update/flash function (not sure what it's called off the top of my head right now) and let it do it's thing and you will be back to normal.
Alternatively if you don't feel like re-rooting your device, download this version and update it using the instructions above.

Thank you! This worked perfectly.
Laquox said:
My kindle did the same thing it's because the OTA update doesn't work right with TWRP. Take a look at my thread. Basically you need to download the update, rename it update.zip put it in the root directory of the kindle, and then power up the kindle it will go into TWRP and click on the update/flash function (not sure what it's called off the top of my head right now) and let it do it's thing and you will be back to normal.
Alternatively if you don't feel like re-rooting your device, download this version and update it using the instructions above.
Click to expand...
Click to collapse

Laquox said:
My kindle did the same thing it's because the OTA update doesn't work right with TWRP. Take a look at my thread. Basically you need to download the update, rename it update.zip put it in the root directory of the kindle, and then power up the kindle it will go into TWRP and click on the update/flash function (not sure what it's called off the top of my head right now) and let it do it's thing and you will be back to normal.
Alternatively if you don't feel like re-rooting your device, download this version and update it using the instructions above.
Click to expand...
Click to collapse
Do you have to wipe. Any "cache"? Or Factory reset...Or do you only do that if you are going to a different ROM. ?
Sent from my Kindle Fire using Tapatalk

can not install bootloader of choice

Do I have to install cwmtouch also if all I want to add is kinfauns fff1.3 bootloader, to change the logo and keep TWRP?. I tried installing just kinfauns fff1.3 bootloader, but can not gain SU.

palmheel said:
Do I have to install cwmtouch also if all I want to add is kinfauns fff1.3 bootloader, to change the logo and keep TWRP?. I tried installing just kinfauns fff1.3 bootloader, but can not gain SU.
Click to expand...
Click to collapse
would try latest kfu 0.9.4 - point install latest firefirefire
hope this is 1.3 ...

palmheel said:
Do I have to install cwmtouch also if all I want to add is kinfauns fff1.3 bootloader, to change the logo and keep TWRP?. I tried installing just kinfauns fff1.3 bootloader, but can not gain SU.
Click to expand...
Click to collapse
You can mix and match whatever bootloader/recovery combination you want. They are on separate partitions, so flashing one does not affect the other.
The only caveat is that you must have TWRP installed before changing the bootloader because the distribution image for TWRP is a boot image that actually boots up and flashes both the recovery and bootloader partitions on its own. That boot image contains version 1.0 of FFF, so you must then overwrite it with whatever bootloader you want.
As a side note, the install process for TWRP is unintuitive and may be confusing for new users to have to use the "fastboot boot" instead of the "fastboot flash recovery" command. I've gone back and forth with CWMR and TWRP several times and it's annoying to have to flash the bootloader over and over again in the process. To get around that, I've extracted just the recovery image from the TWRP distribution and have been using that image instead. I've thought about posting it somewhere, but I didn't want to piss off the developers. Maybe if there's some demand for it, I'll just upload it somewhere to see if anybody comes screaming at me... or maybe just write a how-to for those interested in extracting it for themselves.

I've packaged it in my new method, I just need time to sit down n rewrite the install directions and update my post. I've also compiled a blue cwm of sbloods version 1.1 which will also be in the updated method.
but yup, what kinfaun said lol
Sent from my HTC Glacier using xda premium

Ok. Now, for the the dumb question of the day. I do have TWRP installed, I tried using the instructions on the [gscript][march11]install cwm recovery+bootloader of your choice (no fastboot) thread, but keep getting error with SU.

palmheel said:
Ok. Now, for the the dumb question of the day. I do have TWRP installed, I tried using the instructions on the [gscript][march11]install cwm recovery+bootloader of your choice (no fastboot) thread, but keep getting error with SU.
Click to expand...
Click to collapse
You might want to wait a day or two for everyone to finish banging away at the 6.3 update. I got one of the $139 refurbs and it came today. Trying to root it, I'm running into SU/permission issues too. Something changed but everyone just don't know what yet. From what I can tell, this is fairly standard every time Amazon releases an update.

Got it installed. Thanks to all, for all the info. Learning, all this is new to me.

[Q] Iam not able to install a custom recovery

Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?

Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?
Click to expand...
Click to collapse
What you are doing wrong is using a toolkit. Follow these instructions. http://forum.xda-developers.com/showthread.php?t=2018179

I use mskip's Nexus 4 Toolkit without any issues. So far I've used it to root, install clockworkmod recovery and flash the stock image after messing up a build prop edit. Saved me a lot of headaches as I haven't used adb or fastboot commands in over a year, don't even have the sdk installed any more. This is the first phone since I got my Incredible in 2010 that I actually wanted to put a custom recovery on and play with.
Here are some basic questions. Did you unlock your boot loader? Do you have usb debugging enabled? Does your device show up when when your plugged in and booted up into fastboot? Do you have the correct drivers installed? Which recovery are you trying to install and did you try the other one available? Did you use the toolkit to root and did it work?

Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?
Click to expand...
Click to collapse
After you root the device using the toolkit, it is easiest to download ROM Manager or Goo.im from the Play Store to install your custom recovery.
As Ed Daddy said, it's best to use ADB, however, it would save you some times and a few headache if you could just go ahead and download ROM Manager. Sometimes people forget there are *really easy* ways to do stuffs.

KyraOfFire said:
After you root the device using the toolkit, it is easiest to download ROM Manager or Goo.im from the Play Store to install your custom recovery.
As Ed Daddy said, it's best to use ADB, however, it would save you some times and a few headache if you could just go ahead and download ROM Manager. Sometimes people forget there are *really easy* ways to do stuffs.
Click to expand...
Click to collapse
While I agree there are "really easy" ways to do things, I was trying to point him in the direction of learning.
Obviously since they don't know how to flash a recovery, they probably aren't familiar with much else.
Learning how to do things properly never hurt anyone.
Sent from my Nexus 4

Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp...
...Am i doing anything wrong?
Click to expand...
Click to collapse
El Daddy is correct.
Toolkits are silly on Nexus devices, for Nexus the simplest way is flashing via faboot. At the very least take the time to learn from the guide that El Daddy provided a link to. With that knowledge you'll be able to resolve issues like this and help others who get stuck.

Actually I unlocked my bootloader, rooted the device. Using normal OTA 4.2.1
But it seems that every toolkit cannot flash the recovery.
I will try it now with using adb commands...

All the toolkits are are scripts that run the fastboot and adb commands for you, they're nothing complicated and IMO from someone with experience I prefer using them now as I no longer have the sdk installed. Gave up on custom ROMs, my own and others, a long time ago.
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
Toobie said:
Actually I unlocked my bootloader, rooted the device. Using normal OTA 4.2.1
But it seems that every toolkit cannot flash the recovery.
I will try it now with using adb commands...
Click to expand...
Click to collapse
Actually it's fastboot not adb that you use to flash recoveries, two different animals. and to the poster recommending ROM Manager, its kind of borked right now and I wouldn't use it to flash anything.
Edit: spoke too soon on ROM Manager looks like Koush updated it and it appears to be working properly. This was the first app I ever bought back in 2010 when I first rooted my Eris and couldn't get clockworkmod recovery to install, the moderators at the time recommended ROM Manager to me to get it installed as nothing else worked.

Yeah, but both didn't work.
I used now the adb commands on my one, still remembering them from my Nexus One, and see it works

For sure fastboot and adb will work. I used it very recently when my n4 updated. Just make sure to download the latest cwm. Had a boot loop the first time as I used an old one. Hehehe
Edit: actually not sure if it was the old fastboot files or cwm that caused the error. Anyway I updated my sdk so everything works well
Sent from my Nexus 4 using Tapatalk 2

Actually all the tools booted the phone fine in the fastboot mode, telling me flashing the recovery is fine.
But every time i wanted to reboot in the recovery i got this android roboter with the red alarm...
with the normal adb commands everything was really fine!

You're getting that because flashing custom recovery alone without modifying a file or two generates stock recovery every after a reboot. Go to your /system folder and look for recovery-from-boot.p and rename that to whatever you like then flash the custom recovery again
Sent from my Nexus 4 using Tapatalk 2

thephantom said:
You're getting that because flashing custom recovery alone without modifying a file or two generates stock recovery every after a reboot. Go to your /system folder and look for recovery-from-boot.p and rename that to whatever you like then flash the custom recovery again
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Sounds great, will try that.
Thank you.

Help: Lost Root after 4.2.2 Upgrade

I upgraded to 4.2.2 and it seems I have lost my Root Access. I has SuperSU Pro with OTA Survival mode on installed as a system app before the upgrade but it seems it did not keep Root access. I used Root Checker and it's telling me I am not rooted. I am still seeing the unlock Icon at boot so I assume my boot loader is still unlocked.
Is there an easy way to get my Root access back?
Thanks.

Hey I had the same happen to me, ended up having to fastboot flash recovery to get twrp back and then downloaded the supersu recovery bootable zip and flashed supersu back. Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb. Hope this helps.
Before trying all this maybe try installing busy box, I dunno I'm a bit of a noob
Sent from my Nexus 7 using XDA Premium HD app

Thanks for your reply. I will try to follow the steps you outlined however, most of what you said is new to me. I initially rooted my device with the Nexus 7 Toolkit so it was a fairly simple procedure. I have never used the SDK or twrp are there any tutorials on how these work on 4.2.2? Also they will probably update Nexus 7 toolkit to support 4.2.2 eventually, so if I can't figure out the steps indicated I may have to wait.
Another noob question: After the update I can still open busybox and SupeSU, how come these apps still run if I am no longer rooted?
gastonwalpole said:
Hey I had the same happen to me, ended up having to fastboot flash recovery to get twrp back and then downloaded the supersu recovery bootable zip and flashed supersu back. Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb. Hope this helps.
Before trying all this maybe try installing busy box, I dunno I'm a bit of a noob
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse

hey man yeh i didnt get how i still had supersu but i definitely wasnt rooted. its all a bit complicated aye, basically you need to download the andriod sdk bundle [now called adt bundle] for whatever you have eg. windows 7 32/64, and the jdk java development kit, look for guides on these, there two youtubers who have helpful channels: driodmodderx and wwjoshdew. also search threads here. you want your device to be recognized by the comp, sdk and jdk do this. twrp is a custom recovery that you can use to flash roms zips etc, you use your comp to send this custom recovery to your device. i would have stayed on 4.2.1 because i dont think you can use custom roms on 4.2.2 bootloader, still 4.2.2 is very smooth, i like it.
Sent from my Nexus 7 using XDA Premium HD app

gastonwalpole said:
Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb.
Click to expand...
Click to collapse
Boy did your post make me happy! I had the exact same problem. Managed to install 4.2.2 with modified OTA update (original was failing due to some discrepency in GoogleCalendar.apk) but even though I had SuperSU in survival mode, I lost my root. I've been trying all afternoon to connect via adb to my Nexus and just couldn't - it was always offline.. I tried 3 different computers and my SGNII phone (which worked) but N7 just wouldn't stop being offline...
I hope this is the solution! Thanx a BUNCH!
One question - my bootloader is unlocked telling by the icon on boot "google" screen - will I lose my apps and data after "re-rooting" that is, after flashing custom recovery and SuperSU?
THANX!!!!!!!!!!!!!

you won't lose anything by flashing recovery or su

I just checked the Nexus Root Toolkit site and he says he'll have a new version out very soon that will root 4.2.2 so sit tight, we'll soon be able to root again Just fire up the program from time to time and it should automatically update when it's ready.

burnitdown said:
you won't lose anything by flashing recovery or su
Click to expand...
Click to collapse
Great, managed to do it, everything fine. Thanx again!

SimonP2 said:
I just checked the Nexus Root Toolkit site and he says he'll have a new version out very soon that will root 4.2.2 so sit tight, we'll soon be able to root again Just fire up the program from time to time and it should automatically update when it's ready.
Click to expand...
Click to collapse
And if you can't wait, the workaround is there on http://www.wugfresh.com/nrt/ under IMPORTANT NOTICE.

4.2.2 problems with recovery

First let me start off by saying that I have read a lot of posts about issues with 4.2.2 but mine are different, I promise. If not, sorry.
I am unlocked/rooted and had a custom ROM installed. Decided to change to another so I went back to my stock backup (I really hated the ROM). When I went back to stock I received the notification to update to 4.4.2. I did. A bit later I tried to flash a ROM via goo.manager with no success. I then tried to flash with TWRP. I got the android with the red exclamation when I tried to go into recovery. I've also attempted to flash a recovery again with goo.manager and ROM Manager. I kept getting errors.
My dog chewed up my USB so I can't flash recovery since my nexus won't show on my computer with anything else. Is there any other way I can flash a recovery?
Again, forgive me for any redundancy and please help, I'm a serious noob. Being stuck on stock isn't the worst thing but I'd really like to flash another ROM.
Sent from my Nexus 7 using xda app-developers app

If your ROM is rooted, you can flash the recovery partition from a root shell using the "dd" command.
That is, from a terminal emulator:
$ su
# cd /sdcard
# dd bs=4096 if=name-of-recovery-image-file.img of=/dev/block/mmcblk0p1
good luck. I didn't understand everything you said in your post, but I got the part about the dog

buckwheat_shawt said:
First let me start off by saying that I have read a lot of posts about issues with 4.2.2 but mine are different, I promise. If not, sorry.
I am unlocked/rooted and had a custom ROM installed. Decided to change to another so I went back to my stock backup (I really hated the ROM). When I went back to stock I received the notification to update to 4.4.2. I did. A bit later I tried to flash a ROM via goo.manager with no success. I then tried to flash with TWRP. I got the android with the red exclamation when I tried to go into recovery. I've also attempted to flash a recovery again with goo.manager and ROM Manager. I kept getting errors.
My dog chewed up my USB so I can't flash recovery since my nexus won't show on my computer with anything else. Is there any other way I can flash a recovery?
Again, forgive me for any redundancy and please help, I'm a serious noob. Being stuck on stock isn't the worst thing but I'd really like to flash another ROM.
Click to expand...
Click to collapse
Are you still unlocked and rooted after the update to 4.2.2 ?
If not you must unlock and root your N7 again, but be careful, All root tools doesn't work for 4.2.2. and are not updated for 4.2.2
I unlocked my N7 normally, but I used CF auto-root (update) and now I'm unlocked and rooted with DirtyBox rom.

Thanks a lot. This will be my first time using the terminal emulator, should be a good learning experience
Sent from my Nexus 7 using xda app-developers app

I'm still unlocked and rooted. I just can't access my recovery after the update. This happened once with CWM on my GNex but I still had the oem usb so I just flashed it again with my computer. I don't have an oem usb for my N7. Btw, I was using twrp on the N7.
Sent from my Nexus 7 using xda app-developers app

buckwheat_shawt said:
I just can't access my recovery after the update.
Click to expand...
Click to collapse
The 4.2.2 ota replaced whatever you had flashed into the recovery partition with a stock recovery.
Did you try the "dd" flash?

bftb0 said:
The 4.2.2 ota replaced whatever you had flashed into the recovery partition with a stock recovery.
Did you try the "dd" flash?
Click to expand...
Click to collapse
I've tried that but I keep getting "cannot open for write: Permission denied". I guess I'm doing it wrong. And I can't boot to fastboot to try with my computer because I keep turning the damn thing off. My usb is iffy sometimes. This sucks.

buckwheat_shawt said:
I've tried that but I keep getting "cannot open for write: Permission denied". I guess I'm doing it wrong. And I can't boot to fastboot to try with my computer because I keep turning the damn thing off. My usb is iffy sometimes. This sucks.
Click to expand...
Click to collapse
Permission denied would only occur if you were not root.
Either your ROM is not rooted, or you forgot to run the "su" command first.

bftb0 said:
The 4.2.2 ota replaced whatever you had flashed into the recovery partition with a stock recovery.
Did you try the "dd" flash?
Click to expand...
Click to collapse
bftb0 said:
Permission denied would only occur if you were not root.
Either your ROM is not rooted, or you forgot to run the "su" command first.
Click to expand...
Click to collapse
You're right I wasn't. I just found out and I've rooted and installed my recovery. Thanks alot though, probably wouldn't have figured it out without you all. First time having to make a post to solve an issue. Thanks again! :victory: