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
Related
Hey guys,
I have been trying for ages to get a goldcard to work for the Sensation. I have managed to create a goldcard, but sadly, when trying to flash via fastboot (using RUU) and off the SD card, it doesn't work.
This leads me to think: Have HTC someone disabled the spoofing of CIDs from gold cards? Like I said, the gold card is created properly, the only thing I can think of, is that HTC disabled it? Or could it just be the SD card that is causing it to not work?
I am not a huge expert on this, can anyone else help?
madindehead said:
Hey guys,
I have been trying for ages to get a goldcard to work for the Sensation. I have managed to create a goldcard, but sadly, when trying to flash via fastboot (using RUU) and off the SD card, it doesn't work.
This leads me to think: Have HTC someone disabled the spoofing of CIDs from gold cards? Like I said, the gold card is created properly, the only thing I can think of, is that HTC disabled it? Or could it just be the SD card that is causing it to not work?
I am not a huge expert on this, can anyone else help?
Click to expand...
Click to collapse
nice your trying, will keep my eye on you
capychimp said:
nice your trying, will keep my eye on you
Click to expand...
Click to collapse
Haha thanks capy
I have 4 SD cards which I am testing out. Using bootloader method with PG58IMG.zip (Sensation ROM name in zip via bootloader) and via RUU (fastboot commands and then running the RUU, commands found here
Let's see how it goes. But I am worried that HTC did disable it somehow Is that possible?
i have no idea, but now i have a big intrest as i can get it here now, but if i cannot cook for it, then why by it but would be nice cooking for it along with dhd
I believe goldcard doesn't really help on most modern devices from htc...
pulser_g2 said:
I believe goldcard doesn't really help on most modern devices from htc...
Click to expand...
Click to collapse
I thought it worked on the Incredible S? Certainly worked on the DHD. I didn't ever use one, but I know people have done it (seen it in threads regarding debranding)
Information courtesy of jagaroth via a PM to me:
Sorry to PM but I can't post on a dev section without 10 posts and won't spam other subjects when hacking the desire is what I'm interested in. Feel free to repost if you think anything below is interesting (or will save others time).
Ok, I have at least 2 working gold cards and none of the HTC generic Roms will flash.
Thought I would try flashing my networks ROM (just testing fastboot PG58IMG.zip) & while that passed sig check it failed to install.
So next thing to try was using the RUU.exe and againg a fail. Seems you can't downgrade your existing ROM. I have 1.27.161.1 & the RUU is 1.24.161.1.
With downgrading Roms out for now (even with a gold card) a bit more digging is needed to un-brand and caution in upgrading since going back if an exploit is discovered will be tricky.
There does seem to be a weakness that may enable gingerbreak style root. Data can be pushed to data/local/tmp , chmod used and code executed there. A small chink in the armour.
Much faffing around in adb shell and examining logcat data awaits. Feels very strange having a tethered phone when I've got used to wifi adb!
Click to expand...
Click to collapse
So yeah, seems goldcard is out Such a shame
I hate HTC right now. At least a nice little goldcard would mean I could dump this Vodafone crap, and get proper Sensation Rosie here (the transparent one).
Update: I tried to run the HTC 1.27 shipped RUU (not the 1.24 RUU) and I got a different error. It was a signature error, not a CID error. What could this mean exactly? Not an expert.
madindehead said:
Information courtesy of jagaroth via a PM to me:
So yeah, seems goldcard is out Such a shame
I hate HTC right now. At least a nice little goldcard would mean I could dump this Vodafone crap, and get proper Sensation Rosie here (the transparent one).
Update: I tried to run the HTC 1.27 shipped RUU (not the 1.24 RUU) and I got a different error. It was a signature error, not a CID error. What could this mean exactly? Not an expert.
Click to expand...
Click to collapse
Goldcard's don't allow downgrading on their own. You have to change the ROM version identifier in misc to a lower version - in addition to using a Goldcard if you have a carrier CID and are downgrading to stock - if you want to do that. As far as upgrading/unbranding, I can't say why the sig check is failing as I don't have the phone and I'm not an expert. These instructions work for making a Goldcard for the DHD:
http://androidforums.com/desire-hd-...ding-1-32-405-6-1-84-720-3-a.html#post2657079
dazweeja said:
Goldcard's don't allow downgrading on their own. You have to change the ROM version identifier in misc to a lower version - in addition to using a Goldcard if you have a carrier CID and are downgrading to stock - if you want to do that. As far as upgrading/unbranding, I can't say why the sig check is failing as I don't have the phone and I'm not an expert. These instructions work for making a Goldcard for the DHD:
http://androidforums.com/desire-hd-...ding-1-32-405-6-1-84-720-3-a.html#post2657079
Click to expand...
Click to collapse
So, where is the misc that you can change the version number in to downgrade then?
madindehead said:
So, where is the misc that you can change the version number in to downgrade then?
Click to expand...
Click to collapse
It's the partition on the phone where things like CID, ROM version and other variables are stored. You need at least temp root to write to it so we're not in a position to do this yet.
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
dazweeja said:
It's the partition on the phone where things like CID, ROM version and other variables are stored. You need at least temp root to write to it so we're not in a position to do this yet.
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
Click to expand...
Click to collapse
Damn ok. Thanks for that. Then I will stop with trying to get 1.24 to install. 1.27 gives me a signature error, not a CID error, so not sure what that is (going from Vodafone 1.27 to HTC 1.27).
I guess I will pack it in until we get temp root. And since GingerBreak doesn't work, I don't know how we can get temp root. Really need a proper dev to get the device and start work on it, as I wouldn't know where to start looking, unless people can give me pointers?
If we find a dev willing to work on it we should have a whip round so they can buy a sensation. I saw they did this on an attrix thread if I remember right and they had the money in donations within a couple of days.
Sent from my Desire HD using XDA Premium App
kingguff said:
If we find a dev willing to work on it we should have a whip round so they can buy a sensation. I saw they did this on an attrix thread if I remember right and they had the money in donations within a couple of days.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Not a bad idea.
TO begin with, temp root would be a massive bonus. First allowing rooted apps to at least run, and then work can begin on the actual bootloader.
Yes it was the attrix thread, they got 700$ to a dev in China and he is making progress by the sound of it.
Sent from my Desire HD using XDA Premium App
I cannot find it now. I'll have a look when i get home
Sent from my Desire HD using XDA Premium App
well i tried everything i know related to goldcards and no dice. my sensation has 1.27 base and i was trying to update to 1.28. no matter how many cards i made (yes they were correctly made) i come done to this:
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
The best is to speak with AlphaRev team...........
I only flashed the stock asia rom again,and felt a bit faster than before..
same
Same thing here
I have made a gold card, and i am getting the Country ID (CID) error.
RADLOUNI said:
Same thing here
I have made a gold card, and i am getting the Country ID (CID) error.
Click to expand...
Click to collapse
The same..I tried to flash O2 1.34 ROM, but it said CID incorrect
How i got perm root on my MT4GS (does not give S-off just permroot of an S-off device)
YOU NEED TO HAVE A S-OFF device!
1)Start off with a fresh install of the TMO 1.28 ROM
2)Used temp root from MT4GSROOT.zip Thanks TeamWin for the temproot method Here is thread for orgnial files)
open MT4GSROOT\ADB (on pc)
Make sure that you have USB debugging turned on (on phone) and drivers installed to PC
Run Fre3voMT4gS.bat (from MT4GSROOT\ADB)
3)check in ternimal ((on phone) need to install from market)) and see if you have root (I got permission denied)
4)ran superonclick with Gingerbreak exploit (thanks CLShortFuse for making this tool) (on pc) - S1C thread
open MT4GSROOT and click on Superoneclick.exe
change exploit to Gingerbreak
hit root
Installed busybox when asked by S1C
Run Su test and looked on phone and Superuser asked for permission
5)Tried opening a app that uses root (root explorer) and SU FC on me
6)go to market and make sure you had latest version Installed (i had an update I needed)
7)Update binary when opening SU for the first time
Allow the SU app SU priviliages (funny I know)
8)Open a root app (root explorer again) and SU asked for permission
Test for permroot
turned off fastboot
deleted a system/app file (in this case htcfmwidget and htcfmwidge.obex) -using the r/w option in root explorer
Rebooted phone and reopened root explorer and looked for removed files and they were not there
None of the tools that I included were made by me they were made by the people I thanked. I just wrote the script for the tools to work. go to their threads and thank them.
Disclaimer I am not responsible for breaking your phone, melting it, or anything that may happen when doing this. Remember this is your choice
I have been able to use Root explorer, Titanium backup, terminal emulator and was able to remove APKs from the system folder that I do not want.
This is awesome!
So how did you get s-off? Did it ship that way?
raycaster3 said:
So how did you get s-off? Did it ship that way?
Click to expand...
Click to collapse
Mine was shipped s-off ordered online
Sent from my HTC Sensation Z710e using XDA App
crackeyes said:
Mine was shipped s-off ordered online
Click to expand...
Click to collapse
That's awesome that we've acheived perm root already.
If you don't mind me asking, did you do the preorder process from t-mobile?
I am extremely interested in this, but I hate preorders
crackeyes said:
Mine was shipped s-off ordered online
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Killer. Mine is being shipped the 27th. I can't wait to give this a try. Now all we need is miui for this phone and we're all set! Haha
Sent from my demonSPEED Glacier
raycaster3 said:
Killer. Mine is being shipped the 27th. I can't wait to gibe this a try. Now all we need is miui for this phone and we're all set! Haha
Sent from my demonSPEED Glacier
Click to expand...
Click to collapse
Oh no, I just realized he is probably talking about the DoubleShot.
For some reason I have a feeling that the delay for T-Mobile USA customers is due to HTC installing a S-On bootloader
poormanq45 said:
That's awesome that we've acheived perm root already.
If you don't mind me asking, did you do the preorder process from t-mobile?
I am extremely interested in this, but I hate preorders
Click to expand...
Click to collapse
I didn't preorder I acquired at a meet and greet where they gave me place to get it
Sent from my HTC Sensation Z710e using XDA App
Please don't ask for ETA's people would start coming in MT4GS section soon It come's with stock 2.3.4 so all we need is a custom ROM & were fine . I will be creating a TouchWiz 4.0 ROM w/Sense w/ MIUI icon's .
raycaster3 said:
Killer. Mine is being shipped the 27th. I can't wait to give this a try. Now all we need is miui for this phone and we're all set! Haha
Sent from my demonSPEED Glacier
Click to expand...
Click to collapse
No S-OFF on retail devices folks.
P
I cant get to get my computer to find it, is asking for the driver.... I try but I need the drivers it only appears as android phone on the management.
Update the driver comes on the original SD card, i swapped it which I didn't realized till now
Update 2: After finding the driver I still cant get root access.... anyone done it already?
waiting89 said:
I cant get to get my computer to find it, is asking for the driver.... I try but I need the drivers it only appears as android phone on the management.
Click to expand...
Click to collapse
Install htc sync but make sure it is not running
Sent from my HTC Sensation Z710e using XDA App
I got it working and follow the step of rooting, but I still dont get any root access...
is it possible to extract the s-off boot-loader from a device with s-off already? My understanding of these procedures is rudimentary at best, but if my understanding is correct, the boot-loader is a specific partition on the device, if someone with an s-off device could copy that image to their computer or just a folder on their sd-card, it should be possible then to share that with others who could then write that image to their boot-loader partion using fastboot. or can you not use fastboot until s-off is achieved? i hate that i always forget these things once i have my device running the way i want it to.
shizenyasuya said:
is it possible to extract the s-off boot-loader from a device with s-off already? My understanding of these procedures is rudimentary at best, but if my understanding is correct, the boot-loader is a specific partition on the device, if someone with an s-off device could copy that image to their computer or just a folder on their sd-card, it should be possible then to share that with others who could then write that image to their boot-loader partion using fastboot. or can you not use fastboot until s-off is achieved? i hate that i always forget these things once i have my device running the way i want it to.
Click to expand...
Click to collapse
The Stupid Noob wants to know...
What the heck is "S-off"??
shizenyasuya said:
is it possible to extract the s-off boot-loader from a device with s-off already? My understanding of these procedures is rudimentary at best, but if my understanding is correct, the boot-loader is a specific partition on the device, if someone with an s-off device could copy that image to their computer or just a folder on their sd-card, it should be possible then to share that with others who could then write that image to their boot-loader partion using fastboot. or can you not use fastboot until s-off is achieved? i hate that i always forget these things once i have my device running the way i want it to.
Click to expand...
Click to collapse
In order to flash the s-off bootloader you would have to have a eng bootloader. to put that on you would need s-off dont you love loop 22
As for s-off it means you can flash what ever you want to your device and it will not check to see if HTC signed it and approved it for you
thanks for that works great!!!!!!!!! also mine is from a retail store same day it came out
is it possible to build a PG59IMG file and pack the S-Off hboot into there?? possibly use HexEdit to make sure the version numbers match so that the phone will think it's just a factory reset/update file??
DJAeroX26 said:
is it possible to build a PG59IMG file and pack the S-Off hboot into there?? possibly use HexEdit to make sure the version numbers match so that the phone will think it's just a factory reset/update file??
Click to expand...
Click to collapse
I think just by making that one hexedit you instantly invalidate the sign on the the zip. Mainly because hashing the new file would give you a different result.
This mechanism actually prevents OTA updates from flashing if the file was changed due to (for example) corruption.
Not entirely sure but I think it's how it works.
That being said I was wondering what would happen if someone with an S-OFF hboot were to dump it and someone with S-ON would simply DD the right partition after achieving temp root.
On any normal computer that process would work. Wondering what secret HTC things happen under the hood though.
Akujin said:
I think just by making that one hexedit you instantly invalidate the sign on the the zip. Mainly because hashing the new file would give you a different result.
This mechanism actually prevents OTA updates from flashing if the file was changed due to (for example) corruption.
Not entirely sure but I think it's how it works.
That being said I was wondering what would happen if someone with an S-OFF hboot were to dump it and someone with S-ON would simply DD the right partition after achieving temp root.
On any normal computer that process would work. Wondering what secret HTC things happen under the hood though.
Click to expand...
Click to collapse
There's only one way to find out.
Sent from a Western Union telegram.
Akujin said:
I think just by making that one hexedit you instantly invalidate the sign on the the zip. Mainly because hashing the new file would give you a different result.
This mechanism actually prevents OTA updates from flashing if the file was changed due to (for example) corruption.
Not entirely sure but I think it's how it works.
That being said I was wondering what would happen if someone with an S-OFF hboot were to dump it and someone with S-ON would simply DD the right partition after achieving temp root.
On any normal computer that process would work. Wondering what secret HTC things happen under the hood though.
Click to expand...
Click to collapse
Oh ok. Thanks for clarifying that. I thought it would work because last time I did a warranty exchange, I had to return to stock but I had an ENG hboot and I was scared of bricking by using a factory image, so I took the factory image zip, unpacked it, "injected" the original hboot (which I hex edited to match the version number so that it'll take it as an update) and rezipped it and named it PC10IMG.zip. and yea I have a G2 but I want this phone :]
Sent from my T-Mobile G2 using XDA App
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
schnidex said:
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
Click to expand...
Click to collapse
Go to shippedroms and download the RUU for your phone. Although why you'd want to return to stock is beyond me?
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
schnidex said:
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
Click to expand...
Click to collapse
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
olyloh6696 said:
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
Click to expand...
Click to collapse
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
kartkk said:
do a nandroid backup & also set up your adb beforehand
setting up adb saved me from possibly bricking my device a few times
try this guide
Click to expand...
Click to collapse
ben_pyett said:
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
Click to expand...
Click to collapse
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Sent from my HTC Desire S using XDA Premium App
olyloh6696 said:
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Click to expand...
Click to collapse
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
ben_pyett said:
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
Click to expand...
Click to collapse
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
olyloh6696 said:
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
Click to expand...
Click to collapse
If the ruu runs successfully to competition I believe that it will return the device do that it's identical to stock
Swyped from HTC Desire S using XDA Premium
After many, many hours of trying to figure out what the hell half the terminology about Android actually means and wondering whether or not I would brick my phone..
..I'm now back to S-ON. It's been a pretty horrible experience all in all. Yes, it's easy when you know how but knowing how has been through trial and fortunately not much error.
From being on 6.98.1002, I used the Jorgen method in Ben's link above to get to 0.98.0000. I should note that when my phone was first supplied, I was on 0.98.0002 and very worried that the earlier software wouldn't work - but I tried it anyway, and it did. However, I was still S-OFF.
I then re-installed my stock network ROM using the RUU. This kept me on 0.98.0000 but put the phone to S-ON. I flashed the branded ROM that the phone was shipped with thinking that this would take me to 0.98.0002 but to my surprise it didn't. Otherwise though, the phone is now stock condition again.
So I then tried to update OTA to the problematic software which caused me all this grief in the first place - and it appears my network have withdrawn it. And rightly so, pending a fix.
schnidex said:
Ben, I've seen elsewhere you've said:
"If you load the latest RUU you may end up updating the HBOOT so that it can't be downgraded."
..in which case, Houston, we may have a problem. The latest HTC non-branded ROM (1.47...) gives you HBOOT 6.98.1002.
Click to expand...
Click to collapse
You're right, I'm afriad that this is an area where I'm no expert, But HBOOT = 6.98.1002. = Alpharevx = so you've not upgraded it simply failed to downgrade (which is slightly better- I think )
I notice that there are a couple of guides, allow I've obviously not tried either of them both are in the [GUIDE] A Complete Tutorial for the Beginners and Others sticky
The second guide looks quite complex and not for beginners...
Although I've just spotted a note within the second guide which says says
Note 2: RUU 1.46 or greater can not be downgraded as yet, since gingerbreak does not work on these RUUs.
So Opps....a full nights sleep may shed some more light on this.....and hopefully so sound advice from someone who has already performed this task.
Good luck. (I'll back online in the morning) - but, only really able to answer easier questions and not unfortunately not provide you with a solution.....but I'll do what I can!
Alternate way to restore your phone to S-ON and stock
If your attempts are unsuccessful, there's another potential way to go S-ON.
http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2
Maarten
i was wondering if there is a way to do this. ??
im tired of my MTS4G, i want to install a good rom!
Amen to that
Sent from my myTouch_4G_Slide using Tapatalk
As of right now no, were all basically stuck. Htc say they'll release a update at the end of the month to allow unlocking but that will void your warranty. Im just waiting for a crack for this version. Shouldn't Be too long i hope.
Sent from my myTouch_4G_Slide using Tapatalk
I did not realize that this phone still had an unlocked bootloader when I purchased it a few days ago. It's unfortunate how the HTC Unlocker was glitchy with the MT4GS; it might be why there's such a lack of development right now, haha.
ac3theone said:
As of right now no, were all basically stuck. Htc say they'll release a update at the end of the month to allow unlocking but that will void your warranty. Im just waiting for a crack for this version. Shouldn't Be too long i hope.
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
i hope!! i dont care about the warranty, i hate the stock the sence , is so slow and i hate the interface, im comming from a vibrant runing ics passion v12, you can only imagine my frustration .
Limewirelord said:
I did not realize that this phone still had an unlocked bootloader when I purchased it a few days ago. It's unfortunate how the HTC Unlocker was glitchy with the MT4GS; it might be why there's such a lack of development right now, haha.
Click to expand...
Click to collapse
I think we can start shelving the idea that there's a lack of dev for the device - some definite strides being made in that direction now.
We could always use more people helping make stuff, though.
----
I need a copy of an S-ON bootloader that has not been unlocked.
I need both S-ON 1.44.0007 and S-ON 1.45.0013 - if anyone can get either to me that would be great.
They are only 1MB in size and can be attached to a post in the forum.
If you can get it - attach it as a reply to this post:
http://forum.xda-developers.com/showthread.php?t=1254518
The terminal command to back up a copy of it is:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
That will place a copy of your hboot on your sdcard, called hboot.img, if run from a terminal.
Nlarge got his unlocked S-ON bootloader added to that thread, now we need some regular S-ON ones to compare them to. If anyone can figure out how to get one to us it would be helpful.
We are trying to work the S-ON issue, but it's not exactly an easy nut to crack and we've mostly just started.
Thanks for any help that can be provided. This may not be all we need, but it's a start.
Hasn't anyone been able to flash the original PG59IMG.zip via the OTAbootloader patch?
Delivered via candygram for Mr. Mongo.
Blue6IX said:
I need a copy of an S-ON bootloader that has not been unlocked.
I need both S-ON 1.44.0007 and S-ON 1.45.0013 - if anyone can get either to me that would be great.
They are only 1MB in size and can be attached to a post in the forum.
If you can get it - attach it as a reply to this post:
http://forum.xda-developers.com/showthread.php?t=1254518
The terminal command to back up a copy of it is:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
That will place a copy of your hboot on your sdcard, called hboot.img, if run from a terminal.
Click to expand...
Click to collapse
I'll see if I can figure out how to get that to you. If I can't code, at least I can help with other things.
Cool, we'll look it over and see what we come up with. No promises, just gonna look and see what we see and hope it leads to something.
The hboot may or (more likely) may not be the whole problem for s-off/s-on, but the more we have to play with the more we are learning.
Blue6IX said:
Cool, we'll look it over and see what we come up with. No promises, just gonna look and see what we see and hope it leads to something.
The hboot may or (more likely) may not be the whole problem for s-off/s-on, but the more we have to play with the more we are learning.
Click to expand...
Click to collapse
I tried to copy it with (adb shell <command>) but it says I have permission denied.
Limewirelord said:
I tried to copy it with (adb shell ) but it says I have permission denied.
Click to expand...
Click to collapse
Okay, we are working on that, etn4off is leading the charge on adb through stock recovery, so hold that thought.
Meantime, i've whipped up a new version of the stock restore .zip file, that should work on the new OTA.
( Make sure you have a full battery first!)
Edit - didn't work
What you have to do is rename the file to:
PG59IMG.zip
...then place on the main directory of your sdcard.
Make sure fastboot is turned off in settings on the phone, and then power off.
Hold Volume Down and press Power to turn it on, booting into hboot. The installer will take over from there and guide you through it.
It will load itself, then ask you to press Volume UP to install - then does it's thing and will tell you to press power to reboot when it is done.
This is basically the same restore file you get from here: Thread Link updated for the new OTA.
This should solve the version mismatch problem people were having, but won't know until someone tries to install it.
Afterwards you can run Revolutionary to S-OFF your 1.44.0007 hboot.
You will no longer be on the newest OTA, but then you can apply it if you want and go back - as long as you run the Revolutionary process on the 1.44.0007 hboot before you do.
I'm going to try this asap
Sent from my myTouch_4G_Slide using Tapatalk
Blue6IX said:
Okay, we are working on that, etn4off is leading the charge on adb through stock recovery, so hold that thought.
Meantime, i've whipped up a new version of the stock restore .zip file, that should work on the new OTA.
( Make sure you have a full battery first!)
Stock_Retail_OTA_1-55-531-3_downgrade_PG59IMG.zip
Download link
MD5: c7ea224be738b14824a003fd9c9b4b19
What you have to do is rename the file to:
PG59IMG.zip
...then place on the main directory of your sdcard.
Make sure fastboot is turned off in settings on the phone, and then power off.
Hold Volume Down and press Power to turn it on, booting into hboot. The installer will take over from there and guide you through it.
It will load itself, then ask you to press Volume UP to install - then does it's thing and will tell you to press power to reboot when it is done.
This is basically the same restore file you get from here: Thread Link updated for the new OTA.
This should solve the version mismatch problem people were having, but won't know until someone tries to install it.
Afterwards you can run Revolutionary to S-OFF your 1.44.0007 hboot.
You will no longer be on the newest OTA, but then you can apply it if you want and go back - as long as you run the Revolutionary process on the 1.44.0007 hboot before you do.
Click to expand...
Click to collapse
Has anyone tried this? Not that im saying its bad i just dont want to mess up my newest toy...lol
Sent from my myTouch_4G_Slide using Tapatalk
izzy001 said:
Has anyone tried this? Not that im saying its bad i just dont want to mess up my newest toy...lol
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
No. That's why I said we won't know until someone tries.
I've run the package on both of my devices, so can attest to it working - but they are both s-off.
I've run it from the device in the newest OTA form, and it brought me back, but the old package did too - seems no version check on my devices (probably any s-off devices)
I've run from all versions of the hboot - 1.44.0006, 1.44.0007, 1.44.1107, and 1.45.0013, but they were all s-off.
As for what happens with an s-on device... ...? I updated the version because in another thread that was pinpointed as the problem for it not installing on the newest OTA.
Blue6IX said:
No. That's why I said we won't know until someone tries.
I've run the package on both of my devices, so can attest to it working - but they are both s-off.
I've run it from the device in the newest OTA form, and it brought me back, but the old package did too - seems no version check on my devices (probably any s-off devices)
I've run from all versions of the hboot - 1.44.0006, 1.44.0007, 1.44.1107, and 1.45.0013, but they were all s-off.
As for what happens with an s-on device... ...? I updated the version because in another thread that was pinpointed as the problem for it not installing on the newest OTA.
Click to expand...
Click to collapse
Well i tried it... But it didnt even see it as an update... It just checked it and went straight to the hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
izzy001 said:
Well i tried it... But it didnt even see it as an update... It just checked it and went straight to the hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
Okay thanks, it was pretty much an 'it will do it or it won't' situation, so we'll have to try something else.
I wish I could get an s-on device in my hands that I could try stuff on - for now it's test and test and test on the s-off, then try on the s-on ...
Sorry it didn't work, we'll have to try another way.
I'll give this a try as well, even though it supposedly doesn't work. Better try than not.
Is what you're trying to do make the older ROM (with the 1.44.0007 HBOOT) appear as an update to the newer update so we can, in a way, downflash to the older HBOOT that's compatible with the Revolutionary tool?
I'm kind of new to the whole Android scene and am just curious as to how things work.
Limewirelord said:
I'll give this a try as well, even though it supposedly doesn't work. Better try than not.
Is what you're trying to do make the older ROM (with the 1.44.0007 HBOOT) appear as an update to the newer update so we can, in a way, downflash to the older HBOOT that's compatible with the Revolutionary tool?
I'm kind of new to the whole Android scene and am just curious as to how things work.
Click to expand...
Click to collapse
If this flashes it should revert the phone back to retail launch - but it's probably not going to. Finding a way to force it could have a less then desirable outcome.
If it doesn't take, don't try to force the issue with it unless you know what you're doing and why.
Well I tried it as well and it got a check, but it didn't install anything. I wish I had the know-how to mess around with this stuff.
Limewirelord said:
Well I tried it as well and it got a check, but it didn't install anything. I wish I had the know-how to mess around with this stuff.
Click to expand...
Click to collapse
When it checks and oks it go to recovery in hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
Hi guys. I've just got my brand spanking new HTC Sensation and i'm wondering what order to root/SOFF in and basically anything else as i've not done DIY rooting since my old HTC Desire a couple of years back so i'm a bit rust and confused.
I don't want to mess up and brick my phone so i'd like to know the things to do in the correct order and with the correct software/tools.
1st off i'll give the details about my device:
Phone - HTC Sensation Z710e
HBOOT - 1.27.0000
Android version - 4.0.3
HTC Sense version - 3.6
Software number - 3.32.771.13
Kernel version - 3.0.16-g159c6f3 / [email protected] build- 144 #1 / SMP PREEMPT Tue Apr 3 08:37:16CST 2012
I hope that's enough info but I have more should we need it.
This is how i'm thinking of doing it but please correct me if i'm wrong:
1) S-OFF using the Juopunutbear S-OFF method.
2) Install CWM via this thread.
3) Once that's been done I can go about installing custom ROM's.
Hope that's correct.
Thanks.
hmm as you are on stock ICS
there are few different ways to have root/custom roms
1.staying SON and flashing roms (this involves HTC-DEV unolcked bootloader ..which might void your warranty ...but not a single person was denied warranty until now afaik..but there is risk still involved..as htc keeps your phone info in their data base)
to do that follow this guide to the letter
2.SOFF and flash roms
2.1. SOFF without HTC-DEV unlocked bootloader ...guide link in my signature (ohh forgot to mention HTC-DEV will completely erase your data ..once you do a unlock)
(cons ....wire trick which is required is little bit hard..but all the troubleshoot has been covered)
2.2 SOFF with HTC-DEV unlocked bootloader....guide link here
(you can skip steps #2 and #3 as you are already stock ..igf you decided to use that)
for both the SOFF procedures ..there is a good tool too ..here is the tool (it not only does soff ..but a lot of other stuff...do check it )
after gaining SOFF ..you can flash recovery ..and then ROM installation
thanks for the reply.
So basically to do everything I should just use this?
http://forum.xda-developers.com/showthread.php?t=1668276
Buchtis said:
thanks for the reply.
So basically to do everything I should just use this?
http://forum.xda-developers.com/showthread.php?t=1668276
Click to expand...
Click to collapse
yep you can use that
and for thanks ..there is a button for that
I'm starting to lose it with this SOFF business. I've just beet at it far at least half an hour and it constantly fails with the error 66732337.
Could you link me to any ROM's that don't need SOFF please? Lost patience with this.
I've heard you have to be really precise with the wires
Haha i've literally just done it abour 20 seconds ago, tooted and SOFF! I can't get CWM to work though, i'm trying to flash it with that all-in-one job and i've donw everything it tells me to do but upon pressing the power button I get
CID incorrect!
Update fail!
Press <POWER> to reboot.
Click to expand...
Click to collapse
Any ideas?
For the wire trick it's a matter of timing don't give up.read over instructions again regarding the timing.I know you can do it is just going to take patience. You will be glad later you s off as there is more you can do and it makes things much easier later. Hang in there and I know you will have success . Best wishes.
Sent from my HTC Sensation 4G using xda premium
All sorted now, needed to flash the 11111111 CID.
Off to try some ROM's, is there anything else I need to do before that? I've rotted it, SOFF and installed CWM. As far as I know that's it but if there's anything else please tell me.
Buchtis said:
All sorted now, needed to flash the 11111111 CID.
Off to try some ROM's, is there anything else I need to do before that? I've rotted it, SOFF and installed CWM. As far as I know that's it but if there's anything else please tell me.
Click to expand...
Click to collapse
use 4EXT recovery ..its much better imho
for recovery ..you can do it via 4ext app
but for that you need root
you can use my one click root for that (soff guide link in my signature)
Damn i've just installed CWM, is there any difference between the two there than 1 having touch screen or do they have different functions? Don't really want to keep messing about if both are basically the same.
some rom installation works only on 4EXT (it will be mentioned in the thread ..like ARHD)...so its you call ..it has lot of other features too ..and completely supports backup made by cwm too
Alright, last few questions and i'll be gone!
Currently using the CM9 nightly.
http://forum.xda-developers.com/showthread.php?t=1654409
1) How do I go about installing 4EXT with CWM already installed?
2) I've just installed CM9. When I have the ROM on my desktop, can I go into the 'app' folder and remove some of the crap I won't be using? Things like Email, Movie Studio, Terminal Emulator, DPS Manager, ROM Manager, Voice Dialer, WiFi Calling? I used to do this on my old HTC Desire and it was a trail and error process but it did not damage/brick my phone in any way, all I used to get were screen with 'this application is not responding' etc. Is this still safe to do on the HTC Sensation?
3) In CM9 Nightly, how come I can't overclock past 1.2Ghz (stock speed)?
Thanks guys.
1: if you have root, just download the app from play store
2: yes, you can
3: you need to flash a kernel supporting overclock, like bricked AOSP.
If you run into problems, let me know
Sent from my Sensation using xda premium
Alright, I lied about the 'final question'.
Basically i've uninstalled that 4EXT Easy Flash from here and it's replaced CWM. Works fine but i'm wondering if that's the newest version? Or could someone link me to the newest version please?
Download 4ext recovery updater free from the play store. It lets you update the recovery if u dont have newest version
Guys does anyone know the .apk name of 'Movie Studio'? Removing all the crap I won't use now and I can't find it in the app list folder.
Thanks.
I found VideoEditor.apk in system/app on CM9 RC 1
Got it, thank you very much!
Edit: I've also deleted 'Voice Dialer' and 'Update Me'. Hope that's O.K.
InfinityFTW said:
Download 4ext recovery updater free from the play store. It lets you update the recovery if u dont have newest version
Click to expand...
Click to collapse
Says it costs £1.85.