Related
Having some problems unlocking my sensation,
Ive got s-off, installed clockwork and rooted it with another rom (done the cid etc),
now unlocking it in Terminal Emulator i just get access denied on phone, so i went for using "PG58DIAG " it doesnt seem to have done anything except re-set my phone and data.
Ive also tried the "adb" on pc and get access denied aswell
Any help??
thanks
If you used a ruu to install another rom you need to redo the rooting.
In the post where the steps to rooting are stated that you lose your root after a reboot unless you install a file. Did you do that?
Yep i installed su-2.3.6.3-ef-signed.zip to permanently root it, would it be worth doing it again incase there was an error or something?
In the bootloader i have
pyramid pvt ship s-off rl
hboot 1.18 0000
radio 10.14.9035.02_2
emmc boot
Ive just noticed when i go for recovery i get the phone with a warning triangle and nothing else, what has happened there??
Anyone else?
Ive re-done clockwork install,
should i just root from the start again?
If someone could help i would be willing to make a donation
SKll said:
Yep i installed su-2.3.6.3-ef-signed.zip to permanently root it, would it be worth doing it again incase there was an error or something?
In the bootloader i have
pyramid pvt ship s-off rl
hboot 1.18 0000
radio 10.14.9035.02_2
emmc boot
Ive just noticed when i go for recovery i get the phone with a warning triangle and nothing else, what has happened there??
Click to expand...
Click to collapse
i wanna know the steps you did to root the phone cause by lookin at this i can guess that you ran revolutionary, installed cwm, rooted your phone and than installed a stock ruu. if you did this than a) your hboot changed b) you lost root c) you lost cwm. if this is what you did than you are gonna have to run the process again from the beginning skipping the installation of a stock ruu of course. anytime you install a stock ruu than you will lose root, cwm and your hboot will change. hope this helps.
Thanks
i think that might be the problem, Ive flashed on revolution rom now, and i tried terminal and i get the numbers but no unlock code just the date im going to try the other method now and if that doesn't work ill start from scratch.
So much harder than installing android on my hd2 lol.
Ive re-done everything and now i get "su not found"
Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
edit: Issue solved, see page 2.
Also, in case this information helps - I do have a goldcard.img but it doesn't appear to work. My CID is T-Mob005
this guy seems to have been in the same boat as me but he did everything correctly - http://forum.xda-developers.com/showthread.php?t=1378921
if he still has his goldcard.img is there a chance it would work in my phone? I've PM'd him asking if he still has it
FrakEarth said:
Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
Click to expand...
Click to collapse
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.
tpbklake said:
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.
Click to expand...
Click to collapse
Thanks, that's one problem down!
At present I have this RUU Europe Rom that won't load, and the T-MO UK ones still won't install either. I've installed ClockwordMod Recovery 5.0.2.0, so that's good, but I take it I still need a goldcard if I'm going to install a ROM that doesn't match my phone's carrier ID?
Is the reason these older T-Mobile ROMS won't install because of S-ON and the higher radio version number?
edit: by the way, cyanogenmod and similar ROMs appear to install with no errors in clockworkmod recovery but I don't think they are. If I load one of the RUU exes it shows the same 2.10.4 version number with no changes evident whatsoever.
Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium
gefilus said:
Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
I realise that now... I'm less concerned about rooting / getting full S-Off again and more concerned with just getting any working ROM at all onto the phone... as it seems the only ones that are probably going to work are T-Mobile ones, and the only available ROMs I can find are older - I may have to send this off to someone
So you cab get into fastboot?? If you can then use downgrading without HTC Dec unlocked bootloader, there is a post about this, try it should work and use misc_version to let phone thinks he is on older hboot and then use latest T-Mobile ruu. I hope and it should work.
Sent from my HTC Desire S using xda premium
i would do this:
unlock with htcdev.com
downgrade hboot to 0.98.0000
use revolutionary for s-off
change cid to supercid
relock bootloader again
and flash the ruu of youre dreams.
think this should do it
This worked for me in the same situation
http://forum.xda-developers.com/showthread.php?t=1443636
Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).
FrakEarth said:
Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).
Click to expand...
Click to collapse
Only if you left on USB dedebuging if it's off then sorry can't. Bet if its o n you can easy make him to boot into fastboot. Take a try, and you need to be installed sdk and adb tools on, PC. Try switch on phone put into USB and open terminal, write adb devices if it works there will show a list and HTXXXXXXXXXX something. If it so then adb reboot - bootloader or if you have custom recovery boot there. If don't anderstand look commands in Wikipedia about adb. Good luck
Sent from my HTC Desire S using xda premium
Okay guys, managed to get this sorted.
Firstly, I read that if you mounted /system from Clockwork mod that ADB commands work... well I didn't get to try that out, because something else worked.
One of the reason RUU updates were failing was because the bootloader was unlocked, when I relocked (fastboot oem lock) they started working again, but I was getting Carrier ID errors on the European RUUs and the T-Mobile ones were too old.
I decided to visit a friend who also has a Desire S and from his phone I was able to get the CID (card identification register) code from a smaller microSD card I have -- this was one I hadn't tried as a goldcard before, and I was unable to try without being able to get at the GoldCard Helper app on my phone... so after using his phone and writing down BOTH CIDs, I tried both and it worked -- I now have the phone updated fully using the European RUU.
I think my mistake the first time may have been copying the wrong CID from Goldcard Helper: if you press Menu > Copy Code it seems to copy the code from MMC1, whereas my SD card was clearly MMC2 -- so my goldcard.img was completely incorrect the first time I tried it. I don't know why the phone let me partially install the European RUU without a goldcard and almost brick the phone, but I suspect it was because I had the Revolutionary bootloader with S-OFF.
So in summary if you have this problem I would suggest borrowing an Android phone (any should work) to get the right goldcard CID needed and then try installing an RUU.
Many thanks to everyone who replied and tried to help me, you guys helped me exhaust every other possibility - and I appreciate it a lot! Thanks!
Im currently at the process of unlocking bootloader i ran a exploit and it is 1111 what ever cid.
After i do this htcdev and flash update.zip of super user for root.
How do i change my cid back to my original?
And i hope i didnt have to memorize what my cid what otherwise im crewed.
Thanks, Reason for this is i read around and people had issues with the side being 11111 like for updating the rom or omething like that i dont want to run into that problem afterwards. But if its not really needed please tell me that.
I believe, as long as you never take a OTA an stick with rooted Xda roms you'll be golden.
WR
Injected from My ViperXL
So this seems to be the closest existing thread to ask my question:
Is it possible to change the CID of a Rogers One X to Super CID after having the phone wiped? (No OS installed)
Long stupid story short: I have a Rogers One X, bootloader unlocked, TWRP, regular CID, (which I understand is my grand mistake stopping me from mounting /data, /cache, and /system in order to flash any roms), and no OS to run any of the posted exploits to change CID.
EVITA PVT SHIP S-On RL
HBoot-2.14.0000
Any help, advice, or cold-hard truth is greatly appreciated so I can get this shiny paper weight active again.
if you have twrp installed you should be able to mount the sdcard from recovery transfer the rom.zip over unmount and install a rom
jerrycoffman45 said:
if you have twrp installed you should be able to mount the sdcard from recovery transfer the rom.zip over unmount and install a rom
Click to expand...
Click to collapse
I can mount the sdcard, but every time I try to install a rom (Viper, Nocturnal, CM) it errors out trying to format /cache, /data and /system directories for the install. The terminal in TWRP says that it can't mount any of these volumes (even though I go into aroma file manager and ensure the read/write permissions are checked). The only remaining problem I can find is that I don't have Super CID which would give me access to those directories.
if you are on the most current version of twrp that is your problem there are a lot of problems with it go back to 2.3.3.0 http://techerrata.com/browse/twrp2/evita
Thanks for the quick responses! I've tried a bunch of those recovery versions (some the screen would't work), but they all come up with the same problem: rom installation gets hung up at the part where it wants to format the specific drives. And terminal still says it can't mount the same 3 directories
might need to ruu and start over
Just go S-off and that will stop any problems you may have with updating with a CID 11111111. No need to change the CID back to original.
I'd love to just S-off, but the problem is I don't have SuperCID and no OS to utilize any of the exploits to get it. Looks like starting over is my only option, now to just find the correct RUU as every one I've tried comes back with wrong carrier or ID errors. Thanks for the help!
sixalive said:
I'd love to just S-off, but the problem is I don't have SuperCID and no OS to utilize any of the exploits to get it. Looks like starting over is my only option, now to just find the correct RUU as every one I've tried comes back with wrong carrier or ID errors. Thanks for the help!
Click to expand...
Click to collapse
What is your CID now?
My CID is still the stock ROGER001 (HTCdev unlocked bootloader without changing it (boneheaded move I know now)), but last night while searching for that RUU I came across a ROM that worked for my build So now it's up and running.
Background story:
I was trying to unlock and s-off 1.73 at&t one x phone with 1.09 hboot so that i could install a custom rom... Having experience with some other phones I prepared myself, software, drivers and everything else and plunged into action... I successfully unlocked the phone using a compilation of tutorials since it's so old bootloader and all, as for root i'm not sure I actually managed to get it work, it complained most of the time of missing bin files although I flashed su through recovery again and it settled down. I couldn't s-off it in any of the way tutorials were suggesting, gathering that i would have to update with some newer RUU, so I quit and phone is still s-on. And then I did an incredibly stupid thing, i didn't do nandroid backup, i just wiped system and tried to flash a new rom to no avail... None of the roms won't get flashed, i tryed sense and cm based ones, i'm getting some partition error, something about 2,14 and 2,15, not sure since error reporting is not consistent... Now I'm stuck within recovery and bootloader, i'm unlocked but s-on, i can't flash system img through fastboot nor a custom rom through adb sideload it says that partition is too small.
So question is what am I to do? What is my safest way out? Should i try flashing RUU (the one that should be the original one 1.73.502) or could I run some newer RUU and which would be preferable? If I'm to run RUU 1.73, should I run it as an exe or should I try to flash it as a zip file? Does it matter that the phone is unlocked and s-on? Why won't the smaller cm roms flash, how small could the partition be and does it have something to do with android version (4.1, 4.2 etc)?
To get a working ROM on your phone you can download an old build of cm and flash that. The new builds require updated firmware but the older builds don't. Go here and download the bottom build (stable cm10), and you'll need to get the 4.1 gapps package from here.
Sent from my Evita
What recovery and version number? I have a feeling this is recovery related, more than anything.
Also, newer builds of CM10.2 require hboot 2.14 or 2.15, so that is probably what the error message you mentioned is about.
We should be able to get you back up in and running on the custom ROM of your choice. But if you do decide to go the RUU route, in order to run an RUU, you must relock the bootloader in fastboot. Then you should be able to run the RUU. 1.73 RUU is fine. DO NOT run the 3.18, as there is a bug where with SuperCID and S-on (and you now have both) will BRICK THE PHONE. But the 1.73 or 1.85 RUUs will be fine.
Run the RUU as an .exe. I don't see the point in extracting and running the ROM.zip. You would just be making the process harder than it should be, and also removing some of the safeguards, if I remember properly.
S-off should work on any hboot version. I believe I got s-off while on hboot 1.09.
I'm running twrp 2.5.0.0 recovery, is there newer version? It never crossed my mind that it could something to do with recovery, so I never looked it up... Perhaps I could change it, it's not like that's gonna ruin chance of restoring any previous backups i didn't make...But i'd rather update the phone's firmware just to get those hboot glitches off the way because it, i'm quite sure, obstructed the s-off process (i was getting few 9x errors during s-offing, mostly 99).
So I'd be safe running 1.85 RUU. Is there some other RUU you would recommend, preferably some which will make the whole process of rooting, SuperCIDing and s-offing easier?
Thank you for helping me out!
edit> I tried flashing oldest CM and it worked! Then, feeling safe and all, I flashed newest twrp recovery and then, to my utter amazement, it flashed other rom I was aiming for... So thanks, for that recovery tip, it saved me a lot of pain! Now all is left for me is to figure out that s-off thing...
Two years ago I had this phone and I wanted to flash. I did. I don't remember all the details of it, but I do know that someone on here helped me flash it and it ended up with a European(?) flash on it and I remember he helped me do something with the radio in order that it would take the flash. I also remember that the reason for the flash was so that TMO wouldn't charge me for tethering. In any case, here's the current situation. I sold the phone and the person came and said they were having issues... so I was trying to restore it to a TMOUS ROM. Eventually, I bricked it, and got the qualcom download mode issue. I found the thread on that on how to fix it, and I did. Now the phone boots to the recovery screen and does nothing else. I am unable to flash ANY of TMO's RUU's, some of the PG58IMG.zip files that I've been able to find all fail... very frustrating.
I followed another thread that talked about how to unlock the bootloader, which involved copying the Identifier Token and sending it in to HTC. I received the response, and ran the command and was successful in unlocking it. When the device rebooted, it even showed the Tmobile animated logo. When I go back into the boot loader, it now reads:
My bootloader screen reads as follows:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.27.0000
eMMC-boot
JAN 13 2012.17:33:34
Software info shows:
Android Version: 4.0.3
HTC Sense Version: 3.6
Software number: Blitz_2.0.0
Kernel: 3.0.16-gda3fdfc
[email protected]#1
Baseband version: 11.76A3504300U_11.24A.3504.31_M
Build Number 3.33.401.106 CL391535 release-keys
Browser version: WebKit/534.30
At this point, I would try any flash, any rom, any thing to get this phone working for the guy again. I am skittish about flashing anything from this point so I don't mess up and have to start all over somewhere. Can I flash something working from this point? Can I flash a TMO RUU from here?
I have the RUU_Pyramid_TMOUS_1.27.531.2_RADIO_10.42.9007.00P_10.11.9007.15_M_release_192098_signed.exe as well as several others. Id' rather put this phone onto something stock from tmo but will do a custom as long as the phone is restored to working order.
I won't say I'm a newb... but having been away from flashing for a while, I could really use some step by steps to get going again.
The computer I am using to flash with is a Windows XP machine with all the HTC drivers working etc.
**** UPDATE ****
The phone now boots up as it did when this all started. After I did the token thing and got the bin file from HTC, I applied it and the result was the boot loader info above. It got past the tmobile animated logo and actually into the phone starting up as new including applying all the settings I want. Awesome that the phone now functions like a phone again, but I would still like to flash an official TMO Rom to it to restore it back to like out of the box condition. Any help is appreciated.
read this thread
http://forum.xda-developers.com/showthread.php?t=1672425
rzr86 said:
read this thread
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
I actually have read that... like 6 times to make sure I'm not missing anything. I do remember having to flash the radio back when I did my original flashing, and I think that process is preventing me from using any of the RUU's that I find. Are there any posts/files/resources that will help me flash the radio back to its default, so that I can then flash the RUU?
Also, I am S-ON already, but ANY RUU that I try to flash fails. Do I need to go to S-OFF and then RUU, then back to S-ON?
sc.lord said:
I actually have read that... like 6 times to make sure I'm not missing anything. I do remember having to flash the radio back when I did my original flashing, and I think that process is preventing me from using any of the RUU's that I find. Are there any posts/files/resources that will help me flash the radio back to its default, so that I can then flash the RUU?
Also, I am S-ON already, but ANY RUU that I try to flash fails. Do I need to go to S-OFF and then RUU, then back to S-ON?
Click to expand...
Click to collapse
no you don't need S-OFF
post your cid
rzr86 said:
no you don't need S-OFF
post your cid
Click to expand...
Click to collapse
CID is 11111111
I think I have it licked now.
Used the universal firmware and the viper 5.2.1 flash and it loaded just fine. Never got S-OFF on it, but the viper flash so far is working excellent.
sc.lord said:
CID is 11111111
I think I have it licked now.
Used the universal firmware and the viper 5.2.1 flash and it loaded just fine. Never got S-OFF on it, but the viper flash so far is working excellent.
Click to expand...
Click to collapse
how do you have supercid with S-ON?
also how did you flashed the universal firmware while on S-ON?
those two things can be done only on S-OFF
rzr86 said:
how do you have supercid with S-ON?
also how did you flashed the universal firmware while on S-ON?
those two things can be done only on S-OFF
Click to expand...
Click to collapse
Wish I could tell you.... hence the reason for the original help request.
I can tell you that I hit softbrick on it once and had to unbrick in linux.
Then I got the LOCKED with Security Warning. Then I got the unlock bin file from HTC Dev, used that and got back to UNLOCKED, with no security warning. Then I tried Rumunner without any success at all, stayed S-ON.
in any case, after trying just about everything I could think of, I found the viper post, saw that you said you don't need S-OFF to flash new rom... so i gave it a shot. Updated EXT, flashed the firmware, then the rom and it all went very smoothly. Phone's been working fine since. <shrug>