Trying to install TWRP v3. Phone is unlocked (not rooted yet as not necessary atm). I'm able to sucesfully push the .img to the sdcard via adb and install via "fastboot flash recover twrp.img" but the moment I reboot the phone and try to access recovery to get into TWRP, all I get is a little icon of an android mascot lying down with his belly open. No TWRP.
I know the phone will auto-overwrite custom recovery's if the correct combination of hardware buttons are not pressed after the first TWRP install (as TWRP needs to patch the default recovery the first time to stop the phone from constantly trying to overwrite TWRP every time) but so far i've not been able to find out what it is (i.e. not the usual vol +- and power all at the same time. Its gotta be something else?).
Edit: Delete his post. I figured it out. Turns out it isn't a good idea to execute "fastboot reboot" immediately after TWRP installation
Don't restart the Phone!
Flash Recovery and the do the following:
Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader you can use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable.
I was running stock Marshmallow rooted and updated to the official Nougat stock. After restarting I then ran fastboot flash recovery and installed TWRP 3.1.0-0. After doing so I booted to recovery using the "fastboot boot twrp-3.1.0-0-ether.img" and the phone rebooted to TWRP. So far so good, I exited TWRP and the phone restarted to the warning screen:
"Your device has been unlocked..." and it's now been sitting at that screen for over 20 minutes. The phone doesn't show up as a fastboot or ADB device, but it does show up in windows device manager. I've held the power button down for over 2 minutes and it won't power off, it doesn't respond to volume buttons.
Steps:
1. Updated rooted stock Marshmallow with official Nougat Image downloaded from forums
2. Reboot and flash TWRP 3.1
3. Boot to TWRP (Made no changes)
4. Reboot phone
5. Completely unresponsive, but still powered on
Did I brick my phone? Is there a way to force it to restart or power off?
Update: Eventually I started mashing buttons, holding down Vol - and Power would allow the device to power off. Then I could turn it on while holding Power and Vol +. This allowed me to get into Fastboot. I tried just flashing the recovery image from the Nougat update, but that didn't fix it so I reflashed the entire Nougat image using the Flash-All.bat that came with it and that appears to have fixed it.
Sorry for panicking, carry on
So basically I was trying to get OmniRom set up, and here's what I did:
(was on beta 108 btw)
Unlock the bootloader (worked!)
Then the phone rebooted by itself, and I saw a glimpse of "encrypting phone..."
I turned on USB debugging, then I authed the phone and rebooted into fastboot once again.
Flashed recovery, worked, and then was greeted by "Enter your encryption password" in TWRP.
Clicked the back key, then wiped data (normal settings). Later I mounted usb. Saw that there was nothing in phone, but for some reason, TWRP Files showed that there were.
So I turned off my phone, and I can't get it past the black boot up screen. Can't even turn off the phone.
Help is greatly appreciated. Thanks!
Can you get to twrp? if yes, mount mtp n copy rom n flash.
try various combinations to reboot. All 3 buttons etc for 10plus sec or 2 button combos.
Or let it drain the battery down and boot to twrp after connecting to charger.
long press power button then along with vol down on power down for fastboot... recovery.
sorry double-post.
lolrepeatlol said:
So basically I was trying to get OmniRom set up, and here's what I did:
(was on beta 108 btw)
Unlock the bootloader (worked!)
Then the phone rebooted by itself, and I saw a glimpse of "encrypting phone..."
I turned on USB debugging, then I authed the phone and rebooted into fastboot once again.
Flashed recovery, worked, and then was greeted by "Enter your encryption password" in TWRP.
Clicked the back key, then wiped data (normal settings). Later I mounted usb. Saw that there was nothing in phone, but for some reason, TWRP Files showed that there were.
So I turned off my phone, and I can't get it past the black boot up screen. Can't even turn off the phone.
Help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
hold volume down and power button for up to 15 seconds and you should reach fast-boot mode. Once in fast-boot mode flash the stock ROM using the latest Stock Tool provided by razer https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/ or if you choose to keep TWRP and use stock OS without trouble I recommend @crians new flash-able stock ROM: https://forum.xda-developers.com/ne...tbit-robin-ether-flashable-stock-rom-t3627060
For omni ROM (once in TWRP)
1. Hit advanced wipe in TWRP and wipe everything it lists.
2. Back out and go to format data and type yes.
3. Plug phone into pc and transfer G-Apps and ROM.zip
4. Flash ROM and G-Apps then reboot
Hello everyone! Complete dumbass here!
I was following the guide to root my razer phone. I've had it for a couple months, and decided to root it. I followed the guide here https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137
After a couple bumps in the road, such as fastboot commands not working, not being recognized, etc. I finally was able to unlock bootloader and install twrp. But it was #9 that got me stuck again.
"9.) Once in recovery, go to the install button, and select Install Zip, and select Magisk-v16.0.zip."
In recovery, adb devices and fastboot devices yielded no devices attached. Doing a search, I came across another forum post where it states the sdcard is encrypted and can't be accessed in twrp, and the fix is to do something like "Wipe>Wipe Data> Type Yes" and that should factory set the card. I did this and rebooted the device. I waited for a half hour for the animated PixelFloatingInACircle logo to be done with it's floating in a circle, but ended up going to bed and letting it die. Woke up this morning, plugged it in, got the razer logo splash screen with the orange text telling me of my impending doom, then went back to the animation. I let my dog out and came back and it was still on. I unplugged it and am letting it die again to see if there's another solution.
I'm wondering if anyone else came across this issue, and if so, how did they fix it? Any help would be appreciated.
Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk
waiflih said:
Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk
Click to expand...
Click to collapse
The problem is when I try to enter download/recovery mode after charging the battery a little, it doesn't go to that menu. Instead, it skips right to the particle logo, and that's where it hangs.
The only guide I saw was the one I listed. Is there a guide for this magisk installer?(Ya know, in case I figure the first problem out, so I might try my hand at potentially creating another)
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards
waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons
Click to expand...
Click to collapse
Tried this originally after I let it die the first time. It still boot to the animation logo.
Bloodeagle said:
Tried this originally after I let it die the first time. It still boot to the animation logo.
Click to expand...
Click to collapse
Read the edit, I found that the trigger is having the usb cable connected to the pc. Try that, or you can also try to adb while the device is booting (particles logo). Sometimes adb is responsive even when booting. There you can try to adb reboot bootloader
waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards
Click to expand...
Click to collapse
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?
Bloodeagle said:
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?
Click to expand...
Click to collapse
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition
waiflih said:
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition
Click to expand...
Click to collapse
I moved the flash_all script into the tools folder and after a little while, the phone booted up into setup! After a couple taps, I've realized the wifi isn't working, which I know is a known issue. I'm gonna let it sit for the night and finish it in the morning!
EDIT : Soooo, I know I said I was going to bed, but I decided to fix the wifi issue, which in turn, also rooted my phone. I've downloaded the root checker, and it confirms it! Thanks so much Waiflih! You rock!
Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.
saberhashemi said:
Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.
Click to expand...
Click to collapse
Have you tried holding few combinations of different butt9ns for a minute or two to see if that results in you getting in downl9ad mode?
Hi,
I have a global variant of S20 with Exynos chipset running rooted stock Android 10 with G980FXXS2ATE7 firmware.
Root was done with Magisk and it was properly working.
I installed a Magisk extension that caused the initial boot loop, but Recovery and Download mode was working. I was trying to install TWRP but that failed to load with some DTBO related problems. So I restored the stock recovery for Android 10 and then choose to flash the Android 11 version of dtbo alone without any additional files from that package, because I was hoping that it would make TWRP work. So I have a combination of stock files for Android 10 + corresponding rooted bootloader and stock recovery + Android 11 version of DTBO.
This was a big mistake, as since the device is rebooting every 30 sec. It only shows that the bootloader was unlocked and afterwards the "Samsung Galaxy S20 secured by Knox" screen. It stays here for a while and then reboots automatically.
Download mode and recovery are inaccessible. They simply do not appear, not with any key combination via which they worked earlier.
If I plug the phone into my laptop, there is absolutely no USB traffic, it is not recognized as a device.
Odin does not see the device either (as there is no USB device recognized by the OS).
The only thing I can do else is if I hold the Vol down + power button for a while and then plug in the charger when the screen goes dark, then the charging logo appears without showing the percentage of the battery. I stays there even if the unplug the charger. When touching the buttons, it goes back to the boot loop.
I have not found a way to power down the phone, even pressing and holding any combination of Vol up, Vol down and Power buttons.
I think the problem is that neither Recover nor Download mode can boot and this is because of the wrong DTBO file that I flashed.
Do you have any idea how I could repair and reflash the working DTBO file matching the firmware on the device under these circumstances?
Is there any trick for Exynos to boot from the SD Card like there is something for Qualcomm based phones?
Or any other way via which I could trigger some activity on USB?
Thanks for any suggestion
Try launching fastboot devices while holding fastboot keys.
Thanks for the suggestion!
I solved the problem finally.
It is strange, but recovery and download mode started to work with the hardware buttons after I removed the SD Card from the phone. I do not know how this is related, but afterwards I could flash with Odin and after reflashing the original firmware and the the usual vbmeta zip, the phone booted up properly.
Afterwards, I could reflash the magisk patched bootloader and regained root access as well.