Hi, i updated to 4.4.3 via ota update. After that i tried to open SuperSU and it says 'There is no SU binary instanned and superSU cannot install it.'
Did i lost root? Do i need to start from the beggining ?
I was trying to flash Franco Kernel and i realized that there is a problem after i tried to enter recovery mode. My device failed to enter recovery mode showing me a dead android with a red exclamation mark.
Thanks in advance !!
1) the dead android is stock android recovery
2) yes you lost root
solution: reflash a custom recovery in fastboot and then flash the supersu zip and you're done.
there are a ton of threads about this issue and how to solve it all over the place. please search next time.
Actually he is not alone. I too updated ota to 4.4.3 and lost root. I searched and searched and I am sure the answer is buried "somewhere" but I couldn't find the answer to *my* question.
I previously rooted my Nexus 5, 4.4.2 using adb and Fastboot, but my question is which image do I use for TWRP and 4.4.3? Is 4.4.3 still called hammerhead or something else? Those names are confusing to non experts and flashing the wrong img can brick the phone.
Which TWRP recovery image do I use?
Which Supersu do I use?
And where do I find them?
Thanks.
Anderson2 said:
Actually he is not alone. I too updated ota to 4.4.3 and lost root. I searched and searched and I am sure the answer is buried "somewhere" but I couldn't find the answer to *my* question.
I previously rooted my Nexus 5, 4.4.2 using adb and Fastboot, but my question is which image do I use for TWRP and 4.4.3? Is 4.4.3 still called hammerhead or something else? Those names are confusing to non experts and flashing the wrong img can brick the phone.
Which TWRP recovery image do I use?
Which Supersu do I use?
And where do I find them?
Thanks.
Click to expand...
Click to collapse
The device is hammerhead. The latest official twrp is fine and same with super su. Don't use tool kits that way you know what to do when something like this happens.
This will take you start to finish you were rooted so im assuming your bootloader is unlocked and you can start with flashing recovery image just be sure to read it all .
http://forum.xda-developers.com/showthread.php?t=2507905
Sent from my Nexus 5 using Tapatalk
Anderson2 said:
Actually he is not alone. I too updated ota to 4.4.3 and lost root. I searched and searched and I am sure the answer is buried "somewhere" but I couldn't find the answer to *my* question.
I previously rooted my Nexus 5, 4.4.2 using adb and Fastboot, but my question is which image do I use for TWRP and 4.4.3? Is 4.4.3 still called hammerhead or something else? Those names are confusing to non experts and flashing the wrong img can brick the phone.
Which TWRP recovery image do I use?
Which Supersu do I use?
And where do I find them?
Thanks.
Click to expand...
Click to collapse
Of course you lost root, that's normal. For twrp go to goo.im. for super su Google chainfire supersu xda. Very simple, very easy
Sent from my Nexus 5 using XDA Free mobile app
Got this puppy in the mail today and fastboot unlocked the BL before I even saw a start screen. Took 4.4.3 then fastboot flashed TWRP. Installed SuperSU in recovery.
Boom! Rooted, unlocked and updated.
P.S. howdy y'all
Sent from my Nexus 5 using Tapatalk
Howdy
Sent from my Nexus 5 using Tapatalk
Just use Nexus Root Toolkit its so easy google it.:cyclops:
Lost root 4.4.4
If you (and you will) loose root after installing the zip for 4.4.4 go to http://download.chainfire.eu/446/SuperSU/ and download the zip. use recovery to install.
CliffordS
Sent from my Nexus 5 using Tapatalk[/QUOTE]
people...!
this is exactly tbe same as the very first android update ever in 2008.. if you update via ota or stock manually, YOU WILL LOSE ROOT. stock rom is not rooted by default. you can not expect to have root when updating stock! this is just silly people. the simplest search on google brings you years, yes years, of the same exact question being asked thousands of times over.. and yes, you will also lose your custom recovery.
chainsuk said:
Just use Nexus Root Toolkit its so easy google it.:cyclops:
Click to expand...
Click to collapse
Yes, easy to make you think you "bricked" your phone.
Sent from my Nexus 5
simms22 said:
people...!
this is exactly tbe same as the very first android update ever in 2008.. if you update via ota or stock manually, YOU WILL LOSE ROOT. stock rom is not rooted by default. you can not expect to have root when updating stock! this is just silly people. the simplest search on google brings you years, yes years, of the same exact question being asked thousands of times over.. and yes, you will also lose your custom recovery.
Click to expand...
Click to collapse
Oh dear. So much this.... I have but one thanks to give to this post...
It's like people are completely baffled at this when it literally happens with every freaking update...
#stayparanoid
Just use wugs nexus tool I lost root and fixed it with the root option. No messing just a few clicks its idiot proof
Sent from my Nexus 5 using xda premium
stewartk said:
Just use wugs nexus tool I lost root and fixed it with the root option. No messing just a few clicks its idiot proof
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Yes, but it also makes you look like an idiot when you post on here complaining something doesn't work because of use of a toolkit.
Rooting is just flashing a custom recovery then flashing SuperSU. If you need a toolkit to assist with something as simple as that then I suggest you revert back to stock factory images and stay away from anything regarding "root".
Sent from my Nexus 5
simms22 said:
people...!
this is exactly tbe same as the very first android update ever in 2008.. if you update via ota or stock manually, YOU WILL LOSE ROOT. stock rom is not rooted by default. you can not expect to have root when updating stock! this is just silly people. the simplest search on google brings you years, yes years, of the same exact question being asked thousands of times over.. and yes, you will also lose your custom recovery.
Click to expand...
Click to collapse
Yep, I'm surprised people still ask this question. If you know how to flash an OTA, you should know what happens after. On a side note, when I flashed the 4.4.3 OTA, I actually didn't lose the TWRP. I just used the OTA from the OTA thread. I just thought it strange.
Not true i have used it thousands of others have without a problem, i could say people have bricked their phone with fastboot NOTHING is 100% safe....
chainsuk said:
Not true i have used it thousands of others have without a problem, i could say people have bricked their phone with fastboot NOTHING is 100% safe....
Click to expand...
Click to collapse
ok, i dont know what youre talking about but ill bite.. show me one person thats bricked their phone with fastboot.
I cant show you i can only tell you what ive read on these very forums for whatever reason ppl have reported on xda that their phones have bootlooped and bricked, it my have been user error on commands or glitches i dont know,and all i was saying about Nexus root toolkit is that i have used it many times without a problem as have other ppl but im sure that some ppl have come unstuck but for me its been fine....
Lethargy said:
Yes, but it also makes you look like an idiot when you post on here complaining something doesn't work because of use of a toolkit.
Rooting is just flashing a custom recovery then flashing SuperSU. If you need a toolkit to assist with something as simple as that then I suggest you revert back to stock factory images and stay away from anything regarding "root".
Sent from my Nexus 5
Click to expand...
Click to collapse
I've never had a problem using root kits. I also know how to do it other ways. But some idiots like to do it root kit ways.
Sent from my Nexus 5 using xda premium
stewartk said:
I've never had a problem using root kits. I also know how to do it other ways. But some idiots like to do it root kit ways.
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Maybe you should talk to this guy
http://forum.xda-developers.com/showthread.php?p=53573890
Sent from my Nexus 5 using XDA Free mobile app
Related
I have quick question about rooting this phone I used to have mytouch 3g I had rooted back in day. I was thinking about rooting it for superuser etc but I dont want to run custom roms atm. With Clockwork mod will it still t-mobile OTA update without problems or can the root/clockwork mod interfere and cause problems?
Thanks for the info
Updates come directly from Google.
Sent from my Nexus S
jwr2d2 said:
Updates come directly from Google.
Sent from my Nexus S
Click to expand...
Click to collapse
That doesn't answer the question, you can root without installing Clockwork Recovery. Use SuperBoot method by paulobrien.
zephiK said:
That doesn't answer the question, you can root without installing Clockwork Recovery. Use SuperBoot method by paulobrien.
Click to expand...
Click to collapse
I un-rooted because I had no need for custom recovery as I have no plans to flash a custom ROM, so if I use SuperBoot, I will be able to receive the OTA updates without a hitch from Google, correct?
Sorry for posting in wrong section, Anyways I went through did all the research and here is all the information you need to do it. Also thanks zephiK for the reply that kinda got me on the right track with everything.
[GUIDE] Android Sdk with fastboot, adb and usb drivers
[GUIDE] Unlock/Lock Nexus S Bootloader
[HACK] 23/Dec GRH78: Superboot - rooting the Nexus S
I didnt want to take chance on bad file for the .bat file so if you dont have MD5 checker here is one for firefox.
So to recap... This method will get your Nexsus S rooted, and keep your stock 2.3.1 rom with no modification to the recovery.
...Enjoy...
So just to confirm, this setup will still prompt the OTA update correct? If I accept it I would have to reroot the phone correct?
shata said:
So just to confirm, this setup will still prompt the OTA update correct? If I accept it I would have to reroot the phone correct?
Click to expand...
Click to collapse
as long as you keep your stock ROM it will prompt you,
the custom roms have the portion that calls back to the mothership removed
slowz3r said:
as long as you keep your stock ROM it will prompt you,
the custom roms have the portion that calls back to the mothership removed
Click to expand...
Click to collapse
Thanks man, appreciate the reply.
It will prompt you but will more than likely fail to install.
shata said:
Sorry for posting in wrong section, Anyways I went through did all the research and here is all the information you need to do it. Also thanks zephiK for the reply that kinda got me on the right track with everything.
[GUIDE] Android Sdk with fastboot, adb and usb drivers
[GUIDE] Unlock/Lock Nexus S Bootloader
[HACK] 23/Dec GRH78: Superboot - rooting the Nexus S
I didnt want to take chance on bad file for the .bat file so if you dont have MD5 checker here is one for firefox.
So to recap... This method will get your Nexsus S rooted, and keep your stock 2.3.1 rom with no modification to the recovery.
...Enjoy...
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App
Sorry for post above, I tried to discard the message but it wouldn't delete. Anyway, excellent advice in this thread. Thanks everyone
Sent from my Nexus S using XDA App
My wife accidently updated her phone to the newest OTA and I am wondering if I can still root my phone.
Sent from my Nexus S 4G using XDA App
drsteven2 said:
My wife accidently updated her phone to the newest OTA and I am wondering if I can still root my phone.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
It's a Nexus, you can always root.
So I can root with the current root method with no problems?
Not to hijack your thread, but I didn't want to make an entirely new one and it's kind of a related question.
So I've never rooted my NS before and I'm on 2.3.4. Is there any way I can root without having to wipe my phone, or will I just have to bite the bullet and do it.
I've been perfectly fine without root up until now, but the new colors really bug me and would like to fix them.
Usually when you root data usually gets lost what are you trying save?. The only thing that u are going to be able to save are your contacts.
Sent from my Nexus S 4G using XDA App
drsteven2 said:
So I can root with the current root method with no problems?
Click to expand...
Click to collapse
Not sure what the "current root method" is, but it's the same process as usual: flash ClockworkMod Recovery, mount /system, apply the su zip, done.
(with the usual caveats about doing things properly so the recovery patcher doesn't trigger and remove CWM just after you flashed it)
ok well this is my scenerio..
i just bought my nexus s yesterday.... i got the OTA 2.3.4 and updated it..
i just want to know the EASIEST process to root my nexus s as i am not adb literate. Every phone that i had has been rooted previously so i never had to root a phone but i am getting all these threads to root the nexus s and damn it has to do with adb which i have no clue how to use.. but once im rooted i can change rom change themes etc.. its just the rooting process.. well any methods are welcome..
p.s sorry to jack your thread man
the first time I used adb was yesterday to unlock my nexus s and it really wasnt too bad so you should be good
Will this guide work with 2.3.4 without wipe everything? (i havent unlocked bootloader) h**p://download-apk.blogspot.com/2011/05/tutorial-rooting-unlock-bootloader-for.html ? If it's not, is there any way to root my nexus 2.3.4 with stock rom without wipe? I would appreciate any answers. Thank you.
Computar said:
Not to hijack your thread, but I didn't want to make an entirely new one and it's kind of a related question.
So I've never rooted my NS before and I'm on 2.3.4. Is there any way I can root without having to wipe my phone, or will I just have to bite the bullet and do it.
I've been perfectly fine without root up until now, but the new colors really bug me and would like to fix them.
Click to expand...
Click to collapse
Rooting does not require wiping IF your bootloader is unlocked. An open lock is shown below the Google tag when booting if you're unlocked.
Unlocking bootloader will always wipe for security reasons.
Make sure to sync contacts before doing anything. Then start here
http://forum.xda-developers.com/showthread.php?t=895545
After that, flash a custom roms by the developers. They already comes with root and updated kernels. Hope this helps
Its almost 12 at nite, off to bed i go.
I've seen many different rooting methods for the nexus s but unfortunately they don't allow rooting without unlocking the bootloader like the samsung vibrant allows is there anyway I can root my phone without unlocking the bootloader?
why I don't want to unloack the boot loader because I'm fine with the stock ROM on my nexus s. I was really into installing ROMs and things with my Vibrant but the Nexus S feels really complete so I feel like I don't need to unlock my boot loader
Also for the first time I have decent signal in my house after switiching from my blackberry to android so I don't wanna change my baseband and my battery life is good too so I don't want to mess with the kernel
Really? You posted in the same incorrect forum twice with the same question cut and pasted. Nice work!
Sent from my PC36100 using XDA Premium App
You know you can re-lock the bootloader with a fastboot command, right? And the little open lock goes away.
i'm sorry i accidentally reposted i pmed the moderator right away because i didn't know how to delete the post and this is the right section its a question...
i just have one question i can relock right but if i do unlock the bootloader will it change my kernel or baseband settings? i really couldn't care about the warranty and such
it's like opening the door....if you do nothing inside, nothing will happen
yes i get that but i can't flash back to the original recovery as of now and so no changes to the kernel and baseband alright thanks!!
also is there some sort of a "ODIN" availabale for nexus s because thats what I used to always flash my samsung vibrant back to stock. will OTA updates be affected if I root and unlock the bootloader?
anishs said:
also is there some sort of a "ODIN" availabale for nexus s because thats what I used to always flash my samsung vibrant back to stock. will OTA updates be affected if I root and unlock the bootloader?
Click to expand...
Click to collapse
Yes you can use Odin with Nexus S, but consider it the last resort because normally you can do everything via adb and fastboot -- that's the advantage of having a Google phone.
For OTA updates, I'm pretty sure it will not work because OTA update requires stock recovery but rooting requires you to flash a custom recovery.
suksit said:
Yes you can use Odin with Nexus S, but consider it the last resort because normally you can do everything via adb and fastboot -- that's the advantage of having a Google phone.
For OTA updates, I'm pretty sure it will not work because OTA update requires stock recovery but rooting requires you to flash a custom recovery.
Click to expand...
Click to collapse
thanks for that reply it explained everything can you just tell me if flashing a custom recovery change my baseband or kernel that's all i need to know now
@anishs no
Sent from my Nexus S using XDA App
thanks to everyone for helping a noob with a nexus s
Hey everyone,
So I think I may have done something strange and i'm not sure how to fix it. Long story short, screen cracked, so I bought a new one and I used TWRP to backup my original phone. So now, i'm just trying to unlock and root, you know, the usual. BTW, I tried using ABD/Fastboot, which I never typically do, but I heard it was more efficient and whatnot so I thought I try. I think the unlocking of the bootloader went well. And I even think I flashed recovery properly. But when I tried to access recovery, it prompted me for a password.
I read on the TWRP site I was supposed to let the phone boot as normal before accessing recovery. Oops. So I tried formatting all the data on the phone and no I have no OS or any files to recover from and adb push keeps giving me "Device not found" and now I don't know what to do.
Help?
EDIT: In case anyone has this issue searching threads, I just used Wug Toolkit to flash everything back to stock and then used the same Toolkit to unlock and root. TWRP isn't going to recognize a backup from a different phone. To my understanding, there is a way around that, but I didn't look into it. Oh, and apparently, don't flash the EFS partition lol
New Jer-Z said:
Hey everyone,
So I think I may have done something strange and i'm not sure how to fix it. Long story short, screen cracked, so I bought a new one and I used TWRP to backup my original phone. So now, i'm just trying to unlock and root, you know, the usual. BTW, I tried using ABD/Fastboot, which I never typically do, but I heard it was more efficient and whatnot so I thought I try. I think the unlocking of the bootloader went well. And I even think I flashed recovery properly. But when I tried to access recovery, it prompted me for a password.
I read on the TWRP site I was supposed to let the phone boot as normal before accessing recovery. Oops. So I tried formatting all the data on the phone and no I have no OS or any files to recover from and adb push keeps giving me "Device not found" and now I don't know what to do.
Help?
Click to expand...
Click to collapse
I never heard of this problem before, maybe you can use Odin to flash the recovery again
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
mpalomba3 said:
I never heard of this problem before, maybe you can use Odin to flash the recovery again
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
Click to expand...
Click to collapse
Oh, that reminds me, TWRP wasn't able to mount any of the directories, it seems. I think it can, now, but I remember seeing those errors in the log before I wiped everything. Thanks for that suggestion, i'll give it a shot.
No problem, report back if it works
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?
Odin is for Samsung devices
sent from my HAMMERHEAD neXus
New Jer-Z said:
I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?
Click to expand...
Click to collapse
Odin is a Samsung thing. Not LG.
What you'll need to do is flash the 4.4.2 factory image. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2513701
El Daddy said:
Odin is a Samsung thing. Not LG.
What you'll need to do is flash the 4.4.2 factory image. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
OK!
So, I used the Wug toolkit to basically flash everything to stock, and then root it. I installed TWRP using the app and I tried using the app to restore from my earlier back up. So, it boots into recovery but nothing happened. Looking at the log, it says the TWRP isn't able to locate the files. Trying to just restore from recovery isn't helpful because when I hit "Restore" nothing pops up. As if the SDCard partition isn't being accessed. I can't see any of the files in any directory. Anyone have any ideas?
You need to let the phone boot into android before flashing a custom recovery.
Sent from my Nexus 10 using Tapatalk
El Daddy said:
You need to let the phone boot into android before flashing a custom recovery.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I realize that now lol. Well, I fixed that, but now have a new issue. Any ideas for me?
Flashing the factory image erases everything. Such as backups stored on your phone.
Sent from my Nexus 10 using Tapatalk
El Daddy said:
Flashing the factory image erases everything. Such as backups stored on your phone.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I had a copy saved on my desktop, so I transferred it back.
New Jer-Z said:
I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?
Click to expand...
Click to collapse
Sorry about that, I have a gs4 so I thought Odin was for all devices
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
New Jer-Z said:
I had a copy saved on my desktop, so I transferred it back.
Click to expand...
Click to collapse
Did you put the backup on the root of the sdcard? I think it needs to be in the TWRP folder. You should first make a backup of your current rom even if it's stock rooted.
Sent from my Nexus 5 using Tapatalk
housry23 said:
Did you put the backup on the root of the sdcard? I think it needs to be in the TWRP folder. You should first make a backup of your current rom even if it's stock rooted.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Someone explained to me TWRP won't recognize a backup with a serial number from a different phone. So essentially, I will just have to forego it. I used Wug Toolkit to fix this issue and just flashed everything to stock and had the same toolkit unlock and root. Using ADB was a fail and cost me a whole afternoon lol
I just got the OTA update yesterday to 4.4.4 KitKat. I downloaded the "L" developer preview and was going to flash it on my phone. I rebooted into recovery only to find a droid with a red exclamation mark on it's head. I went into Titanium Backup and it said I didn't have root access.
I tried going onto GooManager and installing a recovery, and TWRP, all failed. I guess I'm going to have to use the CF-Auto Root kit again, but I have one question.
Is there any way to tell if my bootloader is still unlocked? Or will doing this wipe my entire phone out? I have a lot of stuff on here I cannot afford to lose, but also don't want to transfer nearly 30 gigs of stuff to a hard drive. D;
If it matters, when I turn my phone on, it shows a "lock key" and it's "unlocked". I cannot remember that ever being there until after I rooted and stuff when I got the phone. Does this mean my bootloader is still unlocked? Or will I need to unlock everything again.
I learned my lesson. Never again doing OTA update.
OTA removes root and flashes stock recovery. It does not relock your bootloader. The padlock signifies unlocked.
Sent from my Nexus 5 using Tapatalk
Ugh, thank you rootSU! ^.^ I'll use the Auto-Root tool and re-root the darn thing lol
snappycg1996 said:
Ugh, thank you rootSU! ^.^ I'll use the Auto-Root tool and re-root the darn thing lol
Click to expand...
Click to collapse
No. Fastboot flash recovery then root from recovery.
Sent from my Nexus 5 using Tapatalk
i guess you arent one for searching, as this has literally been answered hundreds of thousands of times.
you WILL lose root by updating an official rom, be it via ota or manual. the stock rom is NOT rooted, you can not assume that your root will carry over. it will also replace your custom recovery with the stock recovery. this has been known since the very first android update in 2008. do yourself a favor, search, read, educate yourself.
what you need to do is flash a custom recovery via fastboot, then flash the latest supersu in your newly flashed recovery. then reboot, thats it.
snappycg1996 said:
I just got the OTA update yesterday to 4.4.4 KitKat. I downloaded the "L" developer preview and was going to flash it on my phone.
<Snip>
I have a lot of stuff on here I cannot afford to lose, but also don't want to transfer nearly 30 gigs of stuff to a hard drive. D;
<Snip>
I learned my lesson. Never again doing OTA update.
Click to expand...
Click to collapse
I am just curious why you are flashing a Developer Preview that has not been tested, no threads as of right now from anyone who has flashed it and above all without backing up your stuff? We haven't broken down the preview yet to see what is in there, so if I, and this is just me here, were going to flash something that had high potential for "problems", I would back up or at the very least send all the important things up to the cloud.
OTA was not the problem/lesson to be learned here. I would suggest you read some of the inevitable threads that will pop up with all the answers that you are looking for.