Database Develop

[Q] 1092 TWRP on 5.0 bootloop, stuck in recovery [SOLVED]

Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?

Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657

oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?

HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.

oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic

Nexus 6 soft brick help

I flashed android m preview last night. i needed root so i flashed it and that flash failed, which seems to have corrupted the rom. Im hoping i can get my nexus back but im having some issues.
Recovery- i didnt flash twrp, its stock android m recovery
factory reset- all this does is erase and my rom still is corrupted
fastboot- computer reads it, i can see it in device manager as "android bootloader interface, however adb wont read. no devices in adb devices
ive uninstalled and reinstalled the google drivers several times to no avail. ive tried it on a different pc and same no dice.
ideas?

adb commands will not work in fastboot mode.
read this. it shall set you free
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
ingnore relock bootloader part!!

1. Boot into bootloader 2. fastboot flash system [system.img from preview 3 rom] 3. Wipe caches 4. Reboot

I admit i was trying to use adb to see if the phone was connected... bad habit i guess. The connect to adb in recovery option was not working at all. I blame this all on the MM bootloader. I have a bad taste in my mouth. In the end wugs saved me. I guess that day i needed the process simplified. Sorry for late response.
Anyway, phones fixed, this matter is complete. Both you folks are amazing. Im sending virtual hugs to all.

Nexus 6 Marshmallow stuck in fastboot loop

I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!

turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
how about this, adb NEVER EVER works in fastboot mode. that is reserved exclusively for fastboot. you have to use fastboot to flash a recovery, then the recovery to flash supersu.
---------- Post added at 04:49 PM ---------- Previous post was at 04:48 PM ----------
now it also seems as you have to fastboot flash a factory image as well.

turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: link removed to satisfy forum policy...
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
I asked for help before searching thoroughly enough! I figured out that I needed to download another ROM, transfer it into the phone's storage, and install using TWRP. I really didn't understand the capabilities of this fabulous application and had simply flashed it because the thread instructed me to.

Stuck in Fastboot

Ok..so here's the situation. I was going to install a new ROM ( my son got a new phone a iphone ) but any ways. As I was in TWRP i did everything we all normally do but the phone died mid flashing GAPPS. when i went to pulg the phone to the charger and restart the phone i see that it started to boot up the it jumped straight to FASTBOOT and it's stuck. I can toggle through fastboot but that is it. when i go to restart it will show the boot animation but then goes to fast boot. it wont go to TWRP nothing. I've combed XDA and found the multi tool but don't think that is working or i might be using it wrong. the computer doesn't recognize the phone. im trying to get this phone back up and going and give to my daughter . any help is greatly appreciated. thank you in advacne.

Here's what I'm talking about just in case someone asks

Try installing a stock factory image from fastboot.

runekock said:
Try installing a stock factory image from fastboot.
Click to expand...
Click to collapse
How...I can't get my computer to recognize the phone... When I plug it in it doesn't read it...I should have the drivers already installed...adb push right.... I'll search for the command to see if it finds the phone

adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.

runekock said:
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely be trying this and I'll give you an update soon

Question [Fixed] ASUS logo stucks on recovery, only access to bootloader

Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.

Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.

To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.

From the bootloader you should be able to flash the raw image again, it should flash everything

Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.

semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason

Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).

semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.

Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.

Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?

I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.