Hi
i wasn't able to make this a thread but thought i would try and give a hand to people who accidentally wipe their razer phone of any OS whilst trying to root
If you have got no OS you will need to switch your phone into (download mode) for the following operations.
To get to download mode, turn off device and hold volume down button and download mode will load with razer symbol, (download mode will be stated in top left corner)
You will need to have ADB and Fastboot pre installed on your PC/Mac before starting this procedure
You will need a USB C cable to connect your device to your PC/Mac
Your BOOTLOADER should be unlocked, if you have wiped your phone of an OS, you most likely have it unlocked already as you were trying to Root your phone!
You will need to obtain the Stock firmware from the Razer website, getting it from the Razer website will stop you from accidentally downloading a corrupt file.
Once file is downloaded extract the .zip file and locate the (Windows) flash_all.bat, (mac) flash_all.sh
Open the flash_all.sh or flash_all.bat as a text format, from there you can see what files will be loaded to your razor phone.
You will need to delete the end of each command line for example: ${FASTBOOT_CMD} flash partition:0 gpt_both0.bin (this is the command line in original text format), Now delete the end of the command line (gpt_both0.bin), your new line should read ${FASTBOOT_CMD} flash partition:0, after drag and drop the file (gpt_both0.bin) from the original folder into the text editor, this will apply the address for the file and update your command line.
Once you have edited each following command line, with what it states at the end of each command line, save the document to original folder.
Open up terminal or CMD (CMD run as administrator), once loaded type the command line; adb
This will allow the ADB to run in the terminal
Now check that your device is connected to your PC/Mac, type the command line; adb devices
This should show you a ID number for your phone and what state it is in.
Now drag and drop the file flash_all.sh (mac) or flash_all.bat (windows), this needs to be your edited version, from you original folder and drop into your terminal or CMD page. Now hit enter
This will start the process to re-loading your stock firmware onto your phone.
Wait until the end of the process is complete, after your phone should reboot and load to the phones guide of setting up a new phone
If this has not worked then try the process again or check that your bootloader is unlocked and try again.
After all is good you can re-lock your bootloader by putting your device into (download mode) and typing the command line; fastboot flashing lock
When the bootloader page loads click on yes by using the volume buttons and power button for accepting
Now your device should reboot to working order with stock firmware!
This is my first time trying this so if i have missed stuff out please forgive me and let me know and i will update.
I hope this helps you into getting your razer phone back to life
You. Are. A. Life. Saver.
Isn't it easier to just type "flash_all.bat" (without quotes) directly???
Just use cd.. to go back to a previous folder or type the name of the folder that you want to access directly on CMD, for example, asuming that your OS folder is directly placed on "C" and the name of the folder is RAZER, just type:
cd..
cd..
cd RAZER
flash_all.bat
All the instructions can be found directly on the official Razer site: https://developer.razer.com/razer-p...885.617132994.1525376764-984967671.1524497635
Thank you tho.
Jonlines94 said:
Hi
i wasn't able to make this a thread but thought i would try and give a hand to people who accidentally wipe their razer phone of any OS whilst trying to root
If you have got no OS you will need to switch your phone into (download mode) for the following operations.
To get to download mode, turn off device and hold volume down button and download mode will load with razer symbol, (download mode will be stated in top left corner)
You will need to have ADB and Fastboot pre installed on your PC/Mac before starting this procedure
You will need a USB C cable to connect your device to your PC/Mac
Your BOOTLOADER should be unlocked, if you have wiped your phone of an OS, you most likely have it unlocked already as you were trying to Root your phone!
You will need to obtain the Stock firmware from the Razer website, getting it from the Razer website will stop you from accidentally downloading a corrupt file.
Once file is downloaded extract the .zip file and locate the (Windows) flash_all.bat, (mac) flash_all.sh
Open the flash_all.sh or flash_all.bat as a text format, from there you can see what files will be loaded to your razor phone.
You will need to delete the end of each command line for example: ${FASTBOOT_CMD} flash partition:0 gpt_both0.bin (this is the command line in original text format), Now delete the end of the command line (gpt_both0.bin), your new line should read ${FASTBOOT_CMD} flash partition:0, after drag and drop the file (gpt_both0.bin) from the original folder into the text editor, this will apply the address for the file and update your command line.
Once you have edited each following command line, with what it states at the end of each command line, save the document to original folder.
Open up terminal or CMD (CMD run as administrator), once loaded type the command line; adb
This will allow the ADB to run in the terminal
Now check that your device is connected to your PC/Mac, type the command line; adb devices
This should show you a ID number for your phone and what state it is in.
Now drag and drop the file flash_all.sh (mac) or flash_all.bat (windows), this needs to be your edited version, from you original folder and drop into your terminal or CMD page. Now hit enter
This will start the process to re-loading your stock firmware onto your phone.
Wait until the end of the process is complete, after your phone should reboot and load to the phones guide of setting up a new phone
If this has not worked then try the process again or check that your bootloader is unlocked and try again.
After all is good you can re-lock your bootloader by putting your device into (download mode) and typing the command line; fastboot flashing lock
When the bootloader page loads click on yes by using the volume buttons and power button for accepting
Now your device should reboot to working order with stock firmware!
This is my first time trying this so if i have missed stuff out please forgive me and let me know and i will update.
I hope this helps you into getting your razer phone back to life
Click to expand...
Click to collapse
my phone is just stuck in the green and white loading screen and it wont get past anything i can do
Djcall11 said:
my phone is just stuck in the green and white loading screen and it wont get past anything i can do
Click to expand...
Click to collapse
Hi have you managed to find a way to resolve your issue, i have been on the forum for a long while so sorry for late replies
Jonlines94 said:
Hi have you managed to find a way to resolve your issue, i have been on the forum for a long while so sorry for late replies
Click to expand...
Click to collapse
you have to reinstall the image add me on discord #7136
My guy!
You saved another Razer Phone with this post, just thought I should let ya know. much appreciated, man!
Doesn't work
I think this is really good and all, but it doesn't work. You suggest removing the extensions such as the gpt_both0.bin and to drag the file itself into the text editor. This doesn't work at all, all it does is open the gtp_both0.bin as a text file as opposed to doing whatever it was you were doing. Am I doing something wrong?
I've tried launching the bat file with all the img and bin files in the ADB folder so that I can just double press the flash_all.bat file, but the response to that is that in the CMD it says that over majority of the things have failed with the message "FAILED (remote: 'Flashing is not allowed for Critical Partitions')".
The only ones that do work are the flash system_b system_other.img, yet system_a system.img don't.
People says that if u want to enter Download mode just hold voulme down and plug the cable , but mine goes direct to bootloader page, phone is not working , brick and says your phone is corrupt
Yahyoo said:
People says that if u want to enter Download mode just hold voulme down and plug the cable , but mine goes direct to bootloader page, phone is not working , brick and says your phone is corrupt
Click to expand...
Click to collapse
HEllo I have a problem I install the firmware from razer to fix my phone but it says the file is corrupted
Related
Hello everyone i am having troubles installing adb on my laptop and i need it to flash a splash screen on my mytouch slide so it can match the rom i have made for it. I installed the adnroid sdk to where it needs to be by downloading adb for dummies lol. Except when i open cmd and run adb it says its not an internal batch orrecognized file or whatever but when i type adb.exe on command prompt it shows everything about adb. So can anyone please help me thanks.
Nerd019 said:
Hello everyone i am having troubles installing adb on my laptop and i need it to flash a splash screen on my mytouch slide so it can match the rom i have made for it. I installed the adnroid sdk to where it needs to be by downloading adb for dummies lol. Except when i open cmd and run adb it says its not an internal batch orrecognized file or whatever but when i type adb.exe on command prompt it shows everything about adb. So can anyone please help me thanks.
Click to expand...
Click to collapse
I'm trying to piece together information here. ADB for me is in my C:\, so when opening CMD prompt, I first type "cd/" (without quotes) then "cd AndroidSDK/tools". To get a list of ADB's commands, type "adb help". Maybe you're not using the proper syntax. I base this off the statement you made that when you type adb.exe it shows the adb commands, and command syntax usage.
Also note that changing your splash screen you must first S-OFF your phone. Here's a guide on how to do so
http://forum.xda-developers.com/showthread.php?t=798168
That's the tricky part though, easy part is flashing your custom boot image.
File you will need: View attachment Boot_images.zip
Once you have the 320x480 boot image you want, open "CreateG1Splash", select your boot image, and convert it with this program. Once converted the new file will show in the same folder as CreateG1Splash, named mysplash.rgb565. Move this file to your ADB tools folder. Open CMD prompt and point CMD prompt to your AndroidSDK\tools folder.
Then boot phone into bootloader, then select fastboot. Plug the phone to CPU via USB, and type, "fastboot flash splash1 mysplash.rgb565". Reboot phone to see change.
Hope this helps!
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
neccoguy21 said:
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Know-Fear said:
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Click to expand...
Click to collapse
This is a very helpful way of doing things, but a little too long winded for CWM. But I'm thankful for you taking your time to respond and I'm happy to have this guide handy.
gpfnzl said:
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
Click to expand...
Click to collapse
A similar strategy to know-fear's, but different. Again, thank you very much for your help, but it's not the way I'll handle this one.
ÜBER™ said:
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
Click to expand...
Click to collapse
This was what I was looking for. Thank you so much for your time and help!
Sent from my Galaxy Nexus using xda app-developers app
Long winded perhaps. But it's the same thing for most phones running android. So in essence, once you learn it, you know it for good. I've been using the same method since back in the G-1 days. And honestly, those steps I listed take about 15 seconds to complete. It's just good to be thorough.
I used Team win Recovery Project to wipe my phone Galaxy Nexus, and now when I plug the phone in to the lappy it doesn't show the sd card. Freaking out here cause I can't copy over a zip file to flash a ROM... please help...
The GNEX doesn't have an actual sdcard, so when you wiped the phone i'm guessing you wiped the virtual sd card.
You will have to adb push a rom to your phone.
One the top of the first Q&A page jubakuba has a guide that has a panic section in it.
The guide also shows how to install adb/fastboot and gives you the commands.
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
xskordeal said:
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
Click to expand...
Click to collapse
sorry, complete DOLT here. Where would I input the command?
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
How to get to a MS-DOS prompt or Windows command line
TheDodgey said:
sorry, complete DOLT here. Where would I input the command?
Click to expand...
Click to collapse
Click Start.
Click Run.
Type cmd or command and press enter.
gpfnzl said:
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
Click to expand...
Click to collapse
ok, following your instructions, and the instructions of the link, I have install ADB and can use cmd, however when I type adb shell, I get an error returning "device not found"
I see a lot of threads stating to make sure usb debugging is on, it was before I wiped the phone, but obviously I cant get to any settings at the moment.
on the verge of crying now, and noone likes to see a grown man cry
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
LOL
Normally if you can't see your device listed you haven't installed the drivers correctly.(or the correct drivers)
Also you have to open a command prompt window in the same folder as fastboot.exe and adb.exe
To do this in Windows 7:
Click the windows start button (bottom left hand corner)
In the search bar at the bottom type: cmd
At the top of the search list you will see the program cmd.exe right click and copy it.
Paste it into the same folder that has fastboot.exe and adb.exe
Now you can open the cmd window and type the command:
adb devices
Hit ENTER and if you have installed drivers correctly, the serial number of your phone will be listed.
If not, uninstall the drivers, download a new set of drivers from jubakuba or efrants guide and reinstall.
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
TheDodgey said:
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
Click to expand...
Click to collapse
didn't need to change the name of the rom zip. Just needed to type the full name of the .zip file.
Good to see it worked, and the tears have stopped
Hello,
if is one here to help me i wil give him thousands bottles with beers.
My s3 is stuck in boot loop, i cant to pass samsung logo, i cant to go in cwm or download mode. I have tried to connect on my pc via usb cable but nothing is happening, i have all drivers installed but odin cant to recognized my phone, i think debugging mode is off. When the phone is off and i connect the charger he show me battery what he trying to get power but is not green.
I attach two photos to be more suggestive.
How can to pass this logo to go in cwm or to make this phone to be recognized by odin?
Thank you for reading me and for your answers.
regards,
florin
DobreaFlorin said:
Hello,
if is one here to help me i wil give him thousands bottles with beers.
My s3 is stuck in boot loop, i cant to pass samsung logo, i cant to go in cwm or download mode. I have tried to connect on my pc via usb cable but nothing is happening, i have all drivers installed but odin cant to recognized my phone, i think debugging mode is off. When the phone is off and i connect the charger he show me battery what he trying to get power but is not green.
I attach two photos to be more suggestive.
How can to pass this logo to go in cwm or to make this phone to be recognized by odin?
Thank you for reading me and for your answers.
regards,
florin
Click to expand...
Click to collapse
First question.. Do you have the I9300 (is the international version of the S3) Sprint version is SPH-L710.. If you have the 710 and flashed I9300 stuff.. you probably bricked your phone. If you DO have the I9300 version, I would pop over to that section of the forums and ask there... Here's the I9300 Section. http://forum.xda-developers.com/forumdisplay.php?f=1563
They are not compatible sadly due to different hardware, so flashing something from here will break your I9300.
Ive been where you are about three times. What i have had to do is plug my phone into the computer and have terminal or cmd prompt open.
I have to navigate to a folder that has ADB in it.
I start the bootloop on the phone and when i see the samsung logo boot up i execute the command
./adb reboot recovery
in windows i think you have to go
adb
reboot recovery
not sure though because i currently dont have a windows machine at my disposal. But you have to time this right. There is a few seconds in the bootloop where you have the ability to adb into the phone and force it to reboot into recovery this way you can flush the bad rom/kernel you accidentally flashed.
Hope this helps.
Thank you for your helpp, quick answers, you are the best form internet. All the time i get solve here in xda.
Solved, my battery it was under 25% and he cant to pass on download mode, i charged to 100% and now i can to flash what i want in download mode.
Thank you again for your quick answers.
Regards,
Florin
Hamspiced said:
Ive been where you are about three times. What i have had to do is plug my phone into the computer and have terminal or cmd prompt open.
I have to navigate to a folder that has ADB in it.
I start the bootloop on the phone and when i see the samsung logo boot up i execute the command
./adb reboot recovery
in windows i think you have to go
adb
reboot recovery
not sure though because i currently dont have a windows machine at my disposal. But you have to time this right. There is a few seconds in the bootloop where you have the ability to adb into the phone and force it to reboot into recovery this way you can flush the bad rom/kernel you accidentally flashed.
Hope this helps.
Click to expand...
Click to collapse
hello can you please be specific how to go in adb folder can you please assist with if some kind of tutorial is there I have the same problem and I havent slept from last two nights trying to solve it please help me
rishidgr8143 said:
hello can you please be specific how to go in adb folder can you please assist with if some kind of tutorial is there I have the same problem and I havent slept from last two nights trying to solve it please help me
Click to expand...
Click to collapse
What S3 do you have and exactly what is wrong with it?
Have a great day!
edfunkycold said:
What S3 do you have and exactly what is wrong with it?
Have a great day!
Click to expand...
Click to collapse
I have GT-I9305
i installed cm 10.2 few days ago
it restarted suddenly and keeps restarting again and again
I cant enter into recovery mode nor in download mode
I some how manage to enter into recovery mode it starts again and give no time wipe factory data same is with download mode
please help me
rishidgr8143 said:
I have GT-I9305
i installed cm 10.2 few days ago
it restarted suddenly and keeps restarting again and again
I cant enter into recovery mode nor in download mode
I some how manage to enter into recovery mode it starts again and give no time wipe factory data same is with download mode
please help me
Click to expand...
Click to collapse
Ok your in the wrong section, this is Sprint d2spr. So you should be posting in the forum for your device.
But most likely what you have is SDS sudden death syndrome. Which means your power button has failed. Very common on the S3 devices. Try jiggling the power button maybe blowing some compressed air into the power button area. See if it will dislodge. It is a known defect.
Have a great day!
edfunkycold said:
Ok your in the wrong section, this is Sprint d2spr. So you should be posting in the forum for your device.
But most likely what you have is SDS sudden death syndrome. Which means your power button has failed. Very common on the S3 devices. Try jiggling the power button maybe blowing some compressed air into the power button area. See if it will dislodge. It is a known defect.
Have a great day!
Click to expand...
Click to collapse
Thanks I will try doing that. I hope this works
Stuck at splash screen.
Help! I have a D2SPR and was flashing my nightly for 9/6/13 CM10.2... and now I can't get past the splash screen. What, if anything, can I do to get recovery to boot? (yes, it was a dirty flash(
Power button + volume up + home button at same time should get you into recovery.
Have a great day!
same issue
I have the Sprint SPH-L710 and flashed a Cyanogenmod nightly this morning. At this point, the phone will not boot. I can get to the Samsung screen but there it hangs. I can also get the phone connected to a computer and Odin sees it but I can't do much else with it. Any thoughts on how to force it into recovery from Odin? Any help would be much appreciated.
midkemiapug said:
I have the Sprint SPH-L710 and flashed a Cyanogenmod nightly this morning. At this point, the phone will not boot. I can get to the Samsung screen but there it hangs. I can also get the phone connected to a computer and Odin sees it but I can't do much else with it. Any thoughts on how to force it into recovery from Odin? Any help would be much appreciated.
Click to expand...
Click to collapse
I was able to get into recovery mode after flashing the CWM recovery mod from here: http://forum.xda-developers.com/showthread.php?t=2391616. I also took a look at the Cyanogenmod forum here: http://forum.cyanogenmod.com/topic/77958-20130906-stuck-on-boot-screen-dont-install/.
johnbistricky said:
Help! I have a D2SPR and was flashing my nightly for 9/6/13 CM10.2... and now I can't get past the splash screen. What, if anything, can I do to get recovery to boot? (yes, it was a dirty flash(
Click to expand...
Click to collapse
Pull battery then do the recovery button combo. It is a a known issue that that nightly doesn't boot. You could just dirty flash another nightly that does work. May break some things though.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
@rishidgb
what ive had to do in the past to resolve these issues. Ill Copy/Paste the instructions i have used to Install ADB on my past computers but ill also throw links for the origionals at the bottom of the post.
1. Verify Battery is at least 50% charged. I usually do this by turning the phone off and plugging it into the charger, you should be able to see the battery charging up.
2. Install ADB on your computer. I have a mac, and this was kind of a pain in the ass to do at first but ill explain.
Mac-
1. Download the latest Android SDK from Google: Android SDK - http://developer.android.com/sdk/index.html
2. Extract the ZIP file to your desired location
3. To get ADB, you need to install the SDK: Installing the SDK - http://developer.android.com/sdk/installing/index.html
If you are not a developer and not planning to develop, then just download the following zip file containing only the ADB tool and
proceed with the tutorial: ADB - http://esausilva.com/wp-content/plu...silva.com/misc/android/platform-tools-osx.zip
Create an environment variable (Optional) **This is good because once you create the variable you dont have to navigate to the ADB folder every time to use it.
1. Open Terminal
2. Type cd ~ this will take you to your home directory
3. Type touch .profile this will create a hidden file named profile
4. Type open -e .profile this will open the file you just created in TextEdit
In the file, type export PATH=${PATH}:/pathToTheAndroidSdkFolder/android-sdk-mac_86/platform-tools
Save file, close TextEdit, Quit Terminal, and Relaunch Terminal
NOTE: By creating an environment variable you won’t need to cd to the Android/tools folder every time you want to run ADB
You are good to go, type in terminal adb devices, this should give you a serial number, which corresponds to your phone. Looks something like this:
List of devices attached
HT99PHF02521 device
NOTE: If you did not create an environment variable, then cd to the AndroidSDK/platform-tools folder, then type ./adb devices
Also make sure you have your phone plugged in and have USB Debugging turned on (Settings > Applications > Development)
In Android 4.2.x and up Developer Options is hidden, to make it visible, do the following
Tap seven times in Build Number: Settings > About Phone > Build Number
You will get a message saying you have enabled Developer Options or something like that, go back to Settings and you will see Developer Options in there.
PC-
Step 1: Head over to this link to download the latest version of Android SDK. http://developer.android.com/sdk/index.html
Step 2: Extract the contents of the downloaded file to your hard drive. Within the unzipped “sdk” folder, you’ll find another folder labeled ‘platform-tools’. Since we’re interested in only ADB and Fastboot, this is the one that we’re looking for.
Step 3: Move the platform-tools folder to a convenient location on your PC. The root of C: drive is usually a good idea. I also recommend renaming the folder to something easier, like C:\Android-adb.
By this point, ADB is essentially set up, but to use it, you’ll first need to navigate your command prompt window to this Android-adb folder, and then run all ADB commands inside it. Since it’s too much hassle for most users, we’ll add this location to Windows’ System Path Variable, so you can run ADB commands from anywhere.
Step 4: Right-click the Computer icon on your desktop, and go to Properties.
Step 5: Under System Properties, go to the Advanced tab, and click Environment Variables.
Step 6: The system variables are contained within the lower pane. Locate “Path” here, highlight it, and click the Edit button.
Step 7: There will already be a string of locations here; navigate to the very end, and add the following text (assuming that you have chosen C:\Android-adb as the folder; otherwise, enter whatever path you’ve located adb at):
;C:\Android-adb
Click OK, finally.
Your ADB folder is now configured, and you can run both ADB and Fastboot commands from anywhere in command prompt. To verify, connect your Android device to PC with USB Debugging enabled, launch a command prompt window, and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed.
Mac Instructions
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
Pc Instructions
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Now that ADB is installed. If you find yourself in a Bootloop, OR you find yourself in a situation where it wont pass by the boot animation, open up terminal or command prompt. Then type Adb Devices, it should recognize your device and list the serial. And from there you can use the command:
Adb Reboot Recovery
From there you can wipe/Factory Restore and then Flash a new rom.
If you cannot reboot recovery but ADB still sees your phone. You can use command ADB shell to open a linux command prompt through your phone to push and pull files. Ive done this to push roms when the phone wouldnt mount properly.
I know this isnt "THAT" thorough, however ADB has litterally saved my ass a BUNCH of times. Id reccomend setting it up if you flash frequently.
Sorry it took me a couple days to respond, i am not on XDA as much as i used to be.
RE:
Thanks for documenting this.
So any solutions/ideas to people who can't get our computer's to recognize our device? Unfortunately, that's the position I'm in
Noob again. So I am rooted and I'm currently on build NDE63X on my Verizon 128 gb XL. If i understood the instructions correctly, I have to go back to stock before I can put TWRP on the phone. I know I get the factory images here.
https://developers.google.com/android/images
Do I get the NDE63P image for the phone since that was what was on the phone before I sideloaded the OTA for my current version which is NDE63X or do I just need to download the full image for NDE63X?
Can someone also list the steps needed to accomplish getting phone back to stock? I read Google's instructions and I was a little confused. I understand that I will lose root but should be able to root after installing TWRP since it looks like Chainfire updated the root method for those using TWRP.
Thanks.
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it. ?
Sent from my Pixel XL
Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
Thank you. Gonna attempt it this weekend.
Deleted
Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl
Veid71 said:
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl
Click to expand...
Click to collapse
https://developers.google.com/android/images
Sent from my Pixel XL
My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!
chipslate said:
My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!
Click to expand...
Click to collapse
if you are executing the commands, you are in fastboot, not adb.
try fastboot devices
if it doesnt return anything, your computer is not seeing the device.
you will need the computer to see the device in fastboot before you can proceed.
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
first thing to try is to go into fastboot, then unplug the cable, and then plug it back in.
if it is still not recognized, then its either an outdated adb/fastboot issue, or a driver issue (if you are using windows, if not there may be other possibilities).
chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
When it finds your phone does it say unauthorized or authorized?
See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?
chipslate said:
See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?
Click to expand...
Click to collapse
What happens now when you attempt the next command?
Edit: So after running adb devices, you should be running adb reboot bootloader command next I believe.
Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Also, I have the phone in MTP File Transfer mode and USB Debugging enabled.
chipslate said:
Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Click to expand...
Click to collapse
You should now use the flash-all command but this is going wipe all of your data.
I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.
chipslate said:
I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.
Click to expand...
Click to collapse
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.
magestic1995 said:
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.
Click to expand...
Click to collapse
It finally worked!!! Thanks again for your help and going back and forth. I finally installed Android Studio and it inserted the ADB drivers at the top of Device manager. Worked like a charm then. Finally, Android 7.1.1 and unlocked bootloader... Bring it on, world!
Congrats! I've only used Android Studio for all this stuff since Im a developer. Congrats on getting it all figured out!
i have been trying to take my pixel xl back to stock but the flash-all.bat script hangs on the part where it should flash the system img zip. it says the file size is to large