[Q] How can I access "adb" again to fix bootloop (Android)? Please Help, only simple.
Device: Huawei Y200, RecoveryMode: Clockworkmod
Ok. Here is what Happened:
- I Flashed the device using a batch file, using device's adb access.
- got a market app, mistakenly accepted an intstall request ( a clockworkmod recovery).
- It Must have tried to replace the excisting one, and somehow phone turned off.
- Phone reboot wasn't successful and it went into boot-loop ( the first bootloader logo started and won't go further/ freezes there)
- While phone was boot looping, when in frozen bootloader logo, I could connect it to the PC and gain access to its adb.
- I reflashed it, and not further changes happened. Factory reset it with Recovery Mode, and nothing was solved (still boot looping)
- I then tryed reflashing again (still gained access to adb) and nothng happened.
- Tryed wiping cache partition, then dalvik cache, the cache in "mounts and storage" selection in Recovery Mode. Nothing changed i couldn't solve Bootlooping.
- I then wanted to try a command i found that makes device go into fastboot, and connected the device to computer and found no adb when phone is in bootloader.
- Couldn't go further not seing abd device to flash it and got phone into recovery mode and tried searching for adb and found it but with "recovery" beside it (maybe haven't seen it before as maybe i flashed phone while IN recovery mode too). Tried to inputn a command and it stated "waiting for device" and phone never responded.
- I tried the batch file to reflash it and it said "waiting for device".
- Now I can't reflash the phone, use commands, access adb while in bootloader, and even when I see the adb (under recovery mode) it doesn't access the phone.
I read about how i can make the bootloader update from .img's on SD. and usefull commands to go into fastboot, resolviong boot loop (Using ADB), and using and .img that is a fastboot recovery... But i can't either access adb or when i do (under recovery mode) it doesnt respond. I didn't try .img's yet, or read more about .img's with fastboot recovery. Please help and if any other details needed please inform.
Thank you...
Hello, first post and fisrst tutorial here.
So here I want to show you how you can restore completely died LG p760(or his brothers p765/p768/p769) showing nothing or just LG Logo and so well known "Security Error", or boot loop problems.
The goal is to flash stock recovery, x-loader and u-boot and to unlock the bootloader(u-boot), so it can boot Clockworkmod or TWRP recovery.
First of all you'll need a computer(preferably Win7/8), an died phone , some drivers on the computer and fastboot on the phone. Let's start.
I'm not responsible for any damage to your device made during this guide. You can continue at YOUR OWN RISK.
Please READ IT before taking any actions on your phone!
1. Get fastboot on the phone. How? You can see here and here, or search the internet. There is a driver package, install them following the instructions.
2. After you inserted phone, installed drivers, etc. start the fastboot loader script(I prefer Lelus's one, i'ts more option-rich), and select one option for ICS x-loader and u-boot for your phone. Follow the instructions, it may take 2 or 3 tries before the drivers are correctly installed. Start again if the drivers are not correctly installed.
3. Copy the bin folder that is inside the fastboot files folder in C:, press winkey+R, type cmd and press OK.
Then copy everything from v20c_00 folder inside the C:\bin\ folder, it's in attachments in the end.
Here is the time to say that this files are for p760 only, you can find x-loader, u-boot and stock recovery for you model from internet, or here in the forums. I flashed also the boot.img, but don't think it's necessary for the completion of the process. You can also extract the .img files from stock .KDZ rom with this tool here, thanks to user kuma82. In the archive is the tutorial how to make x-loader.img, it's easy.
Let's continue.
Type in:
Code:
cd C:\bin
Check if the phone is in fastboot mode with this command:
Code:
fastboot devices
It must show something like:
Code:
1234567890 fastboot
If not, check that you are in the correct folder(C:\bin\), go and check drivers(no yellow marks or unknown devices), read the instructions again.
Then after you copied the files from archive, or files that you extracted from your stock rom, type in, or copy and paste into the cmd window:
Code:
fastboot erase x-loader
fastboot erase u-boot
fastboot erase boot
fastboot erase recovery
fastboot flash x-loader 0-x-loader.img
fastboot flash u-boot 1-u-boot.img
fastboot flash boot 2-boot.img
fastboot flash recovery 3-recovery.img
You must be fast, because after 30-60 seconds(don't know exactly) of inactivity, the phone will exit the service mode it is in and try to boot. Nothing bad happened, just load fastboot again and repeat the above fastboot commands.
After all the commands are completed without any errors, plug out usb, plug out battery, put the battery in, start the phone. The "Security Error" message MUST be gone. If it's not, probably your recovery is wrong, flash recovery again, if not, try with other recovery. This is working on P760, at least on mine. Here the S/W Update mode must also work like a charm, and you can try with some KDZ updaters, but that's not for this tutorial.
4. Now for step 4 we will need the phone in Recovery Mode. With phone turned off and battery inserted, press VOL_UP+HOME+POWER, when LG logo shows, release POWER and hold other two while the LG Recovery Mode show up. The phone must go straight into recovery, not bootlooping or showing "Security Error". If this happens, probably you recovery or u-boot is wrong.
Now put the usb into the phone and install the drivers from usb_drv_windows folder that is in the fastboot archive.
5. Type into cmd window:
Code:
adb devices
It must show something like:
Code:
1234567890 recovery
If not, you know..
Then we will unlock the bootloader with this command:
Code:
adb oem-unlock
The phone will restart, don't touch nothing. You'll see screen with info on what to do. Guess what..? We must press the VOL_UP button to confirm that we want to UNLOCK the bootloader, so it can load unsigned recoveries like CWM or TWRP and not to show the annoying "Security Error".
6. The phone will go into fastboot mode itself, you must install the drivers, again from the folder in the archive.
Now we'll flash CWM recovery with the help of fastboot. Copy the recovery-clockwork-6.0.2.9-p760 or recovery that is for your model to C:\bin\ folder.
Write:
Code:
fastboot flash recovery recovery-clockwork-6.0.2.9-p760.img
fastboot reboot
The phone will reboot, and hopefully you will not see "Security Error" error message. Now try to boot into recovery - pull the battery out, the usb cable, put battery in, and hold down VOL_UP+HOME+POWER, you know..
7. If everything is successfull you phone will load the recovery and you will be able to load nandroid backup or stock update.zip or CyanogenMod on your phone. Don't forget to wipe cache/data and dalvik's cache. From here you can backup your data or do whatever you want.
If your phone is not totally bricked, and if you are lucky enough you can continue from step 4(if you have recovery in your phone and it's still loading).
DOWNLOAD
I want to attach them here to the forum, but I can't for now, so here is Google Drive folder.
https://drive.google.com/folderview?id=0B9wMsz4X38L2aE5VdGFZcWczcEk
[I]Root twrp for bluboo Edge-
Disclaimer-
Code:
1. Do always on own Risk i am not responsible for bootloop and damage
2. take a backup before flashing supersu,
3. follow steps correctly
How to Install twrp-
Run Sp flash tool
Load Scatter, Check recovery only
Load twrp under recovery Section, click download,
Connect your Phone to PC [ make sure phone is switched off]
Fastboot-
put recovery in adb folder
use command-
Code:
fastboot oem unlock
fastboot flash recovery [file name here][file format here]
ex, fastboot flash recovery twrp.img
Root-
flash supersu.zip [2.79] via twrp
twrp Bug-
adb shell not work
Credit-
unknown
me to share with you
Downloads-
mod edit - link removed
After flashing twrp with sp flash tools, i am not able to enter into recovery, however i push volume up + power buttons... Phone keeps booting into normal android mode instead.
USB Vcom driver successfully installed, and spflash tool seems to work fine. Any ideas?
After flashing:
reboot with vol-down and power in that "chinese recovery thing" (look like this http://visihow.com/images/9/99/Samsung-chinese-factory-reset.png )
then connect phone with pc and reboot with adb in "real" recovery (adb reboot recovery)
if you boot normal first, recovery gets overwritten by default recovery
I boot into bootloader by pressing home button + power
adb reboot recovery
Dont boot to twrp
I flashing recovery, but I dont boot to twrp. Which version twrp you used?
So, I recently tried to root my Redmi 5 phone and install Lineage OS into it. This is my first time doing it, so I believe I may not have understood the words I had been reading well. Due to this, I'll try to be as descriptive as possible with the actions I had taken that led to my device being stuck.
I had followed this guide, for the most part: https://www.getdroidtips.com/lineage-os-17-xiaomi-redmi-5/
As per the guide, I performed the following actions:
Enabled the developer options
Registered my device to my Mi account
Enabled USB debugging, OEM unlocking
Rebooted in fastboot mode using the ADB tools through CMD (adb reboot bootloader)
While in fastboot mode, I used the Mi Unlock tool to unlock my device.
As per my understanding, these steps would unlock the bootloader. I rebooted my device, set it up (the phone behaves as if freshly booted) and checked the settings menu after enabling developer options again. It shows the bootloader is already unlocked and that Mi Account status is also unlocked. I enabled the USB debugging options again and carried on with the guide.
I then downloaded the rosy TWRP file (version 3.5, I think).
I even downloaded GApps and Lineage 18.1 OS
I tried to copy the above files into my Redmi 5 internal storage
The Lineage and GApps file failed to copy, but I was able to copy the TWRP file
One thing to note here, I am not sure if my USB cable is faulty or if my phone's micro USB port is faulty or if my laptop's USB ports are faulty. When the phone is connected to my PC, it is extremely lousy. If I shake the cable even a bit, it disconnects and reconnects. When I try to use the file explorer to copy the files from my laptop to the android phone, it usually fails for large files or large quantities of small files. I believe this was the reason behind the failure. Nonetheless, I decided to do the TWRP part first.
The guide said to reboot in recovery mode and that would take me to TWRP recovery mode. Well, it did not! It took me to a menu that had the following options:
Reboot
Reboot to System
Back to Main Menu
Wipe Data
Wipe All Data
Back to Main Menu
Connect to MIAssistant
I assumed I had entered recovery mode incorrectly, so I followed the link in the guide on how to enter recovery mode. It suggested using the ADB tools.
I used the command: adb reboot recovery
It did the same thing that I had done. So, I assumed that that is the recovery mode, but I am unable to enter TWRP recovery mode. There was another link that would show me how to do this.
I followed that link and downloaded the files that was mentioned. However, the guide tells little to nothing on what to do with these files. The only file that was used was the rosy twrp file.
I enabled the USB debugging mode on my phone.
Opened CMD from the folder with ADB
Entered the command: adb reboot bootloader
Phone enters fastboot mode
Entered the command: fastboot devices
I can see that a device is connected
Entered the command: fastboot flash recovery rosy-3-5.img (I renamed it for convenience, I believe that was allowed because every website had different name for their file)
I then rebooted into recovery mode by first rebooting it normally: fastboot reboot
Then entering the command: adb reboot recovery
It still showed the same old recovery menu. Nothing had changed. I looked around the internet and found that I could boot with the TWRP image by entering the command: fastboot boot rosy-3-5.img
This opened the screen that I was expecting, but it did not open the chinese menu at all. It directly went to the screen that had options such as Install, Wipe, etc.,
I rebooted normally and then tried to transfer the GApps file and Lineage file into my phone. As usual, it was failing. I tried to use the adb push command and it still failed but with an error saying "permissions denied"
At this point, I looked up how to get root permissions and I learnt that I had to root my device. I looked up how to root with Magisk and SuperSU. The guides all required me to boot in TWRP recovery and then install the files from my phone. Unable to transfer the files to my phone, I uploaded the files to my google drive, and manually downloaded into my phone. I boot up rosy (TWRP recovery, or so I think) using ADB tools. Unfortunately, it does not recognize any of the files in my internal storage. Everything is empty.
Defeated by this, I decided to let it go. I had a factory reset Redmi 5 at the time. I then watched a video that showed how to root with Magisk, but wasn't specific to Redmi 5, it was a generic video for android devices.
I installed the magisk manager apk into my android phone.
Then I copied the boot.img file from the Lineage folder into my android device. Despite the OS being 600 MB large, the boot.img file was only 11 MB.
Anyway, I patched the boot.img file using magisk manager.
It created a file called magisk-patched_1pTOD.img (I'm a bit unsure of the name, but it was similar to that).
The video said that I should copy this file into my laptop and then reboot my phone into fastboot.
Once in fastboot, I had to enter the command: fastboot flash boot magisk-patched_1pTOD.img
I believed that this would root my device and grant me root access. I don't know what my actions were actually supposed to do, but my device is unusable for all intents and purposes. I rebooted the device and it shows the Mi logo for a brief moment and there's no light. An empty dark screen, it's not even a black screen. It's like the display fails to work. I can switch into recovery mode and into fastboot mode but normal reboot did the same.
Thinking that I bricked my phone, I tried to unbrick it.
I downloaded the fastboot rom for Redmi 5 rosy and then installed the Mi Flash tool along with the drivers for it.
I then selected the correct ROM folder (it kept showing up as can't find flash script until I was in the right folder for it)
Rebooted my phone into fastboot mode
Hit refresh on the Mi Flash tool
It showed my device
I chose Clean All option
I hit flash
It goes up till 97%-ish and then fails with an error saying "flash system error".
However, I noticed that now, I can see that the Mi Logo doesn't disappear now. I can still go into recovery mode and fastboot mode, but normal reboot takes me to the permanent Mi Logo Screen. I cannot even shut it down. It auto reboots to the Mi Logo Screen if I do so.
I connected my device to my laptop and then opened the ADB tools.
I entered the following command to see if it's recognized by adb:
adb devices
It did not. I then switched to fastboot mode manually by pressing the Vol Down and Power buttons.
Then entered the following to see if it is recognized in fastboot mode:
fastboot devices
It showed my device there. So I used the following command to reboot and see if it is recognized in fastboot again:
fastboot reboot
While it shows the Mi Logo screen, I typed the command:
fastboot devices
It still shows my device.
I concluded that my device is in an infinite fastboot loop. I cannot boot it up normally. I cannot flash the Redmi 5 ROM into it either. I cannot use my phone.
If anybody has actually gone through this entire mess that I made, and has figured out what went wrong or at least how to fix it, please help me.
Message me on telegram @benzoylperoxide
Hope I could help you with this situation.
If you got data, download fastboot rom based on nought and fastboot rom 9.5.30
Download latest miflash tool from miglobe website.
Install proper drivers from miunlock tool zip file.
And Hope for the best.
Ping me tommorow at anytime.
Good night Bro
incertam7 said:
So, I recently tried to root my Redmi 5 phone and install Lineage OS into it. This is my first time doing it, so I believe I may not have understood the words I had been reading well. Due to this, I'll try to be as descriptive as possible with the actions I had taken that led to my device being stuck.
I had followed this guide, for the most part: https://www.getdroidtips.com/lineage-os-17-xiaomi-redmi-5/
As per the guide, I performed the following actions:
Enabled the developer options
Registered my device to my Mi account
Enabled USB debugging, OEM unlocking
Rebooted in fastboot mode using the ADB tools through CMD (adb reboot bootloader)
While in fastboot mode, I used the Mi Unlock tool to unlock my device.
As per my understanding, these steps would unlock the bootloader. I rebooted my device, set it up (the phone behaves as if freshly booted) and checked the settings menu after enabling developer options again. It shows the bootloader is already unlocked and that Mi Account status is also unlocked. I enabled the USB debugging options again and carried on with the guide.
I then downloaded the rosy TWRP file (version 3.5, I think).
I even downloaded GApps and Lineage 18.1 OS
I tried to copy the above files into my Redmi 5 internal storage
The Lineage and GApps file failed to copy, but I was able to copy the TWRP file
One thing to note here, I am not sure if my USB cable is faulty or if my phone's micro USB port is faulty or if my laptop's USB ports are faulty. When the phone is connected to my PC, it is extremely lousy. If I shake the cable even a bit, it disconnects and reconnects. When I try to use the file explorer to copy the files from my laptop to the android phone, it usually fails for large files or large quantities of small files. I believe this was the reason behind the failure. Nonetheless, I decided to do the TWRP part first.
The guide said to reboot in recovery mode and that would take me to TWRP recovery mode. Well, it did not! It took me to a menu that had the following options:
Reboot
Reboot to System
Back to Main Menu
Wipe Data
Wipe All Data
Back to Main Menu
Connect to MIAssistant
I assumed I had entered recovery mode incorrectly, so I followed the link in the guide on how to enter recovery mode. It suggested using the ADB tools.
I used the command: adb reboot recovery
It did the same thing that I had done. So, I assumed that that is the recovery mode, but I am unable to enter TWRP recovery mode. There was another link that would show me how to do this.
I followed that link and downloaded the files that was mentioned. However, the guide tells little to nothing on what to do with these files. The only file that was used was the rosy twrp file.
I enabled the USB debugging mode on my phone.
Opened CMD from the folder with ADB
Entered the command: adb reboot bootloader
Phone enters fastboot mode
Entered the command: fastboot devices
I can see that a device is connected
Entered the command: fastboot flash recovery rosy-3-5.img (I renamed it for convenience, I believe that was allowed because every website had different name for their file)
I then rebooted into recovery mode by first rebooting it normally: fastboot reboot
Then entering the command: adb reboot recovery
It still showed the same old recovery menu. Nothing had changed. I looked around the internet and found that I could boot with the TWRP image by entering the command: fastboot boot rosy-3-5.img
This opened the screen that I was expecting, but it did not open the chinese menu at all. It directly went to the screen that had options such as Install, Wipe, etc.,
I rebooted normally and then tried to transfer the GApps file and Lineage file into my phone. As usual, it was failing. I tried to use the adb push command and it still failed but with an error saying "permissions denied"
At this point, I looked up how to get root permissions and I learnt that I had to root my device. I looked up how to root with Magisk and SuperSU. The guides all required me to boot in TWRP recovery and then install the files from my phone. Unable to transfer the files to my phone, I uploaded the files to my google drive, and manually downloaded into my phone. I boot up rosy (TWRP recovery, or so I think) using ADB tools. Unfortunately, it does not recognize any of the files in my internal storage. Everything is empty.
Defeated by this, I decided to let it go. I had a factory reset Redmi 5 at the time. I then watched a video that showed how to root with Magisk, but wasn't specific to Redmi 5, it was a generic video for android devices.
I installed the magisk manager apk into my android phone.
Then I copied the boot.img file from the Lineage folder into my android device. Despite the OS being 600 MB large, the boot.img file was only 11 MB.
Anyway, I patched the boot.img file using magisk manager.
It created a file called magisk-patched_1pTOD.img (I'm a bit unsure of the name, but it was similar to that).
The video said that I should copy this file into my laptop and then reboot my phone into fastboot.
Once in fastboot, I had to enter the command: fastboot flash boot magisk-patched_1pTOD.img
I believed that this would root my device and grant me root access. I don't know what my actions were actually supposed to do, but my device is unusable for all intents and purposes. I rebooted the device and it shows the Mi logo for a brief moment and there's no light. An empty dark screen, it's not even a black screen. It's like the display fails to work. I can switch into recovery mode and into fastboot mode but normal reboot did the same.
Thinking that I bricked my phone, I tried to unbrick it.
I downloaded the fastboot rom for Redmi 5 rosy and then installed the Mi Flash tool along with the drivers for it.
I then selected the correct ROM folder (it kept showing up as can't find flash script until I was in the right folder for it)
Rebooted my phone into fastboot mode
Hit refresh on the Mi Flash tool
It showed my device
I chose Clean All option
I hit flash
It goes up till 97%-ish and then fails with an error saying "flash system error".
However, I noticed that now, I can see that the Mi Logo doesn't disappear now. I can still go into recovery mode and fastboot mode, but normal reboot takes me to the permanent Mi Logo Screen. I cannot even shut it down. It auto reboots to the Mi Logo Screen if I do so.
I connected my device to my laptop and then opened the ADB tools.
I entered the following command to see if it's recognized by adb:
adb devices
It did not. I then switched to fastboot mode manually by pressing the Vol Down and Power buttons.
Then entered the following to see if it is recognized in fastboot mode:
fastboot devices
It showed my device there. So I used the following command to reboot and see if it is recognized in fastboot again:
fastboot reboot
While it shows the Mi Logo screen, I typed the command:
fastboot devices
It still shows my device.
I concluded that my device is in an infinite fastboot loop. I cannot boot it up normally. I cannot flash the Redmi 5 ROM into it either. I cannot use my phone.
If anybody has actually gone through this entire mess that I made, and has figured out what went wrong or at least how to fix it, please help me.
Click to expand...
Click to collapse
Flash system error in MiFlash? Probably the stock rom you downloaded and extracted is corrupted.
Please try flashing MIUI 9 for your Redmi 5.
Yeah, users have had issues with twrp being replaced by stock rom.
For TWRP,
fastboot flash revovery (recovery name.img)
Fastboot boot (recovery name .img)
After that flash your custom rom after wiping system,boot, vendor, data and cache, Internal format might be needed if it's encrypted.
Then, after custom rom is flashed, flash gapps and then twrp zip in TWRP, yeah you saw it right, flash twrp zip in TWRP. This way, twrp won't get replaced.
You can give directly flashing TWRP and flashing custom rom the way I told, Flashing Miui isn't important if your goal is to flash custom rom.
TLDR: phone stuck at boot screen. Still can access fastboot mode and twrp recovery mode.
I shouldn't have dived into these stuff without proper knowledge. I wanted to root my phone (redmi note 5a lite) so I unlocked bootloader and ran fastboot flash recovery (attach .img) with bugjaeger app and otg. But after pressing volume up + power, the stock recovery was showing. So I ran fastboot flash recovery (attach .img) again. Still didn't work. So I saw a random tutorial (dumb idea) and renamed the img file to recovery.img. then I ran fastboot flash recovery (attach recovery.img) then ran fastboot boot (attach recovery.img) then twrp opened and I thought everything was good. Then I clicked reboot>system in twrp and my phone is stuck on boot screen. Long clicking the power button gives a little screen off and on and it gets stuck at boot again. I still can access fastboot mode and twrp recovery mode by draining battery and then using bugjaeger app and otg.