Related
I decided I wanted to root my phone and play around with some custom roms, but as I'm a complete hacking/modding noob I decided to go the easy route and unlock my bootloader with HTC dev then flash a custom rom. Whilst this has worked perfectly for me I decided I want to go the whole hog and re-lock the bootloader then S-OFF as I am currently S-ON, as this will make it easier for me to quickly flash multiple roms etc. I understand to re-lock the bootloader you use the command
Code:
fastboot oem lock
but I read somewhere if you do this whilst using a custom rom this can brick your device? If this is true then I want to use an RUU to put my phone back into stock then re-lock it then S-OFF. This will also mean that if I ever needed to give my phone for repair my bootloader should say *locked* instead of *relocked* if I ever S-ONed again. However I have no experience or knowledge of using RUUs and I don't even know which one to use. Can someone help me?
EDIT: My HBoot remains unchanged so will I just have to run an RUU?
I looked at the DS RUU thread and there's 3 with my baseband and region (i was unbranded):
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08...
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08...
RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08...
Which one do I use? And how do I run it?
SOLUTION
take a look at my thread . this wil get you back to stock u will need to change your misc_version so you will be able top use the lowest RUU avalible. here's the link mate -----> http://forum.xda-developers.com/showthread.php?t=1609499
PLEASE USE THE RUU U WANT TO GET BACKTO STOCK THEN GO INTO FASTBOOT AND TYPE fastboot oem lock that will lock up your bootloader then you will be back to stock if u get stuck mail me on here and ill help you. another guy from india had the same problem and i helped him for 2 days straight and i got his phone back on so if u mess up in any way just mail me and dont stress about it im always here to help people mate okay in any need to speak with me give me your number and i will contact u by phone and guide u what to do and get it working 100% my friend okay take care hope u get it sorted buddy
Thanks but is it necessary to flash the hboots as I haven't touched mine? Mine is still 2.00.0002
Duke_Nuke said:
Thanks but is it necessary to flash the hboots as I haven't touched mine? Mine is still 2.00.0002[/QU
EDIT. i just read over your 1st post again so now i can help you. i will pm u exactly what to do okay
Click to expand...
Click to collapse
paul.robo said:
Duke_Nuke said:
Thanks but is it necessary to flash the hboots as I haven't touched mine? Mine is still 2.00.0002[/QU
EDIT. i just read over your 1st post again so now i can help you. i will pm u exactly what to do okay
Click to expand...
Click to collapse
XDA is a forum meant to share ideas and help openly, appreciate if we keep it that way rather than sending out instructions on PM
Click to expand...
Click to collapse
suku_patel_22 said:
paul.robo said:
XDA is a forum meant to share ideas and help openly, appreciate if we keep it that way rather than sending out instructions on PM
Click to expand...
Click to collapse
im helping a guy who is new to this sort of modding. if this is how i want to help thats my choice. its not upto u to say how i help other's. i have my guides to help the more advanced. to help noobs i help via pm. its then upto them to share how they did it. dont judge people. he is new. chucking him into other guides and helping on here will get him confused as other people would jump in and give all diff ways to do it. i have given him the very best and noob proof way to get his phone back to stock then i have provided him the files and a guide needed to get his phone downgraded ready for revolutionary. thats my way dont like it dont come onto here and messege about it
Click to expand...
Click to collapse
yeah sorry suku but paul is being really helpful, I couldn't do it without this communication, I may write a guide or a summary of what I did afterwards
may i know how this one ended up? i'm a noob and i also need some help on this. I unlocked the bootloader from htc dev and rooted using superoneclick.. i'm still s-on with hboot 2.00.0002.. i would like to go back to stock and try another method where i can have s-off..
Official unlocked devices with hboot 2.0..... can not S-OFF. Must downgrade hboot.
el_roi said:
may i know how this one ended up? i'm a noob and i also need some help on this. I unlocked the bootloader from htc dev and rooted using superoneclick.. i'm still s-on with hboot 2.00.0002.. i would like to go back to stock and try another method where i can have s-off..
Click to expand...
Click to collapse
if you still need help let me know ill add you on gtalk and ill help you get your phone s-off properly. after we finish you or me can write up a noob proof guide to help other people let me know mate im ALWAYS willing to help and im always online dont ever hesitate to send me a private message take care
that would be great.. i'll send you a pm..
I do feel that a guide should be written if other people are having the same problem... I would write one but I've forgotten most of the stuff we did
your a nice person paul.robo
its nice to know that your so helpful mate. i now know the 1st person to talk incase something goes horribly wrong with my phone
P.S. sorry for being off-topic.
paul.robo said:
if you still need help let me know ill add you on gtalk and ill help you get your phone s-off properly. after we finish you or me can write up a noob proof guide to help other people let me know mate im ALWAYS willing to help and im always online dont ever hesitate to send me a private message take care
Click to expand...
Click to collapse
Thanks a lot.. took us 2 days to solve the problem.. i'll try to review the things we did and try to make a guide when i have time.. once again, thank you so much paul...
el_roi said:
Thanks a lot.. took us 2 days to solve the problem.. I'll try to review the things we did and try to make a guide when i have time.. once again, thank you so much Paul...
Click to expand...
Click to collapse
No problem. I'm here to help all forum member's it also took me a few days to sort Duke_Nuke's problem also but we prevailed and his phones now working again this is what i am on this forum for. To help people that need help. Any time you need me send me a PM or add me on G-talk my email is [email protected] add me and give me all details of your problem so i can get to work on getting your phone back on . but i must stress. once you have got your phone back on please write up a guide on how we got your phone back on to help others
Not really a guide as such but a rough summary of what happened:
1. First, I had to get my phone back to stock. My bootloader was unlocked so I had to lock it first to run the RUU, using the command fastboot oem lock however that will show up on your bootloader as *relocked* instead of *locked*, so your warranty will still be void, but it'll be fully locked once you have run the RUU.
2. At this point I flashed stock recovery.
3. You then need to run an RUU, to make this easier you can change the misc version, the files for which is attached. This basically means you should be able to run any Desire S RUU and it will work. However the one I originally tried didn't work anyway, so I had to try a second, which worked. You may need to look around and try different ones.
4. Then I S-OFFed my ds using revolutionary.io Just follow the instructions on your screen.
5. Finally flash the hboot.img (attached) which is necessary if you want to return your phone back to stock. Then flash your rom of choice.
As I said, this is just a summary of what I did and is not a guide to be followed by the letter.
Let me also add what we did.
So before we started I was on
*UNLOCKED*
SAGA PVT S-ON RL
HBOOT-2.00.0002
With misc version: 2.10.401.8 –check by going to fastboot and on your computer open cmd and cd to your android sdk folder then type fastboot getvar all.
1. The first thing we did was to lock the bootloader (fastboot oem lock)
2. Then we tried changing the misc version with the one duke attached (or see attachment on see previous post), but it didn’t work. So we tried another one (see attached files). To see if it works, just run the .bat file with the booted device connected to the computer. make sure USB debugging is enabled and fast boot is disabled. If the screen just flashes it means it’s not working. You can double check by looking at the results of fastboot getvar all.
If the attached files don’t work, try entering the codes manually. Still, your phone should be connected with USB debugging on and fast boot off.
a. Open cmd and cd to the tools folder of the attached file.
b. Once you’re sure that your on the tools folder, enter the following codes (one code per line. So you’ll have to press enter after every code):
adb push misc_version /data/local/tmpadb shell chmod 777 /data/local/tmp/zergRush adb shell chmod 777 /data/local/tmp/misc_versionc. (when everything is finished, type)
adb shelld. (you will now be on the $, then type)
./zergRushe. (some things will appear, wait for it to finish. It will say on the last part “[+] Killing ADB and restarting as root... enjoy!”. Then type)
adb shell /data/local/tmp/misc_version -s 1.27.405.6f. After it’s finished, your misc version will now be 1.27.405.6. You can double check that again.
3. Now run the correct RUU for your region/brand. My phone is unbranded and it’s European so paul gave me an unbranded European RUU. You can check out his thread for the RUUs here.
4. Once the phone has booted back, turn on USB debugging and disable fast boot then go to revolutionary.io. Follow the steps on how to s-off.
5. Then flash the eng.hboot.img that duke attached (or see attached file on previous post). To do this, first you should download the file. Then copy the file on your android sdk folder. Connect your phone to your computer and go to fastboot. Open cmd and type “fastboot flash hboot eng.hboot.img” (without the “” of course ). After it’s finished, reboot to bootloader. Now your hboot will say saga pvt eng s-off.
DONE. All credits to paul.robo.. Thanks for helping
el_roi said:
Let me also add what we did.
So before we started I was on
*UNLOCKED*
SAGA PVT S-ON RL
HBOOT-2.00.0002
With misc version: 2.10.401.8 –check by going to fastboot and on your computer open cmd and cd to your android sdk folder then type fastboot getvar all.
1. The first thing we did was to lock the bootloader (fastboot oem lock)
2. Then we tried changing the misc version with the one duke attached (or see attachment on see previous post), but it didn’t work. So we tried another one (see attached files). To see if it works, just run the .bat file with the booted device connected to the computer. make sure USB debugging is enabled and fast boot is disabled. If the screen just flashes it means it’s not working. You can double check by looking at the results of fastboot getvar all.
If the attached files don’t work, try entering the codes manually. Still, your phone should be connected with USB debugging on and fast boot off.
a. Open cmd and cd to the tools folder of the attached file.
b. Once you’re sure that your on the tools folder, enter the following codes (one code per line. So you’ll have to press enter after every code):
adb push misc_version /data/local/tmpadb shell chmod 777 /data/local/tmp/zergRush adb shell chmod 777 /data/local/tmp/misc_versionc. (when everything is finished, type)
adb shelld. (you will now be on the $, then type)
./zergRushe. (some things will appear, wait for it to finish. It will say on the last part “[+] Killing ADB and restarting as root... enjoy!”. Then type)
adb shell /data/local/tmp/misc_version -s 1.27.405.6f. After it’s finished, your misc version will now be 1.27.405.6. You can double check that again.
3. Now run the correct RUU for your region/brand. My phone is unbranded and it’s European so paul gave me an unbranded European RUU. You can check out his thread for the RUUs here.
4. Once the phone has booted back, turn on USB debugging and disable fast boot then go to revolutionary.io. Follow the steps on how to s-off.
5. Then flash the eng.hboot.img that duke attached (or see attached file on previous post). To do this, first you should download the file. Then copy the file on your android sdk folder. Connect your phone to your computer and go to fastboot. Open cmd and type “fastboot flash hboot eng.hboot.img” (without the “” of course ). After it’s finished, reboot to bootloader. Now your hboot will say saga pvt eng s-off.
DONE. All credits to paul.robo.. Thanks for helping
Click to expand...
Click to collapse
hello im having problems with this guide i cant get the second line
the comands say that there is no such file or directory
.. pls help
It is a while ago when i did this. My problem was a file with a. .c after it. I googled for the correct file. This was somewhere to find in xda. I think you need the file without the. . c.
Sent from my Desire S using xda app-developers app
first line is missing, should be:
Code:
adb push zergRush /data/local/tmp
*****
EDIT: PLEASE READ!!!!!!! Before proceeding, you need to find out which hboot your device has and if your device is S-ON or S-OFF. Ensure that Settings>Power>Fast Boot is unchecked and power down your device. Once your device is powered down, hold Power+Volume Down until you reach the bootloader screen.
On the second line, it should say "DOUBLESHOT PVT SHIP S-ON" or "DOUBLESHOT PVT SHIP S-OFF." If you are already S-OFF, great! You can flash a custom recovery in step 5 of this guide (although you need to have ADB/Fastboot installed on your Windows PC).
Your device is most likely S-ON. If so, continue reading. On the third line, your hboot information should be listed. If you have HBOOT-1.45.0013, you have the newer hboot and can follow this entire guide to achieve root. Most newer devices have HBOOT-1.45.0013.
If by chance you have the older HBOOT-1.44.0007, you have two options for rooting your device:
1. Use Revolutionary.io to gain S-OFF on your device. After using Revolutionary to achieve S-OFF, you can install adb/fastboot on your computer (in case you haven't done so already) and continue from step 5 of this guide to flash a custom recovery and Superuser for root,
OR
2. Update to latest OTA release and use this guide from beginning to end. You can update to the latest OTA release by going to Settings>About Phone or by using Blue6IX’s post “How-To: Restore to Stock.” Either method will update you to the latest OTA release (1.63.531.2) and HBOOT-1.45.0013.
IMPORTANT NOTE: If you update to latest OTA release with HBOOT-1.45.0013, you will NOT be able to revert back to the older hboot and S-OFF unless you use JuopunutBear to S-OFF. This involves a "wire trick" that some people are not comfortable with.
Many users have successfully achieved S-OFF with JuopunutBear (including me), but others have reported that it bricked their phone. This is usually because they do not follow the directions that say not to touch the bare wire. Check out the JB S-OFF threads here and here for other users’ experiences.
Confused about S-ON vs S-OFF? S-ON, Revolutionary S-OFF, and JuopunutBear S-OFF are described in detail here.
Revolutionary S-OFF is for HBOOT-1.44.0007. JuopunutBear S-OFF is for HBOOT-1.45.0013. Got it? Good.
*****
This is a step-by-step guide for rooting the MT4GS, designed specifically for new users (aka NOOBS), by a noob. The process is slightly more complicated than rooting other devices (i.e. Samsung), but it is well worth it.
The MT4GS is one of the best qwerty phones on the market and has some of the best developers. Don’t let the process discourage or intimidate you. Just FOLLOW EACH STEP IN SEQUENTIAL ORDER and you’ll be fine.
Here’s a breakdown of the process:
1. INSTALL HTC DRIVERS ON YOUR PC.
2. INSTALL ADB AND FASTBOOT ON YOUR PC.
3. REGISTER AT HTC DEV.
4. UNLOCK BOOTLOADER THROUGH HTC DEV.
5. INSTALL A CUSTOM RECOVERY.
6. ROOT YOUR DEVICE.
7. USE JUOPUNUTBEAR TO GAIN S-OFF (OPTIONAL).
-PREREQUISITES-
Before getting started, please visit the MT4GS Compendium and read over Section One to learn the XDA Lingo. You really need to know this stuff if you’re going to tinker with the MT4GS.
Also, all information in the guide assumes you are using a Windows PC and a MT4GS with the STOCK ROM AND HBOOT-1.45.0013. If you are not on the Stock ROM, please use Blue6IX’s post “How-To: Restore to Stock.” Be sure to use the latest OTA (1.63.531.2). Once you're all set, let’s begin, shall we?
Disclaimer: I am not responsible for anything that happens to your phone. You assume all risks associated with modifying your phone.
-1. INSTALL HTC DRIVERS ON YOUR PC.-
Install the HTC Drivers on your PC from here.
Before connecting your phone, make sure USB Debugging is enabled (Settings>Applications>Development>USB Debugging).
Tip: to save time later, turn off your phone, hold down Power & Volume Down simultaneously until you reach the bootloader. Use the volume buttons to navigate to FASTBOOT and select it with the power button. Connect your phone via USB and the bootloader should now say FASTBOOT USB mode. Allow your PC to install the required drivers automatically. It may take a few minutes for your PC to search for and install drivers, so be patient.
-2. INSTALL ADB AND FASTBOOT ON YOUR PC.-
Installing ADB and fastboot on your PC is easy. Follow this guide and you’re good to go. To confirm that you have successfully installed ADB and fastboot, connect phone (with USB Debugging enabled) to PC via USB, open command prompt, and type “adb devices”. Your device ID number should be listed. Here are some useful commands for ADB and fastboot.
-3. REGISTER AT HTC DEV.-
Self-explanatory. Visit HTCDev.com and sign up with a valid e-mail address, as you’ll be receiving your Unlock_code.bin from HTC through this e-mail. Use an alternate browser such as IE, Google Chrome, or Mozilla Firefox if HTC Dev doesn’t play nice with your current browser of choice. Personally, I had to switch between Chrome and Firefox to get the HTC Dev website to cooperate.
-4. UNLOCK BOOTLOADER THROUGH HTC DEV.-
Make sure you’re logged in to HTC Dev and follow on-screen instructions to unlock bootloader. FYI, our device is listed as “myTouch 4G Slide (T-Mobile US)”. You can skip HTC’s instructions until step 5 since they're just telling you how to install ADB and fastboot, but you should already have ADB and fastboot installed .
After you finish unlocking the bootloader, the first line in your bootloader should read “*** UNLOCKED ***”.
-5. INSTALL A CUSTOM RECOVERY.-
Download official ClockworkMod Recovery 5.0.2.7 from the ROM Manager website or download another custom recovery from the MT4GS Development section. For instruction purposes, I will assume that you use official CWM Recovery 5.0.2.7. Save the img file to C:\.
Put your phone in bootloader FASTBOOT mode and connect to PC. Go to command prompt on PC and type “fastboot devices”. Once your device ID is listed, type “cd\” to get to “C:\” directory. Then type “fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img”.
After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping.
NOTE: Use volume buttons or trackpad to navigate through CWM Recovery 5.0.2.7. Select items by pressing the trackball. Power button may make your screen go blank and Back button returns you to the previous menu.
-6. ROOT YOUR DEVICE.-
Now that you have a custom recovery, you can flash custom ROMs. These custom ROMs are already rooted with Superuser and binary files.
NOTE: If you are S-ON, installing a custom ICS ROM will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
HOWEVER, if you want to root the STOCK ROM and/or continue to step 7 to achieve JuopunutBear S-OFF, you’ll have to root the device yourself. This is very simple. Download Superuser ZIP from androidsu.com/superuser. I can only recommend version 3.0.7 efgh because that is the only one I have tested, but newer versions may work.
Place the “Superuser-3.0.7-efgh-signed” on the ROOT of your SD card. Go to CWM Recovery and use “install zip from sdcard” to flash the Superuser zip. If installation aborts or fails the first time, try to flash the zip again until installation is complete. Reboot your phone and check in your apps to see if Superuser app is there. If so, congratulations, you have successfully rooted your stock MT4GS!
-7. USE JUOPUNUTBEAR TO GAIN S-OFF (OPTIONAL).-
Achieving S-OFF will make your life a lot easier if you want to flash custom ROMs, especially ICS ROMs. Follow instructions for JuopunutBear at unlimited.io and check out the JB S-OFF thread for other users’ experiences.
As I said before, if you are S-ON, flashing ICS ROMs will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
If you are S-OFF, you can bypass this step. For this reason alone, I highly recommend JB S-OFF if you have a half hour to spare and some courage for the wire trick. In this post, Indirect explains why JB S-OFF is superior to S-ON and Revolutionary S-OFF. Also, S-ON Unlocked, Revolutionary S-OFF, and JuopunutBear S-OFF are described in detail here.
However, if you plan on staying on stock-based/Gingerbread ROMs, S-OFF may be unnecessary for you. There are pros and cons to staying on 2.3 Gingerbread vs. upgrading to 4.0 ICS (like the stock HTC camera), but I’ll let you make that decision for yourself.
JB S-OFF NOTE: Users have reported that certain SD cards prevent JB S-OFF from working properly. If the wire trick doesn't work for you, try using another SD card and make sure it's formatted to a "FAT" file system and over 512mb in size (thanks to demkantor for this tip).
/ENDGUIDE
Hopefully this guide has helped you in some way. XDA has helped me out a lot and I simply wanted to contribute to the community that has given me so much. Feel free to share this guide with noobs in case they have questions about rooting their device (for the millionth time).
It is my hope that this guide aids in answering MOST noob root/modding/”this ROM broke my phone” questions. Noobs, please use the search function and many of the resources at your disposal BEFORE posting another thread. Everyone is here to help, so do your best not to annoy the MT4GS devs and vets.
We all were or still are noobs, so we understand your plight. However, we have seen WAYYYY too many threads that ask the same question over and over. Please consider the devs and XDAers that help you for free. Use the search function and remember to hit the “thanks” button. Thank you!
/ENDPSA
P.S. Shout out to the awesome MT4GS devs and contributors. You guys rock!
-Blue6IX
-tbalden
-kornyone
-xmc wildchild22
-strapped365
-sun_dream
-Riyal
-WeekendsR2Short
-anyone else I forgot, you go here!
P.P.S. If any links are broken, click on WeekendsR2Short's name above for alternative mirrors. Be sure to press the 'Thanks' button for him!
P.P.P.S. Thanks to ac3theone for this tip. If you begin experiencing an intermittent data issue on any ICS ROM (where your data turns on and off rapidly with a the 'H', '3G,' or data symbol flashing), try going to CWM Recovery and doing a wipe cache/dalvik and FIX PERMISSIONS. Hopefully this solves your intermittent data issue. This issue is ICS specific, so flashing back to a stock-based Gingerbread ROM should also fix the problem.
hopefull we get this sticky'd so that we gett less questions how to root. Nice guide tho
Nice topic and very helpful informations!thanks for the guide .
John9, how many phones do you have? I see you on every forum
i was originally s-off with the rev method and i followed blues how to on how to return to s-on then i updated all the way to the newest ota. I followed this guide and every link posted in the op and a couple hours later im back to s-off ( wire trick ). this guide should really be stickied! im very appreciative that you took the time to lay this out for new users! even though im not i still dont know it all
Make this thread like a cheap hotel cover!
Sent from my Bulletproof_Doubleshot using Tapatalk 2
Thanks for getting this stickied guys. If you think some info or links need to be added, let me know and I'll be glad to update the OP.
Nice guide! Thanks a lot!
Thanks for this guide, there are a lot of threads explaining how to do this but they were all over the place. Until last night, I was S-ON, unlocked but I decided to brave the wire trick and after about a million attempts, am now S-Off. I used this page as my reference starting point throughout since I had to go back to stock. Much appreciated!
I was going to unlock my device and get Clockworkmod installed, but hold off on anything else for the time being. When I went to HTC's website to obtain the unlock file, they indicated that unlocking the device would also wipe it clean. Is this the case or can you use the HTC Unlock and retain all of the current data on your device?
I was hoping to get CWM installed and then do a full backup of everything on my device as it currently stands before starting to play around with any custom roms.
HTCDev factory resets your phone no matter what. You need to do it in order to get CWM on your phone.
If you absolutely need to backup stuff that isn't on your SD card, look into finding an app that can do a backup without root (i.e My Backup). I can't personally recommend one because I've never used one.
Once you're rooted, you can use CWM and a good backup app like Titanium Backup (paid version is definitely worth it).
jjbz said:
HTCDev factory resets your phone no matter what. You need to do it in order to get CWM on your phone.
If you absolutely need to backup stuff that isn't on your SD card, look into finding an app that can do a backup without root (i.e My Backup). I can't personally recommend one because I've never used one.
Once you're rooted, you can use CWM and a good backup app like Titanium Backup (paid version is definitely worth it).
Click to expand...
Click to collapse
Alright, I figured that was going to be the case but I was hopeful that maybe I was wrong.
Thanks!
What about mytouch q non-slide?
Does this work for the new tmobile mytouch q that DOESN'T have the qwerty keyboard? Since there's no forum for this phone yet...
This won't work for the LG/Huawei MyTouch Q's. The MyTouch 4G Slide is an entirely different device made by HTC.
on HTCdev under Unlock Bootloader is doesn't show myTouch 4G Slide?!?!:crying:
It's there, I just checked. It's listed as "myTouch 4G Slide (T-Mobile US)."
jjbz said:
It's there, I just checked. It's listed as "myTouch 4G Slide (T-Mobile US)."
Click to expand...
Click to collapse
I found it now thanks, but none of the links for either custom recovery are working? What's with that? I'm doing this for my friend and unlocked his bootloader last night, but when I went to get the custom recovery none of the links work?
E4GTUser94 said:
I found it now thanks, but none of the links for either custom recovery are working? What's with that? I'm doing this for my friend and unlocked his bootloader last night, but when I went to get the custom recovery none of the links work?
Click to expand...
Click to collapse
I just checked the link CWM Recovery link in step 5 and it worked for me. Download from here if that doesn't work. Recoveries are in the first post. WeekendsR2Short was kind enough to host most of the dev-related files so make sure to press the "Thanks" button for him.
had to thank you for this well written/up to date guide
things went smooth until the wire trick, tried like 5 times and kept sober!
funny thing in the warning it said may fry sd card, so hell i had an old 128mb sd
from like 8 years ago that i have no problem throwing away. guess i need to use a
bigger card! swapped to a 4gb class 2 (next worse card i own)
worked perfect the first time! maybe add a note with the smallest amount of space
required on card (almost 100% certain the card was to blame as i didnt do anything different)
thanks again for the tut, and thanks to the unlimited.IO team, Fuses and hyuh, WeekendsR2Short and whomever else helped!
*side note, flash crashed at the very moment the phone rebooted after the successful wire trick... strange
demkantor said:
had to thank you for this well written/up to date guide
things went smooth until the wire trick, tried like 5 times and kept sober!
funny thing in the warning it said may fry sd card, so hell i had an old 128mb sd
from like 8 years ago that i have no problem throwing away. guess i need to use a
bigger card! swapped to a 4gb class 2 (next worse card i own)
worked perfect the first time! maybe add a note with the smallest amount of space
required on card (almost 100% certain the card was to blame as i didnt do anything different)
thanks again for the tut, and thanks to the unlimited.IO team, Fuses and hyuh, WeekendsR2Short and whomever else helped!
*side note, flash crashed at the very moment the phone rebooted after the successful wire trick... strange
Click to expand...
Click to collapse
I'm glad the guide helped you get root and JB S-OFF. As for the minimum SD card size, I'm not sure why your 128mb card didn't work for the wire trick.
It probably has more to do with the way a card is partitioned (FAT32, NTFS, etc.) rather than size. I'll add a note about the SD card partition to the guide for anyone else that may encounter the same issue.
Now that you're S-OFF, enjoy flashing all the awesome ROMs from the Dev section!
It's the steps I took to get s-off after upgrading the phone and keeping it until the warranty wore out
1.Follow amidabuddha’s guide to abd and fast boot installation(be sure to thank him its the button on the bottom left of the post)
here:
http://forum.xda-developers.com/showthread.php?t=1272595
2.Go to http://www.htcdev.com/ and follow the instructions to unlock your phone
“note use all other supported models”
3.Install this program onto your phone http://www.4ext.net/get.php?apk
and use it download the latest stable version of recovery and transfer and unzip recovery.img file to where you installed fastboot and abd on your computer.
4.On your phone go to settings/power and make sure fastboot is turned off and then turn off.
Hold the vol down button and power button until you enter the bootloader connect the usb and select fastboot using the power button as select and vol buttons as up and down
5.Now on the computer go to where you installed fastboot and abd and right click while holding shift and select open command window here.
Type the following into the command window
fastboot getvar cid(“write this down and keep it for future knowledge”)
fastboot flash recovery recovery.img
Extrecovery should now be installed
Now type:
fastboot reboot-bootloader
And select recovery from the menu
6.In recovery go to install from sd card and then choose a zip from sd card
Should be something like this cwm-superSu-v0.94.zip
http://forum.xda-developers.com/showthread.php?t=1742522 (“you can download it from here plz thank ArcMan09”)
7.reboot the phone this time letting it boot up
connect the usb select charge only
in the command console
type
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version –s 1.27.405.6
Exit
adb reboot-bootloader
What was entered above should now actually appear in fastboot
8.now use
fastboot oem lock
Whole bunch of stuff comes up but most likely your now locked again
9.Go here
http://pastebin.com/raw.php?i=YcnM8Sr9
rember that thing I told you to write down find it in the table and take note
in fact write the corresponding one down as this is tell you the ruu you must download
Now open the required ruu on the computer
You can download from here(“plz thank football”)it’s the button on the bottom left of posts
http://forum.xda-developers.com/showthread.php?t=1002506
it should be something like this:(this may not be the right one for your phone you should have checked above)
RUU_Saga_hTC_Asia_India_1.47.720.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199605_signed
10.connnect your phone to your computer in fastboot like before
open the ruu on the computer
let it run following the instructions
now if you check the hboot it should say your have something 0.98.0000 S-ON
this means you can now use http://revolutionary.io to s-off your phone
now go back up and flash your desired recovery and rom of your choosing as well as superuser
I recommend the recovery we installed before("you will have to flash this through fast boot again")
Either
Viper Saga
or
Fallout Evolution
Both are senses roms
Recommended things to install after rooting your phone
a rom backup app:Rom manager:might come with the rom
an antivirus: avast(“you can use the root install method”)
4ext recovery control-(or updater for free but control will save you a lot of time)
Superuser but that will likely come with the rom but if it doesn’t
What ever else you want your done your phone is rooted and
I'm pretty sure this is how I did it please post questions or mistakes I've made on the board and remember to thank the creator of each of the links(it takes a lot of time to write these out) I'm really just collating them into something nice and easy to read as I jumped around forums trying to find the answer.
Hope this helps
I Would Like to thank some outstanding members that have helped me create this guide (please thank them they absolutely deserve it)
amidabuddha
n0elite
Skanob
Football
ArcMan09
if I have missed anyone im very sorry i've far too many pages up here just trying to recreate what steps I took to complete this task.
In other words I have to:
1)flash to a custom rom
2)flash to official ruu
3) s-off
4)flash to custom rom again
And why I shouldn't stay at first step? will I have a problem if I have a rooted s-on phone?
Billlis said:
In other words I have to:
1)flash to a custom ROM
2)flash to official ruu
3) s-off
4)flash to custom ROM again
And why I shouldn't stay at first step? will I have a problem if I have a rooted s-on phone?
Click to expand...
Click to collapse
well no you are flashing a recovery the first time then downgrading the ruu then s-off and then flash to custom ROM.
I don't know if there are newer methods out there im currently getting a new phone so im not much help in the experimentation side. but it should be pretty solid the tricky part i found was getting a hold of the right ruu all that saving the misc version and stuff is really important as its needed to downgrade.anyway good luck let me know if it works for you i haven't got too much feed back on this topic. oh and rooting is defiantly worth it opens up the phone completely and everything seems to work all of a sudden.:cyclops: YES YOU WILL NOT BE ABLE TO ROOT AN S-ON AKA SECURITY OR LOCKED PHONE. this of course refers to kernel which is normally locked(s-on) there is a bunch of other uses such as being able to set root to open items very handy worth buying (support the devs buy apps you like!!). you can just do a search on good play is it for root only or s-off apps wich will usually have some usefull tools anyway hope that helps.
I have just unlock my desire throught HTC-dev (still S-On) installed a recovery and a custom ROM. I suppose this is not the right procedure but I have not any problem with root-access apps now. btw its the third time that I have rooted this phone
you will be able to install and run these apps normally but the will be either not working or have limited functionality
use this to check your root and install these programs if you dont have them
root checker does what it says
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5qb2V5a3JpbS5yb290Y2hlY2siXQ.
busy box required for root
https://play.google.com/store/apps/...251bGwsMSwxLDEwMiwic3Rlcmljc29uLmJ1c3lib3giXQ..
superuser sets permissions for apps
https://play.google.com/store/apps/details?id=com.noshufou.android.su&feature=related_apps
as I said before it's the third time that I root my device so I know the required apps. Btw Root checker says that I have root access and any other root-required program works fine till now
First of all, thanks for this tutorial, it got me quite far!
There's one problem:
I can't get any further than step 9, because the thread with the RUU's doesn't exist anymore (http://forum.xda-developers.com/showthread.php?t=1002506)
I can't downgrade now, I've searched the whole internet for the version I need (HTC-Dutch HTC__E11), but I can't find it.
The only thing I found is from HTCdev, but the file I get from there is a .tar, and I don't know what to do with that.
I can unzip it, but the only thing I get from the file are a bunch of folders and files I can't open.
Can you please help me?
//WoZZerZ
WoZZerZ said:
First of all, thanks for this tutorial, it got me quite far!
There's one problem:
I can't get any further than step 9, because the thread with the RUU's doesn't exist anymore (http://forum.xda-developers.com/showthread.php?t=1002506)
I can't downgrade now, I've searched the whole internet for the version I need (HTC-Dutch HTC__E11), but I can't find it.
The only thing I found is from HTCdev, but the file I get from there is a .tar, and I don't know what to do with that.
I can unzip it, but the only thing I get from the file are a bunch of folders and files I can't open.
Can you please help me?
//WoZZerZ
Click to expand...
Click to collapse
Try this site, i think they are still up http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain
jugg1es said:
Try this site, i think they are still up [site]
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain
Click to expand...
Click to collapse
Thanks, but I couldn't find the version I need (HTC-Dutch HTC__E11) :crying:
Do I REALLY need to use that exact version?
WoZZerZ said:
Thanks, but I couldn't find the version I need (HTC-Dutch HTC__E11) :crying:
Do I REALLY need to use that exact version?
Click to expand...
Click to collapse
Now that, i don't know. Sorry.
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain
jugg1es said:
Now that, i don't know. Sorry.
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain
Click to expand...
Click to collapse
Since the TS uses a 1.47 version as an example, and I only found one European version of 1.47, I'm downloading that version.
I'll try to install it tomorrow.
edit:
I tried it today, and it doesn't work... The program crashes when getting device information
edit 2:
Wait, I can't get past step 7 either.
When using the first command, I get this message:
C:\android-tools>adb shell chmod 777 /data/local/tmp/misc_version
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
I tried it again with USB-debugging enabled, and this was the result:
C:\android-tools>adb shell chmod 777 /data/local/tmp/misc_version
Unable to chmod /data/local/tmp/misc_version: No such file or directory
Could somebody help me please?
EDIT 3:
I found out I had to push misc_version on the phone first, (not said in this tutorial), so I did that.
Then I could chmod it, and it worked fine.
I relocked the bootloader, and tried to install the RUU, but the RUU keeps crashing whenever it starts...
I found out I had to push misc_version on the phone first, (not said in this tutorial), so I did that.
Then I could chmod it, and it worked fine.
I relocked the bootloader, and tried to install the RUU, but the RUU keeps crashing whenever it starts...
(Sorry for the double-post, I couldn't find out how to delete my other post)
WoZZerZ said:
I found out I had to push misc_version on the phone first, (not said in this tutorial), so I did that.
Then I could chmod it, and it worked fine.
I relocked the bootloader, and tried to install the RUU, but the RUU keeps crashing whenever it starts...
(Sorry for the double-post, I couldn't find out how to delete my other post)
Click to expand...
Click to collapse
Make a GoldCard and your phone should eat any RUU :highfive:
VnnAmed said:
Make a GoldCard and your phone should eat any RUU :highfive:
Click to expand...
Click to collapse
I don't think the phone is the problem here, the RUU keeps crashing while the phone is ready to accept it.
The problem is that the list of RUU's on XDA-developers is gone (see step 9 in the tutorial, the link is dead), so I might not have the right version.
I've searched everywhere, but I can't find the exact RUU I need according to the tutorial.
WoZZerZ said:
I don't think the phone is the problem here, the RUU keeps crashing while the phone is ready to accept it.
The problem is that the list of RUU's on XDA-developers is gone (see step 9 in the tutorial, the link is dead), so I might not have the right version.
I've searched everywhere, but I can't find the exact RUU I need according to the tutorial.
Click to expand...
Click to collapse
Try here http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
The third-rate mind is only happy when it is thinking with the majority. The second-rate mind is only happy when it is thinking with the minority. The first-rate mind is only happy when it is thinking.
—A. A. Milne
O rly?
WoZZerZ said:
I don't think the phone is the problem here, the RUU keeps crashing while the phone is ready to accept it.
The problem is that the list of RUU's on XDA-developers is gone (see step 9 in the tutorial, the link is dead), so I might not have the right version.
I've searched everywhere, but I can't find the exact RUU I need according to the tutorial.
Click to expand...
Click to collapse
Yea, but as far as I get it that's what GoldCard is for. It fools your phone so the bastard is thinking that the software you're flashing is from nurturing bosom of mother fabrica so it swollows it whole no matter what it is and cries for dessert. I have UK vodafone Desire S and with GoldCard I have flashed official Asia Gingerbread Update
The exact same way i downgraded and achieved s-off on my Desire. I believe i have the correct RUU still somewhere on my laptop. I'm not at home at the moment but i can put up a dropbox link (if i'm not mistaking and still have it) tonight if you like?
Edit; typo
Sent from my HTC One X using xda premium
basd43 said:
The exact same way i downgraded and achieved s-off on my Desire. I believe i have the correct RUU still somewhere on my laptop. I'm not at home at the moment but i can put up a dropbox link (if i'm not mistaking and still have it) tonight if you like?
Edit; typo
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
If you could do that that would be awesome!
WoZZerZ said:
If you could do that that would be awesome!
Click to expand...
Click to collapse
Could you humor me and strat the Phone in fastboot, then open a command prompt and type; Fastboot getvar version main. Please post the version-main here. Just to be sure
---------- Post added at 03:01 PM ---------- Previous post was at 02:29 PM ----------
Here´s the db link, its still uploading so if its not there now wait a while. There are (or gonna be) 5 RUU´s in there, just check your version main and pick the one you need
https://www.dropbox.com/sh/engsv5p1xf9vy63/jOUwJUB55x
basd43 said:
Could you humor me and strat the Phone in fastboot, then open a command prompt and type; Fastboot getvar version main. Please post the version-main here. Just to be sure
---------- Post added at 03:01 PM ---------- Previous post was at 02:29 PM ----------
Here´s the db link, its still uploading so if its not there now wait a while. There are (or gonna be) 5 RUU´s in there, just check your version main and pick the one you need
https://www.dropbox.com/sh/engsv5p1xf9vy63/jOUwJUB55x
Click to expand...
Click to collapse
The bootloader THINKS the main version is 1.27.405.62, but that's the whole point: I had to do that in the tutorial when chmodding misc_version.
I'll try one of the RUU's thanks
EDIT:
It's installing now, I've got further than ever before! Hopefully it all works, I'll let you guys know in a few minutes
EDIT 2:
IT WORKED! Thanks!
I'm on HBOOT 0.98.0002 now, so I'll be able to achieve s-off, THANKS!
I can confirm that this tutorial also works to downgrade from HBOOT 2.02 to 0.98
Hello,
I have an HTC One Mini (m4) and have spent approximately 3 days trying to grasp various pieces of jargon and babble of the Android community without success.
Between S-OFF, S-ON, firmware, recovery, new partition layouts, old partition layouts, OTA, Stock, kernels, custom ROMs, rumrunners, firewaters, various errors, root, adb, fastboot and other meaningless pieces of broken English, I am giving up. I have spent more time ****ing with my phone than using it in the past week.
I currently run a 'version' of Sense 5.5 made by tr1gg3r3d, on Android 4.4.2. Ultimately the only thing I wanted to achieve was to have an ordinary version of Sense but without the extraneous apps that clog it up. My phone is unlocked and 'tampered' (whatever the **** that means). What I have right now does not appear to update correctly and does not run certain apps that dislike root. The SD permissions do not work.
It is more or less useless for what I need it for.
I saw a ROM for Sense 6 here that requires 'S-OFF'... after spending 3 days jumping through hoops and following badly written instructions for 'S-OFF', and failing each time, trying around 4 different ROMs and script files that tell you nothing of what they're actually doing, I have given up trying to achieve 'S-OFF'. Do I even know what 'S-OFF' is? No.
Can someone give me simple instructions on how to achieve the following:
A phone running HTC Sense 6 (or even just 5.5) that behaves normally, isn't gimped with pointless graphics and allows the extra apps to be removed.
Preferably 'unrooted' as I use apps that dislike root.
Ideally recognised as 'official' HTC so that updates can be delivered without having to spend a week wading through 90 page forum threads.
Thanks in advance.
Your 3days of reading have obviously been a complete waste of time bud as you posted in the wrong thread [emoji33]
Maybe you should have also read and understood the implications of unlocking, rooting your phone before you done so. It is well documented that certain apps eg.. banking ones etc will not work on rooted devices.. BUT there are certain modules created that can cloak root and may allow the app to work. As for removing unnecessary apps... There as also scripts/tools available to do so. It's all here on xda!
Slating a devs Rom that they have spent countless unpaid hours to bring to the xda community (that works flawlessly) is not the way to get help, nor is slating the guides/advice that other members have taken the time to post! Seems that you want the best of both worlds. There are guides on here that will help on whatever you choose to do if you can decipher all the babble/jargon and meaningless broken English.
dlyon said:
Hello,
I have an HTC One Mini (m4) and have spent approximately 3 days trying to grasp various pieces of jargon and babble of the Android community without success.
Can someone give me simple instructions on how to achieve the following:
A phone running HTC Sense 6 (or even just 5.5) that behaves normally, isn't gimped with pointless graphics and allows the extra apps to be removed.
Preferably 'unrooted' as I use apps that dislike root.
Ideally recognised as 'official' HTC so that updates can be delivered without having to spend a week wading through 90 page forum threads.
Thanks in advance.
Click to expand...
Click to collapse
Had a similar experience myself trying to return to stock, for me I was getting cheesed off with the bugs and lack of working bank apps on custom ROMS.
I fixed it by following, and reading in between the lines, on this fellows instructions here.
http://forum.xda-developers.com/htc...m-official-stock-android-4-3-sense-5-t2837799
I posted a similar help thread myself a few days ago, someone has replied to say S-OFF isn't crucial to doing this so worth a go maybe. I however did get S-OFF by using the method detailed here.
http://forum.xda-developers.com/showthread.php?t=2573479
I should tell you I was on HBOOT2.19. Not sure how important that is.
So here it was I did to get S-OFF
You've obviously got ADB working on your device so lets skip that.
1.Download revone: http://revolutionary.io/revone and copy it into the same folder as your ADB.
2. Open a CMD prompt and type these commands:
Code:
adb push revone /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/revone
Now wait a minute. I found I always got kicked out of the shell after 20 seconds or so, if you do then run adb shell once again.
3. Now type the below text. It is case sensitive so make sure that -P in the second command is uppercase:
Code:
cd /data/local/tmp
./revone -P
4.You'll get an error message, it should be "-2". This is good. Restart your phone using the power button.
5.Once you're back in open up the shell again and run the following commands:
Code:
adb shell
CD /data/local/tmp
./revone -s 0 -u
BAM! You're now in S-OFF mode.
HBOOT 2.2
I used this thread to get to HBOOT 2.22
http://forum.xda-developers.com/showthread.php?t=2584810
Whilst the instructions are fairly simple I will say it is case sensitive. So when you do
Code:
fastboot oem rebootRUU
the RUU has to be in capital letters.
How to return to stock
1. First you need to get yourself TWRP recovery from here: http://teamw.in/project/twrp2/216 and copy the .img file into the same directory as ADB and fastboot.
2. To flash the recovery you need to go into fastboot (hold the power button and the and the volume down button together from a cold boot) and type from a CMD prompt
Code:
fastboot flash recovery recovery.img
where recovery.img is the name of the download.
Mine was called openrecovery-twrp-2.7.1.1-m4.img so I'd use this text:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
3. Once you've flashed the recovery go into recovery and make a backup from the backup menu.
4. Download every file from the link provided in the first post here:
http://forum.xda-developers.com/htc...m-official-stock-android-4-3-sense-5-t2837799
5. You're going to have to use WinRAR or 7Archive to unzip the RAR files. You'll get a random folder and a stock recovery.img file.
What I did (or eventually did after lots of trail and error) was attached my phone then deleted the backup content in the TWRP folder. I did NOT delete the folders. Just the files within. Then I copied the extracted content from the download folder into the backup folder I'd just emptied on the phone.
6. Now drop back into the recovery again. First make sure what we did in step 5 worked. If you go into Restore can you see the files we generated earlier? Brilliant. Wipe the cache, factory and delvik (I think Delvik is in the advanced settings, obviously don't have it to hand now i'm back on stock!)
7. Now run a restore which should take a few minutes.
8. Reboot the phone but drop straight back into the Bootloader (power and volume down button pressed)
9. If you haven't copied boot.emmc.win into the ADB folder do so now. Whilst you're at it copy the stock recovery.img file into the same folder and rename it to stockrecovery (take the space out).
From a CMD prompt type :
Code:
fastboot flash boot boot.emmc.win/
10. Now we flash the Stock recovery using:
Code:
fastboot flash recovery stockrecovery.img
11. Now relock the OEM thingy by using
Code:
fastboot oem lock
BAM! You're back to a stock albeit a really crappy version based somewhere in the Middle East. But fear not. Boot in, setup your phone and in the Settings area you can run a software update. This will take you to Android 4.3. Once you're in run another software update to go to 4.4.2 with Sense 5.5. Once you've done that do yet another Software Update to get to 4.4.2 with Sense 6.
At this point I did a factory reset from the settings menu. Not sure if it was needed but just wanted any legacy crap completely killing off.
Also you'll see a message about it being a test device. I Google'd it and people said this is because you're S-OFF. It's not important. Nothing is going to HTC, it's merely a log file thingy.
And that my friend, is how my three day headache got me from a rather buggy custom ROM back to Stock. Enjoy.
elmuziko.
Absolutely brilliant post. I can verify that your method to s-off the phone and update to 2.22 works perfectly. I did it 2 days ago.
I changed my cid using supercid. Do you think I should return my cid to its original value before attempting to return to stock or does it matter??
danapoint said:
elmuziko.
Absolutely brilliant post. I can verify that your method to s-off the phone and update to 2.22 works perfectly. I did it 2 days ago.
I changed my cid using supercid. Do you think I should return my cid to its original value before attempting to return to stock or does it matter??
Click to expand...
Click to collapse
Hiya mate
I didn't do any of that at all, although I didn't change my CID knowingly so if it did change, I didn't change it back.
Been on stock a week now with no problems whatsoever. Working like a dream.
Cheers
thank you button is not enough
elmuziko said:
And that my friend, is how my three day headache got me from a rather buggy custom ROM back to Stock. Enjoy.
Click to expand...
Click to collapse
you know what, i just registered to this site to thank you.
i followed your post step by step and BAM, i am in back to stock rom.
thank you, it feels so good
ps: i skipped S-OFF step, so it is not a must.
Help my
Not message for phone unlock bootloader unlock token chek successfully
Failed to Get S-Off
Before my Question:
My HTC ONE MINI Details:
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.28.40e.00.24
OpenDSP-v19.2.0268.0927
OS-4.09.401.3
eMMC-boot 1024MB
Jun 24 2015, 15:21:25.0
Ok, Now, I bought this Mobile in Dubai, Middle East and while i was waiting eagerly for Lollipop Update and the HTC did the cheating, i decided to try some custom roms and in between the process i wiped my internal memory which means i lost my original stock rom. Somehow i got this M4_4.14.401.1_Stock_v3.0.0 flashed it and now my mobile works flawlessly, the thing is the mobile is "TAMPERED" "UNLOCKED" & "S-ON", i tried all the process to S-OFF, i tried sunshine but spending 25$ on something which is available free, i would not do that. Can you please suggest me what is wrong that i am doing here, because i found one more option which says i have to downgrade my HTC ONE MINI to S-Off, Pity is that to downgrade i need my mobile to be S-Off. I am really exhausted and would appreciate alot if you can help me get S-Off. There are my links which are broken, like the revone after a lots of struggle i downloaded it. i have posted 3 queries on XDA forum but none has been answered. I would Really Really appreciate if you can save me from my misery.
I'm stuck in a boot loop after trying to return to stock.
I followed precisely the instructions written by 5m4r7ph0n36uru in the section titled "Restore using a RUU".
On my BadBoyz unlocked rom where I was still on OS version 1.16.617.6 I did was flash with the latest full RUU version 2.42.617.7 then relocked my ROM with fastboot oem lock command.
I've tried clearing the cache and factory reset as instructed in HTC docs to try when stuck in boot loops. I can't get it to go past the boot screen.
Was I wrong to flash to the latest RUU I found in the spreadsheet section for my phone model? Should I have flashed with the RUU of the version I originally had on my phone to return to stock?
Any ideas would be greatly appreciated. Thanks in advanced.
I know that the OP had posted this about a week ago but I was wondering if you had your issue with the phone resolved? I found only when I used the SD card process to flash a RUU zip file I would be successful in flashing another OS/firmware. On my U11, I only was successful in first flashing a older version of the OS on to my phone before I was able to boot my phone up. On my U12+ I was successful in flashing the original (latest) OS. Good luck.
Sent from my coconut frond hut using Tapatalk
el80ne said:
I'm stuck in a boot loop after trying to return to stock.
I followed precisely the instructions written by 5m4r7ph0n36uru in the section titled "Restore using a RUU".
On my BadBoyz unlocked rom where I was still on OS version 1.16.617.6 I did was flash with the latest full RUU version 2.42.617.7 then relocked my ROM with fastboot oem lock command.
I've tried clearing the cache and factory reset as instructed in HTC docs to try when stuck in boot loops. I can't get it to go past the boot screen.
Was I wrong to flash to the latest RUU I found in the spreadsheet section for my phone model? Should I have flashed with the RUU of the version I originally had on my phone to return to stock?
Any ideas would be greatly appreciated. Thanks in advanced.
Click to expand...
Click to collapse
Hey mate can i ask did you boot the rom before locking the bootloader to see if the OS was functional ? Also how many times did you try flash the updated RUU before locking the bootloader,
Youve locked the bootloader down again anyway and will display as relocked in bootloader mode, youve made things a bit harder for yourself here,
Never ever relock the bootloader whilst the system is non functional keep it unlocked until you know the OS is ok, in general now youve locked it your device would usually require a very specific RUU full signed and exact main version match, however luckily for you if you havent already fixed it ive found a way to fix it without sending to HTC if you dont have the exact RUU needed to revive it,
What i want you to do is download the full RUU.zips for your model from the google spread sheet main version wont be an issue will be best to get all releveant RUUs with matching CID from there also
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
Now download the HTC_10 batch tool and install it
http://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
After its installed, place your RUU.zip into your local drive "C://" as an example where your batch tool is installed place the RUUs 1 at a time into /android/com, no more than 1 at a time when flashing
Full length of where RUU needs to be put in simple termns is C://android/com
Now minimise to the desktop, then right click on the batch tool icon and run as administrator,
NOT the HTC FUU icon !
Once the batch tool has booted, press the number 3 on the keyboard and then enter, this will take you to the fastboot terminal,
Take note the screen should be purple and the location on the screen should be as follows C:// is only for example your drive letter may be different,
C://Android/com
Now boot the phone to download mode and connect to pc,
Now type the following,
Fastboot devices
If that didnt work type
htc_fastboot devices
Your device should display now with a serial number,
Now type
fastboot oem rebootRUU
If that didnt work type
htc_fastboot oem rebootRUU
Now type
fastboot flash zip example.zip
If that didnt work type
htc_fastboot flash zip example.zip
!!example is the name of your RUU if you dont want to type it out drag and drop from the minimised window in C://Android/com,
Now your device will start flashing the RUU to your device, in my experience this is the only fastboot terminal that will revive a dead htc in your case without the exact signed ruu it requires,
It will also let you rollback from oreo to nougat whereas any other fastboot terminal you use will give you RUU error Main version fail in info or RUU error zip from usb command,
Try this it will work if you need clearer instructions you can check my thread out, this is pretty much the same case but without the device saying corrupt either way you still have non functional OS and oem unlock will be off FRP lock will be enabled and you wont be able to unlock the bootlaoder again without a functional OS as the full RUUs wipe the device completely resseting everything
My thread link is here for more infomation if needed
https://forum.xda-developers.com/u11/help/fixed-htc-u11corruptrelockeds-t3855157
Thanks
Hey thanks for the reply! Actually I was able to get my phone back up and working again after having gleaned quite a bit of useful info from your very informative OP.
Fortunately I didn't have to go the route of running the HTC 10 batch tool, since I really wasn't looking forward to having to set up a virtual windows machine or having to trust a windows emulator like Wine just to run a dos batch tool. Actually I got the message pretty quick reading your first post that relocking the bootloader was a pretty terrible idea and set right away to unlocking it again. I was able to do it going through the HTC routine of cutting and pasting the ASCII key to HTC web form and having the Unlock_code.bin emailed to me again. It was different from the original ascii and unlock file they sent me the first time, but it did the trick.
It was smooth sailing from there, as I was able to boot to recovery and flash TWRP, which I then used to install the latest BadBoyz rom running Oreo and it just worked.
I was a little surprised, because I was under the impression I would have to apply all my OTAs manually since I was upgrading from Marshmellow. So even though I had a busted /system partition that wasn't letting me boot into the latest HTC RUU stock, that didn't seem to matter. Flashing with the latest RUU must hav the OTAs intact on a separate partition that the latest bad boyz rom just worked out of the box.
I'd been meeting to update this post, sorry to make you type all that out again when your first post was great. It tipped me off to scrutinize that HTC10 batch script line by line to see what was so special about it. Turns out, not a whole lot; I figured I could manage to do all that running the android bridge from my linux console just fine. But it was extraordinarily insightful in practically giving me a written line by line instruction set on how to recover my phone from command line. It was about as straightforward as it gets. I totally appreciate your help! :good:
Matty1993 said:
Hey mate can i ask did you boot the rom before locking the bootloader to see if the OS was functional ? Also how many times did you try flash the updated RUU before locking the bootloader,
Youve locked the bootloader down again anyway and will display as relocked in bootloader mode, youve made things a bit harder for yourself here,
Never ever relock the bootloader whilst the system is non functional keep it unlocked until you know the OS is ok, in general now youve locked it your device would usually require a very specific RUU full signed and exact main version match, however luckily for you if you havent already fixed it ive found a way to fix it without sending to HTC if you dont have the exact RUU needed to revive it,
What i want you to do is download the full RUU.zips for your model from the google spread sheet main version wont be an issue will be best to get all releveant RUUs with matching CID from there also
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
Now download the HTC_10 batch tool and install it
http://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
After its installed, place your RUU.zip into your local drive "C://" as an example where your batch tool is installed place the RUUs 1 at a time into /android/com, no more than 1 at a time when flashing
Full length of where RUU needs to be put in simple termns is C://android/com
Now minimise to the desktop, then right click on the batch tool icon and run as administrator,
NOT the HTC FUU icon !
Once the batch tool has booted, press the number 3 on the keyboard and then enter, this will take you to the fastboot terminal,
Take note the screen should be purple and the location on the screen should be as follows C:// is only for example your drive letter may be different,
C://Android/com
Now boot the phone to download mode and connect to pc,
Now type the following,
Fastboot devices
If that didnt work type
htc_fastboot devices
Your device should display now with a serial number,
Now type
fastboot oem rebootRUU
If that didnt work type
htc_fastboot oem rebootRUU
Now type
fastboot flash zip example.zip
If that didnt work type
htc_fastboot flash zip example.zip
!!example is the name of your RUU if you dont want to type it out drag and drop from the minimised window in C://Android/com,
Now your device will start flashing the RUU to your device, in my experience this is the only fastboot terminal that will revive a dead htc in your case without the exact signed ruu it requires,
It will also let you rollback from oreo to nougat whereas any other fastboot terminal you use will give you RUU error Main version fail in info or RUU error zip from usb command,
Try this it will work if you need clearer instructions you can check my thread out, this is pretty much the same case but without the device saying corrupt either way you still have non functional OS and oem unlock will be off FRP lock will be enabled and you wont be able to unlock the bootlaoder again without a functional OS as the full RUUs wipe the device completely resseting everything
My thread link is here for more infomation if needed
https://forum.xda-developers.com/u11/help/fixed-htc-u11corruptrelockeds-t3855157
Thanks
Click to expand...
Click to collapse
el80ne said:
Hey thanks for the reply! Actually I was able to get my phone back up and working again after having gleaned quite a bit of useful info from your very informative OP.
Fortunately I didn't have to go the route of running the HTC 10 batch tool, since I really wasn't looking forward to having to set up a virtual windows machine or having to trust a windows emulator like Wine just to run a dos batch tool. Actually I got the message pretty quick reading your first post that relocking the bootloader was a pretty terrible idea and set right away to unlocking it again. I was able to do it going through the HTC routine of cutting and pasting the ASCII key to HTC web form and having the Unlock_code.bin emailed to me again. It was different from the original ascii and unlock file they sent me the first time, but it did the trick.
It was smooth sailing from there, as I was able to boot to recovery and flash TWRP, which I then used to install the latest BadBoyz rom running Oreo and it just worked.
I was a little surprised, because I was under the impression I would have to apply all my OTAs manually since I was upgrading from Marshmellow. So even though I had a busted /system partition that wasn't letting me boot into the latest HTC RUU stock, that didn't seem to matter. Flashing with the latest RUU must hav the OTAs intact on a separate partition that the latest bad boyz rom just worked out of the box.
I'd been meeting to update this post, sorry to make you type all that out again when your first post was great. It tipped me off to scrutinize that HTC10 batch script line by line to see what was so special about it. Turns out, not a whole lot; I figured I could manage to do all that running the android bridge from my linux console just fine. But it was extraordinarily insightful in practically giving me a written line by line instruction set on how to recover my phone from command line. It was about as straightforward as it gets. I totally appreciate your help! :good:
Click to expand...
Click to collapse
Glad its sorted mate,
Always keep your bootloader unlockes so you can flash unsigned firmware as unfortunately finding signed_ruu.zip with specific versions is very difficult, and batch tool contains HTC official code for flashing and also lets you flash a lower main version and rollback the bootloader from oreo back to nougat no other fastboot terminal i used would allow it when i did it would always give RUU error main version fail,
Lucky the bootloader let you flash token, mine wouldnt even let me do that i got killswitches enabled on BL, FRP & OEMunlock please unlock lol
And thats no probs on the detailed tutorials i got kinda like ocd where i gotta explain stuff really into detail haha sometimes i dont even notice, keep the BL unlocked thouhh and you should be fine