Related
Hi everybody from XDA, first time posting here !
Let me explain the problem I have :
Two days ago, my HTC One was booting on Android 4.3, I was on a ROM Stock from ORANGE, with root access, recovery by TWRP on...
And then it started to crash when booting, didn't knew why ! So I tried to flash another ROM on my device (Android_Revolution_HD-One_53.0) Android 4.4.2 with Sense 6.0, but I locked the bootloader before booting on the ROM. I have now a scary message on my bootloader :
*** RELOCKED ***
**** Security Warning !*****
Click to expand...
Click to collapse
I tried to unlock my bootloader via htcdev.com, but everytime I have that message :
sending 'unlocktoken' <0 KB>... FAILED <status read failed <Too many links>>
Click to expand...
Click to collapse
I don't know how to resolve that problem, please, anybody, may you help me ?
I give you my device specification down there :
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4D.18.3250.18
version-cpld: None
version-microp: None
version-main: 2.24.73.8
version-misc: PVT SHIP S-ON
serialno: HT37TW908613
imei: <HIDDEN>
meid: <HIDDEN>
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG202
battery-status: good
battery-voltage: 4296mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d959c75800
hbootpreupdate: 11
gencheckpt: 0
Done!
Thank you for everybody reading this post
KoxinHell
KoxinHell said:
Hi everybody from XDA, first time posting here !
Let me explain the problem I have :
Two days ago, my HTC One was booting on Android 4.3, I was on a ROM Stock from ORANGE, with root access, recovery by TWRP on...
And then it started to crash when booting, didn't knew why ! So I tried to flash another ROM on my device (Android_Revolution_HD-One_53.0) Android 4.4.2 with Sense 6.0, but I locked the bootloader before booting on the ROM. I have now a scary message on my bootloader :
I tried to unlock my bootloader via htcdev.com, but everytime I have that message :
I don't know how to resolve that problem, please, anybody, may you help me ?
I give you my device specification down there :
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4D.18.3250.18
version-cpld: None
version-microp: None
version-main: 2.24.73.8
version-misc: PVT SHIP S-ON
serialno: HT37TW908613
imei: <HIDDEN>
meid: <HIDDEN>
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG202
battery-status: good
battery-voltage: 4296mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d959c75800
hbootpreupdate: 11
gencheckpt: 0
Done!
Thank you for everybody reading this post
KoxinHell
Click to expand...
Click to collapse
Power off the phone manually and try it again?
If it doesn't work, try to gain S-OFF using firewater temproot, and then you can unlock bootloader using ADB commands, if your phone is S-OFF.
SaHiLzZ said:
Power off the phone manually and try it again?
If it doesn't work, try to gain S-OFF using firewater temproot, and then you can unlock bootloader using ADB commands, if your phone is S-OFF.
Click to expand...
Click to collapse
I tried like 40 times to power off and doing it again, but it seems that the device is frozen... I still have the original unlock_code.bin sent by HTCDev by the way !
What do you think about that : If I flash my firmware by using fastboot oem rebootRUU, will it change the bootloader with a new firmware or am I wrong ?
Thanks for your attention
KoxinHell
Edit : I can use fastboot, but I can't use adb because the device is not recognized !
KoxinHell said:
And then it started to crash when booting, didn't knew why !
Click to expand...
Click to collapse
this could mean hardware failure...
however, please generate a new unlock code using htc dev, try different computer, cable, usb port, etc.
I had the same problem and I followed this tutorial I fix my problem tried
http://forum.xda-developers.com/showthread.php?t=2475914
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
My device is S-ON and I can't use adb options ! I can only use Fastboot !
Why you can only use Fastboot? Whether S-ON or S-OFF shouldn't be important for ADB.
When I use "adb devices" my devices is not recognized ! But when I do : "fastboot devices" my device is shown !
For adb your phone needs to be booted to android or recovery. If your phone is turned off or in a bootloop, adb won't work
donkeykong1 said:
For adb your phone needs to be booted to android or recovery. If your phone is turned off or in a bootloop, adb won't work
Click to expand...
Click to collapse
Yes I arleady know that ^^ But I can't boot on android or recovery, I can access only to the bootloader ! So adb doesn't works..
I had that <too many links> error, but simple comand repeat always worked for me. So, you could try it yourself. When it gives you the error, just do fastboot flash command again and see what happens
When I send the command :
fastboot flash unlocktoken unlock_code.bin
Click to expand...
Click to collapse
I could wait for hours and hours, because when I unplug my device, the error "too many links" appears !
/UP\ I flashed my firmware last night, I can now access to the recovery, but as I did a factory reset, there isn't any recovery on the device now, my phone can boot aswell, but same as recovery,My bootloader is still ***RELOCKED***. I don't have any ROM installed on ! When I try to flash a recovery, I have a (error signature verify fail)...
I'm waiting for any suggestions !
KoxinHell
You can't flash a recovery without the bootloader unlocked. Did you get another token from the htcdev site
Sent from my HTC One using XDA Premium 4 mobile app
nateboi81 said:
You can't flash a recovery without the bootloader unlocked. Did you get another token from the htcdev site
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In fact, I tried a lot of time to get a new token from htcdev, is it wrong ?
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>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.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
hammaad110 said:
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>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.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
Click to expand...
Click to collapse
Did you do a factory reset? If so you will need to reflash the rom.
zelendel said:
Did you do a factory reset? If so you will need to reflash the rom.
Click to expand...
Click to collapse
i have tried doing factory reset but it stops giving a red triangle with an exclamation mark.
i would be glad if you can guide me to the steps regarding reflashing the rom.
hammaad110 said:
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>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.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
Click to expand...
Click to collapse
waiting for assistance
hammaad110 said:
waiting for assistance
Click to expand...
Click to collapse
Search the site. Everything you need has already been posted.
zelendel said:
Search the site. Everything you need has already been posted.
Click to expand...
Click to collapse
I have downloaded the RUU file
htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_o2_uk_4-20-206-16_radio_4a-23-3263-28_10-38r-1157-04l_release_353143_signed_2-exe
for modelid: PN0710000
cidnum: O2___001
I executed the file while in Fastboot usb mode. The file gave different messages and told me that going to urgrade the ROM to 4.xx. Then it asked me to press next. When I pressed next it restarted the phone and it again went into the infinite loop on restating. while the PC screen was saying waiting for the bootloader and then after 2 or 3 min it said that error in the USB connection.
the phone says MY HTC in Android USB devices when its in Fastboot mode while in normal boot loader mode its not detected. Also adb does not gives anything when i give command adb devices. However Fastboot devices gives serial number if the device.
hammaad110 said:
I have downloaded the RUU file
htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_o2_uk_4-20-206-16_radio_4a-23-3263-28_10-38r-1157-04l_release_353143_signed_2-exe
for modelid: PN0710000
cidnum: O2___001
I executed the file while in Fastboot usb mode. The file gave different messages and told me that going to urgrade the ROM to 4.xx. Then it asked me to press next. When I pressed next it restarted the phone and it again went into the infinite loop on restating. while the PC screen was saying waiting for the bootloader and then after 2 or 3 min it said that error in the USB connection.
the phone says MY HTC in Android USB devices when its in Fastboot mode while in normal boot loader mode its not detected. Also adb does not gives anything when i give command adb devices. However Fastboot devices gives serial number if the device.
Click to expand...
Click to collapse
I would remove all the drivers and start from scratch. FIrst thing you will need to get working is your adb drivers on your PC. Make sure to be running windows 7, uninstall all android drivers, reboot PC, then plug in the android in bootloader mode and let the OS install the needed drivers.
zelendel said:
I would remove all the drivers and start from scratch. FIrst thing you will need to get working is your adb drivers on your PC. Make sure to be running windows 7, uninstall all android drivers, reboot PC, then plug in the android in bootloader mode and let the OS install the needed drivers.
Click to expand...
Click to collapse
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
hammaad110 said:
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
Click to expand...
Click to collapse
Then something is wrong with your driver set up. Check the threads in this section of other ways to get it working. I know that if you had HTC sync installed that it would cause these issues. I have never had this issue where what I discribed above didnt fix
hammaad110 said:
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
Click to expand...
Click to collapse
could you define the difference between "fastboot mode" and "bootloader mode"?
if you are in bootloader and it says FASTBOOT USB (in red), it will detect your device
nkk71 said:
could you define the difference between "fastboot mode" and "bootloader mode"?
if you are in bootloader and it says FASTBOOT USB (in red), it will detect your device
Click to expand...
Click to collapse
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
you should redo all the unlocking procedure try that
hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
not sure what you mean, but:
fastboot commands work in bootloader (FASTBOOT USB on the phone screen), adb does not
adb commands work in custom recovery
adb commands work in booted up phone with USB debuggin enabled
hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
As I explained in our pm's you need to be on hboot 1.55 to use that ruu.
To get your phone unlocked I think you need to flash firmware to refresh your hboot. But unfortunately there isn't any available any where unless @nkk71 knows where you might find it.
With your phone in its current state there is no way for you to use adb, since it won't work in stock recovery. I'm considering going out of my way to help you out here but let's see if nkk71 has anything first.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Danny201281 said:
As I explained in our pm's you need to be on hboot 1.55 to use that ruu.
To get your phone unlocked I think you need to flash firmware to refresh your hboot. But unfortunately there isn't any available any where unless @nkk71 knows where you might find it.
With your phone in its current state there is no way for you to use adb, since it won't work in stock recovery. I'm considering going out of my way to help you out here but let's see if nkk71 has anything first.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
I haven't looked much, but didn't see any 2.24.206.7 or higher firmware.zip in the usual places... it may be out there but i didn't see it.
hammaad110 said:
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
wait, i guess i misunderstood, are you saying HTCdev bootloader unlock is no longer working?? (can you copy/paste command prompt output of that, don't forget to get a new token)
can you also copy/paste the command prompt output of "fastboot oem rebootRUU", do you actually get to ruu mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you can get to RUU mode, you should try to get the RUU to work.
the 4.xx RUUs are OK, but are very picky about PC configuration, USB ports, etc.
nkk71 said:
I haven't looked much, but didn't see any 2.24.206.7 or higher firmware.zip in the usual places... it may be out there but i didn't see it.
wait, i guess i misunderstood, are you saying HTCdev bootloader unlock is no longer working?? (can you copy/paste command prompt output of that, don't forget to get a new token)
can you also copy/paste the command prompt output of "fastboot oem rebootRUU", do you actually get to ruu mode:
if you can get to RUU mode, you should try to get the RUU to work.
the 4.xx RUUs are OK, but are very picky about PC configuration, USB ports, etc.
Click to expand...
Click to collapse
Hi nkk71, I had the same problem with my friends O2uk m7, When it comes helpful files there doesn't seem to be anything for O2.
The bootloader unlocking goes fine up untill the the point he selects "yes" to unlock on the phone. The phone reboots but is still locked.
The RUU in question is an exe I used it myself after many hours of of failing with error 12 signature verification failed, with hboot 1.57. it's the same with this situation. Eventually my friend decided to pay for the sunshine app so I could s-off the device and I finally got the ruu to work by, changing the cid to HTC__001 I then manipulated the firmware using 401 WWE firmware to bring the phone to hboot 1.55. I then changed the cid back to O2__001 and the RUU worked.
So I think he needs the 3.xx.206.x firmware to run the ruu.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Danny201281 said:
Hi nkk71, I had the same problem with my friends O2uk m7, When it comes helpful files there doesn't seem to be anything for O2.
The bootloader unlocking goes fine up untill the the point he selects "yes" to unlock on the phone. The phone reboots but is still locked.
The RUU in question is an exe I used it myself after many hours of of failing with error 12 signature verification failed, with hboot 1.57. it's the same with this situation. Eventually my friend decided to pay for the sunshine app so I could s-off the device and I finally got the ruu to work by, changing the cid to HTC__001 I then manipulated the firmware using 401 WWE firmware to bring the phone to hboot 1.55. I then changed the cid back to O2__001 and the RUU worked.
So I think he needs the 3.xx.206.x firmware to run the ruu.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
ah, yes, i think you're right, HTC did change some "stuff" between earlier releases and later ones, so that would explain the signature fail.
but how did the OP end up in this situation? could very well be a hardware problem... do you have any info on that? considering he's S-On / LOCKED (ie never messed with his phone), and a "semi-successful" HTCdev unlock (ie token is fine, but unlock doesn't unlock) does sound awfully familiar to a hardware problem
* what's the command output of "fastboot oem rebootRUU"? does it go to ruu mode?
* how did this happen?? (is it one of those "it happened suddenly" things?)
nkk71 said:
ah, yes, i think you're right, HTC did change some "stuff" between earlier releases and later ones, so that would explain the signature fail.
but how did the OP end up in this situation? could very well be a hardware problem... do you have any info on that? considering he's S-On / LOCKED (ie never messed with his phone), and a "semi-successful" HTCdev unlock (ie token is fine, but unlock doesn't unlock) does sound awfully familiar to a hardware problem
* what's the command output of "fastboot oem rebootRUU"? does it go to ruu mode?
* how did this happen?? (is it one of those "it happened suddenly" things?)
Click to expand...
Click to collapse
From our pm's
Then it may be because you need to update hboot first.
Are you running the ruu to fix a bootloop problem?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Yes exactly. I want to clear the boot loop problem. The cellphone is of my client and I dont know exactly what he has done wrong with it. As far as he says that he only cleared some junk files and phone is in this condition.
Click to expand...
Click to collapse
I'll be honest I was considering converting my phone to O2 stock and capturing the ota's and making a few stock nandroids. A lot of trouble to help one person especially as you think it could be hardware. But it would help the O2 community as a whole so maybe worth the effort.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Danny201281 said:
From our pm's
Yes exactly. I want to clear the boot loop problem. The cellphone is of my client and I dont know exactly what he has done wrong with it. As far as he says that he only cleared some junk files and phone is in this condition.
Click to expand...
Click to collapse
I'll be honest I was considering converting my phone to O2 stock and capturing the ota's and making a few stock nandroids. A lot of trouble to help one person especially as you think it could be hardware. But it would help the O2 community as a whole so maybe worth the effort.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Well not knowing the background is a real problem.
Do you happen to know the colour of the bootloader? is it a GPE bootloader... this could be another badly done Sense to GPE back to Sense conversion... therefore missing the necessary files/partitions for htcdev unlock to work (even if it's a HTC bootloader)
There is a 4.xx firmware that he could flash (has hboot 1.56 dd Nov 29 2013), though I will not recommend it, as chances of unlocking bootloader will be slim if the O2 RUU fails.
and yeah, capturing all those OTAs for O2, is going to be a bit of work... don't wanna sound selfish, but i'm in no mood for that atm... maybe if i have time on weekend i might consider it, though that is a big maybe
nkk71 said:
Well not knowing the background is a real problem.
Do you happen to know the colour of the bootloader? is it a GPE bootloader... this could be another badly done Sense to GPE back to Sense conversion... therefore missing the necessary files/partitions for htcdev unlock to work (even if it's a HTC bootloader)
There is a 4.xx firmware that he could flash (has hboot 1.56 dd Nov 29 2013), though I will not recommend it, as chances of unlocking bootloader will be slim if the O2 RUU fails.
and yeah, capturing all those OTAs for O2, is going to be a bit of work... don't wanna sound selfish, but i'm in no mood for that atm... maybe if i have time on weekend i might consider it, though that is a big maybe
Click to expand...
Click to collapse
I don't know the bootloader color sorry maybe @hammaad110 can post a picture for us?
I may have a go at capturing the otas if I can make time for it. I won't be capturing them all though may be just the 2.xx and 3.xx with Stock nandroids that would be enough for using the RUU at least and possibility of a reset zip.
Besides I already have the necessary files to make the change to O2. So I wouldn't trouble yourself with that. It was my idea so I wouldn't expect you to go to the trouble of making it happen
As for the bootloader unlocking problem I remember a similar case, although weather we came to a solution is sketchy in my memory. I seem to remember flashing the current firmware fixed the problem. I'll look through my posts and pm's to try to find it so I can clarify it. If that was the case I'll probably capture the ota's to help this guy out and maybe a few others.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
My htc one At&t turned Developer edition was working perfect. No root , No custom rot or whatsoever. I was running latest update 4.4 with Sense 6. It just rebooted and then it just got stuck at the HTC one logo screen. Wont just pass that.
I hard reset with power + down. It rebooted. But then again stuck at the HTC logo screen.
I went to fastboot and tried going to recovery . It just reboots and then comes with a Red Triangle exclamation mark. I was hoping to go in recover and the clean the cache might fix the stuck on boot screen issue. It seems i am not able to go in recovery also. I don't know why.
I tried selecting the factory reset , it took its time. Then it shut down. I again booted it , again stuck at HTC logo screen. It wont load the android. It takes charging fine.
Any idea why going to recovery shows the red exclamation mark ? i have not played with the recovery.. have been getting the HTC update as normal.
Also any way i can boot it now ?? its just stuck at the boot screen.
Was my primary phone.
Thanks,
anirudhgargi said:
My htc one At&t turned Developer edition was working perfect. No root , No custom rot or whatsoever. I was running latest update 4.4 with Sense 6. It just rebooted and then it just got stuck at the HTC one logo screen. Wont just pass that.
I hard reset with power + down. It rebooted. But then again stuck at the HTC logo screen.
I went to fastboot and tried going to recovery . It just reboots and then comes with a Red Triangle exclamation mark. I was hoping to go in recover and the clean the cache might fix the stuck on boot screen issue. It seems i am not able to go in recovery also. I don't know why.
I tried selecting the factory reset , it took its time. Then it shut down. I again booted it , again stuck at HTC logo screen. It wont load the android. It takes charging fine.
Any idea why going to recovery shows the red exclamation mark ? i have not played with the recovery.. have been getting the HTC update as normal.
Also any way i can boot it now ?? its just stuck at the boot screen.
Was my primary phone.
Thanks,
Click to expand...
Click to collapse
the red exclamation mark is normal, the stock recovery is working fine. When you access the recovery and get to this point, hold volume up button and press power to access recovery options. You can factory reset from here and clear cache
stovie_steve said:
the red exclamation mark is normal, the stock recovery is working fine. When you access the recovery and get to this point, hold volume up button and press power to access recovery options. You can factory reset from here and clear cache
Click to expand...
Click to collapse
Great ! Many thanks.
I got to the Recovery menu. I cleared the cache and the selected the factory/reset. And rebooted the device.
But Its till stuck at the boot screen
anirudhgargi said:
Great ! Many thanks.
I got to the Recovery menu. I cleared the cache and the selected the factory/reset. And rebooted the device.
But Its till stuck at the boot screen
Click to expand...
Click to collapse
Can you post a fastboot getvar all and post the results, removing your IMEI and Serial number please?
Are you completely stock, S-on and locked bootloader?
S-on , Bootloader locked. Complete Stock.
stovie_steve said:
Can you post a fastboot getvar all and post the results, removing your IMEI and Serial number please?
Are you completely stock, S-on and locked bootloader?
Click to expand...
Click to collapse
Yes i am Completely on stock with S-on and locked bootloader. I switched my phone from At&t to Dev edition some months back . I installed a Brightstar RUU and did a series of OTA time to time. So it was S-on , bootloader locked and no custom recovery etc All perfect with no playing around. Was my 1st device.
Thanks
anirudhgargi said:
Yes i am Completely on stock with S-on and locked bootloader. I switched my phone from At&t to Dev edition some months back . I installed a Brightstar RUU and did a series of OTA time to time. So it was S-on , bootloader locked and no custom recovery etc All perfect with no playing around. Was my 1st device.
Thanks
Click to expand...
Click to collapse
Please post a fastboot getvar all. To do this, connect your phone to the computer and make sure you have adb/fastboot files. At the bootloader screen it shoulder say FASTBOOT USB
Open a command prompt from the folder where your ADB files are and type the command fastboot getvar all. Post the results here, and remember to remove your serial no and IMEI
GetVar All Output.
stovie_steve said:
Please post a fastboot getvar all. To do this, connect your phone to the computer and make sure you have adb/fastboot files. At the bootloader screen it shoulder say FASTBOOT USB
Open a command prompt from the folder where your ADB files are and type the command fastboot getvar all. Post the results here, and remember to remove your serial no and IMEI
Click to expand...
Click to collapse
Anirudh-Gargis-MacBook:~ anirudhgargi$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -------------------
(bootloader) imei: ----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3790mV
(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
all: Done!
finished. total time: 0.043s
anirudhgargi said:
Anirudh-Gargis-MacBook:~ anirudhgargi$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -------------------
(bootloader) imei: ----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3790mV
(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
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
Your CID is cidnum: 11111111 which means this phone has been rooted before. Did you run any fastboot commands e.g. fastboot writesecureflag 3 and go back to S-ON? Did you install any updates recently?
Rooted when it was 4.1 on At&t. But never then.
stovie_steve said:
Your CID is cidnum: 11111111 which means this phone has been rooted before. Did you run any fastboot commands e.g. fastboot writesecureflag 3 and go back to S-ON? Did you install any updates recently?
Click to expand...
Click to collapse
Yes it was rooted when it was 4.1 and then i installed a 4.2 via RUU.exe to get to Dev Edition. I changed to SuperCid as that time the RUU was not working for some reason. I left it 1111111 as i was able to get the OTA updates normally. Since that 4.3 no rooting and no S-off. Had been like this since then.
I did not install any update recently. Last update was back in Aug for the sense 6.0. Have been using since then without any issue , except for couple of OS crashes.
What you doubt ? Has the OS partition corrupted ? Do i need to reflash ?
anirudhgargi said:
Yes it was rooted when it was 4.1 and then i installed a 4.2 via RUU.exe to get to Dev Edition. I changed to SuperCid as that time the RUU was not working for some reason. I left it 1111111 as i was able to get the OTA updates normally. Since that 4.3 no rooting and no S-off. Had been like this since then.
I did not install any update recently. Last update was back in Aug for the sense 6.0. Have been using since then without any issue , except for couple of OS crashes.
What you doubt ? Has the OS partition corrupted ? Do i need to reflash ?
Click to expand...
Click to collapse
I checked for an RUU for your current version but cannot find one. And because you are S-ON you cannot downgrade or run an earlier RUU
Your option at present may be only to unlock the bootloader via HTC.dev, install custom ROM/Recovery and then obtain S-OFF via firewater or Sunshine to remove the TAMPERED and re-lock the bootloader
Ohh ! i don't have a Window machine also handy
stovie_steve said:
I checked for an RUU for your current version but cannot find one. And because you are S-ON you cannot downgrade or run an earlier RUU
Your option at present may be only to unlock the bootloader via HTC.dev, install custom ROM/Recovery and then obtain S-OFF via firewater or Sunshine to remove the TAMPERED and re-lock the bootloader
Click to expand...
Click to collapse
I was also checking the RUU if theres is one of 4.4 wirh sense6 released by htc.
As i am S-On i cannot download a previous version of RUU and flash that ? Why is that ?
Can a OTA update ( MR ) will do ? i can try searching for the latest OTA file
i can just place the OTA of the latest Sense 6 and then place in storage and choose update via phone storage.
anirudhgargi said:
I was also checking the RUU if theres is one of 4.4 wirh sense6 released by htc.
As i am S-On i cannot download a previous version of RUU and flash that ? Why is that ?
Can a OTA update ( MR ) will do ? i can try searching for the latest OTA file
i can just place the OTA of the latest Sense 6 and then place in storage and choose update via phone storage.
Click to expand...
Click to collapse
S-ON does not permit you to downgrade to another RUU, only upgrade. If you try and flash an RUU.zip via fastboot you will have a beautiful aluminium ornament as the phone will not work.
I don't think there is an OTA either
Many thanks, i will update after doing all those steps.
stovie_steve said:
S-ON does not permit you to downgrade to another RUU, only upgrade. If you try and flash an RUU.zip via fastboot you will have a beautiful aluminium ornament as the phone will not work.
I don't think there is an OTA either
Click to expand...
Click to collapse
I was able to find the Sense 6 4.4 OTA. Just that i am scared now.
I guess i will have to get a window pc to do that what you told.
Many thanks @stovie_steve.
Regards,
ANirudh
anirudhgargi said:
I was able to find the Sense 6 4.4 OTA. Just that i am scared now.
I guess i will have to get a window pc to do that what you told.
Many thanks @stovie_steve.
Regards,
Anirudh
Click to expand...
Click to collapse
1 more question , which file can i download after unlocking the bootloader ?
I mean can i install another binary with S-On and unlocked bootloader ? Which one shall i download
To do S-off i need to have working android (adbshell).
And just to understand the process I need that to install a custom recovery so that i can do a S-off. Once S-off i can run the 4.3 RUU exe. Right ? Of course re-lock the bootloader later as i will be doing a updates from HTC (signed) only.
After that OTA can bring me to latest OS ?
Which Custom rom to flash for next step.
anirudhgargi said:
1 more question , which file can i download after unlocking the bootloader ?
I mean can i install another binary with S-On and unlocked bootloader ? Which one shall i download
To do S-off i need to have working android (adbshell).
And just to understand the process I need that to install a custom recovery so that i can do a S-off. Once S-off i can run the 4.3 RUU exe. Right ? Of course re-lock the bootloader later as i will be doing a updates from HTC (signed) only.
After that OTA can bring me to latest OS ?
Click to expand...
Click to collapse
I have unlocked the bootloader and got a custom recovery (twrp) . I am still s-on. To do S-off
i need to have a working android , for that i need a custom rom. Can anybody tell which rom can be good , i have already the latest Stock 4.4 with "S-ON" and unlocked bootloader.
I cannot flash a htc rom directly as i am S-on and have latest update. To download a version lower (RUU avail) i need to do s-off.
My final aim to get back to Stock 4.4 Sense 6 . This way i approached my HTC one hit a boot loop and not coming out after all methods.
I bought HTC one M7 unlocked from HTC.com when it came out. Last year I modified it to get rid of sense and made it "google play edition". I discovered I can't get OTA updates though due to the presence of stock recovery though.
Question: How can I get rid of TWRP and get back to stock recovery? fastboot getvar version-main returns empty
anil_robo said:
I bought HTC one M7 unlocked from HTC.com when it came out. Last year I modified it to get rid of sense and made it "google play edition". I discovered I can't get OTA updates though due to the presence of stock recovery though.
Question: How can I get rid of TWRP and get back to stock recovery? fastboot getvar version-main returns empty
Click to expand...
Click to collapse
Bump - still looking for answers
anil_robo said:
Bump - still looking for answers
Click to expand...
Click to collapse
everything you need is here >> http://forum.xda-developers.com/showthread.php?t=2358781
Do Not Relock your bootloader !! It will never unlock again
That tutorial still converts to GPE. I need one that converts GPE back to Sense.
anil_robo said:
That tutorial still converts to GPE. I need one that converts GPE back to Sense.
Click to expand...
Click to collapse
What is your android version? 5.1? 5.0?
@alray
Android version is 4.4.4.
The phone downloaded an update (to 5+ ) but I am unable to install it because I have TWRP but not the stock recovery.
anil_robo said:
@alray
Android version is 4.4.4.
The phone downloaded an update (to 5+ ) but I am unable to install it because I have TWRP but not the stock recovery.
Click to expand...
Click to collapse
If its 4.4.4 (Build KTU84P) you need the 4.09.1700.1 stock recovery to install the 5.0.1 update (LRX22C). You'll then receive another notification to install the 5.1 update (LMY47O)
alray said:
If its 4.4.4 (Build KTU84P) you need the 4.09.1700.1 stock recovery to install the update.
Click to expand...
Click to collapse
Thanks a lot!
Actually my "goals" have changed. Now I need to convert the phone into "totally stock" because I want to send it to HTC for free camera fix. If you don't mind, is there an instant messenger etc where I can contact you?
anil_robo said:
Thanks a lot!
Actually my "goals" have changed. Now I need to convert the phone into "totally stock" because I want to send it to HTC for free camera fix. If you don't mind, is there an instant messenger etc where I can contact you?
Click to expand...
Click to collapse
im not really using any IM app but i can help you here. Do you remember your original CID and MID ? Also post the output of "fastboot getvar all" (remove imei/serialno before posting)
alray said:
im not really using any IM app but i can help you here. Do you remember your original CID and MID ? Also post the output of "fastboot getvar all" (remove imei/serialno before posting)
Click to expand...
Click to collapse
My wife has the exact same phone (we bought together) but hers is not tampered at all. So I have the original settings in her phone:
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
I have wife's phone (original) with me right now, and need to convert my phone (tampered) into exact same as my wife's.
fastboot getvar all returns this in my (tampered) phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
Serial and IMEI deleted
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
anil_robo said:
My wife has the exact same phone (we bought together) but hers is not tampered at all. So I have the original settings in her phone:
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
I have wife's phone (original) with me right now, and need to convert my phone (tampered) into exact same as my wife's.
fastboot getvar all returns this in my (tampered) phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
Serial and IMEI deleted
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
So it was originally a developer edition phone right?
First download this ruu and save it in the same folder you have fastboot and adb on your computer. Rename the file "ruu" so it will be easier in the command prompt.
Download this tool and save it on the root of your phone storage
Boot in twrp recovery, select "install" and choose "Guru_Bootloader_Reset_1.0.zip" and then "swipe to install"
Follow instruction of the installer to remove tampered from the bootloader. Don't set the bootloader to locked or re-locked. Keep it unlocked as Developer edition phones are factory bootloader unlocked.
Then boot the phone in bootloader / fastboot usb mode
Confirm that tampered is gone and bootloader is still unlocked.
With the phone still in bootloader, open a command window from your adb/fastboot folder
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver htc logo
Code:
fastboot flash zip ruu.zip
first flash will report "failed, flush image again immediately, so do the same command again:
Code:
fastboot flash zip ruu.zip
this one will report "flashed successfully"
Code:
fastboot reboot-bootloader
If you want to turn the bootloader back to S-ON for warranty do this command as the final step:
Code:
fastboot oem writesecureflag 3
fastboot reboot-bootloader
and confirm phone is S-ON, Unlocked, no tampered flag.
And a big warning here, do not perform this if you are using a windows 8/8.1 computer as the ruu will downgrade hboot to 1.44. hboot 1.44 is not compatible with windows 8.1 and you'll loose fastboot connectivity after the first "fastboot flash zip ruu.zip" and you'll be stuck in ruu mode. Use windows 7. XP, Linux (Ubuntu for example) or use MacOS
alray said:
So it was originally a developer edition phone right?
First download this ruu and save it in the same folder you have fastboot and adb on your computer. Rename the file "ruu" so it will be easier in the command prompt.
Download this tool and save it on the root of your phone storage
Boot in twrp recovery, select "install" and choose "Guru_Bootloader_Reset_1.0.zip" and then "swipe to install"
Follow instruction of the installer to remove tampered from the bootloader. Don't set the bootloader to locked or re-locked. Keep it unlocked as Developer edition phones are factory bootloader unlocked.
Then boot the phone in bootloader / fastboot usb mode
Confirm that tampered is gone and bootloader is still unlocked.
With the phone still in bootloader, open a command window from your adb/fastboot folder
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver htc logo
Code:
fastboot flash zip ruu.zip
first flash will report "failed, flush image again immediately, so do the same command again:
Code:
fastboot flash zip ruu.zip
this one will report "flashed successfully"
Code:
fastboot reboot-bootloader
If you want to turn the bootloader back to S-ON for warranty do this command as the final step:
Code:
fastboot oem writesecureflag 3
fastboot reboot-bootloader
and confirm phone is S-ON, Unlocked, no tampered flag.
And a big warning here, do not perform this if you are using a windows 8/8.1 computer as the ruu will downgrade hboot to 1.44. hboot 1.44 is not compatible with windows 8.1 and you'll loose fastboot connectivity after the first "fastboot flash zip ruu.zip" and you'll be stuck in ruu mode. Use windows 7. XP, Linux (Ubuntu for example) or use MacOS
Click to expand...
Click to collapse
Yes it is a developer edition phone.
Question though: My android version is 4.4.4, and the RUU you linked is 5.0 - does it matter? Won't I run into a "boot loop"?
anil_robo said:
Yes it is a developer edition phone.
Question though: My android version is 4.4.4, and the RUU you linked is 5.0 - does it matter? Won't I run into a "boot loop"?
Click to expand...
Click to collapse
The ruu linked is not 5.0 its 4.1.2 Jelly Bean
anil_robo said:
Yes it is a developer edition phone.
Question though: My android version is 4.4.4, and the RUU you linked is 5.0 - does it matter? Won't I run into a "boot loop"?
Click to expand...
Click to collapse
Wow this was simple! I'm now running stock Jelly Bean, just like a new phone two years ago
I have still left S-OFF and Unlocked - will compare these settings to how my wife's phone is, and then either leave it unlocked or locked to match hers. And then will do S-ON.
Thank you kind sir!
anil_robo said:
Wow this was simple! I'm now running stock Jelly Bean, just like a new phone two years ago
I have still left S-OFF and Unlocked - will compare these settings to how my wife's phone is, and then either leave it unlocked or locked to match hers. And then will do S-ON.
Thank you kind sir!
Click to expand...
Click to collapse
Dev edition are unlocked from factory
Security is set to S-ON from factory
anyway its to late to set the bootloader to locked because the tool to set this requires a custom recovery.
alray said:
Dev edition are unlocked from factory
Security is set to S-ON from factory
anyway its to late to set the bootloader to locked because the tool to set this requires a custom recovery.
Click to expand...
Click to collapse
I'll try this tomorrow: https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
anil_robo said:
I'll try this tomorrow: https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
Click to expand...
Click to collapse
Thats right, I forgot about this. fasboot boot recovery.img will work fine since the phone is now on hboot 1.44, but anayway as I said, dev edition are bootloader unlock from the factory so setting it Locked will be suspicious
@anil_robo see the 4th dot: http://blog.htc.com/2013/03/htc-one-developer-edition/
alray said:
Thats right, I forgot about this. fasboot boot recovery.img will work fine since the phone is now on hboot 1.44, but anayway as I said, dev edition are bootloader unlock from the factory so setting it Locked will be suspicious
@anil_robo see the 4th dot: http://blog.htc.com/2013/03/htc-one-developer-edition/
Click to expand...
Click to collapse
Well I checked wife's phone, and it is "LOCKED" to my surprise. So I have to do the same to match those settings. I bought this phone within few days when it became available, and it may not have been the developer edition I initially thought. It must have been the "international" version rather than the "unlocked developer" version.
anil_robo said:
Well I checked wife's phone, and it is "LOCKED" to my surprise. So I have to do the same to match those settings. I bought this phone within few days when it became available, and it may not have been the developer edition I initially thought. It must have been the "international" version rather than the "unlocked developer" version.
Click to expand...
Click to collapse
The international version is MID PN0710000, version base is .401 e.g. 7.19.401.2 and BS_US001 is not a CID for international version...
There a method to know what your phone was originally. Your original CID/MID and firmware/software version are stored in the MFG partition of your phone. If you can dump this partition to your computer and send it to me, we can determine for sure what it was originally. Unfortnately this partition also include your IMEI and Serial number which should be kept private, if you are ok with sharing this with me here how to proceed:
Boot twrp recovery without flashing it to your phone:
reboot your phone in bootloader / fastboot usb mode
Code:
fastboot boot [URL="https://dl.twrp.me/m7/twrp-2.8.6.0-m7.img.html"]twrp-2.8.6.0-m7.img[/URL]
once booted in twrp main menu, type these commands in the command window:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
exit
exit
Then reboot the phone normally, go to "My Computer --> HTC One --> Internal Storage. You'll find the mmcblk0p6_backup.img file. send it to me via PM only
Tried to go back to stock from another ROM, so relocked bootloader, then ran the latest T-Mobile RUU. The RUU failed and now I'm left with a useless phone. Help is appreciated.
EDIT: It also says "Security Warning" in the bootloader.
Wish39 said:
Tried to go back to stock from another ROM, so relocked bootloader, then ran the latest T-Mobile RUU. The RUU failed and now I'm left with a useless phone. Help is appreciated.
EDIT: It also says "Security Warning" in the bootloader.
Click to expand...
Click to collapse
What RUU did you flash (can you provide a link)? Can you post the output of
Code:
fastboot getvar all
Please remove your serial and imei numbers before posting.
Sent from my HTC One M9 using Tapatalk
Danny201281 said:
What RUU did you flash (can you provide a link)? Can you post the output of
Code:
fastboot getvar all
Please remove your serial and imei numbers before posting.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Got the RUU here: http://www.htc.com/us/support/htc-one-t-mobile/news/
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.531.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Wish39 said:
Got the RUU here: http://www.htc.com/us/support/htc-one-t-mobile/news/
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.531.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
OK so it's definitely the correct ruu, did you relock your bootloader before flashing it? I just read back and see you did relock bootloader.
What was the error message when it failed?
Sent from my HTC One M9 using Tapatalk
Danny201281 said:
OK so it's definitely the correct ruu, did you relock your bootloader before flashing it? I just read back and see you did relock bootloader.
What was the error message when it failed?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I get Error 155: Unknown error
If you still have the Unlock_code.bin file that HTC sent you for unlocking the bootloader, flash that again in Fastboot and then install a custom recovery after that process is done, and finally flash a custom ROM to at least get it working again. If you don't have the file then follow the steps on htcdev.com That's my advice that I can give, hopefully it can help
Edit:
I bet the command to flash it would help too, my apologies. It's fastboot flash unlocktoken Unlock_code.bin This is also all assuming that you unlocked it through their dev website. If you didn't, then you probably can go through their dev site to unlock it again.
Wish39 said:
I get Error 155: Unknown error
Click to expand...
Click to collapse
Error 155 normally is caused by flashing with s-on and unlocked or trying to downgrade firmware with s-on.
It could be due to some outside interference. If you have HTCsync installed it's a good idea to uninstall it.
When you launched the ruu was the device in the bootloader connected with fastbootusb?
What version of windows are you using?
Do you have the latest HTC drivers installed?
https://www.dropbox.com/s/j92rdbh4k2phce4/HTC-Mobile-Driver-v4.17.0.001.zip?dl=0
Sent from my HTC One M9 using Tapatalk
fireball0093 said:
If you still have the Unlock_code.bin file that HTC sent you for unlocking the bootloader, flash that again in Fastboot and then install a custom recovery after that process is done, and finally flash a custom ROM to at least get it working again. If you don't have the file then follow the steps on htcdev.com That's my advice that I can give, hopefully it can help
Edit:
I bet the command to flash it would help too, my apologies. It's fastboot flash unlocktoken Unlock_code.bin This is also all assuming that you unlocked it through their dev website. If you didn't, then you probably can go through their dev site to unlock it again.
Click to expand...
Click to collapse
Ok so to be sure, I did the whole HTCDev process again. Then I dropped the new .bin file into the fastboot folder, opened up adb, and connected the phone when it was in fastboot mode. I ran fastboot flash unlocktoken Unlock_code.bin only for it to fail ("data transfer failed" it said) and the bootloader froze. What is wrong here?
Wish39 said:
Ok so to be sure, I did the whole HTCDev process again. Then I dropped the new .bin file into the fastboot folder, opened up adb, and connected the phone when it was in fastboot mode. I ran fastboot flash unlocktoken Unlock_code.bin only for it to fail ("data transfer failed" it said) and the bootloader froze. What is wrong here?
Click to expand...
Click to collapse
Hmm. Let me quick boot into my bootloader to quick check something. Did you use the volume buttons to select Fastboot in the bootloader? Also I always run fastboot devices just to make sure it's connected, that may have been an issue. I know it might sound redundant but maybe switch the USB port and change the cord if you have a spare one. I have one that acts up from time to time
Edit:
Did you use the ADB prompt or the Fastboot prompt?
Danny201281 said:
Error 155 normally is caused by flashing with s-on and unlocked or trying to downgrade firmware with s-on.
It could be due to some outside interference. If you have HTCsync installed it's a good idea to uninstall it.
When you launched the ruu was the device in the bootloader connected with fastbootusb?
What version of windows are you using?
Do you have the latest HTC drivers installed?
https://www.dropbox.com/s/j92rdbh4k2phce4/HTC-Mobile-Driver-v4.17.0.001.zip?dl=0
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
HTC Sync Manager is uninstalled.
Yes the phone was connected via fastboot when I ran the RUU.
I am using Windows 10.
I just installed the drivers provided by you, so lets see if this works...
fireball0093 said:
Hmm. Let me quick boot into my bootloader to quick check something. Did you use the volume buttons to select Fastboot in the bootloader? Also I always run fastboot devices just to make sure it's connected, that may have been an issue. I know it might sound redundant but maybe switch the USB port and change the cord if you have a spare one. I have one that acts up from time to time
Edit:
Did you use the ADB prompt or the Fastboot prompt?
Click to expand...
Click to collapse
I used Minimal ADB and Fastboot to do this, and I know it works because I used it to unlock the bootloader on my phone. Only this time it can't send the file to the phone.
And yes I selected "Fastboot" in the bootloader menu and when I plug it into the computer it says "Fastboot USB" on the screen.
Wish39 said:
HTC Sync Manager is uninstalled.
Yes the phone was connected via fastboot when I ran the RUU.
I am using Windows 10.
I just installed the drivers provided by you, so lets see if this works...
Click to expand...
Click to collapse
:fingers-crossed: everything seems to be in place. It should flash
Sent from my HTC One M9 using Tapatalk
fireball0093 said:
If you still have the Unlock_code.bin file that HTC sent you for unlocking the bootloader, flash that again in Fastboot and then install a custom recovery after that process is done, and finally flash a custom ROM to at least get it working again. If you don't have the file then follow the steps on htcdev.com That's my advice that I can give, hopefully it can help
Edit:
I bet the command to flash it would help too, my apologies. It's fastboot flash unlocktoken Unlock_code.bin This is also all assuming that you unlocked it through their dev website. If you didn't, then you probably can go through their dev site to unlock it again.
Click to expand...
Click to collapse
Keeps on failing everytime I try to unlock the bootloader
It says something like (data transfer failure-too many links) or whatever.
Wish39 said:
Keeps on failing everytime I try to unlock the bootloader
It says something like (data transfer failure-too many links) or whatever.
Click to expand...
Click to collapse
I took a look at some other threads with people getting that error and they all said they simply switched USB ports, or if you have USB 3.0 to switch it to USB 2.0
fireball0093 said:
I took a look at some other threads with people getting that error and they all said they simply switched USB ports, or if you have USB 3.0 to switch it to USB 2.0
Click to expand...
Click to collapse
Dude! Thanks! I just plugged the phone into the back USB ports on my PC and it successfully unlocked the phone's bootloader! Thanks!
Although that means my PC's front USB ports are screwed up...
Wish39 said:
Dude! Thanks! I just plugged the phone into the back USB ports on my PC and it successfully unlocked the phone's bootloader! Thanks!
Although that means my PC's front USB ports are screwed up...
Click to expand...
Click to collapse
Glad it worked!
Wish39 said:
Dude! Thanks! I just plugged the phone into the back USB ports on my PC and it successfully unlocked the phone's bootloader! Thanks!
Although that means my PC's front USB ports are screwed up...
Click to expand...
Click to collapse
This would also explain the error with your ruu. Should have thought to mention about usb ports.
Your front ports are probably USB1.0 either that or connected to the mainboard through some type of hub. Both will cause problems with fastboot.
Sent from my SM-T230 using Tapatalk