Related
This guide is ancient, guys. The only purpose it should serve now is showing you how to set up ADB or flash something through recovery. You can use unrEVOked Forever to root now, which is much faster and easier. Quit sending me PMs with questions about this.
After the positive response I got from my Swype guide, I decided to do one for root too. I have found that Toast's guide goes way over the head of a lot of new users (Using adb to copy and rename files? C'm on, Toast!), and I want to simplify things down for them.
In this guide, I will provide a way for you to backup your phone in case you have any vital programs, and I will take you all the way through getting back to the rooted stock image and restoring your apps (from there, you will be on your own!). This DOES work with Sprint's latest OTA (ends in .6).
Please let me know if there are any errors or any omissions (something like Titanium Backup not working with unrEVOked; I haven't tested this). Also, if someone wants to take some screenshots of the recovery stuff or just has images of the steps, just let me know, and I can add them.
If you get stuck on a step, please post it in the topic first instead of directly PMing me. It's not that I don't want to personally help you (you can ask all the people I've helped), but I'm not always directly available, and other users can freely help you out if you post in the thread! It also provides a little "mini-troubleshooting" scenario for anyone else with the same issue as you. I also recommend reading the entire guide before doing it so you will have some idea of what steps you will be taking! Thanks!
TABLE OF CONTENTS:
SECTION I: BACKING UP YOUR APPS
SECTION II: ROOTING FOR THE FIRST TIME
SECTION III: INSTALLING A CUSTOM RECOVERY
SECTION IV: INSTALLING A CUSTOM ROM
SECTION V: NESSECARY SOFTWARE INSTALLATION
SECTION VI: INTRODUCTION TO ADB
SECTION VII: UNLOCKING NAND
1. First things first, if you don't want to backup your apps, skip to step #14.
SECTION I: BACKING UP YOUR APPS
2. Go to the settings menu, and select Applications.
3. Check the box next to "Unknown Applications" and accept the warning.
{
"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"
}
4. Go to your web browser and navigate to http://unrevoked.com/m/ .
5. Click the logo to download the file, as it says.
6. Once the file is done downloading, click it.
7. Click the install button, and hit "open" when it is done installing.
8. Click Start!
9. When you get the "Done." message, navigate to the Market and find Titanium Backup. I HIGHLY recommend the donate version, but you need to donate to the dev via PayPal to get a license file, and it could take him up to a day to email it to you.
10. Click "open" after it is done installing and click the "Problems?" tab at the bottom.
11. Click "yes" to install BusyBox.
12. When Titanium Backup restarts, press Menu and select "Batch."
13. Backup all of your apps here.
SECTION II: ROOTING FOR THE FIRST TIME
14. Plug in your phone's USB cable and connect it to your computer. You should get a prompt in the notification bar that the phone is connected. Open the notification bar and select where it says "charge only."
15. Change the type to "disk drive" and select "Done."
16. Download this file, and save it to your desktop.
17. Since your phone is connected as a disk drive, navigate to My Computer and you will see it as "Removable Disk." Drag and drop the file you just downloaded to the icon.
18. At this point, we are about to flash the debug image. YOUR DATA WILL ALL BE WIPED AFTER THIS POINT!
19. Hold down "power" to bring up the following menu. Select "Power off."
20. Select "Ok."
21. Thanks to mrono, we now have some images of the recovery image for your ease of use, but I will post toast's exact words that you should follow to the letter. If you want step-by-step versions of this, skip to step 21a.
- Hold volume down while powering the phone on. continue to hold volume down until you see the WHITE bootloader screen.
- After a few seconds it will begin to checking for files, and find PC36IMG.zip. while its doing this it will show a blue progress bar while its checking. (this takes 30 - 60 seconds to finish)
- It will then list all the images in the zip and ask you if want to flash. SAY YES
- When its finished it will ask you if you would like to reboot. AGAIN... SAY YES
- At this point it will boot into a rooted rom.
Click to expand...
Click to collapse
Essentially, you just have to hold the volume down button as you press the power button, and the phone will do the rest. Just accept any prompts you get.
21a. When powering on, hold down the volume down key, and keep holding it down until this screen appears.
21b. It will search for a second then prompt you to install the PC36IMG.zip. Select yes.
21c. After the installation is complete, select yes to reboot your device.
22. You are now rooted! Congratulations! However, this debug ROM will not show protected apps in the Market, so we're going to install a rooted version of the stock ROM now.
23. After everything is booted, reconnect your USB cable and enter disk drive mode as described before.
24. Navigate to the PC36IMG.zip file and rename it however you want. This prevents it from running when ever you reboot. After this file is renamed, disable "disk mode" the same way you enabled it.
SECTION III: INSTALLING A CUSTOM RECOVERY
NOTE: Steps 25 - 28 were removed due to ROM Manager being updated. Follow the steps in step 29 below.
29. If ROM Manager just won't work for you, download this file, rename it to "update.zip," and copy it to the root of your SD card just like we did with the PC36IMG zip before. A common problem that people have here is actually typing the last ".zip" in when naming the file. ONLY type "update" as the file name because the file you are downloading is already in .zip format, and Windows hides known file extensions. If you get any kind of "file cannot be found" or "verification error" on this step, then you probably made this mistake, and you just need to rename the file.
Please note: This is the ONLY file on your SD card to be named "update.zip." Do NOT rename any other files to "update.zip" or remove this file.
SECTION IV: INSTALLING A CUSTOM ROM
30. At this time, we will download the rooted stock ROM. Get it here and save it to your desktop. Do NOT rename this downloaded ROM to "update.zip!"
31. Copy it to your SD card exactly like we did before with the first ROM. Make sure you re-enable disk mode so you can copy files again.
32. Once again, thanks to mrono we have photos of this step, but I will give you the exact words from Koush on how to boot into recovery. Skip to step 32a for exact step-by-step instructions in this step.
When you want to launch the recovery image
* Turn on your device with 'volume down' pressed and select 'Recovery'
* When the exclamation mark appears, press and hold 'volume up' then press 'power'
* Select the second option, 'Apply sdcard:update.zip
* That's it, ClockworkMod recovery should launch!
Click to expand...
Click to collapse
Just like before, we turn off the phone and hold the volume down key as we power on the device. However, this time we will select "Recovery" from the menu (move down with the volume button and select it with the power button). Now you will see a screen with an exclamation mark. Press and hold the volume up button and press the power button. Select the "apply update.zip" option, and you will be in recovery mode.
32a. Just as before, hold down the volume down key as you power on the phone until this screen appears. Select "Recovery" from the menu.
32b. When you enter recovery, you will see the following screen. Don't panic.
32c. Hold the volume up button and press the power button. You will now be presented with the following screen.
32d. From here, select "apply sdcard:update.zip." Remember, this is the recovery image from before. Your phone will boot into the ClockworkMod custom recovery.
33. First, wipe the cache partition and the user data by selecting their respective menu options. From here, select "install zip from sdcard." Now select "choose zip from sdcard" and navigate to the stock ROM .zip file that we downloaded. Skip to step 33a for step-by-step images, but the text below may help you navigate the recovery menu:
The full recovery menu will read as follows:
-reboot system now
-apply sdcard: update.zip
-wipe data/factory reset
-wipe cache partition
-install zip from sdcard
-nandroid
-partitions menu
-advanced
- *****Go Back*****
Click to expand...
Click to collapse
Select the bolded in the items in the order in which they appear. After all is wiped, select -install zip from sdcard then pick -choose zip from sdcard and finally navigate to the zipped ROM that you want to install.
33a. From the recovery menu, select the following options and confirm them: "wipe data/factory reset" followed by "wipe cache partition."
33b. After everything is wiped, navigate to "install zip from sdcard," then select "choose zip from sdcard."
33c. Now, navigate to the custom ROM that you downloaded and select it. You will get a progress bar.
34. After the ROM is done installing, press "**Go Back**" and then pick "reboot system now" from the menu.
35. Congratulations again! You are now running a rooted version of the stock ROM (or the custom ROM of your choice). You can restore your apps with Titanium Backup or you can get another custom ROM and flash it exactly the same way that you flashed the stock ROM. I highly recommend Fresh ROM, which can be found in this topic. In fact, ANY custom ROM can be flashed in the same manner that is described in steps 30-34.
35a. Make sure you flash the latest radio update before installing any custom ROMs! It flashes just like a ROM, and you can download it and find any warning information here. Don't dp this yet if you plan on continuing the guide and unlocking NAND because you will have to do it again at the end of the guide.
SECTION V: NESSECARY SOFTWARE INSTALLATION
36. We are going to download and install three pieces of software here: 7-Zip, HTC Sync, and the Android SDK. First, we will install 7-Zip. Navigate to the 7-Zip website (http://www.7-zip.org/download.html) and download the appropriate version for your copy of Windows (either 32 or 64 bit). Install it. In my opinion, this is the best archive utility, and it just makes life easier if we're on the same page.
37. Next, head to the HTC website (http://www.htc.com/us/support/evo-sprint/downloads/) and download the HTC Sync update for Windows. Install it. This should take care of your drivers for 32 or 64 bit.
38. Finally, head to the Android Developers (http://developer.android.com/sdk/index.html) website and select the Windows version of the Android SDK. Agree to the software agreement and save the file.
39. Take the zip file that you just downloaded and copy it to your C: drive as shown.
40. Once the file is copied, right click on it and select 7-Zip then "Extract Files Here." You should now see a folder called "android-sdk-windows" in the root of your C: drive. You've installed the Android SDK successfully.
SECTION VI: INTRODUCTION TO ADB
41. Accessing ADB is very easy. Click on the new android-sdk-windows folder, and you will see a bunch of different folders inside. We're going to be concerned with the "tools" folder, but don't open it!
42. Hold down the shift key and right click the tools folder. Select "Open Command Window Here" from the pop-up list. You have now opened an adb window, and any interaction with your phone will be done through this simple command line. You can copy lines directly from this tutorial and paste them into the command window by right clicking and selecting "Paste" (CTRL+V will not work in the command line).
43. If you want to manually navigate to the adb line (you don't need to do this unless you couldn't get step 42 to work), open a Command Prompt window (Run -> "cmd.exe" on XP/Vista, or just search "Command Prompt" in Windows 7). Now enter the following line of code: cd C:\android-sdk-windows\tools\ . This will take you to the tools folder where you must execute all adb commands.
44. Remember how to get to the adb command prompt. Any time I tell you to enter something via adb take the following steps: Connect your phone via USB, ensure USB Debugging is enabled (Menu -> Settings -> Applications -> Development, but this should be already enabled from the previous steps), and open the command window via either method described in steps 42 or 43. You can find a list of basic adb commands here or by typing "adb help" from the adb command line. You should always be able to directly copy and paste any code that I give you, however.
SECTION VII: UNLOCKING NAND
45. Download Toast's EVO Recovery files here. Save the .zip file anywhere you please. When it is done downloadi ng, right click it, and "Extract Files Here" using 7-Zip again. We are going to use a batch file in this folder to enter a custom recovery mode in a minute.
46. Download the new PC36IMG.zip debug ROM located here. When the menu pops up asking you to save the file, remove the "eng-" off the name so it only reads "PC36IMG". It is very important that you do this before you copy the file to your phone, either now or manually after you save it. NOTE: This is NOT the same image that we used in the first portion of the guide. You MUST download this version.
47. Next, download Toast's custom recovery image located here. Again, right click it and select "save target as." This time delete everything else off the front of the file name so it only reads "recovery".
48. The last two files that you will be downloading are mtd-eng.zip (located here) and flash_image.zip (located here). Once both of these files are downloaded them, right click and "Extract files here" with 7-Zip. You will now have the following files downloaded and extracted:
49. Copy the flash_image, mtd-eng.img, recovery.img, and PC36IMG.zip files to the root of your SD card just as shown below.
50. Now the fun part!! Open an adb window and enter the following code:
Code:
adb reboot recovery
Your phone will now reboot and show the yield sign with the red exclamation point. Don't touch it!
51. Navigate to that "evo-recovery" folder that you extracted earlier and right click on the "recovery-windows" batch file. Select "Run as Administrator" from the menu to execute the file. Another command window will pop up and spew out a bunch of lines. Don't touch it! Just look at your phone which is now in the Amon RA recovery image! If right-clicking doesn't work, try double-clicking to run it normally.
52. Special thanks to Riztnack for the wonderful screens in the follownig sections! Select "Backup and Restore" from the recovery menu. After that select the option to backup your current ROM. You have just performed a nandroid backup. Keep this in mind, becase we are going to restore this after the whole process is over.
53. Select "reboot" from the recovery menu and let your phone boot back up. Make sure you are connected to your computer via USB (you should not be in disk drive mode here or you will get an error), and go back to that same adb window we had open before and used to reboot our device (you can close the window that opened when you ran the batch file). Enter the following lines exactly as they are written, ONE LINE AT A TIME (I recommend copy and pasting):
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
You will get an error message if anything goes wrong in the shell. When you enter the last three commands the window will just repeat them again to confirm that they were executed properly.
54. Now power off your phone just as before. Hold the volume down button as you press power to turn the device on. It will enter the bootloader just as before.
55. Select YES to flash the image, and after it is done flashing select YES to reboot. Don't worry if one of the "TP" options is bypassed. This is normal.
56. Once rebooted, go back to your adb command window and enter the following commands:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
You will get the same confirmations when you enter the 2nd through 4th commands. After you enter the last one the phone SHOULD boot into the same recovery that we were in before. If your phone does NOT boot into recovery, take the following steps: Disconnect from USB, pull the battery, reboot the device, and enter the same adb commands as in step 53. After that, enter lines 2 throuh 5 from step 56. You should now be in recovery. Disclaimer: These were just the steps that I took after my phone did not boot into recovery the first time. They worked for me, so let me know if they work for you or not.
57. Your NAND is now unlocked!! Once your phone boots directly into recovery in step #56, take that as confirmation of success! While in recovery, wipe your user data (factory reset) and wipe the Dalvic cache.
58. Head to the Backup/Restore menu and restore that last nandroid backup that you just did. You can now reboot your phone, and it will be exactly the same as before.
58a. Make sure you flash the latest radio update before installing any custom ROMs! It flashes just like a ROM, and you can download it and find any warning information here. Even if you installed it before, you will have to flash it again because the debug ROM writes an older version.
59. Be sure to rename that PC36IMG.zip to something else like "NAND-PC36IMG.zip" just like you did before so that it doesn't try to boot it every time you enter the bootloader.
60. You can now enter recovery mode by entering the bootloader (holding volume down while powering on the device) and selecting recovery or by using the QuickBoot app (I highly recommend it). You can also use apps like AdFree or Root Explorer to freely edit your /system partition.
I really hoped this guide helped you guys, and I look forward to your feedback.
I'm not going to be asking for any donations because I'm not the one doing all of the work--the devs are the real contributers. I've just taken thier methods and spelled them out in an easy-to-follow way. Those guys work long hours contributing to the community so you should be donating to them.
That's all, folks! I hope you enjoy your root! Big thanks to all of the devs who have made this possible!
Here are some important links with relevant discussions:
Original root guide.
Fake-flash recovery guide.
Stock RUU topic with discussion.
Stock OTA topic with discussion.
How to fix QuickBoot and ROM Manager's rebooting functions on some ROMs.
ADB guide for when you're ready to take the next step.
Making ClockworkMod your permanent recovery.
Original NAND unlock guide.
that's beautiful for noobs
madunix said:
that's beautiful for noobs
Click to expand...
Click to collapse
Thank you!
So this is basically like mixed with Toast's root and unrevoked.
Very well done!
May I make a suggestion?
Maybe change step 24 to
24. Navigate to the PC36IMG.zip file and rename it however you want. This prevents it from running when ever you reboot.
Someone might actually look for debig .zip
will this guide work if i installed the OTA update (version ends in .6 instead of .1)
thanks
MrDSL said:
Very well done!
May I make a suggestion?
Maybe change step 24 to
24. Navigate to the PC36IMG.zip file and rename it however you want. This prevents it from running when ever you reboot.
Someone might actually look for debig .zip
Click to expand...
Click to collapse
Done. Thanks for the input.
jblazea50 said:
will this guide work if i installed the OTA update (version ends in .6 instead of .1)
thanks
Click to expand...
Click to collapse
Yes, I believe it will.
thanks, about to try it out
You might add in on step 26 that you need to switch back to 'charge only' mode for Rom Manager to work, otherwise you get a 'SD card not mounted' error. (at least I did )
Otherwise, great post!
How does one go from Clockwork recovery back to stock recovery?
I love how you have your Drives named.....especially the one for Pirated Stuff. I laughed.
strung said:
How do you go from Clockwork recovery back to stock?
Click to expand...
Click to collapse
You can't permanently flash clockwork yet, it's just temporary until you reboot then the stock recovery goes back. Unless there have been some major developments today.
logosmonkey said:
You might add in on step 26 that you need to switch back to 'charge only' mode for Rom Manager to work, otherwise you get a 'SD card not mounted' error. (at least I did )
Otherwise, great post!
Click to expand...
Click to collapse
Oh yes! Good post!
strung said:
How do you go from Clockwork recovery back to stock?
Click to expand...
Click to collapse
ClockworkMod recovery is actually just that file named update.zip in the root of your memory stick. We can't actually flash a real recovery image yet, so it is tricked into thinking we are flashing an update when we are really going into a recovery image.
worked like a charm; installed damagecontrol .v3 rom
jblazea50 said:
worked like a charm; installed damagecontrol .v3 rom
Click to expand...
Click to collapse
Happy to hear it! Did you do the unrEVOked bit, by chance? I actually never tested that out personally because I was already rooted when I wrote this.
Thanks so much for this. I'm new to android and didn't understand any of the terminology people were using. This is good.
I think my only suggestion would be to skip the initial rom manager install to download the recovery. I couldn't get rom manager to actually download the update.zip and it probably would have saved some time to just download the update.zip in the first place and do it manually. It kept saying it was successfully downloaded when it wasn't.
roybotnik said:
Thanks so much for this. I'm new to android and didn't understand any of the terminology people were using. This is good.
I think my only suggestion would be to skip the initial rom manager install to download the recovery. I couldn't get rom manager to actually download the update.zip and it probably would have saved some time to just download the update.zip in the first place and do it manually. It kept saying it was successfully downloaded when it wasn't.
Click to expand...
Click to collapse
Thanks for the input. Please let me know if anyone else is having problems with ROM manager on the debug ROM, and I will switch it around.
TheBiles said:
Happy to hear it! Did you do the unrEVOked bit, by chance? I actually never tested that out personally because I was already rooted when I wrote this.
Click to expand...
Click to collapse
i went from step 1 to 34, followed all of it; the only thing is i installed a different custom rom; had to install the recovery image as an update.zip
also, i don't think you mentioned in your guide to wipe data/factory reset prior to installing custom rom because when i did it the 1st time, got stuck in a boot loop; then i realized i had to wipe and it worked fine;
oh, also, after the boot loop, i had to do flash the recovery image as update.zip again because it wasn't there when i went back to recovery
I know this a noob question but will this work after the htc update?
I keep hearing mixed things!!!!
Thanks and OMG that was beautiful
jblazea50 said:
i went from step 1 to 34, followed all of it; the only thing is i installed a different custom rom; had to install the recovery image as an update.zip
also, i don't think you mentioned in your guide to wipe data/factory reset prior to installing custom rom because when i did it the 1st time, got stuck in a boot loop; then i realized i had to wipe and it worked fine;
oh, also, after the boot loop, i had to do flash the recovery image as update.zip again because it wasn't there when i went back to recovery
Click to expand...
Click to collapse
Yeah, I added in that data wipe bit not long ago because I forgot to. I wonder why the ROM Manager doesn't work in the debug ROM... I'll definitely just remove that later tonight.
If you would like to S-OFF, Install ClockWork Recovery, permanently Root & obtain SuperCID. Follow Steps 1 to 4!
To Debrand or flash an official stock ROM only: follow Steps 1 & 4 only (you may skip step 3 & 4 is you do not need them)
To Root: follow steps 1-3
To install a custom ROM for the first time: Steps 1 & 2 then follow the guide below on how to install a custom Rom (step 3 isn't needed as customs roms are already rooted)
CLICK HERE FOR [GUIDE] TO UNLOCK YOUR SENSATION FREE - WORKING FOR EVERY SENSATION (noobproof) Steps 1-3 Needed! or Steps 1 & 2 plus custom ROM
UPDATE: NEW Recovery 5.0.0.8 - Follow Step 2 below to download and install. you do not need to follow the rest of the steps if you are just updating CWM
For Warranty Purposes/Returns:Follow Step 4 below for removing Clockwork and Root
FOLLOW STEP 5 TO CHANGE BACK TO S-ON - CONFIRMED TO BE WORKING- USE WITH CAUTION
Whether your a noob or not, it nice to see a step by step guide as S-off is developer preview only and doesn't come with much instructions. I have simply Collaborated what is out there into one easy thread. Nothing complex.
here is my very small simple detailed guide. I have put a lot of Time and effort to make sure everyone can benefit so Just push Thanks if it helped
Click here for TROUBLESHOOTING OR FAQ
Step 1. To S-OFF your Sensation - (You do not need to do this if you have S-off already or done this before) - WORKING NOW for TMOUS users
Visit http://revolutionary.io/
download the application for your operating System. AND EXTRACT IT TO A FOLDER
YOU MAY NEED TO DISABLE YOUR ANTIVIRUS PROGRAM- Norton is flagging up Revolutionary as a Virus when it isn't
IMPORTANT
Fill out the form under the download links with your OS, Device, Hboot Version and Serial number. This will give your beta key to enable you to S - OFF. Make a note of this.
How To get your Hboot Version - 3 methods below
1. Run the revolutionary Utility you just downloaded from http://revolutionary.io/ and if it has found your device it should read
"Found your Device: HTC Sensation Z710* Applications -> Development)
4. With the phone switched on (not in HBOOT, just the regular home screen), plug in your USB cable and select HTC sync mode.(IGNORE any warning messages on your phone telling you it cannot find HTC Sync )
5. Launch revolutionary.exe. It should detect the phone and ask for your beta key. Type it (BE CAREFUL, as its case sensitive) or copy and paste it in.
If Revolutionary fails to find your phone verify you have all the drivers installed, try disk drive mode or charging mode (Linux users can use disk drive mode. Confirmed to be working by others)
6. Once you have entered your beta key correctly, follow any on screen prompts or actions from revolutionary and wait for it to S-Off,
7. You're done. Your Device will Successfully have S-OFF....if it hangs on method 3 and doesn't S-Off. See post 2 below for solutions.
IF REVOLUTIONARY SAYS FAILED YOUR PHONE IS NOT SUPPORTED. Go back and check hboot using the methods above. some users are told its failed and they still have S off now. If you have S-off your hboot will now be 1.17.1011 and revolutionary will tell you now your device is not supported
8. Revolutionary will now ask you to Install clockwork recovery mod after S OFF. Type N and install it manually below (the recovery provided is v4.0.1.4 doesn't charge when device is switched off, the one below v5.0.0.1 does charge)
9. Your Device now is S-off.
To install clockwork recovery for the sensation. Follow step 2!
STEP 2. To INSTALL Recovery - v5.0.0.8
1. Download recovery v5.0.0.8 for the Sensation [URL="http://forum.xda-developers.com/showthread.php?t=1277975"]HERE:[/URL] or Multiupload
2. Copy the PG58IMG file into the Root folder of your SD card (The main Folder of your Memory Card)
3. Turn off your phone FUlly and reboot into the Bootloader/HBOOT screen (see post above on how to get to hboot screen)
4. Press Volume up to Accept when it asks" Do you want to start the update"
5. Press Power Off to Reboot back to android after installation is successful (normal screen with homescreen)
6. Delete PG58IMG from your memory card and you can now root using step 3 below or install a custom ROM using CWM (Customs Roms are already rooted)
7. OPTIONAL: Boot into recovery or Completely switch off (Fastboot disabled or remove and reinsert battery)
Follow STEP 4 SUPER CID sub steps 1-6 to get adb running
8. Enter the command "adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status" Phone will confirm it is "CHARGING"
Charging issues fixed with new clockwork recovery. writing is now BLUE not purple or orange
Step 3. To permanently root your Sensation - (This means you will NOT LOSE ROOT on rebooting)
1. Download the file su-2.3.6.3-ef-signed.zip from here: DOWNLOAD
2. Copy su-2.3.6.3-ef-signed.zip to your SD card root folder (main folder of your memory card)
3. Start clockworkmod recovery (instructions below. See To Start Clockwork recovery)
4. BACKUP YOUR ROM USING CWM BEFORE ATTEMPTING ROOT!
5. Navigate to "Backup & Restore" using the Volume Down button and press select (power button to select) then select "Backup"
6. Select "install zip from sdcard" after backing up
7. Then select "Choose zip from sdcard"
8. Then select "su-2.3.6.3-efgh-signed.zip"
9. Then select "Yes - install su-2.3.6.3-efgh-signed.zip" to confirm
10. Then go back
11. Then reboot.
12. You're rooted!
If you are getting error messages regarding S-OFF, Rooting or installation - Troubleshoot below in post 2
See POST 2(HERE):
STEP 4. WRITE SUPER CID [YOU ONLY NEED TO DO THIS ONCE]- (continue from step 11 below if you have already done this)
(allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE)
1. Download adb tools here: download for WINDOWS or download for LINUX or from the attachments below
2. On your pc click on your local disk C: Drive (or D: drive for some) (WINDOWS users: Start > My computer > Local Disk (C)
3. Create a new folder called "adb" and extract the files from adb.zip into it. Make sure it doesn't create another folder in the adb folder when extracting
{
"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"
}
4. open command prompt (or terminal for linux) and type "cd" "followed by the path to your adb folder" (windows users can type "cd C:\adb")
5. Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (Ensure usb debugging is on settings)
6. enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
7. enter the command "adb reboot-bootloader". (nothing further required device WILL reboot in bootloader)
IF it doesn't you can Manually put the phone in the bootloader/hboot mode
Navigate to fastboot by pressing volume down and pressing power button to select (power off > vol down + power on)
It will take you to the fastboot bootloader screen on your phone
Connect your phone via USB
Your Screen should now read fastboot USB
8. enter the command "fastboot oem writecid 11111111"
9. enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
10. enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
11. enter the command "fastboot reboot"
12. You can now flash any ROM you like.
To reinstall any stock ROM after this or De-brand or reinstall a different type of Rom (European, Asian, US).
Just click here to download an Official Rom,
Connect to your phone in charging mode. click the "RUU_pyramid_*****.exe" file you downloaded and follow on screen instructions.
I can confirm SuperCID is successful as i just flashed a Tmous Rom (1.25.***) to my EU unbranded device to check. (added t-mobile tv and other carrier stuff to my apps list)
TO DE-BRAND OR REINSTALL STOCK ROM (Changes to Stock S-off, Removes Root and clockwork)
Reinstall your original stock ROM you had (e.g Vodafone, Tmous, Asian, European unbranded etc. if you are changing back to S-ON)
1. Backup all User Data and Apps (Titanium backup Recommended) SKIP THIS STEP IF YOU WANT TO WIPE EVERYTHING
2. Use the SUPERCID method above. (Confirmed to work)
3. If you cannot get superCID to work. Follow this by Alexp999. HERE: any problems PM ME and i will help
Your phone bootloader will read "PYRAMID PVT SHIP S-OFF RL" after this, Root and clockwork will have been removed now
STEP 5 - CHANGING BACK TO S-ON - PROCEED WITH CAUTION. ONLY DO THIS IF YOU ABSOLUTELY HAVE TO. BEWARE THERE IS A RISK OF BRICKING READ BEFORE GOING TO STEP 1.
YOU MUST Follow this correctly otherwise you could semi-brick your device (Semi bricks recovery by re-flashing RUU). If you follow it correctly YOU WILL GET S-ON SUCCESSFULLY -confirmed by other users
I cannot be held responsible if anything goes wrong but i will help in every situation. 2 unrecoverable bricks so far. 1 due to not flashing RUU
First time i did this with a custom ROM installed - semi-bricked my device (couldn't boot due to security warning as S-on doesn't work with custom roms), restored it using RUU.exe
Second time after S-off i took the following steps and successfully went back to S-ON without any problems and booted up into stock rom.
Confirmed to work by several others as well as myself
1. Follow Step 4 above to get SuperCID - Skip if you already have it
2. Restore your official stock Rom: Just click here to download an Official Rom RESTORE STOCK EVEN IF YOU JUST RESTORED IT RECENTLY OR ARE ALREADY ON STOCK ROM. This is to ensure nothing gets changed in stock for S-on to be successful
So if you are already on a stock ROM or you just went back to stock ROM, i don't care, restore the stock ROM again using the RUU.exe if you don't want to be bricked!
Connect to your phone in charging mode. click the "RUU_pyramid_*****.exe" file you downloaded and follow on screen instructions.
3. Make sure when you download the RUU. download the same or similiar RUU version as your phone came with (e.g. Tmous or EU or Asian etc). As long as you install a stock rom similiar to what you had you should be ok. FAILURE TO DO THIS MAY BRICK YOUR PHONE.
4. Switch your phone on now and let it boot for the first time and just skip through the welcome screen.
5. Go back to Step 4 - SUPERCID and go through 1 to 7 to get to the fastboot bootloader. (so just do what you did before, put adb files in local disk, adb reboot bootloader etc)
6. enter the command "fastboot oem writesecureflag 3" (Thanks Dazweeja)
7. Reboot into bootloader using "fastboot reboot-bootloader" or remove & reinsert the battery and press power on while keeping hold of volume down.
8. Bootloader should now read Pyramid PVT Ship S-ON RL.
9. Remove and reinsert the battery. Press power on as normal
You should now have S-on back and you can return your device or do whatever it is covered again under warranty.
10. IF IT DOESN'T REBOOT and bootloader says ***Security Warning**
Remove and re-insert the battery and go back into bootloader and holding Volume Down +power button select fastboot
11. Run RUU_Pyramid_***.exe to reflash stock rom. (the one u just downloaded in step 1) and then reboot. It should work now
The above method works successfully. So do not under any circumstances try this without going back to stock first using Ruu.exe. and Follow the instructions correctly if you want S-on WITHOUT problems Any doubts or questions PM me and i will get back to you and help you.
Donations welcome as i had a very shaky night experimenting and bricking my device (and having a panic attack over it) to find a safe method for successfully getting S-on back for all you out there complaining about warranty.
To Start Clockwork recovery
1. EITHER make sure fastboot is disabled in settings and shut down your phone
This can be done via Settings > Power> Untick "FAST BOOT" at the bottom.
OR take out your battery and put it back in. (this is easier)
2. Keep hold of the volume down button and switch your phone on.
3. Hboot will start. Navigate to recovery with the vol down button. Press power button to select and enter recovery.
To install a Custom ROM - you will not lose data or apps with this method!
1. Download your chosen ROM by other developers in the development threads and copy the ZIP file to your SD Card ROOT directory
2. Start clockworkmod recovery (instructions above)
3. BACKUP YOUR ROM USING CWM BEFORE ATTEMPTING ROOT! (skip this step if you have already made a backup previously)
4. Navigate to "install zip from sdcard" using the Volume Down button and press select (power button to select)
5. Then select "Choose zip from sdcard"
6. Then select "your_chosen_rom.zip"
7. Then select "Yes - install your_chosen_rom.zip" to confirm
8. Then go back
9. Then reboot.
10. First boot will take quite some time -This is normal, i know you want touch your nice shiny phone but BE PATIENT - ENJOY!
Special Thanks to AlphaRev, unrEVOked Team, Bin4ry & to everyone else that helped with this GUIDE and with S-off and Dazweeja with S-on
TroubleShooting!
signature verification failed in CLOCKWORK
Make sure you have installed Clockwork From Step 2 Above. V 4.0.1.4 specifically for AlphaRevX
1. Load up Clockwork Recovery (See post 1)
2. Navigate and Select "install Zip from SD Card"
3. Select "Toggle Signature Verification". Press it once or twice till you see the message. "Signature Check: DISABLED"
Installation aborted in Clockwork
E:Error in /sdcard/su-2.3.6.3-efgh-signed.zip
(status 0)
Installation Aborted
1. First Try the above method of repeating it 3 times to achieve root. some users are getting installation aborted. but on third attempt rooted successfully
2. Failing that: Download su-2.3.6.1-ef-signed.zip AND su-2.3.6.3-efgh-signed.zip.
3. Place both of them on the root (main folder) of your sd card and flash su-2.3.6.1-ef-signed.zip using Step 3 from post 1. it is likely it may repeat the error above. INSTALLATION ABORTED
4. Flash su-2.3.6.3-efgh-signed.zip now using step 3 in post 1. YOU SHOULD BE NOW ROOTED!
Stuck on White Screen with Green HTC Letters for over 15 minutes or continuously rebooting without starting up
You are not bricked, Whatever you flashed in clockwork didn't flash correctly. Most likely a Rom
This could be due to a bad file, or download error or powering off or pulling the battery part way through. no need to worry
1. Re-download the Rom or file or theme you were trying to flash in clockwork
2. Install again using clockwork. wait till its finished and reboot. you should be cured
3. MAKE sure whatever you are flashing is compatible with the Sensation or made for the Sensation
Revolutionary Hanging on "Method 3"
1. Make sure you have installed all the drivers from above.
2. Please Make Sure you have HTC Sync uninstalled and Droid Explorer uninstalled.
3. Install These Drivers HERE:
4. Basically anything and everything that will allow your phone or other phones to automatically connect or sync to your computer has to be uninstalled
5. Try another Computer or Factory Reset your device as a last resort.
If you are getting root error messages
Some Users acheived root by repeating Step 3 a few times Try this
1. Repeat step 3 at least 3 times or until it installs completely .
2. Download busy box from the market , open it and install the app.
3. Reboot and that should do it , root should be working and WiFi with s off
4. You may get messages telling you it failed to root or installation aborted but reboot and check it with root checker. Many users are told its failed but are actually rooted now
If u want to verify if u have root download the app called root checker it checks for root and for busy box to b installed correctly... if that fails
Try Installing/REINSTALLING SuperUSER and Busybox (or busybox installer) from the market. if it still doesn't work then
Flash a custom Rom as they come Pre-Rooted
Many Tmous users are acheiving root while a few are not. please try all of the above mentioned methods.
Titanium Backup Crashing (when restoring backup)
1. Uninstall and reinstall Titanium backup
2. If that fails reinstall your ROM (Full wipe recommended in clockwork before reflashing rom. Unless you have already made a backup with titanium before. you will lose apps + data)
Titanium Backup not working
The likely Cause of this could there are some files left behind from your temp root. You need to delete the files in /data/bin/ you can do this by
Download Terminal Emulator from the market
open terminal emulator and type:
su
rm -r /data/bin/*
or if you are familiar with using adb: (you can use the adb exe supplied by revolutionary in his tools pack)
adb shell su
adb shell rm -r /data/bin/*
Then reboot into recovery and reapply the su-2.3.6.3-efgh-signed.zip installation. Another User posted this fix as it worked for them
WIFI PROBLEMS (ISOLATED INCIDENTs)
IF YOU ARE EXPERIENCING WIFI ERROR.
Currently the only way to fix this is to flash Stock Rom again or Custom Rom.
1. Follow step 4 above in post 1
2. OR You can flash a custom Rom from Clockwork. LeeDroids Rom is close to Stock and confirmed to be working on a Tmous Sensation
Any problems or fixes PM me please
[GUIDE] TO UNLOCK YOUR SENSATION FREE - WORKING FOR EVERY SENSATION (noobproof)
Method 1 was discovered by a noob - Dav22. Dazweeja came up with a simple ADB command. Skygear for working it in Terminal Emulator
Method 2 was discovered by sieempi (Links at the bottom), STRING: NOT FOUND workaround found by jackmonter5
Big thanks to xplod4202. Risked his Sensation to see if Methd 2 was safe for us all.
And The simple guide : xl Viper lx : I am simply doing what i do best. getting you a noobproof guide and also simplifying the adb/terminal code
All of us will take credit for the collaborating and making of this thread to help everyone unlock with no cost. What???.....Yes thats right......We broke the FTSE index by providing free unlocks! lol
Also 9 people who voted no in the poll, ad voted before we found method 2 which unlocks every sensation
METHOD 1 - USE THIS FIRST
The SIM-Unlock code location for some sensation's (NOT ALL) has been found and confirmed to work for the few users who tested it. Use method 1 below to find your unlock code
(Method 1 ADB guide in post 2 if you don't want to use Terminal Emulator or you just want to use ADB)
Requirements:
-Rooted simlocked Sensation - Enable USB debugging in Settings > Application ->Development
-Terminal Emulator (Download free from the market) or click here to download and install into your phone
Your IMEI Number (Dial "*#06#" in phone keypad to get it)
GUIDE - Method 1
1. Download Terminal Emulator from the market if you havent already done so and Run it. This should bring you a blue screen. Full screen.
2. enter the command "SU".
3. Click allow when Super user pop up appears to give it root access. (If your keyboard disappears, keep hold of menu button to bring it back up)
4. enter the command "strings -n 8 /dev/block/mmcblk0p6"
5. This should give Output a bunch of numbers like in the screenshot! IF IT SAYS STRING: NOT FOUND MOVE TO POST 2 AND USE ADB!
6. The 8 digit number above your IMEI number is your unlock code. See post 2 on how to enter it.
IF it only brings you a date above your IMEI. Then the unlock code is not present in your device. Move to Method 2
GUIDE - Method 2 - USE IF METHOD 1 FAILED!
Revolutionary achieved radio S-OFF for Sensation (among other devices) which means you can practically do whatever you want with your phone (like actually owning it). This means it makes it vulnerable to all sorts of schemes including sim-unlock. The following method is quite efficient and easy to do and can be done with the need for a computer!
Requirements:
-Rooted simlocked Sensation!
-Clockwork Recovery or Revolutionary Recovery - NEEDED FOR NANDROID BACKUP
-Titanium Backup (Download from the market if you don't have it) - YOU ONLY NEED THIS IF YOU DONT WANT TO OR CAN'T NANDROID BACKUP
WARNING!!!
Backup all your settings/apps/sms/network/APN/Data etc.
Using this method to unlock will wipe your data and apps too! (Factory Resets in other words)
But it's this method that actually resets some other things including your sim-lock status.
Guide - Method 2
1. MAKE A NANDROID BACKUP USING RECOVERY - (Completely switch off your phone, Press Volume down + Power button to get into bootloader, Volume down to recovery then press power button to get into Recovery. Volume down to "Backup and Restore" in recovery. Press Power to backup and your done!
(Make a backup in Titanium backup if you don't want to or can't nandroid backup. Menu > BAtch >Backup systems data + Apps with data)
2. Download PG58DIAG for the Sensation HERE or FROM MULTIUPLOAD
3. Copy the PG58DIAG file into the Root folder of your SD card (The main Folder of your Memory Card)
4. Turn off your phone Fully and reboot into the Bootloader/HBOOT screen (see post 2 on how to get to bootloader screen)
5. Press Volume Down to Enter DIAG - Place the phone horizontally when it asks you too. (Flat)
6. Press power button to select "Clean S58 Data
7. Press power again to "clean S58 Data".
8. POW - your unlocked! Try a SIM card from a different provider!
9. Delete the file from your SD Card (Delete PG58DIAG) and REBOOT!!
Your phone Will set up for the first time, go through it all till you get to your home screen
10. Go back into recovery and restore nandroid backup. same method as step 1 above. but instead of backup, you use restore feature
(Use Titanium Backup to restore if you used it to backup instead of Nandroid backup)(Menu > Batch > Restore System Data + Apps with user data)
Now you’re free to go! Bear in mind, though, in certain circumstances you will lose your data connectivity or network signal. You’ll just need to check your APN, network type etc. and re-enter them; Just run the nandroid restore to get everything back
Thanks to Dav22. for discovery of method 1
Dazweeja for his simple Code to find the unlock
sieempi for Method 2.
Thanks to Team Revolutionary for PG58DIAG and S-off
Don't forget to CLICK THANKS, VOTE and RATE if this guide worked for you.
don't forget to thank the above users too by clicking the links
Method 1 ADB GUIDE
METHOD 1 - ADB GUIDE- Skip steps 1 to 5! if you already have already got ADB and can get to the ADB folder through command prompt/Terminal. If your not sure follow all the steps
1. Download adb tools here: download for Windows or Linux or from attachments in the Sensation S-off guide
2. On your PC click on your local disk C: Drive (or D: drive for some) (WINDOWS users: Start > My computer > Local Disk (C)
3. Create a new folder called "adb" and extract the files from adb.zip into it. Make sure it doesn't create another folder in the adb folder when extracting
4. open command prompt (or terminal for linux) and type "cd" "followed by the path to your adb folder" (windows users can type "cd C:\adb")
5.a Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (Ensure usb debugging is on settings) OR!!!!
[ IF YOU GOT THE STRING:NOT FOUND ERROR IN METHOD 1 (terminal Emulator) REBOOT INTO RECOVERY AND CONNECT YOUR USB AND CONTINUE (Turn off your phone completely, volume down + power button, then select recovery to get into it!) ]
6. enter the command "adb shell". Your phone should display a hash sign [#] (if it doesn't then you are not rooted! - GO ROOT)
7. enter the command "SU".
8. enter the command "strings -n 8 /dev/block/mmcblk0p6"
9. This should output a bunch of details as shown in the screenshot below
10. The 8 digit number above your IMEI is your unlock code. See post 2 on how to enter it. IF it only brings you a date and your IMEI. Then the unlock code is not present in your device. Move to Method 2 in Post 1
To unlock your GSM phone with the unlock code follow these simple steps:
1. Power on your Sensation with a SIM card from an unsupported network/carrier/provider.
2. If asked, enter the PIN code of your SIM Card.
3. Enter unlock code when prompted!
FOR DUAL CDMA
How to enter the code in dual CDMA - GSM/LTE HTC Phones
1. Power on your Sensation with a SIM card from an unsupported network/carrier/provider.
2. Phone will tell you to insert an allowed SIM card and that the phone will switch back to CDMA mode.
3. Click OK.
4. Click green button to get to the main screen of the phone.
5. Click on settings.
6. Click on all settings.
7. In the personal tab click on security.
8. The phone will ask you to enter the unlock code. Enter it. Done
FAQ - Frequently Asked Questions
Recovery Charging Issue
Clockwork recovery v4.0.1.4 with the purple writing suplied by revolutionary and 4.1.0.5 from rom manager both have an issue with charging. Your phone will not charge if you turn it off.
So if you flashed it via revolutionary.exe or in post one before i before i uploaded the new updated one.
Post one is now updated with the new clockwork recovery 4.0.1.4 with the blue writing that does not have charging issues.
Just follow Step 2 above to flash the new clockwork Recovery v4.0.1.4 and this will fix your charging issues.
the new recovery is orange while the old one was purple
What is a noob?
A noob is someone new to XDA or new to the device and its methods of rooting/customizing. Its not bad being a noob. we we're all their at one stage. i was a noob for winmo in July 2009. I was a noob for Android in October 2010. you tend to learn everything pretty fast. easy to work with android is.
What is S-OFF?
S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC devices is S-ON (write protected), which means that neither can you access certain areas of the system nor can you guarantee a permanent root
Do i need Rooting?
An unrooted device is like logging onto the guest account of windows, you can do many things, just not everything
Think of Acquiring root as having Administrator Access on the device, so you can install/modify/fix/break anything you want.
What does clockwork Recovery do?
Clockwork allows you to flash Unofficial Roms and Themes via zip files on your SD card, also you can make backups of your current rom and wipe certain types of memory. (User data, system, boot, cache, dalvik cache)
What is flashing? (showing your bits off in public?) NO!
Flashing refers to Downloading themes or apps or Roms onto your SD Card and then installing them using clockwork or any other utility where the phones Operating System is modified
the program sees my phone but my beta key isn't working.
leyvatron said:
the program sees my phone but my beta key isn't working.
Click to expand...
Click to collapse
Fill out the form again correctly and copy paste doesnt work so you gotta make sure you type it letter for letter, it is case sensitive
leyvatron said:
the program sees my phone but my beta key isn't working.
Click to expand...
Click to collapse
its Case-Sensitive
thanks a lot for the guide. i was confused about one thing. you say, "To get your Hboot Version, make sure fastboot is disabled". where exactly do we make sure that fastboot is disabled? is that a setting in android? i thought it had to do with recovery... thanks again!
greves1 said:
thanks a lot for the guide. i was confused about one thing. you say, "To get your Hboot Version, make sure fastboot is disabled". where exactly do we make sure that fastboot is disabled? is that a setting in android? i thought it had to do with recovery... thanks again!
Click to expand...
Click to collapse
its when your turn off your phone and turn it back on, its comes on within seconds,
i have fastboot enabled but the easiest way possible mate is just take out the battery and put it back in, that way you will know definitely its off, not on hibernated
Thanks for the guide!
Just got S-OFF on my phone and installed ClockworkMod
Psyed said:
Thanks for the guide!
Just got S-OFF on my phone and installed ClockworkMod
Click to expand...
Click to collapse
Me too. going to try and flash Leedroid in half an hour
Glad it helped you too, orignally i booted into fastboot and was wondering why it wouldnt recognise my phone till i saw instructions buried in the long thread, rather than people sifting through it, i thought its better if i make it into its own thread
sundar_amn said:
Will this work on T-Mobile US Sensation?
Click to expand...
Click to collapse
ikhzter said:
Me too. going to try and flash Leedroid in half an hour
Glad it helped you too. dont know what Mgormans problem was, orignally i booted into fastboot and was wondering why it wouldnt recognise my phone till i saw instructions buried in the long thread, rather than people sifting through it, i thought its better if i make it into its own thread
Click to expand...
Click to collapse
Too late to flash a rom right now. I'll fix then after waking up... whenever later on today
I had no problem using copy paste ind the command prompt.
My windows is not in english but I think it is something like this in a english windows:
push the cmd icon at the top on the cmd running, edit > paste
/henrik
henhoy said:
I had no problem using copy paste ind the command prompt.
My windows is not in english but I think it is something like this in a english windows:
push the cmd icon at the top on the cmd running, edit > paste
/henrik
Click to expand...
Click to collapse
oh yeh i forgot you could do that, what can i say, too excited about S-OFF
AWESOME !!!!!!!!!!!!!!!!!!!
Yessssssssssssssssssssssssssssssssssssssssssssssssssssss !!!!!!!!!!!!!!!!!! I love youuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
my revolutionary.exe is stuck on: acquiring root (method 3)...
This comes up after i put in the beta key, it says accepted.
i do have usb debugging on, on put it on htc sync
i have an .0011 hboot so it supported, whats the problem?
shatred said:
my revolutionary.exe is stuck on: acquiring root (method 3)...
This comes up after i put in the beta key, it says accepted.
i do have usb debugging on, on put it on htc sync
i have an .0011 hboot so it supported, whats the problem?
Click to expand...
Click to collapse
you have usb debuging enabled???
i have the same version of bootloader and for me it stucks at "waiting for fastboot"
undplug and plug phone, while in fastboot doesnt help, driver is also installed correctly! Anybody knows a solution for that?
Phily757 said:
you have usb debuging enabled???
i have the same version of bootloader and for me it stucks at "waiting for fastboot"
undplug and plug phone, while in fastboot doesnt help, driver is also installed correctly! Anybody knows a solution for that?
Click to expand...
Click to collapse
but when i select it seeks my computer for htc sync, but i uninstalled it like the first post said it needed to. so after about 20 seconds it says that htc sync cannot be found on my computer. is this a good sign?..
Hello, newb here (for now)
My nephew rooted my Best Buy Nexus S (AT&T) and installed Cyanogen 7, it works great, but I think I have a defective screen and I need to exchange it at BestBuy. (Screen Flickers/flashes at times)
The kid is gone back home and I need to get back to stock. Here's where I am right now:
- I launch Rom Manager (4.3.3.0) go to "Download ROM" and scroll down to "stock images" and download Nexus S 2.3.3, it downloads.
- Then the "Rom Pre-Installation" screen comes up and I choose all three options (backup, Wipe data/cache, Wipe Dalvik Cache)
- I press "OK" to reboot and get the Google Screen with the lock and it just stays there (I waited about 10 minutes)
- I pulled the battery, power on with VOL up and get to "Fastboot mode" (I think... screen with choices and android character?)
Anyhow, I've tried every option here and i cannot get it to load anything to replace the Cyanogen 7 Mod.
Maybe I need a stock AT&T Image? The one from Rom Manager is wrong?
With all of that said, I'm using a MAC.
Any pointers or suggestions?
Thanks!
I think my issue is that it will not go into recovery mode. When I choose recovery, ut goes to the google screen with the lock at the bottom and never gets past that.
For whatever reason, using ROM Manager to flash a recovery onto the Nexus S makes it disappear. I did this myself and it made the recovery image vanish.
So use fastboot to re-flash the recovery image.
Download this file: http://download.clockworkmod.com/recoveries/recovery-clockwork-4.0.0.2-crespo.img
Rename it to "recovery.img" and copy it into the "platform-tools" folder.
Plug the phone into your PC, and boot it into fastboot. Open a command prompt and move to the platform-tools folder, and type "fastboot flash recovery recovery.img."
When it's done, reboot fastboot and when fastboot comes back up, scroll down to recovery and select it. It should boot into ClockworkMod Recovery.
Thanks for the reply!
How do I get to the internal storage on the phone? (I'm on a Mac) Plugging it in, I only see the memory card
Cameron_C said:
Thanks for the reply!
How do I get to the internal storage on the phone? (I'm on a Mac) Plugging it in, I only see the memory card
Click to expand...
Click to collapse
Access your phone's memory card from Mac and enter sdcard/ directory. sdcard/ is your internal storage where you should put your ROM, if you decide to flash ROM or any .zip file from CWM's recovery.
Hi all.
I have an Spanish wifi-only Xoom (MZ604) and I'm tired of waiting for motorola's updates (still in Honeycomb 3.2!!!).
I want to test either EOS3 (Android 4.1.1) or EOS2 (Android 4.0.4) custom roms. I've read almost all tutoriales but I still have some doubts about the procedures... could anybody check this message and warn me if I'm going to do something wrong?
DOUBT 1.- Key shortcuts in Xoom
Can anybody tell me the existing key combinations in Xoom? I only know about POWER+VOL_UP key to enter bootloader mode.
DOUBT 2.- How to install CWM.
If I understand it correctly, both EOS2 and EOS3 should be installed from CWM recovery...
Is the following procedure OK?
- Some tutorials say that you have to be root first to install CWM ... is it really needed? Can't be done directly with ADB?
- Install Android SDK in the PC.
- Download eos-recovery-r6.img or eos-recovery-r6-softkeys.img
- Connect XOOM to PC with the original USB cable.
- Reboot XOOM in bootloader mode (Power + VolUp)
- Exec adb and then:
fastboot oem unlock <---- is this a requirement?
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
DOUBT 3.- How to install or upgrade EOS 2 or 3 ROM?
Is the following procedure OK?
- Download ROM and gapps zip files.
- Start XOOM in recovery mode (CWM) -> How to do this?
- Do a nandroid backup.
- Wipe everything (data, cache, dalvik, etc)
- Install ROM zip.
- Install gapps zip.
- No need to do anything to root it, the rom is already rooted <-- is that right?
- Reboot
Is everything OK? Did I miss anything? Do I need to root my 3.2 install before any other step? Do I have to do the "oen unlock"?
Thanks.
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Sent from my MZ601 using Tapatalk 2
wesamothman said:
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Click to expand...
Click to collapse
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
NoP_Compiler said:
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
Click to expand...
Click to collapse
Since you are going to install EOS Jellybean, I don't advise you with CWM. A different recovery made by EOS team is better through which you can do nandroid backup and other stuff...
Here is what you need to do step by step...
Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd or somewhere accessible, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
• GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
• ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 30 - 45 seconds). The more apps you install, the slower it boots...
That is pretty much it. Enjoy, I hope this helps you
Of course it helps! In fact, a lot.
When I was talking about CRW I really meant EOS recovery (which is based in CRW itself IIRC).
The only that I can't understand is why some tutorials ask me to root the tablet before doing all this process...
Anyway, I think I'm finally going with EOS3 + EOS recovery if nobody here advices me to flash EOS 2 instead...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
I will be away for couple of hours, will answer your questions all as soon as I get back...
Sent from my MZ601 using Tapatalk 2
NoP_Compiler said:
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
Click to expand...
Click to collapse
Alright, eos jelly bean is fully stable, ,such faster and smoother than ICS. You want feel the difference until you try it... however, eos ICS is stable too and has more features and addons by eos because it has been there under dev for longer time, jellybean is new, one month old only... I recommend you to go for jellybean, and try and see for yourself. At anytime you can flash ICS since your Xoom booloader is already unlooked and recovery installed, you can do that by just wiping data and flash ICS zip. That is as simple as that...
For Motorola drivers on Linux, I think it is not needed, adb is built in with Linux, but I am not sure as I haven't tried that yet.
For eos recovery, don't use the soft key version, use the normal one...
with this recovery, you will be safe, because at all times, your external SD is accessible in emergencies...
Hope that helps...
Sent from my MZ601 using Tapatalk 2
You have it down perfectly. Just to recap.
1. Set up android sdk. Download recovery image and store in sdk folder. Download rom/gapps and store on tablet.
2. Boot into fastboot (power + volume up).
3. fastboot oem unlock (required). This will wipe all data.
4. fastboot flash recovery recovery.img (whatever recovery you decide to go with, I recommend eos soft key).
5. boot into recovery, make nandroid backup, flash rom of your choice + gapps if necessary.
People tie rooting to flashing custom roms because many people have become so reliant on apps like rom manager that flash the recovery for you, an app that requires root access. I never rooted my galaxy nexus or xoom. I simply flashed recoveries in fastboot and proceeded to flash roms in recovery.
It actually bothers me how some have become so reliant on root access to flash roms. It has gotten to a point where many people genuinely don't know the difference and that, to me, says they don't really understand what it is they're doing, which will lead to issues should they ever need to troubleshoot.
You seem to have it down well though. Good luck.
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Good luck...
Sent from my MZ601 using Tapatalk 2
Ok. EOS6-RECOVERY installed correctly. There are a couple of mistakes and some missing info in the "tutorial", so I'm going to change it to help future users:
I finally did it under Windows because almost all tutorials in Internet explain all the possible problems that you can find in Windows, and it's a "too risky" task for me to "experiment" by myself.
PART 1 .- HOW TO INSTALL EOS6 RECOVERY:
Originally quoted from wesamothman:
First, download the above ROM and GAPPs and put them onto your xoom external SD card. Put them in a folder called /sources/ of your external sd card.
- Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
- Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
- GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
- ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
And the most important:
- Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
Check that the md5sum of this file is correct and matches with the one provided in the download page. This is the most important file because it will allow to install the CWM recovery system and it's CRITICAL that the file is not corrupted.
Steps:
a.- Install in your PC the lastest JavaSE JDK from Oracle's website.
b.- Install in yout PC Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
c.- Enable USB debugging in the XOOM (in settings, development).
d.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
e.- Plug the Xoom to your laptop.
f.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices", if you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device. After a While, Windows will fix it and "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
NO NEED TO DO THIS:
NO -> 1. Power off your XOOM device.
NO -> 2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
Because the first command show after this lines: (adb reboot bootloader) won't work while in fastboot. Only "fastboot" commands work in fastboot mode. If you try that command in fastboot mode, it will say "Error: device not found".
So just, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because WIndows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot"
Issue the following command to unlock the Xoom (you'll void the warranty):
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option.
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc and enable again USB debugging and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the file eos-recovery-r6.img to the android-sdk/platform-tools/ folder and execute:
Code:
fastboot flash recovery eos-recovery-r6.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery eos-recovery-r6.img
sending 'recovery' (4114 KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
You xoom will start again in Android OS mode. Execute:
Code:
adb reboot recovery
And you'll start the nice EOS Recovery (based on Clockworld Mod) recovery system.
You can also do it manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE CWM / EOS RECOVERY
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
PART 3 .- HOW TO INSTALL EOS3 ROM:
Under recovery mode (abd reboot recovery), do:
- Backup/restore -> backup to external SD.
- Wipe data/factory reset
- Wipe cache
- Advanced -> Wipe Dalvik Cache
- Advanced -> Wipe Battery Stats
- Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
- Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
- Reboot
- Enjoy your new rom!
Very well detailed... great...thx.
Sent from my MZ601 using Tapatalk 2
wesamothman said:
Very well detailed... great...thx.
Click to expand...
Click to collapse
No... thank you for the initial info
After restarting, I have a notification about a ROM update (128). The ROM-management app allows me to download it or apply a incremental update...
Do you know if that second option (incremental update) is safe?
Anyway, I can just always do a Nandroid and test it ... having CWM I can't loose never anything, right?
Of course it is safe, I use it a lot. Just boot into recovery now by long press on power menu, select reboot, recovery,
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Sent from my MZ601 using Tapatalk 2
wesamothman said:
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Click to expand...
Click to collapse
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
NoP_Compiler said:
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Click to expand...
Click to collapse
Worth noting that to use fastboot and stuff, you only really need to install the Android SDK Platform-tools, maybe the regular SDK tools as well, I can't remember.
You don't need to install all the other stuff.
---------- Post added at 08:02 AM ---------- Previous post was at 08:01 AM ----------
NoP_Compiler said:
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
Click to expand...
Click to collapse
Yes, any updates/mods/gapps updates need to be flashed in recovery.
Unless specified that its necessary by devs though, you don't need to wipe anything. I've been on JB nightlies from day 1 and I haven't wiped cache or anything since the initial wipe.
Is it possible to...
a.- change the system font (too 'light' in my xoom).
b.- disable jellybean UI animations...
?
I don't know about question a, though I'm sure its possible.
As for question b, try a different launcher. Apex launcher and nova launcher are both popular Android 4.0+ launchers (check play store for them).
Eos ROM,m settings, developer options, disable animations and transitions
Sent from my MZ601 using Tapatalk 2
Since i am afraid, that my Guide will dissapear in the other Thread,
i post this guide in a new Thread !
I have just uploaded a collection of, how i have named it, - s60 essentials - there are ALL files included to flash stock, update to .033, flash twrp recovery and root.
(this is for Win7 x86, you have to check if it works for other versions yourself, sy..)
Here is my collection
HOW TO.... Stock, Update, custom recovery and root your s60 !!!!
Disclaimer: if you brick your phone, it's your fault, i have tested this way of rooting my s60 now for a several times and it works 100%
SO READ TWICE, CHECK TWICE, BEFORE YOU CLICK ONCE !!!!! i will not take any responsibility !!!
Thanks to everybody who contributed here in this thread (Cesarq, OpenMinded, Tuschi, BetonJohn, etc.......) the software in the link
is the collected data, freely available in the net and linked in the original Thread several times, i have only bundled one package and wrote
this, hopefully usefull guide.
in principle do as follows: (I will only explain once how to sideload or load via recovery, afterwards i will only state what kind and what file)
Prerequists
- install USB drivers (for recovery and adb)
- install "minimal ADB and fastboot"
- copy the two updates (update032 & update033) into the folder, where you have installed "minimal ADB and fastboot" (makes live easier later)
- install QPST (the version of QPST is the one from Androidmtk and should be virusfree
(The version of QFIL in my collection is the one without reboot, so you have to reset/reboot your phone manually (resetbutton below hatchdoor on your phone) whenever
stated in this guide.
- format micro SD card in fat32 ! and copy SuperSU.zip onto it.
- connect a WORKING USB cable to your phone (Not to your PC atm !!!)
getting twrp (for saving your old firmware only)
- power off phone.
- start minimal adb on your PC
- start QFIL (part of QPST) on your PC
- press VOL+ & VOL- simultanousely and connect phone with PC (it will vibrate once, top right LED starts blinking red, screen stays black) - DOWNLOAD MODE -
(just in case: to leave Download mode, press and hold power button for apprx. 15 seconds)
- as soon as you connect your phone to the PC, QFIL should show the Phone/port in the topline allready, if not, either try to manually select the port, or you probably still have
a problem with the USB drivers !
- tick in QFIL Flat Build (top left)
- QFIL - select Programmer, "browse" to the saved location of "update-twrp-recovery-nobootpatch" and select the "prog_emmc.blablabla...mbn" file and doubleclick
- QFIL - "load XML" ,select rawprogramm, doubleclick, select patch0, doubleclick
- QFIL - click on "download"
- if everything was OK up till now, it should start download - BE PATIENT- and read the status window on QFIL, when it shows "finish download"....
- disconnect phone from PC
- press and hold simultanousely POWER and VOL+ and use a small tool to push the reset button on the phone under the hatch, while still pressing Power and Vol+ !
- the phone should now be in twrp recovery. If so, do a full backup now to your (allready inserted and fat32 formatted) microSD card!!!
when done
- Power off your phone !
flashing stock 31.02
- enter download mode again (Vol+ & Vol-, connect phone to PC.......)
- this time in QFIL, browse in programmer path to "s60_stockFW_31.02" and select the programmer from there
- load XML's (the onces that belong to Stock31.02)
- start download... this will take a while !!!! BE PATIENT !!!!
- when QFIL status window shows finish download, push the reset button on the phone and let it reboot.
- it is normal, that the phone should restart itself 2, maximum 3 times at the first start, but sometimes it ends up in a bootloop (Cat Logo, reboot, CAT logo, reboot, etc, etc, .......)
(The bootloop mainly happens, if you clear, in twrp recovery, the whole OS, but that's no issue either...)
- if it ends up in a bootloop, no worries, just continue ! Believe me, i did the process now several times ! )
you are back on stock 31.02 !
-Power off your phone again
Updating to 032
- bring up minimal ADB sideload on your PC (start it, if not allready done in previous step (getting twrp)).
- press and hold POWER and VOL+ button on your phone - RECOVERY MODE -
- when in stock recovery select (with Volume keys) "adb sideload" and click the Powerbutton
- connect your phone to the PC
- on PC, type into the black ADB Terminal window "adb sideload update032.zip" and hit enter
- if drivers are there, phone will start downloading the update now.
- when complete, select clear cache, and clear data then reboot your phone.
- again, same as in the step (flashing stock), if bootloop, no worries, just continue, if it boots up, let it boot up and then..
you're on 032 now
- Power off the phone again
Updating to 033
- do the same steps as described under "Updating to 032" only difference, type in adb window " adb sideload update033.zip"
After updating to 033 your phone should boot up normally now, NO MORE BOOTLOOP !
getting twrp
- this is the same step as above "getting twrp" only difference, this time, no backup needed and...
- when in twrp-recovery, select "install" browse to your micro SD-card, and...
- install SuperSU.zip from SDcard.
- once more, clear cache and data and reboot.
The phone should boot up now, you should be on FW 033, with custom recovery and root !!!
That's all !!!
Would a TWRP or fastboot flashable stock recovery let us apply future OTA updates without wiping and starting from stock 031 if we're using systemless root like Magisk?
From stock recovery you can reboot to bootloader which puts us in fastboot (you can select boot mode with Vol +/-), so I'm thinking if we could boot TWRP from fastboot (without flashing, obviously), we could back up the stock recovery. Then when the next update comes around, we flash stock recovery back, apply the update, then reflash TWRP.
I tried fastboot boot recovery.img from update-twrp-recovery-nobootpatch but I got
FAILED (remote: unknown command)
and rebooting into recovery from there just got me stock recovery which makes sense.
QCN please
Hi guys, can anyone share me QCN backup of S60 because i've lost it! Thanks.
Last update for Android 6.0 was from 766 days ago.
Any suggestions on how to patch?
Thanks a million