Currently running stock rom version 4.0.3. Software number 1.85.502.3. I have root,supercid,unlocked and s off. Using TWRP 2.6.3.0 recovery. I tried to flash Cyanogen 10.1.3 stable but it gave an error message which contained something referring to 2.14 and I remember reading that you may need to update your hboot for newer roms. so i followed this thread http://forum.xda-developers.com/showthread.php?t=2156686 and updated my hboot to 2.14. After that I can flash Cyanogen but when I reboot the phone gets stuck in a boot loop. I've tried wiping cache, davlik, system etc and it doesn't help. Also extracted the boot.img from the rom zip and pushed it to my phone and that didn't help either. What is the problem? Is there anything else I can try?
Updating the hboot is only part of the requirement for flashing the ROM. If you read the usual instructions in the cm ROM thread it actually says you need to run the 3.18 RUU.
Sent from my Evita
timmaaa said:
Updating the hboot is only part of the requirement for flashing the ROM. If you read the usual instructions in the cm ROM thread it actually says you need to run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Thank you for the reply timmaaa, my brother had the exact same phone and he was running magio rom on it. he used xfactor root exploit and face palm s off. magio rom only requires 2.20 update and I was able to flash cm 10.1 on it and it worked fine. Whats going on there? Anyway so my only option is to run the 3.18 RUU?
I'm not sure what was going on with the other phone, but yes the requirement for either cm10.1 or cm10.2 is to run the 3.18 RUU. You're s-off so the whole process is very easy. Download the RUU, connect your phone in fastboot mode, double click the RUU program on your PC, follow the prompts and that's it. Just make sure no other programs are running and make sure screen saver / hibernation are turned off. It will return your phone to stock but your unlocked bootloader and s-off status will survive the process. You'll just need to flash TWRP recovery again afterwards.
Sent from my Evita
timmaaa said:
I'm not sure what was going on with the other phone, but yes the requirement for either cm10.1 or cm10.2 is to run the 3.18 RUU. You're s-off so the whole process is very easy. Download the RUU, connect your phone in fastboot mode, double click the RUU program on your PC, follow the prompts and that's it. Just make sure no other programs are running and make sure screen saver / hibernation are turned off. It will return your phone to stock but your unlocked bootloader and s-off status will survive the process. You'll just need to flash TWRP recovery again afterwards.
Sent from my Evita
Click to expand...
Click to collapse
just to confirm is this the file i need
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.exe
lujosh87 said:
just to confirm is this the file i need
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.exe
Click to expand...
Click to collapse
That's the one
exad said:
That's the one
Click to expand...
Click to collapse
worked like a charm. you are the man. thank you.
timmaaa said:
I'm not sure what was going on with the other phone, but yes the requirement for either cm10.1 or cm10.2 is to run the 3.18 RUU. You're s-off so the whole process is very easy. Download the RUU, connect your phone in fastboot mode, double click the RUU program on your PC, follow the prompts and that's it. Just make sure no other programs are running and make sure screen saver / hibernation are turned off. It will return your phone to stock but your unlocked bootloader and s-off status will survive the process. You'll just need to flash TWRP recovery again afterwards.
Sent from my Evita
Click to expand...
Click to collapse
Thank you too timmaaa.
No problem.
Sent from my Evita
Related
Going to RUU to 3.18 but I need to make sure of some things.
From what i've gathered since I'm S-Off I do not have to relock the bootloader. But since I'm running Vanilla Root-Box do I RUN the RUU while in fastboot or do I just run it while fully booted up or do I wipe everything in recovery then do it through fastboot?
c0d_fish said:
Going to RUU to 3.18 but I need to make sure of some things.
From what i've gathered since I'm S-Off I do not have to relock the bootloader. But since I'm running Vanilla Root-Box do I RUN the RUU while in fastboot or do I just run it while fully booted up or do I wipe everything in recovery then do it through fastboot?
Click to expand...
Click to collapse
run while in fastboot. nothing else is required.
exad said:
run while in fastboot. nothing else is required.
Click to expand...
Click to collapse
Thanks exactly what I needed to know
You will need to downgrade the TP firmware and reflash recovery afterwards.
GaBuzz said:
You will need to downgrade the TP firmware and reflash recovery afterwards.
Click to expand...
Click to collapse
Yeah I'm all set thanks, I just needed to know about the fastboot thing. Already finished doing everything.
You don't have to be in fastboot to run the RUU. As long as the screen of the phone is on, it doesn't matter what mode (bootloader, flastboot, fully booted), the RUU will run. This is by design, as the RUU is intended as a recovery tool.
Ruu never works for me unless I'm in fastboot.
I always get a random generic error.
Sent from my HTC One X using xda app-developers app
That's odd. I don't think I've ever had to go into fastboot to run the RUU.
Hi everyone,
This is my very first post and I'll admit I am a NOOB.
As I've searched XDA and Google for my questions, I am really at a loss and thought I would pose my question(s) to the community.
I have a Rogers HTC One X(Evita) running CM 10.0, I am currently S-ON, with TWERP 2.3.1
I would like to install the latest CM but it would seem my HBOOT (1.11) needs to be upgraded.
My first question is if my CID is Roger001 is this similar to being SuperCID?
If so, which firmware is recommended? Which is the latest HBOOT I should upgrade to?
I guess this brings me to my next question, what exactly do I need to be able to upgrade my HBOOT?
I've seen a few walkthroughs but none mention Roger001 as CID and I'd rather not risk bricking my phone.
If you need any other information, please let me know.
Any assistance is greatly appreciated.
You definitely need to update your phone in order to flash the latest cm ROM. But, with your phone in its current state you'll brick it. You don't have SuperCID (11111111), you'll definitely need to get that first, then get s-off, then you can RUU up to the latest. Links to everything you need are in this thread.
Sent from my Evita
Thanks Tim.
I'll give that a whirl and let you know how it turns out.
Another silly question, what exactly is RUU?
Sent from my One X using xda app-developers app
RUU stands for ROM Update Utility. It basically takes your phone back to being completely stock, including recovery. The beauty of being s-off when you run an RUU is the s-off status survives the process, and so will your unlocked bootloader. So all you need to do when it's finished is flash TWRP again via fastboot, then flash your ROM via TWRP.
Sent from my Evita
Ahh
That makes perfect sense!
If I wanted to stay stock, I could?
Sent from my One X using xda app-developers app
Yeah there's nothing stopping you. Then if you change your mind it's as simple as following the steps I mentioned before.
Sent from my Evita
I haven't had a chance to try anything as of yet but I've been doing some reading, could I use the One X Att all-in-one kit 3.0.1 to obtain SuperCID as well S-Off?
I tried another apparently popular program yesterday but it didn't work, as my CID is still Roger001.
Thanks!
Sent from my One X using xda app-developers app
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Yes!
timmaaa said:
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Spoke too soon.. :S
asarrecchia said:
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Click to expand...
Click to collapse
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
asarrecchia said:
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
Click to expand...
Click to collapse
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
timmaaa said:
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps from the link you gave me, under the RUU section, as there was a guide on how to install an RUU for Rogers HTC One X.
It said to relock the phone, so, I did.
ARWizard was part of the guide.
The weird thing is, I didn't flash CM, I flashed the Rogers RUU, so, I'm not even sure how CM10 is even on my phone.
I can get to the Bootloader but I can't launch TWERP and my windows PC now doesn't recognize my phone, it says installing drivers but never does. I had HTC Sync installed in hopes that it would help, it didn't.
Is my only option to do a Factory Reset in Hboot? I've read ill lose all my info on the SD card.
Thanks
Which RUU did you run? Something has gone wrong.
Sent from my Evita
timmaaa said:
Which RUU did you run? Something has gone wrong.
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps in the below thread to help me flash the RUU
http://forum.xda-developers.com/showthread.php?t=1658929&nocache=1
I went to this site to get the Stock image:
http://forum.xda-developers.com/showthread.php?p=37227608
It's 3.17.631.2
OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip
I really do appreciate the help, by the way.
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
timmaaa said:
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
Click to expand...
Click to collapse
I am 2.14 HBOOT and S-off.
The problem is that while my Windows PC recognizes my phone, it doesnt load the drivers and therefore, I cant send any ADB commands.
I am not even able to go into TWERP.
How will I be able to run the AT&T if I cant push any ADB commands from my PC?
You don't need any adb commands to run an RUU, but you do need the pc to recognize the phone. I'd try uninstalling all drivers, then installing them again to see if it helps.
Sent from my Evita
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files, evita ones get the name pj83img.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
If you follow the "or" method for flashing the zip it actually should work. The better correct answer is once s-off to download/install the latest ruu available that you want and ota up from there.
twistedddx said:
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
Click to expand...
Click to collapse
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
timmaaa said:
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
Click to expand...
Click to collapse
Thanks guys.
I'll try uninstalling the phone drivers and reinstall them, hopefully, it'll allow my PC to see my phone.
Worse case scenario, if my computer doesn't load the drivers for my phone, what are my options?
What if I select factory reset from HBOOT?
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Bump
Sent from my One S using XDA Premium 4 mobile app
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
bump
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.
Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.
pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!
So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks
pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755
[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.
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.
Current Situation(summary):
rooted
unlocked
S-on
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
CID-11111111
Lastest TWRP installed 2.7.1.0
After attempting and failing s-off with Facepalm and Rumrunner as well as trying to get newer roms installed over the 4.2.2 rom
I had the S-on way.... had to do a factory reset because I could only get to the bootloader.
Now I have no ROM installed and can only get to bootloader and recovery. Device does show up under adb sideload and fastboot in the respective modes. cannot mount as a filesystem in TWRP for some reason
Not sure where to proceed from here to acheive s-off and get up to 4.4 aosp roms.
Do I need to update the firmware for any reason? Is there an old exploitable rom and Kernal that I can install that has good success with s-off? I'm just lost and frustrated so I'm asking for help.
bathnapkin said:
Current Situation(summary):
rooted
unlocked
S-on
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
Unsure if superCID or not
Lastest TWRP installed 2.7.1.0
After attempting and failing s-off with Facepalm and Rumrunner as well as trying to get newer roms installed over the 4.2.2 rom
I had the S-on way.... had to do a factory reset because I could only get to the bootloader.
Now I have no ROM installed and can only get to bootloader and recovery. Device does show up under adb sideload and fastboot in the respective modes. cannot mount as a filesystem in TWRP for some reason
Not sure where to proceed from here to acheive s-off and get up to 4.4 aosp roms.
Do I need to update the firmware for any reason? Is there an old exploitable rom and Kernal that I can install that has good success with s-off? I'm just lost and frustrated so I'm asking for help.
Click to expand...
Click to collapse
I was in a similar situation a few days ago. In my case i couldn't boot into Android or recovery mode and the device was stuck in a reboot loop. I run RUU to reset everything to original factory settings. You have to relock your bootloader before you run RUU. It'll reset your root etc and you'll have to start from scratch. This link has the details:
http://forum.xda-developers.com/showthread.php?t=2593037
If you're on Mac or Linux use this one:
http://forum.xda-developers.com/showthread.php?t=1668156
Good luck.
Inn0vative1 said:
I was in a similar situation a few days ago. In my case i couldn't boot into Android or recovery mode and the device was stuck in a reboot loop. I run RUU to reset everything to original factory settings. You have to relock your bootloader before you run RUU. It'll reset your root etc and you'll have to start from scratch. This link has the details:
http://forum.xda-developers.com/showthread.php?t=2593037
If you're on Mac or Linux use this one:
http://forum.xda-developers.com/showthread.php?t=1668156
Good luck.
Click to expand...
Click to collapse
Thanks! this Is what I was hoping would help me. Unfortunately I've discovered I do have super CID "11111111"
currently trying to find a fastboot only script that can S-off me which i'm not sure even exists. Or just a way to revert the cid to whatever the AT&T one is
Inn0vative1 said:
I was in a similar situation a few days ago. In my case i couldn't boot into Android or recovery mode and the device was stuck in a reboot loop. I run RUU to reset everything to original factory settings. You have to relock your bootloader before you run RUU. It'll reset your root etc and you'll have to start from scratch. This link has the details:
http://forum.xda-developers.com/showthread.php?t=2593037
If you're on Mac or Linux use this one:
http://forum.xda-developers.com/showthread.php?t=1668156
Good luck.
Click to expand...
Click to collapse
bathnapkin said:
Thanks! this Is what I was hoping would help me. Unfortunately I've discovered I do have super CID "11111111"
currently trying to find a fastboot only script that can S-off me which i'm not sure even exists. Or just a way to revert the cid to whatever the AT&T one is
Click to expand...
Click to collapse
There's no need to run an RUU at this stage. Just downgrade to TWRP 2.6 and you'll be able to use the 'mount usb storage' feature again to copy a ROM zip across. Use the Kickdroid ROM and try Rumrunner s-off again.
The last thing you wanna do is change your CID back, then you'll be totally screwed. Just do what I said above and you should be fine.
Transmitted via Bacon
timmaaa said:
There's no need to run an RUU at this stage. Just downgrade to TWRP 2.6 and you'll be able to use the 'mount usb storage' feature again to copy a ROM zip across. Use the Kickdroid ROM and try Rumrunner s-off again.
The last thing you wanna do is change your CID back, then you'll be totally screwed. Just do what I said above and you should be fine.
Transmitted via Bacon
Click to expand...
Click to collapse
I managed to relock, run the 2.2 RUU, re-unlock and root again to get an unbricked stock phone. Facepalm didn't work so I'll give kickdroid and rumrunner a go.
EDIT: Kickdroid seems to require a firmware higher than the one I have to work which requires s-off for me to get without bricking. know of any older roms that are unsecure and rumrunner will work on?
Just got frustrated and did the RUU again. but this time I managed to get s-off! don't know what I did different this time but thanks to both of you!
bathnapkin said:
I managed to relock, run the 2.2 RUU, re-unlock and root again to get an unbricked stock phone. Facepalm didn't work so I'll give kickdroid and rumrunner a go.
EDIT: Kickdroid seems to require a firmware higher than the one I have to work which requires s-off for me to get without bricking. know of any older roms that are unsecure and rumrunner will work on?
Just got frustrated and did the RUU again. but this time I managed to get s-off! don't know what I did different this time but thanks to both of you!
Click to expand...
Click to collapse
Kickdroid only needs the newer firmware to stop signal loss problems and random reboots. You could have used it to get s-off. But you got it in the end!
Transmitted via Bacon