Hi everyone,
This guide is intended for only snapdragon version of Lenovo devices which supports QFIL (Qualcomm Flashing Tool). For MediaTek Devices, you need different tools.
However, please understand that the device which I had to test in length was LENOVO K5 PLUS and thus, recovery, stock images and development is for K5 plus. As long as you have stock rom, custom recovery or custom rom of your specific device which you own, you can follow this guide for any snapdragon device but booting your device into DIAG mode might need different commands.
TABLE OF CONTENT
Recover Your Device
EFS
Driver Guide
TWRP
Root
Backup device
Stock and Custom Roms
Future Issues
FAQ
Credits
(Don't know what is brick or ANDROID BASICS, click here to quickly go through them) HIGHLY RECOMMENDED
Code:
This guide is for those who understand the risk of their actions.
I have fully tested this guide and I found no issues, however,
I am not responsible for world wars, broken phones,
flying machines, dead SD cards, [B]girlfriend breakups[/B]
or any damage by your actions and only join in the forum
with [B]popcorn[/B] to enjoy myself at your suffering in case you
didn't follow the instructions and later blamed me for it.
IMPORTANT :
I suggest you start this guide by directly going to POST 5 BACKUP FULL DEVICE before you intend to do any experiments with your device. Make a FULL BACKUP WHICH IS HIGHLY RECOMMENDED OR YOU WOULD NOT BE ABLE TO USE OTAs LATER) Requires no root
DRIVERS ARE MUST HERE
You can simply download all the drivers from post three and install them all. In case you have troubles, you can refer HERE for more details.
WHAT YOU NEED
1. DRIVERS
2. USB DEBUGGING
3. ADB
4. TOOLS & STUFF (all in attachments)
5. Little Common Sense
6. Zero Skills
USB DEBUGGING ON
1.Activate the Developer options (Settings> About phone> Device Information> to tap 7 times in Build number)
2. Enable USB debugging (Settings> Developer> USB Debugging)
3. Enable OEM unlock (Settings> Developer> Unlock OEM)
4. Done
SETUP A WORKING ADB
Download platform tools from here in attachment
Extract them to any location.
Navigate to the location where you have extracted platform.zip
Hold crtl+shift on keyboard and then use your mouse to right click on an empty area of the folder.
Select open command prompt here
An cmd window will open
You are ready to go
Alternatively,
if that does not work for you. Simply download the platform.zip and extract it to C:/platform-tools.
Rename platform tools folder to adb
Go to cmd from start menu
Type in these commands until you see C:\> in cmd.
You will need to type twice most probably.
Code:
cd..
cd..
then type the following once you are at C:\>
Code:
cd adb
You will be in ADB folder, which will be now like C:\adb>
Now you have a working adb
RECOVER YOUR BRICKED DEVICE
There are actually 3 methods in theory to recover your phone. However,I also found that sometimes you can not flash your device using download mode and in this case, fastboot mode is the only route which means you will need to use TWRP or find a method to go into EDL from fastboot. So after you brick your device, your device can present in the following states.
No recovery or download mode but fastboot mode
Download mode
Recovery mode
Phone goes into download mode on its own
Possible Solutions
TWRP Method if you have a custom recovery or only fastboot(tested and works)
QFIL (tested and works) if you can boot into download mode
Lenovo Updater (untested)
ONLY FASTBOOT ACCESSIBLE NO DOWNLOAD/ RECOVERY.
Phone goes directly into download mode but QFIL unable to flash at all. Need to find a way to boot into EDL. Currently under working. Check this here Gold for those who need to boot to edl from fastboot
Fail with status when trying to flash using QFIL
Code:
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Two ways possible. Flashed TWRP and it worked by restoring previous backup. Works like a charm
Fastboot to edl needs some work. If that could be achieved. It will be brick proof.
TWRP METHOD
Pre Requisites
Fully working TWRP with root (preferable)
backup of your device (highly recommended) or download stock flashable roms HERE
STEPS
Boot into fastboot mode (bootloader) by switching off your phone and then press volume - and power
Flash TWRP recovery using fastboot commands HERE
Flash your previously made backup using RESTORE function in TWRP
To flash recovery partition, you will need to select flash IMG instead of preset ZIP when you navigate to INSTALL. You will find it on lower left side
DOWNLOAD STOCK RECOVERY FOR YOUR DEVICE HERE
You will need to unroot your device as well from supersu settings if you want to return to FULL STOCK
In case you only have fast boot mode and no recovery AND no download mode
Pre Requisites
You must have a fully working TWRP and possibly rooted
flashable zips of your stock roms or any previously made backup
STEPS
Simply place your update.zip in your sd card if you are using stock images
Or you can copy your previously made TWRP backup in sd card
Restore using TWRP if you have a backup
or flash via TWRP if you are flashing stock Images
Done
I highly suggest you wipe your device in TWRP including system
QFIL METHOD
Download stock image for your device. Make sure you choose the correct file for your device or you can hardbrick your device
Install QPST and QFIL software from attachments.
You may need to install Microsoft Tools which are provided in attachment for QPST to work
I assume that you have already proper drivers installed
Extract your device stock images in any given location of your choice but prefer it like D:/stock images etc
Open QFIL from start menu
Refer to image attachments 1,4,5,6,7 for the next steps
Browser Programmer Path and navigate to where you have extracted stock images.
Select the file with the given extention .(firehose)
Next load XML file and select the image.
It will ask for another file which you will be able to locate in the same folder\
Connect your device and see if the port is detected as QD LOADER
Select DOWNLOAD under LOAD XML
Sit back and enjoy. It should take 5-10 minutes
NOTES FOR QFIL
Bootloader Method does not seem to work. Even after changing drivers and replacing them.
Works with keys too. Hold Volume + and power after switching off device and select download!
Requires EDL method
Lenovo Serial driver required
Adb reboot edl
Then install drivers for Qualcomm port
Flash as instructions
Erase Misc after flash
Wait for device to turn on
STATUS : COMPLETE
Last updated 26.08.16
EFS
Pre Requisites
Installed drivers. ( See Next posts for detailed guide.)
Enable USB debugging. See first post
Working ADB (Download from attachment)
You will need to move to the location where you have extracted adb.zip
Hold crtl+shift + mouse right click and select open command prompt here and then you can give commands.
Root
[*] Recovery
TWRP BACKUP
I find this method most superior to all others.
Download recovery from this forum. All credits to the developer to make it possible
DOWNLOAD IT FROM HERE. TWRP WITH EFS BACKUP AND MORE
After downloading the recovery, using a working adb. Enter commands
Does not require root
Code:
adb devices
adb reboot bootloader
fastboot boot LenovoA6020_TWRP-3.0.2-r3_7M.img
You will boot into recovery with Russian translation. Change translation to your local language as shown in attachments TWRP 1 and TWRP 2.
Make EFS and all other backup and keep it safe.
I suggest you copy this to your PC before you plan to do something else with your device.
Done
Enable DIAG MODE on your device using adb.
Code:
adb shell
su
setprop sys.usb.config diag,adb
Once your phone is in DIAG mode, you can utilise these methods for QCN.
QCN is a file that holds all your data regarding your signals, bluetooth, wifi, imei etc
If you lose it without a back, it may be very hard to fix your phone.
For first two methods, you need to be in DIAG mode. For the last two, you can make a backup on your mobile. All four methods require root.
QCN EXTRACTION BY QFIL
Simply open QFIL on your PC.
You will see
QPST>Tools> QCN backup and Restore.
Select Backup in your desired location
Done
QCN backup by QPST other tools.
1.First time you are trying to make a backup of your QCN using this method, you will need to add DIAG port which you enabled via adb commands in QPST.
For that , go to QPST>BIN>QPSTConfig. You might need to go to show all ports before you are able to add it.
2.Next go to, QPST > Bin> QPSTServer.exe
3.A globe would appear in taskbar. Click on it and select software download from the tab
4.Select port of your diagnostic mode in backup tab of software download.
5. Once in software download, backup your current QCN
4. Done
Backup by blocks
This is a better method to make a backup. You can either use adb commands or simply download PARTITION BACKUP APP from play store. This will automatically backup your partitions.
PARTITION BACKUP TOOL PLAYSTORE LINK
XDA FORUM LINK FOR ANY QUERIES
These are ways to check your device for partitions manually. You can make backup of these yourself as well.
Detailed guide is given here
Code:
adb shell
cat /proc/partitions
[B]OR[/B]
adb shell
ls -al /dev/block/platform/dw_mmc/by-name
make sure you replace dw_mmc with your device partiton. (I have not checked it yet)
[B]OR[/B]
adb shell
cat /proc/partitions
adb remount
adb shell "su" "" "mount -o remount,rw /system"
adb push parted /system/bin/parted
adb shell
chmod 0755 /system/bin/parted
parted /dev/block/mmcblk0
print
Backup by tar.gz and Img
For this method you will need to download EFS BACKUP from playstore and then you can make a backup. I recommend make backup in all three formats.
EFS BACKUP PLAYSTORE
XDA FORUM LINK FOR THE APP
That's all you need for a good EFS Backup. Good Luck!
DRIVERS GUIDE
On Windows, it will automatically detect all drivers.
Make sure your device is attached to PC, before you install these drivers.
You may need to download drivers for ADB and QDLOADER which are all provided in Lenovo Usb driver.
So Installing these driver will be enough for you and you may need to manually select drivers for rest from lenovo folder
For ADB drivers use LENOVOUSB DRIVER 1.1.16 if your device is not detected by Windows.
For QHUB drivers use these in attachment named QDLOADER HS USB DRIVER.
Simply Install them and you are good to go.
INCASE YOUR DEVICE IS NOT DETECTED
All drivers are contained in these folder C:\Program Files (x86)\LenovoUsbDriver on your PC.
Go to My computer> Properties? Device Manager and see if you have any unknown devices like shown in attachment.
If you have, then I suggest you install manually.
Select unknown device and go in its properties.
Next go to drivers tab and select update drivers
Select Browse my computer for drivers
Let me pick from the list of devices
Select have disk
Move to folder C:\Program Files (x86)\LenovoUsbDriver
You will see that there are many folders.
ADB contains all ADB and Bootloader drivers
Use ADB folder if you are installing drivers for adb / fastboot/ bootloader.
Make sure you have usb debugging and device connected when you are installing these drivers. You have to be in normal mode for adb drivers
.
You can check if you have working adb by typing
Code:
adb devices
To download fastboot / bootloader drivers, simply first boot your device into fastboot.
Turn off device
hold power and volume down
Now try to install fastboot drivers
Serial Contains EDL drivers (Download mode drivers)
Select unknown device and go in its properties.
Next go to drivers tab and select update drivers
Select Browse my computer for drivers
Let me pick from the list of devices
Select have disk
Move to folder C:\Program Files (x86)\LenovoUsbDriver
You will see that there are many folders.
Use Serial if you are in download mode / EDL mode.
Working adb is required for this
You can go into EDL mode directly from adb commands by
Code:
adb reboot edl
OR
You can power off device
hold power and volume up
Select download mode and you are in EDL/ Download mode.
Now you can install drivers from above method
Make sure you select QDLOADER 9008 while installing EDL drivers.
How to enable QHUB drivers if no unknown/ undetected device is seen
Sometimes, your device is not detected in QFIL and you have all drivers installed and there is no unknown device in my computers> device manager.
For this, you will need to attach your device first.
Go to Device Manager by going into my computer properties
Look for ADB Interface drivers in device manager.
Update drivers for ADB interface and replace it with QDLoader HS USB driver.
If it asks for any permission, allow it.
In case your windows do not allow you to install these drivers , you need to turn off Digital Signature Verification in windows
run cmd as run as administrator
Type in these commands
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Restart
Then try again to reinstall drivers
To re-enable device verification on Windows
Code:
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Good luck
ROOT AND TWRP
HOW TO ACTIVATE USB DEBUGGING
1. Activate the Developer options (Settings> About phone> Device Information> to tap 7 times in Build number)
2. Enable USB debugging (Settings> Developer> USB Debugging)
3. Enable OEM unlock (Settings> Developer> Unlock OEM)
4. Connect the phone with the USB cable to the computer
5. Install the drivers that come on the CD cell partition.
TWRP:
Download TWRP from HERE or TWRP WITH EFS BACKUP AND MORE
Copy it to the folder where abd is installed.
On working adb, type in these commands
Code:
adb reboot bootloader
fastboot flash recovery LenovoA6020_TWRP-3.0.2-r3_7M.img
OR
fastboot flash recovery TWRP-k5-3.0.2-r2_shreps.img
This will permenantly flash twrp instead of Stock recovery.
If you just want to boot it once. check backup guide by using this command instead
Code:
fastboot boot <file name>
ROOT
Download the ZIP file SuperSU v2.76 and save it in the micro SD card.
Restart the phone in recovery mode:
Turn off the phone, then turn it on while pressing the volume up button. a screen appears with various options and choose "recovery".
You can even boot by adb commands using
Code:
adb reboot recovery
[*]
When opening the recovery, select Install and locate the file you downloaded just now.
Confirm execution flashing, restart the phone and voila!
ORIGINAL POST HERE
Editing the post with permission
BACKUP GUIDE
I HIGHLY RECOMMEND TO BACKUP YOUR DEVICE BEFORE YOU NEED TO EVEN ROOT YOUR DEVICE OR FLASH TWRP . IF YOU FAIL TO DO THIS, YOU WILL HAVE TROUBLE UPDATING YOUR PHONE VIA OTA ESPECIALLY IF YOU ROOT YOUR DEVICE
THIS IS MUST AS YOU CAN ALWAYS EASILY REVERT BACK TO YOUR ORIGINAL STOCK STATE IN CASE YOU NEED IT.
Download TWRP from HERE or Download recovery from this forum. All credits to the developer to make it possible DOWNLOAD IT FROM HERE. TWRP WITH EFS BACKUP AND MORE
YOU DO NOT NEED ROOT
I suggest you use the second TWRP as it supports more partitions than the first one.
Open working adb
TYPE IN
Code:
adb devices
adb reboot bootloader
fastboot boot LenovoA6020_TWRP-3.0.2-r3_7M.img
OR
fastboot boot TWRP-k5-3.0.2-r2_shreps.img
You will be booted into recovery.
Select Read only mode
Go to backup
Backup all partitions by selecting all of them
Swipe to confirm.
Make sure you have about 6GB for a full backup
You can skip user data if you do not want user apps backup
Nothing will be changed unless you enable system modification. So on first boot, simply do not enable system modification and go to backup and then backup all partitions. Keep these safe in case you need them.
Keep it in a safe place
HOW to restore back to your stock using TWRP. HERE
EFS Professional
doesnot work for me. Anyone can check by updating their busybox ? I couldnot on supersu 2.76 without updating busybox
CUSTOM ROMS
PACMAN
CYANOGENMOD 13
SOME HERE ON A RUSSIAN FORUM
STOCK ROMS
SOME HERE ON A RUSSIAN FORUM
Shreps said:
Stock Firmwares:
Firmware collection Thanks to @vache
Firmware collection, 2nd Mirror by @Shreps
TWRP Backups of Stock ROM:
A6020a40 - S027_160519_ROW
A6020l36 - S032_160401_LAS
Click to expand...
Click to collapse
Stock Rom guide to know which is your device by region
[*]American Models
Lenovo K5 Plus dual sim 6020l36 MSM8939v2 SD 616
Lenovo K5 Plus single sim 6020l37 MSM8939v2 SD 616
[*]European Models
Lenovo K5 Plus 6020a46 MSM8939v2 SD 616
[*]Asia Models
Lenovo K5 Plus 6020a46 MSM8939v2 SD 616
Lenovo Lemon 3 K32C36 MSM8939v2 SD 616
[*]Latin America ( Brazil, Chili )
Lenovo K5 dual sim A6020l36 MSM8939v2 SD 616
Some problems of the future. World war? Mobile mind control
OTA FAIL
ERROR 101 System doesnot allow change of carriers
download lenovo smart assistant
Install it and try to update it using this. If it does not update, find update package in lenovo tool folder
C:\Program Files (x86)\LenovoSmartAssistant\LenovoSmartAssistant\plugins\75fc9be6-29e6-495f-8c0a-93f9e1971133
Extract it and find system.zip and your country ota (both) in the sequence
Country.ota.zip (image taken from QPST)
Country2Default.ota.zip (image taken from QPST)
System.zip (image taken from FullOTA)
Does not flash with no error but system not updates and shows update again
Must flash system using QFIL
I used Indian firmware as I couldnot find for my region and thus I always had the error. Can not switch carriers.
I went to recovery and then 0>OTA> Flashed India OTA
Checked for system updates and this time it worked fully.
You can check which is supported by ####6020# in dialer
THIS IS GOLD. DO NOT MISS IT AT ALL
http://lenovo-forums.ru/forum/624-lenovo-k5-plus/
Credits
@Shreps for TWRP/ Custom roms and all his development efforts @samuro625 for TWRP and Rooting instructions @scritch007 cyanogenmod 13
@ more coming soon
@ anyone i left ? PM me and I will be happy to add your name!
@dongordo @axal Stock Firmware information
JUST WANT YOUR NAME FOR NO REASON ? PM and I will add it under this heading
Nice thread ?
Envoyé de mon Moto G (4)
Where on the Qualcomm site can one find the QIFL / QPST? Is it part of the Hexagon SDK?
Hnk1 said:
Custom roms
PACMAN
CYANOGENMOD 13
Orignal Sock Roms
Stock Rom guide to know which is your device by region
American Models
Lenovo K5 Plus dual sim 7020l36 MSM8939v2 SD 616
Lenovo K5 Plus single sim 7020l37 MSM8939v2 SD 616
European Models
Lenovo K5 Plus 7020a46 MSM8939v2 SD 616
Lenovo K5 7020a40 MSM8939 SD 415
Asia Models
Lenovo K5 7020a40 MSM8939 SD 415
Lenovo K5 Plus 7020a46 MSM8939v2 SD 616
Lenovo Lemon 3 K32C36 MSM8939v2 SD 616
Lenovo K5 note K52t38 Mediatek MT6755 Helio P10
Latin America ( Brazil, Chili )
Lenovo K5 dual sim A6020l36 MSM8939v2 SD 616
Click to expand...
Click to collapse
Wrong info. A7020 is K5 Note with MTK SoC.
Envoyé de mon Moto G (4)
Phylum said:
Where on the Qualcomm site can one find the QIFL / QPST? Is it part of the Hexagon SDK?
Click to expand...
Click to collapse
It is a took which was leaked and it is not officially available to you unless you manufacturer devices like samsung, lenovo etc
Download it from the first post. I have attached it in two posts!
Shreps said:
Wrong info. A7020 is K5 Note with MTK SoC.
Envoyé de mon Moto G (4)
Click to expand...
Click to collapse
Just to remember you guys, these methods DON'T WORK on A6020l36. Don't try this on your phone if it's this model, but if you did (like me), here is how to unbrick your phone.
https://www.youtube.com/watch?v=6pF2nT2SsHg
rafaellancas said:
Just to remember you guys, these methods DON'T WORK on A6020l36. Don't try this on your phone if it's this model, but if you did (like me), here is how to unbrick your phone.
https://www.youtube.com/watch?v=6pF2nT2SsHg
Click to expand...
Click to collapse
I think you are mistaken. I have QFIL method in my guide which is used by the user in the video.
Hnk1 said:
I think you are mistaken. I have QFIL method in my guide which is used by the user in the video.
Click to expand...
Click to collapse
Sorry man! Haven't seen it! I thought you were only talking about the TWRP method (which doesn't work on a6020l36).
rafaellancas said:
Sorry man! Haven't seen it! I thought you were only talking about the TWRP method (which doesn't work on a6020l36).
Click to expand...
Click to collapse
Really?
Sent from my Lenovo A6020a46 using XDA-Developers mobile app
Is this software almost the same as XIAOMI MIFLASH (it has EDL flashing mode) ???
Any hope for Vibe X3 etc? getting it dirt cheap and I need a new phone
rafaellancas said:
Sorry man! Haven't seen it! I thought you were only talking about the TWRP method (which doesn't work on a6020l36).
Click to expand...
Click to collapse
It should work flawlessly. I do not see why! Did you do as instructed ?
JoZ3 said:
Really?
Sent from my Lenovo A6020a46 using XDA-Developers mobile app
Click to expand...
Click to collapse
nguyenlucky said:
Is this software almost the same as XIAOMI MIFLASH (it has EDL flashing mode) ???
Click to expand...
Click to collapse
Well, I have not tested this with a XIOAMI device with QFIL. In theory it should work, but I have always preferred MIFLASH as it is designed specifically for Xiaomi devices. Most of snapdragon devices has an emergency download mode.
minigreen said:
Lenovo K5 Plus single sim 6020l37 MSM8939v2 SD 616
Click to expand...
Click to collapse
Do you want me to add it to the guide ? Which region is your device from ?
kkn_13 said:
Any hope for Vibe X3 etc? getting it dirt cheap and I need a new phone
Click to expand...
Click to collapse
What do you mean ? QFIL should work on all lenovo devices (snapdragon) provided you have proper stock images which are specific to your device. Google is your friend ? TWRP and development is not currently my aim for any device yet. As i did all my experiments using a K5 plus so I could write in length about it specifically.
Hnk1 said:
It should work flawlessly. I do not see why! Did you do as instructed ?
Well, I have not tested this with a XIOAMI device with QFIL. In theory it should work, but I have always preferred MIFLASH as it is designed specifically for Xiaomi devices. Most of snapdragon devices has an emergency download mode.
Do you want me to add it to the guide ? Which region is your device from ?
What do you mean ? QFIL should work on all lenovo devices (snapdragon) provided you have proper stock images which are specific to your device. Google is your friend ? TWRP and development is not currently my aim for any device yet. As i did all my experiments using a K5 plus so I could write in length about it specifically.
Click to expand...
Click to collapse
Thank you for your time man! Twrp does not work with my phone (I mean, I can install it, and root/flash some stuff, but it definatelly does not work for flashing any of the images uploaded here, including the backups or the pac/cyanogenmod roms, they all give the same compatibility erros as the roms were not made for this phone). I followed the instructions, wiped system/data/dalvik, tried to flash, compatibility erros. There is no way of backup too, since it crashes at the ending. I'm starting to think that my phone is not the a6020l36 (even though it says that on a label under my battery, on my phone's setup and also on the box), but some variant made for my country only. And I know that are brazillians that claim to make it work on their phones, but since there's no way to guarantee that we really have the same phone, I don't now what to do. The QFIL stock rom (that I got from another place too, the ones uploaded here don't work either (another reason to think that my a6020l36 is different from the ones people claim to work here)). Thank you again for your time.
So, my HTC U Ultra got stuck in bootloop just 3 days after warranty ended(tough luck level : 100).
My phone runs on everything stock and no root.
I press all the buttons when powered off and it goes into bootloader mode. It displays options to boot into recovery mode, boot into download mode and power down, all of which(except power down) gets device into bootloop again.
THE PRIORITY OF GOALS IS : DATA RECOVERY > PHONE BOOTING AND WORKING PROPERLY AGAIN
I did a little research and figured out some sort of procedure by putting bits and pieces together :
1. Download ADB/Fastboot toolkit || universal driver from koush github // I have HTC Sync manager installed as well || twrp custom recovery image for htc u ultra || new ruu from htc support for rom update.
2. Now I put my phone into fastboot mode (since it doesn't show up on adb devices), connect to pc using usb.
3. I type in cmd : "fastboot devices" --> My device shows up there --> Again in cmd : "fastboot boot recovery mytwrp.img" --> the twrp boots into my phone
I was able to put this many steps together and after the last step, i have an abstract idea of what to do :
Enable USB Debugging using twrp recovery --> Use ADB Pull Command to get my all my data from phone to pc --> Use adb wipe the old Firmware (Not sure which command) --> Use adb again to flash new RUU (again not sure how, I've got an .exe file as RUU || should I get it in zip or img or any other format ? || Please help on this too) --> Finally Boot and hopefully everything turns out smooth and secure.
CAN YOU EXPERTS HELP ME TO PUT TOGETHER REMAINING STEPS (AND MODIFY ERRORS, IF ANY, OF EXISTING STEPS ) OF THIS PROCEDURE...???
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
jwoegerbauer said:
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
Click to expand...
Click to collapse
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly ?
noobie12112 said:
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly in my case?
Click to expand...
Click to collapse
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
jwoegerbauer said:
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
Click to expand...
Click to collapse
@jwoegerbauer Thank you for the insight. In my case, the phone wasn't physically damaged, the bootloop occurred out of the blue one day. Now, what I presumed I should do, is to flash a custom recovery (twrp) using "fastboot boot recovery.img" command, and using twrp (Can I enable USB Debugging using twrp ?) to access files, backup and then flash a new RUU. But I found that I need to unlock bootloader, is there any way to use command "fastboot oem unlock" and not lose data, or any other method to unlock bootloader, where i don't lose data?
Thank you for your help.
Unlocking phone's bootloader always causes complete loss of data.
Forget the TWRP thing, it's not helpful at all in your case.
Try to flash phone's Stock ROM by means of ADB - what requires ADB got installed on Windows computer and USB debugging got ( manually !!! ) enabled on phone.
Hi,
Original ROM got corrupted of some sort and I can no longer access settings to enable developers options / ADB
Device is locked. Original recovery is non existing....
So I cant recover, enable ADB or fastboot.
What are my options please?
Ok, I got it going. Here were my steps:
PRE:
Download twrp-3.3.1-0-grouper.img from Download twrp-3.3.1-0-grouper.img
1. Boot into fastboot (volume down + power).
2. From terminal:
Code:
fastboot devices
to confirm it is recognised.
2. From terminal:
Code:
fastboot oem unlock
and confirm on Nexus.
3. From terminal:
Code:
fastboot boot twrp-3.3.1-0-grouper.img
.
4. How to fix unable to mount data internal storage 0mb in twrp permanently : | XDA Developers Forums (xda-developers.com) .
5. Deep format from TWRP (advanced - clear absolutely everything).
6. Job done.
Helpful links:
Semi-bricked??
Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover. Suggestions please?? Note 1: I'm pretty bad...
forum.xda-developers.com
Thanks