Related
If you want to check if your phone has a SuperCID but don't have access to a computer to run the fastboot commands you can do so from your phone with the following procedure.
Verifying SuperCID
I got the information for this from the HTC Vision wiki entry:- http://forum.xda-developers.com/wiki/HTC_Vision
I'm sure there is information about gfree in another post but I can't find it to credit anyone. If you know more about it let me know and I'll put the credits in here.
Ok, to verify that SuperCID was applied download the gfree_verfiy.zip file attached, extract and then use a root file explorer (e.g. ES File Explorer) to move the file to /data/local/tmp. When the file has been moved amend it's permissions to:-
User r/w/e
Group r/w
Other r/w
After you do this open Terminal and type the following:-
Code:
$ su
# cd /data/local/tmp
# stop ril-daemon
# ./gfree_verify
You should get the following returned:-
Code:
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
If it says @CID: 11111111 then you have set SuperCID successfully.
When you are finished start the interface layer again by typing:-
Code:
start ril-daemon
Didn't work for me.
CID Getter still says mine is TELST001
sromer said:
Didn't work for me.
CID Getter still says mine is TELST001
Click to expand...
Click to collapse
I'm not sure, but I would asume the CID Getter app would just get the CID of the current ROM you are using (the same as typing 'getprop ro.cid' into Terminal). The CID of your ROM and the CID of your phone are not the same. You need to use the method above to get the CID of your phone or alternatively you can use the fastboot commands from an adb connection.
waltsalt said:
I'm not sure, but I would asume the CID Getter app would just get the CID of the current ROM you are using (the same as typing 'getprop ro.cid' into Terminal). The CID of your ROM and the CID of your phone are not the same. You need to use the method above to get the CID of your phone or alternatively you can use the fastboot commands from an adb connection.
Click to expand...
Click to collapse
I followed all the instructions, but after i enter
Code:
$ su
# cd /data/local/tmp
# stop ril-daemon
# ./gfree_verify
i get
Code:
gfree verify_cid returned:
@CID: TELST001
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
So it hasn't changed like i should have.
I have no idea why it isn't working.
@sromer - I see, I'm at work at the minute but when I get home I'll run through things on my phone again to check if the attached file, etc. are all doing as they should. The original post is here - http://forum.xda-developers.com/showthread.php?t=1192630 - and this has a link to the file hosted on Multiupload. You could try working through the instructions there. If you do, let me know how you get on.
If it has worked for anybody else can you let me know?
waltsalt said:
@sromer - I see, I'm at work at the minute but when I get home I'll run through things on my phone again to check if the attached file, etc. are all doing as they should. The original post is here - http://forum.xda-developers.com/showthread.php?t=1192630 - and this has a link to the file hosted on Multiupload. You could try working through the instructions there. If you do, let me know how you get on.
If it has worked for anybody else can you let me know?
Click to expand...
Click to collapse
I just tried the one in that thread too and i get the same result.
It says it's worked but my CID stays the same.
Might just have to wait until tomorrow and try it on my pc
I have a really dumb question, but im pretty new to the Sensation, but not android....
Since this is the general section and its related to this thread, ill ask it here.
Why do I need SuperCID and what does it do? Does it have anything to do with flashing ICS firmware or roms? Im still on 2.3 roms as i have not figured out if I need to flash firmware or Hboot (dont even know the difference) to go from 2.3 roms to ICS roms....
SuperCID allows you to flash ROMs from any region e.g. a T-Mobile ROM from the US can be flashed onto a European handset. Without SuperCID this is not possible.
Sent from my HTC Sensation using XDA App
Aren't you supossed to do this while in fastboot?
Sent from my HTC Sensation XE with Beats Audio using XDA App
kboater said:
Why do I need SuperCID and what does it do? Does it have anything to do with flashing ICS firmware or roms? Im still on 2.3 roms as i have not figured out if I need to flash firmware or Hboot (dont even know the difference) to go from 2.3 roms to ICS roms....
Click to expand...
Click to collapse
Yes you will have to perform one of the SuperCID procedures ( there are several ways to do it ) before you can flash the ICS firmware.
OK, I put my phone back to the HTC__001 CID and reworked through these steps. Setting SuperCID from the phone isn't working for me either. I thought it had worked for me previously but I must have done the fastboot SuperCID procedure back in the days when I unlocked the bootloader so then when I checked if this procedure had worked it looked like it had!
I shall update this post to that effect.
The instructions for verifying the CID are still applicable and definitely work. It means you can check if you have SuperCID on your phone before flashing the new ICS firmware (for those that don't have easy access to a computer).
hey before i go ahead i'd like to know if i need to do a nandroid backup? i tried it once but it said gfree_verify not found ? does that mean after setting the perms i need to reboot and then go ahead whit terminal? lol any risks doing the following? sorry new phone kinda scared
Anyone ?
Sent from my HTC-Z710a using xda premium
The process itself is not that risky, BUT given you've tried once with no joy I'd say better safe than sorry. If all goes to plan you're good, but you never know what you might do accidentally when things start to deviate from the script
More experienced/confident operators might disagree but I tend to err very much on the side of caution. You only sacrifice a bit of time and some SD card space and it could save you much more time and stress later on.
"Better to be looking at it than looking for it!"
goatee84 said:
The process itself is not that risky, BUT given you've tried once with no joy I'd say better safe than sorry. If all goes to plan you're good, but you never know what you might do accidentally when things start to deviate from the script
More experienced/confident operators might disagree but I tend to err very much on the side of caution. You only sacrifice a bit of time and some SD card space and it could save you much more time and stress later on.
"Better to be looking at it than looking for it!"
Click to expand...
Click to collapse
Yeah so im about to do a backup whit cwm but idk i hear alot that cmw isn't stable and things like that is that true ?
Sent from my HTC-Z710a using xda premium
For the time I used CWM I had no problems with it, I suppose everyone's opinion of something is based on their personal experience with it.
Having said that I've been using 4ext recovery for a good while now and can highly recommend it, it has a great touch interface and I've had zero problems with it.
There are also plenty of apps available that allow you to do nandroid backups and the like from within the app, you set up what you want to do and the app does the rest (reboot into recovery, perform backup, reboot phone for example), for me I feel like it adds another element of risk so I prefer to do it manually from recovery. The attraction I suppose is the easier interface of a purpose built app but with something like 4ext you have a perfectly good touch interface to use anyway and provided you know what you're doing you should be fine
http://forum.xda-developers.com/showthread.php?t=1377759 if you want to have a look for yourself and see if you like it.
goatee84 said:
For the time I used CWM I had no problems with it, I suppose everyone's opinion of something is based on their personal experience with it.
Having said that I've been using 4ext recovery for a good while now and can highly recommend it, it has a great touch interface and I've had zero problems with it.
There are also plenty of apps available that allow you to do nandroid backups and the like from within the app, you set up what you want to do and the app does the rest (reboot into recovery, perform backup, reboot phone for example), for me I feel like it adds another element of risk so I prefer to do it manually from recovery. The attraction I suppose is the easier interface of a purpose built app but with something like 4ext you have a perfectly good touch interface to use anyway and provided you know what you're doing you should be fine
http://forum.xda-developers.com/showthread.php?t=1377759 if you want to have a look for yourself and see if you like it.
Click to expand...
Click to collapse
Thanks alot for the info and having older version of cmw shouldn't make issues whit flashing roms ?
Sent from my HTC-Z710a using xda premium
To be honest, I'm not sure with CWM, maybe someone with more experience with it can answer that.
I do remember someone using 4ext had an issue due to somehow falling back to a beta version during install and the fix ended up being to just install the newest version and all was well. It's somewhere on xda if you have a search (sorry don't have time to have a look for you) I actually came across the problem myself but had already read that thread and caught it before it caused any issues for me.
Again, I can't answer that for CWM but it might be something to be aware of?
Sent from my HTC Sensation Z710 using XDA
goatee84 said:
To be honest, I'm not sure with CWM, maybe someone with more experience with it can answer that.
I do remember someone using 4ext had an issue due to somehow falling back to a beta version during install and the fix ended up being to just install the newest version and all was well. It's somewhere on xda if you have a search (sorry don't have time to have a look for you) I actually came across the problem myself but had already read that thread and caught it before it caused any issues for me.
Again, I can't answer that for CWM but it might be something to be aware of?
Sent from my HTC Sensation Z710 using XDA
Click to expand...
Click to collapse
No worries thanks alot for the help mate !
Sent from my HTC-Z710a using xda premium
when i wanna install the asia rom, the power down, and i reboot my phone , now is all black screen, i cant open my phone now, i m with rogers htc one x, how can i do ?anyone can help? Now my phone has no any ROM inside
help
Power on and hold volume down. Select fastboot. Install new Rom.
Also I would suggest not using SuperPatchef as it is not completely stable yet.
Sent from my HTC One X using xda premium
ForcedZucchini said:
Power on and hold volume down. Select fastboot. Install new Rom.
Also I would suggest not using SuperPatchef as it is not completely stable yet.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
how to install new ROM in fast boot ? any ROM i can flash?
Look in Development forum for a Rogers RUU. Just follow the instructions in the . exe.
Sent from my HTC One X using xda premium
ForcedZucchini said:
Look in Development forum for a Rogers RUU. Just follow the instructions in the . exe.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
But i cant get into the system to open the usb debugging, so i cant use superpatch , i can only use fastboot. Can it be using in fast boot?
In fastboot, execute the RUU.
lilhyper said:
In fastboot, execute the RUU.
Click to expand...
Click to collapse
i dont know how to do it, could u show me how to ?thx very much
when the phone is off...
hold VOLUME DOWN, then press the power botton
then run RUU, it should work
ytwytw said:
when the phone is off...
hold VOLUME DOWN, then press the power botton
then run RUU, it should work
Click to expand...
Click to collapse
any RUU file i can download this forum?
I love how people leap before they look. Christ, always have a way back to stock plan before jacking with your $600 toy
Sent from my HTC One XL using Tapatalk 2
help needed.
cao0215 said:
help needed.
Click to expand...
Click to collapse
There's an entire dev section you could have read by now. Stop looking for handouts and fix your [email protected]#
Sent from my HTC One XL using Tapatalk 2
cao0215 said:
Click to expand...
Click to collapse
You have given literally NO info on what you have done to try and fix it. Have you even TRIED to read and understand what you have been told and instructed to do? Have you taken it upon yourself to read the dev section about restoring stock? We are not your helpdesk and xda doesn't exist to serve you. Get off your ass and do some basic troubleshooting and problem solving. If you get stuck somewhere along the way, people will lend a hand. But until you prove that you have at least some initiative and can take it upon yourself to at least go through the steps of fixing it don't come here expecting to be spoonfed. The info is already in the dev section and the dev section isn't that big yet. It's not hard to find.
Sent from my HTC One XL using Tapatalk 2
OT, but it is good to see you with a One XL PG. From someone who remembers the Craptivate days...
Sent from my HTC One X using XDA Premium HD app
Pirateghost said:
You have given literally NO info on what you have done to try and fix it. Have you even TRIED to read and understand what you have been told and instructed to do? Have you taken it upon yourself to read the dev section about restoring stock? We are not your helpdesk and xda doesn't exist to serve you. Get off your ass and do some basic troubleshooting and problem solving. If you get stuck somewhere along the way, people will lend a hand. But until you prove that you have at least some initiative and can take it upon yourself to at least go through the steps of fixing it don't come here expecting to be spoonfed. The info is already in the dev section and the dev section isn't that big yet. It's not hard to find.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
/excited standing ovation!
Pirateghost said:
You have given literally NO info on what you have done to try and fix it. Have you even TRIED to read and understand what you have been told and instructed to do? Have you taken it upon yourself to read the dev section about restoring stock? We are not your helpdesk and xda doesn't exist to serve you. Get off your ass and do some basic troubleshooting and problem solving. If you get stuck somewhere along the way, people will lend a hand. But until you prove that you have at least some initiative and can take it upon yourself to at least go through the steps of fixing it don't come here expecting to be spoonfed. The info is already in the dev section and the dev section isn't that big yet. It's not hard to find.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
i just flash recovery into my phone , and use superpatch to flash asia ROM, but the power is dead, so the rom is not install completly, and then i get into the recovery and format the /system. Now my phone is only allowed to fast boot, and i m wondering to get the STOCK ROGERS RUU,but it's .zip , is there any way i can flash stock rom ? i m searching and go to dev section for the whole day, i m still not get the anwser.
cao0215 said:
i just flash recovery into my phone , and use superpatch to flash asia ROM, but the power is dead, so the rom is not install completly, and then i get into the recovery and format the /system. Now my phone is only allowed to fast boot, and i m wondering to get the STOCK ROGERS RUU,but it's .zip , is there any way i can flash stock rom ? i m searching and go to dev section for the whole day, i m still not get the anwser.
Click to expand...
Click to collapse
a whole day? really?
know what i found in about 2 minutes?
http://forum.xda-developers.com/showpost.php?p=25926794&postcount=39
Total recovery - flashing a RUU to completely restore your phone
If all else fails, this is your last resort.
This process will also erase all your data. But hey, beats having a dead phone, right?
First, ensure you have enough battery (more than 30%) to run an RUU.
Next, boot your phone into fastboot bootloader and open a command prompt window on your computer in the platform-tools folder.
Use the command:
fastboot getvar version-main
You now need to find the RUU that corresponds to this version. Start here. If you have problems visit #htc-one-x on freenode.
Now you must re-lock the bootloader using:
fastboot oem lock
It won't hurt to use the clear cache command as well
fastboot erase cache
Finally, run the RUU.exe that you have downloaded (must be used in Windows, and requires HTC drivers, which will have been installed whilst using HTCDev to unlock your phone).
This will write the /recovery, /boot, and /system to stock. You will need to start from scratch to unlock.
[edit]Extracting RUU if you have errors with the above method - Originally by torxx
Please note that this method isn't 100% reliable and should be considered a last resort; there have been various reports of this not working.
Many people have issues with flashing RUU's etc. having a bootlop.
Download a RUU (make sure you get the correct RUU, please see above)
Now open the .exe and make sure that it fully started.
Don't click anything, just go to windows icon and search for %temp%.
You will now find some folders, just search through these folders for the ROM.zip.
If you found it, you can copy it to your desktop or somewhere else.
Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
Plug in your One X, go into the bootloader and go into fastboot mode.
Navigate with the cmd in the folder with the fasboot.exe and the two .img's.
Now type in that:
fastboot flash boot boot_signed.img
fastboot flash system system.img
If everything worked, just reboot:
adb reboot
Click to expand...
Click to collapse
http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
seriously man....if you arent ready to LEARN what you are doing to your phone then you need to back the hell off.
3 options:
stay stock
learn what you are doing
buy an iphone
Pirateghost said:
a whole day? really?
3 options:
stay stock
learn what you are doing
buy an iphone
Click to expand...
Click to collapse
Could not agree more. Please READ the dev forums in detail before trying to do ANYTHING to your phone. Understand what you are doing before diving in.
Staying stock seems to be the best option for you. I know English is not your first language, which is fine; it's not my first language either. Reading all the development stuff can be challenging, but it's more dangerous to venture in this world unprepared.
The HTC One X is really very usable out of the box. Just use it and don't try anything funny.
This thread is just to direct all the noobs into the right direction, related to root and flash new roms in the Inspire 4G.
[*]Rooting and reverting to stock
Due to the retirement of the Hack Kit, rooting methods have been reduced to:
http://forum.xda-developers.com/showthread.php?t=2168500
or if you are skilled in using adb and fastboot commands:
http://tau.shadowchild.nl/attn1/?cat=6
If you are still stuck and want to revert your phone back to out of the box, then use Marsdta's Guide:
http://forum.xda-developers.com/showthread.php?t=1396229
or Gene Poole's Tool (that will revert also S-OFF):
http://forum.xda-developers.com/showthread.php?t=1208507
[*]Flashing a Custom Rom
To flash a custom rom you need to be rooted and S-OFF (if u used the Hack Kit) or have and unlocked bootloader using HTCDEV tool (wich I don't suggest)
Once u are S-OFF and have CWM or some other custom recovery installed (I personally prefer 4ext) you have to follow these steps (read the dev's thread about particularities. This is just a general guide on how to do it):
Download the custom rom .zip file and put it in your sdcard. Make sure that u check md5sum first just to avoid bootloops.
Reboot phone in recovery. There are many ways to do that, the first can be using Rom Manager (I don't suggest using it for anything else but that) and choosing reboot in recovery option. The second way is to boot in bootloader (press power down and reboot choosing hboot) or just turn phone off and power it up pressing power and volume down. And the last is to use adb commands. Plug the phone as charge only with usb debugging on, open a cmd as admin or terminal as root in your PC and then type adb reboot recovery.
Once in recovery, you need to do a full wipe (wipe data / factory reset and wipe cache + dalvik cache). You can also format some other partitions such as data and system, but the full wipe will work.
When full wipe is finished, go to flash zip from sdcard option, choose zip file and then flash that file.
Reboot the phone once it has finished flashing and wait for the device to fully reboot. The first boot will take a while (probably longer than usual) so don't get scared.
If you flashed a CM based rom, you need to flash google apps separately as well, so find the gapps file corresponding to your rom and flash it in the same manner as above described.
Trouble Shooting
Bootloops: If your phone repeats over and over the bootanimation, don't panic, you are not bricked. Something must have gotten wrong but you can reboot in recovery and re flash the rom as previously described. If bootloop is still there, then try downloading the zip again or choose a diffrent rom.
Factory Reset: If you factory reset the phone and you are not stock, then the phone won't have a rom...you will get stuck in the splash screen (white screen with the green HTC). Just do as described above, get a rom to the sdcard and then flash it. You are not bricked, you are just stuck
Well, this was just to try to point you in the right direction. If you think that I missed something, feel free to tell me and will add it to the OP.....Salud! :good:
Reserved just in case
Well done glevitan. On a side note, I finally understood how to use adb. Thanks.
Sent from a dream.
Teichopsia said:
Reserved just in case
Well done glevitan. On a side note, I finally understood how to use adb. Thanks.
Sent from a dream.
Click to expand...
Click to collapse
Thanks, let's hope that people find it usefull...
To help your thread going however 'slightly' off topic it may be, but since you did mention adb, I finally managed to get apk multi tool and sdk manager installed, and with a slight hiccup getting the adb to recognize my device (I started all of this last night), I believe I have everything I need?
Now I need to learn what I can do with those.
All of this would have taken me half the time if I were 15 again
Sent from a dream.
Teichopsia said:
To help your thread going however 'slightly' off topic it may be, but since you did mention adb, I finally managed to get apk multi tool and sdk manager installed, and with a slight hiccup getting the adb to recognize my device (I started all of this last night), I believe I have everything I need?
Now I need to learn what I can do with those.
All of this would have taken me half the time if I were 15 again
Sent from a dream.
Click to expand...
Click to collapse
hahaha...ummmm you shouldn't have problems. Just install SDK and apk multi tool in the SDK>tools folder or somewhere else. Then from command prompt you should be able to run the commands for the apk multi tool. I use the apktool and I have no problem at all. The main thing is to have adb installed...but there's no need to have the phone plugged to use the apk tool.
In the case of your device, make sure that u have the HTC drivers installed, if you have HTC Sync, you should have them...to try that just plug the phone as charge only, make sure that usb debugging is on and then open a cmd as admin and type adb devices...you should see your HTCserialnumber....
I didn't know I didn't need to have the cell plugged in, nice to know.
I had done all of that and it was working.... IT WAS WORKING , I decided to move a few folders around, something got messed up, tried placing them where they were, still no go, it's not recognizing my device anymore.
Don't worry, I'll figure it out eventually, but the problem is my head is going to start hurting any minute now. I'll be back shortly to ask you something you mentioned and I've read which I simply don't get - well, maybe not as shortly as I would like.
Edit: whenever I run the adb devices command it has to be done withing the folder where the adb.exe is located, right?
2nd edit: found it and it's working.
To run the adb devices command, which means going to that specific folder, would be seperate from using the apk tool? Would have moving the folders around somehow messed up the way apk tool would work? Im not even sure if im asking the right question
3rd edit: when you said to install the apk tool and sdk in the same folder, well, I already installed both of them to the default location.... what do you mean by that? Should I move them if they are not there? And if I may ask why?
Sent from a dream.
Teichopsia said:
I didn't know I didn't need to have the cell plugged in, nice to know.
I had done all of that and it was working.... IT WAS WORKING , I decided to move a few folders around, something got messed up, tried placing them where they were, still no go, it's not recognizing my device anymore.
Don't worry, I'll figure it out eventually, but the problem is my head is going to start hurting any minute now. I'll be back shortly to ask you something you mentioned and I've read which I simply don't get - well, maybe not as shortly as I would like.
Edit: whenever I run the adb devices command it has to be done withing the folder where the adb.exe is located, right?
2nd edit: found it and it's working.
To run the adb devices command, which means going to that specific folder, would be seperate from using the apk tool? Would have moving the folders around somehow messed up the way apk tool would work? Im not even sure if im asking the right question
3rd edit: when you said to install the apk tool and sdk in the same folder, well, I already installed both of them to the default location.... what do you mean by that? Should I move them if they are not there? And if I may ask why?
Sent from a dream.
Click to expand...
Click to collapse
What I did, that doesn't mean that is the correct way.... I installed SDK and in the tools folder I installed the apktool. You don't need to be in that folder to run the adb command...I don't do it that way...I just run the command from where I am...
glevitan said:
What I did, that doesn't mean that is the correct way.... I installed SDK and in the tools folder I installed the apktool. You don't need to be in that folder to run the adb command...I don't do it that way...I just run the command from where I am...
Click to expand...
Click to collapse
Right now I feel I'm way over my head. And that includes my choice of using eclipse. I'm not even sure what I can do with all these tools...
My hat off to you guys.
Sent from a dream.
Teichopsia said:
Right now I feel I'm way over my head. And that includes my choice of using eclipse. I'm not even sure what I can do with all these tools...
My hat off to you guys.
Sent from a dream.
Click to expand...
Click to collapse
I don't know either....but it is worth trying....see Adam's tutorials...are awesome. Maybe some day I will learn what to do with all this as well!! lol
glevitan said:
I don't know either....but it is worth trying....see Adam's tutorials...are awesome. Maybe some day I will learn what to do with all this as well!! lol
Click to expand...
Click to collapse
Back and forth
I don't believe that was the link you gave me on the other side. Perhaps posting over here will refresh your memory...?
Sent from a dream.
Teichopsia said:
Back and forth
I don't believe that was the link you gave me on the other side. Perhaps posting over here will refresh your memory...?
Sent from a dream.
Click to expand...
Click to collapse
AHH I was talking about Adamsoutler´s tutorial in XDA TV. He explains how to set SDK and develop APKs....it is awesome!..look at the XDA TV thread.
Bump.
Sent from a dream.
not able to go back to stock
I unlocked my htc inspire and tried to root it. Now i ended up with a ccwm recovery and S on unlocked bootloader .
I tried to go back to stock rom and have tried this guide and other guides also but was unsuccessful . My phone is running gizroot v2 but with taht the wifi mac address is unavailable . So i canniot access wifi .
If i put PD98IMG .zip in the root directory then it does not prompt me to any installation in the bootloader .
Please help
krjkinan said:
I unlocked my htc inspire and tried to root it. Now i ended up with a ccwm recovery and S on unlocked bootloader .
I tried to go back to stock rom and have tried this guide and other guides also but was unsuccessful . My phone is running gizroot v2 but with taht the wifi mac address is unavailable . So i canniot access wifi .
If i put PD98IMG .zip in the root directory then it does not prompt me to any installation in the bootloader .
Please help
Click to expand...
Click to collapse
RUUs can not be flashed with an unlocked bootloader. Relock it first, then run the RUU.
Can some one help me. I want to riot my htc inspire 4g
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
romanvaldezo said:
Can some one help me. I want to riot my htc inspire 4g
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This post is no longer timely. The tool it refers to has been retired. You can no longer get S-Off, but you can unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=2169515.
hey
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
rty123456 said:
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
Click to expand...
Click to collapse
Hey, not being mean, but did you read the post right above yours...? Or anything in the Desire HD forums, which is the same phone and is more populated?
rty123456 said:
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
Click to expand...
Click to collapse
Then are not reading the OP. You have all the information neeeded in there...if your first post in here Is to whine, then you have not Read the rules or understand the spirit of xda.
Follow the instructions And You will be fine, if You don't Get them take time To learn. Nobody Is going To do your homework.
I just recently rooted my inspire it took some time reading and a few attempts to get it down. But after my homework and grasping the concept it was fairly easy.
Sent from my Desire HD using xda app-developers app
Hi, this is my first post and I have looked for the answer but not been able to find it.
I have two questions on the same topic. I have HTC Sensation EU Vodafone running stock ICS.
1) I am half way through rooting my phone with the Hasoon2000's All in one One X rooting kit. More info at http://forum.xda-developers.com/showthread.php?t=1632553
I unlocked Bootloader sucesfully using HTC DEV and then installed clockwork mod like it says in the tutorial. However, the link to the SUperUser ZIP Package is broken so I don't know where to go from here. I have looked around for it but wasn't sure which one to install as I didn't want to take any risks of bricking my phone. Has anyone got the link to one for my phone?
2) Also, I am wondering how to UNflash clockwork mod incase something goes wrong and I want to change my mind about rooting. This is probably simple but I couldn't find the answer anywhere for the sensation. :fingers-crossed:
Thanks!
edwardday57 said:
Hi, this is my first post and I have looked for the answer but not been able to find it.
I have two questions on the same topic. I have HTC Sensation EU Vodafone running stock ICS.
1) I am half way through rooting my phone with the Hasoon2000's All in one One X rooting kit. More info at http://forum.xda-developers.com/showthread.php?t=1632553
I unlocked Bootloader sucesfully using HTC DEV and then installed clockwork mod like it says in the tutorial. However, the link to the SUperUser ZIP Package is broken so I don't know where to go from here. I have looked around for it but wasn't sure which one to install as I didn't want to take any risks of bricking my phone. Has anyone got the link to one for my phone?
2) Also, I am wondering how to UNflash clockwork mod incase something goes wrong and I want to change my mind about rooting. This is probably simple but I couldn't find the answer anywhere for the sensation. :fingers-crossed:
Thanks!
Click to expand...
Click to collapse
1)see from this guide only step 4A
http://forum.xda-developers.com/showthread.php?t=1631861
2)the only way to do that is to flash a ruu.exe which returns your device into cimpletely stock removing even the recovery
Thanks!
rzr86 said:
1)see from this guide only step 4A
http://forum.xda-developers.com/showthread.php?t=1631861
2)the only way to do that is to flash a ruu.exe which returns your device into cimpletely stock removing even the recovery
Click to expand...
Click to collapse
This is really helpful and a very fast reply! Thanks!
However, I have looked into it and this is great but it isn't actually the SuperUser Zip Package. I know that it is the equivalent but it isn't quite what I was looking for. Sorry. Great answer though.
Also, have you got a link to any ruu.exe for the Sensation because I don't want to use the wrong thing as it might possibly be a very expensive mistake... Thanks!
For more information about installing RUU's just have a look in HERE
edit: Actually you can use the link rzr86 gave you. It does contain the superuser and also busybox. You can flash that and you will be rooted! Good luck!
But...?
matekaneve said:
For more information about installing RUU's just have a look in HERE
edit: Actually you can use the link rzr86 gave you. It does contain the superuser and also busybox. You can flash that and you will be rooted! Good luck!
Click to expand...
Click to collapse
I looked into it though and it includes a ROM aswell. I know its pretty much the same as the stock one but I don't really want to change my ROM. Sorry for being awkward.
It doesn't include a rom! It is just going to root your device. Anyway! Have a look at THIS then. It's kgs1992 All in One tool kit.
Sorry!!!
matekaneve said:
It doesn't include a rom! It is just going to root your device. Anyway! Have a look at THIS then. It's kgs1992 All in One tool kit.
Click to expand...
Click to collapse
I tryed that download but it wouldn't work when I used it and unless I can suddenly find the superuser zip, I think I will just do the ruu.exe thing. I really don't have a clue where to find one though so can you PLEASE give me a link to one. (Im a complete NOOB!)
Also, if I use the Android Revolution thing, can I get back to stock ROM because I made a backup from Clockwork mod (just clicked backup and restore)?
Always make a nandroid backup through your recovery. Yes if you want to go back just select Restore. For the right RUU, read the thread I posted before and there will be some links you can download the right one for your device in step "2.4 To find your RUU". But before you do anything READ it carefully!
edwardday57 said:
I looked into it though and it includes a ROM aswell. I know its pretty much the same as the stock one but I don't really want to change my ROM. Sorry for being awkward.
Click to expand...
Click to collapse
actually did click the right link?
the link where step 4A is only
check again
i look even myself what contains the zip.file and it has only the superuser apk and busybox
I went for it!
rzr86 said:
actually did click the right link?
the link where step 4A is only
check again
i look even myself what contains the zip.file and it has only the superuser apk and busybox
Click to expand...
Click to collapse
YAY! My phone is now rooted! You are epic. Thanks. And to the other guy. The only reason that I kept thinking it was a Rom is because the folder was called Android Revolution. Sorry! I looked into the contents and found that there was only the rooting stuff. SOLVED!:good::good::good:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Sent from my Evita
timmaaa said:
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Click to expand...
Click to collapse
Thanks for the reply. I believe the reason I'm not bricked is because I backed out of the installation of Maximus HD during the setup screen progression. The actual ROM was never flashed. However, I have flashed the boot.img and ROMs for Viper, Xylon, and Cyanogenmod with no success. The result is the same every time (HTC screen, then black). I extract the boot.img from each of the roms, flash it, and then flash the ROM. The ROM I flash is a copy of the the original with the boot.img still inside. Perhaps I should be removing the boot.img if I am going to flash it separately in fastboot? And I realize that the threads are specific for certain phones now. It's all kind of a mess to get into at first.
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Madcat8686 said:
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
Click to expand...
Click to collapse
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Oh, that's great. Usually it shouldn't matter which order you flash in, but at least it got you out of trouble this time.
Sent from my Evita
roycedavies said:
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Click to expand...
Click to collapse
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
Hey, you should take the credit, I believe flashing it afterwards was what got his phone booted :thumbup:
Sent from my Evita
Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
timmaaa said:
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply! I will get the bootloader info ASAP bit don't I need to be s-of in order to RUU? from what I've read, if you don't have unlocked bootloader, root access, and s-off, you'll end up bricking your phone with RUU. I'd really like to do it but I have tried to get s-off to no avail.
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
roycedavies said:
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
Click to expand...
Click to collapse
Definitely not normal. A few recommendations:
1. Back up all your stuff, wipe everything except the SD card, Flash a fresh copy of the Rom, Flash the boot.img (you really should consider S-Off), Wipe the cache and DALVIK cache one more time, boot up the system.
2. Same as above except choose another Rom. There are plenty to choose from. The 4.4 Roms are getting a lot better now that the new Kernel fix got rid of the boot loops/reboots.
Sorry about the delay, it's been a heavy week at work. Hope things work out for you.
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
Sometimes is pays to see if there is a page 2 to the thread...Sorry about that! lol
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
timmaaa said:
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have no idea how much I have vicariously learned from your posts. Thanks Timmaa! I keep thinking if more of these folks would go ahead and get S-Off they would have waaaaaaaaaay less issues.
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
timmaaa said:
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I totally agree now because after rereading the post, there is a radio issue in addition to the boot issue. Is it possible that the Endeverou boot.img messed something up?
Yeah, that's exactly what I'm thinking. An RUU will hopefully fix that right up.
Sent from my Evita.
timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
That sounds like a good plan. (I'm really appreciating all your input by the way! Thanks so much!) One question though, upon checking out the rumrunner website, there isn't specific mention of the HTC One X Evita. Call me paranoid, but after what I've been through I want to make 100% sure I'm compatible before moving forward. Have you or anyone used this specific method for S-Off on the One X Evita?
For the Evita you use the universal HTC method. I've created a thread for it if you want to make sure it's worked for other Evita owners.
http://forum.xda-developers.com/showthread.php?t=2540232
Sent from my Evita.