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
Related
ok so i wanted to put stock sense 4.0.4 one my one s its the tmobile us version and i already had a unlocked bootloader and rooted so i relocked it nicely but when i went back it to fastboot/bootloader it says ****TAMPERED**** ****RELOCKED**** ****SECURITY WARNING**** and i tried to go into twrp but nothing just bots back to fastboot/bootloader and i tried to flash cwm image and it says this
./fastboot-mac flash recovery recovery-clockwork-5.8.3.1-ville.img
sending 'recovery' (6614 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
and nothing can anyone help at all?
I recommend using an RUU to return back to stock completely. What is the H-Boot version you have?
i have 1.09.0000 hboot and my fastboost wont work on my laptop i cant install htc sync cause some problem with win 7 64 bit so i cant do that
brandontamas said:
i have 1.09.0000 hboot and my fastboost wont work on my laptop i cant install htc sync cause some problem with win 7 64 bit so i cant do that
Click to expand...
Click to collapse
For me it works on 64 bit win7
If I helped in any way please hit thanks
Run an RUU.
Sent from my locked, tampered ville
brandontamas said:
i have 1.09.0000 hboot and my fastboost wont work on my laptop i cant install htc sync cause some problem with win 7 64 bit so i cant do that
Click to expand...
Click to collapse
You don't need HTC sync, just download the drivers, and this way fastboot will work. Then run the RUU 1.84 while in fastboot and it should update.
ok i tired to use the ruu and it failed and i called htc and im just going to get it fixed by theme thanks for trying guys
You will most likely end up with a higher hboot with more restrictions.
As long as you can get into hboot/fastboot, you're not bricked. I don't believe it is ever necessary to re-lock and ruu. Especially on lower hboots. It may sometimes be necessary to flash a stock recovery, but that's it.
What I think you should have done (I realize that this is not helpful to you anymore at this point, but maybe interesting to others) is format system, data, cache, and then just flash the system and boot images from the RUU and SuperSu in recovery.
You could even have flashed all images from the RUU in recovery (system, boot, radio, adsp, wncss, rpm, tz).
-Jobo
Well I tried flashing a boot image from a rom and nothing it says security warning and doesn't flash
As long as you're (re-)locked, you can't flash anything.
I was able to RUU 1.84 version, however, all I get is the HTC white screen and then reboot over and over again.
dnwong said:
I was able to RUU 1.84 version, however, all I get is the HTC white screen and then reboot over and over again.
Click to expand...
Click to collapse
This phone is just a pain in the A$$. When it comes to rooting, restoring and etc.
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}
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
Hello, after looking into my problem all night (it is 4 a.m. now) I still cannot get my One X out of its issue.
Background to this story:
Bought this phone from a friend who had TWRP2 as the recovery, unlocked, s-on, supercid. I wanted to upgrade to a newer ROM, specifically Carbon on Jellybean 4.2.2, and I needed to update hboot to accept the newer ROM. Follow the procedures of multiple threads and they all lead me down the same path of re-locking your bootloader and let the install do the rest. However, the installer has failed multiple times (error codes 140 and 158) and I am now stuck and have no idea where to go next.
The current status of the One X is not to great. It now has a relocked bootloader, HBOOT version of 2.14.0000, A broken recovery, what seems to be a mismatched baseband, Stuck at FASTBOOT USB, no ADB, will not boot into a ROM, RUU will not complete its job (fails at sending ROM), and I am all out energy and grammar.
*Trying to re-unlock the bootloader via HTCdev will NOT unlock it.
I am stuck, (yea I am a noob). If you need anymore info, just ask.
I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.
Flashing the stock recovery only really applies when you're trying to take an OTA, it isn't required for an RUU.
Sent from my Evita
whoooops just kidding then. might worth a shot to give it a try though? I was just tossing out ideas.
brotherross said:
I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
I am not exactly sure how to do that.
I honestly don't think that's going to help you anyway.
Sent from my Evita
timmaaa said:
I honestly don't think that's going to help you anyway.
Sent from my Evita
Click to expand...
Click to collapse
Alright, gonna need to fix it later. (Recovery still broken, I assume because of the failed RUU)
Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
brotherross said:
After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).
redpoint73 said:
Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).
Click to expand...
Click to collapse
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Anytype of backup was made on the phone with TWRP, if TWRP still exists on the phone, it should be there.
I have not tried flashing TWRP back. I can try that next, can you point me in the right direction? Which version of TWRP do you recommend? (I am a noob)
"With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot." I am not aware of this, (again, noob) do I just extract the boot.img from the zip and use 'fastboot flash boot boot.img' ?
It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita
timmaaa said:
It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from . Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita
Click to expand...
Click to collapse
I may need to reiterate, that my bootloader is still locked.
MDAWG25 said:
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Click to expand...
Click to collapse
This is why you are getting errors 140 and 158. As timmaaa mentioned, you can't run an older RUU than the hboot that is already on your phone. The RUU you stated is very old, the 1.73 firmware with 1.09 hboot that came out at the phone's release. You are on hboot 2.14, so once the RUU sees that your hboot version is greater than that of the RUU (1.09), it fails.
Thye 3.18 RUU (which comes with hboot 2.14) would be what you want. BUT as already mentioned, you should not run this with S-on and SuperCID, as there is a bug with the Jellybean RUUs where this combo will brick the phone (not fixable without JTAG or new motherboard).
Follow timmaaa's steps in the previous post.
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
You might be in a catch-22 here then. As you know, you can't install custom recovery with a relocked bootloader (and S-on). You can keep trying to unlock it, but I'm not sure if that can be done if the phone can't boot.
MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
Sorry, I missed that. As Redpoint said above, you might be in a catch 22 situation here unfortunately.
Sent from my Evita
Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.
redpoint73 said:
Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.
Click to expand...
Click to collapse
I am currently not home to interface with the device physically (RDP). I should be returning around 4PM EST.
The superCID was written by the previous owner. Writing a generic CID (like HTC_001) is not an option with s-on, is it?
*Are there any RUUs that won't brick when flashing?
<Sorry for the double post but this post is different then my last>
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.
You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
MDAWG25 said:
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.
Click to expand...
Click to collapse
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita
timmaaa said:
You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita
Click to expand...
Click to collapse
Fastboot claims it wrote the recovery image, it just failed the signature check, unless it reverted, should it still be there?
I am not home to try it. I am RDPing to my computer at home, which the phone is connected to. I should be home at 4PM EST (4 hours from now).
Here is a 'getvar all'
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT246*********** (omitted for privacy)
(bootloader) imei: 359****************** (omitted for privacy)
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
See anything out of the usual?
Being able to unlock the bootloader will solve all my issues, I should be able to try again when I get home.
It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita
timmaaa said:
It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
I won't post again until 4pm est, as I do not have full access to the device.
Thank you for your help, I really do appreciate it.
.
Hi ppl!
So, I had a working HTC One S (s4) with Bootloader Unlocked, Root, Stock rom and Custom Recovery all done many years ago. I picked it up because I want to give it to someone in my family and I decided to see how it runs Lineage OS. So I found a LOS Rom, copied it and tried to install it via the latest TWRP. I wiped all, changed Data partition to F2FS and tried to install. But it said I needed Hboot 2.16 and it only has 2.15.
So then I found out to update the Hboot I need S-Off. And apparently every method needs a working Rom which I dont have right now. So I tried to find an old CM rom that runs on Hboot 2.15 but I just cannot install it. I'm just too used to how easy is to modify the Moto X so I was overconfident with the One S. And I cannot remember any of the stuff I did with it to achieve a rooted Stock Rom.
Can someone lend me a hand please?
So I have no idea what's wrong with the phone, but I tried to install CM11 and CM12 which supposedly are hboot 2.15 compatible according to their OPs and yet when restarting I just get a blackscreen after the boot image and nothing happens. What I did wrong?
With S-ON you need to flash the boot.img via fastboot after flashing a rom via TWRP or the phone won't boot.
I got S-OFF with Viper 2.x and Facepalm. Alternatively, you can try CM11 and Rumrunner. Or you get back to stock via a RUU* and root the stock rom with TWRP and SuperSU (not sure which versions are compatible with the old android 4.1). After that you should be able to use Sunshine (costs 25 bucks).
* Check your firmware version with fastboot getvar all (either "version-main" or "main version") and find a RUU with the same version.
Flippy498 said:
With S-ON you need to flash the boot.img via fastboot after flashing a rom via TWRP or the phone won't boot.
I got S-OFF with Viper 2.x and Facepalm. Alternatively, you can try CM11 and Rumrunner. Or you get back to stock via a RUU* and root the stock rom with TWRP and SuperSU (not sure which versions are compatible with the old androud 4.1). After that you should be able to use Sunshine (costs 25 bucks).
* Check your firmware version with fastboot getvar all (either "version-main" or "main version") and find a RUU with the same version.
Click to expand...
Click to collapse
Wow, many thanks! Such an easy thing I didnt see posted in all the forums I scourged. Now the phone finally boots.
Btw, I got version-main 3.16.401.10, and I found a RUU for 3.16.401.8 I guess it's ok to use?
You'll need to try. If it was a One M9 then I'd say yes it'll work. However, the One S is so much older and it's been ages since mine was S-ON so I'm not completely sure.
Edit: There won't happen anything bad if it's not the correct RUU. It'll just abort the process before it really starts flashing.
Edit2: I found the needed RUU on AFH. I've been working together with Krocko, in the past. Therefore, I know that he's a reliable source. Boot the phone to fastboot USB mode and flash the file with
Code:
fastboot flash zip PJ40IMG_Ville_U_JB_45_S_HTC_Europe_3.16.401.10_Radio_1.11.50.05.28_10.27.50.08L_release_368741_signed.zip
Check the file's MD5 checksum before you flash so that you can rest assured that it didn't get damaged during the download. The desired value is mentioned on the download page.
Edit3: You'll need to use that command twice. The first try will probably end with error 90 or something like that.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Edit3: You'll need to use that command twice. The first try will probably end with error 90 or something like that.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Darn, I can't thank you enough for all the support!
So indeed it failed, but not the Error 9X, rather "FAILED (remote: not allowed)" Google say such error results when the Bootloader is locked but mine is unlocked. And the MD5 is ok.
Code:
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILED (remote: not allowed)
My bootloader says the following info:
**TAMPERED** (TWRP 3.1)
**UNLOCKED**
VLE PVT SHIP S-ON RL
HBOOT-2.15.000
OpenDSP-v31.1.0.45.0815
eMMC-bot
Dec 14 2012,17:10:57:-1
I'm on Windows 10 and the phone is recognized no problem.
So, I'm lost...
EDIT: And CID = HTC__001
Ah, now that you mention it: On the One S the bootloader needs to be locked or relocked for flashing RUUs if the phone is S-ON. My bad. Sorry.
Code:
fastboot oem lock
In addition, flashing RUUs via fastboot (that's what the *.exe versions do, as well) can be a bit tricky and since the One S has no micro SD card slot there's no alternative method...
I don't have a link with instructions at hand that are specific for the One S but I can link you some troubleshooting tips that I posted in the One M9 forum. They're universal and should theoretically be able to help you (if one of the mentioned problems actually is your issue).
Flippy498 said:
Ah, now that you mention it: On the One S the bootloader needs to be locked or relocked for flashing RUUs if the phone is S-ON. My bad. Sorry.
Code:
fastboot oem lock
In addition, flashing RUUs via fastboot (that's what the *.exe versions do, as well) can be a bit tricky and since the One S has no micro SD card slot there's no alternative method...
I don't have a link with instructions at hand that are specific for the One S but I can link you some troubleshooting tips that I posted in the One M9 forum. They're universal and should theoretically be able to help you (if one of the mentioned problems actually is your issue).
Click to expand...
Click to collapse
Ahhh that explains. Thanks!
One question before I do that though, to unlock it again, do I need the unlock bin file from HTC again?
Sent from my XT1095 using Tapatalk
Yeah, but you'll probably need a new one. At least I had to request a new one whenever I flashed a RUU on my One S.
Sent from my HTC One M9 using XDA Labs
Perfect, I'll do that then, a thousand thanks for all your help!
Sent from my XT1095 using Tapatalk