Hi all.
Im using HTC One S Tmobile Android 4.1.1, i check update software haveing small update 3.14.531.17 but when i downloaded it, my phone boot to recovery and a progress bar appeared down the bottom and it ran the update. But it runs 20% then stop and red triangle appeared. (I using stock recovery)
My HTC One S is unlock bootloader, super cid 111111 and s-off.
So what is the matter with my phone ? Anyone can help me plz. I will be very grateful.
Sory bcz of my bad English.
Thanks all !
a_new_day1503 said:
Hi all.
Im using HTC One S Tmobile Android 4.1.1, i check update software haveing small update 3.14.531.17 but when i downloaded it, my phone boot to recovery and a progress bar appeared down the bottom and it ran the update. But it runs 20% then stop and red triangle appeared. (I using stock recovery)
My HTC One S is unlock bootloader, super cid 111111 and s-off.
So what is the matter with my phone ? Anyone can help me plz. I will be very grateful.
Sory bcz of my bad English.
Thanks all !
Click to expand...
Click to collapse
First thing, you update your phone with SuperCID and OTA, you get a bricked device.
Next, Remove your supercid, change it to original..
Relock your bootloader.
And try to update again.
khan.orak said:
First thing, you update your phone with SuperCID and OTA, you get a bricked device.
Next, Remove your supercid, change it to original..
Relock your bootloader.
And try to update again.
Click to expand...
Click to collapse
Thanks, i'll try with ur tip.
Sent from my HTC VLE_U using xda app-developers app
khan.orak said:
First thing, you update your phone with SuperCID and OTA, you get a bricked device.
Next, Remove your supercid, change it to original..
Relock your bootloader.
And try to update again.
Click to expand...
Click to collapse
I have change CID to T-MOB010 and relock bootloader but it's still stuck at red triangle
So sad.
a_new_day1503 said:
I have change CID to T-MOB010 and relock bootloader but it's still stuck at red triangle
So sad.
Click to expand...
Click to collapse
Try this Thread
---------- Post added at 07:00 PM ---------- Previous post was at 06:59 PM ----------
a_new_day1503 said:
Thanks, i'll try with ur tip.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I think it is because you have custom recovery. Maybe flashing Stock recovery and then updating would help.
khan.orak said:
Try this Thread
---------- Post added at 07:00 PM ---------- Previous post was at 06:59 PM ----------
I think it is because you have custom recovery. Maybe flashing Stock recovery and then updating would help.
Click to expand...
Click to collapse
Thanks for instruction, i have tried at rc420head's thread, then try to flash your recovery, last time, i flash recovery which exists in firmware.zip inside OTA.zip 3.14.531.17 but it is not still change Any ideas for this case ?
a_new_day1503 said:
Thanks for instruction, i have tried at rc420head's thread, then try to flash your recovery, last time, i flash recovery which exists in firmware.zip inside OTA.zip 3.14.531.17 but it is not still change Any ideas for this case ?
Click to expand...
Click to collapse
What command do you use to flash recovery? how do you flash it?
khan.orak said:
What command do you use to flash recovery? how do you flash it?
Click to expand...
Click to collapse
fastboot flash recovery recovery.img ?
btw for sure, i afraid of wrong, i have flash by HTC One S All in One Toolkit v4.0.
a_new_day1503 said:
fastboot flash recovery recovery.img ?
btw for sure, i afraid of wrong, i have flash by HTC One S All in One Toolkit v4.0.
Click to expand...
Click to collapse
yes that's the correct command. I don't understand what do you mean by installing through HTC All In One Toolkit?
do you have fastboot and adb files?
if yes, place recovery.img there.
Open a command window from there, and use the same command to flash the recovery.
khan.orak said:
yes that's the correct command. I don't understand what do you mean by installing through HTC All In One Toolkit?
do you have fastboot and adb files?
if yes, place recovery.img there.
Open a command window from there, and use the same command to flash the recovery.
Click to expand...
Click to collapse
I flash by direct command, but still error red triangle, then i re-flash ur recovery through HTC One S All in One Toolkit V4.0, but same.
So tired, Do u think i should restore backup rom and dont worry about OTA update ?
a_new_day1503 said:
I flash by direct command, but still error red triangle, then i re-flash ur recovery through HTC One S All in One Toolkit V4.0, but same.
So tired, Do u think i should restore backup rom and dont worry about OTA update ?
Click to expand...
Click to collapse
Try flashing my recovery by direct command.
That small update is for some battery improvements from T-Mobile. Maybe it does make a difference. but not critical. I can achieve high battery times with custom kernels. Maybe you have tried them.
khan.orak said:
Try flashing my recovery by direct command.
That small update is for some battery improvements from T-Mobile. Maybe it does make a difference. but not critical. I can achieve high battery times with custom kernels. Maybe you have tried them.
Click to expand...
Click to collapse
Ok, i will try last time.
Now my Htc One S is : S-Off, Relock bootloader, CID : T-MOB010 and ur stock recovery.
a_new_day1503 said:
Ok, i will try last time.
Now my Htc One S is : S-Off, Relock bootloader, CID : T-MOB010 and ur stock recovery.
Click to expand...
Click to collapse
Still not change : Red triangle
a_new_day1503 said:
Still not change : Red triangle
Click to expand...
Click to collapse
You get a red triangle when you select Recovery on Bootloader screen?
khan.orak said:
You get a red triangle when you select Recovery on Bootloader screen?
Click to expand...
Click to collapse
No, if i boot to recovery from bootloader, i know red triangle is normal.
But i downloaded 3.14.531.17 OTA.zip, then i choose install now, it is automatically boot in to recovery, green progress bar run perhaps 20%, then stop and red triangle appear.
a_new_day1503 said:
No, if i boot to recovery from bootloader, i know red triangle is normal.
But i downloaded 3.14.531.17 OTA.zip, then i choose install now, it is automatically boot in to recovery, green progress bar run perhaps 20%, then stop and red triangle appear.
Click to expand...
Click to collapse
Have you tried this?
Go to Fastboot, enter this code:
Code:
fastboot oem rebootRUU
Then when you see the HTC logo.
Code:
fastboot flash zip firmware.zip
first time it might fail. Do it second time and it will progress. 3 4 tries are normal
EDIT: Wait. Is that an OTA.zip? that's a whole ROM not firmware.
khan.orak said:
Have you tried this?
Go to Fastboot, enter this code:
Code:
fastboot oem rebootRUU
Then when you see the HTC logo.
Code:
fastboot flash zip firmware.zip
first time it might fail. Do it second time and it will progress. 3 4 tries are normal
Click to expand...
Click to collapse
I tried like that. I flash firmware.zip which at topic which show me link and result isn't change. Then i flash firmware.zip inside OTA.zip but still red triangle.
Haha, my phone is special or am i wrong at any step?
But if s-off, relock bootloader and cid tmous, are u sure that is ok means can update via OTA/
Sent from my HTC VLE_U using xda app-developers app
a_new_day1503 said:
I tried like that. I flash firmware.zip which at topic which show me link and result isn't change. Then i flash firmware.zip inside OTA.zip but still red triangle.
Haha, my phone is special or am i wrong at any step?
But if s-off, relock bootloader and cid tmous, are u sure that is ok means can update via OTA/
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yeah, okay to flash with CID other than SuperCID. With SuperCID it bricks the phone when you do an OTA update.
Bud, maybe try RUU, go full stock and then get this small update OTA. That will solve all the hassle.
khan.orak said:
Yeah, okay to flash with CID other than SuperCID. With SuperCID it bricks the phone when you do an OTA update.
Bud, maybe try RUU, go full stock and then get this small update OTA. That will solve all the hassle.
Click to expand...
Click to collapse
Thanks, i think it is only way for get newest update from tmobile.
Sent from my HTC VLE_U using xda app-developers app
khan.orak said:
Yeah, okay to flash with CID other than SuperCID. With SuperCID it bricks the phone when you do an OTA update.
Bud, maybe try RUU, go full stock and then get this small update OTA. That will solve all the hassle.
Click to expand...
Click to collapse
I dont need get RUU then get small update OTA, i get lastest RUU which after run it, dont need get any OTA update.
From now, if Tmobile or HTC release any OTA update, i am going to download newest RUU and run it instead of get update via OTA, that is so tired and waste time.
Related
So my ATT One X is soft bricked and when I run RUU_Evita_UL_Cingular_US-1.82.502 It gives me the customer ID error.
I rooted, unlocked bootloader, and flashed CMR, but it is now no longer rooted and the bootloader is relocked.
I did modify the CID to "11111111" to unlock the bootloader, but without me being rooted I am unable to put the original "mmcblk0p4" back on (idk if that even matters.) I have no backups and absolutely everything is erased.
I did flash the stock recovery img file, but I don't know if it was relevant to international One X or if there is one specifically for ATT One X.
I guess a fix would be making a goldcard, without an sd card somehow....
Thanks for the Help.
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
_MetalHead_ said:
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I was actually using the 1.7 RUU
I'll try 1.82 then 1.85. Hopefully that will work.
Thanks for the quick reply! :good:
Have you tried to relocking the boot loader?
fastboot oem lock
Then run ruu.
The ruu will flash the stock recovery.
Sent from my HTC One X using xda premium
Still not going through and getting same error....
Any ideas?
Thanks.
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
18th.abn said:
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No. I'm in US on ATT network. And yes I did change the CID to 11111111 because I used that method to unlock my bootloader.
I've tried several RUUs for my phone and still get same error. If I were to verify I had changed the CID I would have to be rooted.
Is it possible to root a soft-bricked device????
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
---------- Post added at 08:51 PM ---------- Previous post was at 08:44 PM ----------
I was stuck with a soft brick when I interrupted the installation of a ROM that was a bad download.
I was able to do what I said in my previous post and it fixed me right up
gunnyman said:
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
Click to expand...
Click to collapse
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
gunnyman said:
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
ArcriusOneX said:
gunnyman said:
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
gunnyman said:
ArcriusOneX said:
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
ArcriusOneX said:
gunnyman said:
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
yeah I like it better myself it's faster.
glad you're all fixed
Click to expand...
Click to collapse
Hi, i need to revert to stock and want to know if the Vodafone UK RUU will work on my device with the cid VODAP102 (Vodafone Germany) ? Has anyone tried? Or is there a RUU Vodafone DE?
Thanks in advance!
Sent from my HTC Desire S using xda app-developers app
Hi,
The Vodafone uk ruu works perfect.
Gesendet von meinem HTC Desire S mit Tapatalk 2
petjo said:
Hi, i need to revert to stock and want to know if the Vodafone UK RUU will work on my device with the cid VODAP102 (Vodafone Germany) ? Has anyone tried? Or is there a RUU Vodafone DE?
Thanks in advance!
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
When you have the RUU, run it without a device first. When the first window of the RUU opens, drag it to the side of your screen, open Explorer and search your windows drive for "rom.zip". When you find it copy it to another location and close the RUU window.
Open rom.zip archive and you will find a file called "android-info.txt" open it and see if your cid is listed there. If it is present you can flash this RUU safely.
Yep, it's in there. Thank you guys!
Sent from my HTC Desire S using xda app-developers app
Same in reverse ...
petjo said:
Yep, it's in there. Thank you guys!
Click to expand...
Click to collapse
Conversely, that should mean that I can use the Vodafone UK RUU RUU_Saga_Vodafone_UK_1.32.161.1_Radio_20.28b.30.0805U_38.03.02.15_M_release_179398_signed.exe to downgrade my Vodafone DE Desire S (Android 2.3.5, Hboot 2.00.0002, Software 2.10.161.5) using this method here? - http://forum.xda-developers.com/showpost.php?p=20535265&postcount=26
amidabuddha said:
When you have the RUU, run it without a device first. When the first window of the RUU opens, drag it to the side of your screen, open Explorer and search your windows drive for "rom.zip". When you find it copy it to another location and close the RUU window.
Open rom.zip archive and you will find a file called "android-info.txt" open it and see if your cid is listed there. If it is present you can flash this RUU safely.
Click to expand...
Click to collapse
What is the significance of HBOOT Preupdate? All the RUUs have a Preupdate value 13, my phone has a Preupdate value of 12. That doesn't matter probably?
Medhavi said:
Conversely, that should mean that I can use the Vodafone UK RUU RUU_Saga_Vodafone_UK_1.32.161.1_Radio_20.28b.30.0805U_38.03.02.15_M_release_179398_signed.exe to downgrade my Vodafone DE Desire S (Android 2.3.5, Hboot 2.00.0002, Software 2.10.161.5) using this method here? - http://forum.xda-developers.com/showpost.php?p=20535265&postcount=26
Click to expand...
Click to collapse
Medhavi said:
What is the significance of HBOOT Preupdate? All the RUUs have a Preupdate value 13, my phone has a Preupdate value of 12. That doesn't matter probably?
Click to expand...
Click to collapse
I don't know u guys are gonna get a RUU now.... HTC is destroying every RUU Web on earth now....
Sent from my supercharged tank
Dear Guys,
Does anybody have this RUU?
Voda_UK_2.10.161.5
I can not unbrick my friend's phone without this, because it's "s-on" and the above version is installed, but while tring to install custom rom an error occoured. The device doesn't boot, stops at HTC logo...
Thanks in advance
http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
Try this, not sure if the ruu is there but is one of the few sites still open
“Without deviation from the norm, progress is not possible.”*―*Frank Zappa
Thanks for your help, but it's not there. Is there any way to restore DS without this RUU? It's bootloader unlocked, rooted, has the custom recovery. unfortunately the "misc version" was not uploaded in adb mode, thus I cannot change the main version, to be able to downgrade it. But since the main version is "too high" (2.10.161.5) and there is no adb mode and I dont have the original RUU there is nothing to do. Is it possible somehow to change the main version in fastboot???? I think this would be the only chance without the the ruu.
Try this site http://www.androidfiles.org/ruu/?developer=Saga
“I've had great success being a total idiot. ”*―*Jerry Lewis
pezus1 said:
Dear Guys,
Does anybody have this RUU?
Voda_UK_2.10.161.5
I can not unbrick my friend's phone without this, because it's "s-on" and the above version is installed, but while tring to install custom rom an error occoured. The device doesn't boot, stops at HTC logo...
Thanks in advance
Click to expand...
Click to collapse
Guess you forgot to fastboot flash boot boot.img
Also, why would you need a RUU anyway? You can still enter recovery, can't you? Heck, of course you can: even if you couldn't you could always fastboot flash recovery recovery.img a working one.
I fail to see why a RUU would be necessary here.
Aquous said:
Guess you forgot to fastboot flash boot boot.img
Also, why would you need a RUU anyway? You can still enter recovery, can't you? Heck, of course you can: even if you couldn't you could always fastboot flash recovery recovery.img a working one.
I fail to see why a RUU would be necessary here.
Click to expand...
Click to collapse
Thanks for your help, but I dont really understand what u say..... Right now there is clockwork 5.0.2.0 on it, we tried to install custom roms, which seemed to be done, but the phone stops at HTC logo after flashing. I guess I could flash back the original recovery (actually I only have one from RUU 1.32.161.1), but how would it solve my problem? How about the other image files, like system, hboot etc? Please exlain it to me a bit more detailed! Thx
pezus1 said:
Thanks for your help, but I dont really understand what u say..... Right now there is clockwork 5.0.2.0 on it, we tried to install custom roms, which seemed to be done, but the phone stops at HTC logo after flashing. I guess I could flash back the original recovery (actually I only have one from RUU 1.32.161.1), but how would it solve my problem? How about the other image files, like system, hboot etc? Please exlain it to me a bit more detailed! Thx
Click to expand...
Click to collapse
have you done
Code:
fastboot flash boot boot.img
?
Sent from my supercharged :tank:
hisname said:
have you done
Code:
fastboot flash boot boot.img
?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
Lets see again: bootloader unlocked, cwm 5.0.2.0 installed, as you adviced I flased an official 1.32.161.1(older than the original 2.10.161.5) boot.img, then tried to install from recovery the custom rom, which still seems to be ok, but the phone freezes at htc logo during boot. This custom rom is a well known working version, there shouldnt be any problem. What else can I do without the RUU?
pezus1 said:
Lets see again: bootloader unlocked, cwm 5.0.2.0 installed, as you adviced I flased an official 1.32.161.1(older than the original 2.10.161.5) boot.img, then tried to install from recovery the custom rom, which still seems to be ok, but the phone freezes at htc logo during boot. This custom rom is a well known working version, there shouldnt be any problem. What else can I do without the RUU?
Click to expand...
Click to collapse
What? You flashed the boot.img from a RUU and expected it to work with a custom ROM??
Why don't you just flash the boot.img that's included with the custom ROM...?
Aquous said:
What? You flashed the boot.img from a RUU and expected it to work with a custom ROM??
Why don't you just flash the boot.img that's included with the custom ROM...?
Click to expand...
Click to collapse
Thanks guys, problem solved!!
pezus1 said:
Thanks guys, problem solved!!
Click to expand...
Click to collapse
Can you mark thread title solved, thanks.
“Pressure is something you feel when you don't know what the hell you're doing.”*―*Peyton Manning
Its my sisters phone, currently stucked at bootsplash screen
I shall post the bootloader information first....
** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHOP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.0909_L
OpenDSP-vs29.1.0.45.0662
eMMc-boot
Jun 11 2012
CID returned is HTC_044... No matter how i flash recovery, the phone simply reboots... means i cant get into recovery mode.
I tried reflashing boot.img from vipers and relash recovery... doesnt work.
Right now, im trying to flash RUU via zip..... I have relocked my bootloader... Current status is that I managed to send the zip file over... but its stucked at writing for the past 10 mins...
This is the RUU where i extracted the rom.zip from
"RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed"
It should be the same as my current rom... which if i read correctly, it will not get updated? that I should use the newer 3.17 RUUs for asia in order to fix?
************************ Update ************************
Okay great... now after waiting for 4332 seconds for the writing part to finish... I knew its not going to work via waiting any longer... I unplugged the USB... the command prompt shows up an error (FAILED, too many links)... I attempted to restart the phone from the HTC logo and now it doesnt start at all... cant even get into bootloader... =.=
************************ Update ************************
Okay I've managed to save my phone using this method http://unlimited.io/qhsusbdload.htm
So now im back to square one... I can go bootloader... i unlocked it again... but i still cant go recovery...
************************ Update ************************
Now its back to being bricked again... as I was working on the phone outside when i managed to unbricked it. I choose to power off the phone from bootloader menu, thinking that I could work on it when I get home... alas, when i got home... the phone doesnt turn on... and i saw the dreaded QHSUSB_DLOAD thingy again...... omg... And the above method no longer works..........
kedirakevo said:
Its my sisters phone, currently stucked at bootsplash screen
I shall post the bootloader information first....
** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHOP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.0909_L
OpenDSP-vs29.1.0.45.0662
eMMc-boot
Jun 11 2012
CID returned is HTC_044... No matter how i flash recovery, the phone simply reboots... means i cant get into recovery mode.
I tried reflashing boot.img from vipers and relash recovery... doesnt work.
Right now, im trying to flash RUU via zip..... I have relocked my bootloader... Current status is that I managed to send the zip file over... but its stucked at writing for the past 10 mins...
This is the RUU where i extracted the rom.zip from
"RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed"
It should be the same as my current rom... which if i read correctly, it will not get updated? that I should use the newer 3.17 RUUs for asia in order to fix?
Click to expand...
Click to collapse
Stuck in a similar problem not sure what to do...
I dont understand why you guys want to relock and run the ruu... why not just flash a stock rom? Less headache
Sent from my One X using xda app-developers app
If you're relocked then you can't flash the zip. The ruu is an exe you need to run it with your phone in fastboot usb
Sent from my VENOMized HoxL
exad said:
I dont understand why you guys want to relock and run the ruu... why not just flash a stock rom? Less headache
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
how do i flash rom when recovery aint working?
area51avenger said:
If you're relocked then you can't flash the zip. The ruu is an exe you need to run it with your phone in fastboot usb
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1952426
Program says phone's bootloader must be locked in order to flash ruu zip
kedirakevo said:
how do i flash rom when recovery aint working?
Click to expand...
Click to collapse
Unlock boot loader again if its relocked and just fastboot flash twrp.. use the one click tool if you don't know how to flash recovery but as long as boot loader is unlocked you can flash recovery. Once you do, recovery will work again.
Sent from my One X using xda app-developers app
exad said:
Unlock boot loader again if its relocked and just fastboot flash twrp.. use the one click tool if you don't know how to flash recovery but as long as boot loader is unlocked you can flash recovery. Once you do, recovery will work again.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
which i stated in my first post that before relocking my bootloader... I have been reflashing the recovery many times but i cant boot into recovery mode....
kedirakevo said:
which i stated in my first post that before relocking my bootloader... I have been reflashing the recovery many times but i cant boot into recovery mode....
Click to expand...
Click to collapse
When you flash recovery is it successful? When you select recovery from boot loader what happens?
Which recovery and version are you flashing?
Sent from my One X using xda app-developers app
exad said:
When you flash recovery is it successful? When you select recovery from boot loader what happens?
Which recovery and version are you flashing?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
yea command prompt claimed its sucessful... I used the latest all in one toolkit where the creator claimed to use TWRP 2.4.1.0
kedirakevo said:
yea command prompt claimed its sucessful... I used the latest all in one toolkit where the creator claimed to use TWRP 2.4.1.0
Click to expand...
Click to collapse
Maybe A bad download. Download the latest twrp.
Make sure boot loader is unlocked and you have fastboot usb on in bootloader
Then within toolkit pick flash other recovery and manually select the one you downloaded. Then try selecting recovery in bootloader.
Sent from my One X using xda app-developers app
kedirakevo said:
Program says phone's bootloader must be locked in order to flash ruu zip
Click to expand...
Click to collapse
RUU is an exe the fact it creates a rom.zip is fairly well hidden. Are you running the exe or doing some other crazy thing?
You should not be flashing anything to your phone if you are confusing zip and exe's, it means you lack the basic understanding of computers to be able to complete these tasks without failing.
How did you try to flash the recovery? What recovery did you try to flash? What were the errors given?
EDIT: you should not be using one click tools.
Use fastboot and flash recovery yourself, it is a simple task.
exad said:
Maybe A bad download. Download the latest twrp.
Make sure boot loader is unlocked and you have fastboot usb on in bootloader
Then within toolkit pick flash other recovery and manually select the one you downloaded. Then try selecting recovery in bootloader.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
wish I could try that... it bricked now.
twistedddx said:
RUU is an exe the fact it creates a rom.zip is fairly well hidden. Are you running the exe or doing some other crazy thing?
You should not be flashing anything to your phone if you are confusing zip and exe's, it means you lack the basic understanding of computers to be able to complete these tasks without failing.
How did you try to flash the recovery? What recovery did you try to flash? What were the errors given?
EDIT: you should not be using one click tools.
Use fastboot and flash recovery yourself, it is a simple task.
Click to expand...
Click to collapse
the zip file can be obtained via temp folder of the windows directory when you run the exe file.
The all in one toolkit requires the zip so I got it done via that method...
Yes I know how to do it via command prompt but the toolkit is handy...
And lastly you can say my understanding of mobile phone system isnt complete but dont insult me saying I dont understand whats zip and exe......
Bricked? Exactly what is happening.
Sent from my One X using xda app-developers app
exad said:
Bricked? Exactly what is happening.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
beats me man... Told you, was trying to flash RUU through zip then it just hung there... but I managed to save my phone... I redownloaded and reflashed recovery as you advised but still no avail! Basically, back to square one....
kedirakevo said:
the zip file can be obtained via temp folder of the windows directory when you run the exe file.
The all in one toolkit requires the zip so I got it done via that method...
Yes I know how to do it via command prompt but the toolkit is handy...
And lastly you can say my understanding of mobile phone system isnt complete but dont insult me saying I dont understand whats zip and exe......
Click to expand...
Click to collapse
I know it can be obtained from temp folder.
Why go to the effort of getting the rom.zip to use in the toolkit when you could simply just run the RUU, which you had to do to get the rom.zip in the first place? Especially when it was failing, why push on with trying to use the toolkit instead of just using the RUU as it was intended by HTC?
I have not much knowledge of the toolkit, but when it flashes zip's is it for normal ROM's or for RUU rom.zip? The rom.zip is not in a format that can normally be used by most tools, it is not the same as flashing a custom ROM.
The toolkit is likely only for installing custom ROM's via pre installed TWRP and not compatible with rom.zip.
You said you were using a RUU zip and complaining it was failing, it appeared at face value you were confusing what the RUU even is.
I am still lost why running the RUU and grabbing the rom.zip from temp folder and then flashing in a toolkit was your chosen method. This just points more towards you are confused about what a RUU is.
I am sure the RUU would work if you just let it run like it is supposed to.
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
kedirakevo said:
was trying to flash RUU through zip then it just hung there.
Click to expand...
Click to collapse
Why?
Personally because of the state you have got the phone in to I would:
1)go get the correct tools. eg fastboot, unlockcode, twrp and rom
2)Ensure phone is charged
3)fastboot oem lock
4)Run RUU.. and try actually running it which means just click next and yes a lot.. no fancy going to temp folders and trying to incorrectly install rom.zip via random tools
5)fastboot flash unlocktoken Unlock_code.bin
6)fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
7)fastboot flash boot boot.img (from desired rom)
8)boot into recovery
9)mount USB and transfer desired ROM
10)wipe data and system
11)install ROM
12)reboot in to ROM.
twistedddx said:
I know it can be obtained from temp folder.
Why go to the effort of getting the rom.zip to use in the toolkit when you could simply just run the RUU, which you had to do to get the rom.zip in the first place? Especially when it was failing, why push on with trying to use the toolkit instead of just using the RUU as it was intended by HTC?
I have not much knowledge of the toolkit, but when it flashes zip's is it for normal ROM's or for RUU rom.zip? The rom.zip is not in a format that can normally be used by most tools, it is not the same as flashing a custom ROM.
The toolkit is likely only for installing custom ROM's via pre installed TWRP and not compatible with rom.zip.
You said you were using a RUU zip and complaining it was failing, it appeared at face value you were confusing what the RUU even is.
I am still lost why running the RUU and grabbing the rom.zip from temp folder and then flashing in a toolkit was your chosen method. This just points more towards you are confused about what a RUU is.
I am sure the RUU would work if you just let it run like it is supposed to.
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
Why?
Personally because of the state you have got the phone in to I would:
1)go get the correct tools. eg fastboot, unlockcode, twrp and rom
2)Ensure phone is charged
3)fastboot oem lock
4)Run RUU.. and try actually running it which means just click next and yes a lot.. no fancy going to temp folders and trying to incorrectly install rom.zip via random tools
5)fastboot flash unlocktoken Unlock_code.bin
6)fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
7)fastboot flash boot boot.img (from desired rom)
8)boot into recovery
9)mount USB and transfer desired ROM
10)wipe data and system
11)install ROM
12)reboot in to ROM.
Click to expand...
Click to collapse
well... as mentioned, would really love to follow your steps but.... its bricked now... again...
I did run RUU.exe once but it hung for 30 mins without activity... but then again that was when my bootloader was unlocked... then i read that i can relock and do it through ruu.zip instead.... so i went that route.......
Btw I did update my status on my first post...
kedirakevo said:
well... as mentioned, would really love to follow your steps but.... its bricked now... again...
I did run RUU.exe once but it hung for 30 mins without activity... but then again that was when my bootloader was unlocked... then i read that i can relock and do it through ruu.zip instead.... so i went that route.......
Btw I did update my status on my first post...
Click to expand...
Click to collapse
The least risky way would be to flash a stock ROM from here not an ruu. There are some untouched roms. I, myself have bricked running the telus ruu.
Sent from my One X using xda app-developers app
HOX is in bootloop. I could not get it to boot into TWRP or anything but bootloader.
I tried pushing a new boot.img in FASTBOOT. Nothing.
I tried pushing a newer version of TWRP in FASTBOOT. Nothing.
I relocked the bootloader and ran the RUU, which installed fine. Still stuck in a bootloop.
Any ideas?
FarBeyond said:
HOX is in bootloop. I could not get it to boot into TWRP or anything but bootloader.
I tried pushing a new boot.img in FASTBOOT. Nothing.
I tried pushing a newer version of TWRP in FASTBOOT. Nothing.
I relocked the bootloader and ran the RUU, which installed fine. Still stuck in a bootloop.
Any ideas?
Click to expand...
Click to collapse
Can you provide more information ? Which version are you on and what RUU you ran ..
Sent from my Nexus 4 using xda premium
Sounds like you need to wipe all data. Don't know the commands though, sorry. But Android is Linux, so
rm /data/*
rm /cache/*
could work, not sure how to do it through adb.
Make sure you're using files for the S4 evita One X. If you're pushing recovery etc for the Tegra One X, they aren't going to work.
So are saying that you can get into bootloader but not recovery? did you select recovery from bootloader? i know it is a silly question, but you did not mention it...also did you try to manually get into recovery by holding power+vol up+vol down and then letting go power once the phone vibrates? if all else fails, grab the RUU file from http://forum.xda-developers.com/showthread.php?t=2156368 once you get to the black screen that says htc
Herc08 said:
So are saying that you can get into bootloader but not recovery? did you select recovery from bootloader? i know it is a silly question, but you did not mention it...also did you try to manually get into recovery by holding power+vol up+vol down and then letting go power once the phone vibrates? if all else fails, grab the RUU file from http://forum.xda-developers.com/showthread.php?t=2156368 once you get to the black screen that says htc
Click to expand...
Click to collapse
you can't manually get into recovery with a button combination.
Official -> [ http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe ] a40cd830e8c57109d140e1e68e2d1328
Mister J said:
Sounds like you need to wipe all data. Don't know the commands though, sorry. But Android is Linux, so
rm /data/*
rm /cache/*
could work, not sure how to do it through adb.
Click to expand...
Click to collapse
In the recovery.command file:
--wipe_data
--wipe_cache
Get into dowload mode n flashing firmware.. or get into fastboot mode n install recovery.img after install make wipe data/factory reset.
DvineLord said:
you can't manually get into recovery with a button combination.
Official -> [ http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe ] a40cd830e8c57109d140e1e68e2d1328
Click to expand...
Click to collapse
Oh wow. You are right. Sorry about that, been doing too many Samsung phones.
Sent from my One X using xda app-developers app
abhipati said:
Can you provide more information ? Which version are you on and what RUU you ran ..
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
On the newest version of hboot. htc_one_x_RUU_2.20.502.7_att_us_08022012
iElvis said:
Make sure you're using files for the S4 evita One X. If you're pushing recovery etc for the Tegra One X, they aren't going to work.
Click to expand...
Click to collapse
Already checked that.
Herc08 said:
So are saying that you can get into bootloader but not recovery? did you select recovery from bootloader? i know it is a silly question, but you did not mention it...if all else fails, grab the RUU file from http://forum.xda-developers.com/showthread.php?t=2156368 once you get to the black screen that says htc
Click to expand...
Click to collapse
Already did this, yes.
ahmyani said:
get into fastboot mode n install recovery.img after install make wipe data/factory reset.
Click to expand...
Click to collapse
Did this too... Says it completes but still wont boot or go into recovery...
Wait so you're s on and on which hboot?
a box of kittens said:
Wait so you're s on and on which hboot?
Click to expand...
Click to collapse
I had to relock the bootloader to put the RUU on the phone.
Screen says
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.31_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
FarBeyond said:
I had to relock the bootloader to put the RUU on the phone.
Click to expand...
Click to collapse
That's your problem. You have to unlock again to push a custom recovery.
And what happens when you select fastboot or recovery? It should not be a boot loop since it is not booting into the os. Sorry of you already answered, reading from phone worked a double shift
Sent from my One X using xda app-developers app
It was bootlooping And I couldn't get into recovery so I relocked it and flashed the AT&T RUU. It said it installed all the way.
It is still bootlooping!
FarBeyond said:
It was bootlooping And I couldn't get into recovery so I relocked it and flashed the AT&T RUU. It said it installed all the way.
It is still bootlooping!
Click to expand...
Click to collapse
Edit: What have you done since completing the RUU? Anything?
iElvis said:
Edit: What have you done since completing the RUU? Anything?
Click to expand...
Click to collapse
No. In order to install the factory RUU you have to relock the bootloader... Or you get an error...
FarBeyond said:
No. In order to install the factory RUU you have to relock the bootloader... Or you get an error...
Click to expand...
Click to collapse
I'm aware of that. You've done nothing but run the RUU at this point? You might try running it again. It should not be bootlooping if it installed correctly, since that replaces everything on the phone.
iElvis said:
I'm aware of that. You've done nothing but run the RUU at this point? You might try running it again. It should not be bootlooping if it installed correctly, since that replaces everything on the phone.
Click to expand...
Click to collapse
That's what I thought too... I had given the phone to my son a month ago after my wife had used it for a while... Hard telling what he did to it... Will try to reinstall the RUU...
hi guys, ill try and keep it as brief as poss.
Phone was rooted working fine, dropped the phone and cracked the screen so sent for repair. Repair shop returned it back to stock :/
Left phone stock and working fine for a couple of months, accidentally let phone fully discharge and think it damaged the battery. Bought a new battery but the phone just boot loops. Can get into Hboot but when i choose recovery it just starts boot looping again. In a panic i flashed a 3.33 firmware but made no difference. Can someone give me a step by step how to sort? thanks!!
Phone says :
-firmware- 3.33-
pyramid pvt ship s-off rl
hboot 1.27.1100
emmc-boot
Im guessing its also locked because when i do the oem lock in command prompt its saying device is locked. cheers all.
mickey909 said:
hi guys, ill try and keep it as brief as poss.
Phone was rooted working fine, dropped the phone and cracked the screen so sent for repair. Repair shop returned it back to stock :/
Left phone stock and working fine for a couple of months, accidentally let phone fully discharge and think it damaged the battery. Bought a new battery but the phone just boot loops. Can get into Hboot but when i choose recovery it just starts boot looping again. In a panic i flashed a 3.33 firmware but made no difference. Can someone give me a step by step how to sort? thanks!!
Phone says :
-firmware- 3.33-
pyramid pvt ship s-off rl
hboot 1.27.1100
emmc-boot
Im guessing its also locked because when i do the oem lock in command prompt its saying device is locked. cheers all.
Click to expand...
Click to collapse
did you try to reflash recovery to see if will work?
Mile_zdr said:
did you try to reflash recovery to see if will work?
Click to expand...
Click to collapse
If i connect fastboot-usb and use the command prompt to flash a recovery i get (error-partition doesnt exist!!)
Can i put any recovery on the sd card and somehow load it without using the recovery option?
mickey909 said:
If i connect fastboot-usb and use the command prompt to flash a recovery i get (error-partition doesnt exist!!)
Can i put any recovery on the sd card and somehow load it without using the recovery option?
Click to expand...
Click to collapse
what command do you use?
Mile_zdr said:
what command do you use?
Click to expand...
Click to collapse
fastboot flash zip recovery.zip
mickey909 said:
fastboot flash zip recovery.zip
Click to expand...
Click to collapse
why dont you try with recovery.img extract it from zip and use this command fasboot flash recovery recovery.img
Mile_zdr said:
why dont you try with recovery.img extract it from zip and use this command fasboot flash recovery recovery.img
Click to expand...
Click to collapse
Thanks mile_zdr. My Bad. Looks like it wrote ok (writing "recovery" ... OKAY) when i reboot and choose recovery option it still boot loops. :/ maybe im flashing the wrong recovery? Should any sensation recovery work?
Edit : Just flashed the sensation clockwork mod recovery successfully but still getting the boot loop when i hit recovery in the boot loader.
mickey909 said:
Thanks mile_zdr. My Bad. Looks like it wrote ok (writing "recovery" ... OKAY) when i reboot and choose recovery option it still boot loops. :/ maybe im flashing the wrong recovery? Should any sensation recovery work?
Edit : Just flashed the sensation clockwork mod recovery successfully but still getting the boot loop when i hit recovery in the boot loader.
Click to expand...
Click to collapse
i think your only option now is to flash a ruu.exe
then try again with recovery
rzr86 said:
i think your only option now is to flash a ruu.exe
then try again with recovery
Click to expand...
Click to collapse
Thanks rzr86, could you give me more info please? do i just put the ruu in the same tools folder and flash the same as the recovery?
mickey909 said:
Thanks rzr86, could you give me more info please? do i just put the ruu in the same tools folder and flash the same as the recovery?
Click to expand...
Click to collapse
no in that way
read here for more info
http://forum.xda-developers.com/showthread.php?t=1672425
rzr86 said:
no in that way
read here for more info
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
Thank you so much guys, think im beggining to understand it now. I have 1 more massive favour. Im struggling to find the right ruu for my phone, can someone point me in the right direction please?
since you are on S-OFF change your cid to supercid and choose any ruu you want
also remove your imei and serial number
don't show them in public
but i noticed something else
how in the hell you have ics hboot version with gingerbread firmware?
rzr86 said:
since you are on S-OFF change your cid to supercid and choose any ruu you want
also remove your imei and serial number
don't show them in public
but i noticed something else
how in the hell you have ics hboot version with gingerbread firmware?
Click to expand...
Click to collapse
Thats a very good question rzr86 I think i have found the right ruu but i could only find one with a firmware base of 1.73 and my phone is currently 3.33. does it matter or will have to somehow downgrade my firmware to match the ruu?
mickey909 said:
Thats a very good question rzr86 I think i have found the right ruu but i could only find one with a firmware base of 1.73 and my phone is currently 3.33. does it matter or will have to somehow downgrade my firmware to match the ruu?
Click to expand...
Click to collapse
using a gingerbread ruu it will automatically downgrade your firmware too
rzr86 said:
using a gingerbread ruu it will automatically downgrade your firmware too
Click to expand...
Click to collapse
I've successfully managed flash the stock rom but i still have the boot loop. :/
mickey909 said:
I've successfully managed flash the stock rom but i still have the boot loop. :/
Click to expand...
Click to collapse
bootloop in recovery or in the rom?
rzr86 said:
bootloop in recovery or in the rom?
Click to expand...
Click to collapse
I found the stock rom for my phone, double clicked the .exe and it went through all the loading process and installed the stock ruu onto my phone but the problem i started with is still there. If i turn the phone on it just goes to the htc logo and then reboots. If i hold power + vol down then pick recovery it does the exact same boot loop. thanks for your help!! :good:
mickey909 said:
I found the stock rom for my phone, double clicked the .exe and it went through all the loading process and installed the stock ruu onto my phone but the problem i started with is still there. If i turn the phone on it just goes to the htc logo and then reboots. If i hold power + vol down then pick recovery it does the exact same boot loop. thanks for your help!! :good:
Click to expand...
Click to collapse
i think your emmc is damaged
i don't know what else to suggest mate
wait if you get better solutions
rzr86 said:
i think your emmc is damaged
i don't know what else to suggest mate
wait if you get better solutions
Click to expand...
Click to collapse
Ok, Thanks for all your help friend. Im starting to think its a hardware fault now.