**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
Related
I initially looked for a complete update guide on here and eventually found all the information I needed, but it was in multiple places and sometimes hard to find. After getting everything installed on my N1 I thought I would write a guide for other noobs like me that want to try out ICS or JB but would like a step-by-step guide. I hope that it is helpful. SpazeDog ROMs (both ICS and JB) are working wonderfully on my N1 - its a very nice update from CM7 with only minor issues so far.
Note: this was initially written specifically for SpazeDog roms, but as they have not been updated in a while I have provided links to other popular roms as well. If you would like to try a different ICS or JB rom this guide should work, just substitute with the appropriate rom and depending on the one you choose, you may also need to install Google apps.
If you looking at this guide and don't know the basics yet, check out the Newbie Friendly thread first.
Links to popular roms that will work using this guide:
Evervolv JB 4.2
Evervolv JB 4.1
CM 10, JB 4.1.2 by vijendrahs
CM 10, JB 4.2.1 by vijendrahs
Spazedog ICS/JB
Disclaimer: This guide involves making changes to your phone that potentially could brick your phone leaving it unusable. I am not liable for any changes you make or problems you may have with your phone. You should at least be familiar with entering commands using command prompt. This procedure will erase ALL the data on your phone. Make sure you have a backup of everything. A nandroid backup is highly recommended. Proceed at your own risk.
Before we get started make sure you have the following: a rooted Nexus One, a USB cable to attach your phone to a computer, and the Android SDK. If you are just now installing the Android SDK, open the SDK manager and make sure to install the "Tools" and in "Extras" the "Google USB Driver" are checked off and download them. Alternatively, you just download ADB and Fastboot (search this forum or google). If you have a Mac see this thread to get started with ADB and Fastboot.
If you Nexus One is NOT already rooted, then follow this guide from Cyanogenmod to root your phone. If you plan to use the adb commands below (they are optional) make sure you have usb debugging enabled: go to "Settings" → "Applications" → "Development" → enable "USB debugging."
Step 1 - Download everything you will need:
4EXTRecovery Updater - the first link will download the .apk to your computer or phone.
BlackRose - go down to bottom of the first post to "Attached Files" and download the latest BlackRose zip file. If you don't want to do it yourself, check out this thread to flash a pre-made partition scheme. Often the developers (Evervolv) will also have a partition schemes that you can flash via Fastboot from your PC as well.
Your rom of choice - go to the downloads section and choose which rom you would like to try. Download the zip installation file.
Since you will be decreasing the size of your partition that apps can be stored on consider something like Mounts2SD or AD2SDX to move apps to your SD card.
Step 2 - Install and use 4EXTRecovery Updater on your phone:
The easiest thing to do is go to the 4ext link above, download and install it, directly from your nexus one. You can also install it by copying the APK file to your SD card, then using a file manager to find it and install it or you can use command prompt by opening command prompt, cd to the location of the Android SDK tools, and then type in the following command (replacing "path" with the path to where the APK is located on your computer):
Code:
adb install /path/4EXTRecoveryUpdater.apk
After you have installed 4ext open the 4EXT Recovery Updater. Tap "Settings" → "Allow" superuser request → "Yes" to connect to 4ext to get new data. Now select "Online install/upgrade" → "Yes" assuming it detects your nexus one correctly → select and install the latest 4ext recovery (at the top of the list).
After 4ext has installed, it will have placed a recovery image on your SD card - find it (its called recover.img) and it should be located in SD/Download/4EXT_Recovery_Touch/ folder. Copy this to your computer in case something goes wrong later and you need to re-flash the recovery image!
After installation of the 4ext recovery turn off your phone and boot into recovery by turning off your phone, turning it on again while holding the trackball down. This will boot into the bootloader, then press the power button once, use Volume Down to select "recovery" and press the trackball to select. Alternatively you can use the command prompt:
Code:
adb reboot recovery
Your phone should now boot into the 4ext recovery menu. Before moving on make sure you have any important stuff backed up because you are about to erase your entire SD card! Select "tools" →“partition sd card” → “remove all partitions and start from scratch.” Then for the 1st partition select “1024″ for a 1GB partition (this will be where ICS will be able to put your applications & data). Select "skip" for the 2nd partition and for the swap partition. Finally select the system “ext4″.
Step 3 - Copy the Evervolv, SpazeDog, or whatever zip installation file you have chosen to your phone's SD card
Download the ICS or JB zip file above and copy it to the root of your newly formatted SD card.
Step 4 - Installing and using BlackRose to resize the system partition:
Download the BlackRose application and install it on your computer. (Alternatively people have made flash-able partition schemes that you can just flash from your PC - usually links and instructions are provided in the installation rom's thread, Evervolv's here. If you do have access to a computer you can check out this thread).
Make sure your nexus one is attached via USB to your computer.
Open the BlackRose application - it will install and reboot your phone. Then follow along as shown in this video to resize your partitions for a JB ROM.
If you plan to install the ICS rom then use the video above as a guide but use the numbers (sizes) for the different partitions as indicated below.
After BlackRose has installed you will need to restart the application. After it has started up and recognized your device select "apply stock/custom blackrose" by typing in 1 and enter.
Then select "custom blackrose" by typing in 2.
Then type "resize" when prompted.
Now you will need to change the sizes of the system partition to 220 for ICS or 260 for JB.
Change the cache size to 8.
Finally name the new system partition, either "ICS" or "JB" depending on what you plan to install.
Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip.
Step 5 - Install JB or ICS:
Now turn your phone off and boot into recovery as you did in step 2.
4ext will load. Select "wipe/format" → "format all partitions (except sdcard)" and then also "wipe data/factory reset."
Now go back and select "install from sdcard" → "choose zip from sdcard" → and then select the ICS or JB zip you copied to the SD card in step 3.
Now either the ICS/JB installer will load or it will just install in one step. Just follow the prompts to install and enjoy.
Depending on the ROM you chose you may need to install Google apps (see the specific ROM thread for details) and will also likely want to flash an apps-to-SD script as mentioned above so you do not run out of space.
This method worked perfectly for me, hopefully it will work well for you as well. Enjoy.
Great work, your guide is amazing!!! I followeed it and ended with an infinite bootanimation , I'm trying to discover what I did wrong :fingers-crossed:, but the guide was superb!
diegolm said:
Great work, your guide is amazing!!! I followeed it and ended with an infinite bootanimation , I'm trying to discover what I did wrong :fingers-crossed:, but the guide was superb!
Click to expand...
Click to collapse
I am sorry to hear that. Can you boot into recovery or is that broken as well? If you can boot into ext recovery try selecting "wipe/restore" → "wipe data/factory reset" and then try to install BCM again. I probably should have added that above, I will do that now.
If your recovery is broken but you can get into the bootloader (holding down trackball while starting up), you should be ok. You will probably need to flash Amon_Ra's Recovery using Hboot as was described in the guide from cyanogenmod link above. If there is a way to directly hboot flash 4ext recovery I don't know how to do it. Then you can try installing BCM again from the Amon_Ra's recovery and re-install 4ext after you get everything working.
I tried the Texasice ROM and it worked, but I didn't like it! Later I tried again BCM and It worked! I dont know, maybe I did something wrong... Anyway thanks again for the guide!!
Does work the same if using fastboot method? Thx
Sent from my Nexus One using Tapatalk 2
intel415 said:
Does work the same if using fastboot method? Thx
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I am not sure which part you are referring to, but, yes, a few of the above instructions could be replaced with fastboot commands.
The adb commands, instead using adb I can use fastboot commands right. That's what I used to root my n1 kinda familiar with fastboot. Thx
Sent from my Nexus One using Tapatalk 2
intel415 said:
The adb commands, instead using adb I can use fastboot commands right. That's what I used to root my n1 kinda familiar with fastboot. Thx
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I used the adb commands above because you can use adb to reboot directly into recovery (fastboot you can only reboot normally or into the bootloader) and you can also use adb to directly install apk files - fastboot cannot do those two things - it is more for flashing images (recovery, roms, etc). In order for adb to work make sure you have usb debugging enabled: go to "Settings" → "Applications" → "Development" → enable "USB debugging."
Note that adb commands are not required - you can reboot into recovery and install the 4ext manually.
It won't let me post a link right now, but just google "adb commands" to find a list of all the commands you can use.
Hope that helps.
Thx. All I need it was to install black rose and partition it. Put zip on SD card wipe and flash. Installation was easier than I thought it would be lol
Also on ur guide you forgot to put 200 for the data part. You only had 220 and 16
Thx again got ics installed on my n1 smoother than cm 7.2
Sent from my Nexus One using Tapatalk 2
intel415 said:
Thx. All I need it was to install black rose and partition it. Put zip on SD card wipe and flash. Installation was easier than I thought it would be lol
Also on ur guide you forgot to put 200 for the data part. You only had 220 and 16
Thx again got ics installed on my n1 smoother than cm 7.2
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Yeah, its not bad - glad you got it working! ICS has been smoother than cm 7.2 for me as well.
Blackrose didn't ask me about userdata - it just assumed that automatically after putting in 220 system and 16 cache... I'll make note of that in the guide so its clearer. Thanks.
Got the issue with not being able to get into recovery after step 4, but I don't have the recovery image to flash. Once the SD card was formatted in step 2 I don't have a download folder. I attached what is in my SD card right now. Help please.
Look for "recovery.img"
bobbyphoenix said:
Got the issue with not being able to get into recovery after step 4, but I don't have the recovery image to flash. Once the SD card was formatted in step 2 I don't have a download folder. I attached what is in my SD card right now. Help please.
Click to expand...
Click to collapse
Try to find if there is a "recovery.img" anywhere on your SD card, perhaps in the 4ext folder?
If you can't find it, do not worry, you can just go to the first page of this thread, click on the link labeled "follow this guide from Cyanogenmod" and then go to the section on how to download and install Amon_Ra's Recovery. Once you get Amon_Ra's recovery flashed you will be able to install any ROM of your choice.
You can reinstall the 4ext recovery later if you want.
c2med said:
Try to find if there is a "recovery.img" anywhere on your SD card, perhaps in the 4ext folder?
If you can't find it, do not worry, you can just go to the first page of this thread, click on the link labeled "follow this guide from Cyanogenmod" and then go to the section on how to download and install Amon_Ra's Recovery. Once you get Amon_Ra's recovery flashed you will be able to install any ROM of your choice.
You can reinstall the 4ext recovery later if you want.
Click to expand...
Click to collapse
OK I'm stuck on what the path name is suppose to be. I tried it every way I can think of. Can you take a look at my screen shot, and tell me where I'm going wrong? The recovery image is on my desktop, so I'm not sure what exactly I should be replacing "path" with. I tried it from the link, and how you have it in your note. You don't have the "/to/" after path as in the CM link.
Well I tried a couple more times, and I can get it to seemingly do it, but it just hangs on this: (see screen shot) I get no error, and if I try to enter recovery on the phone I still get the reboot to the android and triangle with the ! in it.
place the recovery under the folder which contains fastboot.exe and rename it to recovery.img
now use the command
fastboot flash recovery recovery.img from platform-tools directory
Sent from my Nexus One using Tapatalk
And right-click this folder while pressing the SHIFT key on your keyboard. Then choose "Open command window here".
n1newbie said:
place the recovery under the folder which contains fastboot.exe and rename it to recovery.img
now use the command
fastboot flash recovery recovery.img from platform-tools directory
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
tommert38 said:
And right-click this folder while pressing the SHIFT key on your keyboard. Then choose "Open command window here".
Click to expand...
Click to collapse
WOW Thank you both. I spent literally hours yesterday trying to get it to work. Tried your suggestions, and in five minutes it was up and running!
---------- Post added at 12:31 PM ---------- Previous post was at 11:33 AM ----------
I may have spoke too soon. I followed the instructions to the end. Installed the ROM, and rebooted, but now after the X I get the Spazdog splash screen with the big Z in the middle and green dots moving, but it stays there forever. I waited 20 minutes one time. Tried reflashing, but I get the same thing.
---------- Post added at 01:17 PM ---------- Previous post was at 12:31 PM ----------
Just giving an update on progress (in case someone else is in my boat too) Flashed back to stock GB. Reinstalled recovery, and reflashed Spaz. Got past the X, and the splash screen, but now it's stuck on the Android logo that looks like the night rider beam that goes across the word. Been there now for about 10 minutes.
You do have Blackrose, right?
Yep. Installed everything according to OP. I think it may be the partition sizes as I think flashing back to GB messed with them. It says 220 and 10, but after checking some threads, it looks like there is one missing (userdata). I tried flashing a custom GB from here http://forum.xda-developers.com/showthread.php?t=1214543&page=98 and I was able to install everything. Got it up and running, so I'm going to start over for ICS, or do you think I can flash one of these for ICS http://forum.xda-developers.com/showthread.php?t=1637166 , and then just flash the ROM after?
220/10 means that you have 220MB for system and 10MB for cache, everything that's left will be userdata, so it doesn't ask (total is ~436MB, so userdata will be ~206MB in that case).
In HBOOT you can check how large your partitions are, or you could use the FreeSpace app for example. Always make sure your system partition is large enough before flashing a ROM.
This HOW-TO is meant for individuals who like to do things manually and see each process as they occur, versus using a toolkit. I prefer manually unlocking/rooting as I can confirm each step visually and I believe it makes for a more educational experience. Familiarity and confidence with fastboot/adb can be beneficial later on for restoring/troubleshooting/flashing etc down the road.
Unknown at this point if OTA updates will install after flashing CWM. There may be a check file in the OTA that could prevent installation if modified file structure is detected. I’ll edit when I confirm. At any rate, not really an issue as you can flash the OTA yourself as someone on XDA will most likely post it up, or you could re-flash the stock recovery using fastboot which you will now be comfortable with after using this guide! Additionally, if an OTA causes you to lose root you can revisit the appropriate steps to flash SuperSU again.
There are several ways to do these procedures, and I’ve certainly taken the long way on some of them. So by no means am I claiming this to the best or most efficient method, but my hopes are to make things a little more clear and simple based off some of the questions and challenges I’ve seen in a few threads.
This how-to was written for Windows and uses adb and fastboot for installation.
Please let me know of any corrections, additions or errors. Many thanks to the members and devs who made these files available.
1. Download all of the following files and place them in the same directory. I will note whether you need to extract them or not.
Download and extract platform-tools-v16.zip from here: (thanks to efrant)
http://forum.xda-developers.com/showthread.php?t=1626895
Download and extract [ADB/FB/APX Driver] Universal Naked Driver 0.72 from here:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Download SuperSU from here: (look for UPDATE-SuperSU-v1.25.zip or current version)
http://forum.xda-developers.com/showthread.php?t=1538053
Download ClockworkMod from here: (look for Galaxy Nexus 7, Download Recovery 6.0.3.1 or current version – Recommend non-Touch as of ver 6.0.10, some reported issues with the Touch version)
http://www.clockworkmod.com/rommanager/
2. Now we will install the drivers and verify they are working. If you cannot verify drivers are functioning in both normal boot and recovery you need to stop and figure out what you are doing wrong. Proceeding further would be pointless. If you are having trouble, visit the Naked Driver thread listed above or here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
a. Make sure you have USB debugging enabled on your Nexus: setttings ->develop options ->USB Debugging.
b. USB connect your Nexus to your Windows pc. If you get a notification for unknown/driver not found, look in Device Manager for the exclamation point, and right click for update driver software, then browse my computer, then point to where you saved and extracted the Universal Naked Driver folder. If you get a warning from Windows complaining the driver is not signed, hit ‘Install driver anyway’. After the driver installs, you should now have ‘Nexus 7’ listed under ‘Portable Devices’ with no exclamation point.
Now we will verify using adb. You will need to launch a command prompt from the directory you saved all the files from step 1 to. Easiest way is to navigate to the directory via file explorer, then hold down shift and the RIGHT mouse button, and select “Open command window from here”.
In the cmd prompt, type:
adb devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again. You should see something like:
List of devices attached
945d3339495 device
if instead you see:
List of devices attached
945d3339495 offline
then most likely you need to look on your nexus for a notice to allow the connected computer permissions to use usb debugging. If you don't see a notice, disable/enable usb debugging in "Settings -> Developer options" and then you should get the prompt. You should select 'remember this computer', if not you will have to do it again upon reboot.
c. Now we need to reboot into the bootloader and load the drivers again. So type:
adb reboot bootloader
and your Nexus should reboot into the bootloader. My laptop found the driver on its own, note that in Device Manager it is now listed as ‘Android Device’ instead of under ‘Portable Devices’. If your system does not find the driver, follow the same steps as above to update your driver after you located the exclamation point in Device Manager.
Now we will verify that the driver is installed correctly while in the bootloader. Again from a command prompt opened from the directory where you saved all the files from step 1, type:
fastboot devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again.
3. Perform device unlock. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! Please backup accordingly.
Your Nexus should still be in the bootloader. Type:
fastboot oem unlock
Your Nexus will prompt you to accept. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! After a short moment, the device should report unlocked under “lock state”. Reboot device by typing:
fastboot reboot
After rebooting, sign in, etc.
4. Copy over SuperSU . In windows explorer locate the UPDATE-SuperSU-v1.25.zip and copy it to your Nexus internal storage area. Don’t put it any of the folders, just dump it in there. Now reboot into the bootloader again by typing:
adb reboot bootloader
5. Flash CWM. Once in the bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
after you get ‘finished’ from the command window, reboot your Nexus into CWM recovery by navigating with the volume buttons to ‘recovery mode’, then press power button.
6. Root Nexus. Using the volume keys, navigate to ‘install zip from sdcard’ and hit the power button. Now select ‘choose zip from sdcard’ and hit the power button. Navigate down to UPDATE-SuperSU-v1.25.zip’ and hit the power button. Select ‘Yes’, hit power. Once done select ‘go back’, then ‘reboot system now’.
Congrats, you’ve unlocked and rooted your Nexus!
Now at this point CWM recovery may or may not still be present on your device. There have been mixed reports on whether it will ‘stick’ the first time you flash it. The stock ROM has a check file that will replace CWM with the stock recovery upon reboot. To determine if CWM is still present simply reboot into recovery and see if it is there. Type:
adb reboot recovery
Obviously if you see the droid with exclamation point CWM did not stick. If you have no need for CWM, and simply wanted root you could stop now. Wait a few minutes and your device will reboot on its own and you are all done.
However, if you desire CWM then proceed on.
7. Rename recovery-from-boot.p to prevent stock recovery re-installation. Your Nexus should be booted normally at this point.
a. Go to the Play store and install ES File Explorer File Manager. Under settings enable ‘up to root’, ‘root explorer’, and ’mount file system’.
b. Navigate to /system and rename:
recovery-from-boot.p
to
recovery-from-boot.bak
by long pressing and selecting ‘rename’. Note: Be careful while navigating your device with these options enabled, a typo or slip-up could cripple your device and require a restore. I suggest once this rename is competed to disable the above options to avoid any mistakes in future exploring.
8. Flash CWM again.
a. Reboot into bootloader by typing:
adb reboot bootloader
b. once in bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
c. reboot device by typing:
fastboot reboot
d. verify CWM stuck by rebooting into recovery:
adb reboot recovery
And that should be it!
Some additional notes: CWM does make notice on rebooting with a message ”ROM may flash stock recovery on reboot. Fix? This can not be undone”. I don’t know what CWM will do there, so I prefer to rename the recovery-from-boot file so that I could easily restore it if I wanted. But perhaps that is what CWM does, although the message persists even after I renamed the file. Maybe someone could clarify this.
Hope this helps some people out in enjoying this great device even more, thanks for reading.
4.1.2 and 4.2.1 updates...
Thought I would revisit the thread as we've had two updates since I wrote the above. I installed 4.1.2 OTA with no problems but as expected, I lost root and CWM.
Because I'm lazy, I didn't worry over it much and then 4.2.1 shows up and also installed perfectly. Finally got around to getting root back and here are the steps I used.
Notes:
* Need to make sure drivers are correctly installed. See first post.
* I never really used CWM so I elected not to permanently install it this time.
* This update is a brief synopsis of how I got root back. If the steps are not clear, review the first post as the procedure is very similar.
1.) Ensure USB debugging is still enabled. On 4.2.1 "Developers options" are hidden by default. To enable simply tap "Settings > About tablet > Build number" 7 times. Back out and "Developers options" should now be available. In my case USB debugging was still enabled.
2.) Download SuperSU v0.99 and CWM 6.0.1.9 from links in first post. I used non-touch version of CWM.
3.) Transfer SuperSU over to internal storage of your Nexus. Be sure you know where you dumped it.
4.) Reboot into bootloader: adb reboot bootloader
5.) Temporarily boot or permanently install CWM so we can install SuperSU zip.
for temp boot type: fastboot boot recovery-clockwork-6.0.1.9-grouper.img
for perm install type: fastboot flash recovery recovery-clockwork-6.0.1.9-grouper.img
6.) Once in CWM select:
a. install zip from sdcard
b. choose zip from sdcard
c. navigate to /0/ then wherever you put SuperSU
7.) Once finished back out and reboot system now. I selected "No" on allowing CWM to disable stock recovery. If you are only temp booting CWM then this likely won't matter either choice you make. If you perm flashed CWM then you may wish to choose 'Yes".
That should cover it. Thanks for reading, any questions or corrections be sure to let me know.
I have a question about this:
I rooted and installed CWM on my 4.2 N7, but now, then I try to install the 4.2.1 OTA update, I get this error:
Code:
assert failed: apply_patch_check("/system/lib/libweb rtc_audio_preprocessing.so", "bin_number", "big_number""),
E: error in /cache/jop40d-from-jop40c.zip
(Status 7)
It's wise to apply this if I already have a rooted+CWM N7?
Some root procedures, or third party apps like Titanium Pro can make changes to certain system files that will cause an official update to fail. In your case, it appears at least "rtc_audio_preprocessing.so" located in "/system/lib/libweb" has been altered.
The easiest solution is to flash the current factory image then root. You can find them here: https://developers.google.com/android/nexus/images#nakasi.
However, you will lose your data. So back up accordingly.
If that's not an option, you can try:
a.) figure out which app you have that caused the change, and see if it has a 'revert' option or if uninstalling will put the file(s) back to stock.
b.) find the unmodified contents of /system/app and /system/lib and replace yours. Needs to be from 4.2 in your case.
c.) find a modified manual update patch (either zip for CWM or .img for fastboot) that has been altered to ignore the integrity check.
Curious, just went looking for "rtc_audio_preprocessing.so" in a factory 4.2 system.img and can not locate it, or the lib/libweb directory. Perhaps a third party app made these additions and thus the integrity check is failing as the files are unknown/unaccounted for?
At any rate, I went ahead and sourced a 4.2 system.img and extracted the /app and /lib directories in case this helps you or anyone else searching along.
Extracted from: nakasi-jop40c-factory-6aabb391.tgz
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip.md5
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip.md5
so I factory-reseted my N7, but it didn't helped. I found the file /system/lib/libwebrtc_audio_preprocessing.so so I tried to replace it with the file you posted (thanks btw!), but while using a console (su, then cp file.so file.so.backup) I get the error saying it's a read-only system, so I can't replace that file
any other idea?
EDIT: So I was playing around with the N7 (although I can really remember, I think I formated /system ?):
So, yeah, I actually formated /system for some unknown reason and there is no OS to boot, so I'm downloading at 25 KBps (yes...I know) and I'll be installing the JOP40D version for the N7.
ah, so the file is actually:
/lib/libwebrtc_audio_preprocessing.so
not
/lib/libweb/rtc_audio_preprocessing.so
That makes a little more sense. On cp over the original file, as you discovered the /system partition needs to be remounted as writable before you would be able to make changes. You could easily accomplish this with one of the root file explorers from the market. I use "ES File Explorer" as its free. Then simply copy over your file.
Or if you prefer adb: mount -o remount rw /system
Regardless, you are starting over from scratch so no worries. One of the things I love about this device is the option to start fresh-from-factory with minimal fuss.
igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA
cub0ne said:
igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA
Click to expand...
Click to collapse
I am also on 4.2.1 unlocked and rooted with wugfresh toolkit. I downloaded CWM from the play store, the app can download the latest CWM recovery and flash it for you. That is what I did, All I have used CWM for is a nandroid backup, but have booted into recovery and wiped cache and fixed permission
Has anyone had issue is SuperSU and CWM running Fix Permissions in the CWM app? I get an error...
Thank you!
Thank you very much for the excellent guide, your explanations were very clear!
It was a lot of fun following it, and I am very happy for choosing this guide over the 'one-click' toolkits.
I'll give it a try
After trying a "all in one toolbox" to unlock and root I think I'll give this a shot. I got stuck at not being able to root and like your OP said, doing it manually would help with the learning curve.
Quick questions that has popped up is.
Do I lock my bootloader back to use your guide?
I've noticed drivers I have in device manager have different names. Does this mean there are dif drivers that do the same thing? Should i delete them and use the ones in the OP?
Late response, but I'll answer for future users following this thread...
Once your bootloader is unlocked by any means, no need to relock in order to follow this guide. We simply have to have it unlocked so we can gain root
Drivers are probably the most common issues people have in any instance of trying to interact with their device. While its not imperative that the names are the same, what is most important is that you can communicate with the device. There really isn't the right or wrong driver name, just that the driver works! Having said that, if you are wondering whether you have the correct drivers installed, simply follow the steps and attempt a "adb devices" or "fastboot devices" command depending on your device status as is outlined in the tutorial. If you do not have the appropriate response, then you need to stop and determine the issue.
Update after OTA 4.2.2
Lost root as expected, and followed procedure in post #2 to gain root back. Also updated OP file versions to current as of this post as they all worked successfully.
Only thing I would note: If you get a "offline" notice after trying 'adb devices', be sure to check your nexus for a notification to allow the connected computer access for USB debugging. If you don't see one, go to "Settings -> Developer options" and disable/enable USB debugging and it should pop up. I don't remember this behavior when I first wrote the tutorial, so it may be something new for 4.2.2. After reboot it will require approval again, so you may wish to select 'remember this computer'. I added this note in the OP as well in the appropriate step.
Hey guys,
So i'm sure this is probably already out there, but I wanted to give everyone my method of success with rooting the latest version on Android (5.0) on our N5. Here it is:
Prereqs: You'll need to have these downloaded first
TWRP - Download to your Computer
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.0.1-hammerhead.img
SuperUser v2.19 - Download to your Phone
http://click.xda-developers.com/api...ainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Platform Tools - Download to your Computer
https://www.androidfilehost.com/?fid=9390355257214632011
Steps
1) Download SuperUser v2.19 to your phone.
2) Turn off your phone, and reboot into the BootLoader by holding Power + Vol (-). Wait until you see the Green Android Robot.
3) Plug your phone via Micro USB to your Computer.
4) Download and Extract Platform Tools in a "New Folder" on your C: Drive. Give the folder an easy name such as "N5" or something similiar
5) Download and Extract the TWRP recovery image to the "New Folder". Rename the "openrecovery-twrp-2.8.0.1-hammerhead.img" to "Recovery". NOTE: It may ask you to overwrite the exisiting recovery image (if applicable). Select Ok/Yes
6) Open your Command Prompt (Windows) and type the following: (You can copy and paste if you'd like)
* cd..\..
* cd c:\(Your New Folder)
* fastboot flash recovery recovery.img
6) Let TWRP flash to your phone (Should take no more than ~10 secs).
7) Toggle your phone to "Recovery" by using the Voume Up/Down keys. Press the Power button to select/confirm.
8) Once TWRP has loaded, press the "Install" icon, followed by "Zip File", and proceed to the "Downloads" folder that you have the SuperUser v2.19 zip downloaded.
9) Select the zip and confirm by swiping at the bottom.
10) Reboot back to the "System"
11) Done
_______________________________________________________________________________
I tried to be as clear as I could with this write up, so I hope this makes sense. It really is straight forward.
Although I'm definitely not the one who came up with this method or files, I wanted to share what worked best for me to Root my N5 running the 5.0 OTA.
If this helped you get root back or makes sense, give a "Thanks".
Take it easy...
Thank you for posting this. I tried three other methods to get root back before this, and none of them worked. This one did the trick without any problems at all. Thanks again!
Wug's Nexus Root Toolkit 1.9.4
kyoshiro22 said:
Wug's Nexus Root Toolkit 1.9.4
Click to expand...
Click to collapse
I know there's Toolkit's out there, but this is for those who choose to take the "Fastboot" approach.
gestevez1213 said:
Hey guys,
So i'm sure this is probably already out there, but I wanted to give everyone my method of success with rooting the latest version on Android (5.0) on our N5. Here it is:
Prereqs: You'll need to have these downloaded first
TWRP[ - Download to your Computer
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.0.1-hammerhead.img
SuperUser v2.19 - Download to your Phone
http://click.xda-developers.com/api...ainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Platform Tools - Download to your Computer
https://www.androidfilehost.com/?fid=9390355257214632011
Steps
1) Download SuperUser v2.19 to your phone.
2) Turn off your phone, and reboot into the BootLoader by holding Power + Vol (-). Wait until you see the Green Android Robot.
3) Plug your phone via Micro USB to your Computer.
4) Download and Extract Platform Tools in a "New Folder" on your C: Drive. Give the folder an easy name such as "N5" or something similiar
5) Download and Extract the TWRP recovery image to the "New Folder". Rename the "openrecovery-twrp-2.8.0.1-hammerhead.img" to "Recovery". NOTE: It may ask you to overwrite the exisiting recovery image (if applicable). Select Ok/Yes
6) Open your Command Prompt (Windows) and type the following: (You can copy and paste if you'd like)
* cd..\..
* cd c:\(Your New Folder)
* fastboot flash recovery recovery.img
6) Let TWRP flash to your phone (Should take no more than ~10 secs).
7) Toggle your phone to "Recovery" by using the Voume Up/Down keys. Press the Power button to select/confirm.
8) Once TWRP has loaded, press the "Install" icon, followed by "Zip File", and proceed to the "Downloads" folder that you have the SuperUser v2.19 zip downloaded.
9) Select the zip and confirm by swiping at the bottom.
10) Reboot back to the "System"
11) Done
I tried to be as clear as I could with this write up, so I hope this makes sense. It really is straight forward.
Although I'm definitely not the one who came up with this method or files, I wanted to share what worked best for me to Root my N5 running the 5.0 OTA.
If this helped you get root back or makes sense, give a "Thanks".
Take it easy...
Click to expand...
Click to collapse
This is NOT working.... I tried it 3 times on 2 devices
papayayoghurt said:
This is NOT working.... I tried it 3 times on 2 devices
Click to expand...
Click to collapse
What part are you stuck at?
For me, I needed to erase cache for the TWRP to stick. Otherwise, when I rebooted it was gone and was using the default recovery.
Use the command:
Code:
fastboot erase cache
before
Code:
fastboot flash recovery recovery.img
if you have the same problem installing TWRP.
I used chainfires auto root for the N5 (stock lollipop Boot loader). Worked great. Just download to a PC put phone into boot loader and run the bat file. I can't link but a quick google will find it for you.
Sent from my Nexus 5 using Tapatalk
andrelessa said:
For me, I needed to erase cache for the TWRP to stick. Otherwise, when I rebooted it was gone and was using the default recovery.
Use the command:
Code:
fastboot erase cache
before
Code:
fastboot flash recovery recovery.img
if you have the same problem installing TWRP.
Click to expand...
Click to collapse
Good find. Didn't happen to me, but i'm sure it may to others. Were you all set afterwards with Root?
Personally, I'm using the autoroot from chainfire. Works like a charm, no custom recovery is needed (I have the stock recovery).
gestevez1213 said:
What part are you stuck at?
Click to expand...
Click to collapse
Everything is working, but then SuperSU can´t find a Binary.
gestevez1213 said:
Good find. Didn't happen to me, but i'm sure it may to others. Were you all set afterwards with Root?
Click to expand...
Click to collapse
Yes, I read somewhere that TWRP need this...
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
Are you running the official lollipop release? It should work with that. Delete the app, and try again.
Just put your phone in bootloader and run cf-autoroot from windows if you dont want twrp.
I have twrp but its not working like that
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
Had the same issue and needed to flash the updated kernel from chainfire : https://www.androidfilehost.com/?fid=95747613655047375
Why are you trying to do this the hard way? Just use chainfire's autoroot.
It works perfect and it's literally one command
fastboot boot CHautoroot.img (or whatever the file name is)
cf-auto-root is the way
I agree, just use cf-auto-root. You should be good to go in no time.
Just for FYI, if you already have unlocked bootloader, it won't wipe your data, if you are concerned.
CF-auto-root roots N5 without modifying your kernel. I believe, if you flash the SuperSU in TWRP, it would modify the kernel. It's nothing bad, but if you want to remain "stock" and don't want to reflash stock ROM later to get the OTA, just use "Full unroot" from SuperSU app and you are stock and ready for next OTA.
I have encrypted the storage on my Nexus 5. Will CF-Auto-Root wipe my storage?
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
I have the same error.
Disclaimer: If you are not comfortable with using Fastboot and ADB and editing system files than this guide might not be for you. At this point this is what I have to offer.
Click here for the unofficial twrp image - Latest version as of 12/27/14
So getting right into it.
1. Turn on ADB mode on the watch by going to about and tapping the build info 7 times.
2. Download ADB and Fastboot utilties
3. Plug the watch into the computer and your phone should vibrate and ask you to accept the computers fingerprint, tick the check box to always allow and hit ok
4. Open up a command prompt or terminal inside of where the ADB utilities are located and enter
Code:
adb reboot bootloader
This next step will wipe your data!
5. Now you should be in fastboot, go ahead and on the terminal use the next code and follow prompts to unlock
Code:
fastboot oem unlock
6. Now after you re-set up your watch again you will need to do step 1 and 3 again.
Please do not skip step 6!
7. Go ahead and issue
Code:
adb reboot bootloader
8. Flash unofficial twrp, make sure the recovery image file is in the same location as fastboot than issue
Code:
fastboot flash recovery YOURIMGNAMEHERE.img
9. Upon successfully doing that you should have twrp installed
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB use the proper name of what you downloaded. Issue
Code:
adb push SUPERSUNAMEHERE.zip /sdcard/
11. Issue
Code:
adb reboot recovery
12. than using the very tiny TWRP and somewhat messed up go ahead and use it to install the supersu.zip under the folder /sdcard
13. Enjoy root and twrp.
I will make this guide into a much easier Java program in the very near future to make it easier to use.
This was typed up pretty fast and it is kinda hacky, I will work on a bat script and a shell script if we have enough osx users here. I'm sure someone will come along and make this better if I don't get around to it.
Credits:
Dees-Troy for his TWRP support for dory our fish brother device which worked on our device
Chainfire for all his hard work these many years
Q: ADB complains there is no device listed.
A: Install universal ADB drivers and then go to device manager and under the device with a yellow warning icon go to update driver, Browse my computer, let me pick from list of device drivers, than Google ADB interface. If it still complains turn off debugging, than turn it back on, revoke authorization, then disable and re-enable again.
One more just in case.
Great work!!
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
hatefuel19 said:
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
Click to expand...
Click to collapse
The latest supersu is version 2.36 dated 11.27.2014. 1.94 is well over a year old, you need to update for sure that is why you are force closing.
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
hatefuel19 said:
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
Click to expand...
Click to collapse
I'm here to help! I'm working on adding other mods to my other thread right now I'm working on getting busybox working.
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------
jimmydigital00 said:
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
Click to expand...
Click to collapse
Disregard I did it again and for some reason it worked. Maybe I need to reboot first.
Recovery
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
adamrobles said:
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
Click to expand...
Click to collapse
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
reflashed
tonu42 said:
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
adamrobles said:
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
Click to expand...
Click to collapse
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
Thank you for that information, I stopped the download of the dump.
Downloading the stock recovery now.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
I must have skipped a step...
installed stock recovery
booted into the watch system
enabled adb debugging
reboot to bootloader
install your recovery image
rebooted
pushed supersu
rebooted to twrp
installed supersu
rebooted to system
adb shell - verified root!
You are awesome! Thank you for taking the time to help me!
HYPE for 5.0.1
'm Hype! can't wait to flash the first 5.0.1 system dump on this as stated by +Darek Ross we MAY be receiving update as early as today!
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
zvieratko said:
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
Click to expand...
Click to collapse
My guide is setup like the one you put there. In order to get adb working again you need to re setup the watch step 6. Read the instructions carefully. I'll post a batch script later to simplify this.
Sent from my A0001 using XDA Free mobile app
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
zvieratko said:
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
Click to expand...
Click to collapse
By default debugging is disabled, I'm not sure how you were able to issue an ADB command on step 7 with out first performing step 6.
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
zvieratko said:
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
Click to expand...
Click to collapse
Ah I see, yea the guide is written as the absolute minimum to work right now. Like I said later today I'll try to post a script that automates all of this, its much easier.
Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks
Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!
Yeah that sorted it thanks a lot
Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,
jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!
Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it
@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.