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.
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.
It's a stupid guide for noob as me...
I've spent much time reading these pages to find what i need to revert and use OTA update.
To revert stock rom, following this simple step:
1) download the ruu of your htc
http://forum.xda-developers.com/showthread.php?p=24886181#post24886181
2) run the ruu and waiting it finish
note:
if you previously don't change anything on system partition (for example you don't cancel any application in system\data whit root privileges) you can run the execute the .exe file and wait it finish.
Otherwise you must flash from recovery a stock nand backup ((for example, if you have the 153.x.x... you can download from this http://forum.xda-developers.com/showpost.php?p=24886181&postcount=18the cmw stock backup) to comeback to the originary size partition and run RUU
I'm sorry for my poor english but I hope it is clear and hope this post has not violated terms of section...
Moved To General
Thanks for the post, but this is best off in the general section, as its not really development.
I downloaded the 1.53 RUU and it just wouldnt work for me. I also flashed the image you provided. Coming from Virtuous. Really odd.....
The Jones said:
I downloaded the 1.53 RUU and it just wouldnt work for me. I also flashed the image you provided. Coming from Virtuous. Really odd.....
Click to expand...
Click to collapse
at the end i had got a old nand backup of untouched rom stock and after this restore and reflashed original recovery (but i think it isn't really necessary), the execution of ruu finished without problems.
I think it gets error if we have supersu too, because it modifies the file system space..
I tried that as well and the ruu refused to work. I am re downloading the ruu to aee what happens.
Sent from my HTC One S using XDA
The ruu you had downloaded is correct to me.. try to verify if your CID is present in android.txt (you must enter in temporary directory where ruu put his files, open rom.zip and verify is your CID is present..). Try this, in case you can add it.
i'm sorry for my poor english... i hope it's clear ;-)
nascio said:
The ruu you had downloaded is correct to me.. try to verify if your CID is present in android.txt (you must enter in temporary directory where ruu put his files, open rom.zip and verify is your CID is present..). Try this, in case you can add it.
i'm sorry for my poor english... i hope it's clear ;-)
Click to expand...
Click to collapse
Thanks. I did look for this and it is in there. I got the CID out of some fastboot command that I cant remember now.
The Jones said:
Thanks. I did look for this and it is in there. I got the CID out of some fastboot command that I cant remember now.
Click to expand...
Click to collapse
fastboot command is this: fastboot getvar cid
i need serious help!
i try evertything...i try to flash stock cmw flashable rom,flash the original recovery and try ruu....nothing....the best i can get it's after sending the update say sometingh like "invalid id client"....
i search CID and is VODAP102...someone can help me to restore to stock????? PLEASE!!!
and many thanks
You try to flash wrong version of RUU. I don't know if it's the case here, I do not own the device (yet )but I had a similar problem with my old incredible s. As it turned out RUU didn't match my MODEL-ID. Every htc-device has its model-id, but for some reason there is always released a batch with different model-id (So it was with Incredible S provided by Bell Canada. While almost the whole world enjoyed PG3213000, phones from Bell had model ID- PG3212000, and they needed their own special RUU.)
I'm from Europe but used XTC-clip to unlock bootloader and during this procedure I accidentally changed model-id from PG3213000 too PG3212000. That's why I was unable to flash any WWE RUU ( error [130] model ID error). Once I re-changed model-id (with the same xtc clip) my all problems were gone.
Everything that I need now is RUU 1.78.401.2.
gimmyxx said:
i need serious help!
i try evertything...i try to flash stock cmw flashable rom,flash the original recovery and try ruu....nothing....the best i can get it's after sending the update say sometingh like "invalid id client"....
i search CID and is VODAP102...someone can help me to restore to stock????? PLEASE!!!
and many thanks
Click to expand...
Click to collapse
I need that too.... thanks to who ever made it
chrisrudolf said:
I need that too.... thanks to who ever made it
Click to expand...
Click to collapse
you can try to add manually your CID in android.txt file inside rom.zip (in ruu temporary directory)
In ruu it didn't work, i tried it.
i hear voices in my head
i find it hard to restore my one s because there is no official RUU for my one s c2,i failed to s-off aswel to use older RUU that i have so i found out that you can still restore your rom to stock after using custom roms..this method is tested and working (but me reminded to always have nandroid back up and use it at your own risk)
1st step: download a OTA update,in my case i download ASIA WWE 3.17.707.102 (it is in a zip form): you can find yours here http://splanet.info
or you can obtain it form any other source
2nd step: once you have the zip file open it and extract the firmware.zip (put it beside the fastboot.exe or inside the folder where adb and fastboot is)
now before proceeding to next step you need to verify first your CID
To Get the CID of your phone: reboot the phone in bootloader/fastboot mode (adb reboot bootloader), and use fastboot getvar cid. Match this in the android-info.txt file found inside the firmware.zip file. If it doesn’t match, don’t go any further.
**************If you’re still here, I guess your CID matched.*******************
now we will need tools like notepadc++ and 7zip
3rd step: Now, in the OTA zip file, find the file updater-script in the directory META-INF/com/google/android. In this we’ll need to remove some code that doesn’t work with recoveries other than the default HTC ones. (extract the updater-script)
then Open the file with any decent text editor that preserves newlines (for windows, Notepad++ springs to mind, on Linux/Mac just use vi), and look for a textblock like this:
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__044") == "t");
);
delete that line.. then save it. after that delete the update-script inside the OTA (located in META-INF/com/google/android.) after deleting copy the new updater-script that we have just edited to the same directory where you delete the old updater-script..
4th step: Next, reboot your phone into Clockworkdmod Recovery (or whatever recovery you have installed), make a nandroid backup of your phone, and copy the OTA zip file on the phone. As a safety measure, it’s recommended to make a backup of everything on the SD storage to your computer.
5th step: When the backups are completed, reboot your phone into bootloader/fastboot mode. It’s time to lock the bootloader again, so we can flash the firmware update. This can be done using the command fastboot oem lock. Your phone will reboot.
6th step: Reboot it once again, this time to OEM update mode: adb reboot oem-78
7th step: Flash the firmware update: fastboot flash zip firmware.zip. If this complains without getting you a green progressbar on the screen, try it again – the second time it usually sticks.(even if it fails the the 4th time around just try and try it)
Once this process completes, reboot the phone again in the new bootloader: fastboot reboot-bootloader.
Now you can unlock your bootloader again, using the Unlock_Code.bin file you got from htcdev.com: fastboot flash unlocktoken Unlock_Code.bin.
At this point, you’d sure as hell wish you’d made a backup, if you didn’t. Because now your phone is wiped, reset to factory default. Don’t say I didn’t warn you upfront.
8th step: After the reboot finishes, you can once again boot in booloader/fastboot mode, and flash your recovery anew. For Clockworkdmod Recovery, the command is fastboot flash recovery <filename.img> Now you can boot the phone in the recovery (select the option from the bootloader menu).
9th step: Once in the recovery, it’s time to restore your nandroid backup. You did make one, did you?
If you finished restoring the backup, or you can now flash the OTA zip on the phone, updating the ROM to the new version or stock version.
After this, you just need to reboot one more time, this time to the ROM itself. Let it finish upgrading all applications, and tadaa, your freshly upgraded phone.
This worked for me, might not work for you. No promises.
this tut i found is for the one x but i made a one s version (villec2) which works.. so have fun and restore your device to stock....
Hope This Helps...
if you like this feel free to like and thanks me
ps: sorry for really bad english
-- xander
Would it work as an update for phone which doesn't "see" the OTA update and cheating recovery by placing the OTA as update.zip on phone's memory doesn't work either?
xQrzy said:
Would it work as an update for phone which doesn't "see" the OTA update and cheating recovery by placing the OTA as update.zip on phone's memory doesn't work either?
Click to expand...
Click to collapse
hello mate,
ive tried before but it didnt work,you really have to do the stuff,but incase your one s is in different status it will be different..for mine im still s-on
and the ota rom will only work for the firmware .zip that is inside the ota which you will have to manually flash..
Hi xander1993,
I am sorry to bother you but your answer is not clear to me
You say you tried it but didn't work and just after that you write I have to do the stuff
So let's clarify my situation and then I will wait for your answer:
I am currently using TD6 because I could not update to JB using OTA. My HBOOT now is 2.11.
I did go back to stock 4.0.4 (by RUU, my CID is HTC__032) several times, tried OTA, but no result.
Then I tried (also several times) to download the OTA zip file from splanet, place it on phone and reboot to stock recovery - every time it was showing me first a pgone with green arrows shaping to a circle and one arrow inside the circle and after several seconds it was a phone with red triangle with an exclamation mark - at this stage I had to wait few minutes for reboot every time. No effect.
So my question is:
Will your guide help me to get just update from 4.0.4 to JB?
xQrzy said:
Hi xander1993,
I am sorry to bother you but your answer is not clear to me
You say you tried it but didn't work and just after that you write I have to do the stuff
So let's clarify my situation and then I will wait for your answer:
I am currently using TD6 because I could not update to JB using OTA. My HBOOT now is 2.11.
I did go back to stock 4.0.4 (by RUU, my CID is HTC__032) several times, tried OTA, but no result.
Then I tried (also several times) to download the OTA zip file from splanet, place it on phone and reboot to stock recovery - every time it was showing me first a pgone with green arrows shaping to a circle and one arrow inside the circle and after several seconds it was a phone with red triangle with an exclamation mark - at this stage I had to wait few minutes for reboot every time. No effect.
So my question is:
Will your guide help me to get just update from 4.0.4 to JB?
Click to expand...
Click to collapse
okay now i got your question my guide is about s-on devices restoring to jelly bean stockbecause s3 version havent got any RUU,all the RUU i found is ICS so i made this to restore back to stock,so in your situation you are still in ics? are you s-off? or s-on? and do you have the bootloader unlocked?
i can help you to update to jb with the OTA just find your OTA that matches your phones CID and MID,
after that you will need to have custom recovery like twrprecovery
then just follow my post above start 2nd step... i will wait for your reply...
As I mentioned above I am on TD6 now (TrickDroid 6), HOS S3, ICS base, S-ON (there is no S-OFF for S3 ), bootloader unlocked.
Hmm, what is MID? I haven't heard of it before..
I will follow your guide once I get an answer for this simple question
AW: (GUIDE) RESTORE JB HBOOT 3.06 TO STOCK AFTER CUSTOM ROM ONE S C2 (villec2) !!
I have a One s with cid vodap102 and Android 4.0.3 can i Flash on this way Android 4.1 Euro stock rom on my One s ?
Sent from my HTC One S using xda app-developers app
xantan said:
I have a One s with cid vodap102 and Android 4.0.3 can i Flash on this way Android 4.1 Euro stock rom on my One s ?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
u can try but most probably u cant
Make a backup before doing
AW: (GUIDE) RESTORE JB HBOOT 3.06 TO STOCK AFTER CUSTOM ROM ONE S C2 (villec2) !!
Im testing this
Sent from my HTC One S using xda app-developers app
Yes it will work because this method is also tricking the custom recovery so that ota can be installed
Sent from my HTC One S using xda app-developers app
Mid is the model of device so if yours is one s s3 don't worry about mid,
Sent from my HTC One S using xda app-developers app
Yes you can it update you to 4.1.1 just download the right ota for your device specifically the right ota for your cid
Sent from my HTC One S using xda app-developers app
I read the guide and I barely understood how it works, but my question would be this:
Im on CID BSTAR301 (yeah, Latinamerican fked up CID stuck on 4.0.3) and if I change some of the code of a RUU.zip file (with other updated CID), would it work on my device? Is there any way to cheat the RUU to make it work on others CID? I think this could be possible, it's just some editable files, I hope this could work because I don't wanna be stuck on 4.0.3 while others Villec2 are with official JB
krlwarrior said:
I read the guide and I barely understood how it works, but my question would be this:
Im on CID BSTAR301 (yeah, Latinamerican fked up CID stuck on 4.0.3) and if I change some of the code of a RUU.zip file (with other updated CID), would it work on my device? Is there any way to cheat the RUU to make it work on others CID? I think this could be possible, it's just some editable files, I hope this could work because I don't wanna be stuck on 4.0.3 while others Villec2 are with official JB
Click to expand...
Click to collapse
sorry i am bad in english...but the method up is working...ill help you..first download your OTA for your CID..then tell me when you got it
you can find yours here http://splanet.info/
The problem is that my CID is not in the list, BSTAR301... I want to use other RUU because there is no RUU for my CID Can we cheat on other RUU file?
krlwarrior said:
The problem is that my CID is not in the list, BSTAR301... I want to use other RUU because there is no RUU for my CID Can we cheat on other RUU file?
Click to expand...
Click to collapse
no you cant cheat the RUU but can cheat the OTA update,even if you dont have the the correct OTA it will install but first you need to be unlock via HTCDEV and you got to have twrp custom recovery
When trying to flash the firmware, mine says "remote: 44 hboot version check fail" I have hboot 3.01.0000 :| Any ideea why?
bubert said:
When trying to flash the firmware, mine says "remote: 44 hboot version check fail" I have hboot 3.01.0000 :| Any ideea why?
Click to expand...
Click to collapse
you are not htc dev unlocked?
HTC One S Arabic JB update
Hi,
I bought an HTC One S from Dubai(Arabic Region) and I am using it in India right now. I have not yet received the JB update for the phone.
I was able to find the OTA files for the JB Update to the One S for the Arabic Region here -
splanet.info/
My CID is HTC_J15 as given by the CID Getter app.
I booted into the bootloader and got the following information -
***Locked***
VilleC2 PVT SHIP S-ON RL
HBOOT-2.09.0001
RADIO-16.05.20.24_M
OpenDSP-v05.6.0.2226.00.0418
eMMC-boot
May 10 2012, 17:19:49
This was followed by the HBoot, FastBoot, Recovery. Factory Rset, SIMLock, Image CRC and Show BarCode options.
Can you guide me as to how I can install the JB update?
Please bear with me as I am a noob.
Thanks.
sshray said:
Hi,
I bought an HTC One S from Dubai(Arabic Region) and I am using it in India right now. I have not yet received the JB update for the phone.
I was able to find the OTA files for the JB Update to the One S for the Arabic Region here -
splanet.info/
My CID is HTC_J15 as given by the CID Getter app.
I booted into the bootloader and got the following information -
***Locked***
VilleC2 PVT SHIP S-ON RL
HBOOT-2.09.0001
RADIO-16.05.20.24_M
OpenDSP-v05.6.0.2226.00.0418
eMMC-boot
May 10 2012, 17:19:49
This was followed by the HBoot, FastBoot, Recovery. Factory Rset, SIMLock, Image CRC and Show BarCode options.
Can you guide me as to how I can install the JB update?
Please bear with me as I am a noob.
Thanks.
Click to expand...
Click to collapse
first thing first you need to have htc dev unlock boot loader http://www.htcdev.com/bootloader select "all other supported models" then follow the on screen instruction then after that go back here....
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Flashing boot.img did not work. I'm in bootloop hell.
mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I thought so.....hboot 1.12......
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
Good catch Timmaaa!
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
****, what's my original CID, I didn't write it down?
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
ted77usa said:
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
I thought so.....hboot 1.12......
Click to expand...
Click to collapse
No I have "Android Debug Bridge version 1.0.31".
Ah ok, that makes more sense! Are you absolutely sure the ROM you're flashing is an Evita ROM? Where did you download it and what is the full filename?
You said the phone was s-on but not anymore? Why did you return it to s-on? You're gonna need to get s-off again so you can RUU up to 3.18 so you can flash the recent aosp ROMs. When you get the error 99 after flashing the zip, just force a reboot back to bootloader by holding volume down and power together. Once you're back in bootloader you can start again (without the adb reboot bootloader command because you're already in bootloader) and you should get error 92 now. Now, before you give the adb soffbin commands you need to make sure the screen is unlocked and stays unlocked, also make sure usb debugging is enabled in developer options. If it's an aosp ROM you'll also need to grant root access to adb in developer options.
For now my suggestion would be to download a Sense ROM, preferably Android 4.0 or 4.1, this should at least boot and enable you to get s-off on your phone again. Don't forget top flash the boot.img via fastboot.
Sent from my Evita
---------- Post added at 07:27 PM ---------- Previous post was at 07:25 PM ----------
mollysue said:
No I have "Android Debug Bridge version 1.0.31".
Click to expand...
Click to collapse
Your adb version is fine, you can leave that the way it is.
Sent from my Evita
mollysue said:
****, what's my original CID, I didn't write it down?
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012
Click to expand...
Click to collapse
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.
mollysue said:
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.
Click to expand...
Click to collapse
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE
ted77usa said:
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
Thanks!!!! The rom worked. I'm going to let it sit for a while before doing any more tampering. At least I have a working phone *happy dance*