Develop Bugs

[Q] How to factory reset with broken screen

I'd like to wipe the data from my Galaxy Nexus to send it for repair, but since the screen is blank/broken, I have no feedback to my adb commands, and no way to press on screen prompts. The device is stock, unrooted. Doing adb shell/wipe data gives me no permission, so I think I need to be in bootloader or recovery.
Does any guru here have the steps required to wipe data/factory reset in such a screenless/touchless mode?

you could root it then wipe it using adb like you said.

Just in case someone needs this here goes:
You do NOT need to be rooted. Just install ADB and fastboot.
Turn on your device in bootloader mode, hold volume up and volume down and power button simultaniously, until you feel a vibration, then let go the buttons.
Connect USB cable to PC.
Run ADB as root, type: adb root
Check you are in in fastboot mode and connected, type: fastboot-linux devices
This should show a long number
Finally, type: fastboot-linux -w
And just to be sure type: fastboot-linux erase data.img
fastboot-linux reboot

Or you could fastboot flash the stock images that are provided by google. Fastest method, even more since zyo made a one-click batch file for that.
If you want to make sure everything is wiped correctly, you could boot the phone and connect it with a screen via MHL.
Sent from my Galaxy Nexus using XDA App

tamarian said:
Just in case someone needs this here goes:
You do NOT need to be rooted. Just install ADB and fastboot.
Turn on your device in bootloader mode, hold volume up and volume down and power button simultaniously, until you feel a vibration, then let go the buttons.
Connect USB cable to PC.
Run ADB as root, type: adb root
Check you are in in fastboot mode and connected, type: fastboot-linux devices
This should show a long number
Finally, type: fastboot-linux -w
And just to be sure type: fastboot-linux erase data.img
fastboot-linux reboot
Click to expand...
Click to collapse
ok. so putting the device in bootloader mode is easy. but trying to understand what you mean with "run adb as root" ??
this what i did, i run cmd and see C:\user\name>
typing C:\user\name>c:\adb (which is where my adb folder is located)
only gives me this message:
'c:\adb' is not a recognized as an internal or external command, operable program or batch file.
can some1 give a step to step guide or give a me link that tells me how to do this?

taogenix said:
ok. so putting the device in bootloader mode is easy. but trying to understand what you mean with "run adb as root" ??
this what i did, i run cmd and see C:\user\name>
typing C:\user\name>c:\adb (which is where my adb folder is located)
only gives me this message:
'c:\adb' is not a recognized as an internal or external command, operable program or batch file.
can some1 give a step to step guide or give a me link that tells me how to do this?
Click to expand...
Click to collapse
Type: cd c:\android-sdk\platform-tools to be able to get in the tools.
c:\android-sdk is the location where i have my sdk tools, if yours is different type that instead. Place the sdk directly on the c drive, not in a (sub) folder.
Than type: adb reboot-bootloader and you`re in fastboot mode.
---------- Post added at 09:57 AM ---------- Previous post was at 09:43 AM ----------
I f you`re not familiar with adb/fastboot i advice you to do this:
Install GNex Toolkit from here http://forum.xda-developers.com/showthread.php?t=1614827, Flash a google image from here https://developers.google.com/android/nexus/images#yakjuimm76i.
Install the toolkit, do option 1 (drivers), put the downloaded and the not to be extracted google image (.tgz file) here C:\Galaxy Nexus ToolKit\put_google_factory_image_here ,put your phone in fastboot mode and do option 8. After that lock the bootloader.

gee2012 said:
Type: cd c:\android-sdk\platform-tools to be able to get in the tools.
c:\android-sdk is the location where i have my sdk tools, if yours is different type that instead. Place the sdk directly on the c drive, not in a (sub) folder.
Than type: adb reboot-bootloader and you`re in fastboot mode.
---------- Post added at 09:57 AM ---------- Previous post was at 09:43 AM ----------
I f you`re not familiar with adb/fastboot i advice you to do this:
Install GNex Toolkit from here http://forum.xda-developers.com/showthread.php?t=1614827, Flash a google image from here https://developers.google.com/android/nexus/images#yakjuimm76i.
Install the toolkit, do option 1 (drivers), put the downloaded and the not to be extracted google image (.tgz file) here C:\Galaxy Nexus ToolKit\put_google_factory_image_here ,put your phone in fastboot mode and do option 8. After that lock the bootloader.
Click to expand...
Click to collapse
ok, i tried the Gnex toolkit and i believe it worked. i can see the serial ID when its in fastboot mode. and i followed all those steps to restore the img.
yesterday i just bought an original samsung mhl adapter. i tried to connect it with my Gnex, plugged in the power cable and tried to connect the hdmi cable both to my pc monitor and my flatscreen tv. nothing works. i tried connecting all the cable first while the phone was off and then turn on the Gnex. still nothing works. no Signal/no Device is being recognized by either monitor.
Is there a way to get this to work, so i can see my Gnex "screen" on any Monitor?

I know this is old but......
So I am trying to do what the OP is trying to do, just to refresh, I am attempting a broken screen factory restore. I am pretty new to all of this, but I have been reading for a little while now and attempted to do this a few times. I am having trouble with Gnex ToolKit recognizing my device. I installed all of the drivers, windows said they installed and everything seems to be fine with those. My device is still not showing up at the top.
My question is, all of the instructions above require that the phone was, before the screen was broken, put into usb debugging mode? Regardless if you boot your phone in Bootloader mode? As I cannot see my device at all in adb.

fastboot never start after update to android 6

Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!

Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english

No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.

bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?

krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.

bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.

i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?

bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.

Here is screenshot from minimal adb...
Phone must be in MTP mode.

And here is phone in fastboot

Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.

bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.

Got my bootloader unlocked, trying to boot into TWRP but hit a speedbump?

So I got my bootloader unlocked so obviously fastboot drivers are working, I have the SU zip copied to my internal storage and the IMG file in my Minimal Fastboot folder location....
When I run :
fastboot boot "path to IMG".img
My command prompt just says "waiting for devices" and does nothing?
Do I run this command from while in bootloader mode? Power + Vol down ? When I have it plugged into my PC in this mode and I run "adb devices" it does't find my device? Does that mean I don't have the right drivers installed?
What am I missing here? Damn this phone is complicated.

msmall82 said:
So I got my bootloader unlocked so obviously fastboot drivers are working, I have the SU zip copied to my internal storage and the IMG file in my Minimal Fastboot folder location....
When I run :
fastboot boot "path to IMG".img
My command prompt just says "waiting for devices" and does nothing?
Do I run this command from while in bootloader mode? Power + Vol down ? When I have it plugged into my PC in this mode and I run "adb devices" it does't find my device? Does that mean I don't have the right drivers installed?
What am I missing here? Damn this phone is complicated.
Click to expand...
Click to collapse
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
If you already have TWRP rc1 installed then you just want to boot to recovery and install su2.79sr3
In fastboot type in fastboot devices and if it comes back with your device number your good to go

mac796 said:
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
Click to expand...
Click to collapse
I know the command I want, I'm asking where I run it from? Do i run it while my phone is in Android connected to my PC or do I run the command from fastboot while my phone is in the bootloader mode??? When I have my phone connected normally and run an "adb devices" it doesn't find my phone but obviously it recognizes my phone otherwise it wouldn't have been able to copy dePixel8 and unlock my bootloader.
My question is *where* do I run that command. As I said before, if I run it while my phone is powered up normally and connected to my PC it just says "waiting for devices". If I power my phone up into bootloader mode (power + vol up) my fastboot doesn't see my phone????

mac796 said:
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
If you already have TWRP rc1 installed then you just want to boot to recovery and install su2.79sr3
Click to expand...
Click to collapse
I guess what I am saying is how the heck do I boot into the TWRP IMG ? My bootloader is definitely unlocked, I have SU on my internal storage, I have the IMG in my minimal fastboot folder. I just need to know how the heck to boot into "recovery mode" using the :
fastboot boot "path to".img
If I run that command while my phone is connected normally with USB debugging enabled it just says "waiting for devices"
Am I missing something here...?

[QUOTE.
My question is *where* do I run that command. As I said before, if I run it while my phone is powered up normally and connected to my PC it just says "waiting for devices". If I power my phone up into bootloader mode (power + vol up) my fastboot doesn't see my phone????[/QUOTE]
Run the command with your phone in bootloader mode and your computer in fastboot

msmall82 said:
So I got my bootloader unlocked so obviously fastboot drivers are working, I have the SU zip copied to my internal storage and the IMG file in my Minimal Fastboot folder location....
When I run :
fastboot boot "path to IMG".img
My command prompt just says "waiting for devices" and does nothing?
Do I run this command from while in bootloader mode? Power + Vol down ? When I have it plugged into my PC in this mode and I run "adb devices" it does't find my device? Does that mean I don't have the right drivers installed?
What am I missing here? Damn this phone is complicated.
Click to expand...
Click to collapse
First off get rid of minimal. That is not your current problem, but you will have problems later. It is old, it doesn't know about our partitions or handle their larger size. Get googles
https://developer.android.com/studio/releases/platform-tools.html
Put the TWRP img in the same folder, skip the path
Fastboot BOOT {twrpfilename.img}

mac796 said:
[QUOTE.
My question is *where* do I run that command. As I said before, if I run it while my phone is powered up normally and connected to my PC it just says "waiting for devices". If I power my phone up into bootloader mode (power + vol up) my fastboot doesn't see my phone????
Click to expand...
Click to collapse
Run the command with your phone in bootloader mode and your computer in fastboot[/QUOTE]
You need to follow the steps I gave you. You need su2.79 , and rc1 on your internal storage. Then you need TWRP rc1 boot image on your computer. Put it in your platform tools folder or wherever you got your other firmware. Put phone in bootloader mode, then open a command window where you have TWRP boot image saved , type in fastboot devices, to make sure computer is seeing the phone, then the command should be fastboot boot TWRP.img, then install rc1 off your phone storage, then boot to system once, then boot back to recovery and install su 2.79 sr3

mac796 said:
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
If you already have TWRP rc1 installed then you just want to boot to recovery and install su2.79sr3
In fastboot type in fastboot devices and if it comes back with your device number your good to go
Click to expand...
Click to collapse
OK I figured it out, while the phone is booted into Android you have to actually issue the command to reboot it into the bootloader mode otherwise it won't detect the phone (at least it wouldn't on my PC)
I ran this command from my minimal fastboot folder (shift + right click -> open command prompt)
I then typed this:
adb reboot bootloader
Then once it is rebooted into bootloader mode issue the
fastboot boot .img command
It then rebooted into TWRP, and I was able to flash the SU zip
Sorry for bugging everyone, this phone is a Pain in my....but it's damn fast and damn nice!

Delete
---------- Post added at 06:49 PM ---------- Previous post was at 06:45 PM ----------
Sorry for bugging everyone, this phone is a Pain in my....but it's damn fast and damn nice![/QUOTE]
Good deal. Yea I usually use ADB to put phone in bootloader mode it's faster

TonikJDK said:
First off get rid of minimal. That is not your current problem, but you will have problems later. It is old, it doesn't know about our partitions or handle their larger size. Get googles
https://developer.android.com/studio/releases/platform-tools.html
Put the TWRP img in the same folder, skip the path
Fastboot BOOT {twrpfilename.img}
Click to expand...
Click to collapse
Thanks Tonik, got SU on there and all is right with the world, already installing Ti Backup and root explorer and such.....ahhh so relieved.
Love all of you lol

mac796 said:
Delete
---------- Post added at 06:49 PM ---------- Previous post was at 06:45 PM ----------
Sorry for bugging everyone, this phone is a Pain in my....but it's damn fast and damn nice!
Click to expand...
Click to collapse
Good deal. Yea I usually use ADB to put phone in bootloader mode it's faster[/QUOTE]
Thanks man, I figure other people might run into these problems so I might as well post about them. If I booted directly into the bootloader my PC wouldn't recognize the phone, if I issued the command to reboot it would. Weird...but whatever, I'm unlocked and rooted....
THANK YOU!

Google FRP Woes :(

All, I've been given a WileyFox Swift 1 that hasn't been used for some time and has been factory reset. Google's factory reset protection has enabled and the previous owner can't remember the account the phone was tied to. Is there anyway to bypass FRP on the Swift 1 or is it possible to reflash the ROM or do I chuck it in the bin?
Thanks

pres vol+
conect to usb
download this
use cmd
and comand fastboot erase frp
https://yadi.sk/d/xBz0BlNA38SLnK

Just had to register to say a big thanks and thumbs up for this - tool works flawlessly

Hi, could you please give step by step instructions as I don't know what o do with the extracted file
Thanks!

bighiner said:
pres vol+
conect to usb
download this
use cmd
and comand fastboot erase frp
https://yadi.sk/d/xBz0BlNA38SLnK
Click to expand...
Click to collapse
Thanks, sorted mine. Just a simple fastboot.exe setup and running the command is sufficient. To get the Swift into fastboot mode, from power off hold power+VolUP for 5 seconds. Plug in USB and from command terminal inside the same folder as your fastboot.exe, type the "Fastboot erase FRP" command. Takes 2 seconds to complete! You can then use "Fastboot reboot" to restart your phone if you want to.

New Razer Phone (1) stuck on download mode.

I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything, I haven't even ever been to the home screen. What can I do to fix this?

Get the Google USB Driver and make sure your Razer phone is installed with these drivers
https://developer.android.com/studio/run/win-usb
Get Android SDK Platform Tools for latest ADB and fastboot tool
https://developer.android.com/studio/releases/platform-tools
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...

It says "Waiting for any device" the problem is that it's not recognized by the computer.

Thank you ! Same problem. This is halp! after first run, works. Question, can I block it now? and how please... fastboot flashashing lock ?

Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
Hello. Same problem. ( I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything). It helped me. Now I can block back? fastboot flashashing lock ? Please, sorry my english...

EDIT: The links did not copy paste appropriately. I fixed them now.
These are all posts from various places in this thread:
https://forums.redflagdeals.com/raz...b-1yr-warranty-8gb-64gb-octacore-9-0-2336958/
"Find the driver here:
https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
unzip the files/folder to a location you will remember
Follow the instructions below, point the windows driver update to the .inf file in that folder then driver will install. Make sure you have the latest Android platform tools, the link is also in the PDF below.
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
open a command prompt from within the Android sdk folder while the phone is still in download mode (phone stays and reboots to download mode through each process below making the process fairly easy)
type: fastboot devices
your phone should show up once drivers are installed correctly
type: fastboot flashing unlock
use the phone vol + - and power to select yes
phone should stay in download mode
type: fastboot flashing unlock_critical
use vol + - and power to select yes
phone should stay in download mode
Download the firmware image below or if you want to try the following command type: fastboot set_active a && fastboot reboot
to see if the phone boots, not sure if all the phones have Android installed. One poster below seems to and also seems to have his bootloader unlocked. This won't be the case for everyone. If phone does not boot continue downloading the firmware to install it
https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-6033.zip
unzip all the files and put them in the android sdk folder, from the same command prompt if you're on Windows
type: flash_all.bat
For Mac type: flash_all.sh
Will take a few minutes but firmware will install. These instructions are for RFD members that do not either 1) want the hassle of RMA or 2) take a chance at voiding the warranty (any phone flashing via adb is frowned upon by Razer)"
------------------------------------------------------------
"Yes. Reverse the locking procedure. Put phone back into Download mode (from power off, press and hold Vol up and then plug phone into computer) then issue fastboot commands to lock boatloader starting with critical."
------------------------------------------------------------
"if you have a ryzen pc and getting some error while unlocking... dont plug the phone in at the beginning... type the command when it says [waiting for device] then plug it in ... also dont forget to unlock critical right after"

Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?

365Thanks said:
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?
Click to expand...
Click to collapse
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.

Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...[/QUOTE]
flopticalcube said:
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.
Click to expand...
Click to collapse
after each command you need to disconnect from the computer? fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
I used to enter these commands , the instructions were only after 1
I did not turn off the phone and the question on the screen was only after the first command. I probably entered only 1 command <if it was necessary to disconnect phone? ... thank you for help.

Sudo.
If ur using linux - run it with sudo. always run fastboot with sudo

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot set_active a
error: Device does not support slots