UPDATE 30/11/2013:
This thread describes my efforts in updating my unlocked One S to a hboot higher than 2.13. The phone had an H3G CID but non of the RUU's (see thread) worked. For me the solution was to Super CID and S-OFF the phone. Iḿ now on hboot 2.16.
END UPDATE
After more than two years of using Android (Legend, Desire S) phones and rooting them, I now have to register to be able to ask a question on this great forum.
Yesterday I obtained a One S. It is a UK model (not sim-locked to a carrier). I unlocked the bootloader almost immediatly with the intention of running a 4.3 or 4.4 based ROM (cyanogenmod or codename lungo). Here are some of the getvar details:
Code:
version: 0.5
version-bootloader: 2.13.0000
version-baseband: 1.11.50.05.28
version-misc: PVT SHIP S-ON
cidnum: H3G__001
boot-mode: FASTBOOT
Both cyanogen 4.4 and lungo ended in a bootloop and I figured it had to do with the hboot version. Self assured as I was I did not do a nandroid backup in twrp when flashing cyanogen and lungo and I ended up looking for a rom that would boot. I was succesful with MagioRom_ONE_S_RC6. From that I intended to use a RUU to update my hboot. I tried several (including both the H3G's) from this resource. All ended up in errors (131, 132, 155, 170 and probably some more). After reading some threads I relocked the bootloader and flashed stock recovery. All to no avail, no RUU will install. After reading a bit more I concluded that SuperCID was my best option of getting my brand new One S to a higher hboot version. I decided to go with this tutorial, but I ended up in another frustration: adb is not working for me in both windows (7) and linux (ubuntu). I reinstall the drivers (under windows) and tried some other things, but nothing works.
This is where I am now. I hope someone is willing to help. I tried to be as complete in describing the things I tried and the information I have, but I'd be happy to provide any additional info.
Getting custom roms on the legend and desire s was a lot easier.
First I do not own a UK version One S, I have the TMOUS but these are some tips that I used to help get my phone back from a non booting state.
Couple things,
Make absolutely sure this is a Ville not a VilleC2 (aka S3 One S)
Are you at all able to boot the phone to a recovery program (TWRP/CWM etc)?
Ensure that you have followed these instructions to get adb and fastboot to work. Use the Unlock section. Its best to make sure you can fastboot or at least adb before doing anything with the phone.
If you can get to fastboot (Power and Vol Down button), connect your phone and run the command "fastboot devices" post output - keep in mind command shell has to be at the adb directory most of the time C:\adb or something similar.
Make sure you have the latest driver installed and to remove (completely uninstall it) HTC Sync or Sync Manager. Not needed if you don't keep the stock ROM on your phone IMO. If you are unsure, remove all HTC software and just reinstall the driver.
Make sure you are running the right RUU for your specific device. What carrier was this phone for when it was purchased? Assuming it is H3G this is the latest RUU available for that particular OneS. You will have to run either the same version F/W or later RUU, you cannot go backwards.
Once we get the phone back to stock rom. Then start over by unlocking bootloader and getting S-OFF THEN start to flash roms.
In order to run CM11 Beta you need to have l a certain recovery installed + a few other things. I think it would be best if you can get back on CM10.1.3 Stable first then attempt to go to CM11.
TL;DR
Verify carrier and version of phone
Lock Bootloader if not already done
Download and run carrier specific RUU while in fastboot mode (power +vol down)
Unlock Bootloader
S-OFF
Flash rom
@pyrocide
Thanks for the reply. I've been working through your post. First I wanna point out that the phone is in a working state know running the MagioRom and I can boot into TWRP recovery.
Here is the output for fastboot devices:
Code:
SH24PW402945 fastboot
I'm sure it is an s4. It is says Z520e and 1.5 ghz on the box. I got the phone from ebay, so I'm not 100% which carrier it was on, but there was a T-Mobile sim still in the phone :silly:. The CID reads H3G though and the phone is not locked to a carrier/network since my giffgaff sim works fine.
I got adb to work. Thanks for that :good:.
I relocked the bootloader with fastboot oem lock (it know says 'relocked'). Running the suggested RUU ends in an error 155 during the veryfiying signature step.
And you ran the RUU while you were in fastboot usb mode?
based on Google
"ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again."
So the RUU is wrong, we need to find out specifically what version of OneS it is.
run this command while in fasboot usb mode
Code:
fastboot getvar all
post modelid: XXXXXXXXXX
The output of that:
Code:
modelid: PJ4010000
http://androidforums.appforerunner....ed-problem-restoring-ruu-error-131-151-a.html
Guy had the same problem and same modelid
Used this RUU and was able to go back to stock.
Hopefully this works.
Thanks for the help. Appreciate it.
That RUU ended in an 131 error, unfortunately.
H2Oxide said:
Thanks for the help. Appreciate it.
That RUU ended in an 131 error, unfortunately.
Click to expand...
Click to collapse
At this point i would suggest doing all Euro RUUs. That should have worked considering the modelid is the same for that guy and it worked. Sorry man but I don't know what else to suggest other than to do each RUU. If none of them work then something is definitely wrong.
pyrocide said:
At this point i would suggest doing all Euro RUUs. That should have worked considering the modelid is the same for that guy and it worked. Sorry man but I don't know what else to suggest other than to do each RUU. If none of them work then something is definitely wrong.
Click to expand...
Click to collapse
Would I need to reflash a/the stock recovery to make for a successful RUU flash?
The list of the RUU's I tried. Non worked... Really frustrating.
Code:
RUU_Ville_U_BM_1.70.666.1_R_Radio_0.16.31501S.06_3_10.20.31501S.09L_release_255222_signed.exe
RUU_Ville_U_BM_1.84.666.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265369_signed.exe
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed.exe
RUU_Ville_U_HTC_Europe_1.09.401.1_R_Radio_0.14.3059.14_2_release_243825_signed.exe
RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed.exe
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe
RUU_Ville_U_ICS_40_S_BM_2.40.666.1_Radio_1.09ts.50.02.04_10.08g.50.04L_release_280275_signed.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe
RUU_Ville_U_ICS_40_S_Vodafone_UK_2.38.161.6_Radio_1.08es.50.02.21_10.09c.50.04L_release_280400_signed.exe
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
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.exe
RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed.exe
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
RUU_Ville_U_Vodafone_UK_1.53.161.3_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251482_signed.exe
RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed.exe
H2Oxide said:
Would I need to reflash a/the stock recovery to make for a successful RUU flash?
Click to expand...
Click to collapse
No, running the RUU erases custom recovery & flashes stock recovery.
Did all of the downloads MD5 checkout correctly?
Also, just to make sure we are ruling everything out. Did you run the RUU by double clicking or right clicking and Run as Administrator? If you just did it by double clicking rerun the one I posted that fixed the other guys issue by using Run as Administrator. Again be sure to be in fastboot usb mode and that "fastboot devices" command shows your device in the output. Make sure you use a usb 2.0 port in case of compatibility issues and the cable that came with the phone if possible.
pyrocide said:
No, running the RUU erases custom recovery & flashes stock recovery.
Did all of the downloads MD5 checkout correctly?
Also, just to make sure we are ruling everything out. Did you run the RUU by double clicking or right clicking and Run as Administrator? If you just did it by double clicking rerun the one I posted that fixed the other guys issue by using Run as Administrator. Again be sure to be in fastboot usb mode and that "fastboot devices" command shows your device in the output. Make sure you use a usb 2.0 port in case of compatibility issues and the cable that came with the phone if possible.
Click to expand...
Click to collapse
I used another laptop. Running the suggested RUU again resulted in the same 131 error. I ran as admin and did an md5 check. I'd say the other RUU's will also result in an error again...
H2Oxide said:
I used another laptop. Running the suggested RUU again resulted in the same 131 error. I ran as admin and did an md5 check. I'd say the other RUU's will also result in an error again...
Click to expand...
Click to collapse
Did some digging.
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
So, if one is giving you the 155 error then try with the stock recovery and do the RUU.
The phone does say relocked in bootloader right? Try doing fastboot oem lock again and run the RUU that gave you the 155 error.
Wow, that still didn't work.
So I flashed stock recovery and relocked the bootloader. Then I tried three RUU's, both the H3G RUU's and the HTC Europe RUU mentoined before. The H3G's ended up in a 155 error, the HTC Europe in a 131.
So, still no succes. This is getting annoying, right... ? Any other suggestions besides flushing the One S down the toilet?
Regards.
H2Oxide said:
Wow, that still didn't work.
So I flashed stock recovery and relocked the bootloader. Then I tried three RUU's, both the H3G RUU's and the HTC Europe RUU mentoined before. The H3G's ended up in a 155 error, the HTC Europe in a 131.
So, still no succes. This is getting annoying, right... ? Any other suggestions besides flushing the One S down the toilet?
Regards.
Click to expand...
Click to collapse
Im at a loss man. At this point I would email HTC with the getvar all info and see what they say and which RUU they give you to try. If nothing else itll help narrow down exactly what model phone it is.
pyrocide said:
Im at a loss man. At this point I would email HTC with the getvar all info and see what they say and which RUU they give you to try. If nothing else itll help narrow down exactly what model phone it is.
Click to expand...
Click to collapse
Just a thought. Since the 155 error could point to both a wrong recovery.img or a wrong boot.img, I could try flashing another (stock) boot.img. Maybe the custom rom's boot.img is in the way. So what boot.img would I need?
So I did that. I extracted the boot.img from de H3G RUU and flashed it. I also extracted the recovery and flashed that. I then tried different scenario's with the H3G, the HTC Europe and the O2 UK RUU's. Non worked. The H3G ended up in 155, the others in 131.
Anyone else any ideas on this besides emailing HTC?
H2Oxide said:
Just a thought. Since the 155 error could point to both a wrong recovery.img or a wrong boot.img, I could try flashing another (stock) boot.img. Maybe the custom rom's boot.img is in the way. So what boot.img would I need?
Click to expand...
Click to collapse
You could try to decompile the 155 error exe and fastboot flash boot boot.img but I am very nervous that might screw something up. I still suggest contacting HTC directly to have their input on what exactly RUU is needed and if you do have the right one, why it is not working.
Code:
<T133845><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
Got the line above out the RUU log files. This is the 155 error RUU.
This raises two question:
Is it possible to get the expected hboot version number out the decompiled RUU (decompiled = the stuff placed in user/temp)?
Is it possible to down/upgrade hboot with any of the hboot versions posted here or would I run the risk of softbricking my One S then?
Don't flash any of that hboots. You will brick.
Just try to s-off, follow facepalm method in dev forum.
After that you can flash any ruu.
Sent from my HTC One S using Tapatalk
Related
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.
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
fdavidson said:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
Click to expand...
Click to collapse
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
ganeshp said:
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
Click to expand...
Click to collapse
Thanks ganeshp for the quick answer. I am pretty confident about the RUU as it is the same one I originally ran to move from custom ICS ROM to stock 2.3.4 ROM.
For Revolutionary, even in fastboot, it is stuck in "Waiting for devices..." I think it is because it issues "adb devices" command and expects some answer before carrying on to the bootloader. I would need it to skip this step. Are there any argument to revolutionary to do that?
Fred
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
fdavidson said:
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
Click to expand...
Click to collapse
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Jonny said:
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Click to expand...
Click to collapse
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly change for my device, i.e. PG5810000), would the CID affect anything?
Fred
fdavidson said:
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly chance for my device, i.e. PG5810000), would the CID affect anything?
Fred
Click to expand...
Click to collapse
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
dublinz said:
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
Click to expand...
Click to collapse
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
fdavidson said:
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
Click to expand...
Click to collapse
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
fdavidson said:
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
Click to expand...
Click to collapse
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
ganeshp said:
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
Click to expand...
Click to collapse
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
edit: i just read your first post
so you can not use revolutionary
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
ahh even that got stuck huh ...try revolutionary again ..with phone boot-looping or when stuck at splash screen ..if revolutionary finds the device all good ..otherwise all doors closed
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
he tried revolutionary already ..and he currently didnt have a booting rom ..so it might not work
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
That was my original attempt but it looks like revolutionary expects the phone to be fully booted so it can set it himself in bootloader/fastboot through adb command. Since I can get into fastboot myself, If I could skip that part from revolutionary and have it do the next steps, I think I'd get a successful S-OFF. Any idea on how to do that?
Fred
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
ganeshp said:
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
Click to expand...
Click to collapse
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
fdavidson said:
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
Click to expand...
Click to collapse
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
ganeshp said:
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
Click to expand...
Click to collapse
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
fdavidson said:
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
Click to expand...
Click to collapse
then im out of ideas
one last try
try changing cid
fastboot oem writecid HTC__001
then
fastboot reboot-bootloader
then verify it
fastboot getvar cid
EDIT: if this worked then ..immediately flash the european unbranded 3.33 rom
Hi, i had a S4 which got a broken screen and costs too much to fix a the moment so i brought a Telstra HTC ONE XL off a friend for $100.
I do like the phone but was over the 4.2.1 software as used to the 4.3 on the S4 which i rooted and put on CM10.
I tried with this phone to put on the nightly cm 10.3 but i hit a problem ,when install the nightlies it boot loops and when i try install the stable 10.1 it fails with an error which i do belive is to do with my V2 hboot.
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial
I have unlocked through htcdev and rooted it ok.
Im stuck now though as i pressed backup current original rom which turns out its not.
The phone details are
CID TELST001
Model: HTC ONE XL TELSTRA
If someone can tell where to either find the newest telstra rru for my phone or how to update my hboot so i can use cm10?
My phone is pretty useless at the moment
stueee said:
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
Click to expand...
Click to collapse
Where are you getting CM from (link it) and what is the file named? CM will typically have the phone's code name (EVITA) in the file name. If the code name ENDEAVORU is in the file name, it is in fact for the wrong device, as the ENDEAVORU is for the quad core Tegra3 (non-LTE) version, which is completely different hardware.
Also, I don't know if 10.3 is even released yet for our device, or for the ENDEAVORU for that matter. I think you might be confused about what you are flashing. So again, link what you are trying to install.
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have. Getting s-off disables the security check which would let you run any Evita RUU but you need to get a ROM to boot first before you try that. You also need SuperCID.
Your best bet is probably to flash an older Sense ROM (4.0 or 4.1), then you can at least boot, and get SuperCID and s-off so you can run the 3.18 RUU to meet the requirements for the latest cm ROMs.
Sent from my Evita
timmaaa said:
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have.
Click to expand...
Click to collapse
For some reason, I got confused and thought the OP was saying that the ROM install was failing. But it clearly says the RUU (or "rru" anyway) failed.
But yes, you can only run an RUU for your carrier version. So you will need s-off to run the AT&T RUU (the RUU referenced in the OP).
But still confused about the mention of CM10.3. From what I can see, it doesn't exist for either our EVITA, or the ENDEAVORU.
Maybe he meant cm10.2 and it was a typo?
Sent from my Evita
timmaaa said:
Maybe he meant cm10.2 and it was a typo?
Click to expand...
Click to collapse
Could be. Although if so, its a type that appears twice.
It seems fairly common for folks to try to install the wrong CM (wrong device). So I want to make sure the OP isn't doing that.
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
stueee said:
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
Click to expand...
Click to collapse
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Hi Red,
Sorry i typed out that post at almost 1am after pulling my hair out over a few hours and got a little confused.
My hboot is 2.15 and twrp is 2.6.3.0 which I believe is the latest.
What sense rom would work on mine as i really need this working now as i cant find a rom to suit anywhere with my lesser expertees.
I tried changing the cid using the super cid Telstra bat file but it won't recognize the phone as its not loaded, i tried in off state, bootloader, fastboot and twrp but is just keeps saying cant find phone.
I also tried the hex editor method but it didnt seem to update the CID after i completed it without errors.
thanks for you help.
redpoint73 said:
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Click to expand...
Click to collapse
With 2.15 hboot, you cannot modify the files required for supercid.
You can try the ever so risky jet tool. But this tool deliberately bricks to downgrade your hboot.
Sent from my HTC One XL using xda app-developers app
Any recent Sense ROM will suit your current setup, have a look here and you'll find a whole bunch. Unfortunately for you the 2.15 hboot has write protection enabled so there's no way you can get SuperCID (abd therefore can't get s-off), at least not until an exploit is released.
When you tried to flash CM did you also flash the boot.img via fastboot afterwards? You're s-on so that's necessary to get it to boot. Phones on a higher hboot like yours are unable to flash the boot.img through recovery so it must be done manually.
All you do is retrieve the boot.img from the root of the ROM zip, put it in your fastboot folder on your PC, and after you've flashed the ROM in recovery you reboot to bootloader, connect the phone to the PC, open a command prompt from within your fastboot folder (shift + right click anywhere in the folder then select open command prompt here), then give the following command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the ROM.
Sent from my Evita
stueee said:
My hboot is 2.15
Click to expand...
Click to collapse
That's pretty important. This is the reason why the older CM10.1 failed to install. CM was having issues with older hboots, so a script was added to require hboot 2.14.
Once hboot 2.15 came along, folks found that CM failed to install since the install script explicitly requires 2.14. Later versions include hboot 2.15 in the install script.
As exad and timmaaa mention, SuperCID (and therefore s-off) are not possible on hboot 2.15. So you are stuck with s-on (assuming that is what you are on now). It also means you can't currently run any RUU. Reason being, with s-on you can't run older RUUs, RUUs from another carrier, and there are no RUUs based on hboot 2.15. No "current" RUU exists (for your hboot), you can't run "previous" RUUs with the S-on restriction. So therefore you can't currently run any RUU.
But hboot 2.15 will work with newer versions of CM (and other AOSP ROMs which have been recently updated) as well as any Sense ROMs. But with s-on, you need to extract boot.img and flash manually with fastboot every time you install a ROM (as timmaaa points out). If you did not do this, this is why flashing the recent CM10.2 nightly resulted in a bootloop. Failure to falsh boot.img is the most common reason for bootloop after flashing a ROM.
stuck in bootloop
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
martin-m7 said:
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
Click to expand...
Click to collapse
You're in the wrong forum, buddy. This is the HTC One XL forum.
Hi everyone..
I am sitting on a One S which has an unlocked bootloader, is not S-off, Hboot 2.15.
Previously was rooted and had Viper Rom installed 3.1, experienced lot of random reboots, tried to go S-OFF with rumrunner and moonshine, without it working.
Tried to return to a nandroid backup (TrickDroid 9.0) but now system is not responding and results in a reboot after 1-2 minutes after rom is booted.
I would like to return to Stock Rom with a RUU, but I can't seem to find the right one and I really need some help..
Even if I found the right one I don't know how to install it because phone keeps rebooting and fastboot doesn't seem to work on Win 8.
HELP!!
Okay. I got fastboot to work on my girlfriends computer and windows 7..
I got the following from running "fastboot getvar all":
Code:
<bootloader> version: 0.5
<bootloader> version-bootloader: 2.15.0000
<bootloader> version-baseband: 1.15.50.05.29
<bootloader> version-spld: None
<bootloader> version-microp: None
<bootloader> version-main:
<bootloader> version-misc: PVT SHIP S-ON
<bootloader> serialno: H*************
<bootloader> imei: 35***********
<bootloader> product: vle
<bootloader> platform: HBOOT-8960
<bootloader> modelid: PJ4010000
<bootloader> cidnum: T-MOB101
<bootloader> battery-statis: good
<bootloader> battery-voltage: 3867mV
<bootloader> partition-layout: Generic
<bootloader> security: on
<bootloader> buildmode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> cimmitno-bootloader: dirty-64bedd38
<bootloader> hbootpreupdate: 11
<bootloader> gencheckpt: 0
Which RUU should I get my hands on?
And do I need to run any fastboot commands before I try installing the RUU?
same
i've ****d mine to lmao
I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!
Hammerbak said:
I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!
Click to expand...
Click to collapse
I have not seen a RUU that had a radio version that high. The highest version I have seen is 1.13. I think that's the problem.
Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app
Hammerbak said:
Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
Click to expand...
Click to collapse
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005
808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005
Click to expand...
Click to collapse
Well, no I'm not in the US. I live in Denmark.
The phone however was bought in Germany 2 years ago, and was delivered from T-mobile I think.
I will give this a try.
However the reason I want to get back to STOCK is due to getting S-OFF.
If I can get the phone working as it is now with TrickDroid 9.0 ROM that would also suffice. At least for quite some time.
The problem I have with the ROM is that "system" stops responding on boot.
I am thinking that this problem could be due to kernel incompatibility because the phone had the Viper One ROM before, which I think flashed another kernel together with the ROM.
Could this be the problem and could it be solved with flashing a new kernel?
However is it possible to flash a kernel without the use of the recovery?
I can't mount the internal memory and the phone has no slot for a SD card
Again.. Thanks!
I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?
808phone said:
I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?
Click to expand...
Click to collapse
Already did post in there, with no responses so far..
Well I had TrickDroid 9.0 running fine before I updated to Viper One ROM, and this was when problems started happening.
Then I went back with a NAND restore from recovery..
I don't remember flashing the boot.img, as I thought that followed along when I flashed the TrickDroid ROM, but since I think that doing a NAND recovery, doesn't bring a long the kernel I guess that if I installed the kernel from TrickDroid I could get the phone working with this.. What do you think?
Which file contains the kernel..? Is that the boot.img?
Once again, thanks for putting an interest in this post and helping me out! You're a lifesaver so far!
If you are not s-off then you need to flash the boot.IMG.
If you didn't do this, then could be the problem. AFAIK the boot.IMG contains the kernel.
http://forum.cyanogenmod.com/topic/79408-fastboot-flash-boot-bootimg/
Here's another link that might help.
http://www.guidingtech.com/12705/solve-boot-loop-htc-one-x-custom-rom/
Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck
Rapier said:
Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
Click to expand...
Click to collapse
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD
Rapier said:
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck
Click to expand...
Click to collapse
Thanks.
There's definitively a lot I will have to work with.
As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you.
I would very much like to get back to TrickDroid first of all, since it's the ROM already installed on the device I think I only have to flash the kernel and then it should be working.
If it is so I can then put Viper One ROM on the phone and flash that using the procedure that you described above.
However I am unable to find the TrickDroid 9.0 ROM since the ROM seems to have gone out of development.. Or at least that is my guess. If I'm lucky I have it somewhere on my old laptop and can get the boot.img from there. And as well I know how fastboot and ADB works, I just need the commands that I will be using.
I will try to find the TrickDroid boot.img and flash that using fastboot and then I will get back to you.
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?
Hammerbak said:
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD...
Click to expand...
Click to collapse
HERE is a list with all RUUs, taken from dev section. Find what you may need
Hammerbak said:
...As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you...
Click to expand...
Click to collapse
No, you don't have a card slot but you should be able to mount the internal memory as an sdcard
Hammerbak said:
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?
Click to expand...
Click to collapse
Yes, you could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies
Sounds good. I would try and flash that boot.img. I had a similar problem but was able to find an RUU that worked.
Maybe you just missed this part (or not)
Reboot into bootloader
Go into fastboot mode
fastboot flash boot boot.img
fastboot erase cache
Reboot
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
I should point out that I did NOT have success with ViperOneS. It looks awesome and did lots of things well except hold onto calls! Every time I would make a call, it would hang up for no reason. This problem apparently doesn't happen to everyone, but it did to me.
BTW: I have CM11 running so smoothly on my HTC One S. Pretty much all of my major issues are fixed. Only the limitations of google remain.
Rapier said:
HERE is a list with all RUUs, taken from dev section. Find what you may need
Click to expand...
Click to collapse
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
Rapier said:
You could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies
Click to expand...
Click to collapse
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer..
Another thing I could do would be to go to the HTCDev page and try to unlock the bootloader again..
Which would you recommend?
Hammerbak said:
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer
Click to expand...
Click to collapse
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed). You could even flash an AOSP KK ROM if you like, the same way
Rapier said:
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed)
Click to expand...
Click to collapse
Okay. Just to put in aspect I have the following choices:
Try to gain S-OFF as phone is now with rumrunner or moonshine
Try to get TrickDroid to work by flashing a kernel that is supported
Try to flash Viper and it's kernel from fastboot
If I try to gain S-OFF using rumrunner, do I still need to unlock the bootloader through HTCDevs?
I will try the first mentioned choice first, since gaining S-OFF would ease stuff up quite a bit.
If I can't gain S-OFF using rumrunner I will try to use moonshine.
If that doesn't work either I will be happy with just getting TrickDroid 9.0 to work as a starter.. Step by step procedure to actually gaining a working device firstly.
Then I can start thinking of how to get Viper One working after that or going back to stock to try the S-OFF methods once again.
My list of intentions is to:
Get S-OFF - whether it works or not
Getting the device to be booted and actually perform phone calls and etc.
Research the method and possibilites of getting back to stock to try S-OFF again.
Plan further upgrades to either new ROMs and/or Kernels
I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.
808phone said:
I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.
Click to expand...
Click to collapse
Okay.
Is was just about to write what you put in your edit. Haha lazy me.. xD
Well I guess as a starter I can go and unlock the bootloader, flash a recovery and try rumrunner.
When I get the recovery working I can start to plan what to do next
EDIT:
Bootloader is unlocked now and for some reason recovery wasn't removed
so I have unlocked bootloader and have a working recovery now.
Will try rumrunner S-OFF now..
.
Hi ppl!
So, I had a working HTC One S (s4) with Bootloader Unlocked, Root, Stock rom and Custom Recovery all done many years ago. I picked it up because I want to give it to someone in my family and I decided to see how it runs Lineage OS. So I found a LOS Rom, copied it and tried to install it via the latest TWRP. I wiped all, changed Data partition to F2FS and tried to install. But it said I needed Hboot 2.16 and it only has 2.15.
So then I found out to update the Hboot I need S-Off. And apparently every method needs a working Rom which I dont have right now. So I tried to find an old CM rom that runs on Hboot 2.15 but I just cannot install it. I'm just too used to how easy is to modify the Moto X so I was overconfident with the One S. And I cannot remember any of the stuff I did with it to achieve a rooted Stock Rom.
Can someone lend me a hand please?
So I have no idea what's wrong with the phone, but I tried to install CM11 and CM12 which supposedly are hboot 2.15 compatible according to their OPs and yet when restarting I just get a blackscreen after the boot image and nothing happens. What I did wrong?
With S-ON you need to flash the boot.img via fastboot after flashing a rom via TWRP or the phone won't boot.
I got S-OFF with Viper 2.x and Facepalm. Alternatively, you can try CM11 and Rumrunner. Or you get back to stock via a RUU* and root the stock rom with TWRP and SuperSU (not sure which versions are compatible with the old android 4.1). After that you should be able to use Sunshine (costs 25 bucks).
* Check your firmware version with fastboot getvar all (either "version-main" or "main version") and find a RUU with the same version.
Flippy498 said:
With S-ON you need to flash the boot.img via fastboot after flashing a rom via TWRP or the phone won't boot.
I got S-OFF with Viper 2.x and Facepalm. Alternatively, you can try CM11 and Rumrunner. Or you get back to stock via a RUU* and root the stock rom with TWRP and SuperSU (not sure which versions are compatible with the old androud 4.1). After that you should be able to use Sunshine (costs 25 bucks).
* Check your firmware version with fastboot getvar all (either "version-main" or "main version") and find a RUU with the same version.
Click to expand...
Click to collapse
Wow, many thanks! Such an easy thing I didnt see posted in all the forums I scourged. Now the phone finally boots.
Btw, I got version-main 3.16.401.10, and I found a RUU for 3.16.401.8 I guess it's ok to use?
You'll need to try. If it was a One M9 then I'd say yes it'll work. However, the One S is so much older and it's been ages since mine was S-ON so I'm not completely sure.
Edit: There won't happen anything bad if it's not the correct RUU. It'll just abort the process before it really starts flashing.
Edit2: I found the needed RUU on AFH. I've been working together with Krocko, in the past. Therefore, I know that he's a reliable source. Boot the phone to fastboot USB mode and flash the file with
Code:
fastboot flash zip PJ40IMG_Ville_U_JB_45_S_HTC_Europe_3.16.401.10_Radio_1.11.50.05.28_10.27.50.08L_release_368741_signed.zip
Check the file's MD5 checksum before you flash so that you can rest assured that it didn't get damaged during the download. The desired value is mentioned on the download page.
Edit3: You'll need to use that command twice. The first try will probably end with error 90 or something like that.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Edit3: You'll need to use that command twice. The first try will probably end with error 90 or something like that.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Darn, I can't thank you enough for all the support!
So indeed it failed, but not the Error 9X, rather "FAILED (remote: not allowed)" Google say such error results when the Bootloader is locked but mine is unlocked. And the MD5 is ok.
Code:
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILED (remote: not allowed)
My bootloader says the following info:
**TAMPERED** (TWRP 3.1)
**UNLOCKED**
VLE PVT SHIP S-ON RL
HBOOT-2.15.000
OpenDSP-v31.1.0.45.0815
eMMC-bot
Dec 14 2012,17:10:57:-1
I'm on Windows 10 and the phone is recognized no problem.
So, I'm lost...
EDIT: And CID = HTC__001
Ah, now that you mention it: On the One S the bootloader needs to be locked or relocked for flashing RUUs if the phone is S-ON. My bad. Sorry.
Code:
fastboot oem lock
In addition, flashing RUUs via fastboot (that's what the *.exe versions do, as well) can be a bit tricky and since the One S has no micro SD card slot there's no alternative method...
I don't have a link with instructions at hand that are specific for the One S but I can link you some troubleshooting tips that I posted in the One M9 forum. They're universal and should theoretically be able to help you (if one of the mentioned problems actually is your issue).
Flippy498 said:
Ah, now that you mention it: On the One S the bootloader needs to be locked or relocked for flashing RUUs if the phone is S-ON. My bad. Sorry.
Code:
fastboot oem lock
In addition, flashing RUUs via fastboot (that's what the *.exe versions do, as well) can be a bit tricky and since the One S has no micro SD card slot there's no alternative method...
I don't have a link with instructions at hand that are specific for the One S but I can link you some troubleshooting tips that I posted in the One M9 forum. They're universal and should theoretically be able to help you (if one of the mentioned problems actually is your issue).
Click to expand...
Click to collapse
Ahhh that explains. Thanks!
One question before I do that though, to unlock it again, do I need the unlock bin file from HTC again?
Sent from my XT1095 using Tapatalk
Yeah, but you'll probably need a new one. At least I had to request a new one whenever I flashed a RUU on my One S.
Sent from my HTC One M9 using XDA Labs
Perfect, I'll do that then, a thousand thanks for all your help!
Sent from my XT1095 using Tapatalk