Hi there,
After many days now I've been unable to get my phone to reset back to factory. I've followed many tutorials on this and other websites/forums with absolutely no success.
To cut a looooong story short I cannot change anything on my phone and it keeps restarting itself whenever it does anything remotely intensive.
If I delete a file, once it restarts (either manually or by itself) the file comes back.
If I change an alarm, delete a text message, add a phone number, after it restarts none of the changes have stayed.
The phone seems to literally have NO capability of keeping any changes made and restores back to exactly the same position it was in when the problem first began.
I have managed to get into the settings > factory reset and after it begins it restarts and I get the dreaded red triangle with exclamation mark in it.
I have tried the volume up + power button menu from here to try and factory reset it, doesn't work and just reverts back to the dead-state.
I have followed the unlock tutorials, which involve the unlock token from HTCdev and fastboot , this brings up the warranty warning and I can press yes to unlock the bootloader, but as soon as I select it, the phone restarts and puts it back into the dead-state (nothing has changed!)
Anyway ask me any questions and I'll get back with the information/results, I'm literally at my wits end with this so I really hope somebody can help!
GETVAR ALL
C:\Android>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 5.1204.171.31H
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.771.7_R1
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3807mV
(bootloader) devpower: 57
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.871s
Unlock Dump
C:\Android>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 33928CDBB8D0128C5EEEFF5473D43215
(bootloader) B2DAA4DEFE57CB35F27AC9D84AE99712
(bootloader) 20B9CA683A1A36BAE121535DF6B8071C
(bootloader) 5CAB1F09868ADD176C85C263C4989563
(bootloader) 4359D461C687284B12022D3621C6CE2D
(bootloader) CFFD2D428ABDA2096B192D69DFF1797B
(bootloader) C7EABA3A7385E7585582A7A8EFAB5A5C
(bootloader) 366131600DE8D801CD48734468D779AE
(bootloader) EDABF581DD150C3E768EEB06C0194B3B
(bootloader) 9FC226029276F09EA973FB4F3E064DF0
(bootloader) 46E6FF293CB5011C1DE54C833A352843
(bootloader) D15B57F83E4AA21D7AD69396A5353157
(bootloader) B289C0602018D01F64C523F04B58EF6D
(bootloader) 57F8C9F9C9D77BE2336BD3D1BD5D100F
(bootloader) F6CF341F94497CE693C7F33AD8EDF2A7
(bootloader) 316B42C59DE9A6FB2AB75C238CA0B3ED
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.217s]
finished. total time: 0.220s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 66.483s
Please help
h20xyg3n said:
Hi there,
After many days now I've been unable to get my phone to reset back to factory. I've followed many tutorials on this and other websites/forums with absolutely no success.
To cut a looooong story short I cannot change anything on my phone and it keeps restarting itself whenever it does anything remotely intensive.
If I delete a file, once it restarts (either manually or by itself) the file comes back.
If I change an alarm, delete a text message, add a phone number, after it restarts none of the changes have stayed.
The phone seems to literally have NO capability of keeping any changes made and restores back to exactly the same position it was in when the problem first began.
I have managed to get into the settings > factory reset and after it begins it restarts and I get the dreaded red triangle with exclamation mark in it.
I have tried the volume up + power button menu from here to try and factory reset it, doesn't work and just reverts back to the dead-state.
I have followed the unlock tutorials, which involve the unlock token from HTCdev and fastboot , this brings up the warranty warning and I can press yes to unlock the bootloader, but as soon as I select it, the phone restarts and puts it back into the dead-state (nothing has changed!)
Anyway ask me any questions and I'll get back with the information/results, I'm literally at my wits end with this so I really hope somebody can help!
GETVAR ALL
C:\Android>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 5.1204.171.31H
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.771.7_R1
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3807mV
(bootloader) devpower: 57
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.871s
Unlock Dump
C:\Android>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 33928CDBB8D0128C5EEEFF5473D43215
(bootloader) B2DAA4DEFE57CB35F27AC9D84AE99712
(bootloader) 20B9CA683A1A36BAE121535DF6B8071C
(bootloader) 5CAB1F09868ADD176C85C263C4989563
(bootloader) 4359D461C687284B12022D3621C6CE2D
(bootloader) CFFD2D428ABDA2096B192D69DFF1797B
(bootloader) C7EABA3A7385E7585582A7A8EFAB5A5C
(bootloader) 366131600DE8D801CD48734468D779AE
(bootloader) EDABF581DD150C3E768EEB06C0194B3B
(bootloader) 9FC226029276F09EA973FB4F3E064DF0
(bootloader) 46E6FF293CB5011C1DE54C833A352843
(bootloader) D15B57F83E4AA21D7AD69396A5353157
(bootloader) B289C0602018D01F64C523F04B58EF6D
(bootloader) 57F8C9F9C9D77BE2336BD3D1BD5D100F
(bootloader) F6CF341F94497CE693C7F33AD8EDF2A7
(bootloader) 316B42C59DE9A6FB2AB75C238CA0B3ED
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.217s]
finished. total time: 0.220s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 66.483s
Please help
Click to expand...
Click to collapse
Are you uninstalled HTC Sync before run the command. Uninstall get new code and try again. Change USB cable with original try on differnt port or PC. Use latest drivers from HTC
This FAILED (status read failed (Too many links)) error is normal
Thant said:
Are you uninstalled HTC Sync before run the command. Uninstall get new code and try again. Change USB cable with original try on differnt port or PC. Use latest drivers from HTC
This FAILED (status read failed (Too many links)) error is normal
Click to expand...
Click to collapse
Hi Thant,
Yeah I've seen it is a common error to get the 'Too Many Links' thing. But for most it seems to atleast unlock their phone, which for me it does not.
I did read somewhere about uninstalling HTC Sync while trying to perform the unlock, I tried this, with no success.
I will try the unlock process again tonight, retreive a new code and change the USB cable out.
When you say at the end there 'Use latest drivers from HTC' - you mean installing the latest HTC Sync and then Uninstalling it before I attempt another unlock procedure, right?
h20xyg3n said:
Hi Thant,
Yeah I've seen it is a common error to get the 'Too Many Links' thing. But for most it seems to atleast unlock their phone, which for me it does not.
I did read somewhere about uninstalling HTC Sync while trying to perform the unlock, I tried this, with no success.
I will try the unlock process again tonight, retreive a new code and change the USB cable out.
When you say at the end there 'Use latest drivers from HTC' - you mean installing the latest HTC Sync and then Uninstalling it before I attempt another unlock procedure, right?
Click to expand...
Click to collapse
YES install HTC Sync and then uninstall only HTC Sync leave the drivers and I read somwhere guy that have your problem and changing USB1.1 to USB2.0 solve him problem try on differnt PC too
Hello, I have a verizon htc one m7. I am rooted and s-off.
1: getvar info
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.066s
2: In the the bootloader screen if I choose recovery the phone tries to load twrp screen goes to entering recovery goes black then the entering recovery screen comes back up and stays until I power down:
{
"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"
}
3: I have tried fastboot, flashify, rom toolbox pro and linux to flash twrp images. every one of them does so without error, yet I can not get into twrp. The md5 on every file I have tried to flash checked out ok.
4: I installed the ruu from dottat kitkat 4.4.2 and 4.4.3 and installed the ruu version of twrp 2.7.0.8 and 2.7.1.12 and still recovery does not load. This is after installing an ruu and wipes the phone completely.
5:I have tried everything that has been suggested including running the commands from a linux terminal.
If anybody knows how to fix this please help!
vaping redhead said:
Hello, I have a verizon htc one m7. I am rooted and s-off.
1: getvar info
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.066s
2: In the the bootloader screen if I choose recovery the phone tries to load twrp screen goes to entering recovery goes black then the entering recovery screen comes back up and stays until I power down:
3: I have tried fastboot, flashify, rom toolbox pro and linux to flash twrp images. every one of them does so without error, yet I can not get into twrp. The md5 on every file I have tried to flash checked out ok.
4: I installed the ruu from dottat kitkat 4.4.2 and 4.4.3 and installed the ruu version of twrp 2.7.0.8 and 2.7.1.12 and still recovery does not load. This is after installing an ruu and wipes the phone completely.
5:I have tried everything that has been suggested including running the commands from a linux terminal.
If anybody knows how to fix this please help!
Click to expand...
Click to collapse
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
jpradley said:
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
Click to expand...
Click to collapse
they are in zip format and can be downloaded from dottat thread in the developer section. you use the command fasboot flash zip "filename"
http://forum.xda-developers.com/verizon-htc-one/development/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643
http://forum.xda-developers.com/showthread.php?t=2765784
vaping redhead said:
they are in zip format and can be downloaded from dottat thread in the developer section. you use the command fasboot flash zip "filename"]
Click to expand...
Click to collapse
OK, thanks.
But what's wrong with the file format that most everyone uses for a recovery installation, which isn't a *zip file, but a *img file?
jpradley said:
OK, thanks.
But what's wrong with the file format that most everyone uses for a recovery installation, which isn't a *zip file, but a *img file?
Click to expand...
Click to collapse
It is my understanding that img files can be flashed directly from fastboot or flashify etc. the zip file contains the image file and also a txt file and can only be flashed while your phone is in ruu mode "fastboot oem rebootRUU"
since there is 2 files that it why it is zipped. the txt file contained in there is the istructions that tell the rom update utility how to flash the enclosed recovery image file.
jpradley said:
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
Click to expand...
Click to collapse
Fastboot erase cache
Then flash your recovery again and see what you have.
dottat said:
Fastboot erase cache
Then flash your recovery again and see what you have.
Click to expand...
Click to collapse
I have tried that command, it does not solve recovery not loading. Trust me I have tried every suggestion I can find on the internet and nothing solves this. I am hoping someone out there has knowledge of exaclty how the recovery partition works because at this point it would appear that the recovery partition on my phone is either not being written to or is corrupted.
vaping redhead said:
I have tried that command, it does not solve recovery not loading. Trust me I have tried every suggestion I can find on the internet and nothing solves this. I am hoping someone out there has knowledge of exaclty how the recovery partition works because at this point it would appear that the recovery partition on my phone is either not being written to or is corrupted.
Click to expand...
Click to collapse
When you flash the ruu mode twrp put a -w on the end of the command.
dottat said:
When you flash the ruu mode twrp put a -w on the end of the command.
Click to expand...
Click to collapse
I will try. Here are the results
c:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
c:\adb>fastboot flash zip M7_RUU_TWRP.zip -w
target reported max download size of 1514139648 bytes
sending 'zip' (9360 KB)...
OKAY [ 1.059s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,10
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.179s]
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 4.250s
Revovery still does not load.
vaping redhead said:
I will try. Here are the results
c:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
c:\adb>fastboot flash zip M7_RUU_TWRP.zip -w
target reported max download size of 1514139648 bytes
sending 'zip' (9360 KB)...
OKAY [ 1.059s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,10
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.179s]
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 4.250s
Revovery still does not load.
Click to expand...
Click to collapse
Failed (remote not allowed)
Is a sure sign that something isn't set up right for flashing to the device.
It will never work if that is the result in terminal.
Are you using Usb 2.0 and the original data cable that is meant for the device?
I think you probably never successfully flashed any recovery.
I would advise trying a cable meant for this device.
santod040 said:
Failed (remote not allowed)
Is a sure sign that something isn't set up right for flashing to the device.
It will never work if that is the result in terminal.
Are you using Usb 2.0 and the original data cable that is meant for the device?
I think you probably never successfully flashed any recovery.
I would advise trying a cable meant for this device.
Click to expand...
Click to collapse
I am using the htc cable that came with the phone. I will double check that I am using USB 2.0 and try a different cable.
I also noticed wihen flashing with rom toolbox pro is says successful yet also says #error: cannot locate recovery partition
Is it possible my recovery partitiion is not there?
I just tried several cables including the the one from htc. I also made sure I was using a usb 2.0 port. I still get the failed(remote not allowed)
Thank you for the help btw.
Hi, I think I have figured this one out. I changed my phone from blue to red. Verizon only offers silver or blue. Anyway I thought I might have damaged my motherboard, So I bought a silver verizon htc one off ebay with a cracked screen. (easy fix). So I swapped the hardware from the silver to my red and with a new board in the red shell twrp does not load. However my old board wich twrp would not load on is now in the silver shell and twrp now loads. Bottom line the red shell is the problem.
vaping redhead said:
Hi, I think I have figured this one out. I changed my phone from blue to red. Verizon only offers silver or blue. Anyway I thought I might have damaged my motherboard, So I bought a silver verizon htc one off ebay with a cracked screen. (easy fix). So I swapped the hardware from the silver to my red and with a new board in the red shell twrp does not load. However my old board wich twrp would not load on is now in the silver shell and twrp now loads. Bottom line the red shell is the problem.
Click to expand...
Click to collapse
Update. The red shell is 100% to blame for recovery software not loading. I did some more tinkering with two m7 motherboards and in a stock verizon silver shell twrp loads. Both board when in the red shell, twrp does not load.
If anyone out there was thinking of converting their blue or silver verizon m7 to a different color. Be warned that your recovery software will probably not load once you transfer the hardware over to the new shell.
I guess if I want a red htc one that twrp works on, I have to get a m8
vaping redhead said:
Update. The red shell is 100% to blame for recovery software not loading. I did some more tinkering with two m7 motherboards and in a stock verizon silver shell twrp loads. Both board when in the red shell, twrp does not load.
If anyone out there was thinking of converting their blue or silver verizon m7 to a different color. Be warned that your recovery software will probably not load once you transfer the hardware over to the new shell.
I guess if I want a red htc one that twrp works on, I have to get a m8
Click to expand...
Click to collapse
Or just.... Paint it with a good quality modeling paint (like you buy for model cars, boats, etc). It is durable and lasts if you know how to coat it correctly.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Doesn't seem to me that you solved the initial problem, just found a work around for it. I have the same problem with my phone not accepting the stock recovery for what ever reason. It will, however, accept the TWRP recovery, but this doesn't do me any good wrt warranty returns. before I S-On and Lock it, I need to have the stock recovery installed.
gryghst72 said:
Doesn't seem to me that you solved the initial problem, just found a work around for it. I have the same problem with my phone not accepting the stock recovery for what ever reason. It will, however, accept the TWRP recovery, but this doesn't do me any good wrt warranty returns. before I S-On and Lock it, I need to have the stock recovery installed.
Click to expand...
Click to collapse
Have you tried ruu? That should flash the stock recovery and everything else stock. Need to ruu when you s-on to ensure everything is okay before turning secure flag on.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Have you tried ruu? That should flash the stock recovery and everything else stock. Need to ruu when you s-on to ensure everything is okay before turning secure flag on.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
I have RUU'd the following and in different orders:
5.28.605.2_NoBoot-IMG_firmware.zip
VZW.M7.5.28.605.2.PN0731IMG.zip
as well as "fastboot flash recovery 5.28.605.2_Stock_recovery.img"
all with a scattering of "fastboot erase cache".
The flash says it is successful, but when I boot to recovery, the screen graphics are garbage and when not garbage, it's the ! droid after the usual 15-20 sec blank screen. When I flash TWRP either via flash recovery or RUU that takes and works just fine. But this obviously isn't a "back to stock" set up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3899mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.164s
Thoughts?
gryghst72 said:
I have RUU'd the following and in different orders:
5.28.605.2_NoBoot-IMG_firmware.zip
VZW.M7.5.28.605.2.PN0731IMG.zip
as well as "fastboot flash recovery 5.28.605.2_Stock_recovery.img"
all with a scattering of "fastboot erase cache".
The flash says it is successful, but when I boot to recovery, the screen graphics are garbage and when not garbage, it's the ! droid after the usual 15-20 sec blank screen. When I flash TWRP either via flash recovery or RUU that takes and works just fine. But this obviously isn't a "back to stock" set up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3899mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.164s
Thoughts?
Click to expand...
Click to collapse
Have you tried the 2.x.y.z signed ruu in santod's stock Rom/firmware thread? Unsigned ruus are good, but sometimes a signed, official ruu gets the job done that unofficial ones can't.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Have you tried the 2.x.y.z signed ruu in santod's stock Rom/firmware thread? Unsigned ruus are good, but sometimes a signed, official ruu gets the job done that unofficial ones can't.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Is the signed one located here? I have not only because I have not read that one can go backwards, especially that far back. Can this be done successfully? What are the risks? Does the signed RUU contain all he necessary files to restart after the flash, are there any supporting flashes necessary (HBOOT, Recovery, Radios, etc.) Is this a viable solution or a shot in the dark which could brick the device?
Thanks for the on-going troubleshooting. I'm not trying to be a pain, just being careful since I am unfamiliar with the bootload/security features build into the system.
---------- Post added at 03:33 PM ---------- Previous post was at 02:58 PM ----------
I tried to RUU flash the 1.10.605.10 version .. here was my result:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Android>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 44.569s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 51.044s
C:\Android>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 44.632s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 51.075s
C:\Android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.031s
Well, that didn't do anything, good or bad. Just didn't take and phone operates just fine as a phone, but still no recovery image, stock or otherwise.
Downloading 2.x.y.z signed version now. Will report the results after flash attempt.
Same results:
C:\Android>adb reboot-bootloader
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Android>fastboot flash zip RUU_2_10_605_1.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1232586 KB)...
OKAY [ 41.931s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 48.420s