Related
How To Re-Flash Stock Image
Assuming you have ADB and everything setup already....
1. I just did this for practice. I did not need to do it –but I wanted to do it successfully before I “needed” to do it. I thought I would expand a little on the process and make it a little more noob friendly.
2. Getting started.
a. Read through the entire set of instructions first.
b. I am not responsible if you BORK your phone. I BORKED mine using someone else’s instructions and tried to write a very detailed step-by-step to help others out– but it is completely possible I have also made some small error in the instructions.
3. This will completely wipe your phone – including the SD partition – so transfer any files you need before you do this.
4. This will not re-lock your bootloader. It will remain unlocked.
5. Syntax (spelling, spaces, periods, dashes, CAPITOL, or lower case) matters. There were some spelling errors and file extensions left off the commands – and that will not work.
6.I used the file…
mysid-icl53f-factory-65895fa8.tgz
…which is 4.0.2 for the cdma/lte galaxy nexus [code name = toro/mysid]. The file is located here...
http://www.google.co...NiI9yTxKdUyW1tA
7. Unzip the file (I used 7.zip to do this).
Then you will have a .tar file…
mysid-icl53f-factory-65895fa8.tar
8. Unzip that file and you should end up with a folder…
mysid-icl53f
Inside that folder you will have five files…
i. bootloader-toro-primekk15.img
ii. flash-all.sh
iii. radio-cdma-toro-i515.ek05.img
iv. radio-toro-i515.ek02.img
v. image-mysid-icl53f.zip
Do not unzip “image-mysid-icl53f.zip”
9. Go ahead and copy and paste all these files to your directory…
/android/platform-tools
(or whatever directory you work from. You do not need the “flash-all.sh” so you do not have to copy it).
10. Open the Command Prompt in the directory where you have placed the necessary files by navigating to the directory, pressing shift, and then right mouse click (normally “C: /android/tools” or C: /android/platform-tools). This will bring up the dialogue box and you can select “open a command window here”.
11. Then enter the command…
adb devices
[…this should return your serial number…]
12. enter the command…
adb reboot-bootloader
[wait for bootloader – you should here 2 alert sounds – not just 1]
13. enter the command…
fastboot flash bootloader bootloader-toro-primekk15.img
14. enter the command…
fastboot reboot-bootloader
[wait]
15. enter the command…
fastboot flash radio radio-toro-i515.ek02.img
16. enter the command…
fastboot reboot-bootloader
[wait]
17. enter the command…
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
18. enter the command…
fastboot reboot-bootloader
19. enter the command…
fastboot -w update image-mysid-icl53f.zip
20. So you know, steps 17 (flashing the cdma radio) and step 19 (flashing the update image) took longer than the rest so don't freak out - just be patient. If you did the steps in the proper order after entering the last command your phone should reboot on its own and be completely “fresh”. If you made mistakes (like I did the first time) and flashed the radios out of order (like I did) or did not wait long enough for an “Okay” dialogue (like I did) then when you reboot you will have no signal and no phone number and you will have to go through the process again and do it right (like I did).
Hope this helps someone.
Credit goes to JW at that other site for the fastboot commands. I just added detail for the write up.
Great guide, but what if the serial number doesn't show up?
Thank you for the excellent walkthrough. I am following it, but when I enter "adb devices" at the command prompt I receive "list of devices attached" but no serial number. Also, my Nexus displays: "Fastboot Command Read Error -2147483647". I did a battery pull after getting stuck in a bootloop, and am trying to recover. I can unlock and relock the bootloader, but that is the only command that is working.
Ominous39061 said:
Thank you for the excellent walkthrough. I am following it, but when I enter "adb devices" at the command prompt I receive "list of devices attached" but no serial number. Also, my Nexus displays: "Fastboot Command Read Error -2147483647". I did a battery pull after getting stuck in a bootloop, and am trying to recover. I can unlock and relock the bootloader, but that is the only command that is working.
Click to expand...
Click to collapse
if it does not return a serial number than the phone is not being recognized. I believe that there are 2 different sets of drivers that are needed. Let me look for the link and info.
the fact that it returns "list of devices attached" but no number means that it is not finding your device which means it is probably a driver issue. let me see what I can come up with. But I am no expert at any of this.
Ok - so I just did some testing of my own. I ran into the same problem as you. And I know that I have the drivers installed. So what I did was try and "shut down" any thing that could interfere with with ADB/Fastboot.
Any tethering apps that you may have - PDA NET, Easy Tether, etc, could possibly do this. Also - when you plug your phone in - and the Auto Play options pop up for FTP (File Transfer Protocol) - X out of that.
I initially plugged in my phone. Opened the command prompt in my platform-tools folder. typed in...
adb devices
...and I got the same message as you. I then "turned off" everything that could be causing problems with the process. I unplugged the phone and replugged it in (and closed the dialog box again) and then re-opened the command prompt and entered...
adb devices
...and then I got the proper return message.
thepolishguy said:
Ok - so I just did some testing of my own. I ran into the same problem as you. And I know that I have the drivers installed. So what I did was try and "shut down" any thing that could interfere with with ADB/Fastboot.
Any tethering apps that you may have - PDA NET, Easy Tether, etc, could possibly do this. Also - when you plug your phone in - and the Auto Play options pop up for FTP (File Transfer Protocol) - X out of that.
I initially plugged in my phone. Opened the command prompt in my platform-tools folder. typed in...
adb devices
...and I got the same message as you. I then "turned off" everything that could be causing problems with the process. I unplugged the phone and replugged it in (and closed the dialog box again) and then re-opened the command prompt and entered...
adb devices
...and then I got the proper return message.
Click to expand...
Click to collapse
I got the same problem with mine i dont have anything like pda net installed but nothing i have tried is able to get adb to list my phone
Getting the same issue myself...help!
Thank you so much I'm a total noob with this stuff but your guide was very helpful!
Noev said:
I got the same problem with mine i dont have anything like pda net installed but nothing i have tried is able to get adb to list my phone
Click to expand...
Click to collapse
ChuckTu said:
Getting the same issue myself...help!
Click to expand...
Click to collapse
Ok - so another member posted this...
ADB/Naked Drivers
...and I have heard some people say that it was very helpful. So hopefully this will help you guys to get your devices recognized.
Then there is also this thread and the OP said this...
Code:
On your windows PC. Use the root guide by bman
( [url]http://rootzwiki.com...nlock-and-root/[/url] )
and download the third option for drivers. Extract all
of these tho wherever you have your fast boot
( for me it was c:/users/thatmayh3mguy/) then run
fastboot in the cmd. The adbapi.DLL file will be there
and will make the fast boot work. I didn't have the sdk
installed ( fresh install of win 7 ultimate last week and
don't have it all set up yet) and it worked
thread...
adb help/getting your drivers installed correctly
OK - here is also another method that I found. I have PDA Net installed and I did not have any issues with fastboot. Here are some instructions that say the drivers that PDA Net use are the same drivers that you need for fastboot. So here is a link to the thread and hopefully one of these methods is going to work for you.
Installing PDA Net to solve your fastboot problems
ah ha - just read something else that I should have thought of...
If your phone is already in bootloader - the command...
adb devices
...will not work. so if you are in bootloader you should try the command...
fastboot devices
...instead and see if that returns anything for you.
just wanted to jump back in hear and say i was able to get mine working again. adb was allowing me to lock/unlock the bootloader i toggled that on and off then when i went to boot my phone it took a long time to boot but finally did. Thanks for all the help was in a real jam there for a minute. I used the naked adb drivers posted above not sure if that did anything but it worked for me. Thanks again!
Noev said:
just wanted to jump back in hear and say i was able to get mine working again. adb was allowing me to lock/unlock the bootloader i toggled that on and off then when i went to boot my phone it took a long time to boot but finally did. Thanks for all the help was in a real jam there for a minute. I used the naked adb drivers posted above not sure if that did anything but it worked for me. Thanks again!
Click to expand...
Click to collapse
cool. glad to hear it.
trying this with a Linux OS
So I have a Samsung Galaxy Nexus on Verizon and I put 4.0.4 (IMM30B) using the Galaxy Nexus ToolKit on Windows. Since then I've had a few issues with performance so I want to go back to stock (ICF53F) then maybe goto latest IMM76K (I think). I've retrieved the zip file from steps above and untar'd the file, but when I try to flash the boot file it just sits there waiting for device. I'm not sure what it's waiting for. I'm in fastboot mode and then plugged in the phone to the usb cord but nothing happens.
Any ideas?
UPDATE:
I figured out the issue. On a linux machine using fastboot requires super user privileges. Maybe an update to the instructions may be in order?
CMD keeps telling me waiting for device.
How long will it takes first time?
this after entering: fastboot flash bootloader bootloader-toro-primekk15.img
ladyminnie said:
CMD keeps telling me waiting for device.
How long will it takes first time?
this after entering: fastboot flash bootloader bootloader-toro-primekk15.img
Click to expand...
Click to collapse
Does "fastboot devices" return your device?
If not, you may have a driver issue.
Sent from my Galaxy Nexus using Tapatalk 2
A mistake I made a while ago, if you are sure that you have already installed ADB drivers, and your device still isn't being recognized by ADB..
Be sure USB Debugging is checked on.
Sent from my Galaxy Nexus using Tapatalk 2
adb devices returns my number from the phone
adb reboot-bootloader does bring my phone into bootloader
than it stops with the next command. I waited for 45 minutes/
---------- Post added at 07:03 PM ---------- Previous post was at 06:57 PM ----------
usb debugging was/is still on
The white small led is lightning up every 10 seconds orso
problem solved with:
http://forum.xda-developers.com/showthread.php?t=1766475
Hello. Is there anyone out there that could provide me with basic instructions on how to unroot my device and put back the stock recovery image?
I haven't done too much after I rooted the device, but I will list whats been done.
1. Performed root with Minimal ADB Fastboot 1.3.1 with SuperSU and TWRP
2. Installed Xposed with a failed attempt to remap the Shield Remote for the OK button long press to kodi context menu. (then uninstalled exposed)
3. Since I couldn't get the exposed key remap to work, I performed a factory rest from within the Android TV settings. (SuperSU is still installed, and every now and then I will see the TWRP splash screen on startup.
4. I attempted to restore the Stock Nvidia Shield TV image with ADB by doing the following:
a. Downloaded the Stock Nvidia Shield TV image.
b. Extracted and copied the folder to ADB fastboot program file directory.
c. Connected Shield with USB to Windows computer.
d. Opened ADB and typed "adb devices" to verify and device showed up.
e. Tried Fastboot verification by typing "fastboot devices" in ADB. Device DID NOT show up.
f. Tried "adb reboot bootloader" and then "fastboot devices" Now the DEVICE SHOWS up.
g. typed, "flash-all.bat" in ADB and it says, "flash-all.bat" is not recognized as an internal or external command"
NOTE: I do have Developer mode, and USB Debugging enabled on the Shield.
The reason I want to unroot is because I have experienced some pretty annoying problems since root. Intermittently upon reboot, Netlix and the Nvidia Game apps do not show. They are just empty spaces. Also the recommendations do not show. I also frequently get "Unfortunately Google Play Services has stopped working" also "Unfortunately Tegra Services has stopped working" and apps crashing/freezing on a regular basis, which force quitting does not resolve. Have to restart Shield to get working again.
I have searched online, and looks like for the most part people who root this device end up not having these problems. Seems like everyone is pretty happy with the root and not experiencing these issues. There are a few I have talked to that have these or similar problems.
If someone could provide me with instructions on how to successfully Unroot my Shield, that would help me out a great deal. I just want it to operate like it was when I first got it. Thanks much for your time.
mikie00mike said:
Hello. Is there anyone out there that could provide me with basic instructions on how to unroot my device and put back the stock recovery image?
I haven't done too much after I rooted the device, but I will list whats been done.
1. Performed root with Minimal ADB Fastboot 1.3.1 with SuperSU and TWRP
2. Installed Xposed with a failed attempt to remap the Shield Remote for the OK button long press to kodi context menu. (then uninstalled exposed)
3. Since I couldn't get the exposed key remap to work, I performed a factory rest from within the Android TV settings. (SuperSU is still installed, and every now and then I will see the TWRP splash screen on startup.
4. I attempted to restore the Stock Nvidia Shield TV image with ADB by doing the following:
a. Downloaded the Stock Nvidia Shield TV image.
b. Extracted and copied the folder to ADB fastboot program file directory.
c. Connected Shield with USB to Windows computer.
d. Opened ADB and typed "adb devices" to verify and device showed up.
e. Tried Fastboot verification by typing "fastboot devices" in ADB. Device DID NOT show up.
f. Tried "adb reboot bootloader" and then "fastboot devices" Now the DEVICE SHOWS up.
g. typed, "flash-all.bat" in ADB and it says, "flash-all.bat" is not recognized as an internal or external command"
NOTE: I do have Developer mode, and USB Debugging enabled on the Shield.
The reason I want to unroot is because I have experienced some pretty annoying problems since root. Intermittently upon reboot, Netlix and the Nvidia Game apps do not show. They are just empty spaces. Also the recommendations do not show. I also frequently get "Unfortunately Google Play Services has stopped working" also "Unfortunately Tegra Services has stopped working" and apps crashing/freezing on a regular basis, which force quitting does not resolve. Have to restart Shield to get working again.
I have searched online, and looks like for the most part people who root this device end up not having these problems. Seems like everyone is pretty happy with the root and not experiencing these issues. There are a few I have talked to that have these or similar problems.
If someone could provide me with instructions on how to successfully Unroot my Shield, that would help me out a great deal. I just want it to operate like it was when I first got it. Thanks much for your time.
Click to expand...
Click to collapse
the firmware pack (the img files, and bat file in the zip file) need to be in the same directory as adb and fastboot
you also need to boot the shield in fastboot mode, you can't flash it otherwise.
Need Help With Unroot
xd4d3v said:
the firmware pack (the img files, and bat file in the zip file) need to be in the same directory as adb and fastboot
you also need to boot the shield in fastboot mode, you can't flash it otherwise.
Click to expand...
Click to collapse
Ok, so when I downloaded the file from: http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/#comment-505
(towards bottom of page under "Restore Shield Android TV to Stock" prerequisites)
It was 1 zip file which I unzipped, and left me a folder with all the files in it (boot.img, recovery.img, blob .bat etc.) I transferred that folder into the minimal adb fastboot folder in C:\program files x86\minimal adb fastboot
Is this the correct process? Or should I have copied the contents of the folder into minimal adb fastboot directory, like a patch?
Thanks for your time, I really appreciate it.
mikie00mike said:
Ok, so when I downloaded the file from: http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/#comment-505
(towards bottom of page under "Restore Shield Android TV to Stock" prerequisites)
It was 1 zip file which I unzipped, and left me a folder with all the files in it (boot.img, recovery.img, blob .bat etc.) I transferred that folder into the minimal adb fastboot folder in C:\program files x86\minimal adb fastboot
Is this the correct process? Or should I have copied the contents of the folder into minimal adb fastboot directory, like a patch?
Thanks for your time, I really appreciate it.
Click to expand...
Click to collapse
Direct link from nvidia http://developer.download.nvidia.co...1/nv-recovery-image-shield-atv-upgrade2_1.zip
And instructions http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
if your Shield is not showing up on devices list, you need to install nVidia's driver. It was pretty weird with my Shield. Even with generic drives installed, adb couldn't get authorization from shield. I saw it on a list, but couldn't talk to it. Only after installing official Windows drivers for Shield, I was able to get ADB authorization box to pop up and communicate with device through ADB/fastboot.
mikie00mike said:
e. Tried Fastboot verification by typing "fastboot devices" in ADB. Device DID NOT show up.
f. Tried "adb reboot bootloader" and then "fastboot devices" Now the DEVICE SHOWS up.
Click to expand...
Click to collapse
I'm trying to flash zulu's StockRestyle 3.0 for SATV v1.0 ROM and the "adb reboot bootloader" works fine for me when the shield box is booted up to android (fastboot devices comes up blank), but when I then enter "fastboot" mode, "fastboot devices" comes up with nothing as does "adb devices". It seems once the command to reboot bootloader sends me to what should be fastboot mode, I lose control from the PC.
Any ideas?
gffmac said:
Direct link from nvidia http://developer.download.nvidia.co...1/nv-recovery-image-shield-atv-upgrade2_1.zip
And instructions http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Click to expand...
Click to collapse
I was trying to unroot 2017 Shield TV (16GB) using the instructions provided in this post and failed to notice the recovery image listed here is for 2015 ? version.
Now the shield doesn't boot, not even into fastboot. anyway I can recover?
I should have paid more attention and read more before blindly using the link provided
HELP! fastboot only sees shield for couple seconds
Trying to Restore my 2015 Shield tv.
First couple steps went ok, but in the middle of flashing the system image, I got an error. Now, the shield reboots and I get the laying down android with the "no Command". If I hold down the power button, I get a different boot-loader screen. Then it reboots after a minute. I plugged in my controller into the USB port closest to the HDMI port, hold down the A and B buttons, which gets me into the normal boot-loader.
Problem is that windows sees the shield for a couple seconds, then it disappears. When I type ADB devices, nothing shows up.
What am I missing?
Hello, So i have searched and have been unable to find any info on unroot NVidia Shield Tv (2017) without a computer. I cant seem to find my USB A to USB A cable. I think it may have been stolen last year when a bunch of my stuff was stolen.
Is it possible, if not, is it possible to use the terminal on my phone to unroot.
Any answers would help, and i would greatly appreciate it.
Mnstr3nrgy said:
Hello, So i have searched and have been unable to find any info on unroot NVidia Shield Tv (2017) without a computer. I cant seem to find my USB A to USB A cable. I think it may have been stolen last year when a bunch of my stuff was stolen.
Is it possible, if not, is it possible to use the terminal on my phone to unroot.
Any answers would help, and i would greatly appreciate it.
Click to expand...
Click to collapse
if u only want to unroot pretty sure theres amagisk uninstaller that can be used..
if u also mean relocking the bl then it might be possible if your mobile has adb and fastboot binaries.. theres a module in magisk to install adb and fastboot binaries.. then it would depend if it can connect or not
elliwigy said:
if u only want to unroot pretty sure theres amagisk uninstaller that can be used..
if u also mean relocking the bl then it might be possible if your mobile has adb and fastboot binaries.. theres a module in magisk to install adb and fastboot binaries.. then it would depend if it can connect or not
Click to expand...
Click to collapse
I know that I'm replying super late. My bad. But I just ended up buying a cable off Amazon. Then like 2 days after unrooting, I found the original cable I was looking for in the first place. LOL
EDIT: Solved, please delete mods. Solution on the bottom.
So essentially I'm on 7.1.1 trying to flash the OEM 8.1.zip from the website however I'm having trouble understanding the steps.
On the website it states:
Download the appropriate system image for the Razer Phone from here, then unzip it to a safe directory.
Connect your Razer Phone to your computer over USB.
Start the Phone in Download Mode with one of the following methods:
Using the adb tool: With the Phone powered on, execute: adb reboot bootloader
Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
If necessary, unlock the Phone’s bootloader. See Unlocking the Bootloader and Unlocking the Bootloader Critical Partitions for instructions.
Open a terminal on your computer and navigate to the unzipped system image directory.
Execute the flash_all script. This script installs the necessary bootloader, baseband firmware(s), and operating system for your Razer Phone.
Once the script finishes, your Phone will reboot.
You should now lock the bootloader for security.
See Locking the Bootloader for instructions.
Click to expand...
Click to collapse
So essentially what I'm doing here is unzipping the 8.1 update, opening up a command prompt in that folder, and then typing in "flash_all"?
If that's the case I keep on getting an error. I tried doing an adb sideload for the .zip as well but that did not work either.
I'm certain I have some misunderstanding about how this is supposed to work, if someone could just point out what I'm doing wrong that'd be great.
Thank you.
EDIT: Yeah, apparently I was supposed to just dump the whole .zip file into the master folder. I was trying to use CD to change folders to a folder inside which didn't let me use fastboot.
You need to set your windows environment setting so it knows where your adb folder is so the script can run
I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now. I cannot get anything to flash through fastboot to the phone no matter what I try. At one point I even said screw it and tried flashing the stock boot image back over to re-lock my bootloader, but no luck, still won't flash.
I was originally following this tutorial here but during the flashing of the boot image it kept failing. Then I tried following the "foolproof" guide found here
I either ended up with the error of "no such file or directory" or "too many links" or "unable to identify current slot". Did a ton of Googling but ultimately came up with no solutions.
I have Android SDK and development studio installed. I have the google drivers installed. I have the Razer phone drivers installed and I have ADB and Fastboot installed.
I have all the files I need on the SD card, and when I'm flashing everything I have the files I need placed in the same folder as the ADB\Fastboot files.
I have my bootloader unlocked, developer mode on and USB debugging enabled. I am using a USB Type A to Type C cable as recommended (made by Anker if it matters). I've tried all 3 USB ports on my laptop. I've even disabled Antivirus.
I have flashed many Android devices in the past and none have given me such a headache as this one. I'm even more ticked off that I can't even get the factory boot image back over to re-lock the bootloader after now realizing that I can't install Netflix anymore because they wen't and blocked installations for Rooted android users (for whatever ridiculous reason).
I will say that for whatever reason that when I go to open command prompt by using the shift+right click I only get the option to use Windows Powershell, not Command Prompt. I also have to put a .\ in front of every command I send. I'm unsure why, but I found no work around for it.
I'd like to try to get the TWRP and Magisk installed. I'm sure I can force Netflix to install over to the phone using another method.
Open to any suggestions!
FireGuy0723 said:
I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now.
Click to expand...
Click to collapse
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.
Munk0 said:
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.
Click to expand...
Click to collapse
I've been messing with it today a bunch. I am back to following the "foolproof" guide and this time I have completely uninstalled all my old drivers for anything android or USB or ADB related and reinstalled everything.
All commands work, I am using command prompt now.
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
I've double checked the file names numerous times. I have no idea what I am doing wrong now. I have tried the command "fastboot boot twrp-3.2.1-0-cheryl.img" as stated in the other tutorial and it bounces back with "failed to identify current slot".
So I'm making progress at least. I'm trying to follow the first set of instructions listed in the fool proof guide but still no luck. I also tried the "clean method" listed below on that guide and that one doesn't work either. Apparently the Fool Proof guide thinks I'm a fool!
FireGuy0723 said:
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
Click to expand...
Click to collapse
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.
Munk0 said:
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.
Click to expand...
Click to collapse
I was finally able to get the phone to accept a flash! I ended up saying screw it and dug a old laptop out, fresh install of windows and installed all the proper drivers onto it.
It worked almost flawlessly. It was able to correctly send the twrp.img file and the phone was able to boot into twrp which is about as far as I got. As it was attempting to load twrp it would "crash" the screen would flash twice and try rebooting back to TWRP.
What ended up happening was it got stuck in a boot loop trying to boot into TWRP. (I haven't even installed TWRP.zip yet, just tried booting the .img file).
I couldn't get the phone to boot to the system anymore. I thought I had a nice $600 paperweight on my hands.
I finally got the phone to go back into the boot loader and flashed all the factory stuff back on and relocked the bootloader. So right now I'm 100% back to stock.
I'm not sure what went wrong in the boot up of the twrp.img file. I'd like to try again but I'm kinda getting sick of wiping the phone Everytime something goes wrong.
Sent from my Phone using Tapatalk
I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace
chris5s said:
I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace
Click to expand...
Click to collapse
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk
FireGuy0723 said:
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
In my case I actually had to flash the stock boot.img from the May 2018 stock OS. Then I was able to use Razers guide to flash stock again. I haven't locked my bootloader since I still want to give it a try again. But I want to find a reliable way of rooting and then unrooting in case I want to do so in the feature.
So far I haven't found said documentation.
Installed Magisk v17.1 via TWRP loaded in fastboot boot (not fastboot flash boot ie not permanently installed) and so far all seems well. No boot loops when restarting...
Peace
I see a lot of people have this same problem for different reasons and the solutions are seemingly all over the place if any
My phone recently lagged out and i had to restart it, which is when my issue happened.
I know my space was running low so im assuming that may have something to do with why it happened.
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else. I am new to this and have absolutely no idea what im doing. So ive googled as much as i could but some things arent making sense, id appreciate some help or a step by step
some info
my phone is 100% stock aside from my nova home launcher.
I dont not have custom bootloaders
my phone has a password, idk if that matters but just in case
my phone is not jailbroken (i think is the term?)
I did have USB debugging set already, and I BELIEVE i had developer mode enabled
thats about it for the phone info
In the bootloader main scree, it stats im in fastboot mode, secure boot yes, device state, locked
What ive tried
-I have tried the manual OTA install via the adb stuff
i got success 0 but upon restart, nothing changed and i was still stuck
-i tried the flash steps
but i get "flashing is not allowed in lock state pixel 2"
ive tried to use a pull command via adb, but it said some strings were incorrect? I just copy pasted a command from a similar post, it may not have been catered to my situation fully so i dont know about that
Is there any steps i can take to simply either recover my photos before i factory reset, or reset without wiping, or even maybe delete some files to make space via something somehow?? I just need my data, the phone itself i can replace
Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.
Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat
Edmontonchef said:
Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.
Click to expand...
Click to collapse
i turned that off initially but checked the site just in case, theyre not backed up ):
Sui77 said:
Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat
Click to expand...
Click to collapse
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"
buninthesun said:
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"
Click to expand...
Click to collapse
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata
Edmontonchef said:
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata
Click to expand...
Click to collapse
the OTA sideload has a success of 0 but nothing happens beyond that, the phone still gets stuck at loading
does 0 mean it should have worked? Any idea why nothing changed?
Sorry for the problems.
My bootloader is unlocked, so that might be the reason.
buninthesun said:
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else.
Click to expand...
Click to collapse
Try the following.
1. Download the latest ADB and Fastboot binaries from the links at this page.
2. Extract the zip file you just downloaded to a directory on the root of a drive. For example, I have my copies of ADB and Fastboot stored at a directory I created, D:\ADB.
3. Open a command prompt, not a powershell window, and navigate to that directory using DOS commands.
4. Enter the bootloader on your device and connect your device to your PC.
5. Type "fastboot devices" to make sure the P2XL appears.
6. If it does, type the following commands:
fastboot getvar all
fastboot --set-active=a/b
fastboot reboot
The idea here is to get you into the device by using the second partition. To do this, you need to find out which slot you are currently using, A or B, and set the active slot to the OTHER partition. "fastboot getvar all" will tell you which slot is currently active. "fastboot --set-active=a/b" will change the active partition to the currently unused one. For example, if the active slot is currently a, you would issue the command "fastboot --set-active=b" to switch to the other partition, and then reboot.
Moral of the story here is unlock your bootloader and leave it that way.
So much easier getting out of trouble