Related
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
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).
Due to an update bricking my phone hardcore I found this solution. Please keep in mind my phone's state of function.
BootLoop into erecovery
TWRP was not working
*Have access to FASTBOOT with Bootloader=Unlocked and FRP=Unlocked
1. You must have access to FASTBOOT with Bootloader and FRP Unlocked.
To get to FASTBOOT you need to have a USB cable hooked up to a Windows PC and at the ready.
Turn off the phone and make sure it is disconnected from the charging cable.
Now turn on the phone by holding down the Volume (-) and Power Button Simultaneously.
*Important* As soon as you feel the phone vibrate you must put in the USB cable attached to the PC.
At this point you should be at the FASTBOOT screen.
2. Download the following File and extract it to a folder on the Desktop. 1.2GB in size.
https://mega.nz/#!rAlSBQ7B!zI21XTb_0IrYsD3hBGdn8cYhjK9oh-WXecWuDbkJxl8
3. Now start up the Terminal in Windows (start, Run, then type "CMD" ).
Now change your directory so that your inside the fold you just created from unzipping the downloaded file.
4. Execute the following commands one at a time.
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash ramdisk RAMDISK.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk Twrp_p10_lite_0.5_Pretoriano8.img
fastboot reboot
This should fix the issue.
Can you put the file into google doc? hard for me to download from mega.
When I get back to the computer I'll Google drive it for you.
Still getting bootlooped to erecovery. Not sure if I am missing any step or my phone just bricked AF.
I am using BND-L34/Huawei SE bought from Amazon US.
Update(12/24):
So I finally got my Mate SE working after 3 month of bricked mode and countless of tries to get it un-bricked. I bricked my phone by rooting it/flashing RROS Rom then attempting to go back to EMUI.
Method:
Flash TWRP to recovery,
Follow these two guides,
https://forum.xda-developers.com/hu...ide-manual-update-p20-pro-hurupdater-t3816283
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
before you attempt those two guide, wipe everything on phone except for the external storage(this was the method that really worked for me)
Here is the Google drive link for the zip file.
https://drive.google.com/file/d/1BstLuj0WHrHLWQ2tjen9xtdtdkzYQNVL/view?usp=drivesdk
Bricked BND-L34 8.0.0.362(C567)
Hi,
This is my situation, my Mate SE is bricked, stuck in Huawei Logo. It's a mystery because I don't know what cause it (no root, never flashed, etc.)
Firmware version: BND-L34 8.0.0.362(C567)
Device name: BND-L34
OEMInfo: hw/usaA
Serial N: 4AV7N18A12005478
Bootloader state: Locked
Phone: Locked
FRP: Locked
Could you help me?
Any ideas?
Thanks in advance
peatonurbano said:
Hi,
This is my situation, my Mate SE is bricked, stuck in Huawei Logo. It's a mystery because I don't know what cause it (no root, never flashed, etc.)
Firmware version: BND-L34 8.0.0.362(C567)
Device name: BND-L34
OEMInfo: hw/usaA
Serial N: 4AV7N18A12005478
Bootloader state: Locked
Phone: Locked
FRP: Locked
Could you help me?
Any ideas?
Thanks in advance
Click to expand...
Click to collapse
Have you tried any of the guides here?
Hi,
I am looking how to fix my friend's Realme 8 5G (RMX3241) phone.
Here is the story:
1) My friend downgraded his firmware but by an accident installed ROM for India region, the result was he had no GSM signal on the phone (he lives in EU).
2) He also unlocked bootloader, but probably not correctly, because it shows orange state and I can't go into recovery with combination vol up + power
3) The phone booted, but no GSM.
What I did:
1) Managed to boot into recovery using "adb reboot recovery".
2) Then I pressed 'reboot' in recovery (I wanted to load a proper region ROM) and since then I am watching "realme" logo for like 10 minutes straight, so I assume it went into bootloop.
What I can do now:
1) After pressing vol down + power it shows:
oplus Verify fail
need to verify signature of another brand
oplus Verify pass
fastboot verify success
fastboot_unlock_verify ok
However in this state I can't reach this phone using adb
2) Pressing vol up + power doesn't boot into recovery, just normally boots the system but it goes into bootloop.
3) The orange state is still there.
So assume I am now left with bootlooped system with no access to ADB.
Can anyone help me with this? Are there any solutions to this?
Tried SP Flash tool but after loading scatter file it shows:
Platform MT68 not support on this version.
Please update to latest flashtool and try again.
Well, I have a solution for that.
It seems that the system is bricked, so you need to download a proper firmware version for your phone, and flash the stock ROM via fastboot (platform-tools) by erasing super and vbmeta partitions, and flashing every single IMG file of the firmware stock ROM.
2) He also unlocked bootloader, but probably not correctly, because it shows orange state and I can't go into recovery with combination vol up + power
Click to expand...
Click to collapse
Orange state is normal also as far as i know there is not a button combination to boot into recovery on this phone
1) After pressing vol down + power it shows:
oplus Verify fail
need to verify signature of another brand
oplus Verify pass
fastboot verify success
fastboot_unlock_verify ok
However in this state I can't reach this phone using adb
Click to expand...
Click to collapse
This is fastboot mode and you have to use fastboot which is bundled with adb, in this state you can: unlock bootloader, flash partitions or you can reboot to recovery
Taracair said:
Tried SP Flash tool but after loading scatter file it shows:
Platform MT68 not support on this version.
Please update to latest flashtool and try again.
Click to expand...
Click to collapse
SP_Flash_Tool_v5.2124 works for me
You have to:
Have proper VCOM MTK drivers installed
Boot the phone by pressing vol up + vol down while connected to pc via usb
Use MTKAuthBypass v7 before flashing in order to bypass auth protection system.
UPDATE:
mtkclient it's perfect and on the github everything is explained on how to use it