Database Users

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

[Q] Help with lost root after 4.3 OTA update

Got a question. I lost root after the 4.3 ota update. Is it possible to get it back without losing everything on the tablet again? I was running SuperSU and OTARootkeeper at the time. When I got into OTARootkeeper is says the su file is there, but when I click restore root it seems not to be able to. I am not a super power user. I used WUGs tookkit to unlock it and root it in the first place. Also does this mean I lost unlock also?
Thanks!

I was in the same situation after installing the update through custom recovery. I remained unlocked. I used Wugs toolkit to root and install custom recovery (TWRP). In recovery I installed Chainfire's updated SuperSu zip. After booting back up, I had root and custom recovery. Search for SuperSu v1.43.

Groid said:
I was in the same situation after installing the update through custom recovery. I remained unlocked. I used Wugs toolkit to root and install custom recovery (TWRP). In recovery I installed Chainfire's updated SuperSu zip. After booting back up, I had root and custom recovery. Search for SuperSu v1.43.
Click to expand...
Click to collapse
Did you lose any data?

xzb6np said:
Did you lose any data?
Click to expand...
Click to collapse
No, you do not lose data after flashing a recovery. Chainfire leased SuperSU 1.5 today.

Username invalid said:
No, you do not lose data after flashing a recovery. Chainfire leased SuperSU 1.5 today.
Click to expand...
Click to collapse
Flashed 4.3 and lost root. I have downloaded the latest SU to my N7 and how am unsure how to go about flashing the ZIP since I no longer have access to custom recovery.

it worked
Username invalid said:
No, you do not lose data after flashing a recovery. Chainfire leased SuperSU 1.5 today.
Click to expand...
Click to collapse
Ok opened up Wugs Nexus Root toolkit. Let it update everything it wanted to and then then told it to root. I was indeed still unlocked and it went ahead and reestablished root without losing anything. I updated OTA RootKeeper afterward and all seems happy.
Thanks!

killswitch11 said:
Flashed 4.3 and lost root. I have downloaded the latest SU to my N7 and how am unsure how to go about flashing the ZIP since I no longer have access to custom recovery.
Click to expand...
Click to collapse
Flash the TWRP image via fastboot. Either with a toolkit or manually.

xzb6np said:
Did you lose any data?
Click to expand...
Click to collapse
As username is invalid posted, no you do not lose data by that method. At least, I lost no data.

Groid said:
As username is invalid posted, no you do not lose data by that method. At least, I lost no data.
Click to expand...
Click to collapse
You only lose data if you lock/unlock bootloader or wipe it yourself
Sent from my Nexus 7 using XDA Premium HD app

OK got one crazy issue. I root but sometimes I lose it and have to reboot to get it back. SuperSu can't write the binary. Every time I open it it wants to write the binary but can't seem to. After a reboot Otarootkeeper say root is there. Then later it will be gone and I have to reboot to get it back.
Sent from my Nexus 7 using XDA Premium HD app

xzb6np said:
OK got one crazy issue. I root but sometimes I lose it and have to reboot to get it back. SuperSu can't write the binary. Every time I open it it wants to write the binary but can't seem to. After a reboot Otarootkeeper say root is there. Then later it will be gone and I have to reboot to get it back.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have the same issue, used Wugfreshs Toolkit to root after 4.3, on reboot i have no root.

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!

[Q] Lose root and recovery on every boot. What gives?

I'm on stock 4.4.2. I can fastboot flash CWM and flash SuperSU in recovery. When I boot, SuperSU says there is no su binary. If I reboot into recovery, it's the stock recovery.
I tried CF-Auto-Root as well. That gave me root. Next reboot, I lost root, however (no su binary). Any ideas?
I'm thinking about restoring from a factory image and starting over, but I don't want to lose data.

sgp77 said:
I'm on stock 4.4.2. I can fastboot flash CWM and flash SuperSU in recovery. When I boot, SuperSU says there is no su binary. If I reboot into recovery, it's the stock recovery.
I tried CF-Auto-Root as well. That gave me root. Next reboot, I lost root, however (no su binary). Any ideas?
I'm thinking about restoring from a factory image and starting over, but I don't want to lose data.
Click to expand...
Click to collapse
Try twrp. Also It looks like you might just be booting recovery and not fishing it. Though that doesn't explain why you lose root. Wugfresh toolkit has something that makes recovery stick when you flash it. Try using that and maybe another recovery like twrp or philz touch( this is the one in using and it's solid and reliable)
Sent from my Nexus 5 using xda app-developers app

abdel12345 said:
Try twrp. Also It looks like you might just be booting recovery and not fishing it. Though that doesn't explain why you lose root. Wugfresh toolkit has something that makes recovery stick when you flash it. Try using that and maybe another recovery like twrp or philz touch( this is the one in using and it's solid and reliable)
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thanks. Not sure what you mean by fishing it, though
I flashed just the system.img from the 4.2.2, and now CWM sticks when I fastboot flash recovery. Flashing SuperSU is not working, however. SuperSU still tells me no su binary. I should only need to flash CWM-SuperSU-v0.98.zip in recovery, right?

sgp77 said:
Thanks. Not sure what you mean by fishing it, though
I flashed just the system.img from the 4.2.2, and now CWM sticks when I fastboot flash recovery. Flashing SuperSU is not working, however. SuperSU still tells me no su binary. I should only need to flash CWM-SuperSU-v0.98.zip in recovery, right?
Click to expand...
Click to collapse
Try downloading and flashing the latest SuperSU binary. http://download.chainfire.eu/supersu

sharksfan7 said:
Try downloading and flashing the latest SuperSU binary. http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
Yes, that's exactly what I've been doing. It flashes without errors, but when I open the app, SuperSU says no su binary.
Sent from my Nexus 5 using Tapatalk

sgp77 said:
Yes, that's exactly what I've been doing. It flashes without errors, but when I open the app, SuperSU says no su binary.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I meant flashing lol. And you said you were using .98 super su. Have you tried version 1.85?
Sent from my Nexus 5 using xda app-developers app

abdel12345 said:
I meant flashing lol. And you said you were using .98 super su. Have you tried version 1.85?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Ah ha! I feel stupid. If you Google "SuperSU download", the first link takes you directly to an old version. I'm sure this is my problem. Thanks guys
Sent from my Nexus 5 using Tapatalk

i337m gets auto-unrooted everytime I do system update of nightly version

As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?

khunkami said:
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
Click to expand...
Click to collapse
OK, that's REALLY strange... TWRP shouldn't be getting clobbered unless the way you're installing it is causing weird issues.
Have you tried flashing TWRP using heimdall/odin/JOdin? It sounds like you're using some sort of root app to flash it on-device???
As to losing root - SuperSU->Settings->Install backup script is the workaround until we integrate SuperSU into omni.

Entropy512 said:
OK, that's REALLY strange... TWRP shouldn't be getting clobbered unless the way you're installing it is causing weird issues.
Have you tried flashing TWRP using heimdall/odin/JOdin? It sounds like you're using some sort of root app to flash it on-device???
As to losing root - SuperSU->Settings->Install backup script is the workaround until we integrate SuperSU into omni.
Click to expand...
Click to collapse
I installed TWRP recovery through Goomanager, install script on the phone.
Is that why my TWRP recovery keeps getting removed everytime I do system update?

khunkami said:
I installed TWRP recovery through Goomanager, install script on the phone.
Is that why my TWRP recovery keeps getting removed everytime I do system update?
Click to expand...
Click to collapse
Possibly, goomanager might be doing something weird like doing a fakeflash. I'm not sure.
If you install a TWRP image using heimdall or odin it should persist - the dd method listed in http://teamw.in/project/twrp2/124 should work too. (i337 is the AT&T/Rogers Note2, right?)
Omni shouldn't be flashing recovery on this device (Omni only changes recovery on devices that can't change kernel without changing recovery - like the I9100/I777/N7000 and many Sonys), but even if it is, it should be flashing a TWRP build...

Entropy512 said:
Possibly, goomanager might be doing something weird like doing a fakeflash. I'm not sure.
Click to expand...
Click to collapse
I've seen / had the issue to with GooManager. Indeed it is doing a "fakeflash", if you go into recovery from GooManager you will get into the recovery but after that. If you do it on boot you won't get there. No matter what, unless you do a manual install for the recovery..
Hope this helped,

Gertlily said:
I've seen / had the issue to with GooManager. Indeed it is doing a "fakeflash", if you go into recovery from GooManager you will get into the recovery but after that. If you do it on boot you won't get there. No matter what, unless you do a manual install for the recovery..
Hope this helped,
Click to expand...
Click to collapse
I am just curious. Why does Omni Rom unroot the device after system-update?

khunkami said:
I am just curious. Why does Omni Rom unroot the device after system-update?
Click to expand...
Click to collapse
It is not only the issue on OmniROM but on (almost) every ROM, I've had the same on cyanogen and Samsung Stock.. So flashing it yourself is better.. Hope this bug will get fixed somewhere in the future.
Bye,
Sent from my Nexus 7 using Tapatalk

khunkami said:
I am just curious. Why does Omni Rom unroot the device after system-update?
Click to expand...
Click to collapse
It's because Omni doesn't have root yet. It's on the to do list. The easiest way is to install SuperSU to system, then install the back up script. That way you'll keep root through updates.

khunkami said:
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
Click to expand...
Click to collapse
I know very little about anything, and I was experiencing this same thing. CF-Auto-Root reinstalls stock recovery which overwrites TWRP during the rooting process. Each time I update a nightly and then run CF-Auto-Root to re-root it. After that I use mobile ODIN to reinstall TWRP recovery and all is good.

AKdballs said:
I know very little about anything, and I was experiencing this same thing. CF-Auto-Root reinstalls stock recovery which overwrites TWRP during the rooting process. Each time I update a nightly and then run CF-Auto-Root to re-root it. After that I use mobile ODIN to reinstall TWRP recovery and all is good.
Click to expand...
Click to collapse
You shouldn't be using CF-Auto-Root if you have a custom recovery (which you need in order to install Omni). Just flash SuperSU in recovery.

I knew something wasn't quite right but I did it that way because it works. I have downloaded su onto the SD card, as well as the latest nightly build of Omni. Can I install the new nightly with TWRP, and add su as a second zip to install at the same time? Or should I flash them separately?
Sent from my SGH-I337M using xda app-developers app