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.
Related
Hi.
- I flashed TWRP using ADP, flashed root to change fonts but used Stock OOS 3.2.4
Now i sold device.=, to buy black one or iPhone
- I done data reset in TWRP to unroot, after reboot SU App was gone.
- I flashed stock recovery via ADB
- I left the bootloader unlocked, i was not sure of comand, plus in case of mess up, i could fix it.
New user has no idea as well, he says now when he installs OTA 3.2.6 it fails to install.
What i am missing? how can i fix this?
Help will be much appreciated, thanks in advance.
EDIT: SOLVED
When i locked bootloader, it took me to bootloap, and when i try to sideload new OOS3.2.4 it gave ever, cannot read file.
- I flashed new official TWRP again.
- I flashed stock 3.2.4 with TWRP
- Set up OS
- Flashed stock recovery, in fastboot by doing USB debugging on
- Locked bootloader by "fastboot bootloader oem lock" right after stock recovery
- Set up OS 3.2.4 again, at this moment 3.2.6 fail to down over the air
- I downloaded stock 3.2.6 incremental update, successfully downloaded and install.
Now phone seem to be at stock. I bought it back from to save him from inconvenience, as he was scared as the phone was failing to install update initially.
Also interested on this, same thing happened with me and a friend, modded his phone, he didnt want it modded anymore, flashed a clean stock OOS, flashed stock recovery, and error on install of 3.2.6 OTA, if anyone have any idea how to recover the ability to OTA, appreciated.
What happens if you try to sideload it
https://forums.oneplus.net/threads/...root-non-root-users-without-data-loss.451853/
khaos64 said:
What happens if you try to sideload it
https://forums.oneplus.net/threads/...root-non-root-users-without-data-loss.451853/
Click to expand...
Click to collapse
When i sideload oos.zip which is 3.2.4, it says cannot read zip.
When i relock bootlaoder, it goes into bootloap, i go back to fastboot and unlock bootloader, it boots back into old stock OOS 3.2.4. This rom still has my changed fonts, which i had when i had root and TWRP.
I know there was a firmware change with 3.2.6, so if you flashed the 3.2.6 recovery with OOs 3.2.4, this could possibly be your issue.
Boot into Twrp, don't need to flash it. Clean flash 3.2.6, reboot. Try relocking bootloader see if you still get boot loops.
Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?
Suren Manukyan said:
Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?
Click to expand...
Click to collapse
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!
I'm experiencing this issue as well. I tried to install TWRP after installing that October security updates. I wonder if there's something in the update that is preventing TWRP from installing?
hilla_killa said:
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!
Click to expand...
Click to collapse
It has something called perm.flash.recovery.zipor something which is described to do the thing you said but the problem is when the phone gets the" flash perm.flash.recovery.zip" it does nothing. It does nothing even when I try to flash it manually when I get the "trial" TWRP which disappears after rebooting.
Had the same problem. I solved it by using the old fashioned way, with fastboot commands found on the TWRP page: https://twrp.me/devices/lgnexus5x.html
Of course, I used the last image: twrp-3.0.2-2-bullhead.img
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Bijiont said:
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Click to expand...
Click to collapse
Please read the other Posts about this
Flash the bootloader from april.
****************************
Download last months 7.1.2 factory image.
Extract it and find "bootloader-marlin-xxxxblahblah.img".
Rename it to "bootloader.img" for simplicity's sake, then move it to the side.
:Flash-all" the latest factory image, after its done stay in fastboot.
Run "fastboot flash bootloader_a bootloader.img" from wherever you moved the file to
Disregard if "partition_a" isnt your primary, once the command is ran it will auto flash to the primary partition.
Boot and setup, reboot back to bootloader.
Boot and install twrp, then reboot to recovery.
Delete fstab.marlin in main directory, then flash preferred supersu (i use 2.79 sr3).
Reboot to system and your done. from here reboot to recovery or bootloader to flash your preferred kernel and mods.
Was able to get this all sorted out.
If anyone else happens to see this thread with the same issues and missed the April bootloader deal you can find a good overview Here
To get the April bootloader image which is something I have never loaded myself you need to download the Factory Image from April then extract it. Inside there you will see the bootloader image.
Hope this helps anyone else who didn't read far enough into this issue.
Shortly after receiving my bootloader unlock code, I made a real mess. First, I tried to install TWRP via these instructions: https://twrp.me/huawei/huaweihonorview10.html
Specifically, I used the ADB/Fastboot method. Unfortunately, when I went to reboot to recovery by holding power+vol-up, it always took me to the Huawei eRecovery, not TWRP. I assumed the install failed after multiple attempts, and thought I would try to root with Magisk so I could use the TWRP app to flash the recovery instead.
I downloaded the ramdisk.img from here: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I found this link here: https://forum.xda-developers.com/honor-view-10/how-to/honor-source-program-t3732573
I then proceeded to patch it with Magisk and flashed the patched .img file. After doing this, the phone would bootloop a few times before ending up at the eRecovery again. I cannot get the eRecovery to get the packaged data for the Upgrade/Install recovery option, but when I choose the Factory Reset option, it reboots to TWRP (weird!) for about 3 seconds and then reboots to bootloader. I tried reflashing the original ramdisk.img when in the bootloader, but this made no noticeable difference.
My next guess is to try flashing recovery_ramdisk.img to try to remove TWRP and restore whatever stock image that was. I want some advice from the community first because I fear this may make things worse!
I saw that Magisk did in fact cause bootloops due to a compiler bug, according to this post: https://www.xda-developers.com/magisk-16-bootloop-crash-fix-huawei-honor-support/
Has anyone run into a similar issue? I assume since I can still get to the bootloader I can fix it, but I'm at a loss as to what the best next step is.
I flashed that recovery_ramdisk image. The result is that instead of booting to TWRP for a few seconds, it reboots into another eRecovery which allows me to do a factory reset and wipe the cache. After doing these, I still can't access the system.
So it turns out my device is BLK-104 and the problem was that I tried to flash files for BLK-109!
I'm surprised things worked as well as they did!
Hi guys it's been a while since I've rooted any devices but decided to root my LG G PAD 8.3 (V500), since it is so outdated. I'm gonna go over exactly what I did on how I got here to better understand. Sorry in advance for the long winded post.
-Anyway, I had to downgrade to 4.2.2 by using the LG Flash Tool 2014.
-Then, I rooted my device by running root.bat Also, I had SuperSU when I rooted.
-After rooting, I installed TWRP via the play store, downloaded the most recent twrp.img and flashed it via the app. It took me forever to get to recovery by pressing power+volume down and then pressing power+volume down+volume up. But after what felt like 20+ tries, I got to TWRP recovery.
-I wiped my phone and flashed the most recent Lineage ROM. Unfortunately, after flashing the ROM, I could not flash GApps because it rebooted to the ROM after flashing. TWRP let me know that I had to update TWRP and since I did not have the play store and I was once again having trouble getting into recovery, I downloaded the most recent TWRP apk.
-When trying to open the apk, it gave me a "can't open file" message which I didn't understand why. After rebooting, for some reason, it then let me run the TWRP apk and installed the TWRP app. This is when I found out that I was no longer rooted because TWRP notified me. I double checked with root checker and indeed I was no longer rooted. I have no idea when or how that happened.
-Again, I couldn't get into TWRP recovery until I plugged in my phone to my PC and for whatever reason, it helped me get into recovery. I wiped the phone and proceeded to flash Lineage and GApps.
-I read that by flashing SuperSu I may regain root, so downloaded an updated SuperSu, went into recovery and flashed SuperSu. When rebooting, the LG screen came up with a message at the top left corner reading "secure booting error! Boot certification verify". At that point, I was in a bootloop and had to go into recovery, wipe and flash again minus supersu. So I am now on Lineage with GApps and no root.
How do I regain root? And anyone know how I was able to lose it? Back in the day when I was into flashing, I never had these problems and never lost root out of nowhere like this.
Also, if I wanted to get back to stock LG 4.2.2, how would I go about that? I know that currently, I can't use the LG Flash Tool 2014 because my current ROM does not have a USB Software option in order for the tool to recognize the tablet.
Any help would be greatly appreciated, thank you.