Related
Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.
Sapphire18 said:
Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.
Click to expand...
Click to collapse
Em so is the bootloader unlocked? you could try to see if adb is working in fastboot or if it is unlocked I think TWRP lets you use adb.
Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.
Sapphire18 said:
Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.
Click to expand...
Click to collapse
Ok but have you tried adb in fastboot?
adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.
Goatshocker said:
adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.
Click to expand...
Click to collapse
Omg so forgot you can use a mouse so going to do that now for no reason lol.
Darknites said:
Omg so forgot you can use a mouse so going to do that now for no reason lol.
Click to expand...
Click to collapse
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.
Goatshocker said:
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.
Click to expand...
Click to collapse
Cool think I have a play later.
Okay, here is what I got, the OTG cable is not working, that means the phone doesn't have Android 4.1.
The ShareKM application requires installation into the phone, meaning it is out of question too.
I am experimenting with this ADB in fastboot, but I am not really sure how that fastboot command works when I run ADB.exe trough command prompt and list devices, it show me only my other phone in USB debugging, when I run the fastboot.exe and type adb devices it says "waiting for the device", I do not really know how to work with this with a little guide, it shows me some commands there, i tried the one with rebooting into bootloader, but it still says only "waiting for device".
Could you give me a little guide perhaps link to guide what exactly I am supposed to do to run ADB in fastboot?
I am pretty technical type, dont need noobish explanation.
Thank you
Okay, I managed to get into fastboot, I always thought it is something with the fastboot.exe in SDK Platform-tools, well, anyway, I am inside, it says Fastboot USB, but adb still isnt showing the device in the list.
Also there is a big pink ***LOCKED***, that means that bootloader is locked I guess.
Any other ideas how I could backup the files? or any other suggestions?
Thank you
Moving slowly forward, I was being stupid and I was using the ADB command instead fastboot command, when I am in fastboot mode now, well, trough fastboot command now the PC recognizes the phone, altho what is the next step now?
Thanks again
Yeah, the ShareKM app was never really ment for you, it was more of a suggestion to dark sorry if it confused you.
I ran some quick tests, and yeah Im afraid adb is, in fact, not working in bootloader.
What happens if you boot into recovery? Maybe it works there?
What kind of things do you need to save? Is it just like pictures and stuff from the sdcard?
In that case, you could unlock the bootloader (this will wipe the device data, like applications etc) and install TWRP. Im 100% sure ADB works in TWRP without you needing to use the screen.
Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?
Sapphire18 said:
Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?
Click to expand...
Click to collapse
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.
Darknites said:
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.
Click to expand...
Click to collapse
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?
Sapphire18 said:
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?
Click to expand...
Click to collapse
Em did you try scan under select device?
Darknites said:
Em did you try scan under select device?
Click to expand...
Click to collapse
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.
Sapphire18 said:
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.
Click to expand...
Click to collapse
Then I'm out of ideas because unlocking the Bootloader will wipe the sd.
Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)
Goatshocker said:
Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)
Click to expand...
Click to collapse
And I am not throwing any blame either, I am just open to every solution
How would unlocking the bootloader help me? so I could put that TWRP inside and do some magic with it?
For the recovery part, I am not really sure how it is supposed to work, but every picture I googled shows some text
along with the exclamation mark, but the only thing I am getting is exclamation mark, and after a while the phone reboots.
I am guessing the recovery either wont load up, or something is wrong, should I try running ADB while that exclamation mark is shown?
Hi, I have a friend who has just smashed their Desire S whilst out on Sat.
Unfortunately, as the title says, they have no screen (touch doesnt appear to work either but no real way of telling!), not root, no USB debug and I have already checked and they didnt have their contacts set to sync with their google account but with the phone! :-/
Can anyone give any suggestions other than a screen replacement? They have already got an S3 on the way today so just want to be able to restore their contacts.
Cheers and thanks in advance!
I think this is definitely possible, but it may get very complicated.
Do you have adb in recovery (you'll have to boot into fastboot and blindly navigate to the recovery option)? Is the bootloader unlocked?
Aquous said:
I think this is definitely possible, but it may get very complicated.
Do you have adb in recovery (you'll have to boot into fastboot and blindly navigate to the recovery option)? Is the bootloader unlocked?
Click to expand...
Click to collapse
Thanks for replying Aquous!
I have just been given the phone today from a friend to try and help them out so im not sure on either? Do you have a desire s and would be able to tell me the button sequence to get into recovery to find out? As for the bootloader being unlocked, i very much doubt it as the phone was running a stock orange rom.
Any ideas?
Cheers,
It is unlikely indeed that you will be able to recover the data as the phone is. If you're in the UK (possible as the phone is on Orange) and fancy posting it then I can stick my LCD and touch panel on it for you so I can recover the data.
Also if u r in the uk, try a phone repair shop that has jtag, they should be able to pull any data off the phone.
radeonorama said:
Thanks for replying Aquous!
I have just been given the phone today from a friend to try and help them out so im not sure on either? Do you have a desire s and would be able to tell me the button sequence to get into recovery to find out? As for the bootloader being unlocked, i very much doubt it as the phone was running a stock orange rom.
Any ideas?
Cheers,
Click to expand...
Click to collapse
Then you probably don't have adb in recovery either.
We can try the easy way first: from the Google Play website (on your computer), download TalkBack to your phone and see if you can launch it blind. From there on, your phone will read to you what's on the screen
If you can't manage to do that, I have another option in mind but it's complicated and you may not be able to recover your contacts:
Unlock the bootloader via htcdev. This will wipe your data, but if you don't allow the rom to boot after the unlocking, this is OK.
Immediately after issuing the fastboot oem unlock command, HOLD DOWN THAT VOLUME - BUTTON. If the ROM is allowed to load, your data will be significantly harder, if not impossible, to recover.
If you held Vol - correctly after the unlock, you'll be in fastboot (if the phone vibrated, quickly pull the battery before the rom starts writing to the data partition).
From fastboot, boot a custom recovery ('fastboot boot recovery.img')
In this custom recovery, you have adb. Pull the data partition and run file recovery software to try to reconstruct the data that was on it but was wiped by the unlock process.
Purposefully not giving any clearer instructions than this, because if you don't know what you're doing the chances are very high that you're going to do it wrong and won't be able to recover the data.
Aquous said:
Then you probably don't have adb in recovery either.
We can try the easy way first: from the Google Play website (on your computer), download TalkBack to your phone and see if you can launch it blind. From there on, your phone will read to you what's on the screen
If you can't manage to do that, I have another option in mind but it's complicated and you may not be able to recover your contacts:
Unlock the bootloader via htcdev. This will wipe your data, but if you don't allow the rom to boot after the unlocking, this is OK.
Immediately after issuing the fastboot oem unlock command, HOLD DOWN THAT VOLUME - BUTTON. If the ROM is allowed to load, your data will be significantly harder, if not impossible, to recover.
If you held Vol - correctly after the unlock, you'll be in fastboot (if the phone vibrated, quickly pull the battery before the rom starts writing to the data partition).
From fastboot, boot a custom recovery ('fastboot boot recovery.img')
In this custom recovery, you have adb. Pull the data partition and run file recovery software to try to reconstruct the data that was on it but was wiped by the unlock process.
Purposefully not giving any clearer instructions than this, because if you don't know what you're doing the chances are very high that you're going to do it wrong and won't be able to recover the data.
Click to expand...
Click to collapse
Bloody legend!
Using the above coupled with Droid explorer i managed to pull everything she needed! Thanks so much for taking the time to help me out!
All the best!
radeonorama said:
Bloody legend!
Using the above coupled with Droid explorer i managed to pull everything she needed! Thanks so much for taking the time to help me out!
All the best!
Click to expand...
Click to collapse
Holy ****, you actually did this? And it WORKED? You, sir, have some serious balls! Gratz!
By the way, this has HUGE privacy implications
Aquous said:
Holy ****, you actually did this? And it WORKED? You, sir, have some serious balls! Gratz!
By the way, this has HUGE privacy implications
Click to expand...
Click to collapse
Yup, everything i needed off it worked.
I left it for a while as a last resort because of the risk of total data loss and bought a replacement screen which was DOA!
So you plan came into play and it really worked. It wasnt so hard as the steps you gave just helped me get the order right in my head rather than trying something and mucking it up even more!
Thanks again good sir! She was very pleased!
Good evening , well after few days reading diferent sites , youtube vids on how unlock the device lockscreen, i tryied downloading adb tool , and droidexplorer and even sdk tools.
My main trouble is that half of my screen wont work and i cant get acces to my mobile to unlock it.
I tryied to get in to recovery mode to wipe out the cache so i could get via usb my folder with my family pictures and so on , but after selecting recovery mode it says no commands avaible...
So this option no idea why is not working , no idea if its cuz my usb dont have the settings to get into the folders or what.
So i really would appreciate any help or guide so i can try to pull somehow my family pictures from the phone.. :S
The phone is not rooted , i never enable anything so i guess that debugging i did read some post wont work with that adb comands from cmd... So im kinda lost right now guys.
Thanks for any help
Does the phone have an unlocked bootloader? If it does, you could flash twrp, boot into twrp, and mount the data partition.
If it doesn't have an unlocked bootloader, you could put the motherboard into another working n5 to get the data from the phone. If you don't have a spare n5, your best option may be to buy a replacement lcd, frame, and digitizer from third party seller such as eBay or Aliexpress. You could also look for a cheap and used n5 with a working screen.
I have no idea if the bootloader is unlocked , how can i check it? And there is a option to unlock it somehow? The main problem is that i cannot access to my phone via usb since its locked , if i could force somehow to get the usb working would be enough.
Cuz changin the motherboard it will just make it like new one , but what i need is kinda much the files i have in the phone , the phone is irrelevant , but not my family pictures.
Thanks again
audit13 said:
Does the phone have an unlocked bootloader? If it does, you could flash twrp, boot into twrp, and mount the data partition.
If it doesn't have an unlocked bootloader, you could put the motherboard into another working n5 to get the data from the phone. If you don't have a spare n5, your best option may be to buy a replacement lcd, frame, and digitizer from third party seller such as eBay or Aliexpress. You could also look for a cheap and used n5 with a working screen.
Click to expand...
Click to collapse
If the bootloader is not unlocked, don't unlock it as unlocking will wipe the phone!
If you put the motherboard from your current phone into another phone, you should be fine.
audit13 said:
If the bootloader is not unlocked, don't unlock it as unlocking will wipe the phone!
If you put the motherboard from your current phone into another phone, you should be fine.
Click to expand...
Click to collapse
I understand that a way to solve , but i have no idea how to do a change of the motherboard o.o
When you cold boot the phone, do you see an icon at the bottom of the screen that looks like an unlocked padlock? It appears below the word Google just before the boot animation appears.
maybe you should boot into safe mode first ... it might be an app you downloaded causing the problem
---------- Post added at 07:48 PM ---------- Previous post was at 07:46 PM ----------
when you get to the screen that says no commands available, press and hold the power button and press volume up once ... the commands should show up now
---------- Post added at 07:48 PM ---------- Previous post was at 07:48 PM ----------
[/COLOR]when you get to the screen that says no commands available, press and hold the power button and press volume up once ... the commands should show up now [/QUOTE]
Hello.
Today I installed updates from via Aptoide (i know, dumb idea, but i thought, if smth isnt fitting, i can just deinstall the update) on my Galaxy S7, suddenly the UI crashed, cuz it appears that an App, i dont remember the name since it updated everything, has overwritten the system ui settings. All i remember is, it was a Samsung App.
Now the problem is, i just have a black screen.
I never synchronised my data and would loose like 200 contacts and the last years of my life in pictures and films...
I also hv all my passwords in a password safe on my phone, a lot of documents and so on, but the contacts and private life stuff is even more important.
So, for no chance I will wipe all my data to have a working phone again.
I tried to wipe the cache. Not working.
I tried to go into Secure Mode, but the UI is missing there too.
Maybe im too dumb to install the ADB correctly, but its not even finding a device when I connect the phone with the PC, even though im in Recovery/Apply Update from ADB.
I didnt allow the debbging by ADB in the phones options when it was working. So i dont know whether that could cause the problem or im not able to use configure the ADB drivers right on my PC.
I also tried to just connect the phone with my PC to save the data, but i need to enter the PIN on the Phone to get access to the phone storage.
I also thought about using a custom Recovery to just Save my data, but a friend told me that the phone would recognize that and encrypt the files on my phone then.
I hope you can help me out and excuse my stupid update behavior and my english skills. :/ Ive already learned smth from that incident.
Kind Regards.
RCEPaul said:
Hello.
Today I installed updates from via Aptoide (i know, dumb idea, but i thought, if smth isnt fitting, i can just deinstall the update) on my Galaxy S7, suddenly the UI crashed, cuz it appears that an App, i dont remember the name since it updated everything, has overwritten the system ui settings. All i remember is, it was a Samsung App.
Now the problem is, i just have a black screen.
I never synchronised my data and would loose like 200 contacts and the last years of my life in pictures and films...
I also hv all my passwords in a password safe on my phone, a lot of documents and so on, but the contacts and private life stuff is even more important.
So, for no chance I will wipe all my data to have a working phone again.
I tried to wipe the cache. Not working.
I tried to go into Secure Mode, but the UI is missing there too.
Maybe im too dumb to install the ADB correctly, but its not even finding a device when I connect the phone with the PC, even though im in Recovery/Apply Update from ADB.
I didnt allow the debbging by ADB in the phones options when it was working. So i dont know whether that could cause the problem or im not able to use configure the ADB drivers right on my PC.
I also tried to just connect the phone with my PC to save the data, but i need to enter the PIN on the Phone to get access to the phone storage.
I also thought about using a custom Recovery to just Save my data, but a friend told me that the phone would recognize that and encrypt the files on my phone then.
I hope you can help me out and excuse my stupid update behavior and my english skills. :/ Ive already learned smth from that incident.
Kind Regards.
Click to expand...
Click to collapse
Damn that's crazy I be knowing how you feel like when you make that one mistake and it messes up your phone if your able to use a custom recovery I suggest you flash it and find a decryptor zip to remove decryption from your device and then factory restore from twrp or you could do a hard reset from your phone to factory restore just make sure you remember the last Google account you used when you set up your phone account as to your data like pictures and stuff if you wipe threw custom recovery you won't lose that as internal storage is its only partition not wiped by factory reset however with stock recovery factory reset wipes data and internal storage partition
([emoji813]9/[emoji725]/9[emoji813])
So a friend and me figured out that you can access the phone by pc in secure mode by not even entering the PIN.
So i have the files now, but cant get access onto my contacts, not even with software, since ADB is deactivated in phones options.
Any hint how to get them extracted too?
RCEPaul said:
So a friend and me figured out that you can access the phone by pc in secure mode by not even entering the PIN.
So i have the files now, but cant get access onto my contacts, not even with software, since ADB is deactivated in phones options.
Any hint how to get them extracted too?
Click to expand...
Click to collapse
That's interesting if I knew I would of told you
([emoji813]9/[emoji725]/9[emoji813])
Which recovery works with Samsungs encryption and could restore the files?
Im noob in such things, sorry-
RCEPaul said:
Which recovery works with Samsungs encryption and could restore the files?
Im noob in such things, sorry-
Click to expand...
Click to collapse
Xda is your friend you need to research and next time keep it simple modifying there phone is not for everybody it's a process and something can always go wrong cause you can't plan for everything
([emoji813]9/[emoji725]/9[emoji813])
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