Long story short, I'm attempting to install Magisk. In order to install Magisk apparently I need to flash the stock boot.img.
So I fire up fastboot, download the matching stock image from google, extract the boot.img file, and flash it with fastboot.
But now my phone hangs at the Google screen. I can still get to fastboot and TWRP, but I don't know what to do at this point. I don't mind nuking my rom and starting over (I want to go to Oreo anyway), but I dont' want to risk permanent damage.
Can you just flash the android O(aka 8) ? (Using the stock files from Google)
If you will do it , you will have sort of "protection" because if your phone wont boot , it will boot to recovery automatically.
And will make your Nexus 5x a bit faster..
Related
I have a Pixel C, rooted using the Nexus Rootkit, TWRP and SuperSU.
All was fine and was on build N2G48C.
I had an OTA notification for Oreo, so I downloaded the OPR6.170623.010 Oreo OTA file, and used FlashFire to apply this.
Now everytime it reboots it goes past the Google logo, then to the "waiting for fastboot command" screen. I've tried rebooting to Recovery and I get the same thing!
Google didn't seem to help, so please can anyone else help?
I was manually flashing rather then using flashfire, but I was getting the same problem. First, flash just the stock room (no root or TWRP) and check that it boots. Mine would, but every time I tried to flash TWRP, it would bootloop to fastboot.
You may want to download the full rom, not just the ota. You can modify the flash batch file to not wipe the tablet, or just flash the components.
What was finally successful for me was to flash TWRP and NOT let it finalize. It should ask if you want to mount R/W so it can keep the rom from overwriting the recovery. I told it no, then flashed the Magisk zip for root. I haven't tested SuperSU, but just replace it here to try. This got me a proper boot to Oreo, with Magisk working correctly.
If I understand it right, and I haven't booted to recovery to check, the rom will likely have overwritten TWRP. Worst case, I have to reflash recovery whenever I want to do a backup or update my rom, but that isn't something I do often on this tablet.
I absolutely hate the navigation buttons and the lack of a app drawer so I jumped when I heard I could put a custom Rom on it. So I unlocked the boot loader but couldn't for the life of me get twrp on it so feeling defeated I decided not to mess with it but now the darn thing won't boot it goes to the recovery screen and not any further. So I guess I need help reversing this or completing the twrp install... I don't really care which cuz I just need a working phone. (Preferably with twrp installed so I can put a different Rom on..)
Need a working phone with stock? Extremely easy. Flashing stock has been made very easy.
Just download factory image and follow the instructions here
https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
And since you cannot boot just reach the recovery page, check if you are able to run fastboot command (fastboot devices) and then run the bat file as instructed in the guide above.
This will wipe everything and help you flash stock to your device.
Getting recovery on Robin is easy too. Not sure what went wrong for you. Make sure you have everything in place first.
Download and install Minimal adb/fastboot https://insider.razerzone.com/index...der-flash-custom-recovery-decrypt-root.23775/
Download and install Robin USB Drivers (just in case) https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
Download latest TWRP https://dl.twrp.me/ether/
Download latest factory image https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
If you want to root then get the latest version of Magisk https://forum.xda-developers.com/apps/magisk (v14 worked fine for me)
Download the custom ROM of your choice
After unlocking the bootloader, just flash the recovery file with the fastboot command and select recovery on your device, you should see TWRP in 1-2 minutes.
Watch this video till 7:34 https://www.youtube.com/watch?v=DKyEhn9clNw
Once you have flashed TWRP properly, now you can push magsik, ROM and gapps and flash them one by one to root and install custom ROM of your choice.
Hope it helps.
I've gone through the posts trying to find an answer. seems like people are having similar issues, but either not exactly the same or no solution found.
I have flashed to stock 7.1.2 ( i know its old, but i want back button kill function). I can use the twrp image to fastboot into it. But when i try to flash the twrp zip (ive tried from 3.1-current), i get the encryption issue. I tried doing this with security passcode set and also with it turned off. same result.
And when twrp is encrypted, i can no longer boot into system. If i try to, it just boots back into twrp (which remains encrypted). I then have to use fastboot and twrp.img to open an unencrypted twrp. From there I can at least boot into android. But i lose root.
Could i potentially use fastboot to get into twrp, flash magisk and xposed and it would work? Yes, i wouldnt be able to boot into twrp without fastboot. But at this point im just trying to get things working any way i can.
Was going to try custom rom but when i tried to flash RR i couldnt get past the boot screen (left it going for at least 20-30 min before forcing a reboot).
Since I cant even get twrp to stick. dont want to go trying to flash roms.
cnoevl21 said:
Could i potentially use fastboot to get into twrp, flash magisk and xposed and it would work?.
Click to expand...
Click to collapse
yes, this should work. it's what i do. i fastboot boot the twrp image and then flash magisk. i don't used xposed and i don't flash the twrp zip anymore. if i need to use twrp, i'll just fastboot boot it.
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Darth343 said:
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Click to expand...
Click to collapse
OK use the boot.img and recovery.img made by @janjan HERE. Under the heading ¨Downloads¨ see ¨Xperia XA1¨ and download the KERNEL + RECOVERY the boot.img and recovery.img are compatible with the G3121-G3112-G3125-G3116-G3123 devices on the applicable firmware.
Flash BOTH using fastboot. The boot.img is patched to allow TWRP to boot which it will never do using the stock boot.
If you wish to go back to stock then simply use FlashTool to flash the stock fotakernel.sin and boot.sin contained in the firmware for your device.
Does it works becouse I boot my g3116 from flashtool camand was
Fastboot boot boot.img and then also it's stuck into bootloader
Hello,
In all of the steps to install Magisk on a phone, I never liked the step in which you have to flash the patched boot image on the boot partition. I always thought it is pruned to errors, especially if you do that at every update, an oversight maybe when you download the ROM or maybe you use an older version of the patched image and your device is soft-bricked. So, I always wondered if there are other, safer, solutions to do that step. When searching for various guides, I found one that instead of directly patching the boot image, boots it instead and then uses the direct installation option in the Magisk app to extract, patch, and re-flash the boot image. I know that the result is pretty much the same, but if you screw up with the patched boot image, the result is just a temporary bootloop that you can resolve by just restarting your device. But in all the guides I've read, only one suggested this alternative solution, so I was wondering why this solution isn't suggested or, at least, mentioned, for those who are afraid to do the blind flash. There are possible issues with using this method or what?
I already used this method two times for installing Magisk on a Oneplus 9 and a Pixel 6, and now I'm here with a brand new Pixel 6 Pro and I've to decide what method to use.
Because you're essentially doing the same thing. Even if you flash the incorrect boot image, just flash the correct one afterwards and problem resolved. You can do either way, the alternative just takes a step longer.
Now that restore images/flash to inactive slot after ota is fixed on Magisk (canary 24306 and later), I would boot the patched image, then do a direct install.
This ensures that Magisk makes a backup of the stock boot image so next update can be taken OTA if desired.
Note: the re-root after OTA method may not work on custom kernels which often make changes to partitions other than boot
shoey63 said:
Now that restore images/flash to the inactive slot after OTA is fixed on Magisk (canary 24306 and later), I would boot the patched image, then do a direct install.
This ensures that Magisk makes a backup of the stock boot image so the next update can be taken OTA if desired.
Note: the re-root after OTA method may not work on custom kernels which often make changes to partitions other than boot
Click to expand...
Click to collapse
Thanks for the answer, this is really helpful. So, should I use the canary version for the first installation or can I use the stable and update to the canary when I have to OTA update? This is just to be sure, I don't know how "stable" is the canary since I never used it.
And since I'm, I'll take the opportunity to ask another related question: how bad can I screw up with the boot image? For example, if I flash a boot image of another device (oriole for example), should I still be able to boot into fastboot and flash the original, or this will prevent me to boot in the fastboot mode at all?
Because I'm still not sure if the initial bootloader phase (the one that boots up the fastboot) is included in the boot image or not, since the recovery has been included in the ramdisk of the boot image since the introduction of the A/B devices (or, at least, I think so).
@fuji97
You can patch intially with stable and change to canary before next OTA if stable hasn't been updated by then.
Booting or flashing boot images can't affect the bootloader partition, which is seperate.
Fastboot boot the patched image, if it boots up you are good to go with a direct install from within Magisk. If it bootloops you will just boot up to your original setup with stock boot intact. Then you can troubleshoot.
If you directly flash a scewed up boot image, it will probably boot to bootloader, and you can flash a working boot.img.
If it bootloops 3 times, the phone will boot to the opposite slot, and you will have a working system again.
shoey63 said:
@fuji97
You can patch intially with stable and change to canary before next OTA if stable hasn't been updated by then.
Booting or flashing boot images can't affect the bootloader partition, which is seperate.
Fastboot boot the patched image, if it boots up you are good to go with a direct install from within Magisk. If it bootloops you will just boot up to your original setup with stock boot intact. Then you can troubleshoot.
If you directly flash a scewed up boot image, it will probably boot to bootloader, and you can flash a working boot.img.
If it bootloops 3 times, the phone will boot to the opposite slot, and you will have a working system again.
Click to expand...
Click to collapse
Awesome, thank you! You clarified a lot of my concerns.
fuji97 said:
When searching for various guides, I found one that instead of directly patching the boot image, boots it instead and then uses the direct installation option in the Magisk app to extract, patch, and re-flash the boot image.
Click to expand...
Click to collapse
I do this exact procedure for every OTA. It's just easier for me and I've had numerous problems trying to "keep" root versus just booting to a patched image and reinstalling.