Database Info

[Q] Flashing EU based ROMs on USA TMO One S?

I thought I had read somewhere around here that there was an issue with the EU based ROMs on a TMO USA One S. I can't seem to find where I read that anymore, am I remembering correctly? If so what are the issues involved?
Thanks!

agentc13 said:
I thought I had read somewhere around here that there was an issue with the EU based ROMs on a TMO USA One S. I can't seem to find where I read that anymore, am I remembering correctly? If so what are the issues involved?
Thanks!
Click to expand...
Click to collapse
Not really any issue between the two. T-Mobile just retards the animation of the network popping from 3g to 4g as to where the euro version displays it a little more accurately. Sol safe to flash. I'm on a euro Rom now and my phone is US version. Flash away.
Sent from my HOS

jmercil said:
Not really any issue between the two. T-Mobile just retards the animation of the network popping from 3g to 4g as to where the euro version displays it a little more accurately. Sol safe to flash. I'm on a euro Rom now and my phone is US version. Flash away.
Sent from my HOS
Click to expand...
Click to collapse
Thanks!

I'm not sure if this is really need but while using a eu rom, I also download morelocale2 and faster fix GPS.
Sent from my HTC One S using xda premium

I tried flashing several of the EU roms on my US phone (RUU), and they all error out with error 155. I changed the mid in the android-info.txt file but still the same error.
Someone in a different thread stated that this only works with S-Off. Is that correct, and if so, how do I do it?
Thanks
-J

if you flash the RUU in fastboot you shouldnt get the 155error

azzledazzle said:
if you flash the RUU in fastboot you shouldnt get the 155error
Click to expand...
Click to collapse
Yet I do. Fastboot is my only option anyway, as I have soft-bricked my stock ROM and cannot boot into anything but the bootloader / fastboot or recovery anymore.

searching through google, most people get rid of the error by running it in fastboot, its strange that it doesnt work for you..
you could try extracting the rom.zip from RUU and changing the name rom.zip to PJ4010000.zip (make sure its not .zip.zip) and booting into bootloader, and let HBOOT find the upgrade..
EDIT: just realised you cant get into recovery or boot phone, Please ignore what i said
Does the adb command ''fastboot reboot recovery'' not take you into recovery ? Have you also tried putting the rom inside adb folder and using command ''fastboot flash XXXXX.zip'' XXXX being the name of the rom

azzledazzle said:
searching through google, most people get rid of the error by running it in fastboot, its strange that it doesnt work for you..
you could try extracting the rom.zip from RUU and changing the name rom.zip to PJ4010000.zip (make sure its not .zip.zip) and booting into bootloader, and let HBOOT find the upgrade..
EDIT: just realised you cant get into recovery or boot phone, Please ignore what i said
Does the adb command ''fastboot reboot recovery'' not take you into recovery ? Have you also tried putting the rom inside adb folder and using command ''fastboot flash XXXXX.zip'' XXXX being the name of the rom
Click to expand...
Click to collapse
I am able to get into fastboot and also CWM, but my sdcard is inaccessible ("error mounting /sdcard"), so I am left with whatever can be done through adb or fastboot. I am assuming the method described above only works when putting the PJ4010000.zip file on the sdcard, right?
Edit: I also tried pushing several zips using fastboot, similar to what you described above. I always get a signature verification error.
Code:
C:\androidsdk\android-sdk-windows\tools>fastboot flash /system Rom_xda.zip
sending '/system' (525202 KB)...
OKAY [ 25.529s]
writing '/system'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 67.731s

yeah the PJ4010000.zip needs to be on SD card so this wont work for you,, Did you try with the ROM inside the
C:\androidsdk\android-sdk-windows\tools>
Click to expand...
Click to collapse
TOOLS folder, and asking bootloader to flash it directly ?? without pushing it to sd card..

azzledazzle said:
yeah the PJ4010000.zip needs to be on SD card so this wont work for you,, Did you try with the ROM inside the TOOLS folder, and asking bootloader to flash it directly ?? without pushing it to sd card..
Click to expand...
Click to collapse
Yes, I did. I just updated my prior post with more details of that attempt.
Thanks for trying to help me, I appreciate it!

but you said you tried pushing them, and in the code bit, it says fatsboot flash /system blabla.zip
you dont want to be flashing it from system, Simply put the ROM you want to flash, or the extracted rom.zip inside the location on your PC where you keep adb and fastboot files, Then use the command ''fastboot flash whateverromyouwant.zip'' this way bootloader will attempt to flash the rom directly from your PC not from your phone.

azzledazzle said:
but you said you tried pushing them, and in the code bit, it says fatsboot flash /system blabla.zip
you dont want to be flashing it from system, Simply put the ROM you want to flash, or the extracted rom.zip inside the location on your PC where you keep adb and fastboot files, Then use the command ''fastboot flash whateverromyouwant.zip'' this way bootloader will attempt to flash the rom directly from your PC not from your phone.
Click to expand...
Click to collapse
That is the incorrect syntax. The "fastboot flash" command requires a partition before the filename:
Code:
flash <partition> [ <filename> ]
-J

bummer !
thanks for correcting me, Ive never actually had to try this method, Which is good because it would have got me no where lol...
let me do some research and ill try to find an answer,,, In the meantime head over to http://webchat.freenode.net/ and use channel #helpmenow ive got some mates there from the sensation forums who are very good when it comes to HTC

SOLVED!
azzledazzle,
first off, I want to thank you Sir for pointing me to the IRC channel. Those guys, especially Ghanesh, were serious pros. They spent a good couple of hours with me on troubleshooting and trying different things. They couldn't quite fix it for me, but afterwards I engaged in some more trial-and-error and found out that I could restore access to the sdcard in CWM by flashing back to stock recovery, then choosing to "clear storage", then flashing a CWM version again. This brought the sdcard back to life.
I explain it in more detail here:
http://forum.xda-developers.com/showpost.php?p=25850720&postcount=8
Again, truly appreciate your help yesterday -- it encourage me to try different things on my own after
-J

By flashing the EU based ROM on a TMO S will you lose Wifi Calling etc?

Yes.
If anyone can give me a tmob US ROM I will cook you a Custom ROM.

JB ota update installation aborted SOLVED

Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks

coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
I have the same exact problem, however it also occurs when I try to install the zip directly from CWM...perusing the other threads it seems as though it's an issue with BusyBox overwriting some files in /system/bin. For the life of me I cannot find how to correct this issue even though the it is repeatedly mentioned in the threads that is has been covered already. Seeing as I'm nearing my wits' end, I'd appreciate someone pointing me in the right direction. Thanks in advance.:crying:
---------- Post added at 10:02 PM ---------- Previous post was at 09:42 PM ----------
Just to clarify this is what I get when I try to install 4.1.1:
Verifying current system...
assert failed: apply_patch_check
('/system/bin/gzip", "afdda757b27b444f525a0f41726d2c1a83012869", "5ba3b3ecd509cf6dcee37b2f27110310a1f55045")
E:Error in /cache/9ZGgDXDi.zip
(Status 7)
Installation aborted.
Even flashing 4.0.4 vias CWM doesn't overwrite the problematic /system/bin files. I got as far as trying to flash a factory image of 4.0.4 but got too frustrated with the fastboot commands in Terminal on OSX.
Again, while not a total neophyte, I could really use some hand holding regarding this mess. Thanks in advance.

Bumping in hope that some kind soul can walk me through replacing the /system/bin files that were overwritten by busybox. Tried factory reset and reflashing the 4.0.4 OTA to no avail. I think that flashing a factory image of 4.0.4 would work but I can't figure that out. I'm on OS X for what it's worth.
I appreciate your time.

Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.

albundy2010 said:
Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.
Click to expand...
Click to collapse
Thanks for the prompt reply. I dl'ed the factory image for my device (I9020T) from the developers/google site but couldn't get the ./flash-all.sh script to run. I then took the image.zip file from the factory tgz file and tried to flash it via CWM but got installation aborted/ Error 7 as well. Seems to be the only way to overwrite the system/bin filed that BusyBox replaced is to flash a factory image via fastboot.
Is there a way in which I can replace the problematic system/bin files that are preventing me from installing JB without flashing a stock factory image? And if there isn't, could I get some help with the Terminal commands for getting the /.flash-all.sh script to run on Mac?
Thanks again for your help and patience.

Those images are not mean to flashed through any recovery.
You can ignore that script. Extract what you have downloaded until you are left with ALL .img files. You should have system.img boot loader, radio, and userdata.img
Flash them one at a time with fastboot. Can't remember the exact Mac command but its fastboot flash system system.img etc for windows. Just look it for Mac. Think its fastboot-mac then the command but not sure. I hate Macs.

This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium

jayjay3333 said:
This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Those two links were extremely helpful, thanks for that. I got as far as having all the requisite factory image files ready to be flashed in the same folder, but when I issue the command to flash the bootloader.img I get
Code:
-bash: ./fastboot-mac: Permission denied
.
Think I may have gotten a little over my head with this whole rooting business
For the record I am rooted and have an unlocked bootloader.

coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
try latest touch version here http://bit.ly/QHLhXs when the update go to install in cmw there one dailoge box come choose yes and choose reboot and its appear again dailoge box choose yes disable recovery flash.

I solved the problem flashing this stock rom. http://forum.xda-developers.com/showthread.php?t=1784497

Finally sussed it out as well! Thanks to all for the help. Flashing the stock ICS image allowed me to install the JB OTA - will never install the BusyBox from the market again.
Cheers again to all.

[Q] Cannot load PJ8312000-OneX.zip: Unknown Error

Hi everyone. I'm having some problems getting S-Off on my phone. I'm running CM10 and I'm trying to follow Facepalm's method. I've got the phone to the black htc screen from the bootloader by typing in "fastboot oem rebootRUU" but when I type in "fastboot flash zip PJ8312000-OneX.zip" I get a message that says "error: cannot load 'PJ8312000-OneX.zip': Unknown error". I've tried downloading and redownloading the file a bunch, but the error is still the same.
Now just to give you more info: I don't know too much about using adb or fastboot. I downloaded them as a package with SDK and just extracted it to my desktop. That's where I saved the PJ8312000-OneX file and the soffbin3 file too. Got the error. I tried moving the files to the "platform tools" folder in the SDK folder. Still got the error. I don't know if the SDK folder itself needs to go somewhere else or not.
Any help would be appreciated.

The files just need to be in the same directory as adb and fastboot.
Are you SuperCID?

iElvis said:
The files just need to be in the same directory as adb and fastboot.
Are you SuperCID?
Click to expand...
Click to collapse
Yes, I'm SuperCID. The files are in the same directory as adb and fastboot, but I'm still getting the same error. Checking them with md5 shows that the files are good too.

I don't know if this is relevant or not, but adb won't recognize my device either. I have to get to fastboot either using Quick Boot or holding volume down. Fastboot recognizes my phone in the cmd prompt, but adb won't. Like I said, that might be irrelevant though.

Try this: Reboot your phone and start from the beginning. Create a folder on your desktop and put the adb and fastboot files in there, with the soffbin and PJ file. Then try again. This worked for some people, though I'm not sure why.
Someone else reported success by unzipping the PJ file then rezipping it.
---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------
PatC87 said:
I don't know if this is relevant or not, but adb won't recognize my device either. I have to get to fastboot either using Quick Boot or holding volume down. Fastboot recognizes my phone in the cmd prompt, but adb won't. Like I said, that might be irrelevant though.
Click to expand...
Click to collapse
I was having the same issue--adb devices returned nothing--but it made no difference. The commands still worked.

Sorry for dipping out earlier. Had to run out for a bit. Thanks for your help by the way.
Anyway, I've tried making the separate folder for adb and fastboot and that didn't work. I tried unzipping and rezipping the PJ file and its the same error.

Use a stockish sense Rom. Clean Rom or viperxl. That is what our phone is supposed to be running. Should help you out.
Sent from my HTC One X using XDA Premium HD app

Also for adb commands run it with phn booted into Rom when you get to reboot cmd it will take you into fastboot then when executed
Sent from my HTC One X using xda premium

As suggested, I would try flashing one of the stock rooted roms and see if that helps.

HTC ONE X s off error
PatC87 said:
Hi everyone. I'm having some problems getting S-Off on my phone. I'm running CM10 and I'm trying to follow Facepalm's method. I've got the phone to the black htc screen from the bootloader by typing in "fastboot oem rebootRUU" but when I type in "fastboot flash zip PJ8312000-OneX.zip" I get a message that says "error: cannot load 'PJ8312000-OneX.zip': Unknown error". I've tried downloading and redownloading the file a bunch, but the error is still the same.
Now just to give you more info: I don't know too much about using adb or fastboot. I downloaded them as a package with SDK and just extracted it to my desktop. That's where I saved the PJ8312000-OneX file and the soffbin3 file too. Got the error. I tried moving the files to the "platform tools" folder in the SDK folder. Still got the error. I don't know if the SDK folder itself needs to go somewhere else or not.
Any help would be appreciated.
Click to expand...
Click to collapse
Did you ever figure it out? im stuck at the same part

spinks420 said:
Did you ever figure it out? im stuck at the same part
Click to expand...
Click to collapse
On cm10 don't you have to give adb root access? I haven't run a cm Rom in ages but I think I've seen it discussed about allowing access in one of the setting screens.
Sent from my HTC One XL using xda premium

31ken31 said:
On cm10 don't you have to give adb root access? I haven't run a cm Rom in ages but I think I've seen it discussed about allowing access in one of the setting screens.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah that's right. In developer settings you must turn on usb debugging, and there is another option which is called root access I think. This option has apps only checked by default, you need to change it to apps and adb.
Sent from my Evita

also, if you're on 4.2 jellybean based rom, you will need to make sure that you have a newer version of adb, and that even after you have the debugging settings checked, that you check the checkbox on the phone when it tries to connect the first time. It was an added security "feature" (just double checked, has to be 1.0.31 of adb in this case)
http://android-developers.blogspot.com/2013/02/security-enhancements-in-jelly-bean.html has some more technical information about it....

HELPP
iElvis said:
The files just need to be in the same directory as adb and fastboot.
Are you SuperCID?
Click to expand...
Click to collapse
yes ive tried everything. idk if this is relevant but it says the zip file PJ8312000 is invalid. what can i do?
---------- Post added at 02:50 PM ---------- Previous post was at 02:44 PM ----------
31ken31 said:
On cm10 don't you have to give adb root access? I haven't run a cm Rom in ages but I think I've seen it discussed about allowing access in one of the setting screens.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
yeah but im curently on the viperxl rom im trying to get cyanogenmod 10 but i have to s off first then downgrade the touch panel cause i took the ota and my hboot is 2.14. and i keep getting stuck at the step of s-off where you have to upload the zip file PJ8312000-OneX.zip

spinks420 said:
yes ive tried everything. idk if this is relevant but it says the zip file PJ8312000 is invalid. what can i do?
---------- Post added at 02:50 PM ---------- Previous post was at 02:44 PM ----------
yeah but im curently on the viperxl rom im trying to get cyanogenmod 10 but i have to s off first then downgrade the touch panel cause i took the ota and my hboot is 2.14. and i keep getting stuck at the step of s-off where you have to upload the zip file PJ8312000-OneX.zip
Click to expand...
Click to collapse
Press and hold power on your phone until it shuts off, then after it reboots, try again.

exad said:
Press and hold power on your phone until it shuts off, then after it reboots, try again.
Click to expand...
Click to collapse
still the same problem is says no such directory exists for the s-off bin files and for the zip it just says cannot load and an error has occurred. but thank you. can you think of anything else i might try?

spinks420 said:
still the same problem is says no such directory exists for the s-off bin files and for the zip it just says cannot load and an error has occurred. but thank you. can you think of anything else i might try?
Click to expand...
Click to collapse
Yeah they're not in the directory with ADB and fastboot.

exad said:
Yeah they're not in the directory with ADB and fastboot.
Click to expand...
Click to collapse
they are in the same folder as adb and fastboot which ive named Android-adb and placed in the root of my C:\drive and i then went into my computer settings and added the folder path to the paths. so my adb and fastboot are working fine they issue commans correctly and everything but it wont flash those files.

spinks420 said:
says no such directory exists for the s-off bin files
Click to expand...
Click to collapse
That means they are not in your dirctory with ADB and fastboot. If you did not unzip them into that folder, that constitutes as not being in that folder.

exad said:
That means they are not in your dirctory with ADB and fastboot. If you did not unzip them into that folder, that constitutes as not being in that folder.
Click to expand...
Click to collapse
i tried unzipping soffbin into the directory and it still didnt work and it wont open the pj8312000.zip it says the file is invalid. and ive downloaded it from multiple sites and it says the same thing for every one.

[Tutorial][S4/S3] How to use OTA zip to get back to Stock OS

Lately, many people, including myself, have been at a disadvantage of not having an official RUU for JellyBean so that stock environment can be achieved. Although sometimes, OTA's are available which can do the job. Hence this Tutorial. Also this saves the effort to do S-OFF/SuperCID which often brings along more problems.
This Tutorial, in principle, can be applied to both S4 and S3 variants.
All thanks to @xander1993 at the VilleC2 Development Section who created the original thread Here. Though somewhat unclear and related to VilleC2, I thought of making a thorough guide for Ville with some minor changes.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For T-MOBILE UK Users: (UK people with other operators e.g Three, Vodafone etc can also try the Jellybean Nandroid backup IF their firmware is upgraded to that of Jellybean)
ICS Users: Those stuck on ICS custom ROMs and can't get stock, Use This RUU to get to stock ICS and then update to Jellybean via System Updates Check. Thanks to @ppm48
Jellybean Users:Those stuck on Jellybean custom ROMs wanting to get stock, I have a Stock Jellybean 4.1.1 Nandroid backup for you guys Here Since there isn't any OTA.zip for T-Mobile UK for Jellybean. You can just flash this Nandroid right away without using this tutorial. Again, Thanks to @ppm48 for this. Also, if you have bootloops after restoring this backup, flash a Jellybean Sense boot.img.
Additionally refer to this post by @mkoev , should prove a lot helpful. Then you can follow the tutorial.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For OPTUS Users with CID OPTUS001: (All thanks to @salac)
Get the modified OTA.zip Here. by @salac
salac said:
Follow the instructions from step 12.
Step 14. Flashing the firmware.zip worked the second try for me
Step 22. I did flash the boot.img to make sure it will work since I don't think I had the original one.
Good Luck
Click to expand...
Click to collapse
Optus users please follow @salac 's post above to flash the OTA.zip
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Pre-requisites:
1. Notepad++
2. 7-Zip (Recommended)
3. ADB+Fastboot (Get it Here)
4. HTC drivers (Standalone OR HTC Sync Manager Drivers)
5. Unlock_code.bin from HTCDev to unlock bootloader.
6. Any OS (Custom/Stock) present on the phone. (I have not tested it for phones without any OS, you may try it at your own risk and post results here) Not Needed anymore.
Common Steps:
In this guide, I will ask you to go to fastboot/adb so you should know how you would do that. (All fastboot/adb commands are to be given via Command Prompt from PC)
To execute Fastboot Commands:
- Go to fastboot folder on your PC
- Go to fastboot via bootloader on your phone
- Connect the Phone to PC and on the Phone it should say Fastboot - USB Mode
- Now in the fastboot folder on your PC, Hold Shift + Right-Click and click Open Command Window Here
- Now you can enter commands given in the guide for fastboot.
To execute ADB Commands:
- Same procedure except that you don't need to go to fasboot on your phone. You can execute adb commands while in Android OS/desktop.
To boot into Bootloader:
- While the phone is turned off, Press Volume Down + Power Button simultaneously.
OR
- If you are in Android OS, use the following adb command to boot into bootloader:
Code:
adb reboot bootloader
OR
- If you want to reboot into bootloader from fastboot:
Code:
fastboot reboot-bootloader
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Caution for SuperCID users: Please click the CROSS button on your Browser Tab, as flashing this is not intended for you. Either don't flash the OTA.zip, which will brick your phone if you do, OR change your CID to original one. e.g. H3G__001, BM___001, ORANG001
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Procedure:
- ** - ** - ** - Make Nandroid Backups before you do anything, remember you are doing this at your own risk - ** - ** - ** -
1. Download a OTA.zip – Most likely from Here. (You can rename the OTA file which usually has a long name to simply OTA.zip for ease)
2. Extract firmware.zip from OTA.zip. Then extract boot.img from firmware.zip. For now, copy Boot.img to ADB+Fastboot Folder..
3. Now to match the CID of your phone. You can get the CID of your phone via CID Getter from Play Store. Once opened, at the top will be your CID in Red color.
Alternatively, You can also get CID of your phone via Fastboot. Command for that is:
Code:
fastboot getvar cid
and it should display your CID.
4. Inside firmware.zip, look for android-info.txt. Supported CIDs should be mentioned inside this file. If it matches with that of your phone, Proceed otherwise stop and don't put yourself into more problems. (CID Match Exception: This 4th step may not be applicable to you if & only if you are to skip steps 11 to 16, if this is the case, you may flash OTA.zip skipping steps 11 to 16; Read step 10 for more info and then come back here)
5. We need to remove some code lines from inside the OTA.zip. For this, Open the OTA.zip with 7-zip (Right-click ---> 7-zip ---> Open Archive).
6. Head over to META-INF\com\google\android and find a file named updater-script. Drag it out of the archive to the folder/desktop where you can edit it. You should make an extra copy of this file.
7. Once you drag it out, delete the original updater-script inside the archive. It will recompress OTA.zip.
8. Edit with Notepad++ the extracted updater-script file. Find these lines (in the beginning of the file) and delete them altogether:
Code:
[COLOR="Purple"]assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" ,
"BM___001") == "t");[/COLOR]
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PJ4011000") == "t");,
assert(check_mid("simple", "PJ4011000") == "t");
);
You should delete these lines up to exact semi-colon ; at the end. (the purple lines with different CIDs can be different from those mentioned here, so no need to panic, just delete them)
9. Once edited, Copy this edited updater-script into the OTA.zip archive at the same location from which it was removed. It will recompress OTA.zip. You may now transfer OTA.zip to your SD-Card on your phone.
10. If you previously updated to JellyBean via OTA (Or if you have the exact or newer firmware on your phone than that present inside OTA.zip), skip steps 11 to 16. For example, if you have HBOOT Version 2.15.0000/2.13.0000 or above, it means you have already upgraded to Jellybean firmware so no need for Steps 11 to 16.
In case, if you are to proceed to step 11, that is if you are to flash firmware.zip, make sure to match CID as mentioned in step 4 to avoid any bricks. This is especially useful for those who have ICS and want to get stock JB or those on JB but want complete stock HBOOT, recovery etc.
11. Place firmware.zip extracted from OTA.zip inside ADB + Fastboot Folder.
12. Lock the bootloader, if unlocked. For this, go to fastboot on your phone and give the command:
Code:
fastboot oem lock
The phone reboots after this.
13. While in Android OS/Desktop, fire up Command window on PC to give the following ADB command to boot into OEM Update Mode.
Code:
adb reboot oem-78
OR (if you can't access OS to execute adb)
From Fastboot:
Code:
fastboot oem rebootRUU
You should be seeing HTC logo.
14. While in OEM Update Mode, give the following fastboot command to flash firmware:
Code:
fastboot flash zip firmware.zip
If it fails with error and doesn't show any Green Progressbar, keep trying the above command. Usually works after a few tries.
********** DO NOT REBOOT MANUALLY UNTIL IT FINISHES FLASHING FIRMWARE OR YOU'LL BRICK YOUR PHONE *************
15. Once firmware is updated, reboot into bootloader. Go into fastboot.
16. Place Unlock_code.bin inside ADB + Fastboot Folder. Use the following fastboot command to unlock your bootloader again. (This will wipe your phone except for SD, so you must make a backup before doing this)
Code:
[COLOR="Blue"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
17. Download a recovery. Preferred Recovery is TWRP 2.3.3.0 and I have not tested this guide with any other version. Put the recovery in the ADB + Fastboot folder.
18. Now go into bootloader again. This time to flash the recovery anew.
Code:
fastboot flash recovery recovery.img
19. Now go to the recovery via bootloader. Wipe data/factory reset, cache, dalvik.
20. Restore the Nandroid backup you had made earlier.
21. Now Flash the OTA.zip which is on your SD-Card. It should flash fine.
22. Go to fastboot via bootloader. We are now going to flash kernel with the following command, boot.img you had earlier copied to ADB+Fastboot folder.
Code:
fastboot flash boot boot.img
23. Reboot to the OS and you should see complete stock JB OS.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Please Rate the thread and Hit the Thanks button if this tutorial helped you!

I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?

mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Well, When I edited OTA.zip, it was the same size before/after. But maybe OS X uses different compression values.
I think you should go ahead with it and try it.

I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/

mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
.......................
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Can you use Winzip/Winrar? Might want to check with those two..

mortek said:
I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/
Click to expand...
Click to collapse
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.

khan.orak said:
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.
Click to expand...
Click to collapse
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.

mortek said:
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.
Click to expand...
Click to collapse
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.

khan.orak said:
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.
Click to expand...
Click to collapse
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.

mortek said:
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.
Click to expand...
Click to collapse
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.

khan.orak said:
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.
Click to expand...
Click to collapse
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.

mortek said:
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.
Click to expand...
Click to collapse
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!

khan.orak said:
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!
Click to expand...
Click to collapse
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
sending 'zip' (400 KB)...
OKAY [ 0.226s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 1.735s
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s

mortek said:
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
...........
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s
Click to expand...
Click to collapse
I suspect hardware failure.
Sent from my HTC One S using Tapatalk 4 Beta

Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.

booenson said:
Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.
Click to expand...
Click to collapse
What recovery did you use? And did you edit updater script using notepad++?
Edit: Yup, after searching, Error Status 6 appears when you edit the UPDATER-SCRIPT using wordpad/windows editor which messes all that is inside it. Use Notepad++

khan.orak said:
What recovery did you use? And did you edit updater script using notepad++?
Click to expand...
Click to collapse
TWRP 2.4.1.0. No, I used notepad, but after googling and reading the differences between notepad++ and notepad, I will have to re edit with notepad++. Will try again tomorrow when I have more time, I still need to use this phone for work and can't have it bricked lol

Tried this again, flash went through and then flashed the boot.img included with the OTA zip, and my phones stuck at the "htc one" loading screen
Edit: relocked, flashed the stock recovery, thought it was still stuck at the loading screen so I unlocked it then went to install TWRP again to restore my nandroid, and it decided to finally boot. I guess I just needed to give it more time, currently back on 4.1.1, time to send this thing in under warranty so I can get my 3G/HSPA+ fixed. Thanks!

Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app

asdfasdfvful said:
Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I think yes. You can check if you CID is supported. It is inside the OTA.zip\firmware.zip, a file named android-info.txt and the supported CIDs will be there.
Edit: You should first check your CID. Download CID GETTER from Play Store. Shows CID in red on top.

TWRP for HTC One SV

I'm in need of TWRP or CWM and a stock back up for my Boost HTC One SV. All the threads I have found have dead links. If anyone could link me to these files I'd greatly appreciate it. I'm running Android 4.1.2 and need to restore to stock so I can apply the OTA update. I'm running into an issue because I removed my phones bloatware.
Thank you in advance,
Chris

MooniniteVII said:
I'm in need of TWRP or CWM and a stock back up for my Boost HTC One SV. All the threads I have found have dead links. If anyone could link me to these files I'd greatly appreciate it. I'm running Android 4.1.2 and need to restore to stock so I can apply the OTA update. I'm running into an issue because I removed my phones bloatware.
Thank you in advance,
Chris
Click to expand...
Click to collapse
Tell me your HBoot / firmware version please

LS.xD said:
Tell me your HBoot / firmware version please
Click to expand...
Click to collapse
HBoot = 2.00.4444
Is that the same as firmware or do I find that somewhere else?
Thank you so much.

MooniniteVII said:
HBoot = 2.00.4444
Is that the same as firmware or do I find that somewhere else?
Thank you so much.
Click to expand...
Click to collapse
Connect in fastboot mode. Open CMD in windows (I suppose you have installed adb/fastboot, if not --> DOWNLOAD it! ) and type "fastboot getvar all" and you will get a log. Delete imei/serial and post the log here Then i will get the right software for you

LS.xD said:
Connect in fastboot mode. Open CMD in windows (I suppose you have installed adb/fastboot, if not --> DOWNLOAD it! ) and type "fastboot getvar all" and you will get a log. Delete imei/serial and post the log here Then i will get the right software for you
Click to expand...
Click to collapse
Here you go. I hope I did it correctly. I an app developer but this stuff is pretty new to me.

MooniniteVII said:
Here you go. I hope I did it correctly. I an app developer but this stuff is pretty new to me.
Click to expand...
Click to collapse
I will need some time to check the RUUs. Not more than 1h Probably less...

LS.xD said:
I will need some time to check the RUUs. Not more than 1h Probably less...
Click to expand...
Click to collapse
I have this RUU here, from this thread, here. I've tried using it but it fails when writing the image.

MooniniteVII said:
I have this RUU here. I've tried using it but it fail when writing the image.
Click to expand...
Click to collapse
Which kind of error?
Have you installed a custom recovery?

LS.xD said:
Which kind of error?
Have you installed a custom recovery?
Click to expand...
Click to collapse
It goes through the whole process then when it attempts to write the image it says error writing image (I can run it again and snage a screen shot if it'd help). I had a custom recovery (CWM) but flashed the stock recovery the first time the OTA failed before realizing that it wouldn't work without the bloatware APKs anyways.

S-OFF makes it more easy. You probably first need to flash firmware.zip and then run the RUU. I'm downloading ATM. I'll send you the link when I got the right zip
DOWNLOAD firmware.zip
INSTRUCTIONS:
- extract boot.img + recovery.img from the firmware.zip
- flash both files via fastboot
- reboot bootloader
- type "fastboot oem rebootRUU" (RUU not ruu!!!)
- type "fastboot flash zip firmware.zip" (It will show you "error 90" -> thats ok)
- type "fastboot flash zip firmware.zip" (yes again and firmware will be flashed)
- type "fastboot reboot-bootloader"
- Run the RUU you already tried before.
IMPORTANT --> uninstall HTC Sync before flashing / running RUU

LS.xD said:
S-OFF makes it more easy. You probably first need to flash firmware.zip and then run the RUU. I'm downloading ATM. I'll send you the link when I got the right zip
DOWNLOAD firmware.zip
INSTRUCTIONS:
- extract boot.img + recovery.img from the firmware.zip
- flash both files via fastboot
- reboot bootloader
- type "fastboot oem rebootRUU" (RUU not ruu!!!)
- type "fastboot flash zip firmware.zip" (It will show you "error 90" -> thats ok)
- type "fastboot flash zip firmware.zip" (yes again and firmware will be flashed)
- type "fastboot reboot-bootloader"
- Run the RUU you already tried before.
Click to expand...
Click to collapse
Thank you. I'm attempting now with the instructions you posted. I will post again with the results once I've completed all the steps.

I've made my first attempt. After typing "fastboot flash zip firmware.zip" it went through with no "Error 90" (see screenshot), but my phone is on the black htc screen with the green progress bar stopped a few pixels short and nothing else happening. I've stopped here to double check before continuing to "fastboot reboot-bootloader". Is the process still going correctly or has something gone afoul?
Edit: I forgot to attach the screenshot...

MooniniteVII said:
I've made my first attempt. After typing "fastboot flash zip firmware.zip" it went through with no "Error 90" (see screenshot), but my phone is on the black htc screen with the green progress bar stopped a few pixels short and nothing else happening. I've stopped here to double check before continuing to "fastboot reboot-bootloader". Is the process still going correctly or has something gone afoul?
Click to expand...
Click to collapse
Make sure flash the firmware.zip 2 times. Its ok if the progress bar stops. Thats why you need to reboot via command "fastboot reboot-booloader"
I'm off for a episode of "Game of Thrones". You should be fine with the guide. If not --> I'm back in about 1 hour

LS.xD said:
Make sure flash the firmware.zip 2 times. Its ok if the progress bar stops. Thats why you need to reboot via command "fastboot reboot-booloader"
I'm off for a episode of "Game of Thrones". You should be fine with the guide. If not --> I'm back in about 1 hour
Click to expand...
Click to collapse
You are a savior. It worked flawlessly. I did have to install HTC Sync (an earlier version, I used version 2.4.11) and fix my drivers first. MANY thanks to you. I hope that I get a chance to pass this knowledge on to others.

I'm glad you got it Are you running the latest official version now?
Sent from my beloved HTC One S using (most time buggy) Tapatalk

LS.xD said:
I'm glad you got it Are you running the latest official version now?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Yes. I now officially have Android 4.2.2 w/ Sense 5.5. It's so pretty. I can't wait to play with all the new features and re-root my phone.