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.
Related
Hey XDA
Iv had my Nexus 7 for a day now and am dying to root and mabe install CM10
i currently have a Samsung Galaxy S3 with CM10 on it...thot its extremly buggy sadly... anyways i have been looking up on how to root the nexus 7 but i need to know if i can instead of using toolkit can i instead just use odin to flash stock rom and cwm and so on instead of having to unlock the device?
i am used to using odin for flashing and cwm but here the nexus is close to the same with htc one x in the way it has that fastboot thing and from what iv heard the nexus 7 requires unlock before it can be rooted, also is the tookit the best way to unlock and root the device?
also does unlocking break the warrenty and if i ever decide to return to stock unroot how do i flash stock rom back onto the device? am not sure where i would find the stock roms for it and also can odin be used to flash it...:S
i hate sounding like a noob lol
ok iv used the toolkit 2.0 and its worked great so far...im stuck at not being able to boot into cwm recovery
it installed fine thru the toolkit but whenever i try to hold up and power i cant get it to boot into cwm recovery...
i tryed to reinstall again but still cant get it to boot into cwm am i doing something wrong?
Doing the following won't cause you to loose warranty:
- Unlocking the bootloader
- Rooting
- Flashing custom ROM's and Kernels (however, if you flash a custom kernel that causes your device to explode... I'm somewhat certain this won't be covered)
However, if you are doing anything like that, and have to send the device in for warranty, you "should" factory restore it. Google provides Factory Images for the Nexus 7, which can be restored to your device with semi-ease.
I use this guide to factory restore: http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html Some filenames might need changed though since I think that guide is based off an older factory image (instructions are the same though).
There is a good chance a toolkit also has an easy method for factory restoring, but I don't recommend this at all.
Stop using toolkits.
Sent from my Nexus 7 using Xparent White Tapatalk 2
ÜBER™ said:
Stop using toolkits.
Click to expand...
Click to collapse
Amen, +1. http://forum.xda-developers.com/showthread.php?t=1830108
encryptioncsta said:
ok iv used the toolkit 2.0 and its worked great so far...im stuck at not being able to boot into cwm recovery
it installed fine thru the toolkit but whenever i try to hold up and power i cant get it to boot into cwm recovery...
i tryed to reinstall again but still cant get it to boot into cwm am i doing something wrong?
Click to expand...
Click to collapse
I've never used a toolkit before (until this issue had me stuck). I'm unable to get the Nexus 7 to book into recovery (CWM) after flashing it via fastboot. After giving up, I rooted it using the toolkit.. scariest thing I've ever done.. it did work.. but I'd like to get to the bottom of why a number of people like me seem to be having issues flashing and booting CWM on the Nexus 7.
Did you rename the original system/recovery to .bak first?
Travisdroidx2 said:
Did you rename the original system/recovery to .bak first?
Click to expand...
Click to collapse
No, I flashed it as I normally do.. using the .img file. In this case, CWM.. recovery-clockwork-6.0.1.0-grouper.img
Why would renaming it to .bak be needed?
xyzulu said:
No, I flashed it as I normally do.. using the .img file. In this case, CWM.. recovery-clockwork-6.0.1.0-grouper.img
Why would renaming it to .bak be needed?
Click to expand...
Click to collapse
Its not actually.
Sent from my Nexus 7 using Xparent White Tapatalk 2
I had to rename the stock recovery under system to .bak before I could get twrp to work. Or else when I went into recovery it would get stuck on the android.
But I see you are using fast boot it should write over it.
Travisdroidx2 said:
I had to rename the stock recovery under system to .bak before I could get twrp to work. Or else when I went into recovery it would get stuck on the android.
But I see you are using fast boot it should write over it.
Click to expand...
Click to collapse
I didn't have to. Flashed twrp and forgot to put a ROM on it and went back into recovery and it was twrp still.
Sent from my Nexus 7 using Xparent White Tapatalk 2
I should of just flashed the image file and flashed it myself but I was in a hurry and used goo im and it bit me in the ass. Lesson learned.
Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message
IAmNice said:
usb debugging on? Have you checked that?
Click to expand...
Click to collapse
Hi. Yes mam (usb debugging on) have a look to the attachment.
Toolkit me boot into fastboot then reboot then for something to fastboot loaded and back to android and trying to upload the files but nothing superuser is not recorded because of (read-only file system).
have a look on the attachment is there to see everything ...
yep same issue here - problem with the forum regs is unless you have enough posts you can't actually address the issue to the appropriate person can you? Anyway, able to unlock but then is unable to root and rest due to a permissions problem. have tried as administrator but of coure this doesn't make any difference.
NexusTropers said:
Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message
Click to expand...
Click to collapse
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.
try:
http://forum.xda-developers.com/showthread.php?t=1796109
comminus said:
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.
Click to expand...
Click to collapse
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.
bazabaza said:
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.
Click to expand...
Click to collapse
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.
comminus said:
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.
Click to expand...
Click to collapse
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.
NexusTropers said:
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
Click to expand...
Click to collapse
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
NexusTropers said:
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.
Click to expand...
Click to collapse
I'm not really sure what you're trying to say...
I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.
comminus said:
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
I'm not really sure what you're trying to say...
Click to expand...
Click to collapse
1. THX u i try it.
2. AH sorry translator make crazy text.
homerbrew said:
I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.
Click to expand...
Click to collapse
Oki THX u i try this tool...
I'm also having this same problem but here's my story:
Using the Nexus 1.5.4 Toolkit, I Unrooted + Flashed jzo54k, success. I locked OEM, success. I unlocked again, success. Then I ran the root process again, and it keeps freezing at the android recovery screen. Following the prompt in the toolkit, I walked away for a few hours hoping time would resolve the issue.
If you're wondering why I unlocked + rooted, and decided to unroot, lock, unlock, and root again, its because I'm super-noob to anything android related after version 1.5, I wanted to learn the processes after I found out I was having troubles with certian things after my Nexus 7 updated from 4.1 to 4.1.2
I am having the same issue as you. 4.1.2 is not rooting for me. I can't install CWM or TWRP because it needs to rename recovery files, and to do that you need to be rooted. If I boot in recovery I always get stock
Having the same issue with a stock 4.1.2. I can unlock no problem but I cannot get it rooted. Everything appears to have worked, but it is not rooted. If I revert back to 4.1.1 I can unlock, root, etc. without issue. I was able to root 4.1.1 and use the root keeper app to then update to 4.1.2 and I was rooted still. However, it would not let me install CWM or anything. ROM Manager says it was installed, but booting to recovery always too me to stock.
Any ideas?
Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app
MetalMadness said:
Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I used Nexus Root Toolkit v1.5.4 and selected the "Flash Stock + Unroot" option. When prompted I choose the default 4.1.1 option and away it went.
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!
hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Indy1204 said:
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!
Click to expand...
Click to collapse
Thanks. I did this earlier and it didnt work, but I checked boot instead of flash
FLASH THE OLDER BOOTLOADER DON'T BOOT IT!!!
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
The robot lying on it's back is the stock recovery. You need to flash CWM/TWRP before you can do a Nandroid
itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
Do yourself a favour and learn how to use ADB instead of toolkits that do more harm than good if used by inexperienced users and you`ll learn to do it the right way.
Look here http://forum.xda-developers.com/showthread.php?t=1474956 for how to.
Youtube tutorial link http://www.youtube.com/watch?v=ZY4KSrgi-rE.
itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
If you have Rom Manager Installed and are rooted you should be able to install CWM thru it.
don't have flash recovery on rom manager
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?
itayze said:
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?
Click to expand...
Click to collapse
according to ROM Manager you already have CWM installed and its up to date. Have you tried booting into recovery using ROM Manager?
When I press reboot to recovery directly from rom manager it works...
I'm just affraid that in case that I brick or mess up something I won't be able to get to stock recovery mode.
volume down + power button = bootloader (android on his back) also called fastboot mode
use volume buttons to scroll to recovery then press power button to select it
you should then be in CWM recovery if its installed correctly.
If you are using a custom recovery your stock recovery is gone. You would have to use fastboot to flash the stock recovery image back onto the phone. Its rather simple to do as is flashing the stock image file back onto the phone.
that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Edit: I posted before you edited your comment.
even though I don't know adb, should I learn and follow this guide?
http://www.androidauthority.com/nexus-4-clockworkmod-recovery-134114
itayze said:
that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Click to expand...
Click to collapse
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312
kzoodroid said:
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium
El Daddy said:
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I call it a bug because its an annoying feature. There are a number of threads no how to remove it but using a toolkit to do it is just as easy.
thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !
itayze said:
thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !
Click to expand...
Click to collapse
Glad you got it working. I would still learn adb and fastboot. Though I too use the tool kit every now and then out of convenience.
I was using the tool kit here: [NEXUS 4 TOOLKIT V2.0.0]
I got the drivers to work and i unlocked my device then when the root procedure came around my device failed to flash the unsecure boot img.
so i went to download N-Cry's toolkit to root from their. This also refused to work now my phone will not boot. I can get to the google screen with the unlock logo and fastboot.
UnderZone7 said:
I was using the tool kit here: [NEXUS 4 TOOLKIT V2.0.0]
I got the drivers to work and i unlocked my device then when the root procedure came around my device failed to flash the unsecure boot img.
so i went to download N-Cry's toolkit to root from their. This also refused to work now my phone will not boot. I can get to the google screen with the unlock logo and fastboot.
Click to expand...
Click to collapse
try wiping data/factory reset then try to boot.
simms22 said:
try wiping data/factory reset then try to boot.
Click to expand...
Click to collapse
How do i do that?
UnderZone7 said:
How do i do that?
Click to expand...
Click to collapse
do you have a custom recovery installed? you would do it in the custom recovery. if you dont, you might have to flash the factory image via fastboot http://forum.xda-developers.com/showthread.php?t=2010312
doing everything the right way instead of a root toolkit is easier and faster, you just need to do a little reading first.
simms22 said:
do you have a custom recovery installed? you would do it in the custom recovery. if you dont, you might have to flash the factory image via fastboot http://forum.xda-developers.com/showthread.php?t=2010312
doing everything the right way instead of a root toolkit is easier and faster, you just need to do a little reading first.
Click to expand...
Click to collapse
The root part wasn't working so I never go to the flashing recovery
UnderZone7 said:
The root part wasn't working so I never go to the flashing recovery
Click to expand...
Click to collapse
So flash one
UnderZone7 said:
The root part wasn't working so I never go to the flashing recovery
Click to expand...
Click to collapse
as said above, flash one now via fastboot.
the right way to root a nexus in general terms.. fastboot oem unlock via fastboot, flash a custom recovery via fastboot, flash either the su binaries or a custom rom via your new custom recovery, reboot and profit. thats all that needs to be done when using any nexus, thats one reason we buy nexus devices
I don't think people understand what "brick" really means.
Sent from my iPad 4
Know why I love the XDA community so much?
Because after the 1 millionth "I bricked my Nexus, what do I do??" thread with someone who might not have done all the research they should have before flashing their device, XDA will still post helpful advice and generally help out, instead of posting comments like "omg read before you flash!!!".
And as stated above OP, try to stay clear of toolkits and stuff, at least starting out. That way, you learn a lot about what's going on in the background, and learn how you can prevent things from going wrong, and what to do when they do go wrong. I highly recommend reading at least the first 4 posts in this thread. It is extremely helpful.
simms22 said:
as said above, flash one now via fastboot.
the right way to root a nexus in general terms.. fastboot oem unlock via fastboot, flash a custom recovery via fastboot, flash either the su binaries or a custom rom via your new custom recovery, reboot and profit. thats all that needs to be done when using any nexus, thats one reason we buy nexus devices
Click to expand...
Click to collapse
Thank you so much for all your help. I used the guide got fastboot and the drivers working and I was able to flash a rom.
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?