Database Develop

[q] need help want to go back to stock rom

Hey all Ive opened a few threads and looked at a few threads regarding wanting to go back to stock but im a noob and find somethings confusing in the guides people put up. My phone is a HTC ONE UL from rogers fully unlocked with revone soff and running ARHD 30. i would liek to go back to stock. been noticing some things lagging on my phone and i dont have a recovery as my pc which had the recovery crapped out on me.. cant find a RUU for my phone with the .exe i can only find it with .tar
can anyone help me?
thanks

crisgq27 said:
Hey all Ive opened a few threads and looked at a few threads regarding wanting to go back to stock but im a noob and find somethings confusing in the guides people put up. My phone is a HTC ONE UL from rogers fully unlocked with revone soff and running ARHD 30. i would liek to go back to stock. been noticing some things lagging on my phone and i dont have a recovery as my pc which had the recovery crapped out on me.. cant find a RUU for my phone with the .exe i can only find it with .tar
can anyone help me?
thanks
Click to expand...
Click to collapse
Well honestly I have to say I find it very strange people wanting to go back to stock, I run ARHD 13.3 and LOVE it much better than stock.
But anyway, can you also post a "fastboot getvar all" (remove IMEI and s/n)

i want to go back so i can update my firmware... was trying to do it with fastboot but was having issues... i dont know if its because im on arhd 30 but it kept on failing on loading the firmware zip saying something about my cid

crisgq27 said:
i want to go back so i can update my firmware... was trying to do it with fastboot but was having issues... i dont know if its because im on arhd 30 but it kept on failing on loading the firmware zip saying something about my cid
Click to expand...
Click to collapse
You mentioned you are S-Off, KEEP THAT!!, firmware flashing is VERY easy with S-Off check @vomer's thread: http://forum.xda-developers.com/showthread.php?t=2365506

yea i followed his steps and was getting the fail in loading the firmware

crisgq27 said:
yea i followed his steps and was getting the fail in loading the firmware
Click to expand...
Click to collapse
can it wait till tomorrow? I'm really getting :cyclops: running two threads at the same time. sorry.
I'm sure someone will come along shortly and help out, if not, I'll be back for you tomorrow.
Hit the thanks button, if you feel I've helped out

yea man no prob

crisgq27 said:
yea man no prob
Click to expand...
Click to collapse
Thanks for the Thanks, I'll be back tomorrow. In the meantime, can you post the actual error(s) you were getting. a copy/paste of your command prompt (from beginning to end) would be very helpful

crisgq27 said:
yea man no prob
Click to expand...
Click to collapse
hey man, did you get it solved, or still stuck?

yea still stuck but i had a busy weekend and work has been busy soo i havent bothered to try yet... i was reading that i should go back to ARHD 4.2.2 Rom some people say if you're in a 4.3 rom it wont work on adb command prompt

crisgq27 said:
yea still stuck but i had a busy weekend and work has been busy soo i havent bothered to try yet... i was reading that i should go back to ARHD 4.2.2 Rom some people say if you're in a 4.3 rom it wont work on adb command prompt
Click to expand...
Click to collapse
yeah adb has some issues with 4.3, but I think the updated HTC drivers v4.8.xxxx seem to work, I don't have the link, but sure a search should get you there.
but anyway, you were having firmware problems, right? those are flashed using fastboot, which works fine.
whenever you have time, explain what you want to achieve and where you're getting stuck. copy/paste of the command prompt would help

sorry meant the fastboot from command prompts that some phones with 4.2.2 firmware and on 4.3 rom the fastboot doesnt like that

crisgq27 said:
sorry meant the fastboot from command prompts that some phones with 4.2.2 firmware and on 4.3 rom the fastboot doesnt like that
Click to expand...
Click to collapse
i'm pretty sure fastboot (in command prompt) is fine irrelevant of firmware and rom version.

you would think lol i was doing some google searches on my issues and thats what some people were saying

crisgq27 said:
you would think lol i was doing some google searches on my issues and thats what some people were saying
Click to expand...
Click to collapse
can you copy/paste your command prompt? also have you confirmed the firmware you downloaded is not corrupt.

i downloaded it straight from vomer. i may try the latest 4.2.2 driver first and when i get a chance ill post up my command prompt

C:\adb>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.17.3250.14
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.29.631.4
INFOversion-misc: PVT SHIP S-OFF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: ROGER001
INFObattery-status: good
INFObattery-voltage: 4236mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.150s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader... FAILED (status read failed (Unknown error))
finished. total time: 5.550s
C:\adb>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.043s]
finished. total time: 0.044s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (1045 KB)... OKAY [ 0.419s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.906s
C:\adb>

crisgq27 said:
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (1045 KB)... OKAY [ 0.419s]
Click to expand...
Click to collapse
That doesn't sound right, 1MB. firmware packages are usually around between 20MB to 40MB. probably a bad download. download again, and check MD5 sum preferably.

after getting my cid to 111111111 it worked lol

crisgq27 said:
after getting my cid to 111111111 it worked lol
Click to expand...
Click to collapse
did fastboot getvar all confirm the updated firmware version? sounds really strange for a firmware package to be 1MB, IMHO

[Q] HTC One 802w Unicom - Failed RUU now black screen and no charge light

Hello everyone,
I have an HTC One 802w bought from china unicom version.
I followed this tutorial to S-OFF which worked successfully after unlocking with the HTCDEV method
I then went about changing it to a Google Edition using this tutorial , all was going smoothly until I needed to change the model id using this tutorial.
I believe writing the new model number failed here.
I rebooted using
fastboot oem rebootRUU
Click to expand...
Click to collapse
and got the htc logo up and then I began transferring the modified zip downloaded from that tutorial and I got a 75% status bar at which point under instruction from another poster on that thread manually rebooted.
Now at this point I have an HTC One with a black screen and no charge light, I can't see anything but I can get it recognised by the PC so her is my getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3510mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Can you offer me any help here, it would be greatly appreciated, in NZ where I live these phones cost over $1000 to import.
Cheers

I think you messed partition table . Now you have two choices. One is to flash original firmware and second is to search to find right partition to change model id. That happent because our partition table is different from international one. Anyway congrats for courage of trying that and my advice is second choice. I myself will search for that.
edit: found app in g play : partition table, getting more info
edit2: from what can i see on tutorial you folow >>>> '' Step 3: Change Your Model ID (if Necessary)
Changing your MID is actually not necessary, even if you have a different Model ID. I'll leave this here just in case you want to check, and because we still need to connect our phone and open a command prompt. '' WHY DID YOU TRYED ?
edit3: i think you must write cid to 11111111 and flash that google RUU.
Sent from my HTC 802w

criszz said:
I think you messed partition table . Now you have two choices. One is to flash original firmware and second is to search to find right partition to change model id. That happent because our partition table is different from international one. Anyway congrats for courage of trying that and my advice is second choice. I myself will search for that.
edit: found app in g play : partition table, getting more info
edit2: from what can i see on tutorial you folow >>>> '' Step 3: Change Your Model ID (if Necessary)
Changing your MID is actually not necessary, even if you have a different Model ID. I'll leave this here just in case you want to check, and because we still need to connect our phone and open a command prompt. '' WHY DID YOU TRYED ?
edit3: i think you must write cid to 11111111 and flash that google RUU.
Sent from my HTC 802w
Click to expand...
Click to collapse
Thanks for your reply Criszz,
I originally tried it without changing my model number but it failed without doing so.
I have tried a huge multitude of things of being writing a new cid but when trying to write 11111111 as you suggested i get
fastboot oem writecid 11111111
...
(bootloader) Start Verify: -1
OKAY [ 0.040s]
finished. total time: 0.044s
Click to expand...
Click to collapse
It seems the whole boot loader is fuct. I have tried heaps of roms with different variations of fastboot update, fastboot flashall, fastboot flash **individual img's** nothing seems to work.
Anymore advice or greatly apprecated I will try whatever anyone can throw at me.

Douggyt said:
Thanks for your reply Criszz,
I originally tried it without changing my model number but it failed without doing so.
I have tried a huge multitude of things of being writing a new cid but when trying to write 11111111 as you suggested i get
It seems the whole boot loader is fuct. I have tried heaps of roms with different variations of fastboot update, fastboot flashall, fastboot flash **individual img's** nothing seems to work.
Anymore advice or greatly apprecated I will try whatever anyone can throw at me.
Click to expand...
Click to collapse
flash all firmware from scratch
http://forum.xda-developers.com/showpost.php?p=44033765&postcount=765

criszz said:
flash all firmware from scratch
http://forum.xda-developers.com/showpost.php?p=44033765&postcount=765
Click to expand...
Click to collapse
Thanks again, trying that now, I think the biggest problem is the bootloader rebooting ready for RUU will update here shortly with the exact results.

Douggyt said:
Thanks again, trying that now, I think the biggest problem is the bootloader rebooting ready for RUU will update here shortly with the exact results.
Click to expand...
Click to collapse
Results
fastboot oem rebootRUU
... INFOStart Verify: -1
OKAY [ 0.044s]
finished. total time: 0.045s
Click to expand...
Click to collapse
fastboot flash zip firmware.zip
< waiting for device >
sending 'zip' (40930 KB)... OKAY [ 4.792s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 4.794s
Click to expand...
Click to collapse
fastboot reboot
rebooting...
finished. total time: 0.045s
Click to expand...
Click to collapse
Any thoughts?, thanks again.

criszz said:
flash all firmware from scratch
http://forum.xda-developers.com/showpost.php?p=44033765&postcount=765
Click to expand...
Click to collapse
Sorry I didn't reply with a quote so wasn't sure you would see my update.

that must be working, try another firmware or flash ruu.
did you runn that command as post said TWICE?

criszz said:
that must be working, try another firmware or flash ruu.
did you runn that command as post said TWICE?
Click to expand...
Click to collapse
Apologies, i just put it one return for the second command buut yes each time i run it I get
sending 'zip' (40930 KB)... OKAY [ 4.220s]
writing 'zip'... FAILED (remote: not allowed)
Click to expand...
Click to collapse
Am downloadling some other firmwares to try.
I am still less than an amatuer when it comes to doing these things but the more I read I'm guessing the is restarting really quickly rather than going into Fastboot or Ruu.
When i hold down the power and down vol it quickly disconnects then reconnects to the pc.
Look forward to your next thought and of course will update straight away if one of the other firmwares help.
Cheers

You tried to install on Dual Sim firmware from HTC One. Of course it will not work for you. Firmware from the HTC One does not fit into the HTC Dual Sim.
In addition, you have to reinstall native hboot one that was in the firmware HTC One. And this is very dangerous. Restoring the damaged hboot at home is almost impossible.

drpweb said:
You tried to install on Dual Sim firmware from HTC One. Of course it will not work for you. Firmware from the HTC One does not fit into the HTC Dual Sim.
In addition, you have to reinstall native hboot one that was in the firmware HTC One. And this is very dangerous. Restoring the damaged hboot at home is almost impossible.
Click to expand...
Click to collapse
criszz said:
that must be working, try another firmware or flash ruu.
did you runn that command as post said TWICE?
Click to expand...
Click to collapse
Thanks for your input here guys, as drpweb stated it had the wrong firmware put on it.
After alot of trial and error I have sent it away to be flashed back to stock, if the company come through for me I will put up their details and costs here in case anyone else finds themselves in the same situation.
Cheers

Do you have solved this probelem
Douggyt said:
Thanks for your input here guys, as drpweb stated it had the wrong firmware put on it.
After alot of trial and error I have sent it away to be flashed back to stock, if the company come through for me I will put up their details and costs here in case anyone else finds themselves in the same situation.
Cheers
Click to expand...
Click to collapse
I have the same problem like you? Did you solved it?
When yes, how to do that?

theFAY89 said:
I have the same problem like you? Did you solved it?
When yes, how to do that?
Click to expand...
Click to collapse
I have sent the phone away to multiple repair agents even authorised HTC agents and no one can seem to reflash the chinese dual sim 802w's yet but fingers crossed soon.
I would just be very careful whom you send it to check with HTC they are authorised, I think Taiwan would be your best bet, thats where im going to try next will update this post with results and contact details of the repairer if successful.
Cheers

Douggyt said:
I have sent the phone away to multiple repair agents even authorised HTC agents and no one can seem to reflash the chinese dual sim 802w's yet but fingers crossed soon.
I would just be very careful whom you send it to check with HTC they are authorised, I think Taiwan would be your best bet, thats where im going to try next will update this post with results and contact details of the repairer if successful.
Cheers
Click to expand...
Click to collapse
I had the same issue. My Phone got repaired by doing a boardswap. Gonna pick it up today, no idea about the costs yet.

WreckTangle said:
I had the same issue. My Phone got repaired by doing a boardswap. Gonna pick it up today, no idea about the costs yet.
Click to expand...
Click to collapse
Thanks for the feedback WreckTangle (Dig the handle btw)
It would be great if its a successful repair if you could let me know the contact details of the repair agent and what it cost you.
The repair agent (HTC Authorized and Recommended) I sent it to couldn't seem to source any parts, they also seemingly couldn't be bothered trying.
Cheers

Douggyt said:
Hello everyone,
I have an HTC One 802w bought from china unicom version.
I followed this tutorial to S-OFF which worked successfully after unlocking with the HTCDEV method
I then went about changing it to a Google Edition using this tutorial , all was going smoothly until I needed to change the model id using this tutorial.
I believe writing the new model number failed here.
I rebooted using and got the htc logo up and then I began transferring the modified zip downloaded from that tutorial and I got a 75% status bar at which point under instruction from another poster on that thread manually rebooted.
Now at this point I have an HTC One with a black screen and no charge light, I can't see anything but I can get it recognised by the PC so her is my getvar all
Can you offer me any help here, it would be greatly appreciated, in NZ where I live these phones cost over $1000 to import.
Cheers
Click to expand...
Click to collapse
1. extract firmware.zip from OTA_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.39.1402.1-2.36.1402.1_release_339019
2.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
3. :victory:

style_arun said:
1. extract firmware.zip from OTA_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.39.1402.1-2.36.1402.1_release_339019
2.
3. :victory:
Click to expand...
Click to collapse
I have the same problem... Black screen, no charge light, but PC connection sound. Fastboot working.
I can't flash firmware zip (error: not allowed)

Any update??
Got the same problem here. Any update??

Alright guys. I've had this problem exactly 12 months ago. after I flashed a wrong RUU or something. I was told there was no solution. I am checking back now and see that there is still no solution. Is my HTC One 802W officially a paperweight?

I am having the exactly same problem as discussed here. Anyone on this page got the solution or know the solution or successfully repaired by an external expert from shop please tell the solution...

[SOLVED] Unroot Three UK HTC One

Hi everyone,
I'm having some issues with my HTC One and might need to send it back for Warranty repair. I can't find the RUU anywhere for Three UK.
Does anyone know a way for me to unroot my HTC One, so to speak?
I am a bit of a noob, so go easy on me!
Thanks.

mrgreeny said:
Hi everyone,
I'm having some issues with my HTC One and might need to send it back for Warranty repair. I can't find the RUU anywhere for Three UK.
Does anyone know a way for me to unroot my HTC One, so to speak?
I am a bit of a noob, so go easy on me!
Thanks.
Click to expand...
Click to collapse
There is no RUU for you, check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)

nkk71 said:
There is no RUU for you, check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)
Click to expand...
Click to collapse
So is your route not possible with Windows 8, then?

mrgreeny said:
So is your route not possible with Windows 8, then?
Click to expand...
Click to collapse
The main problem is Win8.1, it should work with Win8 (as far as most users said)... if you do get stuck just have an Ubuntu Live USB ready (it's under the FAQs), Ubuntu won't give you a hard time with drivers etc.

nkk71 said:
The main problem is Win8.1, it should work with Win8 (as far as most users said)... if you do get stuck just have an Ubuntu Live USB ready (it's under the FAQs), Ubuntu won't give you a hard time with drivers etc.
Click to expand...
Click to collapse
Ok, thank you!

nkk71 said:
There is no RUU for you, check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)
Click to expand...
Click to collapse
(Sorry for double post)
So I don't have a RUU for Three UK, so I'd go down the CWM route? I believe my thing is x.xx.771 from what I've read.
Then all I need to do is follow those steps in the fourth post for the CWM route, and then I'll be completed unrooted and hopefully back to normal for warranty repairs?

mrgreeny said:
(Sorry for double post)
So I don't have a RUU for Three UK, so I'd go down the CWM route? I believe my thing is x.xx.771 from what I've read.
Then all I need to do is follow those steps in the fourth post for the CWM route, and then I'll be completed unrooted and hopefully back to normal for warranty repairs?
Click to expand...
Click to collapse
Three UK is CID H3G__001 so yes, use the CWM method and you can even use the files mentioned in post #4, since the example I was using is Three UK.
About the S-On part: from what I've seen, the UK seems pretty lenient with all that, but if you do intend on going S-Off to S-On, you do so as mentioned in the guide before any OTA to 3.xx

nkk71 said:
Three UK is CID H3G__001 so yes, use the CWM method and you can even use the files mentioned in post #4, since the example I was using is Three UK.
About the S-On part: from what I've seen, the UK seems pretty lenient with all that, but if you do intend on going S-Off to S-On, you do so as mentioned in the guide before any OTA to 3.xx
Click to expand...
Click to collapse
I assume to make sure it's definitely safe to return for warranty I should go back to S-On, though?
Is there any risk of bricking the device?

mrgreeny said:
Is there any risk of bricking the device?
Click to expand...
Click to collapse
Can I say that 100% -> no, you could have a power outage, your favourite pet, your "favourite" child , mess with your phone / usb / pc connection at exactly the right (wrong) nanosecond when hboot is being flashed. which may or may not result in a brick.
So I scared you a little there
But in general, no, there is no bricking involved as long as you flash things made for your phone. (ie don't go flash HTC Droid stuff on the M7)
at least nobody has complained in my thread causing a brick.
mrgreeny said:
I assume to make sure it's definitely safe to return for warranty I should go back to S-On, though?
Click to expand...
Click to collapse
If you want your phone to look 100% out of the box, I would say yes to the s-on part, though most posts about UK repairs have shown that they don't really care. but no harm in going S-On.
BUT, please follow the guide correctly, if you have questions, feel free to ask.
the guide has worked for many people (and was actually written after having it done in various threads, so it's sort of a result of experience, not only theory),
but if something isnt clear or doesn't make sense, you should ask; I have no issues with people asking why THIS, and why THAT, and why NOW
I prefer a question before, rather than a question after .... (yeah so I skipped step x cause I thought I didn't need it... so now what ... and yeah I didnt bother with reading it once or twice including the FAQs cause you probably wrote them for someone else )

nkk71 said:
Can I say that 100% -> no, you could have a power outage, your favourite pet, your "favourite" child , mess with your phone / usb / pc connection at exactly the right (wrong) nanosecond when hboot is being flashed. which may or may not result in a brick.
No silly childrena round
So I scared you a little there
But in general, no, there is no bricking involved as long as you flash things made for your phone. (ie don't go flash HTC Droid stuff on the M7)
at least nobody has complained in my thread causing a brick.
Click to expand...
Click to collapse
Haha besides those points obviously! Thank you!
nkk71 said:
If you want your phone to look 100% out of the box, I would say yes to the s-on part, though most posts about UK repairs have shown that they don't really care. but no harm in going S-On.
BUT, please follow the guide correctly, if you have questions, feel free to ask.
the guide has worked for many people (and was actually written after having it done in various threads, so it's sort of a result of experience, not only theory),
but if something isnt clear or doesn't make sense, you should ask; I have no issues with people asking why THIS, and why THAT, and why NOW
I prefer a question before, rather than a question after .... (yeah so I skipped step x cause I thought I didn't need it... so now what ... and yeah I didnt bother with reading it once or twice including the FAQs cause you probably wrote them for someone else )
Click to expand...
Click to collapse
Thank you very much. I shall do it later today or on Monday. Hopefully it will all go to plan!

mrgreeny said:
Haha besides those points obviously! Thank you!
Thank you very much. I shall do it later today or on Monday. Hopefully it will all go to plan!
Click to expand...
Click to collapse
sure no problem,
remember: if something doesn't make sense to you, go ahead and ask.... no harm in asking

nkk71 said:
sure no problem,
remember: if something doesn't make sense to you, go ahead and ask.... no harm in asking
Click to expand...
Click to collapse
Can't get S-Off to work. Just posted in http://forum.xda-developers.com/showthread.php?t=2632351&page=45 still waiting on a reply.
You may have an idea?
C:\Users\Michael>adb reboot
C:\Users\Michael>adb wait-for-device push Desktop/firewater /data/local/tmp
3116 KB/s (4432776 bytes in 1.389s)
C:\Users\Michael>adb shell
[email protected]/# su
su
[email protected]/# chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]/# /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.4.6 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
C:\Users\Michael>
Click to expand...
Click to collapse
Any ideas what's happening here? If I leave it too long on the Yes/No it also kicks back to C:\ Have to type Yes really quickly.

mrgreeny said:
Can't get S-Off to work. Just posted in http://forum.xda-developers.com/showthread.php?t=2632351&page=45 still waiting on a reply.
You may have an idea?
Any ideas what's happening here? If I leave it too long on the Yes/No it also kicks back to C:\ Have to type Yes really quickly.
Click to expand...
Click to collapse
Not really, but can you post output of fastboot getvar all and which version of viperone you're using?

nkk71 said:
Not really, but can you post output of fastboot getvar all and which version of viperone you're using?
Click to expand...
Click to collapse
Just done a nandroid backup, and when rebooting it said I needed to fix root?
For firewater to work, should I change from CWM to TWRP and use ARHD do you think?
As for the fastboot getvar all, it's hanging on < waiting for device >
I'm using ViperOne 5.7.0
edit; fastboot getvar all worked earlier today just before I used firewater
edit2; DUH! Forgot to boot to Fastboot haha!!!
C:\Users\Michael>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.771.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3873mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse

mrgreeny said:
Just done a nandroid backup, and when rebooting it said I needed to fix root?
For firewater to work, should I change from CWM to TWRP and use ARHD do you think?
As for the fastboot getvar all, it's hanging on < waiting for device >
I'm using ViperOne 5.7.0
edit; fastboot getvar all worked earlier today just before I used firewater
edit2; DUH! Forgot to boot to Fastboot haha!!!
Click to expand...
Click to collapse
(bootloader) version-main: 2.24.771.3
your best bet would be with a 2.24 ROM, try this one:
Android_Revolution_HD-One_13.4_(4.2.2).zip 1.01 GB
https://mega.co.nz/#!3VVEjKiJ!ekbbghB0fEx-aSRyppzjG3ITeuAT4xEoO9gXBo0vPpI
MD5: D8529CA3F59CDFA4947FD76333B2F5F8
credits to @mike1986.
then use rumrunner of firewater.
Good Luck

nkk71 said:
(bootloader) version-main: 2.24.771.3
your best bet would be with a 2.24 ROM, try this one:
Android_Revolution_HD-One_13.4_(4.2.2).zip 1.01 GB
https://mega.co.nz/#!3VVEjKiJ!ekbbghB0fEx-aSRyppzjG3ITeuAT4xEoO9gXBo0vPpI
MD5: D8529CA3F59CDFA4947FD76333B2F5F8
credits to @mike1986.
then use rumrunner of firewater.
Good Luck
Click to expand...
Click to collapse
Can I flash this ROM with CWM?
Also, on reboot it says "Root access possibly lost. Fix? Yes - Fix Root (/system/xbin/su)
any ideas?

mrgreeny said:
Can I flash this ROM with CWM?
Also, on reboot it says "Root access possibly lost. Fix? Yes - Fix Root (/system/xbin/su)
any ideas?
Click to expand...
Click to collapse
yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.

nkk71 said:
yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.
Click to expand...
Click to collapse
I will keep you up to date.. Thank you very much

nkk71 said:
yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.
Click to expand...
Click to collapse
S-Off done - now I'm downloading all the files for when they're needed.
Which stock recovery (From http://d-h.st/users/Guich/Stock Recovery M7) should I use?
version-main in fastboot getvar all is version-main: 2.24.771.3 so should I download that from the above link?

nkk71 said:
yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.
Click to expand...
Click to collapse
Okay. this is where I'm stuck at
C:\Users\Michael>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.050s]
finished. total time: 0.050s
C:\Users\Michael>fastboot flash zip ruu.zip
< waiting for device >
sending 'zip' (104391 KB)...
OKAY [ 5.840s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 6.033s
C:\Users\Michael>fastboot flash zip ruu.zip
sending 'zip' (104391 KB)...
OKAY [ 5.645s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 5.843s
C:\Users\Michael>fastboot flash zip ruu.zip
sending 'zip' (104391 KB)...
OKAY [ 5.882s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 6.077s
C:\Users\Michael>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.044s]
finished. total time: 0.044s
Click to expand...
Click to collapse

Bootloop/ errors with GPE still on jellybean

Back in the day, my HTC One M7 GPE was one of the ones that became a soft brick with the initial update. So after Google replaced my phone, I turned off updates, and thereby wound up remaining on jellybean (4.2.2).
All was well and good until last week, when my phone wound up on a bootloop. Originally I could stop it from bootlooping by clearing the cache of certain apps like Gmail. But it would go back into a bootloop after some use like checking email or a webpage. I tried to download/ update the system, but my system was saying it didn't have enough memory. I started mass uninstalling things I don't use, in hopes that this wound work, but no luck.
So, I contacted Google who had me go into the bootloader and recovery. That gave me an android lying on his back with the red triangle/ exclamation point. From there he had me clear the cache.
After that, my phone would go into a bootloop no matter what!!
Out of desperation, I saved whatever I could on my computer, and then factory reset.
However, still with the factory reset I am getting bootloops!!
I was able to re-turn on usb debugging, and I have the file (now) to unlock my bootloader.
However, before I go ahead and do so, I am hoping there is a way to re-load on the OEM ROM and replace whatever has gone bad.... and hope the phone can then do its natural updates??
I've downloaded the 2.14.1700.15 files from the HTCdev website, and I tried to flash the zip files, but I get the "12 signature verify fail" error.
I have confirmed that my cid is still GOOGL001 . I thought that as long as it was a matching ROM that it would flash without unlocking the bootloader?
There are also Framework support files on the HTCdev website - I may need to replace/ flash those also??
If anyone has ideas before I go ahead and unlock the bootloader, that would be great!!
And if i do unlock the bootloader, given that I have never performed an update on the system, what version of the software (file) would you recommend that I flash the system with? I have no need for a custom ROM. The GPE ROMs are fine for me.
Thank you so much for your help!!

elisaw99 said:
Back in the day, my HTC One M7 GPE was one of the ones that became a soft brick with the initial update. So after Google replaced my phone, I turned off updates, and thereby wound up remaining on jellybean (4.2.2).
All was well and good until last week, when my phone wound up on a bootloop. Originally I could stop it from bootlooping by clearing the cache of certain apps like Gmail. But it would go back into a bootloop after some use like checking email or a webpage. I tried to download/ update the system, but my system was saying it didn't have enough memory. I started mass uninstalling things I don't use, in hopes that this wound work, but no luck.
So, I contacted Google who had me go into the bootloader and recovery. That gave me an android lying on his back with the red triangle/ exclamation point. From there he had me clear the cache.
After that, my phone would go into a bootloop no matter what!!
Out of desperation, I saved whatever I could on my computer, and then factory reset.
However, still with the factory reset I am getting bootloops!!
I was able to re-turn on usb debugging, and I have the file (now) to unlock my bootloader.
However, before I go ahead and do so, I am hoping there is a way to re-load on the OEM ROM and replace whatever has gone bad.... and hope the phone can then do its natural updates??
I've downloaded the 2.14.1700.15 files from the HTCdev website, and I tried to flash the zip files, but I get the "12 signature verify fail" error.
I have confirmed that my cid is still GOOGL001 . I thought that as long as it was a matching ROM that it would flash without unlocking the bootloader?
There are also Framework support files on the HTCdev website - I may need to replace/ flash those also??
If anyone has ideas before I go ahead and unlock the bootloader, that would be great!!
And if i do unlock the bootloader, given that I have never performed an update on the system, what version of the software (file) would you recommend that I flash the system with? I have no need for a custom ROM. The GPE ROMs are fine for me.
Thank you so much for your help!!
Click to expand...
Click to collapse
Wrong section thread, should be here http://forum.xda-developers.com/htc-one/help

Droid_Core said:
Wrong section thread, should be here http://forum.xda-developers.com/htc-one/help
Click to expand...
Click to collapse
Oooops, sorry.
Now that the thread has been moved - can anyone assist me with this??

elisaw99 said:
Oooops, sorry.
Now that the thread has been moved - can anyone assist me with this??
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (remove your imei/sn)

alray said:
Post the output of "fastboot getvar all" (remove your imei/sn)
Click to expand...
Click to collapse
ok, here it is!
C:\Users\Owner\sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1700.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *removed*
(bootloader) imei: *removed*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.521s

elisaw99 said:
ok, here it is!
C:\Users\Owner\sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1700.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *removed*
(bootloader) imei: *removed*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.521s
Click to expand...
Click to collapse
You could flash the 5.11.1700.3 GPE RUU and update to the latest version from there using ota
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
File and instructions at post 1 of this thread. Don't forget that flashing a RUU will wipe the phone so backup your important files before.

Thanks for the reply!
Do I have to unlock the bootloader to flash this RUU?
Also it looks like on the webpage that it is a Lollipop Sense RUU? Is that right? I was hoping to stay with the GPE ROMs. And i was guessing that I needed to load on the jellybean original first prior to updating to Lollipop.... but maybe that isn't necessary??
Thanks for all of your assistance!!

elisaw99 said:
Thanks for the reply!
Do I have to unlock the bootloader to flash this RUU?
Also it looks like on the webpage that it is a Lollipop Sense RUU? Is that right? I was hoping to stay with the GPE ROMs. And i was guessing that I needed to load on the jellybean original first prior to updating to Lollipop.... but maybe that isn't necessary??
Thanks for all of your assistance!!
Click to expand...
Click to collapse
The bootloader must be locked to flash the ruu since your phone is S-ON.
.1700 is the GPE version not Sense

alray said:
The bootloader must be locked to flash the ruu since your phone is S-ON.
.1700 is the GPE version not Sense
Click to expand...
Click to collapse
Ok, sounds good! And this is Lollipop I presume?
Unfortunately, it looks like the link to download is broken? Says file does not exist. Is there another download link I can use?
Thanks a lot!

elisaw99 said:
Ok, sounds good! And this is Lollipop I presume?
Unfortunately, it looks like the link to download is broken? Says file does not exist. Is there another download link I can use?
Thanks a lot!
Click to expand...
Click to collapse
5.0.1 GPE RUU:
http://www.graffixnyc.com/download.php
4.4 GPE RUU:
http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/

alray said:
5.0.1 GPE RUU:
http://www.graffixnyc.com/download.php
4.4 GPE RUU:
http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
Click to expand...
Click to collapse
Thanks for the new links!
Do I need to flash the 4.4 first? And then will my phone automatically OTA update?
Or do I need to flash the original 4.2.2 first?
Or does none of it matter, and I can flash the latest version right away??

elisaw99 said:
Thanks for the new links!
Do I need to flash the 4.4 first? And then will my phone automatically OTA update?
Or do I need to flash the original 4.2.2 first?
Or does none of it matter, and I can flash the latest version right away??
Click to expand...
Click to collapse
Actually neither of those links are working either.
If someone could let me know the best options, it would be appreciated!

I'm wondering if the files you are sending are the same as that on the HTCdev website:
http://www.htcdev.com/devcenter/downloads ?
By going into the One Google Play Edition, a bunch of ROMs and Frameworks come up. I'm currently on 2.14.1700.15 . I originally tried to flash that UI, but that's when i got the signature errors.
Do I need to flash the Frameworks first? And, if so, what is the line code to do that?
Or is the reason it failed is because I used the android fastboot, instead of HTC fastboot??

elisaw99 said:
Actually neither of those links are working either.
If someone could let me know the best options, it would be appreciated!
Click to expand...
Click to collapse
The link for 4.4 is still good. Flash this one then install ota updates.
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
elisaw99 said:
I'm wondering if the files you are sending are the same as that on the HTCdev website:
http://www.htcdev.com/devcenter/downloads ?
Click to expand...
Click to collapse
No these are kernel source files, not useful for you, flash the ruu and you should be fine.

Ok, unfortunately it did not work.
Can any one detect what I may be doing wrong?
I tried 3 times to get the flash of the file to work, but no luck. The RUU file I tried to flash was "RUU Zip M7_Google Edition_4.4_3.58.1700.5.zip"
C:\Users\Owner\sdk>htc_fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 53(ms)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.749 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 72(s)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.767 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 71(s)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.576 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 72(s)
C:\Users\Owner\sdk>htc_fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 42(ms)

elisaw99 said:
Ok, unfortunately it did not work.
Can any one detect what I may be doing wrong?
I tried 3 times to get the flash of the file to work, but no luck. The RUU file I tried to flash was "RUU Zip M7_Google Edition_4.4_3.58.1700.5.zip"
C:\Users\Owner\sdk>htc_fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 53(ms)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.749 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 72(s)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.767 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 71(s)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.576 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 72(s)
C:\Users\Owner\sdk>htc_fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 42(ms)
Click to expand...
Click to collapse
12 signature verify fail = Your bootloader is unlocked. It must be locked or re-locked (fastboot oem lock) to flash a RUU.

no, my bootloader is locked. i never unlocked it.
i also tried both the htc fastboot, and regular fastboot. both have the signature fail error.

elisaw99 said:
no, my bootloader is locked. i never unlocked it.
i also tried both the htc fastboot, and regular fastboot. both have the signature fail error.
Click to expand...
Click to collapse
Ok then it might be caused by the RUU not being signed with HTC's signature. Unsigned RUU can only be flashed on S-OFF phone. So you'll need either to find a signed RUU or S-OFF your phone and use that one.

Before I unlock my bootloader and attempt to install something else, could someone let me know if they have an RUU.zip that would work with my phone?!? I have tried just about anything that looked like an RUU.zip that I could find for GPE, and all give me the signature fail. I'm getting horribly frustrated and want a phone again!!
PLEASE HELP!!

HTC One M7 - can not update to android 5.

Hello everyone
First of all sorry for my english. I'm not a native english so please forgive me if I say something wrong. Second - this is my first thread here (since now, reading informations from here was enough to handle all of my problems but at this moment well... I surrender and need some advice) so please be understanding.
I have a problem with HTC M7. My friend gave it to me for a little hardware fix and software update. I fixed the hardware but I'm stuck on firmware update.
I wanted to update firmware to 5.05.651.2 with automatic updates but it crashes somewhere in the middle with red triangle sign.
So I started to read. First I've read that I need to unlock bootloader, so I made it with fastboot - nothing changed. Later found some info that I need a stock firmware to enable updates. So I downloaded some firmware but failed to install it (tried with fastboot). Next info I found that to install stock firmware I need to root the device. So I've rooted it. Still nothing. Trying to flash in "rebootRUU" mode with fastboot gave me info that no "android-info.txt" was found. Some more reading and searching and I've noticed that my HTC is probably Sprint version (to be honest I do not know what is the difference). So I downloaded some Sprint firmware. Still no effect... Ehh I'm depressed and I'm begging for help:crying:
So at this moment I have:
Android ver. 4.4.2
HTC Sense ver. 6.0
Software ver. 5.03.651.3
Kernel ver. 3.4.10-gf22c859
(translated from Polish menu)
Info from bootloader:
*** RELOCKED ***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT - 1.44.0000
RADIO-1.00.31.0603
OpenDSP-v31.120.274.0617
eMMC-BOOT
Jul 5 2013, 17:19:22:3
Custom recovery installed from file: openrecovery-twrp-2.5.0.0-m7wls
Root made with iRoot app.
Also I don't know if it was earlier, but now lockscreen on android is in Chinese while all the rest is in Polish :/
Maybe it's important - friend told me that phone is from Shanghai (I don't know where does he have that info from).
If any additional information is needed please write and I will post it asap.
What I would like to achieve? I would like to install latest available stock firmware (without any changes, cool apps or any additional software). Just an basic android with Google store available. My friend is not advanced android user. He just want latest software.
I would probably fight with this device more but also a big problem are dead links all over the forums (htc1guru etc). I'm counting that maybe some of you here have backups of roms. Or maybe I just don't know how to find a proper one.
Full step-by-step manual what should I do would be great but of course I appreciate any other suggestions or advice. Just need some help.
(one more thing - for those who want to write "use search, there are a lot of manuals on the web, we won't make it for you etc" please, I spent couple of hours searching and reading and I don't understand or I don't know how to use info's I found. I'm not an Android user for last couple of years)
Thank you in advance for any help

See comment in red below
qwe1234 said:
Hello everyone
First of all sorry for my english. I'm not a native english so please forgive me if I say something wrong. Second - this is my first thread here (since now, reading informations from here was enough to handle all of my problems but at this moment well... I surrender and need some advice) so please be understanding.
I have a problem with HTC M7. My friend gave it to me for a little hardware fix and software update. I fixed the hardware but I'm stuck on firmware update.
I wanted to update firmware to 5.05.651.2 with automatic updates but it crashes somewhere in the middle with red triangle sign. Indicating that your software partition isn't 100% stock. The ota update will only replace the required files to be updated, not the whole system. Before updating, the updater-script check integrity of all files to be updated. If only one of these file isn't as expected, the updater-script will abort and the update will not install ----> red triangle
So I started to read. First I've read that I need to unlock bootloader bootloader lock/unlock status isn't related to ota update, so I made it with fastboot - nothing changed. Later found some info that I need a stock firmware to enable updates. So I downloaded some firmware but failed to install it (tried with fastboot). Next info I found that to install stock firmware I need to root the device You don't need root to install firmware. So I've rooted it. Still nothing. Trying to flash in "rebootRUU" mode with fastboot gave me info that no "android-info.txt" was found indicating that you are not using the correct file. Some more reading and searching and I've noticed that my HTC is probably Sprint version (to be honest I do not know what is the difference The sprint variant is a CDMA phone). So I downloaded some Sprint firmware. Still no effect... Ehh I'm depressed and I'm begging for help:crying:
So at this moment I have:
Android ver. 4.4.2
HTC Sense ver. 6.0
Software ver. 5.03.651.3
Kernel ver. 3.4.10-gf22c859
(translated from Polish menu)
Info from bootloader:
*** RELOCKED ***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT - 1.44.0000 old bootloader version not matching your software version
RADIO-1.00.31.0603
OpenDSP-v31.120.274.0617
eMMC-BOOT
Jul 5 2013, 17:19:22:3
Custom recovery installed from file: openrecovery-twrp-2.5.0.0-m7wls twrp 2.5.0.0 is really outdated and won't work with recent files. Not a problem for now since you will not need to use twrp to fix it, just fyi
Root made with iRoot app.
Also I don't know if it was earlier, but now lockscreen on android is in Chinese while all the rest is in Polish :/
Maybe it's important - friend told me that phone is from Shanghai (I don't know where does he have that info from).
If any additional information is needed please write and I will post it asap.
What I would like to achieve? I would like to install latest available stock firmware (without any changes, cool apps or any additional software). Just an basic android with Google store available. My friend is not advanced android user. He just want latest software.
I would probably fight with this device more but also a big problem are dead links all over the forums (htc1guru etc). I'm counting that maybe some of you here have backups of roms. Or maybe I just don't know how to find a proper one.
Full step-by-step manual what should I do would be great but of course I appreciate any other suggestions or advice. Just need some help.
(one more thing - for those who want to write "use search, there are a lot of manuals on the web, we won't make it for you etc" please, I spent couple of hours searching and reading and I don't understand or I don't know how to use info's I found. I'm not an Android user for last couple of years)
Thank you in advance for any help
Click to expand...
Click to collapse
download these 3 files and save it in the folder where you already have fastboot.exe and adb.exe on your computer.
https://androidfilehost.com/?fid=24052804347850182
https://androidfilehost.com/?fid=24588232905725176
https://androidfilehost.com/?fid=24341993505161791
First update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot reboot-bootloader
You need to do the "fastboot flash zip" command twice. First time you'll get the "remote: 90 hboot pre-update! Please flush image again immediately" error. Second time the firmware will flash completely and should see a "OK/ flash sucessful" message. You can disregard the progress bar on the phone screen, it might not indicate 100% but if fastboot tell you "OK/ flash sucessful" it's alright
Then you can confirm everything is alright with
Code:
fastboot getvar all
your version-main should now be 6.23.651.10 and your hboot 1.61 instead of 1.44
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Make sure the phone is fully charged before doing all that and if something goes wrong post here and wait (do not skip any steps).
If everything went ok, the phone should reboot to the latest stock android version and the old twrp version replaced with the stock recovery. If the phone was sim-unlocked it might be relocked to Sprint again and you'll have to sim-unlock again (you can find the procedure in the "Sprint htc one" forum section, in the "general" sub-section.

My friend Thank You very much for all the instructions... but...
Last step:
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Click to expand...
Click to collapse
ended with error ;(
fastboot gave following:
processing file 2/5...
error: cannot load 'C:\Users\x101ch\AppData\Local\Temp\tmpp6r0paxd'
htc_fastboot finished. total time: 297.909s
Phone restarted once in the middle like you said.
I rebooted with "fastboot reboot" . Startup screen show up and now there is a black screen with dimmed backlight. Power button doesn't do anything. Any of commands in fasboot also don't work. Ahh...
One more thing. I haven't noticed that you changed command from fastboot to htc_fastboot so I changed htc_fastboot file name to just fastboot and used command fastboot. Don't know if it matters...

qwe1234 said:
I rebooted with "fastboot reboot" . Startup screen show up and now there is a black screen with dimmed backlight. Power button doesn't do anything. Any of commands in fasboot also don't work. Ahh...
Click to expand...
Click to collapse
Now you probably understand why I said
if something goes wrong post here and wait (do not skip any steps).
Click to expand...
Click to collapse
Rebooting after a failed/incomplete flash can hard brick your phone. If you can't get fastboot connectivity again, there is not much you can do. Sorry

Ahhh. My bad;( I didn't want to leave everything turned on for so many hours. Well nevermind.
What do you think if I open up the phone nad reset it manually by unplugging the battery? Is there a chance to boot it to bootloader? Like I mentioned te start screen appeared so it looks like the phone hangs later. Am I thinking right?

qwe1234 said:
Ahhh. My bad;( I didn't want to leave everything turned on for so many hours. Well nevermind.
What do you think if I open up the phone nad reset it manually by unplugging the battery? Is there a chance to boot it to bootloader? Like I mentioned te start screen appeared so it looks like the phone hangs later. Am I thinking right?
Click to expand...
Click to collapse
maybe or let the battery drain then plug the phone again and try to boot in bootloader with vol down and power.

Ok. I will try to do that tomorrow and will post the result. Thanks again

Ufff...
I'm in bootloader again.
Unplugged battery directly on mainboard and connected again rebooted the phone. So... whats next? I promise I won't do anything more without a consult

qwe1234 said:
Ufff...
I'm in bootloader again.
Unplugged battery directly on mainboard and connected again rebooted the phone. So... whats next? I promise I won't do anything more without a consult
Click to expand...
Click to collapse
:good::good:
Can you post an update of your "fastboot getvar all" please (hide your imei and serialno before posting)

alray said:
:good::good:
Can you post an update of your "fastboot getvar all" please (hide your imei and serialno before posting)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 99000146554636
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
htc_fastboot finished. total time: 0.623s

qwe1234 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 99000146554636
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
htc_fastboot finished. total time: 0.623s
Click to expand...
Click to collapse
try to flash the ruu again and post a screenshot of your cmd window if it doesn't work

alray said:
try to flash the ruu again and post a screenshot of your cmd window if it doesn't work
Click to expand...
Click to collapse
Alray... I don't know how to thank you. You're the best
Second flash went with a success at every step. Now everything seems to be absolutely ok. Firmware is updated.
Tomorrow I will check sim-lock and I will try to make a phone call and if everything will be ok I think it's gonna be the end
Thank you very much again

qwe1234 said:
Alray... I don't know how to thank you. You're the best
Second flash went with a success at every step. Now everything seems to be absolutely ok. Firmware is updated.
Tomorrow I will check sim-lock and I will try to make a phone call and if everything will be ok I think it's gonna be the end
Thank you very much again
Click to expand...
Click to collapse
:good:
you're welcome!

So I checked and the phone probably has a sim-lock. It shows notification that the simcard is wrong (translated from polish so in english it may be in some other words). I checked the subforum like you said in first reply and I found threads: [GUIDE] [fixed] SIM UNLOCK after lollipop and [GUIDE] Sprint sim unlock & Flash. I don't want to mess up anything (again) so could you please tell me which one is right for me?

qwe1234 said:
So I checked and the phone probably has a sim-lock. It shows notification that the simcard is wrong (translated from polish so in english it may be in some other words). I checked the subforum like you said in first reply and I found threads: [GUIDE] [fixed] SIM UNLOCK after lollipop and [GUIDE] Sprint sim unlock & Flash. I don't want to mess up anything (again) so could you please tell me which one is right for me?
Click to expand...
Click to collapse
So it looks like I'm stupid.
I tried to unlock the phone. Again bootloader unlocked, phone rooted. I wanted to unlock it with terminal commands using HtcOMADM_SPCS but I cannot install it. I've installed twrp (this time version 3.1.1.0) but it keeps saying that footer is wrong and signature verification failed...
Any more help, please? ;(

Hey sorry, don't mean to hijack this thread.
But would the same instructions apply for updating any older HTC m7 as far as the firmware and RUU is concerned?
I'm getting crickets on my thread, and just needed a general confirmation on the process again since it's been awhile.
I'm looking to flash a more current ROM and newer twrp recovery(or whatever is the best out there now).
Just confirming the process you described would still work the same way.
Thanks!
alray said:
See comment in red below
download these 3 files and save it in the folder where you already have fastboot.exe and adb.exe on your computer.
https://androidfilehost.com/?fid=24052804347850182
https://androidfilehost.com/?fid=24588232905725176
https://androidfilehost.com/?fid=24341993505161791
First update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot reboot-bootloader
You need to do the "fastboot flash zip" command twice. First time you'll get the "remote: 90 hboot pre-update! Please flush image again immediately" error. Second time the firmware will flash completely and should see a "OK/ flash sucessful" message. You can disregard the progress bar on the phone screen, it might not indicate 100% but if fastboot tell you "OK/ flash sucessful" it's alright
Then you can confirm everything is alright with
Code:
fastboot getvar all
your version-main should now be 6.23.651.10 and your hboot 1.61 instead of 1.44
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Make sure the phone is fully charged before doing all that and if something goes wrong post here and wait (do not skip any steps).
If everything went ok, the phone should reboot to the latest stock android version and the old twrp version replaced with the stock recovery. If the phone was sim-unlocked it might be relocked to Sprint again and you'll have to sim-unlock again (you can find the procedure in the "Sprint htc one" forum section, in the "general" sub-section.
Click to expand...
Click to collapse

cloud66 said:
Hey sorry, don't mean to hijack this thread.
But would the same instructions apply for updating any older HTC m7 as far as the firmware and RUU is concerned?
Click to expand...
Click to collapse
Since yours is also a Sprint HTC One, yes the same procedure should work.
I'm getting crickets on my thread
Click to expand...
Click to collapse
quote me next time and I'll be notified, just like you did in this thread.
I'm looking to flash a more current ROM and newer twrp recovery(or whatever is the best out there now).
Click to expand...
Click to collapse
Don't forget that only Sprint roms and Sprint recovery will work on your phone (roms or recovery for the gsm/m7ul won't work). Make sure the custom rom you want to flash is compatible with the Sprint variant (it will be mentioned in the OP of the rom thread if it's compatible with Sprint/M7_WLS). Flash the Sprint TWRP version:
twrp-3.1.1-0-m7wls.img not twrp-3.1.1-0-m7.img

alray said:
quote me next time and I'll be notified, just like you did in this thread.
Click to expand...
Click to collapse
Hey again. Alray can I ask you for a little bit more help? I've tried every way to sim unlock i found but without any success. Last method I used was from this video: https://www.youtube.com/watch?v=e6hHUae1TMs but when I want to run Unlock helper it crashes. Have no idea what am I doing wrong...;(

alray said:
Since yours is also a Sprint HTC One, yes the same procedure should work.
quote me next time and I'll be notified, just like you did in this thread.
Don't forget that only Sprint roms and Sprint recovery will work on your phone (roms or recovery for the gsm/m7ul won't work). Make sure the custom rom you want to flash is compatible with the Sprint variant (it will be mentioned in the OP of the rom thread if it's compatible with Sprint/M7_WLS). Flash the Sprint TWRP version:
twrp-3.1.1-0-m7wls.img not twrp-3.1.1-0-m7.img
Click to expand...
Click to collapse
Hey so looks like I'm running into an issue when updating my firmware.
I'm getting this:
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware and no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues.
Also flashed twrp recovery without any issues.
Rom is still working, everything is still normal....
Thoughts?

Also wanted to add that I was able to update TWRP to 3.1 and flash ICE ROM 7.1.1 and gapps without any issues. So far running semi-stable.
Tried updating firmware with s-on after i re-locked my bootloader, but that did not work either. I was still getting some weird error so I unlocked my bootloader again and then was able to flash the nougat rom just fine. It's strange that it's working with such an older version of the firmware... oh well.
Will still hold out for any suggestions. I'm sure I will run into some issues soon with the firmware being that out-of-date. Signal issues, battery issues, etc.