Related
Right, had desire s from three, alpharevx'd it installed clockwork mod, flashed eng hboot. Tried to flash RUU 1.47 europe on it, and it started to work and go through process, updated radio fine, then came up with CID error. No option to do anything but exit. Now I have a desire s that will boot into Bootloader, which has now s-on'd itself and upgraded to 0.98.0002.
Only method of comms seems to be via fastboot.
Now i cant flash the h3g one cos its too low a bootloader version, and i cant upgrade to a newer version cos one don't exist. Can anyone come up with a solution please??
Cheers.
What does HBOOT screen say (in full)?
Are you still able to get into recovery? If yes, then have you tried loading a custom ROM onto the SD card and simply flashing that using the flash zip from sd card option of CWM (clock work mod)?
Unfortunately I am unable to get into recovery, only bootloader, nothing else works. Hboot is displaying a security error at the top highlighted in pink, followed by the version number as described
You should have stuck with the alpharev hboot, which does not allow itself to be overwritten by RUU installs.
Anyway, you need to:
- install hboot 0.980000 (so you can run alpharevx again and get S-OFF)
- run alpharevx and reinstall CWM at the end
- DO NOT install the eng hboot
- flash whatever rom whichever way you want. Your hboot is safe
Follow the instructions on:
http://forum.xda-developers.com/showthread.php?t=1187231
How can I run alpharevx when I can only boot into bootloader tho?
Try running it while in bootloader. Never tryed it that way, but I'm pretty sure it only needs the USB comms to be up, same as adb. Which they should be anyway in bootloader...
Have you tried to re-setup your phone by executing one of the RUU.exe?
k, as i expected, with no access to adb in bootloader mode, i am unable to do anything. Remember, i only have bootloader to work from. I don't eve3n have a recovery partition installed, it just comes back to bootloader whatever i choose, well, bootloader and fastboot anyway.
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
If all else fails s-off with xtc clip then flash custom rom
Sent from my HTC Desire S using XDA Premium App
Have you tried to use the original RUU for your phone/network? I'm not sure if it would take care of the CID error.
Any of these:
http://forum.xda-developers.com/showthread.php?t=1002506
Clivectmob said:
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
Click to expand...
Click to collapse
I do not expect this to work, but you said you are able to get into recovery, correct?
Well, I would try to enter fastboot mode and try to flash cwm via fastboot -> fastboot flash recovery XXXXXXXX.img
Correct (windows) drivers installed?
Edit:
lowveld said:
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
Click to expand...
Click to collapse
Good suggestion! Try this one first.
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
I haven't run a RUU in years, but I think that when you run it on a windows machine, it extracts a bunch of files to a directory. Cancel the process, find the directory, find th PG88... in the directory... You get the drift.
Clivectmob said:
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
Click to expand...
Click to collapse
It is not relevant which network you are using !!! Just try newest RUU to get control over your phone again in the first place!
Even if you don't get any network access after setup newest RUU you will definitely be abte to execute alpharevx again, flash cwm and flash any stuff you want to.
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Clivectmob said:
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Click to expand...
Click to collapse
I guess that means you tried flashing recovery via fastboot?
Then concentrate on our RUU-suggestions.
Yes, as i said, flashed via fastboot, and i already explained that i cant up/down grade via ruu method because of bootloader version. I can't think of a way out of this as it stands. The only thing that may work is doing it via the p88img method with my original 3uk rom, but i cant find it in my temp files, searched everywhere for it. I've seen it's location posted on here before now, and i've searched it to death and can't seem to find it now
I'm going to extract and upload your 3GUK-PG88*.img although I think you'll need an newer one. Just a few minutes of patience.
Last night I flashed the gingerbread coredroid ROM and it worked fine. I just didn't really like the looks of some things, so I thought I'd change to a different ROM.
I thought about flashing the ICS Insertcoin ROM, so I flashed it, and it kept trying to boot, but turned off and kept repeating. But then I read that I was supposed to update the firmware, so I took out the SIM card and connected it to the computer and copied the 3.24 RUU to the SD card.
I followed the instructions and the RUU set up properly through HBoot the first time. Then i went in to recovery to wipe data. It had to reboot the phone before I did anything else, and it went back into HBOOT and tried to install the RUU again, but this time it failed due to CID being incorrect! I didn't give it a second thought, but then the insertcoin ROM was doing the same thing, going through the boot up images and shutting off right in the middle, and repeating.
I tried another ICS ROM, Android Revolution, and same result. Failed booting. Then I tried restoring my nandroid backup from before coredroid, and it also kept trying to boot and then shut down. Then I tried coredroid again, and it had the same reaction, failed booting! I redownloaded the ICS RUU 4 times and repeated this process 4 different times, even with other GB versions of insertcoin and ARHD, and no dice!
I'm not entirely tech savvy, so maybe there is soemthing I havent covered yet. Now the RUU fails not because of CID, but because of incorrect Model ID. I read about goldcards, but I can't make a new one because the phone won't even boot! Please help me!
edit: as of now, the phone does not turn on to any rom or homescreen, ONLY Hboot and recovery.
Hello Jagerlowe,
The 3.24 RUU installs fully with 2 Boots into Bootloader, so there is nothing to be worried about. Here's how you could solve your problem.
1. Please follow step 4 from this Guide to obtain SuperCID, make sure that the SuperCID is 11111111! Mismatch of the SUPERCID causes the Error you were previously facing.
2. With the updated SuperCID, reinstall the latest ARHD 6.2.1 ROM.
3. Boot & flash the suggested radio if you are using the ARHD ROM.
You should be alright
Please keep me posted about your problem and hope it helped!
Remember to Thank me!
CursedBat said:
Hello Jagerlowe,
The 3.24 RUU installs fully with 2 Boots into Bootloader, so there is nothing to be worried about. Here's how you could solve your problem.
1. Please follow step 4 from this Guide to obtain SuperCID, make sure that the SuperCID is 11111111! Mismatch of the SUPERCID causes the Error you were previously facing.
2. With the updated SuperCID, reinstall the latest ARHD 6.2.1 ROM.
3. Boot & flash the suggested radio if you are using the ARHD ROM.
You should be alright
Please keep me posted about your problem and hope it helped!
Remember to Thank me!
Click to expand...
Click to collapse
I can't quite do that because the phone doesn't turn on. It goes to the boot screen then shuts off. Then turns on, boot screen, off again. So I can't connect it to the computer or do anything like that.
This thread might help you... ICS flashing is little bit different than GB...
http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation 4G with Beats
Jagerlowe said:
I can't quite do that because the phone doesn't turn on. It goes to the boot screen then shuts off. Then turns on, boot screen, off again. So I can't connect it to the computer or do anything like that.
Click to expand...
Click to collapse
Can you boot your device into Recovery mode?
Jagerlowe said:
Last night I flashed the gingerbread coredroid ROM and it worked fine. I just didn't really like the looks of some things, so I thought I'd change to a different ROM.
I thought about flashing the ICS Insertcoin ROM, so I flashed it, and it kept trying to boot, but turned off and kept repeating. But then I read that I was supposed to update the firmware, so I took out the SIM card and connected it to the computer and copied the 3.24 RUU to the SD card.
I followed the instructions and the RUU set up properly through HBoot the first time. Then i went in to recovery to wipe data. It had to reboot the phone before I did anything else, and it went back into HBOOT and tried to install the RUU again, but this time it failed due to CID being incorrect! I didn't give it a second thought, but then the insertcoin ROM was doing the same thing, going through the boot up images and shutting off right in the middle, and repeating.
I tried another ICS ROM, Android Revolution, and same result. Failed booting. Then I tried restoring my nandroid backup from before coredroid, and it also kept trying to boot and then shut down. Then I tried coredroid again, and it had the same reaction, failed booting! I redownloaded the ICS RUU 4 times and repeated this process 4 different times, even with other GB versions of insertcoin and ARHD, and no dice!
I'm not entirely tech savvy, so maybe there is soemthing I havent covered yet. Now the RUU fails not because of CID, but because of incorrect Model ID. I read about goldcards, but I can't make a new one because the phone won't even boot! Please help me!
edit: as of now, the phone does not turn on to any rom or homescreen, ONLY Hboot and recovery.
Click to expand...
Click to collapse
did you solve this because i think im having the same issue as you
Mookie_Jones said:
did you solve this because i think im having the same issue as you
Click to expand...
Click to collapse
Can you boot your device into Recovery mode?
CursedBat said:
Can you boot your device into Recovery mode?
Click to expand...
Click to collapse
Yes, I can boot it into recovery and HBOOT, thats it.
Jagerlowe said:
Yes, I can boot it into recovery and HBOOT, thats it.
Click to expand...
Click to collapse
What I am about to guide you through is downgrading your HBoot.
Firstly, download 1.17RUU - CHOOSE WHICH Service Provider, Location (CHOOSE THE RIGHT ONE)
http://forum.xda-developers.com/showthread.php?t=1459767
1. Boot into recovery mode and connect your phone to your computer.
2. Select "mounts and storage"
3. Then select mount sd card.
4. Copy the PG58IMG.zip into the Root of your SD Card.
5. Reboot your phone into bootloader again.
Your phone should automatically prompt you to begin update. After the update,
Your Bootloader should be downgraded. Then Flash a simple - any Gingerbread based ROM, and follow my post on doing SuperCID
Goodluck! Cheers
CursedBat said:
What I am about to guide you through is downgrading your HBoot.
Firstly, download 1.17RUU - CHOOSE WHICH Service Provider, Location (CHOOSE THE RIGHT ONE)
http://forum.xda-developers.com/showthread.php?t=1459767
1. Boot into recovery mode and connect your phone to your computer.
2. Select "mounts and storage"
3. Then select mount sd card.
4. Copy the PG58IMG.zip into the Root of your SD Card.
5. Reboot your phone into bootloader again.
Your phone should automatically prompt you to begin update. After the update,
Your Bootloader should be downgraded. Then Flash a simple - any Gingerbread based ROM, and follow my post on doing SuperCID
Goodluck! Cheers
Click to expand...
Click to collapse
Oh my gosh! Can I like marry you!? You fixed my problem! Thank you so much!
Jagerlowe said:
Oh my gosh! Can I like marry you!? You fixed my problem! Thank you so much!
Click to expand...
Click to collapse
You're welcome I'm just glad to be of any use.
Good luck experimenting with ICS
Cheers!
Hey guys, So I initiated flash today and have come across a slight problem;
I followed the guides on here: http://forum.xda-developers.com/show...4#post21711154
and here: http://forum.xda-developers.com/show...php?p=21989107
I saw that the first thing to have done was install 4ext recovery. I followed the read me and tried the "adb reboot bootloader" but it kept saying device not found. Then I noticed I had it already in my phone, so I ran the backup and it said back up complete. So then I turned off the phone, rebooted into bootloader and waited for the update. However, it said "error invalid CID and can't update. Press power to reboot" It was the only option given. So then, I followed the guide on Kohr-Ah's page and took out the SD card, rebooted into bootloader, went to Recovery, ran superwipe and installed ARHD 6.5.1 with Beats Audio. After everything went done and well, it rebooted and turns on but once the beats logo completes its circle, it gets stuck on the beats page. I ran the wipe again, and reinstalled ARHD and still gives the same result. Any body know how I can solve it?
I also forgot to say that when I try to install the PG581IMG (the firmware) it says:
Finding update package...
Opening update package...
Installing update package...
Installation aborted.
Update: I cleared cache from 4ext, and reflashed the rom. After rebooting and passing the htc white screen, I'm at a black screen with "android" written across in metallic silver. It has a white flash pass pass through the whole writing. It's been like this for about 15 or so minutes.
your links are pointing no where...404 page not found, if you have a sensation and not a sensation XE your update zip should be called PG58IMG.zip not PG581IMG.zip
but really need to see where your links point to..
Did you flash the firmware for the rom - 3.32? If not this is the cause of the boot loop. Have you got s-off via revolutionary?
Sent from my HTC Pyramid using xda premium
Happened with me....Insert the SD card again which was inside when you flashed ARHD ROM....it will boot.....
Stringer, No I did not before doing the wipe. Something I realized I should have done after I had run Superwipe. But when I do run it it says installation aborted for some reason. I do have S-off via revolutionary. I'd gotten it done the first time when I flashed the custom rom, along with SuperCID.
Ali3nfr3ak, I made a mistake, I do have the PG58IMG file. Sorry bout the links, here they both are: 1) http://forum.xda-developers.com/showthread.php?t=1459767 and 2) http://forum.xda-developers.com/showthread.php?p=21989107
Mathrania: What do you mean reinsert the SD card? It is inserted, it has been so the whole time, but still gets stuck on the black screen with android on it.
I should put out my Revolutionary
PYRAMID PVt ship s-OFF RL
HBOOT-1.27.1100
RADIO- 10.12.9007.21_2M
eMMC-BOOT
I check the md5sum for the PG58IMG file and it gives the following
fea9240feef50554a17688dc2b1a7bac
However, when I check this page http://forum.xda-developers.com/showthread.php?t=1412618 that Mike linked for the firmware on his page, I can't file that md5sum nor the file itself. I see that the rom is based on Firmware 3.32.401.5 but I can't even find 5, on that page I see only up to "x" and "10x" that's it. Am I missing something?
I'm sorry for being persistent, but I really need the phone working and I've looked in as many places as I can find to see if some one else had the problem so that I could acquire some help that way. But alas, it came fruitless. Any and all help would be appreciated. I've wiped cache and dalvik cache, but still nothing. It now goes up to the beats screen but gets stuck on that screen.
Okay, lets go back to the basics.
Check everything, make sure you're super CID. You need to flash the correct firmware that the rom needed (go with the 3.32), then delete it from the sd card after flashing. Then, you should superwipe. Then flash the correct ARHD (make sure that you used the ICS one)
Sent from a revolutionized HTC Sensation ICS
tohfhu said:
Okay, lets go back to the basics.
Check everything, make sure you're super CID. You need to flash the correct firmware that the rom needed (go with the 3.32), then delete it from the sd card after flashing. Then, you should superwipe. Then flash the correct ARHD (make sure that you used the ICS one)
Sent from a revolutionized HTC Sensation ICS
Click to expand...
Click to collapse
I do remember having done super CID, however when I had the PG58IMG in there it would say "incorrect CID" and "update failed" at the bootloader main screen right after scanning and would tell me to "press power button to reboot." I'm not sure which version of the firmware I should have gotten, I have the hboot version 1.27.1100 and am seeing that the guides say to have 3.32.401.5 of the firmware but I couldn't find that version anywhere.
I did just as you said now, and it still got stuck on beats. It's as though it gets stuck right as it's about to load up.
sano1 said:
I do remember having done super CID, however when I had the PG58IMG in there it would say "incorrect CID" and "update failed" at the bootloader main screen right after scanning and would tell me to "press power button to reboot." I'm not sure which version of the firmware I should have gotten, I have the hboot version 1.27.1100 and am seeing that the guides say to have 3.32.401.5 of the firmware but I couldn't find that version anywhere.
I did just as you said now, and it still got stuck on beats. It's as though it gets stuck right as it's about to load up.
Click to expand...
Click to collapse
If its saying incorrect CID, then you're not on superCID, because when you are on super cid you can flash any firmware from any region or carrier (correct me if im wrong lol). Check the CID, make sure that its "11111111"
The firmware is in here. http://forum.xda-developers.com/showthread.php?t=1412618
Sent from revolutionized HTC Sensation ICS
tohfhu said:
If its saying incorrect CID, then you're not on superCID, because when you are on super cid you can flash any firmware from any region or carrier (correct me if im wrong lol). Check the CID, make sure that its "11111111"
The firmware is in here. http://forum.xda-developers.com/showthread.php?t=1412618
Sent from revolutionized HTC Sensation ICS
Click to expand...
Click to collapse
Well that makes sense. Now here's a wee bit of another problem. I can't get cmd to recognize my devices as as per the guide I need to go into usb charge mode, however I can't even get the phone to boot. I'm wondering now if I do a factory reset via bootloader or 4ext if it would reset the whole thing and get back my stock rom and all? As well as if it will delete anything backed up on to the SD card? I can superCID right after and then run the firmware as well as superwipe and ARHD
If any one's around and can help, please don't hesitate. I'm in a bit of a desperate situation as to the solution. May be if I can get the modelid and edit it into the notepad, that would work? Potentially? If there's an actual solution, even better.
Does boot loader work? If so boot that, select fastboot. Does PC recognise phone now?
EDIT: is recovery working?
Sent from my HTC Pyramid using xda premium
I went into fastboot and noticed it turn into FASTBOOT USB, I rebooted the system but still froze on the beats screen. Should I fastboot bootloader? PC wasn't recognizing phone at all. I think I should keep it in that fastboot USB menu and then play around with CMD, any thoughts? Recovery? Are you asking about Clockwork recovery? Or 4ext?
OK go back to boot loader, plug into PC and open cmd terminal as admin.
cd to whatever folder your fastboot driver is in and enter "fastboot devices". You should get device and serial no returned.
That shows PC recognises phone.
From there you can boot into recovery (yes CWM or EXT4), wipe everything, superCID, and flash fw/rom.
Sent from my HTC Pyramid using xda premium
stringer7 said:
OK go back to boot loader, plug into PC and open cmd terminal as admin.
cd to whatever folder your fastboot driver is in and enter "fastboot devices". You should get device and serial no returned.
That shows PC recognises phone.
From there you can boot into recovery (yes CWM or EXT4), wipe everything, superCID, and flash fw/rom.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
Thank you, sooo much. So what the reason it wasn't going into Fastboot USB was 1) I had the HTC sync software installed on another computer and not the current one, 2) I didn't have SuperCID but BM__001, and using the other computer I switched it to 11111111. I also was using "adb" as a command on CMD rather than "fastboot" I noticed Fastboot followed by command worked but with adb it wasn't finding the device.
SUCCESS! Phone's now operating. Many thanks to all those who contributed. All I have to do now is restore SMS back up as well as some data back up from 4ext. Should I redownload SMS back and restore to restore or should I do a 4ext restore first and then SMS?
Sorry I fell asleep yesterday, good to know that everything is fine now.
Regarding about you new question, well im not sure about that. Correct me if im wrong, 4ext copies an exact image of what your phone is before you flashed it. So when you recover through 4ext it will turn your phone back to the last rom you used. Im correct? lol
Sent from revolutionized HTC Sensation ICS
tohfhu said:
Sorry I fell asleep yesterday, good to know that everything is fine now.
Regarding about you new question, well im not sure about that. Correct me if im wrong, 4ext copies an exact image of what your phone is before you flashed it. So when you recover through 4ext it will turn your phone back to the last rom you used. Im correct? lol
Sent from revolutionized HTC Sensation ICS
Click to expand...
Click to collapse
That's quite alright. Actually what happened is I thought I need to go into 4ext and do a recovery, and did so only to brick the phone. SO I reflashed it and installed the ROM again only to find that 4ext automatically reinstalls all apps. It did and I was soo happy. As for my sms messages, I went back to sms back up and restore and restored them. All's well for me right now. Though I'm noticing some lag on the phone itself, in performance, and sending text messages. And especially in the music player.
followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
kirkcody said:
followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
Click to expand...
Click to collapse
That's a tough one to nail down. Below is the stock recovery from the 1.84 t-mobile OTA. Maybe flash that and try the clear storage option.
Also, you might try doing the the Mainver Fix in the all in one tool kit. It's an option in the box in the lower right hand corner.
https://dl.dropbox.com/s/g4r0ryvjy6oce9k/recovery.img?dl=1
Thankyou my friend ill give it a go
unfortunately that didn't work either...i don't know why this wont work for me
kirkcody said:
unfortunately that didn't work either...i don't know why this wont work for me
Click to expand...
Click to collapse
This same thing happened to me at some point. I would suggest just starting over and redoing all the steps.
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
If that doesn't work use a hammer and smash the thing =)
Actually instead of using a hammer I would change to super cid and use a different RUU that had the same hboot as the one your on.
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
@usaf22 really? Did that method work for you?(thought it may not work because we don't have s-off) Did it also remove the tampered and relocked banners? Thanks for both of you guys help will give it a go.
(Edit Hboot wont detect the PJ40IMG.zip )
usaff22 said:
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
No that won't work. Has it ever worked on the One S?
Didn't work Hboot didn't detect PJIMG.zip :crying:
kirkcody said:
Didn't work Hboot didn't detect PJIMG.zip :crying:
Click to expand...
Click to collapse
Did you try all this?
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
kirkcody said:
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
Click to expand...
Click to collapse
link no good-deleted
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Fixter said:
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Click to expand...
Click to collapse
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
dc211 said:
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
Click to expand...
Click to collapse
I got it working guys, but I know why. I was using the incorrect RUU. The link said it was the one for 1.83 but it was for the 1.5 version. I download it again and sure enough it's the 1.83 one. I guess I'm back to work now.
One question and this may save a big headache lol... did you LOCK your bootloader back? I had a couple RUU's that didn't work for me either, but I didn't follow the step of locking the bootloader I was just trying to flash over. Once I relocked I was good to go.
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
kirkcody said:
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
Click to expand...
Click to collapse
Your problem is that there is only 1 RUU you can use. Only 2 exist for T-mobile US and one you can't use because the hboot is lower then yours. But you're kinda lucky that a new OTA came out today. So a newer T-mobile US RUU should be out in a few days, that's normally how long it takes football to get them.
Here's a link to eh 1.83 RUU that should be fast. https://dl.dropbox.com/u/76257867/RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
Our you can try to get the OTA. You should be able to see it now if you check for software updates but it should fail to install. I saw you're using the 1.06es radio. You'd have to go back to the original radio, recovery, lock the booloader and factory reset. For it to work.
I know you should be able to get it working I was stuck where you're at but my Hboot also said "Security Warning" and RUU's & OTA's wouldn't run which I really haven't seen anyone else get.
Hey Everyone,
I just got a HTC ONE S for my girlfriend to replace her Alcatel OT997D.
Well, first thing I always do - guess what, root it and put a custom rom onto it.
It should be a S4 as it says vil in bootloader and not ville(C2).
And here is where the trouble starts:
1. I started with unlocking the bootloader (which is unlocked now)
2. I installed an recovery (TWRP)
3. I flashed the newest superuser onto it.
4. Somewhere in between I managed to upgrade Hboot to 2.15
So I tried countless stuff - I tried to use the all in one toolkit and tons of other programs to give it a super CID and switch it to S-OFF.
I really got (as far as I figured out) no chance to change the CID from T-MOB101 to 11111111 with the acutal H-Boot - further I can't use S-Off without SuperCID.
So for me right no it goes round and round and round in one big circle.
I also tried several tock-rom versions, I'm getting as far as it is pushed to the device and then the RUU ends with error 155.
I can use fastboot easily (just not "fastboot oem writecid 11111111" - this makes it stuck and I need to switch it off via 15 sec. holding power) and ADB sometimes - I can also use the HEX-Editor mode, but it does not recognize the SU command - so after bootup it stays with the old CID.
Could please anyone help me? Thank you so much!
Regards,
Matthias
I would re-lock the bootloader and install a matching RUU, then run Moonshine or one of the other S-OFF apps first. Then try your CID mods etc...
Others may have better solutions.
808phone said:
I would re-lock the bootloader and install a matching RUU, then run Moonshine or one of the other S-OFF apps first. Then try your CID mods etc...
Others may have better solutions.
Click to expand...
Click to collapse
I already tried it with relocking and stock recovery - the RUU update software always gives error 155, that means AFAIK it is not matching. But when I look inside the Android text, there is my CID listed.
I assume it is related to the hboot version which might is higher than in the RUU.
Regards,
Matthias
AFAIK, you can always go higher in the RUU version. So find an RUU with 2.15 that newer than what you have.
808phone said:
AFAIK, you can always go higher in the RUU version. So find an RUU with 2.15 that newer than what you have.
Click to expand...
Click to collapse
Hmm okay, I will try it! But what if there is no RUU with this version available? Do you have an idea where to find it?
Maeffjus said:
Hmm okay, I will try it! But what if there is no RUU with this version available? Do you have an idea where to find it?
Click to expand...
Click to collapse
Check this out:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
2.15 HBOOT is easily found.
http://www.androidruu.com/?developer=Ville
808phone said:
Check this out:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
2.15 HBOOT is easily found.
http://www.androidruu.com/?developer=Ville
Click to expand...
Click to collapse
Thank you so much!
But now the stupid question from me:
In which part mof the number can I figure out the Hboot?
(in the second link)
And there is only one rom which seems to be compatible with the T-Mob101 - can I flash any other?!
(otherwise where to find a suitable one?)
CHANGE OF PLANS! Check out this:
https://drive.google.com/folderview?id=0B1IYElPvrGZrdGR6SXIwYjgxd1U&usp=sharing
the thread:
http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Someone posted the TWRP NANDROID backup for your phone I believe. So put TWRP on your phone and do a full wipe (Dalvik, cache, system, factory reset) in TWRP and then restore with the NANDROID.
I believe you should be able to use the MOUNT command in TWRP to copy the NANDROID backup onto the sdcard.
I hope someone jumps in here. I know you are not S-OFF so I'm hoping that the NANDROID will work. Otherwise you might have to try some of the RUU that the thread lists.
I guess it's also possible for you to install TWRP and actually try installing another type of ROM like CM11 and then flash the boot.img. Honestly I'm not sure what I would do because there are several choices.
Sounds great - I will try this maybe tomorrow - or in 9 daysw, I going on vacation to Spain tomorrow - so my GF might has to use her old Alcatel
But anyway, I will keep you updated as soon as I got news!
UPDATE: Its writing the backup to the system - I'm trying the newer one first ( - 2013-04-19--08-30-59_tmo_de_stock_3.16.111.7.zip
T-Mobile Germany stock JB, upgraded from 2.38. CID T-MOB101.)... okay REBOOT...
Hmm weird - the screen turned black For some reason I heard some sound before it turned black...
Very weird, I left it with the black screen an somehow I partially hear the Tmobile sound and sometimes later the full sound...
Last thing: I wiped Dalvik, cache, system, and android secure - was this enough (there is not option to wipe "factory reset" but that all I found for wiping a factory factory reset.
Awesome! Have a nice trip!
Thank you so so so much! It finally boots up with the older backup (of the two suitable)!
You are great!
Maeffjus said:
Thank you so so so much! It finally boots up with the older backup (of the two suitable)!
You are great!
Click to expand...
Click to collapse
WOW! Great! Now you can use the phone on the trip!
808phone said:
WOW! Great! Now you can use the phone on the trip!
Click to expand...
Click to collapse
Lets see if my GF likes to configure it on the way to the airport
But right now I'm doing what I had forgotten last time - I goind to make it S-OFF with moonshine - for the superCID I'll see afterwards - after all of this is done, I might flash a new rom
UPDATE - does it always take such long? Look at the attachement - I'm not sure if there is everything okay. But I don't want to unplug the phone from USB - I'm scared to brick it (again).
Maeffjus said:
Lets see if my GF likes to configure it on the way to the airport
But right now I'm doing what I had forgotten last time - I goind to make it S-OFF with moonshine - for the superCID I'll see afterwards - after all of this is done, I might flash a new rom
UPDATE - does it always take such long? Look at the attachement - I'm not sure if there is everything okay. But I don't want to unplug the phone from USB - I'm scared to brick it (again).
Click to expand...
Click to collapse
Okay, I unplugged it - did not work - I'm already here with the "older version" (2.38.111.10) - The OTA does not work, I tried it with TWRP, did not work.
Then I restored the stock recovery and also locked it - did also not work, I always get the triangle with the exclamation mark. (The device says relocked and tampered).
So the very last thing I tried was to copy it back from the SD to my pc and used "fastboot oem rebootRUU" and "fastboot install zip" - it now says:
FAILED (remote: 44 hboot version check fail)
And very last thing - I can't make it CID 11111111 or S-OFF, so - how to go on?
But no rush, tomorrow I'm away for some days
Regards & Thanks!
oh no.
If you can get to the boot loader and fastboot USB. I guess you should try and run an RUU (newer) for your phone. You need to get it back to some type of stock condition.
808phone said:
oh no.
If you can get to the boot loader and fastboot USB. I guess you should try and run an RUU (newer) for your phone. You need to get it back to some type of stock condition.
Click to expand...
Click to collapse
I tried it - but the problem is, the only RUU I got / found is RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed
The next available version is an OTA upgrade which I can not install anyway - so any suggestions? I can lock and unlock it and I got it "tampered" and with HBoot 2.15...
So what exactly is the phone doing now? Is it stuck in a boot loop?
Did you try and restore with TRWP? What if you do a wipe (Full wipe (Dalvik Cache, Cache, System, Factory Data Reset)) in TWRP, and try to restore from TWRP NANDROID?
808phone said:
So what exactly is the phone doing now? Is it stuck in a boot loop?
Did you try and restore with TRWP? What if you do a wipe (Full wipe (Dalvik Cache, Cache, System, Factory Data Reset)) in TWRP, and try to restore from TWRP NANDROID?
Click to expand...
Click to collapse
It boots up flawlessly - but only in the older backup (from the link you gave me - its ver.2.38.111.10).
With the newer version it stucks in bootloop.
And after I installed this, I'm not able to: flash any other rom on top of it or perform the OTA update (when it starts, it notifies me that the OTA is available for download and I can download it also).
(Yes, I installed stock recovery to use the OTA).
So you are running fine with the older ROM? Why not leave it? If you really want to try something different, here's a plan.
In the thread I sent you:
http://forum.xda-developers.com/showthread.php?t=2192964&page=2
These guys all have your same phone/ROM. PM them and ask them if they have found a newer RUU to run that is compatible with an S-OFF method. Or ask any of them if they have gotten S-OFF with their devices. If not, then just stay on the current ROM. If someone has gotten S-OFF, then you can decide to pursue that course. Good luck!