My phone isn't connecting to the computer so adb won't work. I've tried every solution I see. Not sure if I can flash a stock image with twrp. So im hesitant to use flashfire
I tried it using flashfire and it worked perfectly
NateDev said:
I tried it using flashfire and it worked perfectly
Click to expand...
Click to collapse
Would please tell me which zip are you flashfire, Full OTA or Factory img?
Flash the full OTA with Flashfire.
I don't remember, probably the factory images.
unless you want to re-set up your phone flash the ota. An unmodified factory image will wipe your phone.
Related
I can't get TWRP to install on my phone. I've tried manually fastbooting all three TWRP images that are available from the TWRP website. I tried installing TWRP using the Skipsoft Toolkit. Whatever I do I never get past the TWRP splash screen--no menus ever come up. Since no menus ever come up I can't install the TWRP zip or a custom ROM. I've been trying this for hours and it's driving me crazy. Is there a different procedure to boot into temporary TWRP if you are on the June bootloader? Is there another version of the TWRP image file that I'm missing? Am I supposed to let the TWRP sit there for a really long time? This is driving me completely batty.
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
I did. Will give that a try. Thanks.
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
That did the trick! Thanks.
jhs39 said:
That did the trick! Thanks.
Click to expand...
Click to collapse
Np
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
jhs39 said:
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
Click to expand...
Click to collapse
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
noidea24 said:
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
Click to expand...
Click to collapse
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
jhs39 said:
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
Click to expand...
Click to collapse
Booting into the rom, going back into temp TWRP and flashing the TWRP zip seems to have worked --TWRP actually stuck this time and I can boot directly into it now. It's a shame Google made the Pixel XL such a headache to flash on.
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
If you don't want to wipe just update through factory image, just open the factory zip, open flash-all file and remove "-w" from last line, then execute it (update without wipe)
But I suggest to flash the stock factory image with the "-w" to make a clean install, flashing major release like 7.x -> 8.x is always better wipe to avoid potential issues.
But yes, you can first give a try without wipe and only if you find bugs try wiping. Your choice.
simply flash the OTA, then re-root
xraystyle said:
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
Click to expand...
Click to collapse
Use full unroot in supersu. Then take ota. Then root again after upgrading to O
Thanks for the help everyone, you pointed be in the right direction.
In the event that it might help someone else, here's what I ended up doing:
1. I downloaded the OTA, booted into the TWRP I had currently installed, and then sideloaded the OTA.
2. I used ADB to push the newest TWRP flashable zip, the latest SuperSU, and the latest SU-Hide to /sdcard on the device.
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
4. Finally, I rebooted to recovery on the phone (latest TWRP now instead of stock), and flashed SuperSU and SU-Hide.
I'm now stock, rooted, on O. No wipe necessary, kept all my apps and data. So far the OS itself has been entirely stable. I had an issue or two with a few apps after the upgrade, but those were fixed with a quick re-install. Except for Better Terminal Emulator Pro, seems it doesn't want to work on Oreo and it's no longer under active development. It's fine though, there's other terminal emulators out there.
Thanks again for the help!
xraystyle said:
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
Click to expand...
Click to collapse
Which version of TWRP do you have TWRP working with Oreo 8.0?
I can boot into the modded TWRP 3.1 (fastboot boot twrp-3-1-pixel-bootable-mod.img) but AFAIK there is no working flashable recovery for 8.0 yet.
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
gordonlw said:
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
Click to expand...
Click to collapse
That's how I did it. I don't use suhide.
Does the -w in the .bat file format or wipe the data? I want a clean clean , o-fresh in the morning feeling kind of wipe
toknitup420 said:
That's how I did it. I don't use suhide.
Click to expand...
Click to collapse
Thanks! What I ended up doing:
Decided to try and unroot and take the ota. super-su full unroot would not work. so I fastbooted to the mod twrp and flashed UPDATE-unSU. I then took the ota. then fastbooted to mod twrp and flashed super-su. worked perfect!
Hi,
I have Stock Android 8.1.0 ROM from February installed and also Magisk.
I wanted to install March OTA-Update but it just throws "Error" while trying to install OTA-update and reboots back to previous ROM with the hint, that "update could not be confirmed".
Any ideas how to get OTA-Updates to work?
Regards
jsfgsdfhakjf said:
Hi,
I have Stock Android 8.1.0 ROM from February installed and also Magisk.
I wanted to install March OTA-Update but it just throws "Error" while trying to install OTA-update and reboots back to previous ROM with the hint, that "update could not be confirmed".
Any ideas how to get OTA-Updates to work?
Regards
Click to expand...
Click to collapse
OTA's won't work if you're rooted. Get Chainfire's flashfire and flash the ota there. They're are options to retain custom recovery and root.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
OTA's won't work if you're rooted. Get Chainfire's flashfire and flash the ota there. They're are options to retain custom recovery and root.
Click to expand...
Click to collapse
Hi,
but should it not be the reason of using Magisk, that OTA updates are functioning, because it doesn't change the system file system?!
Or does OTA system update also checks the boot loader integrity before updating?
At what state of changing device do OTA updates not work anymore?
Already after unlocking bootloader?
Is there no possibility to get root access and Google OTA updates beside Chainfire's Flashfire?
Magisk, as well as SuperSU, are both systemless root methods. But they also affect the boot image. You need the stock boot image for the ota to work. Magisk can revert the boot image to stock, but I'm much more familiar with using flashfire.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Magisk, as well as SuperSU, are both systemless root methods. But they also affect the boot image. You need the stock boot image for the ota to work. Magisk can revert the boot image to stock, but I'm much more familiar with using flashfire.
Click to expand...
Click to collapse
I restored boot image, tried flashfire but nothing worked for me on my phone.
OTA update still throwed the error after restored boot image.
flashfire throwed a black screen after rebooting and did nothing for a lot minutes. I did a hard reboot after some time.
Finally I did the update manually:
image backup with TWRP boot loaded by Fastboot only
download Google stock ROM from march
extracted ROM
disabled wipe parameter in flash batch file
flashed now
reinstalled current Magisk by TWRP boot loaded by Fastboot only
Finished. :silly:
Nexus 5x
I tried using flashfire myself and got the same results that you did. Thanks for the info. I guess we have to flash the entire ota zip from the google developer site and not just the update.zip.
jsfgsdfhakjf said:
I restored boot image, tried flashfire but nothing worked for me on my phone.
OTA update still throwed the error after restored boot image.
flashfire throwed a black screen after rebooting and did nothing for a lot minutes. I did a hard reboot after some time.
Finally I did the update manually:
image backup with TWRP boot loaded by Fastboot only
download Google stock ROM from march
extracted ROM
disabled wipe parameter in flash batch file
flashed now
reinstalled current Magisk by TWRP boot loaded by Fastboot only
Finished. :silly:
Click to expand...
Click to collapse
Is there any way to install twrp recovery and keep receiving OTAs on stock Pie ROM?
saedkebbeh said:
Is there any way to install twrp recovery and keep receiving OTAs on stock Pie ROM?
Click to expand...
Click to collapse
No.
marstonpear said:
No.
Click to expand...
Click to collapse
How to install OTAs after installing twrp?
You need to flash stock boot.img, as TWRP gets installed to the boot.img on your phone. But you need to do it on the right partition otherwise you won't get the updates. Also if you've tampered with system or any other partition of the device, you need to remove them. To get rid of all the steps, just flash the stock rom via MiFlash (you'll lose your data so take a backup).
marstonpear said:
You need to flash stock boot.img, as TWRP gets installed to the boot.img on your phone. But you need to do it on the right partition otherwise you won't get the updates. Also if you've tampered with system or any other partition of the device, you need to remove them. To get rid of all the steps, just flash the stock rom via MiFlash (you'll lose your data so take a backup).
Click to expand...
Click to collapse
You don't neccesary lose your data with MiFlash, just choose the option without relock/wipe.
thorin0815 said:
You don't neccesary lose your data with MiFlash, just choose the option without relock/wipe.
Click to expand...
Click to collapse
Don't forget to flash the same version!
marstonpear said:
Don't forget to flash the same version!
Click to expand...
Click to collapse
I need to know where to flash the twrp and where to flash stock boot.img when installing OTA
Yesterday I flashed patched boot img using the command: fastboot flash boot patched boot img, without choosing a partition
I made a guide for doing OTA with TWRP and Magisk. You should be able to follow it and just ignore the Magisk bits. The start covers restoring the boot partition.
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
Note that I normally get a boot loop after installing TWRP and reinstall magisk as a fix. I'll assume you have your own way to install TWRP.
Hello.
How can I please reinstall the stock rom via TWRP recovery without data loss, or how can I reinstall it via the Miflash tool?
I have a bootloop and would like to try reinstalling rom. Thanks
basically what u can do is flash stock rom using mi flash tool. ensure that down to the bottom u click save user data. and i think u should be fine flashing the stock rom and preserving your data in that sense. after flashing wait and let the device reboot for itself it usually takes a couple mins
TormentedHeart said:
basically what u can do is flash stock rom using mi flash tool. ensure that down to the bottom u click save user data. and i think u should be fine flashing the stock rom and preserving your data in that sense. after flashing wait and let the device reboot for itself it usually takes a couple mins
Click to expand...
Click to collapse
I have already managed to boot into the system, in TWRP Recovery I wipe dalvik.
But I need root and I must to patch the boot.img again via Magisk. And then I must flash patched boot.img via ADB back to the mobile, but I'm afraid I'll go back to the bootloop.
Any other options to do root or avoid bootloop?
Thanks
jkmaxfli said:
I have already managed to boot into the system, in TWRP Recovery I wipe dalvik.
But I need root and I must to patch the boot.img again via Magisk. And then I must flash patched boot.img via ADB back to the mobile, but I'm afraid I'll go back to the bootloop.
Any other options to do root or avoid bootloop?
Thanks
Click to expand...
Click to collapse
Stupid question but did you extracted boot.img before or after update? Maybe you flashed patched boot.img from previous update to last update? That would cause bootloop
Greenspoof said:
Stupid question but did you extracted boot.img before or after update? Maybe you flashed patched boot.img from previous update to last update? That would cause bootloop
Click to expand...
Click to collapse
It's not a stupid question.
The update was displayed on my phone, downloaded, installed, restarted and booted into the system, everything is fine.
Then I had to download the update manually from the Internet and extract the boot.img. and I then patched it via Magisk and flashed it back to the mobile via ADB, and then a bootloop occurred.
jkmaxfli said:
I have already managed to boot into the system, in TWRP Recovery I wipe dalvik.
But I need root and I must to patch the boot.img again via Magisk. And then I must flash patched boot.img via ADB back to the mobile, but I'm afraid I'll go back to the bootloop.
Any other options to do root or avoid bootloop?
Thanks
Click to expand...
Click to collapse
basically to root its just best to flash the official magisk zip via twrp. it patches the boot img during the process. and u wont get bootloop