Related
I rooted using htc dev tool, I installed Rom manager and clockmodwork 5.0.0.2 backed my Rom from there, then tried to install elegancia but phone was stock on bootloadet! Then restarted back to my stock!
What when wrong?
P.d. I'm a noob I know
Sent from my HTC Sensation 4G using XDA
Did you update the firmware from stock?
Elegencia is an ICS ROM. Those require a firmware update.
Kancur0 said:
I rooted using htc dev tool, I installed Rom manager and clockmodwork 5.0.0.2 backed my Rom from there, then tried to install elegancia but phone was stock on bootloadet! Then restarted back to my stock!
What when wrong?
P.d. I'm a noob I know
Sent from my HTC Sensation 4G using XDA
Click to expand...
Click to collapse
You did not flash the firmware did you?
Follow this to the letter http://forum.xda-developers.com/showthread.php?t=1472298
Read it twice before you do anything.
Oh! I don't think I did!! I'm going to try that, and I let you know guys thanks!
Sent from my HTC Sensation 4G using XDA
If you're not s-off then you'll have to flash boot.img (kernel) using fastboot...
GROGG88 said:
If you're not s-off then you'll have to flash boot.img (kernel), and radio using fastboot...
Click to expand...
Click to collapse
HTC Dev does not unlock the radio partition to read write privileges. Only S-off will do that.
T-Macgnolia said:
HTC Dev does not unlock the radio partition to read write privileges. Only S-off will do that.
Click to expand...
Click to collapse
eitherway he'll have to s-off. Most of the firmware zips aren't properly signed to allow flashing on a s-on phone
S-off
So how can i get S-Off?? boot.img? where can i get that?
P.D. today i tried to install the OTA update and didnt let me
Kancur0 said:
So how can i get S-Off?? boot.img? where can i get that?
P.D. today i tried to install the OTA update and didnt let me
Click to expand...
Click to collapse
If you have Hboot 1.18.000, which if you have not updated you should have, you need to download and run Revolutionary. Go to here for a detailed guide. But relock your bootloader before you run revolutionary.
The boot.img in in the .zip file for ROM you download. You just have to extract it from the .zip and then place it in the tools folder of the SDK and use fastboot to flash it. Or you can make a flashable .zip file to flash in recovery.
You need the stock recovery image on your de ice to flash the official update file.
so i just notice that if you have the HTC sync installed in the computer, the revolutionary.exe wont run!!
S-OFF achieved!! thanks!! Now i will try to flash a ROM again!!
Thanks Guys!
careful
just be careful...need battery or else u might brick
What am I able to do with those in terms of roms and kernels?
doesn't matter for ROMs, but kernels and radios can't be flashed through recovery on that hboot.
Cid just means you're rooted. Your hboot means you can flash kernels and ROMs with an extra step. You'll have to fastboot flash the boot.img then install the .zip from twrp.
To save you from doing that, you can downgrade your hboot and then RUU downgrade to 1.85 so you can flash a radio. Go to the eMMC JET tool in the android dev forum if you want to downgrade your hboot.
Sent from my One X using xda app-developers app
Myrder said:
Cid just means you're rooted. Your hboot means you can flash kernels and ROMs with an extra step. You'll have to fastboot flash the boot.img then install the .zip from twrp.
Click to expand...
Click to collapse
I've had a good amount of luck with Aroma installers taking care of the boot.img flashing for me. Between CleanRom and BeastKernel, I only had to flash the zips from twrp.
Instead of creating a new thread, I thought I'd just bump this one.
Anyway, just bought a used AT&T HTC One XL and it has CID: 11111111 and S-ON. I need to update my HBOOT so I can run CM10. I just want to know what exact firmware/HBOOT to use so I can use the phone.
Thanks in advance!
The easiest thing to do would be to s-off. Then you can flash whatever you want.
Sent from my HTC One X using xda premium
You shouldn't need to update your hboot to run cm10 but I'd be lying if I said I hadn't encountered people with phones that wouldn't boot cm10 unless they updated to the 2.14 HBOOT.
Bear in mind on the 1.14 hboot, you need to extract the boot.img from the rom and flash it using fastboot before most roms will boot. If it still doesn't boot or you don't like the idea of flashing boot.img separately every time you flash a rom then yes I would agree to S-OFF and use the 3.18 ruu.
Sent from my One X using xda app-developers app
ratsack said:
Instead of creating a new thread, I thought I'd just bump this one.
Anyway, just bought a used AT&T HTC One XL and it has CID: 11111111 and S-ON. I need to update my HBOOT so I can run CM10. I just want to know what exact firmware/HBOOT to use so I can use the phone.
Thanks in advance!
Click to expand...
Click to collapse
Thank you for not creating a new thread. Let everyone else said, it would be wise to do s off while you are this far.
Sent from my Carbon-ize Evita using xda-developers app
I think it is my old HBoot as it's doing the same thing my wife's HTC One X did the other day when I tried to put CM10 on it. Updating HBoot fixed that.
I can't boot into Android as it isn't working. Is there a way to S-Off (that's easy) where I don't need to boot into Android? All I really want is to update HBoot and I'll be happy.
---------- Post added at 01:44 AM ---------- Previous post was at 12:48 AM ----------
Well, I think the issue was I that I wasn't using the correct recovery to flash the CM10 & GApps. Was using the recovery for a One X, not XL. Put the correct recovery on and now I'm typing this message on my phone. Yay!
Thanks for the help peoples! Now to find out how to remove the red text on start-up!
Sent from my One X using Tapatalk 2
I decided to downgrade to 1.85 for a fresh start after downgrading hboot to 1.09.000. 1.85, 1.73 RUUs failed and im trying 2.20 as we speak :// if this fails what are mmy options?
thanks
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
area51avenger said:
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
yes
twistedddx said:
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
Click to expand...
Click to collapse
I did this and I keep getting error 140- per this I am stuck in bl and I cant get adb
anyone? im in need of desperate help..
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
superchilpil said:
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Kole_Ackerson said:
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Click to expand...
Click to collapse
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
superchilpil said:
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok, I got the unlock token but its hanging on sending (0kb)
Kole_Ackerson said:
ok, I got the unlock token but its hanging on sending (0kb)
Click to expand...
Click to collapse
Make sure you're in fastboot not hboot
If that doesn't work reset your computer to make sure not programs are interfering with it
Sent from my One X using Tapatalk 2
it is in fastboot usb so ill reset my comp.
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
superchilpil said:
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Kole_Ackerson said:
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Click to expand...
Click to collapse
Nah don't worry about it!
Just helping out where I can
Sent from my One X using Tapatalk 2
Can only boot to bootloader and all RUU failed
I am in a bit of trouble at the moment. I will try to describe what I have done to end up where I am now.
I have a Telstra HTC One XL. Recently upgraded an already unlocked, rooted HOXL to JB using the OTA update (big mistake I know now). This upgraded the hboot to 2.14 and software to 3.17.8xxx.
Spent a lot of time trying to re-root. TWRP didn't work (no touch response). So I eventually found the Interim CWM Recovery (no touch) by Modaco. This seemed to work well and I managed to root the phone.
Then i followed the instructions to flash to KingBeatZ 1.2.0 ROM. Booted fine but had no touch response too.
So I wiped KingBeatZ 1.2.0 and went for the nightly CM10. Again, booted fine but no touch response.
OK, so I figured I should just go back to my restored data. Tried that but apparently no restore data (didn't realise a wipe wiped the restore data as well, what is the point of that?)
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
I do not know what I should do now to restore any functionality to my HOXL. Any help would be greatly appreciated.
o0okiato0o said:
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
Click to expand...
Click to collapse
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
redpoint73 said:
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
Click to expand...
Click to collapse
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
superchilpil said:
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
o0okiato0o said:
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
Click to expand...
Click to collapse
Take a stock ROM and pull out the boot.img
And fastboot flash boot boot.img just to make sure it flashes
Then flash the ROM in recovery
Sent from my One X using Tapatalk 2
I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.
You need to S-off first.
Sent from my HTC One X using xda premium
tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.
knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita
My HBOOT version is 1.27. For some reason I can't seem to successfully get passed installing the required stock Sense ROM that Juopunutbear requires. Is there any other possible way for to S-OFF if I am on a Kit Kat ROM? Any tools that can S-OFF?
Forgot to add that I am HTC Dev unlocked.
johnnyham89 said:
My HBOOT version is 1.27. For some reason I can't seem to successfully get passed installing the required stock Sense ROM that Juopunutbear requires. Is there any other possible way for to S-OFF if I am on a Kit Kat ROM? Any tools that can S-OFF?
Forgot to add that I am HTC Dev unlocked.
Click to expand...
Click to collapse
No you can't,with 1.27 hboot you have to be on stock rom..
From my HTC sensation-sense 5
Mile_zdr said:
No you can't,with 1.27 hboot you have to be on stock rom..
From my HTC sensation-sense 5
Click to expand...
Click to collapse
Since I am HTC Dev unlocked, is there any way to get back to stock without flashing a zip? Would I be able to flash an RUU and still maintain my unlocked status?
Sent from my One X using xda app-developers app
johnnyham89 said:
Since I am HTC Dev unlocked, is there any way to get back to stock without flashing a zip? Would I be able to flash an RUU and still maintain my unlocked status?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
No you need to relock your bootloader to flash RUU , but don't worry after you s-off you will flash 3.33 firmware and that will ulock you bootloader and after that flash recovery and do what you wanna do..
Btw why do you need to s-off?
Mile_zdr said:
No you need to relock your bootloader to flash RUU , but don't worry after you s-off you will flash 3.33 firmware and that will ulock you bootloader and after that flash recovery and do what you wanna do..
Btw why do you need to s-off?
Click to expand...
Click to collapse
I mainly just want to update to firmware 3.33 Universal (found here http://forum.xda-developers.com/showthread.php?t=1459767). Can you link me to an RUU that will allow me to S-OFF. I am also assuming that there is no other way to S-OFF besides using Juopunutbear's method?
johnnyham89 said:
I mainly just want to update to firmware 3.33 Universal (found here http://forum.xda-developers.com/showthread.php?t=1459767). Can you link me to an RUU that will allow me to S-OFF. I am also assuming that there is no other way to S-OFF besides using Juopunutbear's method?
Click to expand...
Click to collapse
You can't flash a custom firmware while s-on (it's the reason htc named this state s-on). There's simply no way unless you can pull off JTAG and sh**.
You can get 3.33.xxx.xxx via RUU (only after locking bootloader), but you can't flash 3.33 universal otherwise. If you want to switch carriers, you gotta s-off man.
you can also use the flashable stock rom to install it from recovery
link in my signature
by the way what recovery do you have and why you can't flash the stock rom?
rzr86 said:
you can also use the flashable stock rom to install it from recovery
link in my signature
by the way what recovery do you have and why you can't flash the stock rom?
Click to expand...
Click to collapse
I'm trying to flash the 3.32 ROM located in this how to thread http://forum.xda-developers.com/showthread.php?t=1614617
Every time I flash it I get the white HTC logo and then a black screen until I pull the battery. I am using 4ext recovery.
Sent from my One X using xda app-developers app
johnnyham89 said:
I'm trying to flash the 3.32 ROM located in this how to thread http://forum.xda-developers.com/showthread.php?t=1614617
Every time I flash it I get the white HTC logo and then a black screen until I pull the battery. I am using 4ext recovery.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
use the one from the link in my signature
before flashing the rom format all partitions excpet sdcard from 4ext
enable smartflash from 4ext
flash the rom