Related
Phone was fine running InsertCoin 2.2.0 and I wanted to try another ROM so I did the usual wipes and flashed it and on reboot, it just sits at the HTC screen till I yank the battery. It does this with every single ROM I try to flash now. It won't boot anything except my Nandroid back up. I haven't changed anything recently besides the SD card. CWM Recovery is 5.0.2.0. Bootloader is S-Off, rooted... Any ideas? Thanks in advance.
Flashing official RUU often solves such problems
Power+Vol Down to inter bootloader, then power again>> fastboot , plug usb cable ,then run the RUU.exe
U sure ur not trynna flash updates instead of whole roms? Just a guess here
I seen some roms where u have to flash, say, 4.2 first, before flashing 4.3 and then 4.4 on top.
Sent by my feau gee
gf7800 , I flashed the official RUU to return to stock and it still won't boot anything. I tried on about 4 different ROMs and all got the same result.
scream_clarity said:
gf7800 , I flashed the official RUU to return to stock and it still won't boot anything. I tried on about 4 different ROMs and all got the same result.
Click to expand...
Click to collapse
Sorry , but this is strange ! Hopefuly someone give us an idea .
Sent from my HTC Sensation Z710e using Tapatalk
B
R
I
C
K
E
D
I am assuming of course you didn't check the MD5 hash that came with the rom to ensure you didnt flash a corrupt file?
you flashed the RUU with the new sd card? Did you s-off and root since doing so? Does it boot after flashing the RUU? What RUU are you flashing?
edit nvmnd, I re read the thread.
which rom did you tried to flash to ?
I tried ARHD, InsertCoin, Senseless Extreme and another one. I managed to get the latest InsertCoin to work. It's weird. It's like every one out of five times I try to flash something, it works.
flash the correct ruu for your phone
Sent from my HTC Sensation Z710e using xda premium
Flashed the correct RUU. I'm assuming so anyway. It's a Bell Sensation and I flashed the RUU that had BM (short for Bell Mobility?) in the file name.
Sent from my HTC Sensation Z710e using xda premium
CAN ANY BODY HELP??? I tried flashing the beta Jellybean Custom Rom. I installed the G Apps first by accident in trwp When i tried installing the actual rom. It failed
# I tried again.
Factory rested it first. So it erased my back ups
It failed again
#Now my phone was bricked
read some forums. tried unbricking it my self by using the ARU wizard and RRU.
All it did was secruity lock it.:crying::crying::crying:
# Now My One X is stuck on Hboot. But i can still get into twrp.
Ive been a fan android forever but new to rooting,.
Can anybody hellp me Please??
Andriod_Kuki_ said:
CAN ANY BODY HELP??? I tried flashing the beta Jellybean Custom Rom. I installed the G Apps first by accident in trwp When i tried installing the actual rom. It failed
# I tried again.
Factory rested it first. So it erased my back ups
It failed again
#Now my phone was bricked
read some forums. tried unbricking it my self by using the ARU wizard and RRU.
All it did was secruity lock it.:crying::crying::crying:
# Now My One X is stuck on Hboot. But i can still get into twrp.
Ive been a fan android forever but new to rooting,.
Can anybody hellp me Please??
Click to expand...
Click to collapse
if u can get into twrp...
mount sd copy a rom
wipe everyrhing except sdcard
and flash the rom... u should be good
Sent from my HTC One X using xda app-developers app
i tried doing that but my phone wont show up on my computer. ILL Try again. But what rom would u recommend.
Also is there another way i can fix it??
Thank you for helpping
Andriod_Kuki_ said:
i tried doing that but my phone wont show up on my computer. ILL Try again. But what rom would u recommend.
Also is there another way i can fix it??
Thank you for helpping
Click to expand...
Click to collapse
one promising fix would be relock your bootloader ...run a ruu....unlock ...twrp...
niceppl said:
one promising fix would be relock your bootloader ...run a ruu....unlock ...twrp...
Click to expand...
Click to collapse
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?
Andriod_Kuki_ said:
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?
Click to expand...
Click to collapse
?
what do u mean?
niceppl said:
?
what do u mean?
Click to expand...
Click to collapse
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/
Andriod_Kuki_ said:
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/
Click to expand...
Click to collapse
Yes, you most likely need to run the 1.85 ruu.
Sent from my One X using xda app-developers app
Andriod_Kuki_ said:
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/
Click to expand...
Click to collapse
yes..relock your bootloader..
also are you att hox? or rogers hox
did you get supercid?
how you running the ruu?
if you running the .exe...did you install htc sync?(need to install this and have it running before running ruu)
Ok thanks ill try it thank u
Sent from my HTC VLE_U using xda app-developers app
Andriod_Kuki_ said:
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?
Click to expand...
Click to collapse
rpomponio said:
Yes, you most likely need to run the 1.85 ruu.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
suggestion to re lock his hox was mentioned but his reply didn't say if he locked it, just said he tried to run the ruu. Bet it still needs locking! Also OP do you have super cid? If so he doesnt need 1.85 right? He can use the 1.73. I would still probably use the 1.85 like rpopo recommended though. Also if you have done everything correct (re locked and 1.85 if not super cid) the USB drivers can make a difference. I was super cid and locked and ruu kept failing. uninstalled my HTC drivers and ran the HTC sync program and used those drivers...Worked first time after that! Just have to remember to not actually have HTC sync running!
Wats a super cid..? Srry I'm new to rooting
Sent from my HTC VLE_U using xda app-developers app
Try the 1.85 ruu. Relocking and running the 1.85ruu usually gets you back up and running.
Sent from my HTC One X using xda app-developers app
You have to be able to use adb on your computer to relock. There is a sticky with the info on how to install drivers, use adb and relock your phone.
Sent from my HTC One X using xda app-developers app
I have used adb to relock it
Sent from my HTC VLE_U using xda app-developers app
Then run 1.85 ruu, make sure you have the USB drivers for the phone installed and then once you do that, re-root and unlock the bootloader.
It works ran the 1.85 ruu. Ten minutes later running perfectly/ :laugh::good::good::good:
Thanks :laugh::laugh::good::good::good:
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that will force your phone to boot.
Stay unlocked push recovery in fastboot again
fastboot oem rebootRUU
Start the RUU. Finish the install, then back into hboot, select recovery
Invest in a copy of titanium backup and use between rom flashing hence there isn't a micro sd card slot in the HOX
Sent from my HTC One X using xda premium
lmnope1 said:
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that will force your phone to boot.
Click to expand...
Click to collapse
8125Omnimax said:
Stay unlocked push recovery in fastboot again
fastboot oem rebootRUU
Start the RUU. Finish the install, then back into hboot, select recovery
Invest in a copy of titanium backup and use between rom flashing hence there isn't a micro sd card slot in the HOX
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
fyi, This is an old thread. It looks like he got what he needed the 2nd day of august.
Hello, I just tried to install the new JB insertcoin version on my HTC One X. Something went wrong and now I am completely stuck. After having searched the internet for a few hours to avoid asking the same question two times, I decided to finally ask for help here as my case seems to be unique.
I'm currently only have access to hboot and fastboot, when I try rebooting the phone I end up in an endless bootloop just as I reach the home screen.
- I can't flash any .img files whatsoever,
- I can't access "recovery" and I promptly receive a text "security warning" just under "RELOCKED".
- when I try entering hboot mode it says "Failed to open USB Master Mode".
- I have tried flashing RUU but it says I have <30% battery, which is not true as it's nearly full.
I have no idea what I should do from here, is my phone dead or is there still hope? Thanks in advance, I really appreciate any input I can get.
Update. I realize I need to download "recovery.img" and proceed with installing a stock rom. However, when I try flashing the recovery.img it says "FAILED" in cmd.
Update2. Dowloaded the stock rom but received error 140 midway through the installation. Probably has something to do with the "FAILED" I get when using the command "fastboot flash recovery recovery.img". Any help is appreciated, my batteries are probably at 50% now....
You say it says "relocked" in hboot? That means your bootloader isn't unlocked. You're gonna have to do that before you can do anything else.
Edit: also, are you sure insertcoin is for our one X and not the international (tegra 3) version? I quick skimmed through both our development sections and didn't see it.
Sent from my One X using xda premium
stnguyen09 said:
You say it says "relocked" in hboot? That means your bootloader isn't unlocked. You're gonna have to do that before you can do anything else.
Edit: also, are you sure insertcoin is for our one X and not the international (tegra 3) version? I quick skimmed through both our development sections and didn't see it.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I have the EU version, my thread was moved here dunno why. Anyway, I unlocked bootloader and it now works to use the command "fastboot flash recovery recovery.img" and when I run the corresponding RUU I receive error 155 instead of error 140. I am now stuck in an endless bootloop where the phone restarts as soon as the home screen is reached.
Edit: Is there any way I can revert the 1.28 firmware for JB? It says HBOOT-1.28.0000 in the bootloader and maybe this is what's causing problem.
I remember one having to put the new hboot on there before they flashed it. Correct if I'm wrong
Update: I installed an older (ICS) version of insert coin and it worked. I won't touch jelly bean for a while....
This thread should probably get moved to the HTC One X forum though. I would give advice but don't know anything about the HTC Endeavor.
For them to run a jelly bean sense ROM they need to flash a updated hboot.
Hopefully that won't happen to us....
Sent from my Nexus 7 using Tapatalk 2
so you might as well run the ruu then to get jb for the endeavor then flash custom roms? can u still run ics roms afterwards? hopefully they dont have to flash boot.img in fastboot.
DvineLord said:
so you might as well run the ruu then to get jb for the endeavor then flash custom roms? can u still run ics roms afterwards? hopefully they dont have to flash boot.img in fastboot.
Click to expand...
Click to collapse
They have to fastboot flash kernels regardless since their kernel partition isn't writeable in recovery
And I believe they can only run jb roms from that point on
Sent from my HTC One XL 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 bought the phone when it first came out. Play around with unlock bootloader, root and custom roms. I Currently have an older version of CM running on the phone with custom recovery.
I haven't touch the phone for months, and certainly I havent follow the forum for a long time. Recently I wanted to start use this phone again. I would like some help to get this phone up-to-date again.
1. Is there a way to turn this phone to the latest stock configuration? I will follow the forum to unlock, s-off, root again. But I wanted to turn it back to stock completely with latest firmware and all.
2. what are the latest version of radio, kernel, stock rom version and so on? how can I get them?
3. Any instruction would help.
My questions may sound very noob, but I hope someone can point me to the right way.
jzhang0818 said:
I bought the phone when it first came out. Play around with unlock bootloader, root and custom roms. I Currently have an older version of CM running on the phone with custom recovery.
I haven't touch the phone for months, and certainly I havent follow the forum for a long time. Recently I wanted to start use this phone again. I would like some help to get this phone up-to-date again.
1. Is there a way to turn this phone to the latest stock configuration? I will follow the forum to unlock, s-off, root again. But I wanted to turn it back to stock completely with latest firmware and all.
2. what are the latest version of radio, kernel, stock rom version and so on? how can I get them?
3. Any instruction would help.
My questions may sound very noob, but I hope someone can point me to the right way.
Click to expand...
Click to collapse
flash a sense rom.
S-off
Ruu to latest.. with s-off bootloader can remain unlocked.
Flash a recovery ( nothing higher than twrp 2.3.3.1 cause of wiping issues)
Then flash a rom.
Hopefully that gets you on track
Sent from my HTC One XL running super smooth Sense 5
31ken31 said:
flash a sense rom.
S-off
Ruu to latest.. with s-off bootloader can remain unlocked.
Flash a recovery ( nothing higher than twrp 2.3.3.1 cause of wiping issues)
Then flash a rom.
Hopefully that gets you on track
Sent from my HTC One XL running super smooth Sense 5
Click to expand...
Click to collapse
Can you plz point me to a link for latest RUU?
Everything you need is in redpoint73's resource compilation thread stickied in the android development section.
Sent from my HTC One X using xda app-developers app
exad said:
Everything you need is in redpoint73's resource compilation thread stickied in the android development section.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I have decided to run RUU and take the phone back to stock.
So i fastboot oem lock. and try to run RUU from computer.
I get error 170.
now my phone stuck in the bootloader, cant boot into system. cant boot into recovery.
Please help~!!!
jzhang0818 said:
I have decided to run RUU and take the phone back to stock.
So i fastboot oem lock. and try to run RUU from computer.
I get error 170.
now my phone stuck in the bootloader, cant boot into system. cant boot into recovery.
Please help~!!!
Click to expand...
Click to collapse
Seems u f'd up.. what exactly happened
Sent from my HTC One XL running super smooth Sense 5
31ken31 said:
Seems u f'd up.. what exactly happened
Sent from my HTC One XL running super smooth Sense 5
Click to expand...
Click to collapse
Thanks for your reply.
All I pretty much did was fastboot oem lock.
then try to connect to computer and run RUU. (I was told this is the way to restore the phone back to stock completely).
now all i can do is boot into bootloader. can't go in recovery can't boot into system.
I am looking for some to restore this phone completely to stock. (I don't need unlock or root).
I am only looking to make this phone an test phone for an new app that we are developing.
thank you
31ken31 said:
flash a sense rom.
S-off
Ruu to latest.. with s-off bootloader can remain unlocked.
Flash a recovery ( nothing higher than twrp 2.3.3.1 cause of wiping issues)
Then flash a rom.
Hopefully that gets you on track
Sent from my HTC One XL running super smooth Sense 5
Click to expand...
Click to collapse
He told you how to get to stock here. I don't see relocking in there anywhere so why would you relock? You can relock the phone after s-off and ruu. This phone will brick if you have supercid and ruu or update to 3.18 so returning completely stock is difficult to say the least.
Sent from my HTC One X using xda app-developers app