Database Users

[Q] NOT BOOTING HELP A noob please!!

OK so phone was rooted with twrp installed. decided to update to latest ota 30b only I wiped and just flashed boot file and supersu without the actual rom. I know. now the phone goes straight into fastboot mode... I would think twrp is still installed but dont seem to be able to boot into it. I had adb and fastboot on my pc from before but havent used this in some time. if I try to open either of these the command window pops up and quickly closes.. What can I do ?.
new info: fadtboot is working in fact i have wrote a twrp recovery but still cant boot out of fastboot... adb device not listed. i reinstalled minimal adb and fastboot. help

My Redmi 2 stuck at mi logo after rooting by super su app.

please help me friends.....
i have redmi 2 and its model no. is 2014818.i rooted my phone by zip file throug updater app.after installation super su app installed automatically.then i opened super su app and it prompts to select continue with normal recovery or twrp/cwm custom recovery.by mistake selected second option which is twrp/cwm custom recovery.then clicked continue.after that my phone booted and that after stucked at mi logo.
my phone is not going to recovery mode.it is stucked at mi logo.
But it is going into fastboot mode properly.also i flashed latest rom by fastboot method and it shows success result in mi flash tool.but after booting it agian stucked at mi logo.i also tried to flash by command prompt by using adb and fastboot tools.all commands i give gets executed properly but the problem is not solved
i went to Mi service center.he told me that "i will do some software update.after some time he came up and said that the phone is taking much time and stucked at mi logo.
then he assumed and told me that ,there is an issue in motherboard i.e. the motherboard is currputed.
but in my perspective i dont think so, because all the fastboot cammands and functions are woring properly.
please help me in this situation and suggest me that whether it is software issue or hardware, and also about the chances of resuming to life of my phone.

you should try to flash the firmware again but don't forget to select clean_all while flashing from mi flash tool. if your phone doesn't revives then maybe it's hardware issue.
and yes also try to install custom recovery and custom os after flashing firmware maybe your phone gets a new life.

U can't flash stock ROM by fastboot r8?
Have u tried to flash T.W.R.P by fastboot by using mi flash tool(try to use latest version of mi flash too).
And direction is here.If that succed then all is good.

not worked
Bhavesh_khatri said:
you should try to flash the firmware again but don't forget to select clean_all while flashing from mi flash tool. if your phone doesn't revives then maybe it's hardware issue.
and yes also try to install custom recovery and custom os after flashing firmware maybe your phone gets a new life.
Click to expand...
Click to collapse
I have done clean install And everything already.But not Working and now phone is not going into fastboot mode also and also not booting on pressing power button.
On connecting to pc the notification message appears and says "unrecognizable device and device may be malfunctioned".

Done already before writing this thread.
raymond_bqg said:
U can't flash stock ROM by fastboot r8?
Have u tried to flash T.W.R.P by fastboot by using mi flash tool(try to use latest version of mi flash too).
And direction is here.If that succed then all is good.
Click to expand...
Click to collapse
i tried to flash TWRP and CWM recovery By Adb and fatboot method using commands (command prompt method) amd on giving commands all executed properly but not resulted.
From now phone is not going into fastboot mode also and not booting on pressing power button.
On connecting to pc the notification message appears and says "unrecognizable device and device may be malfunctioned".sometimes it is detected as Qualcomm Device on connecting.

In that case your device is hard bricked. You need professional help.
But check if your device is listed or not in device manager if it shows an exclamation mark try to update the drivers and though your device doesn't boots into fast boot mi-flash would probably detect your phone and than flash hope it would recover your device up-to certain extent.

I only understand your problem why because I too same thing as you did.
Lavnish said:
please help me friends.....
i have redmi 2 and its model no. is 2014818.i rooted my phone by zip file throug updater app.after installation super su app installed automatically.then i opened super su app and it prompts to select continue with normal recovery or twrp/cwm custom recovery.by mistake selected second option which is twrp/cwm custom recovery.then clicked continue.after that my phone booted and that after stucked at mi logo.
my phone is not going to recovery mode.it is stucked at mi logo.
But it is going into fastboot mode properly.also i flashed latest rom by fastboot method and it shows success result in mi flash tool.but after booting it agian stucked at mi logo.i also tried to flash by command prompt by using adb and fastboot tools.all commands i give gets executed properly but the problem is not solved
i went to Mi service center.he told me that "i will do some software update.after some time he came up and said that the phone is taking much time and stucked at mi logo.
then he assumed and told me that ,there is an issue in motherboard i.e. the motherboard is currputed.
but in my perspective i dont think so, because all the fastboot cammands and functions are woring properly.
please help me in this situation and suggest me that whether it is software issue or hardware, and also about the chances of resuming to life of my phone.
Click to expand...
Click to collapse
Simply flash twrp recovery n your phone through adb drivers or contact me. I can't give you video tutorial because I don't want you make that mistake again. my mail id: [email protected]

Alrighty I think praveen66542 is not wrong.
I have actually a redmi 2 and I had exactly the same problem a year ago; I've tried all the methods but it didn't work
So i've do is :
I installed Android SDK + ADB Drivers
I Turned my phone into fastboot mode
And I wiped all data from ADB But if you don't want to loose your data you can always do a backup from ADB and then wipe device's data
I think that's the one and only working solution.

Sudden Boot-loops

Hi,
Just got an ZUK Z1 from one of my clients and the problem with the device is bootloops when trying to reach OS.
this issue came all of a sudden.
I managed to get into recovery and fastboot modes successfully but cmd won't show any serial after "fastboot devices" command but adb devices (while i'm in recovery mode via Aplly update from adb") showing serial accordingly and identify device.
when trying to push twrp or an update to CM OS in order to fix probable system files cmd replied
error: locked
i assuming it's the locked boot-loader.
even in wondershare mobilego the process stuck in 50%
i just need to backup client data.
Thanks for your kindly help,
- Oria, Israel.

Oria Maymon said:
Hi,
Just got an ZUK Z1 from one of my clients and the problem with the device is bootloops when trying to reach OS.
this issue came all of a sudden.
I managed to get into recovery and fastboot modes successfully but cmd won't show any serial after "fastboot devices" command but adb devices (while i'm in recovery mode via Aplly update from adb") showing serial accordingly and identify device.
when trying to push twrp or an update to CM OS in order to fix probable system files cmd replied
error: locked
i assuming it's the locked boot-loader.
even in wondershare mobilego the process stuck in 50%
i just need to backup client data.
Thanks for your kindly help,
- Oria, Israel.
Click to expand...
Click to collapse
I had the same problem..just reinstall twrp throw your computer ..and install the ROM you like

zukcyprus said:
I had the same problem..just reinstall twrp throw your computer ..and install the ROM you like
Click to expand...
Click to collapse
I can't because device is not recognized via fastboot and I have to save user data
Sent from my Robin using Tapatalk

In my case I erased everything...and throw my gmail I recovered everything..and don't install after cyanogen ROM ...if you can install zui xosp hexagon viper mokee or nuclearom .

Try this: https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056

Can't install TWRP on OP6T

Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?

¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
I'm having the same problem

¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
3.3.1.-1???...

cultofluna said:
3.3.1.-1???...
Click to expand...
Click to collapse
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?

¿GotJazz? said:
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?
Click to expand...
Click to collapse
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482

jp0469 said:
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Click to expand...
Click to collapse
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?

¿GotJazz? said:
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?
Click to expand...
Click to collapse
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?

jp0469 said:
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?
Click to expand...
Click to collapse
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.

¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Stick to good old ones...
Once booted in twrp via fastboot flash the installer zip. It has always worked and will always. Always latest version. And flash Magisk after.

¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Put the latest Magisk zip and TWRP installer (zip file) on your phone's internal memory if you don't already have them there. Now you can fastboot boot the TWRP img file (Q version). Next flash the TWRP zip to permanently install TWRP into recovery. Reboot back to recovery to make sure it worked and then flash Magisk to re-gain root.
Reboot

Thanks, guys - The only reason I asked about the alternate "RAM Disk" method was because it was listed as the installation method by the developer on the link that @jp0469 provided earlier.
I'll try the old-fashioned method, since y'all say that it works OK.

I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install

[email protected] said:
I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install
Click to expand...
Click to collapse
I always install the latest directly from Google. There is a link on this page to the latest version of Windows ADB and Fastboot. Just unzip the file you download into a directory of your choice.

Everytime I try to boot twrp It says waiting on device. What's that mean

[email protected] said:
Everytime I try to boot twrp It says waiting on device. What's that mean
Click to expand...
Click to collapse
It mean you didn't install driver on your PC.
---------- Post added at 03:38 AM ---------- Previous post was at 03:35 AM ----------
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
Type Command: fastboot flash boot
And Use TWRP 3.3.1.30 .

Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
Click to expand...
Click to collapse
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh

uncleheng said:
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh
Click to expand...
Click to collapse
press volume down,up and power button same time for 10sec your phone will boot to bootloader mode.

After doing the fastboot boot twrp-3.3.1-30-fajita-Q-mauronofrio.img in Fastboot Mode, I installed twrp-3.3.1-30-fajita-installer-mauronofrio.zip in the booted TWRP Recovery Mode, and everything is working fine again.
Thanks, guys!

Hey I am running Android 10.3.7 and am having the same problem, I tried unofficial twrp linked abouve and still stuck on fastboot screen, I think I'm using abd 1.43, if twrp doesn't work is there an alternative? I'm newish to rooting I've rooted other phones but that was back in the good old days where it wasn't complicated. I am running a T-Mobile phone converted to international with bootloader unlocked

Unable to install TWRP recovery on Zenfone Max Pro M1

Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.

akhil520c said:
Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.
Click to expand...
Click to collapse
Fastboot flash recovery twrp.img
Sent from my ZenFone Max Pro M1 using Tapatalk

If you can't install TWRP on pie, try reverting to Oreo with AFT and then flash TWRP in fastboot. Also make sure you have unlocked the bootloader whether by the official tool or the unofficial method. THIS WILL DELETE ALL DATA SO BACK UP.

Thanks arko. Is there Asus Flash Tool available for Linux also? Will try and revert. Thanks :svetius

Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?

akhil520c said:
Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?
Click to expand...
Click to collapse
Windows 10 ? Its bcuz Driver Signature Enforcement
Disable it and reinstall adb and fastboot drivers, it will work for sure.
Windows driver security wouldn't accept drivers without proper Signatures,so like i said, just disable it and you are good to go.
:good:

​
Tried steps you mentioned, doesn't work. In fastboot mode, #fastboot devices gives me no output. Looks like my pie ROM is buggy. Basically, I need to install lineage on the phone.

Hi all,
Finally got everything done in about 5 mins I booted up Ubuntu Mate (32 bit) on my other laptop, and found I'd already installed adb and fastboot on it from the repositories (not from google). I booted my phone in fastboot mode, and tried the #fastboot devices command, and voila, my phone got detected! After that, it was a matter of a few minutes, following the installation instructions (of twrp and lineage) from the lineage website. Thanks for all your inputs and help
P.S: I realised (again), after more than 2 decades, that windoze mighty sucks lol.