Sup everyone, I'm new to this forum and I don't know how to navigate here so sorry if I missed. Today I decided to update arrow os 11 (11 Nov build) and I got boot loop. I still can boot into twrp but I don't know what to do.
So you OTA and it goes bootloop?
Dirty flash it again?
Lu5ck said:
So you OTA and it goes bootloop?
Dirty flash it again?
Click to expand...
Click to collapse
yep. i dont want to stay on this broke os cause its so bad. can i flash to new?
also, i have installed new windows, so i got old drivers, installed them but my phone looks like not plugged-in for windows
You have TWRP custom recovery ? If that flash again Arrow Os
Related
Hey guys i have an issue,
i was running Pixel Experience 10 but on MIUI 10, i couldn't update the last one so i thought to get back to stock rom, update to miui 11 and then get back to my Pixel rom. I DID A F*CKING MISTAKE. I installed the Miui 11 Update through TWRP without restoring the stock miui 10 rom. It worked but i had lost my Pixel rom ( i have a backup), ok then i installed TWRP at the MIUI 11 because recovery mode got me at Xiaomi Recovery for some reason. Inside the TWRP i flashed Disabled forc Encryption, but it didnt flash the Magisk, i reboot to system and after 100 bootloops i tried to go back to recovery mode, it boot at TWRP but since then, the TOUCHSCREEN DOESN'T WORK.. I used xiaomi mi flash tool to return to stock rom, it did, locked the bootloader etc...the touchscreen still doesn't work though... I can connect a mouse with OTG Type-C and i can do anything you tell me in order to fix it.. i have already update to MIUI 11, unlock the bootloader, installed TWRP and have Root. Has anyone any idea or a solution to try?
Thanks everyone in advance.
diamoc said:
Hey guys i have an issue,
i was running Pixel Experience 10 but on MIUI 10, i couldn't update the last one so i thought to get back to stock rom, update to miui 11 and then get back to my Pixel rom. I DID A F*CKING MISTAKE. I installed the Miui 11 Update through TWRP without restoring the stock miui 10 rom. It worked but i had lost my Pixel rom ( i have a backup), ok then i installed TWRP at the MIUI 11 because recovery mode got me at Xiaomi Recovery for some reason. Inside the TWRP i flashed Disabled forc Encryption, but it didnt flash the Magisk, i reboot to system and after 100 bootloops i tried to go back to recovery mode, it boot at TWRP but since then, the TOUCHSCREEN DOESN'T WORK.. I used xiaomi mi flash tool to return to stock rom, it did, locked the bootloader etc...the touchscreen still doesn't work though... I can connect a mouse with OTG Type-C and i can do anything you tell me in order to fix it.. i have already update to MIUI 11, unlock the bootloader, installed TWRP and have Root. Has anyone any idea or a solution to try?
Thanks everyone in advance.
Click to expand...
Click to collapse
did you find a solution, I have the same problem. Thanks
Hi all so I am planning to install a Havoc OS on my phone with TWRP and Magisk
So my question is in the event that the install doesnt work out for me or that I dont like the rom (no rearson why I shouldnt) how do I get back to the original A10 rom?
I have downloaded the OxygenOS 10.0.6 [EU] OnePlus 7 Pro 5G.zip file from here already. Would I be able to go ahead boot into TWRP and flash this ifneeded?
TIA Bart
bartjunited said:
Hi all so I am planning to install a Havoc OS on my phone with TWRP and Magisk
So my question is in the event that the install doesnt work out for me or that I dont like the rom (no rearson why I shouldnt) how do I get back to the original A10 rom?
I have downloaded the OxygenOS 10.0.6 [EU] OnePlus 7 Pro 5G.zip file from here already. Would I be able to go ahead boot into TWRP and flash this ifneeded?
TIA Bart
Click to expand...
Click to collapse
Hi Bart,
Make sure you keep TWRP recovery after flashing custom Rom.
Then if you want to go back, flash official Rom zip on both slots after formatting data otherwise it won't boot.
Thanks for that.
Only thing I'm not sure is what you mean by flashing to both slots?
If for example you get a boot loop can you still get into TWRP?
I assume this is a yes as this is before it boots into the phones OS?
bartjunited said:
Thanks for that.
Only thing I'm not sure is what you mean by flashing to both slots?
If for example you get a boot loop can you still get into TWRP?
I assume this is a yes as this is before it boots into the phones OS?
Click to expand...
Click to collapse
When returning to stock,
format data
Flash stock zip
Flash TWRP
Reboot into recovery which is TWRP
Follow the same steps again and reboot...
If you end up in boot loop, don't stress. You can always flash TWRP recovery again via fastboot.
Hi everyone, I'm new to this forum, I have been going crazy with a Huawei P8 Lite 2017 for two days, I was trying to install DarkJoker360's AOSP 11 I have already modded a P8 Lite (not 2017) and I had no problems, I managed to install TWRP recovery 3.2.1-0 (I can't find the recovery that DarkJoker recommends) via ADB on my Windows PC I did all the necessary wipes and tried to install this operating system in the partition (Image System) it is an .img file after doing this I restarted and the only thing it does is bring out the Android writing, as if it had installed the rom but then it ends up restarting after a few seconds of this writing, without even getting to the configuration screen, what could I have mistaken?
I apologize for any mistakes but I'm Italian and I might have something wrong
Chricap said:
Hi everyone, I'm new to this forum, I have been going crazy with a Huawei P8 Lite 2017 for two days, I was trying to install DarkJoker360's AOSP 11 I have already modded a P8 Lite (not 2017) and I had no problems, I managed to install TWRP recovery 3.2.1-0 (I can't find the recovery that DarkJoker recommends) via ADB on my Windows PC I did all the necessary wipes and tried to install this operating system in the partition (Image System) it is an .img file after doing this I restarted and the only thing it does is bring out the Android writing, as if it had installed the rom but then it ends up restarting after a few seconds of this writing, without even getting to the configuration screen, what could I have mistaken?
I apologize for any mistakes but I'm Italian and I might have something wrong
Click to expand...
Click to collapse
I thought huawei doesn't allow bootloader to be unlocked this proves Me wrong
Austinredstoner said:
I thought huawei doesn't allow bootloader to be unlocked this proves Me wrong
Click to expand...
Click to collapse
I unlocked the bootloader via "DC-Unlocker" so I don't think that's the problem
Chricap said:
I unlocked the bootloader via "DC-Unlocker" so I don't think that's the problem
Click to expand...
Click to collapse
If u still have twrp installed after flashing that custom Rom u can try flashing other custom rom like lineage os
Before flashing anything else try to make sure what your doing 1 mistake could make u ruined like forever if u flashed other custom rom still in bootloop but TWRP uninstalled well than your screwed
Austinredstoner said:
If u still have twrp installed after flashing that custom Rom u can try flashing other custom rom like lineage os
Before flashing anything else try to make sure what your doing 1 mistake could make u ruined like forever if u flashed other custom rom still in bootloop but TWRP uninstalled well than your screwed
Click to expand...
Click to collapse
Yes, I still have the TWRP installed, precisely version 3.4.0-0, since I could not find a working ROM I tried to debrand it (it was brand Tim) and I think I have done a damage to follow that guide, now I do not not even install the stock rom anymore. I don't know what to do at this point, I would leave the custom rom alone and reinstall its stock rom, at least debrand ...
Hi,
After ignoring the notification to update to Android 11 for over a month, I finally gave in an tried the update today.
I normally run stock OOS ROM with TWRP and Magisk, and updates are always fairly simple, let the OS update, overwriting the recovery and losing root, plug in to the PC and just `fastboot boot` the TWRP image, and then flash TWRP and Magisk on the phone itself, and bobs your teapot.
Alas, Android 11 shat all over those plans. With all the news out about Android 12 being in Beta, I had forgotten that Android 11 was so new to OP7Pro. Correct me if I wrong, but TWRP doesn't seem to work, which was my first mistake, but now Magisk has moved to a "need to patch the boot.img" model, which I hadn't seen before?
Anyways, after attempting to patch my own boot.img, I can no longer boot anything; phone just gets past the bootloader unlocked warning, then reboots into recovery.
I panicked then and attempted to flash one of the flashable Android 10 images from Mauronofrio's thread, which I think made things worse; now it just reboots repeatedly.
Any help appreciated, thanks!
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
I managed to use the MSM Download Tool from the last time I bricked my phone, which got me back to a bootable Android 10. Not much worse in life than losing all my data but better than a brick.
mc_teo said:
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
(...)
Click to expand...
Click to collapse
You cannot
But we gladly do this for you (as I just did)! Remember that you can always report your own posts for any type of forum maintenance you may need.
At your service and stay safe!
Timmy
Forum Moderator
A fix for your failed patched boot.img is just flashing the stock boot.img.
For upgrading (official OTA) and keep root, after installation finishes don't reboot and go to magisk, select install to the inactive slot and reboot, after reboot your phone will have the lastest update without loosing root.
And the best way to restore your phone is using msmtool
Hi All,
I have a new-to-me Oneplus 7 Pro. I have been trying to get Lineage with MicroG running. Well it has been quite the adventure and I have it to the point where I have Lineage running fine, and go to reflash TWRP and have bricked the phone, which takes a bit of time to get back to the point of having Linage running again. Specifics:
Lineage version: lineage-19.1-20221219-microG-guacamole.zip
TWRP Versions: I have found that twrp-3.6.1_11-0-guacamole.img works since my phone is at Android 11.
My questions are:
Are TWRP versions tied to Android versions?
When I am trying to get the last version of TWRP installed I have tried 2 approaches:
fastboot flash recovery
fastboot flash boot
Neither worked, phone always ends up bricked. I have used:
TWRP-3.5.1-guacamole-Nebrassy-3.img
twrp-3.6.1_11-0-guacamole.img
twrp-3.6.2_11-0-guacamole.img
I also have tried to boot the images 1st using: fastboot boot twrp-3.6.1_11-0-guacamole.img
and that bricks things.
What am I doing wrong?
Thanks
Ray
rbahr said:
Hi All,
I have a new-to-me Oneplus 7 Pro. I have been trying to get Lineage with MicroG running. Well it has been quite the adventure and I have it to the point where I have Lineage running fine, and go to reflash TWRP and have bricked the phone, which takes a bit of time to get back to the point of having Linage running again. Specifics:
Lineage version: lineage-19.1-20221219-microG-guacamole.zip
TWRP Versions: I have found that twrp-3.6.1_11-0-guacamole.img works since my phone is at Android 11.
My questions are:
Are TWRP versions tied to Android versions?
When I am trying to get the last version of TWRP installed I have tried 2 approaches:
fastboot flash recovery
fastboot flash boot
Neither worked, phone always ends up bricked. I have used:
TWRP-3.5.1-guacamole-Nebrassy-3.img
twrp-3.6.1_11-0-guacamole.img
twrp-3.6.2_11-0-guacamole.img
I also have tried to boot the images 1st using: fastboot boot twrp-3.6.1_11-0-guacamole.img
and that bricks things.
What am I doing wrong?
Thanks
Ray
Click to expand...
Click to collapse
If you look at the official installation page for your phone, you will see that Lineage OS 20 and 19.1 are supported. So you should reinstall Lineage OS 18.1 again, and then follow the steps on this page. Don't bother reinstalling GAPPS until after you upgrade it.
If for whatever reason you don't want an Android version higher than 11, let me know.
I specifically don't want GAPPS or anything remotely Google related. I had tried OS 20 and found that I had a problem installing apps - probably user error, but I don't need the latest and greatest. I am currently at Android 11.
I will read through the instructions, although the number of tutorials I have gone through is craze.
Can you tell me what the relationship between TWRP and Android version is, and are you able to sus out what I did wrong with my efforts to get TWRP loaded over the lineage 19 version I was using?
Thanks
Ray
rbahr said:
I specifically don't want GAPPS or anything remotely Google related. I had tried OS 20 and found that I had a problem installing apps - probably user error, but I don't need the latest and greatest. I am currently at Android 11.
I will read through the instructions, although the number of tutorials I have gone through is craze.
Can you tell me what the relationship between TWRP and Android version is, and are you able to sus out what I did wrong with my efforts to get TWRP loaded over the lineage 19 version I was using?
Thanks
Ray
Click to expand...
Click to collapse
rbahr said:
I have been trying to get Lineage with MicroG running
Click to expand...
Click to collapse
So I guess you don't want GAPPS, just MicroG. Definitely read through the instructions I gave you, as they are the official installation and upgrade instructions.
I would recommend installing Lineage OS 20, because it is the version that is being maintained right now.
I will attempt to guide you through the steps, but I need to know what your situation is right now: Is your bootloader unlocked? What OS do you have installed right now? What recovery are you using? etc.
I appreciate your help. Currently I am looking at a freshly updated phone with Android 11, and Oxygen 11.0.9.1.GM21AA.
The phone is a GM1917
Bootloader is unlocked and I am in developer mode. I have adb and fastboot loaded on my computer. I also have a working version of msm as I have bricked this thing 6 or 7 times...
Several times now, I have done the following:
Install TWRP
Install Lineage
Try and reflash TWRP <-- consistently fails at this point, gets stuck in a boot loop in the bootloader screen
Thanks
Ray
rbahr said:
I appreciate your help. Currently I am looking at a freshly updated phone with Android 11, and Oxygen 11.0.9.1.GM21AA.
The phone is a GM1917
Bootloader is unlocked and I am in developer mode. I have adb and fastboot loaded on my computer. I also have a working version of msm as I have bricked this thing 6 or 7 times...
Several times now, I have done the following:
Install TWRP
Install Lineage
Try and reflash TWRP <-- consistently fails at this point, gets stuck in a boot loop in the bootloader screen
Thanks
Ray
Click to expand...
Click to collapse
"Try and reflash TWRP" what do you mean, update the OS over TWRP?
I mean trying to re-install TWRP after installing Lineage
rbahr said:
I mean trying to re-install TWRP after installing Lineage
Click to expand...
Click to collapse
OK. Can you try following the installation instructions and skip the unlock bootloader step? Do so at your own risk, because the steps say you have to be on Android 12 first. If you do follow them, just make sure you follow them very carefully.
rbahr said:
I mean trying to re-install TWRP after installing Lineage
Click to expand...
Click to collapse
To my knowledge the guides that are provided on the TWRP site don't work for Android 12 and 13. From what I've heard, you have to root your phone and then install TWRP through Magisk.
Honkette1738 said:
To my knowledge the guides that are provided on the TWRP site don't work for Android 12 and 13. From what I've heard, you have to root your phone and then install TWRP through Magisk.
Click to expand...
Click to collapse
The guides I linked to point to the official Lineage OS instructions, right?
ethical_haquer said:
The guides I linked to point to the official Lineage OS instructions, right?
Click to expand...
Click to collapse
Yeah, but I was just saying how they should probably reflash TWRP instead of how TWRP's site says to, which doesn't work
Honkette1738 said:
Yeah, but I was just saying how they should probably reflash TWRP instead of how TWRP's site says to, which doesn't work
Click to expand...
Click to collapse
This build uses Lineage OS Recovery instead of TWRP.
ethical_haquer said:
This build uses Lineage OS Recovery instead of TWRP.
Click to expand...
Click to collapse
I know, but TWRP can be installed with Android 13 custom roms according to the TWRP thread.