Develop Bugs

[Q] my HTC ONE M8 doesnt boot- PLEASE HELP!

I trying to modify build.prop and reboot the device but after that my device didnt rebooted,
I manged to get him into twrp at the first time and tried to replace the modify build.prop with his backup but now the device is stuck and dont let me get into bootloader and his loading up the HTC logo (that you can see when the device is boot up) every something like 5 minutes.
and the pc isnt recognized it too.
do I have something to do? when I pressing Volume up +power the device is restarting and showing the HTC logo but staying on black screen.
sorry for my poor english but I really need some help.

Did you make a nandroid before making the build.prop changes? If so, just restore the backup.
If not, why the heck not???
Do you have custom recovery (TWRP or CWM) installed, or stock? Any custom ROM zip on the phone? If you have custom recovery and a ROM zip on the phone, try flashing it.
Do you have adb/fastboot working, and any response when you use the command:
fastboot devices
If you have working fastboot, push a ROM zip to the phone and flash with custom recovery; or sideload in TWRP.

redpoint73 said:
Did you make a nandroid before making the build.prop changes? If so, just restore the backup.
If not, why the heck not???
Do you have custom recovery (TWRP or CWM) installed, or stock? Any custom ROM zip on the phone? If you have custom recovery and a ROM zip on the phone, try flashing it.
Do you have adb/fastboot working, and any response when you use the command:
fastboot devices
If you have working fastboot, push a ROM zip to the phone and flash with custom recovery; or sideload in TWRP.
Click to expand...
Click to collapse
I am new in that htc thing but i just backup the build.prop I have no clue what nandroid is...
I have TWRP installed but I cant boot into it, and when im trying adb/fast boot its says waiting for device.
btw my htc one m8 is connecting to the pc for a second only and thats not allows me to do adb things

romhaja said:
I am new in that htc thing but i just backup the build.prop I have no clue what nandroid is...
I have TWRP installed but I cant boot into it, and when im trying adb/fast boot its says waiting for device.
btw my htc one m8 is connecting to the pc for a second only and thats not allows me to do adb things
Click to expand...
Click to collapse
A nandroid is a full recovery image made with custom recovery (TWRP in your case), same as a TWRP backup. You should always make a nandroid when making changes to system files. Especially if you are inexperienced with making such changes.
Bootloader is always available as long as the screen comes on. If you can't get into bootloader, its because you aren't doing the button combo correctly:
1) While the screen is on, press and hold vol up and power button until the device reboots (takes 10 seconds or more).
2) The instant the screen goes dark and the phone start to reboot, let go of the power and vol up buttons, and start holding the vol down button. Don't let go of the vol down button until the bootloader comes up.
3) If you don't go into bootloader, you either didn't start holding the vol down button fast enough, or you let go of it too soon.
Once in bootloader, try going into recovery (TWRP). Although TWRP is of limited use if you don't have a nandroid, don't have a ROM zip on the phone, and if you don't have PC connectivity. You are going to have to troubleshoot the PC connectivity. Or you can try to put a ROM on a MicroSD card, and flash in TWRP.
Whatever you do, do not do a factory reset in bootloader. This will corrupt the phone's internal memory and make your situation even more complicated.
Did adb/fastboot work previously? If not, its hard to get out of your present situation without PC connectivity. Try re-installing the HTC drivers (HTC Sync), try another USB cable, or a different USB port, or even a different computer.

redpoint73 said:
A nandroid is a full recovery image made with custom recovery (TWRP in your case), same as a TWRP backup. You should always make a nandroid when making changes to system files. Especially if you are inexperienced with making such changes.
Bootloader is always available as long as the screen comes on. If you can't get into bootloader, its because you aren't doing the button combo correctly:
1) While the screen is on, press and hold vol up and power button until the device reboots (takes 10 seconds or more).
2) The instant the screen goes dark and the phone start to reboot, let go of the power and vol up buttons, and start holding the vol down button. Don't let go of the vol down button until the bootloader comes up.
3) If you don't go into bootloader, you either didn't start holding the vol down button fast enough, or you let go of it too soon.
Once in bootloader, try going into recovery (TWRP). Although TWRP is of limited use if you don't have a nandroid, don't have a ROM zip on the phone, and if you don't have PC connectivity. You are going to have to troubleshoot the PC connectivity. Or you can try to put a ROM on a MicroSD card, and flash in TWRP.
Whatever you do, do not do a factory reset in bootloader. This will corrupt the phone's internal memory and make your situation even more complicated.
Did adb/fastboot work previously? If not, its hard to get out of your present situation without PC connectivity. Try re-installing the HTC drivers (HTC Sync), try another USB cable, or a different USB port, or even a different computer.
Click to expand...
Click to collapse
adb worked with my phone at the first time so I think I will try to reinstall the drivers, and if it won't work I will buy a micro as writer/reader and will put a rom there to flash.
Thank you for helping me! Do you have any recommendation about the sd writer?
Thanks again!

romhaja said:
Do you have any recommendation about the sd writer?
Click to expand...
Click to collapse
Not really. Any one should work, even cheap ones that go for $5-10 US.

Trying to fix an M8

So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.​
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!

TMartin said:
So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.​
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
Click to expand...
Click to collapse
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.

xunholyx said:
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
Click to expand...
Click to collapse
I can get into TWRP but it won't mount the data partition. Are you saying I should try flashing another ROM the normal way through TWRP or try the sideload option? I tried to fastboot flash stock recovery. It says it worked but then continues to boot to TWRP.
I can get into bootloader. I'm pretty sure it's a 4.16.401.x ROM but I'll have to double check when I get home. I've tried to flash stock everything but it you know how it restarts through the process? When it restarts, it seems to want to restart to OS.
I'm about 99% sure the OS is there because it boots into Android but only gets me to the "Decrypt storage" screen.

Can't get into Download mode

Edit: I somehow could reach to fastboot mode and flashed laf.img to recover download mode but I get a boot certification verify error. I can access the phone and recovery but cant access download mode.
I decided to upgrade to MM from LP using kdz method. However I could not boot into download mode with any method. The phones just reboots normally. I tried hard button(volume up and connecting to pc), I tried adb reboot bootloader, I tried to reboot to bootloader from twrp and none of them worked. In every method I used the phone just reboots normally.
I have root + twrp with stock 5.0 rom. Any help appreciated, thanks!

Tried flashing CM13, now can't enter normal boot

So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks

Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.

Phone might be bricked. Need help to find a solution!

Hello everyone! Complete dumbass here!
I was following the guide to root my razer phone. I've had it for a couple months, and decided to root it. I followed the guide here https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137
After a couple bumps in the road, such as fastboot commands not working, not being recognized, etc. I finally was able to unlock bootloader and install twrp. But it was #9 that got me stuck again.
"9.) Once in recovery, go to the install button, and select Install Zip, and select Magisk-v16.0.zip."
In recovery, adb devices and fastboot devices yielded no devices attached. Doing a search, I came across another forum post where it states the sdcard is encrypted and can't be accessed in twrp, and the fix is to do something like "Wipe>Wipe Data> Type Yes" and that should factory set the card. I did this and rebooted the device. I waited for a half hour for the animated PixelFloatingInACircle logo to be done with it's floating in a circle, but ended up going to bed and letting it die. Woke up this morning, plugged it in, got the razer logo splash screen with the orange text telling me of my impending doom, then went back to the animation. I let my dog out and came back and it was still on. I unplugged it and am letting it die again to see if there's another solution.
I'm wondering if anyone else came across this issue, and if so, how did they fix it? Any help would be appreciated.

Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk

waiflih said:
Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk
Click to expand...
Click to collapse
The problem is when I try to enter download/recovery mode after charging the battery a little, it doesn't go to that menu. Instead, it skips right to the particle logo, and that's where it hangs.
The only guide I saw was the one I listed. Is there a guide for this magisk installer?(Ya know, in case I figure the first problem out, so I might try my hand at potentially creating another)

i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards

waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons
Click to expand...
Click to collapse
Tried this originally after I let it die the first time. It still boot to the animation logo.

Bloodeagle said:
Tried this originally after I let it die the first time. It still boot to the animation logo.
Click to expand...
Click to collapse
Read the edit, I found that the trigger is having the usb cable connected to the pc. Try that, or you can also try to adb while the device is booting (particles logo). Sometimes adb is responsive even when booting. There you can try to adb reboot bootloader

waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards
Click to expand...
Click to collapse
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?

Bloodeagle said:
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?
Click to expand...
Click to collapse
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition

waiflih said:
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition
Click to expand...
Click to collapse
I moved the flash_all script into the tools folder and after a little while, the phone booted up into setup! After a couple taps, I've realized the wifi isn't working, which I know is a known issue. I'm gonna let it sit for the night and finish it in the morning!
EDIT : Soooo, I know I said I was going to bed, but I decided to fix the wifi issue, which in turn, also rooted my phone. I've downloaded the root checker, and it confirms it! Thanks so much Waiflih! You rock!

Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.

saberhashemi said:
Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.
Click to expand...
Click to collapse
Have you tried holding few combinations of different butt9ns for a minute or two to see if that results in you getting in downl9ad mode?