Hey folks. Congrats for all that fantastic stuff. I am new in the custom rom world and it is a pleasure to read and learn... Thanks for that.
My topic: In April I bought a Snapdragon based phone, the Le Pro 3 Elite LEX722 (xl0). Followed your instructions here: adb, TWRP, LineageOS 15.1 (April-version), GApps micro. After ten minutes I had a great operating system. Even with full root access thanks to AddonSU. Really superb. Happy for five months.
Then I decided to update. Download via phone internal "LineageOS Update". Flashed the file on device via TWRP. And the disaster began.
First my "desktop" was mixed up. It was a mess to get it back to what I wanted.
So, I decided to get a new set up (like in April, only the new versions TWRP and LineageOS). All worked fine. I got the latest LOS on screen and had GApps.
But when trying to get root access, trouble started again. Since then I can get no root access via this easy way (TWRP and AddonSU). TWRP is encrypted, it doesn t show internal storage. All errors: "not mounted" etc. It happened AFTER (!) the successful installation of LOS and GApps.
I tried everything I found here: Five versions of TWRP (older ones, original, codeworkx). Repair, Ext4->Ext2, FAT, Mount, even ten times Wipe -> Format. No effect.
I cannnot see any zip.file (the most important is addonsu) on TWRP. Internal storage 0MB.
At least, I tried to get back to my April-situation when all worked fine. TWRP 3.2.1-0 and April-LOS 15.1 nightly. But the same. TWRP not showing internal storage.
WTF is this? I did the same, but result is different?
Anything I can do? Thanks for your help, Michael
Have you tried flashing from an otg pedrive?
eqyliq said:
Have you tried flashing from an otg pedrive?
Click to expand...
Click to collapse
Okay. I will try. But seems to me like a bit "unclean". Like a detour. Why isn t it possible the straight way? Especially I had a full operating version with root. Now, the same phone, same zip-files. And a "closed" twrp AFTER LOS installation.
Thanks for flash drive tip.
Michael Wolf said:
Okay. I will try. But seems to me like a bit "unclean". Like a detour. Why isn t it possible the straight way? Especially I had a full operating version with root. Now, the same phone, same zip-files. And a "closed" twrp AFTER LOS installation.
Thanks for flash drive tip.
Click to expand...
Click to collapse
if you have mounted twrp go to the recovery the option cleaning even side in the inferred part see format only put yes and ready do not turn on the rom and the gaps turns on the phone and ready I hope it serves
Michael Wolf said:
Hey folks. Congrats for all that fantastic stuff. I am new in the custom rom world and it is a pleasure to read and learn... Thanks for that.
My topic: In April I bought a Snapdragon based phone, the Le Pro 3 Elite LEX722 (xl0). Followed your instructions here: adb, TWRP, LineageOS 15.1 (April-version), GApps micro. After ten minutes I had a great operating system. Even with full root access thanks to AddonSU. Really superb. Happy for five months.
Then I decided to update. Download via phone internal "LineageOS Update". Flashed the file on device via TWRP. And the disaster began.
First my "desktop" was mixed up. It was a mess to get it back to what I wanted.
So, I decided to get a new set up (like in April, only the new versions TWRP and LineageOS). All worked fine. I got the latest LOS on screen and had GApps.
But when trying to get root access, trouble started again. Since then I can get no root access via this easy way (TWRP and AddonSU). TWRP is encrypted, it doesn t show internal storage. All errors: "not mounted" etc. It happened AFTER (!) the successful installation of LOS and GApps.
I tried everything I found here: Five versions of TWRP (older ones, original, codeworkx). Repair, Ext4->Ext2, FAT, Mount, even ten times Wipe -> Format. No effect.
I cannnot see any zip.file (the most important is addonsu) on TWRP. Internal storage 0MB.
At least, I tried to get back to my April-situation when all worked fine. TWRP 3.2.1-0 and April-LOS 15.1 nightly. But the same. TWRP not showing internal storage.
WTF is this? I did the same, but result is different?
Anything I can do? Thanks for your help, Michael
Click to expand...
Click to collapse
Go to wipe and format data. You will lose everything on external storage, but it will work again
Reboot to fastboot mode, open ADB&fastboot on your pc, type those commands
'fastboot erase cache'
'fastboot erase userdata'
That'll erase everything from your phone but it works. I've had same problem
After that just flash twrp and other stuff.
Got it. OTG flash brought me on the track...
I explain it here, maybe others profit.
The solution is hidden in
Problem: LePro3 has no external SD
So, I took OTG USB drive, got Magisk-zip on it.
Follow the steps shown in mentioned thread.
AFTER (!) wipe, format, yes, you put in otg usb drive
Change storage selection to "otg"
Voila, there is the zip, flash it, reboot system, you got Magisk.
Enable its functions on smartphone
Disappointing: Go to TWRP and it is still locked.
Solution: Flash an older TWRP with Computer via ADB.
Then reflash the actual version again.
Now my TWRP shows everything.
Sounds a bit like: "Black cat at night, full moon on graveyard etc" but it worked for me. Thanks for inspiration.
Related
It's been a year already since I checked this sub and I am still using the TWRP that flickers and is chinese. Is there like an upgraded version for our device? Specifically for the non elite variant US version?
I think I might have screwed my phone because after I flashed a new rom(RR) my internal storage won't mount on recovery and when I connect it to pc. But I can see it in my phone when I'm on system(thank god) This is weird because I have not put any security lock on my phone before backing it up. So I am assuming that I need to update my TWRP to something latest to solve this issue, but I haven't been keeping up to this sub, i don't know if there's a newer compatible of TWRP.
And I also forgot why I did not went with the official one from TWRP. Maybe because it messes up the bootloader? or something like that, forgot since it's been a year already and I remember reading into a guide to use the chinese twrp.
[Solved]
If this happens to your device and you happen to use the chinese screen flicker fest TWRP, just go on and flash the latest official TWRP for our device. And you're going to be able to see your internal storage again.
you can either flash it ADB or from your recovery, but I flashed mine through TWRP
drckml said:
It's been a year already since I checked this sub and I am still using the TWRP that flickers and is chinese. Is there like an upgraded version for our device? Specifically for the non elite variant US version?
I think I might have screwed my phone because after I flashed a new rom(RR) my internal storage won't mount on recovery and when I connect it to pc. But I can see it in my phone when I'm on system(thank god) This is weird because I have not put any security lock on my phone before backing it up. So I am assuming that I need to update my TWRP to something latest to solve this issue, but I haven't been keeping up to this sub, i don't know if there's a newer compatible of TWRP.
And I also forgot why I did not went with the official one from TWRP. Maybe because it messes up the bootloader? or something like that, forgot since it's been a year already and I remember reading into a guide to use the chinese twrp.
Click to expand...
Click to collapse
Stop reading out of date articles, and use the latest Twrp here: https://twrp.me/leeco/leecolepro3.html
The Chinese bootloader issue is no longer an issue
* So to be clear about you issue you cannot boot to recovery.
* You do see you phone when you connect it to the computer...Right?
* BTW, I also have an X727
Your issue is most likely due to corruption and encryption
Backup whatever data you can and then use the All in One ( "AIT " ) tool to remove encryption ( NOTE: this is going to erase your data.
Next Using AIT install Twrp and magisk 17.1 or the easier way to resolve this may be to temporarily go back to stock.
Option 1
Try flashing the latest Twrp and magisk 17.1, using either ADB or AIT
After flashing boot into TWRP recovery
1. Go to "Wipe" and then to "Advanced Wipe".
2. Mark "Dalvik / ART Cache", "System", "Data" and "Cache".
3. "Swipe to Wipe" and proceed back the main menu.
4. Go to "Install".
5. Select the ROM zip file and then press "Add more Zips" and select the Gapps zip file, and then the Magisk file.
6. "Swipe to confirm Flash" and wait for some time.
7. After the flashing is finished, just reboot to recovery, check boxes to keep Twrp installed
8. Boot to system go through setup.
Option 2
You could flash my Recovery which includes Twrp and Root. ( Instructions at Link Below)
Afterwards you will be able to update the Twrp, and Root, then Flash whatever you want.
Le Eco Pro 3 X727 Twrp Backup : Clean Full Stock X727 recovery EUI 5.8.21s
https://forum.xda-developers.com/showpost.php?p=75021582
Option 3
Use All in One tool to restore my recovery, Flash a Stock Rom , or simply Flash TWRP/ROOT and then your Rom> Gapps> Magisk once again > Reboot to Recovery ( Check Boxes, for Twrp manager installation) Reboot to recovery > do not choose to make you drive read only! Clear Cache ( Not Dalvik) Reboot to system > Finished.
However, there is a faster way: @mauronofrio created a tool called: "TOOL ALL IN ONE"" and its great!
https://forum.xda-developers.com/and...ctory-t3358711
Its an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool can also unencrypt your storage
After install the All in One Tool
Make sure to check for the AIT program for updates, to the tool itself and to ADB.
Next, click button to allow ADB privileges system wide.
Get more information here:*https://toolaio.tk**
XDA page for Le pro 3 : https://forum.xda-developers.com/le-...1#post71627491
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Remove Encryption
* Install TWRP,
* Install your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
Of course use ADB or AIT once the phone is restored but you would be better off buying an OTG adapter and a USB 3.0 USB Flash drive. This way you can quickly make changes on the fly. I recommend buying at least 32GB usb 3.0 drive. Absolutely, the OTG adapter is the best method, because you will have all of your files available for quick installation and you can make numerous nandroid backups of your favorite rom installations. So If you get bored with one Rom, you can quickly restore another Rom in 5 to 10 minutes.
Again , if you do not use an OTG drive. Just use ADB or AIT for flashing your files, the steps are same as with any other phone.
Finally, look past any typos, I don't have time to proofread after spending so much time on a single post.
Thanks for the detailed response!
my issue was, I can go to recovery but it is not mounting my internal storage. It was showing as 0mb. I am aware that this is usually happens when you encrypt your device and back it up in the recovery and try to restore. But I never put any encryption on my device let alone it doesn't even ask me for a password when I am on the recovery. Anyway, I solved it by just flashing the latest official TWRP on our device. And I'm glad that I am finally away from the buggy chinese twrp.
I was just worried if there was any dangers on flashing the official latest twrp because I am seeing a lot of people getting bricked. So much for the halfassed allowing us to unlock our bootloader in this device by leeco.
Anyway, I really appreciate all that detailed guide. I will keep them in reference in the future.
drckml said:
Thanks for the detailed response!
my issue was, I can go to recovery but it is not mounting my internal storage. It was showing as 0mb. I am aware that this is usually happens when you encrypt your device and back it up in the recovery and try to restore. But I never put any encryption on my device let alone it doesn't even ask me for a password when I am on the recovery. Anyway, I solved it by just flashing the latest official TWRP on our device. And I'm glad that I am finally away from the buggy chinese twrp.
I was just worried if there was any dangers on flashing the official latest twrp because I am seeing a lot of people getting bricked. So much for the halfassed allowing us to unlock our bootloader in this device by leeco.
Anyway, I really appreciate all that detailed guide. I will keep them in reference in the future.
Click to expand...
Click to collapse
That's great!
In the future
If you have an encryption issue again, and you have latest tarp and magisk.
Just format storage and reboot to recovery, then wipe and issue will be resolved.
Hi, I'm new to rooting. A week ago or so I installed Pixel Experience Rom to my device but didn't liked it to much and my phone was constantly freezing for a second or so. I decided to go back to Oxygen OS with android 9 but keep the TWRP as my recovery and root my phone with Magisk.
Anyways today I got this notification saying that after phone downloads and install the software update my phone will reboot and unroot itself and I should back up my data. /a/DWgVyTK (imgur link)
After using my phone with root I liked it better this way. Anyways because I'm beginner level on this topic I don't know what should I do. I don't want to set up my phone again from the start after the update and I like root but I want my software to be latest as well. Is there any other way to install the update without deleting everything on phone?
Also if I download the latest software update can I flash it with TWRP without deleting anything on phone? Or back up my things with TWRP and install the software and use that back up to get everything back together again? Little bit help would be appreciated.
Ebeninyo said:
Hi, I'm new to rooting. A week ago or so I installed Pixel Experience Rom to my device but didn't liked it to much and my phone was constantly freezing for a second or so. I decided to go back to Oxygen OS with android 9 but keep the TWRP as my recovery and root my phone with Magisk.
Anyways today I got this notification saying that after phone downloads and install the software update my phone will reboot and unroot itself and I should back up my data. /a/DWgVyTK (imgur link)
After using my phone with root I liked it better this way. Anyways because I'm beginner level on this topic I don't know what should I do. I don't want to set up my phone again from the start after the update and I like root but I want my software to be latest as well. Is there any other way to install the update without deleting everything on phone?
Also if I download the latest software update can I flash it with TWRP without deleting anything on phone? Or back up my things with TWRP and install the software and use that back up to get everything back together again? Little bit help would be appreciated.
Click to expand...
Click to collapse
Questions about your Oneplus 5:
What's your current OxygenOS version?
What's the version you want to install?
For OxygenOS Open Beta just follow instructions in the first post here
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
For stable OxygenOS here in the first post
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
There's no need doing an ota update, cause rom files are mirrored on xda
strongst said:
Questions about your Oneplus 5:
What's your current OxygenOS version?
What's the version you want to install?
For OxygenOS Open Beta just follow instructions in the first post here
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
For stable OxygenOS here in the first post
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
There's no need doing an ota update, cause rom files are mirrored on xda
Click to expand...
Click to collapse
Thank you very much for answering. I tried dirty rom installing but twrp is not seeing my device's internal memory. I'm guessing that it's because oxygen os encrypts my phone when i enter the system after installation. It happened earlier as well when I tried to install oxygen os and root my phone and the time i tried to install pixel experience rom. I decided not to do clean installation as of now because I don't want to loose my data. (i certainly can get back everything on my phone but it usually takes few hours for that). Is there any other way to unencrypting the phone without wiping everything off?
My current oxygen os version is 9.0.2
I was trying to install 9.0.3.
Ebeninyo said:
Thank you very much for answering. I tried dirty rom installing but twrp is not seeing my device's internal memory. I'm guessing that it's because oxygen os encrypts my phone when i enter the system after installation. It happened earlier as well when I tried to install oxygen os and root my phone and the time i tried to install pixel experience rom. I decided not to do clean installation as of now because I don't want to loose my data. (i certainly can get back everything on my phone but it usually takes few hours for that). Is there any other way to unencrypting the phone without wiping everything off?
My current oxygen os version is 9.0.2
I was trying to install 9.0.3.
Click to expand...
Click to collapse
With which recovery and rom are you able to access your internal storage?
strongst said:
With which recovery and rom are you able to access your internal storage?
Click to expand...
Click to collapse
I've only tried using TWRP as my recovery, Pixel experience rom and oxygen os rom. The thing is because upon entering the phone after flashing a rom you can't access the internal storage of the phone with TWRP because phone encrypts itself. That means I can't dirty flash it and need to wipe everything out with TWRP then reboot TWRP again and install new rom after that flash magisk and reboot to system and set everything up from the scratch.
When I started this thread I didn't knew how to dirty flash a rom. Now I know and realize the problem I'm having is phone's encryption.
UPDATE:
I have used this guide to disable encryption on my phone. (I tried putting the link to the guide but for some reason i can't. It was on Custom Droid about how to remove one plus 5's encryption) I wiped everything on my phone with TWRP, installed the new OTA with Oxygen OS 9.0.3, flashed the file they provided on the guide, started system, went through steps and checked my encryption status and it was still encrypted.
Entered recovery again and wiped everything once more. Installed Magisk entered my system. (I was wiping everything down because otherwise TWRP wasn't able to see my device's storage), went through all the steps again. Installed Magisk's apk. Checked my root status. Everything was okay but still my phone was encrypted. Downloaded latest version of the Magisk. Wiped everything down once more installed Magisk. Rebooted into my system to see my phone's encryption was still there. At this point I gave up and started restoring my apps, data and everything with it.
Now I can't update my software whenever I want because TWRP won't see my device's storage because of encryption. Basically dirty flashing isn't available for me.
Have you guys tried and find a solution for this? If so please let me know. I would highly appreciate it.
Ebeninyo said:
UPDATE:
I have used this guide to disable encryption on my phone. (I tried putting the link to the guide but for some reason i can't. It was on Custom Droid about how to remove one plus 5's encryption) I wiped everything on my phone with TWRP, installed the new OTA with Oxygen OS 9.0.3, flashed the file they provided on the guide, started system, went through steps and checked my encryption status and it was still encrypted.
Entered recovery again and wiped everything once more. Installed Magisk entered my system. (I was wiping everything down because otherwise TWRP wasn't able to see my device's storage), went through all the steps again. Installed Magisk's apk. Checked my root status. Everything was okay but still my phone was encrypted. Downloaded latest version of the Magisk. Wiped everything down once more installed Magisk. Rebooted into my system to see my phone's encryption was still there. At this point I gave up and started restoring my apps, data and everything with it.
Now I can't update my software whenever I want because TWRP won't see my device's storage because of encryption. Basically dirty flashing isn't available for me.
Have you guys tried and find a solution for this? If so please let me know. I would highly appreciate it.
Click to expand...
Click to collapse
To prevent the OxygenOS to encrypt your phones storage you need to flash no verity patch before first boot(instructions). But coming from a custom rom requires to format internal storage, otherwise it won't work.
strongst said:
To prevent the OxygenOS to encrypt your phones storage you need to flash no verity patch before first boot(instructions). But coming from a custom rom requires to format internal storage, otherwise it won't work.
Click to expand...
Click to collapse
Can you be able link me that patch and instructions?
Ebeninyo said:
Can you be able link me that patch and instructions?
Click to expand...
Click to collapse
I already gave you the link to instructions how to flash stable oxygenOS in the 2nd post https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Just follow the CLEAN FLASH INSTRUCTIONS and on the 2nd last step you flash that patch which prevents you from encrypted storage.
strongst said:
I already gave you the link to instructions how to flash stable oxygenOS in the 2nd post https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Just follow the CLEAN FLASH INSTRUCTIONS and on the 2nd last step you flash that patch which prevents you from encrypted storage.
Click to expand...
Click to collapse
I've already tried the clean flash instructions. However I flashed the patch before magisk last time I tried it but it didn't work. Maybe because my order was wrong. Since I don't have much time right now. I'm going to try that once again tomorrow this time exactly like on the guide. I will let you know about the results.
Thank you very much again. I really appreciate your help.
Ebeninyo said:
I've already tried the clean flash instructions. However I flashed the patch before magisk last time I tried it but it didn't work. Maybe because my order was wrong. Since I don't have much time right now. I'm going to try that once again tomorrow this time exactly like on the guide. I will let you know about the results.
Thank you very much again. I really appreciate your help.
Click to expand...
Click to collapse
Remember to format the internal storage exactly written in the instructions and then flash the no verity patch, otherwise it will not work.
strongst said:
Remember to format the internal storage exactly written in the instructions and then flash the no verity patch, otherwise it will not work.
Click to expand...
Click to collapse
I was looking for other threads in this sub section. I saw this thread. https://forum.xda-developers.com/oneplus-5/help/twrp-encryption-t3889161
I flashed codeworkx twrp like you said on that thread. Now I can decrypt the phone. TWRP asks me for screen password and when I entered it, it showed me the internal memory. Now I can see my device's internal memory from recovery without wiping out everything.
My previous TWRP was twrp-3.2.3-0-cheeseburger.img
Installed twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger.img via twrp app on my phone like you said on that thread. Thank you very much again.
Ebeninyo said:
I was looking for other threads in this sub section. I saw this thread. https://forum.xda-developers.com/oneplus-5/help/twrp-encryption-t3889161
I flashed codeworkx twrp like you said on that thread. Now I can decrypt the phone. TWRP asks me for screen password and when I entered it, it showed me the internal memory. Now I can see my device's internal memory from recovery without wiping out everything.
My previous TWRP was twrp-3.2.3-0-cheeseburger.img
Installed twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger.img via twrp app on my phone like you said on that thread. Thank you very much again.
Click to expand...
Click to collapse
Cool:good:
I recently upgraded my OP5 from LOS 15.1 to 16.0. I Copied the LOS ROM and GAPPS zip file to the phone's storage and tried to install them with TWRP (3.2.1-1 I think). I got an error about unsupported zip format (treble), and I found that I needed to upgrade TWRP. I then flashed the latest (9.0) stock firmware for the device, rebooted to bootloader, and flashed TWRP 3.2.3-0 via fastboot.
At that point, I lost the ability to access storage from TWRP. I put TWRP in sideload mode and installed LOS 16.0 and GAPPs via sideload over the USB interface. With TWRP still unable to access storage, I flashed the stock recovery via fastboot. This completed successfully, but when I rebooted the phone into recovery it stopped and never re-started. Likewise booting into recovery with the power and volume buttons did not succeed.
I then re-flashed TWRP via fastboot, and found I could launch the recovery, but again with no storage access. Then I copied all the data from my SD card to my computer, and in TWRP I selected "Format Data". This succeeded, and after restoring my apps from google backup, I copied all the data back onto the SD card. Still TWRP cannot access the data.
It shows 0B contents, and all the directories are empty. If I try to mount, it fails, and if I try to select a storage type it's always stuck on internal and does not allow me to even select external. If I try to repair files, it fails also. I re-flashed TWRP several times, and it's always the same problem.
Well I guess there's TWRP and there's TWRP. I had been flashing the cheeseburger TWRP build downloaded with the Official TWRP app. I found this post that has links to other TWRP builds. I clicked the first link under Recoveries, and then navigated to this codeworkx cheeseburger build, and that works the way it's supposed to.
MidnightJava said:
Well I guess there's TWRP and there's TWRP. I had been flashing the cheeseburger TWRP build downloaded with the Official TWRP app. I found this post that has links to other TWRP builds. I clicked the first link under Recoveries, and then navigated to this codeworkx cheeseburger build, and that works the way it's supposed to.
Click to expand...
Click to collapse
Don't use official builds, only codeworkx or Blu spark for permanent usage are recommended
strongst said:
Don't use official builds, only codeworkx or Blu spark for permanent usage are recommended
Click to expand...
Click to collapse
Thanks, I'll certainly keep that in mind for the future. I'm curious, however, what is the purpose of official builds and the official TWRP app if they should never be used? Are you saying never use them with the One Plus phones in particular? Even then, they are advertising cheeseburger builds, which I assume will lead many to think that it will work on the OnePlus Five.
MidnightJava said:
Thanks, I'll certainly keep that in mind for the future. I'm curious, however, what is the purpose of official builds and the official TWRP app if they should never be used? Are you saying never use them with the One Plus phones in particular? Even then, they are advertising cheeseburger builds, which I assume will lead many to think that it will work on the OnePlus Five.
Click to expand...
Click to collapse
There's a reason when you have encryption issues and with newer builds that need comp check like oos pie.
After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?
MorneDJ said:
After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?
Click to expand...
Click to collapse
That's really strange.
What is your firmware date?
physwizz said:
That's really strange.
What is your firmware date?
Click to expand...
Click to collapse
I used this Firmware: XFA-A205FXXU2ASFA-20190803073130
MorneDJ said:
After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?
Click to expand...
Click to collapse
Reflash stock firmware via ODIN
then reinstall twrp
Or if you don't have a pc download a GSi in another phone with a SD card , extract the .img GSi file , put the sd card in your phone and flash it via Twrp to SYSTEM
Also use twrp 3.0.2-0 because newer versions are reported to have some problems
Imyou said:
Reflash stock firmware via ODIN
then reinstall twrp
Or if you don't have a pc download a GSi in another phone with a SD card , extract the .img GSi file , put the sd card in your phone and flash it via Twrp to SYSTEM
Also use twrp 3.0.2-0 because newer versions are reported to have some problems
Click to expand...
Click to collapse
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20
MorneDJ said:
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20
Click to expand...
Click to collapse
GSIs are here
https://forum.xda-developers.com/galaxy-a20/how-to/gsi-galaxy-a20-t3964546
Not sure about 3.0.2-0
I use this one
https://forum.xda-developers.com/ga...p-samsung-galaxy-a20-custom-recovery-t3955271
MorneDJ said:
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20
Click to expand...
Click to collapse
Gsi* - I recommend HavocOs
Very stable , everything works and no bugs so far.
Been using it as my daily driver for like 2 weeks!
And as for twrp you can retry with the one you have but I don't know if the problem will happen again.
I'm sorry I have lost the link that I found my twrp
OK. I have tried a few GSI roms, but all of them the same problem where the phone gets stuck in the bootloader. I finally just decided to go back to standard Samsung ROM, but my touchscreen is dead. I am currently setting it up using an OTG connector with a USB mouse ....
Any idea what I can try. Yesterday the touchscreen was working in TWRP, but, after numerous retries and flashing that is no longer working. I do not want to chuck the phone ...
MorneDJ said:
OK. I have tried a few GSI roms, but all of them the same problem where the phone gets stuck in the bootloader. I finally just decided to go back to standard Samsung ROM, but my touchscreen is dead. I am currently setting it up using an OTG connector with a USB mouse ....
Any idea what I can try. Yesterday the touchscreen was working in TWRP, but, after numerous retries and flashing that is no longer working. I do not want to chuck the phone ...
Click to expand...
Click to collapse
Touch screen not working.
I would take it back under warranty.
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
Did you get twrp installed? Wipe data by typing yes after flashing?
dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
You can follow this. If you want to install lineage os and want Google service make sure follow the "non gapp version" under installation method.
Havoc Flashing Notes for OnePlus 6 /6T from OOS 11 [Using TWRP Recovery]
1. Clean Flash : 2. Dirty Flash 3. Update oos base 1. Clean Flash : 🔊 Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; we're going to format the data partition and you're going to lose everything from internal storage. Basic requirements ○...
telegra.ph
Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my 6T.
dequadim said:
Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my
Click to expand...
Click to collapse
OnePlus definitely didn't do anything to make it harder. You need to fastboot boot twrp.img then flash the twrp installer zip. I'll attach both In next post. Reboot to recovery. Then install OOS, twrp installer, reboot to recovery. Install oos again, twrp installer again, reboot to recovery. Now install lineage, twrp installer, reboot to recovery. Install lineage again, twrp installer again, reboot to recovery. Factory reset and wipe data by typing yes. Boot to system
The img is for fastboot boot
The zip is for installing in twrp
Thanks for your reply.
I'm still wondering how to speed up the boot.
dequadim said:
Thanks for your reply.
I'm still wondering how to speed up the boot.
Click to expand...
Click to collapse
If everything is installed correctly it won't take long to boot
Brettroth said:
If everything is installed correctly it won't take long to boot
Click to expand...
Click to collapse
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?
If you can't fastboot boot into that twrp on a11 without crash dumping there is something really wrong
If you can't fastboot boot into that twrp on a11 without crash dumping there is something really
dequadim said:
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?
Click to expand...
Click to collapse
You sure you didn't try 3.6.0_9?
Clearing your cache might help with current boot. But once you install a new os everything will run smooth like it should
Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?
dequadim said:
Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?
Click to expand...
Click to collapse
That twrp version always will crash dump on a11. Use the one I sent
I followed these steps:
after having managed to make MSM Download Tool detect the phone in EDL mode, I proceeded by reinstalling OOS v9.0.13, after which I reconfigured the phone and restored the apps backup stored in my Google account.
Later, I don't remember the details well, I received the update notification for OOS v10 and later for OOs v11.1.2.2.
I don't remember exactly where the boot started to stretch, however this is more or less the process I followed to bring my 6T back to life.
Brettroth said:
That twrp version always will crash dump on a11. Use the one I sent
Click to expand...
Click to collapse
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(
dequadim said:
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(
Click to expand...
Click to collapse
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh
Brettroth said:
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh
Click to expand...
Click to collapse
Keep your finger crossed...
Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?
dequadim said:
Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?
Click to expand...
Click to collapse
Or you could use USB OTG. Or a PC and use adb sideload