Related
Hey guys,
I've been messing around with my brand new N7 yesterday and somehow screwed up badly.
Right now, all I have is a working TWRP recovery and a locked bootloader.
When I try to unlock the bootloader, the device just freezes so flashing stock images is not an option.
Can I do something via TWRP to get my N7 working again?
I already opened a RMA with amazon.
Second question: If I am out of options, is there a way to remove TWRP?
Really need your help right now,
thanks in advance,
DrTek
which method did u try to unlock the bootloader?
MoonBlade said:
which method did u try to unlock the bootloader?
Click to expand...
Click to collapse
I tried with "fastboot oem unlock"
The moment I choose yes and push the power button for confirmation - the device freezes.
drtek said:
I tried with "fastboot oem unlock"
The moment I choose yes and push the power button for confirmation - the device freezes.
Click to expand...
Click to collapse
is it freezing for more than 2 mins ? it should not freeze like that unless it is already unlocked ??
It might already be unlocked. Do you have an unlocked symbol when you turn it on? If you do, run the Dead Nexus batch file from here. I was unable to do anything from TWRP or CWM. Just a bunch of errors when it tried to do anything with the drive. Flashing, copying, formatting, etc. This saved my Nexus!
http://forum.xda-developers.com/showthread.php?t=2381582
Do you have access to the internal SD? From a computer or anywhere? Because if you do you can just flash a ROM from twrp
sent from my nex7
The wife got a refurbished 5x from the Best Buy Sales this week, it was already on N. We went and opted out of the preview and it downloaded and installed 6.01. Since then it has gone into boot loop where it shows the Google Logo, then beginning on the animation, then starts over.
I am able to get into recovery mode, I tried a reset and that didn't work. I can get into adb, and the device is seen, but when I try to sideload, I get a E:footer error.
I also tried Nexus Root Kit, but its wants me to turn on developer mode for USB debugging, and the phone cant get me there.
Frustrated enough to call Best Buy, they sent me to the store Geek Squad. He said they could only exchange, and since they are out of phones, I am SOL for getting a working unit. Money back only.
Edit: When I try to run "fastboot flashing unlock" I get "FAILED (remote: oem unlock is not allowed)"
Pattond said:
The wife got a refurbished 5x from the Best Buy Sales this week, it was already on N. We went and opted out of the preview and it downloaded and installed 6.01. Since then it has gone into boot loop where it shows the Google Logo, then beginning on the animation, then starts over.
I am able to get into recovery mode, I tried a reset and that didn't work. I can get into adb, and the device is seen, but when I try to sideload, I get a E:footer error.
I also tried Nexus Root Kit, but its wants me to turn on developer mode for USB debugging, and the phone cant get me there.
Frustrated enough to call Best Buy, they sent me to the store Geek Squad. He said they could only exchange, and since they are out of phones, I am SOL for getting a working unit. Money back only.
Click to expand...
Click to collapse
I would be irritated too. Lets figure out where you are.
Lets boot into fastboot mode and see your bootloader is locked... Power off the phone then hold the power button and volume down button simultaneously. A few seconds later you will boot into fastboot mode. The bottom half of the screen should be information about your device. The last line should say DEVICE STATE = unlocked/locked. If it says locked you are in good shape. Just flash the latest factory images. If it is still locked, you need to figure out what path you want to get it running again.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options. Reboot to fastboot mode as described above. Connect the phone to your computer. Then open a terminal (or command prompt) in the directory where your fastboot file is located and issue the following command:
Code:
fastboot oem unlock
If by some miracle it allows you to unlock, do it. You are in very good shape if you can. If you get to that point someone will help you fastboot the factory images. If not continue to path 2 below.
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
PiousInquisitor said:
I would be irritated too. Lets figure out where you are.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options.
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Returned with
FAILED (remote: oem unlock is not allowed)
PiousInquisitor said:
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Click to expand...
Click to collapse
SHA256 Checksums on bullhead-ota-mtc19t-4ea6522b.zip match. When sideloading, at about 50% the phone says
"Warning: no file contextsThis package is for "bullhead" devices: this is a " ".
"E:Error in /sideload/package.zip
(Status 7)
Installation Aborted"
PiousInquisitor said:
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
I'm going to try that now.
You can use the Nexus root toolkit, manually put the phone in bootloader and click OK to get past the "enable debugging window". It's asking you to do that so it can reboot the phone itself into bootloader.
PiousInquisitor said:
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
The LG reset software got me going, but after it loaded, I did get an internal error message. I hit OK, it seem to be running fine. Will reload apps and see what happens.
Pattond said:
The LG reset software got me going, but after it loaded, I did get an internal error message. I hit OK, it seem to be running fine. Will reload apps and see what happens.
Click to expand...
Click to collapse
If I were you I'd unlock the bootloader, flash the latest factory images then relock the bootloader. Check the build number and date. I'm sure it's pretty old.
Sent from my SM-G930V using Tapatalk
PiousInquisitor said:
If I were you I'd unlock the bootloader, flash the latest factory images then relock the bootloader. Check the build number and date. I'm sure it's pretty old.
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
it is an old copy, 6.0. I started the update process, and got an update failed notice. I used the LG software again and it is getting it running, but I am still getting the internal error message (see attached)
.
Pattond said:
it is an old copy, 6.0. I started the update process, and got an update failed notice. I used the LG software again and it is getting it running, but I am still getting the internal error message (see attached)
.
Click to expand...
Click to collapse
The vendor image is out of date. When you boot up. Enable developer options. In developer options there is a toggle to allow OEM unlocking. Tick it. Then use fastboot to unlock the bootloader. Download and flash the latest images. You won't have any more problems.
Sent from my SM-G930V using Tapatalk
PiousInquisitor said:
The vendor image is out of date. When you boot up. Enable developer options. In developer options there is a toggle to allow OEM unlocking. Tick it. Then use fastboot to unlock the bootloader. Download and flash the latest images. You won't have any more problems.
Click to expand...
Click to collapse
All good, got it to 6.01, no internal error message on boot. I did the OEM unlock as you suggested, then let WugFresh's Nexus Root Toolkit take it from there. Thanks!
Damn I'm in the same situation but it will actually boot all the way to the lock screen and as soon as I put in my password it reboots. It actually will reboot regardless after sitting on the lock screen for about 10 seconds.
I really really don't want to lose everything on the phone. I have the factory image and can unzip it and manually install parts. I just don't want to wipe the data. Bootloader is still unlocked and I had oem unlock option enabled prior.
PiousInquisitor said:
I would be irritated too. Lets figure out where you are.
Lets boot into fastboot mode and see your bootloader is locked... Power off the phone then hold the power button and volume down button simultaneously. A few seconds later you will boot into fastboot mode. The bottom half of the screen should be information about your device. The last line should say DEVICE STATE = unlocked/locked. If it says locked you are in good shape. Just flash the latest factory images. If it is still locked, you need to figure out what path you want to get it running again.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options. Reboot to fastboot mode as described above. Connect the phone to your computer. Then open a terminal (or command prompt) in the directory where your fastboot file is located and issue the following command:
Code:
fastboot oem unlock
If by some miracle it allows you to unlock, do it. You are in very good shape if you can. If you get to that point someone will help you fastboot the factory images. If not continue to path 2 below.
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
Ok, i feel really stupid asking this.....WHAT ARE YOU TALKING ABOUT WHEN YOU SAY "FLASH" THE LATEST FACTORY IMAGE????
Ive been stuck in a boot loop for 3 days now. it only gets as far as the "google" logo before rebooting agin and again and again and again....:crying::crying::crying::crying:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.
Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?
Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/
After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...
Are you going to be able to RMA it? Is it still under warranty?
Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse
Good news! I got an RMA!!
Thanks for your help everyone!
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
try sideloading the full OTA.
https://developers.google.com/android/ota
robertoancini51 said:
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
Click to expand...
Click to collapse
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
v12xke said:
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
Click to expand...
Click to collapse
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Badger50 said:
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
Click to expand...
Click to collapse
ok, thank you
v12xke said:
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Click to expand...
Click to collapse
I just cannot believe that the phone is unusable
robertoancini51 said:
I just cannot believe that the phone is unusable
Click to expand...
Click to collapse
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
sliding_billy said:
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
Click to expand...
Click to collapse
Yes
robertoancini51 said:
Yes
Click to expand...
Click to collapse
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
sliding_billy said:
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
Click to expand...
Click to collapse
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
robertoancini51 said:
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
Click to expand...
Click to collapse
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
sliding_billy said:
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
Click to expand...
Click to collapse
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
i have the same problem
robertoancini51 said:
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
Click to expand...
Click to collapse
who did you write to? can you share please? also if you manage to solve the problem, please share the solution.
many thanks,
Cant you take the back of and use EDL Mode? its qualcomm so its available.? wheres all the master techys in the pixel thread?You can push the entire factory image whether its locked or unlocked with EDL.
---------- Post added at 04:56 PM ---------- Previous post was at 04:50 PM ----------
https://www.leakite.com/revised-how-to-unbrick-qualcomm-android/
Remember to change any images to googles.
Hi lads
Wonder if someone could help. The brothers phone is in trouble. He knows nothing about rooting etc so it's official but just keeps rebooting. His data stopped working and he rebooted it for the first time in months and it just won't boot. Pic attached from recovery. Any advice would be great. He doesn't care about the phone but has some family photos and stuff on it.
Thanks all
you can try to flash twrp twrp-3.0.1-0-hima via fastboot with this command if the bootloader is unlocked
fastboot flash recovery twrp-3.0.1-0-hima.img
then plug a usb cord into the phone and computer. the computer should see the phone as a usb drive and pull the photos or whatever that way
Hey thanks for the reply. I presume the attached picture means the bootloader is locked? Are there any other options would anyone know? Thanks
corkie1 said:
Hey thanks for the reply. I presume the attached picture means the bootloader is locked? Are there any other options would anyone know? Thanks
Click to expand...
Click to collapse
Yes the purple text is your bootloader status, mine says "*** UNLOCKED ***". So you won't be able to RAM boot TWRP OR flash.
Ah right thanks for that. So basically factory reset is the only option I presume so?
Go for it!