I'm at a loss I've been trying for hours with not luck at restoring my phone. there is no backup. no roms will seem to boot. my SD card was wiped. i can boot into recovery and see my SD card and everything. and when trying to revert to a stock rom I use "fastboot getvar version-main' to find what version i need but it comes back blank. i have tried relocking and running a ruu with no luck
I have it unlocked
CID is stock with telus
hboot is 2.14
radio -0.18a.32.09.01_2
Cbaird said:
I'm at a loss I've been trying for hours with not luck at restoring my phone. there is no backup. no roms will seem to boot. my SD card was wiped. i can boot into recovery and see my SD card and everything. and when trying to revert to a stock rom I use "fastboot getvar version-main' to find what version i need but it comes back blank. i have tried relocking and running a ruu with no luck
I have it unlocked
CID is stock with telus
hboot is 2.14
radio -0.18a.32.09.01_2
Click to expand...
Click to collapse
I'm going to guess you're S-ON. Also, Good thing Telus doesn't make a 3.17 RUU or you'd have a shiny paperweight. You're messing with dangerous things and have no idea what you're doing.
To get a rom to boot, flash it and then extract the boot.img from the rom and
fastboot flash boot boot.img
then S-OFF once you get a rom to boot so you can RUU in the future if you need to
Still stuck in the boot loop at the white htc screen. does it matter the rom? as well when flashing the rom it comes back successful however says there is no md5 file found
Cbaird said:
Still stuck in the boot loop at the white htc screen. does it matter the rom? as well when flashing the rom it comes back successful however says there is no md5 file found
Click to expand...
Click to collapse
the rom should not matter.
Did you check the MD5 after downloading?
There is never an md5 file within the rom so it will always say that. You have to manually check the md5 with an md5 checker.
What rom are you flashing?
exad said:
I'm going to guess you're S-ON. Also, Good thing Telus doesn't make a 3.17 RUU or you'd have a shiny paperweight.
Click to expand...
Click to collapse
Brick from RUU while S-on and the Telus CID?
the nightly cm rom 10.2 from the 27th
redpoint73 said:
Brick from RUU while S-on and the Telus CID?
Click to expand...
Click to collapse
Ack true I forgot no supercid *facepalm* im rusty.
You should ba able to boot it. Did you check the md5?
checked and tried a different rom (slimbeam) and still stuck in boot loop. does it matter the order in which i flash the boot.img and the rom in?
It shouldn't matter what order you flash them in, before or after the ROM is fine. Can you elaborate on what you were doing to the phone before all this happened?
Sent from my Evita
http://forum.xda-developers.com/showthread.php?t=2450305&highlight=no+main+version
I was having this issue then I got it to boot into recovery mode so I figured i got it fixed but its stuck in a boot loop now with no rom
Ok but what caused all this to happen? Phones don't usually just get stuck in that situation on their own.
Sent from my Evita
timmaaa said:
Ok but what caused all this to happen? Phones don't usually just get stuck in that situation on their own.
Sent from my Evita
Click to expand...
Click to collapse
exactly the same way as the post says relocking the phone to go back to upgrade the hboot to flash roms that required them.
Ok, but you need to be more specific if you want help, linking to someone else's problem isn't really ideal. I'm gonna have to guess that you relocked the bootloader and ran an RUU? Which RUU exactly did you use? What's the filename?
Sent from my Evita
relocked the phone through fastboot. then tried to run this ruu RUU_Evita_UL_TELUS_WWE_1.91.661.4_Radio_0.18a.32.09.01_2_10.94.32.20L_release_266645_signed.exe to update hboot to 2.14 which is where it is now. however like the other forum my install failed and only got half the update. used the fix in the other forum to get it to at least recovery. where i discovered the my sd card had become corrupted fixed that issue and everything seem to be working in recovery when i went to flash a new rom. attempted to flash new rom and now all i get is a boot loop
Ok, the RUU only partially succeeded? You might need to try running an RUU again in that case, as that's probably what's causing your issues at the moment.
Sent from my Evita
tried running it again and get error 155 but for telus there is only 1 ruu and one ota
You'll have to research what error 155 means and try to rectify the problem.
Sent from my Evita
its says its the wrong ruu however there is only this ruu and an older ota for telus
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.
Click to expand...
Click to collapse
Cbaird said:
its says its the wrong ruu however there is only this ruu and an older ota for telus
Click to expand...
Click to collapse
you cannot run that RUU because you're hboot is from 3.17 and that's an older RUU you need to be S-OFF to run an older RUU. You can try running the OTA for 3.17
You will need to download the 3.17 telus ota zip. Extract the recovery.img, copy the 3.17 OTA zip file to the phone, flash the recovery img in fasboot, boot to recovery, it will say cant load sd card, this is normal as it's looking for an external sd card of which there is none. select install from phone storage or install from internal storage. If you pick install from sd card it will error as there is no external sd card. then select the telus ota zip file.
I dont see and recovery.img in the file. there is a boot.img though
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, I want to flash a development RUU, but everytime I try, I get Error [155]. This RUU is supposed to have 1.13.0000 bootloader version, but I don't know how to update from 1.06.0000 and if it may cause the error.
Any suggestion about it? Thanks in advance.
You're talking about ONE S, right?
Right, HTC One S
Well first of all is the chosen RUU compatible with your CID ?? If it isnt it will fail so you need to download one that is compatible, Or change your CID to match the one inside the RUU..
Secondly, If you haver done this and still get the error, Try to run the RUU from fastboot.
Oh and also, RUU requires a LOCKED / RELOCKED bootloader and sometimes stock recovery too !
azzledazzle said:
Well first of all is the chosen RUU compatible with your CID ?? If it isnt it will fail so you need to download one that is compatible, Or change your CID to match the one inside the RUU..
Secondly, If you haver done this and still get the error, Try to run the RUU from fastboot.
Oh and also, RUU requires a LOCKED / RELOCKED bootloader and sometimes stock recovery too !
Click to expand...
Click to collapse
Yes, I have the same CID that is inside the RUU.
Could you tell me how to run it from fastboot?
I'm trying almost everything I can (locked, relocked, unlocked, stock recovery...), even I'm trying now to update to the latest OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2 (now I have 1.53.401.2 from Orange Spain) as it has a firmware update (maybe hboot 1.13.0000?) what I think that can be one of the reasons why I can't flash the rom I need.
Thanks in advance!
boot into bootloader and connect USB cable, Select fastboot and then run the RUU on your PC.
Make sure bootloader is locked BEFORE running the ruu
azzledazzle said:
boot into bootloader and connect USB cable, Select fastboot and then run the RUU on your PC.
Make sure bootloader is locked BEFORE running the ruu
Click to expand...
Click to collapse
Yes, it's something I've already tried. Another problem I'm trying to solve is when installing from stock recovery, cause it says sdcart can't be mounted...
What are you trying to install from Stock Recovery ?? you cant flash an RUU and all flashable zip files MUST be signed otherwise it will fail..
I also had the cant mount sd card error in stock recovery, But when i tried CWM i didnt.. Dont know much about how stock recovery works, I just know i dont like it lol
lol, me neither!!!
I'm trying to install a stock rom, so I am supposed to do it from stock recovery, that's the matter. But I can't do it because it can't mount sdcard. I'm getting crazy, but now it is something personal, between the phone and me!!! I'll try to be patient and find the solution.
Stock ROM ?? How have you obtained this ? has someone posted it in a flashable .zip file ? If so, You need to flash it via CWM Recovery THEN flash stock recovery through fastboot.
If the Stock ROM is a Nandroid you will also need to restore this using CWM Recovery. THEN flash stock recovery after.
If the Stock ROM is dissected from an RUU you will need to flash this via bootloader, BUT unless you have a S-OFF phone (which i doubt you do cause there is no S-OFF yet) It wont work.
azzledazzle said:
Stock ROM ?? How have you obtained this ? has someone posted it in a flashable .zip file ? If so, You need to flash it via CWM Recovery THEN flash stock recovery through fastboot.
If the Stock ROM is a Nandroid you will also need to restore this using CWM Recovery. THEN flash stock recovery after.
If the Stock ROM is dissected from an RUU you will need to flash this via bootloader, BUT unless you have a S-OFF phone (which i doubt you do cause there is no S-OFF yet) It wont work.
Click to expand...
Click to collapse
Ok, it is the third option, and evidently, I'm not S-OFF. I had read a thread where they dissected this zip and I thought it was useful. Now I have found the RUU, I will try to install it. I've changed the zip and relocked it but I'm still finding Error [155]
Its useful if you are S-OFF, You just extract the ROM.zip from the RUU, Rename it to the phones model number, So in our case it would be PG40100.img ( i think) and then flash it in bootloader. However ignore this option as it wont work with a S-ON device...
If you still get the Error 155 message and you're positive you've done everything correctly, Maybe download the same / another RUU, Chances are it could have been a bad / corrupted download It happens to us all !
Ok, finally I solved it. I found original RUUs for HTC_Europe 1.53 and 1.78
Firstly, I changed my CID to HTC__001, extracted recovery.img from 1.53 RUU, flashed it, relocked the bootloader and installed the 1.53 RUU... and it worked!!! After that, nothing special to say installing 1.78 (hboot and radio updated!)
rpachecoh said:
Ok, finally I solved it. I found original RUUs for HTC_Europe 1.53 and 1.78
Firstly, I changed my CID to HTC__001, extracted recovery.img from 1.53 RUU, flashed it, relocked the bootloader and installed the 1.53 RUU... and it worked!!! After that, nothing special to say installing 1.78 (hboot and radio updated!)
Click to expand...
Click to collapse
I have done exactly (!!) the same, but you know, I have Hboot in version 2.15. And I can run none of RUUs, because I think they are not compatible with this version of Hboot (And this is that Error 155 for me). Well, so what can I do for installing the Stock RUU to my One S ?
OK, need a bit of help with a Desire S that can only get to HBOOT screen (vol down + power) otherwise it's just a white HTC screen.
Phone is S-ON. HBOOT 0.98.002.
I've tried Revolutionary.io's guide to convert to S-OFF but I just get 'Waiting for Device'. Tried uninstalling HTC drivers then installing again without luck, disabling firewall and AV, still no luck. Kinda given up on that front.
Trying 'fastboot devices', device is recognised, but if I try to flash a recovery ROM from fastboot I get an 'out of memory' error.
I don't know if USB debugging is enabled or not (how can I tell & enable from HBOOT if not)?
I thought about going via HTCDEV and their method, but my HBOOT is at the wrong version (can I upgrade it to V 2.000.2?)
I'm really running out of options now....anything else I can try??? HELPPPP!
Run htc ruu exe file and don't close the windows, find rom.zip in windows temp folder, rename it to PG88IMG.zip ale copy to sdcard. Turn on your phone in hboot mode, rom will be flashed automaticaly.
Or just go to fastboot mode in hboot and then run RUU, should work if you have bootloader locker (relocked).
amdr said:
Run htc ruu exe file and don't close the windows, find rom.zip in windows temp folder, rename it to PG88IMG.zip ale copy to sdcard. Turn on your phone in hboot mode, rom will be flashed automaticaly.
Or just go to fastboot mode in hboot and then run RUU, should work if you have bootloader locker (relocked).
Click to expand...
Click to collapse
Thanks. Noobish of me, but where do I download the relevant RUU file from? I don't know what carrier the phone is locked to by the way.
Download original ics rom here : http://dl4.htc.com/RomCode/Source_a...401.2_20.76.30.0835_3831.19.00.110_275068.zip
it has hboot 2!!!:fingers-crossed:
uberduder101 said:
Thanks. Noobish of me, but where do I download the relevant RUU file from? I don't know what carrier the phone is locked to by the way.
Click to expand...
Click to collapse
dave3002 said:
Download original ics rom here : .htc.com/RomCode/Source_and_Binaries/RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068.zip
it has hboot 2!!!:fingers-crossed:
Click to expand...
Click to collapse
I couldn't open that, but thanks.
sorry, but I'm really not getting this. I'm looking for a RUU to flash a recovery ROM. When I went to HTC dev, there were all the ROMs for all the different carriers. I don't know what mine is. I tried downloading one for Vodafone, unzipped and searched for RUU.exe but there isn't one.
I need to get to this RUU.exe but dont know how.:crying:
what is a recovery ROM? anyway, people over here at the DS forum has already extracted the radio, Hboot and ROM of official ICS. search around...
Sent from my supercharged :tank:
I had a bit of progress. I downloaded the latest 4.0 RUU util from HTC Dev, ran it, extracted the ROM.zip and renamed it to PG88IMG.zip, copied it up to the SD card, rebooted the phone into FASTBOOT and the phone recognised it and started installing.
Wahey, I thought, that's it I've cracked it, but then it gets stuck on Updating the bootloader. Stuck for nearly an hour. Tried twice and different SD cards...same thing.
Is this because I'm still S-ON and bootloader is locked, or do you think my internal memory is fried?
uberduder101 said:
I had a bit of progress. I downloaded the latest 4.0 RUU util from HTC Dev, ran it, extracted the ROM.zip and renamed it to PG88IMG.zip, copied it up to the SD card, rebooted the phone into FASTBOOT and the phone recognised it and started installing.
Wahey, I thought, that's it I've cracked it, but then it gets stuck on Updating the bootloader. Stuck for nearly an hour. Tried twice and different SD cards...same thing.
Is this because I'm still S-ON and bootloader is locked, or do you think my internal memory is fried?
Click to expand...
Click to collapse
you can't flash that when you are s-on
Sent from my supercharged :tank:
uberduder101 said:
..., or do you think my internal memory is fried?
Click to expand...
Click to collapse
You're right, that's the case. Search and you'll see similar cases.
hisname said:
you can't flash that when you are s-on
Click to expand...
Click to collapse
Absolutely irrelevant. He's not flashing anything himself, he's executing RUU which can flash everything.
OK, so how do I enable USB debugging if I can only get into HBOOT? Is there a FASTboot or ADB command that can do it? I think that's what's stopping Revolutionary.
Jack_R1 said:
Absolutely irrelevant. He's not flashing anything himself, he's executing RUU which can flash everything.
Click to expand...
Click to collapse
if you read again, he said he was flashing the rom zip after extracting the rom from the RUU
Sent from my supercharged :tank:
hisname said:
if you read again, he said he was flashing the rom zip after extracting the rom from the RUU
Sent from my supercharged :tank:
Click to expand...
Click to collapse
And the difference is?
Sent from my HTC Desire S
FYI - I tried executing the RUU itself, and that just hangs too.
I'm going down the line of toasted internal memory and am now throwing in the towel. Besides I just can't spend any more time on it.
Thanks for all your help.
amidabuddha said:
And the difference is?
Sent from my HTC Desire S
Click to expand...
Click to collapse
difference is he isn't flashing the RUU, just the ROM
Sent from my supercharged :tank:
hisname said:
difference is he isn't flashing the RUU, just the ROM
Sent from my supercharged :tank:
Click to expand...
Click to collapse
And what means to flash a RUU? Do you see any RUU running on your phone?
Trying to help people is a good thing but not before trying the stuff yourself, knowing the differences, how it works and WHY it should be done
amdr said:
Run htc ruu exe file and don't close the windows, find rom.zip in windows temp folder, rename it to PG88IMG.zip ale copy to sdcard. Turn on your phone in hboot mode, rom will be flashed automaticaly.
Or just go to fastboot mode in hboot and then run RUU, should work if you have bootloader locker (relocked).
Click to expand...
Click to collapse
Same problem with this post!
When i followed your step, this has many time to wait. I'm waiting 45 minute but this just show:
Can you help me?
Do you have recovery?Can you get in? If you can fastboot then flash recovery and try to get in.Once in try to open info or just try to wipe all (no SD card) then you will see bricked or not.
SKENER said:
Do you have recovery?Can you get in? If you can fastboot then flash recovery and try to get in.Once in try to open info or just try to wipe all (no SD card) then you will see bricked or not.
Click to expand...
Click to collapse
i don't have recovery, when i press power, my device just show HTC with white screen
When I press power + volume down, then come to recovery, it's not show
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.
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
MAsterokki said:
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
Click to expand...
Click to collapse
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
heavy_metal_man said:
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
Click to expand...
Click to collapse
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
MAsterokki said:
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
Click to expand...
Click to collapse
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
MAsterokki said:
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
Click to expand...
Click to collapse
Its cool pal it is, but then again ruus won't flash unless your bootloader is relocked
Sent from my Nexus 7 using Tapatalk