Hi,
My phone originally had S-OFF and root access. It is now S-On only and HBOOT is at 1.23 (long story)
I am unable to get into recovery and when I try to flash another RUU it fails. If I extract the ROM.zip from the RUU and rename it as PGA158IMG.zip it fails as "HBOOT version is too old" I've tried several different RUUs, none of them work. My attempts to just flash earlier HBOOT firmware have also failed.
When I am in HBOOT I get ***LOCKED*** and ***Security Warning *** displaying at the top of the screen
Is there another method I could try? Does anyone know of an RUU that could/should work? So far I've tried the Telstra RUU (for my phone) as well as the Europe_1.50.401 RUU
Edit: I should also mention that I can't ADB into recovery.
Haha! I fixed it!
fired a command prompt cd into platform-tools
adb reboot-bootloader and then ran an RUU from there. Hopefully this helps someone in the future.
Pack it up lads, we're done here for today.
Edit: Actually no, the update still fails.
Did you change your CID to SuperID 11111111 before? It doesn`t sound to me like that.
Otherwise there is no way back for now.
Perhaps somebody else with more knowledge has another idea
Dr. Locker said:
Did you change your CID to SuperID 11111111 before? It doesn`t sound to me like that.
Otherwise there is no way back for now.
Perhaps somebody else with more knowledge has another idea
Click to expand...
Click to collapse
I have super-CID
But when you are really S-On then you are unable to flash anything.
And with the hboot 1.23 it is till now impossible to unlock.
Dr. Locker said:
But when you are really S-On then you are unable to flash anything.
And with the hboot 1.23 it is till now impossible to unlock.
Click to expand...
Click to collapse
Ahhh well. With a bit of luck ICS will be on HBOOT 1.24 and I'll be able to update. Live and learn.
FriedPie said:
Hi,
My phone originally had S-OFF and root access. It is now S-On only and HBOOT is at 1.23 (long story)
I am unable to get into recovery and when I try to flash another RUU it fails. If I extract the ROM.zip from the RUU and rename it as PGA158IMG.zip it fails as "HBOOT version is too old" I've tried several different RUUs, none of them work. My attempts to just flash earlier HBOOT firmware have also failed.
When I am in HBOOT I get ***LOCKED*** and ***Security Warning *** displaying at the top of the screen
Is there another method I could try? Does anyone know of an RUU that could/should work? So far I've tried the Telstra RUU (for my phone) as well as the Europe_1.50.401 RUU
Edit: I should also mention that I can't ADB into recovery.
Click to expand...
Click to collapse
You need to do the procedure called XTC..
Google it.. its quiet Expensive..
I gave it to Service Centre..
Problem was solved for me./
abhishek.magaji said:
You need to do the procedure called XTC..
Google it.. its quiet Expensive..
I gave it to Service Centre..
Problem was solved for me./
Click to expand...
Click to collapse
Looks like XTC only works up to 1.18 right now. It's a shame.
I'm having the same issue but I can boot my phone, and boot into recovery and flash rooms. But RUU won't flash.. I have HBOOT 1.20
Do official HTC unlock and go from there.
Tinky1 I did that myself and yes it unlocked the bootloader, but it's still S-on with 1.20 HBOOT and won't take the official RUU roms.
HTC unlock doesn't appear to work for me.
Try superCID and report back.
frankd14321 said:
Tinky1 I did that myself and yes it unlocked the bootloader, but it's still S-on with 1.20 HBOOT and won't take the official RUU roms.
Click to expand...
Click to collapse
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
Tinky1 I went to go to Super CID like your said but in bold red letters at the top of the page it says you must be S-OFF which I am not. I only have an Unlocked bootloader but it's still S-ON
Give it a go anyway. I'm not sure what exactly is unlocked by HTC.
Sent from my HTC Sensation Z710e using XDA App
you should still be able to fasboot supercid,
the only things you can dont with htc dev unlock is advance commands like fastboot flash
going to try now
---------- Post added at 11:58 PM ---------- Previous post was at 11:16 PM ----------
Not workng guys...
Using this:
http://forum.xda-developers.com/showthread.php?t=1192300
Step 4
I enter fastboot oem writecid 11111111
And it says error on fat, cannot find Smart_IO.CRD
I tried this:
http://forum.xda-developers.com/showthread.php?t=1192630
But when I enter dd if=/mnt/sdcard/mmcblk0p16 of=/dev/block/mmcblk0p16
It says it doesn't know what dd is.... This is while I am connected to adb but am I missing something there?
http://forum.xda-developers.com/showthread.php?t=1459369
give this a try
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
frankd14321 said:
going to try now
---------- Post added at 11:58 PM ---------- Previous post was at 11:16 PM ----------
Not workng guys...
Using this:
http://forum.xda-developers.com/showthread.php?t=1192300
Step 4
I enter fastboot oem writecid 11111111
And it says error on fat, cannot find Smart_IO.CRD
?
Click to expand...
Click to collapse
stupid question to ask but are you in fastboot on phone when you do that?
Not a stupid question..... yes I am in fastboot when I try.
---------- Post added at 12:54 AM ---------- Previous post was at 12:35 AM ----------
I tried that Auto Super CID Script and it just says waiting for device.. I did what he said to do, and I have everything required..
---------- Post added at 12:56 AM ---------- Previous post was at 12:54 AM ----------
Ah, I put it into fastboot and the script worked but nope, same error as before when i did it manually.
I'm afraid I am probably stuck until the official RUU comes out for ICS someday..
Unless anyone else has any ideas I can try
Related
So, I used to be an Android expert and knew what was wrong just by the symptoms of the problem, having had an iPhone for about 4 months has changed all that. I'm still familiar with some of the stuff, fast boot, installing a recovery, mostly basic things, so I come here to the community I uses to help in.
Here's my issue: Viper ROM was installed, and I wanted to try out Rebel ROM. Downloaded it, but wouldn't connect to my computer through the ROM, so I booted to recovery to mount the internal storage.
It wouldn't flash, stating an error, tried CleanROM, same error. Now there's no OS on the phone, so I decided to RUU so I'd have something too work with.
Its on 2.20 so I downloaded that one, and program ran fine till it told me there was an error and so I can't even have a stock ROM.
TL;DR It can boot to recovery, fast boot, but can't flash a ROM or RUU. Any ideas? Thanks guys for your replies.
Sent from my Nexus 7 using Tapatalk 2
Did you try extracting the boot.IMG from the ROM, fastboot flash boot.img. if your on 1.14 Hboot you'll need to do this.
Sent from my HOX w/CM10.1 4.2.2 s-off
The error is because you didn't lock your bootloader before running the ruu fastboot oem lock
subarudroid said:
Did you try extracting the boot.IMG from the ROM, fastboot flash boot.img. if your on 1.14 Hboot you'll need to do this.
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
I am on hboot 1.14, can I use XsMagicals program? I'd rather use the ADB commands but I've forgotten them.
a box of kittens said:
The error is because you didn't lock your bootloader before running the ruu fastboot oem lock
Click to expand...
Click to collapse
Oh, thank you sir! I'll look up how to do that.
There's no way to downgrade the hboot, is there?
Flashing boot imgs can only be done through fastboot without s off(which I highly recommend you do) but tutorial on fastboot coming up!
---------- Post added at 10:48 PM ---------- Previous post was at 10:47 PM ----------
Flashing boot img through fastboot...
download the file in the link which above which will include adb and fastboot....put that on your computer somewhere you can find it.. now take the boot image out of the Rom zip and place it in that folder... Boot your phone into bootloader scroll down and select fastboot and now open a command prompt with in the fastbootbadb folder on your comp and type to command without the quotes "fastboot flash boot boot.img"...now go wipe in recovery and install the Rom it doesn't matter if you keep the boot img in the Rom zip or not
a box of kittens said:
Flashing boot imgs can only be done through fastboot without s off(which I highly recommend you do) but tutorial on fastboot coming up!
Click to expand...
Click to collapse
My device is S-ON, so I should S-OFF it?
And no way to downgrade the hboot? I know you can't RUU down to an earlier version because of this.
http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533 here is the download link
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
theking_13 said:
My device is S-ON, so I should S-OFF it?
And no way to downgrade the hboot? I know you can't RUU down to an earlier version because of this.
Click to expand...
Click to collapse
Yes s off makes things 100 x easier and without s off you can't downgrade hboot through ruu
Thank you sir! With S-OFF, I can RUU back to an earlier version? I tried searching through the dev section, I mostly found ROMs, and a couple mods.
http://forum.xda-developers.com/showthread.php?t=2155071 here is our s off thread very easy after that you can flash the ruu and it will downgrade your hboot... I recokmend you flash to viper than you do s off..but I'll link you to the ruu thread in a sec
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
http://www.androidfiles.org/ruu/?dir=Evita all the ruus... Get the att 1.85 ruu
theking_13 said:
I am on hboot 1.14, can I use XsMagicals program? I'd rather use the ADB commands but I've forgotten them.
Click to expand...
Click to collapse
Yes you can. But I'd go with what kitten says. S-off = happiness with flashing ROMs to your hearts content.
Sent from my HOX w/CM10.1 4.2.2 s-off
I keep sending the boot.img to the HOX via ADB, but when I try to install it in TWRP, I still get that same error. What am I missing here guys?
Turn off the md5 check before u flash the ROM zip
Sent from my HOX w/CM10.1 4.2.2 s-off
subarudroid said:
Turn off the md5 check before u flash the ROM zip
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
In the settings? Nothing is checked, and when I flash the ROM, the option that says "Zip file signature verification" is also unchecked.
Here's the error I get.
Code:
E: error in sdcard/CleanROM JL Beta 1.zip
(Status 1)
Error flashing zip 'sdcard/CleanROM JL Beta 1.zip'
Updating partition details...
[COLOR="Red"]Failed[/COLOR]
Nvm, fixed it! Thanks to both of you, couldn't have done it without your input.
i'm on JB (saturn III) hboot 2.0 with superCID/s-off. i can downgrade to hboot 1.0 but i can not change my CID to flash ICS RUU (error 130 with superCID )
first...when i enter code
Code:
adb shell
(device not found)
what shoud i do ?
and there's a issue with my ussd code, it's chinese... i've tried wipe and flash other roms but it's still there
i think if i could flash ICS RUU then the problem will be solved
sorry if my questions are stupid because i'm a newbie
thanks!
rJiLz said:
My cid is supercid!
Click to expand...
Click to collapse
do you already have superCID or not, your post are becoming confusing.
please post your whole CID#
your whole bootloader#
what you're romver#
we need solid information to further help/guide/assist you.
please help me help you
russellvone said:
do you already have superCID or not, your post are becoming confusing.
please post your whole CID#
your whole bootloader#
what you're romver#
we need solid information to further help/guide/assist you.
please help me help you
Click to expand...
Click to collapse
+1
Lol, just now i wanted to post the same.
rJiLz said:
i'm on JB (saturn III) hboot 2.0 with superCID/s-off. i can downgrade to hboot 1.0 but i can not change my CID to flash ICS RUU (error 130 with superCID )
first...when i enter code
Code:
adb shell
(device not found)
what shoud i do ?
and there's a issue with my ussd code, it's chinese... i've tried wipe and flash other roms but it's still there
i think if i could flash ICS RUU then the problem will be solved
sorry if my questions are stupid because i'm a newbie
thanks!
Click to expand...
Click to collapse
#1 did you facepalm s-off or moonshine s-off?
#2 what is your CID?
#3 what ROM are you currently running?
#4 is adb enabled?
#5 do you have YOUR phone's stock boot.img and recovery.img available for flashing when needed?
#6 what/which RUU file are you attempting to use?
#7 is your bootloader still unlocked, or is it relocked?
---------- Post added at 02:25 AM ---------- Previous post was at 02:21 AM ----------
@rJiLz
did you log off?
It's magic, but there are no problems with ussd in CM alfa room.
Flshing stock room will slove the problem too.....
I said :
I'm on JB ( saturn III) , S-OFF, UNLOCKED, MY CID: 11111111,MY HBOOT:1.0... ICS RUU K2_UL
Please help me
russellvone said:
#1 did you facepalm s-off or moonshine s-off?
#2 what is your CID?
#3 what ROM are you currently running?
#4 is adb enabled?
#5 do you have YOUR phone's stock boot.img and recovery.img available for flashing when needed?
#6 what/which RUU file are you attempting to use?
#7 is your bootloader still unlocked, or is it relocked?
---------- Post added at 02:25 AM ---------- Previous post was at 02:21 AM ----------
@rJiLz
did you log off?
Click to expand...
Click to collapse
Sorry for my bad English.
1. FACEPALM S-OFF
2. SUPERCID
3. SATURN III
4. ADB - ENABLED
5. YES, I DO
6. ICS RUU FOR K2_UL
7. UNLOCKED
rJiLz said:
Sorry for my bad English.
1. FACEPALM S-OFF
2. SUPERCID
3. SATURN III
4. ADB - ENABLED
5. YES, I DO
6. ICS RUU FOR K2_UL
7. UNLOCKED
Click to expand...
Click to collapse
You say, adb - enabled.
But the message
adb shell (device not found)
seems to say something else.
Also i said, you should try the ruu with relocked bootloader.
old.splatterhand said:
You say, adb - enabled.
But the message
adb shell (device not found)
seems to say something else.
Also i said, you should try the ruu with relocked bootloader.
Click to expand...
Click to collapse
Relocked bootloader to flash ruu but error 130 with supercid
Adb works well when i relock and unlock but enter "adb shell" - device not found
ok, so you've already accomplished superCID.
and you are wanting to change your CID back to stock CID because the ICS RUU you are trying you use gives error.
but....when bootloader is unlocked you cannot use adb shell?----(no device found)
but when your bootloader is relocked you can use adb?
so just keep your bootloader locked and run the adb shell as root
adb shell
su
? Maybe this will work?
---------- Post added at 01:48 PM ---------- Previous post was at 01:45 PM ----------
rJiLz said:
Relocked bootloader to flash ruu but error 130 with supercid
Adb works well when i relock and unlock but enter "adb shell" - device not found
Click to expand...
Click to collapse
fastboot is used to lock and unlock
?
russellvone said:
ok, so you've already accomplished superCID.
and you are wanting to change your CID back to stock CID because the ICS RUU you are trying you use gives error.
but....when bootloader is unlocked you cannot use adb shell?----(no device found)
but when your bootloader is relocked you can use adb?
so just keep your bootloader locked and run the adb shell as root
adb shell
su
? Maybe this will work?
---------- Post added at 01:48 PM ---------- Previous post was at 01:45 PM ----------
fastboot is used to lock and unlock
?
Click to expand...
Click to collapse
when i relock bootloader and enter "adb shell" - still there (device not found)
now i can not change my cid (from supercid to HTC__032) to flash ICS RUU
I'd like to give you some other things to try but I'm afraid that my actual experience vs what I've read are too far apart from each other.
try googling flash RUU with fastboot.
:thumbup:
russellvone said:
I'd like to give you some other things to try but I'm afraid that my actual experience vs what I've read are too far apart from each other.
try googling flash RUU with fastboot.
:thumbup:
Click to expand...
Click to collapse
now i have a real question:
what is the easiest way to change the cid (to flash ICS RUU without error 130) ?
currently: i've got a k2_ul on JB - Hboot 1.0 - unlocked - superCID - S-off
@rJiLz
superCID should not be an issue. I think it's your Hboot.
you keep posting you have Hboot 1.0
what is the rest of your Hboot#
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
http://forum.xda-developers.com/showthread.php?t=2251800
check this thread out
---------- Post added at 10:35 PM ---------- Previous post was at 10:09 PM ----------
I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE
I am trying to help
so.... that thread summed up
#1 relock your bootloader
Code:
fastboot oem lock
plug phone into computer and run RUU
a do NOT continue with the RUU, but look in your %temp% folder/directory for the rom.zip
#2 place the rom.zip into your fastboot directory
#3 verify connectivity with
Code:
fastboot devices
#4 send cmd
Code:
fastboot oem rebootRUU
#4a pause *** Wait readiness HTC * **
#5 send cmd
Code:
fastboot flash zip rom.zip
#5a If you get the message: FAILED (Remote: 90 hboot pre-update! please flush image again immediately) It's okay. In this situation it is necessary to re-issue the command
Code:
fastboot flash zip rom.zip
#6 send cmd
Code:
fastboot reboot
---------- Post added at 10:45 PM ---------- Previous post was at 10:35 PM ----------
and I think your adb issue with no devices found might have something to do with you trying to run the RUU.
it might have disabled adb. you could try right clicking on the fastboot/adb folding and clicking on "RUN AS ADMINISTRATOR"
maybe that will help with changing CID..... even though superCID is universal.......
just a couple more thoughts
My Hboot info:
TAMPERED
UNLOCKED
K2_UL PUT SHIP S-OFF RL
CID-11111111
HBOOT-1.01.0000
RADIO-0.11.40g.00.15
OPENDSP-v62.0221.1112
eMMC-boot
Dec 7 2012,03:10:20-1
now i'm busy...i will try again later
@rJiLz
any luck?
russellvone said:
@rJiLz
any luck?
Click to expand...
Click to collapse
Thank you very very much but i'm far away from home now. I will report later
to be continued.....
lol
:beer:
russellvone said:
to be continued.....
lol
:beer:
Click to expand...
Click to collapse
Code:
fastboot flash zip rom.zip
so sad, checking model id (failed)
so, what condition is your phone at now?
---------- Post added at 10:05 PM ---------- Previous post was at 09:58 PM ----------
http://forum.xda-developers.com/showthread.php?t=1275632
[TROUBLESHOOTING]/!\ Root | S-OFF | Flashing | RUU | Bootloop | Brick | Resources /!\
this guide says to make a goldcard
HI all,
I tried to flashed the RUU but it seems that the version I flashed was lower than the one I had.
Now the screen is just black and I can not use the power + down vol to get to fastboot at all.
it will be greatly appreciated if I can get some guidance to get to the fastboot.
Cheers
What exactly did you flash? What does the phone show up on windows as? Does charge light come on when plugged into wall? Did the ruu complete? s-on or s-off?
You really didn't give much info.
Sent from my iPhone using Tapatalk
apology - duplicate post
bricked
thanks you for the response.
sorry I was not sure what info to give.
I was trying to flash RUU asia HK because I originally from STOCK turge but everytime I have a conversation my phone keep shuting down.
so I did (quoting from the instruction page):
Download HTC One X Stock Recovery
Download correct HTC One X boot.img and RUU based on CID. Download CID Getter from Google Play Store and run it, it will show your CID.
For this case, cidnum is HTC_044. The correct RUU is X.XX.707.X. Make sure you have downloaded the correct RUU.
Extract Fastboot.zip into a new folder, renamed the folder to Fastboot. Recommended to extract the folder to drive.
Copy and paste the downloaded stock recovery img and boot img into Fastboot folder.
Boot HTC One X into fastboot mode by press and hold Volume Down + Power button.
Connect your phone to the computer via USB cable.
At your computer, open up Command Prompt windows. (To OpenCommand Prompt –> Windows Logo–> Type CMD in search box –>Enter)
Type fastboot flash recovery endeavoru_recovery_signed.img , followed by fastboot reboot-bootloader and fastboot erase cache.
Once you flashed the stock recovery, continue to flash boot.img to your phone. Type fastboot flash boot boot.img, followed by fastboot reboot-bootloader and fastboot erase cache.
Now, relock the bootloader by typing fastboot oem lock, followed by fastboot reboot-bootloader and fastboot erase cache.
Your phone will restart after you have relock the bootloader.
Boot into Fastboot mode.
Double click the RUU, follow the updater instruction.
Wait the sending file to your phone, it normally takes 5-6 minutes.
Once the installation/update completes, your phone will automatically reboot.
when I last look at the details My CID is still 11111111 but status "RELOCKED" - it says also "EVITA PVT SHIP S-OFF RL"
HBOOT 2.14.0000
does this mean that I can safely run RUU:
RUU_EVITA_UL_ICS_40_S_hTC_Asia_HK_2.42.708.3_Radio_0.20os.32.09.15_10.113.32.28L_release_286715_signed.7z
If there still more things to do, would you kindly direct me to the correct link to follow.
THank you
Never mind, didn't read properly. Will edit and repost.
Sent from my Evita
---------- Post added at 10:48 PM ---------- Previous post was at 10:44 PM ----------
Your first problem is that you're flashing things that aren't intended for your device. The recovery you flashed is for the Endeavoru, you have the Evita. The second problem is it looks like you're getting your information from the wrong place, to go back to stock you don't need to flash a recovery or a boot.img, all you need to do is flash the right RUU for your device. What RUU did you already run? I need the exact filename. Does your phone power on at all? Can you reach the bootloader?
Sent from my Evita
---------- Post added at 10:51 PM ---------- Previous post was at 10:48 PM ----------
I see you're looking at all kinds of different threads at the moment, that isn't going to help because I don't think you know exactly what you're doing, you don't know what you've done, and you don't know how to recover from it. Your best bet is to stay in this thread and I'll try to help you work out what's gone wrong.
Sent from my Evita
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Radio_5.1204.162.29_release_299865_signed.exe
this is the one I ran earlier.
The progress is that I somehow manage to get to fastboot by pressing the vol down and power .
I am trying to download : RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe at the moment but it seems that the first download did not complete - so I am downloading again,
is this what I need to do? just run the RUU?
Cheers
ardabelati said:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Radio_5.1204.162.29_release_299865_signed.exe
this is the one I ran earlier.
The progress is that I somehow manage to get to fastboot by pressing the vol down and power .
I am trying to download : RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe at the moment but it seems that the first download did not complete - so I am downloading again,
is this what I need to do? just run the RUU?
Cheers
Click to expand...
Click to collapse
U should download one that has the same radio as yrs also it will take fast download speed otherwise it will keep breaking up. t took me 4 attempts before I manage to download it yesterday (same file as one u r trying) good luck cheers!
You got seriously lucky. You ran an RUU intended for the HTC One X (codename Endeavoru), you don't have that phone. You have the HTC One XL / at&t One X (codename Evita), they're completely different phones. Note how the first RUU you ran has Endeavoru in the filename, that's bad, really bad, don't ever flash anything that doesn't have the Evita codename within the filename. If it has Evita in the filename it's for your phone, if it has anything else don't touch it, burn it, run away. Like I said, you're incredibly lucky your phone isn't bricked right now.
I can only assume that you're a bit confused and have been hopping between the two forums for these phones. In future stay within this device forum that you're posting in now, don't ever go anywhere else. You don't even need to visit other websites because, seriously, everything you'll ever need is right here within this device forum. Plus other sites don't properly distinguish between the models which causes confusion.
Anyway. The second RUU that you've listed there is perfectly fine for your phone. I can't guarantee that it's going to work though because previously running the wrong RUU could have really messed things up on your phone. But your only hope is to cross your fingers and run it now. Let me know how it all goes.
Sent from my Evita
---------- Post added 28th November 2013 at 12:12 AM ---------- Previous post was 27th November 2013 at 11:49 PM ----------
ndmuni said:
U should download one that has the same radio as yrs also it will take fast download speed otherwise it will keep breaking up. t took me 4 attempts before I manage to download it yesterday (same file as one u r trying) good luck cheers!
Click to expand...
Click to collapse
What are you talking about? He doesn't need to use an RUU with the same radio/baseband that's currently on his device, that's just wrong. Firstly the idea of an RUU is to update your device, therefore traditionally you'd be updating to a newer radio version than the one that's currently installed. With s-on you can only run an RUU that contains a firmware version that's equal to or greater than your current firmware. This user has s-off though so he can run any RUU that he wants to, including earlier ones (RUU'ing backwards). I don't know where you got the idea that you need to run an RUU with the same radio as your existing radio but it's just plain wrong, and you really shouldn't be telling people that.
Sent from my Evita
ndmuni said:
U should download one that has the same radio as yrs
Click to expand...
Click to collapse
False. With s-on, you can only run RUUs for your CID, and with the same or latter hboot and firmware number. So if you were having trouble flashing an RUU, its probably because you were s-on and trying to either flash another carrier's RUU, or an older version.
The OP is s-off, so therefore all security checks are off. He can flash the RUU for any carrier, any version. As long as its meant for our device (EVITA), of course.
Hi guys
Thank you for all the guidance.
I got the 4.1.1 on my phone now and phone is use-able. I can not thank you guys enough for the help.
After i finished RUU flash the phone detected the new firmware update. When i dowloaded and tried to update, it says that the phone has been modified and they can not run/install the update. When i checked my boot it shows :
"relocked"
cid is still 111111.
Evita pvt ship s-off RL
HBOOT: 2.14
radio : 0.23a.32.09.29
Do i need to do more installation before my phone can get the update from HTC like the one coming out from the factory?
Cheers.
Arda
Sent from my HTC One XL using Tapatalk
You need to change your CID back to the stock CID to take the OTA update.
Sent from my Evita
timmaaa said:
You need to change your CID back to the stock CID to take the OTA update.
Sent from my Evita
Click to expand...
Click to collapse
I searching in the forum about changing CID. But it seems that is all about how to change CID to 111111. Is there any tutorial to revert back to original CID?
Do i need to sort out my s-off first before changing CID?
Thank you in advance.
Regards
Arda
You said in a previous post that you're s-off. So are you s-off or s-on? Please boot into bootloader and post your bootloader details again.
Sent from my Evita
Hi Timmaa
I believe I am S-OFF - when I look at the bootloader screen it said S-OFF.
Do I need to flash anything at all to get my CID back to original?
On that note I was looking at the RedPoint73 resource guide page but I am not able to find the tutorial to make the CID back to original.
Any info is greatly appreciated.
Cheers
All you need to do is issue a fastboot command:
Code:
fastboot oem writecid xxxxxxxx
The x's represent the new CID.
Sent from my Evita
Hi Timmaa
I believe I am S-OFF - when I look at the bootloader screen it said S-OFF.
Do I need to flash anything at all to get my CID back to original?
On that note I was looking at the RedPoint73 resource guide page but I am not able to find the tutorial to make the CID back to original.
Any info is greatly appreciated. I have attached the screen shot
Cheers
I did :
fastboot oem writecid 622 but it came back with ....INFOfail: [writecid] invalid CID
I flashed the RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe
was the 622 number incorrect?
cheers
No, 622 isn't a CID. A correct CID consists of eight characters, that's why I put eight x's in my example. What model is your phone? You need find the right CID for your model and change it to that. You need to be more careful, you're attempting things without knowing what you're doing again, you're in serious danger of damaging your phone.
Sent from my Evita
timmaaa said:
No, 622 isn't a CID. A correct CID consists of eight characters, that's why I put eight x's in my example. What model is your phone? You need find the right CID for your model and change it to that. You need to be more careful, you're attempting things without knowing what you're doing again, you're in serious danger of damaging your phone.
Sent from my Evita
Click to expand...
Click to collapse
Hi Timmaa
My phone is HTC ONE XLTE
I use CID Getter and it came up with HTC__622, so I entered that into the fastboot command and it changed my CID but when I try to flash the new update downloaded directly through the phone it came up with the messsage below after verifying the phone.
not sure why.....( pls see attached)
So you ran the RUU.exe? You didn't extract it or anything? What have you done to the phone since then?
Sent from my Evita
Hey guys,
My phone died from the dreaded "qhsusb_dload" issue, and since I cannot afford the replacement phone I really want, I bought another AT&T One X.
I had my previous one since March of last year and I have gotten everything done with no issues, including S-OFF, upgrading Firmware to 3.17 to use JB 4.2.2 and trying various Radios and Kernels, so I do have experience.
With this phone, completely stock, I unlocked the Bootloader, and at the top it shows TAMPERED and UNLOCKED. I now have two issues:
1. I cannot get into the Recovery. I flashed it manually from "Fastboot USB", as well as with EZ Toolkit Advanced (Evita) and WinDroidXL Tookit and it showed it was successful with each method, yet when I try to access it, I get the boot screen with the HTC logo for about 3 seconds then it just powers off completely.
I researched and tried TWRP 2.6 as well as CWM from WinDoidXL toolkit. I have also ran the "fastboot erase cache" command after installing the Recovery yet I still have the problem. I installed gapps to accomplish the same thing but I don't wanna use it just yet.
I am asking for help as I am afraid of bricking this phone as well. When it powers off after failing to access the Recovery, it stays off for a while, and Device Manager even shows "qhsusb_dload" I have to hold the power button for a long time (and multiple times in some instances) before it powers on and boots into the OS.
Please help me get this working as I am afraid to try it again with the fear of having it bricked.
I do not have root access (I need recovery to flash t he Super User zip file first, correct?) and my HBoot is 2.14 (can't remember what it was on my last phone). Do any of those play a part in the problem i'm having?
Thanks so much in advance
Does the phone boot up into the OS? What are your bootloader details?
Sent from my Evita
Hello again, timmaaa.
timmaaa said:
Does the phone boot up into the OS? What are your bootloader details?
Click to expand...
Click to collapse
badbwoydes said:
When it powers off after failing to access the Recovery, it stays off for a while, and Device Manager even shows "qhsusb_dload" I have to hold the power button for a long time (and multiple times in some instances) before it powers on and boots into the OS.
Click to expand...
Click to collapse
My phone works fine with stock ATT 4.1.1 that it came with, it's just the Recovery that won't launch, even though it appears to install fine when I flash it with fastboot.
My Bootloader shows:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14-1
Thanks
Are you checking the md5 after downloading the recovery?
Sent from my Evita
timmaaa said:
Are you checking the md5 after downloading the recovery?
Sent from my Evita
Click to expand...
Click to collapse
No, but I have tried 2 different versions from here, the one I had on my previous Evita, and I have also used the ones embedded in the WinDroidXL and EZToolkit Advanced (Evita).
I've seen others saying their phone ends up booting normally after selecting Recovery from the Bootloader but mine just powers off when I select it and I can't find a previous thread with this issue.
It's possible your partitions are a bit funky. Running the 3.18 RUU might help.
Sent from my Evita
---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------
We need to check your CID first.
Sent from my Evita
timmaaa said:
It's possible your partitions are a bit funky. Running the 3.18 RUU might help.
Sent from my Evita
---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------
We need to check your CID first.
Sent from my Evita
Click to expand...
Click to collapse
Would this be what you're referring to? http://forum.xda-developers.com/showthread.php?t=2390405
And if so, I can try S-OFF even though I don't have root access?
My CID is all 1's
My HBOOT wouldn't cause this prob?
You can disregard all that. I ran the install for TWRP 2.6.3.0 from the EZToolkit Advanced (Evita) then cleared the cache with the automated option in the same Toolkit, which I have tried like 10 times a few hours ago and now it's working... I swear all I did differently was leave the phone idle and plugged in for a while.
I'd still like to get the S-OFF done at this time. When I run "fastboot getvar cid" it returns "cid: 11111111" which means I have SuperCID and I can go through with S-OFF?
Finally, I cannot find a S-OFF guide for HBOOT 2.14 and ATT Firmware 3.18. This is for my HBOOT but not my Firmware http://forum.xda-developers.com/showthread.php?p=42631876
I found this http://forum.xda-developers.com/showthread.php?t=2485865 which states it's for 3.18 Firmware but shows nothing for my HBOOT.
I also found this http://forum.xda-developers.com/showthread.php?t=2540232
S-off isn't specific to firmware, it works on all. Anyway, try Facepalm s-off.
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my Evita
timmaaa said:
S-off isn't specific to firmware, it works on all. Anyway, try Facepalm s-off.
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my Evita
Click to expand...
Click to collapse
You have no idea how terrified I am right now, modding a phone that is basically the same as the one that got bricked a few days ago.
Thank you for your assistance. I will indeed go with Facepalm as that's the one I used in the past
I'm trying to update a phone I haven't used for a while with a newer ROM, but I'm not able to get in to recovery to do it. It's already rooted with an old ViperOne ROM on and I thought it already had CWM on., but Flashify is telling me it has the stock recovery. I've tried installing CWM and TWRP via Flashify and Fastboot and they've completed without any errors, but I'm never able to get in to it and it boots as normal. I can't even get in to the stock recovery that's supposedly there.
Does anyone have any idea what the problem might be?
Thanks.
Well try this.
Download Rom Manager
It wil flash the CWM by itself and then reboot into the Recovery. Notice what happens.
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
If Helped Click Thanks...
I've tried that too, still just reboots as normal.
Then it might be a Dead Recovery. Well which device are you using. And maybe Flashing your Device back to stock which would flash back the stock recovery.
Hope This Works ..!
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
Tell me wgich device are you using.
HTC One S S4 running Android 4.0.4 ICS
mrkwtrs said:
HTC One S S4 running Android 4.0.4 ICS
Click to expand...
Click to collapse
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all
LS.xD said:
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all
Click to expand...
Click to collapse
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?
mrkwtrs said:
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?
Click to expand...
Click to collapse
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before
LS.xD said:
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before
Click to expand...
Click to collapse
Just seen an O2 UK RUU further down the list so I'll try that.
mrkwtrs said:
Just seen an O2 UK RUU further down the list so I'll try that.
Click to expand...
Click to collapse
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.
LS.xD said:
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.
Click to expand...
Click to collapse
Think I'm all sorted. Thanks for your help! :good: