Related
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 XDA ,
I have only been here for a couple of weeks (2-3 weeks ) and I must say, this place has a fantastic community. Everyone is always very nice and respectful. :highfive:
However, I have looked through this place and sometimes, some guides may be outdated (new ROMs, recovery, HBOOTs etc.) so I want to create this thread and hopefully maintain it to my best abilities. I will try and come back here at least once everyday to help anyone
DISCLAIMER: IF YOU SCREW UP YOUR PHONE IN ANYWAY FOLLOWING THIS GUIDE I AM NOT TO BE HELD RESPONSIBLE!!! Please understand this!!!
CREDITS: I take absolutely no credit for anything that I write here. I took it from other people's threads and from here, here, and here.
Your phone should be HBOOT 2.02.0002 or HBOOT 2.03.0000 with official ICS 4.0.4 with HTC Sense 3.6.
This method will also work if you have Gingerbread but you may still have HBOOT that is not 1.13.0000
Throughout this guide I will give u (hopefully) working links that will give you everything you need, Backup your data, Unlock your bootloader, Flashrecovery, Install Superuser, Backup Stock ROM, Downgrade your HBOOT, Use revolutionary to gain S-OFF, flash custom ROM, and (optional) install Blackrose 2.03.0000.
Just a few suggestions and little information here:
Be aware that this could take quite a bit of time and everything might not go through as planned. If it does not go as planned, then try googling it, search XDA for an answer, or ask people on XDA. Everyone on XDA is very nice and is always willing to help (as long as it coems within forum rules).
Secondly, I suggest u remove your SIM card from the phone so you will not be receiving any phone calls or messages or whatnot that could possibly mess the process up (optional. I did it just in case).
Thirdly, make sure to have a full battery charge even though you will have your phone connected to the computer from time to time.
1. Download and Set Everything up
On your C: drive, create an "android" folder. I will be referring to this throughout the guide.
This next part is really optional but it will help you be more tidy and orderly.
In C:/android create a "Blackrose" folder
In C:/android create a "Revolutionary" folder
In C:/android create a "Downgrade" folder
In C:/android/Downgrade, create a "Downgradekit" folder and an "RUU" folder.
Get HTC Sync here
Get IncS_MVDTKv3.4.1.zip and the RUU here. For the RUU, download the Typical IncS one unless you are with Sasktel or Bell in Canada or a South American user.
Get ClockworkMod Recovery here. Scroll to HTC Incredible S. At time of writing, the latest version was 5.0.2.0.
***You are also more than welcome to try ClockworkMod Recovery v6.0.2.7 If you would like the link, here it is. However this is not an official release but remains pretty much bugless. You may also choose to flash 4ext (touch) recovery, though you better read up on how to flash it cause it is slightly different (although more automated and simple). I will NOT help you if you choose to flash 4ext (cause if you screw it up, then you better stop right there... This is not joke, thats how simple it is)
Get SuperUser here here
Get CyanogenMod ROM here
Get Blackrose here
Install HTC Sync, then uninstall it. We only need the drivers so the actual application is uneeded. (In the control panel, make sure you only select the one with the icon!)
Extract the files from the IncS_MVDTKv3.4.1.zip into the C:/android/Downgrade/Downgradekit. In the downgradekit folder, you should now have the "runme.cmd" and the "files" folder
Put the clockworkmod recovery on the root of C:/android (no folders or anything)
Put Superuser-3.1.3-arm-signed.zip on the root of your SD card on the Incredible S. DO NOT EXTRACT ANY FILES
Put CyanogenMod ROM on the root of your SD card. DO NOT EXTRACT ANY FILES
Take note of your devices serial number. It is either under the phone's battery or in the settings>About Phone. I forget the exact location of the serial number in the About Phone section of the settings but it should not take too long to find it. It started off with "HT......."
Enable USB Debugging on your phone. On Gingerbread this can be found under Settings>Applications> Enable Unknown Sources> Development and check USB Debugging. On ICS 4.0.4, it is found under Settings>Developer Options>Check Android Debugging
2. Backup your data
This step is completely optional and I will not post any apps whatsoever here. Google Play Store will help you here. I did not back up any thing on my phone (I do not have anything important so I did not really care).
3. Unlock Bootloader
Go to htcdev.com/bootloader. Create a free account and unlock the Bootloader. The steps are very simple and you should not run into any trouble. At some point during this process, you will receive confirmation on your phone that will ask you If you want to Unlock your Bootloader. Click Volume up and Power (these are hardware buttons on the side and top, just in case) to click yes.
Note: they tell you to download some thing like Android SDK. Put it all in your C:/android folder
Congrats. You just unlocked your bootloader.
4. Flash a recovery
Switch off your phone and go into bootloader. You will now see, highlighted in pink, UNLOCKED. Tog et into the bootloader, power down, then hold Volume Down and press Power button at the same time.
Plug your phone to the computer via USB cable, highlight fasboot and press power button to confirm. On your PC go to C:/android. Press Shift and right click. Press "Open Command Window here"
then type "fastboot devices". Your devices serial number should show up.
Then type in fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img (assuming you did not change the name of the recovery image. If you did change it, type what you changed it too and do not forget the .img at the end
After a few seconds, the recovery should have been flashed to your phone.
5. Install Superuser and Test Root Access
From the fastboot menu, click volume down and press power button. This should bring you back to the bootloader screen.
Press volume down once to highlight RECOVERY and press power button. The HTC Splash screen should come up for a few seconds, the you will see the ClockworkMod interface. To navigate through this, use the volume up and down buttons to scroll and press the power button to confirm something.
Select "Install zip from sdcard"
Select "Choose zip from sdcard"
Select the Superuser-3.1.3-arm-signed.zip (this should be on the root of your sd card)
Select yes in the field of no's (lool i know XD)
Once it is done installing, reboot your phone. In the app drawer, you will notice that a new app called Superuser or SuperSU has showed up.
You should have root access but lets just be sure anyways. Go to C:/android and Shift, right click to Open Command Window here.
Type in adb.exe shell and press enter
You should get $ meaning adb has connected to your phone.
Next, type in su. If you obtain #, this means you have root access. Hooray
EXTREMELY IMPORTANT IF YOU ARE PLANNING TO STOP GUIDE HERE. LIKE REALLY IMPORTANT!!!!!!!!!!!!!!!!!!!!!!!
At this point you will be able to flash most ROMs. The exceptions are the one that require S-OFF (the ROM requirements in the thread will state so). Also you will have to flash the boot.img manually
To do this download your select ROM. Extract the boot.img to where you have the fastboot.exe, adb.exe, and AdbWinApi.dll (you should have gotten these 3 files when you unlocked the bootloader). Then open the command window (shift, right click, open command window here) and type:
fastboot flash boot boot.img
the boot.img can be renamed to whatever you would like. I keep all my boot images and the fastboot.exe, adb.exe, and AdbWinApi.dll in 1 folder because i download a lot of ROMs. If you do rename the boot.img, i suggest renaming it to the name of the ROM its for. When you type in the fastboot command, just remember to put the .img at the end. This is necessary or it will not work.
If you want to gain S-OFF continue through the guide.
6. Backup Stock Rom
(optional but highly advised just in case something does not work right, then you have something to fall back on)
Go back to ClockworkMod Recovery (reboot into bootloader>select recovery)
Scroll to Backup and Restore
Then press Backup.
7. Run Nonverbose's script
***IF YOU HAVE HBOOT 1.13.0000 THEN YOU DO NOT DO THIS STEP***
Plug your phone into PC if it is not already. Select Charge Only, enable USB Debugging, and make sure fastboot is OFF (Settings>Power)
In C:/android/downgrade/downgradekit, launch runme.cmd
This part should be relatively simple. Just answer the questions honestly, and the script will do its stuff. If i recall correctly, the first question was are you running official ICS unlocked bootloader. I typed n.
Are you rooted?-n
Do you want to create a goldcard?- answer "y" or else you will get a customer ID error (which I believe is either Error 130 or Error 131) while running the downgrade RUU
Are you running HTC bootloader unlocked (or something similar to that)?-y (unless your version main comes out as something other than 2.00000000... in which case, type "n")
Note: Use this second method ONLY if the script did not work.
This script has worked for a lot of people, but it did not seem to work for me. So i typed in the command prompt
Navigate to the downgradekit folder or alternatively, shift right click within the folder to opwen command window here
adb push misc_version /data/local/tmp <------ copies the file to the device
adb.exe shell <------ you will get $ prompt
su <------ gain root access
chmod 777 /data/local/tmp/misc_version <------ changing permissions of the file to execute
/data/local/tmp/misc_version -s 1.00.000.0 <------ you are faking the device to run the RUU installler to "upgrade" to Gingerbread
reboot bootloader <------ self-explanatory
In the bootloader>fastboot, check to see if the misc_version worked, type:
fastboot getvar version-main
If it returns
version-main: 1.00.000.01
then you are good to go
8. Run the RUU
***IF YOU HAVE HBOOT 1.13.0000 THEN YOU DO NOT DO THIS STEP***
After you run Nonverbose's script, reboot into the bootloader>fastboot and launch the RUU file from the C:/android/Downgrade/RUU
This process takes about 10 minutes so be patient. At the end of that, reboot to bootloader and the you should read somewhere
HBOOT-1.13.0000
This indicates you successfully downgraded the HBOOT.
9. Use Revolutionary to gain S-OFF
Put phone in normal charge mode, USB debug ON, fastboot off
Go to revolutionary.io
Scroll down to Downloads. Click download from Windows
Fill out the Beta Key form:
Your Operating System- Windows
Your Device- HTC Incredible S
HBOOT version- 1.13.0000
Serial number- Enter your serial number
Click Generate Key. Copy and Paste the Key to notepad or something.
Now I, for some reason could not get Revolutionary to work just by opening the exe file..... Since pictures are worth a thousand words, i have decided to post a Youtube clip which gives you verbal and graphical instructions on how to run Revolutionary.
The clip is right here. It is really simple the way the person describes the process. Just follow exactly how he does it and you will be fine.
If you reboot your phone into bootloader after running revolutionary, you will see **REVOLUTIONARY** where it once said **UNLOCKED**
After you have successfully run Revolutionary, check for root access by repeating step 5. If you get # at the end you are good to go If you do not have root, then re-flash the superuser-3.1.3-arm-signed.zip in ClockworkMod Recovery.
**Please keep in mind that during the revolutionary, it asks you whether you want to flash a recovery. This flashes, (if i remember correctly) version 4.XXXXXX.... of ClockworkMod. You can choose to select yes to this, but i would suggest saying "no" because its an older version. After you successfully run revolutionary, reboot into bootloader>fastboot and do step 4 again where you flash CWM 5.0.2.0. **
At step 5, i mentioned the command line fastboot flash boot boot.img. This is now unnecessary if you gain S-OFF. Now you can flash any ROM you want on the go.
10. Flash a Custom ROM
Here is a nice index of ROMs, Kernels, Radios etc. This is updated once a month by the OP and has everything you need to get started.
I did request that you download CyanogenMod 7.2 so let's just use that for now.
Go back to ClockworkMod Recovery and make another backup. Keep in mind that this should be done everytime you decide to flash a new ROM to your phone.
Once you are done, go back and select Wipe data/factory reset, Wipe Cache Partition, and under advanced, wipe dalvik cache.
Go back to main recovery menu, select Install Zip from sd card.
Choose the CM7 zip (cm-7.2.0-vivo.zip if you did not rename it to something else)
Wait for it to be installed to your phone. When it is finished, reboot your phone and voila! You are running your first ROM.
11. Install Blackrose 2.03.0000
This eleventh step is optional as most ROMs do not require Blackrose HBOOT. However, if you have blackrose HBOOT and you flash a ROM that has just S-OFF as a requirement, nothing should go wrong. The ROM should still work perfectly fine.
To install BlackRose 2.03.0000
Plug your phone, charge only, USB debug on
In your C:/android/blackrose, run BlackRose_IS.exe
If it tells you, you need HTC Sync, just reinstall it, not that hard.
After that, wait for it the Blackrose.exe to finish executing
If everything ran correctly, turn off your phone, then back in bootloader mode.
Where it said **REVOLUTIONARY**, it should now say **BLACKROSE** Your HBOOT will also change from 1.13.0000 to HBOOT-2.03.0000
Some people have stated that they get stuck on the HTC splash screen. If so, just reinstall CyanogenMod 7 ROM like you did in step 10 and reboot.
After this you should now have BlackRose HBOOT, S-OFF, and a CM7 ROM flashed to your phone. Congratulations!!!
***Do not ask why Blackrose is not running unless you are sure you are running a rooted ROM (just use CM7, like cmon, its known to work so just use it to have less headaches)
Hey guys. Heres a great edition to this guide that can supplement or pretty much replace this section of Blackrose installation. This guide was made Sandeep_Jagtap. Give thanks to him :good:
If you would like to try a different ROM go to the index and select a ROM.
Happy Hunting
Note: Never compare ROMs. That means no: which ROM is best for this or that or what ROM is smoothest or anything like that.
You don't compare ROMs because:
1. Developers spend a lot of time making their respective ROMs.
2. Its disrespectful and rude to the developers.
3. XDA is not a competition ground for who can make the best ROM. Its here to give us the ability to discuss how we do so and so or whatever, just not comparing things with another.
In essence, the only comments going up about ROMs should be "Great ROM but I had so and so problem" (assuming so and so problem existed of course)
Appreciate the contribution, but you should have posted this in the General section. This is not a Development topic and should not have been posted here.
super
super super super !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
thanks ................................ Спасибо все отлично
072665995 said:
Hey XDA ,
I have only been here for a couple of weeks (2-3 weeks ) and I must say, this place has a fantastic community. Everyone is always very nice and respectful. :highfive:
However, I have looked through this place and sometimes, some guides may be outdated (new ROMs, recovery, HBOOTs etc.) so I want to create this thread and hopefully maintain it to my best abilities. I will try and come back here at least once everyday to help anyone
DISCLAIMER: IF YOU SCREW UP YOUR PHONE IN ANYWAY FOLLOWING THIS GUIDE I AM NOT TO BE HELD RESPONSIBLE!!! Please understand this!!!
CREDITS: I take absolutely no credit for anything that I write here. I took it from other people's threads and from here, here, and here.
Your phone should be HBOOT 2.02.0002 or HBOOT 2.03.0000 with official ICS 4.0.4 with HTC Sense 3.6.
This method will also work if you have Gingerbread but you may still have HBOOT that is not 1.13.0000
Throughout this guide I will give u (hopefully) working links that will give you everything you need, Backup your data, Unlock your bootloader, Flashrecovery, Install Superuser, Backup Stock ROM, Downgrade your HBOOT, Use revolutionary to gain S-OFF, flash custom ROM, and (optional) install Blackrose 2.03.0000.
Just a few suggestions and little information here:
Be aware that this could take quite a bit of time and everything might not go through as planned. If it does not go as planned, then try googling it, search XDA for an answer, or ask people on XDA. Everyone on XDA is very nice and is always willing to help (as long as it coems within forum rules).
Secondly, I suggest u remove your SIM card from the phone so you will not be receiving any phone calls or messages or whatnot that could possibly mess the process up (optional. I did it just in case).
Thirdly, make sure to have a full battery charge even though you will have your phone connected to the computer from time to time.
1. Download and Set Everything up
On your C: drive, create an "android" folder. I will be referring to this throughout the guide.
This next part is really optional but it will help you be more tidy and orderly.
In C:/android create a "Blackrose" folder
In C:/android create a "Revolutionary" folder
In C:/android create a "Downgrade" folder
In C:/android/Downgrade, create a "Downgradekit" folder and an "RUU" folder.
Get HTC Sync here
Get IncS_MVDTKv3.4.1.zip and the RUU here. For the RUU, download the Typical IncS one unless you are with Sasktel or Bell in Canada or a South American user.
Get ClockworkMod Recovery here. Scroll to HTC Incredible S. At time of writing, the latest version was 5.0.2.0.
Get SuperUser here here
Get CyanogenMod ROM here
Get Blackrose here
Install HTC Sync, then uninstall it. We only need the drivers so the actual application is uneeded. (In the control panel, make sure you only select the one with the icon!)
Extract the files from the IncS_MVDTKv3.4.1.zip into the C:/android/Downgrade/Downgradekit. In the downgradekit folder, you should now have the "runme.cmd" and the "files" folder
Put the clockworkmod recovery on the root of C:/android (no folders or anything)
Put Superuser-3.1.3-arm-signed.zip on the root of your SD card on the Incredible S. DO NOT EXTRACT ANY FILES
Put CyanogenMod ROM on the root of your SD card. DO NOT EXTRACT ANY FILES
Take note of your devices serial number. It is either under the phone's battery or in the settings>About Phone. I forget the exact location of the serial number in the About Phone section of the settings but it should not take too long to find it. It started off with "HT......."
Enable USB Debugging on your phone. On Gingerbread this can be found under Settings>Applications> Enable Unknown Sources> Development and check USB Debugging. On ICS 4.0.4, it is found under Settings>Developer Options>Check Android Debugging
2. Backup your data
This step is completely optional and I will not post any apps whatsoever here. Google Play Store will help you here. I did not back up any thing on my phone (I do not have anything important so I did not really care).
3. Unlock Bootloader
Go to htcdev.com/bootloader. Create a free account and unlock the Bootloader. The steps are very simple and you should not run into any trouble. At some point during this process, you will receive confirmation on your phone that will ask you If you want to Unlock your Bootloader. Click Volume up and Power (these are hardware buttons on the side and top, just in case) to click yes.
Note: they tell you to download some thing like Android SDK. Put it all in your C:/android folder
Congrats. You just unlocked your bootloader.
4. Flash a recovery
Switch off your phone and go into bootloader. You will now see, highlighted in pink, UNLOCKED. Tog et into the bootloader, power down, then hold Volume Down and press Power button at the same time.
Plug your phone to the computer via USB cable, highlight fasboot and press power button to confirm. On your PC go to C:/android. Press Shift and right click. Press "Open Command Window here"
then type "fastboot devices". Your devices serial number should show up.
Then type in fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img (assuming you did not change the name of the recovery image. If you did change it, type what you changed it too and do not forget the .img at the end
After a few seconds, the recovery should have been flashed to your phone.
5. Install Superuser and Test Root Access
From the fastboot menu, click volume down and press power button. This should bring you back to the bootloader screen.
Press volume down once to highlight RECOVERY and press power button. The HTC Splash screen should come up for a few seconds, the you will see the ClockworkMod interface. To navigate through this, use the volume up and down buttons to scroll and press the power button to confirm something.
Select "Install zip from sdcard"
Select "Choose zip from sdcard"
Select the Superuser-3.1.3-arm-signed.zip (this should be on the root of your sd card)
Select yes in the field of no's (lool i know XD)
Once it is done installing, reboot your phone. In the app drawer, you will notice that a new app called Superuser or SuperSU has showed up.
You should have root access but lets just be sure anyways. Go to C:/android and Shift, right click to Open Command Window here.
Type in adb.exe shell and press enter
You should get $ meaning adb has connected to your phone.
Next, type in su. If you obtain #, this means you have root access. Hooray
At this point you will be able to flash most ROMs. The exceptions are the one that require S-OFF (the ROM requirements in the thread will state so). Also you will have to flash the boot.img manually
To do this download your select ROM. Extract the boot.img to where you have the fastboot.exe, adb.exe, and AdbWinApi.dll (you should have gotten these 3 files when you unlocked the bootloader). Then open the command window (shift, right click, open command window here) and type:
fastboot flash boot boot.img
the boot.img can be renamed to whatever you would like. I keep all my boot images and the fastboot.exe, adb.exe, and AdbWinApi.dll in 1 folder because i download a lot of ROMs. If you do rename the boot.img, i suggest renaming it to the name of the ROM its for. When you type in the fastboot command, just remember to put the .img at the end. This is necessary or it will not work.
If you want to gain S-OFF continue through the guide.
6. Backup Stock Rom (optional but highly advised jsut in case something does not work right and you have something to fall back on)
Go back to Clockworkmod Recovery (reboot into bootloader>select recovery)
Scroll to Backup and Restore
Then press Backup.
7. Run Nonverbose's script
***IF YOU HAVE HBOOT 1.13.0000 THEN YOU DO NOT DO THIS STEP***
Plug your phone into PC if it is not already. Select Charge Only, enable USB Debugging, and make sure fastboot is OFF (Settings>Power)
In C:/android/downgrade/downgradekit, launch runme.cmd
This part should be relatively simple. Just answer the questions honestly, and the script will do its stuff. If i recall correctly, the first question was are you running official ICS unlocked bootloader. I typed n.
Are you rooted?-n
Do you want to create a goldcard?- optional though i would suggest it
Are you running HTC bootloader unlocked (or something similar to that)?-y (unless your version main comes out as something other than 2.00000000... in which case, type "n")
This script has worked for a lot of people, but it did not seem to work for me. So i typed in the command prompt
Navigate to the downgradekit folder or alternatively, shift right click within the folder to opwen command window here
adb push misc_version /data/local/tmp <------ copies the file to the device
adb.exe shell <------ you will get $ prompt
su <------ gain root access
chmod 777 /data/local/tmp/misc_version <------ changing permissions of the file to execute
/data/local/tmp/misc_version -s 1.00.000.0 <------ you are faking the device to run the RUU installler to "upgrade" to Gingerbread
reboot bootloader <------ self-explanatory
In the bootloader>fastboot, check to see if the misc_version worked, type:
fastboot getvar version-main
If it returns
version-main: 1.00.000.01
then you are good to go
Note: Use the second method ONLY if the script did not work.
8. Run the RUU
***IF YOU HAVE HBOOT 1.13.0000 THEN YOU DO NOT DO THIS STEP***
After you run Nonverbose's script, launch the RUU file from the C:/android/Downgrade/RUU
This process takes about 10 minutes so be patient. At the end of that, reboot to bootloader and the you should read somewhere
HBOOT-1.13.0000
This indicates you successfully downgraded the HBOOT.
9. Use Revolutionary to gain S-OFF
Put phone in normal charge mode, USB debug ON, fastboot off
Go to reviolutionary.io
Scroll down to Downloads. Click download from Windows
Fill out the Beta Key form:
Your Operating System- Windows
Your Device- HTC Incredible S
HBOOT version- 1.13.0000
Serial number- Enter your serial number
Click Generate Key. Copy and Paste the Key to notepad or something.
Now I, for some reason could not get Revolutionary to work just by opening the exe file..... Since pictures are worth a thousand words, i have decided to post a Youtube clip which gives you verbal and graphical instructions on how to run Revolutionary.
The clip is right here. It is really simple the way the person describes the process. Just follow exactly how he does it and you will be fine.
If you reboot your phone into bootloader after running revolutionary, you will see **REVOLUTIONARY** where it once said **UNLOCKED**
After you have successfully run Revolutionary, check for root access by repeating step 5. If you get # at the end you are good to go
At step 5, i mentioned the command line fastboot flash boot boot.img. This is now unnecessary if you gain S-OFF. Now you can flash any ROM you want on the go.
10. Flash a Custom ROM
Here is a nice index of ROMs, Kernels, Radios etc. This is updated once a month by the OP and has everything you need to get started.
I did request that you download CyanogenMod 7.2 so let's just use that for now.
Go back to ClockworkMod Recovery and make another backup. Keep in mind that this should be done everytime you decide to flash a new ROM to your phone.
Once you are done, go back and select Wipe data/factory reset, Wipe Cache Partition, and under advanced, wipe dalvik cache.
Go back to main recovery menu, select Install Zip from sd card.
Choose the CM7 zip (cm-7.2.0-vivo.zip if you did not rename it to something else)
Wait for it to be installed to your phone. When it is finished, reboot your phone and voila! You are running your first ROM.
11. Install Blackrose 2.03.0000
This eleventh step is optional as most ROMs do not require Blackrose HBOOT. However, if you have blackrose HBOOT and you flash a ROM that has just S-OFF as a requirement, nothing should go wrong. The ROM should still work perfectly fine.
To install BlackRose 2.03.0000
Plug your phone, charge only, USB debug on
In your C:/android/blackrose, run BlackRose_IS.exe
If it tells you, you need HTC Sync, just reinstall it, not that hard.
After that, wait for it the Blackrose.exe to finish executing
If everything ran correctly, turn off your phone, then back in bootloader mode.
Where it said **REVOLUTIONARY**, it should not say **BLACKROSE** Your HBOOT will also change from 1.13.0000 to HBOOT-2.03.0000
Some people have stated that they get stuck on the HTC splash screen. If so, just reinstall CyanogenMod 7 ROM like you did in step 10 and reboot.
After this you should now have BlackRose HBOOT, S-OFF, and a CM7 ROM flashed to your phone. Congratulations!!!
If you would like to try a different ROM go to the index and select a ROM.
I have personally tried all the Jellybean 4.1.X ROMs, almost all the Ice Cream Sandwich 4.0.X with Sense 4.X Roms, almost all the ROMs from the Ice Cream Sandwich 4.0.X with Sense 3.6/3.5 and Rebased Multilang MIUI4 ROM under MIUI ROM's. I really liked all of them. Great job out there devs :good: :good: :good: :good:
Ones i liked in particular are
From Jellybean 4.1.X: Unofficial CyanogenMod 10 (seems to have the least problems) Android Open Kang Project Release v2 (great customizability though browse through the pages as there are still a number of bugs), and Paranoid Android v1.9.7 (again great number of features here)
From ICS 4.0.X with Sense 4.X: Sabsa Prime v12 (very few bugs as well as a number of different mods that you can add from the installer) and ViperVIVO 1.3.0 (for its great level of customizability clearly evident through the creation of the Venom Hub).
From ICS 4.0.X with Sense 3.6/3.5: Incredible Bliss v1 (its stable, adds a new look, and its really smooth like Project Butter), Android Revolution HD 4.0 (its essentially the same thing as HTC Sense 3.6 except the developper added a lot of hardware speed upgrades and improved its stability) as well as the Second Sun V2.5 (all that's got to be said is that its a great ROM that is similar to Android Revolution HD; improced stock sense 3.6)
These are just my favorites but you really have to try them all out to know which ones you like best Happy Hunting
Please note this is my first guide. If I am missing anything here please inform me and I will correct it. Thank you very much!
Click to expand...
Click to collapse
I tried, but it said thats error [131] Customer ID ERROR in step 8 (run RUU)
My IS Hboot 2.0.2 - S on
I think It might have goldcard?
V77V77 said:
I tried, but it said thats error [131] Customer ID ERROR in step 8 (run RUU)
My IS Hboot 2.0.2 - S on
I think It might have goldcard?
Click to expand...
Click to collapse
Yes you need a goldcard to proceed.
V77V77 said:
I tried, but it said thats error [131] Customer ID ERROR in step 8 (run RUU)
My IS Hboot 2.0.2 - S on
I think It might have goldcard?
Click to expand...
Click to collapse
Yes you do need a goldcard. Did you select yes when nonverbose's script asked you do you want a goldcard? If you pressed no, then I would suggest you rerun the script and press "y" when it asks you.
Starting Now
Im Trying now, wish me luck! :good:
072665995 said:
Yes you do need a goldcard. Did you select yes when nonverbose's script asked you do you want a goldcard? If you pressed no, then I would suggest you rerun the script and press "y" when it asks you.
Click to expand...
Click to collapse
Thank you very much.
I have done jet.:victory:
Ah, when i run nonverbose's script, make the gold card, the script run very fast.So where did the goldcard save?How can i backup it?
V77V77 said:
Thank you very much.
I have done jet.:victory:
Ah, when i run nonverbose's script, make the gold card, the script run very fast.So where did the goldcard save?How can i backup it?
Click to expand...
Click to collapse
The script turned your SD card into a goldcard. It wrote a special signature to the SD Card. You can continue to use it as a normal SD card.
tpbklake said:
The script turned your SD card into a goldcard. It wrote a special signature to the SD Card. You can continue to use it as a normal SD card.
Click to expand...
Click to collapse
Ahh tpbklake, u always beat me to it but its always great that everyone's always willing to help those who need it
Hi there,
I am following the guide but somehow i don't know why the computer cannot detect the devices during the fastboot mode. But the device can be found if it is booted into the android OS. I am using a mac and thus using a VM with Windows XP. I don't know if it may cause the issue.
When I was trying to type "fastboot devices", it actually doesn't work in XP (connected to Xp). But it's able to work in Mac where I type "fastboot-mac devices" (connected to mac). Thus I can go thru the step 4.
Now I am stuck at Step 7 where the script boot the device into the fastboot mode.
Could anyone help?
chpchai said:
Hi there,
I am following the guide but somehow i don't know why the computer cannot detect the devices during the fastboot mode. But the device can be found if it is booted into the android OS. I am using a mac and thus using a VM with Windows XP. I don't know if it may cause the issue.
When I was trying to type "fastboot devices", it actually doesn't work in XP (connected to Xp). But it's able to work in Mac where I type "fastboot-mac devices" (connected to mac). Thus I can go thru the step 4.
Now I am stuck at Step 7 where the script boot the device into the fastboot mode.
Could anyone help?
Click to expand...
Click to collapse
Go to fastboot menu in bootloader. Does it say fastboot usb. If it does not, then there might be something wrong with your phone miniHDMI port, the computers USB port, or the cable. If it does then i must ask, in command prompt, did u navigate to the location of the adb.exe, fastboot.exe, AdbWinApi.dll (during bootlaoder unlock process, they should have asked for these files)??
072665995 said:
Go to fastboot menu in bootloader. Does it say fastboot usb. If it does not, then there might be something wrong with your phone miniHDMI port, the computers USB port, or the cable. If it does then i must ask, in command prompt, did u navigate to the location of the adb.exe, fastboot.exe, AdbWinApi.dll (during bootlaoder unlock process, they should have asked for these files)??
Click to expand...
Click to collapse
I figured out the issue that it should be related to the driver installation was not successful in fastboot mode. I changed to a Windows 7 notebook then it is fine. And I was able to install the ROM successfully following your instruction. Thanks. :victory:
chpchai said:
I figured out the issue that it should be related to the driver installation was not successful in fastboot mode. I changed to a Windows 7 notebook then it is fine. And I was able to install the ROM successfully following your instruction. Thanks. :victory:
Click to expand...
Click to collapse
Alright. its great to know that you have resolved your problem. Congratulations on obtaining S-OFF :good:
Help on this step.
wong post .... oops
Thanks a lot for this instructions!
It's the first time i'm dealing with this things (got completely pissed of after that ****ty HTC ICS upgrade) and it went all right.
The only two places which were not completely clear to me and you might suppose to put more details:
1. Step 8 RUU should run in bootloader->fastboot
2. After step 9 (revolutionary) Recovery should be flashed again: either answer yes during that script execution or repeat step 4.
andropol said:
Thanks a lot for this instructions!
It's the first time i'm dealing with this things (got completely pissed of after that ****ty HTC ICS upgrade) and it went all right.
The only two places which were not completely clear to me and you might suppose to put more details:
1. Step 8 RUU should run in bootloader->fastboot
2. After step 9 (revolutionary) Recovery should be flashed again: either answer yes during that script execution or repeat step 4.
Click to expand...
Click to collapse
Alright thank you. I will update it.
excuse me guys. my device is rooted and s-on
if i make my device s-off ihave to root it again or not????
shmetal said:
excuse me guys. my device is rooted and s-on
if i make my device s-off ihave to root it again or not????
Click to expand...
Click to collapse
Nope. If you are already rooted, Start from where it says to run Nonverbose's script. This will fake the ID of your device to run the RUU to "upgrade" to HBOOT 1.13.0000. Then run revolutionary.
Thank you and its all going great for a noob here.
Thank you for the detailed process. I've done a Mimmi root and custom kernel and CM-7 mod before and for the Vivo that I got recently this was really useful as all the information was out there.
As far as this process goes, all went well except that when you do the RUU upgrade by fooling the upgrader that your Hboot is 1.00 or something and then it copies all those system files of stock 2.3 to the phone - somehow I lost the recovery and root (which I hassled about for some time and realized I can do the following :
1. Bootloader > Fastboot
2. USB connect
3. cmd.exe
4. fastboot flash recovery recovery-image.img
(ONCE AGAIN after the RUU) and everything seems to have worked like butter thereafter.
ROM's I could install after that:
1. MIUI roms (tried the MAUI WOWIE 2.9) Then tried the MIUI3.2.8 - worked well but little laggy - both work well except some apps wont install - very stable, battery lasted as good as stock, slightly better
2. Cyanogenmod 7.2 (hats off to these guys. worked most awesome but wanted to try so moved on) battery great, no bugs, plain simple fast.
3. Virtuous for - the Quattro. This was amazingly fast but there are bugs that need to be ironed out
here I installed 4EXT recovery and
4. Stock gingerbread with SENSE. - boring
5. Now running JellyTime 4.2.1. Not buggy, smooth, Battery seems to be doing well so far and call sound is okay and till now this one I liked a lot.
NOTE: Offline Dictation - Even after enabling google now and updating all google apps, there is no option do downlod offline speech recognition data in google voice typing settings........ If someone has got this to work I'd be glad to know.
I looked around and everyone seems to be suggesting that there is a check box within the google voice input options dialogue. But all I see is Language (automatic) and Block Offensive Words
Overall, seems like this is a great tutorial for anyone starting on their VIVO. Go Incredible! You've got my Flashing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Setup, Preparation and Prerequisites
Basic tasks that I may refer to throughout this guide:
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
Enter the bootloader - Turn the phone off. Hold volume down + power. The bootloader is also known as fastboot mode.
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long (5-15 minutes), but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Driver Installation - Try this first, but if that doesn't work look here. Still having issues? Give this a try. None of these working? Hopefully this does the trick.
Downloads
Download a custom recovery of your choice and the SuperSU zip below. Place both files (recovery image and root zip) in the platform-tools folder located on your desktop within the android-sdk-windows folder.
Custom Recovery:
TeamWin Recovery Project (TWRP) or ClockworkMod (CWM)
Root:
SuperSU
Information
Rooting a nexus device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in my opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has. Using a toolkit will only make things worse in the long run...learn to do it properly. It has been proven that every time you use a toolkit, god kills a kitten. Save the kittens.
If you are confused by anything in this guide, I would highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also I'd suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understand? Good...lets begin:
1. Unlocking Bootloader
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Plug the phone into your PC, then open a command prompt window window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
On the phone a screen should pop up asking whether or not you would like to unlock the bootloader. Use the volume rockers to highlight "Yes" then press power to confirm the action.
After the above command has finished excuting, run the following (DO NOT skip this step, it is more important than you think):
Code:
fastboot reboot
The phone will reboot. Next you will be presented with a screen containing an android logo and a progress bar (this may take up to ten minutes to complete). Wait until the phone has fully booted up into android, then proceed onto the next section of the guide.
Close the command prompt window.
2. Installing a Custom Recovery
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that you should place the file in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it. After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Close the command prompt window.
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock rom
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. Leave the phone at the home page of the custom recovery.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Instructions for ClockworkMod (CWM):
install zip from sdcard > choose zip from sdcard.
Next, browse to the location where you previously copied the SuperSU zip and select the it.
To confirm the installation, scroll down to "Yes" and select it. The installation shouldn't take very long, and once it has completed you may reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the Nexus 5 Android Development and Nexus 5 Original Android Development section) onto the phone (remember the location where you copy it to)
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. To install a custom rom the general procedure to follow is: factory reset, wipe cache + dalvik cache, flash ROM, flash GApps. Here are the recovery specific instructions:
Instructions for TeamWin Recovery Project (TWRP):
Wipe > Swipe to Factory Reset
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Instructions for ClockworkMod (CWM):
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
install zip from sdcard > choose zip from sdcard > navigate to the location of the rom > select the rom > confirm the installation by selecting "Yes"
After that you may install the GApps using the same method for flashing the rom, and finally reboot the phone.
Keep in mind that the first boot after installing a custom rom & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted...Plus you saved a kitten. Enjoy
Troubleshooting & FAQ
Why am I seeing a red triangle with a dead android when booting into recovery even after I flashed a custom recovery?
What you are seeing is the stock recovery, meaning that the custom recovery that you flashed did not install correctly. Try the following suggestions:
Make sure you are using the USB cable that came with your phone. Only use other ones, if the stock one isn't working
Try using different USB ports. USB 2.0 ports (the ones that ARE NOT blue) are preferable. USB 3.0 ports (the blue ones) may cause problems with connectivity.
If you are on a desktop, use the ports on the back of the tower instead of the ones in the front. These ports are directly connected to the motherboard, rather than the ones in the front which are usually attached to a header cable which then indirectly connects to the motherboard.
My phone wont boot into android. I can only access the bootloader and custom recovery. What do I do?
Suggestion 1: Factory reset via recovery.
TWRP Instructions:
Boot into recovery
Wipe > Swipe to Factory Reset
Reboot
CWM Instructions:
Boot into recovery
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
Reboot
If that doesn't work continue onto Suggestion 2.
Suggestion 2: Push a ROM to your phone and flash it.
Download a ROM onto your computer. If you don't have time to look for a ROM, just download the stock ROM.
Move the downloaded ROM onto your desktop, and rename the file to "ROM.zip" (without the quotation marks)
Boot phone into recovery
Open command prompt and run the following commands:
Code:
cd Desktop
adb push ROM.zip /sdcard/
Wait for it to finish copying the file, then flash the ROM. If you need further details on how to flash a ROM take a look at the OP, section 3. Rooting, Option B)
If that doesn't work continue onto Suggestion 3.
Suggestion 3: Flash the factory images.
Flash the factory images
My phone wont boot into android. I can only access the bootloader. What do I do?
Flash the factory images
My phone exploded. What do I do?
Tape it back together then flash the factory images
Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk
dombera said:
Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
Awesome, thx
Sent from my Nexus 4 using Tapatalk
This is awesome, will come in handy.
Sent from my HTC Desire using XDA Premium 4 mobile app
Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
---------- Post added at 01:43 AM ---------- Previous post was at 01:41 AM ----------
Xero258 said:
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!
Click to expand...
Click to collapse
If you unlock bootloader & root, and modify some system files, OTAs may not be able to pass some pre-install checks, at least this has happened to me on N4 before. I added one line to /etc/build.prop, also one of the older SuperSU versions had to be uninstalled for pre-install OTA checks to pass.
Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
Click to expand...
Click to collapse
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.
I see some Desire folks
Did u order one chromium?
Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.
talz13 said:
Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.
Click to expand...
Click to collapse
If you wipe cache exactly after you unlock the bootloader, without booting, no.
Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
Not yet. Hoping to eventually get it though.
Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful
Click to expand...
Click to collapse
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app
Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
I'm not a really famous desire user but yes I bought it. Did you buy it to? Happy to see some other desire users.
Sent from my HTC Desire using XDA Premium 4 mobile app
Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?
boysetsfire said:
Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?
Click to expand...
Click to collapse
It should work fine, but whats wrong with booting it up for the first time?
Chromium_ said:
It should work fine, but whats wrong with booting it up for the first time?
Click to expand...
Click to collapse
Nothing wrong, just the laziness of not wanting to do the initial setup two times
Chromium_ said:
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app
Click to expand...
Click to collapse
abaaaabbbb63 said:
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.
Click to expand...
Click to collapse
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?
Whyzor said:
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?
Click to expand...
Click to collapse
Yes that is correct, they do not boot. I will update the OP now, sorry for the confusion.
Originally I had read the following threads and it seemed that they were somewhat functioning, but it is now confirmed that neither one boots.
TWRP
CWM
Hi all, I wrote a long-winded Tutorial to put Evervolv KitKat on a stock N1. I don't have a stock N1 (I stumbled all the way through this process and got done yesterday, was so excited I wrote this tutorial) and don't know how to get it back to stock, so I'm wondering if anyone who has one and has experience putting new ROMs on other devices would like to test this out and let me know if anything doesn't work as written. Please go ahead if you like and reply your updates! Once it's dialed I'll make it a thread in the N1 ROMs forum.
Here's the text:
How to put KitKat on a Nexus One (And have computing power & space to spare):
Things you'll need:
1. A Windows/Linux computer with internet connection, USB port, and terminal
2. A USB Cable
3. A Nexus One with the most recent stock gingerbread rom (Settings->about, look for Android 2.3.6 or GRK39F, else apply/google updates to get to that version)
Before you begin, note that you're playing with a generally safe form of fire, but when playing with fire, you may brick your phone. The maker of this guide and any sites you visit during the process assume no responsibility, the user assumes full responsibility for lost work and damaged or ruined phones. Your warranty will be voided about six times over. Save all your stuff somewhere, save apps with Titanium Backup (Google it) or something, and do a full Nandroid backup (Goog that too) before you begin. You will be fully wiping your phone and SD card multiple times. Make sure at every step of the process that your battery is at least half full. Running out of battery during an update can cause bricks. In this guide, “Boot” means standard boot, the way it normally turns on. Not hboot or fastboot or recovery.
I did part of this from a Windows7 computer on Cygwin and part on Ubuntu 12.04, each presented some annoyance but by far the greatest was due to my Linux ineptitude with PATH and Root. If you're trying the same, I've made an appendix for that.
It may help to have a brief conceptual overview of what you'll be doing in case you run into snags and have to step out of the walkthrough. Your N1 has a few basic parts: Internal memory that is chopped into 3 partitions: One for the system files (System) , one for the files that they will need to make during the first bootup and use in order to operate, along with your apps and their created files (Data) and one for temporary files that your OS and apps can regenerate (Cache). Somewhere in there it also has space for a Radio (that also includes some critical power functions, flashing a new radio is the easiest way to brick an N1 but we won't), as well as a Recovery partition and an Hboot&Fastboot partition. We will be messing with Recovery and Hboot. The virtual machine that turns all the friendly pseudo-english computer code into 1s and 0s for the processor to deal with is called Dalvik, named after a town in Iceland where some old dev's family is from. It has its own Cache (the VM, not the town, as there are no longer any fish in Iceland ). It's SOP to wipe Cache & Dalvik before and after applying any updates, and wipe Data (Factory reset) before applying most updates. Sometimes when my phone bogs I reboot to recovery and wipe caches just for funsies. This makes it take longer to boot the phone and to use each app just the first time after that, while the files are created fresh. The phone also should have an SD-Card. You should have or buy an 8+MB, Class 10 SD card. The class relates to read/write speed, anything less than 10 will noticeably slow your Nexus One's operation. Why?
Because we're going to put some of your operating system on the SD card. We're going to use a special recovery system (aka recovery ROM) called “4ext” to partition your SD card. Mine is 16GB, partitioned to 14GB for storage and 2GB to use as fake internal memory, where my system's Data and Cache live. The KitKat System files that normally live on internal memory's System partition are too big for a normal N1, so we'll use a special Hboot called BlackRose to repartition your internal memory so you can fit KitKat, and then after you first boot it up we'll use an app called Mounts2SD to install a startup script so that every other time you boot it up after that, it will know to find Data and Cache on the SD card. In order to install BlackRose, you'll need to be running CyanogenMod Rom as your main OS, and in order to do that you'll need ClockWorkMod Recovery ROM. So the installation order will be: ClockworkMod recovery->Cyanogen7OS (Gingerbread based)->4ext recovery to partition SD card->BlackRoseHboot to repartition internal memory->Evervolv KitKat-based N1 ROM-> run Mounts2sd for startup scripts ->reboot to your new life among the anatomically modern cyborgs (and then you're on your own for getting all your apps and music and contacts and stuff back on the phone from wherever you saved it).
Ready? Here we go!
1. Install the Android SDK on your computer.
1. Get the appropriate version here: http://developer.android.com/sdk/index.html
2. Unzip it.
3. Run the setup.exe (if using windows)
4. When asked which packages to install, choose “Android SDK Tools”, “SDK Platform Android 2.1″, and “Usb Driver package” (If you use eclipse, check that last link for instructions on using the ADT plugin (Not the same ADT that cuts your paycheck, much less inept))
5. Make sure the USB drivers installed properly (windows).
1. Go to printers and devices in the control panel, or device manager
2. If you see an android device with no warnings, you're golden. If it has warnings, right click it and go properties->update driver (driver can be found in your android sdk directory where you unzipped the sdk bundle, in \usb_driver).
6. Boot up your N1 and plug it in to the computer. If the computer recognizes it and they play nice, you're set with the sdk. To extra check, open terminal and cd to the sdk's platform-tools folder that should contain the adb utility. Type #adb devices and see if it comes up with a message telling you that it's running a daemon on a port like 5037, and then lists something like HT9CPP800063 device. This is your phone, it's telling you you're beyond connected. You've got the sdk working. Else have your friend Google help you get the SDK properly installed.
2. Root the phone so it will let you dig in.
1. Put your N1 in USB debugging mode (Settings > Applications > Development > USB Debugging)
2. In the terminal, in the platform-tools folder, type #adb reboot bootloader. (((My phone has a power hardware issue and will not reboot while plugged in ever to any mode ever at all ever, if yours does too you can unplug (first type #adb kill-server to make it ok to unplug) the usb cable, power down, wait five seconds, and hold the trackball and power button to power back up into the bootloader, then plug in again. There was a lot of unplugging, waiting fifteen seconds, booting while holding buttons, plugging in, adb devices -ing that I will omit henceforth due to low likelihood that you have the same problem.)))
3. Using the onscreen directions on the phone and the hard buttons, navigate to fastboot mode. It may be unresponsive and throw some not-found messages for five seconds before it lets you do anything.
4. In the terminal on your computer, in the platform-tools folder, type #fastboot devices to see if your devices is connected (it should come up with the same HT#XXX###### number).
5. This step will gain Root access, unlock the bootloader, and WIPE ALL YOUR ****. Now type #fastboot oem-unlock . You may have to accept the warranty voiding. If for whatever reason it doesn't work, use this method http://code.google.com/p/bexboot/, and unzip the files to the platform-tools folder.
6. Using the phone buttons, reboot. Your little lock logo during the bootup should be unlocked now.
7. Power down and boot again for good measure. Re-enable usb debugging in the phone app dev settings.
3. Get ClockworkMod Recovery.
1. Download koush's ClockworkMod Recovery from : recovery-clockwork-5.0.2.0-passion.img and put it in the platform-tools folder.
2. To make sure the file is not corrupted and will not brick your goods, check the md5sum. This is the result of a complicated equation that easily reveals even a single flipped bit in the file by vastly changing the output. Google how to do this, in windows you'll need to download a tool like winmd5free. The output for this particular file should be: md5: 45716c8d51ed2375873f01f0b14b2184 If it's anything else don't use it.
3. Reboot to the bootloader again, either by #adb reboot bootloader or by powering up while holding the trackball, and navigate to fastboot.
4. Verify that you're connected with #fastboot devices
5. Flash ClockworkMod Recovery by typing #fastboot flash recovery recovery-clockwork-5.0.2.0-passion.img
6. It should give a success message. Reboot to recovery from the fastboot menu. It should be a sweet new blue and white ClockWorkMod recovery. Power down and reboot to recovery by holding volume up as you power up, just for good measure.
4. Get CyanogenMod7 ROM.
1. On your computer, go to http://download.cyanogenmod.org/?device=passion&type=stable and download the latest stable CM7 zip. Put it in the platform-tools folder.
2. Check its md5 as you did in part 3.
3. Do #adb-devices, which should give you that serial again, and the word recovery.
4. Place the zip file on the root of your SD card by doing #adb push cm-7.2.0-passion.zip /sdcard/
5. If that last step failed, try running #adb shell mount /sdcard or #adb kill-server then #adb devices then #adb shell mount /sdcard, then try the push again. Or mount the sdcard through the recovery menu before running that push command. Or use your computer's file system to drag and drop the .zip to the root (lowest) folder of the sd card.
6. Using the recovery menu, in backup and restore options, backup your current ROM.
7. In the format menu, do a wipe data/factory reset. Wipe the cache and dalvik cache while you're at it.
8. Back in the main recovery menu, do install zip → choose zip from sd card.
9. Select that CM7 zip file.
10. Return to the main menu and reboot the system. It should come up with a totally different looking leaner meaner version of Gingerbread, that gives you more control and speed and saves battery. But even with this system, given modern app sizes, you'll soon run out of room on the internal memory if you stop now. And besides, you're having too much fun.
5. Get 4EXT recovery
1. Go to 4ext.net and download the free .apk file: http://www.4ext.net/get.php?apk Congratulations if you're about to install your first not market app (apps are now .apk, not just something you get from the store's GUI.). Save it in platform-tools. Or, to be really nice to Max, you can just buy the app in the play store and skip the next two steps.
2. Enable USB debugging, plug in and #adb-devices.
3. # adb install 4EXTRecoveryUpdater.apk. You should get back a success message in a fistful of seconds.
4. At this point you may need to back out to regular settings, turn on wifi, and hook up to your wifi router.
5. Open the 4ext recovery updater app. Go to settings. Allow superuser permissions and everything else. It should detect Nexus One, connect to the internet, and boot you back to the main menu.
6. Go to online install. They're all release candidates and no stable versions, so just go with the newest one. Select install.
7. Wait for it to finish and then reboot to recovery, either by # adb reboot recovery or manually. You should have a beautiful new touchscreen recovery.
6. Partition your SD Card
1. In recovery, go to tools->partition sd card->remove all partitions and start from scratch.
2. For the first Ext partition, where you'll be keeping a good chunk of your OS, The consensus online is not to go above either 1.5GB or 2GB. I'm working fine with 2GB aka 2048MB.
3. You can skip the 2nd Ext partition.
4. The internet says Swap size should be 0.
5. Internet says File system should be ext4. This should do the partitioning, the rest of your SD card will still be great for storage as before.
7. Repartition internal memory using BlackRose:
1. I have never used BlackRose on Windows, but here goes: go here : http://forum.xda-developers.com/showthread.php?t=1270589 and download this zip archive: http://forum.xda-developers.com/attachment.php?attachmentid=1016437&d=1334971685; It has windows and linux files. The site also has a manual in case this walkthrough lets you down.
2. Unzip it into a folder in your platform-tools. Execute it with a ./ in linux or a .exe in win. It should say waiting for devices.
3. Reboot your phone manually. BlackRose should hijack the startup, install itself, and quit. Boot your phone up again.
4. Blackrose is rumored to have an interactive guide to partitioning, but it didn't work for me and at least some other genius on the internet, but being an industrious Austrian, he figured out the fix: Run Blackrose in Editor mode. Type resize as prompted.
5. The post here http://forum.xda-developers.com/showthread.php?t=2540366 on Evervolv KitKat implies that 250MB for System works with enough space for Gapps (Google does not allow their standard apps like Play Store to be included with Mod roms anymore, so you will need to install them from recovery too, but they distribute them bundled so it's not hard.), and some commenter said 260MB, but that didn't work for me long enough to run startup scripts and move some of it off. So I had to redo it and I went with 265MB for System and 10MB for Cache, which is working fine. Give it a name, I went with Kat.
6. BlackRose will shut down, but it will leave a golden turd in the form of a file called hboot_brcust.nb0 probably in the folder called “other.” That's what you want.
7. Put that file in the same folder as the Blackrose utilities fastboot-l and fastboot-w if it's not already there. Then boot your phone into fastboot again, via adb or manually. I think. Maybe try this from being standard booted up if the next part doesn't work.
8. Run # fastboot-l flash hboot hboot_brcust.nb0 . Windozers should use fastboot-w instead. Blackroot will wait for the device again.
9. Reboot your phone into the bootloader manually, by holding the trackball while powering up. The image should install on this boot, resizing your phone's internal memory partitions.
10. Run # fastboot -w. Your Bootloader should be loaded up, with the 1st line saying something about BlackRose and the 2nd line saying 265/10/161. This is how you know it worked. That 265 is where it's at for KitKat. Your main OS had been destroyed, but your Recovery ROM should still work.
8. Install Evervolv KitKat.
1. Go here http://evervolv.com/devices/passion and download the latest stable release. At press time that's the 4.0.0p4.2 version. Save it to platform-tools.
2. Reboot to Recovery from the menu in the BlackRose bootloader.
3. Do # adb devices. Then do # adb push ev_passion-4.0.0p4.2-perdo-squished.zip /sdcard/ . If it doesn't work, try using the touch recovery menu to toggle mount USB, then push, then unmount. Or mount USB, use the computer's file system to move the file to the root of the sd card, then unmount USB. Or try as root if you're using linux.
4. From the main recovery menu, select install zip from SD card → choose zip → select the ev_passion-4... zip. Wait up, it could take a while.
5. Success!! Right? Right. #adb kill-server, you can unplug now and won't need to plug back in! Reboot the phone, you're getting perilously close! This boot could take five plus minutes, or just one, but be patient.
9. Install Gapps.
1. You are such a lucky dog. Gapps bundled updates are available through the Evervolv toolbox. So you can get Play Store and everything else will come easy. Go to settings → wifi, turn it on, hook it up to your wifi router.
2. Back up to settings, and go Evervolv Toolbox → Updates and swipe over to the Gapps section. Tapp the most recent Gapps-kk zip. Tap the down arrow to download.
3. Reboot manually to recovery.
4. From the main recovery menu, select install zip from SD card → choose zip → select the gapps-kk... zip. This could also take a sec.
5. Reboot again! You're almost done! When it's all loaded up, Play Store should now be installed, as well as various google options that you can enable through the Evervolv settings.
10. Install Mounts2sd.
1. Go to the Play Store and get Mounts2sd.
2. Hit the top right corner for application settings. You'll need to install a startup script. Agree, give it permanent superuser status.
3. Reboot.
4. Go back into Mounts2sd, and go to the Tool menu (Wrench). Note that boxes aren't checked unless they're green-checked.
5. Enable the Cache to move cache partition to data or sd-ext. Storage threshold is up to you. Make sureApplications, Libraries, Data, and Media are all checked. Dalvik should stay unchecked, System apps can too.
6. Reboot again.
11. You're done!!! Or at least we're done. You still have to restore your apps and put all that music back on and figure out how to resync your contacts and... Good Luck.
12. If you want to get extra tricky, it's believed to be possible to leave app data on the real internal memory by default, and use Titanium Backup to move the data of most of your apps to the SD-ext, thereby leaving the data of your favorite apps on real internal memory. Use at your own risk.
ENJOY!!
Appendix 1:
Linux PATH env: I put all my android stuff in a file called androidy, so my path to my platform-tools was /androidy/adt/sdk/platform-tools, and my blackrose was in there too. So to set my PATH, I used: $ export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/sean/androidy/adt/sdk/platform-tools:/home/sean/androidy/adt/sdk/platform-tools/blackrose_120421/binary"
In order to make sure that while using it as root (as was necessary for some fastbot operations), I referenced the same PATH instead of the messed up root PATH, I used sudo env PATH = $PATH a few times.
Appendix 2:
The only actual bug I've noticed in a few days with this ROM is that my Chrome bookmarks don't add shortcuts to the homescreen when I tell them to from within Chrome. The widget-adder (longpress homescreen) has a bookmark option though, so if you bookmark it you can put it on the homescreen from there.
Huge Thanks to everyone involved with ClockworkMod, Cyanogen, 4Ext, BlackRose, and Evervolv!
Sources:
http://wiki.cyanogenmod.org/w/Install_CM_for_passion
http://nexusonehacks.net/nexus-one-...n-how-to-unlock-bootloader-on-your-nexus-one/
http://marian.schedenig.name/2012/07/22/installing-android-4-ics-on-the-google-nexus-one/
http://forum.xda-developers.com/showthread.php?t=2540366&page=24
Wooooh, Amazing book ! Everything is soo.... deep. In my opinion, tutorials should be only few lines.
Some mistakes :
Why installing CM7 and then backing up ? (You can install non market apps without CM7, and when flashing CM7 you erase all user data)
Why using m2sd if the rom has a built-in feature called a2sd ?
Why installing CWM then 4EXT recovery ? (TWRP is a touch one, and you can flash recovery once you have root access)
"You should have or buy an 8+MB, Class 10 SD card" ? typo ?
In my mind, big steps should be :
1) Backup SD, and SMS and Apps
2) Root
3) Install recovery (TWRP is advised by evervolv, but CWMRecovery is OK)
4) Partition SD
5) Install Blackrose (using 260mB system)
6) Flash ROM
7) Flash GAPS
8) A2SD Y N Y
Notes :
About SD-Ext size, i recommend reading this post from his creator : http://forum.xda-developers.com/showthread.php?t=1716124
A2SD is an old version of INT2EXT+
Using terminal is not friendly for beginners. Avoid it at maximum.
Provide a link for a MD5 sum checker.
I don't know if it works with actual stock rom, but when i rooted my n1, i used SuperOneClick. Plug, Click, Wait, Smile. (I still have it if needed)
ldFxl said:
In my opinion, tutorials should be only few lines.
Click to expand...
Click to collapse
This tutorial doesn't need to exist at all. All the information is available elsewhere on the internet, I did nothing original. Its only value is that it puts all the information in full detail in one place so you don't have to look in the forums for elaboration on each line of a more concise tutorial. Hopefully with info this detailed, someone with more chops than me could script it.
ldFxl said:
Why installing CM7 and then backing up ? (You can install non market apps without CM7, and when flashing CM7 you erase all user data)
Why using m2sd if the rom has a built-in feature called a2sd ?
Click to expand...
Click to collapse
I had already installed CM7 when I thought to write this, Marian (my 3rd source) seems pretty skilled as he is the only one who could make BlackRose work for me so I trusted his advice that it was the easiet procedure he found. Have you put TWRP Recovery on from stock after unlocking the bootloader (fastboot oem unlock)? And have you successfully repartitioned SD (fat32 &ext4) from TWRP? If so and you want to quickly write up the steps, I'd gladly replace my steps 3-6, that would save people a lot of time and doing.
ldFxl said:
Why installing CWM then 4EXT recovery ? (TWRP is a touch one, and you can flash recovery once you have root access)
Click to expand...
Click to collapse
4EXT is also touch, CWM cannot repartition SD. If you can go stock to TWRP this might be the best option. Or if not, stock to 4ext.
ldFxl said:
"You should have or buy an 8+MB, Class 10 SD card" ? typo ?
Click to expand...
Click to collapse
Yes! Thanks.
ldFxl said:
Using terminal is not friendly for beginners. Avoid it at maximum.
Click to expand...
Click to collapse
Don't you have to use terminal to use the built in A2SD? At any rate, it didn't work for me (I'm kind of a beginner), Mounts2SD's GUI seemed a little more beginner friendly. Also I certainly wouldn't have been able to make BlackRose work
ldFxl said:
Provide a link for a MD5 sum checker.
Click to expand...
Click to collapse
Good idea
ldFxl said:
I don't know if it works with actual stock rom, but when i rooted my n1, i used SuperOneClick. Plug, Click, Wait, Smile. (I still have it if needed)
Click to expand...
Click to collapse
I once used SuperOneClick on another phone, it looked like it struggled and finally worked with a DDoS style attack, it seemed simpler to just do it the way the manufacturer intended (if that's even a thing). But I suppose if it works with one click it really is simpler as seen by the user. Anyone have a report on whether it worked from stock N1?
Fituate said:
I had already installed CM7 when I thought to write this, Marian (my 3rd source) seems pretty skilled as he is the only one who could make BlackRose work for me so I trusted his advice that it was the easiet procedure he found. Have you put TWRP Recovery on from stock after unlocking the bootloader (fastboot oem unlock)? And have you successfully repartitioned SD (fat32 &ext4) from TWRP? If so and you want to quickly write up the steps, I'd gladly replace my steps 3-6, that would save people a lot of time and doing.
Click to expand...
Click to collapse
On my first flash, i was pretty beginner, so i followed a tutorial ; ) . And they used CWM. But flashing a recovery procedure from .img file doesn't differ with the recovery. TWRP allows you to partition SDCard. I did it last week (on HTC wildfire S, TWRP 2.6 as for N1).
Flashing step is the same -> just replace img file name. You can get it Here (From official TWRP Website)
Procedure from TWRP Website said:
Download the above file. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fasboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
Click to expand...
Click to collapse
6. Partition your SD Card
1. In recovery, Tap Advanced
2. Tap Partition SD Card
3. Set 2048 (MB max) on EXT Size and 0 on Swap Size
4. Tap EXT4 then swipe to start partitioning
Fituate said:
3. Reboot your phone manually. BlackRose should hijack the startup, install itself, and quit. Boot your phone up again.
Click to expand...
Click to collapse
Backrose is a custom Bootloader-> it replaces your HBoot/Fastboot
You don't need to reboot your phone to install blackrose. You just need your phone in ADB over USB, then the win setup will install blackrose.
Once done, run setup again, your phone will automaticaly go to HBoot, then choose 1, and 1 again.
Then enter "resize", "260" and "8".
In case that the installer don't work correctly, you can get flashable HBOOT from [Provide a nb0 (texasice recommend 260/8/168) AND MD5 Checksum]
While googling to find some infos (I don't remember me unlocking my bootloader) I found this guide : http://forum.xda-developers.com/wiki/HTC_Nexus_One/Flashing_Guide
Apperently SuperOneClick does not even need unlocked bootloader on 2.3.3 or previous ...
Isn't what we are trying to write down ?
There are many links pointing to this forum aswell.
First, thanks to @Uzephi and @41rw4lk for helping me to use/recover my phone. Please, read and do not underestimate the guides: our phone is tricky! We have two system partitions (slot a and b) to allow stock updates on-the-fly. This complicates the normal flashing process and if you do not follow the steps, you may bootloop. Use these guides at your own risk!
Reading this page is a good beginning to understanding the A/B partitioning scheme and how Motorola Z2 Force works:
1) Our phone has A/B partitioning, so flashing Magisk/XPosed is different
2) It does not support Project Treble (faster stock updates)
3) It does not a recovery partition, so flashing TWRP is different
Note also that the RSD Lite from Motorola has issues with Windows 10 and you’ll need to manual flash firmware if you bootloop (see Process E below). Other way is directly flashing from Qualcomm EDL mode (Emergency Download Mode) from which users can perform various tasks like unbricking, unlock bootloader, and installation of any custom ROMs.
Right now, this guide has 5 parts (maybe we can dual boot our phone in the future). If you just want to use a rooted stock ROM, please, search for other guides here on xda. These guides were written (and tested) using a Motorola Z2 Force XT1789-05 phone (Brazil), although most of it should work for other variants if you download and use proper firmware files for these other phones. For other models, better if you follow Uzephi’s guide.
A. Opening bootloader
B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
C. Flashing a custom AOSP ROM + rooting
D. Dirty flashing AOSP ROM updates
E. Recovering from bricks or returning to stock
F. Oreo ROM features comparison table
If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.
A. Opening bootloader
With enough battery in your phone (80%), you can follow the Motorola official guide which steps are:
1. Backup everything you need. Your phone will be reseted including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options, click the OEM unlock option to enable it. Also enable USB debugging.
3. Install the Motorola drivers in your computer, but (in my personal experience) not the Android SDK suggested in the official guide. Instead, extract these adb/fastboot files in a blank folder of your computer.
3.1) Do not use other adb/fastboot binaries: I cannot guarantee they will work.
3.2) You need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Open a command line window in the adb/fastboot folder (step 3), reboot the phone into the bootloader (see adb command below or press power + volume down buttons). Plug the phone on computer (see 3.2 above). Test the connection and run the command to get the code for unlocking:
Code:
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data
You’ll get:
Code:
(bootloader) Unlock data:
(bootloader) <code 1>
(bootloader) <code 2>
(bootloader) <code 3>
(bootloader) <code 4>
(bootloader) <code 5>
5. You’ll need to join 5 codes and, after logging into your own Motorola account, check by clicking the button “Can my device be unlocked” (step 6) by Motorola here. Read the text: your warranty will be void if you go ahead. Consider if you have enough knowledge, time and money to deal with a troublesome (or bricked) device. Although, it’s not that easy to hard brick this phone (see process E below).
Code:
<code 1><code 2><code 3><code 4><code 5>
6. You’ll receive back an email with the code to unlock your bootloader (if it is available for your model). Then you’ll run the following command:
Code:
fastboot oem unlock <code 1><code 2><code 3><code 4><code 5>
7. You’ll receive a warning that all your data would be erased (see step 1 above) and need to re-run the same command to confirm. At this point, your bootloader should be unlocked. As an Android restriction, each time you boot the phone you’ll see a warning. Do nothing, wait for 5 seconds and the phone boots normally. Some users bother with this warning and try to get rid of it.
B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
Requirements: unlocked bootloader (see guide A) and no security lock: disable PIN, gestures and fingerprinting (because TWRP cannot read the locked/cryptographed data of the phone). Enough battery in your phone (80%).
If you do not prepare your phone to custom ROMs and if you do not have both bootloaders of the phone in the same Android version of the ROM you’ll flash, you’ll hard brick the phone and lose also the access to the bootloader! You’ve been warned: follow the guide!
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool.
1. Backup everything you need. Your phone will be reset including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options and enable USB debugging.
3. Install the Motorola drivers and the adb/fastboot files.
3.1) do not use other adb/fastboot binaries: we cannot guarantee they will work.
3.2) you need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Download the firmware of the same Android major version of the future ROM you’ll install (Oreo for Oreo ROMs, for instance). When (and if) we move to Android P, most probably we will need to follow this guide again.
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
5. Extract the zip contents to a blank folder in your computer.
6. Download the FlashAll_XT1789-05.zip file, extract the content and move all files to the same firmware folder (step 5 above). Be sure to overwrite any file (if needed).
7. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
8. Reboot the phone into the bootloader (see adb command below or power + volume down buttons). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 7.
Code:
adb devices
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
9. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
10. Reboot your phone into the system (ROM) and do a quick configuration (remember that everything will be deleted when you install TWRP further…).
11. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging.
12. Download both the .img and .zip file of the TWRP recovery from the official site. It's the same file for all models/variants of Z2 Force phone. Put the files into our firmware folder (step 5 above). Copy the .zip file to the phone internal card. Note: versions older than 3.2.2-2 does not support PIN/Password/Fingerprint, so disable them before proceed. Most probably, ROMs before July 20th, 2018 cannot be flashed in older TWRP.
13. Now boot (not flash) the TWRP .img file using a command line window in the same firmware folder (step 5 above):
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot <TWRP file name>.img
14. Only now that you’re inside TWRP temporarily flash the TWRP .zip file you’ve saved into the phone (step 12 above).
15. Reboot into TWRP (use the main reboot menu in TWRP).
16. Now, you should reboot again into bootloader: inside TWRP, go to Reboot menu and choose Bootloader.
17. Now you will wipe all user data via bootloader. This is necessary to use an AOSP ROM when you come from stock. Using a command line window in the same firmware folder of your computer (step 5 above), run the following commands:
Code:
fastboot devices
fastboot -w
18. Now you can reboot the phone into System using the buttons volume up/down to navigate and confirming with the Power button. You’ll be with stock ROM and TWRP. If you want to move to a custom AOSP ROM, do a quick configuration: into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging and go to the proper guide (Process C).
C. Flashing a custom AOSP ROM + rooting
1. Requirements:
1.1 Motorola drivers.
1.2 Our custom adb/fastboot files (others may not work!).
1.3 USB debugging enabled into the Developer Options.
1.4 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.5 An USB 2.0 port of your computer (some users report that USB 3.0 will also work).
1.6 Two Oreo bootloaders (process B above).
1.7 Permanent TWRP
1.8 Enough battery in your phone (80%).
2. Download the AOSP ROM you want and move the .zip files to the phone. Right now, we have:
2.1 Dirty Unicorns: no need for Gapps. Official and Weeklies can be dirty flashed interchangeably. RC has a different signature. Support on Google+ page. More about DU kernel.
2.2 Lineage OS 15.1. MindTheGapps needed. OpenGapps not compatible yet. XDA thread.
2.3 Mokee: Gapps needed. Take care: online guides assume that you already have an AOSP ROM, TWRP and rooted device.
Deprecated (?)
2.4 AOSiP: no need for Gapps. XDA thread.
2.5 Invictrix. Gapps are built in. XDA thread
3. Choose the root method and download the .zip files: Magisk (suggested) or LineageOS SU Addon. Move the .zip files to phone. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk or you did not reboot between flashing ROM/Gapps and Magisk. Note: SuperSu is deprecated.
4. Reboot into TWRP:
Code:
adb reboot recovery
Then flash the ROM. It will be flashed in two steps only in the “other” slot. We have two slots, A and B. Our phone can be upgraded on-the-fly because the update is always applied to the slot not booted, the “other” slot. Then, immediately, flash the .zip TWRP or you will lose it.
5. Go to Reboot menu of TWRP and reboot into bootloader. Then, in the folder with adb/fastboot binaries (see 1.2 above), you need to wipe data (including sdcard) with the following commands:
Code:
fastboot devices
fastboot -w
6. Now you need to reboot the phone into System using the buttons volume up/down and confirming with the Power button (or typing fastboot reboot into the command line windows). You’ll be with an AOSP ROM and TWRP.
7. Once into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging if you intend to dirty flash ROM updates.
8. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved). Note: if you bootloop on Magisk, remember it is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
9. A good place to read what is not working is in the section known problems of LineageOS.
D. Dirty flashing AOSP ROM updates
1. If you follow all the processes above, you can dirty flash updates because you have:
1.1 Motorola drivers installed.
1.2 Specific adb/fastboot files for our phone and an USB 2.0 port in a Windows computer (some users report that USB 3.0 will also work).
1.3 Unlocked bootloaders (Process A above).
1.4 Permanent TWRP running and TWRP .zip file placed inside your phone and ready to be flashed again.
1.5 An AOSP ROM already running.
1.6 Developer Options and USB debugging enabled.
1.7 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.8 Enough battery in your phone (80%)
2. Download your ROM .zip update, copy it into the phone sdcard and reboot your phone into TWRP. See download links here.
3. Within TWRP you should flash (install) things in the following order:
3.1 ROM update .zip file. Remember that, at this time, the update will be flashed int the other slot and inside phone you’ll have both the system before update (in the booted slot) and updated ROM in the other slot.
3.2 TWRP .zip file (step 1.4 above) once again (do not skip this step or you’ll bootloop!).
4. Reboot to System: if you skip this step, you’ll bootloop.
5. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved) or LineageOS SU Addon .zip file. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk. I suggest v16.0 and, after you got rooted with 16.0, you can update. It is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
Note: SuperSu is deprecated.
6. Wipe Dalvik/ART cache: go to Wipe menu of TWRP > Advanced Wipe > Dalvik/ART Cache only.
7. Reboot your phone into System (ROM) will use the “other” slot, the one with the updated ROM.
8. You can use XPosed installer app (and reboot).
9. Now you can add your PIN, fingerprint, gestures back until next flashing.
E. Recovering from soft bricks or returning to Stock
If you’re reading this is because you already unlock your bootloader (see guide A) and anything went wrong, but you still can boot your phone into bootloader. Plug your phone and get enough battery (even if you do not see any charging signal).
1. Install the Motorola drivers and the specific adb/fastboot files for our phone. Remember, follow the rules because our device is tricky!
1.1) Do not use other adb/fastboot binaries: we cannot guarantee they will work.
1.2) You need to use a USB 2.0 port of your computer (some users report that USB 3.0 will also work).
2. Download the latest firmware for your model:
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
3. Extract the zip contents to a blank folder in your computer.
4. Download the FlashAll_XT1789-05.zip file (it should work for other Motorola Z2 Force models as well), extract the content and move all files to the same firmware folder (step 2 above). Be sure to overwrite any file (if needed).
5. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
6. Reboot the phone into the bootloader (see adb command below or power + volume down). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 5.
Code:
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
7. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
8. Reboot your phone into system (ROM) and do not forget, later, to enable the Developer Options and USB debugging again.
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool. Maybe these Latest 2017 Qualcomm Diag QD-Loader Windows 10 Drivers signed will help you.
F. Oreo ROM features comparison
This is a table for Oreo ROM features comparison for Motorola Z2 Force - nash.
I would like to receive feedback and updates from the users, as I can't keep changing from one ROM to another and they get new features, updates, improvements, etc.
I consider Lineage OS 15.1 our stock ROM regarding to customization. So, it's not listed there.
Legend:
Code:
X = Feature present
XX = ROM excels in this particular feature (in my opinion).
If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.
I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.
renanjones said:
I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.
Click to expand...
Click to collapse
I see two possible scenarios:
1. Your bootloader is locked (yet) (see guide A).
2. Your in a "false locked" situation that, maybe, could be solved by resetting data via recovery or in bootloader (with the command: fastboot -w).
Great tutorial, but I did not get 4g in any of the roms, only 3g
Gutto said:
Great tutorial, but I did not get 4g in any of the roms, only 3g
Click to expand...
Click to collapse
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).
Technical said:
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).
Click to expand...
Click to collapse
My cell phone and Sprint, I did every process that you indicated, but not 4G
So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again
shalpp said:
So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again
Click to expand...
Click to collapse
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.
41rw4lk said:
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.
Click to expand...
Click to collapse
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?
shalpp said:
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?
Click to expand...
Click to collapse
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.
41rw4lk said:
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.
Click to expand...
Click to collapse
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect
shalpp said:
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect
Click to expand...
Click to collapse
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.
41rw4lk said:
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.
Click to expand...
Click to collapse
It appears as Qualcomm 9008
It only starts the loop after starting a blankflash. That's about the only response I get out of the device, otherwise it does absolutely nothing, no combination of buttons do anything
Edit: Confirmed connect/disconnect on another machine with the same driver configuration