Database Users

[Q] Lost TWRP and root - Help needed

Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.

Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
tigas68 said:
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Click to expand...
Click to collapse

spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
thanks. :good:

tigas68 said:
thanks. :good:
Click to expand...
Click to collapse
Still isn't working...
When i tried to fastboot the recovery img the device turns off and never turns on again on is own!
Help please!
I like my root...!

here's the screens of waht happens.
This his what happens when i try to go into recovery mode...

first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip

I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.

zephiK said:
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
Click to expand...
Click to collapse
zephiK,
Already done that! I flashed the CWM recovery throught fastboot. The device turned off. When i turn it on again and tried to go into recovery mode, so i can flash the SU from chain fire, but got the image on my post!
The phone is unlocked!

That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!

Johnsonyc said:
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
Click to expand...
Click to collapse
I used the sctock rom downloaded from the google developers website!

Johnsonyc said:
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Click to expand...
Click to collapse
What he said. The recovery flash isn't going through.
Sent from my Nexus 4 using Tapatalk 4 Beta

Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world

spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.

kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.

kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Johnsonyc said:
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
Click to expand...
Click to collapse
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:

sn0warmy said:
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
Click to expand...
Click to collapse
I don't even really use root explorer anymore just like having the ability to make nandroid backups. But after doing a clean install of 4.3 in fastboot and it only took 30 minutes from start to finish including app and data restores nandroids to me are not that useful anymore (I don't flash custom ROMs anymore). Google automatically re-installed all my apps as soon as I reconfigured my WIFI, they also restored my APN and my work WIFI settings but not Bluetooth. And I used Helium to restore the user app data and all my texts and helium doesn't need root access to work.
Here is the start of Koush's post on Google+ where he talks about superuser on 4.3.
I finally had a chance to dig into seeing why Superuser is broken on Android 4.3. https://android.googlesource.com/platform/dalvik/+/9907ca3cb8982063a846426ad3bdf3f90e3b87c2
Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc.
This is a pretty nasty change. It seems that SuperSU works around this by replacing install-recovery.sh to run a su daemon that pipes subsequent through it. Pretty hacky, but understandable why it was done this way.
Will need to look into how to do this in a less invasive fashion, if that is even possible. Of course, if building from source, this change can simply be reverted.

Here's a better explanation about superuser from Android Police.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/

Rooting for me is used for restoring my apps and stuffs using titanium backup. Another useful thing about rooting is the ability to check saved wifi passwords.

Just install twrp from fastboot and then flash the su zip file in twrp
Sent from my Nexus 4 using Tapatalk 2

EddyOS said:
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
Click to expand...
Click to collapse
@EddyOS
Your answer is what forums are not about! Instead of helping you had an atitude of an ass...!
@ Everyone else
After 5 or 6 attemps, doing it by the book, the CWD worked and i now have a Recovery mode! I didn´t did anything different, so i couldn´t really understand what went wrong before... SU from chainfire works perfectly! It´s now Rooted! And yes, the tuturials are idiot proof!
There´s something that´s bothering my mind... I can´t unistall some trash that cames with the 4.3 version using titanium backup, because he can´t find the apk files...! I could do it with the 4.2.2 version, but not with this one. I'm using the deoxed version.
Does anyone has the same problems?

Need some help please

Hi guys..
Few of you guys might already know me from around the forums. I know my ins and outs of android but today i am kinda stuck and i have not got a clue what to do. Here is the story.
Currently on my device i have a clear sd card. Only things i have on there is a slimkat build and gapps ready to flash. Problem is when i tried to make a backup it failed. Running TWRP recovery 2.6.0.0. Tried different things to get it working and nothing.
Now i tried to use a toolkit to be able to push the files to flash and get my phone going and still nothing it just goes back into recovery and nothing...Anyways another thing is adb is not working as it should...in recovery it recognizes my phone as connected but when in bootloader it does not
any help would be appreciated

Just some ideas here:
On device:
Try other version of TWRP or Multirom TWRP or CWM.
On PC:
Reinstall driver (Universal Naked Driver)

wcn said:
Just some ideas here:
On device:
Try other version of TWRP or Multirom TWRP or CWM.
On PC:
Reinstall driver (Universal Naked Driver)
Click to expand...
Click to collapse
kinda in the process reflashing stock factory settings again and see what happens..many thanks anyway...
is there anything wrong with TWRP? cause anything i do it fails and i have not got a clue why

There are mixtures of results of peoples using different versions of TWRP/MultiromTWRP/CWM and nobody had a dam* clue what/why causes the incompatibility. Btw, I'm on latest MultiromTWRP which works great for me flashing variants of roms. Anyway, happy reflashing.

why dont you update twrp to 2.6.3.3

rakludnet said:
why dont you update twrp to 2.6.3.3
Click to expand...
Click to collapse
i have..but even that one has given me troubles..the thing that seems to work is when you go into mounts just untick the system and everything seems to work okay..am just surprised that this is an issue though

[Q] Tried to update ATT G2 booted into TWRP, unable leave TWRP or go to Download mode

When I got my ATT G2 I rooted it, and installed TWRP custom Recovery. A week ago I got a system update notification, without thinking I updated the phone. It rebooted into TWRP recovery, and all I can do is navigate around the Recovery. I factory restored my phone, so I don't have SU, and I can't enter download mode. Any ideas on how I can fix my phone, or go about getting it replace?

SpectralFlames said:
When I got my ATT G2 I rooted it, and installed TWRP custom Recovery. A week ago I got a system update notification, without thinking I updated the phone. It rebooted into TWRP recovery, and all I can do is navigate around the Recovery. I factory restored my phone, so I don't have SU, and I can't enter download mode. Any ideas on how I can fix my phone, or go about getting it replace?
Click to expand...
Click to collapse
You could try pushing a rom to twrp from adb if your PC doesn't recognize try Koush universal drivers to make it recognize

RubbleTea said:
You could try pushing a rom to twrp from adb if your PC doesn't recognize try Koush universal drivers to make it recognize
Click to expand...
Click to collapse
Could you give me instructinos on how I would do that?

I was having the same issue after accidentally installing an update on my VZW G2. I tried evey solution for 9 hours with no luck including the Koush universal drivers. The only way I could get the phone to be recognized by any computer was to use ubuntu. Once I had the JDK and SDK installed I ran the commands from this tutorial - http://forum.xda-developers.com/showthread.php?t=2451696
I hope this helps someone out
if you dont have ubuntu installed on a computer you could always make a live cd and run it from that

CoryFNM said:
I was having the same issue after accidentally installing an update on my VZW G2. I tried evey solution for 9 hours with no luck including the Koush universal drivers. The only way I could get the phone to be recognized by any computer was to use ubuntu. Once I had the JDK and SDK installed I ran the commands from this tutorial - http://forum.xda-developers.com/showthread.php?t=2451696
I hope this helps someone out
if you dont have ubuntu installed on a computer you could always make a live cd and run it from that
Click to expand...
Click to collapse
MATE you saved my day...thanks so much....got the stock image back working again with the help of the command in the thread you where mentioning.
thanks once more.
best.
upage

Bricked my phone?

Well, I did something stupid and accidentally wiped system without backing up and now I don't have a ROM installed. When I try sideloading a ROM in recovery, I get the verification failed. I believe I am somehow back on android default recovery.
Can someone help me get a ROM pushed onto the device?
Thanks

phazey12 said:
Well, I did something stupid and accidentally wiped system without backing up and now I don't have a ROM installed. When I try sideloading a ROM in recovery, I get the verification failed. I believe I am somehow back on android default recovery.
Can someone help me get a ROM pushed onto the device?
Thanks
Click to expand...
Click to collapse
have you tried Odin'ing the stock tar back on?
i thought that usually fixes it, but please do a lil searching first before trying that

evilbeef54 said:
have you tried Odin'ing the stock tar back on?
i thought that usually fixes it, but please do a lil searching first before trying that
Click to expand...
Click to collapse
I ended up going back into download mode and using odin to install TWRP recovery. I guess that doesn't have problems with ADB sideload. Its sending now.. so I will see if it works. Had to do a few battery pulls =\ hope that didnt harm my device too much
TWRP ADB sideload worked. Weird... wonder why CWM adb sideload was having errors

phazey12 said:
I ended up going back into download mode and using odin to install TWRP recovery. I guess that doesn't have problems with ADB sideload. Its sending now.. so I will see if it works. Had to do a few battery pulls =\ hope that didnt harm my device too much
TWRP ADB sideload worked. Weird... wonder why CWM adb sideload was having errors
Click to expand...
Click to collapse
great, i was pretty sure flashing recovery or stock .tar with odin would work, but i am not 100% lol

Lost Custom recovery a while after i installed 4.4.4

Hi
I have a major problem!
I was following a guide and downgreaded to 4.4.2 . Installed Root and Custom recovery.
Installed 4.4.4 according to the guide i cant find right now and everything was working as it should! I then installed all apps i need and also Xposed framework,Busybox and another all in one tool.
Now when i try to boot into recovery mode its gone!
How do i get recovery back in a easy way or do i need to redo the process again by downgrading ? How did i loose recovery so i can avoid it again?

Thewiruz said:
Hi
I have a major problem!
I was following a guide and downgreaded to 4.4.2 . Installed Root and Custom recovery.
Installed 4.4.4 according to the guide i cant find right now and everything was working as it should! I then installed all apps i need and also Xposed framework,Busybox and another all in one tool.
Now when i try to boot into recovery mode its gone!
How do i get recovery back in a easy way or do i need to redo the process again by downgrading ? How did i loose recovery so i can avoid it again?
Click to expand...
Click to collapse
you lost recovery by installing and updating busybox...as stated on this forum dozens of times you CAN'T UPDATE busybox if you're on NUT dual recovery... The fix is easy, just run the dual recovery installer in your pc and the recovery will be back. Busybox is included with the recovery, no need to install it. if you read the dual recovery known issues you would know this, just search next time... http://forum.xda-developers.com/showpost.php?p=43698321&postcount=2

ptmaniac said:
you lost recovery by installing and updating busybox...as stated on this forum dozens of times you CAN'T UPDATE busybox if you're on NUT dual recovery... The fix is easy, just run the dual recovery installer in your pc and the recovery will be back. Busybox is included with the recovery, no need to install it. if you read the dual recovery known issues you would know this, just search next time... http://forum.xda-developers.com/showpost.php?p=43698321&postcount=2
Click to expand...
Click to collapse
Thanks well im on 4.4.4 and it doesn't seam to work just trying to reinstall recovery again. Guess i must roll back again . I didn't know that!I mean i haven't had the time to read everything here
Thanks again !

Thewiruz said:
Thanks well im on 4.4.4 and it doesn't seam to work just trying to reinstall recovery again. Guess i must roll back again . I didn't know that!I mean i haven't had the time to read everything here
Thanks again !
Click to expand...
Click to collapse
http://nut.xperia-files.com/ --> download this file: Z2-lockeddualrecovery2.8.0-RELEASE.installer.zip (23.91MB)
Enable USB Debugging on your phone, make sure correct drivers are installed on pc, run the installer for the recovery and choose option 1. Installation on ROM rooted with SuperSU.
Make sure you autorize your pc on your phone screen if asked. I've reinstalled / updated recovery lots of times on several z2's and it never failed, as long as root is working the install should succeed...

Thank you!
yes well i had the files but it didnt work until i first installed the drivers from flashtool again. Also i installed the ADB drivers i the 4th options of this tool . Now its working. Thanks again!