Related
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!!!
I am so confused at this point that I have to ask for help. I DID search but couldnt find the answers that related to my current situation. I am keenly aware after watching the video that I do not want to cause a stir by posting perhaps a subject thats been covered over and over but here I go.
I purchased a Nexus 7 WiFi only and have updated to 4.2.1 build JOP4OD. I want to load a custom ROM, specifically:
http://forum.xda-developers.com/showthread.php?t=1830016
I have downloaded said "ROM, along with Nexus Root Toolkit 1.6.1. I have the drivers installed on my PC (win7 x64) with the device showing up under "portable devices."
I have tried all that I can to get the custom ROM to work and for the life of me I cant get it to load so I opened up the Root Toolkit and hit "Flash Stock + unroot."
I rebooted and installed the system update that was downloaded. So here I am and am asking for someone to please walk me thru getting the custom ROM on my device. Feel free to dummy down the steps for me. Clearly I need it after my failed attempts.
Thanks so much for any help.
Regards,
Chris
stonecb said:
Nexus Root Toolkit 1.6.1.
Click to expand...
Click to collapse
I use MSkip's Toolkits for all my Nexus devices.
Steps I took to install the ROM
Here's what I did:
1) Downloaded and installed Wug's Nexus Tool Rootkit v1.6.1 (http://forum.xda-developers.com/showthread.php?t=1766475)
2) Using the above toolkit (it is GUI driven) made a complete backup first
3) Clicked on the "Unlock" button on the GUI to unlock my Nexus 7
4) Clicked on the "Root" button to root my device
5) Downloaded GooManager from the Google Play store
6) Installed latest TWRP using GooManager (Tutorial: http://www.youtube.com/watch?v=leCiKG9-tNc)
7) Downloaded CleanRom to my PC (http://forum.xda-developers.com/showthread.php?t=1830016)
8) Copied this downloaded ROM to Nexus 7
9) Rebooted to TWRP recovery
10) Wiped Data and Factory Reset using TWRP recovery
11) Flashed the ROM
12) Rebooted device using TWRP
13) Booted automatically into the new custom CleanROM and it runs great.
Good Luck!
Follow this guide.
http://www.androidcentral.com/how-unlock-bootloader-and-root-your-nexus-7
After you have unlocked and installed a custom recovery, just
adb push C:\File_path_to_rom_on_computer /directory_where_you_want_the_ROM_to_be_on_Nexus7
And then wipe and flash the ROM.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
fljoe:
Thanks.. your steps worked like a charm!!!!
All I need do now is learn Android and NovaLauncher etc.
Thanks so much!!!! Just awesome!!!
stonecb said:
fljoe:
Thanks.. your steps worked like a charm!!!!
All I need do now is learn Android and NovaLauncher etc.
Thanks so much!!!! Just awesome!!!
Click to expand...
Click to collapse
If someone helps, please click the thanks button as a token of appreciation. That's what it's there for. :thumbup:
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
(OK, the board ate my first post; maybe this one will do better...)
I am trying to root my Nexus 4 in order to install Titanium Backup. (I have some user data to transfer over from my old Samsung Vibrant before I retire it.) I'm using the Nexus Toolkit for Linux, here:
http://forum.xda-developers.com/showthread.php?t=1999065
The first two steps work fine. I can unlock the bootloader and install clockwork mod. When I try to actually root the device and install su, though, I run into a problem. Specifically, going into recovery mode (either automatic through the toolkit or manually myself) I get the Andy the Android "error" icon (Android flat on his back, chest open, with a red warning triangle over it). That remains until I reboot the device.
Any suggestions? I'm not an experienced rooter (Ti Backup is the ony reason I'm even bothering), so keep it basic please.
Crell42 said:
(OK, the board ate my first post; maybe this one will do better...)
I am trying to root my Nexus 4 in order to install Titanium Backup. (I have some user data to transfer over from my old Samsung Vibrant before I retire it.) I'm using the Nexus Toolkit for Linux, here:
http://forum.xda-developers.com/showthread.php?t=1999065
The first two steps work fine. I can unlock the bootloader and install clockwork mod. When I try to actually root the device and install su, though, I run into a problem. Specifically, going into recovery mode (either automatic through the toolkit or manually myself) I get the Andy the Android "error" icon (Android flat on his back, chest open, with a red warning triangle over it). That remains until I reboot the device.
Any suggestions? I'm not an experienced rooter (Ti Backup is the ony reason I'm even bothering), so keep it basic please.
Click to expand...
Click to collapse
It sounds like you're losing recovery. Do you restart your device after you flash CWM?
Try flashing CWM manually through fastboot, don't restart the device (will overwrite custom recovery) and just go directly into recovery then flash SU.
Alternatively, make sure you're using the right version of CWM and/or double check that the writing process for CWM is going to completion. I don't know if you can disable the stock recovery overwrite without first having root, but you can also look into that
hoponpop said:
It sounds like you're losing recovery. Do you restart your device after you flash CWM?
Try flashing CWM manually through fastboot, don't restart the device (will overwrite custom recovery) and just go directly into recovery then flash SU.
Alternatively, make sure you're using the right version of CWM and/or double check that the writing process for CWM is going to completion. I don't know if you can disable the stock recovery overwrite without first having root, but you can also look into that
Click to expand...
Click to collapse
I'm using whatever version is included in the Universal Tooklkit download. It has two versions included, Standard and Touch. I've tried both, same effect.
Any pointers on "manual" installation of CWM? (As I said, rooting newbie.)
Can i install CWM on locked bootloader?
Ben Ling said:
Can i install CWM on locked bootloader?
Click to expand...
Click to collapse
Yes.
An 'exploit' has recently become available for ROOTING the Nexus 7 without unlocking the BOOTLOADER.
This 'exploit' works... I have tested it myself.
Until recently, I believed that because FASTBOOT wasn't an option (as a result of a LOCKED BOOTLOADER), there was no way of FLASHING anything.
Happily, I was disabused of this notion by bftb0... and I can confirm, you can indeed install CWM (or TWRP) with a locked BOOTLOADER.
-----------------------------
Here's how...
First, you need to run this 'exploit' to acquire ROOT.
Upon reboot, you should now be rooted, with Chainfires SuperSU package and associated SU binary installed.
It's important that you are ROOTED before you proceed.
Next, get Android Terminal Emulator from PlayStore.
Download a CUSTOM RECOVERY .img of your choice... either CWM (Both 'Grouper' and 'Tilapia' variants are available)...
...or TWRP for 'Grouper' (N7 WiFi) or TWRP for 'Tilapia' (N7 3G).
Rename it to recovery.img... and copy it to the root of the Nexus 7's internal storage (emulated SD card).
In Terminal Emulator, run the following command...
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Upon completion of this command, shutdown and reboot your device into the BOOTLOADER, and from there, boot into your CUSTOM RECOVERY... in pretty much the same way had you FASTBOOT FLASHED it.
-----------------------------
You are now free to flash whatever ROMs or kernels you like.
However, a word of caution... because the BOOTLOADER remains locked, FASTBOOT is strictly off limits; it simply won't work.
So the first thing you should do after flashing TWRP or CWM is...
*** MAKE A NANDROID BACKUP ***
If the device becomes 'wedged/bootlooped' as a result of some ROM flash gone wrong, then you will have no choice but to unlock the BOOTLOADER (with full wipe) in order to fix it.
But if you have a NANDROID backup... piece of cake... just restore.
-----------------------------
Credits and kudos must go to XDA members, nhshah7, who made this 'exploit' available and bftb0, whose post pointed me in the right direction, with regard to the 'dd' command.
-----------------------------
I can confirm all of this works... my Nexus 7 is currently rooted, running a custom recovery (TWRP), with a custom ROM and Kernel (see sig) installed - all sitting behind a LOCKED BOOTLOADER.
...no Factory Reset (wipe) required...
...and no Unlocked Padlock Symbol upon boot.
Rgrds,
Ged.
Previously I installed cwm and can boot,just 1 time.
I tried to boot into but nothing.
What to do?
Sent from my Sony Xperia™ sola using XDA Premium App
@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"
SSyar said:
@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"
Click to expand...
Click to collapse
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.
GedBlake said:
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.
Click to expand...
Click to collapse
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium
Ben Ling said:
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium
Click to expand...
Click to collapse
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.
GedBlake said:
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.
Click to expand...
Click to collapse
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App
Ben Ling said:
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
Shut down the tablet completely.
Press and hold the VOL DOWN button... whilst holding, press the POWER button.
This will boot you into the BOOTLOADER.
Using the VOL buttons, navigate to RECOVERY.
Press the POWER button to select.
Rgrds,
Ged.
Just tested this method... again... (using dd to install a Custom Recovery)... with both CWM and TWRP... and in both instances, the installations survived a reboot. So I'm puzzled why there seems to be a problem here.
---------------------------------
I have semi-automated the process in order to avoid typing long complicated commands into Android Terminal Emulator. A process, which, by it's nature, is subject to typographical error.
Here's how...
Download the Custom Recovery of your choice to your Nexus 7.
Rename it to recovery.img
Copy it to the root of the emulated SD card (internal storage).
---------------------------------
Download this script file...
writerecovery.zip
Unzip and copy it to the root of the emulated SD card (internal storage).
(Alongside the recovery.img).
---------------------------------
Install Script Manager from Google Playstore.
Open Script Manager and locate the script file writerecovery.sh on the root of the emulated SD card.
Press ENTER on it...
Select OPEN AS... Script/Executable...
Select SU (root) from the toolbar...
Select Run...
The script will now execute the following command...
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
...writing the recovery.img to the recovery partition.
See attached thumbnails for the sort of thing you should expect to see.
---------------------------------
I have tested this method several times... switching between CWM and TWRP. And performing multiple reboots, to ensure that the Custom Recovery 'stuck' in each instance.
---------------------------------
Hope this works... if it doesn't... then I'm at a loss to explain why.
Maybe somebody with more technical knowledge can assist.
All I know, is it works for me... on my Nexus 7.
Rgrds,
Ged.
well i installed recovery using goo manager ,.,. got this response from other thread and is working for me ,.,., goo manager also has the option to restart in recovery so really good for me
Help with my Condition
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.
junisheikh said:
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.
Click to expand...
Click to collapse
Hi, junisheikh...
To answer your question...
junisheikh said:
"WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?"
Click to expand...
Click to collapse
Yes, you should be able to.
---
The bootloader lock state is irrelevant when it comes to flashing stuff via a Custom Recovery (such as CWM or TWRP).
All an unlocked bootloader does, is it allows the device to accept fastboot flash commands from a connected PC or Mac, and which is the usual way of flashing a Custom Recovery, and then subsequently rooting it.
I would, however, advise against using CWM. ClockWorkMod Recovery is old and hasn't been updated for quite some time, and may cause problems.
Instead, you should take a look at TWRP (TeamWin Recovery Project). This Custom Recovery has a better user interface, and is less likely to cause you problems.
---
Although your bootloader is locked, you have managed to acquire root via KingRoot... which means you can flash a Custom Recovery with the Flashify app...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
This app allows you to flash Recoveries and Boot images (stock and custom) directly from the device itself, providing the device is rooted. The free version of Flashify has a limit of 3 flashes per day. This shouldn't be a problem though... Custom Recoveries aren't something you generally flash on a regular basis.
(See my attached screenshots for a flavour of how Flashify works.)
---
You can find the latest version of TWRP for the Nexus 7 WiFi model here...
http://techerrata.com/browse/twrp2/grouper
Download to your Nexus 7, and use the Flashify app to flash.
And then download whatever Custom ROM+GAPPS you like, and flash via TWRP.
Incidentally, the NANDROID backup you've already created with CWM is NOT compatible with TWRP. So you'll need to create a new NANDROID backup, should you choose to flash TWRP.
---
junisheikh said:
This is going to be a one way ride for me, if I brick I have a paperweight.
Click to expand...
Click to collapse
This is possible, because you don't have access to fastboot (due to your broken USB port) you won't be able to fastboot flash back to Google Factory stock should you not be able to boot Android (for whatever reason) after flashing some Custom ROM. But providing you have a NANDROID backup and a Custom Recovery (CWM or TWRP) installed, you **should** be able to recover from softbricks such as bootloops. But having said that, I would tread carefully.
Hope this helps, and good luck.
Rgrds,
Ged.
Newbie here.
Pls guide me..
Many tks!
Sent from my SM-N9005 using xda app-developers app
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Issues with rooting (4.4), stuck after flashing recovery
I just got my Nexus 10, and unlocked the boot loader, then flashed the custom recovery. All was fine, and I could boot into recovery, however recovery can not mount any filesystems. So I rebooted, now the Nexus does not boot, but hangs on the intro animation, normally meaning in my experience that the kernel is looped and is no longer finding (or else) booting the OS. I've tried booting 3 times.
So then, the steps I took,
enable USB debugging
were copy over the zip file for supersu
reboot to (fastboot mode), verify device
unlock boot loader "fastboot oem unlock"
flash the recovery "recovery-clockwork-touch-6.0.4.3-manta"
reboot into recovery
Failed to mount filesystems
for instance "E: Can't mount /cache/recovery/command or E:Can't mount /sdcard .... (you get the idea).
rebooting again a leaving it does nothing.
I also tried side loading a new image in my case "ThunderKat_manta-KRT16S-20131201" and after installing the "UniversalAdbDriverSetup", I was able to do so, I also was also able to side load the google apps "GoogleAppsPack-4.4-20131128", in both cases I get a success message after the install, however there after when I attempt to reboot I'm still stuck looking at the boot animation.
Now I'm really confused as if if the OS was destroyed when I unlocked the device, then side load of the zip contains a new kernel and OS image so it should be working, but it is not. In fact, recovery while still working throws the same can not mount exceptions after the flash as it did before (I rebooted) as I was previously getting and a factory reset, fails to mount /data, but does flash /cache and sd-ext without issues, so again I'm lost as to what to do.
Best guess I have is that partitions such as /data are just missing, I have no idea the state of teh device in such a case, but recovery and side loading using adb are working, how do I recover a working ANDROID OS from here?
Thanks,
ERIC
stuck in loading screen
Hi,
i just got my Nexus 10 yesterday. I tried to root it, but it is stuck in the loading screen. What can i do now? Can i like undo it to get it back to work?
I have the same issue egandt described.
Edit: I just got it back with this tutorial to android 4.2.2 and now i am updating it back up
nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/
I unlocked nexus10,
Flashed cwm,
Installed su, but whn i turned it on, su not found, rootchecker shows no root access..
I also encounter bootloop initially,
Need to wide data / factory reset then its normally booted..
Sent from my SM-N9005 using xda app-developers app
Agreed the factory reset was required to fix the issues I encountered, then installing super-su worked.
I still cannot root the Nexus10..
Any one can help?
Thanks in advance!
XxLordxX said:
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Click to expand...
Click to collapse
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
xing369 said:
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
Click to expand...
Click to collapse
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
shimp208 said:
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
Click to expand...
Click to collapse
Thanks for your kind offering of hands!
Last night I tried again to re-flashed latest TWRP as well as latest SuperSU.
I ran 2x Root Checker,
1 said rooted,
1 said no root access, no BusyBox available.
I tried some apps like GMD Gesture, no working or no root access.
So,
Should I redo everything: enable USB Debugging then unlock bootloader then flash CWM then install SuperSU?
I initially gone thru above steps w/o enabling USB Debug..
Many thanks!
Sent from my SM-N9005 using xda app-developers app
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
xing369 said:
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
fritzhy said:
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
Click to expand...
Click to collapse
Very much appreciated for reviving my nexus!
However, after flashing latest TWRP, and installed SuperSU 1.80,
It seems my nexus still unrooted.
Any ideas?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
fritzhy said:
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
xing369 said:
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
If it's needed the app will say so when you open it.
fritzhy said:
If it's needed the app will say so when you open it.
Click to expand...
Click to collapse
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
xing369 said:
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Not that I can think of, nope...