hi guys, im not new to this, and i have a good understanding of adb and fastboot. i have just purchased a htc one xl (telstra) im running Hboot 2.15 and have unlocked bootloader via htc dev, installed TWRP ver; 2.6.0.0, rooted via flashing superSU and am currently running stock android ver 4.2.2 htc sense 5.0. i sim unlocked it so i could run my vodafone sim, and radio is working fine but i think the telstra RUU isnt allowing the sims internet conectis-on, therefore i am deciding to flash another rom. i first tried flashing pacman rom unsuccessfully but have yet to flash the boot.img as i havent got S-OFF and figure it wont allow writing to that partition yet, i have had alot of problems rewriting the CID for superCID, have tried many methods including xfactor and manually via fastboot and have been unsucessfull thus far, i understand that its not possible to downgrade Hboot unless S-off is achieved, alas facepalm is not possible unless superCID is achieved, and i cannot rewrite the CID manually or using any scripts i have found, is my Hboot version the problem or is there something im missing here?
help would be much appreciated
Have you tried the hex edit method?
Sent from my Evita
Yeah it returns with an error in adb, system mounted read only, and its deffinatly rooted so I'm not sure how to make system readwrite
Sent from my Wildfire S A510e using xda app-developers app
It would seem there s no sure fire way around this. Unless someone can help me figure out the read only issue in adb using the hex edit method
Sent from my Wildfire S A510e using xda app-developers app
hex edit progress
ok so i fixed the problem by uninstalling htcsync and re installing adb and fastboot via sdk tools, i got the file pulled from my phone and hex edited it, from cid; TELST001 to cid; 11111111 and pushed the file back onto my phone as per instructions, yet when i reboot into bootloader and do fastboot oem readcid it still comes back TELST001. somehow the phone knows what is happening and is changing the hex back to original form..??
ok scratch that, it actually never pulled the file from my phone, that was a file leftover from some script that didnt work, it had a cid of telus001 and my cid reads telst001 so i know that wasnt my file, the adb shell is able to read my phone but not ble to take the mmcblk0p4 file, so when i enter the command dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4 i get 2.0 records in 2.0 records out 1024 bytes transferred at <40960> bytes. so im guessing it was successful, yet when i check my sd root the file is nowhere to be seen!? where am i going wrong here
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
argh
O..K so i rebooted the one xl ad the file was there, i copied to desktop, hex edited, and did dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4 to push the file back. read as successful in adb, so i did reboot fastboot and fastboot oem readcid, CID READS TELST001 STILL i must be retarded or something
timmaaa said:
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
Click to expand...
Click to collapse
ok thanks man, ill give it a go now
st3wy said:
ok thanks man, ill give it a go now
Click to expand...
Click to collapse
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
st3wy said:
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
Click to expand...
Click to collapse
i even tried doing echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
and still get INFOcid: TELST001
is it possible that my cid is stored somewhere other than mmcblk0p4 or mmcblk0p5??
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
timmaaa said:
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
Click to expand...
Click to collapse
sounds about right, i did read about this. so im guessing because i used temp root to spoof cid and unlock bootloader using the unlock code from that process, that there is no way to 'officially' relock the bootloader, and start the whole process again using a different method, say for instance using adb.. and thus getting bootlocker unlocked without spoofed cid and temp root possibly resulting in the ability to obtain supercid and full root? i have got supersu flashed through recovery.. but yeah obviously having serious issues with supercid atm.. thanks so much for your help this far man came a long way this arvo, just cant see the light at the ed of the tunnel... its like if i was able to flash Hboot i may be able to get around, but that requires s-off, which reuires super cid, which requires different Hboot lol
you wouldnt happen to know anyone else that might be able to brainstorm on this would you? although from looking at the threads youve made, it seems your possibly THE most educated person on this matter... idk might just have to wait for a dev to look into this and find a loophole. im not that good unfortunately. again, thanks for your help man. if you do get any ideas dont hesitate to post em up on this thread. cheers.
I'm definitely not the most educated person in this kinda stuff, I just read a lot on here and remember the ins and outs of this device. Finding a loophole around this is something that the HTC experts would have to work on, people like beaups, jcase, those kinda guys. Like I said though I'm not even sure if what I said is what's stopping you, I could be completely wrong.
Sent from my Evita
well, ive had one thaught that might be a stupid one but possibly one of the only things i am yet to try.. if i go through with the s-off and see if it works, although my phone is reading cid it may actually have supercid because like i say, its been successful in adb just hasnt returned a supercid through the fastboot commands, i guess the only question is will i brick my device if i follow through with s-off when i dont have supercid or will it just fail and all will be gravy
is there anyway to get them in on this thread so they know where im up to, or would i have to PM them exclusively and explain all over again
btw i think your right, system is read only. thats why the pushes arent working, even though they say they are in adb, either that or the phones cid and the RUU's cid are different and fastboot oem readcid is reading softwares cid and not the phones cid?
either way im going to drink a beer and go outside for a while, thanks again timmaaa, i didnt expect anyone to reply to this thread for a good while. like i said if u happen to have contact with the devs or anyone else that might be able to help, id be stoked. cheers bro and peace out!
You can try SuperCID but it just won't work. You can try contacting them and pointing them to this thread, but I think they're pretty busy guys so I don't know if they'll be able to help. The CID that shows up when using the fastboot command is definitely the phone CID and not the software CID.
Sent from my Evita
Related
HI everyone. i have started this thread as i didnt know what to do when i first had to send my wildfire back for repairs. first download the attatched zip. unzip to desktop and make sure u have got the drivers for your bootloader interface already installed. to do this you will need just two things. the zip you have just downloaded and the HBOOT which i included inside the ziped file. once extracted run the java file named S-ON.jar and plug your phone in and turn on fastboot. once connected make sure you click on check connection. once you have done that you should see your serial number appear. okay your ready to go. look for the first tab and click on it. then click on HBOOT/SPL. locate the HBOOT file you inzipped with the S-ON tool and then click it. once done just click on flash HBOOT/SPL. once done you will see it says FLASH HBOOT/SPL/SUCCESS. thanks for takuing time to look at my GUIDE and i hope it helps you. just remember one thing only flash the new HBOOT after you have installed the RUU which is android 2.1 update 1 so you can root again.
thanks for posting this, gonna try it now since I have to send my wildfire in for repair..
no problem if you have any trouble let me know and ill help you gain s-on
Hmm well it didn't work, so just sent it in as it was. I replaced the custom recovery and the custom rom with stock from an RUU, I hope thats enough.
To gain S-ON I also tried the suggestions from a few other posts, I guess the problem is that I didn't gain S-OFF by software but by using an XTC-Clip. The fastboot command to flash the hboot always returned something like remotly denied or simular
kaefert said:
Hmm well it didn't work, so just sent it in as it was. I replaced the custom recovery and the custom rom with stock from an RUU, I hope thats enough.
To gain S-ON I also tried the suggestions from a few other posts, I guess the problem is that I didn't gain S-OFF by software but by using an XTC-Clip. The fastboot command to flash the hboot always returned something like remotly denied or simular
Click to expand...
Click to collapse
this will not work with xtc clip i have 1 other way tho. please try this.
go into you start menu click RUN the type cmd in the dialog box. when you have the cmd up type C:\fastboot>fastboot oem mb 9C068490 1 30 then it will say okay. then open the s-on tool then try to flash the HBOOT. let me know if you have anymore problems. but this way shud work for you
they will not accept it as they just have to go into the HBOOT menu and they will be able to see it is s-off. and they will send it back as it is and wont carrie out any sort of repairs on it as you have hacked the phone and comprimised the security software
hmm, well we will see. I will post as soon as I get an response. That command "fastboot oem mb 9C068490 1 30" always threw an error and somewhere I read that maximum 3 parameters are allowed
kaefert said:
hmm, well we will see. I will post as soon as I get an response. That command "fastboot oem mb 9C068490 1 30" always threw an error and somewhere I read that maximum 3 parameters are allowed
Click to expand...
Click to collapse
okay no worries. if they wont repair it. then get back to me and ill cook somthing up and get you back to s-on. this is the trouble when gaining s-off with a xtc clip. its a pain to get back to s-on again lol but good luck anyways
Thanks for the moral support, I hope they will repair it...
Well back then I had no chance, my Wildfire was delivered to me with hboot 1.01.001 back in the time where there was no software S-OFF method for 1.01.001 and up, so I found myself a shop that had an XTC-Clip and invested 10€ on him
Okey! So they repaired it although it had S-OFF done by XTC-Clip. Got it back yesterday, and the phone earpeace is working again
kaefert said:
Okey! So they repaired it although it had S-OFF done by XTC-Clip. Got it back yesterday, and the phone earpeace is working again
Click to expand...
Click to collapse
Great news for you mate im glad they sorted it out for you. and your very lucky as they sent mine back twice for being s-off lol.
lol, where are you from? and where did they send your device? Im from austria and they sent my device to slovakia and they gave me a slovenian report of what they did so I had to use google translate to understand it
so i unlocked my device via HTCDev.com thinking since its htc device and all they said was i had to unlock bootloader to flash custon OS's i already knew about S-OFF but being the site didn't talk about it(why would it) i went and flash virtouous ROM and got stuck at the HTC screen. i wasnt thinking so i never backed up the stock HTC Rom!!
now i tried 2 of those RUU's in the shipped rom thread the tmous ones with 29 and 50 both saying wrong version.
my question here is there anyway to get at least one RUU to work or get s-off from HBOOT?
my reason of doing this after going back to completely stock is i cant wait any longer for HTC/Tmobile to get us ICS so i tried the custom way and failed lol
I am sure unless you super SID you will have to find ROMs specific for the country the phone came from.
Eg my phone was from Asia region and I could not flash Euro ROMs
ok from the Shipped rom thread in the dev section for the sensation i was trying to go back to stock to gain s-off but the tmous(USA) which is where i am from said wrong version.
futty said:
ok from the Shipped rom thread in the dev section for the sensation i was trying to go back to stock to gain s-off but the tmous(USA) which is where i am from said wrong version.
Click to expand...
Click to collapse
What h boot version do you have?
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Hboot: 1.18.0000
Check your CID using fastboot getvar cid to see if these still match the ROM you were trying to flash.
says for cid is t-mob010
i guess out of the 2 stock ruu"s from the post doesnt match that?
edit: ok from what i learned in another post i opened up the rom.zip file and looked at android-info.txt both the cid and mid matched my phones from the RUU file "RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed" buuuuttttt it tried to update it but fails saying i need to correct version :\
futty said:
Hboot: 1.18.0000
Click to expand...
Click to collapse
Are you on t mous us?
Also you can s off and super cid and flash any ruu.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Yes i am. the 2 Ruu's i am using seem to have matching info to my phone when i went to get the rom.zip it uses to send to my phone and looked in the android-info.txt but tell me to get the correct RUU and try again. i got the from here:http://forum.xda-developers.com/showthread.php?t=1074559 under the tmous RUU one with 29 and the other 50.
so i am just stuck at the white screen with the word HTC. if i could get s-off and SuperCID through fastboot that would be awesome but googling it shows up that i cant s-off via fastboot ughhh
still no luck cant seem to flash anything without s-off or supercid
so looks like i am jumping the boat going to sprint this thursday and geting the iphone 4s...byebye android
If you can get into fastboot you should be able to flash RUU from there. Just download the RUU.exe and run it as administrator. Follow the prompts in the exe program while your phone is in fastboot mode.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
futty said:
still no luck cant seem to flash anything without s-off or supercid
so looks like i am jumping the boat going to sprint this thursday and geting the iphone 4s...byebye android
Click to expand...
Click to collapse
Maybe iCrap is better for you. When you use Android phones and want to complete unlock them for flashing customroms aso you shoud realy learn to read before you do something. I hate it when people are not able to read about the stuff they want to do and when something goes wrong they blaim Android for it.
To get s-off, super CID and root on a HTC Android device is realy easy if you read the how-to threads and normaly takes about 15 minutes.
Have fun with your iCrap 4S and please don't try to jailbreak it before you read some stuff.
Sent from my Revolver powered ICS Asus Transformer TF101
first off let me say i have rooted and flashed roms on my sensation before just fine. i was unlocking via htcdev.com and figured their method didnt require s-off since it didnt say anything about it. it just talked about unlocking it to put customs os's on it. 2nd i always had a love hate thing for IOS since i had the 3G and ipod touch.
far as using the RUU'ss it tells me i need the correct Ruu version or something like that. maybe because i didnt run as admin but i have all that stuff turned off due to the theme i used for windows 7 required it off.
If I were you I would Super CID your device. That is what I had to do. A great guide that I used was http://forum.xda-developers.com/showthread.php?t=1472298
i tried and i get this error
vreg_set: request is duplicated id 14
pyramid_init_sd, SD card power on ok
sdcc_init_memory_device done
[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
[JAVACARD_ERR] SMART_IO.CRD cann't find
Click to expand...
Click to collapse
and my cid remains the same as t-mb010
how can i fix it? would love to get mt device back up and running
You can recover this. Firstly read this guide, regarding downgrading hboot and getting s-off.
http://forum.xda-developers.com/showthread.php?p=23222794
The problems are due to HTC.dev not unlocking all parts of the boot loader - you can't flash radio.img or boot.img so nothing is working.
Sent from my Pyramid-T
stringer7 said:
You can recover this. Firstly read this guide, regarding downgrading hboot and getting s-off.
http://forum.xda-developers.com/showthread.php?p=23222794
The problems are due to HTC.dev not unlocking all parts of the boot loader - you can't flash radio.img or boot.img so nothing is working.
Sent from my Pyramid-T
Click to expand...
Click to collapse
thanks for your help. i went to your link and i flashed a stock tmobile rom as suggested and before i could take out boot.img and send it over fastboot my sensation booted to the home screen. i went ahead and s-off'd and SuperCID. just need to create a backup before i screw up again.
again thanks for the help everyone.
I got a bricked T-mobile Sensation today at the shop and after checking it out I thought it would be easy to fix but unfortunately its proving to be much more difficult than I expected. Here's what I'm working with:
Locked s-on
Hboot 1.18.0000
radio 10.14.9035.01_m
First, I tried all kinds of PG58 zips. None worked. I figure I need to be unlocked to do it. Did the HTC unlock and got to the warning screen and where it asks to choose yes or no. I can navigate to yes or no but when I choose yes it just freezes and doesn't do anything. I tried it 3 different times, same thing. I can't even choose factory reset in Hboot, it just freezes. I don't know what the eff is going on. I've been downloading RUUs but have yet to find the correct one. I don't know what firmware it has because it does not boot up.
I thought, well shoot, I have fastboot, maybe I could just s-off and root from fastboot, but I can't find any thread explaining how to do it.
Any help would be great.
Thanks!
Edit:
Found the correct RUU, 1.50.xxxx whatever. WHen I run the utility It says its rebooting into bootloader but stays in the same screen and doesn't do anything. I don't know if this helps, but when I go into the bootloader I cannot go back into hboot. It just, freezes.
Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.
As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.
Kazireh said:
Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.
Click to expand...
Click to collapse
gol_n_dal said:
As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.
Click to expand...
Click to collapse
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
I have all drivers installed, adb, fastboot, etc
If your on hboot 1.18 you have a gingerbread fw, look for that
Sent from my HTC Sensation 4G
its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?
q said you did not understand, is how I explain more thoroughly I am new to the subject
and my device does not enter the system and when using the mode prop vo comand says device not found what to do? sensation with my ta hboot 1.27.0000 s-s on rl unloked help me
2strokenut said:
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
Click to expand...
Click to collapse
Can you get into "Fastboot USB" ?
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
Click to expand...
Click to collapse
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
Click to expand...
Click to collapse
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
I have all drivers installed, adb, fastboot, etc
Click to expand...
Click to collapse
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.
nickL0V3 said:
its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?
Click to expand...
Click to collapse
Yeah that's what I'm leaning toward right now, there is nothing else I can do. I have 4 or 5 Mytouchs on the shelf with bad eMMc chips so I guess this one is joining them.
gol_n_dal said:
Can you get into "Fastboot USB" ?
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.
Click to expand...
Click to collapse
Yes the RUU was 1.50.531.xxxxxx
Yes, I can get into Fastboot usb, I can do fastboot commands, it just freezes when the RUU tries to do its thing.
Jbear would still work if the bootloader were locked, but I couldn't unlock the bootloader. Revolutionary will not work either because its run while the phone is on, which I can't do.
I think I've exhausted every option, it seems to all point to a failed eMMc chip, shame though, I really like these phones.
Thanks for the help fellas
GL
///////////////
Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
theonetruewill said:
Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
Click to expand...
Click to collapse
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
AndroidSupporter318 said:
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
astar26 said:
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
I have put card in-between this to keep it secure before on a trial and error when it was having connection issues. It is not this that is the problem. Thank you for your input though.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
How do I do this. Please bear in mind I have not rooted etc before. I performed Step 4 of this guide before and that is why I believed I had done this. http://forum.xda-developers.com/showthread.php?t=1192300
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
This is where I got confused and started to seek assistance. I have no idea what my CID is or really how to use an RUU or what one to pick. It was a UK Vodafone handset but I don't know how this corresponds to anything or what to do about it.
AndroidSupporter318 said:
...If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
When I do (and did before) step 3 I just get a list of commands and no current software version showing. This was exactly when I came here. I thus went no further as what I had did not correspond.
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
astar26 said:
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
Click to expand...
Click to collapse
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
in the sensation forums no one reported that he had supercid while on S-ON
theonetruewill said:
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
Click to expand...
Click to collapse
open the cmd window in the folder where you have adb and fastboot files and perform there the command
also make sure that in hboot screen it shows fastboot usb
rzr86 said:
in the sensation forums no one reported that he had supercid while on S-ON
Click to expand...
Click to collapse
Hi. Maybe no one has reported it but u can have supercid with s-on, and i dont mean by going s-off first. It is very rare tho, like if u work for lets say vodafone then u can get a stock s-on phone with supercid. For development r something i think. But like i said, its very rare that us general public get our hands on them. But it is possible
Got it to show my cid. Error when flashing the rom using the executable file. Will try again when back from work
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
maybe you used an RUU of SE when you are not (or otherwise, regular for XE). beside CID, there is MID. the procedure of adding your MID and checking the MID is similiar to the CID.
MID indicates your model - in this case mainly three are possible: one for regular sensation, one for XE, and one for 4G.
theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
rzr86 said:
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
Click to expand...
Click to collapse
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Managed to get a RUUto flash to it - http://freakshare.com/files/gt7345y....23.3504.07_M2_release_251541_signed.exe.html
Unfortunately this has not fixed the problem. I suspect this may be terminal. Any suggestions?
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
theonetruewill said:
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Click to expand...
Click to collapse
with that hboot version you can only use juopunutbear method to S-OFF the device
try to unlock the bootloader via htcdev site
flash a custom recovery(i suggest 4ext)
flash a custom rom from recovery(before flashing enable smartflash from 4ext)
---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------
TotallydubbedHD said:
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
Click to expand...
Click to collapse
post your bootloader details and what exactly did you do ?
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
theonetruewill said:
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
Click to expand...
Click to collapse
do it with notepad++
Hello,
This might be a repetitive question but I couldn't find an exact answer.
Through the research I've done, so far I know that I should S-off my device first and then update my RUU to get android 4.3 on my device.
I am S-on and on hboot 1.11. Using clean rom right now. I'm a noob in this and have no idea abt details.
I bricked my phone once and don't want to do it again.
So, For S-off should I follow facepalm method and then should I update my RUU?? The cingular one??
Also, if anyone has a video on s-off it would be great. I can follow it easily.
Thanks. Any help will be appreciated.
You have it right. Get s-off first, then run the RUU. The facepalm method is the only method for s-off and you don't really need s video, you just need to follow the instructions, it's very easy. If you're with at&t then the Cingular RUU is the right one for you. After the RUU you'll need to flash TWRP recovery again.
Sent from my Evita
timmaaa said:
You have it right. Get s-off first, then run the RUU. The facepalm method is the only method for s-off and you don't really need s video, you just need to follow the instructions, it's very easy. If you're with at&t then the Cingular RUU is the right one for you. After the RUU you'll need to flash TWRP recovery again.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the quick reply. I'm with Rogers. Live in canada. I guess they're both the same right??
And after I run RUU, is my phone still going to be rooted or do I have to do all that again?
Also, I found this link online to run RUU, http://www.youtube.com/watch?v=SZuAjz4PIjU
Can you please check and tell me, if I should do the same or not? Go to fastboot and command prompt stuff??
One more thing. S-off says I need superCID? I have no idea what that is. How do I check for that?
Sorry for all the questions but I can't lose the phone again.
Thanks again.
saagar_mistry said:
Thanks for the quick reply. I'm with Rogers. Live in canada. I guess they're both the same right??
And after I run RUU, is my phone still going to be rooted or do I have to do all that again?
Also, I found this link online to run RUU, http://www.youtube.com/watch?v=SZuAjz4PIjU
Can you please check and tell me, if I should do the same or not? Go to fastboot and command prompt stuff??
One more thing. S-off says I need superCID? I have no idea what that is. How do I check for that?
Sorry for all the questions but I can't lose the phone again.
Thanks again.
Click to expand...
Click to collapse
To run the RUU, all you need to do is plug in you s-off'd phone and run it. No additional steps are required.
For superCID, first go into bootloader and run.
fastboot oem readcid.
Tell us what it says.
Sent from my HTC Evita with XDA Premium 4
RollTribe said:
To run the RUU, all you need to do is plug in you s-off'd phone and run it. No additional steps are required.
Sent from my HTC Evita with XDA Premium 4
Click to expand...
Click to collapse
I tried the S-off method but got error 99 instead of error 92.
I think I don't have supercid. Any idea how I should install that!???
saagar_mistry said:
I tried the S-off method but got error 99 instead of error 92.
I think I don't have supercid. Any idea how I should install that!???
Click to expand...
Click to collapse
Try this.
fastboot oem writecid 11111111
Sent from my HTC Evita with XDA Premium 4
RollTribe said:
Try this.
fastboot oem writecid 11111111
Sent from my HTC Evita with XDA Premium 4
Click to expand...
Click to collapse
It shows read failed. too many links.
Also shows no device attached. My usb is attached. I'm in bootloader and it shows fastboot usb.
Still shows no device attached.
saagar_mistry said:
It shows read failed. too many links.
Also shows no device attached. My usb is attached. I'm in bootloader and it shows fastboot usb.
Still shows no device attached.
Click to expand...
Click to collapse
Super CID. Use ADB.
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
If you don't follow procedure or try things without knowing the current state of your phone, you're on a fast track to a second brick. I am only warning you because you seem to care whether you brick or not.
exad said:
Super CID. Use ADB.
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
If you don't follow procedure or try things without knowing the current state of your phone, you're on a fast track to a second brick. I am only warning you because you seem to care whether you brick or not.
Click to expand...
Click to collapse
Thanks for the reply!
And yes I don't want to brick it again. I'll leave the phone as it is. I don't think I should proceed with S-off. I downloaded the ADB bundle stuff but gonna stop here. lol.
Anyways. Thanks a lot for help, all of you guys!
saagar_mistry said:
Thanks for the reply!
And yes I don't want to brick it again. I'll leave the phone as it is. I don't think I should proceed with S-off. I downloaded the ADB bundle stuff but gonna stop here. lol.
Anyways. Thanks a lot for help, all of you guys!
Click to expand...
Click to collapse
S-Off isn't so difficult, but at least you know where to draw a clear line on when to stop messing with the phone, unfortunately a lot of people don't really know when they are in over their heads.
As long as you can read and follow directions you will be ok. I suggest reading material on what you are doing to your phone, and if what you're doing is beneficial for it. If you read and don't understand then wait until you do so you don't brick your phone.
Sent from my HTC One X using xda app-developers app