tried updating to A11, installed to inactive slot, and rebooted but I don't boot into the OS I just boot into stock recovery can't boot the phone normally, I can flash TWRP and format the phone and it'll work normally, any reason why its doing this?
ah nevermind the issue still persists but got around it by formatting the phone which pretty much reset OOS 11 on my phone and let me boot normally
heres some twrps
https://mega.nz/file/ejgDBI6T#HVqWNmwJ4r8Ins9htRuS91BjE9QmF4AFRr-zO7rLRVk
and to install in twrp here dual/single twrp installer zip file
Related
Hi all,
Recently I updated my Nexus 5 from Lollipop to Marshmallow 6.0.1 (MMB29Q) - latest build.
everything stock works fine but, once I flash a customer recovery, in my case TWRP it stops working...I get either a startup loop or TWRP gets erased by stock recovery.
I tried various steps ...
flashed TWRP 2.8.7.1 - rebooted to boot loader was able to get into TWRP but, once I reboot system, everything works but TWRP is gone/erased and replaced by stock recovery?
Flash TWRP 2.8.7.1, then flash latest TWRP 3.0, reboot to boot loader and can get into TWRP but once i reboot into system, I am stuck on the initial boot loop.
I have to start from scratch of flashing system and boot etc to get past the loop and it still replaces TWRP with stock recovery.
I can always get into Fastboot but when I go to recovery it seems its being replaced by stock recovery.
anyone experiencing this issue? thanks for your help.
I guess I am doing something stupid but, not sure what...and thanks for your help
If you give more detail on the steps you are taking it will be easier for someone to help. Also, have you tried doing a factory reset when it bootloops?
thanks for the response..here are the details..
I had Lollipop with TWRP 2.8.7.1
yesterday, I downloaded latest build from android site...extracted all files....booted into bootloader and flashed all files..
rebooted - Marshmallow works perfectly...offcourse it not rooted yet or its locedback due to this flash
Scenario:1
So downloaded TWRP 2.8.7.1 and flashed it as recovery, no errors nothing...i rebooted to bootloader and went to recovery to confirm TWRP is there
I rebooted the system - TWRP gives option to root which I said yes so its rooted. I reboot system, this goes into bootloop - I wait for say 5-10 min in this loop mode and I see that adb can recognize the device but nothing else....its stuck in loop
when I force shut down by holding power button for few sec - and go back bootloader/recovery - TWRP is still there
***note*** I did factory wipe in TWRP but that did not fix above condition.
Scenario2:
exact same steps but after I flashed twrp2.8.7.1, I rebooted bootloader and flashed twrp 3.0 as well confirmed twrp 3.0 is flashed and rebooted system - phone start normally no issues - when I restart to bootloader - no TWRP exists, its replaced by stock recovery
Scenario 2, I tried couple of other ways and still the same thing happens - twrp 3.0 get erased.
not sure what I am doing wrong but TWRP doesn't stick
since this is my active device - i flash system.img and boot.img to get the phone to working condition
thanks for your help
Try flashing the latest supersu to get root.
audit13 said:
Try flashing the latest supersu to get root.
Click to expand...
Click to collapse
That did the trick.....thank you very much. I was using older version of supersu thinking it was latest.....I downloaded V2.65 and installed it and that fixed all my troubles..
muchas gracias
After I unlocked my bootloader of my Xiaomi Mi A1, I wanted to boot into TWRP by using this command: fastboot boot twrp.img but it wouldn't do anything so then I typed 'fastboot reboot' and it started to reboot and went onto the screen with the MI logo but then the screen went blank, the phone vibrated and it started rebooting again. I left it for a while and when I returned, it was still rebooting constantly. I do not know what is happening but I tried to lock the bootloader and then boot into recovery but that didn't work. I managed to somehow get into TWRP (not knowing how) twice and the first time I just rebooted and the second time, I factory reset my device. From that point onwards I couldn't get into TWRP because I was trying to flash Ressurection Remix rom if I could get into the recovery. My phone is not yet rooted.
Good/Bad news
I installed a different version of TWRP and was able to boot to TWRP successfully so I installed Lineage OS 15.1 and it said that it can't mount '/system' or '/storage' as it doesn't exist after that, I booted and it went into some kind of Lineage OS recovery and I
didn't know what to do with it as applying an update from SD card didn't work so then I installed the pixel experience ROM which also put me into a recovery and the apply update from SD card didn't work as it says 'couldn't mount /sdcard Installation aborted.
Instaling an update from ADB doesn't work either as it tells me to sideload the zip file which I did and nothing happened. Whenever I choose reboot system now, it just reboots back to the recovery.
My phone is not yet rooted but if that would help in any way, I could root in TWRP.
Please help, I don't know what to do.
I has a pretty big problem of that Crash Dump screen some hours ago and i still can't get to fix it. Here is the story, after trying Havoc 2.0 rom i decided to go back to stock so in TWRP i erased the system, cache (dalvik cache and cache), data and internal storage (i wiped internal storage because TWRP just couldn't decrypt it even though the passwd was correct), after that i flashed the stock OOS rom and the TWRP installer (all these being booted on twrp), but when i rebooted into recovery the twrp splash screen just froze there, so i tried to boot twrp through fastboot, but then the crash dump screen apeared, this post: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 said this was a way to recover from that problem so i tried it, it worked as far as booting into OOS is concerned, but when i try to boot into twrp through fastboot the crash dump screen keeps showing up.
Any ideas?
mateuxi said:
I has a pretty big problem of that Crash Dump screen some hours ago and i still can't get to fix it. Here is the story, after trying Havoc 2.0 rom i decided to go back to stock so in TWRP i erased the system, cache (dalvik cache and cache), data and internal storage (i wiped internal storage because TWRP just couldn't decrypt it even though the passwd was correct), after that i flashed the stock OOS rom and the TWRP installer (all these being booted on twrp), but when i rebooted into recovery the twrp splash screen just froze there, so i tried to boot twrp through fastboot, but then the crash dump screen apeared, this post: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 said this was a way to recover from that problem so i tried it, it worked as far as booting into OOS is concerned, but when i try to boot into twrp through fastboot the crash dump screen keeps showing up.
Any ideas?
Click to expand...
Click to collapse
Use bluespark twrp not official
ON rom 8.1 best is official twrp
on rom 9.0 best is blues park twrp
yldlj said:
Use bluespark twrp not official
Click to expand...
Click to collapse
akswap said:
ON rom 8.1 best is official twrp
on rom 9.0 best is blues park twrp
Click to expand...
Click to collapse
It worked!
Now i'm installing all my mods again.
Thanks!
UPDATE:
Nevermind, it boots into twrp, but it wont boot OOS, i already tried erasing all the partitions (system, data and cache) and installing OOS and bluspark TWRP.
It turns on, shows the bootloader unlocked screen and then it reboots back to twrp.
UPDATE 2:
Fixed it by erasing all data on oneplus recovery, thanks again, my phone is back from the death (a quite unrooted one).
Fixed it by erasing all data on oneplus recovery, thanks again, my phone is back from the death (a quite unrooted one).
Click to expand...
Click to collapse
When u upgrade from os 8.1 to 9 .0 after flash install blues spark twrp.
When Downgrade 9.0 to 8.1 use official OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip
& flash official Twrp & Stable magisk only
for 8.1
1- must have a copy of Oxigen Fastboot ROM 8.1
2- Oxigen 8.1 rom ( Revovery) .zip
3- twrp-installer-enchilada-3.2.3-0zip & img file
for 9.0
4- twrp-3.2.3-x_blu_spark_v9.86_op6.zip & img file
5- magisk 16.7 beta & 17.1 Stable
6- official 9.0 Stable rom
7- tool all in One (PC)
Enjoy flashing
Hello,
I have been struggling to root my device. I have not wiped and rooted it in some time and now coming back to it again magisk keeps breaking my device.
I have clean flashed the latest android 9.0.0 build. I have flashed TWRP custom recovery 3.3.0 successfully. I have tried to flash magisk 3 times now and afterwards my phone wont boot. I originally used magisk manager to get the latest zip and patch my boot image. I then rebooted to to bootloader and ran fast boot flash boot patched_Magisk.img. This wiped out my twrp recovery and my phone wouldn't boot, i couldn't get back into twrp recovery. I reflashed latest 9.0 build and wiped everything. I flashed twrp again and tried to flash Magisk 20.0 from recovery. It was successful but again i couldn't boot into my phone and it eventually restarted back into recovery which i still had twrp this time. I then tried it again with 19.3 and the same thing happened. can anyone tell me what is going on here? What am I missing? I have been having reflash factory 9.0 build each time just to get it to remove the patched boot image and boot up again.
Hey
My phone dont detected sim card in custom rom Havoc 3.0.
My phone: OnePlus
Guide install ROM:
https://forum.xda-developers.com/oneplus-7-pro/development/rom-havoc-os-2-6-t3942337
Hope this can help
I had similar issues flashing the rom in slot b instead of slot a fixed it for me
Kreiden_123 said:
I had similar issues flashing the rom in slot b instead of slot a fixed it for me
Click to expand...
Click to collapse
How do you choose slot b while flashing on TWRP?
This seems really convoluted to me, but it totally worked:
Boot TWRP (from fastboot)
Install TWRP from phone storage
Reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into system and wait for something like 5 minutes while it sat on the "Your bootloader is unlocked!" screen.
I believe that installed into both slots for me.
I also had to ADB push the install files after the first ROM install because my encrypted data all got lost. This was all SUPER inconvenient, but it ended up working for me.
jfsat said:
This seems really convoluted to me, but it totally worked:
Boot TWRP (from fastboot)
Install TWRP from phone storage
Reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into system and wait for something like 5 minutes while it sat on the "Your bootloader is unlocked!" screen.
I believe that installed into both slots for me.
I also had to ADB push the install files after the first ROM install because my encrypted data all got lost. This was all SUPER inconvenient, but it ended up working for me.
Click to expand...
Click to collapse
Love it, I'm going to try it tonight