Hi Everyone.
Recently I factory reset my HTC One M8 and now It hangs on logo screen when powered on. sometimes after a hard reset using vol+ and power it loads past logo screen to android starting, optimizing app, but hangs after optimizing apps.
cant get access to recovery mode phone wont load bootloader.
ThomasHoey said:
cant get access to recovery mode phone wont load bootloader.
Click to expand...
Click to collapse
Hold vol up and power on, until the screen goes dark (may take a minute or so). While the screen is dark, and before the white logo screen comes on, let go of the buttons and only hold vol down. Don't let go of vol down, until the bootloader screen appears.
This virtually always works. So if you can't get into bootloader, try again. Failure to get into bootloader this way, is usually due to not pressing vol down fast enough, or letting go too early.
From there, if you need more help, do fastboot getvar all, and post the results (delete IMEI and serial number) so we can get more info about the device.
Thank you for the reply, will try this and get back to you.
thanks again
redpoint73 said:
Hold vol up and power on, until the screen goes dark (may take a minute or so). While the screen is dark, and before the white logo screen comes on, let go of the buttons and only hold vol down. Don't let go of vol down, until the bootloader screen appears.
This virtually always works. So if you can't get into bootloader, try again. Failure to get into bootloader this way, is usually due to not pressing vol down fast enough, or letting go too early.
From there, if you need more help, do fastboot getvar all, and post the results (delete IMEI and serial number) so we can get more info about the device.
Click to expand...
Click to collapse
I have a question regarding this method
do I hold vol+ and power and immediately let go when screen goes black?
if i hold them for a few seconds longer then the phone vibrates
ThomasHoey said:
I have a question regarding this method
do I hold vol+ and power and immediately let go when screen goes black?
if i hold them for a few seconds longer then the phone vibrates
Click to expand...
Click to collapse
You have about 3 seconds while the screen is dark to let go of vol up, and start holding vol down. If you the white HTC logo screen appears, its too late to start pressing vol down. If you had a working OS, pressing vol down "too late" during the logo screen initiates safe mode. But in your case, since you can't boot OS, nothing happens and it stays on the logo screen.
Really, its only sliding your finger down from vol up, to vol down, that matters. It actually doesn't matter if you continue to hold the power button or not.
redpoint73 said:
Hold vol up and power on, until the screen goes dark (may take a minute or so). While the screen is dark, and before the white logo screen comes on, let go of the buttons and only hold vol down. Don't let go of vol down, until the bootloader screen appears.
This virtually always works. So if you can't get into bootloader, try again. Failure to get into bootloader this way, is usually due to not pressing vol down fast enough, or letting go too early.
From there, if you need more help, do fastboot getvar all, and post the results (delete IMEI and serial number) so we can get more info about the device.[/QUOTE
redpoint73 said:
You have about 3 seconds while the screen is dark to let go of vol up, and start holding vol down. If you the white HTC logo screen appears, its too late to start pressing vol down. If you had a working OS, pressing vol down "too late" during the logo screen initiates safe mode. But in your case, since you can't boot OS, nothing happens and it stays on the logo screen.
Really, its only sliding your finger down from vol up, to vol down, that matters. It actually doesn't matter if you continue to hold the power button or not.
Click to expand...
Click to collapse
still no luck getting bootloader to load
Click to expand...
Click to collapse
ThomasHoey said:
redpoint73 said:
Hold vol up and power on, until the screen goes dark (may take a minute or so). While the screen is dark, and before the white logo screen comes on, let go of the buttons and only hold vol down. Don't let go of vol down, until the bootloader screen appears.
This virtually always works. So if you can't get into bootloader, try again. Failure to get into bootloader this way, is usually due to not pressing vol down fast enough, or letting go too early.
From there, if you need more help, do fastboot getvar all, and post the results (delete IMEI and serial number) so we can get more info about the device.[/QUOTE
still no luck getting bootloader to load
Click to expand...
Click to collapse
So I have managed to find the problem. When the phone loads the bootloader/fastboot mode I cannot see it as the screen is blank but I am able to use the vol keys to highlight and power to select an option problem being I dont know what I'm selecting or if im even in bootloader or Fastboot mode.
Click to expand...
Click to collapse
ThomasHoey said:
ThomasHoey said:
So I have managed to find the problem. When the phone loads the bootloader/fastboot mode I cannot see it as the screen is blank but I am able to use the vol keys to highlight and power to select an option
Click to expand...
Click to collapse
Gotcha, I've seen this problem (black screen in bootloader) reported here once or twice. But its pretty rare (which is one reason I said the button combo "virtually" always works).
ThomasHoey said:
problem being I dont know what I'm selecting or if im even in bootloader or Fastboot mode.
Click to expand...
Click to collapse
I haven't seen any solution for this, aside from just guessing, and trial and error.
If you M8 version has the RUU in zip format, you can rename it to 0P6BIMG.zip then put it on an SD card, and boot into bootloader, and it should install automatically. Although an RUU won't install if the bootloader is unlocked and phone is s-on.
Click to expand...
Click to collapse
redpoint73 said:
ThomasHoey said:
Gotcha, I've seen this problem (black screen in bootloader) reported here once or twice. But its pretty rare (which is one reason I said the button combo "virtually" always works).
I haven't seen any solution for this, aside from just guessing, and trial and error.
Yeah thats what I have been doing. I managed to get it to go into recovery, cleared cache and then cleared data and factory reset, still stuck in bootloop.
If you M8 version has the RUU in zip format, you can rename it to 0P6BIMG.zip then put it on an SD card, and boot into bootloader, and it should install automatically. Although an RUU won't install if the bootloader is unlocked and phone is s-on.
Click to expand...
Click to collapse
Do you know where I can get a Stock ROM to do RUU. I haven't modded my phone at all so would the bootloader not be locked and S-off by default.
again thanks for taking time to reply.
Click to expand...
Click to collapse
ThomasHoey said:
Do you know where I can get a Stock ROM to do RUU. I haven't modded my phone at all so would the bootloader not be locked and S-off by default.
Click to expand...
Click to collapse
If the phone is not modded, it would be bootloader locked, which is what you want in order to RUU. Probably also s-on (although s-off from the factory is rare, but we have seen it). But s-on or s-off doesn't affect your ability to RUU (as long as the bootloader is locked).
Which RUU depends on the version (CID) of your phone. If you don't know the CID, you'll need to try to get into fastboot, and do fastboot getvar all, and post the results here (delete IMEI and serial number before posting).
redpoint73 said:
ThomasHoey said:
Which RUU depends on the version (CID) of your phone. If you don't know the CID, you'll need to try to get into fastboot, and do fastboot getvar all, and post the results here (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
I dont know the CID, How would I get into fastboot if I cant see the screen. I take it I would yous the CMD on my laptop to run the command.
I have already got ADB and Fastboot on my laptop.
Click to expand...
Click to collapse
ThomasHoey said:
How would I get into fastboot if I cant see the screen.
Click to expand...
Click to collapse
Yes, I realize that. That is why I typed: try to get into fastboot
With no OS, you'll need fastboot to determine the needed info.
Your other option is to read the model number off the back of the phone. But this isn't always reliable (better to verify with fastboot getvar) as we've seen a lot of M8 phones with the back cover swapped to remove carrier branding.
But if you obtained the phone from a reputable source, such as your carrier, it likely won't have had its back cover changed. But you haven't told us anything about the phone. Is it carrier branded, what version you think it is, where you bought it from, etc.
ThomasHoey said:
I take it I would yous the CMD on my laptop to run the command.
I have already got ADB and Fastboot on my laptop.
Click to expand...
Click to collapse
That is correct, in CMD window, change directory to whatever folder you have fastboot.exe located. Windows shortcut here is to find fastboot.exe, open that folder, then hover your cursor inside that folder, press Shift+right mouse, and select "Open command window here" from the popup menu.
Then in command, simply type: fastboot getvar all
Or you can check the phone is properly in fastboot mode with the command: fastboot devices
The phone's serial number should be returned, if the phone is properly in fastboot mode. No serial number (no devices listed) or device indicated as "offline" means you don't have a proper fastboot connection. If everything else is okay (drivers, cable, etc.), but phone is not in fastboot mode, the likely result is the phone's serial number, but shown as "offline".
Again, don't post your IMEI or serial number to the forums.
redpoint73 said:
Yes, I realize that. That is why I typed: try to get into fastboot]
But if you obtained the phone from a reputable source, such as your carrier, it likely won't have had its back cover changed. But you haven't told us anything about the phone. Is it carrier branded, what version you think it is, where you bought it from, etc.
The phone is on contract to 02, purchased fro the 02 store.
That is correct, in CMD window, change directory to whatever folder you have fastboot.exe located. Windows shortcut here is to find fastboot.exe, open that folder, then hover your cursor inside that folder, press Shift+right mouse, and select "Open command window here" from the popup menu.
Then in command, simply type: fastboot getvar all
Or you can check the phone is properly in fastboot mode with the command: fastboot devices
The phone's serial number should be returned, if the phone is properly in fastboot mode. No serial number (no devices listed) or device indicated as "offline" means you don't have a proper fastboot connection. If everything else is okay (drivers, cable, etc.), but phone is not in fastboot mode, the likely result is the phone's serial number, but shown as "offline".
I have tried all the modes in bootloader.
1 when in bootloader if I just press power button to select first option all the phone does is stay in a continual loop of vibrates with a 2 sec pause in-between each vibrate.
2 Press vol- down then power then I see another screen with a small phone logo with a green circle going round with an green arrow pointing down. if i press vol+ power or vol- power the I get power icon with a red line through it.
3 press vol- 2 times then it takes me to screen with red exclamation mark and circle, then a press vol+ and power takes me to recovery.
in recovery it gives me the option to update via ADB would this be an option. if so could you instruct me on how to do so if you know
Thank you so much for taking the time to reply
Click to expand...
Click to collapse
ThomasHoey said:
I have tried all the modes in bootloader.
1 when in bootloader if I just press power button to select first option all the phone does is stay in a continual loop of vibrates with a 2 sec pause in-between each vibrate.
2 Press vol- down then power then I see another screen with a small phone logo with a green circle going round with an green arrow pointing down. if i press vol+ power or vol- power the I get power icon with a red line through it.
3 press vol- 2 times then it takes me to screen with red exclamation mark and circle, then a press vol+ and power takes me to recovery.
Click to expand...
Click to collapse
What if you go into bootloader, and press nothing (any response to fastboot devices)? Fastboot mode is often the default bootloader mode, if a USB cable is connected.
redpoint73 said:
What if you go into bootloader, and press nothing (any response to fastboot devices)? Fastboot mode is often the default bootloader mode, if a USB cable is connected.
Click to expand...
Click to collapse
I never thought of that. will try that and give it a go. will get back to you.
thanks again
redpoint73 said:
What if you go into bootloader, and press nothing (any response to fastboot devices)? Fastboot mode is often the default bootloader mode, if a USB cable is connected.
Click to expand...
Click to collapse
ok so I managed to get it into fastboot with your last instructions here is the info from fastboot getvar all
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\T.Hoey>fastboot devices
SH43MWM12276 fastboot
C:\Users\T.Hoey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH43MWM12276
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.139s
You'll find the RUU for your version here: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Plus instructions on that link on how to flash using htc_fastboot. Note, that you need to use the htc_fastboot.exe provided in that thread, the RUU probably won't run with the "generic" fastboot you are presently using.
Or you can rename the RUU file to 0P6BIMG.zip (first character is a zero, not the letter "O"), put it on an SD card, insert into the phone, and reboot into bootloader, and it will install automatically.
The RUU will install a completely new factory stock image, which will hopefully get you booted into Android OS, and fix the black screen on hboot issue.
redpoint73 said:
You'll find the RUU for your version here: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Plus instructions on that link on how to flash using htc_fastboot. Note, that you need to use the htc_fastboot.exe provided in that thread, the RUU probably won't run with the "generic" fastboot you are presently using.
Or you can rename the RUU file to 0P6BIMG.zip (first character is a zero, not the letter "O"), put it on an SD card, insert into the phone, and reboot into bootloader, and it will install automatically.
The RUU will install a completely new factory stock image, which will hopefully get you booted into Android OS, and fix the black screen on hboot issue.
Click to expand...
Click to collapse
Thamk you so much for ll your help. will give this a go and get back to you. here is hoping
View attachment 3726366
ThomasHoey said:
Thank you so much for ll your help. will give this a go and get back to you. here is hoping
Click to expand...
Click to collapse
So I have tried this option but when I enter the third command had to change it from htc_fastboot flash zip RUU.zip to htc_fastboot.exe flash zip 0P6BIMG.zip for it to run.
got an failed mesage. (pic attached)
now its hung on sending zip
pic attached
ThomasHoey said:
So I have tried this option but when I enter the third command had to change it from htc_fastboot flash zip RUU.zip to htc_fastboot.exe flash zip 0P6BIMG.zip for it to run.
Click to expand...
Click to collapse
It clearly says in the instructions for this method: Rename the RUU zip to RUU.zip
In any case, what you did also works, of course. The point is you are telling fastboot to flash the zip named in the command. You can rename the zip file whatever you want, and still flash it:
htc_fastboot flash zip whatever.zip
The file name 0P6BIMG.zip is only required if you use the SD card install method.
If the RUU stopped at the "flush image again immediately" error, just flash it again (this is a common and normal result).
Related
Hello,
My device was S-OFF and rooted and was running MIUI-AU ROM and decided to try and revert it to a Stock ROM bog standard etc and ran a TMO RUU, which failed with an error 140.
Problem is I have a blank screen now, with battery out I have tried getting into Fastboot (back button and power) which seems to work as I can run the Android Flasher to try and flash the stock boot from Alpharev, which detects the phone but fails and I know it is there since when you press the power button it vibrates from the Fast boot.
I have tried flashing recoveries and HBoots with the android flasher but am getting nowhere. I do not have a gold card and have tried to set up adb which can't find the device either.
I am hoping some of the incredibly clever people here can help me!
Thanks in advance,
Graham
I did manage to use fastboot commander to get the following, but still have the same issue:-
SPL/hboot version: 0.80.0000.
Radio version: 5.17.05.08.
Main software version: 2.12.110.2.
cid: t-mob005.
cpld: none.
product: bravo.
mid: pb9920000.
security: on.
build-mode: ship.
Hello,
My device was S-OFF and rooted and was running MIUI-AU ROM and decided to try and revert it to a Stock ROM bog standard etc and ran a TMO RUU, which failed with an error 140.
Problem is I have a blank screen now, with battery out I have tried getting into Fastboot (back button and power) which seems to work as I can run the Android Flasher to try and flash the stock boot from Alpharev, which detects the phone but fails and I know it is there since when you press the power button it vibrates from the Fast boot.
I have tried flashing recoveries and HBoots with the android flasher but am getting nowhere. I do not have a gold card and have tried to set up adb which can't find the device either.
I am hoping some of the incredibly clever people here can help me!
Thanks in advance,
Graham
I did manage to use fastboot commander to get the following, but still have the same issue:-
SPL/hboot version: 0.80.0000.
Radio version: 5.17.05.08.
Main software version: 2.12.110.2.
cid: t-mob005.
cpld: none.
product: bravo.
mid: pb9920000.
security: on.
build-mode: ship.[/QUOTE]
see this http://forum.xda-developers.com/showthread.php?t=1363855
this must solve your problem...
If not PM me .. Ill see another option...
and you DON't NEED a GLODCARD for this
It cannot find the device when I get the adb devices, the only way i seem to be able to get adb to work is when I somehow press a combination of buttons to get to recovery. So i end up with a set of numbers in adb followed by the words recovery.
Thanks again,
Graham
Already checked bortak's troubleshooting guide?
I have....Really odd, I have tried the WWE RUU and the T Mobile one, the WWE says it is the wrong Customer ID and the T Mobile one says it is the wrong Bootloader version...
greeham said:
It cannot find the device when I get the adb devices, the only way i seem to be able to get adb to work is when I somehow press a combination of buttons to get to recovery. So i end up with a set of numbers in adb followed by the words recovery.
Thanks again,
Graham
Click to expand...
Click to collapse
you may not have enabled adb at your PC...
BTW there will not be any device list... The message will be like.."List of adb devices attached"
Than you folow the procedure..
enter fastboot commands..
Hi There,
That's exactly what it says when i type adb devices. I have tried a colleagues Desire and adb works fine with his, so I presume there is something else going on?
Thanks,
Graham
I did get into adb when the device is in Recovery but when I try and run fastboot it says '/sbin/sh: fastboot: not found'
greeham said:
Hi There,
That's exactly what it says when i type adb devices. I have tried a colleagues Desire and adb works fine with his, so I presume there is something else going on?
Thanks,
Graham
I did get into adb when the device is in Recovery but when I try and run fastboot it says '/sbin/sh: fastboot: not found'
Click to expand...
Click to collapse
mAY BE YOu have not follwed the whole procedure I wrote in the POST...
Right now the tools folder is missing fastboot.exe file..CHECK it..
2.Download these(http://www.multiupload.com/5ZAPJTFXMM) and put them into C drive in to "C/android sdk/tools" after UNZIPING by 7ZIP...
Hi,
I did follow exactly what you had said and fastboot.exe was in the tools folder but the error is the same...
Thanks,
Graham
greeham said:
Hi,
I did follow exactly what you had said and fastboot.exe was in the tools folder but the error is the same...
Thanks,
Graham
Click to expand...
Click to collapse
Tell me thewhole procedure with EXACT commands..you followed...
Remove battery and place back.
press back and then Power button, phone vibrates.
Plug USB in and then open CMD prompt and attempt adb devices.
Says 'List of adb devices attached' and nothing is listed. If you try anything else it doesn't work since doesn't have device to 'see'.
If I remove battery and place back and power on whilst holding down volume, it vibrates.
I then press volume down button and power button.
if i then adb devices it says '123456789ABCDEF recovery'
I then can adb shell but always has similar errors when trying anything about '/sbin/sh'
Does that help at all?
Thanks again,
Graham
greeham said:
Remove battery and place back.
press back and then Power button, phone vibrates.
Plug USB in and then open CMD prompt and attempt adb devices.
Says 'List of adb devices attached' and nothing is listed. If you try anything else it doesn't work since doesn't have device to 'see'.
If I remove battery and place back and power on whilst holding down volume, it vibrates.
I then press volume down button and power button.
if i then adb devices it says '123456789ABCDEF recovery'
I then can adb shell but always has similar errors when trying anything about '/sbin/sh'
Does that help at all?
Thanks again,
Graham
Click to expand...
Click to collapse
It is not possible that the the phone will not except any command on fastboot...
What are you seeing on your phone screen....oh....you'r missing a thing...
to got to the fastboot mode on your phone..
reboot
press BACK+POWER button..
you currently using volume down+power.. that ends up at the splash screen.. NOT fastboot-Bootloader..
Try this...
The screen is completely blank.
I am pressing back and the power button, I mentioned the volume buttons as I tried that as well.
So, neither works for the fastboot command.
greeham said:
The screen is completely blank.
I am pressing back and the power button, I mentioned the volume buttons as I tried that as well.
So, neither works for the fastboot command.
Click to expand...
Click to collapse
I don't know waht exactly is happening with you... I've never encountered this problem when NOT having anything on screen whille pressing BACK+Power Button...
If this does't solves the problem..
Download the official ruu .. flash it and got to htc...
I am still feeling that you are missing something...may be...
Try this again...if you feel this can help..
I tried this procedure couple of times ... but never got a BLANK SCREEN...
Have tried both the TMO RUU and get a Bootloader is wrong version error and the WWE tells me that the Customer ID is wrong.
greeham said:
Have tried both the TMO RUU and get a Bootloader is wrong version error and the WWE tells me that the Customer ID is wrong.
Click to expand...
Click to collapse
your signature is showing that the PHONE is S-ON....
For all I've written you must have root access...
Have you tried REVOLUTIONARY.IO also for getting S-OFF this time????
Hi greet to all,
I bought HTC Wildfire before 3 days it was working perfect just i installed a theme changer application named "SPD Shell" then i restarted my wildfire it came to boot screen and volume keys and power button are not working and i am unable to select any of the option " BOOTLOADER , REBOOT, REBOOT BOOTLOADER, POWER DOWN ". I removed battery then put it back and hold the down volume key and power button it came to HBOOT screen but there too i am unable to select any of the options. My all keys are perfect and not defected. I have so many times flashed roms which upgraded my HBOOT to different version i.e 1.01.0001, 1.01.0002, 0.08.0008 and some thing like this but after all my htc not loaded its OS. I tried to install revolutionary & unrevoked but these software demand to connect phone in charge only mode with pc but i can't load OS so how can i connect my phone in charge only mode. Following are the important details.
Kindly Help me.
My boot screen values currently are:
BUZZ PVT SHIP S-OFF
HBOOT-1.01.0001
MICROP - 0622
TOUCH PANEL - ATMEL224_20aa
RADIO-3.35.20.10
Nov 17 2010, 12:08:53
and " Fastboot getvar all " values are:
C:\android\fastboot>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.01.0001
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.22.405.1
INFOserialno: HIDE BY ME (for security purpose)
INFOimei: HIDE BY ME (for security purpose)
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC49*****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3750mV
INFOpartition-layout: HTC
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-72b8c698
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Syed_Jawad said:
i installed a theme changer application named "SPD Shell"
Click to expand...
Click to collapse
you mean "SPB Shell 3D" from the market? Says "incompatible with device" - so this might cause some troubles of course...
I removed battery then put it back and hold the down volume key and power button it came to HBOOT screen but there too i am unable to select any of the options
Click to expand...
Click to collapse
What exactly does that mean? You can't select "Recovery" from the Fastboot menu? Can't move between the options with Vol up/down keys? - Bear in mind: from the Fastboot menu you *select* an option by pressing the power button while in Recovery (Clockworkmod) you do it with the trackball...
eventcom said:
you mean "SPB Shell 3D" from the market? Says "incompatible with device" - so this might cause some troubles of course...
What exactly does that mean? You can't select "Recovery" from the Fastboot menu? Can't move between the options with Vol up/down keys? - Bear in mind: from the Fastboot menu you *select* an option by pressing the power button while in Recovery (Clockworkmod) you do it with the trackball...
Click to expand...
Click to collapse
No i downloaded SPB Shell from another site and it may be incompatible with my HTC Wildfire but i installed it. Yeah i can't select any option from the Fastboot menu, Power and both volume key do not work in fastboot and hboot menu. Recovery option is not available because i have not installed (Clockworkmod Recovery Application) and i can't install it because to install clockworkmod recovery software the mobile is to be attached with pc in charging mod only but my OS is not booting so i cant connect my phone with pc in charg only mode. Please have a look in the bootlader details ganied by fastboot getvar command, there may be some clue about my problem. thnx
I'm pretty sure spb shell didn't cause this, at the end of the day its just a launcher which is very much incompatible with a wildfire. In my eyes the only damage installing an incompatible launcher can cause would be if you have ticked the default setting and rebooted because obviously after the restart it won't work and you would be unable to change the default. It cannot harm your devices hardware buttons especially when the system isn't loaded.
Why you don't have a recovery loaded I just don't understand, you can still use fast boot to flash cwm and then adb command "adb reboot recovery" to enter recovery and try to flash it if the buttons still don't work try an ruu.
Why you don't have a recovery loaded I just don't understand, you can still use fast boot to flash cwm and then adb command "adb reboot recovery" to enter recovery and try to flash it if the buttons still don't work try an ruu.[/QUOTE]
Listen:
1. My phone is in off state i press power button it turns ON and stuck on Fastboot Screen & Volume and power keys not working on this screen so i cant not select any of the option. Fastboot screen values are as under:
BUZZ PVT SHIP S-OFF
HBOOT-1.01.0001
MICROP-0622
TOUCH PANEL-ATMEL224_20aa
RADIO-3.35.20.10
Nov 17 2010, 12:08:53
Fastboot
<Volume Up> to previous item
<vol down> to next item
<power> to select item
Bootloader
Reboot
Reboot Bootloader
Power Down
2. Then I remove battery and put it back in the phone then hold down volume key + power button so it turns ON and stuck on the HBOOT screen and still volume and power button not working on this screen. The values of HBOOT screen are as under:
BUZZ PVT SHIP S-OFF
HBOOT-1.01.0001
MICROP-0622
TOUCH PANEL-ATMEL224_20aa
RADIO-3.35.20.10
Nov 17 2010, 12:08:53
HBOOT
<Volume Up> to previous item
<vol down> to next item
<power> to select item
Fastboot
Recovery
Clear Storage
Simlock
Power Down
3. I have tried to connect phone with pc. I turned on phone so it stuck on the Fastboot screen then i plugged usb cable in the phone and run the exe file from computer "RUU_Buzz_Froyo_HTCCN_CHS_2.10.1400.3_Radio_13.53.55.24H_3.35.19.25_release_151119_signed.exe" then installation process started in the computer as well as on the screen of the phone after completion my phone reboots and HTC logo with white background comes and sticks on this screen, I waited about 15 mins but OS didnt start. Then i removed and placed battery so my phone came again on the fastboot screen. I tried to install revolutionary & unrevoked & clockworkmod recovery but these all application required phone to connect with PC in CHARGE ONLY mode but my OS is not starting so i cant connect phone in charge only mode. Only fastboot command is working with the following options " getvar & reboot & devices ". I tried to send file to phone using fastboot command it gave me error [ melformed 1 ]. and adb command is also giving me same response. one more this when i place some files in my SD CARD and place it in my phone and start the phone and comes to hboot menu where my phone scans SD Card for the files " PC49IMG.ZIP PC49IMG.NBH PC49DIAG.ZIP PC49DIAG.NB ". I placed recovery-clockwork-5.0.2.0-buzz.zip file after changing its name to PC49IMG.ZIP in SD Card the booted my phone. My phone scanned PC49IMG.ZIP file but didn't install it.
I hope now everything is clear, and you can help me.........
Try with this PC49IMG.zip
http://www.mediafire.com/?398dklf1uzss5f6
Hopefully that'll work to get recovery, if not I'd try a different ruu next.
In fact you may as well give this a shot too, on your PC click start or the windows orb and type %temp% to open your temp folder, run the ruu and look for some new files appearing in the temp folder. Look through the new folders for a file named rom.zip and drag it to your desktop, this basically contains the whole phones os, bootloader and all. Here you can either rename that zip to PC49IMG.zip and drop it on your SD although it does ask to press volume up to install so that may not work still. You could also try extracting the rom.zip and fastboot flash the files to your phone.
Thanx for your effort. My phone updated from this PC49IMG uploaded by you but after rebooting nothing changed, still same condition. i tried your second advice of rom.zip from temp. I placed rom.zip in my SD CARD after changing its name to PC49IMG.zip then rebooted and installed it but after installation nothing happened my phone came to FASTBOOT screen after reboot.
Did you try adb reboot recovery command?
I'm all out of ideas it seems your boot loader has somehow corrupted I'm pretty sure if you could somehow flash the bootloader or get an ruu to successfully flash it may fix the problem. Only other thing I can think of is a different ruu (eclair ones always seemed to work best for me) if you haven't tried one already.
If you have then maybe its a good excuse for an upgrade....
...
Yes i have tried adb command but it does not work, it says " device not found " because my phone is connected in fastboot screen condition not properly. I think adb required charge only mode from the OS but my OS is not starting. I have installed the following RUU successfully because it's a EXE file so when i run this setup from my computer it identifies my wildfire and install the RUU and it reboots my wildfire after rebooting HTC logo comes with white background but doesn't go ahead and stick on that screen. then i remove battery and place back and turn on again so it comes to fastboot screen.
" RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe "
I don't know how to flash boot loader, waiting for your lead.
Syed_Jawad said:
Thanx for your effort. My phone updated from this PC49IMG uploaded by you but after rebooting nothing changed, still same condition
Click to expand...
Click to collapse
just to make sure: you also still couldn't use vol up/down keys?
Swyped from my HTC Wildfire (Buzz)
Syed_Jawad said:
Yes i have tried adb command but it does not work, it says " device not found " because my phone is connected in fastboot screen condition not properly. I think adb required charge only mode from the OS but my OS is not starting. I have installed the following RUU successfully because it's a EXE file so when i run this setup from my computer it identifies my wildfire and install the RUU and it reboots my wildfire after rebooting HTC logo comes with white background but doesn't go ahead and stick on that screen. then i remove battery and place back and turn on again so it comes to fastboot screen.
" RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe "
I don't know how to flash boot loader, waiting for your lead.
Click to expand...
Click to collapse
Try using fastboot to reboot into the the recovery.
I think the command is just "fastboot reboot recovery"
Sent from my Galaxy Nexus using xda premium
This command is not working giving no any response.
OK try boot the device without the SD card in. Then test and see if the volume buttons work. I have seen an issue similar to this where the SD card was defective and hboot got stuck in a loop when trying to scan it resulting in the buttons appearing not to work.
Sent from my HTC Sensation using xda premium
I have tried without SD card but volume keys not working in fastboot and hboot menu. My Volume key are fine mechanically because i can go hboot menu by holding down volume key + power button.
Syed_Jawad said:
I have tried without SD card but volume keys not working in fastboot and hboot menu. My Volume key are fine mechanically because i can go hboot menu by holding down volume key + power button.
Click to expand...
Click to collapse
That is very strange indeed...
Are you running the stock hboot or the revolutionary one?
Sent from my HTC Sensation using xda premium
heavy_metal_man said:
That is very strange indeed...
Are you running the stock hboot or the revolutionary one?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
yeah - very unlikely hardware nor any useful error messages - if flashing PC49IMG.zip files does work there might be hope, though
I am using Stock Hboot not revolutionary. and i have tried PC49IMG.ZIP, my phone updates from this file but after restarting mobile nothing changes. I have only used my phone only one day it's very painful for me.
Syed_Jawad said:
I am using Stock Hboot not revolutionary. and i have tried PC49IMG.ZIP, my phone updates from this file but after restarting mobile nothing changes
Click to expand...
Click to collapse
hm, but as scratch mentioned (if I'm correct I remember that, too) you have to confirm the installation of the PC49IMG.zip (with vol up? - not sure) - so if your volume keys don't work: how do you know the update did work?
My volume keys are perfect but not only working in fastboot n hboot menu. When i place PC49IMG.zip in my SD Card and start the phone by holding down volume key + power button it brings me to HBOOT menu where it stays for a while then starts reading for PC49IMG.zip. After reading it give me the option to " Press Volume up key for update & power button to reboot " then i press VOLUME UP button and it starts updating, after updating it says OK and it tells me to press power button to reboot. After reboot nothing hapens it comes to fastboot screen and still volume keys not working on this screen.
Same here
Hi. I just signed up to post here that SAME ISSUE is happening to me.
I can use volume keys to enter boot screen; but then I am not able to use them to move between the options.
I have an HTC DESIRE device.
Before happening that to me I DIDN'T:
- Upgraded Android OS
- Installed new programs
UPDATED: After sending this post; my device, suddenly, started to shake!!
I had to remove battery to make it stop!
---------- Post added at 12:16 PM ---------- Previous post was at 11:52 AM ----------
Hi guys again,
This worked for me like charm. Check in Google:
Restarting or factory resetting your phone
I can't put HTML link because of stupid 'no link before 10 posts' policy. Sorry guys, one thing is to fight spam; but this is too much.
Check this section; where it explains how to perform reboot without the need of getting into boot screen:
If you cannot turn on your phone or access the phone settings, you can still perform a factory reset by using the buttons on the phone.
Press and hold the VOLUME UP, VOLUME DOWN and END CALL/POWER buttons.
When you see a warning message on screen, press the VOLUME DOWN button to perform the factory reset, or press any other button to cancel the reset.
After factory reset is complete, press the VOLUME DOWN button to restart your phone.
HI all,
I've asked this question on the firmware thread, but I do not have an answer. So I'm trying here.
I installed the new firmware without any problems. But after the reboot I'm stuck on the white screen with the green logo, and I do not have connection with the computer via fastboot (waiting for device). As against the phone is communicating with the computer by HTC Sync or Windows Explorer.
What can I do?
Thanks
ggreg said:
HI all,
I've asked this question on the firmware thread, but I do not have an answer. So I'm trying here.
I installed the new firmware without any problems. But after the reboot I'm stuck on the white screen with the green logo, and I do not have connection with the computer via fastboot (waiting for device). As against the phone is communicating with the computer by HTC Sync or Windows Explorer.
What can I do?
Thanks
Click to expand...
Click to collapse
How did you install the firmware?
Have you tried fastboot from the bootloader?
thanks clsA
For mike's method (re-lock the bootloader and fastboot) :
1.If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
2.If you are S-OFF ---> no need to re-lock the bootloader.
3.Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
4.Re-name .zip file to firmware.zip
5.Open command prompt
6.Boot your device in fastboot mode (vol down + power ===> fastboot)
7.Connect device to the PC
8.In command prompt cd to fastboot.exe location
9.Make sure you have correct modeid and cidnum (type: fastboot getvar all)
10.Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
11.Type: fastboot oem rebootRUU and wait for device to reboot
12.Type: fastboot flash zip firmware.zip and wait for process to complete
13.Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
14.Type: fastboot flash zip firmware.zip and wait for process to complete
15.Type: fastboot reboot
Currently I have no access to the bootloader
Although the phone is stuck on the white screen it rings when they call me
Turn off the phone holding power button for almost 15seconds till completely shut down. Then hold volume down and power button. You'll be able to enter boot loader. Also provide more details...version firmware, rom, etc
Are you flash a fw twice ?
Try to unlock bootloader and recovery again brother
lennita said:
Turn off the phone holding power button for almost 15seconds till completely shut down. Then hold volume down and power button. You'll be able to enter boot loader. Also provide more details...version firmware, rom, etc
Click to expand...
Click to collapse
I can not. The only possible action is Power and he returns on the white screen.
c3scr33 said:
Are you flash a fw twice ?
Try to unlock bootloader and recovery again brother
Click to expand...
Click to collapse
Yes, twice. And it was ok. I do not have access to the bootloader
You don't provide enough details. But for me it seems like you flash firmware with stock recovery and if you have custom Rom the phone won't boot. Are you sure you are shutting down the phone properly? Then hold volume down for a second. Then WITHOUT release the volume button hold down power WITHOUT release anything till I boot to boot loader?
The phone vibrates once and nothing happens. Still the white screen.
hold power + vol up....if the phone reboots...hold vol down...
Alex-V you are THE GENIUS
Thank you very very very much :good:
ggreg said:
Alex-V you are THE GENIUS
Thank you very very very much :good:
Click to expand...
Click to collapse
nice that its working for you
Hi!
I wanted to update my firmware as some recent lollipop roms refused to flash (I was at AOSPA 4.5 I think). So I looked up, what firmware I had and tried to get back to stock somehow.
It turned out that I had a 1.57.112.2 firmware (T-Mobile AT branding) although I bought an unbranded one (so I should have some x.xx.401.x I think). Nevertheless I looked for stock recovery and backup and found some here (1.57.112.2 recovery) and here (1.57.111.2 twrp backup).
After flashing both, I had a stock ROM running and got an OTA offered which I accepted. After the OTA got downloaded completely, the system said, that it couldn't apply this update. I assume this is because it downloaded the german OTA (1.57.111.2 rom) and wanted to apply it on the austrian firmware (1.57.112.2).
So I thought, maybe I can trick you to download the correct ota by making the rom think, it is the austrian one. I therefor patched the following files:
- system/build.prop
- system/customize/AAInfo.txt
- system/customize/MNS/26201_CS.xml
- system/customize/MNS/26201_Telekom.xml
- system/customize/MNS/default.xml
- system/customize/resource/CCInfo.txt
I basically changed every firmware version or sku occurence from 111 to 112 or t mobile de to t mobile at.
To patch these files I edited them on my pc, pushed to sdcard, booted the phone into recovery, mounted /system and /storage/sdcard1 and then moved the files I had on my sdcard into the correct /system directories.
Then I issued
Code:
adb reboot
to try the OTA once again. But after the htc splash screen, the screen just turns black. I'm not even able to get into hboot/fastboot during this splash screen.
After a few minutes, the phone reboots, thus showing the htc splash screen once again and turning black afterwards.
While the screen is black, I'm not able adb/fastboot into the device. Also the phone doesn't react on pressing some buttons or plugging the power cable.
Do you have some ideas how to get a working base back?
fastboot, recovery, anything?
What you did was a really bad idea. OTA updates are often not complete images (only updated modules are updated). And since you forced the phone to install the 112 OTA over an existing 111 install, its possible there was a bad mixing of components ("old" 111 modules + "new" 112 modules) such as the 3 hboot modules (or some other combination of things that don't play together well). One might not think there would be that much difference between the 1.57.111 versus 1.57.112. But without the proper research, who knows?
The proper sequence would have been to s-off (it probably was already, if in fact it was unbranded with T-Mob firmware applied), change CID and MID, then RUU back to stock. Or if no RUU, restore stock WWE ROM, and firmware.
Try holding down power & vol up, power & vol down, or just power for 30 seconds or more. With or without the charger plugged.
Any response if you plug the phone to a computer?
If none of the above works (and no LED), it probably JTAG for you.
Why so impulsive to try that? Seems like you winged it without looking up any repercussions.
@redpoint73
It is/was S-ON atm.
I've tried RUUs before but either there was a version mismatch or the RUU wasn't able to keep the connection and failed to connect to the device after the first reboot into ruu mode.
The power + volume up + volume down works in terms of rebooting but doesn't bring the device out of the bootloop (or whatever it's looping). I'm having adb and fastboot waiting for a device connection but both didn't fire up yet, so I assume, the phone won't provide any adb or fastboot client.
@jduke05
Well.. For the m7 I read, that the german and austrian version were exchangeable so I hoped something like that would count for the m8 too. (typically me....)
Also the ota said, it can't and won't update. I thought it didn't change anything if it complained that it won't change anything.
Uroc327 said:
@redpoint73
It is/was S-ON atm.
I've tried RUUs before but either there was a version mismatch or the RUU wasn't able to keep the connection and failed to connect to the device after the first reboot into ruu mode.
The power + volume up + volume down works in terms of rebooting but doesn't bring the device out of the bootloop (or whatever it's looping). I'm having adb and fastboot waiting for a device connection but both didn't fire up yet, so I assume, the phone won't provide any adb or fastboot client.
Click to expand...
Click to collapse
When S-on, RUU needs to match your CID and MID, and has to be equal or greater software version than what is on the phone. No exceptions.
The phone boots, that is good, as it means its not bricked.
Although, you're pretty stuck if you don't get adb/fastboot working. Connection issues are usually on the PC side. Try different USB ports, cables. Or try to re-install HTC Sync. Also, adb will only work when booted into OS or recovery. Fastboot will work when booted into bootloader fastboot mode. This alone may be your issue (adb won't work in bootloader/fastboot).
S-on is also a good thing in your case. It means that probably nothing installed anyway, since with s-on the OTA would have failed with wrong CID (and you can only change CID with s-off).
Uroc327 said:
Well.. For the m7 I read, that the german and austrian version were exchangeable so I hoped something like that would count for the m8 too. (typically me....)
Click to expand...
Click to collapse
What applies for another device should never be assumed to be the same for yours.
A lot of things change, even from one software build to the next (same device) so I would erase any assumption that they are interchangeable. Don't ever assume anything, for that matter.
Hmm.. although I don't get any fastboot/adb response, udev (oh yeah, forgot to mention I'm on linux) fires some events when the device reboots. Though I don't know any protocol I can use to speak to the device.
Well the problem with the RUUs was, that Windows tried to install some new drivers as soon as the device rebooted into ruu mode instead of using the already installed drivers.
But, though I'm having S-ON, it installed enough to not enter the bootloader/fastboot/rom/... (whatever the first thing not showing up is).
It seems like it's just an ordinary damaged boot partition.
After having it rebooting the night the battery was finally empty and I was able to get into the (undamaged) bootloader and into the (also undamaged) recovery.. Isn't it great that one can't take out the battery any more?
Anyways.. thanks for your replies
Uroc327 said:
After having it rebooting the night the battery was finally empty and I was able to get into the (undamaged) bootloader and into the (also undamaged) recovery.. Isn't it great that one can't take out the battery any more?
Click to expand...
Click to collapse
If the phone is rebooting, all you need to do is hold vol down, and it will go to bootloader on the next reboot.
Battery pull isn't needed on this phone, but the correct knowledge is.
redpoint73 said:
If the phone is rebooting, all you need to do is hold vol down, and it will go to bootloader on the next reboot.
Battery pull isn't needed on this phone, but the correct knowledge is.
Click to expand...
Click to collapse
That's exactly what I did! I know how to get into the bootloader... But nothing happened.
The only way to influence the device was to hold down power + volume up + volume down. Then it wen't to the white splash screen with the green htc on it (then holding down volume down didn't do anything either) and continued with the loop.
Uroc327 said:
.....it wen't to the white splash screen with the green htc on it (then holding down volume down didn't do anything either) and continued with the loop.
Click to expand...
Click to collapse
when it is on the white splash screen,
Press & hold volume up & power buttons until the screen goes dark (it's rebooting)
then release both buttons, quickly press & hold volume down button. This will take it to bootloader screen.
On method above ... require only one or two buttons press at one time ... there is no three button press at the same time.
If you can get to bootloader, post result of fastboot getvar all minus serial no. & imei no.
I may have the correct TWRP backup for your software version.
ckpv5 said:
when it is on the white splash screen,
Press & hold volume up & power buttons until the screen goes dark (it's rebooting)
then release both buttons, quickly press & hold volume down button. This will take it to bootloader screen.
On both method above ... require only one or two buttons press at one time ... there is no three button press at the same time.
If you can get to bootloader, post result of fastboot getvar all minus serial no. & imei no.
I may have the correct TWRP backup for your software version.
Click to expand...
Click to collapse
Gonna try the volume up + power next time.. (Probably it's the same as both volumes + power but i really don't know).
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA10G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.112.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It would be awesome, if you could find a twrp version that boots
I've tried versions 2.7.0.1, 2.8.5.0 and 2.8.6.0 and every time I've waited forever on the htc splash screen with the purple 'Entering Recovery ...' without seeing anything happening.
Currently I'm using philz touch (booting fine) for clockworkmod backups and a simple tar -xf in the adb shell and fastboot flash boot for twrp backups
Uroc327 said:
That's exactly what I did! I know how to get into the bootloader... But nothing happened.
The only way to influence the device was to hold down power + volume up + volume down. Then it wen't to the white splash screen with the green htc on it (then holding down volume down didn't do anything either) and continued with the loop.
Click to expand...
Click to collapse
It sounds like you are actually talking about the phone being stuck on the boot splash, not a "boot loop".
A boot loop means the phone is rebooting itself over and over on its own. When this is the case, holding the vol down will send you to bootloader on the next reboot "loop".
If its stuck on the bootsplash, its probably just a timing issue. Power+ vol up reboots the phone. The moment screen goes dark, but before the HTC boot slash appears, let go of those buttons, and only hold vol down, and don't let go until bootloader comes up. Failure to get into bootloader is virtually always a case of not pressing vol down soon enough, or letting go too early. After dozens of claims of this not working, I've seen every single one proven as being a case of not performing the button combo timing correctly. The only exception, is the (very rare) instance of the power button or vol rocker being physically broken.
redpoint73 said:
It sounds like you are actually talking about the phone being stuck on the boot splash, not a "boot loop".
A boot loop means the phone is rebooting itself over and over on its own. When this is the case, holding the vol down will send you to bootloader on the next reboot "loop".
If its stuck on the bootsplash, its probably just a timing issue. Power+ vol up reboots the phone. The moment screen goes dark, but before the HTC boot slash appears, let go of those buttons, and only hold vol down, and don't let go until bootloader comes up. Failure to get into bootloader is virtually always a case of not pressing vol down soon enough, or letting go too early. After dozens of claims of this not working, I've seen every single one proven as being a case of not performing the button combo timing correctly. The only exception, is the (very rare) instance of the power button or vol rocker being physically broken.
Click to expand...
Click to collapse
As I've state in post #4 I don't exactly know what it's actually looping. I just know, that it shows this splash screen over and over again.
The screen goes dark automatically: It was like splash screen (few seconds.. normal time) -> black screen (a few minutes) -> return to splash screen
So the screen turned dark anyways (which indeed indicates a timing issue from my side as you said).
Uroc327 said:
Gonna try the volume up + power next time.. (Probably it's the same as both volumes + power but i really don't know).
Click to expand...
Click to collapse
It is the same. Power + vol up + vol down is not a valid button combo.
Power + vol up (force reboot)
Power + vol down (boot recovery when powered off; vol down only needed when rebooting)
Uroc327 said:
It would be awesome, if you could find a twrp version that boots
I've tried versions 2.7.0.1, 2.8.5.0 and 2.8.6.0 and every time I've waited forever on the htc splash screen with the purple 'Entering Recovery ...' without seeing anything happening.
Click to expand...
Click to collapse
Did you fastboot erase cache before flashing a new TWRP version?
redpoint73 said:
Did you fastboot erase cache before flashing a new TWRP version?
Click to expand...
Click to collapse
Of course
Unfortunately I don't keep 1.57.112.2 (I've deleted most of the 1.xx.xxx.x backups as I thought no one will ever need them anymore)
I have only 2.23.112.3, 3.29.112.9 & 4.19.112.2
ckpv5 said:
Unfortunately I don't keep 1.57.112.2 (I've deleted most of the 1.xx.xxx.x backups as I thought no one will ever need them anymore)
I have only 2.23.112.3, 3.29.112.9 & 4.19.112.2
Click to expand...
Click to collapse
I've found a 2.23.112.x for cwm, too. But is it a good idea to flash 2.23 onto a 1.57 firmware and then downloading an OTA?
I think I somewhere read that those firmware updates are incremental.
Uroc327 said:
I've found a 2.23.112.x for cwm, too. But is it a good idea to flash 2.23 onto a 1.57 firmware and then downloading an OTA?
I think I somewhere read that those firmware updates are incremental.
Click to expand...
Click to collapse
No ... that's not correct. Restore a one version lower backup on a higher firmware is ok but restore a one version higher than the firmware is a no.
Damn .. I don't keep the firmware too. If you can find the 2.23.112.3 firmware then it's good too.
You can restore the 2.23.112.3 then flash 2.23.112.3 firmware, reboot and do OTA
ckpv5 said:
No ... that's not correct. Restore a one version lower backup on a higher firmware is ok but restore a one version higher than the firmware is a no.
Damn .. I don't keep the firmware too. If you can find the 2.23.112.3 firmware then it's good too.
You can restore the 2.23.112.3 then flash 2.23.112.3 firmware, reboot and do OTA
Click to expand...
Click to collapse
I've looked the last two days but I didn't find firmwares for 112 by now.
Does flashing the firmware need s-off already? Do OTAs and RUUs (for this firmware) work with s-on?
Uroc327 said:
I've looked the last two days but I didn't find firmwares for 112 by now.
Does flashing the firmware need s-off already?
Click to expand...
Click to collapse
No need S-Off when flashing a signed firmware.
I will see whether I can find 2.23.112.3 firmware in a day or two
I have 3.29.112.5 & higher firmware but not 2.23.112.3
I'm not a HTC user myself, but my friend got his 816 on bootloop, and if he hold the power + vol- button in boot he will get the android robot screen, but not the menu which is supposed to come.
Sorry I'm a sony user and i'm not familiar with htc, the phone is not even on my hand but i'm just trying to flash the stock firmware again. Could someone give me a simplest possible guide，maybe something like flashtool on xperia.
And how do i completely shut down a HTC phone? it keeps rebooting itself with power and vol+
Thanks
First of all, to help, we'll need to know more specs of the phone..
If your in a bootloop, try holding vol +, vol - and power at the same time, once the screen is completely black, hold vol- and power. If you're doing it right, your device should boot in the boatloader. White background, phone specs at the top.
Please post this data, since we'll need to know the device model to help.
If this doesn't work, try to use adb commands.
First of all, make sure USB-Debugging is enabled on your device and all drivers are up-to-date (HTC Sync, Java and fastboot).
- Download ADB fastboot folder (just extract it to C:\ and you're good to go)
- Connect your device and PC using usb data cable
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window' here
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
adb reboot fastboot
to reboot your device. It should start in fastboot mode.
And if that doesn't work either, try using
Code:
fastboot getvar all
instead of
Code:
adb reboot fastboot
and post the result.
Please make sure to delete the lines
(bootloader) serialno: and (bootloader) meid: since they won't be needed. Never post your imei on the internet.
nukaru said:
First of all, to help, we'll need to know more specs of the phone..
If your in a bootloop, try holding vol +, vol - and power at the same time, once the screen is completely black, hold vol- and power. If you're doing it right, your device should boot in the boatloader. White background, phone specs at the top.
Please post this data, since we'll need to know the device model to help.
If this doesn't work, try to use adb commands.
First of all, make sure USB-Debugging is enabled on your device and all drivers are up-to-date (HTC Sync, Java and fastboot).
- Download ADB fastboot folder (just extract it to C:\ and you're good to go)
- Connect your device and PC using usb data cable
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window' here
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
adb reboot fastboot
to reboot your device. It should start in fastboot mode.
And if that doesn't work either, try using
Code:
fastboot getvar all
instead of
Code:
adb reboot fastboot
and post the result.
Please make sure to delete the lines
(bootloader) serialno: and (bootloader) meid: since they won't be needed. Never post your imei on the internet.
Click to expand...
Click to collapse
Thanks for your help, i'll give a try