Related
Boy oh boy, I had a really tough few days trying to flash a custom rom. I was pretty heavy into flashing roms from the G1 days until I got my sensation on the day it was released. I then took a long break. Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON(security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock. And picture this living in a area with tmobile that is still using the edge network(2 ****ing g) OMFG I was so mad trying to even boot a new rom without wifi is a nightmare, took me literally 20 minutes to download rom manager. Anyway's this rom was the last one I tried before busting my phone into pieces.
Rom's I tried:
1. Android Revolution 3.6.1, and 4.1 (3.6.1 booted but had no wifi)
2. RCMix 3.5 v04 (bootloop)
3. LeeDroid booted fine (no wifi)
4. I believe there was one other I tried. NO GO
5. Then I flashed this one late last night, and to my surprised it worked.
I was so happy I almost pissed myself.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
Anyway I guess what I am getting at. For anyone else that might have to go through what I did.
1. How in the world can you get you phone back to complete stock?
2. Why is this happening?
3. Why is my wifi not working with any other rom? And everyone else's is?
4. How do I go about getting my S-OFF?
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
I probably have more question's. I just wanted to see if I might be able to get a few answers from you fine people. Help me understand what in the world is going on and how many other people are dealing with what I am dealing with.
droiddv said:
Boy oh boy, I had a really tough few days trying to flash a custom rom. I was pretty heavy into flashing roms from the G1 days until I got my sensation on the day it was released. I then took a long break. Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON(security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock. And picture this living in a area with tmobile that is still using the edge network(2 ****ing g) OMFG I was so mad trying to even boot a new rom without wifi is a nightmare, took me literally 20 minutes to download rom manager. Anyway's this rom was the last one I tried before busting my phone into pieces.
Rom's I tried:
1. Android Revolution 3.6.1, and 4.1 (3.6.1 booted but had no wifi)
2. RCMix 3.5 v04 (bootloop)
3. LeeDroid booted fine (no wifi)
4. I believe there was one other I tried. NO GO
5. Then I flashed this one late last night, and to my surprised it worked.
I was so happy I almost pissed myself.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
Anyway I guess what I am getting at. For anyone else that might have to go through what I did.
1. How in the world can you get you phone back to complete stock?
2. Why is this happening?
3. Why is my wifi not working with any other rom? And everyone else's is?
4. How do I go about getting my S-OFF?
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
I probably have more question's. I just wanted to see if I might be able to get a few answers from you fine people. Help me understand what in the world is going on and how many other people are dealing with what I am dealing with.
Click to expand...
Click to collapse
Personally i would just do the normal s-off method as it gives you a little more freedom compared to HTC unlocking method.
My wifi is dead too, but i have no way of fixing it at all, i've got a thread called "wifi is dead" in the q+a section of the sensation forum.
Let me know if you get yours working, i imagine that if you revert your phone back to stock again and then use the alpha rev method that you will have better luck.
1. You can Relock your bootloader using HTC site but this time u will see Relocked instead of Locked
2. No idea
3. Did you try resetting your router? Works for me. Also try flashing a different radio.
4. No idea
5. You can relock bootloader on HTC site but have no idea of you can unlock it with Revolutionary again.
Try write secureflag command, just search for.the correct one on xda. Also, try flashing your RUU and then s-offing via revo.
Sent from my HTC Sensation Z710e using XDA App
tinky1 said:
Try write secureflag command, just search for.the correct one on xda. Also, try flashing your RUU and then s-offing via revo again. You might need eng s-off, pm EddyOS, he should be able to help, I believe he's done it before.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Sent from my HTC Sensation Z710e using XDA App
[ Solved ] WiFi error , Radio flash Problem , and revert back to any Custom Rom
droiddv said:
Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON (security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
.
Click to expand...
Click to collapse
[Solved ] WiFi error , Flash Radio Problem , Install any Custom Rom without errors , Wrong S-on Brick
this is Solved and the wifi error is because of kernel included in Boot.img
you can use the following solution to install any custom rom without wifi errors
first read " how htc dev works " to have an understanding why this happened to you and why you are still S-on and why you can't flash Radio . link is here " Solve WiFi Errors , Radio Flashing Problem , Caused by htc Dev Unlock Method "
the solution itself is in the following link , Read title " Custom Rom Flash " and "[FONT="][ Implementation ][/FONT][FONT="] Successful S-OFF using my above method " . [/FONT]link is here " Successful S-OFF after brick (wrong S-ON) for ICS or GB , Downgrade OTA firmware "
this also solve wrong S-on Brick , hope that helps
Press the thanks Button for this Post
Hi to all, i'm jauffre and i'm new in XDA. I have a problem and, as i searched all the forum without finding an answer, i need your help.
Last week i rooted my htc incredible s using the revolutionary tool, wich upgraded the hboot to 6.13.1002. i installed with the clockwork mod recovery tool a modded rom, and it was great. but sunday my phone crashed to the ground, and now the cover is broken (so i need to send it to the warranty).
i spent last day searching a guide for dummies to unroot the phone, and using the signed RUU (downloaded from this site) it appeared to work, but my htc is still s-off.
now, i know i need to downgrade the hboot, and i tried everything (i reinstalled froyo, updated the radio and then updgraded to 2.3.3), but this is still a problem.
please, help me!
Hey guys, this is the procedure i did to solve my problem. do it at your own risk.
first of all i must say that with this process i'll have the hboot back, but NOT the bootloader (so when you hold "volume back+power on" you will see the modded bootloader, not the stock one). i don't know how did you rooted your phone, what programs did you use, and i cannot assure you this procedure will work. if you're not sure, don't do anything.
first, you have to look for the original RUU of your phone (you can find it on this site). then follow this thread to find the rom.zip file (http://forum.xda-developers.com/showthread.php?t=790022), where you can find several files. you need the android-info.txt and the hboot_xxx.img files.
open the hboot.img file with a text editor; in the first line you can find many strange symbols, and after that there will be a string of numbers (that is the hboot version).
you have to know what version of hboot have you currently on your phone (if you used the revolutionary tool, it will be probably 6.13.1002) and simply change the hboot.img string so that the release number is higher (than the modded hboot; i.e. you can write 7.09.0000).
after that you have to make a zip file with the android-info.txt and the hboot_xxx.img file you have just modified, and if you have an incredible s, call it "pg32img.zip".
if you have another device, simply you can turn on your phone in the bootloader mode, and if there's a memory card the device will look for a file, which name appears (it's the code you need).
then put that pg32img.zip file on the root of your sd card, reboot in bootloader mode (volume down+power) and follow the instructions to do the upgrade. after that, if you restart in bootloader, you'll see that the hboot version will be 7.09.0000 (the same you wrote) and will be s-on.
now, search and download the latest version of "superoneclick" (an application that should root and unroot your phone), and start it. link your phone to the pc and start the unroot process.
when it is done, simply leave your phone linked to the pc and start the RUU.exe file you downloaded. start the update process and if you have done everything good, at the end you'll have your phone with the stock hboot and the s-on.
i'm not a serious programmer, i simply was really lucky (i really didn't know if that could have worked) but i did it. i don't know how did you do the root, and how does the superoneclick work, so i am not responsible for any bricked phone.
if you are not sure, simply send your device to the htc assistance (better pay than have a new paperweight).
good luck
download superoneclick select unroot and uninstall the superuser app.Oh and download and flash your phone's stock rom
ok, thank you for the help!
there's a little problem: at the end of the superone process it says me "superuser not found", so it can't be deleted.
so i remade the root (using superone) and unrooted; then installed the RUU, but nothing: it's still s-off. what can i do now?
i tried to make superoneclick work, but with no success... although i have installed the superuser.apk, the program still says me there's no SU, and can't unroot my device.
Any suggestions?
ok guys, i did it...
first i remade the root process, and flashed the superuser.apk. then i wanted to "upgrade" the hboot, from 6.13.1002 (revolutionary) to 7.13.0000 (simply i changed the 1 to 7 opening the hboot signed image with a text editor). then i launched superoneclick, and started the unroot process. at the end, i launched the signed htc RUU with gingerbread, and now i have my htc incredible s with s-on and hboot 1.13.0000.
=)
the last thing: does someone know hot to put the original htc bootloader?
cant someone build a uniform high performance rom
i added a guide to do the process go to the first post and read it all
thanks for the guide, just one confusion here, that after putting the pd****.img into the sdcard, i need to goto bootloader right? (not recovery)
Edit: worked in first attempt . Just one suggestion if you can replace word "Recovery" with "Bootloader" inorder to avoid confusion for other users
thank you fshami! i just corrected the guide
Hi I just tried following the guide posted on the first post using the android-info.txt and the hboot_xxx.img files received by the OTA update released recently as well as one downloaded from the net "OTA_Vivo_Gingerbread_S_hTC_Asia_India_2.12.720.5-1.36.720.1_release_190041sn70bk4icw74exvv"
On both occasions the bootloader update failed.
I am unable to install the OTA update. This has been downloaded quite a few times already and the phone just hangs with the android logo screen.
P.S. My phone is an Incredible S purchased legally in India around June 2011.
Thanks.
then put that pg32img.zip file on the root of your sd card, reboot in bootloader mode (volume down+power) and follow the instructions to do the upgrade. after that, if you restart in bootloader, you'll see that the hboot version will be 7.09.0000 (the same you wrote) and will be s-on.
Sorry my friend , but this don´t work....
Sorry.....
I thought this is what I was searchinf for years but...What if I have an USB issue? Like usb brick? So I cant connect my htc with the pc x.x for superoneclick
Hello,
I try to unlock my bootloader with htcdev but i get this error :
C:\Users\Administrator>cd C:\Android
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.009s
How to fix this ? :$
I'm looking too, but for the [Doubleshot].
Trying the same thing myself on the HTC Doubleshot (MyTouch 4G Slide) and no joy, same exact error.
ericosman, did you by chance follow all the advice on HTC's site -- including specifically installing HTC Sync? I didn't install Sync because it looks like stuff I won't use and don't need, except that Sync has some dependencies (like a USB BMP Driver, whatever that is) that might make the difference. I haven't tried yet but I plan to.
I've tried two different versions of Fastboot, one I downloaded from masterjason.com and another I downloaded from Google's Android SDK manager. Both behave identically, despite one being nearly a megabyte where the other was 70 kilobytes.
I've tried reinstalling USB drivers, no joy.
I can get fastboot devices to work, as well as adb anything when the phone is booted, so I don't think drivers are really the issue.
I think it's HTC making a blanket promise that all the phones in that list can do this and indeed not all can.
[EDIT 2012-01-07: Add more info I found]
Gotta love it. Edited the post, and when saving, was told to refresh and log in. Then I wasn't given a chance to copy-paste what I typed. Annoying.
Anyway, see if I can remember what all I typed...
uhm...
I found through Google, and directed to Yet Another Android Forum somewhere on the 'net, that fastboot oem h will provide you a list of commands that are supported, and get_identifier_token was not among them. I suspect it's the phone's bootloader which contains supported commands, not Fastboot executable itself, so it may require downgrading/upgrading to a different HBOOT that has the necessary command support.
I did find readsecureflag which returns the integer "3" on my S-ON device. I assume then that the command I found called writesecureflag similarly takes an integer value, but what value to feed it, I don't know, and I don't want to risk my phone. Seems benign enough, but I know from computer programming that anything looking benign is not always.
Anyway, if you run fastboot oem h and get_identifier_token isn't there, I'd recommend giving up on this particular method of rooting.
Hope this helps.
[Edit 2012-04-15: Strikeout above no longer applicable info]
Turns out, see Aisho's post below, which sums up what eventually worked for me.
I actually had to wait for an OTA to be available long enough for a dev to package it up to a bootloader-flashable package, which included the get_identifier_token. Once I had that version on my phone, I was able to get the token to HTCDEV and get my bootloader unlocked. Not full access, but not bad: The only downside is if I need to flash a kernel I have to do it separately from the ROM through fastboot, and I don't think I can update my radio (not that I should need to). But hey, I can flash a custom ROM and get rid of this nasty crap T-Mobile thinks everyone should have (I will never play bejeweled, so I don't even want that adware/nagware on my phone).
[/edit]
I actually had this same problem with my HTC Wildfire S, and found this thread in searching for answers -- since I figured it out, I figured I'd put the solution out there.
My HBOOT was precisely the version HTC was advertising on their site as necessary for the unlock, which made it all the more perplexing when I repeatedly got this error. But then it occurred to me that while my version might be the same, HTC had stuck a neat little asterisk* next to the Wildfire S initially, saying that it required a new HBOOT anyway. I'd thought I was smarter than they were, but really what's different in the new download is the incorporation of just the command you're missing here. Since the ability to unlock is fairly new (through HTC officially, I mean) they're providing new HBOOTs with that command line included. I flashed the new HBOOT (even though it was exactly the same version) and lo and behold when I tried it again, it accepted the fastboot oem get_indentifier_token command.
I'd check to make sure that the HTC Legend doesn't have an asterisk as well, and maybe redownload the HBOOT anyway just in case. It can't hurt.
Aisho said:
I flashed the new HBOOT (even though it was exactly the same version)
Click to expand...
Click to collapse
I'm having the same problem on htc salsa, I have the version it says i should have, but have no get_indentifier_token, how is HBOOT updated?
My phone is S-ON and Hboot is 1.07.0000
HBOOT is updated via bootloader mode (on my phone, assumably the same for most HTC phones). You will need the correct HBOOT for your phone, and it will probably have to be contained within a full update package (for my phone, it's PG59IMG.ZIP, for the Dream it was DREAIMG.ZIP, your phone model will have its own filename). That file goes on the SD card, you boot into bootloader (usually, remove battery to ensure phone is full off, replace battery, and power up while holding the "VOLUME DOWN" button in). It then checks the file and asks you if you want to update.
However, if your phone is the same or newer version as the file you are trying to use, there's a good chance it will not work (the phone will not downgrade (usually (I think (I could be wrong) ) ) ).
You might also be amongst the lucky few who have a phone with what's called an RUU available. That's an .EXE file you run in Windows, connect your phone, and it writes what's in the file directly to the phone regardless of version.
HIH.
I have the upgraded HBOOT version as Im following a thread for how to do it, which incidentally isnt working, when I go to the bootloader menu it finds the file but does not up date it. It has been updated to the current version stated on htcdev with a FOTA update which may be why the HBOOT upgrade doesnt work.
I have the HTC salsa and it does reference RUU a few times. I dont use windows but HTC sync doesnt seem to find the phone, I have tried many things to get it working
Am I meant to run the EXE provided by htcdev and dont run HTC SYNC? Should I be in the bootloader menu/recovery first before running it?
@ericosman
did you follow every single steps ?
I just did it on my Legend (24 hours ago), in the end I followed the post of BlaY0 (http://forum.xda-developers.com/showpost.php?p=22613990&postcount=62) and it worked great.
And yes, the RUU file is the one of a few MiB that you find at the very beginning at HTCdev.
The only trick is that I had to restore my data backup but also my boot backup, otherwise I was stuck in the hboot.
I did it by flashing the recovery image, as I deleted my old update.zip of ClockWorkMod, following the steps of http://forum.xda-developers.com/showthread.php?t=1290841 (see the end of the post: 'New recovery'). Then I went to 'Advanced restore' and restored both my boot image and my data back.
Always backup your system before playing around !
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
chris... said:
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
Click to expand...
Click to collapse
Alright, let's try again.
Before the step 1 of HTCdev, it asks you to upgrade your phone to the latest RUU. You don't have to. (see BlaY0's post [1])
Just download the RUU file, thus you will be able to retrieve the very hboot's zip (just run the EXE, don't go through the installer but instead locate its temporary extraction folder with the task manager and get that rom.zip).
They only want you to install HTC Sync so that your phone is recognized by Windows and the RUU can located it.
[1] BlaY0 explains that you don't have to upgrade to the latest HTC ROM or even RUU.
got it, and dump that zip file with the correct file name onto the root of the sdcard and start the bootloader
YAY it works, time to proceed to unlock
The version I got from a different post must not have been the correct one
im sure im bumping an old thread, but im trying to unlock an old espresso, but its having the same issue as the OP, i cant find the RUU with the new hboot, it currently has the 1.02 hboot, any clues?
Have you tried following the steps I referred to ?
Look at my two posts.
In fastboot, What is displayed besides the hboot version ? Something like "unlocked" ?
If note you have to re-flash your hboot with HTC dev method, once again read the post I linked to.
Sent from my Legend using XDA
just to add that on my MyTouch 4G slide I had hboot-1.44.0007 and gave me the same error as the first post when trying to unlock through htcdev.com. I did an OTA update to HBOOT-1.45.0013 (Software version 1.63.531.2 710RD) then went back to htcdev.com and it worked without problems
Getting this while trying to re-unlock evo 3d ics. hboot 1.58.
It's an old thread but maybe it's helping someone...
If you receive the error described in the topic title/first post you need to simply register to htcdev dot com and follow each step(including the 1st step because that's actually what you need to do )
i got same problem w my Z3 plus hbot will work on my z3 plus????????
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
sunster00 said:
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
Click to expand...
Click to collapse
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
jags_the1 said:
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
Click to expand...
Click to collapse
Hi mate thanks for offering advice and help. I have not had to use your method as I decided to give the HTC bootloader unlock code one final try before proceeding to your rescue plan and all of a sudden it was successful again. I got into recovery and did a nandroid restore so am back online again, but have nevertheless made note of your method in case I become stuck again in the future. Thanks anyway for your reply! :good:
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.