Database Develop

[Q] need some help understanding lol

hi guys ive been off the htc one thread for a few months and so much has happend just need some help
ive unlocked the bootloader
done S OFF
done this http://forum.xda-developers.com/showthread.php?t=2316726
my phone is a 3uk branded rom with cidnum: H3G__001 (which i changed to fastboot oem writecid 11111111)
so now ive done them basically my phone is as good as sim free (apart from the sim lock)
so if i needed to return phone i just follow steps and reinstall any stock rom (as a 3 branded one i dont think they is any)
and 3 would never know any different
thanks

A great start would be to check the other 15,000 threads covering this subject.

Is there a question in there somewhere?

brockyneo said:
hi guys ive been off the htc one thread for a few months and so much has happend just need some help
ive unlocked the bootloader
done S OFF
done this http://forum.xda-developers.com/showthread.php?t=2316726
my phone is a 3uk branded rom with cidnum: H3G__001 (which i changed to fastboot oem writecid 11111111)
so now ive done them basically my phone is as good as sim free (apart from the sim lock)
so if i needed to return phone i just follow steps and reinstall any stock rom (as a 3 branded one i dont think they is any)
and 3 would never know any different
thanks
Click to expand...
Click to collapse
I think he is asking about what he will need to do if he needs to return to stock for a phone return/exchange.
brockyneo,
Since you are s-off you can reset everything needed before returning the phone if needed.
However since there is no RUU for your device, it will be a little harder than just re-installing a stock rom. Since you flashed a modified hboot you will need to reset all your sytem stuff back like hboot, splash screen, recovery, etc before you can relock the phone so it looks the same as it did out of the box.
I won't go into all the steps needed, but just know if you need to go back to stock there are many threads here that detail how to do so.
Just keep your bootloader unlocked and keep s-off until you need to return/exchange the device.

If you haven't flashed a custom recovery yet, do:
fastboot boot customrecovery.img
And do a backup. This will backup stock ROM and recovery. There is no 3 RUU and probably never will be, I don't know what their deal is..
Then to go back to stock, restore your backup, flash your recovery.img from your backup, change your CID back to original, flash a STOCK hboot, and last use Revone to lock the bootloader and then do s-on.
EDIT : just noticed on another thread you said you were running TrickDroid - disregard my post..
Sent from my HTC One using xda premium

ok guys i think ive screwed up big time i did a full wipe in cwm (sc card too) then was going to adb sideload the rom but now my pc doesnt reconise my phone i remember having to relock my bootloader to fix this so i went back to the original file in this thread http://forum.xda-developers.com/showthread.php?t=2316726
and relocked bootloader then when i tried to unlock it i get this error
sending 'unlocktoken' (0 KB)...
OKAY [ 0.159s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.173s
any help please

brockyneo said:
ok guys i think ive screwed up big time i did a full wipe in cwm (sc card too) then was going to adb sideload the rom but now my pc doesnt reconise my phone i remember having to relock my bootloader to fix this so i went back to the original file in this thread http://forum.xda-developers.com/showthread.php?t=2316726
and relocked bootloader then when i tried to unlock it i get this error
sending 'unlocktoken' (0 KB)...
OKAY [ 0.159s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.173s
any help please
Click to expand...
Click to collapse
Can you unlock using rev one?

redbull123 said:
Can you unlock using rev one?
Click to expand...
Click to collapse
problem i have is i have no rom installed and doesnt seem to be reconzing my phone only thing that works is fastboot

brockyneo said:
problem i have is i have no rom installed and doesnt seem to be reconzing my phone only thing that works is fastboot
Click to expand...
Click to collapse
can you post a photo of your hboot?

redbull123 said:
can you post a photo of your hboot?
Click to expand...
Click to collapse
sorry i have no way of taking a pic it was 1.44.0000

brockyneo said:
sorry i have no way of taking a pic it was 1.44.0000
Click to expand...
Click to collapse
What have you been using to unlock/lock your bootloader? HTC-Dev? This is just a guess - probably wrong, but you may need to ask for a newer unlock token and try again?

You have to go back and request a new token at htcdev.
FYI -once your bootloader is unlocked and you have s-off, KEEP IT THAT WAY. There is not really a reason to keep flipping, only if you need to return/exchange the phone.
Bootloader should not have an effect on ADB sideload. I'm unlocked and I use that all the time. If you have an issue with sideloading or something else, just post about it and someone will help, but you shouldn't need to flip your bootloader.

[Q] Unable to reunlock the hboot 1.44 bootloader on 4.2.2 GE

I got the 4.2.2 Ruu installed and in order to downgrade on dev edition i flashed the 1.44 stock Hboot.
When i try to flash the RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3 it allways shows me the error 158 while tries to flash the RUU.
So i relocked my bootloader, as some states that could solve my prob. But i got the same error 158 again.
So i wanted to reunlock the bootloader again.(Still 4.2.2 GE and the Hboot 1.44)
Normally on GE roms(1.54 hboot) u just hit "fastboot oem unlock" but on 1.44 this is impossible. So i managed to get a token id key from htc dev
for my hboot 1.44.
The token works but theres no " are u really want to unlock bl" request, like it is on stock sense roms at the end of the bl-unlock procedure.
So bl stays relocked! I
Am i stucked now on a relocked bl with no way to get it unlocked again????

Code:
fastboot oem unlock
won't every work on an HTC device, by the way what does the terminal returns?

matt95 said:
Code:
fastboot oem unlock
won't every work on an HTC device, by the way what does the terminal returns?
Click to expand...
Click to collapse
C:\Android\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot flash
unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.005s]
finished. total time: 0.162s
The terminal returns this after flashing the token. So this should be right! but bl stays relocked.
fastboot oem unlock :
C:\Android\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot oem un
lock
...
FAILED (remote: loading custom splash failed)
finished. total time: 0.002s
C:\Android\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>

That's strange, try to download again your unlockcode.bin, If it does not work then you're pretty much stucked there

matt95 said:
That's strange, try to download again your unlockcode.bin, If it does not work then you're pretty much stucked there
Click to expand...
Click to collapse
No ,new token didnt helped. Is there any chance to get the RUU.exe to work? heres the intresting part of the log of it:
Im on the right cid and mid!
<T235448><DEBUG><CMD>htc_fastboot -s SH362W900689 -d flash zip C:\Users\Bruno\AppData\Local\Temp\{164DC584-095D-4AE4-A69C-6DECA925F94E}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T235448>
<T235545><DEBUG><OUT>sending 'zip'... (1004418 KB) OKAY</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>writing 'zip'... (bootloader) rom parsing start ...</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>(bootloader) rom parsing finish ...</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>(bootloader) zip header checking...</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>(bootloader) zip info parsing...</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>FAIL22 loading zip info fail</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>FAILED (remote: 22 loading zip info fail)</OUT>

SOLVED !
Yeah man I got it finally! Somehow i was able to enter RUU mode with locked bl! Flashed a RUU and i was back in the game! I hit the token command first, which maybe caused a temp bypass,cause on the first try i rebooted bl before hiting the Ruu command, which didnt worked !
GN8 and Thanks

Yeah, with an official GPe HTC One you only unlock it using 'fastboot oem unlock' - you do NOT have to use HTCDev at all...
Taken from this HTC Blog post - http://blog.htc.com/2013/05/htc-one-google-nexus-experience/:
"***The HTC One special edition bootloader can be unlocked by standard method for “Nexus experience” devices"
Meaning you use the standard Nexus unlock procedure
EDIT: Re-read the OP, seems you have converted it to Sense so in that case, normal HTC unlock rules apply

EddyOS said:
Yeah, with an official GPe HTC One you only unlock it using 'fastboot oem unlock' - you do NOT have to use HTCDev at all...
Taken from this HTC Blog post - http://blog.htc.com/2013/05/htc-one-google-nexus-experience/:
"***The HTC One special edition bootloader can be unlocked by standard method for “Nexus experience” devices"
Meaning you use the standard Nexus unlock procedure
EDIT: Re-read the OP, seems you have converted it to Sense so in that case, normal HTC unlock rules apply
Click to expand...
Click to collapse
Yeah i know thats the way to do this on GE Roms! I solved it allready . No u cant open a sense bootloader under GE.(The request "are u really want to unlock the bl" wont appear(cause of wrong rom) and after u hit the token nothing happens and bl stays relocked .
As i described the post before i somehow "bypassed" the bl with the htc dev token to get into RUU mode.
My bl was still on relocked after i installed the new 4.3 GE RUU. For sure i could it unlock with "fastboot oem unlock" after new RUU was on!
So what ive learned?
DONT RELOCK A Hboot 1.44 BL on a GE ROM CAUSE U WILL STAY RELOCKED!

Converting Play Edition to Sense Developer Edition?

Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?

hjjfffaa said:
Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?
Click to expand...
Click to collapse
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.

fenstre said:
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.
Click to expand...
Click to collapse
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.

hjjfffaa said:
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.
Click to expand...
Click to collapse
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.

fenstre said:
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.
Click to expand...
Click to collapse
But I can downgrade to 1.44 and that would allow me to S-On and get OTA updates right? Or am I totally wrong?

Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.

hjjfffaa said:
Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.
Click to expand...
Click to collapse
You have S-off which is good. I'm going to ask you to use the BS_US001 CID. Try downloading the 1.29.1540.17 zip from HTC Dev. Do a fastboot oem rebootRUU and flash the zip from there. It should prompt you to do this twice.
Sent from my HTC One using XDA Premium 4 mobile app

Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.

hjjfffaa said:
Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2497712
You can follow that thread if you want to set the phone to locked.
I'm sorry I forgot about the 4.3 zip, use that one if you want to go straight to 4.3. Again, my apologies
Sent from my HTC One

I don't care if it says re-locked (so long as it functions how it should), I just want my Sense ROM. I already have the 4.3 Dev Edition zip, should I try flashing it with fastboot?
I tried flashing the 3.22.1540.1 zip and got this problem, which doesn't seem consistent with the one guide I've seen for this process.
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.663s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.625s
Click to expand...
Click to collapse

Try 'fastboot erase cache' and 'fastboot reboot-bootloader' before you 'fastboot oem rebootruu' and then run the fastboot flash zip filename.zip'
Sent from my HTC One

The results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot erase
cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.065s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot reboo
t-bootloader
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.038s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.359s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.318s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
Could this be a result of the 1.54 bootloader?

hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
Can you take an image of your bootloader for me real quick

gusto5 said:
Can you take an image of your bootloader for me real quick
Click to expand...
Click to collapse
Here you go.

hjjfffaa said:
Here you go.
Click to expand...
Click to collapse
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.

gusto5 said:
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.
Click to expand...
Click to collapse
Thanks for all your help. Trying a different USB port.
You were right, it did nothing.

hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
You may be right. Let's have you downgrade the Bootloader to 1.44 and then try running the RUU again.
Just remember that you already have the right MID and CID. CID you changed yourself, MID already matches as the Google Play Edition shares the same MID as the Developer edition (and a few other North American HTC Ones).

Here are the (real) results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.049s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip hbootRUU.zip
target reported max download size of 1526722560 bytes
sending 'zip' (508 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 0.516s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.

hjjfffaa said:
Here are the results:
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.
Click to expand...
Click to collapse
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app

gusto5 said:
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
All right, should I add it to the android-text file though?

[Q] Writecid results in SD/USBDISK Init error message

Hey all,
I am trying to convert my phone to the GPE (using a guide from wonderhowto). I have done this before, but unfortunately I have had to send my phone back twice for unrelated repairs, so I am now using a new phone.
I stuck Maximus ROM on the phone, but decided I wanted vanilla android for a bit, when I followed the guide I got stuck at the writecid step, I get the following error message:
fastboot oem writecid GOOGL001
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.003s]
finished. total time: 0.003s
Click to expand...
Click to collapse
I have not been able to move past this step now, and I've struggled to find any posts anywhere detailing a way around this error.
Any ideas?

Are you s-off ? Have you tried supercid ?

Seanie280672 said:
Are you s-off ?
Click to expand...
Click to collapse
Yep.
Seanie280672 said:
Have you tried supercid ?
Click to expand...
Click to collapse
Just tried that now, same results.

[Q] Need help desperately - Back to stock

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!