Related
Hi
I was side loading the new 5.1 to both my N5 and N6. N5 was ALL GOOD. N6 however is not. After waiting for a rediculous time for it to reboot when it was stuck on the white Google Image, I disconnected the USB cable. Now it won't boot past the Google screen at all.
I can see it as a fastboot device and can boot into bootloader. There appears to be no recovery. When I try to re flash or side load, I get the warning along the lines of 'unlock before flash'.
So........can anyone assist please?
Thanks in advance of responses.
Cheers
Thommo
Look here..
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
That might help, otherwise since you can get into BL mode can you try flashing stock recovery from the image you originally had? I guess I don't know if that works or not or if that is what you were trying to reflash..
fastboot command to flash recovery is
fastboot flash recovery recovery.img <--replace recovery.img with the name of the recovery you are trying to flash. It's most likely recovery.img if you are taking it from a stock image.
Good luck.
Ha66is said:
Hi
I was side loading the new 5.1 to both my N5 and N6. N5 was ALL GOOD. N6 however is not. After waiting for a rediculous time for it to reboot when it was stuck on the white Google Image, I disconnected the USB cable. Now it won't boot past the Google screen at all.
I can see it as a fastboot device and can boot into bootloader. There appears to be no recovery. When I try to re flash or side load, I get the warning along the lines of 'unlock before flash'.
So........can anyone assist please?
Thanks in advance of responses.
Cheers
Thommo
Click to expand...
Click to collapse
did you solve? how you solved?
i have a similary problem with my nexus 9.. locked bootloader and can't do anythings.. please help me
we need help
paviz96 said:
did you solve? how you solved?
i have a similary problem with my nexus 9.. locked bootloader and can't do anythings.. please help me
Click to expand...
Click to collapse
i have the same prob bro i am waiting for a fix i still have hope
So the lesson learned is: Always unlocking the bootloader once you have the phone/tablet should be the first thing to do so you can fix issues !
I also need someone to find a way to unlock the bootloader ! btw try booting into recovery (it will say no command) and then hold the volume up and power for 10 seconds and then let go, then select adb sideload ...let it time out...then try to clear data and cache. I tried to clear that when i had a bootloop but wouldnt work, i got it to work by selecting adb sideload and then letting it time out(takes a while to timeout)..must mount the partitions...
jordy787 said:
I also need someone to find a way to unlock the bootloader ! btw try booting into recovery (it will say no command) and then hold the volume up and power for 10 seconds and then let go, then select adb sideload ...let it time out...then try to clear data and cache. I tried to clear that when i had a bootloop but wouldnt work, i got it to work by selecting adb sideload and then letting it time out(takes a while to timeout)..must mount the partitions...
Click to expand...
Click to collapse
If you do not have TWRP recovery, there's nothing you can do. RMA.
Evolution_Tech said:
If you do not have TWRP recovery, there's nothing you can do. RMA.
Click to expand...
Click to collapse
think i can rma with a cracked glass but still works?
jordy787 said:
think i can rma with a cracked glass but still works?
Click to expand...
Click to collapse
Doubt it. There are some GooglePlay versions that have been RMA'd as it was a promo. Still gonna go back to original Account for the RMA.
stupid question . if this is Motorola you cant use RSD this with the correct FXZ. or they no longer use this since its a nexus.
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
lostnthought said:
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
Click to expand...
Click to collapse
Please provide more info. Stock or custom recovery?
Evolution_Freak said:
Please provide more info. Stock or custom recovery?
Click to expand...
Click to collapse
Custom Recovery.. TWRP v2.8.2
lostnthought said:
Custom Recovery.. TWRP v2.8.2
Click to expand...
Click to collapse
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
DebianDog said:
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
This may sound silly but I'm not 100% sure. A system notification had been on my screen for over two weeks saying that I had a system update to 5.1 and I finally decided to download and install said update and then it sent me to recovery mode. I don't know why I did but I hit fix permissions.. Just fiddling trying to figure everything out and this is where we are.
Evolution_Freak said:
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
Click to expand...
Click to collapse
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
I'm not asking you to boot to recovery. Boot to bootloader.
lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
move a rom via a computer to your phone. either connect the recovery to your computer and move it, or connect to a computer and adb push it to your phone.
Sorry, I guess I misread your post. I thought you said can't get to recovery. From TWRP you should be able to enable MTP transfer. Then your PC should see it and you can transfer files as @simms22 suggested.
lostnthought said:
"No OS found."
Click to expand...
Click to collapse
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
vormund said:
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
Click to expand...
Click to collapse
you dont need adb to move anything to your phone when using twrp. just connect to twrp using the mtp option.
Hi Guys.
So recently I posted about resetting nexus 6 to factory default so I can send it off for a warranty repair.
In the mean time. I've dropped it about 20 times.
The glass is cracked and the screen is broken too.
I want to back everything up before sending the device off for a repair but there's a problem.
The device has a pin at boot and I can't get in because the digitizer is dead.
Whenever I try to use adb it just says "offline".
Is there any way I can get around this and make a backup??
please help thanks
can i dirty flash something from bootloader? i don't care if it breaks all the apps because I just want to boot the device and pull /sdcard/ via adb. Any help pleeeeeeeeaaaaase
joncy92 said:
can i dirty flash something from bootloader? i don't care if it breaks all the apps because I just want to boot the device and pull /sdcard/ via adb. Any help pleeeeeeeeaaaaase
Click to expand...
Click to collapse
first off, question and need for help gets posted in the q&a/help section, ill ask a mod to move your thread there. and secondly, you can flash the factory img via fastboot, via your bootloader
Use an otg cable and mouse to punch in the pin? Or will that not work that early in the boot process?
btw, you can boot into the recovery and use adb.
thanks for replies. I can't get into recovery it asks for a password. When I try to access the device through ADB it says "device offline"
If I flash factory through bootloader will it wipe all the pictures n stuff?
joncy92 said:
thanks for replies. I can't get into recovery it asks for a password. When I try to access the device through ADB it says "device offline"
If I flash factory through bootloader will it wipe all the pictures n stuff?
Click to expand...
Click to collapse
if you unlock the bootloader, it will. if its already unlocked, you can flash a certain way, to keep your data.
simms22 said:
if you unlock the bootloader, it will. if its already unlocked, you can flash a certain way, to keep your data.
Click to expand...
Click to collapse
hi thanks.
Bootloader is unlocked and device running chroma rom and twrp recovery. i think forced encryption is on but I didn't decrypt the device.
Please advise how to flash and keep data. If I reflash will the pin disappear so i can backup??
joncy92 said:
hi thanks.
Bootloader is unlocked and device running chroma rom and twrp recovery. i think forced encryption is on but I didn't decrypt the device.
Please advise how to flash and keep data. If I reflash will the pin disappear so i can backup??
Click to expand...
Click to collapse
itll probably ask you for your code again. and if you could get into recovery, you could make a nandroid backup of your rom, then restore it onto another n6 later. anyways, i *think* you just avoid flashing the userdata.img, but i could be wrong. see if you can google it.
simms22 said:
itll probably ask you for your code again. and if you could get into recovery, you could make a nandroid backup of your rom, then restore it onto another n6 later. anyways, i *think* you just avoid flashing the userdata.img, but i could be wrong. see if you can google it.
Click to expand...
Click to collapse
how will I get into recovery after flashing? Won't it still be asking for a password?
joncy92 said:
how will I get into recovery after flashing? Won't it still be asking for a password?
Click to expand...
Click to collapse
you will have a stock recovery after flashing the factory.img, youd have to flash twrp again, via fastboot via your bootloader. if you will still have that issue, i dont know.
joncy92 said:
Hi Guys.
So recently I posted about resetting nexus 6 to factory default so I can send it off for a warranty repair.
In the mean time. I've dropped it about 20 times.
The glass is cracked and the screen is broken too.
Click to expand...
Click to collapse
How could this be a warranty repair?
Hi,
Well as I said I'd dropped in after logging a warranty repair with Motorola. The problem was with the volume rocker getting stuck when I pressed the up or down buttons.
I was just giving some background
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
claytonjn said:
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you lock the bootloader just to be clear?
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
gee2012 said:
Did you lock the bootloader just to be clear?
Click to expand...
Click to collapse
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
simms22 said:
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
Click to expand...
Click to collapse
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
have you tried fastboot oem unlock again ?
uicnren said:
have you tried fastboot oem unlock again ?
Click to expand...
Click to collapse
Yes, it says it needs to be enabled in developer options
Sent from my Developer Edition Galaxy S5 using Tapatalk
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
uicnren said:
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
Click to expand...
Click to collapse
It says it will reboot in 5 seconds, but after 5 seconds the screen just goes blank. It appears the device is off, but maybe not.
Do you know what adb commands I would need to use to recover from this state?
Sent from my Developer Edition Galaxy S5 using Tapatalk
claytonjn said:
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
Click to expand...
Click to collapse
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
simms22 said:
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
Click to expand...
Click to collapse
Unfortunately that is not working for me (Not allowed in locked state!)
uicnren said:
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
Click to expand...
Click to collapse
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
claytonjn said:
Unfortunately that is not working for me (Not allowed in locked state!)
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Click to expand...
Click to collapse
If you have TWRP, boot to bootloader and use the following fastboot commands:
fastboot format userdata
fastboot format cache
Then boot to TWRP, connect to PC. Download a ROM to your PC and drag and drop in the root of internal storage. Then flash the ROM from TWRP, boot up, enable OEM unlock. Then boot back to bootloader and:
fastboot oem unlock
You should be good after that.
holeindalip said:
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
Click to expand...
Click to collapse
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
claytonjn said:
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
Click to expand...
Click to collapse
Follow my instructions listed above.
Evolution_Tech said:
Follow my instructions listed above.
Click to expand...
Click to collapse
II'm attempting that now.but fastboot format userdata and fastboot format cache fail. after booting into twrp the Nexus shows up in My Computer, but internal storage does not. I can push a ROM zip to the device with adb, but haven't figured out how to flash it yet because touch doesn't work...
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
claytonjn said:
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
Click to expand...
Click to collapse
glad you got it back, persistence pays off.
Lesson learned today? QUIT RE-LOCKING YOUR BOOTLOADER!
You can lock boot loader, you just have to make sure your phone boots first before locking it
Hi,
I had a bootloader locked mi a2 stuck in a bootloop so I took it apart put it into EDL mode and flashed stock images via MiFlash tool using the 'save user data' option. Now it boots and it asked for the previous lock pattern but it did not restore any data. Is all hope and data lost or am I missing something?
I really don't understand where is all the data gone if the data partition was not flashed. Its my gfs phone she had tones of photos on it, it would be amazing if somehow it could be restored.
In these process sometimes device reset itself and erase all internal data as edl is not a normal mode for flashing (May be i am wrong) .
MIN313 said:
In these process sometimes device reset itself and erase all internal data as edl is not a normal mode for flashing (May be i am wrong) .
Click to expand...
Click to collapse
If so, then why did it ask for the previous pass code at start up? I am really confused by this whole thing.
SidCounter said:
If so, then why did it ask for the previous pass code at start up? I am really confused by this whole thing.
Click to expand...
Click to collapse
Because it has been hard rest intentionally or un intentionally , according to android security you have to enter your last pattern , your email last sync and it is necessary even if you flash in edl using test points , you have to enter your last credentials and pattern or pin etc.
Don't be confuse , it normal Security Pass.
MIN313 said:
Because it has been hard rest intentionally or un intentionally , according to android security you have to enter your last pattern , your email last sync and it is necessary even if you flash in edl using test points , you have to enter your last credentials and pattern or pin etc.
Don't be confuse , it normal Security Pass.
Click to expand...
Click to collapse
Huh, okay so it is not to restore the data partition, it is just to confirm the owner of the device. Thanks for the info.
SidCounter said:
Huh, okay so it is not to restore the data partition, it is just to confirm the owner of the device. Thanks for the info.
Click to expand...
Click to collapse
hi, did you get your data back?
mcsergeant said:
hi, did you get your data back?
Click to expand...
Click to collapse
Sadly not, I gave up.
SidCounter said:
Sadly not, I gave up.
Click to expand...
Click to collapse
Thanks for quick reply
BTW you need to take backup of your internal data files if you need to flash stock or custom rom becouse thats mi a2 even with the official updates this phone can get bootloop.
i recomendeding you the use fastboot not MiFlash becouse you can control all the things happenin on flashing.
here is the ota flasher batch file without *fastboot erase ddr* command i have deleted it becouse if there is fastboot erase ddr command this will earse all the things on your phone
if you want to try this method:
1 install adb drivers
2 extract all image files to the same folder with OTAFlasher.bat
3 open CMD and type fastboot devices on fastboot mode (or adb devices reboot bootloader for enter fastboot mode)
4 if everything looks correct just type *OTAFlasher.bat* then press enter
this will take 30 mins to finish after that everything will be okay
have good day
Maharram said:
BTW you need to take backup of your internal data files if you need to flash stock or custom rom becouse thats mi a2 even with the official updates this phone can get bootloop.
i recomendeding you the use fastboot not MiFlash becouse you can control all the things happenin on flashing.
here is the ota flasher batch file without *fastboot erase ddr* command i have deleted it becouse if there is fastboot erase ddr command this will earse all the things on your phone
if you want to try this method:
1 install adb drivers
2 extract all image files to the same folder with OTAFlasher.bat
3 open CMD and type fastboot devices on fastboot mode (or adb devices reboot bootloader for enter fastboot mode)
4 if everything looks correct just type *OTAFlasher.bat* then press enter
this will take 30 mins to finish after that everything will be okay
have good day
Click to expand...
Click to collapse
Is it possible to flash the official ROM in fastboot with a locked bootloader? I also can't enbale usb debugging since the phone is in a bootloop.
Nope u need to unlock bootloader first
I assume that it's impossible to save the user data if the bootloader is locked in the case of a Mi A2 device? My Mi A2 randomly shut itself down and now it won't boot into Android anymore. I get the error "Can't load Android system. Your data may be corrupt. ..., TRY AGAIN or FACTORY DATA RESET". I didn't want to reset my phone before searching for a possible solution that would restore my user data. In the meantime I bought a replacement phone, on this phone I noticed that Google Photos did not backup any photos I took with my Mi A2 in the last 30 days. That's why it's so important to me to restore the user data, I just don't want to lose these photos. But I assume that there is no such solution that can achieve this with a locked bootloader right?
Moustachio_ said:
I assume that it's impossible to save the user data if the bootloader is locked in the case of a Mi A2 device? My Mi A2 randomly shut itself down and now it won't boot into Android anymore. I get the error "Can't load Android system. Your data may be corrupt. ..., TRY AGAIN or FACTORY DATA RESET". I didn't want to reset my phone before searching for a possible solution that would restore my user data. In the meantime I bought a replacement phone, on this phone I noticed that Google Photos did not backup any photos I took with my Mi A2 in the last 30 days. That's why it's so important to me to restore the user data, I just don't want to lose these photos. But I assume that there is no such solution that can achieve this with a locked bootloader right?
Click to expand...
Click to collapse
İn the fastboot mode u can access to the your internal storage. You need to do factory reset for fix the phone
So you're saying that I can restore the files by booting into fastboot and connecting the phone to the pc over usb right? Do I need any commands for this, or will it be recognized as external storage by Windows? The phone doesn't have USB-debugging enabled and isn't unlocked.
Maharram said:
İn the fastboot mode u can access to the your internal storage. You need to do factory reset for fix the phone
Click to expand...
Click to collapse
I tested it, but while in fastboot my computer doesn't show any storage devices.
Moustachio_ said:
I tested it, but while in fastboot my computer doesn't show any storage devices.
Click to expand...
Click to collapse
Boot into twrp and try this too
---------- Post added at 09:11 PM ---------- Previous post was at 09:07 PM ----------
Moustachio_ said:
So you're saying that I can restore the files by booting into fastboot and connecting the phone to the pc over usb right? Do I need any commands for this, or will it be recognized as external storage by Windows? The phone doesn't have USB-debugging enabled and isn't unlocked.
Click to expand...
Click to collapse
Ohh sorry i didn't know that your phone isn't unlocked. At this point all u need to do is factory reset i think
Maharram said:
Boot into twrp and try this too
---------- Post added at 09:11 PM ---------- Previous post was at 09:07 PM ----------
Ohh sorry i didn't know that your phone isn't unlocked. At this point all u need to do is factory reset i think
Click to expand...
Click to collapse
Yeah, that's the thing, I was hoping there was a way to at least restore the pictures on the phone because Google Photos did not backup my pictures for a month. But I guess there is just no way to restore those, not even with the EDL mode Time to reset the phone and move on then I guess.
Thank you for your time!
Moustachio_ said:
Yeah, that's the thing, I was hoping there was a way to at least restore the pictures on the phone because Google Photos did not backup my pictures for a month. But I guess there is just no way to restore those, not even with the EDL mode Time to reset the phone and move on then I guess.
Thank you for your time!
Click to expand...
Click to collapse
Anytime also maybe last time try recovery softwares
Just google it
Maharram said:
Anytime also maybe last time try recovery softwares
Just google it
Click to expand...
Click to collapse
Wow, why didn't I think of that myself?... I've done it a couple of times for other people! Thanks for the great suggestion, hopefully I can recover some stuff that way.
Moustachio_ said:
Wow, why didn't I think of that myself?... I've done it a couple of times for other people! Thanks for the great suggestion, hopefully I can recover some stuff that way.
Click to expand...
Click to collapse
No problem if this'll help you just let me know