Hi, I am new to the nexus 4 and to android in general, And I just rooted my phone using one of the toolkits(don't remember the name and I am not in home to check). I wasn't sure I am rooted so I downloaded an app called "Root checker" and it says I'm not rooted. Is it 100% I'm not rooted or is there a more reliable way to check if I'm rooted? And if I'm not, any idea why it didn't work? I got the drivers properly and unlocked the phone.
Thx!
PriStol said:
Hi, I am new to the nexus 4 and to android in general, And I just rooted my phone using one of the toolkits(don't remember the name and I am not in home to check). I wasn't sure I am rooted so I downloaded an app called "Root checker" and it says I'm not rooted. Is it 100% I'm not rooted or is there a more reliable way to check if I'm rooted? And if I'm not, any idea why it didn't work? I got the drivers properly and unlocked the phone.
Thx!
Click to expand...
Click to collapse
Unlocking the bootloader does not root the phone. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2266654 to complete the process of gaining root access and installing a custom recovery on your Nexus.
This is exactly why you shouldnt use a toolkit. You have no idea what you have done to the phone, whereas if you did it manually/properly you would've known what you actually did. Did you flash a custom recovery? Did you flash the supersu zip through the recovery?
download a terminal emulator app. open it, type su(press enter), if it gives you a # sign then youre rooted, if not then youre not rooted. that app you used doesnt work. and yes, just unlocking the phone does not give you root.
I didn't mean I only unlocked the phone, I meant that after I unlocked it, I rooted. Anyways, I downloaded the emulator, typed sh in the emulator and it didn't show me the # so I guess I'm not rooted. I'll try doing it manually, thx!
PriStol said:
I didn't mean I only unlocked the phone, I meant that after I unlocked it, I rooted. Anyways, I downloaded the emulator, typed sh in the emulator and it didn't show me the # so I guess I'm not rooted. I'll try doing it manually, thx!
Click to expand...
Click to collapse
Not sure if it was just a typo, but you need to type "su" not "sh".
chromium96 said:
Not sure if it was just a typo, but you need to type "su" not "sh".
Click to expand...
Click to collapse
Yes I wrote su not sh. It just says "su not found" and shows a $.
PriStol said:
Yes I wrote su not sh. It just says "su not found" and shows a $.
Click to expand...
Click to collapse
yup, no root. if you installed a custom recovery, all you have to do is download the latest supersu or superuser binaries, then flash it via your recovery.
Is it really that hard to open a command prompt and type "fastboot oem unlock" and then type "fastboot flash recovery desiredrecovery.img" and flash the supersu.zip through recovery...
Sent from my Nexus 4 using xda app-developers app
I am pretty much new to android so I didnt really understand most of the things u said. I'll try to learn more about those things but if you could explain more about what u wrote it would be really nice.
Oh and I just got home and checked what toolkit I used, and it is WugFresh toolkit, and below the ROOT button I ticked the "also flash custom recovery" so now I just need to download the superuser binaries and then flash it throguh the recovery?
Thibaultvw said:
Is it really that hard to open a command prompt and type "fastboot oem unlock" and then type "fastboot flash recovery desiredrecoveryname.img and flash the supersu.zip through recovery...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i agree.
the issue is that these root toolkits are so pushed around here(even posted in the original development section, wtf???) that people think that root toolkits are easier. they difference being that you have to read a little if you never rooted the right way(and you also have to figure out the toolkit). but once you know how to do it the right way, it literary takes 3-4 minutes to root the phone.
---------- Post added at 05:34 PM ---------- Previous post was at 05:31 PM ----------
PriStol said:
I am pretty much new to android so I didnt really understand most of the things u said. I'll try to learn more about those things but if you could explain more about what u wrote it would be really nice.
Oh and I just got home and checked what toolkit I used, and it is WugFresh toolkit, and below the ROOT button I ticked the "also flash custom recovery" so now I just need to download the superuser binaries and then flash it throguh the recovery?
Click to expand...
Click to collapse
if it flashed a recovery for you, then yes. it might of just booted a recovery for you too for a 1 time use, if so then youll have to flash your recovery again later.
simms22 said:
i agree.
the issue is that these root toolkits are so pushed around here(even posted in the original development section, wtf???) that people think that root toolkits are easier. they difference being that you have to read a little if you never rooted the right way(and you also have to figure out the toolkit). but once you know how to do it the right way, it literary takes 3-4 minutes to root the phone.
---------- Post added at 05:34 PM ---------- Previous post was at 05:31 PM ----------
if it flashed a recovery for you, then yes. it might of just booted a recovery for you too for a 1 time use, if so then youll have to flash your recovery again later.
Click to expand...
Click to collapse
I remember that when I rooted through the toolkit it said that it will flash the recovery temporarily, so I guess it was just for the root proccess and I do need to flash it again. Oh and by command prompt you guys mean the cmd in the computer or there is a command prompt in the phone somewhere?
And another question; I want to do the whole thing of unlocking bootloader, flashing a custom recovery and rooting again, but now doing it without the toolkit, will it do something If I already unlocked the bootloader but now I Do it again? or If I will flash a custom recovery twice?
PriStol said:
I remember that when I rooted through the toolkit it said that it will flash the recovery temporarily, so I guess it was just for the root proccess and I do need to flash it again. Oh and by command prompt you guys mean the cmd in the computer or there is a command prompt in the phone somewhere?
And another question; I want to do the whole thing of unlocking bootloader, flashing a custom recovery and rooting again, but now doing it without the toolkit, will it do something If I already unlocked the bootloader but now I Do it again? or If I will flash a custom recovery twice?
Click to expand...
Click to collapse
no, since youre unlocked. if you wanted to, you can always flash the factory img via fastboot and do everything over again. nevertheless, use fastboot to flash the recovery permanently. yes, command prompt in the desktop(adb or fastboot). but really, once you learn how, your next nexus will be rooted in just a few minutes, since its the same process for every nexus. unlock the bootloader(fast oem unlock, fastboot flash a custom recovery, flash either a custom rom or the su binaries, then reboot. thats all)
simms22 said:
no, since youre unlocked. if you wanted to, you can always flash the factory img via fastboot and do everything over again. nevertheless, use fastboot to flash the recovery permanently. yes, command prompt in the desktop(adb or fastboot). but really, once you learn how, your next nexus will be rooted in just a few minutes, since its the same process for every nexus. unlock the bootloader(fast oem unlock, fastboot flash a custom recovery, flash either a custom rom or the su binaries, then reboot. thats all)
Click to expand...
Click to collapse
Thanks for all your help dude I did it!!! I used this guide: http://forum.xda-developers.com/showthread.php?t=2266654 and I was a little bit stressed but it literally took like 10 minutes and im rooted! This cmd linked with android thing rocks lol.
PriStol said:
Thanks for all your help dude I did it!!! I used this guide: http://forum.xda-developers.com/showthread.php?t=2266654 and I was a little bit stressed but it literally took like 10 minutes and im rooted! This cmd linked with android thing rocks lol.
Click to expand...
Click to collapse
simms22 said:
Click to expand...
Click to collapse
I actually got another question so I figured I will ask you since I dont want to open a lot of threads :laugh: , Can you tell me what is deodexed/odexed, I saw it in a requirement for something that I wanted and I dont really know what this means.
PriStol said:
I actually got another question so I figured I will ask you since I dont want to open a lot of threads :laugh: , Can you tell me what is deodexed/odexed, I saw it in a requirement for something that I wanted and I dont really know what this means.
Click to expand...
Click to collapse
generally, stock roms are odexed. most other roms will be deodexed. people deodex them because it makes the rom themeable. heres an old link, but it explains http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
Related
i posted this here cause no one answers my Q&A posts, but here's the story - i was running CM7 on my phone and i was having problems with my phone and decided to restore to stock and unroot via PD15IMG.zip, but i didnt know how to undo gfree cause grankin's instructions are all over the place. so the PD15IMG.zip did it's thing but it says update failed and reboot. so i reboot and the phone goes to the android recovery, not the CWM recovery. what do i do to get back on track, cause its not bricked if i can go to the bootloader and recovery, right? im stuck
This may or may not be the issue, but what recovery version are you running?
TeeJay3800 said:
This may or may not be the issue, but what recovery version are you running?
Click to expand...
Click to collapse
well, it WAS CWM 3.0.0.6 but now it's the stock android recovery, i think i might try installin CWM by adb since s is still off...
I2IEAILiiTY said:
well, it WAS CWM 3.0.0.6 but now it's the stock android recovery, i think i might try installin CWM by adb since s is still off...
Click to expand...
Click to collapse
You can use ADB or even fastboot if you have the engineering SPL. Once you have a good recovery installed, it's just a matter of wiping everything and flashing a stable ROM. If CM7 didn't work well for you but you want Gingerbread and the plain Android look, try RoyalGinger.
TeeJay3800 said:
You can use ADB or even fastboot if you have the engineering SPL. Once you have a good recovery installed, it's just a matter of wiping everything and flashing a stable ROM. If CM7 didn't work well for you but you want Gingerbread and the plain Android look, try RoyalGinger.
Click to expand...
Click to collapse
i decided to reroot cause all roms i installed, even after clean wipes, would lag and be unresponsive at times. and what's SPL? i'm kinda new to the android game, but iphones and ipods are a different story...
I2IEAILiiTY said:
i decided to reroot cause all roms i installed, even after clean wipes, would lag and be unresponsive at times. and what's SPL? i'm kinda new to the android game, but iphones and ipods are a different story...
Click to expand...
Click to collapse
The SPL is often referred to as "hboot" or "bootloader". It sounds like you're having enough trouble as it is, so I wouldn't worry about that. If you still have S-OFF, then you're still rooted. I honestly don't think that un-rooting and the re-rooting will solve your problems. It's possible your previous recovery was corrupt, that's why everything you flashed was slow (although apps and setups can also cause that). I would flash CWM 3.0.0.6 via ADB and then try another ROM.
TeeJay3800 said:
The SPL is often referred to as "hboot" or "bootloader". It sounds like you're having enough trouble as it is, so I wouldn't worry about that. If you still have S-OFF, then you're still rooted. I honestly don't think that un-rooting and the re-rooting will solve your problems. It's possible your previous recovery was corrupt, that's why everything you flashed was slow (although apps and setups can also cause that). I would flash CWM 3.0.0.6 via ADB and then try another ROM.
Click to expand...
Click to collapse
Or too much of a load for the CPU settings if he has it Under or over clocked... or a bad kernel (aka not one fauxs ;D )
Sent from my HTC Glacier using XDA Premium App
TeeJay3800 said:
The SPL is often referred to as "hboot" or "bootloader". It sounds like you're having enough trouble as it is, so I wouldn't worry about that. If you still have S-OFF, then you're still rooted. I honestly don't think that un-rooting and the re-rooting will solve your problems. It's possible your previous recovery was corrupt, that's why everything you flashed was slow (although apps and setups can also cause that). I would flash CWM 3.0.0.6 via ADB and then try another ROM.
Click to expand...
Click to collapse
how do i get adb to work in bootloader? cause it obviously wont in the android recovery
Nicgraner said:
Or too much of a load for the CPU settings if he has it Under or over clocked... or a bad kernel (aka not one fauxs ;D )
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
i've used faux's and grankin's...it's still bad
I2IEAILiiTY said:
how do i get adb to work in bootloader? cause it obviously wont in the android recovery
Click to expand...
Click to collapse
just kidding, i figured it out...
but when i try to use the method on unlockr.com (not sure if everyone does it this way) i cant navigate to adb via the command terminal
See here for instructions on setting up ADB. You can't use ADB while in your bootloader, that's what fastboot is for. ADB is done with the phone fully booted.
I2IEAILiiTY said:
just kidding, i figured it out...
but when i try to use the method on unlockr.com (not sure if everyone does it this way) i cant navigate to adb via the command terminal
Click to expand...
Click to collapse
alright, the problem right now is, i've figured out how to use usb on my f***ed up phone, but the drivers won't install, and adb is still being a pain in the arse.
I2IEAILiiTY said:
alright, the problem right now is, i've figured out how to use usb on my f***ed up phone, but the drivers won't install, and adb is still being a pain in the arse.
Click to expand...
Click to collapse
That doesn't tell me much. Do you get an error when running "htcdrivers.exe" during the setup procedure?
TeeJay3800 said:
That doesn't tell me much. Do you get an error when running "htcdrivers.exe" during the setup procedure?
Click to expand...
Click to collapse
lol, just kidding. i didn't see your post til i said that. alright, so do i type fastboot devices or whatever from the command menu and then install CWM?
I2IEAILiiTY said:
lol, just kidding. i didn't see your post til i said that. alright, so do i type fastboot devices or whatever from the command menu and then install CWM?
Click to expand...
Click to collapse
It is that simple, but only if you have the engineering SPL/hboot/bootloader. Towards the bottom of this post is instructions for flashing that.
TeeJay3800 said:
It is that simple, but only if you have the engineering SPL/hboot/bootloader. Towards the bottom of this post is instructions for flashing that.
Click to expand...
Click to collapse
yea...i didn't take the risk of flashing that when i rooted my phone...will i still be able to flash this recovery img?
I2IEAILiiTY said:
yea...i didn't take the risk of flashing that when i rooted my phone...will i still be able to flash this recovery img?
Click to expand...
Click to collapse
Yes, in fact fastboot is the safest way to flash things like recoveries. Once the SPL is installed, boot the phone normally, connect ADB, enter "reboot bootloader", once the phone has booted into the SPL enter "fastboot flash recovery recovery.img" and press enter. Just remember to have the IMG file in the ADB folder of your computer.
TeeJay3800 said:
Yes, in fact fastboot is the safest way to flash things like recoveries. Once the SPL is installed, boot the phone normally, connect ADB, enter "reboot bootloader", once the phone has booted into the SPL enter "fastboot flash recovery recovery.img" and press enter. Just remember to have the IMG file in the ADB folder of your computer.
Click to expand...
Click to collapse
so, in order to complete this, do i need the engineering hboot?
Only to do it via fastboot (the safest way). You can also do it from the terminal emulator while the phone is booted normally.
TeeJay3800 said:
Only to do it via fastboot (the safest way). You can also do it from the terminal emulator while the phone is booted normally.
Click to expand...
Click to collapse
my phone is still stuck in the boots and recoveries is the problem. i don't have the engineering hboot and when i try to flash the recovery.img it says writing recovery...failed
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!!!
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.
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.
hello guys this guide helps you to root your nexus 4 (4.3) and install custom recovery
things needed
1)superuser http://d-h.st/Hhw
2)twrp http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img
3)andriod sdk (google it)
* [dont have sdk? then download this http://d-h.st/jCU a replacement for sdk/platformtools (this tools include stuff for windows,linux and mac too.)]
4)adb drivers installed (follow the below mentioned guide)
note:- this is almost same process as this guide http://forum.xda-developers.com/showthread.php?t=2018179 but just updated for 4.3 version
ROOTING process
1)I hope your boot loader is unlocked, if not first unlock it and then start the rooting process and turn on usb debugging (follow above mentioned guide for unlocking bootloader and to turn on usb debugging) after unlocking bootloader reboot device and then copy root.zip(links above) into your phones storage and then reboot to fastboot
2)now download the twrp recovery image and rename it to twrp and move it to sdk/platform tools. in the same directory(i.e platformtools directory) open cmd prompt(to open cmd prompt press shift+rightclick at the same time and select open cmd prmpt window option) and type (without quotes) "fastboot flash recovery twrp.img" and thats it you have flashed twrp
3)now go to twrp (recovery mode) and flash the root.zip (that u copied to the phones storage earlier) and that's it u have obtained the root access.
im not responsible if u bricked your device do it at your own risk
follow this wonderful video if u have any problem or trouble http://www.youtube.com/watch?v=jn5ih0omlxI
hit thanks button if this thread helped ya
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
thank you
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
Thank you I will update that!
thank you
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
BTW you can update that manually via WiFi from playstore as chainfire mentioned in the thread that "if u already have root root access then update it from playstore"
Except the bug fixed version of supersu, there's nothing different from the original thread...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
The latest su version is not compatible with 4.3 yet...only v1.43 is compatible presently...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
when i enter the command line the command window gets stuck at <waiting for device> ........ I made sure that i have the drivers are properly configured and the nexus unlocked ...... any ideas why this happens ??
M.Zaki said:
when i enter the command line the command window gets stuck at <waiting for device> ........ I made sure that i have the drivers are properly configured and the nexus unlocked ...... any ideas why this happens ??
Click to expand...
Click to collapse
Hi,
I can suggest you some thing but i am not responsible if u bricked your device do it at your own risk
I had same issue " waiting for device" SO you need to install correct drivers for your device i can suggest you to download nexus 4 toolkit version 2 from here http://forum.xda-developers.com/showthread.php?t=1995688 and you need disconnect your nexus from usb and open your toolkit and you need :
1.choose option 13 "13. Android 4.2.2 [Build JDQ39]" (I know that your version is 4.3 but the drivers for PC is samething)
2.It will download drivers for your pc
3.Now choose option 1 that say " 1. Install Device Drivers on your PC [DO THIS FIRST] [UnPlug Device First] "
4. After driver installation you can close this tool and try again to flash your recovery like you did it before with (See above "ROOTING process")
Let me know if you succeed
Good luck
When I try to load the YT vid it says "invalid request"...
Oh its more than a vid. I am sorry in the android app it doesnt show the whole post for any reason.
And why download the whole sdk? Grab the platform tools from efrant's tutorial on how to flash a factory image. Then just place the desired recovery in the same directory and you can flash the recovery.
Sent from my Nexus 4 using xda app-developers app
amnon.m said:
Hi,
I can suggest you some thing but i am not responsible if u bricked your device do it at your own risk
I had same issue " waiting for device" SO you need to install correct drivers for your device i can suggest you to download nexus 4 toolkit version 2 from here http://forum.xda-developers.com/showthread.php?t=1995688 and you need disconnect your nexus from usb and open your toolkit and you need :
1.choose option 13 "13. Android 4.2.2 [Build JDQ39]" (I know that your version is 4.3 but the drivers for PC is samething)
2.It will download drivers for your pc
3.Now choose option 1 that say " 1. Install Device Drivers on your PC [DO THIS FIRST] [UnPlug Device First] "
4. After driver installation you can close this tool and try again to flash your recovery like you did it before with (See above "ROOTING process")
Let me know if you succeed
Good luck
Click to expand...
Click to collapse
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern
M.Zaki said:
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern
Click to expand...
Click to collapse
I am very happy
M.Zaki said:
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern
Click to expand...
Click to collapse
so it might not have recognized your adb drivers at the first time.or you could have just downloaded the nexus4toolkit by mrskip and installed adb from it. anyways did u root it?
Thibaultvw said:
When I try to load the YT vid it says "invalid request"...
Oh its more than a vid. I am sorry in the android app it doesnt show the whole post for any reason.
And why download the whole sdk? Grab the platform tools from efrant's tutorial on how to flash a factory image. Then just place the desired recovery in the same directory and you can flash the recovery.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
now try the link i fixed it
punitthereddevil said:
Except the bug fixed version of supersu, there's nothing different from the original thread...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
The latest su version is not compatible with 4.3 yet...only v1.43 is compatible presently...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
Click to expand...
Click to collapse
as i mentioned in the thread "this is the similar guide as that is mentioned above just updated for 4.3 version"
Just one question do the recovery flashed this way stick after reboot even on stock ROM? I remember something about having yo flash an additional ZIP for that...
Sent from my Nexus 4 using Tapatalk 4 Beta
Hi guys,
I know this topic is about installing custom recovery, but does anybody knows hot to root android 4.3 without flashing custom recovery? Yesterday I tried to boot both CWM and TWRP using:
Code:
fastboot boot recovery.img
All I got was a blank screen...
bartiki said:
Hi guys,
I know this topic is about installing custom recovery, but does anybody knows hot to root android 4.3 without flashing custom recovery? Yesterday I tried to boot both CWM and TWRP using:
Code:
fastboot boot recovery.img
All I got was a blank screen...
Click to expand...
Click to collapse
i have the same problem with "fastboot boot xxxx.img"!! both CWM and TWRP , return blank!
I actually found this today:
http://forum.xda-developers.com/showthread.php?t=2380675
they say:
the new version of bootloader shipped with Android 4.3 factory image changed some of the "fastboot boot" command so you need to specify a kernel commandline to use "fastboot boot" command.
Click to expand...
Click to collapse
for Nexus 4, it's:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
although I don't have time to test it out right now
bartiki said:
I actually found this today:
http://forum.xda-developers.com/showthread.php?t=2380675
they say:
for Nexus 4, it's:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
although I don't have time to test it out right now
Click to expand...
Click to collapse
yes.. now i find this me too and work!!!
i install the SuperSU , but now do n't installing the binary file. stuck on "installing, please wait..." any ideas?
EDIT: uninstall the update of SuperSU (v.1.51) and return to stock (that flashed before v1.43) AND WORKING!! ( no prompt to update the binary file..) any ideas? the v.1.51 maybe not working??
bbsnick said:
yes.. now i find this me too and work!!!
i install the SuperSU , but now do n't installing the binary file. stuck on "installing, please wait..." any ideas?
EDIT: uninstall the update of SuperSU (v.1.51) and return to stock (that flashed before v1.43) AND WORKING!! ( no prompt to update the binary file..) any ideas? the v.1.51 maybe not working??
Click to expand...
Click to collapse
Somebody mentioned this on first page newest su not compatible only v1.43
Sent from my Nexus 4 using Tapatalk 4 Beta
boysetsfire said:
Just one question do the recovery flashed this way stick after reboot even on stock ROM? I remember something about having yo flash an additional ZIP for that...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yep it still works after reboot . no problem with that