I bought my 11 year old son a N7 yesterday for his birthday. I'm not new to Android, rooting, recovery & flashing ROMs. All my experience is with HTC Sense however. Is it a matter of unlocking bootloader *??* (HTC has htcdev.com for unlocking bootloader), flashing custom recovery via fastboot/adb and then flashing custom roms via recovery? I assume there is no S-Off or S-On for that matter with a Nexus. It is my son's 1st tablet and my family has seen dad brick a few phones in his day.. Lol Any suggestions would be much appreciated, including roms for a 11 year old boy...(and his dad lol).
Honestly? Just use it as is.
Sent from my Nexus 7 using XDA Free mobile app
actually Nexus 7 is so resistant to hard brick in my experience.
It is so easy to unlock bootloader.
1- install adb drivers and having fastboot application on your PC
2- enter to bootloader (turn off tablet > hold Vol - > power on)
3- connect Nexus 7 via USB
4- run in command prompt:
fastboot oem unlock
this will ask you to confirm factory reset and wipe all your data and voiding warrenty
5- done
after this, you have to flash a custom recovery (TWRP I prefer) to flash a custom ROM (I myself use Dirty Unicorn) and so on.
Related
After I got my new nexus, I decided to root it. I used mskips toolkit with 4.1 and it worked like a beaut. But I can't for the life of me root 4.1.2.
Checklist:
Downloaded the drivers succesfully
Can enter ADB succesfully. Under device manager it says "Google Nexus 7 ADB interface"
Tried WugFresh's toolkit
Unlocked bootloader
Tried installing custom recovery (see below)
(Checklist to know what I have done, for people to help me and future people with problems)
The reason adding CWM or TWRP doesn't work is because the device can't be rooted. You need to be rooted to change recovery file names, and whenever I boot recovery, I get the dead android and a red ! (stock recovery).
When it sees if busybox is installed, and sends the command, it comes back negative.
I'm having the exact same problem -- generating the same set of error messages as you show at the top of your screen capture. I bought a new Nexus 7 32GB and updated it to 4.1.2 before trying to root it. At the time I hadn't read anything that told me this might be a bad idea. I figured -- update to the latest version then root it. I've tried changing how I have it connected (media or camera), what USB port I connect to, what USB cable I use, which boot options I select -- NOTHING makes a difference. I have gotten my bootloader to unlock, or so it seems, as I've got the unlocked padlock image during boot up. But I'm totally stuck on how to proceed to get root.
lesdense said:
I'm having the exact same problem -- generating the same set of error messages as you show at the top of your screen capture. I bought a new Nexus 7 32GB and updated it to 4.1.2 before trying to root it. At the time I hadn't read anything that told me this might be a bad idea. I figured -- update to the latest version then root it. I've tried changing how I have it connected (media or camera), what USB port I connect to, what USB cable I use, which boot options I select -- NOTHING makes a difference. I have gotten my bootloader to unlock, or so it seems, as I've got the unlocked padlock image during boot up. But I'm totally stuck on how to proceed to get root.
Click to expand...
Click to collapse
When you run wugs toolkit to root, does it reboot your nexus? I have not rooted a 32GB yet but I have done a 16GB on 4.1.2 factory image without any problems.
There is nothing different between rooting an 8/16GB unit versus the 32GB ones. Nor does 4.1.1 or 4.1.2 matter.
I bought a 32GB one a few days ago, upgraded to 4.1.2, and had the bootloader unlocked, custom recovery installed and device rooted in about 5 minutes.
The issues you are having are why I hate these "toolkits". They don't always work properly, and when they fail, the user has no idea what's going on. It's much better for people to actually perform the steps manually so that they understand what's going on behind the scenes. Because when you understand, you can better troubleshoot problems.
Based on the errors, it looks like the toolkit failed to remount /system as writable. As such, it couldn't push the APKs for superuser, nor make the su binary suid root. Which of course would break the rest of the install script.
It's a very simply process and doesn't need a toolkit. Use the android development toolkit tools adb and fastboot.
1) adb reboot bootloader
2) fastboot oem unlock
(select yes on tablet)
3) fastboot reboot-bootloader
(confirm bootloader is unlocked)
4) fastboot erase recovery
5) fastboot flash recovery <recovery.img>
(recovery.img should be a downloaded custom recovery file - CWM or TWRP, your choice).
6) Reboot into recovery
7) adb push <superuser.zip> /sdcard/superuser.zip
(superuser.zip should be whatever recovery flashable 'root' zip you want to use).
8) Using recovery, flash the zip file.
9) Reboot
10) Done.
phonic said:
There is nothing different between rooting an 8/16GB unit versus the 32GB ones. Nor does 4.1.1 or 4.1.2 matter.
I bought a 32GB one a few days ago, upgraded to 4.1.2, and had the bootloader unlocked, custom recovery installed and device rooted in about 5 minutes.
The issues you are having are why I hate these "toolkits". They don't always work properly, and when they fail, the user has no idea what's going on. It's much better for people to actually perform the steps manually so that they understand what's going on behind the scenes. Because when you understand, you can better troubleshoot problems.
Based on the errors, it looks like the toolkit failed to remount /system as writable. As such, it couldn't push the APKs for superuser, nor make the su binary suid root. Which of course would break the rest of the install script.
It's a very simply process and doesn't need a toolkit. Use the android development toolkit tools adb and fastboot.
1) adb reboot bootloader
2) fastboot oem unlock
(select yes on tablet)
3) fastboot reboot-bootloader
(confirm bootloader is unlocked)
4) fastboot erase recovery
5) fastboot flash recovery <recovery.img>
(recovery.img should be a downloaded custom recovery file - CWM or TWRP, your choice).
6) Reboot into recovery
7) adb push <superuser.zip> /sdcard/superuser.zip
(superuser.zip should be whatever recovery flashable 'root' zip you want to use).
8) Using recovery, flash the zip file.
9) Reboot
10) Done.
Click to expand...
Click to collapse
I agree with you, the problem of the tool kits, I experimented two of then
M, is that you are lost when something don't work, I lost hours and hours before understand it and do it by myself for 50 per cent .
Now that everything is good, I am very prudent with theses helpers,:good:
I just purchased a N7 yesterday, and it's supposed to arrive in a couple of days. I'm using a Mac OS computer and comfortable with ADB, so which is better: root first before updating the firmware, or update to the most recent version of firmare and then root? And which rooting method do you recommend with a Mac?
Thanks for your suggestions!
mj56gt said:
I just purchased a N7 yesterday, and it's supposed to arrive in a couple of days. I'm using a Mac OS computer and comfortable with ADB, so which is better: root first before updating the firmware, or update to the most recent version of firmare and then root? And which rooting method do you recommend with a Mac?
Thanks for your suggestions!
Click to expand...
Click to collapse
I would update first then root, and use wug's toolkit to help you through the process.
mj56gt said:
I just purchased a N7 yesterday, and it's supposed to arrive in a couple of days. I'm using a Mac OS computer and comfortable with ADB, so which is better: root first before updating the firmware, or update to the most recent version of firmare and then root? And which rooting method do you recommend with a Mac?
Thanks for your suggestions!
Click to expand...
Click to collapse
I personally have done the following steps:
- I've rooted it first;
- installed OTA RootKeeper (to keep the root after updating - the app must be configured before updating firmware);
- I've updated the firmware to the last version.
I performed all those steps using my notebook which has Windows 7 OS, so for Mac OS I cannot make any recommendation.
I hope this helps you.
Thank you both for the suggestions! Is the Wug's toolkit for Windows OS? Any such toolkit for Mac OS or Linux system? Thanks!
Leonhan said:
I would update first then root, and use wug's toolkit to help you through the process.
Click to expand...
Click to collapse
Good Dog. The OP said he had a Mac.
@OP
May as well do stock firmware upgrade first if it is needed.* On the rare chance that you get a device that suffers some kind of infant mortality - the device will be pure stock for the first little bit of operation (in case an RMA is needed). And the flashing operations which take place IF an OTA is needed will give flash memory a little workout.
Just bear in mind that the bootloader unlock operation will erase everything from /data (factory reset) when the "fastboot unlock" command occurs. So, if you operate the device as pure stock for a while, you will either need to backup stuff or regard your initial customizations as disposable.
fastboot methods are the most expeditious way to proceed on a Mac.
If you use TWRP 2.4.4.0 as your custom recovery, it will peek in /system to see if you are rooted and offer to root your device with SuperSU for you (just before you reboot from within TWRP).
The way I see it, the rooting procedure is 4 steps total:
(Note: use the "tilapia", not grouper recovery image if you have the 3G/LTE Nexus 7)
Code:
fastboot unlock
fastboot boot openrecovery-twrp-2.4.4.0-grouper.img
... make a pure stock Nandroid backup
... reboot TWRP and it will offer to install SuperSU for you
(optionally: fastboot flash recovery openrecovery-twrp-2.4.4.0-grouper.img )
Those 4 steps above will leave you with Pure Stock + Rooted ; even the recovery on the tablet will be pure stock until you flash it there (optional step 5 above).
It's up to you to get the Mac SDK (for fastboot & adb) installed and figure out using command lines - search for that, don't ask.
good luck
* I thought I saw a report recently that someone had JDQ39 on a device purchased less than 4 weeks after the last update - your device may not need upgrading yet.
bftb0 said:
@OP
May as well do stock firmware upgrade first if it is needed.* On the rare chance that you get a device that suffers some kind of infant mortality - the device will be pure stock for the first little bit of operation (in case an RMA is needed). And the flashing operations which take place IF an OTA is needed will give flash memory a little workout.
Just bear in mind that the bootloader unlock operation will erase everything from /data (factory reset) when the "fastboot unlock" command occurs. So, if you operate the device as pure stock for a while, you will either need to backup stuff or regard your initial customizations as disposable.
fastboot methods are the most expeditious way to proceed on a Mac.
If you use TWRP 2.4.4.0 as your custom recovery, it will peek in /system to see if you are rooted and offer to root your device with SuperSU for you (just before you reboot from within TWRP).
The way I see it, the rooting procedure is 4 steps total:
(Note: use the "tilapia", not grouper recovery image if you have the 3G/LTE Nexus 7)
Code:
fastboot unlock
fastboot boot openrecovery-twrp-2.4.4.0-grouper.img
... make a pure stock Nandroid backup
... reboot TWRP and it will offer to install SuperSU for you
(optionally: fastboot flash recovery openrecovery-twrp-2.4.4.0-grouper.img )
Those 4 steps above will leave you with Pure Stock + Rooted ; even the recovery on the tablet will be pure stock until you flash it there (optional step 5 above).
It's up to you to get the Mac SDK (for fastboot & adb) installed and figure out using command lines - search for that, don't ask.
good luck
* I thought I saw a report recently that someone had JDQ39 on a device purchased less than 4 weeks after the last update - your device may not need upgrading yet.
Click to expand...
Click to collapse
Thanks a lot for the detailed information and the kind help, bftb0! I really appreciated it.
I had a two-year-old version of Mac SDK, and only used adb before. Just finished grabbing the most recent version. I prefer command lines instead of button pushing. Once N7 arrives, I will start to have fun with fastboot...
bftb0 said:
Code:
fastboot unlock
fastboot boot openrecovery-twrp-2.4.4.0-grouper.img
... make a pure stock Nandroid backup
... reboot TWRP and it will offer to install SuperSU for you
(optionally: fastboot flash recovery openrecovery-twrp-2.4.4.0-grouper.img )
Click to expand...
Click to collapse
One more question. Is the first step (unlocking) necessary for the later steps such as root access? The reason I'm asking is that, unlike rooting, unlocking is irreversible, and would avoid the warranty.
Edit: I guess that the bootloader has to be unlocked to flash a custom recovery, right?
Unlocking is necessary to use fastboot commands and it's not irreversible as you can relock it with "fastboot oem lock" but if you want to unlock it another time it will wipe your device again. And if you flash recovery with fastboot then yes your bootloader must be unlocked but you can relock it after.
Nico_60 said:
Unlocking is necessary to use fastboot commands and it's not irreversible as you can relock it with "fastboot oem lock" but if you want to unlock it another time it will wipe your device again. And if you flash recovery with fastboot then yes your bootloader must be unlocked but you can relock it after.
Click to expand...
Click to collapse
That's great! Thanks a lot for the help...
Hello,
I tried to flash my nexus 7 with a new Paranoid android rom, but i forgot to update TWRP with the latest version and when i flash my rom i had a Failed message... :crying:
Now I can only go into BootLoader and Recovery, but i don't know how to restore the stock ROM....
Is my nexus 7 totally bricked or is there a solution to restore it ?
Thank you, and happy new year !
There is. Enter bootloader mode. Download the nexus 7 toolkit from: nexus7.wonderhowto.com/how-to/definitive-guide-restore-your-nexus-7-tablet-even-if-youve-bricked-it-0145541/
Sent from my LG-D802 using Tapatalk
Hey Guy's i have the same problem but my device does not show up on my PC (running windows 8.1) as a drive, but does appear under device manager as an ADB device entitled 'full',
Any advice how i can add a new rom to my device with this scenario ?
Judgie351 said:
Hey Guy's i have the same problem but my device does not show up on my PC (running windows 8.1) as a drive, but does appear under device manager as an ADB device entitled 'full',
Any advice how i can add a new rom to my device with this scenario ?
Click to expand...
Click to collapse
Hi, Judgie351...
It depends on what you mean by "add a new rom...".
If, as I suspect, you mean to flash a custom ROM, then that's done via a Custom Recovery such as CWM or TWRP... which first needs to be fastboot flashed.
The procedure is relatively straightforward...
-----------------------------------------------------
1). Unlock the bootloader (if it isn't already unlocked) with fastboot oem unlock. This, however, has the unpleasant side effect of completely wiping the device; it essentially performs a factory reset.
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery custom_recovery.img
3) . Using Chrome (or any other Android browser), download the Custom ROM .zip of your choice, directly to the Nexus 7.
4). Via the bootloader, boot into your recently fastboot flashed Custom Recovery... navigate to where the Custom ROM .zip downloaded to (usually the /download folder)... and flash it. (After, of course, wiping everything other than internal storage.)
-----------------------------------------------------
As you can see, there is no requirement for ADB when flashing a Custom ROM ... just fastboot... and that only for unlocking the bootloader and flashing a Custom Recovery.
Once both are accomplished, ROM flashes can be handled directly from the Nexus 7 itself... without recourse to a PC... or ADB.
And when you are rooted, you can even flash new Custom Recoveries or Boot images, using the rather excellent Flashify app, without going anywhere near a PC/Mac...or ADB.
Rgrds,
Ged.
GedBlake said:
Hi, Judgie351...
It depends on what you mean by "add a new rom...".
If, as I suspect, you mean to flash a custom ROM, then that's done via a Custom Recovery such as CWM or TWRP... which first needs to be fastboot flashed.
The procedure is relatively straightforward...
-----------------------------------------------------
1). Unlock the bootloader (if it isn't already unlocked) with fastboot oem unlock. This, however, has the unpleasant side effect of completely wiping the device; it essentially performs a factory reset.
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery custom_recovery.img
3) . Using Chrome (or any other Android browser), download the Custom ROM .zip of your choice, directly to the Nexus 7.
4). Via the bootloader, boot into your recently fastboot flashed Custom Recovery... navigate to where the Custom ROM .zip downloaded to (usually the /download folder)... and flash it. (After, of course, wiping everything other than internal storage.)
-----------------------------------------------------
As you can see, there is no requirement for ADB when flashing a Custom ROM ... just fastboot... and that only for unlocking the bootloader and flashing a Custom Recovery.
Once both are accomplished, ROM flashes can be handled directly from the Nexus 7 itself... without recourse to a PC... or ADB.
And when you are rooted, you can even flash new Custom Recoveries or Boot images, using the rather excellent Flashify app, without going anywhere near a PC/Mac...or ADB.
Rgrds,
Ged.
Click to expand...
Click to collapse
Worked a treat - Thankyou :good:
Worked for me too !
Thank you guys for your help !!
Hello fellow XDA. I was wondering if anyone was successful at unlocking and install twrp on a stock NEXUS 4 running 4.4.2 KOT49H? I have searched ang googled but have no luck on a legitimate guide. Any information is appreciated. Thanks for reading.
Try the toolkits available on the forum
Sent from my Nexus 5 using Tapatalk
jyuuken said:
Try the toolkits available on the forum
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I never used the toolkit when I rooted the nexus 4 running stock jelly bean a while back, it just seem unreliable when I read up on it. I used Fastboot instead. Anyway, looks like no one in this forum who has successfully rooted a stock kit kat 4.4.2 yet it seems .
How to Root Nexus 4 and Get a Custom Recovery: http://youtu.be/7mHy32B-GFM
Good on you for not using toolkits. First make sure you have the correct drivers installed, as well as latest versions of adb and fastboot. Then you have to unlock the bootloader (wipes your device). Go into bootloader mode either by using the command 'adb reboot bootloader' (with usb debugging enabled) or by switching your phone off, holding both volume keys then pressing the power button. Then use the command 'fastboot oem unlock'
Next flash a custom recovery. (I suggest TWRP as it has root function built in and seems to work best.) 'fastboot flash recovery "nameofrecovery.img"'
Then boot into your custom recovery. From there reboot to system and TWRP will prompt you to root your device, alternatively you could sideload supersu http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip.
DrFredPhD said:
Good on you for not using toolkits. First make sure you have the correct drivers installed, as well as latest versions of adb and fastboot. Then you have to unlock the bootloader (wipes your device). Go into bootloader mode either by using the command 'adb reboot bootloader' (with usb debugging enabled) or by switching your phone off, holding both volume keys then pressing the power button. Then use the command 'fastboot oem unlock'
Next flash a custom recovery. (I suggest TWRP as it has root function built in and seems to work best.) 'fastboot flash recovery "nameofrecovery.img"'
Then boot into your custom recovery. From there reboot to system and TWRP will prompt you to root your device, alternatively you could sideload supersu http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip.
Click to expand...
Click to collapse
Seems like it's the same step when I rooted when it was at jellybean. I'm just making sure since certain android version might require other method of rooting. I will try and let you guys know. Thanks again for all input.
Hey guys I just unlocked, rooted, and installed the latest TWRP recovery on my phone. Yay-ugh :victory: Anyway I wanted to install a couple rom that works with this 4.4.2 KITKAT. I have the Paranoid Android 3+ with that awesome pie feature before when I was in jelly bean, but I was wondering if that rom is compatible with my currents stock rooted kitkat? Also any suggestion on compatible kernel that goes with it? Please let me know which kernel version as well.
I have a Nexus 7 (2013) which was recently upgraded to Lollipop 5.0.1 from KitKat 4.4.4 via OTA, and it randomly restarted and is now stuck on the Google screen. I can get to the bootloader via the hardware buttons, and it's recognized as an Android device when plugged in via USB (USB debugging and developer options were previously enabled.) However, I can't get to recovery mode to wipe the device, as it simply gets stuck on the Google screen again. Fastboot commands are nonresponsive in fastboot mode, and I assume I need to get to recovery mode to run any fastboot/ADB commands.
Note that my Nexus 7 is entirely stock and has not been rooted or altered in any way, aside from OTA updates.
I can wipe and reinstall KitKat once I get my Nexus device to function in recovery mode, but I need to get there first!
Sir,
Please wait until mods will move this thread to the device specific forum.
For reply or more questions please register an account on XDA forums.
Stand by
Until then read this thread: [GUIDE] Flashing a Factory Image with fastboot / return to stock
Good luck