First, you’ll need ADB and fastboot, which can be downloaded here. To set up ADB, go to Settings/About Phone/Software Info and tap on build number until you get a toast notification saying “You are now a developer!” You will now have a new category in Settings called Developer Options. Go into developer options and enable USB debugging and OEM Unlock. You won't be able to turn it on if your phone is plugged in to your PC. Once you've turned it on, go to your PC, open Terminal or Command Prompt and type “adb devices”. Then plug in your phone and hit enter. You'll get a prompt on your phone to “Allow connections to this PC?”. Check Always allow and Allow. Now run “adb devices” again. Your device should now appear in Terminal.
If you have a SD card, download the latest zips from here and here onto your SD card. It'll save you a step later on.
Then you'll need to reboot to fastboot by holding down VOL- and plugging in USB while power is off. Alternatively, you can type “adb reboot bootloader” in Terminal or Command Prompt.
Next, you'll need to unlock the bootloader. Bootloader unlocking will factory reset your phone! Once you're in fastboot, run “fastboot oem unlock” in Terminal or Command Prompt. Now the bootloader is unlocked.
Now it's time to flash TWRP, a custom recovery for Android. It's going to be the way you install custom ROMs and add-ons. Download Official TWRP here. Once you've extracted the recovery.zip, run this command: “fastboot flash recovery path/to/recovery.img”. Once the file has flashed, disconnect the USB cable and battery. The next step is important! You're going to need to boot into TWRP for the first time. With the phone off, hold down VOL- and press power until the phone vibrates and the LG logo appears. While still holding down VOL-, release and immediately press and hold power. You should now be at a white screen that says “Reset all data and restore to factory settings?” Use the volume and power keys to select yes and yes again. If you've installed TWRP successfully, it won't actually factory reset your phone. Now you should see the TWRP screen. If you don't see the TWRP screen and instead see a floating ring that says “Erasing”, don't worry. Let if complete and try flashing TWRP in fastboot again.
In TWRP, you'll be greeted by a screen that says “Swipe to allow modifications?” Swipe it, then go to the Wipe tab. Go to Wipe, then Format Data, then type yes, then go to the Reboot tab and select Recovery to reboot into TWRP again. If you're prompted to install the TWRP app, don't bother.
Once you've rebooted into TWRP again, it's time to disable encryption and root the phone. Download the latest zips here and here. Skip downloading them if you already put them on your SD card earlier. On your PC, push the files to your phone using the command “adb push path/to/file.zip /sdcard/”. You can drag and drop the file into Terminal or Command Prompt to copy file path. Then go to the Install tab in TWRP and select the no-verity-opt-encrypt.zip, tap Add more zips, then add the root zip, then swipe to flash. Let the zips flash, then tap the Reboot System button when it's done. Your phone will take a little longer to boot and might reboot a couple times.
Once you're back in the OS, go through the setup wizard. Set up Magisk. If you stay on stock, you should install an app like Quick Reboot Pro from the Play Store to make it easier to reboot into recovery. Now reboot back into TWRP and go to the Backup tab. If you have a SD card, set it as the backup location. You can enable compression if you want. This will make a full system backup that you can restore from as long as you have TWRP. If the backup takes up too much space, you can put it in Google Drive or your PC later on.
You are now ready to install ROMs!
Thanks to @messi2050
My device will not start boot loader with command "adb reboot bootloader" or with the method of holding volume down and pugging it into the PC, it just restarts and boots like normal. i cannot even get to the stage to use the command "fastboot oem unlock"
I cant get it too boot into TWRP
? Has anyone else have had issues geting into bootloader mode on lg stylo 2 boost mobile.
meg540 said:
? Has anyone else have had issues geting into bootloader mode on lg stylo 2 boost mobile.
Click to expand...
Click to collapse
Please explain more in detail so you can be helped better In what ways? What are you doing to get into bootloader mode? I've never had any issues on my T-Mobile Stylo 2 plus. Are you trying to get into bootloader using buttons manually or through twrp or adb?
SM210 said:
Please explain more in detail so you can be helped better In what ways? What are you doing to get into bootloader mode? I've never had any issues on my T-Mobile Stylo 2 plus. Are you trying to get into bootloader using buttons manually or through twrp or adb?
Click to expand...
Click to collapse
Im trying too put my phone into bootloader mode to unlock bootloader but it keeps restarting phone and wont go into it. Also i have tryed on my computer command promt but phone into bootloader mode it. Restarts phone but not into bootloader mode. Also i have tryed power down and holding power button that doesn't work.
meg540 said:
Im trying too put my phone into bootloader mode to unlock bootloader but it keeps restarting phone and wont go into it. Also i have tryed on my computer command promt but phone into bootloader mode it. Restarts phone but not into bootloader mode. Also i have tryed power down and holding power button that doesn't work.
Click to expand...
Click to collapse
You hold volume DOWN and power then soon as screen comes on and you see LG you let go of the power button and then immediately press power again and you never let off volume DOWN. That doesn't work?
Edit
SM210 said:
You hold volume DOWN and power then soon as screen comes on and you see LG you let go of the power button and then immediately press power again and you never let off volume DOWN. That doesn't work?
Edit
Click to expand...
Click to collapse
Ill try that i think i wasnt doing it correctly i was holding down power button then i let go an i was holding down the down button. Ty for u help ill try it later today.
Hey there, I've got the LG K530F, is there any chance of unlocking it? I looked up the LG developer website and it's not listed in there, filling that form will just lead to a popup regarding that. I thought about downgrading it back to MM (Android 6.0) using the K350F10d_00_02221.kdz firmware package aiming to be able to run fastboot oem unlock, but I'm afraid of getting it bricked. Anyone tried it? I recall doing something like that to unlock the LG Optimus L9, but that one was way older and had much weaker security measurements.
Can't get into Bootloader
Hi i have a LGL82VL and when trying to use adb reboot bootloader it just restarts, And when using Vol Down and Power it just comes to the factory reset page (Hard Reset)
Any ideas on how to get to the bootloader? i checked with fastboot devices while on the hard reset page and got nothing. Any Ideas?
Related
I have 2 Xoom tablets, in Germany, and I took the SD Card from one of them to put it on a new phone, the Tablet kept working fine until last week that I forgot to plug it and the battery ran out. When I charged it and started it, it didn´t work again, I got the Encryption message, nothing happens when I click the Reset Tablet either, I tried putting the SD card from my other Xoom but still nothing. I enter the Recovery mode and did a Factory Reset and the tablet was OK.
Battery run out again yesterday and got the same problem once again, but now factory reset is not working, tablet stays stuck at the "M" logo after doing it, I have repeat the operation a zillion times and nothing, it stays on the M. Plus I can´t turn it off either.
The model is the MZ604 and Android Version 4.0.4
I connected the xoom to the computer after installing the drives but it won´t recognize it. I got to do the fastboot and flashed motorolas images but nothing. I can´t do the adb reboot bootloader command because ADB won´t work, because I don´t have USB Debbuging checked, but I can´t check it now because I can´t get to settings (
What can I do to recover the tablet?
Anyone, is driving me crazy, no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either
I tried RDS too and after the reboot stays the same in the M logo, nothing changes. What can I do?
No ideas? :crying:
I want to save the tablet if possible.
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
alecbond said:
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
Click to expand...
Click to collapse
Yes I mean stock images, and yes, it always stays on Xoom default, it never changes no matter which Recovery image I flash.
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
alecbond said:
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
Click to expand...
Click to collapse
Thanks for the info, sadly I have done almost all that, I can´t use adb commands because I never allowed the tablet to do USB Debbuging, since I wasn´t doing anything that needed that and never thought I would need it. I think I didn´t kept the tablet connected to the PC, so I will try again and let you know if it works.
Like I said before, I'm unsure whether it'll work as I'm not an expert.
However, you may find this helps:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
I believe ClockworkMod Recovery enables USB debugging anyway, through modifying default.prop
I'd recommend trying the above, and/or if that fails for any reason download Motorola USB Drivers here.
Thanks again but nothing works, I tried rebooting being connected to the PC and the same thing happens, the default recovery from the Xoom stays there, fastboot shows on the command Prompt and in the tablet that everything went ok and the new image was flashed but the rebooting kills it, and I can´t use any ADB commands because of the stupid USB Debugging, if something like this can happen, Motorola should have left it open from default or at least have a fail safe in case something like this could happen. RDS also flashes an image but when it rebbots the whole thing goes to hell, it stays on the damn logo with the same images. I think I can throw the tablet to the trash :crying:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
alecbond said:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
Click to expand...
Click to collapse
Thanks, but I have done everything, what is the good thing of a successful flash when the tablet returns to it´s previous state as soon as it reboots?
Plus I can´t use one of the most important things, adb, because of the usb debugging, I can´t get into the tablet to activated it, and even if there are recoveries which bypass this thing, I can´t flash them into the tablet, well I can, they just aren´t there after the reboot. And all this because the tablet run out of battery :crying:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Click to expand...
Click to collapse
alecbond said:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Click to expand...
Click to collapse
The problem lies with the recovery, I only have the default recovery from the xoom, it doesn´t matter how many times I flash it and everything seems to work correctly, when I restart the tablet I get the default recovery. I don´t understand why this happens, command prompt and the tablet in fastboot mode tell me the recovery has been flashed, but to use it I have to reboot and when I do I always find the same good for nothing recovery.
recovery
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
pots22 said:
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
Click to expand...
Click to collapse
Here is what happens, I flash new recovery, I restart the xoom with power and volume up, when the logo appears, after 3 seconds, I push volume down, recovery option shows, I press volume up and the default recovery is still there, not the new one I just flashed.
Is really no one out there that can help? :crying:
There's nowhere stated that, however I believe you already have unlocked your bootloader, didn't you? Because it's REALLY weird that it can't flash the recovery, I mean, you left the battery run out, then after charging you wasn't able to boot normally again.
I'll think a little, but give a check if your bootloader is really unlocked, the device should have installed the recovery, and as you didn't restart it entirely (let it go after the dual core logo), the recovery should be there...
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
I have done the fastboot oem unlock command, should I do it everytime? I can´t use adb, because like I said, I never check the USB Debugging, which I have done in my other tablet now, don´t want the same thing to happen twice.
is it dead?
hgokuh said:
is it dead?
Click to expand...
Click to collapse
I unfortunately believe that yes, however I'm still thinking about it! So don't give up! As soon as I have another answer I shall post something
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Hi I have the following problem: after I flash Cannibal open touch recovery I could not flash any .zip file so I decided that I go back to CWM touch so I restarted my phone. Phone booted into fastboot mode with the following message no boot or recovery IMG so I decided to flash recovery with fastboot. I opened the folder with fastboot command flash_recovery connect the phone to usb but the command line always showed waiting for device. I unplugged the phone and tried to press the volume keys but nothing happened as if it freezes. I pulled the battery and try it again but no response. I cant connect phone to odin because it has broken power button and after I insert the battery it always turn on itself. Please advise me what to do thank you.
Seems your drivers have gone corrupt. Try a different system and use Nexus Root Toolkit.
I tried this option but without success. Phone does not respond to anything. No volume up or volume down. It´s just stucked on bootloader.
This link says that if you get <waiting for device> , then fastboot is not configured properly. Check out the link over here.
You may also try this command "fastboot boot recovery-clockwork-6.0.4.3-crespo.img" to boot into recovery without installing it.
no hope
The reason you cannot navigate in fastboot/bootloader is that your powerswitch is probably stuck in the "on position"...does your device immediately power on when battery is inserted?
The way i solved this a few months ago was to completly remove my powerswitch from the board power my device on..use quickboot to enter fastboot menu and input commands...
Also completely removing your power button makes powering on your nexus alot more complicated.
what i did was go to download mode (holding vol+ and -) and pluging phone in..this takes you to download mode
then you need to get a copy of a boatloader file to flash via odin which will reset your phone and power it on...pm me if interested i can provide you with files necessary
Hey guys, so I have this dilemma on my hands. One of my friends has a Nexus 5 that has a power button issue. It seemed like a stuck power button, because even cleaning it did not solve the issue. So I removed the power button, and it finally turned on. However, it's now stuck in a Google logo bootloop.
The Objective:
To recover all data on the device. This is a must.
The Obstacles:
- No physical power button, but I can place a pair of tweezers on the terminals on the board to simulate a power button press.
- Bootloader is locked (I can unlock it, but that erases all data on the phone).
- Cannot enter proper stock recovery (I get a "no command" error when I do; I've tried all button combinations afterwards, including the ones from HERE, but to no avail).
- USB debugging was not enabled on the phone when booting normally, so even though the phone is recognized by my PC, I cannot do anything using ADB.
- Fastboot mode is the only successful mode I can reach on the phone.
The Final Question:
Does anyone know how I can successfully recover all the data on the phone using ADB or any other method, having the above obstacles?
Thanks in advance.
If you can reach fastboot without any problem, you can try to boot a custom recovery image using the following command : fastboot boot recovery yourcustomrecovery.img
(if you dont have a custom recovery, you need to flash one with : fastboot flash recovery yourcustomrecovery.img)
It will boot in recovery mode and, I hope, allow you to have an adb access and recover your data.
edit : since your bootloader is locked, i guess this won't work.
MrKhozam said:
Hey guys, so I have this dilemma on my hands. One of my friends has a Nexus 5 that has a power button issue. It seemed like a stuck power button, because even cleaning it did not solve the issue. So I removed the power button, and it finally turned on. However, it's now stuck in a Google logo bootloop.
The Objective:
To recover all data on the device. This is a must.
The Obstacles:
- No physical power button, but I can place a pair of tweezers on the terminals on the board to simulate a power button press.
- Bootloader is locked (I can unlock it, but that erases all data on the phone).
- Cannot enter proper stock recovery (I get a "no command" error when I do; I've tried all button combinations afterwards, including the ones from HERE, but to no avail).
- USB debugging was not enabled on the phone when booting normally, so even though the phone is recognized by my PC, I cannot do anything using ADB.
- Fastboot mode is the only successful mode I can reach on the phone.
The Final Question:
Does anyone know how I can successfully recover all the data on the phone using ADB or any other method, having the above obstacles?
Thanks in advance.
Click to expand...
Click to collapse
I bit of a trick. Try 'fastboot flash boot recovery.img' but instead of kernel flash twrp. After flash do a 'fastboot reboot'. It will boot recovery. Via twrp the pc will recognize phone as a media storage. You will not erase any data
icrunchbanger said:
I bit of a trick. Try 'fastboot flash boot recovery.img' but instead of kernel flash twrp. After flash do a 'fastboot reboot'. It will boot recovery. Via twrp the pc will recognize phone as a media storage. You will not erase any data
Click to expand...
Click to collapse
Thanks for the response, but the bootloader has to be unlocked for that to work, and while I can do that, it will wipe the data I need.
Hi,
I was trying to flash TWRP, but now I am stuck with flashing TWRP logo after rebooting or powering the phone on.
I am unable to get to the fastboot.
STEPS I did before brick:
1. unlocked OEM via official way
2. flashed TWRP
3. after that my phone was reset however most of the apps was missing, I was trying to do factory reset once again but it failed with the message "Data partition was heavily damaged"
4. I re-locked EOM
5. brick as mentioned above
Please help, I have the phone only two weeks and I have no idea how to fix this without fastboot.
Thank you.
Meiton said:
Hi,
I was trying to flash TWRP, but now I am stuck with flashing TWRP logo after rebooting or powering the phone on.
I am unable to get to the fastboot.
STEPS I did before brick:
1. unlocked OEM via official way
2. flashed TWRP
3. after that my phone was reset however most of the apps was missing, I was trying to do factory reset once again but it failed with the message "Data partition was heavily damaged"
4. I re-locked EOM
5. brick as mentioned above
Please help, I have the phone only two weeks and I have no idea how to fix this without fastboot.
Thank you.
Click to expand...
Click to collapse
Sounds like you flashed the 3030 version of TWRP. Download the 3020 version and put it in your fastboot folder. Plug in the USB to PC
Hold power and volume up untill the phone reboots. While it's still off immediately change to power and volume down and hold till it goes into fastboot (bootloader)
Now fastboot flash recovery TWRP.img
With the 3020 version.
Unplug the USB and hold power and volume up until it says the phone is booting.. let go and TWRP will load.
Go to Wipe / format data / type yes
Reboot to system and your all set
Sent from my Nexus 6P using Tapatalk
clsA said:
Sounds like you flashed the 3030 version of TWRP. Download the 3020 version and put it in your fastboot folder. Plug in the USB to PC
Hold power and volume up untill the phone reboots. While it's still off immediately change to power and volume down and hold till it goes into fastboot (bootloader)
Now fastboot flash recovery TWRP.img
With the 3020 version.
Unplug the USB and hold power and volume up until it says the phone is booting.. let go and TWRP will load.
Go to Wipe / format data / type yes
Reboot to system and your all set
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So I've tried that but the phone is still booting to recovery (flashing TWRP logo) no matter what.
Basically the phone is always on now because if hold the power button (or any other combination) for a few second it will just reboot back.
I have an access only to ADB, but I am not able to boot to bootloader at all, it seems the bootloader is damaged somehow.
Also that warning about unlocked OEM doesn't have that text saying "hold volume up to boot to recovery" etc. like before brick.
Hi there,
Try using the Huawei Multi Tool with the Unbrick option : https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
Speaking from experience, this little fellow helped me recover my phone when I bricked it ON DAY ONE after failed root attempt... (Derp)
Let me know if it helped you
(Leave a thanks if it did )
EDIT : This tool is also useful if you want to get lazy whilst rooting. I use it constantly when flashing diffrent bits and pieces
Clearly follow My steps To unbrick and get normal device ::
Step 1 ::
Download the full firmware of your device.
Step 2 :
make sure that your bootloader is in unlocking state
Follow the video blindly ::: https://youtu.be/OMKDnBqbi3U?list=PL...eT9J26lkefvVkK
don't panic of mobile.
Step 3 :: done ..enjoy u did it
--------------------------------------------------------------------------
If you bricked on nougat then follow the below steps
step one :::
download the downgrade package to mm .
then extract the zip and open the update.app using HuaweiUpdateextrator in that select recovery and extract
1.now, boot your device into fastboot and flash the recovery (Optional)(try this if it said incompatible version on recovery)
2. on your sd card and make a folder "dload" . and copy the update.app which we have extracted earlier
3.the switch off the device and press all three buttons you will be reboot into recovery and done . you device will be okey
Meiton said:
So I've tried that but the phone is still booting to recovery (flashing TWRP logo) no matter what.
Basically the phone is always on now because if hold the power button (or any other combination) for a few second it will just reboot back.
I have an access only to ADB, but I am not able to boot to bootloader at all, it seems the bootloader is damaged somehow.
Also that warning about unlocked OEM doesn't have that text saying "hold volume up to boot to recovery" etc. like before brick.
Click to expand...
Click to collapse
Booting to the bootloader is just a timing issue
Phone must be hooked to PC with USB
And volume up and power till it goes black
Then immediately volume down and power and Hold untill the bootloader loads
Keep trying until you get it
Sent from my Nexus 6P using Tapatalk
clsA said:
Booting to the bootloader is just a timing issue
Phone must be hooked to PC with USB
And volume up and power till it goes black
Then immediately volume down and power and Hold untill the bootloader loads
Keep trying until you get it
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I appreciate your help but I've tried it multiple times always with the same result.
I also can use "adb reboot bootloader", but it will reboot again to stuck recovery.
DJ Daemonix said:
Hi there,
Try using the Huawei Multi Tool with the Unbrick option : https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
Speaking from experience, this little fellow helped me recover my phone when I bricked it ON DAY ONE after failed root attempt... (Derp)
Let me know if it helped you
(Leave a thanks if it did )
EDIT : This tool is also useful if you want to get lazy whilst rooting. I use it constantly when flashing diffrent bits and pieces
Click to expand...
Click to collapse
I've tried that, but I am still stuck as that tool is using fastboot as every other tool to flash .img files.
Thank you for the tip though.
Plug phone into computer with USB, then hold down power + volume down until it eventually boots into bootloader. I had the same scenario as you and that's how I got into the bootloader. You can flash either a good TWRP or the stock recovery, either one will work.
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
No need double reboot
Os_Herdz said:
No need double reboot
Click to expand...
Click to collapse
It is not necessary, but a preventative measure. I've had instances where I hadn't rebooted twice and the phone booted into erase mode. This is a guide for people who want to make sure they won't lose data.
Another tip:
If you're with stock everything and don't want to loose data, do not boot into recovery mode (power + vol+) as it sometimes try to wipe data without any confirmation. Did happened here once, back in March 2019, but thankfully my pictures and most data are stored in MicroSD card.
RFD80M-75679 said:
Another tip:
If you're with stock everything and don't want to loose data, do not boot into recovery mode (power + vol+) as it sometimes try to wipe data without any confirmation. Did happened here once, back in March 2019, but thankfully my pictures and most data are stored in MicroSD card.
Click to expand...
Click to collapse
Can confirm, if your bootloader is unlocked and you don't have TWRP installed, booting into recovery mode will wipe the device.
marstonpear said:
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
Click to expand...
Click to collapse
When I type fastboot oem unlock and press enter, a screen shows on the device to select unlock or do not unlock. Then what?
softgadget said:
When I type fastboot oem unlock and press enter, a screen shows on the device to select unlock or do not unlock. Then what?
Click to expand...
Click to collapse
It shouldn't ask you to unlock phone or not in fastboot mode, as what I did unlocked mine for months ago. It should return you to fastboot mode in a flash (a fraction of seconds) and manually restart your phone by holding up power button until you'll see unlocked warning and AndroidOne logo.
If it is, try to select "unlock", but your data may wipe afterwards.
RFD80M-75679 said:
It shouldn't ask you to unlock phone or not in fastboot mode, as what I did unlocked mine for months ago. It should return you to fastboot mode in a flash (a fraction of seconds) and manually restart your phone by holding up power button until you'll see unlocked warning and AndroidOne logo.
If it is, try to select "unlock", but your data may wipe afterwards.
Click to expand...
Click to collapse
I am running Android 10 latest update on my Mi A2 and my phone shows a screen to select Unlock or Not to Unlock options. It is in fastboot mode. What is the problem?
softgadget said:
I am running Android 10 latest update on my Mi A2 and my phone shows a screen to select Unlock or Not to Unlock options. It is in fastboot mode. What is the problem?
Click to expand...
Click to collapse
You have another device. This is for Mi A2 Lite, not Mi A2. And on top of that, it works for Android Pie. I don't know for stock Android 10 since we (Mi A2 Lite users) don't have it yet (as of my writing).
RFD80M-75679 said:
You have another device. This is for Mi A2 Lite, not Mi A2. And on top of that, it works for Android Pie. I don't know for stock Android 10 since we (Mi A2 Lite users) don't have it yet (as of my writing).
Click to expand...
Click to collapse
Oh. OK then.thank you
I downgrade to oreo and now when power om phone show message that is bootloader unlocked, so can lock again bootloader to remove that message without lost data or must live with that? If can do that, how? I forgot to say after flash oreo bootloader was locked, but i must unlock again to fix sim cards.
popadic022 said:
I downgrade to oreo and now when power om phone show message that is bootloader unlocked, so can lock again bootloader to remove that message without lost data or must live with that? If can do that, how? I forgot to say after flash oreo bootloader was locked, but i must unlock again to fix sim cards.
Click to expand...
Click to collapse
You can unlock with the same method. But I believe you will flash a zip from TWRP to fix SIM cards and that will break your phone if you lock the bootloader. So after fixing the SIM cards, you need to leave the phone unlocked, otherwise phone will be bricked. If you want to get rid of the ugly splash screen, you can flash a custom splash you can find in the forum.
marstonpear said:
Can confirm, if your bootloader is unlocked and you don't have TWRP installed, booting into recovery mode will wipe the device.
Click to expand...
Click to collapse
So after unlocked the devices, it's recommended to install TWRP to avoid this right ?
gusbalaa said:
So after unlocked the devices, it's recommended to install TWRP to avoid this right ?
Click to expand...
Click to collapse
You can leave it as is, but don't ever boot into recovery if you value your data from Internal Storage or if haven't backed up data to MicroSD.
RFD80M-75679 said:
You can leave it as is, but don't ever boot into recovery if you value your data from Internal Storage or if haven't backed up data to MicroSD.
Click to expand...
Click to collapse
I think I'm gonna install TWRP for safety, my data is already on MicroSD.
EDIT : Is possible to install TWRP & Root without losing data / need to flash Decrypt ?
gusbalaa said:
I think I'm gonna install TWRP for safety, my data is already on MicroSD.
EDIT : Is possible to install TWRP & Root without losing data / need to flash Decrypt ?
Click to expand...
Click to collapse
You don't need to decrypt. You can install TWRP and flash Magisk through TWRP.
marstonpear said:
You don't need to decrypt. You can install TWRP and flash Magisk through TWRP.
Click to expand...
Click to collapse
Thanks, already done it.
Flashed TWRP & Magisk without losing any data.
marstonpear said:
Hi,
Click to expand...
Click to collapse
will this metode also work on mi10
-fluffy- said:
will this metode also work on mi10
Click to expand...
Click to collapse
I'm not sure but probably not. Because Mi 10 is a MIUI device and this is an Android One. Still you gotta try to make sure, but the risk is all yours. Cheers.
marstonpear said:
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
Click to expand...
Click to collapse
Wowwww! Thank you very much, time ago I've unlocked the bootloader without losing any data
That's a very good solution