Develop Bugs

Need some advice....

I tried to root my phone and followed all steps until it asked to boot into the custom recovery and that only displayed a blackscreen and if I tap on the screen the phone vibrated. I cannot boot into bootloader as the phone just automatically tries to enter recovery with blackscreen.
Hold all buttons the phone boots normally and can use the phone as usual.
I've tried to use the adb and fastboot cmds to restore and factory reset but just reboots and tries to enter recovery with the blackscreen.
My device is htc_a51ul if that helps.
Thanks,
Phatzy

Tighten two volume buttons and the power button when you see a black screen and holding down the volume- and power button that would go to zagruzchik.Telefon must be connected to kompyuteru.Esli got to go to the boot loader, boot into download sistemu.Esli not work then you have forgiven stock rekaveri of loader. https://yadi.sk/d/nWnRAChBnEtxG

I think you have flashed a wrong recovery ,first thing to do now is flash stock recovery and whether if it is working fine if so then flash the proper version of twrp 2.8.7.0 is recommended and see if it works
I had the same issue when I first flashed twrp on lollipop but then I did the above and now everything is fine.

while its on the blackscreen only adb commands work. If i try fastboot commands its just waiting for device and phone dont respond. I cannot get into bootloader at all with volume keys or with adb command.
Many thanks for suggestions.

Ok I have now managed to get bootloader back and I can now enter the stock recovery but when I enter recovery it has a red triangle. Is there anyway to remove this?
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.

can't get into recovery mode

hi
i just unlocked my mi5s now, but when im trying to get into recovery mode (volume up + power) it still shows me the phone picture.
there is something that i am missing?

Flash the recovery, when in fastboot reboot into recovery by "fastboot boot recovery.img" if that's the name of the file on your computer. It will boot into recovery. After that, turn of the phone and boot into recovery with the button combination. Do not boot into the OS as it will disrupt the process! After this you should be fine. If not, try again, as you probably failed to directly boot into recovery with the button action.
Also, do check that you push both the volume keys plus the on/off button. So three in total.

8166uy said:
Flash the recovery, when in fastboot reboot into recovery by "fastboot boot recovery.img" if that's the name of the file on your computer. It will boot into recovery. After that, turn of the phone and boot into recovery with the button combination. Do not boot into the OS as it will disrupt the process! After this you should be fine. If not, try again, as you probably failed to directly boot into recovery with the button action.
Also, do check that you push both the volume keys plus the on/off button. So three in total.
Click to expand...
Click to collapse
as far as i know, when im unlock the phone, it unlock the recovery mode so i can access it by volume up + power instead of the phone picture.
i want for now stay with the stock recovery and not flash a custom one

Mm, you could use the phrase "fastboot reboot recovery". If that doesn't work, flash the latest Global beta and try again both ways.
If that also doesn't work, recheck if the phone is really unlocked (sometimes Xiaomi phones relock after an update without any good reason).
You could also try to find the stock recovery and use it in the method in my first reply. But keep that for last, as I don't know for sure how that recovery reacts to such a thing. Although I can't think of a reason why it would go wrong, it's better to be save than sorry.

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?

Can't boot to recovery

Hello guys,
I have a Ginko device. It started to act weird, as if the volume down button was held down at all times. I took it to some shop and they told me it's most likely software and not hardware, and to try and flash a new ROM.
Now, I believe he was talking out of his ass. Rebooting the phone automatically puts it into fastboot because of the volume- button being broken. If it was a software issue this would not happen, I believe.
Whatever, I decided to try and flash a ROM just because maybe if I have root I will be able to block that button from working somehow.
The issue is, I can't boot into TWRP.
I unlocked the phone through Xiaomi and downloaded TWRP for Ginko. I did the `fastboot flash recovery twrp.img` thing and it works fine, but after that the command to reboot it to recovery `fastboot boot twrp.img` does not work. The fastboot image goes black for .1s then it shows the fastboot image again. Nothing happens. If I run the command again it takes a few seconds shoing "booting..." then the phone reboots to SYSTEM and an error shows on the CMD saying "FAILED (status read failed (Too many links))".
The only way I've found to boot to recovery is by using `adb reboot recovery` but that needs me to boot into system, which means TWRP is erased and the default recovery comes up.
If I reboot the phone the only way to go into system is by holding volume+, as it seems to counter the broken volume- button... But that means I can't boot to recovery, no matter how many times I try.
So I have no idea what to do.

AckmanDESU said:
Hello guys,
I have a Ginko device. It started to act weird, as if the volume down button was held down at all times. I took it to some shop and they told me it's most likely software and not hardware, and to try and flash a new ROM.
Now, I believe he was talking out of his ass. Rebooting the phone automatically puts it into fastboot because of the volume- button being broken. If it was a software issue this would not happen, I believe.
Whatever, I decided to try and flash a ROM just because maybe if I have root I will be able to block that button from working somehow.
The issue is, I can't boot into TWRP.
I unlocked the phone through Xiaomi and downloaded TWRP for Ginko. I did the `fastboot flash recovery twrp.img` thing and it works fine, but after that the command to reboot it to recovery `fastboot boot twrp.img` does not work. The fastboot image goes black for .1s then it shows the fastboot image again. Nothing happens. If I run the command again it takes a few seconds shoing "booting..." then the phone reboots to SYSTEM and an error shows on the CMD saying "FAILED (status read failed (Too many links))".
The only way I've found to boot to recovery is by using `adb reboot recovery` but that needs me to boot into system, which means TWRP is erased and the default recovery comes up.
If I reboot the phone the only way to go into system is by holding volume+, as it seems to counter the broken volume- button... But that means I can't boot to recovery, no matter how many times I try.
So I have no idea what to do.
Click to expand...
Click to collapse
Did you also try to flash recovery as you did before but right after that booting directly into recovery using hw buttons (vol- and pwr button till boot splash appears) from fastboot?

AckmanDESU said:
The only way I've found to boot to recovery is by using `adb reboot recovery` but that needs me to boot into system, which means TWRP is erased and the default recovery comes up.
Click to expand...
Click to collapse
to prevent twrp to be erased flash vbmeta (attached) using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
i suggest you use OrangeFox and enable "aggresive stock recovery deactivation" in settings
This is a hardware problem and it's better to replace it
you can disable that button (while on Android) using xposed edge by setting "none" to click and long clic (need root + lsposed or edxposed)