Database Develop

[Q] Wiped OS and Wiped SDcard

Hello.
I have been trying to repair this by myself for 3 days reading this forum but I just can't do it.
My phone had unlocked bootloader, rooted and SOFF. When I was flashing a rom I don't know what happened but it deleted my OS.
Then I tried to update my firmware and it deleted my SD card. I'm stuck at TWPR recovery.
Now when I try to use a RUU installer it always shows an error, I also tried to use a RUU via fastboot command and it shows error 42. My bootloader is relocked btw.
I cannot sideload anything because my SD was wiped.
I'm now somewhat desperate. I just want my phone to revive.
My MODEL ID is PN0712000 and I got SuperCID 1111111
My firmware is version is 3.17.502.3.
PLEASE help me.

MsDosExe said:
Hello.
I have been trying to repair this by myself for 3 days reading this forum but I just can't do it.
My phone had unlocked bootloader, rooted and SOFF. When I was flashing a rom I don't know what happened but it deleted my OS.
Then I tried to update my firmware and it deleted my SD card. I'm stuck at TWPR recovery.
Now when I try to use a RUU installer it always shows an error, I also tried to use a RUU via fastboot command and it shows error 42. My bootloader is relocked btw.
I cannot sideload anything because my SD was wiped.
I'm now somewhat desperate. I just want my phone to revive.
My MODEL ID is PN0712000 This indicates your phone is AT&T or Developers edition and I got SuperCID 1111111
My firmware is version is 3.63.707.4.
PLEASE help me.
Click to expand...
Click to collapse
What Ruu did you try ?
and can you boot to bootloader and give me the results for
fastboot getvar all
minus your serial no and IEMI, I can help you much better with this info.
If you are s-off it should be no problem getting you up and running

clsA said:
What Ruu did you try ?
and can you boot to bootloader and give me the results for
fastboot getvar all
minus your serial no and IEMI, I can help you much better with this info.
If you are s-off it should be no problem getting you up and running
Click to expand...
Click to collapse
I'm trying RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
These are my results from getvar:
C:\abd\platform-tools\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s

MsDosExe said:
I'm trying RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
These are my results from getvar:
C:\abd\platform-tools\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
Click to expand...
Click to collapse
Everything looks Good !!
Hold the power button and vol down till the phone reboots
continue holding just vol down back to the bootloader
then do
fastboot erase cache
fastboot reboot-bootloader
then to fastboot USB and start the RUU on your PC again (rebooting the PC before doing all this is a good idea also).(If your on windows 7 running the RUU as Administrator is good too)
Also check the md5 of the RUU you downloaded to make sure it's good

clsA said:
Everything looks Good !!
Hold the power button and vol down till the phone reboots
continue holding just vol down back to the bootloader
then do
fastboot erase cache
fastboot reboot-bootloader
then to fastboot USB and start the RUU on your PC again (rebooting the PC before doing all this is a good idea also).(If your on windows 7 running the RUU as Administrator is good too)
Also check the md5 of the RUU you downloaded to make sure it's good
Click to expand...
Click to collapse
I dit everything and the ruu installer keeps saying the same error.
"Error 155 IMAGE ERROR"
How can I check the MD5? Maybe that's the problem.

MsDosExe said:
I dit everything and the ruu installer keeps saying the same error.
"Error 155 IMAGE ERROR"
Click to expand...
Click to collapse
does the phone ever reboot to RUU mode ?
correct file and md5
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/

clsA said:
does the phone ever reboot to RUU mode ?
Click to expand...
Click to collapse
When I run the installer it reboots in RUU Mode (the grey HTC letters) then it checks my phone, deletes my user data, and then it says "sending..." after that it fails and shows the 155 IMAGE ERROR and something about getting the right ROM.
How can I check the MD5? Maybe that's the problem.

MsDosExe said:
When I run the installer it reboots in RUU Mode (the grey HTC letters) then it checks my phone, deletes my user data, and then it says "sending..." after that it fails and shows the 155 IMAGE ERROR and something about getting the right ROM.
How can I check the MD5? Maybe that's the problem.
Click to expand...
Click to collapse
The post above yours
extract it to the desktop
go to the other link and copy the listed md5 for your ruu
then find you ruu in the bottom box and check it
if it's red you need to redownload

clsA said:
The post above yours
extract it to the desktop
go to the other link and copy the listed md5 for your ruu
then find you ruu in the bottom box and check it
if it's red you need to redownload
Click to expand...
Click to collapse
I got the wrong MD5 on the RUU. I downloaded the one you provided and my HTC One is back to life again.
Thank you very much. I have never figure it out without you.

MsDosExe said:
I got the wrong MD5 on the RUU. I downloaded the one you provided and my HTC One is back to life again.
Thank you very much. I have never figure it out without you.
Click to expand...
Click to collapse
I'm Glad your back up and running !!

HTC One stuck at HTC quietly brilliant

To start off, I have had my htc one for about 4 months and around December my battery died and I charged it back up. I was then shown the boot loader screen which I never had seen before. Ever since then when I restart my phone it randomly goes to that screen sometimes so I just then did fast boot and booted into the android os. Yesterday my phone froze so I attempted to restart it and then I was stuck with the htc quietly brilliant screen. I have let the battery die like that and charged it back up but nothing happens. I tried to factory reset it in the boot loader but that does not work either. The boot loader currently shows this:
Tampered
Locked
S-ON
Keep in mind I have never tried to install custom roms or anything else I have left it purely at stock. I also got it straight from a T-mobile store. Help is appreciated.
-Thanks!

maxt95 said:
To start off, I have had my htc one for about 4 months and around December my battery died and I charged it back up. I was then shown the boot loader screen which I never had seen before. Ever since then when I restart my phone it randomly goes to that screen sometimes so I just then did fast boot and booted into the android os. Yesterday my phone froze so I attempted to restart it and then I was stuck with the htc quietly brilliant screen. I have let the battery die like that and charged it back up but nothing happens. I tried to factory reset it in the boot loader but that does not work either. The boot loader currently shows this:
Tampered
Locked
S-ON
Keep in mind I have never tried to install custom roms or anything else I have left it purely at stock. I also got it straight from a T-mobile store. Help is appreciated.
-Thanks!
Click to expand...
Click to collapse
So if you got it straight from T-mo and never flashed stuff, why is the bootloader tampered?
post your ''fastboot getvar all'' minus imei/sn

alray said:
So if you got it straight from T-mo and never flashed stuff, why is the bootloader tampered?
post your ''fastboot getvar all'' minus imei/sn
Click to expand...
Click to collapse
I'm not sure why. Heres the info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxx
(bootloader) imei: xxxxxx
(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: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

maxt95 said:
I'm not sure why. Heres the info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxx
(bootloader) imei: xxxxxx
(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: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
ok, the bootloader tampered flag mean someone already unlocked it. If you are 100% sure you did not attempted to mod anything, this mean your phone wasn't new when you bought it and you should consider returning it back to store. The main problem is that they will probably deny the warranty because of this tampered flag. They will probably assume that you have tampered the phone.
You can also try to reset back to 100% stock with an ruu.exe. Be sure to use a windows 8.0, 7 or xp computer. not a windows 8.1. Connect the phone to your computer and boot it to bootloader mode then, lauch the ruu.exe.
This is the ruu you need
edit: note that it will completely wipe your data.
edit2: note that the ruu will not remove the tampered flag unless you want to go trough many other steps.

alray said:
ok, the bootloader tampered flag mean someone already unlocked it. If you are 100% sure you did not attempted to mod anything, this mean your phone wasn't new when you bought it and you should consider returning it back to store. The main problem is that they will probably deny the warranty because of this tampered flag. They will probably assume that you have tampered the phone.
You can also try to reset back to 100% stock with an ruu.exe. Be sure to use a windows 8.0, 7 or xp computer. not a windows 8.1. Connect the phone to your computer and boot it to bootloader mode then, lauch the ruu.exe.
edit: note that it will completely wipe your data.
edit2: note that the ruu will not remove the tampered flag unless you want to go trough many other steps.
Click to expand...
Click to collapse
Ok I'll do that and see what happens. Thanks for the help!

@maxt95
If your phone still have issue after the ruu (freeze/reboot) then we can assist you to s-off, remove tempered flag etc etc... make the device looks like if it had never been tampered with and you'll be able to send it under warranty
if you screwed this yourself don't be shy to admit it. Much easier to assist when we know all the details.

alray said:
@maxt95
If your phone still have issue after the ruu (freeze/reboot) then we can assist you to s-off, remove tempered flag etc etc... make the device looks like if it had never been tampered with and you'll be able to send it under warranty
if you screwed this yourself don't be shy to admit it. Much easier to assist when we know all the details.
Click to expand...
Click to collapse
I finally got it to work. I had to try multiple computers to do it though haha. Anyways thanks for helping out!

I need your help!
maxt95 said:
I finally got it to work. I had to try multiple computers to do it though haha. Anyways thanks for helping out!
Click to expand...
Click to collapse
Hey it seems like you got your phone workin. I am having the same issue, I understand we need to reset the rom or something. Will you be able to tell me the steps required? Thanks bro

kingk3n said:
Hey it seems like you got your phone workin. I am having the same issue, I understand we need to reset the rom or something. Will you be able to tell me the steps required? Thanks bro
Click to expand...
Click to collapse
please post the output of ''fastboot getvar all'' minus IMEI/SN and explain a little more your situation.

im using htc one
alray said:
please post the output of ''fastboot getvar all'' minus IMEI/SN and explain a little more your situation.
Click to expand...
Click to collapse
Hi thanks for your response. I am using HTC one and, I'm not sure how to execute the fastboot getvar all command. I know how to get to the bootloader w/c is holding the power button down and, holding volume down at the same time

kingk3n said:
Hi thanks for your response. I am using HTC one and, I'm not sure how to execute the fastboot getvar all command. I know how to get to the bootloader w/c is holding the power button down and, holding volume down at the same time
Click to expand...
Click to collapse
You will need to have fastboot/adb tools installed on your computer ----> HERE
and you'll need latest HTC drivers installed. This can be done by installing HTC sync software you can find HERE
then reboot in bootloader mode, select fastboot, open minimal adb and fastboot and enter the cmd.
btw you still didn't described your issue ...

alray said:
You will need to have fastboot/adb tools installed on your computer ----> HERE
and you'll need latest HTC drivers installed. This can be done by installing HTC sync software you can find HERE
then reboot in bootloader mode, select fastboot, open minimal adb and fastboot and enter the cmd.
btw you still didn't described your issue ...
Click to expand...
Click to collapse
My issue is that my phone is stuck at the "HTC Quiently Brilliant" screen. I tried reboot, recovery and reset factory settings, I still get stuck at the htc screen.. Let me try what you've suggested.
And, by the way my bootloader says ****LOCKED*** (Pink Font) on top of the menu.. Not sure if that helps...

kingk3n said:
My issue is that my phone is stuck at the "HTC Quiently Brilliant" screen. I tried reboot, recovery and reset factory settings, I still get stuck at the htc screen.. Let me try what you've suggested.
And, by the way my bootloader says ****LOCKED*** (Pink Font) on top of the menu.. Not sure if that helps...
Click to expand...
Click to collapse
ok waiting for your ''fastboot getvar all'' can you also post a picture of your bootloader screen or write down all info?

alray said:
ok waiting for your ''fastboot getvar all'' can you also post a picture of your bootloader screen or write down all info?
Click to expand...
Click to collapse
Here it is brother... Please see below & attached screen shot of my bootloader
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4112mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s

kingk3n said:
Here it is brother... Please see below & attached screen shot of my bootloader
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4112mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
So it looks like your phone is completely stock and you never tampered it. Since you already did a factory reset, there is not much you can do... you should try to erase cache and see if the phone can boot properly:
reboot phone in bootloader/fastboot mode and type this command:
Code:
fastboot erase cache
fastboot reboot
if your phone still don't boot you should consider go back to a bell mobility store and ask for a repair/replacement if your phone is still under warranty. If not under waranty you can try the guide linked in my signature below (return stock for canadian user by SaHiLzZ). The guide require to flash a custom recovery which need an unlocked bootloader. Unlocking the bootloader will wipe the phone and may void your warranty.

alray said:
So it looks like your phone is completely stock and you never tampered it. Since you already did a factory reset, there is not much you can do... you should try to erase cache and see if the phone can boot properly:
reboot phone in bootloader/fastboot mode and type this command:
Code:
fastboot erase cache
fastboot reboot
if your phone still don't boot you should consider go back to a bell mobility store and ask for a repair/replacement if your phone is still under warranty. If not under waranty you can try the guide linked in my signature below (return stock for canadian user by SaHiLzZ). The guide require to flash a custom recovery which need an unlocked bootloader. Unlocking the bootloader will wipe the phone and may void your warranty.
Click to expand...
Click to collapse
No Luck !!!! Thanks for helping me though. I will call HTC and ask them to fix it for me.
Damnnn HTC !!!!

alray said:
So it looks like your phone is completely stock and you never tampered it. Since you already did a factory reset, there is not much you can do... you should try to erase cache and see if the phone can boot properly:
reboot phone in bootloader/fastboot mode and type this command:
Code:
fastboot erase cache
fastboot reboot
if your phone still don't boot you should consider go back to a bell mobility store and ask for a repair/replacement if your phone is still under warranty. If not under waranty you can try the guide linked in my signature below (return stock for canadian user by SaHiLzZ). The guide require to flash a custom recovery which need an unlocked bootloader. Unlocking the bootloader will wipe the phone and may void your warranty.
Click to expand...
Click to collapse
Hey, is there a way for me to recover all my pictures while its on the bootloader? I need to get those pictures copied. Please advise.
Thanks

[Q] Bell Mobility M7_ul is bricked, could someone give me some guidance?

Hello,
This is my first post but I've been reading for months and months everything I could find here on ways to fix my M7. In the meantime I've bought an M8, call me crazy but I'd really like to get my M7 back up and running. I'm stubborn, but now it's time to ask for help
One day, a few months ago, I tried installing a custom splash screen. I kind of thought, well, this might brick it, but I can fix it. I had tested my backup but somewhere along the line it became corrupted and I didn't have a backup of my backup. Since then, I have tried flashing different recoveries (CWM, TWRP, Philz), tried converting to Google Play edition per the instructions I found on these forums, tried various RUU's, both zips and exe's. I edited the android-info.txt file to match what the phone said in "fastboot getvar all", I changed CID's where appropriate to match the RUU's, tried running with the bootloader locked and unlocked and still the closest to life I could bring this thing was stuck on a Google splash screen. It will not boot into recovery, although it seems to install a recovery. It just sits on "entering recovery". Even if I leave it there for a day thinking maybe it's just taking it's time.
So then I tried flashing the original firmware, and a copy of a Nandriod backup for version 3.23.666.1 for Bell, none of which has worked. I am unable to get any results from "adb devices" (it just returns a blank line), so pushing anything via adb won't work either. Adb does indeed work because I am able to access my M8 with adb commands.
I have tried all of this on Windows 7, Ubuntu (a few different version), and a MacBook.
Is there any hope for this phone? Here are the details:
It's unlocked and S-OFF, here are the results of getvar all:
C:\adb\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.666.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.107s
Thanks a bunch for taking the time to read all of this, and any input at all is greatly appreciated.
Take Care,
~PittieInPink

PittieInPink said:
Hello,
This is my first post but I've been reading for months and months everything I could find here on ways to fix my M7. In the meantime I've bought an M8, call me crazy but I'd really like to get my M7 back up and running. I'm stubborn, but now it's time to ask for help
One day, a few months ago, I tried installing a custom splash screen. I kind of thought, well, this might brick it, but I can fix it. I had tested my backup but somewhere along the line it became corrupted and I didn't have a backup of my backup. Since then, I have tried flashing different recoveries (CWM, TWRP, Philz), tried converting to Google Play edition per the instructions I found on these forums, tried various RUU's, both zips and exe's. I edited the android-info.txt file to match what the phone said in "fastboot getvar all", I changed CID's where appropriate to match the RUU's, tried running with the bootloader locked and unlocked and still the closest to life I could bring this thing was stuck on a Google splash screen. It will not boot into recovery, although it seems to install a recovery. It just sits on "entering recovery". Even if I leave it there for a day thinking maybe it's just taking it's time.
So then I tried flashing the original firmware, and a copy of a Nandriod backup for version 3.23.666.1 for Bell, none of which has worked. I am unable to get any results from "adb devices" (it just returns a blank line), so pushing anything via adb won't work either. Adb does indeed work because I am able to access my M8 with adb commands.
I have tried all of this on Windows 7, Ubuntu (a few different version), and a MacBook.
Is there any hope for this phone? Here are the details:
It's unlocked and S-OFF, here are the results of getvar all:
C:\adb\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.666.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.107s
Thanks a bunch for taking the time to read all of this, and any input at all is greatly appreciated.
Take Care,
~PittieInPink
Click to expand...
Click to collapse
What was the error when trying to flash RUUs? it should be very easy to restore your phone with s-off. you could try the dev edition ruu
change cid to BS_US001:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
then confirm the cid is correct:
Code:
fastboot oem readcid
then download this ruu.zip and save it to your adb/fastboot folder, rename it to "ruu" (ruu.zip)
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
btw your blank line when typing "adb devices" is normal. Adb doesnt work from the bootloader, only from a custom recovery of from the OS whit usb debug ON.

Good morning and thank you, I'm downloading the RUU you posted and will give it a try following all of your instructions.
I didn't actually get any error messages when flashing the RUU's, for the most part (when I had the correct cid etc) there were no error messages and it actually said successful on both the first and second executions of the flash command. It just wouldn't boot, it would get stuck on either the HTC or Google splash screen, depending which RUU I was trying.
No error logs either. I'm obviously doing something wrong eh? Fingers crossed the above works!

@alray
I followed all of the above steps and got the RUU seemed to flash okay, it said "sucessful" both times. I ran the fastboot reboot command and it's just sitting on the white screen with the green htc logo.

htc one m7 gpe stuck in bootloop

Hi all,
So I woke up this morning and power on my phone to find it stuck in some sort of boot loop. It loads to the home screen which seems like it might work but 30 seconds later it reboots on its own.
The phone is stock, unrooted and the bootloader is locked (and S-ON).
I already did a factory reset (wipe cache + data) but didn't work.
I'm trying to unlock the bootloader to flash a recovery and a new rom but I'm not able to do that.
I followed all the steps to unlock the bootloader as reported in HTCdev, but after I typed the last command
fastboot flash unlocktoken Unlock_code.bin
the "splash" screen didn't appear on my phone so I wasn't able to complete the unlock.
Can anyone help me with unlocking the bootloader?? Or did anyone know another method to unbrick my phone that is stuck in a bootloop??
Thank you in advance,
Mattia.

raffoaddicted said:
Hi all,
So I woke up this morning and power on my phone to find it stuck in some sort of boot loop. It loads to the home screen which seems like it might work but 30 seconds later it reboots on its own.
The phone is stock, unrooted and the bootloader is locked (and S-ON).
I already did a factory reset (wipe cache + data) but didn't work.
I'm trying to unlock the bootloader to flash a recovery and a new rom but I'm not able to do that.
I followed all the steps to unlock the bootloader as reported in HTCdev, but after I typed the last command
fastboot flash unlocktoken Unlock_code.bin
the "splash" screen didn't appear on my phone so I wasn't able to complete the unlock.
Can anyone help me with unlocking the bootloader?? Or did anyone know another method to unbrick my phone that is stuck in a bootloop??
Thank you in advance,
Mattia.
Click to expand...
Click to collapse
The bootloader unlock issue is well known on the gpe bootloaders and unfortunately, they never fixed it. Sunshine S-OFF willl be the only way to unlock (and s-off). Otherwise you could try a RUU if there is one for your phone (need to know you "fastboot getvar all").

alray said:
The bootloader unlock issue is well known on the gpe bootloaders and unfortunately, they never fixed it. Sunshine S-OFF willl be the only way to unlock (and s-off). Otherwise you could try a RUU if there is one for your phone (need to know you "fastboot getvar all").
Click to expand...
Click to collapse
Hi, thank you for your reply!
fastboot getvar all gives
Code:
(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: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Thanks,
Mattia

raffoaddicted said:
Hi, thank you for your reply!
fastboot getvar all gives
Code:
(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: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Thanks,
Mattia
Click to expand...
Click to collapse
This one should work
https://www.androidfilehost.com/?fid=24369303960689828

Hi,
I apologize for not answering sooner!
Btw, thank you for the file, but now... How am I supposed to preceed?
My problems are also that:
1) fastboot recognizes my phone, but adb does not. I'm confident that I actived usb debugging but i'm not totally sure of that... so I think that it's why adb doesn't find my phone.
2) as soon as try to do ''apply from storage" or "apply from sd card" in the recovery of my phone... it reboots with ''invalid operation, check cid failed".
Thank you so much, and sorry to bother you again, but i'm a novice.
Cheers,
mattia

raffoaddicted said:
Hi,
I apologize for not answering sooner!
Btw, thank you for the file, but now... How am I supposed to preceed?
My problems are also that:
1) fastboot recognizes my phone, but adb does not. I'm confident that I actived usb debugging but i'm not totally sure of that... so I think that it's why adb doesn't find my phone.
2) as soon as try to do ''apply from storage" or "apply from sd card" in the recovery of my phone... it reboots with ''invalid operation, check cid failed".
Thank you so much, and sorry to bother you again, but i'm a novice.
Cheers,
mattia
Click to expand...
Click to collapse
1)abd is only accessible from a custom recovery or from a booted OS. fastboot is the only thing you need to flash a ruu.
fastboot oem rebootRUU
fastboot flash zip "filename".zip
fastboot flash zip "filename".zip
fastboot reboot
If your bootloader is unlocked, you must relock it first using "fastboot oem lock"

alray said:
1)abd is only accessible from a custom recovery or from a booted OS. fastboot is the only thing you need to flash a ruu.
fastboot oem rebootRUU
fastboot flash zip "filename".zip
fastboot flash zip "filename".zip
fastboot reboot
If your bootloader is unlocked, you must relock it first using "fastboot oem lock"
Click to expand...
Click to collapse
ok!
Thank you!!

M7 - boots to fastboot and recovery, can't boot custom ROMs, errors in RUUs

Hello everybody!
I am loosing my mind with this, would be grateful if someone could help me!
Received an HTC One M7 Nordic (HTC__Y13) version, HBOOT 1.61.0000, radio 4T.35.3218.16, ODSP 35.120.274.0718 OS.
Firstly, I unlocked the bootloader via HTCdev, then, as I did with other devices, installed CWM which I used to wipe just about everything and I installed LineageOS. (S-ON, Tampered, Unlocked bootloader). To my surprise, LOS didn't boot, booting back to fastboot. I gave it another try, reinstalling it, failed to boot again. Then I started trying the RUUs, and the farthest I could reach was the signature rejection at 4%. I am using a Mac with both Sierra and a windows XP SP3 VM in Parallels, which I also used to try with a myriad of toolkits made for this phone. In HTC Sync, although the phone is recognised, all info, like OS version, are blank.
Well, here I am with a device without OS which boots to fastboot and TWRP/CWM. Since the beginning of this adventure, I couldn't boot once to a ROM, and I lost 3 long nights on this already. I believe the only things I could have missed are: using the right RUU.exe or zip, or someway getting the phone S-OFF without using an OS, since I don't have one.
When trying to "fastboot flash -zip ruu.zip", I always have some kind of error like "remote 02 data length is too large" or a variant of this.
I am getting kinda afraid I may have bricked the phone. Could someone help me?
Thanks!
here is the "getvar" dump
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3BRWxxxxxx
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

wasserprojekt said:
When trying to "fastboot flash -zip ruu.zip", I always have some kind of error like "remote 02 data length is too large" or a variant of this.
Click to expand...
Click to collapse
You must use htc_fastboot.exe from a Windows pc, not the regular fastboot. Make sure you have the latest RUU for your cid/mid

Thanks for your answer. I was about to give up on this, but then I finally found the right RUU. There are so many variants it becomes a nightmare finding the adequate one, eve worse if version is not one of the best selling.
But, as someone may need this advice in the future, I'll leave a summary of the important steps in here:
Return to stock ROM (for S-ON & unlocked bootloader & tampered):
- relock your device;
fastboot oem lock
Click to expand...
Click to collapse
-find the adequate RUU;
(for HTC__Y13, it's the RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe)
-close all programs which may connect to phone (includes HTC sync, any fastboot or adb command window...), otherwise there will be no progress in the RUU;
-start the RUU with phone connected (VMs work - at leaset in Parallels with XP SP3).
Thanks to everyone.