Recently I had some trouble with my pixel 2 as my magisk root had magically disappeared, because of this I decided to fix it and re-flash magisk using fastboot to flash the modified boot.img. Since then my Pixel 2 XL wont turn on, I attempted to also flash twrp as well but was met with only a frozen splash screen. Since then I've tried to re-flash the entire OS that was downloaded from the google database and yes for the right version (taimen). I've auto tried to restore it using the android flash tool available through google online as well with limited success.
So here's my current situation. Right now turning on the phone takes me straight to the bootloader screen, attempting to hold volume up or anything other button combinations does nothing but take me to the bootloader screen. Attempting to use the android flash tool now turns the phone off the instant the pc detects it, trying to flash manually with fastboot (the latest version yes) does not work and even a simply "fastboot devices" returns "???????????? fastboot" which then reboots the phone. I'm kinda at a loss of what to do here, i've had softbricks on other phones before but have always managed to fix it one way or another but this one has sadly beaten me
p.s. I've already tried 3 different cables
tcxufatime said:
Recently I had some trouble with my pixel 2 as my magisk root had magically disappeared, because of this I decided to fix it and re-flash magisk using fastboot to flash the modified boot.img. Since then my Pixel 2 XL wont turn on, I attempted to also flash twrp as well but was met with only a frozen splash screen. Since then I've tried to re-flash the entire OS that was downloaded from the google database and yes for the right version (taimen). I've auto tried to restore it using the android flash tool available through google online as well with limited success.
So here's my current situation. Right now turning on the phone takes me straight to the bootloader screen, attempting to hold volume up or anything other button combinations does nothing but take me to the bootloader screen. Attempting to use the android flash tool now turns the phone off the instant the pc detects it, trying to flash manually with fastboot (the latest version yes) does not work and even a simply "fastboot devices" returns "???????????? fastboot" which then reboots the phone. I'm kinda at a loss of what to do here, i've had softbricks on other phones before but have always managed to fix it one way or another but this one has sadly beaten me
p.s. I've already tried 3 different cables
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-2-xl/help/pixel-2-bricked-t3889296 on the last page there are possible solutions to try. Have you tried a different port?
Also, as you can use fastboot in the bootmenu, download the twrp.img (link) to your adb.exe directory and use the adb shell to type 'fastboot boot twrp.img'.
If that works you could go to the reboot option and change the A/B slot to the other version used.
Through twrp - tools, you can also select adb mode to allow your PC adb shell to use 'adb sideload ota.zip'.
Use the ota.zip version of your current version which you download here.
Related
First off, this forum rocks. First post but have read a tremendous amount since learning to root and rom my Thunderbolt.
I upgraded to the Galaxy Nexus (CDMA), and decided to try the "one-click root" which left me with the followign problem.
It seemed to work ok, however when I booted into recovery, recovery failed to load and I got the android w/ exclamation.
I tried a few other things to no avail, at one point I hit a volume up and down and got a limited clockwork menu on the screen, one which was factory wipe (as I was intending to install a ROM).
The wipe hung, so I pulled the battery and was left in a loop.
I booted back into fastboot, and it shows as unlocked, but I can't get it to show as a device in ADB.
I'm assuming this may be a driver issue. I did re-download the Android SDK but this didn't seem to make a difference.
I get the USB connection, but the phone displays "Fastboot Command Read Error -2147483647". I did try to kill server and try again as I saw suggested in some other posts but no luck.
In device manager it shows as "SAMSUNG Android ADB Interface" for the driver 2.9.310.1125.
I'm thinking fastboot should be a non-samsung branded driver?
Anyhelp is appreicated.
thanks!
soulman1980 said:
First off, this forum rocks. First post but have read a tremendous amount since learning to root and rom my Thunderbolt.
I upgraded to the Galaxy Nexus (CDMA), and decided to try the "one-click root" which left me with the followign problem.
It seemed to work ok, however when I booted into recovery, recovery failed to load and I got the android w/ exclamation.
I tried a few other things to no avail, at one point I hit a volume up and down and got a limited clockwork menu on the screen, one which was factory wipe (as I was intending to install a ROM).
The wipe hung, so I pulled the battery and was left in a loop.
I booted back into fastboot, and it shows as unlocked, but I can't get it to show as a device in ADB.
I'm assuming this may be a driver issue. I did re-download the Android SDK but this didn't seem to make a difference.
I get the USB connection, but the phone displays "Fastboot Command Read Error -2147483647". I did try to kill server and try again as I saw suggested in some other posts but no luck.
In device manager it shows as "SAMSUNG Android ADB Interface" for the driver 2.9.310.1125.
I'm thinking fastboot should be a non-samsung branded driver?
Anyhelp is appreicated.
thanks!
Click to expand...
Click to collapse
When you boot back into fastboot look under device manager on your computer and you will probably find a yellow question mark by your device. You will need to download the Samsung driver and manually install it at that screen. Then you can fastboot oem lock and then fastboot oem unlock and that should fix your boot loop issue. The android with exclamation point is the factory recovery, if you rooted and still have root download rom manager in the market and flash clockworkmod through it.
badassirocz said:
When you boot back into fastboot look under device manager on your computer and you will probably find a yellow question mark by your device. You will need to download the Samsung driver and manually install it at that screen. Then you can fastboot oem lock and then fastboot oem unlock and that should fix your boot loop issue. The android with exclamation point is the factory recovery, if you rooted and still have root download rom manager in the market and flash clockworkmod through it.
Click to expand...
Click to collapse
definitely check for any drivers, but i haven't heard anybody needing to re-lock & unlock before. once you have the drivers you should be able to use 'fastboot' from the fastboot screen. not adb. after your drivers, type 'fastboot devices' and see if anything comes up.
also, if you can get into clockwork recovery, look at your device manager again for yellow errors....often there is another driver that doesn't install itself properly; the one that allows you to use adb while in CWM.
cancerouspete said:
definitely check for any drivers, but i haven't heard anybody needing to re-lock & unlock before. once you have the drivers you should be able to use 'fastboot' from the fastboot screen. not adb. after your drivers, type 'fastboot devices' and see if anything comes up
Click to expand...
Click to collapse
Fastboot OEM lock and the Fastboot OEM unlock is a known fix to correct a loop soft brick issue that he noted
badassirocz said:
Fastboot OEM lock and the Fastboot OEM unlock is a known fix to correct a loop soft brick issue that he noted
Click to expand...
Click to collapse
which is because it is just doing a factory wipe correct? if he fixes his drivers & fastboot issue, he should be able to just flash an image without wiping the whole phone
I guess in some aspect yes but if the phone is not softbricked anymore that he should be fine not doing it. Most of the time the ADB issue is like you stated that when you boot into fastboot the driver is not recognized so you need to do a manual install to fix it. If his battery pull left the phone stuck in a boot loop he will have to re-lock and then unlock to fix it.
You guys really are a godsend.
So, the drivers all seemed good and installed properly (no exclamation or question mark in Device Manager).
Ultimately, I knew there was a driver issue so I just went to a different computer (running win7 64). Coulnd't get that to work, then found drivers arn't supported. I also found the PDANET work around.
This allowed me to install the driver and fastboot WAS able to detect the device.
Following some advice and some other posts I tried "fastboot oem lock", which worked successfully.
I then rebooted, was still in a loop, then pulled the battery.
I ran "fastboot oem unlock", then rebooted.
This time I got past the "google" screen and got the graphic screen.
This sat for awhile (3-4 minutes)??
Then it rebooted again (I almost cried) and I was back to the google logo. Again, it went past this point and displayed the graphical animation again.
Than, on the second time around came the "Welcome!" screen!!!!!!
As well as a rush of relief that is indescribable....
I spent 5 minutes living as Phillip Seymour Hoffman in Boogie Nights sitting in his car outside the party - then did a human xanax reboot and am happy to go to bed!
I'm only posting all of this in detail as an update, and so it is available for anyone else who may come into this problem.
It seems there are many ways to get stuck into this boot-loop besides what I did.
NOW - the next problem....
I'm in my phone, everything works. HOWEVER, I apparantly have a corrupt or bad install of Clockworkmod on my phone.
Do I just try everything again from scratch, or is there something I should do differently to reinstall CWM Recovery?
Thanks again!
glad you got booted. drivers are supported for windows 7 64x, using them currently btw.
i would download a new copy of cwm, confirm its md5 checksum first, and flash it again if you think its corrupt, or if you have rom manager you should be able to do it from there.
good luck
Glad you got it fixed. The lock and unlock fixes the boot loop issues as you found out. I would root your phone with cf-root using adb which you can find here on xda. Then install clockworkmod through rom manager which you can download free in the market.
Thanks again guys, all is good in the hood.
I followed the instructions to re-install CWM here:
http://forum.xda-developers.com/showthread.php?t=1392336
I picked up where I had left off (I already had phone unlocked).
All is perfect!
can't thank you all enough
I've searched this and other forums, and tried virtually everything that has been suggested or that I can think of.
I have a Zenfone 2 Laser ZE551ML rooted. Phone has worked like a dream. Installed TWRP 3.0, made and saved several backups in several different places, internally and externally.
Two days ago, flashed a TWRP recovery (I was looking to get back some data I had deleted inadvertently), seemed to go well until it booted, and could not get past the screen that says "Fastboot Mode!!!". Connected to a PC and was able to execute fastboot commands; supposedly can flash various recoveries, and seemingly does so, with everything looking right on the PC, and the phone actually rebooting. But always stops at the same screen.
ADB, on the other hand, shows no devices listed. Every command results in "Error: Missing Device."
I have done everything I can think of...uninstalled and reinstalled the ADB drivers, used different ADB drivers, removed the external SD card, removed the battery (which is the ONLY way the phone will shut off...pressing the on/off button for 10 seconds just results in it booting up to the same screen. Have tried the fastboot wipe command, again it seems to do so, but always comes back to the same screen. Fastboot flashing a recovery.img appears to successfully write a recovery, then goes to same screen upon reboot.
Any ideas? I've only had this phone a couple of weeks, and really like it. But flashing what was apparently a bad TWRP backup seems to have destroyed it.
Thanks so much for any suggestions!
i have the same problem.. please help!
i have the exact same problem you had.. please tell me how you restored it
As i have a similar problem i cannot help you on the technical side.
But isn't the laser 551 KL instead of ML. Maybe you flashed the wrong files trying to restore the phone
BeachNYC said:
I've searched this and other forums, and tried virtually everything that has been suggested or that I can think of.
I have a Zenfone 2 Laser ZE551ML rooted. Phone has worked like a dream. Installed TWRP 3.0, made and saved several backups in several different places, internally and externally.
Two days ago, flashed a TWRP recovery (I was looking to get back some data I had deleted inadvertently), seemed to go well until it booted, and could not get past the screen that says "Fastboot Mode!!!". Connected to a PC and was able to execute fastboot commands; supposedly can flash various recoveries, and seemingly does so, with everything looking right on the PC, and the phone actually rebooting. But always stops at the same screen.
ADB, on the other hand, shows no devices listed. Every command results in "Error: Missing Device."
I have done everything I can think of...uninstalled and reinstalled the ADB drivers, used different ADB drivers, removed the external SD card, removed the battery (which is the ONLY way the phone will shut off...pressing the on/off button for 10 seconds just results in it booting up to the same screen. Have tried the fastboot wipe command, again it seems to do so, but always comes back to the same screen. Fastboot flashing a recovery.img appears to successfully write a recovery, then goes to same screen upon reboot.
Any ideas? I've only had this phone a couple of weeks, and really like it. But flashing what was apparently a bad TWRP backup seems to have destroyed it.
Thanks so much for any suggestions!
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
where TWRP.img is the directory of twrp
then you should get back to TWRP
flash TWRP image again in TWRP itself because the method on line 1 only temporary flashes TWRP and will auto discard TWRP after a reboot
HI everyone,
I updated "successfully" from Kitkat to 5.0.2 on my rooted (stock ROM) Nexus 7 second gen.
Unfortunately, when I tried to upgrade to 5.1 everything seem to be normal until the device rebooted and it went through the "update process". 3/4 the way through, the green droid went on his back and the "ERROR" message appeared.
I wiped the cache partition but that doesn't help. I tried to download the update in safe mode, but no success. I also find it odd that each time I reboot my device, I get a message from Android that it is "updating my apps".
If I didn't have any apps and a lot of data on my Nexus, I would wipe the device clean but I'd rather avoid this, if at all possible.
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Thanks
Michael Carleone said:
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Click to expand...
Click to collapse
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
k23m said:
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
Click to expand...
Click to collapse
Hi,
Thanks for the reply. I rooted with Kingroot. I don't believe I have a custom recovery. The bootloader is locked as shown when I boot into recovery mode.
I want to avoid transferring my data and APK files to my PC.
Should I assume there is no way of reinstalling the OS without wiping out the device?Also, there is no link in the above quote: fastboot boot twrp-3.0.2-0-flo.img
Since I got no other replies, I went and restored to factory image. I do have another question. I hope I get a better response there: http://forum.xda-developers.com/nex...a/nexus-7-2013-wifi-root-marshmallow-t3515072
Thanks for the reply.
Can we compare using fastboot flashing TWRP vs Nexus Root Tool Kit: http://www.wugfresh.com/nrt/? I ended up using this utility instead because it was pretty much one click and it didn't require command lines and for whatever reason, I found instructions using fastboot a bit confusing. Which method is better or has more advantages? I left my bootloader unlocked.
Incidentally, I think there was something wrong with my Nexus image. As a result, I did use Google's instructions on how to flash etc. the OEM image. Instructions weren't ideal but I managed to figure things out: https://developers.google.com/android/images
The instructions are here which I assume would be similar if I wanted to fastboot TWRP?
To flash a system image:
Download the appropriate system image for your device below, then unzip it to a safe directory.
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
Using the adb tool: With the device powered on, execute:
adb reboot bootloader
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device. For example, to put a Nexus 5 ("hammerhead") into fastboot mode, press and hold Volume Up + Volume Down + Power as the device begins booting up.
If necessary, unlock the device's bootloader by running:
fastboot flashing unlock
or, for older devices, run:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal 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.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Also, I could've sworn that when I rooted KitKat on my Nexus, my data wasn't wiped out. I don't recall doing anything to the bootloader. I can't recall which method I used, but I know for certain I didn't use the Nexus Root Toolkit. I should've recorded my steps when I rooted.
i rooted my nexus 7 using towel root on kitkat .. i unrooted using supersu... and ota untill marhsmallow with out a problem never use kingroot as its so un stable.
Hey all,
I was on android P and wanted to go back to Oreo so i booted twrp and wiped system/data and then afterwards, fastboot is giving me errors and i cant even boot twrp to my phone it just says remote: unknown command. Heres a pic https://imgur.com/a/odn4w
edit: i was able to get the feb image to flash but now im stuck at the loading G screen. If i open fastboot and try fastboot boot twrp i get unknown command. See here https://imgur.com/a/Ropme
Hold the power button while at no command. Then hit volume up and release both. That will give you the menu.
Get rid of minimal adb and fastboot. I don't understand why people are using something made before even the original pixels were released. It doesn't understand dual partitions or handle the larger sizes of our partitions. Get adb and fastboot from Google.
joedajoester said:
Hey all,
I was on android P and wanted to go back to Oreo so i booted twrp and wiped system/data and then afterwards, fastboot is giving me errors and i cant even boot twrp to my phone it just says remote: unknown command. Heres a pic https://imgur.com/a/odn4w
edit: i was able to get the feb image to flash but now im stuck at the loading G screen. If i open fastboot and try fastboot boot twrp i get unknown command. See here https://imgur.com/a/Ropme
Click to expand...
Click to collapse
Try a different USB port.
Ensure you have USB drivers installed first.
TonikJDK said:
Hold the power button while at no command. Then hit volume up and release both. That will give you the menu.
Get rid of minimal adb and fastboot. I don't understand why people are using something made before even the original pixels were released. It doesn't understand dual partitions or handle the larger sizes of our partitions. Get adb and fastboot from Google.
Click to expand...
Click to collapse
Problem is for sure the Minimal setup.
Only setup to use (ever) is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Updated regularly.
michaelbsheldon said:
Problem is for sure the Minimal setup.
Only setup to use (ever) is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Updated regularly.
Click to expand...
Click to collapse
I am using that platform tools and i still get the remote:unknown command error. Any idea what i should do? I already factory reset and relocked and unlocked the bootloader and critical. I cant even boot twrp to flash magisk. it broke when i was on android p i booted twrp and wiped system data cache from slot a and b. Reboot and then fastboot was wonky like it still is now.
joedajoester said:
I am using that platform tools and i still get the remote:unknown command error. Any idea what i should do? I already factory reset and relocked and unlocked the bootloader and critical. I cant even boot twrp to flash magisk. it broke when i was on android p i booted twrp and wiped system data cache from slot a and b. Reboot and then fastboot was wonky like it still is now.
Click to expand...
Click to collapse
Just curious, but when your in the OS, and open a command prompt on the platform-tools folder and type...adb devices...do you see your device ID?? Same thing for when your in bootloader mode and type...fastboot devices...??? ?
did you fix this? im in the same boat, on p beta tried to flash factory image back to 8.1 and getting "target didn't report max download size".
Im using platform tools
OP, have you managed to solve the issue?
I ran into a lot of trouble updating June OTA and had the same error. Tried to change ports, USB cables, etc. and just when I was about to give up, I decided to restart my PC and tried again, this time things worked fine without any issue whatsoever.
This is likely not your issue, but if your computer has less than 4 gigs of RAM, or you are trying to flash a file larger than your available RAM you will get this message.
This (i.e. rebooting PC) worked
DanteXXL said:
OP, have you managed to solve the issue?
I ran into a lot of trouble updating June OTA and had the same error. Tried to change ports, USB cables, etc. and just when I was about to give up, I decided to restart my PC and tried again, this time things worked fine without any issue whatsoever.
Click to expand...
Click to collapse
This indeed worked when I rebooted my pc.
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