Database Users

4.2.2 Install Problems

After doing the update ota it reboots and takes my to cwm recovery and asks to if I want to install this untrusted zip but when I say yes it gives me an error. I am on stock kernel rooted with an unlocked bootloader.

like the million other upgrade threads, you cant update to OTA with a custom recovery....

You can download the OTA update file and install it with cwm or twrp recovery. I used cwm recovery with supersu and voodoo ota rootkeeper and installed the update, kept cwm recovery and root.

Groid said:
You can download the OTA update file and install it with cwm or twrp recovery. I used cwm recovery with supersu and voodoo ota rootkeeper and installed the update, kept cwm recovery and root.
Click to expand...
Click to collapse
How to install using twrp?

Maybe a little more noob friendly idea. Is there an easy way to get stock recovery back? May also help those without easy access to a computer.
Is there a way to restore factory recovery using a terminal emulator?
Sent from my SGH-I777 using xda app-developers app

Iv download 4.2.2 and flash it with cwm recovery but still get status 7 erorr and instalation abortion
Sent from my Nexus 7 using Tapatalk 2

Leonhan said:
How to install using twrp?
Click to expand...
Click to collapse
Sorry, not sure about twrp. I've never used it, but I've seen other threads where people have used it successfully.

litesout said:
Is there a way to restore factory recovery using a terminal emulator?
Click to expand...
Click to collapse
Code:
$ su
# dd if=stock-recovery.img of=/dev/block/mmcblk0p1 bs=4096

Can you guys boot into custom recovery in Android 4.3?

Hey guys I was trying to boot into the latest CWM image to install superSU in the oficial android 4.3 image, however I got stock in the bootscreen, I tried manually typing the commands as always did and using a toolkit... Maybe is it broken?
Regards

I can't get super su working,
Sent from my Nexus 4 LTE @1.728 GHz on Stock 4.2.2

IRX120 said:
I can't get super su working,
Sent from my Nexus 4 LTE @1.728 GHz on Stock 4.2.2
Click to expand...
Click to collapse
But you were able to boot into recovery?

rootusr said:
But you were able to boot into recovery?
Click to expand...
Click to collapse
Yeah just no root
Sent from my Nexus 4 LTE @1.728 GHz on Stock 4.2.2

rootusr said:
Hey guys I was trying to boot into the latest CWM image to install superSU in the oficial android 4.3 image, however I got stock in the bootscreen, I tried manually typing the commands as always did and using a toolkit... Maybe is it broken?
Regards
Click to expand...
Click to collapse
Working fine here. Installed latest TWRP then super su and root works fine.

cwm recovery boot into a blank screen...not able to see anything.

22sl22 said:
Working fine here. Installed latest TWRP then super su and root works fine.
Click to expand...
Click to collapse
This is my game plan as well....Make sure I have the latest TWRP and Super SU before I attempt to re-root.
EDIT: I forgot, I switched from the Super SU app to the superuser app from clockworkmod a while back.
TWRP updated to 2.6.0.0
Superuser already at 1.0.1.8
re-downloaded superuser.zip (unknown version)
Ready for the 4.3 OTA.

22sl22 said:
Working fine here. Installed latest TWRP then super su and root works fine.
Click to expand...
Click to collapse
Can you upload the SuperSu zip file you used to root?

I have exactly the same problem. Before updating to 4.3 I've booted CWM and did a nand backup.
After updating I can't boot into CWM or TWRP to flash the root zip. I get a blank screen instead of the recovery menu.
I don't want to flash a recovery, just boot like thousands times before to flash the root.zip from chainfire that works.

Same problem : I get a blank screen when booting CWM
I can connect with adb, backlights turns off after some time, and on again if I press a key.
I can boot in the recovery after flashing it !
So booting a flashed recovery from the bootloader works, but booting it with "fastboot boot" don't...

blitzzz3434 said:
Can you upload the SuperSu zip file you used to root?
Click to expand...
Click to collapse
Read here. Make sure you read the bit about Titanium Backup if you use it:
https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L

22sl22 said:
Read here. Make sure you read the bit about Titanium Backup if you use it:
https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Click to expand...
Click to collapse
Are you by any chance experiencing that high cpu usage which causes horrible battery drain?
Sent from my Nexus 4 using xda premium

Coming back to the subject of this thread, I was NOT able to boot into TWRP from fastboot using the command:
fastboot boot openrecovery-twrp-2.6.0.0-mako.img
the n4 was starting but I was just getting a black screen.
I had to flash the recovery to my nexus 4 with:
fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img
and after that I was able to boot as usual to the recovery and install chainfire modified .zip to gain root in android 4.3
Any other is experiencing this problem with booting into recovery on N4 ?
On my nexus 7 I was able to boot as usual into the recovery, without flashing it

@bagl0312 How I wrote, I have exactly the same problem. I will going to flash twrp, flash root zip and flash back the stock recovery for now.
Never the less fastboot boot recovery.img does not work atm

superSU cant update binary

stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app

minjiet said:
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would recommend flashing or temporarily booting a custom recovery and then flash the latest version of SuperSu which can be found here in recovery. This should give fix the binary need's to update error your encountering. Let me know if you still have questions.

shimp208 said:
I would recommend flashing or temporarily booting a custom recovery and then flash the latest version of SuperSu which can be found here in recovery. This should give fix the binary need's to update error your encountering. Let me know if you still have questions.
Click to expand...
Click to collapse
how to boot a custom recovery? any link?

minjiet said:
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine did the same. Then I chose the other option not normal and it installed it automatically through recovery. Before that it might be needed to download twrp recovery from here
http://www.teamw.in/project/twrp2/128. Use Android App Install Method.

I got my nexus 10 yesterday...
did the regular stuff:
fastboot oem unlock followed by fastboot flash recovery ... then i applied SuperSU.1.65 but its not workin > pic below.. any idea folks?
http://tinypic.com/r/2ziocra/5

awyeahh1 said:
I got my nexus 10 yesterday...
did the regular stuff:
fastboot oem unlock followed by fastboot flash recovery ... then i applied SuperSU.1.65 but its not workin > pic below.. any idea folks?
http://tinypic.com/r/2ziocra/5
Click to expand...
Click to collapse
I would recommend flashing SuperSU again in recovery and if that still doesn't work take a look at CF-Auto root which will allow you to gain root access.

shimp208 said:
I would recommend flashing SuperSU again in recovery and if that still doesn't work take a look at CF-Auto root which will allow you to gain root access.
Click to expand...
Click to collapse
thanks for the answer.. I flashed 10x times.. same story... doesn't CF-Auto root flash an old version of supersu which is not compatible with android 4.3 ?

awyeahh1 said:
thanks for the answer.. I flashed 10x times.. same story... doesn't CF-Auto root flash an old version of supersu which is not compatible with android 4.3 ?
Click to expand...
Click to collapse
People have reported that CF-Auto Root works fine with Android 4.3 on the Nexus 10. You can also always update the SuperSU app and binary after successfully rooting with CF-Auto Root.

Thx my prob was solved by appying latest recovery and latest supersu 1.65
Beamed from my Htc kickass Sensation using tapatalk 4.

Same problem here
On starting SuperSU, here’s what I get:
>The SU binary needs to be updated. Continue?
[selected: Continue]
>If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary? (Normal / TWRP/CWN)
[selected: Normal]
>Installing, please wait
>Installation failed!
As far as I can tell, I can’t install TRWP/CWN because the SuperSU binary is not updated, and I can’t update the the SuperSU binary unless TRWP/CWN is installed. This looks like a vicious circle, can anyone recommend a way out of it please?
Further background:
Device: Evolveo Xtraphone 4.5 Q4, rooted by SRSroot which recognised it as an HTC device.
Also attempted: updating from SD card with UPDATE-SuperSU-v1.86.zip, by running Superuser.apk from the zip folder. This takes me back to square one: “The SU binary needs to be updated. Continue?” etc.
Any recommendations enormously appreciated, thanks!

Flash issues

I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app

wrong advice, my mistake... thanks for the reminding simms22.

But I wanna stay rooted
Sent from my Nexus 4 using xda app-developers app

You don't have to unroot. Just download and flash TWRP 2.6.3.2. On that build, they fixed the issues of 4.4 ROMS incorrectly flashing. Using it myself with no problems. Its in Original Android Development if I'm not mistaken

Flashing 4.4 Factory Image issues
Currently on my Nexus 4.
Android 4.3 Unlocked and Rooted
Kernel Version: 3.4.0-perf-gf43c3d9
Build: JWR66Y
Baseband: M9614A-CEFWMAZM-2.0.1700.84
Using ClockWorkMod Recovery v6.0.4.3, when trying to flash the 4.4 factory image .zip file on the SD Card I keep getting an "Installation Aborted" error after "Installing update..." step and the red Triangle on the android figure.
When attempting to sideload using stock recovery, getting a "Signature Verification Failed"
Any Suggestions? Thanks

darkfire2040 said:
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you haven't already tried it, under Mount uncheck system, that solved the problem for me.

Yeah I wanna stay in twrp so I will try flashing the latest. The error I'm getting is. Error while trying to update binarys
Sent from my Nexus 4 using xda app-developers app

will_chrome said:
you've got to unroot and back to stock rwcovery 1st if I'm not mistake. the guide to flash stock rom can be found in http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
wtf??? never ever give advice on android ever again!
op, all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.

simms22 said:
all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
Click to expand...
Click to collapse
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk

ph37rd said:
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.

simms22 said:
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
Click to expand...
Click to collapse
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk

ph37rd said:
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?

simms22 said:
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
Click to expand...
Click to collapse
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk

ph37rd said:
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
na. really the only 100% working fix is to delete the recovery, then reflash.

simms22 said:
na. really the only 100% working fix is to delete the recovery, then reflash.
Click to expand...
Click to collapse
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk

ph37rd said:
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.

simms22 said:
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
Click to expand...
Click to collapse
OK that confuses me. If using fastboot to place a new boot loader, radio, recovery and ROM are onto the phone and I have to 'fastboot flash recovery recovery.img' to replace the stock recovery that doesn't wipe out the stock recovery? Fabulous sentence structure.
Sent from my Nexus 4 using Tapatalk

I have a feeling I'm missing sometihng....

So, I've downloaded and installed CM11 nightly (20140112, clean wipe) on both mine and my wife's N4, and super user isn't working right. I mean it says that Romtoolbox Pro has permissions...but it won't let it do anything. I can't remount using adb. I can't Mount rw using adb...
Does SU/root even work with 4.4?

RavenII said:
So, I've downloaded and installed CM11 nightly (20140112, clean wipe) on both mine and my wife's N4, and super user isn't working right. I mean it says that Romtoolbox Pro has permissions...but it won't let it do anything. I can't remount using adb. I can't Mount rw using adb...
Does SU/root even work with 4.4?
Click to expand...
Click to collapse
Download this:
http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
Flash via recovery.
Sent from my Nexus 7 (2013)

Didn't work...

RavenII said:
Didn't work...
Click to expand...
Click to collapse
You did flash it via recovery right? What recovery do you have btw?
Sent from my Nexus 7 (2013)

Berrydroidcafe said:
You did flash it via recovery right? What recovery do you have btw?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Yup, flashed through Philz 6.something recovery...

RavenII said:
Yup, flashed through Philz 6.something recovery...
Click to expand...
Click to collapse
Honestly, I've never heard of that recovery before. :what:
Sent from my Nexus 7 (2013)

Try installing supersu from market, it worked for me (after flashing supersu by recovery)
https://play.google.com/store/apps/details?id=eu.chainfire.supersu

So this is a common issue?

Phil'z is cwm and cwm always have issues with root does not stick. However, try to use latest cwm 6.0.4.5 instead of phil'z (cause it might be outdated) or better yet, use latest twrp 2.3.6.6. Link to twrp is in my sign.

Overdose1986 said:
Try installing supersu from market, it worked for me (after flashing supersu by recovery)
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Click to expand...
Click to collapse
There's no reason to install SuperSU from the Play Store if you flash the zip file via the recovery. It installs the apk and Binaries at the same time. Play store only the app.
Sent from my Nexus 7 (2013)

CM's built in superuser should be working fine!
Sent from my Nexus 7 using Tapatalk

Yeah go into settings of supersu. There's an option with cm superuser. You have to tick that (as I remembered someone posted before).

I'll double check...I'll try another Recover (I was at the latest available for the N4)...

I just don't get it...it doesn't work. Tried unchecking the box in the stock SU menu...running latest twrp...flashed that zip, installed it from the store (tried one, then the other, then both)....I can't be the only one having this issue...

Soooo....the zip posted by Berrydroidcafe worked...you have to uncheck "respect Cyanogenmod Super user"...or something to that extent...it's in the settings....Thanks a lot bud.