Related
hi all
i have htc one m8, unlocked rooted i had previousl had viperOne rom installed and decided to change to Sky Dragon ... i wiped all the data system sd card etc and then proceeded to install the rom, installed the rom and then rebooted, recovery asked root access seems missing so i clicked no to install root access and now it is stuck on the htc screen with the this build is for dev purposes in red and now i cant get into recovery or bootloader ? what to dooooo
MrH871 said:
hi all
i have htc one m8, unlocked rooted i had previousl had viperOne rom installed and decided to change to Sky Dragon ... i wiped all the data system sd card etc and then proceeded to install the rom, installed the rom and then rebooted, recovery asked root access seems missing so i clicked no to install root access and now it is stuck on the htc screen with the this build is for dev purposes in red and now i cant get into recovery or bootloader ? what to dooooo
Click to expand...
Click to collapse
i think their is no OS installed but i still should be able to access bootloader/recovery ?
MrH871 said:
i think their is no OS installed but i still should be able to access bootloader/recovery ?
Click to expand...
Click to collapse
I've had similar issues earlier today. Read my thread, maybe it'll help.
http://forum.xda-developers.com/showthread.php?t=2759524
EDIT: If the screen 'hangs' press power button + volume up, wait for the screen to turn black and press volume down. That should get you into your bootloader!
Niorun said:
I've had similar issues earlier today. Read my thread, maybe it'll help.
http://forum.xda-developers.com/showthread.php?t=2759524
EDIT: If the screen 'hangs' press power button + volume up, wait for the screen to turn black and press volume down. That should get you into your bootloader!
Click to expand...
Click to collapse
Need some help daorderdillon...I have an HTC One M8
I wanted to flash to the UNROOTED Google Play Edition...so I rooted, TWRP'ed and did the S-OFF
and then tried to flash the ROM while in RUU mode...it gave me back a "41 error"...
so I tried to change the ModelID in the android.txt file...flashed, and then my HTC One M8 kept going into the HTC logo screen with 4 triangle error screen
When I do fastboot oem reboot, it gets me back into the device - but any normal restart after, and I'm back in the HTC logo error screen
I can't go into recovery mode either - using the POWER and UP / DOWN buttons or through the software...
Stuck, and I really don't know what to do
Thanks in advance!
wikwikwik said:
Need some help daorderdillon...I have an HTC One M8
I wanted to flash to the UNROOTED Google Play Edition...so I rooted, TWRP'ed and did the S-OFF
and then tried to flash the ROM while in RUU mode...it gave me back a "41 error"...
so I tried to change the ModelID in the android.txt file...flashed, and then my HTC One M8 kept going into the HTC logo screen with 4 triangle error screen
When I do fastboot oem reboot, it gets me back into the device - but any normal restart after, and I'm back in the HTC logo error screen
I can't go into recovery mode either - using the POWER and UP / DOWN buttons or through the software...
Stuck, and I really don't know what to do
Thanks in advance!
Click to expand...
Click to collapse
Have you tried flashing a stock recovery via fastboot? Or flash TWRP again then flash a stock nandroid backup from the backup/recovery thread?
m8 white screen
Good evening community
I think I bricked my M8. Tryed to flash a custom ROM, unrooted and installed it but didn't liked and decided to go back to stock ROM. Went to TWRP and wiped one position more than needed - data. So now my M8 booted just into white screen with HTC logo, power off doesn't work at all, hard reset combination doesn't work, power on + volume up - doesn't work. It's always on and CMD says <waiting for device>
Who can help me?
Thank you in advance
Edit: got into bootloader, thanks to Niorun post edit.
djstammo said:
I think I bricked my M8.
Click to expand...
Click to collapse
For this phone, as long as the screen comes on, its almost certainly not bricked.
Being stuck with OS not booting is a common thing when flashing ROMs. It just happens from time to time for one reason or other. Folks that freak out about this (and think their phone is bricked) need to relax and learn some basic recovery steps.
djstammo said:
Went to TWRP and wiped one position more than needed - data. So now my M8 booted just into white screen with HTC logo
Click to expand...
Click to collapse
Wiping data will not make the phone get stuck on the HTC logo screen. Wiping data just erases user data. So the phone would have just booted into the OS, but with no previous user data present any longer. Failure to boot was for some other reason.
djstammo said:
power off doesn't work at all, hard reset combination doesn't work, power on + volume up - doesn't work. It's always on and CMD says <waiting for device>
Click to expand...
Click to collapse
Power + Vol Up reboots the phone, this should always function as long as the screen comes on.
Power + Vol Down to boot into bootloader similarly should always work as long as the screen comes on. Failure to do so is almost always a matter of user error, not performing the button combo correctly (either not pressing vol down fast enough, or letting go of it too early).
Power + Volume Down
So, in response to
Power + Vol Up reboots the phone, this should always function as long as the screen comes on.
Power + Vol Down to boot into bootloader similarly should always work as long as the screen comes on. Failure to do so is almost always a matter of user error, not performing the button combo correctly (either not pressing vol down fast enough, or letting go of it too early).
Click to expand...
Click to collapse
Pressing Power + Vol Up does show the HTC screen for me, then it goes black.
Pressing Power + Vol down doesn't do anything.
Am I following the instructions correctly?
CBribiescas said:
Pressing Power + Vol Up does show the HTC screen for me, then it goes black.
Pressing Power + Vol down doesn't do anything.
Am I following the instructions correctly?
Click to expand...
Click to collapse
Try it this way:
1) Reboot the phone using Power+Vol Up
2) The moment the screen goes dark to reboot and before the white HTC logo screen appears, let go of the buttons, and hold the Vol down button. Do not let go of vol down until you see the bootloader screen
3) If the bootloader doesn't appear, you either started pressing Vol Down too late, or let go of it too early. Just do the steps again until you get it right.
Clarification
I have to anticipate when the screen is going go from black to showing the white HTC logo? Then do vol down then?
htc m8 brick
i too am having issues with a bricked htc 0ne m8. We purchased the phone as-is really cheap. its freezes while booting up. i can get into fastboot and recovery just fine. i have been successful in installing ruu files but the ruu file doesn't fix the "boot loop" freeze at startup issue. The device is s-on still which sucks because i can't find a method of achieving s-off in fastboot mode. i was able to unlock the bootloader, hoping that it would help and now the ruu files won't work anyone. now i can't get the bootloader to lock through the method that htcdev.com tells me to use. ive also tried to install update through adb sideload through recovery without success.
so i have a s-on, unlocked bootloader htc m8 that i still can't get it to boot up.
any help would be appreciated.
redpoint73 said:
Try it this way:
1) Reboot the phone using Power+Vol Up
2) The moment the screen goes dark to reboot and before the white HTC logo screen appears, let go of the buttons, and hold the Vol down button. Do not let go of vol down until you see the bootloader screen
3) If the bootloader doesn't appear, you either started pressing Vol Down too late, or let go of it too early. Just do the steps again until you get it right.
Click to expand...
Click to collapse
It works perfectly. thanks!
CBribiescas said:
I have to anticipate when the screen is going go from black to showing the white HTC logo? Then do vol down then?
Click to expand...
Click to collapse
I just timed it (in my head, not with a stopwatch), and you have about 3 seconds while the screen is black, before the HTC logo screen appears. Plenty of time to let go of the power and vol up buttons, and hold the vol down button.
The reason I say "the moment the screen goes dark" is that some folk wait too long, and start pressing vol down when the HTC logo screen is already up. By then, its too late.
---------- Post added at 10:53 AM ---------- Previous post was at 10:41 AM ----------
w0dan812 said:
i too am having issues with a bricked htc 0ne m8. We purchased the phone as-is really cheap. its freezes while booting up. i can get into fastboot and recovery just fine. i have been successful in installing ruu files but the ruu file doesn't fix the "boot loop" freeze at startup issue. The device is s-on still which sucks because i can't find a method of achieving s-off in fastboot mode. i was able to unlock the bootloader, hoping that it would help and now the ruu files won't work anyone. now i can't get the bootloader to lock through the method that htcdev.com tells me to use. ive also tried to install update through adb sideload through recovery without success.
so i have a s-on, unlocked bootloader htc m8 that i still can't get it to boot up.
Click to expand...
Click to collapse
Need more info.
What hboot number?
What radio numer?
What CID (or original carrier version)?
What RUUs did you try?
Don't know what method HTCDev says to relock the bootloader, but as long as you can still get into fastboot mode, its simply the command: fastboot oem lock
Also, there is no other currently working s-off method aside from sunshine (which requires booting into OS) so you can stop looking for one.
I "Softbricked" my htc one m8 AT&T
i recently rooted it and made 4 back ups. I deleted two of them and tried to roboot to fastboot. but it says 'No OS installed" . My computers reconize it as a disk drive and when i click on it, it asks me to insert a disk...Please, ANYONE with information that will help, share
Craz Basics said:
i recently rooted it and made 4 back ups. I deleted two of them and tried to roboot to fastboot. but it says 'No OS installed" . My computers reconize it as a disk drive and when i click on it, it asks me to insert a disk...Please, ANYONE with information that will help, share
Click to expand...
Click to collapse
Download a ROM on your PC, transfer it to your extSD, put that in your phone and flash it in recovery.
MrH871 said:
hi all
i have htc one m8, unlocked rooted i had previousl had viperOne rom installed and decided to change to Sky Dragon ... i wiped all the data system sd card etc and then proceeded to install the rom, installed the rom and then rebooted, recovery asked root access seems missing so i clicked no to install root access and now it is stuck on the htc screen with the this build is for dev purposes in red and now i cant get into recovery or bootloader ? what to dooooo
Click to expand...
Click to collapse
Well, you say you can't get in the bootloader or recovery, have you tried to hold down the power button and volume up button, and then when the screen goes off switch to power and volume down? That should take you to your bootloader! If you can get there I would guess you would have a backup in recovery
---------- Post added at 10:01 AM ---------- Previous post was at 09:58 AM ----------
w0dan812 said:
i too am having issues with a bricked htc 0ne m8. We purchased the phone as-is really cheap. its freezes while booting up. i can get into fastboot and recovery just fine. i have been successful in installing ruu files but the ruu file doesn't fix the "boot loop" freeze at startup issue. The device is s-on still which sucks because i can't find a method of achieving s-off in fastboot mode. i was able to unlock the bootloader, hoping that it would help and now the ruu files won't work anyone. now i can't get the bootloader to lock through the method that htcdev.com tells me to use. ive also tried to install update through adb sideload through recovery without success.
so i have a s-on, unlocked bootloader htc m8 that i still can't get it to boot up.
any help would be appreciated.
Click to expand...
Click to collapse
As I said in another post. Try holding down the power button and volume up button, then when it turns off switch to power and volume down! That should take you to bootloader.
---------- Post added at 10:08 AM ---------- Previous post was at 10:01 AM ----------
redpoint73 said:
I just timed it (in my head, not with a stopwatch), and you have about 3 seconds while the screen is black, before the HTC logo screen appears. Plenty of time to let go of the power and vol up buttons, and hold the vol down button.
The reason I say "the moment the screen goes dark" is that some folk wait too long, and start pressing vol down when the HTC logo screen is already up. By then, its too late.
---------- Post added at 10:53 AM ---------- Previous post was at 10:41 AM ----------
Need more info.
What hboot number?
What radio numer?
What CID (or original carrier version)?
What RUUs did you try?
Don't know what method HTCDev says to relock the bootloader, but as long as you can still get into fastboot mode, its simply the command: fastboot oem lock
Also, there is no other currently working s-off method aside from sunshine (which requires booting into OS) so you can stop looking for one.
Click to expand...
Click to collapse
Try this, this is what I did to unlock and root mine along with installing twrp. You can change your recovery and relock the bootloader. It has an option to switch to s-off but idk if it works
http://forum.xda-developers.com/showthread.php?t=2699065
---------- Post added at 11:07 AM ---------- Previous post was at 10:08 AM ----------
wikwikwik said:
Need some help daorderdillon...I have an HTC One M8
I wanted to flash to the UNROOTED Google Play Edition...so I rooted, TWRP'ed and did the S-OFF
and then tried to flash the ROM while in RUU mode...it gave me back a "41 error"...
so I tried to change the ModelID in the android.txt file...flashed, and then my HTC One M8 kept going into the HTC logo screen with 4 triangle error screen
When I do fastboot oem reboot, it gets me back into the device - but any normal restart after, and I'm back in the HTC logo error screen
I can't go into recovery mode either - using the POWER and UP / DOWN buttons or through the software...
Stuck, and I really don't know what to do
Thanks in advance!
Click to expand...
Click to collapse
If it is rooted, you can download a app that should take you to recovery. I think ROM toolbox is one. Hope this helps good luck. I'm here if you need me
AndroidEducator said:
Hope this helps good luck. I'm here if you need me
Click to expand...
Click to collapse
Do you realize you are responding to old posts, the most recent of which is over 3 months old?
You also responded to my post, as if I was having an issue. I was the one giving help/advice.
---------- Post added at 09:51 AM ---------- Previous post was at 09:48 AM ----------
AndroidEducator said:
. It has an option to switch to s-off but idk if it works
Click to expand...
Click to collapse
It doesn't. The tool is very outdated, and I typically (virtually always) recommend against using it for that reason. The toolkit uses the old firewater s-off method, which hasn't worked since December 2014.
When I said there is no other working s-off method besides sunshine (and to stop looking for one), it was a statement of fact, not a guess.
I need some help, I have a m8 rooted and to make an update from htc (I have te stock rom) I have flash de stock recovery (te old one was the twrp) but now after the update de phone is stuck in the htc logo, I can enter in the fastboot but I dont know what to do and what direction I should take
Follow my steps if your phone is not booting up.
1. Lock bootloader if you have unlocked bootloader.
2. Download HTC One M8 4.16.401.10 Stock Lollipop RUU [0P6BIMG] ( search google because I can not post link since I am new forum member).
3. Rename the downloaded RUU to 0P6BIMG and send the zip file to your phone SD Card.
3.Reboot your phone in to the bootloader mode by powering off the phone and rebooting with Power button and volume down or use fastboot mode command : adb reboot-bootloader.
-This way our phone will automatically detect the RUU file that you pasted in SD card (step 3) and flash it.
Your HTC One M8 is alive
W_KuP said:
I need some help, I have a m8 rooted and to make an update from htc (I have te stock rom) I have flash de stock recovery (te old one was the twrp) but now after the update de phone is stuck in the htc logo, I can enter in the fastboot but I dont know what to do and what direction I should take
Click to expand...
Click to collapse
g510 said:
Follow my steps if your phone is not booting up.
1. Lock bootloader if you have unlocked bootloader.
2. Download HTC One M8 4.16.401.10 Stock Lollipop RUU [0P6BIMG] ( search google because I can not post link since I am new forum member).
3. Rename the downloaded RUU to 0P6BIMG and send the zip file to your phone SD Card.
3.Reboot your phone in to the bootloader mode by powering off the phone and rebooting with Power button and volume down or use fastboot mode command : adb reboot-bootloader.
-This way our phone will automatically detect the RUU file that you pasted in SD card (step 3) and flash it.
Your HTC One M8 is alive
Click to expand...
Click to collapse
The advice given here is good, except it assumes too many things. There is the assumption of S-On, and of current firmware version. Also, if you are using ADB to reboot to bootloader, the user might as well fastboot flash the RUU.zip, or run the RUU.exe that is also available.
@W_KuP, Post the results of fastboot getvar all (edit out your IMEI and serial# ~ that's private info)
If you are indeed on WWE/International firmware, that RUU.zip will work for you. Download link here.
If you are S-On, you will need to relock your bootloader first. In fastboot: fastboot oem lock. If you are S-Off there is no need to relock your bootloader.
i just bricked my M8 (stock 4.4.2 just rooted)
i rooted my phone so i couldn't get OTA updated to i tried to use "[GUIDE] How to add root access & and keep official OTA updates | 3.28.401.9"
but after i flashed boot.img using fastboot flash boot boot.img command in the fastboot mode the phone stuck on boot screen (HTC logo boot up screen) even after i heard the rom sound load up
now i can't even restart my phone to be able to access the boot menu
i tried to use Android Revolution HD rom to i use their "Flash_recovery_3.28.401.7" now i can't even log into recovery "i wait to the battery is empty to be able to access boot menu :crying
any help plzzzzz :crying:
thx in advance
sahmeds said:
i just bricked my M8 (stock 4.4.2 just rooted)
i rooted my phone so i couldn't get OTA updated to i tried to use "[GUIDE] How to add root access & and keep official OTA updates | 3.28.401.9"
but after i flashed boot.img using fastboot flash boot boot.img command in the fastboot mode the phone stuck on boot screen (HTC logo boot up screen) even after i heard the rom sound load up
now i can't even restart my phone to be able to access the boot menu
i tried to use Android Revolution HD rom to i use their "Flash_recovery_3.28.401.7" now i can't even log into recovery "i wait to the battery is empty to be able to access boot menu :crying
any help plzzzzz :crying:
thx in advance
Click to expand...
Click to collapse
Well that's one of the perks of flashing a 3.xx.xxx.x ROM on 1.xx.xxx.x(4.4.2) firmware. You get to have extremely long boot up times and you won't have a proper working radio which leaves you with no wifi, data, gps, bluetooth...
Your OTA probably didn't work because of a custom recovery, not because it was rooted. Root does NOT prevent OTA updates from installing, though you might lose root access after the OTA.
If you're stuck at Boot screen hold Volume UP + Power button for 10seconds, as soon as the screen goes black press volume Down + Power button to enter into Bootloader.
Flash a custom recovery like TWRP. Go into recovery and restore a nandroid backup for your device.
first thx alot for replaying
i already got TWRP installed but the screen is stock on boot screen but still manage on the back ground to load my current rom as i'm hearing the log in sound of the rom :S
so i tried to power it off without seeing by holding the power key the power option pop up and touching random parts of the screen but i failed
i even waited for the battery to empty and factory reset the phone with no use
is these is any way even by adb to power off my phone
plzzz help
thx again for replaying
sahmeds said:
first thx alot for replaying
i already got TWRP installed but the screen is stock on boot screen but still manage on the back ground to load my current rom as i'm hearing the log in sound of the rom :S
so i tried to power it off without seeing by holding the power key the power option pop up and touching random parts of the screen but i failed
i even waited for the battery to empty and factory reset the phone with no use
is these is any way even by adb to power off my phone
plzzz help
thx again for replaying
Click to expand...
Click to collapse
By the look of things you are booted in OS but have no screen, hence why try and hold power button in and randomly tap to shut off?
I told you already to Hold Volume UP + Power button for about 10seconds and then hold volume down + power to enter bootloader.
You can of course also just plug it in and try to reboot to bootloader using adb, if you have USB debugging enabled. adb reboot bootloader
As already said just hold power and volume up for around 12 seconds then immediately press and hold power and volume down. This will always get you into the boot loader.
However if adb is working just use the command above. Reflash the original boot.img and you should be good.
ashyx said:
As already said just hold power and volume up for around 12 seconds then immediately press and hold power and volume down. This will always get you into the boot loader.
However if adb is working just use the command above. Reflash the original boot.img and you should be good.
Click to expand...
Click to collapse
ya power and volume up worked for me thx
i flashed the boot.img using adb and stock recovery that make it don't even continue to the rom but hang up
so i installed twrp-2.8.0.1 so now i got recovery working but i still can't get in the rom as it's still no screen
must it install a new rom or can you give me a stock boot.img (may be mine have an issue)
and if i need to install a new rom can u recommend one for me (just direct me to the link)
thx again now i got a new hope
http://forum.xda-developers.com/showthread.php?t=2701376
Use that to get back to the stock rom for your phone. Then after installing the right one, get the OTA
sahmeds said:
ya power and volume up worked for me thx
i flashed the boot.img using adb and stock recovery that make it don't even continue to the rom but hang up
so i installed twrp-2.8.0.1 so now i got recovery working but i still can't get in the rom as it's still no screen
must it install a new rom or can you give me a stock boot.img (may be mine have an issue)
and if i need to install a new rom can u recommend one for me (just direct me to the link)
thx again now i got a new hope
Click to expand...
Click to collapse
Never leave your device with an empty battery. In any circumstances.
Because you might not be able to charge it. Recover the device while you have some power on your battery.
Remember, this is a unibody device. It's not so easy to pull out the battery.
I have a F400K G3 (Korean Olleh). It's rooted and bumped. I flashed the bumped TWRP image via Flashify and rebooted recovery via Flashify. It works. But when I try boot to recovery from a complete shutdown. It just boots into safe mode. I did exactly what was stated in the Bump thread (Power+V. Down, when logo appears, release then press again quickly) and also tried substituting V. Down button with V. Up, but it still wont boot to recovery. It just keeps going into safe mode. The video provided in the thread was using an AT&T model so maybe it differs from every variant. I want to know if I'm doing something wrong or the instructions are wrong.
Thank you.
You tried without releasing? Just keep holding buttons
---------- Post added at 11:38 AM ---------- Previous post was at 11:37 AM ----------
Do you get to that factory reset screen?
DelBoy said:
You tried without releasing? Just keep holding buttons
---------- Post added at 11:38 AM ---------- Previous post was at 11:37 AM ----------
Do you get to that factory reset screen?
Click to expand...
Click to collapse
I have tried it as well without releasing. Does the same thing. And it never shows the reset screen. It just goes directly to the boot animation. Rebooting from Flashify also doesn't show the reset screen but it does get to TWRP. But I need to boot it from complete shutdown because I'm gonna test a Flashable zip ROM without root so rebooting using Flashify would be impossible.
Bump.
Seriously. Anyone?
I am subscribing because I have the exact same problem. I have tried every key combination I could find for the G2 and G3 but no luck...
This is exactly the kind of problems you get when using stuff like Flashify. The holding of the buttons etc you mentioned should work. Are you sure you aren't connected using a micro usb?
sprremix said:
This is exactly the kind of problems you get when using stuff like Flashify. The holding of the buttons etc you mentioned should work. Are you sure you aren't connected using a micro usb?
Click to expand...
Click to collapse
No, I am not connected to USB. If I reflash the recovery using ADB will it work? But I do have some worries because I'm using KitKat bootloader on a Lollipop Stock-based ROM (here) and I think I may get some errors.
It's not very important right now because I have root now and can reboot to recovery using Flashify.
I think all korean models cant enter recovery via hardware keys, mine is F400L and have the same problem.
Untouched LG G3
I have a completely untouched LG G3 uk version only official software no root etc and mine won't go into hard reset mode. I have tried 3 or 4 times it always goes into safe mode
same issue
f400k.
able to boot into recovery by softwares
but unable with hard keys.
last night was installing bliss pop. but stuck on boot animation. now wont go to recovery watsoever.
help.
rhtash said:
f400k.
able to boot into recovery by softwares
but unable with hard keys.
last night was installing bliss pop. but stuck on boot animation. now wont go to recovery watsoever.
help.
Click to expand...
Click to collapse
Turn off the phone completely. Press and hold Power and Volume Down. When the LG logo appears, release. After a split second, press volume down and volume up. White screen asking you to reset will appear. Press Yes two times using Volume buttons.
UP!!!
Any remedies? I justed from stock to cm12 LG g3 F400L..
Cant go to recovery mode. Cant flash anything..
Same prob,always going to safemode.f400k rooted,cloudy2.5
i've Lg g3 F4ooL and using Resrruction remic 5.5.5
I stuck in a Bootloop and my device is also not booting into Recovery or safe Mode.
Lg flash Tool is also not Connecting to my device in Downloadmode.
I think There is NO solution At ALl
Has anyone solved this issue?
to get in recovery on F460s, worked on mine, Press Vol-up + Power, as the logo appears release the keys and press Vol-up + Vol-down, you will boot into recovery.
I have the same issue, cant go into recovery using hard buttons on F400K. Any one able to succeed in this?
Same issue on LG G3 F460S, no combination of power + volume buttons + releasing them and pressing again when LG logo appears works. The device go straight into booting system and gets stuck. Is there any other method - maybe short-circuit some pins on the motherboard, to boot into recovery or do a system reset? Please...
OK, turns out that the combination is different for Korean models of G3, as misbah711 wrote, volume UP + power, when logo appears, release and press both volume UP + volume DOWN. If that does not work, try again, but release only the POWER button and press immediately volume DOWN (while volume UP was held all the time). Also, I first tried it without the back cover, as I have to remove battery to turn it off, did not work. Then with the cover it did, not sure if it's an important detail or not.
However it's not the end of the story for me. An image with Korean text appears, and nothing. No combination of power and volume buttons pressing does anything. I'm attaching the image. Also tried a web service to do Korean OCR and then used Google Translate - does not make any sense. Could anyone advise how to proceed and do a factory reset on this device? It won't boot into the system (gets stuck), no adb or any other communication with it.
Edit:
Turns out that when the Korean text appears and I connect USB cable to my PC, adb works correctly. Typed:
adb reboot recovery
The phone rebooted into recovery and now I'm doing a factory reset on it. Looks like all will be fine.
i have d851 on stock kitkat. I flashed TWRP and Philz but no way i can get into recovery mode. it always goes to fastboot mode no matter how I reboot into recovery. Now i am looking for stock recovery image. or a way to fix the twrp/philz. ROM boots just fine.
Hi guys, months ago i rooted my HTC 526G with Kingoroot. I later tried to update the software over wifi. It updated but in restarting its now stuck in boot screen and sometimes goes into recovery by itself. Is there a way I can revive the firmware? Any help appreciated
HTC Desire 526G
I have problem like this ....cant fix it
Warning/Disclaimer: This will erase everything you have on the phones internal memory. (if you have play store set up right, you can just log back in afterwards and it will pull all your data/apps back, however if you don't, make sure to backup any contacts, data, ect that may be on the phones storage before attempting this) (then again, if you were already trying to root, you should have had everything backed up already anyway )
Charge the device to at least 50% (or an hour or two at least if the battery was completely dead)
Hold the Volume Down Button, Press power button, keep holding the volume down button
Phone should boot into HBOOT or Download mode,
use the volume up and down buttons to highlight Recovery Mode
press power button to select Recovery Mode
Phone will reboot with a red triangle icon, press all three buttons at the SAME time (vol up, vol down, power)
use the volume up and down buttons to highlight Clear Data (Factory Reset) press power button to select, let it finish clearing /data/ and /cache/
Once this has completed, Pull the battery out, let it sit for like 30 seconds without the battery
Put battery back in
hold power button for a while until it vibrates, release power button
let it sit at the htc boot screen for 10 minutes phone should eventually move to the verizon boot screen (if it goes over 10 minutes on the htc screen, try procedure again)
Post here if you have any trouble.
Still have problems
wassti said:
Warning/Disclaimer: This will erase everything you have on the phones internal memory. (if you have play store set up right, you can just log back in afterwards and it will pull all your data/apps back, however if you don't, make sure to backup any contacts, data, ect that may be on the phones storage before attempting this) (then again, if you were already trying to root, you should have had everything backed up already anyway )
Charge the device to at least 50% (or an hour or two at least if the battery was completely dead)
Hold the Volume Down Button, Press power button, keep holding the volume down button
Phone should boot into HBOOT or Download mode,
use the volume up and down buttons to highlight Recovery Mode
press power button to select Recovery Mode
Phone will reboot with a red triangle icon, press all three buttons at the SAME time (vol up, vol down, power)
use the volume up and down buttons to highlight Clear Data (Factory Reset)
Once this has completed, Pull the battery out, let it sit for like 30 seconds without the battery
Put battery back in
hold power button for a while until it vibrates, release power button
let it sit at the htc boot screen for 10 minutes phone should eventually move to the verizon boot screen (if it goes over 10 minutes on the htc screen, try procedure again)
Post here if you have any trouble.
Click to expand...
Click to collapse
i've done the procedure but unluckly i'm still having this problem, did someone fix the loop with this method? should i just wait for custom roms? :crying:
I had it happen to me after trying to root with just about every tool out there, mine would boot up but wouldn't go past the htc boot screen white background green htc. After I cleared the data a few times (at least 3) it came back up, try the procedure more than once. Also be patient and wait the full 10 minutes for it to come back up, sometimes it can be slow to load for the first time after this kind of wipe.
wassti said:
I had it happen to me after trying to root with just about every tool out there, mine would boot up but wouldn't go past the htc boot screen white background green htc. After I cleared the data a few times (at least 3) it came back up, try the procedure more than once. Also be patient and wait the full 10 minutes for it to come back up, sometimes it can be slow to load for the first time after this kind of wipe.
Click to expand...
Click to collapse
Try to root with "PhilZ Recovery by Ajit", search on google, i don't remember where i have download it, but it is an .exe file.
After you install it on your computer, you select USB debugging, and connect your phone to the computer, the rest of the process is auto.
After the installation process, the phone will autoreboot in recovery, here you will select ---> Advanced Function---> RE-root System (SuperSU).
After that, reboot, and install SuperSU from GooglePlay.
Success.
Root without boot loop (you may want to wipe Dalvid Cache before reboot after selecting root).
I hope this works for you ( it worked for me HTC desire 526g ).
Have a nice day.
IF you dont find the Philz, contact me, i wil send it to you.
Philz Recovery by ajit is designed for devices using the Mediatek processor; Sadly our 526 (no g, no +) uses a qualcomm processor. I do not recommend anyone to attempt to use "Philz recovery by Ajit" to attempt to root their HTC 526 as at best it will fail and at worse it will flash a non-compatible recovery and turn your device into a hard-brick.
wassti said:
Philz Recovery by ajit is designed for devices using the Mediatek processor; Sadly our 526 (no g, no +) uses a qualcomm processor. I do not recommend anyone to attempt to use "Philz recovery by Ajit" to attempt to root their HTC 526 as at best it will fail and at worse it will flash a non-compatible recovery and turn your device into a hard-brick.
Click to expand...
Click to collapse
I know...i said it is for HTC 526G.
Yep, I know you said it; just needed to clarify for other members so there is no confusion if someone comes here from a google search or what not
This forum is for 526 only, not the g or +
Bricked
I tried to wipe, but it still staing on htc screen...can someone do a backup or something and send me a link and reply me. i need it
sorry for bad english
I have the same problem please help us
emwakishi said:
Hi guys, months ago i rooted my HTC 526G with Kingoroot. I later tried to update the software over wifi. It updated but in restarting its now stuck in boot screen and sometimes goes into recovery by itself. Is there a way I can revive the firmware? Any help appreciated
Click to expand...
Click to collapse
I've exactly the same problem... does anybody have a rom for this model?
emwakishi said:
Hi guys, months ago i rooted my HTC 526G with Kingoroot. I later tried to update the software over wifi. It updated but in restarting its now stuck in boot screen and sometimes goes into recovery by itself. Is there a way I can revive the firmware? Any help appreciated
Click to expand...
Click to collapse
http://forum.xda-developers.com/chef-central/android/htc-desire-526g-bootloop-solution-t3241938
solve it by flashing rom using re recovery mode
I also got 526g+ totally finished only restarting I asked so many mobile repairing places no luck at all
PodolskiMeki said:
i've done the procedure but unluckly i'm still having this problem, did someone fix the loop with this method? should i just wait for custom roms? :crying:
Click to expand...
Click to collapse
Similar bootloop condition HTC 526g
wassti said:
Warning/Disclaimer: This will erase everything you have on the phones internal memory. (if you have play store set up right, you can just log back in afterwards and it will pull all your data/apps back, however if you don't, make sure to backup any contacts, data, ect that may be on the phones storage before attempting this) (then again, if you were already trying to root, you should have had everything backed up already anyway )
Charge the device to at least 50% (or an hour or two at least if the battery was completely dead)
Hold the Volume Down Button, Press power button, keep holding the volume down button
Phone should boot into HBOOT or Download mode,
use the volume up and down buttons to highlight Recovery Mode
press power button to select Recovery Mode
Phone will reboot with a red triangle icon, press all three buttons at the SAME time (vol up, vol down, power)
use the volume up and down buttons to highlight Clear Data (Factory Reset) press power button to select, let it finish clearing /data/ and /cache/
Once this has completed, Pull the battery out, let it sit for like 30 seconds without the battery
Put battery back in
hold power button for a while until it vibrates, release power button
let it sit at the htc boot screen for 10 minutes phone should eventually move to the verizon boot screen (if it goes over 10 minutes on the htc screen, try procedure again)
Post here if you have any trouble.
Click to expand...
Click to collapse
My phone was also rooted using kingroot. I received an OTA update and I downloaded it. Once the download was complete, the phone restarted and got bootlooped. Occasionally, it goes into recovery. I tried factory resetting it several times as mentioned in the solution. But each time I turn the phone ON again after factory reset, it is looping. Its not stuck at the boot logo. Instead it reboots automatically and in some cases to recovery. So the wait-for-10-mins thing is not working for me.
1. I received a stock ROM from the Russian section of XDA. Will flashing that ROM using the stock recovery using "install update from SD card" help me recover my phone from bootloop?
2. Will flashing the stock ROM unroot the phone? Presently, even after the factory resetting, "check the software partition" option in recovery returns a message "error - system has root". So I was hoping that unroofing might fix the problem. Will it?
3. If the above method fails, is there any other method? Like flashing a custom recovery or flashing a custom ROM etc?
Please help me fix the phone. Thanks in advance.
I am experiencing the same problem and have tried everything to avail, will this devise ever work again its still stuck with a white screen and green HTC
negomo said:
I am experiencing the same problem and have tried everything to avail, will this devise ever work again its still stuck with a white screen and green HTC
Click to expand...
Click to collapse
Hey negomo. I just fixed the phone yesterday. It seems that installing an OTA update while the phone is rooted can result in a bootloop or bricking(as in my case). I fixed this issue by flashing a stock ROM of the HTC 526g which I got from another Russian forum in XDA. Anyway I am posting the link of that stock ROM here.
( I am not allowed to post link. So please delete the spaces to get the actual link)
h t t p s :// yadi.sk/ d/gNKBahgZiwGmo
Once you download it do the following procedure
1. Copy it to an SD card and insert the card in your phone.
2. Press power button+volume up key button to enter HBOOT menu (while turning on the phone, press power and vol up button instead of power button alone)
3. Choose recovery option and press volume down to enter
4. Press power button once to enter recovery
5. Choose "install update from SD card"
6. Wait till it finishes installation
7. Wipe cache
8. Reboot phone
PS: I had already done a factory reset from recovery menu. I don't know if that had helped.
This will bring your phone back to life. Give around 10 mins for the first boot.
I hope I was able to help you.
Hit thanks if I did.
how to know my device 526g or 526
---------- Post added 24-06-2016 at 12:05 AM ---------- Previous post was 23-06-2016 at 11:51 PM ----------
https://www.imageupload.co.uk/image/ct0U
thx you are pro ??my problem solved ??
Recently I bricked my phone after flashing wrong boot.img. I can't get into bootloader and once the device turns on, I can't do anything except of waiting until the battery runs out of power. Is there any way to recover this phone?
First of all, it is not bricked. As long as the screen comes on (even if just stuck on the HTC logo screen) the device is likely recoverable. A true brick is a device that can only be recovered by opening up the phone (replace motherboard, JTAG, etc.). You are simply stuck in a condition, where it won't boot to the Android OS.
Bootloader is a protected partition, and therefore can't be over-written by something like flashing a boot.img, as long as your are s-on (default condition).
Bootloader therefore is most likely still working, you just aren't accessing it properly. You probably just aren't doing the proper button combo, to get the bootloader. Try this:
1) No need to wait for battery to drain. To reboot the phone simply hold power + vol up button, until the screen goes dark to reboot. May take up to a minute, before this happens, in a "stuck" condition.
2) The moment the screen goes dark to reboot, but before the HTC logo screen comes back on, let go of the power button, and simply slide your finger from vol up, to vol down. Keep vol down pressed, until you see the bootloader screen.
3) If you don't get the bootloader, you probably just got the timing wrong. You either started pressing vol down too late, or let go of vol down too early. Simply repeat Steps 1 and 2 above, until you get the timing correct.
From bootloader, you should be able to flash the correct boot.img
Although your comment that you flashed the "wrong boot.img" raises some questions:
a) How do you know it is the wrong boot.img? Where did you get it from?
b) Why did you flash this boot.img? What were you trying to accomplish? Is it a custom kernel, or trying to solve some other problem?
If you need help finding the right boot.img, in addition to answer the above questions a-b, you should also do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
First of all, it is not bricked. As long as the screen comes on (even if just stuck on the HTC logo screen) the device is likely recoverable. A true brick is a device that can only be recovered by opening up the phone (replace motherboard, JTAG, etc.). You are simply stuck in a condition, where it won't boot to the Android OS.
Bootloader is a protected partition, and therefore can't be over-written by something like flashing a boot.img, as long as your are s-on (default condition).
Bootloader therefore is most likely still working, you just aren't accessing it properly. You probably just aren't doing the proper button combo, to get the bootloader. Try this:
1) No need to wait for battery to drain. To reboot the phone simply hold power + vol up button, until the screen goes dark to reboot. May take up to a minute, before this happens, in a "stuck" condition.
2) The moment the screen goes dark to reboot, but before the HTC logo screen comes back on, let go of the power button, and simply slide your finger from vol up, to vol down. Keep vol down pressed, until you see the bootloader screen.
3) If you don't get the bootloader, you probably just got the timing wrong. You either started pressing vol down too late, or let go of vol down too early. Simply repeat Steps 1 and 2 above, until you get the timing correct.
From bootloader, you should be able to flash the correct boot.img
Although your comment that you flashed the "wrong boot.img" raises some questions:
a) How do you know it is the wrong boot.img? Where did you get it from?
b) Why did you flash this boot.img? What were you trying to accomplish? Is it a custom kernel, or trying to solve some other problem?
If you need help finding the right boot.img, in addition to answer the above questions a-b, you should also do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
a) This is where i got it from: https:// androidfilehost.com/?fid=385035244224400814. The boot.img file was most likely not matching the system installed (LineageOS 16). It's stock boot.img for my device (propably).
b) I was trying to fix the problem, where I couldn't install Magisk, because when installing, it said that I have custom boot.img and cannot proceed. I could've ask first how to solve this instead of doing this, so I'm just an idiot.
DarkKnightComes said:
a) This is where i got it from: https:// androidfilehost.com/?fid=385035244224400814. The boot.img file was most likely not matching the system installed (LineageOS 16). It's stock boot.img for my device (propably).
b) I was trying to fix the problem, where I couldn't install Magisk, because when installing, it said that I have custom boot.img and cannot proceed. I could've ask first how to solve this instead of doing this, so I'm just an idiot.
Click to expand...
Click to collapse
It worked! Thanks for help!
DarkKnightComes said:
a) This is where i got it from: https:// androidfilehost.com/?fid=385035244224400814. The boot.img file was most likely not matching the system installed (LineageOS 16). It's stock boot.img for my device (propably).
b) I was trying to fix the problem, where I couldn't install Magisk, because when installing, it said that I have custom boot.img and cannot proceed. I could've ask first how to solve this instead of doing this, so I'm just an idiot.
Click to expand...
Click to collapse
a) I can't tell from the link alone, what that boot.img even is, and it seems that you don't either. Even if stock boot.img, what version number (there are many - and that matters). My advice (maybe already a lesson learned) is not to flash things, if you aren't 100% sure what they are.
b) I'm not a Lineage user, so I'm not familiar whether that is a known error or not. AFAIK, Lineage should be compatible with Magisk, so as you already figured, the error may be a result of custom kernel, another previously installed root method (SuperSU?) or some other mod. In which case, there are better ways to get back to a "clean" and correct boot.img, rather than flashing files which you are unsure of. Easiest way, is to simply dirty flash the Lineage ROM again. Either just the boot.img (which is included with the ROM.zip) of the whole ROM. Whole ROM is probably the best, as it will give you a clean ROM baseline, in case there is anything else modified (besides boot.img) that is interfering with Magisk. Dirty flash means flashing the file while keeping user data, only wipe cache and Dalvik.
---------- Post added at 09:12 AM ---------- Previous post was at 09:10 AM ----------
DarkKnightComes said:
It worked! Thanks for help!
Click to expand...
Click to collapse
What worked exactly? Getting into bootloader by the method I described, I pretty much figured would work. Did you also get the right boot.img flashed, and get it rooted with Magisk?
What worked exactly? Getting into bootloader by the method I described, I pretty much figured would work. Did you also get the right boot.img flashed, and get it rooted with Magisk?
Click to expand...
Click to collapse
I forgot about the Power+VolDown combination. I launched Recovery from bootloader and I just installed ROM on top of the previous one. The ROM that I have has Magisk integrated.