Hello,
I have been posting in the AT&T HTC One area, but was directed to this area. My previous post is here: http://forum.xda-developers.com/showthread.php?t=2637302
My issue, it seems, is that my firmware and CID do not match, but my device is S-ON and relocked. Unfortunately, I cannot use the HTC method of unlocking my phone, since all I can get into is bootloader/fastboot. Is there any chance of getting this thing back to stock?
Have you tried fastboot oem unlock ?
SaHiLzZ said:
Have you tried fastboot oem unlock ?
Click to expand...
Click to collapse
Yes that simply yields the following message:
Code:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.001s
How did you unlock the first time around? This page says the unlock procedure is different for AT&T devices than the other HTC Ones.
fenstre said:
How did you unlock the first time around? This page says the unlock procedure is different for AT&T devices than the other HTC Ones.
Click to expand...
Click to collapse
When I originally unlocked it, I used the HTC official method, and it worked fine.
@codejunkie83 - In the original thread you mention converting to GPE which would be 3.62.1700.1, but your current firmware is 4.06.1540.2 dev edition. How did you get onto this firmware?
There is no 4.06.1540.2 RUU, but there is a 3.22.1540.1 to 4.06.1540.2 OTA that has signed firmware you should be able to flash in RUU mode with S-ON and locked bootloader. This might get things straightened out so that you'll be able to unlock bootloader. CID CWS__001 will work with this firmware.
Is it correct there is no OS loaded in /system ?
@cschmitt - I initially tried loading one of the guru reset roms, but I did not have touch screen capabilities. So, I found the 4.06.1540.2 firmware and flashed that - I think in error a site had that listed as AT&T, or I may have just misread. At any rate, I did not load an OS before turning S-ON and relocking - something I will definitely never forget to do again.
Do you have a link for that firmware? I will definitely give it a shot once I get home from work today.
The OTA is linked in this post. Open the OTA zip, and firmware.zip is there.
I'm not sure it will help, but won't hurt anything to try.
You might be stuck waiting for the AT&T KK update, they usually link an RUU on the HTC support site and if the version > 4.06 it should work.
Might also try contacting HTC and see if they can get you a 4.06.1540.2 RUU. There is an RUU, because they use it during repairs to refurbish devices, it's just not publicly released.
cschmitt said:
The OTA is linked in this post. Open the OTA zip, and firmware.zip is there.
I'm not sure it will help, but won't hurt anything to try.
You might be stuck waiting for the AT&T KK update, they usually link an RUU on the HTC support site and if the version > 4.06 it should work.
Might also try contacting HTC and see if they can get you a 4.06.1540.2 RUU. There is an RUU, because they use it during repairs to refurbish devices, it's just not publicly released.
Click to expand...
Click to collapse
Okay, thanks for the link. I'll give it a shot this afternoon, and if that doesn't work I'll just wait on the AT&T KK release - I believe that it is supposed to be out sometime soon. In the meanwhile I may attempt to contact HTC for that RUU. Thank you for your assistance - I'll report back my findings.
Okay, the firmware flashed correctly, but unfortunately I'm still in the same boat. I have sent an email to HTC, but I am not holding out much hope for that. I'll just keep waiting for a 4.06 RUU to magically appear.
So, a quick update on this (in case it helps anyone else in the same boat). I've spent the past few weeks going back and forth with HTC, who have been very responsive and helpful. Unfortunately, we came to the conclusion that I would need to send my phone in for repair. However, this was before the AT&T update was released.
So, along with this update, does anyone think flashing the AT&T firmware for 4.18 would help my situation, since I am currently on 4.06.1540.2? I think that it would flash ok, but not sure if I would be able to proceed at all after that, since I have no android installed.
codejunkie83 said:
So, a quick update on this (in case it helps anyone else in the same boat). I've spent the past few weeks going back and forth with HTC, who have been very responsive and helpful. Unfortunately, we came to the conclusion that I would need to send my phone in for repair. However, this was before the AT&T update was released.
So, along with this update, does anyone think flashing the AT&T firmware for 4.18 would help my situation, since I am currently on 4.06.1540.2? I think that it would flash ok, but not sure if I would be able to proceed at all after that, since I have no android installed.
Click to expand...
Click to collapse
Looks like someone tried it already. http://forum.xda-developers.com/showpost.php?p=50598383&postcount=71
Did not work for this user, unfortunately, you are welcome to try. You would need to download the ATT OTA for 4.4.2, extract firmware.zip and then run the following commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip (second time)
fastboot reboot-bootloader
and then unlock using HTC Dev..
Okay I will give it a shot when I get home, see what kind of results I get. Thanks!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Do post back your results!
---------- Post added at 04:44 PM ---------- Previous post was at 04:44 PM ----------
codejunkie83 said:
Okay I will give it a shot when I get home, see what kind of results I get. Thanks!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Do post back your results!
SaHiLzZ said:
Do post back your results!
---------- Post added at 04:44 PM ---------- Previous post was at 04:44 PM ----------
Do post back your results!
Click to expand...
Click to collapse
Alright, so quick update - I think I'm making progress! I downloaded the OTA file from this thread http://forum.xda-developers.com/showthread.php?t=2659374 and extracted the firmware.zip from it. I flashed that, and am finally back on an AT&T base version (4.18.502.7). So, from here, I am going to attempt to unlock again and get a custom recovery on it. Will update as I progress - if anything else comes to mind, let me know!
Also., for giggles/information, here is my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
EDIT 2:
Okay, well, seems I'm still in the same boat - just on AT&T's version instead of dev edition. I'm still in contact with HTC, so hopefully I can get something worked out with them.
So htc Dev unlock didn't work?
Like @SaHiLzZ says, use the htcdev, there is a tuturial http://forum.xda-developers.com/showthread.php?t=1432199
spider84a said:
Like @SaHiLzZ says, use the htcdev, there is a tuturial http://forum.xda-developers.com/showthread.php?t=1432199
Click to expand...
Click to collapse
Unfortunately, it does not work. I get a successful message, but nothing happens on the phone. The next command I run on the phone (no matter what it is) gives an error message that custom splash could not be shown.
codejunkie83 said:
Unfortunately, it does not work. I get a successful message, but nothing happens on the phone. The next command I run on the phone (no matter what it is) gives an error message that custom splash could not be shown.
Click to expand...
Click to collapse
If you flashed the GPE Conversion RUU you will never be able to unlock via HTC Dev because that RUU writes sp1.img to mmcblk0p13 where the custom splash screen is stored and it's not the correct one for non-GPE devices such as AT&T, TMO, or the Developer Edition.
For these devices that have been converted to GPE they will always show something like:
Code:
[DISPLAY_ERR] sp_custom partition: sp_custom_img_hd read error!
when attempting to unlock the bootloader by flashing the unlock token.
Unfortunately, even flashing the correct firmware.zip for the device (such as the 4.18.502.7 firmware from the OTA) won't fix it because firmware zips generally do not include the splash screen files sp1.img or splash1.nb0; these are only included in a full RUU.
Only hope is to wait for a 4.18.502.7 signed RUU from HTC.
cschmitt said:
If you flashed the GPE Conversion RUU you will never be able to unlock via HTC Dev because that RUU writes sp1.img to mmcblk0p13 where the custom splash screen is stored and it's not the correct one for non-GPE devices such as AT&T, TMO, or the Developer Edition.
For these devices that have been converted to GPE they will always show something like:
Code:
[DISPLAY_ERR] sp_custom partition: sp_custom_img_hd read error!
when attempting to unlock the bootloader by flashing the unlock token.
Unfortunately, even flashing the correct firmware.zip for the device (such as the 4.18.502.7 firmware from the OTA) won't fix it because firmware zips generally do not include the splash screen files sp1.img or splash1.nb0; these are only included in a full RUU.
Only hope is to wait for a 4.18.502.7 signed RUU from HTC.
Click to expand...
Click to collapse
This totally makes sense, and answers a few of the questions I had in the back of my mind. I knew there had to be one little thing I was missing.
Funny that HTC never mentioned this, but then again...tech support, so yeah.
I'll just hang on for the RUU - thanks @cschmitt !
Related
I followed all the directions on relocking and unrooting my One back to factory settings and when I made it to the last step it keeps failing on me.
sending 'zip' (243622 KB)...
OKAY [ 9.533s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 33.051s
That's what it keeps saying to me. What should I do???
Kenmaster828 said:
I followed all the directions on relocking and unrooting my One back to factory settings and when I made it to the last step it keeps failing on me.
sending 'zip' (243622 KB)...
OKAY [ 9.533s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 33.051s
That's what it keeps saying to me. What should I do???
Click to expand...
Click to collapse
Why are you using a zip? Can't you use the exe RUU? Obviously has to be for your CID and MID. Check on androidruu.com if you can find one.
nkk71 said:
Why are you using a zip? Can't you use the exe RUU? Obviously has to be for your CID and MID. Check on androidruu.com if you can find one.
Click to expand...
Click to collapse
There was no .exe for my version.
I'm on the Sprint 1.31.651.2 version
Kenmaster828 said:
There was no .exe for my version.
I'm on the Sprint 1.31.651.2 version
Click to expand...
Click to collapse
to flash a RUU.zip you need to be in RUUmode (command: fastboot oem rebootRUU) and you'll need S-OFF.
herwegan said:
to flash a RUU.zip you need to be in RUUmode (command: fastboot oem rebootRUU) and you'll need S-OFF.
Click to expand...
Click to collapse
So I basically screwed myself when I reverted back to S-ON.
Kenmaster828 said:
So I basically screwed myself when I reverted back to S-ON.
Click to expand...
Click to collapse
Are you still on hboot 1.44? Then get S-Off again.
nkk71 said:
Are you still on hboot 1.44? Then get S-Off again.
Click to expand...
Click to collapse
I just got back on S-OFF. I am a happy camper
Kenmaster828 said:
I just got back on S-OFF. I am a happy camper
Click to expand...
Click to collapse
:laugh::good:
IMHO, keep S-Off no matter what, even if you have to return it for warranty (hopefully not) or even sell it. some phones are actually shipped with S-Off and (from what I've read) it's very difficult to say that you "tampered" with your phone because you have s-off. several people (on the posts) have returned their phones to service center for repair, and got them back s-off again. no complaints, unless it said RELOCKED, UNLOCKED, or TAMPERED in the bootloader. S-Off is OK.
now you can go ahead and get it back to stock.
nkk71 said:
:laugh::good:
IMHO, keep S-Off no matter what, even if you have to return it for warranty (hopefully not) or even sell it. some phones are actually shipped with S-Off and (from what I've read) it's very difficult to say that you "tampered" with your phone because you have s-off. several people (on the posts) have returned their phones to service center for repair, and got them back s-off again. no complaints, unless it said RELOCKED, UNLOCKED, or TAMPERED in the bootloader. S-Off is OK.
now you can go ahead and get it back to stock.
Click to expand...
Click to collapse
Last time I tried using Sprint 1.31.651.2, now that I am on S-OFF, can I use 1.29.651 version since that is a .exe version instead of a .zip version? I'm also asking this so I can strictly follow QBKING77's tutorial on going back to stock.
Kenmaster828 said:
Last time I tried using Sprint 1.31.651.2, now that I am on S-OFF, can I use 1.29.651 version since that is a .exe version instead of a .zip version? I'm also asking this so I can strictly follow QBKING77's tutorial on going back to stock.
Click to expand...
Click to collapse
Don't know "QBKING77's tutorial", but you can use pretty much any RUU now that you're S-Off. Downgrading is possible thanks to S-Off. Just stick to SPRINT RUUs, ROMs etc, as I understand they (and possibly Verizon) are different from other carriers.
And remember to keep S-Off, that will always allow you to downgrade if needed or flash firmware, etc.
How do you get S-Off after custom ROM
So I'm also getting the "12 signature verify fail" the OP was getting... I don't have (never have had) S-Off. I htcdev unlocked and rooted by AT&T HTC One and put the GPe ROM on it... now I'm trying to go back to stock. Can't run the RUU w/o S-Off apparently, but also apparently can't get S-Off with this ROM? Halp! How do I get out of this situation?
---------- Post added at 09:51 PM ---------- Previous post was at 09:10 PM ----------
I figured it'd be good to provide more info..
C:\and\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34NW******
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4279mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 5.554s
I have tried the 502.12 and 502.15 "cingular" RUU (ZiIPs and EXEs), to no avail.
Can't revone (get "error code = 1" [not -1]), so I can't seem to get S-Off. Moonshine fails in test 2.1 (between reboots basically).
Any ideas?
Have you tried to install viper or ARHD and get S-off again?
michaeljthom said:
So I'm also getting the "12 signature verify fail" the OP was getting... I don't have (never have had) S-Off. I htcdev unlocked and rooted by AT&T HTC One and put the GPe ROM on it... now I'm trying to go back to stock. Can't run the RUU w/o S-Off apparently, but also apparently can't get S-Off with this ROM? Halp! How do I get out of this situation?
---------- Post added at 09:51 PM ---------- Previous post was at 09:10 PM ----------
I figured it'd be good to provide more info..
C:\and\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
Any ideas?
Click to expand...
Click to collapse
Check the date in bootloader; if it's before June 2013, then revone should work. If the date is June or after then it's a patched hboot 1.44, and you need to downgrade before running revone, check this thread it has the downgrade instruction (T-Mob and ATT only): http://forum.xda-developers.com/showthread.php?t=2431515
and remember you need to be on a Sense 5, 4.1.2 based ROM.
nkk71 said:
and remember you need to be on a Sense 5, 4.1.2 based ROM.
Click to expand...
Click to collapse
So this is part of what I'm struggling with... It seems I can't get S-Off without being on a Sense 5/4.1.2 ROM, but how can I get that ROM loaded without S-Off? All the "stock" images I've found seem to all be RUUs or otherwise not work with S-On. What am I missing here?
michaeljthom said:
So this is part of what I'm struggling with... It seems I can't get S-Off without being on a Sense 5/4.1.2 ROM, but how can I get that ROM loaded without S-Off? All the "stock" images I've found seem to all be RUUs or otherwise not work with S-On. What am I missing here?
Click to expand...
Click to collapse
1- first thing, did you check the bootloader date? if it's the patched 1.44 (ie June 2013 or after) then if you do the downgrade (only for ATT and T-Mobile), I think that also includes the ROM.
2- and just to get a Sense 5/4.1.2 based ROM on your phone, you just flash it through custom recovery (any custom or stock ROM will do), if you can't find one I'll PM you a link to one that worked for me, but first check point 1
Thanks nkk71... So yeah, hboot, while v. 1.44, is dated Jul 5, 2013. So it looks like I need to downgrade that. But as you note, that link says I have to be on a stock Sense 5 ROM. I have found a TMO Germany rom, but I haven't yet found an AT&T one.
michaeljthom said:
Thanks nkk71... So yeah, hboot, while v. 1.44, is dated Jul 5, 2013. So it looks like I need to downgrade that. But as you note, that link says I have to be on a stock Sense 5 ROM. I have found a TMO Germany rom, but I haven't yet found an AT&T one.
Click to expand...
Click to collapse
I just took a quick look at the ATT downgrade guide and the first thing it asks (actually point 3) is to install a nandroid backup, that will put the correct Sense 5 ROM on your phone, no need to go look for one.
Hit the thanks button if I've helped
Score. Thanks so much. I think finding a nandroid backup (and then switching to cwm from twrp) was really the key here. But I'm now all fully restored to stock. Thanks again!!
Can someone link me to a thread or video on how to go to S-off, I don't have any rom installed and I can't go back in to recovery.
Hope I'm not screwed
LMH1998 said:
Can someone link me to a thread or video on how to go to S-off, I don't have any rom installed and I can't go back in to recovery.
Hope I'm not screwed
Click to expand...
Click to collapse
same problem . Please help!
Hello everyone,
I'm trying to return my HTC ONE Hboot 1.57 to Stock using an RUU, but its not working. It shows error 155 after a while.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4331mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Version-Main and BaseBand are empty for some reason...
I need your help please.
ahmadghizzawi said:
Hello everyone,
I'm trying to return my HTC ONE Hboot 1.57 to Stock using an RUU, but its not working. It shows error 155 after a while.
I need your help please.
Click to expand...
Click to collapse
Error 155 means your using the wrong RUU, post your fastboot getvar all please, remove your IMEI and serial number before posting.
Seanie280672 said:
Error 155 means your using the wrong RUU, post your fastboot getvar all please, remove your IMEI and serial number before posting.
Click to expand...
Click to collapse
Post Updated
Well, the Version is not showing for some reason.
ahmadghizzawi said:
Post Updated
Well, the Version is not showing for some reason.
Click to expand...
Click to collapse
ok, you have an M7U, you must pretty much have the latest version main otherwise known as firmware as your on HBOOT 1.57, it will also be the 401 firmware based on your cid, so my next question is, are you returning to stock for warranty purposes or you just want it working as im not so sure there is an RUU available for your device, however its my understanding, you can flash M7UL rom's, just the LTE parts will be skipped.
Seanie280672 said:
ok, you have an M7U, you must pretty much have the latest version main otherwise known as firmware as your on HBOOT 1.57, it will also be the 401 firmware based on your cid, so my next question is, are you returning to stock for warranty purposes or you just want it working as im not so sure there is an RUU available for your device, however its my understanding, you can flash M7UL rom's, just the LTE parts will be skipped.
Click to expand...
Click to collapse
Nah not for warranty. I just want it working, because right now it's bricked and I dont know what to do. I appreciate your help.
ahmadghizzawi said:
Nah not for warranty. I just want it working, because right now it's bricked and I dont know what to do. I appreciate your help.
Click to expand...
Click to collapse
just follow this, save me typing it all again: http://forum.xda-developers.com/showpost.php?p=58542916&postcount=6
Any problems, just report back. :good:
Seanie280672 said:
just follow this, save me typing it all again: http://forum.xda-developers.com/showpost.php?p=58542916&postcount=6
Any problems, just report back. :good:
Click to expand...
Click to collapse
Thanks man, I'll give a try. Will this method enable me to download OTA updates from HTC later on?
ahmadghizzawi said:
Thanks man, I'll give a try. Will this method enable me to download OTA updates from HTC later on?
Click to expand...
Click to collapse
probably not as its initially built for the M7_UL, you'll be stuck with custom rom's now unless you can find an RUU and get s-off to enable back flashing, you have to be full stock, nothing custom or modified to get HTC updates, to be honest, most Dev's on here release the rom's before HTC do, take Lollipop as an example, ive been using custom rom's since day 1 of getting my device, most of them blow the stock rom out of the water.
---------- Post added at 09:12 AM ---------- Previous post was at 09:07 AM ----------
ahmadghizzawi said:
Thanks man, I'll give a try. Will this method enable me to download OTA updates from HTC later on?
I tried flashing the custom rom here's what I got:
sending 'recovery' (9184 KB)...
OKAY [ 1.172s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.907s
Click to expand...
Click to collapse
is your bootloader unlocked ?
Seanie280672 said:
probably not as its initially built for the M7_UL, you'll be stuck with custom rom's now unless you can find an RUU and get s-off to enable back flashing, you have to be full stock, nothing custom or modified to get HTC updates, to be honest, most Dev's on here release the rom's before HTC do, take Lollipop as an example, ive been using custom rom's since day 1 of getting my device, most of them blow the stock rom out of the water.
---------- Post added at 09:12 AM ---------- Previous post was at 09:07 AM ----------
is your bootloader unlocked ?
Click to expand...
Click to collapse
It wasn't xD
Forgot to unlock it. I'm downloading the stock rom right now. I'll let you know if anything happens.
Seanie280672 said:
probably not as its initially built for the M7_UL, you'll be stuck with custom rom's now unless you can find an RUU and get s-off to enable back flashing, you have to be full stock, nothing custom or modified to get HTC updates, to be honest, most Dev's on here release the rom's before HTC do, take Lollipop as an example, ive been using custom rom's since day 1 of getting my device, most of them blow the stock rom out of the water.
---------- Post added at 09:12 AM ---------- Previous post was at 09:07 AM ----------
is your bootloader unlocked ?
Click to expand...
Click to collapse
I've installed the rom., picked full wipe, and waited 20 minutes for it to boot for the first time. However, it is restarting each time I try to unlock the screen for some reason. Please help.
ahmadghizzawi said:
I've installed the rom., picked full wipe, and waited 20 minutes for it to boot for the first time. However, it is restarting each time I try to unlock the screen for some reason. Please help.
Click to expand...
Click to collapse
strange that it didn't work, as you'll see here, M7_UL roms are fully compatible with the M7 U http://forum.xda-developers.com/showthread.php?t=2223236
Maybe the Rom just doesn't like your device, it happens, i'll see if I can find another for you.
Give this one a try https://www.androidfilehost.com/?fid=95916177934516346
Seanie280672 said:
strange that it didn't work, as you'll see here, M7_UL roms are fully compatible with the M7 U http://forum.xda-developers.com/showthread.php?t=2223236
Maybe the Rom just doesn't like your device, it happens, i'll see if I can find another for you.
Give this one a try https://www.androidfilehost.com/?fid=95916177934516346
Click to expand...
Click to collapse
Okay man, I'll give it a try. Thanks.
Seanie280672 said:
strange that it didn't work, as you'll see here, M7_UL roms are fully compatible with the M7 U http://forum.xda-developers.com/showthread.php?t=2223236
Maybe the Rom just doesn't like your device, it happens, i'll see if I can find another for you.
Give this one a try https://www.androidfilehost.com/?fid=95916177934516346
Click to expand...
Click to collapse
Same thing happened with this rom. What the hell is wrong
Baseband is showing N/A does it have anything to do with it?
ahmadghizzawi said:
Same thing happened with this rom. What the hell is wrong
Baseband is showing N/A does it have anything to do with it?
Click to expand...
Click to collapse
Don't know how I missed that one , yes I very much expect that's whats wrong, however, how did that happen ?
should be able to fix it by flashing the firmware for your device, however that leads to another problem, no baseband, no version main = which firmware.
All I can suggest at this point is try all of the 6.09.401.x firmware from the link below, start with the earliest one (6.09.401.5) if it fails try the next one up, when one of those install, stop there, the 6 series firmware's came with HBOOT 1,57, if they are older than your current firmware they will fail, if its the same as your current firmware it will install, don't forget each firmware must be flashed twice, first time will say please flush again immediately (flush is HTC Typo, they meant flash), also your bootloader must be locked or re-locked to flash firmware whilst s-on.
on another note, you will need to open each firmware that you download and edit the anroid info txt file, change the model id number in that file to the same number as your phone, then save and flash.
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Before proceeding with this just let me get it confirmed by some of the guys on here, yep im calling you @clsA @Danny201281 @nkk71 :good::good::good:
Seanie280672 said:
Don't know how I missed that one , yes I very much expect that's whats wrong, however, how did that happen ?
should be able to fix it by flashing the firmware for your device, however that leads to another problem, no baseband, no version main = which firmware.
All I can suggest at this point is try all of the 6.09.401.x firmware from the link below, start with the earliest one (6.09.401.5) if it fails try the next one up, when one of those install, stop there, the 6 series firmware's came with HBOOT 1,57, if they are older than your current firmware they will fail, if its the same as your current firmware it will install, don't forget each firmware must be flashed twice, first time will say please flush again immediately (flush is HTC Typo, they meant flash), also your bootloader must be locked or re-locked to flash firmware whilst s-on.
on another note, you will need to open each firmware that you download and edit the anroid info txt file, change the model id number in that file to the same number as your phone, then save and flash.
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Before proceeding with this just let me get it confirmed by some of the guys on here, yep im calling you @clsA @Danny201281 @nkk71 :good::good::good:
Click to expand...
Click to collapse
He is s-on so won't be able to flash a modified firmware so changing the model I'd in android info.txt is not an option.
As he's on hboot 1.57 he must be on a 5.xx or a 6.xx firmware so flashing strait to the latest won't be an issue. I posted a link to the firmware 6.09.401.111 for another user just a day or 2 ago. That is what he needs just a sec I'll be back with a link
---------- Post added at 09:23 PM ---------- Previous post was at 09:20 PM ----------
@ahmadghizzawi @Seanie280672
Everything you need is here http://forum.xda-developers.com/htc-one/development/backup-100-stock-6-09-401-111-twrp-t2992871 :good:
Danny201281 said:
He is s-on so won't be able to flash a modified firmware so changing the model I'd in android info.txt is not an option.
As he's on hboot 1.57 he must be on a 5.xx or a 6.xx firmware so flashing strait to the latest won't be an issue. I posted a link to the firmware 6.09.401.111 for another user just a day or 2 ago. That is what he needs just a sec I'll be back with a link
---------- Post added at 09:23 PM ---------- Previous post was at 09:20 PM ----------
@ahmadghizzawi @Seanie280672
Everything you need I'd here http://forum.xda-developers.com/htc-one/development/backup-100-stock-6-09-401-111-twrp-t2992871 :good:
Click to expand...
Click to collapse
Your a star :good:
Seanie280672 said:
Your a star :good:
Click to expand...
Click to collapse
:good: no problem, your welcome
@Seanie280672 @Danny201281 Thank you so much guys. I really appreciate your help. I'll give it a try and tell you what happens. Thank you again
Danny201281 said:
He is s-on so won't be able to flash a modified firmware so changing the model I'd in android info.txt is not an option.
As he's on hboot 1.57 he must be on a 5.xx or a 6.xx firmware so flashing strait to the latest won't be an issue. I posted a link to the firmware 6.09.401.111 for another user just a day or 2 ago. That is what he needs just a sec I'll be back with a link
---------- Post added at 09:23 PM ---------- Previous post was at 09:20 PM ----------
@ahmadghizzawi @Seanie280672
Everything you need is here http://forum.xda-developers.com/htc-one/development/backup-100-stock-6-09-401-111-twrp-t2992871 :good:
Click to expand...
Click to collapse
@Seanie280672 @Danny201281 When trying to flash the radio, this is what I am getting
sending 'radio' (76800 KB)...
OKAY [ 4.823s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.003s
ahmadghizzawi said:
@Seanie280672 @Danny201281 When trying to flash the radio, this is what I am getting
sending 'radio' (76800 KB)...
OKAY [ 4.823s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.003s
Click to expand...
Click to collapse
Try flashing the firmware, it will contain the radio, that's your best bet, again make sure the bootloader is locked or relocked then issue these commands:
fastboot oem rebootRUU (screen will go black with silver HTC logo)
fastboot flash zip "name of firmware".zip
fastboot flash zip "name of firmware".zip - yup twice
at this point make sure it says successful at the end, if so:
fastboot reboot-bootloader
Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...
scirto said:
Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...
Click to expand...
Click to collapse
Ignore my last paragraph. I completely misread what that file was providing (stock recovery, duh, of course that's what it's providing. Not what I need).
Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
scirto said:
Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
EDIT: I will also note that my last attempt with an RUU was with my phone starting on the home screen. Not sure if starting in bootloader/fastboot is better or worse or makes no difference? I'll try that too
scirto said:
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
Click to expand...
Click to collapse
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk
deleted
Danny201281 said:
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!
scirto said:
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!
Click to expand...
Click to collapse
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Exactly... Might be the software developer in me, but I feel a huge sense of relief as long as I start to see something different happening. OTA is downloading, no root is detected, so the process should complete successfully. Major kudos to you, my friend.
So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!
scirto said:
So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!
Click to expand...
Click to collapse
Your Welcome. Enjoy
Sent from my SM-T230 using Tapatalk
So ive been helping out as much as i can in the Q&A threads,but alot of the resources that are usually needed are scattered around in links,so ive decided to post the latest RUUs per carrier i could find.
For some unapparent reason,the ROM downloads page on the htc website is still outdated with LP RUU links,whereas most of the usual carriers have MM available.
Sprint MM:
http://www.htc.com/us/support/htc-desire-626s-sprint/news/
Boost Mobile MM:
http://www.htc.com/us/support/htc-desire-626s-boost/news/
MetroPCS MM:
http://www.htc.com/us/support/htc-desire-626s-metro-pcs/news/
T-Mobile US MM:
http://www.htc.com/us/support/htc-desire-626s-t-mobile/news/
Virgin Mobile MM:
http://www.htc.com/us/support/htc-desire-626s-virgin-mobile/news/
At the bottom of each respective page,theres a download link for the full RUU thats specific to your device.
If anyone has any other RUUs/Carriers theyd like added please let me know.
Keep in mind,in order to run these RUUs,your Bootloader MUST be locked/Relocked via fastboot.
After the RUU,you can reunlock your bootloader using the htcdev process again.if you saved your unlocktoken great,if not just request another.
The command to relock your bootloader is "fastboot oem lock" without quotes.
awesome thank you so much, very clear, re-locked BL and RUU
Hi @GotHeart,
Can you please upload Verizon 626 RUU. Thank you.
minhajlk said:
Hi @GotHeart,
Can you please upload Verizon 626 RUU. Thank you.
Click to expand...
Click to collapse
Here is the HTC ruu download link: http://www.htc.com/us/support/rom-downloads.html
But it says that RUUs aren't available for Verizon, try using HTC sync manager.
IsaacGuti said:
Here is the HTC ruu download link: http://www.htc.com/us/support/rom-downloads.html
But it says that RUUs aren't available for Verizon, try using HTC sync manager.
Click to expand...
Click to collapse
Hi,
Thanks for your reply, Verizon is not listed in HTC link, my phone is softbricked, since its s-off I can easily recover with a RUU. I am not sure if it is possible to recover with syncmanager since the phone is in softbricked state.
minhajlk said:
Hi,
Thanks for your reply, Verizon is not listed in HTC link, my phone is softbricked, since its s-off I can easily recover with a RUU. I am not sure if it is possible to recover with syncmanager since the phone is in softbricked state.
Click to expand...
Click to collapse
I looked as well,and could not find an RUU for the verizon model.try using htc sync manager while in download/bootloader mode maybe?
i have updated my htc desire 626 virgin mobile to marshmellow 6.0.1 now i cant root it can i downgrade back to 5.1.1
Thank you GotHeart for opening this topic!
I've looked and looked but I can not find a RUU.exe for this model... ( one SIM card ), It came from uk! Any suggestion?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CC5CKYM04174
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a32_ul
(bootloader) platform: hTCBmsm8916
(bootloader) modelid: 0PKX20000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 1001
Im not entirely sure to be honest,i did some searching and came up empty as well.what carrier are/were you using?
GotHeart said:
Im not entirely sure to be honest,i did some searching and came up empty as well.what carrier are/were you using?
Click to expand...
Click to collapse
This phone is unlocked to the network.
I think that I have to wait, otherwise I will not be able to recover the operating system ...
b8engl said:
This phone is unlocked to the network.
I think that I have to wait, otherwise I will not be able to recover the operating system ...
Click to expand...
Click to collapse
If theres no RUU available for your carrier,youre better off not messing with anything.if the changes you make end you in a bootloop or something,they may not be fixable dependent upon when an RUU is available.
GotHeart said:
If theres no RUU available for your carrier,youre better off not messing with anything.if the changes you make end you in a bootloop or something,they may not be fixable dependent upon when an RUU is available.
Click to expand...
Click to collapse
That's the problem! I broke the phone when I flash a "supposed" TWRP.img for the HTC Desire 626. Now I just have access to bootloader and the original recovery.
b8engl said:
That's the problem! I broke the phone when I flash a "supposed" TWRP.img for the HTC Desire 626. Now I just have access to bootloader and the original recovery.
Click to expand...
Click to collapse
You do have the original recovery? Try flashing it under fastboot.what format is it in?and does the TWRP you flashed work?
GotHeart said:
You do have the original recovery? Try flashing it under fastboot.what format is it in?and does the TWRP you flashed work?
Click to expand...
Click to collapse
It was hard to find the original recovery... and yes, I flash thru fastboot mode.
When i flash the TWRP.img, after reboot to recovery i get a black screen. I think this is the 32-bit version.
My options are: Flash a custom recover and then a custom ROM. Or execute a RUU.exe that match my phone.
What do you think GotHeart?
b8engl said:
It was hard to find the original recovery... and yes, I flash thru fastboot mode.
When i flash the TWRP.img, after reboot to recovery i get a black screen. I think this is the 32-bit version.
My options are: Flash a custom recover and then a custom ROM. Or execute a RUU.exe that match my phone.
What do you think GotHeart?
Click to expand...
Click to collapse
Dont flash the TWRP in fastboot,flash the original recovery. "fastboot flash recovery YOURFILENAME.img" where yourfilename is the name of the original recovery.if the file is just named recovery, add the .img at the end.
GotHeart said:
Dont flash the TWRP in fastboot,flash the original recovery. "fastboot flash recovery YOURFILENAME.img" where yourfilename is the name of the original recovery.if the file is just named recovery, add the .img at the end.
Click to expand...
Click to collapse
I already flash the original recovery.img GotHeart, but the phone doesn't go past htc logo. I think the term for this is "soft-brick"
b8engl said:
I already flash the original recovery.img GotHeart, but the phone doesn't go past htc logo. I think the term for this is "soft-brick"
Click to expand...
Click to collapse
Sorry,i should have been more specific,what is the original carrier?i know you said its unlocked,but who originally sold the phone?
GotHeart said:
Sorry,i should have been more specific,what is the original carrier?i know you said its unlocked,but who originally sold the phone?
Click to expand...
Click to collapse
Don't worry! I have fault here, because i didn't explain myself.
Well... I bought this phone on ebay, is a unlocked version. The information that i have is:
Box:
HTC Desire 626 (OPKX200-BL)
Octa-Core 1.7 Cortex-A53, 1GB Ram, 16 HDD
Phone:
(bootloader) product: a32_ul
modelid: 0PKX20000
But... when the phone was ok I installed cpuz.apk and saw the qualcomm chip, and it was a quad-core. To be more i upgrade to marshmallow version using OTA update provided by the phone.
In gsmarena dot com i try to distinguish my phone but i cant.
I bought the unlocked 626 direct from HTC unfortunately I never unlocked the bootloader and recently it got stuck in a boot loop after an OTA update. I believe the firmware is the same as the ATT version however since its using a different cid (BS_US001) I am unable to load the firmware. Any chance anyone has the RRU for this?
Nice
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.