Database Info

[Q] [HTC LEGEND] (bootloader) [ERR] Command error !!!

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????????

So what do I do now?

firstly, Im not asking for a detailed explanation of what to do here.. I can read up on various sections, but I do need steps to follow. This phone is the most complicated thing to flash, give me ODIN and a galaxy S any day.
Im trying to upgrade to the latet open Europe.HTC-SAGA 401_9 not a custom rom, my DS is the same Radio Version so thats ok.
After following the various guides, What I have so far is:
1) the Stock HTC 401_9 Rom from File Factory.
2) Ive downloaded Goldcard Helper, fitted my 2GB SD and gotten the reverse ID
3) Ive d/l'd the GoldCard Image for my DS reverse ID
4) Ive d/l'd the HexD editor for making the goldcard.
5) I know about having FastBoot OFF, USB debugging ON and the phone USB set to Disk Mode for making the Goldcard and the USB to "Charge only" when flashing.
So, now what. Can I just flash the HTC Stock 401, or do I root it first. My Hboot is 2.000.002 and its S-ON.
The phone has Virgin UK Software, but its not Locked.. Ive had both O2 and Orange sim cards in and they work fine.
I just need to know the 1, 2, 3 .. steps for flashing this stock rom
Thanks in advance

Always helps to write your full bootloader screen.

ben_pyett said:
Always helps to write your full bootloader screen.
Click to expand...
Click to collapse
Im all for protecting your product against time wasting "bricked" returns, but Whoever at HTC thought of this system wants slapped... hard, Bootloader says:
### Locked ###
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822. 10. 08. 04_M
eMMC-boot
Aug 22 2011, 15:22:11
HBOOT
Then it lists on screen:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Hope that helps and hope you can give some steps. Seriously, Ive looked on here for days but there seems to be so many questions about different aspects and parts of the flashing, its confusing.
Thanks in advance

First of all, forget all about radios you know from Samsung.
At htc you can use every radio on every rom, there are only 3 possibilities you need to change radio:
It is shipped with a ruu you want to use
You face issues with radio related hardware
You want to be up to date
Ok, now to your question.
At HTC the bootloader version is important (only at stock roms).
If your bootloader has the same or a smaller version than the one from the ruu and your device had no branding, just reboot to bootloader plug it to your pc, enable fastboot usb and start the ruu.
If a branding is present and you want to stay with it, do the same with the fitting ruu.
If your version is higher or you want to remove a branding , you need a goldcard first and maybe the extracted rom.zip from the ruu, if the ruu fails with goldcard only, because you need to put it at the root of your sd renamed to PG88IMG.zip and flash it directly with your bootloader.
(also to change misc_version can be needed, but i guess not here because you don't want to downgrade)
For both cases are guides at the index (see my or bens signature).

Tectas said:
If your version is higher or you want to remove a branding , you need a goldcard first and maybe the extracted rom.zip from the ruu, if the ruu fails with goldcard only, because you need to put it at the root of your sd renamed to PG88IMG.zip and flash it directly with your bootloader.
(also to change misc_version can be needed, but i guess not here because you don't want to downgrade)
For both cases are guides at the index (see my or bens signature).
Click to expand...
Click to collapse
Ok I used this guide for the goldcard:
http://www.addictivetips.com/mobile...gold-card-for-htc-desire-without-hex-editing/
So, because Im not changing anything about the kernel, just debranding to an offical ROM, once I set up my Goldcard, I activate debugging, copy the RUU 401_9 to SD Root of my Goldcard, click "Image CRC" from bootloader menu and it should install it.
Is that correct?.

Ive just checked..
Wait and It detects the new ROM "update" automatically in bootloader menu
Yes?

NightOrchid said:
Ive just checked..
Wait and It detects the new ROM "update" automatically in bootloader menu
Yes?
Click to expand...
Click to collapse
Image crc just checks your rom, got nothing to do with updating.
The ruu itself is a exe, means a windows program , do the steps i described before with fastboot, the only difference is that you need to create the goldcard before, otherwise the bootloader won't allow (if your lucky) you to flash the ruu with the different branding.
If it fails that way run the ruu without attached device as far as you can go without closing, don't close it and search for the rom.zip at your temp folder, copy it to another folder and close the ruu, rename it, copy it to the root of your sd and reboot to bootloader and let it flash it directly, just to say it, you also need a goldcard before you do it this way.
One additional thing, be sure you got a ruu for the desire s, i just say it, because your goldcard guide is for the desire, what is no real problem there, but a wrong ruu will always fail and if it won't lead to a brick at worst case.

Sorry Tectas.. Just wont work.. I created my goldcard, extracted the RUU, changed the rom name from "disk1" to PG88IMG as you said, copied to root of goldcard, selected Fastboot then bootloader, but it just doesnt detect any image or file.
I am struggling a little with your english because you are telling me too many different ideas, Im confused... instead of telling me.. just 1, then do 2, then do.. 3, but Thank you for trying, i appreciate your help..
I will try again later..

Small thing the file you copy to the sd card must be called (case sensitive) PG88IMG.zip
Swyped form ym Dersie S unsig XAD Permuim

First method:
1. Create goldcard
2. plug in your device
3. Reboot to bootloader and enable fastboot
4. Start the ruu at your desktop and follow the instructions
5. Enjoy
If it fails make sure the drivers are installed, by downloading and installing htc sync, but uninstall it straight after you installed it, the drivers will still be present but the program itself can cause problems with ruus and/or adb.
If it still fails, try the second method.
Second method:
1. Create goldcard
2. Start the ruu without attached device
3. Go on till the only remaining possibility is to close the program, but don't close it
4. hit the windows button + r, a window should pop up
5. Type %TEMP% into the textbox of this window and hit enter, the explorer should open up and show your temporary folder
6. Search for the rom.zip (make sure hidden files are down if you can't find it)
7. Copy it to another folder i.e. the desktop
8. Close the ruu
9. Rename the rom.zip to PG88IMG.zip (case sensitive)
10. Copy it to the root of your sd
11. Reboot to bootloader
12. Choose bootloader
13. Confirm the update with vol +
14. Let it update
15. Reboot by hitting power
16. remove the PG88IMG.zip, otherwise it will update your device every time you access the bootloader
17. Enjoy

Thank you very much tectas for taking the time to sort and explain this. The 2nd methord worked just fine. However, at the end of the update flash, bootloader said:
"image on device is newer, update aborted"..
It does say that my virgin software is 2.13.351... the image is 2.10.401, so, in computer world, the numbers 2.13 is newer than 2.10. This may not be the case of the ROM itself, becasue the date is 22 Aug 11, but theyve engineered it that way probably so you cant flash it Open Europe.
The great thing is, youve taught me about the desire s and how the flash updater works, plus I have a 2GB goldcard out of it for future custom roms.. so all is not lost.. thanks for the lesson, its much appreciated.. Im gonna have a go at routing next.
It would be great to sticky this or copy it as a very Basic guide to flashing an HTC Rom.
Many Thanks again Tectas

This can also be solved, you need to change the misc_version for it as first step and afterwards do the same as this time.
About customs, you need to unlock or s-off your bootloader first.
For all three things are guides in the index thread.

I have now found that my phone is actually Locked to Virgin Mobile (has a Virgin media splash screen on boot up). Sorry for the confusion about that:
I followed the advice of Tectas and followed this:
http://forum.xda-developers.com/showthread.php?t=1399331
everything went great until I got to the end of the procedure and I only go the
"$" which after typing line 5: adb shell /data/local/tmp/misc_version -s
said "access denied" then mentioned "blue flames".
On page 6 or 7 of that thread, someone mentions this "blue flames" as being a new security mod that HTC have implemented to stop modding at all.
Is this true?.
Also, Virgin mobile and other places have quoted me £15 to unlock my DS. £15 seems alot of money, but would an unlock help (would it be worth it) for me being able to flash both Stock and custom ROMS.
I do enjoy the challenges of modding, so to me this is frustrating.
cheers

The $ indicates you have no root access, i must confess i never heard about the blue flame before, but also have to say, i never got deep into the downgrade stuff, because i used xtc clip to unlock my device, which made my device s-off and debranded.
If those Sellers use the same method, your good to go and spend the money, it saves you from a few traps you can run into with other methods (i paid €20 about a year ago), but you need to be aware that this is a hardware unlock which is irreversible, what can bring problems at warranty purpose (but must not).
Your second choice would be to use htcdev at first step and get root and so on afterwards, the downside here is also warranty, because your device is stated as unlocked at the htc database and if you leave it this way and won't use it to gain full s-off you also need to flash the kernel for each new ROM yourself with fastboot, because the recovery got no write permissions there.
If the seller would also use htcdev, safe the money, you can do it yourself, at xtc i can recommend it, but it's your choice.

Thanks for the advice Tectas. The guy in the street said it would take about 1 hour.. not sure if that helps to know. I suppose with Virgin, theyll be removing their own locks, so the virgin way might be better.
Also, the phone was bought from a 2nd hand shop, it was an unwanted upgrade someone just traded in without using it, the box it came in and the outer shell of the phone has no branding whatsoever.. thats why i was confused about it being locked.
Anyway, Ill have a think about who to go with and ill ask which methord they use before I hand it over.
Thanks again.

Tectas said:
This can also be solved, you need to change the misc_version for it as first step and afterwards do the same as this time.
About customs, you need to unlock or s-off your bootloader first.
For all three things are guides in the index thread.
Click to expand...
Click to collapse
Its Done.. phew.. hehe. After I got back to Virgin 1.31, just used the goldcard with rom.zip and it worked fine. 1 thing though, doing it this way flashes the rom in 7 stages, so what ever you do, when it reboots after the 1st install, do not think its repeating itself.. leave it. i Nearly did that, anyway, I sorted things using this thread:
http://forum.xda-developers.com/showthread.php?t=1443636
As long as you follow it to the letter, it all goes fine, the whole thread is really good support as well, so if anyones interested, read through the whole 13 pages (so far).
Also had access to the phones Recovery menu, so wiped Cach partition and did a factory reset, also probably not necessary, but backed up my SD card and formated it under the new OS.. I find this is always good on a new rom, for the file table and prevents app errors.
Happy i now know how to flash a rom, didnt quite root it yet, just flashed a stock RUU first.. which is what you should do if, like me, your new to this.
Anyway, Open Eu 2.10.401.9 is sweet and slick smooth.
Have a good one all, Thanks Tectas.

[s-off] hboot 2.15 htc one s flawless

So there are many tutorials out there for obtaining S-OFF for the HTC ONE S for all kinds of HBOOTS. But what about those of us with the newest model and HBOOT 2.15 and so on? Well it's been solved after months of trying.
1) First thing you're going to need is an appropriate RUU for your device. Mine is "RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2"
There is a thread for obtaining the proper RUU and how to distinguish which one you need. If you're here, you probably already have the appropriate RUU.
2) Second, youre going to need THE CORRECT VERSION of Moonshine. If your device is like mine, it will look like this: HTC One S T-MOB Windows 3.14.531.11 moonshine_ville_3.14.531.11.zip. If you have a different ROM version, get that one. Same goes for the carrier. Use your RUU name for a cheat sheet if you have to. Note the similarities??
3) Probably one of the most important steps is making sure that you have FASTBOOT AND ADB both installed and running AND detecting your device!!! I can not stress enough how important these are! Without them, you're gonna have a bad time. MAKE SURE USB DEBUGGING IS ON AT ALL TIMES! Snoop05 made a fantastic tool called 15 SECONDS ADB INSTALLER 1.1. Here's the link for that http://forum.xda-developers.com/showthread.php?t=2588979
Follow his instructions in the OP for a how to if you run into a problem, which you shouldn't if you can read.
Use the terminal command " adb devices " and you should get something like this
C:\Users\C***********\Desktop>adb devices
List of devices attached
HT26TW407378 device
This means your phone is being recognized as an adb device, which is fantastic! If not, try disabling and re-enabling USB DEBUGGING.
Boot into BOOTLOADER and go back to your command prompt and enter " fastboot devices ". You should get a reply that looks something like this:
C:\Users\C***********\Desktop>fastboot devices
HT26TW407378 fastboot
CONGRATULATIONS, you're almost there!
4) Once you have ADB and FASTBOOT both running properly, it is ALMOST time to run your RUU. First we have to relock our BOOTLOADER! It is very simple. Go into your Bootloader and make sure you have FASTBOOT USB on your screen. Once you see that, open a command terminal on your PC where fastboot is located, or anywhere if you used the 15 file I have above, as it makes sets fastboot machine wide! (exciting, huh?) In the command window type in " fastboot oem lock ". Now your bootloader is relocked and you are ready to run the RUU.
Run the RUU and allow it to finish. Reboot your device. HERE IS WHERE STUFF CHANGES!! Other people would have you ROOT. All you need to do is this:
-RE-ENABLE USB debugging and set your screen to NEVER TURN OFF. Trust me, you want this for now.
-Unlock your BOOTLOADER again
-DO NOT root
-DO NOT install SU or busybox
-DO NOT flash a custom recovery
-ONLY RUN MOONSHINE, follow the prompts, answer Yes twice and let it do its magic. My phone took 4 tries to get it done, but it worked!
If you followed my instruction to the T you should be moonshine S-OFF. Your device will be turned off when it finishes. Reboot your phone into Bootloader and profit, because you are S-OFF!

>My phone took 4 tries to get it done, but it worked!
What do you mean by this? You had to run the moonshine 4 times before it worked? Why would this be?

Misconception, sorry pal
808phone said:
>My phone took 4 tries to get it done, but it worked!
What do you mean by this? You had to run the moonshine 4 times before it worked? Why would this be?
Click to expand...
Click to collapse
Allow me to clarify.
When Moonshine is running it sends your phone into bootloader and restarts the phone.
After it checked to see that ADB and fastboot were working properly, it started doing that.
It went into fastboot to adb to fastboot to adb and had a running line of "moonshining<1,2,3,4>.........." after each time.
It did this four times before moonshine actually gained S-OFF.
It went something like this:
Waiting for device..........................................................................
Device found
Moonshining<1>.........................................................
Moonshining<2>..................................................
Moonshining<3>...........................................
Moonshining<4>......................................
Waiting for ADB Device
Waiting for device
Powering off device. Unplug and reboot device (or something of that nature)
Hope you enjoyed the moonshine.
Keep in mind this is off of my memory of what the terminal said. I did NOT have to restart moonshine 4 times. I ran it once, and was done.
It took about 10-15 minutes all together.

What do I need to know about RUU to use Moonshine
Thanks for this tutorial. I have had a million problems trying to get S-Off but I'm hopeful that your technique will work since it seems like we both have the One S from Tmobile.
Can you please point me to some info about RUU? I've heard of them but not sure exactly what they are. If you have a link to a good tutorial it would be much appreciated.
p.s. Here is the link to my current thread documenting my difficulties getting s-off: http://forum.xda-developers.com/showthread.php?t=2658650

fonnae said:
Thanks for this tutorial. I have had a million problems trying to get S-Off but I'm hopeful that your technique will work since it seems like we both have the One S from Tmobile.
Can you please point me to some info about RUU? I've heard of them but not sure exactly what they are. If you have a link to a good tutorial it would be much appreciated.
p.s. Here is the link to my current thread documenting my difficulties getting s-off: http://forum.xda-developers.com/showthread.php?t=2658650
Click to expand...
Click to collapse
An RUU (recovery update utility, I believe) can be used to upgrade your device OR (in our case) return your phone to stock. There is a sticky in the development area that has a page with an RUU repository. That page should tell our exactly how to match the correct RUU with your phone. I'm sorry I don't have the link handy, I'm not on my laptop right meow.
Sent from my One S using Tapatalk

Thanks. Just a couple more quick questions. After I do moonshine:
Will I be root?
Can I simply flash cwm recovery and then restore my current nandroid backup?

fonnae said:
Thanks. Just a couple more quick questions. After I do moonshine:
Will I be root?
Can I simply flash cwm recovery and then restore my current nandroid backup?
Click to expand...
Click to collapse
You should be able to! Right after I moonshined, I went right into flashing a recovery and then flashed my ROM. It was so exciting not having to boot into bootloader and the use fastboot to flash the kernel. It was instantaneous!
Flash a recovery (I've noted having trouble with old recoveries meow)
Restore your nandroid and report back here?
I'm sure there will be another user with your question. I'll add it to the OP if all goes well. And it should go perfectly. The recovery should fix root, it'll ask you before you reboot the device.
Sent from my One S using Tapatalk

Seeking assistance to return to stock ROM

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.

Stuck in boot loop when trying to return to stock.

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