Hello, I'm not usually a poster to any forum as my questions can be found with enough digging but I can't find my answer, so here goes.
BACKGROUND:
Stock: Motorola 5G Ace (kiev). Android 10. I think it was Snapdragon 690.
Unlocked bootloader
Installed to TWRP 3.5.2 for the 5g ace to both partions _a, _b
Used TWRP to flash lineage-18.1-20210701-UNOFFICIAL-kiev
All commands sent through BASH
DISCUSSION:
Tried to install Gapps after LineageOS, recieved errors that said something like no room or storage and went through each line with a fail. Verified cache was wiped, tried again. Failed again then moved to reboot with just OS.
Lineage OS installed with success.
Boot back to recovery, TWRP is gone and now it's LineageOS recovery. Could not figure out how to flash Gapps to with LineageOS, but learned that if reducing Gapps size it should work in TWRP, so re flashed TWRP, no problems.
PROBLEM:
TWRP will not load. At load screen it shows the TEAMWIN logo and lasts for a min or so then times out, reboots and loads OS.
Will adb to bootloader.
Will adb to fastboot, BUT enters TWRP, no screen touch will accept commands then lock screen initates at about 30-60s and hard reset to get out.
Can fastboot to recovery. but enters orginal TWRP boot time out.
-----------------------------------
REQUEST:
Please assist in troubleshooting why recovery will not boot so I can get Gapps flashed.
-----------------------------------
ADDITIONAL NOTES:
If plugged into charger/power it wont stay turned off and boots. Will only turn off from LineageOS.
Can not boot into fastbootd but I'm guessing that was something related to the original recovery that I wiped.
Comments:
Would this have something to do with LineageOS at Android 11 and my original TWRP was set for android 10?
All I was trying to do was get Gapps to load, super bummed that I was so close. At least my phone is still a phone.
Your TWRP is old. You can flash gapps from the linage recovery. If it was me, I would reflash the ROM and use the lineage recovery to flash the gapps. Once you know that the system is working, worry about the TWRP. The best place to look is the Telegram channel.
Your TWRP is old.
That's what I figured, what version would be better? Reading the TWRP pages make me believe I can't just pick anything that has a newer release date.
You can flash gapps from the linage recovery.
Lineage recovery appears gone. Do you know how to get it back, or if i'm wrong and then how do I get back into it?
If it was me, I would reflash the ROM and use the lineage recovery to flash the gapps.
Once you know that the system is working, worry about the TWRP. The best place to look is the Telegram channel.
I agree this would be a good path, but I have no access to any recovery SW. From what I understand I can't do this from inside the LineageOS either. Silver lining; Lineage is working fine.
Are you rooted with Magisk?
I am using TWRP 3.6.0_11.0 RC1.4. There is an installer that you can use Magisk to flash. It downloaded it from the Telegram channel. There is also a .img file in the Telegram channel.
https://t.me/MotoG5GOfficial is the correct channel.
That was it. Old TWRP. Thank you very much.
You are welcome.
Related
Hello everyone!
I am new here and really looking forward for some answers. I own oneplus one and had a good experience with it. I had upgraded to custom rom that is lineage os 14.1
I wanted to upgrade it to 15.1 through Twrp. I followed the same procedure as i did for last flashing. I wiped the old data and everything and started to flash new rom. But this time twrp was giving an error. When I did research on that i found that i needed to upgrade to newer version of twrp to install lineage os 15.1
I did the same. And then end of it I just unselected the Supersu root and it reboots. Now when I go to the twrp recovery. The oneplus icon shows but then nothing happens. My phone now doesn't have a rom and twrp recovery won't open. When I connect it to my laptop through fastboot, cmd doesn't recognizes the device. I don't have any knowledge about tech and stuff. And I might have done something wrong. Please help me with some solutions
First of all, try to reinstall TWRP trough fastboot (boot in bootloader mode with Volume UP + power), just google a guide if you don't know how fastboot works. also be sure to use the correct twrp for bacon
After that you should be able to boot back in recovery and flash your rom
if still it doesn't work, follow this guide
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sometimes it happens we brick our phones but No worries as long as you can go to fastboot you can always restore back to how it was before.
Either use the Program the guy above provided or this guide:
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I want to know how to flash the twrp again through fastboot, because when I connect it, phone is not detected in cmd. It says no fastboot devices are there. But then I checked and it says some android thing is connected in device manager. I hope it is my Oneplus one. How to pass this step?
It's the android drivers. Make sure you have the drivers installed.
Thank you so much. I was able to download the twrp again and flashed the 14.1 lineage os. The latest twrp is not flashing in the phone i don't know why and because of that 15.1 lineage os is not flashing and shows error. But still it's a relief that my phone is working. Also, when i switch on the camera it's not working and the flashlight icon also is dim and doesn't gets clicked and not works.
I just got a used Pixel off Ebay, and had an adventure unlocking the bootloader (f-ing Verizon), but finally got that done. I was expecting the usual easy time of installing TWRP, performing a complete wipe, and LineageOS 16 after that. Instead, I spent the next three hours making no progress at all.
First I used fastboot to boot TWRP.
Next, I used the TWRP installer zip to install TWRP to "both slots". WTF are the slots?
Then I got LineageOS 16 installed and started up. It was really buggy. I figured I had a bad flash, so I thought a wipe and reinstall would be good.
When I rebooted into recovery, it wasn't TWRP, it was Lineage Recovery. WTF is Lineage Recovery? I never installed that.
From here onward, the only way I could get into TWRP was to use fastboot. If I boot into recovery, I get this Lineage Recovery garbage.
I've wiped the phone multiple times, but it fails to wipe /system and /vendor because they are "unavailable or busy".
I can't install another ROM, and it continues to boot into Lineage Recovery.
Obviously, I'm not understanding how "slots" A and B work.
Can anyone explain the partition scheme on this thing to me, please?
The lineage recovery now installs as standard on official builds wether you like it or not, see their wiki for details, helps with the a/b seamless updates. There is a dedicated thread for sailfish/marlin lineageOS16, might pay to ask in there for details on removing the lineage recovery.
Also this should explain the slot thing a bit better
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Thanks. The installation instructions in the LineageOS changeLog make it clear that the behavior I was seeing was the new normal.
https://www.lineageos.org/Changelog-19/
I've decided to accept it, even if I don't like it.
Mattzees said:
I just got a used Pixel off Ebay, and had an adventure unlocking the bootloader (f-ing Verizon), but finally got that done. I was expecting the usual easy time of installing TWRP, performing a complete wipe, and LineageOS 16 after that. Instead, I spent the next three hours making no progress at all.
First I used fastboot to boot TWRP.
Next, I used the TWRP installer zip to install TWRP to "both slots". WTF are the slots?
Then I got LineageOS 16 installed and started up. It was really buggy. I figured I had a bad flash, so I thought a wipe and reinstall would be good.
When I rebooted into recovery, it wasn't TWRP, it was Lineage Recovery. WTF is Lineage Recovery? I never installed that.
From here onward, the only way I could get into TWRP was to use fastboot. If I boot into recovery, I get this Lineage Recovery garbage.
I've wiped the phone multiple times, but it fails to wipe /system and /vendor because they are "unavailable or busy".
I can't install another ROM, and it continues to boot into Lineage Recovery.
Obviously, I'm not understanding how "slots" A and B work.
Can anyone explain the partition scheme on this thing to me, please?
Click to expand...
Click to collapse
@Mattzees was you Oem unlocking in developer options greyed out ?(connect to the internet or contact your carrier). if so is there any solution or its a waste of time
Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU
Same question here. It seems that you can only boot from TWRP, not install it.
Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.
Hi everyone,
Currently I can only boot to fastboot mode - i.e. not recovery or the system. I don't want to go back to OOS. When I try to flash or boot to recovery, nothing happens and the boot does not work. I'm not sure where to go to from here - do I need to flash stock ROM? I don't even know what version of Android the phone was on...
Edit: Partly fixed, as per below.
I ended up flashing the stock ROM using the MSMDownloadTool:
How To Unbrick OnePlus 6/6T
Download %
networktips.in
At some point I'm going to try using Magisk to flash LineageOS.
OK, got onto LineageOS using this:
Install LineageOS on enchilada | LineageOS Wiki
wiki.lineageos.org
I used this the first time around, so I'm not sure what went wrong. I suspect it was either the fact that it was on Android 11 or that I might have somehow messed up flashing the recovery file.
Anyone doing the sideload with ADB should be aware that it reports a 47% completion rate with success. The flashing has still completed successfully, read the last comment here:
https://www.reddit.com/r/LineageOS/comments/af12lu
Unsure if this is the place since its also related to TWRP 3.7, any help is appreicated
Got stuck in a weird situation and wondering if anyone has ideas.
Current State:
Slot_A on OOS 11, can boot TWRP via Fastboot
Slot_B on OOS 12, can only boot into Fastboot
Originally on OOS 11, booted TWRP and made backups of all partitions (data, boot, system image, vendor image, etc.). Forgot to move this to computer so this is all still stored on device.
Proceeded with OOS 12 upgrade (into Slot B). Patched magisk, rebooted, then flashed TWRP 3.7 (FBEv1), direct installed magisk, rebooted. - Everything was functional, but decided to go back to OOS 11.
Thinking I could just use the TWRP backup made on OOS 11, I did the following:
Booted into 3.7 TWRP
Restored the backup for boot, system image, and vendor image
Set active slot to Slot A and reboot
It doesn't allow me to boot into the OS (Presumably because the data was re-encrypted for OOS 12?)
Set active-slot=b and reboot, but it's locked to fastboot.
I've attempted a few things, but I can't boot back into OOS. I would prefer to retrieve my TWRP backups first before doing an MSM reset.
When on Slot_A (older), I can only boot into TWRP 3.6.2 and 3.7. I'm guessing 3.6.2 can't decrypt since it's only configured for A11 and under, but not sure why 3.7 can't decrypt my data.
- It doesn't even ask for pin when TWRP launches; maybe it's reading the System for Slot_A and thinks i'm still on A11?
- running `twrp decrypt {pin}` doesn't seem to work. Unsure if there's something done to my lockscreen pin to be used as the encryption key/password?
When on Slot_A, attempting to boot into either the system or TWRP hangs.
Things I've tried:
Flashing A11 boot.img and magisk-patched boot.img to Slot_A -> Hangs on 1+ Spinning dots
Flashing A12 boot.img and magisk-patched boot.img to Slot_B -> Hangs on 1+ logo (Does show up on ADB though)
Booting Slot_B into TWRP 3.6.2 (Official, and Nebrassy unofficial for A12) and TWRP 3.7 -> Gets stuck on "Fastboot Mode" screen (fastboot cli still responds) or Hangs on snapdragon logo
Edit: Ended up using MSM. Needed device for work
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
I got it working with crdroid. heres some stuff
guacamole - Google Drive
drive.google.com
be carefull
¯\_(ツ)_/¯
------------------------------------
I got stable and decrypted fs RW working on crdroid 9.1 firmware other than some weird bugs
i put it in the 2023-twrp
MissAnthropin said:
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
Click to expand...
Click to collapse
I have the exact same problem! Have you found a fix yet? This seems to happen when I try to install Android 13 based roms, and when I install a rom like Lineage OS, using their recovery, it works just fine.
No, and I don't know why, maybe i do something wrong or it is the Modell that make this trouble.
I thinking to sell my OP7PRO and buy another one ( and then I have the same problem with the new phone )
No no let the jokes aside, it must work, i mailed with OnePlus Support Germany but they only helped me to install A11 w/root and recovery, i thought ok now I can update to A13 so I loaded A13, unpacked the boot.img, Patched the boot.img
Installed A13 w/out errors, rebooted - Fastboot loop
RIP
Started ranting instead
TWRP for guacamole development seems to be fairly scarce, last working recovery I tried was when they started using fastboot boot to enter it. It was pretty hacky even then, currently it seems that nebrassy is the maintainer for twrp for guacamole.
Github: https://github.com/nebrassy Android 12 thread: https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4269551/ Nebrassys Telegram has helpful info as well: https://t.me/NSSFB
last update I found was 2022:10:2 - https://www.pling.com/s/Phones/p/1835156
after a few days of torture I read a thread on here saying if you flashed twrp via magisk like you would if it was a magisk moule it would work normally. It worked on my device so I assume that its universal. I have filled my computer with guacamole related files Im uploading here before im forced to reinstall my os:
guacamole - Google Drive
drive.google.com
Just a fyi from what I have gathered from my experience you can get a stable twrp recovery with persistant / read write access and disabled encryption and basically use it with little error up until you try flashing a newer custom rom. My guess is when flashing a cfw the bootloader gets rewritten causing our boot image to become corrupted. Flashing twrp over / booting to twrp via fastboot or trying to install it via another custom recovery causes boot / recovery failures... meaning you cant really use it for flashing custom roms. I cant find the post with the install instructions I seen that helped me so here is what I think it was,
Found it: https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
~ I have bricked this device constantly while ****ing around so unless youre prepared to go to war with the ****er, Id quit messing with it.
MSM flashing with windows is the only way to recover from the void.
Click to expand...
Click to collapse
using Linux systems for EDL is a bit more difficult to figure out but can be done > EDL https://github.com/bkerler/edl/blob/master/edl | https://github.com/andersson/qdl
Click to expand...
Click to collapse
~If you do brick I created a fastboot flashable A13 Oxygen os recovery rom and uploaded it to my google drive found under recovery_brick_fastboot.zip ~
Click to expand...
Click to collapse
lastly be mindful of a/b partition configuration or youll find yourself lost or bricked
Installation:
1. Obviously unlock the bootloader - OEM Unlock
2. Flash custom recovery (lineage/crdroid/etc)
3. (Personally I root here and again on the active slot so) flash magisk.zip
4. Reboot into installed ROM and install magisk android app and complete setup, reboot system
5. (another thing I like to do before flashing twrp) setup magisk enable all the basic options like prophide, deny list then set root userspace option to global.
6. Flash TWRP .zip (https://dl.twrp.me/guacamolev2/twrp-installer-3.7.0_12-0-guacamolev2.zip) via magisk
Alright! After all that you should be able to reboot into recovery via adb reboot recovery / fastboot or power menu and you find a working twrp recovery installed.
If you need help or want to **** around with the device you can @ me anytime and ill do my best to halp
2600 IRC (cornelius.scuttled.net >Nick captain >channel #guac)
Telegram https://t.me/+pxvpKToFo6pkMGYx
Discord https://discord.gg/MhvWgEfY
Pics
RolandStoner said:
Pics
Click to expand...
Click to collapse
You Confussing me a lot with your Posts before ...
i´m unsure what you mean exactly,
my bootloader is unlocked, with magisk i got a working root but after that i fail
what you mean with flash twrp with magisk ?
after unlocking the bootloader and get root, i tryd to flash twrp like before on other devices but that seems not working because i get then the fastboot loop
on another thread i found here on xda too, the guy wrote dont forget to activate the fastboot loop fix in the advanced options
but i not tried it yet again , so what should i do now ?
for now , i´m back on android11 , with stock oxygen os firmware
i have to do now the things like i did before again , unpack boot.img from the firmware that is installed on the device
patch it with magisk, flash it with "fastboot flash boot boot-patched.img" or is this step senseless ?
i mean you only wrote unlock bootloader and flash a cfw , but i don´t have a chance to flash a custom fw without a custom recovery ??
my recovery on my op7pro have no options for "install zip" or something else
addendum:
like i said you confused me a lot
addendum two:
or i do what i said before .. i sell my op7pro and buy me a one where i havent so much trouble installing twrp and root
i never had a phone before that made so much trouble in installing simple twrp ...
but i don´t found a phone yet that is compatible with kali and the pentest tools or wardriving tools like the oneplus , so i have a problem ,... i think i should drink now my selfmade blackberry liquor ( or blackberry booze ? ) and let the smartphone be a smartphone for now and power off my brain for a while
Yes, you need to patch your boot image via magisk and flash it with fastboot.
After you let magisk do its first time setup and then once it reboots you go to Magisk > Modules and flash the twrp recovery .zip file you got from twrp. link:https://twrp.me/oneplus/oneplus7pro.html just like you would if it was a magisk module.
the password for twrp decryption is your pin. Here are simpler instructions
https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
****... I forgot a step.
after flashing twrp as a module in magisk you dont reboot, you go back to the main screen hit the install button and choose direct install
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
MissAnthropin said:
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
Click to expand...
Click to collapse
Thank @yassine2217 because I would never have done so either.... Still many bugs but twrp is twrp