Database Info

Device stuck in Bootloop | Can Access Fastboot | Commands don't work

My Oneplus One - 64GB was running LiquidSmooth's Alpha ROM.
I hadn't used the phone in like a month. A couple of days ago i thought there'd be an updated version so i just downloaded a later version. I think I flashed the 01-22 Build.
I did not do a full wipe however. (I realize now that It would have been a good idea to do a full wipe before the flash. :s )
I assumed that since the base of the ROM was the same lollipop, all I had to do was wipe cache/dalvik and flash the update.
Installation proceeded as usual and I wiped cache/dalvik(I'm never sure when to do this so i do it before and after install) once more and then Reboot System.
But the phone went on a bootloop for like 10minutes or so.
I tried to get into Recovery but it just wouldn't. It would just show the 1+ Logo and Powered by android screen and then turn off..
I did however manage to get into the fastboot mode by pressing power +vol up.
Now the problem is, the device doesn't show up in the command prompt when i type
Code:
fastboot devices
I uninstalled all the usb drivers from my pc.
Installed the Universal ADB drivers from kouch's site but still no progress..
Device manager still shows the phone as an unknown device.
What am I doing wrong? What can i do to get the phone to be recognized so I can flash the recovery and flash a new ROM?

It's related of firmware change. After 01.17.2015 you must flash the latest CM12 rom and then flash the rom you want.
That's a known "issue". Hope it helps.

Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.

thetearer said:
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
Click to expand...
Click to collapse
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.

timmaaa said:
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
Click to expand...
Click to collapse
That's the order I did stuff in last time I believe. I'll try it again and report back

How to install TWRP into the LG P500H from Koodo?

I have a Koodo LG P500H. I am having a very hard time installing TWRP.
Firstly Play store doesn't work. It has this old thing called "Market" that has some apps, but not all. Market eventually gets updated to Playstore, but I can't even find TWRP manager. There was another app in the Playstore that I tried called ROM Manager. It said it installed TWRP for me. I restarted the phone, and nothing happened.
Restarting and Holding power/volume down/home will show a picture that seems to be some sort of recovery mode. But it only run for 1-2 seconds before the phone restarts itself. Nothing happens.
I tried to use ADB. But after rebooting the device it just restarted without ever going into recovery mode. So the flash command just get stuck at "Waiting for Device." Does this phone even have a recovery mode?
This phone doesn't support Odin.
I am used to using TWRP. Without it I cannot flash the phone into new OS.
And every single time I fail, the whole phone seems to have reformatted. So I have to enter in my wifi password and gmail again. All of that typing on a very small keyboard takes a lot of time. I had spent hours on this phone without getting TWRP working.
Please help.

going to twrp web site here
downloading the recovery
reboot to fastboot ( bootloader ) than using terminal whit adb driver :
fastboot flash recover '' recovery.img ''

Gw4nM4n said:
going to twrp web site here
downloading the recovery
reboot to fastboot ( bootloader ) than using terminal whit adb driver :
fastboot flash recover '' recovery.img ''
Click to expand...
Click to collapse
The problem is when I reboot into fastboot (adb reboot bootloader), the phone will go into "phone off battery charging mode". It never actually goes into the bootloader.

Ok I did the following and it seems fastboot and TWRP works now. Be sure to enable USB Debugging on your P500.
1) Fastboot tutorial (I did everything here. I hit "ok" on the LGMDP 1.5 tool as needed. Do not wait till the countdown timer goes to zero.)
http://forum.xda-developers.com/showpost.php?p=15122833&postcount=100)?
FastBoot Tutorial
1. Please download this (or from here) file and unzip it in to any folder.
2. Start LGMDP 1.5 tool with the phone connected (you need to have USB drivers installed) and click on Select Port
3. A separate window should appear like the one below
Just click connect
4. Another window will take shape (LGE Mobile security) with lots of options (links)
Click on the first upper right Browse and select the folder in with you have unzipped the files. You will get some errors that some image, table or headers are missing. Just click OK and in the end everything that should remain selected is Partition Table, APPSBL Image Header and APPSBL Image.
Now just close the window (click on x)
5. Now you are back on the main window and here you'll have to click on Download
6. You are almost done and from now on everything should go on automatically.
NV Backup
Autorestart in Emergency\Download mode and upgrade the files (you selected on step 4)
NV Restore (the last step) Do not disconnect the USB cable until the restore is done
Wait for the phone to restart in normal mode (your current rom).
That should be everything you need to do to get fastboot enabled.
Click to expand...
Click to collapse
2) Install PdaNet+ (This was the only thing I did in this tutorial. It fixed the usb driver and the fastboot can then communicate with my PC.)
http://forum.xda-developers.com/showthread.php?t=1350733
http://pdanet.co/a/
(Note: On top of Partition Table, APPSBL Image Header and APPSBL Image in step 4, I also selected the TWRP image file as my RECOVERY image. Not sure if this make a difference. )
(Note 2: I think you can also get the LG drivers here.)
3) Restart, hold down power + home to boot to the fastboot. Or in ADB type adb reboot bootloader.
4) Open ADB (while phone is still in fastboot mode) and type fastboot flash recovery twrp.img (after downloading the TWRP image, renaming it and moving it to my ADB root folder. I am using TWRP 2.8.0.1 here.)
5) Type fastboot reboot
6) After the phone restarts, type adb reboot recovery. TWRP runs for me. Power+Home+Volume Down (3 button combo) also works now. (Previously this would reset the phone.)

Hey Man, im glad it worked. I could use your help.
I bricked my phone and need the restore file, Do you think you could make a backup from TWRP and upload it?
I would be super grateful.
Thank you.
Here is a zip with CM11, twrp 3.0.2.0 and Gapps for CM11.
Its the best rom I found.
https://www.dropbox.com/s/qt7z1cxq92nhpz5/LgP500CM11V4.4.4.zip?dl=0

Hi. What is your "brick" like? Does your TWRP still run? If yes you can just copy a custom OS into your Microsd card and install it from your Microsd.
You can also use ADB push to move files from your PC to the phone.
http://www.androidauthority.com/android-customization-transfer-files-adb-push-adb-pull-601015/
Sent from my MT2L03 using XDA-Developers mobile app
If you TWRP doesn't run, you need to install that first. Do steps 3 and 4 in the above post to boot into bootloader and install TWRP.
3) Restart, hold down power + home to boot to the fastboot. Or in ADB type adb reboot bootloader.
4) Open ADB (while phone is still in fastboot mode) and type fastboot flash recovery twrp.img (after downloading the TWRP image, renaming it and moving it to my ADB root folder. I am using TWRP 2.8.0.1 here.)

S7 G930T Booting issue (Even after upgrading OS via Odin)

Hello Everyone,
I hope you are doing good, Cant run my S7 G930T mobile.
I have upgraded OS via Odin, it passed but phone is not getting work.
Sometimes it doesn't open recovery boot and gets stuck at Recovery Booting.....
Sometimes it restart from the installing applications screen.
If you have any files for binary 11 (B) or anything i need to do before flashing OS via Odin.
Please help me
I'd be very thankful to you.
Thanks!
[email protected]

sabeel43 said:
Hello Everyone,
I hope you are doing good, Cant run my S7 G930T mobile.
I have upgraded OS via Odin, it passed but phone is not getting work.
Sometimes it doesn't open recovery boot and gets stuck at Recovery Booting.....
Sometimes it restart from the installing applications screen.
If you have any files for binary 11 (B) or anything i need to do before flashing OS via Odin.
Please help me
I'd be very thankful to you.
Thanks!
[email protected]
Click to expand...
Click to collapse
Can you be more specific about your booting issues?
Is the device boot looping? How far through the booting process do you get before failure? and what happens after failure?
Can you get your phone into recovery mode or download mode?

ReboundGuy said:
Can you be more specific about your booting issues?
Is the device boot looping? How far through the booting process do you get before failure? and what happens after failure?
Can you get your phone into recovery mode or download mode?
Click to expand...
Click to collapse
Sometimes it gets ON normally and after some time it reboots itself and then it keeps doing it again and again, and sometimes it gets on and goes straight to the recovery mode, and yes i can get my phone into download mode too.

If you have precious data you want to keep, then you should create a back up of your phone, if you haven't already done so.
If you're unconcerned about data or have created a backup, then you could factory restore from recovery mode.
Alternatively, if you haven't got the latest version of Odin, then you could try downloading the latest Odin software and attempt another flash.
Another thing you could try, is to sideload the update via adb. You will of course need the latest adb software which is easy to find. You can follow this xda guide here (https://www.xda-developers.com/install-adb-windows-macos-linux/), or if you prefer it you could download Android Studio from here (https://developer.android.com/studio).
To sideload the update you will have to:
1. Boot phone into recovery mode. Hold the volume up, home, and power buttons, and then let go of the power button when it power on.​2. When in recovery mode, select the option, "Apply update from ADB."​3. With your phone plugged into the computer, open the cmd/terminal and type "adb devices". The cmd should start up adb and display something like:​List of devices attached​[device id] sideload​4. Navigate to the folder that contains the update file. It needs to be a .zip file.​5. Type in the command, "adb sideload [file name]".​
To make things easy you can set up adb so you can run its commands from any directory, the steps for this are covered at the end of the xda guide I have linked.

ReboundGuy said:
If you have precious data you want to keep, then you should create a back up of your phone, if you haven't already done so.
If you're unconcerned about data or have created a backup, then you could factory restore from recovery mode.
Alternatively, if you haven't got the latest version of Odin, then you could try downloading the latest Odin software and attempt another flash.
Another thing you could try, is to sideload the update via adb. You will of course need the latest adb software which is easy to find. You can follow this xda guide here (https://www.xda-developers.com/install-adb-windows-macos-linux/), or if you prefer it you could download Android Studio from here (https://developer.android.com/studio).
To sideload the update you will have to:
1. Boot phone into recovery mode. Hold the volume up, home, and power buttons, and then let go of the power button when it power on.​2. When in recovery mode, select the option, "Apply update from ADB."​3. With your phone plugged into the computer, open the cmd/terminal and type "adb devices". The cmd should start up adb and display something like:​List of devices attached​[device id] sideload​4. Navigate to the folder that contains the update file. It needs to be a .zip file.​5. Type in the command, "adb sideload [file name]".​
To make things easy you can set up adb so you can run its commands from any directory, the steps for this are covered at the end of the xda guide I have linked.
Click to expand...
Click to collapse
I tried to update from ADB but it said, unauthorized access!
and I also think it is a hardware issue

Can you start in safe mode?

ReboundGuy said:
Can you start in safe mode?
Click to expand...
Click to collapse
Yes if it boots normally and then i can go safe mode too.

Just so you know, I'm running out of ideas. Can you try the other suggestion that I mentioned above?
The one where I suggested flashing through Odin again?
I'm kind of assuming that USB Debugging and OEM Unlock were turned on as well.

ReboundGuy said:
Just so you know, I'm running out of ideas. Can you try the other suggestion that I mentioned above?
The one where I suggested flashing through Odin again?
I'm kind of assuming that USB Debugging and OEM Unlock were turned on as well.
Click to expand...
Click to collapse
now Its not turning on , not even on charging

Ikes! Are you able to try and downgrade to your original stock firmware? Seems like the issues began with trying to update.

where can I download original stock firmware from the internet? Can you provide me the link kindly? Last time I used Frija (desktop app) to download firmware.

Pretty much everyone on xda (including me) uses this website for firmware: https://www.sammobile.com
You have to create a free account but it's worth it for all the firmware they have available.
I believe you already know this, but I'm just going to cover the bases anyway, make sure to download firmware for your specific model G930T.

How to root zenfone 7 ZS670KS

hello guys
how do i root this phone please.
none of the google searched guides seem to work.
1. i've unlocked the bootloader using the asus app
2. i have adb installed on my pc
3. i've enabled usb debug mode on phone and allowing installation unknown apps
4. i've installed magisk v23 by downloading from github and just installing the apk file normally
5. i've downloaded a 2.9gb zip file from asus for androind 11 firmware onto phone and pc (but its a zip file that extracts a bin file, no image file)
my problem seems to be i don't know how to CREATE AND PATCH an image file or install twrp and install image file that way.
Could someone help, there doesn't seem to be any guides for rooting in this phones forum.

Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip

Seosam said:
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Click to expand...
Click to collapse
i keep getting era waiting for device when i want to flash the phoben with twrp.
adb reboot bootloader (works and i enter the recovery menu start, bootloader, recovery, power off etc)
fastboot flash recovery_a twrp.img (when i type this cmd power shell just says waiting for device)
i have universal drivers installed and android sdk installed. not sure why it isn't recognising the phone?
When my phone is switched on normally, cmd recognises it, when i use adb devices. but as soon as i reboot into recovery mode using cmd "adb reboot bootloader" it stops recognising the phone on the list of devices using the cmd "adb devices"

so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?

Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
no answer from phone when in fastboot mode.
but i do get a reply in cmd when phone is switched on normally.
I'll try with another cable, but if it responds to adb when in normal mode. doesn't it mean it's not a cable issue but a software driver issue?

Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?

is it possible to root using adb sideload or install twrp using adb sideload?

articoceanic said:
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
Click to expand...
Click to collapse
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.

Seosam said:
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Click to expand...
Click to collapse
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.

articoceanic said:
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
Click to expand...
Click to collapse
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.

Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
i think its definitely a driver issue. windows 10 seems to be overriding the drivers and installing wrong ones. and won't let me install right ones.
haven't tried in a different pc. will need to get hold of one and try.

Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
dont'know what happened. but weirdly i used usb 2.0 as you said and the driver listed on page 2 of this link got recognised.
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 7 Series
*** Disclaimer *** All flashing is done at your own risk! While nothing from this thread should break your device, don't come back here blaming anyone if it does! Introduction Team Win Recovery Project 3.x, or twrp3 for short, is a custom...
forum.xda-developers.com
all this time windows 10 wouldn't let me install it. kept saying the drivers i already had was the best ones. but weirdly this time it did.
thanks friend. i think i have root access now. magisk keeps asking me to install the app tho. not sure why. i have version 23.0 installed.
but when i opne magisk it shows install icons for magisk and an unknown App. both listed as version 23.0.

Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.

articoceanic said:
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
Click to expand...
Click to collapse
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer

decade 1 said:
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
Click to expand...
Click to collapse
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more

articoceanic said:
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
Click to expand...
Click to collapse
I try factory reset normal again I hope no recurrence

[Q] Adb devices command don't work while in fastboot and EDL mode

I have access to fastboot and EDL mode. Does this mean that I can also access the mode that will show the phone after the adb devices command?

If device gets booted into FASTBOOT or EDL mode then it can't additionally get accessed via ADB: this can only get achieved when device got booted into RECOVERY mode.
To clarify:
ADB ( short for Android Debug Bridge ) deals - as its name implies - with a device's Android OS.
FASTBOOT deals - as its name implies - with device's bootloader, if that isn't bricked.
EDL ( short for Emergency Download Mode ) - specific to devices with a Qualcomm Snapdragon chipset - deals with the device itself, is used if bootloader is bricked.

Thank you for your quick help. Is it possible to access adb during bootloop?
I entered something called recovery mode, but the computer doesn't recognize that any device has been connected - adb devices doesn't see anything either.
On one of the pages I read this information:
Spoiler
Ed Reynolds says:
December 2, 2018 at 4:31 am
Unfortunately, there really is no “recovery” per set, yet. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a simpler form of phone. There are no options to go into bootloader or Fastboot mode. ADB won’t get you there. Sometimes, using ADB, you can boot into a simple android recovery with no command! There you remain until hard booting back it back into full functionality. Developer is apparently working on it
Reply
Deepak Gupta says:
December 2, 2018 at 4:38 am
Hi Ed Reynolds,
Thanks for sharing your knowledge. We appreciate your efforts. Yes, stock recovery doesn’t offer many options. One has to install a custom recovery like TWRP to get over this problem and to maximize productivity.
Reply
Ed Reynolds says:
December 8, 2018 at 7:48 pm
That is correct. but, in order to install a custom recovery, one must be able to get into bootloader, in some way. Either through physical buttons or through the ADB tool. forget about using the physical buttons – they get you to the recovery that you mention, but cannot get you into Fastboot (bootloader) mode. If you use the ADB tools while in this particular recovery mode, and try to reboot into bootloader mode from there, it boots back into the system. So, using that route, you cannot ever get to a place where you can install TWRP or anything else, for that matter – including applying an unlocking code if one were available. Next, if you try to get into recovery mode using the ADB tools (not the physical buttons, you do arrive at a more “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this problem before and sometimes, using the physical buttons, you can reveal commands at this stage. However, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, you use the ADB tools to boot into bootloader mode, you return to the system! The result is, again, you cannot install any sort of custom recovery because there is no internal or external way to flash it. If you have overcome this problem, please share! It is very frustrating! Thanks. Ed
Does this mean that I will need to flash custom recovery to gain access via adb during bootloop?

Android's Recovery is nothing else than a minimalistic working Android OS, comparable to Windows Recovery Environment ( WinRE ), so it's accessible via ADB.
A Custom Recovery ( like TWRP ) isn't needed at all, because such a only is an UI version operable by touches.

So if Windows don't see device when is in recovery mode (but recognize correctly when is in fastboot mode), there is a problem with drivers?
I want to access to adb pull for backup. Device is rooted with unlocked bootloader and allowed USB debugging and no PIN password, but bootlooped after trying to restart after uninstalling YouTube app

OMG
when in Recovery mode then you've to connect device via USB-cable with computer and you can launch adb pull command on computer.

When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list

Then obviously USB Debugging didn't get enabled in Android's Developer Options.

Robert997 said:
When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list
Click to expand...
Click to collapse
As the other user said, USB Debugging is not enabled or proper drivers are not installed. The drivers for fastboot and adb are different. Search for correct drivers, disable driver signing in Windows and install the drivers.