Database Info

[Q] Recovery of files

Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated

bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
You don't need to boot in recovery, boot in bootloader only.

polobunny said:
You don't need to boot in recovery, boot in bootloader only.
Click to expand...
Click to collapse
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.

bahagiga said:
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.
Click to expand...
Click to collapse
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
http://junefabrics.com/android/

polobunny said:
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
link
Click to expand...
Click to collapse
Hmm, on the third step where it says "installing pdanet to your phone" it just like freeze and on my phone in the bottom it says "FASTBOOT STATUS - FAILInvalid Command"
what should I do??

bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium

Bkadleck said:
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I tried but I dont think I can, when I try it just goes into that 'bootup screen, with the Google text and lock icon'. :/ Not sure what to do

Im still stuck and havent been able to get around this, any helpful information is appreciated. Thanks in advance

Hey guys, Im still stuck with this issue. Anyone who has some tips on what to do or has an idea of what it could be? I just formatted my PC yesterday Windows 7 32bit and everything should be up to date.
Kind regards,
baha

If there's anyone out there I would greatly appreciate your help! I have some pictures that are very valuable to me (pictures of my dog) and would really love to see if I could recover them.
I cannot start up my phone the "normal" way, I can only start up the Fastboot mode. I have the Samsung phone drivers installed along with the Google USB drivers. I have attached a picture that shows that there should be no problems with the drivers. I have tried to use the google usb drivers specifically but still the same. I have also attached a picture of the command prompt and as you can see nothing really happens. I have tried different tutorials and all kinds of ways trying to make it work but I have no clue what the problem is since I am not getting any other error message.
Any help is appreciated, please!
I typed fastboot devices in the cmd prompt and it actually listed a device serial number which matches then one stated on my phone in the fastbootmode. Any idea what to do or what this means?

Phone wont connect

Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.

InV15iblefrog said:
Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.
Click to expand...
Click to collapse
your phone must be in FASTBOOT bootloader mode..not in the HOME of your ROM..
if you don't wan to turn off your phone first and pressing volume down + power to go to bootloader..then you can using a adb command on cmd while your phone is still in the HOME of your ROM.. type "adb reboot bootloader" then select "FASTBOOT" now you can type "fastboot oem get_identifier_token"
don't forget to disabled Fast boot mode and enable USB Debuging first from the system settings and just connect your phone to pc as charge mode..
hope this help..

Sorry mate. Tried that before your post though.
However the person for whom I was doing this no longer needs it doing, and plans for a newer device, so I no longer have this device available. Thus, i thanked you, since it was a cue for me to mention that.
Cheers.

This model of HTC is died

[GUIDE] V20 Fastboot access in Windows.

So I'm seeing a ton of posts of folks not able to get fastboot to see their devices. I've done some tinkering around and found a set of drivers that work fine for both ADB and Fastboot. (Attached)
Uninstall any ADB drivers you have on your system. Easiest way is to plug your phone in, go into device manager, right click your phone and select uninstall and check the box that says to remove the driver as well.
Then download this package, extract, simply run install.exe as admin. Don't panic, it doesn't do anything visual.
Now plug your phone in and see if adb works, you may need to authorize the computer again on the phone so make sure it's unlocked.
Reboot into bootloader and check if fastboot sees the phone by using
Code:
fastboot devices
If not then go back into device manager and right click on your phone, select update driver, let me select one from a list and you should see "Fastboot interface (Google USB ID)". Select this one.
Check fastboot without unplugging with the same command. Check and see if you can send commands to the phone by using for instance,
Code:
fastboot getvar unlocked
If the command fails, simply plug the phone into a different USB port and the same Google driver should install again and you should be able to send commands to the phone. Alternatively, you can reboot the phone by tapping the battery out and starting it all over again.
Now she chooches.
Lemme know if you're still having problems.

bless up ??

Does this work for sprint variant?

im having problems...damn it i don't get this
---------- Post added at 03:19 PM ---------- Previous post was at 02:42 PM ----------
any help please?

Verizon variant here,
I cannot seem to get this dang V20 in the right mode
(I've seen a bootloader or two in my day):highfive::laugh::silly:
I have used the adb command (several times)
Code:
adb reboot bootloader
to get it into bootloader mode, alas it is to no avail since all the command does is send the phone into "Restart" mode; nor can I get fastboot to recognize it when it is in, what I believe to be , the bootloader for said LG V20 of the
Verizon persuasion!​
Suggestions?

You need fastboot, not bootloader... To get it, turn off your phone, plug your LG cable into the computer, ( but not the phone yet) hold the volume down key for 5 seconds then plug it into your cable, do not release the button till your phone boots. It should boot into fastboot... Provided you have turned on USB debugging in developer settings (turn on oem unlock while you are in there too. (this is the way on the tmo V20 at least... If that doesn't work, I would use the dirty Santa guide
Sent from my LG-H918 using Tapatalk

Not sure how I finally got it working for my Verizon variant as I tried like four or five different ways, but someone should definitely make a video.. Perhaps I will since I think visuals are a good aid to go along with written instructions..

Thanks bro works
Very easy
With my t mobile v20

My phone shows as connected in adb devices. I can also get it to reboot bootloader, but once im there.. I cant issue any commands such as fastboot oem device-id. It gives me the dreaded waitng for any device.

can't manage to make this work for H990DS, i don't get the usual authorization window to the computer, only get the window to choose which USB mode (battery charge, file transfer, so on...) I'm trying to get adb to work to activate agressive Doze on Greenify app, any help?

Thanks
Vexamus said:
So I'm seeing a ton of posts of folks not able to get fastboot to see their devices. I've done some tinkering around and found a set of drivers that work fine for both ADB and Fastboot. (Attached)
Uninstall any ADB drivers you have on your system. Easiest way is to plug your phone in, go into device manager, right click your phone and select uninstall and check the box that says to remove the driver as well.
Then download this package, extract, simply run install.exe as admin. Don't panic, it doesn't do anything visual.
Now plug your phone in and see if adb works, you may need to authorize the computer again on the phone so make sure it's unlocked.
Reboot into bootloader and check if fastboot sees the phone by using
Code:
fastboot devices
If not then go back into device manager and right click on your phone, select update driver, let me select one from a list and you should see "Fastboot interface (Google USB ID)". Select this one.
Check fastboot without unplugging with the same command. Check and see if you can send commands to the phone by using for instance,
Code:
fastboot getvar unlocked
If the command fails, simply plug the phone into a different USB port and the same Google driver should install again and you should be able to send commands to the phone. Alternatively, you can reboot the phone by tapping the battery out and starting it all over again.
Now she chooches.
Lemme know if you're still having problems.
Click to expand...
Click to collapse
Perfect and Easy!!!! :good:

thx..ur ma angel

I can't find my phone in Device Manager.

this is great and works like a charm! thanks!

Thanks!

The Unofficial Official Nokia 8 Bootloader Unlock Method

If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3

why another topic ?!

foxbatul said:
why another topic ?!
Click to expand...
Click to collapse
Because I don't expect people to dig around in all the Nokia 8 Guide threads to find the exact and, to my knowledge, only way to unlock the bootloader. Furthermore, I found this solution in a sort of unrelated thread, which would make the solution even harder to find for the average user.

S5Guy said:
Because I don't expect people to dig around in all the Nokia 8 Guide threads to find the exact and, to my knowledge, only way to unlock the bootloader. Furthermore, I found this solution in a sort of unrelated thread, which would make the solution even harder to find for the average user.
Click to expand...
Click to collapse
I understant but not.
Here it's not the place for lazy ones. Or for apple boys.
Unlock, modding, ROMs are for people with other approach. So this kind of topics make more noise instead to help.
Just my 2 cents.
BTW - thank you posting "downgrade to oreo" procedure.
it s the offline one ( my choice was to use "register to beta" and" unregister").
no need SD card or something, just a good wifi connection and patience.

Thanks for this. I just noticed that the "OEM unlocking" is disabled and greyed out on my TA-1012 device. Will it still work?

I cant get into the Phone without establishing an Internet connection, any tips?

Thank you so much OP this method worked perfectly I finally was able to unlock the bootloader

There seems no way for me to get past the Wifi selection page, how did all of you got into the system?

Ok solved this one, had to Update to P remove the Google Account linked to the Device and downgrade again.
It's Part of the Factory Reset Protection that you cant skip the Wifi and Update Screens.

Thank you for posting this guide, it got me to unlocking the bootloader on my TA-1004 after I received the described "Device not support" error.
I enabled "OEM unlocking" before downgrading my firmware and the option was grayed out for me afterwards. However the bootloader unlock still worked correctly other than being forced to us a Mac as none of my windows machines would show the device in fastboot mode.

ma401 said:
Thank you for posting this guide, it got me to unlocking the bootloader on my TA-1004 after I received the described "Device not support" error.
I enabled "OEM unlocking" before downgrading my firmware and the option was grayed out for me afterwards. However the bootloader unlock still worked correctly other than being forced to us a Mac as none of my windows machines would show the device in fastboot mode.
Click to expand...
Click to collapse
If only Nokia 8 had support for custom roms. Im stuck on the december security patch of Pie because it has a prerooted boot img posted somewhere on this forum. Ot would be fun to play around with a google-free custom rom like lineageOS. But sadly devs dont seem to give a damn about the phone

MDV106 said:
If only Nokia 8 had support for custom roms. Im stuck on the december security patch of Pie because it has a prerooted boot img posted somewhere on this forum. Ot would be fun to play around with a google-free custom rom like lineageOS. But sadly devs dont seem to give a damn about the phone
Click to expand...
Click to collapse
I think we can thank HMD for that by making unlocking the bootloader so difficult. I only ended up buying the Nokia 8 because I got it for such a good deal ($220 CAD) and needed a temporary phone to tide me over until I can get something better. I feel sorry for anyone who paid full price for this phone and I don't blame developers for moving to something more accessible.

S5Guy said:
If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3
Click to expand...
Click to collapse
Hello i too tried unlocking my nokia 8 but the laptop doesnt recognise my phone in fastboot Mode.i need help i installed all drivers but the same problem arises

shivaji namburu said:
Hello i too tried unlocking my nokia 8 but the laptop doesnt recognise my phone in fastboot Mode.i need help i installed all drivers but the same problem arises
Click to expand...
Click to collapse
try fastboot -i 0x2e04 [Your_Command]

sumitinhome said:
try fastboot -i 0x2e04 [Your_Command]
Click to expand...
Click to collapse
Actually even pc doesnt detect the device and it doesn't show in my pc section
---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------
sumitinhome said:
try fastboot -i 0x2e04 [Your_Command]
Click to expand...
Click to collapse
What is that i didn't get it will it work.....?
If possible put the command clearly ....to understand

shivaji namburu said:
Actually even pc doesnt detect the device and it doesn't show in my pc section
---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------
What is that i didn't get it will it work.....?
If possible put the command clearly ....to understand
Click to expand...
Click to collapse
If pc is not detecting the phone the its driver problem. try to install proper drivers.

sumitinhome said:
If pc is not detecting the phone the its driver problem. try to install proper drivers.
Click to expand...
Click to collapse
I mean it detects when the phone is in nornal mode but when mobile is booted into fastboot mode it doesn't detect

shivaji namburu said:
I mean it detects when the phone is in nornal mode but when mobile is booted into fastboot mode it doesn't detect
Click to expand...
Click to collapse
Yes i understood, make sure you are using latest adb drivers.
More on it. Make sure you have USB debugging on from Developers options. Also make sure oem unlocking option is on.
1 - Connect your phone to pc while powered on.
2 - From adb folder open command prompt and type adb devices (If your device is detected in adb mode while powered on)
2.1 - if not detected in adb devices.. then go to developer settings and revoke USB debugging authorizations. then again repeat the above process in point no. 2.
3 - if detected now then type adb reboot bootloader, let it reboot in download mode.
4. then type 'fastboot flash unlock [your unlock key]' if this doesnt work then try 'fastboot -i 0x2e04 flash unlock [unlock key]'
5. after that either 'fastboot oem unlock' or 'fastboot -i 0x2e04 oem unlock'
See if this works.

Struck on Nokia Logo
S5Guy said:
If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3
Click to expand...
Click to collapse
after this my phone struck on nokia logo, please help,,,,
i'm training to recovery mode \ download mode but not working both

gvreddy said:
after this my phone struck on nokia logo, please help,,,,
i'm training to recovery mode \ download mode but not working both
Click to expand...
Click to collapse
Factory reset by wiping cache and data via recovery. Start over and try again.

Botched Graphene install on Pixel 3A - need help restoring default settings

Hello,
I am hoping for some advice on how to revert my phone back to its original "factory settings" after a botched instal of GrapheneOS onto an unlocked Google Pixel 3A.
I got to the point at which I needed to Flash the Graphene Rom to the phone, but rather than installing, I received a message from Smart Screen MS edge asking if I really wanted to run as it's protecting my PC - I clicked run anyway and a blank command line window appeared for a second. Now my pc doesn't seem to be recognising the pixel 3A when I type ADB devices. My phone is currently in Fastboot mode "unlocked" and I'm hoping for some advice on what to do next. I'm total noob, so unsure how to start the process over (return the phone to it's previous state) before, maybe, trying again on a different PC.
I have since turned on my phone and Android 11 is still present and seems to work fine (however it gives me a warning on startup that the bootloader is unlocked.
Any help would be very much appreciated - thank you in advance.

Is all what happened that your phone now:
complains about "'maybe not safe bootloader unlocked".
This is just what android does when the bootloader is unlocked.
This you did before trying the flash.
If you want the warning gone simply lock it again.
However if you into the market for graphene OS then I would recomend: along with following their guide to a t to also read up here on xda about the general rooting unlocking thing a bit more so you get the overall process a bit better perhaps next time.
About windows. There are so many tools out there to help ya with disabling some of it's spying, turning off smartscreen, auto - uploads of all your data to M$oft, etc etc.
It's not hard to find.

Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.

Ignore

deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go

Tamsta_T said:
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go
Click to expand...
Click to collapse
Hey there,
This is brilliant - thanks for all the advice. Having this support is helping me gain the confidence to learn more, research more, and then give it a go.
All the best.

deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
thats if I am not wrongly remembering my experience:
because now your phone is in fastboot mode thus it won't show up with that command anymore.
Try: 'fastboot devices'
I imagine you put it into fastboot through: 'reboot fastboot' when you where in adb?
When in fastboot you can go on and flash the recovery and such.
Are you still in need of help here?

Hey, thanks for the clarification - been away and so haven't implemented all suggestions, yet.
I typed "adb reboot booloader" which I assumed put it into fastboot mode and then unlocked it using "fastboot flashing unlock".
I tried fastboot devices but the PC still doesn't see the phone. I'm going to try the update usb driver suggested by Tamsta_T and see how it goes.
Thanks for your help.