I was just done doing an s-off and getting ready to flash to boost when all of a sudden blank...black screen...
didnt panic until adb devices said no devices checked my device manager and it was sill there...
now when i do fastboot devices i get ??????????? fastboot....
tried RUU and i get stuck on checking the information on your pda
tried flashing through fast boot and i get remote not allowed...this is my get var results
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3418mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
any hope for me ...?
thanx for your help in advance....
yikes
this is scarry....
perfectlywireless said:
I was just done doing an s-off and getting ready to flash to boost when all of a sudden blank...black screen...
didnt panic until adb devices said no devices checked my device manager and it was sill there...
now when i do fastboot devices i get ??????????? fastboot....
tried RUU and i get stuck on checking the information on your pda
tried flashing through fast boot and i get remote not allowed...this is my get var results
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3418mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
any hope for me ...?
thanx for your help in advance....
Click to expand...
Click to collapse
Not sure I can help you out... but you can help the community out by letting us know what the conditions were when you did this. Such as, were you running a custom ROM? Etc...
mrinehart93 said:
Not sure I can help you out... but you can help the community out by letting us know what the conditions were when you did this. Such as, were you running a custom ROM? Etc...
Click to expand...
Click to collapse
did you check the ruu folder to make sure its the ruu you flash and that it doesn't contain a setup.exe file to run?
I believe the encrypted ruu contains an exe file
conditions
wranglerray said:
did you check the ruu folder to make sure its the ruu you flash and that it doesn't contain a setup.exe file to run?
I believe the encrypted ruu contains an exe file
Click to expand...
Click to collapse
I was rooted and removed sprint security, i was soff running phils recovery and super cid...
the ruu does have a setup...ive installed ruu before without the setup through fastboot but everytime i fastboot a command
i get remote not allowed....im stuck...
perfectlywireless said:
I was rooted and removed sprint security, i was soff running phils recovery and super cid...
the ruu does have a setup...ive installed ruu before without the setup through fastboot but everytime i fastboot a command
i get remote not allowed....im stuck...
Click to expand...
Click to collapse
not stuck.
extract the ruu
run the fastboot command
fastboot oem rebootRUU
run the setup file....
but it disapears...
wranglerray said:
not stuck.
extract the ruu
run the fastboot command
fastboot oem rebootRUU
run the setup file....
Click to expand...
Click to collapse
Ok ill try but when i run that command the adb device dissapears from my device manager...
my battery is low now i, charging even though no lights come on...
ill leave it on the charger for a while then ill try running the command.
thanx
perfectlywireless said:
Ok ill try but when i run that command the adb device dissapears from my device manager...
my battery is low now i, charging even though no lights come on...
ill leave it on the charger for a while then ill try running the command.
thanx
Click to expand...
Click to collapse
adb devices only works while booted to OS or recovery
fastboot devices while in bootloader
update
When i type fastboot oem rebootRUU my device dissappears from the device manager..
i typed oem boot and heres what i got... what can i do..??
C:\18\platform-tools_r16.0.1-windows\platform-tools>fastboot oem boot
...
(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!
(bootloader) [ERR] Boot/Recovery image does not exist!!!
OKAY [ 0.000s]
finished. total time: 0.000s
Related
I accidentally wiped the OS, and had no rom saved, so I used adb to transfer this rom over, because it works on sprint
http://forum.xda-developers.com/showthread.php?t=2183023
Then, with TWRP, I installed it, and wiped the cache/dalvik
No errors were had when installing, so I rebooted my phone, and I'm stuck on the "HTC quietly brilliant" logo
No way, that I know of, to exit.
It's at 5% battery, so I can just wait a bit. I still have access to the custom recovery.
How can I make it work again?
Using pc Odin flash stock pull battery down volume+home+power as long as your plugged into computer it will charge itself but you have to return to full stock and start over
SENT FROM MY SAMSUNG NIZOTE 2 DN3
Cod3L1ne said:
Using pc Odin flash stock pull battery down volume+home+power as long as your plugged into computer it will charge itself but you have to return to full stock and start over
SENT FROM MY SAMSUNG NIZOTE 2 DN3
Click to expand...
Click to collapse
LOL whoops this is the HTC One forums ... odin won't help and pulling the battery will be quite the chore
Yeah, Odin won't work.
I probably should mention this too: I can't remember what version I was on, but I know there was no RUU available for it.
Not sure if that counts for anything
Oh my bad lol
SENT FROM MY SAMSUNG NIZOTE 2 DN3
rxvtk said:
Yeah, Odin won't work.
I probably should mention this too: I can't remember what version I was on, but I know there was no RUU available for it.
Not sure if that counts for anything
Click to expand...
Click to collapse
can you do fastboot getvar all
and post it (minus the serial no and iemi)
I'll help you look
clsA said:
can you do fastboot getvar all
and post it (minus the serial no and iemi)
I'll help you look
Click to expand...
Click to collapse
My phone freezes when I do that. That may be important, but here is what is outputed
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 99000146124263
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3533mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.037s
rxvtk said:
My phone freezes when I do that. That may be important, but here is what is outputed
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 99000146124263
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3533mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.037s
Click to expand...
Click to collapse
your phone is Sprint you need flash this
http://www.htc1guru.com/dld/guru_reset_m7_sprint_3-04-651-2-zip/
you can sideload it or push it with adb in recovery from your PC
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload /path/to/rom.zip
ADB Push from Recovery - If Sideload Fails For You
adb push rom.zip /data/media/0/
Even though it's 3.04, when my phone is 1.31?
rxvtk said:
Even though it's 3.04, when my phone is 1.31?
Click to expand...
Click to collapse
yes otherwise your going backwards
clsA said:
yes otherwise your going backwards
Click to expand...
Click to collapse
Alright. I got it installed, yet I get
"unfortunately, qualcomm enhanced location service has stopped"
And can't actually use it. Whenever I try to unlock it, an HTC logo appears, and stays like that
rxvtk said:
Alright. I got it installed, yet I get
"unfortunately, qualcomm enhanced location service has stopped"
And can't actually use it. Whenever I try to unlock it, an HTC logo appears, and stays like that
Click to expand...
Click to collapse
Well I'm not sure
here's the development forum for the rom you just flashed
http://forum.xda-developers.com/showthread.php?t=2467607
maybe you need the firmware update or you may have to flash the full RUU
http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Well, after trying the stock rom, and the one I tried before, I continue to get the "qualcomm enhanced location service has stopped" which prevents me from even unlocking the phone.
should I make a new post?
rxvtk said:
Well, after trying the stock rom, and the one I tried before, I continue to get the "qualcomm enhanced location service has stopped" which prevents me from even unlocking the phone.
should I make a new post?
Click to expand...
Click to collapse
I post the full RUU for you if that doesn't fix your phone it needs to go back to sprint
http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Hi, I have been hunting around and cant seem to resolve this problem.
Yesterday my phone locked up (blank screen) and so I hard reset it.
I was not doing anything with it at them time (in my pocket).
It would then only boot into the bootloader, no recovery.
I have been running CM nightlies with no problem up until now.
I have been running custom roms for a number of years, but would still say that I have limited knowledge.
Outline of Issue
ADB returns an error for every command
Fastboot will see the device, and provide a getvar but returns an error when i try to push a recovery image
I think i have been able to get into RUU (reboots and screen goes black) as i can still get basic fastboot command returns.
No other commands seem to work.
I have gone through a number of guides and used a few different tools but to no avail. (best of all im on the other side of the world from home so cant even use my old phone)
This is what Getvar returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.044s
note the failed line at the bottom.
I have also checked drivers, uninstalled them and reinstalled the naked drivers.
Any advice would be appreciated.
LTP88 said:
Hi, I have been hunting around and cant seem to resolve this problem.
Yesterday my phone locked up (blank screen) and so I hard reset it.
I was not doing anything with it at them time (in my pocket).
It would then only boot into the bootloader, no recovery.
I have been running CM nightlies with no problem up until now.
I have been running custom roms for a number of years, but would still say that I have limited knowledge.
Outline of Issue
ADB returns an error for every command
Fastboot will see the device, and provide a getvar but returns an error when i try to push a recovery image
I think i have been able to get into RUU (reboots and screen goes black) as i can still get basic fastboot command returns.
No other commands seem to work.
I have gone through a number of guides and used a few different tools but to no avail. (best of all im on the other side of the world from home so cant even use my old phone)
This is what Getvar returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37BW901827
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.044s
note the failed line at the bottom.
I have also checked drivers, uninstalled them and reinstalled the naked drivers.
Any advice would be appreciated.
Click to expand...
Click to collapse
nvm. I misread your post.
@cr1960 Please remove IMEI from your quote above
LTP88 said:
Outline of Issue
ADB returns an error for every command
Fastboot will see the device, and provide a getvar but returns an error when i try to push a recovery image
I think i have been able to get into RUU (reboots and screen goes black) as i can still get basic fastboot command returns.
No other commands seem to work.
I have gone through a number of guides and used a few different tools but to no avail. (best of all im on the other side of the world from home so cant even use my old phone)
This is what Getvar returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.044s
Click to expand...
Click to collapse
Remove your IMEI/SN from your post!
1) That is normal, adb only work inside the OS or from custom recovery
2) Which error? Is your bootloader locked or unlocked?
3) When in ruu mode there should be a black screen with a silver HTC logo. Btw I can't find any ruu for your version, do you have one?
4) define ''no other commands''
LTP88 said:
I have also checked drivers, uninstalled them and reinstalled the naked driver
Click to expand...
Click to collapse
Your phone should be listed in windows devices manager as Android usb device --> My HTC. If not then your drivers aren't installed correctly.
There is a guru reset rom you could use to restore your phone,
alray said:
@cr1960 Please remove IMEI from your quote above
Remove your IMEI/SN from your post!
1) That is normal, adb only work inside the OS or from custom recovery
2) Which error? Is your bootloader locked or unlocked?
3) When in ruu mode there should be a black screen with a silver HTC logo. Btw I can't find any ruu for your version, do you have one?
4) define ''no other commands''
Your phone should be listed in windows devices manager as Android usb device --> My HTC. If not then your drivers aren't installed correctly.
There is a guru reset rom you could use to restore your phone,
Click to expand...
Click to collapse
2. unlocked
3. no silver logo is seen. Yes I think it is available RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed
4. I tried
Flash recovery ###.img
Erase Cache
reboot-bootloader
(and a few variations of this)
all of them returned error messages
LTP88 said:
2. unlocked
3. no silver logo is seen. Yes I think it is available RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed
Click to expand...
Click to collapse
No this ruu isn't for your phone, its a .707 you need .980
LTP88 said:
Flash recovery ###.img
Erase Cache
reboot-bootloader
(and a few variations of this)
Click to expand...
Click to collapse
''Flash recovery'' is not a command you must type ''fastboot flash recovery <name_of_recovery>.img'' no capital letters
same for ''Erase cache'' ---> ''fastboot erase cache''
LTP88 said:
all of them returned error messages
Click to expand...
Click to collapse
if you can't be more precise I can't help you! What is the error message?
Edit: better to post a screenshot of your command prompt when you got that error + a screenshot of your adb/fastboot folder will help.
alray said:
No this ruu isn't for your phone, its a .707 you need .980
''Flash recovery'' is not a command you must type ''fastboot flash recovery <name_of_recovery>.img'' no capital letters
same for ''Erase cache'' ---> ''fastboot erase cache''
if you can't be more precise I can't help you! What is the error message?
Edit: better to post a screenshot of your command prompt when you got that error + a screenshot of your adb/fastboot folder will help.
Click to expand...
Click to collapse
Thanks for the help.
I am going to put this on hold until I get home in a week or so.
It's too hard to resolve out of a hotel room with inconstant internet.
How can I flash a ruu? I tryed this RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1 but the setup loop at 5% verifying something. I relocked the bootloader and change cid to htc__001 and I update the firmware to 5.11.401.10
C:\Users\xxx>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Klinda said:
How can I flash a ruu? I tryed this RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1 but the setup loop at 5% verifying something. I relocked the bootloader and change cid to htc__001 and I update the firmware to 5.11.401.10
C:\Users\xxx>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Click to expand...
Click to collapse
your s-off so no need to relock bootloader
you need to downgrade your hboot
see @nkk71 superguide for returning to stock on how to downgrade hboot and RUU > http://forum.xda-developers.com/showthread.php?t=2541082
clsA said:
your s-off so no need to relock bootloader
you need to downgrade your hboot
see @nkk71 superguide for returning to stock on how to downgrade hboot and RUU > http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
I have to only fix my partitions and restore imei and baseband,I don't want to return stock. So why I have to flash hboot 1.44? it's old I think.. I followed this guide in order to downgrade hboot http://forum.xda-developers.com/showthread.php?t=2365506 .. Are you sure I have to downgrade with this old hboot? maybe can be other problems because is too old? so when i will flash hboot 1.44 I will try to flash the ruu I say to you?
Klinda said:
I have to only fix my partitions and restore imei and baseband,I don't want to return stock. So why I have to flash hboot 1.44? it's old I think.. I followed this guide in order to downgrade hboot http://forum.xda-developers.com/showthread.php?t=2365506 .. Are you sure I have to downgrade with this old hboot? maybe can be other problems because is too old? so when i will flash hboot 1.44 I will try to flash the ruu I say to you?
Click to expand...
Click to collapse
yes the old hboot will help with ruu flashing errors
it can create problems if your on windows 8.1
clsA said:
yes the old hboot will help with ruu flashing errors
it can create problems if your on windows 8.1
Click to expand...
Click to collapse
I have windows 7 32 bit.. so I have to change to super cid in order to flash the hboot(i remove tampared also),then change cid to htc__001 and I don't need to relock bootloader in order to flash the ruu?
Klinda said:
I have windows 7 32 bit.. so I have to change to super cid in order to flash the hboot(i remove tampared also),then change cid to htc__001 and I don't need to relock bootloader in order to flash the ruu?
Click to expand...
Click to collapse
not if you have s-off
clsA said:
not if you have s-off
Click to expand...
Click to collapse
I have problem with fastboot commands with windows 7... I can do only one command now.
C:\Users\Lorenzo\Desktop>fastboot getvar all
getvar:all FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
C:\Users\Lorenzo\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.065s
C:\Users\Lorenzo\Desktop>fastboot getvar all
^C
C:\Users\Lorenzo\Desktop>fastboot devices
xxx fastboot
C:\Users\Lorenzo\Desktop>fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.580s
C:\Users\Lorenzo\Desktop>fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.580s
C:\Users\Lorenzo\Desktop>fastboot devices
xxxx fastboot
C:\Users\Lorenzo\Desktop>fastboot getvar all
^C
C:\Users\Lorenzo\Desktop>fastboot devices
xxx fastboot
C:\Users\Lorenzo\Desktop>fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.580s
C:\Users\Lorenzo\Desktop>
So i can't flash the ruu and I think when I do the one command the phone 'freeze' and sometimes if i press power button it leave the fastboot usb or i need to restart the phone.
[email protected]:~$ sudo fastboot devices
[sudo] password for klinda:
xxxx fastboot
[email protected]:~$ sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4264mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.064s
[email protected]:~$ sudo fastboot getvar all
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 1.001s
[email protected]:~$ sudo fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-cpld: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei: xxx
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) battery-status: good
(bootloader) battery-voltage: 4271mV
(bootloader) security: off
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 43.338s
[email protected]:~$ sudo fastboot getvar all
all: Done!eckpt: 0
finished. total time: 0.000s
[email protected]:~$ sudo fastboot getvar all
^C
^C^C^C^[email protected]:~$
Also in linux :/ What can i do? I think I 'bricked' my phone by downgrade hboot(the phone boots without problems but with imei and baseband uknow and it reboots.(I have to fix this with ruu))
Klinda said:
[email protected]:~$ sudo fastboot devices
[sudo] password for klinda:
xxxx fastboot
[email protected]:~$ sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4264mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.064s
[email protected]:~$ sudo fastboot getvar all
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 1.001s
[email protected]:~$ sudo fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-cpld: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei: xxx
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) battery-status: good
(bootloader) battery-voltage: 4271mV
(bootloader) security: off
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 43.338s
[email protected]:~$ sudo fastboot getvar all
all: Done!eckpt: 0
finished. total time: 0.000s
[email protected]:~$ sudo fastboot getvar all
^C
^C^C^C^[email protected]:~$
Also in linux :/ What can i do? I think I 'bricked' my phone by downgrade hboot(the phone boots without problems but with imei and baseband uknow and it reboots.(I have to fix this with ruu))
Click to expand...
Click to collapse
your phone is fine run the RUU
clsA said:
your phone is fine run the RUU
Click to expand...
Click to collapse
I have to change cid? but I think no because if I do the commands of change cid... not have response.. there isn't also the write 'waiting of device' nothing...
Klinda said:
I have to change cid?
Click to expand...
Click to collapse
your super CID no need to change
clsA said:
your super CID no need to change
Click to expand...
Click to collapse
Watch the edited message..
Klinda said:
Watch the edited message..
Click to expand...
Click to collapse
Turn off the phone
hold power and volume down for 20 seconds when it shuts off in the bootloader let go of the buttons.
power the phone back on holding volume down to get to fastboot
plug the phone in to the windows 7 pc and get fastboot usb.
run this RUU >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
clsA said:
Turn off the phone
hold power and volume down for 20 seconds when it shuts off in the bootloader let go of the buttons.
power the phone back on holding volume down to get to fastboot
plug the phone in to the windows 7 pc and get fastboot usb.
run this RUU >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
ERROR [158]: Image error
What can i do?
Klinda said:
ERROR [158]: Image error
What can i do?
Click to expand...
Click to collapse
did you md5 check the file you downloaded to see if it's complete ?
you can also try this one
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
it flashes in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot-bootloader
clsA said:
did you md5 check the file you downloaded to see if it's complete ?
you can also try this one
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
it flashes in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
Yes I check it,now I am dowloading the zip file and I try it.. and wait I need to fix my partitons.. with this old ruu partitions get fixed?
clsA said:
did you md5 check the file you downloaded to see if it's complete ?
you can also try this one
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
it flashes in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
C:\Users\Lorenzo\Desktop>fastboot flash zip rom.zip
sending 'zip' (1010240 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 0.020s
I think with hboot 1.44 fastboot commands bricked. Sorry for answer too late but I was on holiday. There is another way to fix imei and baseband? Sometimes it recgonize imei etc but after 7 8 hours the phone reboots and show the same message.
Up
Someone can help me? or I have to buy a new smartphone? :/
Klinda said:
Up
Someone can help me? or I have to buy a new smartphone? :/
Click to expand...
Click to collapse
is the bootloader locked or unlocked
clsA said:
is the bootloader locked or unlocked
Click to expand...
Click to collapse
Unlocked
So I have an HTC One s-off rooted with cm11.Two days ago it suddenly turned off.Now I can't:
-reboot,it just shows the logo thn turns of
-go to recovery.When I press recovery in bootloader,it just reboots to the bootloader
-cannot flash recovery via fastboot
sending 'recovery' (4336 KB)... OKAY [ 0.391s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.281s
Please help!
Trinity99 said:
So I have an HTC One s-off rooted with cm11.Two days ago it suddenly turned off.Now I can't:
-reboot,it just shows the logo thn turns of
-go to recovery.When I press recovery in bootloader,it just reboots to the bootloader
-cannot flash recovery via fastboot
sending 'recovery' (4336 KB)... OKAY [ 0.391s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.281s
Please help!
Click to expand...
Click to collapse
Try to flash a RUU for your original OS version. This should return you back to stock rom and firmware.
majmoz said:
Try to flash a RUU for your original OS version. This should return you back to stock rom and firmware.
Click to expand...
Click to collapse
How can I decide witch RUU is suitable for my phone?
Trinity99 said:
How can I decide witch RUU is suitable for my phone?
Click to expand...
Click to collapse
post your fastboot getvar all without imei and serial number
Seanie280672 said:
post your fastboot getvar all without imei and serial number
Click to expand...
Click to collapse
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
here it is , thanks for the help.
Trinity99 said:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
here it is , thanks for the help.
Click to expand...
Click to collapse
You should be able to use this RUU: ruu_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe
There is all so an OTA update you can get if it doesn't automatically down load.
Thanks I try it
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\username\Data>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
(bootloader) SD: write failed in CMD25.
OKAY [ 1.073s]
finished. total time: 1.075s
This is the error I get when trying to get in RUU mode
Any ideas?
Trinity99 said:
Any ideas?
Click to expand...
Click to collapse
just run the exe file in windows with your phone in fastboot USB mode, let the RUU do the rest.
Seanie280672 said:
just run the exe file in windows with your phone in fastboot USB mode, let the RUU do the rest.
Click to expand...
Click to collapse
When the installer restarts the phone and "waiting for bootloader" appears the phone doesent boots.Manual boot does nonthing cause the program cannot see the device
Trinity99 said:
When the installer restarts the phone and "waiting for bootloader" appears the phone doesent boots.Manual boot does nonthing cause the program cannot see the device
Click to expand...
Click to collapse
check the drivers in device manager, does it say MyHTC ? even whilst in the bootloader.
Seanie280672 said:
check the drivers in device manager, does it say MyHTC ? even whilst in the bootloader.
Click to expand...
Click to collapse
Yes
Hi everyone, I've brick HTC One. Now it stuck on fastboot mode but the screen is always black even I try to hold power button or power + volume down. I can use fastboot, but seem like it has relock bootloader so I can't do any thing like RUU or recovery....
Here is fastboot getvar all. All phone info has been changed( like imei...) or missed
Code:
(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: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4207mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also I can't flash unlock token
Code:
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.009s
So anyone know how to put it to QHSUSB_DLOAD mode. I can try linux to unbrick it . Thanks so much
Have you tried the RUU and if so what error did you get? I always run my RUU from fastboot.
Sent from my HTC One_M8 using XDA Free mobile app
legion423 said:
Hi everyone, I've brick HTC One. Now it stuck on fastboot mode but the screen is always black even I try to hold power button or power + volume down. I can use fastboot, but seem like it has relock bootloader so I can't do any thing like RUU or recovery....
Here is fastboot getvar all. All phone info has been changed( like imei...) or missed
Code:
(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: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4207mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also I can't flash unlock token
Code:
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.009s
So anyone know how to put it to QHSUSB_DLOAD mode. I can try linux to unbrick it . Thanks so much
Click to expand...
Click to collapse
It shows it's s-off so flashing an ruu should be possible with or without a relocked boot loader. Do you remember your original CID and MID?
You if you can flash firmware it may be possible to forece QHSUSB_DLOAD but it won't necessarily help and you need to know the cid mid. @nkk71 knows more about this than I do, I've only seen this once before and it didn't get fixed
need more info, how did this happen.... messing around with MID by any chance?
Like I've said, I can't use RUU or recovery
Code:
C:\adt-bundle-windows-x86_64-20140624\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: -1
(bootloader) SD: write failed in CMD25.
OKAY [ 1.068s]
finished. total time: 1.069s
. I didn't do anything, the phone auto turn into black screen with no OS, no recovery, Just can go to Hboot, but now after run some fastboot command like rebootRUU ... when reboot-bootloader, the screen is black too
legion423 said:
So anyone know how to put it to QHSUSB_DLOAD mode. I can try linux to unbrick it . Thanks so much
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2363516
http://forum.xda-developers.com/showthread.php?t=2770684
yatindroid said:
http://forum.xda-developers.com/showthread.php?t=2363516
http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
My question is how to put it into QHSUSB_DLOAD mode, 2 topics you give are only working if your phone is in QHSUSB_DLOAD mode.
Anyway thanks you guys for help. I've sent my phone to store, they can use the RIFF BOX to repair boot
legion423 said:
My question is how to put it into QHSUSB_DLOAD mode, 2 topics you give are only working if your phone is in QHSUSB_DLOAD mode.
Anyway thanks you guys for help. I've sent my phone to store, they can use the RIFF BOX to repair boot
Click to expand...
Click to collapse
I think sending for Riff box repair was probably the best course of action. Forcing QHSUSB_DLOAD as i said probably wouldn't help. In fact would most likely make it worse.
You need to flash firmware to get out of QHSUSB_DLOAD but getting it to that state wouldn't restore you MID, CID IMEI, Version main and so on. So flashing firmware still wouldn't work. :good: That's the reason you didn't get an answer to that question no one wants to help make it worse.
For the record QHSUSB_DLOAD is caused by skipping firmware updates so to do it you would still need to flash firmware. e.g If the device has 2.24.401.1 firmware and you flash a firmware 6.09.401.5 from an OTA that would almost certainly put the device in QHSUSB_DLOAD. The Unbrick project merely repairs the emmc enabling you to get to the bootloader to flash the correct firmware to repair this missing parts of the firmware. In this case it would probably just bring you back to the same problem or simply wouldn't work giving you a "device not found" error