[Q] ISO hox rogers 4.1.1 / 3.18 ruu.. - AT&T, Rogers HTC One X, Telstra One XL

Phone is the HTC One X, 4.1.1 / 3.17.6312 (evita )
Carrier is Rogers
Unlocked, s-on
Custom recovery installed ( openrecovery-twrp-2.5.0.0-evita.img)
And was rooted with (Superuser-3.2-RC3-arm-signed)
Phone seemed to be stable and working fine, But the ear speaker wasn't working ( couldn't hear callers unless I went into speaker mode )
Figured I would try a re-install to see if that would help.. But in the process I must have formatted to corrupted the OS...
After trying: C:\Android>fastboot flash system OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23
a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip the os won't boot... stays in HTC quietly brilliant screen..
I am able to get into fastboot / bootloader / recovery. I'm wondering if it's the OTA ... Perhaps a newer RUU ? The only one I can find is outdated and I can't install cause s-on..
RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe
Click to expand...
Click to collapse
Anyone know of a RUU for 3.17 ( rogers / evita )??? Or perhaps an alternative way to re-install the OS?
Cheers and Thanks.

Fleasus said:
Phone is the HTC One X, 4.1.1 / 3.17.6312 (evita )
Carrier is Rogers
Unlocked, s-on
Custom recovery installed ( openrecovery-twrp-2.5.0.0-evita.img)
And was rooted with (Superuser-3.2-RC3-arm-signed)
Phone seemed to be stable and working fine, But the ear speaker wasn't working ( couldn't hear callers unless I went into speaker mode )
Figured I would try a re-install to see if that would help.. But in the process I must have formatted to corrupted the OS...
After trying: C:\Android>fastboot flash system OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23
a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip the os won't boot... stays in HTC quietly brilliant screen..
I am able to get into fastboot / bootloader / recovery. I'm wondering if it's the OTA ... Perhaps a newer RUU ? The only one I can find is outdated and I can't install cause s-on..
Anyone know of a RUU for 3.17??? Or perhaps an alternative way to re-install the OS?
Cheers and Thanks.
Click to expand...
Click to collapse
did you flash the ota using stock recovery with a locked bootloader? I'm assuming you didnt supercid since youre s-on and with rogers.
to ota with s-on you must flash stock recovery and relock.

exad said:
did you flash the ota using stock recovery with a locked bootloader? I'm assuming you didnt supercid since youre s-on and with rogers.
to ota with s-on you must flash stock recovery and relock.
Click to expand...
Click to collapse
I did a factory reset, cleared cache, oem lock and ...
C:\Android>fastboot flash system OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.2
a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip
sending 'system' (650005 KB)...
OKAY [ 25.835s]
writing 'system'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 87.419s
Click to expand...
Click to collapse
hang's on HTC quietly brilliant screen,,,

Fleasus said:
I did a factory reset, cleared cache, oem lock and ...
hang's on HTC quietly brilliant screen,,,
Click to expand...
Click to collapse
Are you sure you have 3.18 software on your device? Looking at the output, it's not accepting because you're using the wrong RUU.
Find redpoints index thread in the dev section, it will have the correct RUU in there.
EDIT: Well... Looking at OP it seems you are using the wrong RUU. 1.94 isn't what you have on your phone.

Myrder said:
Are you sure you have 3.18 software on your device? Looking at the output, it's not accepting because you're using the wrong RUU.
Find redpoints index thread in the dev section, it will have the correct RUU in there.
EDIT: Well... Looking at OP it seems you are using the wrong RUU. 1.94 isn't what you have on your phone.
Click to expand...
Click to collapse
Thats exactly the issue... The only executable ruu I can find is the 1.94 version... I need 3.17. ( 3.18 was my typo in the title .oops ) and for some reason flashing the 3.17 OTA isn't working also.. I'm assuming cause it's an update and not the entire OS install..
I noticed when in TWRP recovery, if I reboot it asks if I'm sure cause there is no OS installed... The question is now, how the heck do I reinstall said os?
Thanks.

Yeah you can't fastboot it you have to flash it from within stock recovery.
Unlock.
Extract recovery.img (may also be called recovery_signed.img) from the ota zip
Fastboot flash recovery recovery.img
Relock.
Select recovery from bootloader.
When a picture comes on the screen, hold volume up and press power
Then select install from phone storage (not from sdcard)
Then select your ota.
It will flash successfully
Sent from my HTC One X using xda app-developers app

When in Android System Recovery <3e>
Device_CW_Install: Can't mount /data
"install from phone storage" gives the following error
Invalid operation... rebooting

Did you factory reset within bootloader at any point? This would have corrupted your sd card.
It's also possible you got a bad ota download.
Sent from my HTC One X using xda app-developers app

It's very possible I did a factory reset within bootloader... As for the OTA, it took nearly an hour to download it..not sure if teh host was slow or if it was my end .. Perhaps it corrupted on transfer?

Do i need to mount ( in twrp recovery ) and copy the OTA file onto the sdcard in order to "select install from phone storage"??

That's right. But you'll need to copy the file to your phone first, then unmount, then flash it.
Sent from my HTC One XL using xda premium

Should I place it in a specific folder?

No you can put it anywhere
Sent from my HTC One X using xda app-developers app

device_CM_Install: Can't mount /data
Invalid Operation
I don't even have an option to select the OTA file after selecting "install from phone storage"...straight to invalid Operation error.
ANy ideas how to fix the mount?

Attempted the Nocturnal guide for corrupted sd card.. same result.

Fleasus said:
Do i need to mount ( in twrp recovery ) and copy the OTA file onto the sdcard in order to "select install from phone storage"??
Click to expand...
Click to collapse
yes
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
Fleasus said:
Do i need to mount ( in twrp recovery ) and copy the OTA file onto the sdcard in order to "select install from phone storage"??
Click to expand...
Click to collapse
It doesnt need to be on the internal memory to select install from phone storage. It does need to be on there to select the OTA though.
Mount the SD card in twrp and format it. then copy the ota over

Formatted and trying to scan / repair sdcard... hopefully able to repair..

formatted sdcard in windows ( after mounting in twrp ) .. Not sure if that helped any... I was able to wipe / clear in twrp also... which seems to have remounted the /data, /system /cache and /sdcard partitions..
Now, if I can only get the OTA to flash....

C:\Android>fastboot flash zip OTA.zip
sending 'zip' (650005 KB)...
OKAY [ 25.760s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.618s
HOw does one get past the signature verify? ( phone is locked, and recovery.img was run prior to OTA rom )

Fleasus said:
C:\Android>fastboot flash zip OTA.zip
sending 'zip' (650005 KB)...
OKAY [ 25.760s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.618s
HOw does one get past the signature verify? ( phone is locked, and recovery.img was run prior to OTA rom )
Click to expand...
Click to collapse
You have to flash stock recovery before locking.
*edit* my bad, misread. do fastboot oem readcid
no wait.. Why are you fastboot flashing it? Flash it from within Stock recovery. "install from phone storage". Sorry -_- I am in an altered state of conciousness

Related

[Q] HBoot 1.27.000, S-Off... How to install CWM

Hi guys,
I've got a Sensation here that has S-OFF and HBOOT 1.27.0000. From here, can I install CWM or 4EXT recovery? If I can, can someone tell me how or point to a guide?
Thanks
QB
qballds said:
Hi guys,
I've got a Sensation here that has S-OFF and HBOOT 1.27.0000. From here, can I install CWM or 4EXT recovery? If I can, can someone tell me how or point to a guide?
Thanks
QB
Click to expand...
Click to collapse
hi.. just download cmw apk from market and choose the version to be flash. then its download and automatically flash tje recovery. i recommend 4EXT recovery. its having so many features
Sent from my HTC Sensation 4G using XDA App
install rom maneger and let rom maneger install what u whant
Or search xda for the cwm thread and install via bootloader pmg58img file.
Sent from my HTC Pyramid using xda premium
I'm in the same boat as I followed EdyyOS's guide to install ICS OTA. So I have S-OFF and HBOOT 1.27.0000 but I'm not rooted or have CWM. I can't use Rom Manager as I don't have root. When I try to follow this guide http://forum.xda-developers.com/showthread.php?t=1192300 there seems to be something missing as I can't get the recovery to install the CWM files it links to.
Also on HBOOT it says in pink locked but I am S-Off.
I've attached 2 files to this post. The first is a PG58IMG.zip for the latest non-touch version of CWM. The second is for the current version of 4EXT
To flash, put the file you want to use first rename it to PG58IMG.zip (not PG58IMG.zip.zip) and put it on the root of your SD card and boot into HBOOT. It will ask you if you want to update so just select yes and it'll flash the recovery. Once done, press power to reboot and voila - you now have CWM/4EXT!
Thanks again Eddy!
---------- Post added at 03:00 PM ---------- Previous post was at 02:48 PM ----------
I see what my problem was now, your android-info.tx files contained modelid: PG5813001. The ones from the guide had modelid: PG5813000. Kept giving me a model ID error.
Get 4Ext Recovery. It's got an amazing amount of features AND it's touch.
Install 4ext recovery control. The application is free and there is on the market. With this application it is very easy to flash 4ext touch recovery.
Conflict?
I have CMW and just installed 4ext. will they have conflict?
4EXT over writes CWM, so no
There will be no problem.
4EXT all the way
Sensational sent from my Sensation.
How to make S-Off with HBOOT 1.27.000?
After repairing my HTC Sensation, lost the S-OFF and ROOT.
Now I have S-ON HBOOT 1.27.000, and through the website HTCDev fails in step 14, is this error:
C: \ Android> fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB) ...
OKAY [0.156s]
writing 'unlocktoken' ...
FAILED (remote: unlock token check failed)
finished. Total time: 0.172s
How to make S-Off with HBOOT 1.27.000?
You can't, stick with your own thread
Try 4EXT recovery. It's so easy to use.
Tantrumxp said:
I have CMW and just installed 4ext. will they have conflict?
Click to expand...
Click to collapse
The CWM app and 4ext apps will not conflict. But you only can flash one of them into your recovery.
Sent from my HTC Sensation XE with Beats Audio using XDA Premium HD app
EddyOS said:
I've attached 2 files to this post. The first is a PG58IMG.zip for the latest non-touch version of CWM. The second is for the current version of 4EXT
To flash, put the file you want to use first rename it to PG58IMG.zip (not PG58IMG.zip.zip) and put it on the root of your SD card and boot into HBOOT. It will ask you if you want to update so just select yes and it'll flash the recovery. Once done, press power to reboot and voila - you now have CWM/4EXT!
Click to expand...
Click to collapse
Hi,
I also have a Sensation, HBOOT 1.27.0000, S-OFF but with the pink "LOCKED" statement.
I try to flash the 4EXT recovery you provided, but I get an error message Invalid CID.
Any idea about what I should do?
Many thanks!
K
bertonegt said:
After repairing my HTC Sensation, lost the S-OFF and ROOT.
Now I have S-ON HBOOT 1.27.000, and through the website HTCDev fails in step 14, is this error:
C: \ Android> fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB) ...
OKAY [0.156s]
writing 'unlocktoken' ...
FAILED (remote: unlock token check failed)
finished. Total time: 0.172s
How to make S-Off with HBOOT 1.27.000?
Click to expand...
Click to collapse
Well, you can't. You have to root and get it S-OFF before the upgrade to ICS.
EddyOS said:
I've attached 2 files to this post. The first is a PG58IMG.zip for the latest non-touch version of CWM. The second is for the current version of 4EXT
To flash, put the file you want to use first rename it to PG58IMG.zip (not PG58IMG.zip.zip) and put it on the root of your SD card and boot into HBOOT. It will ask you if you want to update so just select yes and it'll flash the recovery. Once done, press power to reboot and voila - you now have CWM/4EXT!
Click to expand...
Click to collapse
Thank you EddyOS for the flashable recovery files. Do you have any containing stock recovery for the Sensation ?

Help! Problem unlocking Htc sensation

Hello! I am from Russia Federation. I had a problem with unlocking htc sensation, with the command "fastboot flash unlocktoken Unlock_code.bin" at the command prompt windows 7 leave message "sending 'unlocktoken' (0 KB) ...
OKAY [0.156s]
writing 'unlocktoken' ...
FAILED (remote: unlock token check failed)
finished. total time: 0.170s "and nothing happens after all the double-checking. I can not find a solution, I think people from xda help me. on the phone a new motherboard. transfers to google transtale part, so sorry for the text of the curve
If you got a new motherboard, you can't unlock with HTCDev, use Juopunutbear (http://unlimited.io) to S-OFF instead
there is a project for different imei after replacing motherboard(that's why you are failing in achieving htcdev method)
but i don't remember anymore where it is
do as above user suggested
How do I know if the motherboard is replaced?
Hi,
I have the same problem as the opener of this post. How do I know if the motherboard has been replaced? I just bought is as a second hand.
Just fyi.
Output from Terminal:
./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
Specifications:
Hboot 1.27
Model number: HTC Sensation Z710e (--> that is Sensation (EU) is supose on the HTCdev.com website? I am in the Netherlands..)
Android is: 4.0.3
USB debugging is checked.
I followed these guides:
http://forum.xda-developers.com/showthread.php?t=1417839
and had a look at:
http://forum.gsmhosting.com/vbb/f48...ader-hboot-s-off-flash-recovery-root-1581398/
Thanks very much!
phonographymobile said:
Hi,
I have the same problem as the opener of this post. How do I know if the motherboard has been replaced? I just bought is as a second hand.
Just fyi.
Output from Terminal:
./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
Specifications:
Hboot 1.27
Model number: HTC Sensation Z710e (--> that is Sensation (EU) is supose on the HTCdev.com website? I am in the Netherlands..)
Android is: 4.0.3
USB debugging is checked.
I followed these guides:
http://forum.xda-developers.com/showthread.php?t=1417839
and had a look at:
http://forum.gsmhosting.com/vbb/f48...ader-hboot-s-off-flash-recovery-root-1581398/
Thanks very much!
Click to expand...
Click to collapse
from cmd type
fastboot getvar all
somewhere you will see your imei
check if it is the same with the one from your box
also make sure in hboot screen says fastboot usb
rzr86 said:
from cmd type
fastboot getvar all
somewhere you will see your imei
check if it is the same with the one from your box
also make sure in hboot screen says fastboot usb
Click to expand...
Click to collapse
Thanks very much for the reply.
I checked the data from the terminal with the box.
Serial numbers are similar, but the IMEI numbers are different.
I guess this means the logicboard has been changed then and it will be safe to use the other unlock mechanism.
Appreciate the quick reply!
phonographymobile said:
Thanks very much for the reply.
I checked the data from the terminal with the box.
Serial numbers are similar, but the IMEI numbers are different.
I guess this means the logicboard has been changed then and it will be safe to use the other unlock mechanism.
Appreciate the quick reply!
Click to expand...
Click to collapse
uss this guide
http://forum.xda-developers.com/showthread.php?t=1661631
if you have windows just request for the windows version of the tool
Here I am again. Thanks very much for the guide. I was only able to try it today, and it worked perfectly! Thank you very much
Now my next question. How exactly can I install Cyanogenmod now? And am i already root? If you can point me to a guide or post that helps me further that is very much appreciated!
I have tried searching around, but there is so much information, and I don't understand when something is for the people that unlocked via HTCdev.com or via this method.
Thank you for understanding
btw I am on Mac OS X or Linux...
I have already tried to follow http://wiki.cyanogenmod.org/w/Install_CM_for_pyramid
everything worked until installing from the zip in recovery.
Everything OK until the wipe data/factory reset. But the next step didn't work out.
There was no choice to install zip from sdcard
I chose "Update from external storage" but that got me back into the main menu of Recovery.
rzr86 said:
uss this guide
http://forum.xda-developers.com/showthread.php?t=1661631
if you have windows just request for the windows version of the tool
Click to expand...
Click to collapse
phonographymobile said:
Here I am again. Thanks very much for the guide. I was only able to try it today, and it worked perfectly! Thank you very much
Now my next question. How exactly can I install Cyanogenmod now? And am i already root? If you can point me to a guide or post that helps me further that is very much appreciated!
I have tried searching around, but there is so much information, and I don't understand when something is for the people that unlocked via HTCdev.com or via this method.
Thank you for understanding
btw I am on Mac OS X or Linux...
I have already tried to follow http://wiki.cyanogenmod.org/w/Install_CM_for_pyramid
everything worked until installing from the zip in recovery.
Everything OK until the wipe data/factory reset. But the next step didn't work out.
There was no choice to install zip from sdcard
I chose "Update from external storage" but that got me back into the main menu of Recovery.
Click to expand...
Click to collapse
if you aren't rooted use the one click root tool from the same guide
then from my signature go to 4ext recovery thread and download the 4ext updater
from that app download and install 4ext recovery touch
after that reboot your device to 4ext recovery
and install the new rom
note :before flashing the new rom make a nandroid from recovery
format all partitions except sdcard from it
flash the new rom
I am really sorry but I cannot figure out how to root from Linux. I see the .bat file in Gedit and recognize commands, but is there a way to run the .bat file in linux?
Thanks!
rzr86 said:
if you aren't rooted use the one click root tool from the same guide
then from my signature go to 4ext recovery thread and download the 4ext updater
from that app download and install 4ext recovery touch
after that reboot your device to 4ext recovery
and install the new rom
note :before flashing the new rom make a nandroid from recovery
format all partitions except sdcard from it
flash the new rom
Click to expand...
Click to collapse
phonographymobile said:
I am really sorry but I cannot figure out how to root from Linux. I see the .bat file in Gedit and recognize commands, but is there a way to run the .bat file in linux?
Thanks!
Click to expand...
Click to collapse
i really don't know mate
try this then
flash from this thread 3.33 universal
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also the patched hboot which is unlocked
follow the instructions to the letter
before flashing check md5 sums(important)
after that flash 4ext recovery via fastboot command
http://forum.xda-developers.com/showthread.php?t=1631861 (only step 2)
finally flash the new rom from recovery
Thanks for the info. I will have a look at it.
In the mean time I have found a dutch guide, but that is not exactly working as well..
1. I did install ClockWorkRecovery by putting PG58IMG. on the SD card. and installing it from Hboot.
I fixed this! I had the SD card formated in MAC OS as Master Boot Record, apparently that is not compatible. After reformatting the SD Card in a camera it mounted!
Step 2 would be to root via su-2.3.6.3-efgh-signed. But everytime I try, CWR says the SD card cannot be mounted "error mounting /sdcard".
I have tried formatting, fixing permissions, manually mounting SD and redid everything about 5 times. But I cannot find out how to get the SD card mounted..
rzr86 said:
i really don't know mate
try this then
flash from this thread 3.33 universal
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also the patched hboot which is unlocked
follow the instructions to the letter
before flashing check md5 sums(important)
after that flash 4ext recovery via fastboot command
http://forum.xda-developers.com/showthread.php?t=1631861 (only step 2)
finally flash the new rom from recovery
Click to expand...
Click to collapse
phonographymobile said:
Thanks for the info. I will have a look at it.
In the mean time I have found a dutch guide, but that is not exactly working as well..
1. I did install ClockWorkRecovery by putting PG58IMG. on the SD card. and installing it from Hboot.
I fixed this! I had the SD card formated in MAC OS as Master Boot Record, apparently that is not compatible. After reformatting the SD Card in a camera it mounted!
Step 2 would be to root via su-2.3.6.3-efgh-signed. But everytime I try, CWR says the SD card cannot be mounted "error mounting /sdcard".
I have tried formatting, fixing permissions, manually mounting SD and redid everything about 5 times. But I cannot find out how to get the SD card mounted..
Click to expand...
Click to collapse
did you try to format it in FAT32?
rzr86 said:
did you try to format it in FAT32?
Click to expand...
Click to collapse
If you have access to linux try using gparted to format the sd card from the pc, not android. Go for fat32 as rzr86 suggests and then try to mount from your recovery
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

[Firmware Update] For AOSP ROMS-3.4 KERNEL-NEW OFFICIAL CM NIGHTLIES [27June]

When 1st time the new 3.4 kernel released many users had several issues with booting this amazing kernel or had boot loop,
You need this firmware update so you
can install new official CM nightly
so here is what you should do to enjoy it :
I will not be held responsible for your phone do at your own risk
1. First of all backup everything you need .
2. Download This :
2.1 A. For unbranded international devices & full package :
http://www.mediafire.com/?mc1mh05p669hspm
(Include Fastboot , Recovery , ADB , updated Firmware 2.15.0000, everything you'll need)
2.1 B. Here this link contains both firmware for international & T-Mobile devices :
https://www.dropbox.com/sh/ehihpbjf0shqgio/qu3vhYYDWe
2.2 For T-Mobile devices
You have to use T-Mobile firmware.zip from 2nd link replace it with my firmware.zip in the 1st file (A) and continue the steps.
2.3 Then extract it (The A-file) .
Hold Shift then right click on the folder and choose " Open Command Window Here " .
3. Boot into HBoot . Choose fastboot . in command Window type
"fastboot oem lock".
your phone will be locked .
4. Firmware (including HBoot , Boot , Recovery, Radio, every firmware partition needed for this new kernel... ).
Boot into HBoot again . Choose fastboot . in command Window type :
"fastboot oem rebootRUU".
after you are seeing HTC Screen then type :
"fastboot flash zip firmware.zip".
first time it get ERROR .
type again :
"fastboot flash zip firmware.zip".
now it should work and getting installed .
after install it does not reset use this command :
"fastboot reboot"
Or you have to reset by keeping power for some seconds .
5. unlock your phone again via the HTC Unlocking tool (HTC Dev site).
If you have the Unlock_code.bin file you received
originally, copy it into the working directory that you
have been using, return your phone to fastboot, and
issue the following command:
"fastboot flash unlocktoken Unlock_code.bin"
Your will be warned that you are voiding your warranty.
Select Yes or OK and continue. When the phone reboots
to the boatloader, it will announce that it has been
tampered with and is unlocked,
Note : Unlocking your bootloader will wipe your personal which is just data data partition not your internal SD .
6. Open command window again . type :
"fastboot flash recovery recovery.img".
this will install the latest TWRP Recovery .
Some users reported that this recovery.img in my package (A) is some how corrupted so download the latest TWRP RECOVERY and fastboot flash it don't use the one in my zip file
Get the latest TWRP recovery here http://goo.im/devs/OpenRecovery/ville
7. boot in recovery . for the first time it does not boot .
boot another time in recovery . it should work now .
8. Install The NEW CM KERNEL- WITCH IS IN YOUR ROM ZIP - IN FASTBOOT MODE THEN INSTALL The ROM IN TWRP RECOVERY after 3x full wipe .
9. Enjoy your CM 10.1 based ROM -3.4 KERNEL.
Please hit thanks button if this helped you
Hope you all enjoy the new amazing kernel with amazing new ROMS with it,
Thanks to all devs behind this great work
If your device is S-OFF you can just skip the relock & unlock steps And you won't lose any data by this way if you're running stock and just wanna upgrade the firmware but even with this I'd recommend to have backup before
Ps: check 2nd post
Tip: I'd recommend :
1.First if you don't want to risk TRY to run your device official JB RUU if you get errors with that try to get official JB update from the ota then the last way to get firmware update is to use my method here .
2.Get S-OFF and Super-CID if you get errors r with flashing the firmware.zip otherwise no need for that.
People to thank:
HTC
CyanogenMode team
@intervigil
@$droyd$
@BehradGH
@ron_e
@mo976
EVERYONE ELSE I FORGET.
mo976 said:
LIONS1 I hope I'm not stepping on your toes as its based on your Zip's and instructions so big thanks for your hard work.
Here's a little guide FOR S-OFF and SuperCID (111111) only and unlocked bootloader of course.
I TAKE NO RESPONSIBILITY if this messes up your phone. Or if your girlfriend breaks up with you or getting fired by your boss or whatever this is all at your own risk.
That said this is how I flashed and it worked for me!
1: Get the firmware from the opening post I used the T-Mobile firmware.zip https://dl.dropboxusercontent.com/sh...RuMvPhMiA&dl=1 (not the full RUU) but if your phone is not T-Mobile you may need the first download BehradGH_HBoot_2.15.0000_TWRP_Recovery.rar which includes adb and other goodies along with the firmware.zip inside.
2: Download the One S all in one toolkit here http://forum.xda-developers.com/show....php?t=1604677
3: Optional as the lastest is included in the latest version of the toolkit but just in case or if you already have an older version of the toolkit you can get the latest TWRP recovery here http://goo.im/devs/OpenRecovery/ville
My recommendations for file locations are all for making things easier to find
First unzip the toolkit to drive C example c:/one_s in this folder you should see "one s.exe" and a folder called data
Now unzip (or open using 7zip) the firmware and copy the recovery.IMG file inside of firmware.zip (for non T-mobile its inside of BehradGH_HBoot_2.15.0000_TWRP_Recovery.rar) to the recovery folder example c:/one_s/data/recovery (optional if you needed to dowload it copy the TWRP recovery IMG to the same folder).
Last step before beginning the upgrade process copy FIRMWARE.zip into the data folder c:/one_s/data
I recommend using an original USB cable and not some aftermarket or generic POS!
Now the fun begins. Start the all in one toolkit c:/one_s/One_S.exe
And choose reboot to bootloader make sure your phone shows fastboot usb
First we need stock recovery so select flash "your own recovery" in the upper right box and and the click on "flash recovery" when it shows you the file explorer box choose the stock recovery that you extracted before it will do its thing and should show finished okay in the command prompt window after it says done reboot to fastboot.
So far so good you should be back on the bootloader.
From the toolkit main screen in the lower left corner menu select "Flash a factory RUU zip" and click "run"! It will give you some BS message about needing a locked boot loader etc ignore and continue, it will now take you your phone to a black screen with a silver HTC logo and will ask you to locate the "RUU" choose the firmware.zip file and it should start on its own if not open a command prompt from the c:/one_s/data file and type in fastboot flash zip firmware.zip and it should do its thing when it says okay and finishes choose reboot into bootloader if it doesn't work and stays on the HTC screen with the green line hard reboot with power and volume down and go back into the fastboot menu.
Last but not least from the toolkit flash recovery again use the TWRP (S4) or if needed "your own recovery" (select the TWRP IMG that you downloaded) click "flash recovery" and wait for it to say done.
Reboot the bootloader and choose recovery from the menu happy flashing don't forget a full (data/system/cache) wipe might be needed before flashing the ROM.
Sent from my Nexus 7 using XDA Premium HD app
Always read lots post little
Click to expand...
Click to collapse
Hope this will help you guys :thumbup:
Sent from my HTC One S using xda premium
Perfect. Thanks. I was just researching this. I'll need to wait till I get back from vacation to do this though.
Sent.
Oh, wait! Does the hboot matter? I have 1.06...
Guess I can skip relocking it if s-off?
Sent from my HTC One S using Tapatalk 4 Beta
Darknites said:
Guess I can skip relocking it if s-off?
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
I skipped it without any trouble
Sent from my One S using xda app-developers app
Bowmanspeer said:
Perfect. Thanks. I was just researching this. I'll need to wait till I get back from vacation to do this though.
Sent.
Oh, wait! Does the hboot matter? I have 1.06...
Click to expand...
Click to collapse
This will uodate all your Firmware including the HBoot to be able to boot the new 3.4 kernel
Sent from my HTC One S using xda premium
Did not work for me.
sending 'zip' (35551 KB)...
OKAY [ 2.461s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 7.148s
I did try flashing the firmware zip twice.
I have not found an RUU that works for me. All give a 155 error. I have flashed stock recovery. I have oem lock.
I am totally stuck. I have tried everything I can find to fix the 155 error and nothing works.
I started down this path because my phone just boot loops after installing this ROM.
I have T-Mobile branded HTC One S. That ran SENSE and CM before the 3.4 kernel OK.
zguithues said:
I skipped it without any trouble
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Cool and thanks.
Sent from my HTC One S using Tapatalk 4 Beta
ron_e said:
Did not work for me.
sending 'zip' (35551 KB)...
OKAY [ 2.461s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 7.148s
I did try flashing the firmware zip twice.
I have not found an RUU that works for me. All give a 155 error. I have flashed stock recovery. I have oem lock.
I am totally stuck. I have tried everything I can find to fix the 155 error and nothing works.
I started down this path because my phone just boot loops after installing this ROM.
I have T-Mobile branded HTC One S. That ran SENSE and CM before the 3.4 kernel OK.
Click to expand...
Click to collapse
Okay bro you have to
1.Try your T-Mobile JB RUU this way you'll update the necessary Firmware
If you still get 155 error
2.Try to extract firmware.zip from the T-Mobile JB ota UPDATE ZIP FILE then replace it with my firmware.zip
I'll try to get you another firmware.zip from T-Mobile JB RUU
Sent from my HTC One S using xda premium
LIONS1 said:
Okay bro you have to
1.Try your T-Mobile JB RUU this way you'll update the necessary Firmware
If you still get 155 error
2.Try to extract firmware.zip from the T-Mobile JB ota UPDATE ZIP FILE then replace it with my firmware.zip
I'll try to get you another firmware.zip from T-Mobile JB RUU
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Where has the one in the op come from?
Sent from my HTC One S using Tapatalk 4 Beta
ron_e said:
Did not work for me.
sending 'zip' (35551 KB)...
OKAY [ 2.461s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 7.148s
I did try flashing the firmware zip twice.
I have not found an RUU that works for me. All give a 155 error. I have flashed stock recovery. I have oem lock.
I am totally stuck. I have tried everything I can find to fix the 155 error and nothing works.
I started down this path because my phone just boot loops after installing this ROM.
I have T-Mobile branded HTC One S. That ran SENSE and CM before the 3.4 kernel OK.
Click to expand...
Click to collapse
What's your cid?
That's probably what it's checking.
I would recommend getting super cid and trying then.
My phone is a Cincinnati Bell phone, and it took the tmo jb ruu no problem.
You might as well get soff while you're at it. Then you don't have to worry about fastbooting kernels.
Sent from my One S using xda app-developers app
Darknites said:
Where has the one in the op come from?
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
I updated the Op with two firmware.zip one from international JB ota update and other one from T-Mobile JB ota
Sent from my HTC One S using xda premium
LIONS1 said:
I updated the Op with two firmware.zip one from international JB ota update and other one from T-Mobile JB ota
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
The one from December?
Sent from my HTC One S using Tapatalk 4 Beta
LIONS1 said:
Okay bro you have to
1.Try your T-Mobile JB RUU this way you'll update the necessary Firmware
If you still get 155 error
2.Try to extract firmware.zip from the T-Mobile JB ota UPDATE ZIP FILE then replace it with my firmware.zip
I'll try to get you another firmware.zip from T-Mobile JB RUU
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Thanks,
I still get the 155 error
When I open the RUU file in 7zip I only see a couple of files and none of them are firmware.zip. I do not know how to extract it.
ron_e said:
Did not work for me.
sending 'zip' (35551 KB)...
OKAY [ 2.461s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 7.148s
I did try flashing the firmware zip twice.
I have not found an RUU that works for me. All give a 155 error. I have flashed stock recovery. I have oem lock.
I am totally stuck. I have tried everything I can find to fix the 155 error and nothing works.
I started down this path because my phone just boot loops after installing this ROM.
I have T-Mobile branded HTC One S. That ran SENSE and CM before the 3.4 kernel OK.
Click to expand...
Click to collapse
If you get this error your using the wrong firmware for your phone..
Sent from my One S using xda premium
ron_e said:
Thanks,
I still get the 155 error
When I open the RUU file in 7zip I only see a couple of files and none of them are firmware.zip. I do not know how to extract it.
Click to expand...
Click to collapse
Run ruu and leave it running then go to windows temp folder and dig around in there.
Sent from my HTC One S using Tapatalk 4 Beta
Darknites said:
The one from December?
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes the 1st JB ota UPDATE cuz the 2nd one just updated the radio so to have all your Firmware updated you need this one for December
Sent from my HTC One S using xda premium
LIONS1 said:
Yes the 1st JB ota UPDATE cuz the 2nd one just updated the radio so to have all your Firmware updated you need this one for December
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Cool.
Sent from my HTC One S using Tapatalk 4 Beta
ron_e said:
Thanks,
I still get the 155 error
When I open the RUU file in 7zip I only see a couple of files and none of them are firmware.zip. I do not know how to extract it.
Click to expand...
Click to collapse
Check the OP the firmware.zip is in the T-Mobile JB ota UPDATE not in the RUU
Sent from my HTC One S using xda premium
{delete, read PAC thread reply, sorry}

[Q] Flashing splash1.img error

Installed Cricket update for 4.22/Sense 5.
Downgraded hboot to 2.0 from 2.21.
Running unlocked/SuperSU/SuperCID.
When flashed splash screen under 4.12, no errors. Now when attempting getting unable to write error.
Checked for putting in to PL80IMG.zip but uncertain of android info format to make it work.
Used info file from hboot downgrade but gave invalid build error.Any suggestions would be appreciated.
BTW, Device is seen in ADB.
C:\Android\ADB>fastboot devices
HT36HS701349 fastboot
C:\Android\ADB>fastboot flash splash1 splash1.img
sending 'splash1' (750 KB)...
OKAY [ 0.223s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.257s
DOrtego said:
Installed Cricket update for 4.22/Sense 5.
Downgraded hboot to 2.0 from 2.21.
Running unlocked/SuperSU/SuperCID.
When flashed splash screen under 4.12, no errors. Now when attempting getting unable to write error.
Checked for putting in to PL80IMG.zip but uncertain of android info format to make it work.
Used info file from hboot downgrade but gave invalid build error.Any suggestions would be appreciated.
BTW, Device is seen in ADB.
Click to expand...
Click to collapse
are you s-off ?
Yes, S-Off carried over from 4.12 to 4.22
DOrtego said:
Installed Cricket update for 4.22/Sense 5.
Downgraded hboot to 2.0 from 2.21.
Running unlocked/SuperSU/SuperCID.
When flashed splash screen under 4.12, no errors. Now when attempting getting unable to write error.
Checked for putting in to PL80IMG.zip but uncertain of android info format to make it work.
Used info file from hboot downgrade but gave invalid build error.Any suggestions would be appreciated.
BTW, Device is seen in ADB.
C:\Android\ADB>fastboot devices
HT36HS701349 fastboot
C:\Android\ADB>fastboot flash splash1 splash1.img
sending 'splash1' (750 KB)...
OKAY [ 0.223s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.257s
Click to expand...
Click to collapse
use the android-info.txt from the OTA you received.
place it in the PL80IMG.zip with the splash1.img and try again
Sent from my C525c using Tapatalk
OTA info attempt
Built the zip with 7zip and "Store" option to create.
Copied to root of SDCARD.
In hboot, it looks and reports it as being "Wrong zipped image" giving only option to press power to reboot.
This method worked on hboot downgrade you sent me to use.
russellvone said:
use the android-info.txt from the OTA you received.
place it in the PL80IMG.zip with the splash1.img and try again
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
The new HBoot has some changes to it, and will take time for people to find these changes and update them on XDA. Trials and errors
Sent from my K2_CL using Tapatalk
Solved
Was able to update via zip.
Had in root of Internal SD when should have been External.
The little things that cause biggest problems.
Thank you.
Modding.MyMind said:
The new HBoot has some changes to it, and will take time for people to find these changes and update them on XDA. Trials and errors
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
Trials and errors lol
Sent from my K2_CL using Tapatalk

k2_CL RUU freezing @ black HTC screen

I am trying to restore my phone obviously but when I try to use the RUU it keeps freezing at the update progress screen, but the bar never shows up. Any ideas?
Tried a different cable, and now I am getting error 155, (The rom update utility couldn't update your android phone.)
The reason this is such a problem, is because I can't get intpo TWRP, it gives me the twrp loading screen, but then softboots loops over and over into the twrp loading screen. I flashed recovery.img a couple of times and still can't get it working.
Basically at this point I feel like it's RUU or bust.
tootone said:
I am trying to restore my phone obviously but when I try to use the RUU it keeps freezing at the update progress screen, but the bar never shows up. Any ideas?
Click to expand...
Click to collapse
RUU will boot you into [fastboot's OEM rebootRUU] mode. Do you mean there is not a green progress bar? What ROM ver are you currently on?
Sent from my HTC Sensation using Tapatalk
eduardog131 said:
RUU will boot you into [fastboot's OEM rebootRUU] mode. Do you mean there is not a green progress bar? What ROM ver are you currently on?
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Yes no green progress bar. Currently there is no rom, because I cannot get into twrp. I edited my original post with some additional info.
Another update. I finally got into twrp, and now I just need a rom to flash I believe.
I have flashed a rom still no luck.
I flashed stock recovery, and relocked my bootloader. and tried the RUU again still getting error155. if anyone has a TWRP nandroid or a rom I could try that would be amazing.
bad english
tootone said:
Another update. I finally got into twrp, and now I just need a rom to flash I believe.
I have flashed a rom still no luck.
I flashed stock recovery, and relocked my bootloader. and tried the RUU again still getting error155. if anyone has a TWRP nandroid or a rom I could try that would be amazing.
Click to expand...
Click to collapse
Check this out i had the same problem than you, and this was the answer
First at all restore this backup with TWRP
http://forum.xda-developers.com/showthread.php?t=2734434
ICS preferred,
FLASH BOOT.IMG with Fastboot
Second if you can start up your HTC,
flash stock ICS
recovery.img with fastboot.
http://forum.xda-developers.com/showthread.php?t=2317379
then you can update via OTA.
Send me a message if you have problems
SORRY FOR MY BAD ENGLISH.
omarmando said:
Check this out i had the same problem than you, and this was the answer
First at all restore this backup with TWRP
http://forum.xda-developers.com/showthread.php?t=2734434
ICS preferred,
FLASH BOOT.IMG with Fastboot
Second if you can start up your HTC,
flash stock ICS
recovery.img with fastboot.
http://forum.xda-developers.com/showthread.php?t=2317379
then you can update via OTA.
Send me a message if you have problems
SORRY FOR MY BAD ENGLISH.
Click to expand...
Click to collapse
I am trying the first method you sent me, but which boot.img are we talking here?
Ics Bolt.img
Sent from my C525c using XDA Free mobile app
There is an encrypted Rom.zip pulled from the actual RUU itself posted for K2_CL.
Using fastboot:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Rom.zip
Give it time. Could take ten minutes or longer until it is complete. Had a guy do it over on AF and he has his phone back now.
Sent from my C525c using Tapatalk
Modding.MyMind said:
There is an encrypted Rom.zip pulled from the actual RUU itself posted for K2_CL.
Using fastboot:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Rom.zip
Give it time. Could take ten minutes or longer until it is complete. Had a guy do it over on AF and he has his phone back now.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Yeah that fails with
C:\adb>fastboot flash zip Rom.zip
sending 'zip' (616945 KB)...
OKAY [ 23.035s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 92.353s
tootone said:
Yeah that fails with
C:\adb>fastboot flash zip Rom.zip
sending 'zip' (616945 KB)...
OKAY [ 23.035s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 92.353s
Click to expand...
Click to collapse
What shows on your device screen when doing it?
Also, if you are S-On and was on 4.2.2 prior to your device giving problems then it will fail because the RUU is 4.1.2 and would require a "downgrade" which can only be achieved if S-Off.
With that said, I went back up on this thread and saw you are having problems with TWRP. Make sure you are using the correct one. Should be 2.7.0.2d or 2.7.0.2c. If attempting to flash another version and you are on 4.2.2 then you will get boot problems with the recovery.
In addition, make sure your bootloader isn't locked if S-On while messing with TWRP or that will cause a security problem on your device.
Sent from my C525c using Tapatalk
Modding.MyMind said:
What shows on your device screen when doing it?
Also, if you are S-On and was on 4.2.2 prior to your device giving problems then it will fail because the RUU is 4.1.2 and would require a "downgrade" which can only be achieved if S-Off.
With that said, I went back up on this thread and saw you are having problems with TWRP. Make sure you are using the correct one. Should be 2.7.0.2d or 2.7.0.2c. If attempting to flash another version and you are on 4.2.2 then you will get boot problems with the recovery.
In addition, make sure your bootloader isn't locked if S-On while messing with TWRP or that will cause a security problem on your device.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
bootloader is unlocked but I am s-on maybe that is causing all of my problems. I will see what I can do to remedy that. Well nevermind, I can' t s-off without a working rom, and I can't get a working rom without s-off.
tootone said:
bootloader is unlocked but I am s-on maybe that is causing all of my problems. I will see what I can do to remedy that. Well nevermind, I can' t s-off without a working rom, and I can't get a working rom without s-off.
Click to expand...
Click to collapse
Hmm, well, there is one thing I know for sure and that it that you are definitely able to restore your phone, so I'm pretty sure that some attempts being made In regards to trying other methods are possibly not being done exactly like they should.
This device is VERY hard to wreck and I have done LOTS to my phone and have always been able to bring it back to life in 5 minutes or less.
Sent from my C525c using Tapatalk
I am fairly certain I am doing it right. My mistake here was not doing a backup before I flashed anything. Let me go through what I had tried.
The RUU, I run it with my bootloader locked and I get error 158, I run it unlocked, I still get error 158.
I have tried the rom from the RUU, fastboot into ruu mode, transfer it, and I get an error
I tried putting PL80IMG in the root of my sd, it seems to flash correctly but it boots in white htc quietly brilliant screen. and flash boot.img for that rom.
I restore a rom via TWRP boots into white htc quietly brilliant screen.
and countless other things.
What about the other backups for boost (older than 4.2.2), does none of them work?
tootone said:
I am fairly certain I am doing it right. My mistake here was not doing a backup before I flashed anything. Let me go through what I had tried.
The RUU, I run it with my bootloader locked and I get error 158, I run it unlocked, I still get error 158.
I have tried the rom from the RUU, fastboot into ruu mode, transfer it, and I get an error
I tried putting PL80IMG in the root of my sd, it seems to flash correctly but it boots in white htc quietly brilliant screen. and flash boot.img for that rom.
I restore a rom via TWRP boots into white htc quietly brilliant screen.
and countless other things.
Click to expand...
Click to collapse
1. RUU won't work because it's 4.1.2 and you were on 4.2.2. The RUU has the HBoot in it and your device will not allow the HBoot to be downgraded because you are S-On. Only time you can use an RUU is if it is equivalent to 4.2.2 which one does not currently exist for us.
2. PL80IMG.zip's only work for those who are S-Off. Which is why it won't work for you.
3. When you restore your device using TWRP you ALSO have to rename boot.emmc.win to boot.img and flash it using fastboot:
Code:
fastboot flash boot boot.img
-- This is because, once again, you are S-On and cannot write to your boot partition EXCEPT using fastboot. You could using dumlock but to get dumlock initially set up for the first time would require your device to be able to load an OS so for you that is currently out of the question.
You must restore your device using a twrp backup, AND NOT REBOOT THE SYSTEM when it is done.
Instead, reboot the bootloader, and using fastboot, flash the boot.img which comes with the twrp backup as I just stated earlier.
Then you may reboot.
That will ALWAYS work, so if it fails, then this is an end user problem.
Sent from my C525c using Tapatalk

Categories

Resources