Related
Hey,
I was wondering, is there anyway to gain temproot until we have full root? Am I right in thinking that temproot allows programs requiring root access to work e.g. AdFree?
Thanks
Sent from my HTC Sensation Z710e using XDA Premium App
There's an app called gingerbreak which works on the S E Arc (it roots anything on Gingerbread) so I wonder if it will work on the Sensation?
I'm waiting to get mine at the moment...
Hopefully tuesday
Hi !
I've fund this, but can't try, the sensation is not yet available in France
http www zenilshroff.com/ how-to-root-htc-sensation-android-2-3-gingerbread-smartphone/
(sorry, I can't post URL, i'm new on this forum)
-------------
HTC P3600 WM6.1
HTC HD2 WM7+Android 2.2
Roccoswell said:
Hi !
I've fund this, but can't try, the sensation is not yet available in France
http www zenilshroff.com/ how-to-root-htc-sensation-android-2-3-gingerbread-smartphone/
(sorry, I can't post URL, i'm new on this forum)
-------------
HTC P3600 WM6.1
HTC HD2 WM7+Android 2.2
Click to expand...
Click to collapse
Is that saying you need to remove HTC Sync from the device, and then run Gingerbreak?
Sent from my HTC Sensation Z710e using XDA Premium App
credits to this guide: http://www.zenilshroff.com/how-to-root-htc-sensation-android-2-3-gingerbread-smartphone/
1. First download the Gingerbreak.apk file.
2. Save on your computers desktop.
3. Connect the phone to your computer. (do not connect using htc sync)
4. Mount SD card as flash drive as you generally do for USB cable file transfers.
5. Copy the downloaded Gingerbread apk file to SD card root.
6. You should have any File Manager (e.g., Astro File Manager) on your phone. If not, download from Market. These are generally free apps.
7. Disconnect your phone from computer and launch File Manager. You will find in the menu of the phone.
8. Follow the onscreen instructions on File Manager to install APK to your phone from SD card root. You may also use the default application installer software to do this.
9. After installation completes, open the APK.
10. Press ‘root’ button. Simple, isn’t it?
11. The APK exploit will run for some time. Usually it runs for around 10 minutes. Your phone will be rebooted. In case it takes more than ten minutes for auto reboot, please reboot it yourself. Not to panic, this happens a lot of times.
12. Your device is now rooted. Congrats!
13. Make sure that SuperUser app is installed and is running. This is very important for you to enjoy the benefits of rooting.
In order to test if your phone has been successfully rooted, just click a screenshot of your phone. That should show that your phone has been rooted.
Yeah, but does it REALLY work?
Sent from my HTC Sensation using XDA Premium App
Gingerbreak exploit is patched on the SGS II so doubt that will work. Also if phone needs to reboot, no way will root persist due to signed locked bootloader. Go ahead and try but we will need some L33t devs to break this phone.
Sent from my HTC Hero using XDA App
drspikes said:
Gingerbreak exploit is patched on the SGS II so doubt that will work. Also if phone needs to reboot, no way will root persist due to signed locked bootloader. Go ahead and try but we will need some L33t devs to break this phone.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Yeah, I'm not really willing to believe it works either mate.
If the guide has some proof (i.e. a bootloader photo) then I will try it. If not, it's all just based on theory, but nothing practical.
Somebody has to be the guinea pig.
Darnell_Chat_TN said:
Somebody has to be the guinea pig.
Click to expand...
Click to collapse
Well, I have tried it, doesn't seem to do a thing so far.
It does say it fails a lot, but still, zero proof that is works, I'm very suspicious that it's all ********
It would be great if we could get this partial root. I personally don't mind not being able to flash custom ROM, but it is very important to me to be able to use some apps that require root permissions like adfree or titanium backup. From what I understand, this 'half-root' should not be very difficult to achieve cause it is not needed to mess with the bootloader for this purpose. The only requirement is to be able to uninstall htc sync for some time.
Here also a link detailing the differences between root levels and clarifying vocabulary. I am posting this cause it has been very useful for me to help understand, so it might also serves others..
http://androidforums.com/evo-3d-all-things-root/329819-no-need-panic-about-locked-bootloader.html
madindehead said:
Well, I have tried it, doesn't seem to do a thing so far.
It does say it fails a lot, but still, zero proof that is works, I'm very suspicious that it's all ********
Click to expand...
Click to collapse
Thank you for trying it. I think you should now do a full factory reset, to totally get that thing off your Sensation. It does not do what it's supposed to do and who knows what it might be doing behind the scenes. Yea, be very suspicious!
Darnell_Chat_TN said:
Thank you for trying it. I think you should now do a full factory reset, to totally get that thing off your Sensation. It does not do what it's supposed to do and who knows what it might be doing behind the scenes. Yea, be very suspicious!
Click to expand...
Click to collapse
Yeah, doing a full reset was in the back of my mind. Think I will go do that now
I'm not optimistic thought. They who owns the website emailed me (I posted a comment doubting it, and it was deleted, so I reposted, and he emailed me), to say the guy who posted it hadn't got back to him, so he was removing it from the site until he had confirmation that it did work. I am still VERY sceptical of it. He said, uninstall HTC Sync from the PC, as that causes problems with root? VERY random thing IMHO.
madindehead said:
Yeah, doing a full reset was in the back of my mind. Think I will go do that now
I'm not optimistic thought. They who owns the website emailed me (I posted a comment doubting it, and it was deleted, so I reposted, and he emailed me), to say the guy who posted it hadn't got back to him, so he was removing it from the site until he had confirmation that it did work. I am still VERY sceptical of it. He said, uninstall HTC Sync from the PC, as that causes problems with root? VERY random thing IMHO.
Click to expand...
Click to collapse
Well, a factory reset and trying to run GingerBreak right after hasn't done a thing. It says to reboot after it doesn't succeed after 10 mins, and that this happens a lot. But EVERY attempt I have been rebooting after 10 mins.
If the guy who "discovered" it can't even post proof, it sounds like a load of ****.
madindehead said:
Well, a factory reset and trying to run GingerBreak right after hasn't done a thing. It says to reboot after it doesn't succeed after 10 mins, and that this happens a lot. But EVERY attempt I have been rebooting after 10 mins.
If the guy who "discovered" it can't even post proof, it sounds like a load of ****.
Click to expand...
Click to collapse
Yea, if they discovered it they can prove their claim with a simple photo.
This speaks to not only the lack of credibility of the person who posted it, but also to the site that allowed it to be posted and remain till the complaints came in. A very untrustworthy source is how I view them because of this.
Gingerbreak won't help you, as there will be a nand lock, and the fact the kernel will be patched...
pulser_g2 said:
Gingerbreak won't help you, as there will be a nand lock, and the fact the kernel will be patched...
Click to expand...
Click to collapse
Yeah, I didn't think it would work to be honest. That really as wishful thinking. The person who posted that seems like a proper idiot
this will work once we get s-off to perminate root and then you can flash the recovery from fastboot or rom manager
xboarder56 said:
this will work once we get s-off to perminate root and then you can flash the recovery from fastboot or rom manager
Click to expand...
Click to collapse
Given your confidence, we'll let you test it first.
Darnell_Chat_TN said:
Given your confidence, we'll let you test it first.
Click to expand...
Click to collapse
Gingerbreak won't help you, as there will be a nand lock, and the fact the kernel will be patched...
Click to expand...
Click to collapse
Even the website states we need s-off so when that is achieved it will work and i will test it once we find a crack for the radio to get s-off/nand lock.
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
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
Hey all. I wanted to get something going here on this. I've been trying all sorts as I'm sure other have.
I've tried pushing a modified mmcblk0p4 to dev/block folder but on closer inspection there's files perhaps controlling that file in platforms and deeper.
I've attached my zip file to flash in recovery for push modified mmcblk0p4 and p4 to the phone.
Please note it doesn't work! It doesn't seem to harm anything so don't worry but it simply doesn't write.
So having said all this. Has anyone got any idea how the files are controlled? Maybe one of the loop files tells the other files what they should be? Or could there be hidden files.
Anyway devs please feel free to have a look at my zip and maybe someone with a bit more knowhow might be able to mod it to function
Link to zip attempt here = http://d-h.st/mkh
Sent from my Tricked out 'One'
Found another file containing CID and also my origional stock software number. mmcblk0p19. It allowed me to change the CID in this file and it stuck. But it has effected nothing currently. Going to look deeper and see what else might be there.
Sent from my Tricked out 'One'
The War Horse said:
Found another file containing CID and also my origional stock software number. mmcblk0p19. It allowed me to change the CID in this file and it stuck. But it has effected nothing currently. Going to look deeper and see what else might be there.
Sent from my Tricked out 'One'
Click to expand...
Click to collapse
awesome! keep us posted
The War Horse said:
Hey all. I wanted to get something going here on this. I've been trying all sorts as I'm sure other have.
I've tried pushing a modified mmcblk0p4 to dev/block folder but on closer inspection there's files perhaps controlling that file in platforms and deeper.
I've attached my zip file to flash in recovery for push modified mmcblk0p4 and p4 to the phone.
Please note it doesn't work! It doesn't seem to harm anything so don't worry but it simply doesn't write.
So having said all this. Has anyone got any idea how the files are controlled? Maybe one of the loop files tells the other files what they should be? Or could there be hidden files.
Anyway devs please feel free to have a look at my zip and maybe someone with a bit more knowhow might be able to mod it to function
Link to zip attempt here = http://d-h.st/mkh
Sent from my Tricked out 'One'
Click to expand...
Click to collapse
Unfortunately I won't be able to help you on this as I'm a bit of a noob :silly:. Just here to express my encouragement for your endeavours as I stand to benefit if you succeed as I am porting ORANG001 which I suspect will be right at the bottom of the pile update wise.
Perhaps some genius will crack the s-off riddle for this device which is hopefully more likely as this is running on qualcom . If I can be of any assistance in testing I would gladly help for what it's worth. Good Luck. :good:
Found more files but still no SuperCID. Wondering if there's some hidden files at work here...hmm
Sent from my Tricked out 'One'
It's already known that the CID partition is write protected, you need to find out how to bypass the protection
Sent from my HTC One using Tapatalk 2
superchilpil said:
It's already known that the CID partition is write protected, you need to find out how to bypass the protection
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
That is right. I have been trying to figure out how to write to that partition but i think im not that smart... I was thinking if anyone tried similar method to Facepalm S-OFF from HOX forums. I bet if we can somehow semi-brick the phone then it would open partitions for writing. JET used the same approach to downgrade HBOOT which is protected in S-ON
igagnidz said:
That is right. I have been trying to figure out how to write to that partition but i think im not that smart... I was thinking if anyone tried similar method to Facepalm S-OFF from HOX forums. I bet if we can somehow semi-brick the phone then it would open partitions for writing. JET used the same approach to downgrade HBOOT which is protected in S-ON
Click to expand...
Click to collapse
Facepalm takes advantage of supercid, so for that to work we would need to figure this out first
The semi brick was caused by flashing an evo lte p4 (extended partition table I believe) and no the HBOOT wasn't write protected so that's how it worked, but the signature was checked so you could only write a hboot from HTC.
So I doubt that would work, if I remember correctly the write protection is brought on early in the boot process, and to disable it you had to do some sort of power cycle without rebooting the phone
Sent from my HTC One using Tapatalk 2
superchilpil said:
Facepalm takes advantage of supercid, so for that to work we would need to figure this out first
The semi brick was caused by flashing an evo lte p4 (extended partition table I believe) and no the HBOOT wasn't write protected so that's how it worked, but the signature was checked so you could only write a hboot from HTC.
So I doubt that would work, if I remember correctly the write protection is brought on early in the boot process, and to disable it you had to do some sort of power cycle without rebooting the phone
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I'll be hunting until I find that file.
Does anyone know the order of boot?
Sent from my Tricked out 'One'
superchilpil said:
Facepalm takes advantage of supercid, so for that to work we would need to figure this out first
The semi brick was caused by flashing an evo lte p4 (extended partition table I believe) and no the HBOOT wasn't write protected so that's how it worked, but the signature was checked so you could only write a hboot from HTC.
So I doubt that would work, if I remember correctly the write protection is brought on early in the boot process, and to disable it you had to do some sort of power cycle without rebooting the phone
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I said that hboot was write protected and to unprotect it they had to semi-brick it using corrupted p4 partition. So YES, hboot is write protected during normal boot cycle, and when they introduced corrupted partition and semi-bricked the device, it disabled write protection on hboot.
Sorry if my english is confusing, its not my first language.
It's power on write protection. It doesn't get any earlier in the boot process than that.
P4/5 are your cid partitions. Anyother references to cid in other partitions are only that, and changing them will not change device cid.
Sent from my HTCONE using Tapatalk 2
18th.abn said:
It's power on write protection. It doesn't get any earlier in the boot process than that.
P4/5 are your cid partitions. Anyother references to cid in other partitions are only that, and changing them will not change device cid.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Man!
There still has to be some way to disable it though.....Must figure this one out!!!
Just had a go at something a bit different.
Managed to write Goldcard.img to mmcblk0 and it seems to have stuck. BUT.....Nothing's changed lol, and I attempted an RUU I knew shouldn't work....and it didn't.....So....I dunno....Anyone got any Ideas?
There is always an exploit. I'm not saying the write protection means it's impossible.
HTC doesn't use gold cards anymore.
Sent from my HTCONE using Tapatalk 2
18th.abn said:
There is always an exploit. I'm not saying the write protection means it's impossible.
HTC doesn't use gold cards anymore.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
No gold cards? Ah man!!
Yeh how can that even be?
Yeh there's gotta be a way. Hopefully some epic dev will already be on their way to finding it!!
I'm going to keep on playing until I either kill my phone and end up claiming on the insurance, I find a way or someone else does lol!
The War Horse said:
No gold cards? Ah man!!
Yeh how can that even be?
Yeh there's gotta be a way. Hopefully some epic dev will already be on their way to finding it!!
I'm going to keep on playing until I either kill my phone and end up claiming on the insurance, I find a way or someone else does lol!
Click to expand...
Click to collapse
If you're not a dev you're way on your way to becoming one, persistence like that is a virtue.
Appreciate your efforts sir.
What about Alpharev and unrEVOked? They were responsible for S-Off on the Sensation and such, i haven't heard anything but they may be looking into it too.
either way, good luck.
dladz said:
If you're not a dev you're way on your way to becoming one, persistence like that is a virtue.
Appreciate your efforts sir.
What about Alpharev and unrEVOked? They were responsible for S-Off on the Sensation and such, i haven't heard anything but they may be looking into it too.
either way, good luck.
Click to expand...
Click to collapse
Cheers. I'm actually loving the phone and for once have only really rooted it etc just because and not really for any gain but I can't help but want to try and help 'crack the nut' as it were....I doubt I will manage it though as I think it seems a bit above my skills but it's all worth a shot.
The War Horse said:
Cheers. I'm actually loving the phone and for once have only really rooted it etc just because and not really for any gain but I can't help but want to try and help 'crack the nut' as it were....I doubt I will manage it though as I think it seems a bit above my skills but it's all worth a shot.
Click to expand...
Click to collapse
Being a dev myself (not android - mostly just web stuff for work), it always seems like things are "above my skills" until I figure it out. Like the above poster said, persistence is all that is needed. We have "bang head here" signs at my office for a reason
The War Horse said:
Cheers. I'm actually loving the phone and for once have only really rooted it etc just because and not really for any gain but I can't help but want to try and help 'crack the nut' as it were....I doubt I will manage it though as I think it seems a bit above my skills but it's all worth a shot.
Click to expand...
Click to collapse
Yea i'm not even trying m8, i'd break something, i keep meaning to get into this dev lark but you need a lot of knowledge and a lot of people don't realise that.
If it were windows then lol, i'm in there but android has always been a bit of a hard nut to crack for me.
I've got some basic knowledge on the OS and the background workings but not nearly enough to make my own rom. One day i'll research it but at the moment with my life i have no time for anything let alone developing.
---------- Post added at 02:00 PM ---------- Previous post was at 01:59 PM ----------
scotty2hotty1125 said:
We have "bang head here" signs at my office for a reason
Click to expand...
Click to collapse
I like that
scotty2hotty1125 said:
Being a dev myself (not android - mostly just web stuff for work), it always seems like things are "above my skills" until I figure it out. Like the above poster said, persistence is all that is needed. We have "bang head here" signs at my office for a reason
Click to expand...
Click to collapse
Haha yeh definitely. It's all about trying and trying and sooner or later you suddenly know what's going on....at least with that little bit anyway haha!
dladz said:
Yea i'm not even trying m8, i'd break something, i keep meaning to get into this dev lark but you need a lot of knowledge and a lot of people don't realise that.
If it were windows then lol, i'm in there but android has always been a bit of a hard nut to crack for me.
I've got some basic knowledge on the OS and the background workings but not nearly enough to make my own rom. One day i'll research it but at the moment with my life i have no time for anything let alone developing.
---------- Post added at 02:00 PM ---------- Previous post was at 01:59 PM ----------
I like that
Click to expand...
Click to collapse
Yeh I didn't touch anything until I dabbled with a ROM for the DHD. I didn't do much dev work but I took a ROM and then tweaked it a bit. If you google enough you soon figure out how to do the odd bit here and there. Wish I had more programming knowledge but I suppose everyone's gotta start somewhere!
hey guys, i would really appreciate if someone has a minute to help me, cause i am lost in terminology and forums, and am working too much these days so cannot really read thousands of posts right now, and your experience could probably help.
so i installed rom manager , did i dont know what, went to work, my phone went battery dead, came back home, plugged it, but it wont recharge, nor go to boot loader, nor but normally, the light flashes randomly here and there when unplugging or pressing pwr button.
when connected to pc, the pc bips ta ta ta, or ti da, or ta di, but phone doesnt show anywhere, but the pc runs the device driver installation.
any clues?
it is an htc one x from rogers canada
thank you!
salissimo said:
hey guys, i would really appreciate if someone has a minute to help me, cause i am lost in terminology and forums, and am working too much these days so cannot really read thousands of posts right now, and your experience could probably help.
so i installed rom manager , did i dont know what, went to work, my phone went battery dead, came back home, plugged it, but it wont recharge, nor go to boot loader, nor but normally, the light flashes randomly here and there when unplugging or pressing pwr button.
when connected to pc, the pc bips ta ta ta, or ti da, or ta di, but phone doesnt show anywhere, but the pc runs the device driver installation.
any clues?
it is an htc one x from rogers canada
thank you!
Click to expand...
Click to collapse
Thanks for starting your own thread.
Screen stays black, power button stays black, can't get HTC screen or reovery up? If that's the case, it's bricked. You can try the Unbricking thread, you'll need a linux boot disk if you don't run linux and some time and patience. I'll brb to post helpful links.
Create bootable linux USB: http://forum.xda-developers.com/showthread.php?t=2223669&highlight=boot*+linux+usb
Unbrick thread: http://forum.xda-developers.com/showthread.php?t=1966850 If you make it past step 3 you may be able to save it. Otherwise, needs Jtag or warranty repair.
Good luck.
Did you flash anything with ROM Manager? I'm not sure it's supported for the One XL, but that could have changed. In the early days, a lot of people bricked because it was flashing things for the quad-core phone, which uses a different partition layout.
Was it functioning correctly, but then the battery went dead and it never revived? That sounds like the power management bug. Some people, unfortunately, have had their phones just die like this, like it just decides the battery is dead and won't recharge. If that's the case, you're due for a warranty replacement.
thanks.
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
ihave googled jtag but it is still unclear what that would be...
uhh, linux tralalaaaa a long night in front of me ha?
can you please explain in a few words?
thanks
exad said:
Thanks for starting your own thread.
Screen stays black, power button stays black, can't get HTC screen or reovery up? If that's the case, it's bricked. You can try the Unbricking thread, you'll need a linux boot disk if you don't run linux and some time and patience. I'll brb to post helpful links.
Create bootable linux USB: http://forum.xda-developers.com/showthread.php?t=2223669&highlight=boot*+linux+usb
Unbrick thread: http://forum.xda-developers.com/showthread.php?t=1966850 If you make it past step 3 you may be able to save it. Otherwise, needs Jtag or warranty repair.
Good luck.
Click to expand...
Click to collapse
well, the problem is it dint let me to do a lot of things trhough rom manager because it wasnt the premium version but it did let me change a bootable setting and i do not remember which. the phone after that worket normally. but my stupid self forgot i have changed that in rom manager, went to work, my battery emptied during the day and the phone went off. when i plugged it when i came home it would not charge or turn on. so my guess is it is trying to boot something i set up but doesnt have enough power to finish it and cannot recharge further because it is stuck in that booting... if I understood anything about this things in these few hours i was trying to be smart and jerked off around the phone
i guess i deserve it
thanks
iElvis said:
Did you flash anything with ROM Manager? I'm not sure it's supported for the One XL, but that could have changed. In the early days, a lot of people bricked because it was flashing things for the quad-core phone, which uses a different partition layout.
Was it functioning correctly, but then the battery went dead and it never revived? That sounds like the power management bug. Some people, unfortunately, have had their phones just die like this, like it just decides the battery is dead and won't recharge. If that's the case, you're due for a warranty replacement.
Click to expand...
Click to collapse
Charge it overnight and see if it turns on at all afterwards.
Sent from my One X using xda app-developers app
Delete.
Sent from my HTC One X using xda premium
salissimo said:
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
Click to expand...
Click to collapse
There's bit of etiquette involved. If the thread is "mature" in the sense that the OP's issue has been resolved, or multiple discussion threads have evolved, then popping in with a related question is fine. It's just not polite to pop in on the second page of someone else's query when people are still trying to help him, unless you have the identical problem.
salissimo said:
well, the problem is it dint let me to do a lot of things trhough rom manager because it wasnt the premium version but it did let me change a bootable setting and i do not remember which. the phone after that worket normally. but my stupid self forgot i have changed that in rom manager, went to work, my battery emptied during the day and the phone went off. when i plugged it when i came home it would not charge or turn on. so my guess is it is trying to boot something i set up but doesnt have enough power to finish it and cannot recharge further because it is stuck in that booting... if I understood anything about this things in these few hours i was trying to be smart and jerked off around the phone
Click to expand...
Click to collapse
It's possible, but sounds unlikely. I don't think that just changing some setting would stop it from at least powering on. ROM Manager would have had to overwrite something critical that would prevent the CPU from even finding hboot. Had you merely messed up some boot setting, you should still be able to get the boot screen, which would then start looping.
Plug your phone into your PC and see what pops up in Device Manager. I expect you'll get QHUSB_DLOAD, which means you're bricked.
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
salissimo said:
thanks.
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
ihave googled jtag but it is still unclear what that would be...
uhh, linux tralalaaaa a long night in front of me ha?
can you please explain in a few words?
thanks
Click to expand...
Click to collapse
salissimo said:
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
Click to expand...
Click to collapse
I've never used that unbrick tool but I'm assuming you would need to be able to get to the bootloader to get it to work. Correct me if I'm wrong.
Sent from my HTC One X using xda app-developers app
salissimo said:
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
Click to expand...
Click to collapse
bakp4 is the null p4
I think killp4 is the same but I used bakp4 when i did it.
can you please try to answer my question? do i have to edit the file? which file? what and where to write in? can i skipo this step maybe?
thanks
exad said:
bakp4 is the null p4
I think killp4 is the same but I used bakp4 when i did it.
Click to expand...
Click to collapse
salissimo said:
can you please try to answer my question? do i have to edit the file? which file? what and where to write in? can i skipo this step maybe?
thanks
Click to expand...
Click to collapse
Hex edit your imei into bakp4 You cannot skip any steps. Did step 3 bring up your emmc partitions? if not you can't move any further. It's a full brick.
thanks,
i think i got ack something like sda1 sda2 sda3 so i am still hoping.
i have just opened my phone to find out there is no imei code printed anywhere in it.
so i am digging through my **** to find that little sticker which i think no longer exists.
heh, am i lucky.
is there an imei printed somwhere within the phone to your knowledge?
thanks a lot man
exad said:
Hex edit your imei into bakp4 You cannot skip any steps. Did step 3 bring up your emmc partitions? if not you can't move any further. It's a full brick.
Click to expand...
Click to collapse
salissimo said:
thanks,
i think i got ack something like sda1 sda2 sda3 so i am still hoping.
i have just opened my phone to find out there is no imei code printed anywhere in it.
so i am digging through my **** to find that little sticker which i think no longer exists.
heh, am i lucky.
is there an imei printed somwhere within the phone to your knowledge?
thanks a lot man
Click to expand...
Click to collapse
Needs to be the same amount of partitions as shown in the picture.. I think it's 32? if I'm not mistaken. If not, then you cannot recover.
no, it's not printed on the phone anywhere. It's in the Hboot or in the box the phone came with. that's it.
If you got it from AT&T, contact them and ask for bit. Whenever they activate a phone, we store it in the system and keeps track of what phone the customer is using.
Sent from my Carbon-ize Evita using xda-developers app
in the screenshot there are dev/sda dev/sda1 dev/sda2 dev/sda3 dev/sda5 dev/sda6
i have dev/sda dev/sda1 dev/sda2 dev/sda3 i think
but i havent done that with imei when i tried
so no chance ha?
what if i dont find the imei?
thank you!
exad said:
Needs to be the same amount of partitions as shown in the picture.. I think it's 32? if I'm not mistaken. If not, then you cannot recover.
no, it's not printed on the phone anywhere. It's in the Hboot or in the box the phone came with. that's it.
Click to expand...
Click to collapse
do you think mz phone is still under warranty considering it was tampered, and i cracked it open?
thanks!
salissimo said:
in the screenshot there are dev/sda dev/sda1 dev/sda2 dev/sda3 dev/sda5 dev/sda6
i have dev/sda dev/sda1 dev/sda2 dev/sda3 i think
but i havent done that with imei when i tried
so no chance ha?
what if i dont find the imei?
thank you!
Click to expand...
Click to collapse
I doubt AT&T can tell you unlocked it. They'll assume it's a power issue like Telus did for me. HTC may or may not warrant it. Mixed results from xda members
Sent from my One X using xda app-developers app
It should be in the EFS nv_data.bin. folder.
Sent from my HTC One X using xda premium