Database Develop

[Q] [HELP] INCREDIBLE S goes in infinite boot loop

I have got an issue with HTC incredible S going in boot loop. The phone is 2 yrs old and was running fine with official ICS installed on it. One fine day it just hung and after restart went into bootlaoder.
HBOOT is unlocked, rooted, and S-ON
HBOOT-2.02.002
RADIO-3831.18.00.11_M
I have tried a lot of things like stock ICS rom, recovery cleanup, cache+dalvik clean-up using recovery, RUU installation etc.
However, it refuses to get repiared . It runs fine for say a day after stock rom update and then starts throwing exception like process android.acore.*** has stopped or similar and after restart again goes to bootloader.
I have tried different RUUs, however, none of theme seems to support and some say error 171 related to customer Id.
Tried to create goldcard but revskills site is down.
So bottomline is I have tried everything possible, and now I think my phone is bricked
Any other suggestions you may have?

Anyone?????? EXperts PLLLLLLLLLZZZZZZ help me out.......................

Whoa !!! Where've all the experts gone ........

Flash boot.img manually..
Fastboot flash boot boot.Img
This ll be inside ur Rom zip :thumbup:
Just in case if u ve forgotten to boot
Sent from my Incredible S
---------- Post added at 11:13 PM ---------- Previous post was at 11:01 PM ----------
If you have a custom recovery installed.. wipe all except your SD.. and then flash a custom Rom and flash boot.img manually as you are S-on. And restart..
Sent from my Incredible S

Thanks for the reply mafie!!!
I had tried it but just wanted confirm it and just connected my IncS to laptop and ou know what ??? my handy is not getting detected... all I can see is
123456789012 fastboot
Is my phone dead???

Fastboot get var all
Give some more info on your phone..
Sent from my Incredible S

Here it is
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.02.0002
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: 123456789012
(bootloader) product: vivo
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s

droidseeker1 said:
Here it is
finished. total time: 0.008s
Click to expand...
Click to collapse
1. take down all the imei and stuff like that cuz u really dont want other people to know that stuff.
2. Make sure adb and fastboot drivers are corrrectly installed
3. If its properly installed and you say ure computer can't detect your device, how did u enter command fastboot getvar all??? Is your computer detecting your device properly?

072665995 said:
1. take down all the imei and stuff like that cuz u really dont want other people to know that stuff.
2. Make sure adb and fastboot drivers are corrrectly installed
3. If its properly installed and you say ure computer can't detect your device, how did u enter command fastboot getvar all??? Is your computer detecting your device properly?
Click to expand...
Click to collapse
Hmm sorry for the confusion, but what I meant by *not detecting* was computer is not properly recognizing it properly.
it is running all the fastboot commands but serial id is shown as 123456789012 and charging light is not turning on.
meanwhile, i checked the drivers and they look good to me....
I am worried now

F5 ... Please help me guys....

droidseeker1 said:
F5 ... Please help me guys....
Click to expand...
Click to collapse
So from bootloader can you go to recovery?

poondog said:
So from bootloader can you go to recovery?
Click to expand...
Click to collapse
Sorry couldn't reply .. wasn't wired lately ....
No ... I am not able to go to Recovery and can not even flash it as whenever I try to flash it, it says something about writing error (Perhaps it is because of phone not being recognized)

[Recovery]5.0.1 Google Play Edition Stock Recovery + Bootloader + Firmware

Thanks to @pasker17 this wouldn't have been possible without him and his device!
Stock Recovery(Unlocked bootloader required. S-off not needed)
To flash boot into fastboot (either by adb reboot bootloader or holding down volume down and power when device is off) and run the command
fastboot flash recovery recoverygpe.img
GPE Bootloader & Splash Screen (to be flashed in RUU Mode S-off required)
To flash boot into fastboot (either by adb reboot bootloader or holding down volume down and power when device is off) and run the command
Once in bootloader type fastboot oem RebootRUU once at the HTC logo screen (RUU Mode) run
fastboot flash zip zipfilename.zip
All files can be downloaded from my website http://www.graffixnyc.com/m8.php
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, or flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....

added bootloader and splash screen to OP

Is there a thread describing the installation process and pre-requisites?

I assume flashing this bootloader on normal m8 will result in GE dark bootloader?
Sent from my Viper One

@graffixnyc Would this be ok to flash on an Att m8

I'm sorry if this is a retarded question. But what is the difference between flashing this ROM --> http://forum.xda-developers.com/showthread.php?t=2706441 and using the recovery from this thread?

graffixnyc,sent you a general question via pm if you get a minute

Will this work on my M8?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.21331831.A05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.22.980.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
----------------------------------------------------------------
Viper OneM8 + ElementX

If I change one of MID's to mine will it flash properly, without any adverse effects?
Sent from my HTC One_M8 using Tapatalk

Within the 'android-info.txt' file that is
Pushed from my Freed Viper OneM8

Will it have any adverse effect on Att devices?
Sent from my HTC One_M8 using xda app-developers app

graffixnyc said:
Thanks to @pasker17 this wouldn't have been possible without him and his device!
Stock Recovery(Unlocked bootloader required. S-off not needed)
To flash boot into fastboot (either by adb reboot bootloader or holding down volume down and power when device is off) and run the command
fastboot flash recovery recoverygpe.img
Link: http://www.androidfilehost.com/?fid=23329332407584495
Mirror: http://d-h.st/nMe
GPE Bootloader & Splash Screen (to be flashed in RUU Mode S-off required)
To flash boot into fastboot (either by adb reboot bootloader or holding down volume down and power when device is off) and run the command
Once in bootloader type fastboot oem RebootRUU once at the HTC logo screen (RUU Mode) run
fastboot flash zip zipfilename.zip
[/SIZE][/COLOR]
Click to expand...
Click to collapse
Installed the gpe recovery, adb said installed ok. If I boot into bootloader then recovery I get the dead android icon which stays on screen for 1 minute then the phone reboots
Secondly the command to fastboot oem RebootRUU gives
ERR command error?
Phone is unlocked, Rooted, S-off and Super CID

grentuu said:
Installed the gpe recovery although no recovery is showing after installing even though it said success.
Secondly the command to fastboot oem RebootRUU gives
ERR command error?
Phone is unlocked, Rooted, S-off and Super CID
Click to expand...
Click to collapse
the stock recovery requires a button press to show once the android is on ur screen, i think its vol up+pwr or vol dwn+pwr
also the command is fastboot oem rebootRUU it is case specific.

djkinetic said:
the stock recovery requires a button press to show once the android is on ur screen, i think its vol up+pwr or vol dwn+pwr
also the command is fastboot oem rebootRUU it is case specific.
Click to expand...
Click to collapse
Recovery sorted but the RebootRUU wont work and I have been case specific forget it... I see the error. Thank you. Will try now
---------- Post added at 06:04 PM ---------- Previous post was at 05:54 PM ----------
grentuu said:
Recovery sorted but the RebootRUU wont work and I have been case specific forget it... I see the error. Thank you. Will try now
Click to expand...
Click to collapse
I dumbly followed the instructions on page one which says RebootRUU lol. I should know better

If we flash this can we ever go back to sense? And do we need to wipe data after we flash?
Sent from my HTC One_M8 using xda app-developers app

bpdev said:
@graffixnyc Would this be ok to flash on an Att m8
Click to expand...
Click to collapse
I too would like to know this. I wouldn't mind the dark splash screen but want to make sure there are new ill effects.
Sent from my HTC One_M8

REDFOCZ said:
I too would like to know this. I wouldn't mind the dark splash screen but want to make sure there are new ill effects.
Sent from my HTC One_M8
Click to expand...
Click to collapse
I flashed then to my AT&T m8,but upon boot it sat at the splash screen. I booted into recovery and it said I didn't have an OS installed to /system. So I had to flash the GPE RUU to get back going.
Sent from my HTC One_M8 using xda app-developers app

wera750 said:
I flashed then to my AT&T m8,but upon boot it sat at the splash screen. I booted into recovery and it said I didn't have an OS installed to /system. So I had to flash the GPE RUU to get back going.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Oh wow, thanks for the heads up. I'm not sure if I'm ready to convert to a Gpe device just yet. I'll stick with what I have.
Sent from my HTC One_M8

WreckTangle said:
I assume flashing this bootloader on normal m8 will result in GE dark bootloader?
Sent from my Viper One
Click to expand...
Click to collapse
I thought it would, but I believe the system partition is smaller. I flashed it thinking I could have dark boot loader with my sense ROM, but it wiped my phone and I couldn't install venom back on my device, and it wouldn't boot. Finally thought it might be boot loader related so when I flashed back it worked again. But even with hboot back to the Dev hboot it says version 3.16 or whatever the gpe boot loader version is.
Sent from my HTC One_M8 using Tapatalk

Is 3.16 the hboot version on all HTC m8s? I may have been mistaken in my previous post
Sent from my HTC One_M8 using Tapatalk

My HTC One is soft-bricked(?) and i have no idea what to do

Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000

George Kayogre said:
Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?

George Kayogre said:
Hello,
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592

clsA said:
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592
Click to expand...
Click to collapse
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".

George Kayogre said:
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".
Click to expand...
Click to collapse
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful

alray said:
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful
Click to expand...
Click to collapse
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something

George Kayogre said:
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something
Click to expand...
Click to collapse
uninstall htc sync and try again

alray said:
uninstall htc sync and try again
Click to expand...
Click to collapse
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.

George Kayogre said:
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.
Click to expand...
Click to collapse
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.

alray said:
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.
Click to expand...
Click to collapse
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
This is what "fastboot getvar all" returned:
(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: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
clsA said:
Unzip this to your desktop and open a command window from it's folder (right click - command prompt here)
plug in your phone to the pc boot to the bootloader with power + volume down
type fastboot devices
your phone serial number should be listed
now type fastboot erase cache
it should say something about formatting cache
now fastboot reboot
hopefully your phone will boot back up
Click to expand...
Click to collapse
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen

George Kayogre said:
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
This is what "fastboot getvar all" returned:
(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: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen
Click to expand...
Click to collapse
have you tried to perform a factory reset from the bootloader?

alray said:
have you tried to perform a factory reset from the bootloader?
Click to expand...
Click to collapse
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.

George Kayogre said:
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.
Click to expand...
Click to collapse
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms

alray said:
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms
Click to expand...
Click to collapse
Here's something new: after unlocking my phone, and having confirmed that i wanted all my "personal data erased", it just booted up normally and it worked, but then, while using it, t=it simply crashed...and got stuck in the bootloop again, which kinda points in the arrow of hardware issue again. I'm gonna try installing a rom (after i figure out how) and see where that leads me.
Update: Flashed CM11, phone still on boot loop, sending to repair soon.
Everyone, thanks for the help anyway, I really appreciate it.

bootloader refuses to unlock

I've tried to unlock the boot loader of my HTC one m7 to no avail.
I tried unlocking it via htcdev but after wiping my phone, my boot loader still remained locked.
is there any alternative way of unlocking the boot loader without htcdev?
I saw one that involved typing some commands in fastboot but I'm afraid that might wreck the phone.
PS, I'm a newbie so please make any suggestions as plain as possible

gravity02 said:
I've tried to unlock the boot loader of my HTC one m7 to no avail.
I tried unlocking it via htcdev but after wiping my phone, my boot loader still remained locked.
is there any alternative way of unlocking the boot loader without htcdev?
I saw one that involved typing some commands in fastboot but I'm afraid that might wreck the phone.
PS, I'm a newbie so please make any suggestions as plain as possible
Click to expand...
Click to collapse
So is your device ***LOCKED*** or ***RELOCKED*** by which I mean has it ever been unlocked before or this is the first time?
Normally the course of action for bootloader unlocking issues is to flash a matching firmware package and request a new Unlock_code.bin. But let's see what variant of M7 you have first not all M7s can be unlocked via HTCdev.
Could you post the out put of
Code:
fastboot getvar all
Please remove your IMEI and Serial numbers before posting for security purposes
If you can't use HTCdev and your device is s-on then the only option is Sunshine App but it costs $25 so let's see what you've got and go from there :good:

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3721mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))

gravity02 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3721mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Ok your s-off That's good you have a couple of options here. You can flash a firmware package and request a new Unlock_code.bin as I mentioned above. :good: I'll see if I can find a firmware zip for you and post the link here
EDIT: -You can download a matching firmware here http://d-h.st/NPJ. Do you know how to flash firmware.zips with fastboot?
Or you can boot a custom recovery and unlock it yourself using "adb shell"
With the recovery image file in your fastboot folder. Connect fastboot usb and in the command window type
Code:
[B]fastboot boot recovery "name-of-recovery".img[/B]
[B]adb shell[/B]
[B]su[/B] (if needed to get a*#*prompt)
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/B]
(i would very strongly recomend you copy/paste this)
[B]exit[/B]
(exit a second time if you need to to get back to a normal > prompt)
[B]adb reboot bootloader[/B]
verify you are now unlocked
The above method is taken from this thread http://forum.xda-developers.com/showthread.php?t=2475914 Thanks should go to the OP :good:

thanks for the quick replies. I already have twrp installed. should I now run the command?
will it erase my files?

gravity02 said:
thanks for the quick replies. I already have twrp installed. should I now run the command?
will it erase my files?
Click to expand...
Click to collapse
HTCdev method will wipe your DATA and SDCARD
Recovery command method will not wipe anything :good:
Quoted from the Main Thread in above link
piterk said:
Could you tell me if this method to lock/unlock bootloader wipes phone data like the method via htcdev?
Click to expand...
Click to collapse
scotty1223 said:
no,it does not erase data.
the flashing of unlock code,and relock command initiate hboot to factory reset. this is only changing the flag that hboot checks.
Click to expand...
Click to collapse

tried this but it didn't work. the boot loader remained locked.
the phone was once bricked and I had it fixed via a JTAG. could this be a reason for this?

gravity02 said:
tried this but it didn't work. the boot loader remained locked.
the phone was once bricked and I had it fixed via a JTAG. could this be a reason for this?
Click to expand...
Click to collapse
Mmmm that's strange try again but this time use CWM https://www.dropbox.com/s/82kt3edku0j2sup/cwm.img?dl=0 you don't need to flash it just boot it with
Code:
fastboot boot cwm.img
Failing that did you try the firmware method?

I haven't tried the firmware method. can you walk me through it?

gravity02 said:
I haven't tried the firmware method. can you walk me through it?
Click to expand...
Click to collapse
Download the firmware package linked in my previous post. Put the zip in your fastboot folder and rename it "firmware.zip"
Boot your phone to the bootloader and connect fastbootusb, Now in the fastboot command line type
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now go to htcdev and complete the Unlock my bootloader procedure to get a new Unlock_code.bin :fingers-crossed:
FYI :- Flashing the firmware will restore the Stock Recovery so after the Unlock you will need to flash your Custom recovery again

I followed the steps but my phone is now stuck in the htc logo. I can't even switch it off

done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:

gravity02 said:
done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:
Click to expand...
Click to collapse
Hold down the power button and the volume down together, the capacitive buttons will flash, don't worry just let them flash and just keep holding down those 2 buttons, when they stop flashing which is about 12 to 15 times, release the power button, but continue to hold down the volume down the phone should now boot to the bootloader.

Seanie280672 said:
Hold down the power button and the volume down together, the capacitive buttons will flash, don't worry just let them flash and just keep holding down those 2 buttons, when they stop flashing which is about 12 to 15 times, release the power button, but continue to hold down the volume down the phone should now boot to the bootloader.
Click to expand...
Click to collapse
Don't forget it needs to be in a bright lighted room (really!)

gravity02 said:
done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:
Click to expand...
Click to collapse
Your Stuck on the HTC logo because you flashed the firmware and you have a custom rom. The Firmware restored your Stock Recovery and boot.img. Were you able to unlock the bootloader? You need to do that before you try flash anything. It was the Custom recovery and boot.img that caused the problem with unlocking the bootloader.
To make your phone boot to your rom again open the zip file of the rom installed on the phone and extract the boot.img to your fastboot folder. Then flash it with fastboot
Code:
fastboot flash boot boot.img
or just flash your rom again or any compatible rom :good:
P.S for the record when you post you should be quoting my last post or mention me like this @Danny201281 Then I will get a notification and you will get a faster response :good:

i'm currently in fastboot and there doesn't seem to be any change even after flashing the firmware.
i'm still s-off.
tried unlocking the bootloader again and it still remains locked. should i retry flashing the firmware?

gravity02 said:
i'm currently in fastboot and there doesn't seem to be any change even after flashing the firmware.
i'm still s-off.
tried unlocking the bootloader again and it still remains locked. should i retry flashing the firmware?
Click to expand...
Click to collapse
That is weird, are there any files on the device you need to keep? I'm running out of ideas here but you could try factory reset from the stock recovery but i'm not sure it will help. After that the only other thing I can suggest is flashing a full RUU.
Stock recovery factory reset instructions
Select recovery from the bootloader menu. The screen will turn black for a while and then display an image of a phone with red exclamation. Don't worry that's normal. Hold Volume up and press the power button to reveal the stock recovery menu. You will also see some errors about failed to mount sdcard that's also normal in Stock Recovery.
Select Factory Reset from the recovery menu. :good:
In the mean time i'll check out your options for RUU
---------- Post added at 10:44 AM ---------- Previous post was at 10:30 AM ----------
Danny201281 said:
That is weird, are there any files on the device you need to keep? I'm running out of ideas here but you could try factory reset from the stock recovery but i'm not sure it will help. After that the only other thing I can suggest is flashing a full RUU.
Stock recovery factory reset instructions
Select recovery from the bootloader menu. The screen will turn black for a while and then display an image of a phone with red exclamation. Don't worry that's normal. Hold Volume up and press the power button to reveal the stock recovery menu. You will also see some errors about failed to mount sdcard that's also normal in Stock Recovery.
Select Factory Reset from the recovery menu. :good:
In the mean time i'll check out your options for RUU
Click to expand...
Click to collapse
Ok it seems your in luck. There's plenty of RUU's for your T-Mobile device. Look here http://forum.xda-developers.com/showthread.php?t=2375223 and download this T-Mobile HTC One RUU 1.27.531.11
Simple to use just connect fastboot usb in the bootloader and launch the ruu on your pc. This will also wipe your device and return you to Stock.

@Danny201281, i'll download the RUU but will it be possible to flash twrp recovery and restore a backup of the ROM I made so?
won't that bring the phone back to life?

gravity02 said:
@Danny201281, i'll download the RUU but will it be possible to flash twrp recovery and restore a backup of the ROM I made so?
won't that bring the phone back to life?
Click to expand...
Click to collapse
You can't flash recovery while the bootloader is locked not even with s-off.
You could open the firmware zip you flashed and replace the recovery and boot.img with twrp and the boot.img of your Rom. Then flash the firmware zip. The phone should then boot up no problem. And you'll have the custom recovery back. If you want you can send me the boot.img or a link to the Rom on your phone and I can make the zip for you
Can I ask why you locked it in the first place? There's really no need to lock or relock when the device is s-off.
It's starting to look more like a hardware problem though. As I say normally it's some customization in the firmware that causes the problem. But with non of the methods working even with stock firmware it seems like the bootloader is not excepting any unlock instruction.

@ Danny201281, I replaced the stock recovery in the firmware.zip with twrp and flashed the firmware and was able to boot into twrp. I then copied a nandroid backup I made previously into the phone and restored it and the phone booted up properly.
how do I extract the boot.IMG from the nandroid?
thanks for your help so far

Help please. Phone started boot looping

Hi guys,
A few days ago my phone started crashing after bout 10 seconds of getting to the android home screen. It literally didn't stop so i thought it might be smart to do a factory restore. That wiped everything but the boot/crashes still occurred. Now i'm stuck and don't know what to do. All the videos i've watched don't seem to match up with my issue and the fixes don't work. I've uploaded a video to show you what is happening.
I would be extremely grateful for any help or advice
With thanks
James

The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions. That will allow you to flash a custom recovery, such as TWRP. To flash that recovery after unlocking your bootloader, make sure you are in Fastboot and in the fastboot prompt on your PC/Mac type fastboot flash recovery recovery-name.img. From there, you can look around at the custom roms on this forum and see if anything suits you. If you prefer stock android then there are Lollipop and a few Marshmallow builds, if you prefer Sense 6/7 there's some builds for that as well. I'm going to be leaving and busy here for about 2-3 hours but when I get back if you need more assistance feel free to let me know on here.

jamesdf5 said:
Hi guys,
A few days ago my phone started crashing after bout 10 seconds of getting to the android home screen. It literally didn't stop so i thought it might be smart to do a factory restore. That wiped everything but the boot/crashes still occurred. Now i'm stuck and don't know what to do. All the videos i've watched don't seem to match up with my issue and the fixes don't work. I've uploaded a video to show you what is happening.
I would be extremely grateful for any help or advice
With thanks
James
Click to expand...
Click to collapse
It looks like a recovery issue. Can you get it to bootloader menu? Hold power + vol down till it enters bootloader
dey tuuk ur juurbs

fireball0093 said:
The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions. That will allow you to flash a custom recovery, such as TWRP. To flash that recovery after unlocking your bootloader, make sure you are in Fastboot and in the fastboot prompt on your PC/Mac type fastboot flash recovery recovery-name.img. From there, you can look around at the custom roms on this forum and see if anything suits you. If you prefer stock android then there are Lollipop and a few Marshmallow builds, if you prefer Sense 6/7 there's some builds for that as well. I'm going to be leaving and busy here for about 2-3 hours but when I get back if you need more assistance feel free to let me know on here.
Click to expand...
Click to collapse
Hi,
Thanks for the reply
The first thing i tried was unlocking the bootloader but my PC couldnt see the phone. I'll have to try again later and let you know

donkeykong1 said:
It looks like a recovery issue. Can you get it to bootloader menu? Hold power + vol down till it enters bootloader
dey tuuk ur juurbs
Click to expand...
Click to collapse
Thanks for replying. Yes i can get into bootloader

jamesdf5 said:
Thanks for replying. Yes i can get into bootloader
Click to expand...
Click to collapse
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
dey tuuk ur juurbs

fireball0093 said:
The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions.
Click to expand...
Click to collapse
His bootloader his already unlocked see video @ 3:00, and that unlocked bootloader most likely caused the ota update to fail an so the bootloop (see video @ 0:49) (unlocking the bootloader = wipes /data/preload = ota will fail).
donkeykong1 said:
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
Click to expand...
Click to collapse
Yep see video @ 3:00. So its the 1.44 + Win 8/10 incompatibility issue.
jamesdf5 said:
Hi,
The first thing i tried was unlocking the bootloader but my PC couldnt see the phone. I'll have to try again later and let you know
Click to expand...
Click to collapse
Its already unlocked as you can see from your bootloader screen ***UNLOCKED***
I guess you are using a Windows 8 or 10 PC? This is the reason why your PC doesn't detect your phone. It still running the old 1.44 Hboot version which isn't compatible with Win 8/10 for fastboot commands. Btw USB debugging on/off doesn't matters for using fastboot commands in bootloader or for using adb commands when in a custom recovery, its only needed to use adb commands from a booted rom. The simplest solution would be to get your hands on a Win 7 PC, install adb/fastboot and the drivers, and post the output of "fastboot getvar all" (don't post your imei / sn). Your phone is running a pretty old version, I'm sure we'll be able to find a RUU or a Guru reset rom to restore your phone back to stock.

alray said:
His bootloader his already unlocked see video @ 3:00, and that unlocked bootloader most likely caused the ota update to fail an so the bootloop (see video @ 0:49) (unlocking the bootloader = wipes /data/preload = ota will fail).
Yep see video @ 3:00. So its the 1.44 + Win 8/10 incompatibility issue.
Its already unlocked as you can see from your bootloader screen ***UNLOCKED***
I guess you are using a Windows 8 or 10 PC? This is the reason why your PC doesn't detect your phone. It still running the old 1.44 Hboot version which isn't compatible with Win 8/10 for fastboot commands. Btw USB debugging on/off doesn't matters for using fastboot commands in bootloader or for using adb commands when in a custom recovery, its only needed to use adb commands from a booted rom. The simplest solution would be to get your hands on a Win 7 PC, install adb/fastboot and the drivers, and post the output of "fastboot getvar all" (don't post your imei / sn). Your phone is running a pretty old version, I'm sure we'll be able to find a RUU or a Guru reset rom to restore your phone back to stock.
Click to expand...
Click to collapse
Thanks for your reply. Really helpful. I am using windows 10 but thankfully I have a windows 7 laptop that is stuck in an update loop . So i'm now using the laptop and have unlocked the bootloader. (I didnt have an unlocked bootloader, the image on the video i uploaded was just a screenshot of an example).
So now i'm at the unlocked bootloader stage. I now need to know what order to do things next. The phone is still bootlooping.
Using the laptop the bootloop screen now shows USB
Thanks again

donkeykong1 said:
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
dey tuuk ur juurbs
Click to expand...
Click to collapse
It does now i've unlocked it. yes

jamesdf5 said:
It does now i've unlocked it. yes
Click to expand...
Click to collapse
Post a fastboot getvar all so we can tell you which RUU is for your phone. Be sure to delete your IMEI and serial no from the output before you post it
dey tuuk ur juurbs

donkeykong1 said:
Post a fastboot getvar all so we can tell you which RUU is for your phone. Be sure to delete your IMEI and serial no from the output before you post it
dey tuuk ur juurbs
Click to expand...
Click to collapse
Okie dokie thanks
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(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

jamesdf5 said:
Okie dokie thanks
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(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
Click to expand...
Click to collapse
Latest firmware and s-on... Not good... There is no signed firmware for your phone, but there is a way to trick your phone to think it's on older firmware. @alray knows everything about that, so we'll have to wait for him to see this
dey tuuk ur juurbs

donkeykong1 said:
Latest firmware and s-on... Not good... There is no signed firmware for your phone, but there is a way to trick your phone to think it's on older firmware. @alray knows everything about that, so we'll have to wait for him to see this
dey tuuk ur juurbs
Click to expand...
Click to collapse
ok thank you :good:

jamesdf5 said:
Thanks for your reply. Really helpful. I am using windows 10 but thankfully I have a windows 7 laptop that is stuck in an update loop . So i'm now using the laptop and have unlocked the bootloader. (I didnt have an unlocked bootloader, the image on the video i uploaded was just a screenshot of an example).
So now i'm at the unlocked bootloader stage. I now need to know what order to do things next. The phone is still bootlooping.
Using the laptop the bootloop screen now shows USB
Thanks again
Click to expand...
Click to collapse
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
jamesdf5 said:
Okie dokie thanks
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(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
Click to expand...
Click to collapse
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.

alray said:
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
Click to expand...
Click to collapse
Yes it was my video but the bootloader image was a screenshot i found on Google cos my phone wasn't getting me to bootloader so I wanted to refer to it.
alray said:
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.
Click to expand...
Click to collapse
Fab thanks i'll give this a go tomorrow. I'll let you know how i get on
Thanks
James

jamesdf5 said:
Yes it was my video but the bootloader image was a screenshot i found on Google cos my phone wasn't getting me to bootloader so I wanted to refer to it.
Fab thanks i'll give this a go tomorrow. I'll let you know how i get on
Thanks
James
Click to expand...
Click to collapse
PS definitely not recognised on my Windows 10. Won't see it at all.

jamesdf5 said:
PS definitely not recognised on my Windows 10. Won't see it at all.
Click to expand...
Click to collapse
Strange, keep using your w7 pc for now. Maybe a driver problem, or maybe you are using an usb 3.0 port instead of a 2.0?

alray said:
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.
Click to expand...
Click to collapse
Ok i got it working on my Windows 10.
I've just managed to flash the recovery image, cleared cache and rest. Thank you for the amazingly easy instructions.
However it won't go into the recovery it just keeps boot looping to the HTC logo.
When i select recovery i see the HTC logo and words that say entering recovery but then it restarts and continues boot looping.
Interestingly my bootloader now says **Tampered**. I'm guessing that is normal.
I appreciate all your time and effort trying to help me.
Regards
James

jamesdf5 said:
Ok i got it working on my Windows 10.
I've just managed to flash the recovery image, cleared cache and rest. Thank you for the amazingly easy instructions.
However it won't go into the recovery it just keeps boot looping to the HTC logo.
When i select recovery i see the HTC logo and words that say entering recovery but then it restarts and continues boot looping.
Interestingly my bootloader now says **Tampered**. I'm guessing that is normal.
I appreciate all your time and effort trying to help me.
Regards
James
Click to expand...
Click to collapse
Yes tampered is normal after flashing custom software. Try the old twrp 2.6.3.3, it sometime doing miracles. Mdmower's versions of TWRP are also known to boot when some other official twrp versions can't.
https://dl.twrp.me/m7/
http://android.cmphys.com/twrp-m7/
Btw did you erased the cache and rebooted the bootloader before attempting to boot in recovery ("fastboot erase cache" then "fastboot reboot-bootloader"? Its the main cause of non-booting recovery, just to be sure.

alray said:
Yes tampered is normal after flashing custom software. Try the old twrp 2.6.3.3, it sometime doing miracles. Mdmower's versions of TWRP are also known to boot when some other official twrp versions can't.
https://dl.twrp.me/m7/
http://android.cmphys.com/twrp-m7/
Btw did you erased the cache and rebooted the bootloader before attempting to boot in recovery ("fastboot erase cache" then "fastboot reboot-bootloader"? Its the main cause of non-booting recovery, just to be sure.
Click to expand...
Click to collapse
Oh dear. I have to confess i accidentally restarted the phone after i flashed it without erasing cache. :crying::crying: I then went back and flashed again and erased as you said in the instructions.
I have have tried the older version on twrp. No luck. I'm guessing i ballsed it up first time! Sorry