Develop Bugs

[Q] Maybe in a bootloop?

Rooted my phone using Temporary CWM method, installed Titanium Backup and restored from my old phone. Selected All Apps and Data. Rebooted my phone and I assume that it is now stuck in a bootloop. It gets to the ASUS and Intel Inside screens, then I get a spinning circle forever (well, at least 3 minutes).
Where do I go from here? Reflash the ROM and start over and don't restore system data? Is there an easier/quicker way?
Thanks

Go to fastboot mode by holding the power and volume up button,connect USB cable be sure that you installedmusb and fastboot driver.go to folder of fastboot and hold shift key then right click open command window here and type:fastboot erase cache then enter fastboot reboot and voila..

Thanks for the reply, but that didn't do it.
I was able to execute the commands, but still no luck. I got into recovery to try and wipe from there, but got the dead android. I them held power up and tapped vol up to get into recovery. tried to wipe cache from there and the phone just sat there for 3-4 minutes with nothing. Now when I get into recovery, I get a flashing dead android, and the power/vol up trick doesn't work. I can still boot into fastboot.
Di I just need to reflash the stock image? Or is there something else I can do?

arrosen said:
Thanks for the reply, but that didn't do it.
I was able to execute the commands, but still no luck. I got into recovery to try and wipe from there, but got the dead android. I them held power up and tapped vol up to get into recovery. tried to wipe cache from there and the phone just sat there for 3-4 minutes with nothing. Now when I get into recovery, I get a flashing dead android, and the power/vol up trick doesn't work. I can still boot into fastboot.
Di I just need to reflash the stock image? Or is there something else I can do?
Click to expand...
Click to collapse
I had the same problem as yours and it took 3 hours before i figured it out and managed to run the phone normally.I downloaded all the files,drivers and latest prerooted system img. here in this forum.you can download it there and there is the instruction how to do it.
To Begin :
1. on Fastbootmode connect your device and on the flashtool folder hold shift key and right click and go to open command here,be sure that downloaded images are in the same folder.Recovery img.,Boot Img. and the big pre-rooted System img.
2. type fastboot devices then hit enter key - the device nos. should appear and you can start now to flash...
a. fastboot -w then hit enter this will erase the system
b.fastboot flash system system.img then hit enter key
c.fastboot erase userdata then hit enter key
d. fastboot erase cache then hit enter key
e. fastboot reboot then hit enter key..

THANK YOU!!!
Thank You, Thank You, 1000 times, Thank You.
I did everything you mentioned, with a few small exceptions
1. Make sure you have the lastest version of Fastboot
2. Instead of step b above, I did the following. Not sure if it was needed or not, but it worked for me
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
3. At the end, after I did a Fastboot Reboot, I got the dreaded dead android again. I nearly cried. However, I rebooted again, and everything seemed to work. Note that on the first boot, it may take 2-3 minutes for the OS to come up.
4. All of the files and great insight can be found here: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596

HELP blink sleeping android error on normal boot(not on recovery mode)

I can't boot up my device it's have blink sleeping android error. (my device is ze551ml running WW_2.19.40.22 firmware and never ever ROOT!!! )
I tried hold power button and press volume up button but its doesn't work.
I also can't access to recovery mode too.
It's have the same blink error message and can't pass by hold power button and press volume up button.
Oh but i can access to fastboot page.
and my computer don't recognize my phone at all(i already install driver)
Before this problem happen I get in to recovery mode try to wipe cache but i miss press and i selected "apply update from adb"
and that time my phone doesn't connected with PC. I don't know what to do so I turn off my phone.
then I open recovery mode again and select wipe cache then I go out to take a bath.
I came back and see my phone is off so I boot it.
It's booting about 2-3 mins and nothing happen so i go to recovery mode again but this time they have problem like i explain before(blink error message that can't pass by hold power button and press volume up button)
So anyone have a solution for my problem. please I really need your help!
Sorry for my bad english

Hi,
I had this when I went to wipe my system cache and it failed. Your best bet, especially if you can't get into recovery is to fastboot flash the recovery again if you have an unlocked bootloader.
If you don't you'll want to unlcok the bootloader and follow the instructions for using ADB if you're new to it: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596

How can I unlock my boot loader when i can't even open up my phone.

stultus136 said:
How can I unlock my boot loader when i can't even open up my phone.
Click to expand...
Click to collapse
If you hold volume down and power, it should go to bootloader first, then you have your choices for recovery....Get it to the bootloader screen, then run the commands to unlock it...

Could you please tell me everything step by step on how to cure my phone?
I'm very noob.

okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code

stultus136 said:
okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code
Click to expand...
Click to collapse
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.

Same Problem
smokinjoe2122 said:
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.
Click to expand...
Click to collapse
Hey I'm having the same problem, how'd you get the computer to recognize that the phone was plugged in? My computer does not recognize that the phone is on when I have the flashing error screen, so ADB doesn't recognize that there is a device connected.

Hi,
I had the exact same problem, and I managed to boot up again thanks to you!
What I did :
Install ADB and Drivers
Boot my phone into Fastboot (Power+Volume Up at boot, keeping VolumeUp button pressed while booting). Don't go into any menu (do not select recovery or so). At this point your computer should recognize your Android phone when you plug it in through USB.
Open up a cmd with admin rights, navigate to adb install path by typing : cd C:\adb
Then type : fastboot erase cache
It should trigger an action on your device, and the prompt should display sth like "Cache successfully erased" (I don't remember exactly)
Finally type : fastboot reboot, press volume up while booting again, and access Recovery like usual!
Now you can try wiping your partition cache again.
Worked like a charm for me! Thanks a lot

Boot-Looped device. I'm willing to try anything at this point.

So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.

From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?

addisontodd said:
So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
Click to expand...
Click to collapse
it's seems like me , it's been a month i can't boot it up .

sfhub said:
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
Click to expand...
Click to collapse
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.

addisontodd said:
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
Click to expand...
Click to collapse
what if you try
fastboot boot twrp.img

I've bootlooped so many times I don't know where to start.
So you flashed the factory IMG from your bootloader correct.
Fastboot -w will wipe without wiping system.
Then reflash your whole system. I would redownload from the Google site through Skipsoft...the easiest way. When it asks to keep or flash new recovery you want to flash the stock recovery.
http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444
You'll have to reroot afterwards which you can also do through skipsoft.
Profit... Thank me if I helped.

It's a Hardware issue. Installing system again will not fix it. Send it to LG for a repair. My phone had the same issue.

refurbed and still bootlooping

LG refurb updated the ROM to 20x, and (supposedly) replaced MB & RF.
Now I can't get into bootloader, with either ADB or power/vol down combo. Bootloops instead and takes 15 mins to become a working phone again.
I've factory reset 2x today.
Perhaps factory reset and don't restore from Google?
Perhaps 20x is corrupt?
I have no idea what to do next other than deal with the apparent idiots at LG Texas. This is the 2nd "refurb" in a month and 3rd since I've had the G4.
HTC M7 is saving my sanity as backup.

finally got out of bootloop. OEM unlock was the issue in Developer options.
But now having problem getting it to boot into twrp.
fastboot flash recovery twrp.img - went ok, as per past experience.
but - fastboot boot twrp.img - is a no go.
I get this back - cannot load 'twrp.img': No such file or directory.
Can't power down with power button held for 10secs.
Only fastboot reboot works.

What happens if you try to boot into recovery with the key combo (power and vol down until lg logo appears, then release power briefly whilst still holding vol down and then press power again whilst still holding vol down - should bring you to "factory reset page" but once factory reset is confirmed should go to TWRP)

nope, goes to factory reset. tried that twice.

Ok so even after you have flashed twrp, when you enter that factory reset page and click yes twice, it actually factory resets it (that screen is there for everyone but it normally goes to twrp afterwards). Did you boot into your phones OS inbetween flashing twrp and booting to it? LG software replaces twrp with stock recovery if you don't patch the os.
The way to permanently install twrp is:
1) reboot to bootloader and perform "fastboot flash recovery twrp.img"
2) fastboot reboot
3) AS SOON AS IT REBOOTS (<-- that is important) - use key combo and click yes twice - do NOT let it boot back into the main android system inbetween, or you will need to start again

k, I'll give that a go tonite after work. Don't recall the issue with the earlier OS, 20v (before "refurb"), but I'll do oit.

What model of phone is it?
In terms of flashing twrp, that has always been the process (I have a G4 on v20g firmware and it took me a while to work out why twrp kept being wiped)

it's a G40 w/20x. Never had this issue before 20x.
still actually having an issue on reboot. Takes about 7 mins now as it optimizes 1 unknown app.

used this method from fastboot:
fastboot boot twrp.img and pointed (d&d) to twrp on my drive.
then installed twrp from memory as described on twrp page/Fastboot Installation Method.
Ding Ding Ding!
thanks.

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)