HTC One Dev edition root question - One (M7) Q&A, Help & Troubleshooting

Hey guys, I have been looking through the forums and have not found an answer to my confusion. I have the dev edition in the US, and I am not sure what steps to follow to root and unlock the bootloader. I don't know the difference between unlocked and s-off, so I am not sure where to start.
I have rooted a number of phones before, but they were always carrier versions so I knew exactly where to start from. Any direction would be great, and I apologize if this has been asked 50 times before.
Sent from my HTC One using Tapatalk 2

Mindstar1 said:
Hey guys, I have been looking through the forums and have not found an answer to my confusion. I have the dev edition in the US, and I am not sure what steps to follow to root and unlock the bootloader. I don't know the difference between unlocked and s-off, so I am not sure where to start.
I have rooted a number of phones before, but they were always carrier versions so I knew exactly where to start from. Any direction would be great, and I apologize if this has been asked 50 times before.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
What version of hboot do you have? If you have 1.44.0000 you can do S-Off and Unlock the bootloader using Revone
If you have 1.54.0000 you can't do S-Off

Dev edition comes with an unlocked bootloader, all you would need to do is flash a custom recovery,twrp will root the device for you,simplest way if JUST looking for root

Dev edition comes with an unlocked bootloader, all you would need to do is flash a custom recovery,twrp will root the device for you,simplest way if JUST looking for root
Click to expand...
Click to collapse
Pardon my ignorance, but what would I gain by looking for more than root?
Sent from my HTC One using Tapatalk 2

What version of hboot do you have? If you have 1.44.0000 you can do S-Off and Unlock the bootloader using Revone
If you have 1.54.0000 you can't do S-Off
Click to expand...
Click to collapse
How do I check which hboot I have?
Sent from my HTC One using Tapatalk 2

At some point you will need a USB cable and a computer (with the android sdk installed on it) to make any of the changes you are contemplating, and there are commands you can run from your computer's terminal app (while the phone is connected to the computer via USB) that tell you what HBOOT you have, but for purely informational purposes, the is a non- technical way to determine your HBOOT:
- power off phone all the way (make sure "fast boot" is turned off in settings..power)
-hold down volume-down and power buttons simultaneously for several seconds until screen turns white
- HBOOT version is clearly visible from this screen. Write down every version number or other info that you see for future reference. Consider taking a photo of this screen.
-to leave this environment, use volume key to change the highlighted selection, and the power button to actually invoke it: select "fastboot" then "reboot" to reboot gracefully
Sent from my HTC One using xda app-developers app

NxNW said:
At some point you will need a USB cable and a computer (with the android sdk installed on it) to make any of the changes you are contemplating, and there are commands you can run from your computer's terminal app (while the phone is connected to the computer via USB) that tell you what HBOOT you have, but for purely informational purposes, the is a non- technical way to determine your HBOOT:
- power off phone all the way (make sure "fast boot" is turned off in settings..power)
-hold down volume-down and power buttons simultaneously for several seconds until screen turns white
- HBOOT version is clearly visible from this screen. Write down every version number or other info that you see for future reference. Consider taking a photo of this screen.
-to leave this environment, use volume key to change the highlighted selection, and the power button to actually invoke it: select "fastboot" then "reboot" to reboot gracefully
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
OK, I just did what you said and the HBOOT is 1.44.0000. So, based on what was said earlier, I am good to do the Revone option? If I do Revone, what am I missing out on compared to any other option? Thanks for the help!

Go for it. I had 1.44 and eventually got revone to work. [ there is an undocumented tip that may help you (power off the device "hard", ie hold down power button for like 15 or 20 seconds, between each step), but you'll want to discuss that and any other issues you encounter with revone in the revone thread of course. ] I cant think of any negative side effects that i have experienced. And as those with hboot 1.55 have discovered, its always good to get S-OFF while you can. You may not have the chance later. Good luck.

Well obviously your looking to flash thngs,there are many options,this is why i said if you were just looking to root the device
Mindstar1 said:
Pardon my ignorance, but what would I gain by looking for more than root?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse

Wonders_Never_Cease said:
Well obviously your looking to flash thngs,there are many options,this is why i said if you were just looking to root the device
Click to expand...
Click to collapse
Yeah, I want to flash. If all I do is root, am I still able to flash other ROMs? I can never keep straight what each of the different processes do.

NxNW said:
Go for it. I had 1.44 and eventually got revone to work. [ there is an undocumented tip that may help you (power off the device "hard", ie hold down power button for like 15 or 20 seconds, between each step), but you'll want to discuss that and any other issues you encounter with revone in the revone thread of course. ] I cant think of any negative side effects that i have experienced. And as those with hboot 1.55 have discovered, its always good to get S-OFF while you can. You may not have the chance later. Good luck.
Click to expand...
Click to collapse
Whats the deal with Revone and the HTC One tool kit here http://forum.xda-developers.com/showthread.php?t=2183942. My goal is to flash 4.2.2 roms and soon 4.3, so would I want to do both or just Revone.

Mindstar1 said:
Whats the deal with Revone and the HTC One tool kit here http://forum.xda-developers.com/showthread.php?t=2183942.
Click to expand...
Click to collapse
Here is an old article that covers some basic terminology, specifically geared toward HTC phones. Much of it applies to the HTC One (although the stuff about the difficulty flashing kernels in recovery does not pertain- we have it much easier).
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
Also check out this famous post https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
The second article clearly states you don't need S-Off to flash ROMs, but the first article also notes those who are going through the trouble of unlocking/rooting generally do S-OFF while they are at it.
As for hasoon's toolkit, I personally have avoided it. There are other ways to root.
For instance, if you install the latest version of a custom recovery such as TWRP or CWM, they actually give you a menu option to root whatever ROM is currently installed.
Check back again after you've gotten caught up on your reading.

NxNW said:
Here is an old article that covers some basic terminology, specifically geared toward HTC phones. Much of it applies to the HTC One (although the stuff about the difficulty flashing kernels in recovery does not pertain- we have it much easier).
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
Also check out this famous post https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
The second article clearly states you don't need S-Off to flash ROMs, but the first article also notes those who are going through the trouble of unlocking/rooting generally do S-OFF while they are at it.
As for hasoon's toolkit, I personally have avoided it. There are other ways to root.
For instance, if you install the latest version of a custom recovery such as TWRP or CWM, they actually give you a menu option to root whatever ROM is currently installed.
Check back again after you've gotten caught up on your reading.
Click to expand...
Click to collapse
Its funny, I came across the first article while looking for answers while I waited for your response. I never mess with radios so S-Off is not really important to me. The second article was even better and more clear so I think I know where I am now.
The last question for you is what you would suggest I use for the most trouble free rooting process. I am looking for a pretty low impact route, and you did seem to imply that it took some work to get revone working for you. The toolkit seems to be a good way to go, but it also says that it unlocks the boot, which I already have with the dev edition. Will that be a problem if the process tries to unlock an already unlocked phone?

Ok one last reading assignment, a good guide from the guy who does ARHD:
Read http://forum.xda-developers.com/showthread.php?t=2265618
For your case, my interpretation of his guide would go like this:
The dev edition came unlocked. A lot of "rooting guides" spend a long time explaining how to unlock since they assume you are not already. but if you *are* unlocked already then any time you stumble across any procedure that involves htcdev.com or "get identifier token" etc you can ignore it.
[If, at some time in the future, someone persuades you to "re-lock" your bootloader for some reason (and as far as i'm concerned there are very few good ones), fine, it won;t hurt anything, but later on if you ever wanted to be unlocked again you would need to go to htcdev.com and follow all those steps to re - un - lock your bootloader. but for now, you're unlocked, life is good.]
with an unlocked bootloader, you can flash a custom recovery.
you want to do this.
using a custom recovery is the simplest and easiest way to flash ROMs going forward.
the most reliable recovery available on the One is CWM non-touch version. so go to http://d-h.st/users/flyhalf205/?fld_id=11322#files and find a file with the highest version number (currently 6.0.x something) that does not say "touch" in it.
The basic steps to loading a custom recovery are
- make sure phone's bootloader is unlocked (with stock dev edition obviously you are already set)
- make sure your computer has android sdk installed and you know where the fastboot executable is
- once you have the latest recovery zip from location above, check its md5, and then rename it something simple like recovery.img and place it in the same folder as your fastboot executable
- on your phone, make sure "fast boot" feature is turned off
- boot phone into HBOOT then Fastboot
(in case it is not obvious, connect your phone now via USB and type the necessary commands into a terminal emulator on the computer)
- while phone is in fastboot, use command "fastboot erase cache"
- while phone is in fastboot, use command "fastboot flash recovery recovery.img" where recovery.img is the name you chose above
at this point you should be able to reboot the phone into your new recovery and have a look around.
first step is always make a backup (known as a "nandroid" backup).
if your goal was to root your existing ROM, then you don;t actually have to do the steps in the guide i linked to above anymore: as soon as you try to exit CWM it will notice you are not already rooted and prompt you if you want to root it.
But if you want to do it the old fashioned way where you go and flash your own super user zip and other useful files that go with it, just refer back to the guide above. If the crucial link to the "rooting tools" is still broken, let me paste it again for you here http://www.androidrevolution.nl/dow...le=Android_Revolution_HD_Root_and_BusyBox.zip
I'll let you read up on how to "flash a zip from recovery". It should be pretty straightforward. (download zip and put zip somewhere on phone, reboot into recovery, say you want to flash a zip, navigate to where it is on the phone, start flash, profit)
Once you have an unlocked bootloader, you can flash a custom recovery
Once you have a custom recovery, you can
- root an existing rom and/or
- flash a custom rom compatible with your setup, presumably one with root baked in
Once you have root on any rom, you can run titanium, wireless tether etc.
Hopefully this is enough to get you started down the right path.

NxNW said:
Ok one last reading assignment, a good guide from the guy who does ARHD:
Read http://forum.xda-developers.com/showthread.php?t=2265618
For your case, my interpretation of his guide would go like this:
The dev edition came unlocked. A lot of "rooting guides" spend a long time explaining how to unlock since they assume you are not already. but if you *are* unlocked already then any time you stumble across any procedure that involves htcdev.com or "get identifier token" etc you can ignore it.
[If, at some time in the future, someone persuades you to "re-lock" your bootloader for some reason (and as far as i'm concerned there are very few good ones), fine, it won;t hurt anything, but later on if you ever wanted to be unlocked again you would need to go to htcdev.com and follow all those steps to re - un - lock your bootloader. but for now, you're unlocked, life is good.]
with an unlocked bootloader, you can flash a custom recovery.
you want to do this.
using a custom recovery is the simplest and easiest way to flash ROMs going forward.
the most reliable recovery available on the One is CWM non-touch version. so go to http://d-h.st/users/flyhalf205/?fld_id=11322#files and find a file with the highest version number (currently 6.0.x something) that does not say "touch" in it.
The basic steps to loading a custom recovery are
- make sure phone's bootloader is unlocked (with stock dev edition obviously you are already set)
- make sure your computer has android sdk installed and you know where the fastboot executable is
- once you have the latest recovery zip from location above, check its md5, and then rename it something simple like recovery.img and place it in the same folder as your fastboot executable
- on your phone, make sure "fast boot" feature is turned off
- boot phone into HBOOT then Fastboot
(in case it is not obvious, connect your phone now via USB and type the necessary commands into a terminal emulator on the computer)
- while phone is in fastboot, use command "fastboot erase cache"
- while phone is in fastboot, use command "fastboot flash recovery recovery.img" where recovery.img is the name you chose above
at this point you should be able to reboot the phone into your new recovery and have a look around.
first step is always make a backup (known as a "nandroid" backup).
if your goal was to root your existing ROM, then you don;t actually have to do the steps in the guide i linked to above anymore: as soon as you try to exit CWM it will notice you are not already rooted and prompt you if you want to root it.
But if you want to do it the old fashioned way where you go and flash your own super user zip and other useful files that go with it, just refer back to the guide above. If the crucial link to the "rooting tools" is still broken, let me paste it again for you here http://www.androidrevolution.nl/dow...le=Android_Revolution_HD_Root_and_BusyBox.zip
I'll let you read up on how to "flash a zip from recovery". It should be pretty straightforward. (download zip and put zip somewhere on phone, reboot into recovery, say you want to flash a zip, navigate to where it is on the phone, start flash, profit)
Once you have an unlocked bootloader, you can flash a custom recovery
Once you have a custom recovery, you can
- root an existing rom and/or
- flash a custom rom compatible with your setup, presumably one with root baked in
Once you have root on any rom, you can run titanium, wireless tether etc.
Hopefully this is enough to get you started down the right path.
Click to expand...
Click to collapse
I ran into an issue following your directions (which were basically the same as the YouTube video about the "easiest way to install custom recovery for the htcone" that I got off another xda thread. I run the command to fastboot flash recovery, and my PC gives me an error saying that fastboot is not a valid command. I have the proper drivers installed, and I am in fastboot on my phone but it won't work. I did notice that on the thread you linked to above, they want my recovery file to be in some sdk folder or something. My directions didn't mention that and the directions you linked to mention an sdk file in the bootloader section, but it tells me to skip that if I have a dev edition. Is the sdk file the reason why my computer won't recognize the command? For what it's worth, I tried that toolkit and it did not seem to recognize my phone either.
Sent from my HTC One using Tapatalk 2

EDIT Just a general tip - you can copy the text of any error message you get and paste it into google and you will doubtless turn up a bunch of interesting info - you are very likely not the first person to encounter the issue.
Anyway here's what I think is happening:
Sometimes when you try to give a command from the command line, a computer doesn't know where the necessary executable file is.
If the SDK was installed ok , then somewhere on your computer is the actual fastboot.exe executable.
Find it.
If it is in a folder called C:\path\to\files\blah\blah then you need to actually type out C:\path\to\files\blah\blah\fastboot.exe to run it.
If you will be doing more commands in this location or any commands that refer to other files in the same location (and some if these procedures assume you will since you'll be putting the flashable image files in this location), you really should tell your terminal program to just change the "working directory" to that location: then whenever you refer to something the computer will look there first. Here's how that looks:
cd C:\path\to\files\blah\blah
fastboot
(Final note- going forward you can make it easier to launch executables by adding their location to your "PATH variable" - google it. )
Maybe you knew all this? But for the benefit of anyone else following these bread crumbs, here's the upshot: Most of these "procedures" that people write down assume some general knowledge of command line syntax. If you're not comfortable with that yet, you're going to need to be persistent and search google a lot.

Related

[Q] ICS Update for Nexus One

Hi,
My Nexus One details are as follows:
Model number : Nexus One
Android version : 2.3.4
Baseband version : 32.50.00.32U_5.12.00.08
Kernel version : 2.6.35.7-ge0fb012
[email protected] #1
Build number : GRJ22
Which is the best way for me to update my phone to ICS (Android 4.0). I have read the official message from Google on categorizing Nexus One as "old" and will no more air the updates.
I am not familiar with the MODs and so; eventhough I scanned through the ROM section; I couldn't figure out myself which way should I opt to upgrade my phone.
Thanks to all for reading my request as it might be a thousandth time such a request is coming through. Thanks for your patience and your advise is eagerly awaited.
Jabir
PS: I have never done a "jailbreak" or "rooting" (whatever name is it) on my phone except those Google aired updates.
You are going to have to root--no way around it
I did it the old fashion way and installed sdk/fastboot oem unlock/flash recovery and a rom with super user in it or flash super user
instructions are in Wiki
there are different ways now I am not familiar with, but prefer the sdk method
you will also need to be on hboot 35.0017 to install blasckrose, although some ICS roms have a miniversion that can run on stock hboot
However, I would root and flash some roms like CM7 stable to get use to things. The hboot and ICS is a bit more complicated at first--read the threads carefully before attempting
Start reading.
http://forum.xda-developers.com/showthread.php?t=1366897
ursJAR said:
Hi,
My Nexus One details are as follows:
Model number : Nexus One
Android version : 2.3.4
Baseband version : 32.50.00.32U_5.12.00.08
Kernel version : 2.6.35.7-ge0fb012
[email protected] #1
Build number : GRJ22
Which is the best way for me to update my phone to ICS (Android 4.0). I have read the official message from Google on categorizing Nexus One as "old" and will no more air the updates.
I am not familiar with the MODs and so; eventhough I scanned through the ROM section; I couldn't figure out myself which way should I opt to upgrade my phone.
Thanks to all for reading my request as it might be a thousandth time such a request is coming through. Thanks for your patience and your advise is eagerly awaited.
Jabir
PS: I have never done a "jailbreak" or "rooting" (whatever name is it) on my phone except those Google aired updates.
Click to expand...
Click to collapse
0. Set up ADB correctly.
1. Root.
2. Optional: Unlock the bootloader
3. Optional: Set SecuFlag off, i.e. S-OFF
4. Fastboot flash a custom recovery
5. Fastboot flash blackrose's hboot. Either stock blackrose or the one specifically for ICS (custom partition layout)
6. Download an ICS ROM of your choosing. My pick would be texasice's.
7. Download an A2SD script as the default one is a li'l buggy.
8. Boot into the recovery of your choosing (4EXT or AmonRa preferred)
9. Make a FULL wipe of settings and partitions and wipe cache and dalvik cache.
10. Flash the ROM zip file
11. Flash the A2SD script file
12. Reboot and boot up your phone. Enter a terminal emulator. Type: su
13. Accept the root request and then type a2sd install,
14. Let your phone reboot on its own and then boot it up again,
15. Return to the terminal emulator, type su and then a2sd cachesd and let it reboot once more.
16. Now you're good to go.
Find out all info on your own, I simply tell you what you need to do.
Theshawty said:
0. Set up ADB correctly.
1. Root.
2. Optional: Unlock the bootloader
3. Optional: Set SecuFlag off, i.e. S-OFF
4. Fastboot flash a custom recovery
Click to expand...
Click to collapse
If you are going to be using fastboot to flash a custom recovery, root is not needed and unlocking the bootloader is not Optional. Root is only needed if you are going to flash the recovery through Android with a program like ROM Manager. Also, S-Off also is something we can't officially get with our phones without using the XTC Clip. But for pretty much all things that we need to do with our phones, S-Off is not required due to it being a dev phone.
As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
I only started modding recently (a month ago) and in that time, I've already moved to ICS and using a custom Blackrose HBOOT. Its fairly easy - you just have to have the ability to read patiently.
Here is what I would advise, being a bit of a noob myself - yet having never had a single hiccup. This is pretty much the fastest way to do it.
1. Enable USB debugging (in settings>applications>development)
2. Download SuperOneClick (Google it, also has USB drivers if necessary)
3. Connect your phone to the computer, and once all drivers are installed, fire up SuperOneClick, hit 'Root' and watch the magic unfold
4. Download ROM Manager from the Market, follow the instructions (Flash recovery>Download a ROM (CM7 recommended))
Once you are familiar with the basics of installing a ROM from ZIP, head over to the Dev forums, and download ICS for stock HBOOT to get you started!
mrhohoha said:
As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
Click to expand...
Click to collapse
This is true. I was just going off the instructions that Theshawty wrote. In the instructions he included directions to use fastboot. And without replacing the bootloader to Blackrose (which is probably too in depth to do include here), using fastboot would require the bootloader to be unlocked.
bassmadrigal said:
If you are going to be using fastboot to flash a custom recovery, root is not needed and unlocking the bootloader is not Optional. Root is only needed if you are going to flash the recovery through Android with a program like ROM Manager. Also, S-Off also is something we can't officially get with our phones without using the XTC Clip. But for pretty much all things that we need to do with our phones, S-Off is not required due to it being a dev phone.
Click to expand...
Click to collapse
I have S-OFF'd my device and I didn't use anything called XTC Clip?
Yep. Nothing special required for S-OFF. Heck, you can S-OFF in like 20 seconds by just installing Blackrose! And revert to stock S-ON HBOOT whenever you like!
Using Blackrose does not actually make your device S-Off. The upgraded HBOOT just ignores the flag that is set saying the S-On is still there and displays that you are S-Off. And so, essentially you have S-Off when you use blackrose, but that is only because blackrose ignores the actual setting saying the S-On is still in place. The one thing this will not allow is relocking the bootloader, which full S-Off, when acheived with the XTC Clip, will do.
mrhohoha said:
As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
I only started modding recently (a month ago) and in that time, I've already moved to ICS and using a custom Blackrose HBOOT. Its fairly easy - you just have to have the ability to read patiently.
Here is what I would advise, being a bit of a noob myself - yet having never had a single hiccup. This is pretty much the fastest way to do it.
1. Enable USB debugging (in settings>applications>development)
2. Download SuperOneClick (Google it, also has USB drivers if necessary)
3. Connect your phone to the computer, and once all drivers are installed, fire up SuperOneClick, hit 'Root' and watch the magic unfold
4. Download ROM Manager from the Market, follow the instructions (Flash recovery>Download a ROM (CM7 recommended))
Once you are familiar with the basics of installing a ROM from ZIP, head over to the Dev forums, and download ICS for stock HBOOT to get you started!
Click to expand...
Click to collapse
The SuperOneClick Application just gets not responding when I click the Root button and after these messages on the right pane are shown
* daemon not running . starting it now on port 5037 *
* daemon started successfully *
Please advise..
Make sure you run it with administrator rights (right click to see the option), and verify that USB Debugging is turned on on the phone. If it is turned on, you need to make sure you have the adb drivers installed (different than the standard USB drivers that windows automatically installs).
Hi all. I have read quite a few pages of the s off blacks install guide. Not really getting it. Can someone please give me simple steps to install blackrose?
Please and thank you.
Sent from my Nexus One using xda premium
Blackrose install guide
Sent from my Nexus One using xda premium
hardrockinandroid said:
Blackrose install guide
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
Black rose thread http://forum.xda-developers.com/showthread.php?t=1270589
I've read that and everything sounds so complicated. I've watched the vid for resizing partition but they don't say anything. Can someone give a step by step for us noobs for resizing partition please?
Sent from my Nexus One using xda premium
do you have all requirements met from br op page
if so, you need to download the latest br from op and extract it to the download folder you just downloaded br to. then open the extracted folder and clickon br.exe
follow instructions inside the command window that opens
then you need to resize partition to ics sizes thru the breditor
What is op page?Yes bootloader unlocked. Rooted. I have the blackrose zip.the adb and fastboot drivers for windows. Don't know what to do now. I put both files on my desktop. Now what?
Sent from my Nexus One using xda premium
OP page is first page of Dev's thread--mmm
Needs read as well as most of thread to get an understanding of this--lots of folks are running into big trouble if they don't understand it first--
If you are rooted and unlocked do you have sdk installed and can you run adb devices and fastboot devices in command window and see phone's serial number? If so you don't need the usb drivers from OP page--
Yes I have ran commands on a my touch4g, a HTC sensation and a g 2x. Do I just do exactly as the YouTube video shows and then flash the blackrose zip after resizing
the partition? Then flash an Ics Rom?
Sent from my Nexus One using xda premium

[MINI-GUIDE] Roadmap to a Custom ROM!

Roadmap to Custom ROM​
1.Unlock Bootloader from htcdev.com.
2.Flash a multi hboot recovery.
3.Root using the permanent root solution flashed via recovery, found here.
4.Flash S-OFF Hboot from unlimited.io.
5.Flash custom ROM with no problems.
To check your Unlock Token, Flash Recovery and S-OFF you should use the tool provided by me here .
This is the easiest guide to follow.. I'm also using this step to install custom Rom on my SXL before I got One X.. I'm also don't get it.. why people don't use unlimited.io trick.. it easier for me.
BTW.. it good to see a new dev for sxl.. it a good device.. but lack of developer.. wish you good luck with your project.
Sent from my HTC One X using Tapatalk 2
Agreed.
I've flashed on a lot of devices and the SXL guides are all a bit random.
The info is out there but sometimes you need to dig a lot to find it.
And a lot are out of date.
Hope this becomes the go-to guide for everyone and hope to see some dev work happening.
I think its time to move on for me..... getting flash withdrawal.
Prof Peach said:
Agreed.
I've flashed on a lot of devices and the SXL guides are all a bit random.
The info is out there but sometimes you need to dig a lot to find it.
And a lot are out of date.
Hope this becomes the go-to guide for everyone and hope to see some dev work happening.
I think its time to move on for me..... getting flash withdrawal.
Click to expand...
Click to collapse
I'm just getting familiar with the forum and the device (almost 4 days since i bought it).
Soon enough if i have time (back2school), i will try to work on CM9 or CM10, depends, CM9 seems the obvious road to take as some work was previosly made by [vertigo], and some fixes are needed (he said that are kernel related), so i think i will try to fix his CM9 rather than port it again form scratch.
As for CM10, i think the best road to take is to compile AOSP JB from source and edit the kernel so it likes the jelly flavour.
If everything works as intedend, in a couple of months we should see both CM9 and JB/CM10 up and going.
(The worst thing is that i will surely need help, i think i can find around the forum, some testers already enrolled to the call to arms thread, so maybe we can build up a team., i really like this device )
I will say that some of the guides are if you were on a GB rom, and then installing a custom rom wasn't so easy, but since the upgrade to ICS it has become a lot easier, although I had noticed that it is easier to softbrick the phone if you don't flash the chinese boot.img and then chinese rom. Also s-off isn't essential for flashing custom roms...
[vertigo] said:
I will say that some of the guides are if you were on a GB rom, and then installing a custom rom wasn't so easy, but since the upgrade to ICS it has become a lot easier, although I had noticed that it is easier to softbrick the phone if you don't flash the chinese boot.img and then chinese rom. Also s-off isn't essential for flashing custom roms...
Click to expand...
Click to collapse
Well, i'm fairly new to this device, but from what i've learned, the chinsese rom is optional if you have s-off, as s-off let's you to access all the partitions, system and other things you need.
Maybe i'm wrong, that's why i've started this thread, i think this is easier, and softbricking a phone with Android seems almost impossible to me...as i said, to me
Yeah I know the chinese rom is optional, but as I said from my point of view, once I'd flashed the chinese rom, I didn't manage to softbrick the phone where as before when I was trying various ports I managed to softbrick it a few times. Just my opinion and what I'd noticed with my device...
As for s-off mine (although broken) is still s-on and I've never felt the need to make it s-off. Again just my opinion
[vertigo] said:
Yeah I know the chinese rom is optional, but as I said from my point of view, once I'd flashed the chinese rom, I didn't manage to softbrick the phone where as before when I was trying various ports I managed to softbrick it a few times. Just my opinion and what I'd noticed with my device...
As for s-off mine (although broken) is still s-on and I've never felt the need to make it s-off. Again just my opinion
Click to expand...
Click to collapse
Well, i know what youre pointing at, i was just wandering when i first read te forum, why on earth should i install a Chinsese ROM when i will change it anyways for a new ROM...so the boot.img is a different one in the custom one, and other things.
I'm not so expeirenced with S-Off/On, as this is my first HTC phone i have and changed ROM (not too many HTC's in my area), but from what i've read online, S-Off is the best road to take to ensure you don't softbrick your phone, as you have the real "Full Control" over the Device and the ROM parts you can flash, like you, this is my opinion, a begginers opinion
Double Post because reedited thread
Hi Lexmazter,
Thanks for making this guide, it is easy to follow. But I'm stuck at a small point and face below response; -
>>>>>>>>>>>>>>'fastboot' is not recognized as an internal or external command, operable program or batch file.<<<<<<<<<<<<<
Please let me know where did I do wrong? Thanks.
My steps were: -
factory reset
root via DooMLoRD_v4_ROOT
titanium backup worked and restore all apps and settings
unclocked the bootloader from htcdev.
all data gone, no more, like factory reset again
superuser app still exist, didn't root again
booted and rooted as you said
connect PC to phone via USB in charge mode only.
run your tool
doing select 5 Flash HBOOT S-OFF Unprotected (via adb) - choose hg hi both failed - but face above message 3 repeat lines.
reboot to bootloader FASTBOOT, >>>>>USB<<<<< appear
UNLOCK at top also appear
then select 4 Flash Recovery. (via fastboot) - then choose rei reg both failed - but face above message. 1 line.
Hope can teach me, thank you very much in advance.
And I'm sure I didn't do something right before hand.
cx5 said:
Hi Lexmazter,
Thanks for making this guide, it is easy to follow. But I'm stuck at a small point and face below response; -
>>>>>>>>>>>>>>'fastboot' is not recognized as an internal or external command, operable program or batch file.<<<<<<<<<<<<<
Please let me know where did I do wrong? Thanks.
My steps were: -
factory reset
root via DooMLoRD_v4_ROOT
titanium backup worked and restore all apps and settings
unclocked the bootloader from htcdev.
all data gone, no more, like factory reset again
superuser app still exist, didn't root again
booted and rooted as you said
connect PC to phone via USB in charge mode only.
run your tool
doing select 5 Flash HBOOT S-OFF Unprotected (via adb) - choose hg hi both failed - but face above message 3 repeat lines.
reboot to bootloader FASTBOOT, >>>>>USB<<<<< appear
UNLOCK at top also appear
then select 4 Flash Recovery. (via fastboot) - then choose rei reg both failed - but face above message. 1 line.
Hope can teach me, thank you very much in advance.
And I'm sure I didn't do something right before hand.
Click to expand...
Click to collapse
Extract the contents of the archive in C:/ and try again, it is most likely because you are running from a folder that has spaces (" ").
Thanks for replying so quickly, some questions before sleep tonight.
I moved the folder to c:\xmtool and run as administrator as usual. But without connecting the phone, and select 5 flash H boot. The 3 repeat message appear still. Hahah, may be I want to test in theory.
Anyway, reading more more other post and try again this weekend.
Thanks !!!! many of your post and reply has been insightful.

[HOWTO] HBOOT 2.02.0002 - ICS 4.0.4 - Unlock, root, downgrade, S-OFF, BlackRose, ROM

Hi there
This thread was originally written to get some answers about rooting my Incredible S, and as I have succeeded, I promised a guide-ish thing about the procedure I've followed. So here it is !
You can find the original post quoted at the end of this one.
\\ WARNING //
I'm really no expert in rooting, nor in anything close to that. If you do not have the exact same specifications that I had (see below), I won't be able to answer any questions regarding issues you may encounter while following the steps listed here.
However, I'm sure there are plenty of other people here who know a lot and could help you if necessary !
Also, I may not hold this topic updated, as new recovery/rom/blackrose/etc versions may be released.
\\ SPECIFICATIONS //
Here is how the device looks like before doing aything :
HTC Incredible S
***LOCKED***
VIVO PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.18.00.11_M
(To get that info : Turn off your phone - Hold Volume Down and press the power button - Bootloader screen will show up)
Android 4.0.4
Sense 3.6
Software 4.10.405.1
20.74.30.0833U_3831.18.00.11_M
(To get that info : Go into Settings > About and browse the various menus)
\\ CREDITS //
I take no credit whatsoever for the knowledge on which this post is based. Anything other that the phrasing (and some specific steps) is not mine, and mostly extracted from here, there, here, there, here and there.
I thank everyone of these threads for that.
\\ SUMMARY //
Through this guide, you will :
1/ Download and set up everything you need
2/ Backup your data
3/ Unlock your bootloader via HTCdev
4/ Flash a recovery (Clockworkmod)
5/ Install Superuser and test root access
6/ Backup the stock ROM
7/ Run Nonverbose's script
8/ Install new RUU
9/ Use Revolutionary to get S-OFF
10/ Flash a custom ROM (CyanogenMod 7)
11/ Install Blackrose 2.03.0000
12/ Pick a ROM and flash it
\\ BEFORE YOU START //
Allright, you decided to step into the big unknown, nice !
Well, it's probably not that unknown, but it was for me when I started.
First, be aware that this might take a while, meaning no using of your phone during the process. I might recommend to remove your SIM card, that way you'll be certain nothing (no one) is going to crush your evil plans.
Then, be sure to have a full battery charge before you start, even though you'll be on charging mode now and then.
___________________________________________
1 // DOWNLOAD AND SET UP EVERYTHING
> On your C: drive, create an Android folder
> In C:/Android, create a "Download" folder, where you'll put everything listed below
> In C:/Android, create a "Revolutionary" folder
> In C:/Android, create a "Downgrade" folder
> In C:/Android, create a "BlackRose" folder
> In C:/Android/Downgrade, create a "DowngradeKit" and a "RUU" folder
a - Get HTCSync here
b - Get IncS_MVDTKv3.4.1.zip here
c - Get the RUU here (RUU used for downgrade, model number PG3213000(Typical IncS) ) and put it in the C:/Android/Downgrade/RUU folder
d - Get ClockWorkMod recovery here and put it in C:/Android (Scroll to HTC Incredible S, and get last version - 5.0.2.0 at the time)
e - Get SuperUser here
f - Get Cyanogen ROM here (I used stable version, but feel free to use release candidate if available)
g - Get BlackRose here, at the end of the post. Unzip it in your BlackRose folder.
> Install HTCsync, then uninstall it (we only want the drivers)
> Unzip IncS_MVDTKv3.4.1.zip into C:/Android/Downgrade/DowngradeKit - Copy everything from the "files" folder to C:/Android
> Put Superuser-3.1.3-arm-signed.zip at the root of your SD card
> Put the Cyanogen ROM zip at the root of your SD card
> Take note somewhere of your Serial Number (usually under the battery)
Allright, now you're all set up to begin !
2 // BACKUP YOUR DATA
You should know that by doing step 3, you'll erase everything on your phone (not on the SDcard).
So if you want to backup stuff, now is the right time !
Unfortunately, I couldn't find any way to backup app data like saved games and such without a rooted phone. If anyone finds it, say the words !
Depending on apps and the way that are handled contacts, SMS, etc, everyone's phone is different.
To know how to backup your stuff, google will probably be your best friend. What I used was :
- App Backup & Restore (only saves the .apk of the apps, so you don't have to download them again)
- SMS Backup & Restore
- Contact export via the stock contact app
3 // UNLOCK BOOTLOADER
Now that you've backed up everything and you are absolutely sure you want to proceed, visit htcdev.com/bootloader and create a free account.
Select your device (mine was Incredible S WWE), and follow the steps. These are pretty simple and well explained, you shouldn't have any trouble. Your phone will show up a confirmation screen at some point, last chance to cancel.
When it's over, your Bootloader is officially unlocked !
4 // FLASH A RECOVERY
Switch off your phone, and go into the bootloader by holding Volume Down and pressing the power button.
Now there is a nice **UNLOCKED** where there previously was a **LOCKED** !
Wait a bit for some zips to be checked, then plug in your USB to your computer.
Using volume up and down, navigate into the menus, highlight FASTBOOT and press the power button to confirm.
On your PC, go to the start menu, Run, and type "cmd". Manage your way through here to go into C:/Android.
From this point, you should be certain that in this folder there is the ClockWorkMod .img file, your Unlock_code.bin and the files you moved earlier from the downgrade kit.
You can now type just after the C:/android :
fastboot flash recovery recovery_name.img
In my case, that was :
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
After a few seconds, your recovery is now flashed. Select "bootloader" on your phone, and you're back on the first bootloader screen.
5 // INSTALL SUPERUSER AND TEST ROOT ACCESS
From the bootloader screen, highlight "recovery" and press the power button. The HTC screen comes up for a while, then you're on the ClockWorkMod Interface.
- Volume down to select "install zip from sdcard".
- "choose zip from sdcard"
- Select the SuperUser zip you put on your SD on step 1 (Superuser-3.1.3-arm-signed.zip)
- Reboot your phone.
Now you have rooted your phone ! Let's just be sure :
- Activate USB debugging (Settings > Developper options) and connect your phone to the computer (charge only)
- Start menu > Run > cmd
- Go into C:/Android
- Type adb.exe shell and press Enter - You obtain $, meaning you're connected to your device.
- Type su and press Enter - You obtain #, meaning that you got root access !
You can now also see a new SuperUser app in your appdrawer.
6 // BACKUP STOCK ROM
Now that you have rooted your phone, you should make a nandroid backup (= backup the entire current state of your phone) in case something goes wrong and you want to go back to this step.
- Switch off your phone, boot into the bootloader screen (Vol Down + Power button).
- Go into recovery, select "Backup and restore", then "backup"
- Reboot your system
There is now a backup on your SD card, in a clockwordmod folder : transfer it to your PC if you want.
7 // RUN NONVERBOSE'S SCRIPT
- Plug your phone to your PC, charge only, USB debugging ON, fast boot OFF (in Settings > Power)
- Launch runme.cmd located in Android/Downgrade/DowngradeKit
- It'll do its stuff, while asking questions you have to answer with "y" or "n". Be honest ! For instance, "have you unlocked via HTCdev ? - y", "have you rooted your phone ? - y", "do you want a goldcard ? - [answer depending what you want]".
- It may show some disturbing lines, like "Failed no such file or directory", "Note : run RUU from fastboot". I just ignored that. But you still got to be sure that it's no major error, in that case or if you're not sure, you'll probably find an answer in the corresponding thread.
8 // INSTALL NEW RUU
After the runme.cmd has completed succesfully, you can launch the RUU file that you downloaded in step 1.
At the end of that thing, you can turn off your phone, and back on into the bootloader (Vol down + ¨Power)
Be happy, you should now have something like this :
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3805.06.03.03_M
eMMC-boot
Meaning that you downgraded your bootloader from HBOOT 2.02.0002 to HBOOT 1.13.0000 succesfully !
9 // USE REVOLUTIONARY TO GET S-OFF
- Phone in normal charge mode, USB debug ON, fast boot OFF
- Go to revolutionary.io
- Download the thing in the Download folder you created and fill the form (note : your HBOOT is now 1.13.0000)
- Keep somewhere the beta key you got
- Unzip revolutionary.zip in your Revolutionary folder.
- Run revolutionary.exe
- It'll ask to type your beta key, so go on
- It'll ask if you want to flash ClockWorkMod recovery. If you don't want to bother, say yes, you'll have a working recovery. However, it'll not be the last version, so if you prefer you can flash the recent one, exactly how you did it in step 4.
You can now turn off you phone, and back on the bootloader (vol down + power), and check that you have something like that :
-Revolutionary-
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-3805.06.03.03_M
eMMc-boot
Well done !
Last thing to do, get SuperUser (root) back : do step 5 again (you don't have to verify root access afterwards if you are lazy)
10 // FLASH A CUSTOM ROM (CyanogenMod 7)
Great, now you're all set to flash a custom ROM, at last !
Some ROMs need BlackRose HBOOT installed (Revolution HD for example).
The thing is, to install BlackRose, you need an unsecured boot.img, which can be obtained by flashing a custom ROM !
I chose CyanogenMod 7 for the purpose of this guide, and also because I believe this is a good start if you're not yet sure what final ROM you want.
Let's get started :
- Do a second nandroid backup like explained in step 6. It's always better to have a plan B in case things go wrong.
- If you didn't put the CyanogenMod 7 (CM7) zip at the root of your SD card during step 1, do it now.
- If you're still in ClockWorkMod recovery, stay here. If not, switch off your phone, turn it back on in bootloader mode, go into recovery.
- In recovery from first menu, chose to [wipe data/factory reset], when it's done go into [advanced] and select [wipe dalvik cache]. Remember that it's always good to do these two things before flashing a new ROM.
- Go back and select [install zip from sd card], choose the CM7 zip (mine was cm-7.2.0-vivo.zip), and rock this world.
Reboot your system, and here you are with a custom ROM, oh yeah that's a relief !
You don't have to follow the rest of this guide if you're happy with this ROM, or if you wish to use another ROM which doesn't require BlackRose installed. In that case just flash the new ROM like explained in this step.
Otherwise, keep reading.
11 // INSTALL BLACKROSE 2.03.0000
- Plug your phone, charge only, USB debug ON
- Into your C:/Android/BlackRose folder, where you unzipped the BlackRose stuff you got in step 1, run BlackRose_IS.exe.
- Wait for it to be finished, you phone may reboot in bootloader/recovery.
- Turn off your phone, then back on bootloader mode.
- Hurray, you've done it ! You problably get something like that :
*** BlackRose ***
VIVO PVT SHIP S-OFF RL
HBOOT-2.03.0000
RADIO-3805.06.03.03_M
eMMc-boot
After this step, I got stuck on the HTC screen when I tried to turn my phone on.
If that happens to you, go into your ClockWorkMod recovery, [wipe data/factory reset], and [Advanced > wipe dalvik cache] ; then install your CM7 ROM zip again from you SD card, like you did in the previous step. Everything should go back to normal.
You have now BlackRose, S-OFF, and the CM7 ROM !
If you're pleased with that, well, keep it
If you'd like to try some other stuff, keep reading.
12 // PICK A FINAL ROM AND FLASH IT
Well, here you are ! You have done 99% of the work.
Here is a very nice thread indexing everything you might be interested in (ROMs, kernels, radios, recovery, guides, ...).
Pick a ROM from there, study it a bit to be sure that it matches your uses of the phone, then take the leap and follow the directions given in the ROM's thread !
It shouldn't be very different from what you did in step 10, but if you're not sure ask ! People will be likely to help you if you have doubts.
___________________________________________
Allright ! This guide is now over.
I hope you didn't run into any issues, well you shouldn't have !
If that's the case, ask me and if you started off with the exact same specifications as mine, I might help you !
Otherwise lots of people here know more than I do
Enjoy the ultimate power !
Original post :
[Q] Backup said:
Hi there
First, you should know that I have been reading forum posts around the web for a few days, comparing sources and trying to find the adequate solution for me and my phone, as I'm a pure noob in rooting.
I think I have come close to begin the procedure of rooting, but as there are multiple guides to mix, and none really spoke about backup (apps, sms and other stuff), I wanted to be 100% sure of what I'm doing, and ask here if I was doing it right !
So, I currently have :
HTC Incredible S
***LOCKED***
VIVO PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.18.00.11_M
Android 4.0.4
Sense 3.6
Software 4.10.405.1
20.74.30.0833U_3831.18.00.11_M
Kernel : 3.0.16-gfa98030 [email protected]#1
SD card 8GB, almost full
> As I want to root that device, I landed on this nice guide from Fallen
I understood this guide, even if it doesn't mention how to flash a ROM.
But it precises "Remember it erases all data so if you need to, backup everything". And that, I don't know how.
> The attachment link for the Downgrade Kit in Fallen's guide not working, I landed on that other guide to download it, Nonverbose's script.
Again, this guide is clear, but as I've got HBOOT 2.02.0002, this part "Please note that phones with the latest ICS hboot (2.02 currently) will have to be bootloader UNLOCKED from htcdev.com. If your hboot 2.02 phone does not have an unlocked bootloader, do NOT run this script." made me thinking.
I don't really know how to unlock trough htcdev.com (I understand it might be easy and self-explanatory while doing it), and I don't know if unlocking the bootloader that way is the only thing to do before following this guide.
And this guide doesn't mention any backup, nor "carefull it erases everything", and is not explained noob-style. I wasn't so sure anymore.
> Then, I read that guide from msarmad.
I have no idea if I updated my phone with "official RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.3 0.0833U_3831.18.00.11_M_release_266013_signed", so I don't know if this applies to me.
And again, it briefly goes through the htcdev.com step. Also, the explanation mentions command entries and manipulations that are not quite cristal clear for the miserable newbie that I am.
No mention of this procedure erasing everything, nor backup process.
> This guide looked like the perfect match for me when I studied it a bit
But it is written in telegraphic style, with so many () )))(() that I can't be sure of fully understanding it.
Also, brief step on htcdev.com, and no mention of backup (actually it even clearly asks to wipe data factory and format sd card)
> This last guide looks simple, and explains how to flash a ROM, but all of a sudden I don't see any trace of downgrading like I read before.
So, I think all the keys for my delivrance are in these threads, but also in the answers you may give me !
My real questions are probably :
1/ How can I backup my phone before anything gets erased ?
(I mean saved games, SMS/MMS, anything on the phone that needs to be backed up)
I read a bit about MyBackup, but understood that in the 30 days trial, if you root your phone it considers it's another phone, so you can't restore your stuff.
I read a bit about Titanium backup, which seems nice but apparently only works with rooted devices.
2/ I understood that I need to downgrade from HBOOT 2.02.0002, to HBOOT 1.13.0000, so I could use revolutionary to get S-OFF, and then put Blackrose 2.02.0002 plus any choice of ROM
- Do I unlock my bootloader from htcdev.com (I should choose Incredible S WWE right ?), and then follow Fallen's guide with the Downgrade Kit downloaded on Nonverbose's guide ?
- Or unlock bootloader, then follow Nonverbose's guide (which is not a newb-step-by-step guide) ?
- Or maybe follow msarmad's guide, even though it's lots of command lines ?
- Or probably 77[...]77's guide, which I don't quite understand but seems to bring us from downgrade to ROM installing ?
3/ Talking about ROMs, I was thinking about Android Revolution HD, or MIUIv4. I've read that choosing a ROM depends on personal use of the device, so I guess I'll try and see what fits.
Is the last guide the way I have to flash a ROM after I got downgraded/S-OFF ?
I think I covered everything, in the case I did not I may post further questions in this thread !
I tried to make this post as clear as possible, as I know it's kind of unpleasant to read such a thing, especially with so much HowTos and guides out there.
I thank you in advance for your help !
Click to expand...
Click to collapse
My real answers are definitely:
1. Use titanium, it's not hard to root your phone after you unlock it, all you need is to flash recovery via fastboot and flash superuser package from recovery. However your phone will be factory reset after unlock so you'll lose your data anyway.
Recovery source: http://www.clockworkmod.com/rommanager
Superuser source: http://androidsu.com/superuser/
Flashing of recovery: fastboot flash recovery c:\'path to your recovery'
And you'll be needing adb: http://developer.android.com/sdk/index.html but you'll install it during unlock.
2. htcdev, of course. To know which version you should choose download Android Assistant app from Play Store, in section tool of the app you have system info the first is the one you need.
Use Nonverbose guide, but I had a problem with making of goldcard so I needed RUU for my version, so the info you got in chapter 1. of my story can point you to the one compatible with your device (cause WWE that's given in tutorial won't work if you have region and carrier specific one). Here is the source for RUUs: http://www.filefactory.com/f/e45d6fe3dcf51228/ just choose Gingerbread version (it iz named like that) that is specific for you. If you dont know which one tell me what version of phone you have and i will find you the right one.
Also, one more recommendation, root you device before downgrade cause I had a problem with Tacoroot exploit provided with downgrade tool, so when downgrade tool asks you if you are rooted just answer yes.
3. About rom, it's your choice, go here and find something for yourself: http://forum.xda-developers.com/showthread.php?t=1136463
When you're s-off, to install custom rom just put the rom.zip that you downloaded to your SD, go to recovery, do a full wipe and install it as a zip from sd card.
If you need anything more just say.
Thanks for your answer ! So, to keep it organised :
nlooooo said:
1. Use titanium, it's not hard to root your phone after you unlock it, all you need is to flash recovery via fastboot and flash superuser package from recovery. However your phone will be factory reset after unlock so you'll lose your data anyway.
Recovery source: http://www.clockworkmod.com/rommanager
Superuser source: http://androidsu.com/superuser/
Flashing of recovery: fastboot flash recovery c:\'path to your recovery'
And you'll be needing adb: http://developer.android.com/sdk/index.html but you'll install it during unlock.
Click to expand...
Click to collapse
Titanium, alright. Something I don't get, though : how do I backup data with Titanium if I have to unlock/root before to use it (therefore deleting data before I can back it up) ? Isn't the snake biting his tail ? Or maybe I didn't understand what you meant.
nlooooo said:
2. htcdev, of course. To know which version you should choose download Android Assistant app from Play Store, in section tool of the app you have system info the first is the one you need.
Use Nonverbose guide, but I had a problem with making of goldcard so I needed RUU for my version, so the info you got in chapter 1. of my story can point you to the one compatible with your device (cause WWE that's given in tutorial won't work if you have region and carrier specific one). Here is the source for RUUs: http://www.filefactory.com/f/e45d6fe3dcf51228/ just choose Gingerbread version (it iz named like that) that is specific for you. If you dont know which one tell me what version of phone you have and i will find you the right one.
Also, one more recommendation, root you device before downgrade cause I had a problem with Tacoroot exploit provided with downgrade tool, so when downgrade tool asks you if you are rooted just answer yes.
Click to expand...
Click to collapse
Well, it looks a lot more complicated than just following a guide ! Basically, you say :
- Unlock bootloader via htcdev.com, using Android Assistant to know what choice I should pick in the list (htc_wwe HTC Incredible S for me, then)
- Follow Nonverbose's guide, but actually pick another RUU depending on my version (is that one the right one ?)
- Still follow the guide, but actually root before downgrade ? I thought downgrading from HBOOT 2.02.0002 to HBOOT 1.13.0000 was mandatory in order to root the device ?
I think I'm all confused about what I learned on the web the past few days, I may have mixed it up then.
So, isn't there any guide already out there, or maybe a mix of guides I could make, to take me there step by step ?
Like, for example, can't I just unlock my bootloader from htcdev.com, and then follow Fallen's guide with the Downgrade Kit downloaded on Nonverbose's guide, then flash a ROM starting from step 8 of this guide ?
Won't that work ?
If I do that, do I need to change the RUU version Fallen is giving (which seems the same that Nonverbose's) depending on mine (from the filefactory link you gave me, should I pick this one instead ?)
nlooooo said:
3. About rom, it's your choice, go here and find something for yourself: http://forum.xda-developers.com/showthread.php?t=1136463
When you're s-off, to install custom rom just put the rom.zip that you downloaded to your SD, go to recovery, do a full wipe and install it as a zip from sd card.
Click to expand...
Click to collapse
Allright, thanks for the confirmation. Any suggestion though ?
Epilogue said:
Thanks for your answer ! So, to keep it organised :
Titanium, alright. Something I don't get, though : how do I backup data with Titanium if I have to unlock/root before to use it (therefore deleting data before I can back it up) ? Isn't the snake biting his tail ? Or maybe I didn't understand what you meant.
Well, it looks a lot more complicated than just following a guide ! Basically, you say :
- Unlock bootloader via htcdev.com, using Android Assistant to know what choice I should pick in the list (htc_wwe HTC Incredible S for me, then)
- Follow Nonverbose's guide, but actually pick another RUU depending on my version (is that one the right one ?)
- Still follow the guide, but actually root before downgrade ? I thought downgrading from HBOOT 2.02.0002 to HBOOT 1.13.0000 was mandatory in order to root the device ?
I think I'm all confused about what I learned on the web the past few days, I may have mixed it up then.
So, isn't there any guide already out there, or maybe a mix of guides I could make, to take me there step by step ?
Like, for example, can't I just unlock my bootloader from htcdev.com, and then follow Fallen's guide with the Downgrade Kit downloaded on Nonverbose's guide, then flash a ROM starting from step 8 of this guide ?
Won't that work ?
If I do that, do I need to change the RUU version Fallen is giving (which seems the same that Nonverbose's) depending on mine (from the filefactory link you gave me, should I pick this one instead ?)
Allright, thanks for the confirmation. Any suggestion though ?
Click to expand...
Click to collapse
Ok, as I told you you'll loose you data when you unlock bootloader so Titanium is not a solution. To backup SMS/MMS you can use some app rom app store like Backup SMS, and for contacts just export them to sd card.
Downgrade is mandatory to s-off your device, not to root it. To root it, as I explained you, after unlocking flash recovery via fastboot, and then from that recovery flash Superuser app as a flashable zip that can be obtained on the link I gave you.
As your device is WWE version you can use RUU given in Nonverbose guide. The RUUs you posted are ICS and they have 2.02 hboot and that's the same hboot you have on your device that has to be downgraded to 1.13 to use Revolutionary. For that GINGERBREAD RUU is needed, and the appropriate one is RUU given in Nonverbose tutorial.
So unlock, root, downgrade, revolutionary to s-off are the steps you need. I recommend root cause sometimes Tacoroot exploit that is used to flash unsecured boot.img doesn't work (like in my case), so when downgrade toolkit asks you if you have root just type yes.
I had more problems than you, I had CHN_HK version and given RUU didn't work for me, goldcard tool from toolkit also, so I flashed some RUU i had (and was Sense 3.0 with 2.00 hboot). After that I had to downgrade again but toolkit didn't want to work (tacoroot problem), so I had to root it and download Gingerbread version for Asian market, and after that I succeded to downgrade.
For rom, hmm, I use Android Revolution HD 4.0 but for that you need Blackrose hboot, for that, and that's another story. Just search along the index thread I gave you and when you find what you like read the requirement and will work something out.
Allright ! Thanks for your help mate
I'm thinking about editing my first post and make it a guide-ish thing, explaining with my poor experience how I got where I am now, from where I left, step by step. It may help someone as noob as I am, with the same device setup, to change everything !
Anyway, what I did was turning :
HTC Incredible S
***LOCKED***
VIVO PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.18.00.11_M
Android 4.0.4
Sense 3.6
Software 4.10.405.1
20.74.30.0833U_3831.18.00.11_M
into :
HTC Incredible S
*** BlackRose ***
VIVO PVT SHIP S-OFF RL
HBOOT-2.03.0000
RADIO-3805.06.03.03_M
ROM : CyanogenMod 7 (Release candidate not available, so I used stable 7.2.0)
Android 2.3.7
20.2808.30.085AU_3805.06.03.03_M
I have CyanogenMod 7 because I used it in order to install BlackRose, and i'm keeping it until I know what ROM I want to use. Is there a place where ROMs are listed and compared, regarding battery performance, bugs, functionalities... ? If not I guess I'll just have to test among the ones listed here
The path I chose was a mix of information from nlooooo's intel, Fallen's guide, Nonverbose's, msarmad's, 77777777777777's, Lynt's, and some info from BlackRose or ROM threads.
All of these were very helpfull, so here is a global thanks !
I spent some hours decrypting all these with my untrained_to_anything_about_rooting brain to make it a (kind of) sucessfull succession of steps, but it was worth it !
The only bad news is that I couldn't find any way to save my saved games and app data before I had to erase everything. Well, it'll be a good excuse to play again the games I loved, finished and forgot !
If anyone wants to know the procedure I used before I get the time to transform the first post into a simili-guide, don't hesitate to ask !
Thanks again everywhere
guide
Hey there,
I would love to know the procedure that you have used, as I have an HTC INCR S with the exact specifications as yours. If you could post some kind of a guide, I would be eternally grateful! I am quite afraid of being stuck in HTC 'limbo' and/or making my device unusable :-" ) Thanks a lot! Looking forward to your post
Epilogue said:
Allright ! Thanks for your help mate
I'm thinking about editing my first post and make it a guide-ish thing, explaining with my poor experience how I got where I am now, from where I left, step by step. It may help someone as noob as I am, with the same device setup, to change everything !
Anyway, what I did was turning :
HTC Incredible S
***LOCKED***
VIVO PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.18.00.11_M
Android 4.0.4
Sense 3.6
Software 4.10.405.1
20.74.30.0833U_3831.18.00.11_M
into :
HTC Incredible S
*** BlackRose ***
VIVO PVT SHIP S-OFF RL
HBOOT-2.03.0000
RADIO-3805.06.03.03_M
ROM : CyanogenMod 7 (Release candidate not available, so I used stable 7.2.0)
Android 2.3.7
20.2808.30.085AU_3805.06.03.03_M
I have CyanogenMod 7 because I used it in order to install BlackRose, and i'm keeping it until I know what ROM I want to use. Is there a place where ROMs are listed and compared, regarding battery performance, bugs, functionalities... ? If not I guess I'll just have to test among the ones listed here
The path I chose was a mix of information from nlooooo's intel, Fallen's guide, Nonverbose's, msarmad's, 77777777777777's, Lynt's, and some info from BlackRose or ROM threads.
All of these were very helpfull, so here is a global thanks !
I spent some hours decrypting all these with my untrained_to_anything_about_rooting brain to make it a (kind of) sucessfull succession of steps, but it was worth it !
The only bad news is that I couldn't find any way to save my saved games and app data before I had to erase everything. Well, it'll be a good excuse to play again the games I loved, finished and forgot !
If anyone wants to know the procedure I used before I get the time to transform the first post into a simili-guide, don't hesitate to ask !
Thanks again everywhere
Click to expand...
Click to collapse
Glad to see someone could use the time I spent on this
I'm currently writing the guide on my spare time, it might take a few days ! But I hope it'll be cristal clear and easy to follow.
Thanks for the interest !
thanks!
thanks a bunch!! I'll be waiting
Epilogue said:
Glad to see someone could use the time I spent on this
I'm currently writing the guide on my spare time, it might take a few days ! But I hope it'll be cristal clear and easy to follow.
Thanks for the interest !
Click to expand...
Click to collapse
Allright, this took a while, but here it is !
I also changed the topic's name to be more accurate.
If anyone notices any mistake, please report ! As I'm no pro in rooting, I would not like to lead folks to somewhere bad.
Also, excuse my english, as it is not my native.
Hope it helps
Hi Epilogue,
I've registered on xda just to say thank you. Specifications you mentioned are same with my phone's. So I followed the instructions step by step. I did exactly what you did. Finally, I have a rooted, unlocked and S-Off phone. This is the best guide on xda about Incredible S and you did great job. Other guides look complicated for newbies. This thread is highly useful, so I'm appreciated for your help and effort. I want to ask a few questions if you don't mind.
After the installation of BlackRose, can I flash any ROM I'd like ? I mean, are there any ROM that I must get back to Revolutionary in order to work the ROM properly ? Besides, which ROM do you prefer in your device ? CyanogenMod 7 looks smooth and fast, but I'd like to flash JellyBean ROM. However, JB ROMs that Nikhil007 made for IncS, seem buggy and I've no idea which one is fastest and stable. Hope you suggest me something about it. Thank you so much.
step 8 making problems
First of all, i find your guide very comprehensive and helpful - but I have a problem with installing the new RUU. If I have checked everything correctly, my phone is absolutely the same like yours. But when i make the RUU run, I get "error 155". that means obviously, that I have to install another RUU. Does anyone know this and can help me. What I should mention perhaps is, that the link for the HTC-Drivers does not work correctly, so I couldn't install them. when I connect my phone to my PC, there is some Driver-software installed from my phone. As my PC then recognizes the phone, I hope, this is ok?!
derkleinebroicher said:
First of all, i find your guide very comprehensive and helpful - but I have a problem with installing the new RUU. If I have checked everything correctly, my phone is absolutely the same like yours. But when i make the RUU run, I get "error 155". that means obviously, that I have to install another RUU. Does anyone know this and can help me. What I should mention perhaps is, that the link for the HTC-Drivers does not work correctly, so I couldn't install them. when I connect my phone to my PC, there is some Driver-software installed from my phone. As my PC then recognizes the phone, I hope, this is ok?!
Click to expand...
Click to collapse
Error 155 means that you have not relocked the 2.02.0002 bootloader. You must relock the bootloader before you can install a RUU.
tpbklake said:
Error 155 means that you have not relocked the 2.02.0002 bootloader. You must relock the bootloader before you can install a RUU.
Click to expand...
Click to collapse
UUUPS! Didn't I read somewhere, that bootloader in version 2.02.0002 has to be unlocked for downgrade? But if you think so, I will try and report. And to relock, I use the HTCdev or what?
Yesterday I tried to downgrade with relocked bootloader but got another error, while running the RUU (I think, it was error 140 - wrong bootloader). With an alternative RUU it didn't work neither. So if anyone could help, I would be thankful.
OK, I finally found the mistake, I had made. I had put some of the required things for the runme.cmd into the wrong place. Tokk some time to find it out. Now I'm happily rooted and s-off. So this thread may be closed.
derkleinebroicher said:
OK, I finally found the mistake, I had made. I had put some of the required things for the runme.cmd into the wrong place. Tokk some time to find it out. Now I'm happily rooted and s-off. So this thread may be closed.
Click to expand...
Click to collapse
This thread is not made for you or by you so don't ask for the impossible
nlooooo said:
This thread is not made for you or by you so don't ask for the impossible
Click to expand...
Click to collapse
lol why would we want to close this? Its a helpful instruction thread
Yeah, you,re right of course. Must have been to tired after hours of trying to get s-off. Off course, this thread may NOT be closed, as it is really awesome!!
Thanks everyone for the positive feedback !
destroyer313 said:
Hi Epilogue,
I've registered on xda just to say thank you. Specifications you mentioned are same with my phone's. So I followed the instructions step by step. I did exactly what you did. Finally, I have a rooted, unlocked and S-Off phone. This is the best guide on xda about Incredible S and you did great job. Other guides look complicated for newbies. This thread is highly useful, so I'm appreciated for your help and effort. I want to ask a few questions if you don't mind.
After the installation of BlackRose, can I flash any ROM I'd like ? I mean, are there any ROM that I must get back to Revolutionary in order to work the ROM properly ? Besides, which ROM do you prefer in your device ? CyanogenMod 7 looks smooth and fast, but I'd like to flash JellyBean ROM. However, JB ROMs that Nikhil007 made for IncS, seem buggy and I've no idea which one is fastest and stable. Hope you suggest me something about it. Thank you so much.
Click to expand...
Click to collapse
Glad it could help you, thanks for the opinion !
After BlackRose, I think every ROM should work properly, but to be sure check the requirements on the ROM you'd like to flash.
Personally, i tried Viper Vivo (which is endlessly customizable), but had some lag issues with it, along with the camera not working. So I tried Cyan Vivo JellyBean (that one), which looks great and works just fine, fast and stable, although it has less features than ViperVivo does. I've had some issues with the camera lately, but maybe i should just try to reflash it.
Anyway, don't hesitate to check that topic as I mentioned in the guide, where you can compare latest updates and ROMs.
To flash, following step 10 just as before should do it !
htcdev.com: Unlocking Bootloader
congratulation for the guide!
i'm following it to root my phone.. but i have a question:
In htcdev.com/bootloader have i to follow all the steps or only some of them?
Because from step 5, it's necessary to install the SDK Manager.exe and and put in folder C:/Android the 3 files
- adb.exe
- AdbWinApi.dll
- fastboot.exe
but in this folder I have already this files, created during the unzipping action as describe in this guide at step 1 // DOWNLOAD AND SET UP EVERYTHING
> Unzip IncS_MVDTKv3.4.1.zip into C:/Android/Downgrade/DowngradeKit - Move everything from the "files" folder to C:/Android
Click to expand...
Click to collapse

[Q] where to proceed next? - i F'd up!

all,
it was with reckless abandon and blind/naive decisions that got me to this point. i will just lay it all out what ive done in the hopes one of you brilliant minds will lead me into the light. before i lay out the steps in which ridiculous choices led me to this conundrum, here is the question...
Where do i go from here to resolve the issue that i have and can get into bootloader (tampered/unlocked and in S-ON) but i have no operating system?
keep in mind that Ive probably and admittedly should not have been dabbling in things i had no business doing with the little to no proper due diligence...."i am awarded no points and may god have mercy on my soul!!!!!!!!!!!!"
1) i used the htc dev process to unlock my bootloader and it worked well.
2) i then proceeded to flash some custom recovery .img files via "fastboot flash recovery <insert filename here" and the .img at the end of course.
recovery-clockwork-touch-6.0.3.4-m7 <---didnt take the first time or anytime. kept saying "entering recovery" but then the screen would go black, not boot into the recovery screen and then the phone would reboot as it would normally and go into stock OS
i then tried the following .img files below, all with the same result...
openrecovery-twrp-2.6.0.1-m7
openrecovery-twrp-2.6.0.0-m7
openrecovery-twrp-2.5.0.0-m7
recovery-clockwork-6.0.3.2-m7ul <<<---this was the only recovery .img file that would take so i then decided to play around with the options.
3) i then proceeded to make another ridiculous choice. under one of the options in clockwork recovery "classic" menus i went forth and selected the "wipe data/factory reset" option.
so what i have now is i believe a htc one sprint phone that has bootloader unlocked with what i believe is no OS. i hear on my computer the sound when it connects via "fastboot usb" but obviously the computer doesn't recognize it so i can copy and paste a zip file onto it.
i was looking at a few threads here and could really use some guidance/encouragement. the threads are
http://forum.xda-developers.com/showthread.php?t=2277892 <<< the FAQ sticky
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [ROM] stock sprint one 1.31.651.2 thread
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [RUU] sprint htc one 1.29.651.10 thread
what would be the best course of action for me to take? bear in mind that the end result would probably be obviously a working phone, probably stock or w/e seems best.
thank you for taking the time in reading my post. if you require any additional information, please ask. i am probably leaving out important pieces of info.
deadly
All you need to do is fastboot flash recovery a working recovery then check and see if adb works for you in recovery.
If it does then you can adb push a Rom to /sdcard and flash it in the recovery.
Sent from my HTCONE using xda app-developers app
insuusvenerati said:
All you need to do is fastboot flash recovery a working recovery then check and see if adb works for you in recovery.
If it does then you can adb push a Rom to /sdcard and flash it in the recovery.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
thank you for your quickresponse.
as i am very very "scared" to this up any further. what would the suggested "working recovery" file i should choose and then what rom should i use? honestly im tempted at the stock one that i linked but im worried that if that doesnt go smoothly, i will lose my unlocked bootloader feature.
deadlytwin said:
thank you for your quickresponse.
as i am very very "scared" to this up any further. what would the suggested "working recovery" file i should choose and then what rom should i use? honestly im tempted at the stock one that i linked but im worried that if that doesnt go smoothly, i will lose my unlocked bootloader feature.
Click to expand...
Click to collapse
Use this tool, you cant mess up http://forum.xda-developers.com/showthread.php?t=2236814 just make sure you use the Sprint recoveries and download and sideload a sprint Rom.
Konfuzion said:
Use this tool, you cant mess up http://forum.xda-developers.com/showthread.php?t=2236814 just make sure you use the Sprint recoveries and download and sideload a sprint Rom.
Click to expand...
Click to collapse
THANKS! i saw this thread earlier. ill take a look. ive at least watched wwjoshdew's video and i think that should work too. downloading the stuff now.
just tried wwjoshdew's directions. looks like i cant do the RUU 1.29xxxx. it goes through all the steps but at the end it says error because of the 1.31xxxx version i have already. i guess that means i have to wait until someone releases an RUU for 1.31.651.2
and if i am not sure if usb debugging mode ins enabled and i cant get back into normal bootup for the phone because i think i wiped my OS like stated in my first post. is my next step to do hansoon's AIO tool kit?
deadlytwin said:
all,
it was with reckless abandon and blind/naive decisions that got me to this point. i will just lay it all out what ive done in the hopes one of you brilliant minds will lead me into the light. before i lay out the steps in which ridiculous choices led me to this conundrum, here is the question...
Where do i go from here to resolve the issue that i have and can get into bootloader (tampered/unlocked and in S-ON) but i have no operating system?
keep in mind that Ive probably and admittedly should not have been dabbling in things i had no business doing with the little to no proper due diligence...."i am awarded no points and may god have mercy on my soul!!!!!!!!!!!!"
1) i used the htc dev process to unlock my bootloader and it worked well.
2) i then proceeded to flash some custom recovery .img files via "fastboot flash recovery <insert filename here" and the .img at the end of course.
recovery-clockwork-touch-6.0.3.4-m7 <---didnt take the first time or anytime. kept saying "entering recovery" but then the screen would go black, not boot into the recovery screen and then the phone would reboot as it would normally and go into stock OS
i then tried the following .img files below, all with the same result...
openrecovery-twrp-2.6.0.1-m7
openrecovery-twrp-2.6.0.0-m7
openrecovery-twrp-2.5.0.0-m7
recovery-clockwork-6.0.3.2-m7ul <<<---this was the only recovery .img file that would take so i then decided to play around with the options.
3) i then proceeded to make another ridiculous choice. under one of the options in clockwork recovery "classic" menus i went forth and selected the "wipe data/factory reset" option.
so what i have now is i believe a htc one sprint phone that has bootloader unlocked with what i believe is no OS. i hear on my computer the sound when it connects via "fastboot usb" but obviously the computer doesn't recognize it so i can copy and paste a zip file onto it.
i was looking at a few threads here and could really use some guidance/encouragement. the threads are
http://forum.xda-developers.com/showthread.php?t=2277892 <<< the FAQ sticky
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [ROM] stock sprint one 1.31.651.2 thread
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [RUU] sprint htc one 1.29.651.10 thread
what would be the best course of action for me to take? bear in mind that the end result would probably be obviously a working phone, probably stock or w/e seems best.
thank you for taking the time in reading my post. if you require any additional information, please ask. i am probably leaving out important pieces of info.
deadly
Click to expand...
Click to collapse
first off thats the wrong recovery, you want openrecovery-twrp-2.5.0.0-m7wls.img (this is for sprint the m7 is international)2.6 has been giving some problems, don't know if they have it worked out yet, 2.5 is good, so
deadlytwin said:
just tried wwjoshdew's directions. looks like i cant do the RUU 1.29xxxx. it goes through all the steps but at the end it says error because of the 1.31xxxx version i have already. i guess that means i have to wait until someone releases an RUU for 1.31.651.2
and if i am not sure if usb debugging mode ins enabled and i cant get back into normal bootup for the phone because i think i wiped my OS like stated in my first post. is my next step to do hansoon's AIO tool kit?
Click to expand...
Click to collapse
Use the tool I posted above and try to install htc drivers, install recovery and sideload a SPRINT rom. You could also try s-off and follow this guide for RUU on 1.31 if your still having trouble. http://forum.xda-developers.com/showthread.php?t=2390821
Konfuzion said:
Use the tool I posted above and try to install htc drivers, install recovery and sideload a SPRINT rom. You could also try s-off and follow this guide for RUU on 1.31 if your still having trouble. http://forum.xda-developers.com/showthread.php?t=2390821
Click to expand...
Click to collapse
appreciate it!
Update: yea my phone is not in usb debugging mode. ><
Aldo101t said:
first off thats the wrong recovery, you want openrecovery-twrp-2.5.0.0-m7wls.img (this is for sprint the m7 is international)2.6 has been giving some problems, don't know if they have it worked out yet, 2.5 is good, so
Click to expand...
Click to collapse
ill check this.
Update: im in recovery now. next step isnt looking so good ><
so this is starting to look bleak. i am now able to get into recovery but i cant do adb sideload. it fails. has it got to do with the possibility that usb debugging was not turned on before i wiped data?
any ideas on my next try?
deadlytwin said:
so this is starting to look bleak. i am now able to get into recovery but i cant do adb sideload. it fails. has it got to do with the possibility that usb debugging was not turned on before i wiped data?
any ideas on my next try?
Click to expand...
Click to collapse
go to file manager in twrp and see if there is an 0 folder at the top if so delete it(make sure its empty first) then try a sideload
or use es file explorer and look at your files

[Q] First Nexus

So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Cf auto root does not remove all data per se, but unlocking your phone will if it is not.. And it's part of the process.
Rooting probably doesn't affect OTAs, and if it does, can easily be undone.
Yes, I haven't found a common root app that isn't compatible.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
1. No it does not wipe your data unless your bootloader was locked.
2. It has no effect. You'll be able to accept the OTA and lose root (you can enable a survival script).
3. Yes.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
zephiK said:
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
Click to expand...
Click to collapse
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
TheSkillfulTroll said:
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
Click to expand...
Click to collapse
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Click to expand...
Click to collapse
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
For information sake (I have already rooted via TK) your post actually does prove a point. For myself and maybe others, would you be willing to P.M me the instructions to do it via ADB/Fastboot just in case , I , myself get screwed over. Thanks Z
Sent from my Nexus 6 using XDA Free mobile app
flash you phone manually you will learn a lot about how the toolkits work.
I find it faster to flash manually than to use a tool kit.
once an OTA is available you can grap the image from the google site and flash the files manually.
There is a way to manually flash you phone and save userdata so you keep all your apps.
One you learn and get a little practice It will be so easy you will be able to flash like it is second nature. (I was a noob that came from iphone and jailbreaking)
I can actually flash the files manually faster that an OTA can update a phone and I type with maybe a total of 6 fingers. because i never took a typing class
zephiK said:
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Sent from my Nexus 6 using XDA Free mobile app
if you have drivers installed already from first link above then you can follow these steps:
Download the required factory image files to your computer and extract them
1) Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
2) If all you want to do is unlock your bootloader, skip to step 6 in this section.
3) Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
4) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
5) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
6) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
7) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu just cd to the directory.
Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-some-description-number.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot format cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
I'm not the original writer of these instructions, but I found these helpful to people wanting the step by step instructions.
TheSkillfulTroll said:
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Click to expand...
Click to collapse
Read the first couple of posts of the following threads. The first talks about how to root, and the other, about how to flash the factory images. Very detailed.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
How true. I certainly don't want a paper weight...
Larzzzz82 said:
How true. I certainly don't want a paper weight...
Click to expand...
Click to collapse
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
zephiK said:
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
Click to expand...
Click to collapse
I agree the hardest part for me was on windows trying to get the stupid drivers to work correctly.
Dumped windows for Linux and followed the manual steps i found on XDA and never looked back.
No drivers needed in Linux either.
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
TheSkillfulTroll said:
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah ok, this is what i was looking for.
miike1106 said:
Ah ok, this is what i was looking for.
Click to expand...
Click to collapse
Or... You could live dangerously and try a dirty flash first every time... Worst case... You go back and wipe in recovery
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
You can dirty flash but this is only the case when you update from the same ROM to a newer update of the version.
When we say wipe, it only wipes the OS not internal storage.

Categories

Resources