Database Info

[Q] Bricked my Milestone XT720. Anyone know how to factory reset from PC?

Well today I was looking at root apps on the Android Market on my Motorola Milestone XT720 and downloaded Eris Market Fix. I wasn't too sure what the app was for, but I was under the understanding that it would give me full access to the market, even the hidden apps. I used it to fix my market which seemed to create a rom and used a cache clearing app like it had recommended. I turned off my phone, restarted it but when it turned on it showed the Motorola logo at the start then went into a black screen which it hasn't gotten out of since.
So now that my phone is bricked, are there any tricks or program out there that will let me factory reset or unbrick my phone over pc? I think realistically I just need to find a way to remove the rom.

reflash with rsdlite, will be fine

solnyshok said:
reflash with rsdlite, will be fine
Click to expand...
Click to collapse
Thank you for the suggestion but doesn't my pc need to recognize the phone first? Since it's in a black screen after start up, my phone cannot connect with my pc cable, it is not recognized as connected that is.

NorskHelgen said:
Thank you for the suggestion but doesn't my pc need to recognize the phone first? Since it's in a black screen after start up, my phone cannot connect with my pc cable, it is not recognized as connected that is.
Click to expand...
Click to collapse
press Camera + volume + Power,
you'll see some text "Battery OK, blah blah blah ,... OK To Program"
then connect it using USB, (hope all the necessary drivers are installed).
RSDLite will recognized it. Flash your way through heaven

spiderx_mm said:
press Camera + volume + Power,
you'll see some text "Battery OK, blah blah blah ,... OK To Program"
then connect it using USB, (hope all the necessary drivers are installed).
RSDLite will recognized it. Flash your way through heaven
Click to expand...
Click to collapse
Crap, I need special drivers as well? Sorry, I know this is a hassel aiding a misguided noob (was an iPhone user for 2 years up til last week) but are there any recommended drivers I should be Googling? I mean I have connected with my computer the days leading up to this, so I assume the default drivers are automatically installed, but even with you suggestion to hold the specified buttons I am getting no response on the USB.

Ok thanks alot guys, I have the bootloader going now. Now is there a specific flash file I should have downloaded to use on my XT720?

Found a Southeast Asian rom and flashed it. Thanks alot for both your guys hel. Saved me from sending it away and spending $50 for nothing

no need to flash with computer
i think you don't have to flash your phone to restore to factory just pres the media bottom+ power bottom to select the restore to factory using the volume bottom up n down to exe using the media bottom again...

Oh ok, well know I know. I actually tried your method of rebooting the phone, but once I got to the screen with the triangle and exclamation mark it wouldn't do anything. I pressed the camera button and media button but neither created a reaction. It wasn't until i finally pressed power when it just simply restarted the phone. The only time I've gotten recovery to give me scroll options is recovering through ROM Manager for the Android Market.

spiderx_mm said:
press Camera + volume + Power,
you'll see some text "Battery OK, blah blah blah ,... OK To Program"
then connect it using USB, (hope all the necessary drivers are installed).
RSDLite will recognized it. Flash your way through heaven
Click to expand...
Click to collapse
my xt720 says battery low when i pressed camera + volume + power . but i already charged it morethan 4 hours why did this happen ?

Same Problem
Hello guys
I have the same problem. my phone has bricked and it's only going into Bootloader.
i don't know which rom i should flash in it using RSD lite. From where i can get Southern Asian Rom ???
plz anyone can guide me plzzzz

Critical error
i installed UK sbf using RSD Lite V. 60 but it says "Critical Error ...." at the last ........
what would be the solution ?? i live in Pakistan .......
should i try Singapore sbf ?

Fixed it
Ok AlhamduLILLAH i have fixed my problem ...
actually i was using wrong Rom for my motorola milestone A853
Advice:
Check first which model you are using then install a specific rom on your phone via RSD lite .....

Fixing a bricked Nexus S

I had a Vibrant before and flashed it constantly. I soft bricked it several time and it was easy just to Odin back to stock and try again. Before I begin to flash Roms on this phone I would like to know how one would fix a bricked Nexus S. I searched "bricked Nexus S" and didn't come up with much.
Sent from my Nexus S using XDA App

Flash a stock img thru fastboot/adb. Just as painless as Odin was if not easier.
Sent from my Nexus S

Yeah I figured that much but I have never used ADB before. What are the commands to flash a stock img and where can I get a stock img? I already have ADB set up, serial # comes up when I enter - adb devices. I'm ready to root and flash but I want to be prepared for anything. I don't want to panic for ten minutes like I did the first time I bricked my Vibrant.
Sent from my Nexus S using XDA App

You should be able to snag a stock image from the development section. As far as what adb commands to use check out any of the root tutorials in development.
Sent from my Nexus S

bricking the phone is not easy... everything can be wiped and reinstalled with ease. Recovery is your friend.

leyvatron said:
bricking the phone is not easy... everything can be wiped and reinstalled with ease. Recovery is your friend.
Click to expand...
Click to collapse
That's why I love this phone. When I first rooted my wife's phone she was a nervous wreck about me ruining it. Now, she jokingly cheers when it boot loops or hangs on the google splash screen.

kenvan19 said:
That's why I love this phone. When I first rooted my wife's phone she was a nervous wreck about me ruining it. Now, she jokingly cheers when it boot loops or hangs on the google splash screen.
Click to expand...
Click to collapse
Coolest wife ever? haha

risegeek said:
Coolest wife ever? haha
Click to expand...
Click to collapse
hehe why'd'ya think I married her

Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?

Van_Dyke said:
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Click to expand...
Click to collapse
not enough information is present. you can attempt to get into bootloader / recovery, plug USB to the computer. When plugged, does the computer make a plugged in noise? if it does.. try turning it on, try using adb on it, etc.
as a last resort: if its not rooted or modified in any way, you can go back to best buy and exchange it since you said you've only had it for 3 days

Van_Dyke said:
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Click to expand...
Click to collapse
First thing to do is pull the battery, let it sit a minute or two, then put the battery back in and try to boot.
Also, try booting into recovery or fastboot. With power off, press and hold volume up button, then press/hold power on switch. You should enter fastboot mode. From fastboot menu, select boot to recovery. The phone will reboot and you'll get to a screen with an "!" and an android robot on it. At that point you press hold power, then press/hold volume up (make note that this is the reverse of what you did earlier).
Once in Recovery, try wiping cache from the menu.
Reboot.
If still no good, then repeat the process but pick factory reset/wipe from the menu in recovery. Note that this will wipe all personal data and apps off the phone but it won't touch your sdcard contents.

The case with pull battery - not working.
I can't enter fastmode using 2 keys combination.
Computer don't recognize the phone. It's brick...

Van_Dyke said:
The case with pull battery - not working.
I can't enter fastmode using 2 keys combination.
Computer don't recognize the phone. It's brick...
Click to expand...
Click to collapse
Last option is to try to trick it into Samsung's Download Mode (see the Odin thread in Development section), but if the keys aren't recognized you can't soft boot into it so you'll need a dongle with a resistor to get there.
Sounds like it's truly a brick at this point. You'll probably have to return it, but I'm concerned about returning a phone that has your personal data on it without being able to wipe it. Doesn't seem like much way around that at this point if you can't get fastboot or download.

get the 301k resistor JIG and then you can go into the download mode even without the 2 keys + usb plug
you can always make your own JIG if you have the materials at home or a nearby Radio shack

Thx for all Your advices
Problem was with the dead battery. The battery died during the night - i don't know why. I think the system waren't able to boot up ant start charging process.
My solution:
I took 9V battery, 2 wires and charged dead battery for a while from 9V battery. Then a put it into phone and plug in to wall charger. Charging process started
Now everything is ok

That's pretty scary that it wouldnt take a charge if run down completelty. But hey handy to know incase it happens to any of us,
If you get any repeat i would take it back to get a fresh battery of course (only right to do so).
here's hoping you never need to though

Van_Dyke said:
Thx for all Your advices
Problem was with the dead battery. The battery died during the night - i don't know why. I think the system waren't able to boot up ant start charging process.
My solution:
I took 9V battery, 2 wires and charged dead battery for a while from 9V battery. Then a put it into phone and plug in to wall charger. Charging process started
Now everything is ok
Click to expand...
Click to collapse
That is scary......
Sent from my Nexus S using XDA App

Bricked
Tried unlocking nexus s last night, now it appears bricked. Cannot connect to computer to reflash as it seems to have wiped the driver. Any ideas on how to bring it back from the dead? thanks
I have managed to see the phone with fastboot. I was hoping that fastboot update, would re-image the brick. Can anyone let me know the correct syntax. I am not able to copy an image onto the phone. Thanks again

Noob {MAC User}... Please be gentle
Greetings Everyone,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I reboot.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamara

warrenb said:
Tried unlocking nexus s last night, now it appears bricked. Cannot connect to computer to reflash as it seems to have wiped the driver. Any ideas on how to bring it back from the dead? thanks
I have managed to see the phone with fastboot. I was hoping that fastboot update, would re-image the brick. Can anyone let me know the correct syntax. I am not able to copy an image onto the phone. Thanks again
Click to expand...
Click to collapse
It would be easier to help you if we knew exactly what you did that caused the problem. You said you tried to unlock it...you mean fastboot oem unlock or something else?
If you can get into fastboot, you're not totally lost, but the computer needs to see the phone to do it.
I'm working in a vacuum here on what your real problem is, but without further details, the things you can try are boot into recovery (from the fastboot mode select boot recovery)...if you're stock recovery, press/hold power, then volume up once you see the android "!". From there wipe cache and whatever else it will let you wipe. Try rebooting. IF that didn't work go back to recovery and try a factory reset of the phone (will delete all your apps and stuff on the phone, but not on the sdcard (pics and stuff).
If none of that works, you can still try getting Clockwork recovery on the phone via fastboot. Boot phone to fastboot and then on computer type the command "fastboot flash recovery <put file name of recovery version you're flashing here>"
Once in clockwork, you should have access to adb via the computer. On your computer go to the Development section here and download any of the various nandroid images posted there. Now you use clockwork mounts and storage menu to mount the sdcard. Then use adb to "adb push <insert path and filename of your nandroid image here> /sdcard"
Unmount the sdcard with the clockwork mounts and storage menu. Now go to the backup menu, select advanced restore and find the nandroid image and restore it.
With any luck, you should be able to boot into a fresh phone.

Oneplus One Dead

Hey guys. I'm kinda desperated so let's see if there is anything else I can do.
I was playing a game on my phone and it started rebooting alone.
At this point, I long pressed the power button, don't ask me why, but I did it. and bang. it is dead. No boot, no loading, nothing. It still vibrates when I try to turn it on.
I had 30% Battery left.
I have root and my phone for 3 months.
I had Nandroid backup.
Long press power button, volume up + power, volume down + power doesn't work.
When connected to PC, I get the QHSUSB_BULK device on.
Tried to ColorOS Method but:
I cannot install ColorOS drivers cause it doesn't detect them.
I tried Qualcomm drivers and they worked, so then I used the program Msm8974DownloadTool to install ColorOS.
It went okay, all finished and I got the green letters in the end.
Still doesn't boot up, nothing changed.
I cannot detect my phone via ADB. Tried with the drivers and without the drivers and with clean drivers.
What can I do? I always had such care for my phone in case of an emergency, but for some weird reason this happened. I wasn't even messing up with the phone, it just died cause I turned it off while booting up?

Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...

cyldman said:
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
Click to expand...
Click to collapse
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..

jukiewalsh said:
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
Click to expand...
Click to collapse
What do you mean I lost my adb access? I can still find my phone there and it's still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesn't boot back up.

cyldman said:
What do you mean I lost my adb access? I can still find my phone there and its still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesnt boot back up.
Click to expand...
Click to collapse
Disregard that then, when the phone is booted you have to manually give adb access but you're right when it's in recovery or other modes it's already there.
Does your screen power on at all? Do you think your LCD/digitizer could've somehow just died on you?

I highly doubt it, it happened when I shut off the phone when it was rebooting. I dont hear anything when I turn on the phone and i cant press anything or slide to unlock. nothing. so ....yeah. Weird stuff is that I did fastboot reboot and now i can't get to fastboot again. sigh.

Read this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
Somewhere within it is the solution to your QHSUSB_BULK problem.

Already did bro, and I fixed it, did you even read my full post? I managed to install colorOS, but it's still not booting up.

Hello guys! Last update! My phone was not even vibratting when i pressed power button. I put it to charge and finnaly I got a screen. its not what I wanted...but its a small step!
Its the Low battery charge icon! So...I've heard about this other issue about the phone not charging. Could this be it? I will be trying some techniques like https://forums.oneplus.net/threads/...een-opo-not-booting-due-over-discharge.88107/.
Hopefully it will help, but it may take some days.

[Q] Android won't boot...

Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!

kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?

ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/

If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:

Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.

kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?

The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.

howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor

Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.

kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.

theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!

You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.

Question HELP PHONE STUCK ON BOOTLOOP AT GOOGLE WRITING AND CANT GET DATA OUT

Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.

andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
If you can enter recovery mode try to sideload the same exact ota package of the rom she's running, maybe that can help. Good luck!

andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
As @acuicultor said;
Here's Googles official OTA updates and instructions etc.
From what i've read briefly and as far as i can gather (still running a stock pixel 7 pro - for the first phone in god knows how long, so i'm not well read on this device but...) if you can sideload the latest OTA update via sideload then you should in theory be able to save the data and boot again. But if you flash full firmware then your device will be wiped in the process (if that's even possible with a locked bootloader).
Very best of luck
EDIT: hmm thinking about it, you won't have enabled USB debugging in dev options, hang on, i'll reboot direct to recovery to see if i can get the device recognised without USB debugging enabled. Sorry to be vague (hopefully someone more experienced with this device will chime in with more advice), like i say, i'm not rooted, flashed with custom rom - nothing, just plain old stock so i've not read up much on proceedures for this device. Bare with me!!

Had another thought, do you or have you been using Google photos to view your images on the device. If so, did you enable backup photos online when you first set the app up? If so, they could be backed up automatically...
Edit: my bad..
Try this link
If that fails just Google 'Google photos sign in'

Just tried from recovery to run some adb cmd's, no joy without enabling debugging 1st
There may be hope... If your photos aren't backed online already from above link...
EDIT:
1. From power off state (make sure the device is charged before apply any ota update) Press vol down and power together. As soon as it boots to google logo, let go of vol down, then power. That will put you in fastboot mode where you use the vol up/down to navigate to Recovery mode and power button to select.
2. Then when you have the screen that says 'no command', press power button and CLICK vol up (releasing vol up straight away but keeping power pressed). That'll take you a blue menu at top of screen.
3. Use vol buttons to navigate to 'apply update from adb'. I have checked using 'adb devices' and 'adb reboot sideload' cmd's on PC and the device is now recognised...
Will write further instructions shortly. (no guarantees this will work tho without losing data...or even if it'll work at all - i suspect the OTA update with just fail to transfer)
OR there is another option, using the same instructions above (1) in fastboot mode use the volume buttons to navigate the menu, power button to select Rescue mode. Then contact your service center for support who will advise/offer support - hopefully, which may end up having to send the device in and still offers no guarantee of preserved data

reg66 said:
@acuicultor said;
Here's Googles official OTA updates and instructions etc.
Click to expand...
Click to collapse
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.

WoKoschekk said:
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.
Click to expand...
Click to collapse
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol

reg66 said:
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol
Click to expand...
Click to collapse
yes, maybe...
FYI: Stock recovery only uses a minimal adbd with a very limited set of commands. That's why some known ADB commands won't work.
minadbd