I've rooted my HTC ONE X (EVITA) with spoof-cid method. Couldn't turn S-OFF. Tried to install roms - didn't like something, wanted to go back to original.
Here when everything went wrong.
While not having any bootable roms,
I've changed CID to "CWS__001" (that was stupid)
Did "fastboot oem lock" (even more stupid)
And here I am - I can boot into fastboot only, no recovery, no rom. Can't flash anything - signature fail.
Fastboot output:
Code:
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v43.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
Here is "fastboot getvar all":
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT2B3W304230
(bootloader) imei: 359691049791521
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4163mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Is there anything I can try at that point? Also, I have linux on my pc, so, can't run RUU.exe (don't also know if it would help).
Thanks for any help.
Edit: to eliminate confusion, read my post below.
This is a shining example of why you need to actually know what you're doing before doing it.
That link you provided is for the HTC One, you're lucky you haven't bricked your phone. Do you still have the proper Evita hboot etc?
Sent from my Evita
Dimath said:
Did "fastboot oem lock" (even more stupid)
Can't flash anything
Click to expand...
Click to collapse
Of course not. You can't flash anything with a relocked bootloader and S-on. Its the very definition/purpose of a locked/relocked bootloader.
---------- Post added at 10:06 AM ---------- Previous post was at 10:01 AM ----------
timmaaa said:
This is a shining example of why you need to actually know what you're doing before doing it.
Click to expand...
Click to collapse
Agree 110%.
The biggest mistake by the OP was the lack of understanding, research, and knowledge.
I'm guessing the reason for ROMs not originally installing was as simple as a ROM for the wrong device (as the OP seems to be dangerously bouncing around device forums) or just neglecting to extract and flash boot.img manually (required with s-off).
The the subsequent steps of changing CID and relocking the bootloader seem misguided. The only reason to ever relock the bootloader is to run RUU, which OP already says he can't do on his Linux machine, anyway.
redpoint73 said:
Of course not. You can't flash anything with a relocked bootloader and S-on. Its the very definition/purpose of a locked/relocked bootloader.
Click to expand...
Click to collapse
You all are absolutely right - you need to know what you're doing if you don't want to brick the device. And I didn't really research that much.
I've locked the bootloader to flash original, signed image, that was the idea. I feel like I need to clarify what I've actually done:
1. I've got RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe from here.
2. Since I have linux, I couldn't just run the RUU.exe. I've used HTC ROM-extractor to convert RUU.exe to RUU.zip.
3. I've flashed the RUU.zip as:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
Since the rom has correct signature, it worked on S-ON and signed bootloader. The problem was, I guess, to find the correct RUU (with correct signature), and then to figure out how to flash it on linux. Well, and to know better what I'm doing
Did you have some issue when trying to flash a custom ROM (when you were still bootloader unlocked)? I don't know what "didn't like something" means in the OP.
The fix you are suggesting is complicated and risky. Extracting files from the RUU and manually flashing is very dangerous, unless you know exactly what you are doing. I've seen at least a couple folks on here brick their phones trying something similar.
Did you try both s-off methods (facepalm and Rumrunner)? Rumrunner is supposed to be easier.
Also, there was no reason to have ever changed the CID. RUU can still be run with SuperCID.
3.18 contains 2 rom.zip packages inside the exe. No one really knows why HTC did this and I have no idea what you have created via extracting from the exe.
I would say your 3.18 rom.zip is not correct.
If you want the quickest and easiest way forwards, just run the ruu exe on a Windows machine. I am sure between family, friends and work/school you have access to a Windows XP/Vista/7/8 machine.
twistedddx said:
If you want the quickest and easiest way forwards, just run the ruu exe on a Windows machine. I am sure between family, friends and work/school you have access to a Windows XP/Vista/7/8 machine.
Click to expand...
Click to collapse
That's my thought as well. Windows machines are so common, most people should be able to find one they can use for the purposes of running the RUU. Much easier and safer than what the OP is trying to do.
Related
Hi Guys, need your help on this.
I was using Fall Out Custom Rom. and then I want to restore back to my stock with S-ON of course. but after I run RUU, I've got bootloader version error, and right now just stuck in HBOOT/Fastboot. I cannot access ADB. I'm trying to find latest RUU, but there is no version higher than mine.
My Fastboot getvar all :
INFOversion: 0.5
INFOversion-bootloader: 0.98.0002
INFOversion-baseband: 3805.06.02.03_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.04.401.1
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG8810000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4193mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 0e35ea5b
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
Are you able to help?
Thanks.
Remove your serial and IMEI from the post...
suku_patel_22 said:
Remove your serial and IMEI from the post...
Click to expand...
Click to collapse
Ok. Can help with my question?
Use Gold Card - Not working
I manage using gold card and flash ruu 2.10 but still not working cause my main version is > 3. Anybody can help? please....
try reading this thread
http://forum.xda-developers.com/showthread.php?t=1728513
some ideas you can try
You forgot to downgrade misc_version before restoring to stock.
Now, you have one of 2 options:
1) If your HBOOT is modified - you can fastboot flash recovery, connect by ADB, execute misc_version script in recovery (that step saves you ROM installation) to downgrade main version, and then execute RUU again.
2) If your HBOOT is stock and you can't do anything - you'll have to unlock it the HTC way, after unlock - execute all the above (including relocking the bootloader after main version is downgraded).
Jack_R1 said:
You forgot to downgrade misc_version before restoring to stock.
Now, you have one of 2 options:
1) If your HBOOT is modified - you can fastboot flash recovery, connect by ADB, execute misc_version script in recovery (that step saves you ROM installation) to downgrade main version, and then execute RUU again.
2) If your HBOOT is stock and you can't do anything - you'll have to unlock it the HTC way, after unlock - execute all the above (including relocking the bootloader after main version is downgraded).
Click to expand...
Click to collapse
Finally it solved, I manage to found firmware with main version bigger than mine, flash it, unlock via htc dev, install recovery, change version, and return to stock successfully.
Thank you very much.
hansgregory said:
Finally it solved, I manage to found firmware with main version bigger than mine, flash it, unlock via htc dev, install recovery, change version, and return to stock successfully. can i please have a link 2 the latest version 2 please please
Thank you very much.
Click to expand...
Click to collapse
i'm stuck on htc screen laptop wont identify usb would it be possible to get some idea of how you solved this problem please i would love to know cuz i'm in the same situation my gold card wont work i keep getting error main version is older or something like that please please any help would be very helpful my details below and i also have unlocked bootloader i also cant go into recovery it jus keeps booting to bootloader or the htc screen
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4023mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.038s
kisame d shark said:
i'm stuck on htc screen laptop wont identify usb would it be possible to get some idea of how you solved this problem please i would love to know cuz i'm in the same situation my gold card wont work i keep getting error main version is older or something like that please please any help would be very helpful my details below and i also have unlocked bootloader i also cant go into recovery it jus keeps booting to bootloader or the htc screen
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4023mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.038s
Click to expand...
Click to collapse
Since your hboot already using 2+, you can do following steps:
1. unlock your bootloader using htc dev
2. after unlocked, install recovery
3. go to recovery you've previous installed then connect usb and change misc version via adb
4. relock again the bootloader
5. then you can install the RUU
Hope this help.
unlock bootloader
hansgregory said:
Since your hboot already using 2+, you can do following steps:
1. unlock your bootloader using htc dev
2. after unlocked, install recovery
3. go to recovery you've previous installed then connect usb and change misc version via adb
4. relock again the bootloader
5. then you can install the RUU
Hope this help.
Click to expand...
Click to collapse
i have already unlocked my bootloader but every time i try to change my misc version my usb can't be recognized and i cant install any recovery to my device for some reason it keeps saying image fail or it flashes the image then i try to enter recovery mode then it just boots up to the htc logo and don't go into recovery
hansgregory said:
Finally it solved, I manage to found firmware with main version bigger than mine, flash it, unlock via htc dev, install recovery, change version, and return to stock successfully.
Thank you very much.
Click to expand...
Click to collapse
Hey hansgregory, I got the same problem you had. Would u kindly tell me where to find that firmware?? my phone is dead atm
Thank you,
ahmedsalahais said:
Hey hansgregory, I got the same problem you had. Would u kindly tell me where to find that firmware?? my phone is dead atm
Thank you,
Click to expand...
Click to collapse
Snap. I'm in exactly the same boat
I downloaded it from here :
http://forumt.xda-developers.com/showthread.php?t=1722571
extract the zip and get the firmware.zip
hansgregory said:
I downloaded it from here :
http://forumt.xda-developers.com/showthread.php?t=1722571
extract the zip and get the firmware.zip
Click to expand...
Click to collapse
Link does not work
EDIT - Manager to open the thread by right click (Copy link address) and paste into google, The link is for the Chinese OTA, Can you confirm that this works OK and is all in English
Thanks
dannyhoughton74 said:
Link does not work
EDIT - Manager to open the thread by right click (Copy link address) and paste into google, The link is for the Chinese OTA, Can you confirm that this works OK and is all in English
Thanks
Click to expand...
Click to collapse
It doesn't. At least in my case.
I had to add my cid to make it loadable but that's about it:
Loading .. [PG88IMG.zip]
Checking .. [PG88IMG.zip]
Then it returns to Fastboot menu again with nothing changed!
ahmedsalahais said:
It doesn't. At least in my case.
I had to add my cid to make it loadable but that's about it:
Loading .. [PG88IMG.zip]
Checking .. [PG88IMG.zip]
Then it returns to Fastboot menu again with nothing changed!
Click to expand...
Click to collapse
Hi Ahmed,
What is the version of your hboot? is it already 2.00+? if it is you can just unlock via htc dev to flash the recovery. No need to flash the firmware
kisame d shark said:
i have already unlocked my bootloader but every time i try to change my misc version my usb can't be recognized and i cant install any recovery to my device for some reason it keeps saying image fail or it flashes the image then i try to enter recovery mode then it just boots up to the htc logo and don't go into recovery
Click to expand...
Click to collapse
IMO is that you dont need to flash the firmware, since you already said that you've already unlock the bootloader. I did flash the firmware because i want to unlock my bootloader.
I download this recovery image www.4ext.net/ddl/saga/recovery.zip, I flash this image in fastboot and the recovery installed successfully, maybe you can try it also.
after that you can install tacoroot for temporary root and misc version your device image version, then you can install ruu afterward.
hansgregory said:
Hi Ahmed,
What is the version of your hboot? is it already 2.00+? if it is you can just unlock via htc dev to flash the recovery. No need to flash the firmware
Click to expand...
Click to collapse
My problem is complex. Hboot is 0.98.0002 so i can't use HTCDev to unlock. At the same time adb is not working so i can't s-off. RUUs of 2.x or 1.x do not work either as latest image was 3.x .
I think i need to upgrade Hboot (somehow) to enable HTCdev Unlock then downgrade and s-off. That may require RUU > 3.x ... and it must be RUU not OTA or update package.
My case was the same as yours thats why i flash the firmware so i can unlock my bootloader. But you are not able to flash from chinese ota i gave you earlier?
Sent from my HTC Desire S using xda app-developers app
hansgregory said:
My case was the same as yours thats why i flash the firmware so i can unlock my bootloader. But you are not able to flash from chinese ota i gave you earlier?
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
At first i wasn't able to. Then i edited android-info.txt inside firmware.zip to fake it to support middle east. But it just load and check without asking for apply!
Hello, i'm new guy on this forum. I'm going back from s-off to s-on and official stock t-mobile ruu and i'm using tutorial form this forum. But then i try install RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed i'm getting this ERROR[170]: USB CONNECTION ERROR. But my phone is properly connected, i tried europe ruu(no usb erros), but then i got cid error.
Hboot 0.98.0000
cid t-mob005
Ok, turn in bootloader and now no usb error, but now i'm getting bootloader error 140. Any suggestions?
I'm using this ruu RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
My phone info
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
It seems that you used an European unbranded RUU. To fix you have to create a goldcard, use the 1.47.401.4 RUU again to have a booting system, then change the main version and after that flash the TMOB RUU again
Sent from my HTC Desire S
thanks, but now i got another problem, my phone turn only in bootloader(but i cant see it using adb devices). But i can choose fastboot and then i see my device using fastboot devices. So i'cant get card cid maybe there is another way to get goldcard?
cezzka said:
thanks, but now i got another problem, my phone turn only in bootloader(but i cant see it using adb devices). But i can choose fastboot and then i see my device using fastboot devices. So i'cant get card cid maybe there is another way to get goldcard?
Click to expand...
Click to collapse
Use this to get the CID
Then this to make the GoldCard
Big thanks to amidabuddha. Finally i flashed 1.47.401.4 RUU(phone is booting fine), so how i can change main version to install TMOB RUU?
cezzka said:
Big thanks to amidabuddha. Finally i flashed 1.47.401.4 RUU(phone is booting fine), so how i can change main version to install TMOB RUU?
Click to expand...
Click to collapse
Follow this guide.
When you are done I suggest to fill the offset 00000000 to 00000170 of your sdcard with zeroes (as it was before) because various users reported that running a device with a goldcard inside can cause issues.
amidabuddha said:
Follow this guide.
When you are done I suggest to fill the offset 00000000 to 00000170 of your sdcard with zeroes (as it was before) because various users reported that running a device with a goldcard inside can cause issues.
Click to expand...
Click to collapse
Thanks again ! you and this forum really helped me. Now i got what i wanted
Thanks
amidabuddha said:
Use this to get the CID
Then this to make the GoldCard
Click to expand...
Click to collapse
I've signed up JUST to say thanks for this post. Bacon saved.
Help!?
Im a bit confussed, im desperately trying to get back to stock ics but can work out how, i have what seems to be a rare cid: TMOB005, my phone is S-ON, can i use this method?
Thanks!
im having this exact problem same phone same ruu flashed
amidabuddha said:
It seems that you used an European unbranded RUU. To fix you have to create a goldcard, use the 1.47.401.4 RUU again to have a booting system, then change the main version and after that flash the TMOB RUU again
Sent from my HTC Desire S
Click to expand...
Click to collapse
im having this exact problem same phone same ruu flashed can you please tell me what is the 1.47.401.4ruu please give me a link where to download it also i tried to make a gold card think i did but i dont know how to use it as on my bootloader it dont say update from zip on sd card anymore also its got s-on. please help
Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.
theconverter said:
Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.
Click to expand...
Click to collapse
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now
rzr86 said:
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now
Click to expand...
Click to collapse
Hi,Yep tried that one still getting signed error.
Thanks for looking
You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **
lot's of problems
Gatosbil said:
You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **
Click to expand...
Click to collapse
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s
theconverter said:
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s
Click to expand...
Click to collapse
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
rzr86 said:
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
extract the recovery.img and flash it via fastboot command
Click to expand...
Click to collapse
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts
theconverter said:
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts
Click to expand...
Click to collapse
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked
rzr86 said:
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked
Click to expand...
Click to collapse
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?
theconverter said:
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?
Click to expand...
Click to collapse
i really don't know mate
rzr86 said:
i really don't know mate
Click to expand...
Click to collapse
Hi, just a update ive fixed my phone, :laugh: done so by making a gold card following the tut's on this fourm installed 4ext via the card booted into recovery cleared dalvik cache ect and now boot's without any loop's.
Looking forward to flashing cyanogenmod and maybe going s-off
Many thanks for all your help and suggestions ill hit the thanks button for you.
Just need to mark as " solved " not sure how ( mod's ? )
I'm not sure where to start. My brother handed me his phone after stupidly following a friend's suggestion that his phone would be faster if he did a factory reset. The phone displays the white screen with the HTC logo, then goes to a black screen and gets stuck there.
I'm able to get to fastboot, but I'm not really sure where to go from there.
The phone's never been tampered with before. S-ON, locked bootloader.
Here's the text I'm seeing on fastboot:
Code:
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012 <- I assume this date is because of the factory reset?
If I understood correctly from what I've been reading, I'm probably gonna need to reflash a stock ROM from fastboot through adb.
I got this HTC_One_X_RUU_5.18.502.1.exe from one of the threads. How do I extract the ROM from there?
I'd appreciate if anyone pointed me in the right way. I'm a Samsung guy and this phone is absolutely alien to me.
EDIT: Here's some more info I got from fastboot:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Here goes Serial#
(bootloader) imei: Here goes IMEI
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3780mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
How did he do the factory reset? Through recovery?
The symptoms you list are identical to what happens when flashing a new Rom without S-OFF.
My understanding is that due to write restrictions it can't copy the boot.img file to boot, which is required begin running the operating system.
I'm not sure if this is the case for factory resets though. So it may depend on how he tried to do the factory reset.
If the above situation is the case, then the fix is to flash the boot.img file of the same stock rom. Alternatively, you could flash a new rom and it's respective boot.img file.
He did that through fastboot. In fact he did the factory reset several times after the phone didn't boot.
I already tried flashing a boot.img from a ROM I found in the development section, but fastboot just says (remote:signature verify fail).
I have absolutely no freaking idea where to get that specific stock ROM. (It's 3.18.502.6, right?)
I added some extra info in the OP in case its useful.
EDIT: I downloaded the 3.18.502.6 OTA update, extracted the boot.img and the phone keeps spitting (remote:signature verify fail)
Since he flashed through recovery it may have screwed up because the bootloader is still locked (this may be the reason why you're getting errors too).
Unlocking the bootloader is what allows you to write to internal memory and is required to flash a rom.
I unlocked my bootloader using this nifty tool:
http://forum.xda-developers.com/showthread.php?t=2470972
This should then allow you to flash the boot.img file with the command
Code:
fastboot flash boot boot.img
I don't think flashing a boot.img is going to help. You're gonna need to run an RUU, either of these should be fine:
http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Transmitted via Bacon
Hey timmaaa, thanks for the help.
This phone is insufferable. Now I'm getting this:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip rom_02.zip
sending 'zip' (798796 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
I actually managed to flash rom_01.zip and now I'm able to boot into recovery.
When I'm on recovery the log says:
Code:
Can not mount SD Card (No such file or directory)
What would you suggest I do next?
Why are you doing that though? That's not how you use an RUU, you're not meant to extract anything, it's an executable file so all you do is connect your phone in bootloader mode and run the program. Plus, who knows what's been done to the device at this point with all the mucking around that's happened with it, flashing just the ROM component won't achieve the desired result. You need to run the RUU as intended so it can update all aspects of the phone and bring everything back into line. There's a pretty good guide to using an RUU here:
Running a Rom Update Utility (RUU) on the HTC One XL Evita
Follow that guide exactly and your phone will hopefully be revived.
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Mighty_Rearranger said:
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Click to expand...
Click to collapse
All good, is the phone booting now?
Transmitted via Bacon
Yup, it booted up alright. I think I'm gonna see how to install a custom recovery so I can fix it easier if he screws the phone up again.
Cool, I have detailed instructions for this device here:
http://forum.xda-developers.com/showthread.php?t=2593382
Hello.
I have been fighting very long time with this, I was digging through this forum and rest of the Internet for possible solutions and I'm stuck.
I am using Linux Mint 17.2.
I have HTC One S - probably s4 version - which does not boot into any system or recovery.
I am able to get to this point where I can see this menu:
- fastboot
- recovery
- factory reset
- clear storage
- simlock
- image crc
- show barcode
At the top of the screen I see the following info:
*** UNLOCKED ***
VLR PVT SHIP s-OFF RL
CID-11111111
HBOOT-2.15.0000
RADIO-1.35a.32.45.27
OpenDSP-v33.1.0.45.1128
eMMC-boot
Dec 14 2012, 17:10:57:7799
Every time I was trying to flash something new, I did the "factory reset" and "clear storage", so probably now there is no OS nor recovery (if I am wrong please explain, I want to know why I can't succeed).
I think I have the S4 version of the phone (ville). Anyway, I tried to flash recovery for S3 version as well.
After typing "sudo fastboot devices" in console I can see:
FA37KW401167 fastboot
The command "adb devices" does not bring any results.
I was trying to flash recovery with the command "sudo fastboot flash recovery <recovery.img>"
I have no idea what I am doing wrong. It seems I have unlocked bootloader, security turned off, even I have changed CID. Since I am on Linux and I can see fastboot device, it is not a driver issue (right?)
I can also give you the result of "sudo fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.35a.32.45.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA37KW401167
(bootloader) imei: 359901043437330
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4******
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
The only thing which worries me is empty version-main, but I have no idea why and how to fix it.
If you have any clue, please help me. I hope I have not made any lame thing, I was trying to carefully read everything I have found on the Internet and I have no other idea except asking here.
mormegil6
In fastboot mode, you can't see the device with adb, this is normal. From your getvar all, I understand that you have an S4/ville. Your radio version is not a recommended one but it should not be a problem.
When you say that you tried to flash recoveries, which ones did you actually use? From my tests, you should try the modified one from there: http://android.cmphys.com/twrp-ville/
2.8.6.5 is the best one and have a nice button in Wipe: Format Data. It can save wrong fstabs, symlinks and things like that.
Anyway, you should try an RUU to restore your system as new. As your CID is 1111111, you can put the generic european one (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe on androidruu.com). As you're using Linux, the RUU .exe won't work, even in Wine. If you can't access a Windows computer, I can provide you a way that works well under any Linux.
I think I understand why I am not seeing anything in ADB - to see something there, I would need to have "USB debugging" option set in Android. And since there is no Android..
I tried with the following recoveries:
r2-modaco-recovery-clockwork-touch-ville
twrp-2.1.6-ville
recovery-clockwork-touch-5.8.3.1-ville
recovery-clockwork-touch-6.0.4.8-ville
recovery-clockwork-6.0.4.8-ville
twrp-2.8.7.0-ville
twrp-2.6.3.0-villec2
I have been rooting phones and flashing different OS previously (Galaxy Ace GT-S5830, Xperia Go ST27i), but I have never met "RUU". I saw some posts connected with HTC One S, but since I was not sure what it is, I was not trying to do anything there. This is sort of "stock-ROM-and-recovery-set"?
I have access to Windows 8.1, but I was using Linux to avoid driver issues. I will switch now to Windows and I will try the options you suggested. (as a Linux fan, I would also like to know how to manage this RUU on Linux, the more I can do on Linux the better )
An RUU is a program that will put your phone in a restore mode and push a big zip with almost every partitions. This is a big exe with a nice GUI, adb, fastboot and a ZIP.
From Linux it's running those commands :
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip <archive.zip>
fastboot reboot
Search XDA and you'll find better documentation.
Envoyé de mon HTC One S en utilisant Tapatalk
Thanks a lot for your help!
The recovery you recommended did not work, but the RUU did. I was not sure if I would know which zip file to use from my Linux, so I used the EXE on my Windows 8.1. Obviously I had driver issues - this fix solved them: http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
So now I have my HTC One S working like a charm. I am not sure what this RUU did - is the phone locked again? Or the security and CID were changed? I would like to install CyanogenMod there, and I hope I will not have any issues again.
Thousands of thanks once again!
No your phone is not locked and no the CID was unchanged. You should install a recovery (TWRP) and you can install CyanogenMod. Don't forget the Google Apps zip.