Related
Hi All,
I have an international HTC ONE M8 which I managed to root and s-off without a problem. However since I s-off-ed the phone will not reboot into bootloader.
When I try to power off and reboot with vol-down and power it either reboots or flashes between the battery screen and TWRP, which say swipe to unlock but it flashes too quick for mee to do this. This a strange error I never come across before in the years Ive been flashing and modding devices.
Also ADB no longer sees this phone in fastboot, I can issue fastboot commands but not ADB
Can anyone help
Jonnibravo said:
Hi All,
I have an international HTC ONE M8 which I managed to root and s-off without a problem. However since I s-off-ed the phone will not reboot into bootloader.
When I try to power off and reboot with vol-down and power it either reboots or flashes between the battery screen and TWRP, which say swipe to unlock but it flashes too quick for mee to do this. This a strange error I never come across before in the years Ive been flashing and modding devices.
Also ADB no longer sees this phone in fastboot, I can issue fastboot commands but not ADB
Can anyone help
Click to expand...
Click to collapse
Press and hold power and volume up until phone shuts off. Let go of power and volume up then hold volume down until bootloader comes up -_-
exad said:
Press and hold power and volume up until phone shuts off. Let go of power and volume up then hold volume down until bootloader comes up -_-
Click to expand...
Click to collapse
Genius, thanks. I'm too used to my other devices where you simply did the power button down.
Jonnibravo said:
Hi All,
I have an international HTC ONE M8 which I managed to root and s-off without a problem. However since I s-off-ed the phone will not reboot into bootloader.
When I try to power off and reboot with vol-down and power it either reboots or flashes between the battery screen and TWRP, which say swipe to unlock but it flashes too quick for mee to do this. This a strange error I never come across before in the years Ive been flashing and modding devices.
Also ADB no longer sees this phone in fastboot, I can issue fastboot commands but not ADB
Can anyone help
Click to expand...
Click to collapse
You might also try making sure Fastboot in the power menu is off. And ADB won't work in Fastboot mode - you either have to boot into recovery or android for ADB.
Sent from my HTC One_M8 using Tapatalk
Something happened to my M8 so I can't access bootloader anymore. Pressing Power and Vol Up just boots the phone and then the screen goes blank. Pressing Vol Down to get into fastboot doesn't work anymore (it used to up until now). Any clue?
mpogr said:
Something happened to my M8 so I can't access bootloader anymore. Pressing Power and Vol Up just boots the phone and then the screen goes blank. Pressing Vol Down to get into fastboot doesn't work anymore (it used to up until now). Any clue?
Click to expand...
Click to collapse
Press and hold the volume down, then at the same time press and hold the power button (both should be held now).
Wait for the screen to go blank.
When the screen goes blank, release the power button, but continue to hold the volume down button.
You should then eventually see the fastboot/hboot menu.
OK, found what the issue was. The problem was that my phone's screen was going blank after the normal boot screen, so I couldn't see when it gets turned off. I was simply pressing the Vol Up + Power for too long, so it would go into full reboot. I just measured the amount of time it was taking to do this (was ~12 seconds). So I pressed Vol Up + Power for ~10 secs, then released those and pressed Vol Down. That finally brought me into Fastboot.
I could have probably gotten the same result by pressing Vol Down + Power, however, the phone screen was blank all the time, so it was difficult to understand when I should have released the Power button to let it go into Fastboot.
mpogr said:
OK, found what the issue was. The problem was that my phone's screen was going blank after the normal boot screen, so I couldn't see when it gets turned off. I was simply pressing the Vol Up + Power for too long, so it would go into full reboot. I just measured the amount of time it was taking to do this (was ~12 seconds). So I pressed Vol Up + Power for ~10 secs, then released those and pressed Vol Down. That finally brought me into Fastboot.
I could have probably gotten the same result by pressing Vol Down + Power, however, the phone screen was blank all the time, so it was difficult to understand when I should have released the Power button to let it go into Fastboot.
Click to expand...
Click to collapse
Thanks for this post! I've spent a total of 5+ hours trying to get into the bootloader so I could restore a backup after a bad flash soft bricked me.
"Press and hold power and volume up until phone shuts off. Let go of power and volume up then hold volume down until bootloader comes up -_-"
Holy mackerel! You saved me! The Blackhawks are playing and I need to be able to text my mom and cousin. I was having a mini-panic attack. Your fix worked like a charm. I am back in texting business!!! Thank you, thank you, thank you! Go Hawks!
i have a htc one m8 and its stuck on the logo with triangles around the four corners around the screen..what do i do?
antonio14843 said:
i have a htc one m8 and its stuck on the logo with triangles around the four corners around the screen..what do i do?
Click to expand...
Click to collapse
The red triangle screen is stock recovery. Power + vol up when on the stock recovery, will bring up the recovery menu.
Not sure what you are trying to do. Based on the subject of this thread you decided to post in, are you trying to get into bootloader? Or just trying to get the phone to boot to OS?
If you are trying to get into OS. You can try to wipe cache, and reboot to see if you can reboot back into OS (or factory reset and reboot, if you don't mind losing your personal data). But depending on what is wrong with the phone, you may need to do more to get into OS.
Can't access bootloader
exad said:
Press and hold power and volume up until phone shuts off. Let go of power and volume up then hold volume down until bootloader comes up -_-
Click to expand...
Click to collapse
Everytime I do this, hold POWER, then VOL UP till screen goes black, release BOTH, then press POWER and VOL DOWN, then release POWER first time screen flashes, while still holding VOL DOWN, it returns to the OS every time!
Everytime I do this, hold POWER, then VOL UP till screen goes black, release BOTH, then press POWER and VOL DOWN, then release POWER first time screen flashes, while still holding VOL DOWN and then press POWER again, the screen CYCLES between BLACK and the RASTER glow on the LCD. About 3-4 secs of BLACK, then RASTER glow, then repeat. If I let go of POWER, it goes right to the OS again, every time.
Everytime I do this, hold POWER, then VOL UP till screen goes black, release BOTH, then press POWER and VOL DOWN, wait for RASTER glow and continue to press BOTH until first time goes BLACK, then release POWER while still holding VOL DOWN, it goes right to the OS again, every time.
I don't know what I'm doing wrong. I followed the HTC directions at the DEV site, to change the boot speed, but it wasn't in the BATTERY menu, it was in ACCESSIBILITY and called QUICK BOOT. For units with Android 4.2.x and up, HTC site said to turn on OEM unlocking in Developers menu, but this is 4.4.2 and there is no option in there to do that.
This is a DUAL SIM phone, so I assume that is an international version, also.
Further, when I do try the HTC site method of entering the bootloader menu, (press Volume Down and while pressing Volume Down, press Power holding both buttons to start the device into Bootloader mode (now Download mode for One M9 and newer devices) I get a menu
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
, but I don't read Chinese/Korean, or whatever language these characters are from, but it works like a TEST or SERVICE menu, as it puts the phone thru all the self-tests of its' various hardware functions. Not much help to me.
This phone has a crashed Android update that never completes every time it starts, but I can't tell what version or from whom. It does not APPEAR to be locked to any carrier as there are no logos on the phone or in the bootup screens. If I can every get it where I can flash it, then I hope to learn WHAT there is to flash it with.
Right now, I just want to get to the bootloader, so I can see if it will talk with the laptop using the apps I downloaded from HTC; Android studio, Java and the Sync Manager. Once all those hurdles have been jumped, if it succeeds and functions properly, and flashing rids it of the nasty malware, xrated crap its' infested with, I'll order a glass to repair it make it my own for a while.
Any help figuring out why I can't make the VERY CLEAR instructions I found in this thread work for me, will be very, very, VERY much appreciated.
Thanks to you all.
There is no "then press POWER and VOL DOWN" in the instruction, after release both power & volume up, press only volume down button.
What device is that ? Definitely not M8 & not M8 dual SIM.
If you still can boot, enable usb debugging in Developer options then run adb devices to see the serial no.
If it come out as weird as 123456789abcdef then it's fake htc.
Your screenshot looks familiar and I manage to find the same that written in English
https://forum.xda-developers.com/showpost.php?p=50678371&postcount=3
Can't access bootloader
ckpv5 said:
There is no "then press POWER and VOL DOWN" in the instruction, after release both power & volume up, press only volume down button.
Click to expand...
Click to collapse
I was very frustrated by the directions I got from HTC inserted below:
press Volume Down and while pressing Volume Down, press Power holding both buttons to start the device into Bootloader mode (now Download mode for One M9 and newer devices). If you have difficulty, power up normally, go to Settings->Battery and deselect Fast boot. Power down and try again.
Click to expand...
Click to collapse
Then I came here after a Google search listed many hits, this one seemed like the best (as always XDA would be my first choice) of them all. Then I tried the button instructions here. But all led to further frustrations. I am an antiquated fossil of 63 years old, a mere high school graduate of the Class of 1971, a once upon a time in dog years (1996-1998), Novell NetWare CNA/CNE network geek, PC/server hardware tech, systems programmer, systems analyst, and Windows OS & Office Suite Desktop End-User Support Specialist. In other words, I am qualified to not only read English, I can even compose my thoughts and present them using it.
Most of the time.
What device is that ? Definitely not M8 & not M8 dual SIM.
Click to expand...
Click to collapse
Great question!! Unfortunately, the answer may be the solution to at least most of the problem. The next question would be "What implications does that present? Does that make it irreparable and essentially worthless?"
The serial number is EXACTLY what you posted;
123456789ABCDEF
Just to be thorough, here are the other details. But, I did NOT get these using ADB, because I can NOT get ADB to work at all. These details came from About Phone.
IMEI Slot1: 355131214676268
(I forgot the label): 78
IMEI Slot2: 355131214676276
(?????????? label): 78
S/N: 123456789ABCDEF
Model: M8
Android version: 4.4.2
Baseband:
MOLY.WR8.W1315.MD.WG.MP.V43, 2014/09/17 10:10
Kernel: 3.4.67 [email protected] #1 Thu Sep 24 09:46:01 CST 2015
Build Number: X5_72KK_KK_3GW_B15_EMMC_32_4_QHD_XLD_MII_ZX 20150924.103623
Custom Build Version: 1442306041
If you still can boot, enable usb debugging in Developer options then run adb devices to see the serial no.
If it come out as weird as 123456789abcdef then it's fake htc.
Click to expand...
Click to collapse
Needless to say, but I already told how I got this. I don't mean to sound like a smartass, but I can't help it. I flashed and modded my first Motorola Droid back in 2012. This ain't my first rodeo, its' just that this phone has been one of the more frustrating broncs I've tried to break lately. If this is a "FAKE" HTC phone, I would not be surprised to learn that. I had not been aware until now that there are fakes.
I mean, WTF?
Your screenshot looks familiar and I manage to find the same that written in English
https://forum.xda-developers.com/showpost.php?p=50678371&postcount=3
Click to expand...
Click to collapse
Yep. Now, what do you recommend? WAIT!
I want you to know that I followed the link to your GUIDE. Very Well done, sir.
I found it remarkably well organized, detail specificity very professionally presented, and written for a layperson without sacrificing the value of educating them with vernacular of the high level technician. I commend you.
With that said, whether ir is while I have the OS up, or from recovery menu ADB function, this is what I get when trying to use ADB on this potentially worthless waste of time:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb start-server
adb server version (31) doesn't match this client (35); killing...
error: protocol fault (couldn't read status): Connection reset by peer
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037: Only one usage of each socket address (protocol/network address/port) is normally permitted. (10048)
could not read ok from ADB Server
* failed to start daemon *
error: cannot connect to daemon
AND
C:\Program Files (x86)\Minimal ADB and Fastboot>flashing get_unlock_ability
adb server version (31) doesn't match this client (35); killing...
* daemon started successfully *
error: no devices/emulators found
So, with all that, what say you to my question, "Now what?"
My Opinion, if it is a fake, disassemble it to explore the guts,
like a 1st year med-student exploring human anatomy on a
homeless, unidentified cadaver from the Morgue.
dbreed53 said:
Just to be thorough, here are the other details. But, I did NOT get these using ADB, because I can NOT get ADB to work at all. These details came from About Phone.
IMEI Slot1: 355131214676268
(I forgot the label): 78
IMEI Slot2: 355131214676276
(?????????? label): 78
S/N: 123456789ABCDEF
Model: M8
Android version: 4.4.2
Baseband:
MOLY.WR8.W1315.MD.WG.MP.V43, 2014/09/17 10:10
Kernel: 3.4.67 [email protected] #1 Thu Sep 24 09:46:01 CST 2015
Build Number: X5_72KK_KK_3GW_B15_EMMC_32_4_QHD_XLD_MII_ZX 20150924.103623
Custom Build Version: 1442306041
If this is a "FAKE" HTC phone, I would not be surprised to learn that. I had not been aware until now that there are fakes.
Click to expand...
Click to collapse
It's a clone HTC that we know existed since 2014 and nothing much that we can offer to help.
See this for some screenshots - https://forum.xda-developers.com/htc-one-m8/help/token-initializer-chinese-htc-one-m8-t2813316
There's a screenshot about phone that more or less same as yours
And this for some video - https://forum.xda-developers.com/showthread.php?t=2761985
I have the same issue. I have pressed power and vol dowm couple times, my battery is full but nothing happened. What to do????
renniefb said:
I have the same issue. I have pressed power and vol dowm couple times, my battery is full but nothing happened. What to do????
Click to expand...
Click to collapse
Same issue as who? The OP has an issue with the button combo making the phone reboot or flash between battery charge screen and TWRP. Plus, that post is from 2014, so their firmware most likely does not match what you have, even remotely. Another person who posted to this thread. has a dual SIM Chinese version. I doubt either accurately describes your situation.
Do yourself a favor, and don't post "I have the same issue" while giving zero details on your M8 version (CID, MID) whether it is modded (unlocked bootloader, custom recovery, root, s-off, etc.) as well as the current condition: is the phone powered off when you try the button combo, or stuck on a boot screen, etc.
Giving as many details about your device and situation makes it easier for us to help you.
The button combo power+ vol down will only boot to bootloader if the phone is powered down. And you may have to hold the buttons for a minute or more, depending on the current condition of the phone. If this doesn't work, of the phone is in another state (such as stock on boot screen with HTC logo) tell us of this, and we will advise you further.
volume down button doesnt work
hi,
Volume down button doesnt work so i cant access bootloader. (https://www.youtube.com/watch?v=ZomJvkphGms) also i tried to short two pins like this video. but no success.
Is there any alternative way to access to bootloader.
thanks in advance
turksailorman said:
hi,
Volume down button doesnt work so i cant access bootloader. (https://www.youtube.com/watch?v=ZomJvkphGms) also i tried to short two pins like this video. but no success.
Is there any alternative way to access to bootloader.
thanks in advance
Click to expand...
Click to collapse
Does your phone boot into Android OS, or not? If so, I believe there are some market apps you can install to boot to bootloader, that you can try. Or you can do adb reboot bootloader.
redpoint73 said:
Does your phone boot into Android OS, or not? If so, I believe there are some market apps you can install to boot to bootloader, that you can try. Or you can do adb reboot bootloader.
Click to expand...
Click to collapse
No stuck on HTC logo.
Tonight I was playing around with my new Nexus 5X, then it suddenly rebooted. First it was kinda in a bootloop, it booted till the animated google logo, then the animation stopped and after a second it rebooted again. This happened a few times by itself (I was unable to switch the phone off, it just started over again and again) until during a new reboot the LED illuminated blue permanently and this screen appeared:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that I could switch the phone off, but couldn't turn it on again, even not by holding the power button for more than 10 seconds. The screen just leaves blank, no boot image, no LED, no sign of life anymore. :crying: I also tried removing sim-card, charging, nothing works...
I received my Nexus two days ago. First of all I unlocked the bootloader, decrypted the data partition and rooted it. All worked fine until tonight...
Well, I already wrote the Google support. I hope the warranty is still valid? Does anybody else probably have another idea?
What was the root method?
Sent from my Nexus 5X using Tapatalk
I used Chainfire's systemless root (bullhead-mdb08i-boot-systemless.zip) on MDB08M.
If you can still get into the bootloader, you have to reflash the boot.img, the ramdisk of the boot image permissions got changed somehow. I got the same message when I flashed a boot.img with a bad ramdisk permissions.
You say you can turn it off but not on. Can you access the bootloader? Turn phone off, hold volume down + power button until you see the android lying on his back with his hatch open?
If you can, I'd try flashing factory images and start fresh.
Sent from my Nexus 5X using Tapatalk
No way to access the bootloader.
I guess I need a fix like this: http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
When I connect the phone to my PC and hold the power button for 10 secs a new device is listed in the device manager "QHSUSB_BULK". However the screen is still completly off.
Koboldchen said:
No way to access the bootloader.
I guess I need a fix like this: http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
When I connect the phone to my PC and hold the power button for 10 secs a new device is listed in the device manager "QHSUSB_BULK". However the screen is still completly off.
Click to expand...
Click to collapse
1) Tell me what you can do exactly with the phone (bootloader,recovery,reboot,etc) and the reactions i.e vibrates while starting or something else
2) Your pc recognizes the phone, even if its the qualcom (I guess) and thats good
3) I'm pretty sure, that there is a way to fix it somehoe
Gesendet von meinem SM-N920C mit Tapatalk
I got that same exact screen when I was trying to flash the vendor. img and the way I got out of it was by holding the volume up and the power button and got me into this download mode which was asking me to flash firmware so I keep holding the volume down button and the power button for a long time and finally if we booted into the ROM again I hope that helped
tlopez1973 said:
I got that same exact screen when I was trying to flash the vendor. img and the way I got out of it was by holding the volume up and the power button and got me into this download mode which was asking me to flash firmware so I keep holding the volume down button and the power button for a long time and finally if we booted into the ROM again I hope that helped
Click to expand...
Click to collapse
I can't get into the bootloader at all, neither with holding volume down + power nor with volume up + power (and also with volume down + up + power). The screen just leaves black with no backlight.
Mucky2 said:
1) Tell me what you can do exactly with the phone (bootloader,recovery,reboot,etc) and the reactions i.e vibrates while starting or something else
2) Your pc recognizes the phone, even if its the qualcom (I guess) and thats good
3) I'm pretty sure, that there is a way to fix it somehoe
Click to expand...
Click to collapse
Right now I can't do anything. There are no reactions, no vibrations, no LED, no screen... Yesterday I could at least get into the qualcomm-mode while holding down the power-button for 10 seconds and have the phone connected to my PC. Yesterday evening as I was trying again to get into the bootloader the LED just flashed red shortly and nothing else happened (even not the qualcomm-boatloader was accessible). I charged the phone overnight, but it still does nothing. It looks like the Nexus is really dead now.
I still wonder what happened. As I wrote I could use the phone two days long with no problems. Then it crashed/rebooted itself, I saw that screen I attached into my first post and blue light, yesterday I could at least get into the qualcomm-mode and now (after that red LED flash) really nothing works anymore.
Till Monday I'll keep watching and testing since I can't send it back on weekends. But I'm afraid that I have to get it fixed by Google/LG. Thanks for your help anyways, fortunately I still have my Nexus 4...
Some news: I can access the google bootloader again.
Whyever, during this day the phone became discharged completely again (red LED flashed by pressing the power button), but this time I charged it only for a few minutes... After this I held volume down + power and the LED was blue again and the screen was the same like the screenshot I posted. I held power to switch off the phone and next volume down + power for 10 sec immediately again. This time the bootloader was shown.
So I restored the stock image completely:
Code:
fastboot flash bootloader bootloader-bullhead-bhz10i.img
fastboot reboot-bootloader
fastboot flash radio radio-bullhead-m8994f-2.6.28.0.65.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
The only thing I didn't do was relocking the bootloader.
All went fine, however, the phone still crashes upon reboot and switches off itself. I did another factory reset via recovery which didn't help. After a restart I usually get back to the blue-LED-thing, but like described above I can access the bootloader again.
So I guess something else is corrupted. Even when I use TWRP instead of stock recovery it crashes after a few seconds after use. What else differs: By holding volume down + power the bootloader doesn't appear immediately, I need to hold for about 10 seconds.
Any ideas?
Hi,
I am not getting Qualcomm 9008 mode even after installing and reinstalling the drivers manually or via setup
I see this under Other Devices in device manager
QHSUSB__BULK
Then I ran miflash it worked fine as per following attached screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But when I unplug device and turn it on it does not show any thing, just a long (2/3 seconds) vibration and done
So basically I cannot get any thing on my screen, Plz help me to get to recovery mode, as if I get till that point
I would be able to flash a proper stock ROM form SD Card
(I have tried the things after removing SD card as well)
it is fixed now
I resolved it, the Diagnostics 9006 mode problem happened to my device twice due to various reasons
in first attempt I was seeing a lot of read only partitions when I connected phone, it was solve using QPST/QFill
before resolving this problem I was able to go to Stock recovery almost all the times but was unable to flash
any thing from there even with the use of SD card
2nd time the problem was same, but this time I was not seeing any partitions in my Computer
actually both times the real problem was going to proper 9008 mode which I finally got to know how to do it from
following thread
http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
I feel I shall put the text as well:
If you were on Lollipop : Phone must be completely off. Pressing �Volume Up�
key plug the USB cable in WITHOUT PRESSING POWER BUTTON ! Port will open.
If you were on Marshmallow : Phone must be completely off. Plug the USB cable in
and immediately press Power On button. Port will open.
Since I bricked from Marshmallow, so I used the Plug in Cable + Power button only to got
to 9008 mode and once there I knew I can make a come back, which yet came after a couple of tries
as one has to click immediately on Download button when Qfil can see 9008.
Actually I bricked my phone a whole lot of times even after my post thats because once I knew that it is just soft bricked and I can get it back somehow, I got the confidence and tried advanced things that bricked my phone again and again
And it was only the recent time (around 3 weeks ago), that I figured the 100% working 9008 method for my phone
actually u have to drain the battery completely out then it will get 9008 mode to do it u shall try turning your phone on again and again so that battery goes off
For example: Press Power button for a few seconds to turn it on.
Or press 3 buttons at same time (VOL+, VOL- and Power), then release only Power button when you get vibration. Then after 2 seconds release both VOL buttons as well (this is for going to recovery mode)
This way you can drain all battery of phone, and you will know when the battery is all gone when you will press the Power button and phone will not show any LED light or screen light, it will just vibrate and will be off
Now you connect ur phone to PC in following way:
If at bricking you you were on Lollipop (Android 5): Pressing VOL+ key and plug the USB cable in WITHOUT PRESSING POWER BUTTON ! 9008 will open use Qfil to flash the ROM u want
OR If at bricking you were on Marshmallow (Android 6): Plug the USB cable in phone, then connect cable to PC and exactly at the same time press power button (some times u dont need to press power button so try with both options). Then if you see 9008 mode in Qfil, then immediately press the Download button in Qfil
If you see Qfil error then repeat the above process to get 9008 mode and use miflash instead of Qfil miflash worked for me better than Qfil from such situation as Qfil often gives error in between
And when you get the flashing 100% then phone will either auto restart or you have to restart it manually Using Qfil it shows u message when it is restarting the phone, and I think using miflash it just says process 100% complete then u have to restart phone yourself
Remember at this point (after restart) connect your phone charger properly in a electricity power socket instead of PC as the battery was already drained so you need to charge the device while it shows the long booting process due to new ROM flashed.
Good luck,
hi guys im having a problem here and would greatly appreciate some help. I have already installed android platform tools and the htc usb drivers. The phone will start in hboot only but will not go to fastboot (power button will not activate fastboot). The pc does not recognize the device either so cant use fastboot commands. Power button + vol up will boot to safe mode but then the os starts acting crazy with the touchscreen being activated all over the place (very annoying). while in safe mode, adb devices command shows that it recognizes the phone but also says unauthorized. What the heck can i do here to get this phone operational again?
What is the history of the device? Was it broken when you got it? Was there any problem with the power button before it started having these problems (only boots to bootloader or safe mode)?
Hey thanks for replying. I got the device new from att around 4 or 5 years ago and have had no problems out of it aside from a badly cracked screen which i replaced myself about 8 months ago. All of the buttons have always worked just fine.
I forgot to mention I unlocked the phone through htc website about 3 years ago and planned on rooting and modding the phone but never got around to it. I can't quite remember if I flashed a custom recovery though. I should also mention the phone got wet before all this started happening (not submerged kind of wet just rained on some )
So I'm assuming ADB sees the device as unauthorized because I'm unable to select OK when the debugging window pops up on the phone. This is due to the OK button being in a dead zone on the touch screen. This zone is the middle half of the screen top to bottom. I'm hoping it's just corrupted firmware and not a physical hardware issue as I mentioned earlier I have already replaced the screen once already.
As for fastboot not recognizing the device, I'm starting to think it's because of this older mini laptop I'm having to use as a backup because my good laptop is being loaned out to someone for a while longer. This mini laptop has 3 usb ports on it but all I believe are usb 1.1 (LOL!). Does fastboot require usb 2.0 or higher to work properly? The phone is visible in Device Manager (both internal and external storage), and I'm able to move files around no problem.
Also, does the sim card have to be in the phone in order to fix the firmware and os? I have the sim in a very basic flip phone right now just so I can make and recieve calls! I need my M8 back badly!
I'm assuming since the phone will actually get to hboot and will also boot into safe mode that this phone is recoverable ie. not bricked. I just need help with doing everything in the right order , so I dont end up doing something very wrong and rendering the device useless. Again thanks for replying and any help you might be able to give would be greatly appreciated!
My responses below in red font:
brokenm8 said:
I should also mention the phone got wet before all this started happening (not submerged kind of wet just rained on some )
Not clear on what you are telling us here. Are you saying that the current condition (stuck in hboot/safe mode) happen directly after it getting wet? Is so, then it would be pretty clear to me, that it is a hardware issue caused by water damage.
So I'm assuming ADB sees the device as unauthorized because I'm unable to select OK when the debugging window pops up on the phone.
You need debugging selected in phone Settings>Developer Options, as well as being able to "OK" the debugging connection request when you are connected to PC. Failing to do either of those, will prevent adb from being used. But I'm not clear on what adb command you want to use. Fastboot and adb should be thought of as 2 related, but different things. For recovering a phone in your condition, fastboot is the one you want.
As for fastboot not recognizing the device, I'm starting to think it's because of this older mini laptop I'm having to use as a backup because my good laptop is being loaned out to someone for a while longer. This mini laptop has 3 usb ports on it but all I believe are usb 1.1 (LOL!). Does fastboot require usb 2.0 or higher to work properly? The phone is visible in Device Manager (both internal and external storage), and I'm able to move files around no problem.
I don't remember USB 1.1 being an issue with adb/fastboot. In fact, it's probably more compatible then USB 3.0, which is known to cause issue with some of the HTC tools. I think I was using an old PC with Windows XP on it, when I first got my M8 (although not sure what type USB ports).
More important, is that fastboot will only work when fastboot mode selected while in bootloader (highlighted in red near the top of the screen). From what I remember, it goes to fastboot mode by default, if you boot into bootloader while the phone is connected to a PC. If not, and you can't select fastboot with the power button, than that is a problem
Also, does the sim card have to be in the phone in order to fix the firmware and os?
SIM card is not needed to fix the OS.
I'm assuming since the phone will actually get to hboot and will also boot into safe mode that this phone is recoverable ie. not bricked. I just need help with doing everything in the right order , so I dont end up doing something very wrong and rendering the device useless.
If the phone is s-on, there isn't much you can do, that is not reversible, or will make the condition worse. But as you said, it's best to follow specific instructions as we give them to you.
Click to expand...
Click to collapse
Not clear on what you are telling us here. Are you saying that the current condition (stuck in hboot/safe mode) happen directly after it getting wet? Is so, then it would be pretty clear to me, that it is a hardware issue caused by water damage.
Click to expand...
Click to collapse
Yes the current condition happened directly after getting wet.
More important, is that fastboot will only work when fastboot mode selected while in bootloader (highlighted in red near the top of the screen). From what I remember, it goes to fastboot mode by default, if you boot into bootloader while the phone is connected to a PC. If not, and you can't select fastboot with the power button, than that is a problem
Click to expand...
Click to collapse
Mine doesn't go into fastboot by default when booted into bootloader while connected to PC. While at the HBOOT main screen, Fastboot is at the top of the list of options available to select followed by Recovery, Factory Reset, etc... The power button does not activate any of the options in HBOOT but it works just fine to power the phone on or off and in combination with the Vol Up button to boot the OS which always goes into safemode. However, the Vol Down button doesn't work anywhere. This seems to indicate to me that HBOOT and/or the firmware might be corrupted? As I mentioned earlier, I am able to move files around with no problem. Pretty sure I can't put a RUU into the root directory and fix this because I'm unable to relock the bootloader due to fastboot not working right? If so, is there a way to load/flash a good copy of HBOOT and/or firmware to the phone via my sd card?
brokenm8 said:
However, the Vol Down button doesn't work anywhere. This seems to indicate to me that HBOOT and/or the firmware might be corrupted?
Click to expand...
Click to collapse
I'd say that is a big leap of logic, and probably not a correct one. Hboot is required for the very basic functioning of the phone. Hboot corruption usually equals hard brick (screen won't even come on).
I'd say it's more likely the water damage caused hardware failure of the vol down button.
brokenm8 said:
Pretty sure I can't put a RUU into the root directory and fix this because I'm unable to relock the bootloader due to fastboot not working right? If so, is there a way to load/flash a good copy of HBOOT and/or firmware to the phone via my sd card?
Click to expand...
Click to collapse
You can only flash RUU or firmware with an unlocked bootloader, if the device is s-off.
You also can't flash hboot separately unless you have s-off. You can flash firmware, which contains hboot. But again, unless you have s-off or can relock the bootloader, you can't flash firmware.
Hi there
I got the same exact problem with my m8. At the screen telling : s-on, locked..., the power button and the vol down button are not working, the vol up button is scrolling down instead of scrolling up. It appears that I am stuck in Hboot only I can't use fastboot or any other option. This is the second time I am facing that problem. The first time, I have replaced the motherboard, but since then I didn't flash any rom or done any mod on my htc and here I am now with the same mess.
Glasskeramika said:
I got the same exact problem with my m8.
Click to expand...
Click to collapse
Did you drop it in water, like the OP?
I would suggest anyone refrain from saying you have the "exact same problem" on this forum. I've seen that phrase (or similar) posted dozens (probably hundreds) of times. And not once, have I found (after digging for details) that statement to actually be true. Way too many variables in phone versions, software, what was done to it, etc.
Your time is much better spent giving specific details on the phone, and letter us go from there.
I did not drop in the water.
It went off after battery fully drained. When I tried to turn it on after I plugged it in my computer to charge it, the screen in the attachment showed off. It does show options like fastboot, recovery..etc, but I can't select any of them : the power button (on that screen) doesn't work but it does turn on my phone, the volume down button doesn't work at all (neither on safe mode nor on the attached screen). The vol up button works good when it's running on safe mode, but it plays the role of the vol down button once on that screen (it scrolls down instead of scrolling up).
I need to mention that I had that problem (the same exact haha) two years ago when I rooted my htc m8. Everything was just fine till one day, my phone suddenly started lagging a lot. When I tried to reboot it, that famous screen showed off. I took it to a guy who has replaced the motherboard :crying:. The phone was doing good, I didn't mod anything or rooted it, but it wasn't recognizing the second camera (once on the htc's camera app, it says that my finger is hiding the second camera). But everything was all good for about 1 year, till I got that problem again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 08:09 AM ---------- Previous post was at 07:54 AM ----------
Glasskeramika said:
I did not drop in the water.
It went off after battery fully drained. When I tried to turn it on after I plugged it in my computer to charge it, the screen in the attachment showed off. It does show options like fastboot, recovery..etc, but I can't select any of them : the power button (on that screen) doesn't work but it does turn on my phone, the volume down button doesn't work at all (neither on safe mode nor on the attached screen). The vol up button works good when it's running on safe mode, but it plays the role of the vol down button once on that screen (it scrolls down instead of scrolling up).
I need to mention that I had that problem (the same exact haha) two years ago when I rooted my htc m8. Everything was just fine till one day, my phone suddenly started lagging a lot. When I tried to reboot it, that famous screen showed off. I took it to a guy who has replaced the motherboard :crying:. The phone was doing good, I didn't mod anything or rooted it, but it wasn't recognizing the second camera (once on the htc's camera app, it says that my finger is hiding the second camera). But everything was all good for about 1 year, till I got that problem again.
Click to expand...
Click to collapse
Link (remove all space, please) to the mentioned screen : https: // imgur. com/a/yPY Z4rX
(The image doesn't appear in the previous post that I couldn't edit, oh yeah spam )
Unable to boot into recovery or Download mode on Samsung Note10 Plus SM-N975F Exynos version. I usually remove/bypass FRP (google account) on devices for customers.
I have a customer's Note10plus devices which is still on pincode lock screen trying to hard reset and remove FRP but can't enter into recovery mode. Tried to enter into download to flash with new firmware but unable to boot into download mode either. Looks like the device is remotely locked via Find my mobile which is preventing to hard reset the device, anyone knows about any new security feature ?
RECOVERY MODE:
1: Begining the process by holding the Volume Down + Power key in order to shut off the phone.
2: As soon as the phone is off, hold the Volume Up and Power button till the Samsung logo appears
3: Let go of held buttons when the SAMSUNG Galaxy logo pops up.
4: At this moment i should be seeing the Recovery mode but no its rebooting and getting error : "[PDP] backup fail: setup-wizard finish"
I'm a pro in rebooting devices into recovery and download mode usually get success in first attempt but sometime have to try 2-3 times as well as timing is the key in pressing and holding the combination of keys so surely not the timing issue on this devices.
Can't even use the ADB method as well coz the device is on lock screen, Can't enable USB debugging or see the pop-up on screen to enable it due to being on lock screen.
.\ADB DEVICES - Not reading or showing the connected Note10plus via the official USB cable.
Any help or information would be very helpful and highly appreciated Thanks.
This don't even make sense. If the customer can log in on the pc and lock the screen and such they can also log in and remove it. This whole shebang seems shady and more than likely you will find no help here. Most of us do not support bypassing of frp especially since you stated the customer obviously has access to the device in some form
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It is with the legitimate owner i guess but when they are entering the pin code its coming up with the error " [PDP] back-up:fail setup-wizard [FINISH]" as per the image attached.
Click to expand...
Click to collapse
I have that PDP toast message also when trying to enter recovery mode etc. No pin or passwords are set on my device.
arshad926 said:
Unable to boot into recovery or Download mode on Samsung Note10 Plus SM-N975F Exynos version. I usually remove/bypass FRP (google account) on devices for customers.
I have a customer's Note10plus devices which is still on pincode lock screen trying to hard reset and remove FRP but can't enter into recovery mode. Tried to enter into download to flash with new firmware but unable to boot into download mode either. Looks like the device is remotely locked via Find my mobile which is preventing to hard reset the device, anyone knows about any new security feature ?
RECOVERY MODE:
1: Begining the process by holding the Volume Down + Power key in order to shut off the phone.
2: As soon as the phone is off, hold the Volume Up and Power button till the Samsung logo appears
3: Let go of held buttons when the SAMSUNG Galaxy logo pops up.
4: At this moment i should be seeing the Recovery mode but no its rebooting and getting error : "[PDP] backup fail: setup-wizard finish"
I'm a pro in rebooting devices into recovery and download mode usually get success in first attempt but sometime have to try 2-3 times as well as timing is the key in pressing and holding the combination of keys so surely not the timing issue on this devices.
Can't even use the ADB method as well coz the device is on lock screen, Can't enable USB debugging or see the pop-up on screen to enable it due to being on lock screen.
.\ADB DEVICES - Not reading or showing the connected Note10plus via the official USB cable.
Any help or information would be very helpful and highly appreciated Thanks.
Click to expand...
Click to collapse
Samsung recently changed the download mode entry process.
1. Power down device
2. Hold volume down/up buttons and keep them pressed
3. Connect phone to a pc using usbc cable
dezborders said:
Samsung recently changed the download mode entry process.
1. Power down device
2. Hold volume down/up buttons and keep them pressed
3. Connect phone to a pc using usbc cable
Click to expand...
Click to collapse
Plug the phone into a pc with USB -c cacble whilst the phone is on and you inside of windows, in other word you need to be logged into windows 10.
Power off the phone (keep cable plugged in and pc on at all times)
Hold Volume Up + Power Button until you get into recovery mode.
plug in the official earphone the original one from the box, then try to enter to the recovery mode
Limeybastard said:
I have that PDP toast message also when trying to enter recovery mode etc. No pin or passwords are set on my device.
Click to expand...
Click to collapse
plug in the official earphone the original one from the box, then try to enter to the recovery mode
godsboy7777 said:
Plug the phone into a pc with USB -c cacble whilst the phone is on and you inside of windows, in other word you need to be logged into windows 10.
Power off the phone (keep cable plugged in and pc on at all times)
Hold Volume Up + Power Button until you get into recovery mode.
Click to expand...
Click to collapse
THX mate worked )
dezborders said:
Samsung recently changed the download mode entry process.
1. Power down device
2. Hold volume down/up buttons and keep them pressed
3. Connect phone to a pc using usbc cable
Click to expand...
Click to collapse
Thanks man... It worked
After the second android 11 update, "recovery mode" can be accessed as follows: turn off the phone, wait 10 sec. , connect it to the laptop with the USB-C cable. After the battery percentage appears, press BIXBY + VOLUME UP + POWER BUTTON. When the logo appears, release VOLUME UP and POWER BUTTON and press VOLUME DOWN without releasing the BIXBY button.
same thing was happending with my s10 plus my google maps and youtbe werent working video will work to 6 seconds and stop workling maps wont show routes when searching. couldnt get into recov mode as didnt know the new procedure this helped so much than you so much man
Silviu001 said:
After the second android 11 update, "recovery mode" can be accessed as follows: turn off the phone, wait 10 sec. , connect it to the laptop with the USB-C cable. After the battery percentage appears, press BIXBY + VOLUME UP + POWER BUTTON. When the logo appears, release VOLUME UP and POWER BUTTON and press VOLUME DOWN without releasing the BIXBY button.
Click to expand...
Click to collapse
Can't be right as Bixby button = Power button...
TheMadScientist said:
This don't even make sense. If the customer can log in on the pc and lock the screen and such they can also log in and remove it. This whole shebang seems shady and more than likely you will find no help here. Most of us do not support bypassing of frp especially since you stated the customer obviously has access to the device in some form
Click to expand...
Click to collapse
Can someone here plese help me. Easter Sunday I get a text gif from my Sister and now I cant do anything with my S9. I read here about plugging S9 into windows machine but that scares me. I'm ready to call it quits with Samsung. This is the second device in a few years that has locked up on me. Could this be a hack or maleware? The new login feature for widows that includes a pin didnt work today either. I can get into windows fine with password. I did go to Google find my device and a map shows Africas west coast. HELP
In s10 plus i can't yet insert in recovery mode...Turn off the device, after the buttons combination Power button+Volume up+Bixby button and inserting usb cable in laptop doesn't insert in recovery mode and when open normally is displayed the error " [PDP] back-up:fail setup-wizard [FINISH]"
Any solution in this problem.......?
Hi, I have a similar problem. My Note 10+ stuck at bootloader page and will not power down. I could not use normal procedures to go to download or recovery mode. I drained off my Note's battery but once I plug the charger back to charge its battery. The bootloader page shows up. Any suggestions that can resolve this problem? I attached a screenshot here. Thanks in advance.
user109 said:
Hi, I have a similar problem. My Note 10+ stuck at bootloader page and will not power down. I could not use normal procedures to go to download or recovery mode. I drained off my Note's battery but once I plug the charger back to charge its battery. The bootloader page shows up. Any suggestions that can resolve this problem? I attached a screenshot here. Thanks in advance.
Click to expand...
Click to collapse
Hey there,
I've got some possibly important questions:
Does the Samsung logo show up on boot?
How did you try to boot into download- or recovery-mode, specifically did you press the power- and volume buttons to boot, just pressed the volume buttons, with/without plugged-in USB cable?
Does ADB/Fastboot/Odin/Heimdall/Smart Switch or anything recognize your device?
Any idea of what had been flashed onto the phone?
Does the battery percentage thingy show up when you plug a charger into the phone?
Have a nice morning/afternoon/evening.
Cheers
user109 said:
Hi, I have a similar problem. My Note 10+ stuck at bootloader page and will not power down. I could not use normal procedures to go to download or recovery mode. I drained off my Note's battery but once I plug the charger back to charge its battery. The bootloader page shows up. Any suggestions that can resolve this problem? I attached a screenshot here. Thanks in advance.
Click to expand...
Click to collapse
Does it boot if you press the power button from that screen.
I believe that screen appears after bootloader has been unlocked....which probably means device is rooted.
You should be able to boot into the system by tapping the power button from that screen.
Nic0_ said:
Hey there,
I've got some possibly important questions:
Does the Samsung logo show up on boot?
How did you try to boot into download- or recovery-mode, specifically did you press the power- and volume buttons to boot, just pressed the volume buttons, with/without plugged-in USB cable?
Does ADB/Fastboot/Odin/Heimdall/Smart Switch or anything recognize your device?
Any idea of what had been flashed onto the phone?
Does the battery percentage thingy show up when you plug a charger into the phone?
Have a morning/afternoon/evening.
Cheers
Click to expand...
Click to collapse
Hi,
I have tried every methods that I could think of. I left it drain the battery three days ago and once I plugged in my phone charger and immediately it show this screen. The only way i can do is press vol dwn + power, it rebooted and came back to this screen again. No metter how many times I "reboot" it still come back this.
The last flash i did was used the odin to flashed the Magisk in "AP" cause I lost my root for some reason. I followed Magisk instruction to create a patching tar from the phone itself. Then re-flashed with odin. My Rom was using "N975FXXU6FUCD". After odin prompted "pass" and I left it to reboot. It usually will show this screen a while after rebooted.( normally it'll take around 45 sec to full boot but not this time.) No boot to Android page after left it about 10 minutes thought it still initialize.
I left it almost half an hour and phone still show the bootloader page. What i did was try to reboot or power off by press power button. I couldn't power off it even i hold the button for about 15 sec. Next move I just tried press vol up + power , vol down + power, insert USB plug while holding the vol up + dwn + power. I tried the combination of buttons and last I left it to drain out power.
I'll try if any other suggestions. I don't think there's a reset button unless open out its case..
user109 said:
Hi,
I have tried every methods that I could think of. I left it drain the battery three days ago and once I plugged in my phone charger and immediately it show this screen. The only way i can do is press vol dwn + power, it rebooted and came back to this screen again. No metter how many times I "reboot" it still come back this.
The last flash i did was used the odin to flashed the Magisk in "AP" cause I lost my root for some reason. I followed Magisk instruction to create a patching tar from the phone itself. Then re-flashed with odin. My Rom was using "N975FXXU6FUCD". After odin prompted "pass" and I left it to reboot. It usually will show this screen a while after rebooted.( normally it'll take around 45 sec to full boot but not this time.) No boot to Android page after left it about 10 minutes thought it still initialize.
I left it almost half an hour and phone still show the bootloader page. What i did was try to reboot or power off by press power button. I couldn't power off it even i hold the button for about 15 sec. Next move I just tried press vol up + power , vol down + power, insert USB plug while holding the vol up + dwn + power. I tried the combination of buttons and last I left it to drain out power.
I'll try if any other suggestions. I don't think there's a reset button unless open out its case..
Click to expand...
Click to collapse
Hey there,
With my N10, the combination for getting into Odin-mode is vol-up + vol-down and having a cable plugged in to a computer. Please try "rebooting" your phone (while having it plugged into your computer) and immediately after the screen goes blank, press vol-up + vol-down (without the power button).
I would recommend first trying to flash the full stock ROM (AP, BL and everything else you get) and if it boots, try modding it again.
Have a nice morning/afternoon/evening.
Cheers