Right, had desire s from three, alpharevx'd it installed clockwork mod, flashed eng hboot. Tried to flash RUU 1.47 europe on it, and it started to work and go through process, updated radio fine, then came up with CID error. No option to do anything but exit. Now I have a desire s that will boot into Bootloader, which has now s-on'd itself and upgraded to 0.98.0002.
Only method of comms seems to be via fastboot.
Now i cant flash the h3g one cos its too low a bootloader version, and i cant upgrade to a newer version cos one don't exist. Can anyone come up with a solution please??
Cheers.
What does HBOOT screen say (in full)?
Are you still able to get into recovery? If yes, then have you tried loading a custom ROM onto the SD card and simply flashing that using the flash zip from sd card option of CWM (clock work mod)?
Unfortunately I am unable to get into recovery, only bootloader, nothing else works. Hboot is displaying a security error at the top highlighted in pink, followed by the version number as described
You should have stuck with the alpharev hboot, which does not allow itself to be overwritten by RUU installs.
Anyway, you need to:
- install hboot 0.980000 (so you can run alpharevx again and get S-OFF)
- run alpharevx and reinstall CWM at the end
- DO NOT install the eng hboot
- flash whatever rom whichever way you want. Your hboot is safe
Follow the instructions on:
http://forum.xda-developers.com/showthread.php?t=1187231
How can I run alpharevx when I can only boot into bootloader tho?
Try running it while in bootloader. Never tryed it that way, but I'm pretty sure it only needs the USB comms to be up, same as adb. Which they should be anyway in bootloader...
Have you tried to re-setup your phone by executing one of the RUU.exe?
k, as i expected, with no access to adb in bootloader mode, i am unable to do anything. Remember, i only have bootloader to work from. I don't eve3n have a recovery partition installed, it just comes back to bootloader whatever i choose, well, bootloader and fastboot anyway.
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
If all else fails s-off with xtc clip then flash custom rom
Sent from my HTC Desire S using XDA Premium App
Have you tried to use the original RUU for your phone/network? I'm not sure if it would take care of the CID error.
Any of these:
http://forum.xda-developers.com/showthread.php?t=1002506
Clivectmob said:
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
Click to expand...
Click to collapse
I do not expect this to work, but you said you are able to get into recovery, correct?
Well, I would try to enter fastboot mode and try to flash cwm via fastboot -> fastboot flash recovery XXXXXXXX.img
Correct (windows) drivers installed?
Edit:
lowveld said:
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
Click to expand...
Click to collapse
Good suggestion! Try this one first.
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
I haven't run a RUU in years, but I think that when you run it on a windows machine, it extracts a bunch of files to a directory. Cancel the process, find the directory, find th PG88... in the directory... You get the drift.
Clivectmob said:
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
Click to expand...
Click to collapse
It is not relevant which network you are using !!! Just try newest RUU to get control over your phone again in the first place!
Even if you don't get any network access after setup newest RUU you will definitely be abte to execute alpharevx again, flash cwm and flash any stuff you want to.
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Clivectmob said:
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Click to expand...
Click to collapse
I guess that means you tried flashing recovery via fastboot?
Then concentrate on our RUU-suggestions.
Yes, as i said, flashed via fastboot, and i already explained that i cant up/down grade via ruu method because of bootloader version. I can't think of a way out of this as it stands. The only thing that may work is doing it via the p88img method with my original 3uk rom, but i cant find it in my temp files, searched everywhere for it. I've seen it's location posted on here before now, and i've searched it to death and can't seem to find it now
I'm going to extract and upload your 3GUK-PG88*.img although I think you'll need an newer one. Just a few minutes of patience.
Ok, i need help here. i'm not sure what is the problem here.
Current Bootloader System
S-Off
hBoot 2.14
Radio 3.18
Super CID - 1111111
Everytime i try to install a ROM, not all of them. i got Install Failed: Status 1. Which i didn't know why.
Previously in previous root i didnt have a problem
Couple days back i decided to tried OTA to 4.1.1 from ATT and this start happening. I relock my bootloader before the OTA and re-unlock before the update following this method. i managed to back to AOSP and some AOKP. but i always had a problem on Viper, very laggy and dialer are almost useless. I cant even flash CleanROM 6.
But, i was thinking. On my bootloader i have Unlocked flag but didnt have Tampered flag, which is i think the issue here. May i get a confirmation on that? and if that the case, may i have the guideline to re-root it this software.
THanks
Try a lower version of twrp if you are using 2.4.3.0
What tez1 said. Though the I believe "failure" is actually just a failure to wipe cache at the end of the flash procedure (at least, that's what it's been for me when I get the error). If you manually wipe cache after install, and then reboot, the flash should have succeeded.
incofstupid said:
But, i was thinking. On my bootloader i have Unlocked flag but didnt have Tampered flag, which is i think the issue here. May i get a confirmation on that?
Click to expand...
Click to collapse
That's not an issue at all. It's what happens when you install new stock system software (like the OTA or a ruu) after you're s-off. S-off stops all security checks, so you don't get that rooted flag anymore.
Problem TWRP... install 2.4.2!
thank you for all the answers i will try it.
EDIT: thanks, you can close this thread. it was the TWRP 2.4.X.X i decided to go back to 2.3.3.1.
Hi all,
I installed MaximusHD ROM and messed up my partitions so now I have only 2 GB available. I want to fix it by going back to stock ROM.
Currently my phone is superCID, s-off, hboot 2.16, radio 1.20.
From what I've read I should be able to install any RUU but I have not been able to. I tried to do it in fastboot mode and in normal mode when Android is on but without success. Setup starts but some unknown error appears, I think it is error 105... or 150.
I've followed some guides here but the setup won't work because of the unknown error Do I have to look for a specific RUU ?
The only thing that I have not done is to lock my bootloader prior to installing the RUU. However the guides state that I do not have to lock it if my phone is S-OFF.
If I do fastboot getvar all next to "version main" I see nothing, it is empty.
Please help!
I changed my CID to HTC__001 but this did not help Please help me to get back to stock !
mkoev said:
I changed my CID to HTC__001 but this did not help Please help me to get back to stock !
Click to expand...
Click to collapse
I had similar issue what I ended up doing was pulling the recovery image out of the install package and flashing it via fastboot and it restored my sd storage I had to use the modified recovery supplied I would try that- I believe you could change your cid to whatever RUU your trying to flash and it should work also,its seems some have downgraded to hboot 2.1.5 to flash RUU (read,read,read)best of luck
Somehow I fixed my problem yesterday. I was not able to install RUU however I was able to change my hboot back to 1.04 ... afterwards I installed the latest version of TWRP and suddenly I was able to see stuff on my internal memory. Prior to that TWRP 2.3.x.x was not able to detect my whole internal memory. Anyway... my advice to people is not to install MaximusHD via CWM although it says that it works. It does work, but it is easier with TWRP
Hi everyone
You must be pretty bored of threads like these!
Basically I can't s-off, so I was hoping for some advice. Here is my fastboot info:
TAMPERED, UNLOCKED
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.23.40e.00.26
OpenDSP-v19.2.0268.0927
OS-
eMMC-boot 1024MB
I'm running TWRP 2.7.1.1 through which I installed JmzM4StockRootedOdex-WWE-1.22.401.1.zip and JmzM4_Kernel-09-4-13.zip. SuperSU is configured.
I have tried rumrunner, revone and firewater.
Rumrunner: Fails during Test 2. Tried two different PCs running Windows 7 and Ubuntu respectively. Last three entries are:
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at rumrunner.us
Revone: ./revone -P gives error message 2 as it should, then after reboot I get error 1 with ./revone -s 0 -u
Firewater: Error: "Kernel contains anti-firewater patch".
So, does anyone have any ideas as to what I can try next? I have seen a couple of other people on the forum who can't s-off under similar circumstances. I don't usually have problems with this sort of thing, but this one has me stumped.
Any help would be appreciated. Thank you.
Any news? I'm in the same boat.
European unlocked regular HTC One Mini.
Have been running 4.3 and I think 4.4.2 ok for a while (don't even know).
I'm 'tampered', 'unlocked' but 's-on'. Hboot 2.21.
Can't supercid, can't flash firmware.
I can flash the twrp 2.7.1.1 though.
I'm now running the JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip rom, with regular SuperSU flashed after it was installed.
Fast boot is off, usb-debugging is on.
Rumrunner gives 'fatal, download updated package at www.rumrunner.us'
Revone gives the 'error -2' when doing ./revone -P.
But after rebooting, 'revone -s 0 -u' just gives 'error -1' and fails, without an error message.
dipje said:
Any news? I'm in the same boat.
European unlocked regular HTC One Mini.
Click to expand...
Click to collapse
Interesting. Glad to hear I'm not alone! What is your CID, out of interest?
moomoomoo2 said:
Interesting. Glad to hear I'm not alone! What is your CID, out of interest?
Click to expand...
Click to collapse
INFOversion-bootloader: 2.21.0000
INFOversion-main: 2.12.401.1
INFOversion-misc: PVT SHIP S-ONINFOplatform: HBOOT-8930
INFOmodelid: PO5820000
INFOcidnum: HTC__E11
revone just keeps giving errors -1/-2.
firewater finally bails out saying I'm running a kernel that has the anti-firewater patch. But I'm running custom kernels that are in the howto's. I flashed boot.img manually through fastboot and made sure by 'uname -a' that I'm indeed running the intended kernel. Tried 'JmzM4_Kernel-09-4-13.zip' and the 'bubba kernel' from 01-nov-2013.
And as I said, rumrunner seems to run OK. (during 'hold please' where you see the **** that become --- slowly, the bar fills up. After that it says it's rebooting into bootloader again, and after that it bails by saying 'FATAL: Download updated package at www.rumrunner.us'.
Different firmware packages I tried to flash all bail with some 'android_info' error, even after making sure the CID and model-ID match. But the way I see it I need to be s-off before those packages work anyway.
Sounds like we've both tried the exact same things. Hopefully someone will be able to help.
I take it you are going through this pain to get sense 6?
Have you guys tried going to SuperSU and change the Default access to grant? And then run rumrunner?
Everest_ said:
Have you guys tried going to SuperSU and change the Default access to grant? And then run rumrunner?
Click to expand...
Click to collapse
Yup, that's how I have my SuperSU. Thank you for your reply.
I will check and try again, but I can't imagine it having an impact, since I'm running firewater and revone from a root-prompt already, and rumrunner runs happily but bails _in_ one of the later fastboot things.
I tried relocking and unlocking through the HTC dev thing again, just in case. Of course (I forgot) that has the effect of my entire /data (including 'sdcard') being wiped, so I now have to push a rom through ADB into recovery to flash and get the device running again.
From that I can turn usb-debugging on again, flash supersu and try setting it to always-grant and try again.
@moomoomoo2: Did you have your device sent to HTC for repairs by any chance?
dipje said:
@moomoomoo2: Did you have your device sent to HTC for repairs by any chance?
Click to expand...
Click to collapse
Not me personally, but I bought the phone second-hand in October 2013 so theoretically it could have been sent to HTC before then.
Hey guys. I am in the same situation. I have htc one mini Europe version with:
Android 4.4.2
Sense 5.5 stock
Hboot 2.21
Unlocked
Rooted
S-On and CID HTC_035
And I can't get S-Off. I tried rumrunner, firewaters, revoke. Same errors like you.
I really want the sense 6 ))
Sent from my HTC One mini using XDA Free mobile app
Seems there's a pattern emerging! For the record, my CID is ORANG001.
Can you guys (or girls) report if your device was ever sent to HTC or not? Just a sneaky suspicion. Mine is, the original posters 'could be'.. until we get a definitive 'no' I'm having a feeling that they did something at the HTC repair .
Right this moment I managed to get my device pretty much back to stock 4.4.2 / sense 5.5 (in detail, firmware 3.10.401.4). I'm 'relocked' (so still tampered) and on the firmware package (hboot, kernel, radio, recovery) that came in the european OTA update.
The thing is, that OTA update was ment to bring me to 3.10.401.6 (the last number is different). My software version now says .4.
If I do the 'search for software updates' it says there is nothing available?! It should report an upgrade to .6 or to the new Sense6 rom I guess. It's the regular european / international version.... my CID and model ID is in the sense6-OTA update's firmware... so I should be able to flash it...
Maybe I'll try that. Flash the untouched firmware that is in the sense6-OTA (it's an OTA file for my model anyway, no idea why it's not showing in the software-updates scan),
The same situation, device was sent to HTC repair.
Well, I'm no closer to the s-off business...
I locked my htcdev bootloader, flashed the firmware from the OTA Europe-3.10.401.6 (4.4.2, Sense 5.5). Then unlocked the bootloader again (Wiping /data, grr) and installed TWRP 2.7.1.1 again.
Then I managed to install Europe-2.12.401.1 from a odex'ed full rom dump here on XDA. Simple flash from TWRP.
Once it is loaded it detects an OTA update to Europe-3.10.401.6 (I already had the OTA files, exactly the same as posted on XDA here).
I kinda modified the update-script for it. Removing the cid checks from the start, and removing the md5-check and patch for '/system/bin/app_process', and then making sure the mount() and unmount() calls matched (no double mounts, etc...) the update-script ran fine from TWRP! I removed the firmware business from the update-script (was already running it) and added an 'app_process' to the system folder so it would be copied. I also removed the 'fota' business at the end of the script.
And it ran! So ignoring the single app_process file (which I took from a 3.10.401.4 dump here on XDA) I was running a pretty good stock 4.4.2-Sense5.5 rom, with official matching firmware. Once the rom loaded up, it detected the OTA update to Europe-4.09.401.3 (4.4.2-Sense6).
I first booted back to fastboot mode, and flashed the official recovery that was in the 3.10 OTA (so I got the proper stock recovery) but left the device unlocker. Booted the ROM back up, started the OTA download and just clicked 'install now' at the end.
It took some time, but the OTA update ran without any modification perfectly it seems. It even flashed the new firmware (I got a slightly new boot logo and I'm on hboot 2.22 all of a sudden) without me needed to relock and unlock the device, and the new 4.09 rom seems to run just fine. It boots, runs fast, camera works, I got signal and wifi works.. I think it's ok. It's late, the rest I gotta check out tomorrow.
Mental note for me: Now make backups of your system dump since it's nice clean and stock, and don't forget to make a backup of the /data/preload folder in case you wipe your /data again. I can still flash TWRP, so getting root should be easy.
I now wonder if just using the supplied firmware package in the Sense6-thread, and modifying it to match my CID and MID would've worked anyway. I tried it, didn't work.. but I didn't know you had to relock the bootloader before flashing firmware as s-on. Anyway, I got my device up to the latest official firmware as stock as it's going to be (hboot, recovery, kernel, system, preload, all stock at the moment. Only htcdev-unlocked and it shows 'tampered'. Feels as a nice base to root and just use it for now .
All this still doesn't answer why our devices will not get s-off working at all.. but the reason I wanted s-off is done now for me, so I'm afraid I don't care anymore
Hi dipje,
I am exactly in the same situation like you was.
But my htc was never send to service.
If your kind please could you write down the process you did step by step and attach some links where needed with the location of the firmware, roms etc that you used and the files that you modified to not check the cid and other.
I will be very thankful.
Thank you very much.
Ovidiu
Sent from my HTC One mini using XDA Free mobile app
Excellent work dipje. Some more info would be great, including the modified script if you still have it. Regarding Europe-2.12.401.1 - was this vrvr's straight dump, or tr1gg3r84's international odex?
This worked for me because I apparently had the right device (right CID). Since we can't change CID without s-off, I was lucky. Also, I was on the 4.4.2 3.10 firmware I believe from an official OTA, but to be honest, I have no clue. Since I'm s-on I could only have installed official firmware files from OTA packages, so I guess I was on hboot 2.21 from the start. Just FYI.
If your CID is not in the list of supposed devices for these OTA updates, you're **** out of luck. At least, as far as I know, I'm not all knowing and only got into flashing my mini not too long ago. My CID is HTC__E11 and that _is_ in the list of supported CIDs for these OTA packages (and the 2.12 international rom we start with). That might be something to check first if you start down this path.
Do yourself a favour, try installing the firmware from OTA 3.10 (it's in the instructions below, you need to relock your device first, try to flash it by reading the fastboot commands, then you can htcdev-unlock again).. If that 'takes' and works OK, you're in the right CID list .
REMEMBER, ALL OF YOUR /DATA (including internal storage) WILL BE GONE!!
(because htcdev-unlocking does that, and to install an official firmware package we have to relock and then unlock again afterwards... If I'm wrong about this, please let me know ).
Anyway, yes I've used "Stock2.12.401.1Odex(tr1gg3r84).zip" as a starting point (http://forum.xda-developers.com/showthread.php?t=2575766).
Then get the 3.10 OTA from http://forum.xda-developers.com/showthread.php?t=2722370. Or, once you have 2.12 booted up let it download the OTA package, but _do not_ execute it. Once downloaded it should be in 'Download' in your internal storage/sdcard. Transfer it to your PC.
Install TWRP 2.7.1.1, then use it to flash tr1gg3r84's 2.12 as is. Start it up, do as minimal setup as you can, make sure you disable fast-boot in the power options (to be sure) and I always enable USB debugging first. (google how to do it if you don't know, it's a sort-of hidden option these days).
Then, relock your bootloader. Go to the bootloader menu and choose fastboot if you have to (hold vol-down while restarting / booting up).
From your PC, use the command line 'fastboot oem lock'. In the command line it will do some stuff (and read error at the end, don't worry) and your device should reboot automatically. After it is booted up, go to the bootloader / fastboot _again_, and this time give the command 'fastboot oem rebootRUU'. Your device should restart quickly to a black screen with a small white HTC logo. Give the command 'fastboot flash zip firmware.zip'. That firmware.zip file is the file that is _inside_ the 3.10 OTA, so you need to extract that first.
If correct, it will start doing stuff and a green bar will slowly fill up. It will _NOT_ reach the end. In your command-line window it should say it completed OK.
Ok, so now we have a 2.12 rom installed with the 3.10 firmware installed. Unlock your device again through htcdev.com, and install TWRP again.
If all is OK, you should be able to flash my modified 3.10 patch (http://clients.maxx-traxx.eu:8080/tmp/xda/mine3.10.zip)
I hope the bandwidth will be OK for that server, if it will be too much I have to upload it somewhere else.
That's what I used in the end, and should be able to install it without problems.
How I created it: The only file from trigger84's 2.12 rom that fails to MD5 check is the modified '/system/bin/app_process'. So I took the file from another 3.10 full dump (the 3.10.401.4 one from trigger too) and placed it inside the /system folder of the extracted OTA update. It will be copied automatically. I removed the lines from the updater-script that try to verify and patch /system/bin/app_process, but left the 'setting permisions' alone. Then I removed all the CID-checking from the start of the script (TWRP can't do that apparently) and removed all the 'fota' stuff from the end ( no clue what it is). Also, remove the lines that try to transfer the firmware.zip package. And as I said, fixed some unmatched mounts/unmounts. With that I mean everytime /system is mounted, it should be unmounted first before trying to be mounted again. The script tries to mount /data multiple times and only unmounts it once or something, and that tends to fail on TWRP.
I've attached my updater-script if you want to check it out and try to do it yourself. Compare the differences between mine and the original in the OTA to see what I mean.
You can delete the fota*** files and the firmware.zip from the OTA package, rezip it (properly, take care of the folder structure, ahem ) and try to flash it.
In the end, it should update OK, and since you already were on the firmware from 3.10, it should boot up OK like normal, _IF_ we flash the correct kernel. So before booting up 3.10 (it will bootloop if you try, no big problem) go to bootloader-fastboot mode again, and give the command 'fastboot flash boot boot.img'. The boot.img is the file that is inside the 3.10 Firmware.zip. The 3.10 should now boot up OK.
So, now you're on 3.10 ROM with 3.10 firmware (notice, 3.10.401.6, not the .4 version). Now, we're gonna install the stock 3.10 recovery again.
Take the 3.10 OTA extracted firmware.zip, and take the recovery.img out of it. Go to bootloader-mode again, and use 'fastboot flash recovery recovery.img' to install it. You now have your stock 3.10 recovery installed, but are still htcdev-unlocked. Start the ROM again.
A software update should be available to 4.09.401.3. Let it download, and let it execute. It should work without any problems, and your phone should reboot a couple of times.
At the end, after Sense6 is up and running, you can go into bootloader-mode again, and flash TWRP again, and use TWRP to flash the SuperSU update package to get root. (Because we're still unlocked, we don't have to do the htcdev-unlock thing this time).
Remember, your /system/bin/app_process file is not stock for sure, and there might be other files. The 4.09 OTA update (Sense6) just doesn't touch those files so it runs without modification, but with a next OTA we might not be so lucky and might have to modify the OTA package again. Do yourself a favour and make a backup of your current /system layout (I guess TWRP can do it), and yourself another favour by also making a backup of the /data/preload folder as it is now. Those files can be hard to come by later on, and if you ever do the htcdev-unlock thing again, they are gone (/data is wiped). Use a root-file-explorer app or something to copy the /data/preload folder to your sdcard/internal storage. Then copy it your PC and zip it up, label it preload-eu-4.09.401.3.zip and keep it safe .
This is not the most noob-friendly guide, but then it isn't intended to be. People who've been fighting to get s-off should know most key-shortcuts, fastboot and adb commands by now
Great guide dipje. Will hopefully help those who have the more generic CIDs. Counts me out unfortunately, but hopefully someone will figure out how to s-off the damn thing!
Hi everybody,
Just for information, i am french (sorry for my poor English ) and i am in the same situation :
One mini rooted, TWRP 2.7.1.1, S-ON, hboot 2.21.0000, revone : fail, rumrunner : fail, firewater : fail...
And my HTC also was sent for repairs (cracked shell, speaker HS, software update).
i am desperate...
I'm getting the feeling that (EU?) hboot 2.21 is simply protected against s-off tricks.
Is downgrading hboot possible with s-on? Guess not.