I want to return my cellphone to the service center to repair my camera.But I s-off and unlock my device,so I want to s-on it back.However I only have the 1.29 hboot version RUU zip,and I upgraded my Hboot to 1.55 version and I s-on it and locked it now.And I trying to restore it by the RUU,it kept showing the 155 error. What should I do now , I can't get into the system now and the hboot showing the red title: security warning. Should I just send it to the service center? :crying::crying:
cycber said:
I want to return my cellphone to the service center to repair my camera.But I s-off and unlock my device,so I want to s-on it back.However I only have the 1.29 hboot version RUU zip,and I upgraded my Hboot to 1.55 version and I s-on it and locked it now.And I trying to restore it by the RUU,it kept showing the 155 error. What should I do now , I can't get into the system now and the hboot showing the red title: security warning. Should I just send it to the service center? :crying::crying:
Click to expand...
Click to collapse
You cannot downgrade on S-ON
try to unlock and gain s-off again
cycber said:
I want to return my cellphone to the service center to repair my camera.But I s-off and unlock my device,so I want to s-on it back.However I only have the 1.29 hboot version RUU zip,and I upgraded my Hboot to 1.55 version and I s-on it and locked it now.And I trying to restore it by the RUU,it kept showing the 155 error. What should I do now , I can't get into the system now and the hboot showing the red title: security warning. Should I just send it to the service center? :crying::crying:
Click to expand...
Click to collapse
You'll need to get s off using rumrunner again
To install the ruu you need to downgrade your hboot, which is only possible when you are s-off
stovie_steve said:
You'll need to get s off using rumrunner again
To install the ruu you need to downgrade your hboot, which is only possible when you are s-off
Click to expand...
Click to collapse
But after I re s-off my device,the RUU still can't use and keep showing Error 155.
And I tried to use fastboot flash it,it shows this:
sending 'zip' (1284373 KB)... OKAY
writing 'zip'... INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
What should I do now?
Thanks
cycber said:
But after I re s-off my device,the RUU still can't use and keep showing Error 155.
And I tried to use fastboot flash it,it shows this:
sending 'zip' (1284373 KB)... OKAY
writing 'zip'... INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
What should I do now?
Thanks
Click to expand...
Click to collapse
Maybe your MID or CID is different for the RUU?
What is your MID? Have you changed your CID for the RUU? And did you downgrade the hboot?
EDIT:
You are using hboot version 1.29? Surely 1.44 is the earliest hboot??
Related
Hello,
im from Germany, so sorry for my bad english.
I have an HTC One, hboot 1.54, S-ON and unlocked via HTV-Dev.
Now i want to go back to stock, cause of warranty.
I would gain s-off with rumrunner and then downgrade to hboot 1.44.
From 1.44 i would install the original German unbranded RUU an lock the bootloader with moonshine.
Is it this way going?
Tekkno_Fan said:
Hello,
im from Germany, so sorry for my bad english.
I have an HTC One, hboot 1.54, S-ON and unlocked via HTV-Dev.
Now i want to go back to stock, cause of warranty.
I would gain s-off with rumrunner and then downgrade to hboot 1.44.
From 1.44 i would install the original German unbranded RUU an lock the bootloader with moonshine.
Is it this way going?
Click to expand...
Click to collapse
1- rumrunner to get s-off -> yes
2- no need for moonshine
3- do you need to go S-ON?
read through my guide in my signature, then think about it, then read it again , then think about it again
and let me know where you need help.
Is it possible to dowgrade the hboot 1.54 to 1.44 if the phone is shipped with 1.54?
Because i know it from other devices, that i can only downgrad to a bootloader version, that come with the phone.
Edit: Tried to downgrad from hboot 1.54 to 1.44 FAILED:
sending 'zip' (501 KB)...
OKAY [ 0.245s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.726s
Click to expand...
Click to collapse
EDIT2:
Got it, just changed CID to HTC__001
Via:
fastboot oem writecid HTC__001
Tekkno_Fan said:
Is it possible to dowgrade the hboot 1.54 to 1.44 if the phone is shipped with 1.54?
Because i know it from other devices, that i can only downgrad to a bootloader version, that come with the phone.
Edit: Tried to downgrad from hboot 1.54 to 1.44 FAILED:
EDIT2:
Got it, just changed CID to HTC__001
Via:
fastboot oem writecid HTC__001
Click to expand...
Click to collapse
take it easy and dont rush things, if you need help, do ask.
and since you're s-off don't go s-on, unless you know EXACTLY when to do it!! (preferably, never)
nkk71 said:
take it easy and dont rush things, if you need help, do ask.
and since you're s-off don't go s-on, unless you know EXACTLY when to do it!! (preferably, never)
Click to expand...
Click to collapse
All is back to Stock, including S-ON.
I bring the Phone on Monday to my reseller, and he will fix my microphone issue
Thx to all
I have an HTC One that feels kinda bricked as it won't run a stock RUU (keeps giving me bootloader version error)
Here's what I have on the bootloader screen:
Tampered
Relocked
M7 WLS PVT SHIP S-ON RH
HBOOT 1.55.0000
RADIO 1.00.20.0315
OPENDSP V32.120.274.0909
OS 3.05.651.6
I've tried with several stock RUU files, but I imagine they don't work because it's not S-OFF so I can't downgrade as I please.
Then I try with this file: RUU_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.05.651.6_Radio_1.00.20.1108_NV_SPCS_4.38_003_release_348053_signed_2
which seems to be the current OS installed and the file doesn't work, it just quits on its own. Running Windows 7 64x.
I've downloaded the same file a few times (from an XDA thread, no less) and it won't budge.
Any ideas?
Try a different cable
Different USB port
USB 2 works the best
The installer quits (crashes?) right after I accept the terms of user blah blah agreement. Way before I have anything plugged in.
Pigbenis12 said:
The installer quits (crashes?) right after I accept the terms of user blah blah agreement. Way before I have anything plugged in.
Click to expand...
Click to collapse
Have you tried it with the device plugged in?
Also right click and run as admin
Yep, it will just crash and I need to run again. Maybe I'll look from a different download source.
Pigbenis12 said:
I have an HTC One that feels kinda bricked as it won't run a stock RUU (keeps giving me bootloader version error)
Here's what I have on the bootloader screen:
Tampered
Relocked
M7 WLS PVT SHIP S-ON RH
HBOOT 1.55.0000
RADIO 1.00.20.0315
OPENDSP V32.120.274.0909
OS 3.05.651.6
I've tried with several stock RUU files, but I imagine they don't work because it's not S-OFF so I can't downgrade as I please.
Then I try with this file: RUU_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.05.651.6_Radio_1.00.20.1108_NV_SPCS_4.38_003_release_348053_signed_2
which seems to be the current OS installed and the file doesn't work, it just quits on its own. Running Windows 7 64x.
I've downloaded the same file a few times (from an XDA thread, no less) and it won't budge.
Any ideas?
Click to expand...
Click to collapse
You are going to have to wait for the new RUU to come out, from what TommyJones has said soon. If you had S-off you could run the KK to JB downgrade, then run the RUU found here: http://forum.xda-developers.com/showthread.php?t=2634256
Why do you need to run the RUU? If you are having errors, can you do a hard reset?
weidnerj said:
You are going to have to wait for the new RUU to come out, from what TommyJones has said soon. If you had S-off you could run the KK to JB downgrade, then run the RUU found here: http://forum.xda-developers.com/showthread.php?t=2634256
Why do you need to run the RUU? If you are having errors, can you do a hard reset?
Click to expand...
Click to collapse
I need to run the RUU because there's no functional OS installed. It was given to me like this, unfortunately.
It's a project, so to speak.
Sure the drivers are installed correctly?
I have the latest HTC Sync installed.
C:\Android>fastboot flash zip firmware6516.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1174208 KB)...
OKAY [ 56.854s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.952s
This is the zip method.
Pigbenis12 said:
I have the latest HTC Sync installed.
C:\Android>fastboot flash zip firmware6516.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1174208 KB)...
OKAY [ 56.854s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.952s
This is the zip method.
Click to expand...
Click to collapse
Check PM
Seen, read, replied.
Having the same issue
Pigbenis12 said:
Seen, read, replied.
Click to expand...
Click to collapse
Could you please post it here if you ever have got it to work ?
Hi all,
Several months ago I have converted my HTC One M7 to GPE.
Now I need to return back to stock. I have followed the (quite simple) guide that I found in this forum but I don't seem able to reach my goal.
I need an helping hand so bad.
This is what I have tried so far:
- Changed my CID from GOOGL001 to HTC__001 (OK)
- Re-Locked my bootloader.
- Recovery is GPE stock. ROM is GPE stock (4.4.4)
- Executed "fastboot oem rebootRUU" and then
- fastboot flash zip ruu.zip (where ruu.zip is the full stock, Wipe ZIP 6.06.401.1 rom taken from here: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
- Issued the above command twice, as usual.
After rebooting my device, the HTC logo (powered by Android) appears followed by the old Google Edition animation (ie: 4 colored spinning circles).
The phone seams to remain stuck at this point.
I have restored the GPE Rom and everything seems to be perfectly working.
Tried the above steps twice then finally gave up.
Has anybody here managed to revert his device from GPE to WWE Sense (.401.) ?
Any clues please?
Thanks a lot.
slvrbllt said:
Hi all,
Several months ago I have converted my HTC One M7 to GPE.
Now I need to return back to stock. I have followed the (quite simple) guide that I found in this forum but I don't seem able to reach my goal.
I need an helping hand so bad.
This is what I have tried so far:
- Changed my CID from GOOGL001 to HTC__001 (OK)
- Re-Locked my bootloader.
- Recovery is GPE stock. ROM is GPE stock (4.4.4)
- Executed "fastboot oem rebootRUU" and then
- fastboot flash zip ruu.zip (where ruu.zip is the full stock, Wipe ZIP 6.06.401.1 rom taken from here: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
- Issued the above command twice, as usual.
After rebooting my device, the HTC logo (powered by Android) appears followed by the old Google Edition animation (ie: 4 colored spinning circles).
The phone seams to remain stuck at this point.
I have restored the GPE Rom and everything seems to be perfectly working.
Tried the above steps twice then finally gave up.
Has anybody here managed to revert his device from GPE to WWE Sense (.401.) ?
Any clues please?
Thanks a lot.
Click to expand...
Click to collapse
wel if I read your post right, all you have flashed is the 401 firmware, you've not actually flashed the 401 rom or RUU, so all you changed was the firmware, the link you supplied is firmwares and HBOOT only, its not rom's
slvrbllt said:
Hi all,
Several months ago I have converted my HTC One M7 to GPE.
Now I need to return back to stock. I have followed the (quite simple) guide that I found in this forum but I don't seem able to reach my goal.
I need an helping hand so bad.
This is what I have tried so far:
- Changed my CID from GOOGL001 to HTC__001 (OK)
- Re-Locked my bootloader.
- Recovery is GPE stock. ROM is GPE stock (4.4.4)
- Executed "fastboot oem rebootRUU" and then
- fastboot flash zip ruu.zip (where ruu.zip is the full stock, Wipe ZIP 6.06.401.1 rom taken from here: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
- Issued the above command twice, as usual.
After rebooting my device, the HTC logo (powered by Android) appears followed by the old Google Edition animation (ie: 4 colored spinning circles).
The phone seams to remain stuck at this point.
I have restored the GPE Rom and everything seems to be perfectly working.
Tried the above steps twice then finally gave up.
Has anybody here managed to revert his device from GPE to WWE Sense (.401.) ?
Any clues please?
Thanks a lot.
Click to expand...
Click to collapse
change cid to htc__001 and if required, your MID to PN0710000
no need to relock bootloader when s-off
flash the appropriate ruu.zip or .exe, there is no 6.06.401 ruu.
reboot phone and enjoy
if you return back to stock for warranty purpose you will need to set back the bootloader to "locked" not "relocked"and remove the tampered flag before running the ruu.
for more information check nkk71 guide linked in my signature.
list of ruu for your phone:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
dont use the 1.20.401.1 ruu, its a pre-release version with no ota updates.
Seanie280672 said:
wel if I read your post right, all you have flashed is the 401 firmware, you've not actually flashed the 401 rom or RUU, so all you changed was the firmware, the link you supplied is firmwares and HBOOT only, its not rom's
Click to expand...
Click to collapse
I didn't realise that it was just the firmware.
alray said:
[...] omissis [...]
Click to expand...
Click to collapse
I will try to flash the exe you have linked as soon as I get back from my holidays.
Thank you guys! I've really appreciated your help.
I'm gonna make things easy. Ive used this method twice for returning to stock, as ive had to return my phone for issues twice. I guarentee that it works. youtube.c om/watch?v=uEBAKSDxbkI. This is 100% stock. :highfive:
Mickey Meyers said:
I'm gonna make things easy. Ive used this method twice for returning to stock, as ive had to return my phone for issues twice. I guarentee that it works. youtube.c om/watch?v=uEBAKSDxbkI. This is 100% stock. :highfive:
Click to expand...
Click to collapse
and that's the easy way ?........lol, took him 10 mins to lock his bootloader, the easy way is to reboot to your bootloader and type fastboot oem lock, 2 seconds its done, that applies to firmware flashes, ruu flash commands and then to s-on too.
alray said:
change cid to htc__001 and if required, your MID to PN0710000
no need to relock bootloader when s-off
flash the appropriate ruu.zip or .exe, there is no 6.06.401 ruu.
reboot phone and enjoy
if you return back to stock for warranty purpose you will need to set back the bootloader to "locked" not "relocked"and remove the tampered flag before running the ruu.
for more information check nkk71 guide linked in my signature.
Click to expand...
Click to collapse
I'm back and so are my issues.
Following your suggestions I have downloaded the following RUU:
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Despite I'm S-OFF, I usually keep my bootloader (re)locked for safety reasons.
My bootloader screen shows:
Code:
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.54.0000
RADIO-4T.27.3218.09
OpenDSP-v32.120.274.0909
OS-4.09.1700.1
eMMC-boot 2048MB
Jun 16 2014,20:13:15.8
As you can see I have already changed my CID.
When I launch the exe it start trying to flash but I immediately get an Error 158 and it quits.
I extracted the rom.zip from the file and tried the fastboot method.
This is what I get upon executing the command:
Code:
fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
[b]Invalid sparse file format at header magi[/b]
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
sending sparse 'zip' (1490936 KB)...
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
OKAY [ 61.513s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 61.715s
Did anybody run into similar issues before?
Any help would be pretty much appreciated.
Thanks, guys.
slvrbllt said:
I'm back and so are my issues.
Following your suggestions I have downloaded the following RUU:
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Despite I'm S-OFF, I usually keep my bootloader (re)locked for safety reasons.
My bootloader screen shows:
Code:
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.54.0000
RADIO-4T.27.3218.09
OpenDSP-v32.120.274.0909
OS-4.09.1700.1
eMMC-boot 2048MB
Jun 16 2014,20:13:15.8
As you can see I have already changed my CID.
When I launch the exe it start trying to flash but I immediately get an Error 158 and it quits.
I extracted the rom.zip from the file and tried the fastboot method.
This is what I get upon executing the command:
Code:
fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
[b]Invalid sparse file format at header magi[/b]
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
sending sparse 'zip' (1490936 KB)...
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
OKAY [ 61.513s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 61.715s
Did anybody run into similar issues before?
Any help would be pretty much appreciated.
Thanks, guys.
Click to expand...
Click to collapse
use the 1.28.401.7 ruu.zip, there are some issues with 4.x ruus. Do not flash it using a windows 8.1 computer
alray said:
use the 1.28.401.7 ruu.zip, there are some issues with 4.x ruus. Do not flash it using a windows 8.1 computer
Click to expand...
Click to collapse
Well, guess what ?
Code:
target reported max download size of 1526722560 bytes
sending 'zip' (1009784 KB)...
OKAY [ 37.420s]
writing 'zip'...
(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: 42.758s
I've also tried with super CID but got the same results.
Any other hints ?
slvrbllt said:
Well, guess what ?
Code:
target reported max download size of 1526722560 bytes
sending 'zip' (1009784 KB)...
OKAY [ 37.420s]
writing 'zip'...
(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: 42.758s
I've also tried with super CID but got the same results.
Any other hints ?
Click to expand...
Click to collapse
How about trying a Guru Reset 5.11.401.10 you will have to unlock your bootloader and put TWRP back on your phone to flash it. It should take you back to stock and at the end it will ask you if you want to root. If you want to go complete stock just select the no option.
majmoz said:
How about trying a Guru Reset 5.11.401.10
Click to expand...
Click to collapse
I will.
But wasn't I supposed to flash any RUU I like given I'm S-OFF ?!?!
I would like to figure out why my device isn't flashing the stock ruu at all...
slvrbllt said:
Well, guess what ?
Code:
target reported max download size of 1526722560 bytes
[B][COLOR="Red"]sending 'zip' (1009784 KB)...[/COLOR][/B]
Any other hints ?[/QUOTE]
you should have checked MD5, the actual filesize is 1009792KB
here's an AFH mirror: [URL="https://www.androidfilehost.com/?fid=23329332407584993"]RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7[/URL]
Click to expand...
Click to collapse
nkk71 said:
you should have checked MD5, the actual filesize is 1009792KB]
Click to expand...
Click to collapse
You're right! I extracted the rom.zip from the ruu but did not decrypted it.
The one you have suggested worked fine.
I'm back stock now.
Thank you everybody for your help.
PS: On a side note, GURU reset saved me from the hassle of going through all the updates from 1.28.401.7 up to 6.09.401.5.
Cheers
slvrbllt said:
PS: On a side note, GURU reset saved me from the hassle of going through all the updates from 1.28.401.7 up to 6.09.401.5.
Cheers
Click to expand...
Click to collapse
you mean after you downgraded using ruu 1.28.401.7, you flashed a newer Guru Reset ROM, and took OTAs after that?
I'm glad it worked for you, but I would highly recommend against that, because the firmware upgrades (within the OTAs) are incremental, so skipping versions could potentially miss important upgrades within the firmwares, or even worse send you into QHSUSB_DLOAD mode
eg, assuming you installed a 4.xx Guru Reset ROM, and took OTA update to 5.xx, then there's a high chance you would have ended in QHSUSB_DLOAD mode, because the 5.xx firmware (inside the OTA) is missing SBL3
nkk71 said:
you mean after you downgraded using ruu 1.28.401.7, you flashed a newer Guru Reset ROM, and took OTAs after that?
Click to expand...
Click to collapse
Well, after having flashed 1.28.401.7 (I was on latest GPE before), it started downloading a few OTAs (if I recall well, I applied all otas up to version 2.x).
It took me 1.5hrs to get to this point, so I gave up and installed the Guru Reset 5.11.401.10 instead.
Upon reboot it downloaded the latest OTA and jumped straight to 6.09.401.5.
The smartphone seems to be working fine. How can I be sure that all the required pieces are in place?
Hi,
I'm totally Helpless.... Im trying do perform sim unlock on my sprint HTC One for four days... My phone is rooted, custom recovery (TWRP), S-Off, Hboot is downgraded from 1.57 to 1.55, my bootloader is relocked, but i cant perform downgrade to 4.3 or 4.1... can anyone help me?
If I try to flash RUU, it says Error 155 and if I try to flash it via CMD it shows me FAILED (remote: 32 header error)...
I'm totally HOPELESS now
Try THIS
Thanks for reply,
I already tried (i think) All of guides here on XDA or other sites... link u provide shows me error" FAILED (remote: 32 header error)" while "pushing" rom into device...
SkopiX said:
Thanks for reply,
I already tried (i think) All of guides here on XDA or other sites... link u provide shows me error" FAILED (remote: 32 header error)" while "pushing" rom into device...
Click to expand...
Click to collapse
Did you re-lock your bootloader?
Did you use the correct RUU zip (decrypted)
Yea, my bootloader is RELOCKED and I think Yes, im using correct RUU
*** TAMPERED***
***RELOCKED***
s-OFF
CID- 11111111
HBOOT- 1.55
Radio- 1.00.20.0626 (i think i tried flash radio [some guide told me])
this is what I can see when i go to bootloader
//edit 2: finally succes i downloaded another RUU from htc1guru and finally it worked
//edit 3: now all works
I was using the latest Viper Rom and my Camera busted on my phone. So naturally I needed to get the M7 back to stock. I have never done it before so I did some searching and found the method right in this same forum.
So Walking through the instructions everything went well
I locked the bootloader
went through the process of flashing the stock rom with fastboot and it keeps erroring out. I am consistently getting "FAILED (status read failed (Too many links))" I tried the RUU and I keep getting unknown errors from those too. I have tried multiple PC and different usb cables and ports. I am completely stumped.
I was under the impression that it didn't matter which stock ROM you tried but I did try many different ones.
Would anyone have any suggestions?
I'm not sure what RUU guide you used, but I and a few others have had success with the guide I wrote. Try it and follow up here or in that thread if you have issues (or if it worked for you).
http://forum.xda-developers.com/spr...de-reset-phone-using-ruu-htcfastboot-t2876110
Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.
Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!
raremind said:
Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.
Click to expand...
Click to collapse
raremind said:
Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!
Click to expand...
Click to collapse
I think this is the issue: since you are s-off, you should have ignored step 4 and not have locked your bootloader. A locked bootloader will not allow you to flash the firmware (it fails the security check since it wasn't created by HTC). Unlock your bootloader and try to flash the firmware file again. The reason I'm not sure is because it was my impression that an s-off phone ignores the locked/unlocked flag. But, I never lock my bootloader so I'm not sure.
By the way, s-off =/= unlocked and s-on =/= locked. Phones start as locked and s-on. Unlocking the bootloader through HTC Dev allows you to install custom recoveries and ROMs. However, it is limited because you are still s-on (security on). For example, you can only upgrade hboots, but can never downgrade to an older one. Same with RUUs. Being s-off is very flexible but more dangerous as you can access normally protected partitions. Hope that clears things up some.
Thank you again for your help. I seem to be a little more confused now. Line 4 of your guide states;
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
Click to expand...
Click to collapse
Why would I lock the the bootloader using "fastboot oem lock" if I already have s-on. You said you can not flash firmware with s-on but line 4 says I should before I flash firmware. What I just got from you, am I understanding right that I should not "fastboot oem lock" before you flash the firmware? If you are s-on the bootloader is already locked and you would not be able to do step 5.
I am s-off right now. Would I flash the firmware now, then s-on when run the RUU?
Unlocked bootloader does not = s-off.
My guess is you are unlocked not s-off.
S-OFF explained - by a Developer
So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.
raremind said:
So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.
Click to expand...
Click to collapse
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).
BD619 said:
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).
Click to expand...
Click to collapse
That's just the thing. I am s-on and relocked and every RUU I have tried failed. I have tried it with fastboot the exe and everything else under the sun. Everything I have tried has failed. here is what I am seeing:
Code:
*** TAMPERED ***
*** RELOCKED ***
*** Security warning ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO- 1.01.20.0984_2
OpenDSP- v32.120.274.0909
OS-5.05.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42:0
I rooted and flashed TEAMWIN recovery and Viper 7.1 - My Camera started acting up and I couldn't talk on calls so I wanted to get it back to stock. The only thing I was able to do successfully trying to get it back to stock was lock the bootloader. Everything beyond that has failed.
This is what I get updating the firmware:
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking..
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830s
This is what I got when I locked the bootloader:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.199s
Trying to flash RUU I get:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot flash zip Sprint_HTC
_One_m7wls_1.29.651.7_encrypted_ROM.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1029700 KB)...
OKAY [ 37.166s]
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...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 133.077s
Running the RUU.exe I recieve an unknown error. Am I screwed?
Ok first off you are using the wrong RUU.
You need to use the 5.05.651.2 RUU
So, you are s-on and relocked (you said s-off before so that threw me off). Because you are s-on, you may not be successful flashing the firmware, hence the security warning in the first box (see the link explaining s-off that @BD619 left). I probably need to fix my guide to reflect that issue. In the second box, you get an error trying to relock which makes sense since you are already locked. In the third box, it looks like you get an error since you are trying to flash an older RUU (not allowed since you are s-on).
At this point, as BD said, you should be able to just go here and download the ruu exe (it's the first link). I run it as an administrator just to be safe. Follow the prompts and wait around ten minutes for it to do its thing.
Don't get too frustrated. The (forced) learning process from this is very valuable. BD and I are just members who have been on here long enough to have a good understanding of what's going on. Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.
Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.
Click to expand...
Click to collapse
You knew more then me lol.
My first couple posts were me begging for help because I bricked my sons Epic 4G Touch lol (posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)
BD619 said:
(posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)
Click to expand...
Click to collapse
Haha, noob! I would have replied with "Cool ROM, bro".
Well thank you both! I was able to successfully flash the 5.05.651.2 RUU. Such a simple thing that was causing me such problems. I was under the impression that the RUU version didn't make a difference. I wish they would add that to the guides! Well thanks to both of you!