Database Develop

[ROOT][CWM] Root Nexus 4 & Install Official ClockworkMod Recovery

I originally posted this method at AddictiveTips. The method I posted there is targeted at everyone including the absolute beginners and I have also included instructions there for setting up the required tools, and for reverting back to the original recovery and boot image in case anything goes wrong. All external credits should be given to that guide (it does link back to this thread). Here is the link: How To Root Nexus 4 and Install ClockworkMod Recovery on it.
To my knowledge, this is the first confirmed working rooting method for Nexus 4 posted here at XDA. Though my knowledge is limited, so please correct me if I am wrong.
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
This method requires an unlocked bootloader. You can find instructions for unlocking it at XDA, or at the AddictiveTips guide linked above (the link to the bootloader unlock guide is in the requirements section there).
UPDATE 2: If your device does NOT get wiped after unlocking the bootloader, fret not. While this isn't expected behavior, several users have experienced the same on the Nexus 4. This could be due to some error at Google's end, but unlocking still works perfectly fine.
That said, let's get on with rooting and flashing CWM.
ClockworkMod Recovery Method:
Download the latest official ClockworkMod recovery from CWM website and rename it to recovery.img
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Download the recovery flashable SuperSU package with Busybox and transfer it to your phone's internal SD card.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Enter this command in a command prompt to flash the ClockworkMod recovery (making sure you are in the directory where you downloaded the recovery file):
Code:
fastboot flash recovery recovery.img
OR
If you simply want to root without flashing a custom recovery and want to stick to your stock recovery, simply boot this recovery once using this command:
Code:
fastboot boot recovery.img
If you flashed the recovery in the previous step, you can now boot into recovery by pressing volume-up or volume-down twice to select the recovery option, and then the power button to enter it. If you simply booted into the recovery file without flashing it in the previous step, you should already be in recovery now.
Once in recovery, take a backup to be on the safe side.
Flash the downloaded SuperSU and busybox package zip file from recovery.
Clear cache and dalvik cache just in case (not required but won't hurt).
Reboot the device.
ADB and Insecure Boot Image Method:
Grab the insecure boot image from this thread.
Also download these root files. This package includes the latest SuperSU 0.98, latest su binary that comes with it, and working busybox (not sure if latest).
Extract the contents of the downloaded zip file to your computer.
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Get back into bootloader mode and boot into the downloaded insecure boot image:
Code:
fastboot boot boot.img
Don't worry, this will not replace your existing boot image and will only boot from the insecure one once.
If it does NOT work for you and you get stuck in a boot loop, simply reboot your phone into bootloader and use the above command again. Some users had issues with booting from it the first time, but a second attempt worked.
Once booted into Android successfully using the insecure boot image, simply enter these commands one by one in command prompt (making sure you are in the directory where you downloaded the files):
Code:
adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
Reboot your device.
You will now have root access. Tested and confirmed working by Stryder5 and many others.
Credits:
Stryder5 for testing, confirming, tipping me about working CWM, providing the required drivers, and helping others on the thread. :highfive:
Harry GT-S5830 for the insecure boot image.
fkrone for his recovery revert disabler script and his unofficial working CWM before an official one became available.
Kstarz for posting this same recovery method with his own working CWM in this thread before an official one was out.
evaradar for informing about the release of official ClockworkMod recovery.
Koush for developing ClockworkMod recovery.
Chainfire for developing SuperSU.
Everyone else on this thread for testing, providing feedback and hitting the 'THANKS' button. =)
I have tried my best to give everyone the due credit but if I have missed out on anyone, please do remind me.

Yep, worked like a charm. Got Titanium running and restored all my apps
Btw, check your PM.

Checked...thanks. =) Added the links.

stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied

jshaw06 said:
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
Click to expand...
Click to collapse
You need to boot the unsecure boot.img first.

BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.

HQRaja said:
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
Click to expand...
Click to collapse
I'm pretty sure I used the one Harry GT-S5830 provided.

I used the one in the OP of that thread.. is there a different one I'm supposed yo use?
Sent from my SGH-T999 using Tapatalk 2
---------- Post added at 06:41 AM ---------- Previous post was at 06:23 AM ----------
It works
Sent from my SGH-T999 using Tapatalk 2

jshaw06 said:
It works
Click to expand...
Click to collapse
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.

Stryder5 said:
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Click to expand...
Click to collapse
No issues with installing the OTA after root?
Edit: Just noticed in your sig that you did not install the update.

I installed after ota
Sent from my SGH-T999 using Tapatalk 2

jshaw06 said:
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You mean you gained root after you installed the OTA?
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
apzalo said:
No issues with installing the OTA after root?
Click to expand...
Click to collapse
I gained root, but haven't installed the OTA yet.

when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?

Yes sorry gained root after OTA
Sent from my SGH-T999 using Tapatalk 2

Elemenopee said:
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Click to expand...
Click to collapse
Nope, it isn't. Try again...it's safe to try as many times as you want since we're not flashing the boot image; merely booting from it, which is temporary and doesn't last after reboot. Hope it works on the next try.

After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!

quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?

Ngo93 said:
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
Click to expand...
Click to collapse
Step 8 itself will boot up the phone normally into Android, just using that insecure boot image instead of the stock one. And yes, you then just start entering those adb commands. =)

0.0 said:
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Click to expand...
Click to collapse
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.

HQRaja said:
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
Click to expand...
Click to collapse
so i extract the "occam-jop40c-factory-cd3dc140.tgz" file, then double-click the "flash-all.bat" file?

Help Needed Please

Hi, I know this is going to sound so stupid but I need help ASAP.
I was fooling around with installing different ROM's for my HTC One, I tried the Google Edition for a while and decided it wasn't for me as I lost the TV remote. I then tried to re-flash the Android Revolution HD 12 I had on before and it wouldn't flash. I thought a wipe would work but now I've succeeded in ending up with a TWRP recovery that works fine but no software whatsoever to flash or boot to. The phone says 'No OS Installed'
Every time I turn off the phone it also says that it doesn't appear to be rooted, do I want to install supersu? The phone says 'unlocked' with CID 11111111
I have totally fallen into the idiot trap, too much confidence and ambition, zero skill and talent.

NailFace said:
Hi, I know this is going to sound so stupid but I need help ASAP.
I was fooling around with installing different ROM's for my HTC One, I tried the Google Edition for a while and decided it wasn't for me as I lost the TV remote. I then tried to re-flash the Android Revolution HD 12 I had on before and it wouldn't flash. I thought a wipe would work but now I've succeeded in ending up with a TWRP recovery that works fine but no software whatsoever to flash or boot to. The phone says 'No OS Installed'
Every time I turn off the phone it also says that it doesn't appear to be rooted, do I want to install supersu? The phone says 'unlocked' with CID 11111111
I have totally fallen into the idiot trap, too much confidence and ambition, zero skill and talent.
Click to expand...
Click to collapse
You should be able to use this toolkit to install SU and also to sideload a rom zip from your PC to the phone to reinstall your ROM of choice. Sounds like you wiped your data partition entirely. Since you have S-off and Super CID you should have no problems loading another rom. Just have to use one of the creative ways to get it on the phone (sideload, USB-OTG adapter, etc.)
http://forum.xda-developers.com/showthread.php?t=2242635

crushalot said:
You should be able to use this toolkit to install SU and also to sideload a rom zip from your PC to the phone to reinstall your ROM of choice. Sounds like you wiped your data partition entirely. Since you have S-off and Super CID you should have no problems loading another rom. Just have to use one of the creative ways to get it on the phone (sideload, USB-OTG adapter, etc.)
http://forum.xda-developers.com/showthread.php?t=2242635
Click to expand...
Click to collapse
Thanks for your reply,
could you do a step by step guide for me please, I don't have an USB-OTG adaptor.

I cannot install the program, it says its not supported by my OS (im on Windows 8)

NailFace said:
Thanks for your reply,
could you do a step by step guide for me please, I don't have an USB-OTG adaptor.
Click to expand...
Click to collapse
The steps should be here in the guide:
http://forum.xda-developers.com/showthread.php?t=2325853
Also here for sideload:
http://forum.xda-developers.com/showthread.php?t=2318497

crushalot said:
The steps should be here in the guide:
http://forum.xda-developers.com/showthread.php?t=2325853
Also here for sideload:
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I really need a more step by step guide, I've ****ed things up already so I think I need a baby walk through

NailFace said:
I really need a more step by step guide, I've ****ed things up already so I think I need a baby walk through
Click to expand...
Click to collapse
Well the easiest way to do a sideload is using the All in One tool. Do you have access to any other PC that have Windows 7 or XP? I don't have a win 8 system to try to assist with compatibility mode with the one.exe tool.
If no other PC options are available then we will have to go the long way which will involve installing ADB like in this guide: (Under Installation section - It has 5 steps for installing ADB)
http://forum.xda-developers.com/showthread.php?t=1427008
Once ADB is installed we can use these steps from the sideload guide that I posted:
Make Sure HTC Drivers are installed and ADB is already working
1. Reboot into TWRP
2. in TWRP, Hit advanced and find Sideload
3. Swipe to start Sideload
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. type adb devices and it should show your device connected and say sideload
6. Your ZIP file should already be in your adb folder - See Example Below
7. You are now ready to push the zip.....
8. type adb sideload nameofzip.zip <------------See Example Below
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery

crushalot said:
Well the easiest way to do a sideload is using the All in One tool. Do you have access to any other PC that have Windows 7 or XP? I don't have a win 8 system to try to assist with compatibility mode with the one.exe tool.
If no other PC options are available then we will have to go the long way which will involve installing ADB like in this guide: (Under Installation section - It has 5 steps for installing ADB)
http://forum.xda-developers.com/showthread.php?t=1427008
Once ADB is installed we can use these steps from the sideload guide that I posted:
Make Sure HTC Drivers are installed and ADB is already working
1. Reboot into TWRP
2. in TWRP, Hit advanced and find Sideload
3. Swipe to start Sideload
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. type adb devices and it should show your device connected and say sideload
6. Your ZIP file should already be in your adb folder - See Example Below
7. You are now ready to push the zip.....
8. type adb sideload nameofzip.zip <------------See Example Below
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
Click to expand...
Click to collapse
I owe you a beer, thank you very much. Everything working now.

[TUTORIAL] Applying an OTA update with stock + root/custom recovery

Preamble
As the title suggests, I had a Nexus 5 running stock Android 5.0, with root and TWRP, and wanted to update to Android 5.0.1 (without losing all my data, of course). I couldn't find any guides for my particular circumstances, so after working out how to do it myself, I thought I'd share my method.
Note: This guide is not for the uninitiated. Be prepared to Google something for yourself if you don't understand it.
Prerequisites
Before starting this guide, you should have:
A Nexus 5 that running stock Android. The presence of root/Xposed/custom recovery (maybe custom kernels?) shouldn't be relevant, but I can't vouch for the efficacy of this guide if you've done something obscure to your install.
Android SDK tools, specifically the ADB and fastboot binaries. Additional USB drivers may be required on Windows.
The factory image for the Android version you are currently running.
1. Uninstall root and other /system modifications
If you have rooted your Android, and/or installed BusyBox, Xposed or other modifications to /system, you will need to uninstall these modifications. Failing to do so will cause the OTA to complain that there's something funky going on in your /system partition.
You may be able to manually uninstall each of these modifications, but this was not enough for my install – doing a ‘Full unroot’ in SuperSU still left behind files in /system. The easiest way to uninstall all /system modifications is to reflash the /system partition.
Extract the Nexus 5 factory image (e.g. hammerhead-lrx21o-factory-01315e08.tgz), yielding a directory with files such as flash-all.bat and image-hammerhead-XXXXXX.zip. Do not use the flash-all script, as this will unnecessarily wipe all data on the device.
Extract the image-hammerhead-XXXXXX.zip file, specifically the system.img file.
Open a command prompt/terminal window.
Connect the phone to the computer with a USB cable.
Boot the phone into the bootloader.
Method 1: Power down the phone, then hold VolUp + VolDn + Power until the phone boots into the bootloader.
Method 2: From the terminal, run adb reboot bootloader while the phone is still powered on.
From the terminal, run fastboot flash system /path/to/system.img.
2. Uninstall any custom recovery
Custom recoveries don't seem to support OTA updates, making it necessary to uninstall the custom recovery by reflashing the stock recovery.
Extract the recovery.img file from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash recovery /path/to/recovery.img.
Optional: Reflash boot.img and/or cache.img
Some users have reported that reflashing system.img was not sufficient, and that reflashing boot.img and/or cache.img was also necessary. I did not have this problem, but if you do:
Extract the boot.img and/or cache.img files from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash boot /path/to/boot.img.
From the terminal, run fastboot flash cache /path/to/cache.img.
3. Apply the OTA update
The simple part. In the bootloader, use the VolUp/VolDn buttons to select ‘Start’, then press the Power button, to reboot into Android. Follow the system update instructions to install the OTA update.
4. Reflash the custom recovery and re-root
Also self-explanatory.

Hey,
I just wanted to say thanks. This totally fixed the problem I was having. I also want to add that after I flashed the system.img, I was getting errors related to "EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot" with a bunch of numbers after. I googled it and found I had to also flash boot.img, and after that, the OTA worked fine. I would assume if anyone else gets errors like this, they should flash whatever img it shows in the error (ie: mine said /by-name/boot so I flashed boot.img).
-BGM

It worked for me

I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?

azlan96 said:
I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?
Click to expand...
Click to collapse
I also had problems using ‘Full Unroot’ in SuperSU. It's not actually as ‘full’ as it sounds.
Flashing a full factory image would normally wipe everything, but carefully following this guide will only reset the /system partition, not any user data.

I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo

Taiyo85 said:
I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo
Click to expand...
Click to collapse
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..

azlan96 said:
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..
Click to expand...
Click to collapse
Flash Stock + Unroot wipes everything and defeats the purpose of the tutorial made by RunasSudo
First and foremost you should download Android SDK (Tools only) on http://developer.android.com/sdk/index.html and then ask to install the extra: Google USB Driver.
With Nexus Root Toolkit you don't need terminal, click on advanced and you should see options to flash through fastboot the system only, recovery and kernel. It is pretty straighforward and it asks where the .img are in your computer

Thanks! This guide worked.
For Ubuntu users, you need to install adb and fastboot with these commands :
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update (optional)
sudo apt-get install android-tools-adb android-tools-fastboot

Thanks for the great step by step.
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img. Once that was done, I had no problems side loading the update and am now running LRX22C.
I only seem to fiddle with adb once a year - when it OTA time comes - and can never seem to remember some of the steps that need to be taken. Reading through some of the other threads, I have a feeling a lot of people who rooted/custom recovery and cant do the OTA are going to be doing complete image re-flashes when this guide makes that completely unecessary.
thanks again,
.d

BananasGoMoo said:
I googled it and found I had to also flash boot.img, and after that, the OTA worked fine.
Click to expand...
Click to collapse
datcon said:
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img.
Click to expand...
Click to collapse
Thanks for the feedback! I've added a note about boot.img to the OP.

+1 for flashing boot.img worked perfect after I did that.

I tried with this tutorial. I flashed system and recovery and then restart. Confirm OTA but I get ERROR.
Then I flashed boot as it was described. Now I don't get OTA In About phone, I'm still on 5.0.0, Check for updates now don't find update
Any idea?
UPDATE - UPDATE: After hour now it is here ... super, it works.

This walkthrough was most helpful! Ended up replacing the boot.img as well since I had ElementalX installed. My apps are optimizing as we speak. Thank you!

Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
adb reboot bootloader
Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache (this is optional. I didn't have to do it, but you might)
Use Volume Up/Down to select Start > press Power Button to reboot
Update via Settings > About Phone > System Update
Re-flash TWRP recovery:
Get the file from here: http://forum.xda-developers.com/showpost.php?p=57580889&postcount=1
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img

Paul22000 said:
Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
1. Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
2. Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
3. Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
4. Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
5. adb reboot bootloader
6. Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
7. Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
8. Use Volume Up/Down to select Start > press Power Button to reboot
9. Update via Settings > About Phone > System Update
Click to expand...
Click to collapse
Maybe you could add `fastboot erase cache` as stepp 8.

gee2012 said:
Maybe you could add `fastboot erase cache` as stepp 8.
Click to expand...
Click to collapse
I added it to step 7, thanks. :good: I also cleaned up the formatting and added step 10 about re-flashing TWRP.

Loading problem
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.

guangy said:
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.
Click to expand...
Click to collapse
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.

RunasSudo said:
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.
Click to expand...
Click to collapse
I flashed the cache image as well, then the problem solved. Thanks

Everything urbane root easy how-tos and all the files you need in one place (11/26)

The purpose of this thread is to make the rooting process easier with all the files you need in one place to root and tutorials and a list of must have apps
You will be able to find everything you need in one spot.
I TAKE NO RESPONSIBILITY FOR ANYTHING YOU DO TO YOUR DEVICE.
* Please Leave Suggestions On What Else You Would Like To See Included In This Thread
Check back often as this will be a work in progress
Please vote yes or like so I can get a feel for how many people are interested in a thread like this so I can decide whether or not it's worth my time to continue it.
I've also provided two prerooted system images ( just be sure to follow steps 1 thru 12 and step 18 ( optional depending on the image )
Thanks Rob
__________________________________
Let's start by voiding your warranty lol by unlocking the bootloader ( Warning this will erase all data and factory reset your watch ). You will need an adb fastboot program of your choice installed on your computer. I prefer minimum ADB fastboot link in downloads section. Plus the proper drivers ( I will be providing links to them as well later)
Now what I like to do is create a folder on the desktop of my computer and name it urbane. Then download all the files and apps I will need and put the in the folder.
That way you can open that folder and have ADB open at the same time and you can just drag and drop the file your planning on pushing or flashing to your watch by placing it after the proper command. Which will be explained later.
1- On your Watch go to settings
2- Scroll down to about click on it
3- Find and click on build number 5 to 8 times
4- Swipe back and now go into developer options and enable USB debugging
5: Put watch in the charger and plug into computer wait for computer to recognize it and install the drivers
6- Now open terminal emulator (minimum ADB fastboot) on your computer and without the quotes and hitting enter after each command type in
"adb devices"
You should see your watch there
7- Now type
"adb reboot bootloader"
8- Wait for it to boot into fastboot mode then type
"fastboot oem unlock"
9- Follow instructions on device
device will factory reset & reboot
10- Wait for it to fully reboot then follow steps 1 thru 7 again and we can flash TWRP
This is where the drag and drop comes in. In the command line where you see (drop here) that's where you will grab the file/image from your urbane folder and drop it onto the terminal screen
11- Now that you're back into fastboot mode type in
"fastboot flash recovery (drop twrp image here)"
12- OK let's see TRWP so type in
"adb reboot recovery"
Alright now that we know we have TWRP
Do a backup and reboot
Now is a good time to install a file browser, if you haven't already done so and advanced settings. I prefer the file browser I listed in the downloads section as you can send and install apks and files from your phone to your watch.
Now we're going to pull that backup to our computer
Use the file browser on your watch to get the exact path to your backup location which will look something like this /scars/TWRP/BACKUPS/and a bunch of numbers and letters/
So type in
"adb pull /sdcard/TWRP/BACKUPS/*************/ (drop your urbane folder here)/"
Wait for it to finish will take a few minutes and reboot
13- Plug your watch back into computer and wait for computer to recognize it again. Now we can install super su
type in
"adb push (drop su zip here) /sdcard/
14- Reboot into recovery
" adb reboot recovery "
Now's the tricky part, using TWRP's tiny navigation go to install then install zip then to sdcard and find and click on the su zip and install. Reboot
15- Now let's install busybox ( Note if you are going to install skin's kernel you can skip this step and proceed to step 18 as his kernel had busybox built in ). With the watch plugged into your computer. ADB and your urbane folder open
Type in
"adb push ( drop busybox apk here) /sdcard/"
16- On your watch open the file browser and navigate to the busybox apk and click on it. It will install and do is thing, once installed go to your applications find and click on it. It will act weird then probably say it's stopped working but that's OK it's installed and working
17- Kernel time
Type in
"adb push ( drop kernel image here) /sdcard/"
"adb reboot recovery"
In recovery click install then click image then click boot image
And navigate to your sdcard and find skin's kernel click on it and swipe to install
18- Let's start by doing another backup, so assuming you've already backed up at least once already and have pulled the backups to your computer. You can if you haven't already done so delete the backups on your watch before you backup again
19- Next let's take some control over our new custom kernel by installing kernel auditor
Type in
"adb push (drop kernel auditor apk here) / data/local/tmp/"
"adb install -r ( drop kernel auditor apk here)"
Reboot and enjoy
*PLEASE HIT THANKS*

DOWNLOADS
IF YOU ARE NEW TO THIS PLEASE READ THE OP ENTIRELY BEFORE TRYING TO FLASH OR INSTALL ANYTHING.
I TAKE NO RESPONSIBILITY FOR ANYTHING YOU DO TO YOUR DEVICE
Stock images provided by @Skin1980 -
Recovery- https://www.androidfilehost.com/?fid=24269982086988347
Boot- https://www.androidfilehost.com/?fid=24269982086988339
System- https://www.androidfilehost.com/?fid=24269982086988934
__________________________________
Rooted system images
After flashing be sure to wipe caches dalvik/cache
Rooted system imaged 5.1.1 LCA44B (super su installed) - https://www.androidfilehost.com/?fid=24269982087001702
The following images have some unnecessary system apps and watch faces uninstalled to slim down the system and to make room on the system partition to change other apps to system apps . ( you can get back any of the uninstalled apks by flashing the stock image file rebooting then using file browser on your watch navigate to the apk you want back and send it to your phone then after flashing this image send the apk back to your watch and install it)
Rooted system imaged 5.1.1 LCA44B ( su, busybox and kernel auditor installed ) to be combined with stock kernel as skin's kernel has busybox preinstalled -
https://www.androidfilehost.com/?fid=24269982087004874
Rooted system image 5.1.1 LCA44B (su and kernel auditor installed ) for use with skin's kernel-
https://www.androidfilehost.com/?fid=24269982087005360
My personal kernel auditor settings with skin's kernel for best performance-
https://www.androidfilehost.com/?fid=24269982087005023
___________________________________
Stuff for root ( images, apks, zips )
@Skin1980 kernel-
Original thread- http://forum.xda-developers.com/wat...rnel-skin1980s-g-watch-urbane-kernel-t3210691
Direct download-
https://www.androidfilehost.com/?fid=24269982086999750
TWRP 2.8.7.0 -
Original source- https://dl.twrp.me/bass/#
Alternate download-
https://www.androidfilehost.com/?fid=24269982086988968
Wear Supersu zip - https://www.androidfilehost.com/?fid=24269982086990060
Kernel auditor ported by @bitstra from @Grarak work -
Original thread- http://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122
Direct download-
https://www.androidfilehost.com/?fid=24269982086989489
BusyBox on rails apk - https://www.androidfilehost.com/?fid=24269982086989488
Minimum ADB fastboot for windows - http://forum.xda-developers.com/showthread.php?t=2317790
Google ADB drivers can be found here-
http://developer.android.com/sdk/win-usb.html
__________________________________
OTHER USEFUL APPS:
File manager for android wear - https://play.google.com/store/apps/details?id=com.woiapp.filemanagerwear&hl=en
Advanced settings - https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en
Reset Wear Client-
Original thread- http://forum.xda-developers.com/and.../app-reset-wear-client-switch-phones-t3058962
Direct download- https://www.androidfilehost.com/?fid=24269982087005403
Wear internet browser- https://play.google.com/store/apps/details?id=com.appfour.wearbrowser&hl=en
VFP benchmark for android wear-
https://play.google.com/store/apps/details?id=jp.flatlib.flatlib3.vfpbenchw
____________________________________
Useful apks that can be sideloaded:
Greenify - https://www.androidfilehost.com/?fid=24269982086999820
/system/appmover
Used to convert user apps into system apps and vice versa ( USE CAUTION )
https://www.androidfilehost.com/?fid=24269982087004923

Other How-tos
Flashing images via fastboot
1- plug watch into computer and start ADB
2- Type in
"adb reboot bootloader"
"fastboot flash boot ( drop boot image here)"
"fastboot flash recovery ( drop recovery image here)"
"fastboot flash system ( drop system image here)"
__________________________________________
Returning to Stock
1- Download the stock images from the downloads section to your computer
2- Follow the above instructions for flashing images
3- Now on the watch click one of the arrows till you see recovery then click the circle (center button)
4- You will see a droid laying down with a red triangle
Swipe from the top left of the screen down to the bottom right
Now you're in recovery
Now you want to do a factory reset

I would just like to give a big thanks to those of you kind enough to hit the thanks button and that goes to a select few as I've had well over 100 downloads, 2100 views and only 21 thanks. I see it all over we really need to show the people that make this site great some appreciation

Awesome work! Keep it up!

Robshr said:
The beginnings of the downloads section is up.
Working on tutorials and links to threads
Also a prerooted (super su and busybox installed) latest version system image
Click to expand...
Click to collapse
So I only have to flash the prerooted system image and I'm fine to be rooted?
(TWRP for a backup at first of course..)
Sent from my HTC One M9 using XDA Free mobile app

meand0g1 said:
So I only have to flash the prerooted system image and I'm fine to be rooted?
(TWRP for a backup at first of course..)
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Yes that's what I'm hoping for. After you flash it you can test by typing
"adb shell"
"su"
And you should see something like this
[email protected]:/ #
If you do then super su is installed and you're rooted

meand0g1 said:
So I only have to flash the prerooted system image and I'm fine to be rooted?
(TWRP for a backup at first of course..)
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Just wondering if it all worked out for you?

Will test it when I own the watch..
Sent from my HTC One M9 using XDA Free mobile app

Doing all of this right now. Will report back when finished! Thanks man
---------- Post added at 06:35 PM ---------- Previous post was at 05:38 PM ----------
Okay so I unlocked bootloader, flashed twrp and rebooted into recovery. I can't backup anything because nothing is mounted. I've tried mounting though twrp with no luck whatsoever. So I tried erasing system and boot using fastboot to flash system image and skins kernel. But when I reboot the watch it boots straight into recovery....

anthonyg45157 said:
Doing all of this right now. Will report back when finished! Thanks man
---------- Post added at 06:35 PM ---------- Previous post was at 05:38 PM ----------
Okay so I unlocked bootloader, flashed twrp and rebooted into recovery. I can't backup anything because nothing is mounted. I've tried mounting though twrp with no luck whatsoever. So I tried erasing system and boot using fastboot to flash system image and skins kernel. But when I reboot the watch it boots straight into recovery....
Click to expand...
Click to collapse
Boot into fastboot and if you already have skin's kernel flashed try just flashing the system image and make sure you wipe the caches Dalvic/cache
Questions- did you flash su or did you use a prerooted image. I think su needs to be installed to do a back up

Robshr said:
Boot into fastboot and if you already have skin's kernel flashed try just flashing the system image and make sure you wipe the caches Dalvic/cache
Questions- did you flash su or did you use a prerooted image. I think su needs to be installed to do a back up
Click to expand...
Click to collapse
I'm using preroot image for skins kernel with kernel auditor . I've tried using
Fastboot flash system "drag and drop system.img" then
Fastboot flash boot "drag and drop skins boot.img"
Then reboot and it goes straight into recovery
The only way I could get data to show up in twrp was formatting data

anthonyg45157 said:
I'm using preroot image for skins kernel with kernel auditor . I've tried using
Fastboot flash system "drag and drop system.img" then
Fastboot flash boot "drag and drop skins boot.img"
Then reboot and it goes straight into recovery
The only way I could get data to show up in twrp was formatting data
Click to expand...
Click to collapse
I'm not sure what happened but somewhere along the line a step was missed or something was either flashed wrong or a corrupt download. I would say to stay over boot into recovery and do a factory data rest and start over

Robshr said:
Boot into fastboot and if you already have skin's kernel flashed try just flashing the system image and make sure you wipe the caches Dalvic/cache
Questions- did you flash su or did you use a prerooted image. I think su needs to be installed to do a back up
Click to expand...
Click to collapse
Robshr said:
I'm not sure what happened but somewhere along the line a step was missed or something was either flashed wrong or a corrupt download. I would say to stay over boot into recovery and do a factory data rest and start over
Click to expand...
Click to collapse
Gonna try download stock images and flash those to see if I can e en get this thing to boot, it doesn't even try it goes straight into recovery.

anthonyg45157 said:
Gonna try download stock images and flash those to see if I can e en get this thing to boot, it doesn't even try it goes straight into recovery.
Click to expand...
Click to collapse
That's strange because I just had to reset my watch back to stock and prerooted with my above post and everything went fine
Please keep me updated so if I have to I can make any necessary changes or help in anyway

Robshr said:
That's strange because I just had to reset my watch back to stock and prerooted with my above post and everything went fine
Please keep me updated so if I have to I can make any necessary changes or help in anyway
Click to expand...
Click to collapse
Was looking over the steps again from OP and it looks like step 10 is missing? Maybe that's something, I'm starting from the beginning
---------- Post added at 07:54 PM ---------- Previous post was at 07:16 PM ----------
Starting to lose hope, I've even tried erasing all data, booting into fastboot
Fastboot flash system (stock system.img)
Fastboot flash boot (stock kernel boot.img)
Whenever I reboot it goes straight into recovery , I've never even saw the android screen

anthonyg45157 said:
Was looking over the steps again from OP and it looks like step 10 is missing? Maybe that's something, I'm starting from the beginning
---------- Post added at 07:54 PM ---------- Previous post was at 07:16 PM ----------
Starting to lose hope, I've even tried erasing all data, booting into fastboot
Fastboot flash system (stock system.img)
Fastboot flash boot (stock kernel boot.img)
Whenever I reboot it goes straight into recovery , I've never even saw the android screen
Click to expand...
Click to collapse
The missing step ten was just a mistake
Fastboot flash only the stock recovery then try to boot into recovery and you should see an upside down android just swipe across the screen to get into stock recovery then fastboot stock image and follow the instruction to root again
Please message me with any other problems as to no clog up the thread
As I will post our findings later

Figured everything out for anyone following this thread. I ended up starting over after formatting data. I flashed everything stock, flashed modified system image and skin1980 boot image then booted rom, went back andf flashed twrp again and everything is working as expected. Not really sure what caused the issue,
Thanks to @Robshr for all of his help

I installed a different file manager on the watch just like you installed the kernel auditor. this file manager gives the message "sdcard inaccessible" when I try to open the sdcard. Do you think that this is doing this because it was installed in the tmp folder? Do you recommend paying for the paid app and I should have access to the sdcard?
Also I was unable to pull the backup from the watch, some error stating some file was not created because it wasn't found?
any ideas?

cubandanger05 said:
I installed a different file manager on the watch just like you installed the kernel auditor. this file manager gives the message "sdcard inaccessible" when I try to open the sdcard. Do you think that this is doing this because it was installed in the tmp folder? Do you recommend paying for the paid app and I should have access to the sdcard?
Also I was unable to pull the backup from the watch, some error stating some file was not created because it wasn't found?
any ideas?
Click to expand...
Click to collapse
As far as the file manager it depends on what one you are using does it state the the free version can't access the sdcard otherwise it should be able to read it
Not sure about the error message you're getting without seeing it
But it sounds like you didn't first copy the image to the sdcard and that's why it can't find it or didn't give it sufficient time to copy before you gave the pull command

Soft bricked phone? Can't install recovery and can't install a rom

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.