Hello everyone,
I have a problem with my Le Pro 3. I installed an update a few days ago over the Lineage 15.1 settings. Like always the phone restarted in TWRP and everything went fine. But after that it did not reboot normally. Instead the Recovery mode was booted. At this point I should mention that I bought the phone used with Lineage 15.1 and have never flashed Android before.
So I read a lot (really a lot) and tried everything I could find in this forum until nothing worked anymore
Last chance I found in the forum was QFIL using FlashOne.
This worked fine (after a few tries). After that I could reinstall TWRP (tried different versions) using TOOL ALL IN ONE and enter Recovery Mode again.
After bringing it back to life I decided to install Lineage 15.1 again. So first formatting Internal Storage, then wiping everything and give it a go. No problem during installation but phone boots in Recovery Mode again.
So nothing new. Next try: Installing the latest versions of TWRP and Lineage 16.
I started again with FlashOne to clean everything up. Installed TWRP version from the Lineage 16 thread.
But I was not able to format Internal Storage: "Failed to mount '\vendor' (invalid argument)"
Okay. Tried to install Lineage 16 anyways. Again 2 errors: "Updater process ended with ERROR: 7 Error installing zip file '\sdcard.......zip' " AND "Failed to mount '\vendor' (invalid argument)".
At the moment I am not sure what to do because I am really new to the topic. I read a lot and tried everything.
Is this a possible hardware problem or did I do something wrong/ miss anything?
Would love to use my Le Pro 3 again. Love this phone.
Thanks for any advice,
Max---Power
UPDATE:
Managed to install the latest TWRP 3.2.3 TREBLE LP3 in ALL In ONE TOOL and after that I could format and install Lineage 16 without errors.
When restarting the phone TWRP does not say "no OS on phone", so I think Lineage is ready to use.
But after restart same issue: Boots in Recovery Mode.
Please help
Okay. Still no progress.
Tried different Firmwares and started all over again with FlashOne2.0.
ATM I managed to install TWRP with Magisk over TOOL ALL IN ONE , then Firmware 20S, then a partitions.zip and then Lineage 16.
No Errors, everything was okay. Vendor is mountable and TWRP does not say "No OS installed".
But it still boots to Recovery Mode.
Can I check somehow if Lineaoge OS ist really installed over the FileManager in TWRP?
Or any other tips to verify the Installation?
Max---Power said:
Okay. Still no progress.
Tried different Firmwares and started all over again with FlashOne2.0.
ATM I managed to install TWRP with Magisk over TOOL ALL IN ONE , then Firmware 20S, then a partitions.zip and then Lineage 16.
No Errors, everything was okay. Vendor is mountable and TWRP does not say "No OS installed".
But it still boots to Recovery Mode.
Can I check somehow if Lineaoge OS ist really installed over the FileManager in TWRP?
Or any other tips to verify the Installation?
Click to expand...
Click to collapse
First, you didn't need to use Qfil for this issue.
Okay, I am leaving my house at this very moment so I can only give you a few minutes. But will provide more details in a few hours.
Potential Quick Fix
If you can get into TWRP : Use my Recovery to restore your phone.
https://forum.xda-developers.com/showpost.php?p=75021582
Instructions are on that page
Basics
It has to be placed on your SD card and unpacked. Use Twrp to restore and select all options except for EFS, Your EFS is not damaged and you would only want to change this in a worse case scenario.
After restoring the recovery, you will have an older version of TWRP, root and EUI.
From there you can start over.
Thank you very much for this quick guide.
You made my day already!
So I started all over again with the following steps:
1. QFIL via FlashOne
after that Windows says: You have to format the drive
2. TWRP (3.2.2 LP3) via TOOL ALL IN ONE with Magisk 17.3
3. TWRP-> Wipe-> Format data to get the full volume of the drive
4. Reboot to Recovery to get TWRP Folder created
5. Copied Backup to sdcard\TWRP
6. Wipe Dalvik, System, Cache and Data
4. TWRP-> Restore-> extracted folder
5. Everything except EFS
6. Reboot-> Recovery
7. Reboot-> System
TWRP asks to install the app, so I guess there is an OS.
Even if I reboot System the Phone starts Recovery Mode.
Problem unfortunately not solved :crying:
Max---Power said:
Thank you very much for this quick guide.
You made my day already!
So I started all over again with the following steps:
1. QFIL via FlashOne
after that Windows says: You have to format the drive
2. TWRP (3.2.2 LP3) via TOOL ALL IN ONE with Magisk 17.3
3. TWRP-> Wipe-> Format data to get the full volume of the drive
4. Reboot to Recovery to get TWRP Folder created
5. Copied Backup to sdcard\TWRP
6. Wipe Dalvik, System, Cache and Data
4. TWRP-> Restore-> extracted folder
5. Everything except EFS
6. Reboot-> Recovery
7. Reboot-> System
TWRP asks to install the app, so I guess there is an OS.
Even if I reboot System the Phone starts Recovery Mode.
Problem unfortunately not solved :crying:
Click to expand...
Click to collapse
When you go into TWRP, Reboot to Recovery, yes check boxes to install the TWRP manager. When you boot into TWRP > do not choose read only mode.
You may have an encryption issue, which can be resolved but try this first.
Once back in Twrp, go to restore, you should see the folder that stasrt with 1970-xxx.xxx etc
Choose that
No you will see choose Partitions to restore choose everything except for EFS > then select Swipe at the bottom.
\When that is finished reboot to Twrp ,
You are now back on a clean version of EUI with Root and Twrp.
Now at this point you need to update to the latest version of TWRP ( only the version that is compatible for your device. ) Flash new TWRP and Reboot to Recovery > At this point , using a OTG usb drive would be the easiest way to go forward.
If you don't have one , Place your Rom in the SD storage, along with Magisk 17.3 and a compatible Gapps ( choose something that is still supported such as AICP of Lineage)
Flash the Rom by clicking install, next flash Gapps and then Magisk > Reboot to recovery, then reboot to system > Finished
If you are still having issues after all of this> Send me a PM and I can help you over the phone/team viewer as I just did for Roger. His similar issue is resolved and he is now using Android 9.0
Right now its 7:00 pm EST, I will not be available until 10 pm EST
---------- Post added at 08:14 PM ---------- Previous post was at 08:13 PM ----------
Max---Power said:
Thank you very much for this quick guide.
You made my day already!
So I started all over again with the following steps:
1. QFIL via FlashOne
after that Windows says: You have to format the drive
2. TWRP (3.2.2 LP3) via TOOL ALL IN ONE with Magisk 17.3
3. TWRP-> Wipe-> Format data to get the full volume of the drive
4. Reboot to Recovery to get TWRP Folder created
5. Copied Backup to sdcard\TWRP
6. Wipe Dalvik, System, Cache and Data
4. TWRP-> Restore-> extracted folder
5. Everything except EFS
6. Reboot-> Recovery
7. Reboot-> System
TWRP asks to install the app, so I guess there is an OS.
Even if I reboot System the Phone starts Recovery Mode.
Problem unfortunately not solved :crying:
Click to expand...
Click to collapse
Also click under my post and click reply, otherwise, I will not get your message. To PM click my name and you will see the option to send a message.
tsongming said:
When you go into TWRP, Reboot to Recovery, yes check boxes to install the TWRP manager. When you boot into TWRP > do not choose read only mode.
You may have an encryption issue, which can be resolved but try this first.
Once back in Twrp, go to restore, you should see the folder that stasrt with 1970-xxx.xxx etc
Choose that
No you will see choose Partitions to restore choose everything except for EFS > then select Swipe at the bottom.
\When that is finished reboot to Twrp ,
You are now back on a clean version of EUI with Root and Twrp.
Now at this point you need to update to the latest version of TWRP ( only the version that is compatible for your device. ) Flash new TWRP and Reboot to Recovery > At this point , using a OTG usb drive would be the easiest way to go forward.
If you don't have one , Place your Rom in the SD storage, along with Magisk 17.3 and a compatible Gapps ( choose something that is still supported such as AICP of Lineage)
Flash the Rom by clicking install, next flash Gapps and then Magisk > Reboot to recovery, then reboot to system > Finished
If you are still having issues after all of this> Send me a PM and I can help you over the phone/team viewer as I just did for Roger. His similar issue is resolved and he is now using Android 9.0
Right now its 7:00 pm EST, I will not be available until 10 pm EST
---------- Post added at 08:14 PM ---------- Previous post was at 08:13 PM ----------
Also click under my post and click reply, otherwise, I will not get your message. To PM click my name and you will see the option to send a message.
Click to expand...
Click to collapse
Thank you very much for your effort! I like the way you describe and hope this will work out.
I did all you described. First part is up until my point 6.
I keep on numbering. Here is what I did afterwards:
8. TWRP-> Install-> twrp-3.2.3-0-20181031-codeworkx-zl1.img-> Recovery selected
9. Reboot-> Recovery (Version is the updated one)
10. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage.....zip'
Failed to mount '/vendor' (invalid argument)
-> I got that already. I have to install partition.zip
11. Install-> partition.zip
12. Wipe Dalvik, System, Cache and Data
13. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage.....zip'
-> Told you I read a lot: This could be the wrong Firmware
14. Install-> firmware-20S-X720-le_zl1.zip
15. Reboot Recovery
16. Wipe Dalvik, System, Cache and Data
17. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
-> finally without errors
18. Install-> Magisk-v17.3.zip
19. Install-> open_gapps-arm64-9.0-pico-20181125.zip
20. Reboot Recovery
Install System App? -> YES
7. Reboot System
Same as before. Not booting to System. TWRP starts.
Could it be the encryptionm issue? Or some other ideas?
If you want you can reply here, so everyone can read.
If it gets too complicated we cann arrange Skype or TeamViewer. Problem with that is that I live in Europe -> MEZ. It is 5:30PM right now.
Max---Power said:
Thank you very much for your effort! I like the way you describe and hope this will work out.
I did all you described. First part is up until my point 6.
I keep on numbering. Here is what I did afterwards:
8. TWRP-> Install-> twrp-3.2.3-0-20181031-codeworkx-zl1.img-> Recovery selected
9. Reboot-> Recovery (Version is the updated one)
10. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage.....zip'
Failed to mount '/vendor' (invalid argument)
-> I got that already. I have to install partition.zip
11. Install-> partition.zip
12. Wipe Dalvik, System, Cache and Data
13. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage.....zip'
-> Told you I read a lot: This could be the wrong Firmware
14. Install-> firmware-20S-X720-le_zl1.zip
15. Reboot Recovery
16. Wipe Dalvik, System, Cache and Data
17. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
-> finally without errors
18. Install-> Magisk-v17.3.zip
19. Install-> open_gapps-arm64-9.0-pico-20181125.zip
20. Reboot Recovery
Install System App? -> YES
7. Reboot System
Same as before. Not booting to System. TWRP starts.
Could it be the encryption issue? Or some other ideas?
If you want you can reply here, so everyone can read.
If it gets too complicated we can arrange Skype or TeamViewer. Problem with that is that I live in Europe -> MEZ. It is 5:30PM right now.
Click to expand...
Click to collapse
Okay , there seems to be a Brand NEW bug with the most recent version of TWRP ( your Vendor issue) I saw this issue yesterday with someone else that I helped privately
Use this version of TWRP instead
https://forum.xda-developers.com/le-pro3/development/recovery-twrp-3-x-p-codeworkx-t3844528
If so reason, you get the same error use an old version of non treble TWRP first and then the one from my link.
This will absolutely fix this issue, so that you can go forward.
Edit after re-reading your post -
On point 6 you mentioned wipe> Format resolves encryption, wipe does not.
Wipe> Format> type Yes> Wipe>Reboot to Recovery> Advanced Wipe> Reboot to Recovery
You do not need the partition zip files, that is for an outdated version of TWRP
Try the old version of TWRP first, install the Rom> Gapps> Magisk> Reboot to Recovery
Flash new Treble TWRP to the Recovery partition. > Issue should be resolved
tsongming said:
Okay , there seems to be a Brand NEW bug with the most recent version of TWRP ( your Vendor issue) I saw this issue yesterday with someone else that I helped privately
Use this version of TWRP instead
https://forum.xda-developers.com/le-pro3/development/recovery-twrp-3-x-p-codeworkx-t3844528
If so reason, you get the same error use an old version of non treble TWRP first and then the one from my link.
This will absolutely fix this issue, so that you can go forward.
Edit after re-reading your post -
On point 6 you mentioned wipe> Format resolves encryption, wipe does not.
Wipe> Format> type Yes> Wipe>Reboot to Recovery> Advanced Wipe> Reboot to Recovery
You do not need the partition zip files, that is for an outdated version of TWRP
Try the old version of TWRP first, install the Rom> Gapps> Magisk> Reboot to Recovery
Flash new Treble TWRP to the Recovery partition. > Issue should be resolved
Click to expand...
Click to collapse
Hello and thanks for the quick help!
That is the link I got the orther TWRP from I guess.
I now tried the oldest Version listed there, did not work.
The second latest does. (twrp-3.2.3-0-20180919-codeworkx-zl1.img)
I like numbers
22. Install-> twrp-3.2.1-0-20180413-codeworkx-zl1.img-> Recovery selected
23. Reboot-> Recovery
24. Wipe Dalvik, System, Cache and Data
25. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
E:String resource 'zip_compatible_err' not found. Using default value. Zip Treble compatibility error!
Error installing zip file '/sdcard/lineage....zip'
->This is a new one. Lets try a newer TWRP-version
26. Install-> twrp-3.2.3-0-20180919-codeworkx-zl1.img-> Recovery selected
27. Reboot-> Recovery
28. Wipe Dalvik, System, Cache and Data
29. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
30. Install-> open_gapps-arm64-9.0-pico-20181125.zip
31. Install-> Magisk-v17.3.zip
32. Reboot Recovery
Install System App? -> YES
33. Reboot System
Same issue again. Rebooting in Recovery Mode.
I am going crazy. Did I do anything wrong?
Hope you are not going crazy
---
Saw your edit too late, so here is my EDIT:
After I reached point 33 I did the following:
34. Wipe> Format> type Yes> Wipe>Reboot to Recovery> Advanced Wipe> Reboot to Recovery
35. Install-> twrp-3.2.1-0-20180413-codeworkx-zl1.img-> Recovery selected
36. Reboot Recovery
37. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Same Error like before. So new TWRP...
38. Install-> twrp-3.2.3-0-20180919-codeworkx-zl1.img-> Recovery selected
39. Reboot Recovery
40. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
41. Install-> open_gapps-arm64-9.0-pico-20181125.zip
42. Install-> Magisk-v17.3.zip
43. Reboot Recovery
Install System App? -> YES
44. Reboot System
Again: going directly into Recovery Mode
Max---Power said:
Hello and thanks for the quick help!
That is the link I got the orther TWRP from I guess.
I now tried the oldest Version listed there, did not work.
The second latest does. (twrp-3.2.3-0-20180919-codeworkx-zl1.img)
I like numbers
22. Install-> twrp-3.2.1-0-20180413-codeworkx-zl1.img-> Recovery selected
23. Reboot-> Recovery
24. Wipe Dalvik, System, Cache and Data
25. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
E:String resource 'zip_compatible_err' not found. Using default value. Zip Treble compatibility error!
Error installing zip file '/sdcard/lineage....zip'
->This is a new one. Lets try a newer TWRP-version
26. Install-> twrp-3.2.3-0-20180919-codeworkx-zl1.img-> Recovery selected
27. Reboot-> Recovery
28. Wipe Dalvik, System, Cache and Data
29. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
30. Install-> open_gapps-arm64-9.0-pico-20181125.zip
31. Install-> Magisk-v17.3.zip
32. Reboot Recovery
Install System App? -> YES
33. Reboot System
Same issue again. Rebooting in Recovery Mode.
I am going crazy. Did I do anything wrong?
Hope you are not going crazy
---
Saw your edit too late, so here is my EDIT:
After I reached point 33 I did the following:
34. Wipe> Format> type Yes> Wipe>Reboot to Recovery> Advanced Wipe> Reboot to Recovery
35. Install-> twrp-3.2.1-0-20180413-codeworkx-zl1.img-> Recovery selected
36. Reboot Recovery
37. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Same Error like before. So new TWRP...
38. Install-> twrp-3.2.3-0-20180919-codeworkx-zl1.img-> Recovery selected
39. Reboot Recovery
40. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
41. Install-> open_gapps-arm64-9.0-pico-20181125.zip
42. Install-> Magisk-v17.3.zip
43. Reboot Recovery
Install System App? -> YES
44. Reboot System
Again: going directly into Recovery Mode
Click to expand...
Click to collapse
So there is still a problem with your storage, did you ever change the partition type from Ext4 to F2FS? I could be wrong but I am going to guess that maybe you did> Since a format should have resolved this issue, yesterday. F2FS is a bad idea and there is no benefit. > so change it back to EXT4 > Of course only if you did in fact change the format type.
Don't worry too much, you are not the first person that this has happened to, and there will be someone else with issue next week.
As far as numbers, how about asterisks, I typed similar instruction out a hundred times within the Leeco threads, search and you will see that I used instructions with numbers a thousand times already so I am switching it up :silly:
Try this:
Click Mount , make sure that System, Vendor, Cache, Data, are selected > Click Home key
Format storage once again , Reboot to Recovery, Click Advanced> Click File Manager > What do you see here?
It should only show a TWRP folder and nothing else > If you see more that folder the storage is not getting formatted.
If you only see the TWRP Folder
Flash Rom Twice, Flash Magisk> Reboot to Recovery, ( check Boxes)
Boot to system, and see If it boots. If it boots to system > Go back to Recovery > wipe cache > Flash Gapps> Boot to system
Still have an issue
Do Full Wipe ... Yes Again...unfortunately.
flash Rom
flash Magisk
flash dm-verity & force encryption disabler : http://zackptg5.com/android.php#disverfe
Flash Gapps
Reboot to Recovery > Wipe cache ( only cache) Reboot to system > Did this work? Yes, thats awesome that will be $5.99
Oh my God, you still have an Issue
Let me know, there is still other things that we can try.
tsongming said:
So there is still a problem with your storage, did you ever change the partition type from Ext4 to F2FS? I could be wrong but I am going to guess that maybe you did> Since a format should have resolved this issue, yesterday. F2FS is a bad idea and there is no benefit. > so change it back to EXT4 > Of course only if you did in fact change the format type.
Don't worry too much, you are not the first person that this has happened to, and there will be someone else with issue next week.
As far as numbers, how about asterisks, I typed similar instruction out a hundred times within the Leeco threads, search and you will see that I used instructions with numbers a thousand times already so I am switching it up :silly:
Try this:
Click Mount , make sure that System, Vendor, Cache, Data, are selected > Click Home key
Format storage once again , Reboot to Recovery, Click Advanced> Click File Manager > What do you see here?
It should only show a TWRP folder and nothing else > If you see more that folder the storage is not getting formatted.
If you only see the TWRP Folder
Flash Rom Twice, Flash Magisk> Reboot to Recovery, ( check Boxes)
Boot to system, and see If it boots. If it boots to system > Go back to Recovery > wipe cache > Flash Gapps> Boot to system
Still have an issue
Do Full Wipe ... Yes Again...unfortunately.
flash Rom
flash Magisk
flash dm-verity & force encryption disabler : http://zackptg5.com/android.php#disverfe
Flash Gapps
Reboot to Recovery > Wipe cache ( only cache) Reboot to system > Did this work? Yes, thats awesome that will be $5.99
Oh my God, you still have an Issue
Let me know, there is still other things that we can try.
Click to expand...
Click to collapse
I did not change anything at the format of Internal Storage. Maybe it was done by the previous owner?
I tried cheking over Wipe-> Advanced Wipe-> Select Internal Storage-> Repair or change File System
But it says "Invalid partition selected" and deselects Internal Storage. Dont know if that is nomal.
45. Mount-> Select System, Vendor, Cache and Data-> Home key clicked
46. Wipe-> Format Data-> YES (prompt says "Formatting Data using make_ext4fs" so I guess thats right)
47. Reboot Recovery
48. Advanced-> Filemanager
In sdcard is just TWRP-folder which is empty.
49. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
50. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
51. Install-> Magisk-v17.3.zip
52. Reboot Recovery
53. Reboot System
Boots into Recovery
So once again!
54. Wipe-> Format Data
55. Reboot Recovery
56. Wipe Dalvik, System, Cache and Data
57. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
58. Install-> Magisk-v17.3.zip
59. Install-> Disable_Dm-Verity_ForceEncrypt_11.26.2018.zip
60. Install-> open_gapps-arm64-9.0-pico-20181125.zip
61. Reboot Recovery
62. Wipe Cache
63. Reboot System
Boots into Recovery
I am getting crazy...
I am doing this step by step with numbering that I (and everyone who has no clue) can understand what I do.
Dont worry about your 5.99$... If we can get this going I will name my firstborn child after you, if you want
Max---Power said:
I did not change anything at the format of Internal Storage. Maybe it was done by the previous owner?
I tried cheking over Wipe-> Advanced Wipe-> Select Internal Storage-> Repair or change File System
But it says "Invalid partition selected" and deselects Internal Storage. Dont know if that is nomal.
45. Mount-> Select System, Vendor, Cache and Data-> Home key clicked
46. Wipe-> Format Data-> YES (prompt says "Formatting Data using make_ext4fs" so I guess thats right)
47. Reboot Recovery
48. Advanced-> Filemanager
In sdcard is just TWRP-folder which is empty.
49. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
50. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
51. Install-> Magisk-v17.3.zip
52. Reboot Recovery
53. Reboot System
Boots into Recovery
So once again!
54. Wipe-> Format Data
55. Reboot Recovery
56. Wipe Dalvik, System, Cache and Data
57. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
58. Install-> Magisk-v17.3.zip
59. Install-> Disable_Dm-Verity_ForceEncrypt_11.26.2018.zip
60. Install-> open_gapps-arm64-9.0-pico-20181125.zip
61. Reboot Recovery
62. Wipe Cache
63. Reboot System
Boots into Recovery
I am getting crazy...
I am doing this step by step with numbering that I (and everyone who has no clue) can understand what I do.
Dont worry about your 5.99$... If we can get this going I will name my firstborn child after you, if you want
Click to expand...
Click to collapse
Okay this one needs to be brief. Because, I only have a few minute at the moment.
First, I am assuming that you have tried other Roms such as a Nougat Rom. Nougat Gapps etc.
Yes? Next.
Download the All in One tool (AIT) ,
https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
Ensure it's up to date and not blocked by your firewall.
Use the AIT, to double check that the bootloader is still unlocked. Next, use the advanced option to remove encrypted data/wipe phone.
Use AIT to download stock Rom, to fully restore phone to stock, which should also repair any partition damage
After, phone has been restored, you can check to see that Leeco recovery has also been restored.
Next, boot to and setup the system, including through basic Google. Setup.
If you can do all of those steps to then you should surely be able to go forward and prepare the phone for a custom Rom.
Hopefully, this will finally get it.
Well that was longer than intended, and I didn't check for typos. Do look past those.
Sent from my LEX727 using XDA Labs
tsongming said:
Okay this one needs to be brief. Because, I only have a few minute at the moment.
First, I am assuming that you have tried other Roms such as a Nougat Rom. Nougat Gapps etc.
Yes? Next.
Download the All in One tool (AIT) ,
https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
Ensure it's up to date and not blocked by your firewall.
Use the AIT, to double check that the bootloader is still unlocked. Next, use the advanced option to remove encrypted data/wipe phone.
Use AIT to download stock Rom, to fully restore phone to stock, which should also repair any partition damage
After, phone has been restored, you can check to see that Leeco recovery has also been restored.
Next, boot to and setup the system, including through basic Google. Setup.
If you can do all of those steps to then you should surely be able to go forward and prepare the phone for a custom Rom.
Hopefully, this will finally get it.
Well that was longer than intended, and I didn't check for typos. Do look past those.
Sent from my LEX727 using XDA Labs
Click to expand...
Click to collapse
First: Thank you very much for your effort. Don't be stressed, I have time. No need to hurry with a reply!
Yes I have tried Oreo before. But lets do that again:
64. Install-> lineage-15.1-20181129-nightly-zl1-signed.zip
65. Install-> Magisk-v17.3.zip
66. Install-> open_gapps-arm64-8.1-pico-20181129.zip
67. Reboot Recovery
68. Reboot System
Boots into Recovery
Lets try AIO:
(numbering from 1 because I can only count up to 70)
My X720 (64GB/6GB) is detected as LEX727, ist that alright?
1. Bootloader Status
Unlocked
2. Erse All Data / Decrypt Internal Storage
3. Flash Factory Image-> LE_ZL1_LEX720-CN-FN-WAXCNFN5902012312S-5.9.020S-FASTBOOT.zip
with Wipe all Data and Reboot after Flash
-> it reboots, vibrates two times and boots Recovery Mode (EUI with chinese checkboxes)
4. Long press Powerbutton
Boots into Recovery
At this point AIO says "no devices found" and the phone is not listed in Windows Explorer anymore.
Tried this before already. At this point I always used QFIL.
Any other plans, or am I screwed?
Max---Power said:
First: Thank you very much for your effort. Don't be stressed, I have time. No need to hurry with a reply!
Yes I have tried Oreo before. But lets do that again:
64. Install-> lineage-15.1-20181129-nightly-zl1-signed.zip
65. Install-> Magisk-v17.3.zip
66. Install-> open_gapps-arm64-8.1-pico-20181129.zip
67. Reboot Recovery
68. Reboot System
Boots into Recovery
Lets try AIO:
(numbering from 1 because I can only count up to 70)
My X720 (64GB/6GB) is detected as LEX727, ist that alright?
1. Bootloader Status
Unlocked
2. Erse All Data / Decrypt Internal Storage
3. Flash Factory Image-> LE_ZL1_LEX720-CN-FN-WAXCNFN5902012312S-5.9.020S-FASTBOOT.zip
with Wipe all Data and Reboot after Flash
-> it reboots, vibrates two times and boots Recovery Mode (EUI with chinese checkboxes)
4. Long press Powerbutton
Boots into Recovery
At this point AIO says "no devices found" and the phone is not listed in Windows Explorer anymore.
Tried this before already. At this point I always used QFIL.
Any other plans, or am I screwed?
Click to expand...
Click to collapse
Within the EUI Recovery: Reset the phone and then try boot.
You would not be able to access the phone from the PC until the system is setup. However, this should have fixed the issue if if was merely encryption or corruption.
Stockware does not resolve it and restoring my full backup recovery doesn't solve the issue. Then you could try flash the bootloader again, after using Qfil. Or try my Recovery one more time: https://forum.xda-developers.com/showpost.php?p=75021582
Outside of that we are beginning to run out of options. This issue is highly unusual and I now also talking to other people via PM with a very similar issue. A rare coincidence? These issues are always fixed with everything we have tried. Unfortunately, it could be a hardware issue.
tsongming said:
Within the EUI Recovery: Reset the phone and then try boot.
You would not be able to access the phone from the PC until the system is setup. However, this should have fixed the issue if if was merely encryption or corruption.
Stockware does not resolve it and restoring my full backup recovery doesn't solve the issue. Then you could try flash the bootloader again, after using Qfil. Or try my Recovery one more time: https://forum.xda-developers.com/showpost.php?p=75021582
Outside of that we are beginning to run out of options. This issue is highly unusual and I now also talking to other people via PM with a very similar issue. A rare coincidence? These issues are always fixed with everything we have tried. Unfortunately, it could be a hardware issue.
Click to expand...
Click to collapse
Within EUI the upper checkbox is update and the lower is reset, right?
So select the lower checkbox and click the right button.
Then it displays and error in red:"*chinesesymbols*Data*chinesesymbols*"
So probably something is wrong with Data...
I click the chinese OK and it goes on with wiping Cache.
Then I return to main screen and click the left button for reboot.
Phone vibrates twice and goes back into Recovery.
So once again from the beginning:
1. QFIL via FlashOne (zl1_qfil.zip)
2. AIO Bootloader Status: Unlocked
3. AIO Lock Boatloader
4. AIO Unlock Boatloader
ERROR:
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
5. command in adb: fastboot oem unlock-go
6. AIO Unlock Boatloader
Device already: unlocked!
This does not sound right.. Any clue?
If we cant get it fixed make a suggestion for a new (used) phone, pls
Should I buy LeEco again? Only had it for 4-5 month now.
Max---Power said:
Within EUI the upper checkbox is update and the lower is reset, right?
So select the lower checkbox and click the right button.
Then it displays and error in red:"*chinesesymbols*Data*chinesesymbols*"
So probably something is wrong with Data...
I click the chinese OK and it goes on with wiping Cache.
Then I return to main screen and click the left button for reboot.
Phone vibrates twice and goes back into Recovery.
So once again from the beginning:
1. QFIL via FlashOne (zl1_qfil.zip)
2. AIO Bootloader Status: Unlocked
3. AIO Lock Boatloader
4. AIO Unlock Boatloader
ERROR:
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
5. command in adb: fastboot oem unlock-go
6. AIO Unlock Boatloader
Device already: unlocked!
This does not sound right.. Any clue?
If we cant get it fixed make a suggestion for a new (used) phone, pls
Should I buy LeEco again? Only had it for 4-5 month now.
Click to expand...
Click to collapse
After everything that has been done, I feel that you without a doubt have a hardware issue, and unfortunately it is very likely the main board. It would be cheaper to buy another phone.
Ordinarily, I would say absolutely get another Leeco, I found a Brand new X727 on Ebay for $175. But, the more I think about it I would suggest moving on to another phone from a company that is still in business. Technically, Leeco still exists, but I doubt that they will do anything new with phones for a while. The have lost face, and it would be dificult for them to repair trust in their home country and attract investors.
As far as getting something else. I guess it depends on your budget. If you want stay around $200 I would consider the Xiaomi A2, Its plenty power enough, looks expensive and modern. Has plenty of Ram, HD space, and the battery is big enough. Plus it comes bloat free.
If you can spend $300 to $350 - Maybe consider the Xiaomi Poco F1 , Mi 8 or mi8 Lite. All stellar phones. The Mi8 is probably the overall best of the 3.
Hello,
I found this guy that had my similar problem,
I hope it's not my main board.
I have a x720
I tried to flash AICP 9.0 over dirtly ove the prevous ROM,
Got error 7 and /vendor unable to mount.
I donwloaded stock rom from LEECO but before that I've done a "Erase all data and decrypt internal storage" with "MAURO ALL IN TOLL", now that i think about it, very dumb move, anyway.
When I try to flash the LEECO stock rom i get those errors + Unable to mount /system
Hope anyone can help me.
fiume97 said:
Hello,
I found this guy that had my similar problem,
I hope it's not my main board.
I have a x720
I tried to flash AICP 9.0 over dirtly ove the prevous ROM,
Got error 7 and /vendor unable to mount.
I donwloaded stock rom from LEECO but before that I've done a "Erase all data and decrypt internal storage" with "MAURO ALL IN TOLL", now that i think about it, very dumb move, anyway.
When I try to flash the LEECO stock rom i get those errors + Unable to mount /system
Hope anyone can help me.
Click to expand...
Click to collapse
Your issue is not the board or even a big deal at all.
Can you boot into TWRP Recovery ( by pressing the volume up and power? ) If not go to the all in one thread and read the instructions
You can use the All in One tool to flash TWRP, Once TWRP has been installed,
Boot to Recovery
Format Storage
Type “Yes.”
afterwards select Wipe > Factory Reset
Now Reboot to Recovery > Check Boxes for TWRP Manager installation if you see them
Now you can try Installing your Rom, Gapps, and Magisk > Reboot to Recovery again /Check Boxes
Clear Cache ( Not Dalvik)
Reboot to System > You should now be fine.
Related
Hello, I have N9005 with KK bootloader, yesterday I installed TWRP and got the message below. I still can flash ROMs (actually installed Omega with no problem). Later I tried CWM and Philz, but get the same message. Even if I try to manually mount cache it does not work. How to solve this issue? I would be glad if anyone can help. And another thing, when I installed Omega ROM in aroma and chose custom kernel, phone did not boot, with the message on boot screen was something about ''selinux kernel not ...''. Then I installed again with stock kernel and phone booted normally...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anyone with the same issue, how did you solve it? Is there a partition corruption involved?
McIringer said:
Anyone with the same issue, how did you solve it? Is there a partition corruption involved?
Click to expand...
Click to collapse
Flash latest TWRP
-Reboot into Recovery.
-Go to "Wipe".
-Go to "Advanced Wipe".
-Choose "Cache".
-Go to "Repair or Change Filesystem".
-Press "Change Filesystem".
-Press "EXT4".
-Reboot system and wait until Android completely boot up.
-Reboot into recovery to check if problem still persists.
-Go to "Wipe"
-Go to "Advanced Wipe"
-Choose "Cache"
-Press Wipe and when finished, post how long it took to finish cache wipe.
Thank you very much for the instructions. Actually I somehow managed to solve the issue few minutes ago. I just used wipe cache function, left the phone for about 10 min and it did it. After that there was no message about can't mount cache anymore and wiping cache takes only few seconds from then on. Hope it is solved... Or should I still do what you suggested, fixing file system... Is it safer to use TWRP or CWM based recovery. Is it just personal preference?
One more thing if I may, Do you happen to know if there is problem with custom kernels and booting ROMs on Note 3... With custom omega kernel phone did not boot, when using stock kernel it did without problem...
McIringer said:
Thank you very much for the instructions. Actually I somehow managed to solve the issue few minutes ago. I just used wipe cache function, left the phone for about 10 min and it did it. After that there was no message about can't mount cache anymore and wiping cache takes only few seconds from then on. Hope it is solved... Or should I still do what you suggested, fixing file system... Is it safer to use TWRP or CWM based recovery. Is it just personal preference?
One more thing if I may, Do you happen to know if there is problem with custom kernels and booting ROMs on Note 3... With custom omega kernel phone did not boot, when using stock kernel it did without problem...
Click to expand...
Click to collapse
No, no need to to it anymore. Glad you got your phone working again. If it happens again, try the steps I mentioned in my first post. I'd be happy if you then could report whether it worked or not. I can only guess if it's just about personal preference. Both recovery systems do basically the same with TWRP being the most advanced and easy to use. I use TWRP because of the many options and most importantly password protection to enter recovery. But be aware that some ROMs are only flashable with certain recovery systems. I can't tell the reason behind it.
I'm sorry, I can't tell you why your phone didn't boot up on Omega kernel. The best thing you can do is re-read OP and ask in the dedicated threads for help.
Thank you very much for being helpful!
Greetings from Slovenia!
Can anyone help i get error when try wipe dalvik cache & cache i get this E:Unable to mount '/cache im on latest version of TWRP
Thans for the solution
hey thanx.... this method worked for me.....!!! u know i was so tensed that i thought that now i have lost my chance to live.. !!!
but anyways thnx...
nitrous² said:
Flash latest TWRP
-Reboot into Recovery.
-Go to "Wipe".
-Go to "Advanced Wipe".
-Choose "Cache".
-Go to "Repair or Change Filesystem".
-Press "Change Filesystem".
-Press "EXT4".
-Reboot system and wait until Android completely boot up.
-Reboot into recovery to check if problem still persists.
-Go to "Wipe"
-Go to "Advanced Wipe"
-Choose "Cache"
-Press Wipe and when finished, post how long it took to finish cache wipe.
Click to expand...
Click to collapse
Same issue, solved with this method, 2 secs for wiping after the method, thank you man
try to follow my thread, is the same issue. maybe we get the solution, i'm close, very close
Thank you, it works on TWRP YU Yuphoria.
:good:
nitrous² said:
Flash latest TWRP
-Reboot into Recovery.
-Go to "Wipe".
-Go to "Advanced Wipe".
-Choose "Cache".
-Go to "Repair or Change Filesystem".
-Press "Change Filesystem".
-Press "EXT4".
-Reboot system and wait until Android completely boot up.
-Reboot into recovery to check if problem still persists.
-Go to "Wipe"
-Go to "Advanced Wipe"
-Choose "Cache"
-Press Wipe and when finished, post how long it took to finish cache wipe.
Click to expand...
Click to collapse
nitrous² said:
Flash latest TWRP
-Reboot into Recovery.
-Go to "Wipe".
-Go to "Advanced Wipe".
-Choose "Cache".
-Go to "Repair or Change Filesystem".
-Press "Change Filesystem".
-Press "EXT4".
-Reboot system and wait until Android completely boot up.
-Reboot into recovery to check if problem still persists.
-Go to "Wipe"
-Go to "Advanced Wipe"
-Choose "Cache"
-Press Wipe and when finished, post how long it took to finish cache wipe.
Click to expand...
Click to collapse
Can you help me? TWRP is showing a message that no OS is installed. When I tried formatting cache or data, I'm getting a message saying "unable to mount /data"
Heelixx said:
Can you help me? TWRP is showing a message that no OS is installed. When I tried formatting cache or data, I'm getting a message saying "unable to mount /data"
Click to expand...
Click to collapse
Possibly because there is no OS installed, or correctly installed. Clean flash the latest stock ROM via Odin and repeat the process.
nitrous² said:
Possibly because there is no OS installed, or correctly installed. Clean flash the latest stock ROM via Odin and repeat the process.
Click to expand...
Click to collapse
My fault. I should have clarified. Its an Alcatel phone, not a Samsung so Odin doesn't work. The phone was performing poorly so I decided to wipe the cache. It took really long to wipe. After 12 hours, it was still wiping so I decided to just reboot the device. After that, I saw the "No OS installed" in twrp. I didn't wipe the system partition, only the cache. At this moment I can't wipe anything because twrp is unable to mount any partition and I'm unable to mount any partition with adb. Debugging is turned on
Heelixx said:
My fault. I should have clarified. Its an Alcatel phone, not a Samsung so Odin doesn't work. The phone was performing poorly so I decided to wipe the cache. It took really long to wipe. After 12 hours, it was still wiping so I decided to just reboot the device. After that, I saw the "No OS installed" in twrp. I didn't wipe the system partition, only the cache. At this moment I can't wipe anything because twrp is unable to mount any partition and I'm unable to mount any partition with adb. Debugging is turned on
Click to expand...
Click to collapse
Oh, ok. You're new here. That's ok. Welcome at XDA =)
First I'd like you to post in the appropriate forums. This thread and the steps I provided are meant for the international Galaxy Note 3. Applying a fix that was designed for a different device than you have may brick your phone. Always look for, and apply solutions dedicated to your specific device model and OS version. When asking for help, always tell your exact device model. There are many Alcatel devices out there, you know. They all have different hardware.
A cache wipe shouldn't take more than a few seconds. On certain devices minutes. Use google to learn how you can flash a clean, stock ROM on your device. I don't know anything about Alcatel phones. Sorry.
For the Alcatel phone, restore using alcatels mobile upgrade software with the phone in download mode.
audit13 said:
For the Alcatel phone, restore using alcatels mobile upgrade software with the phone in download mode.
Click to expand...
Click to collapse
I'm getting a download error when it reaches stage 3 which is to format the userdata. Its strange because the Alcatel mobile upgrade worked on 2 different alcatel phones that I have. I think this phone is done for.
---------- Post added at 06:04 PM ---------- Previous post was at 06:03 PM ----------
nitrous² said:
Oh, ok. You're new here. That's ok. Welcome at XDA =)
First I'd like you to post in the appropriate forums. This thread and the steps I provided are meant for the international Galaxy Note 3. Applying a fix that was designed for a different device than you have may brick your phone. Always look for, and apply solutions dedicated to your specific device model and OS version. When asking for help, always tell your exact device model. There are many Alcatel devices out there, you know. They all have different hardware.
A cache wipe shouldn't take more than a few seconds. On certain devices minutes. Use google to learn how you can flash a clean, stock ROM on your device. I don't know anything about Alcatel phones. Sorry.
Click to expand...
Click to collapse
Thanks for the tip
PLEASE HELP ME Using Twrp recovery
I have a yunique 4711
I had wiped my system and i dont have any backup
When i tried to flash my rom of android 7.1 resurrection remix
It gave me an error as- failed to mount cache(no such device)
And failed to found recovery.img
And i hve twrp recovery
Please help me
I also shows no os installed
---------- Post added at 10:03 AM ---------- Previous post was at 09:47 AM ----------
Hii
I found a way to skip ir fix error e1001 or recovery.img is missing or FAILED TO MOUNT CACHE
FOE THAT FIX
SOLVE1
FIRST LEAVE YOUR PHONE UNUSED FOR 15 HOURS DONT TOUCH IT
THEN GO TO TWRP RECOVERY AND SELECT WIPE CACHE USING EXT4
THEN GOT TO WIPE DALVIKE OR ART CACHE THEN FLASH ANY ZIP ROM YOU WANT
KF IT WRKD PLEASE SUBSCRIBE ME ON YOUTUBE AS TECHNICAL BREECH
For me the formatting still very long since that method, and i still have no wi fi. But theres no "unable to" anymore !
On Note 3??
Stupid me, I think I made a boo boo, and need some help please.
I followed these instructions before installing a new ROM I wanted to test out;
Wipe In Recovery
-Wipe -> Swipe to factory reset (3x)
-Format data -> yes (3x)
-Advanced wipe -> check all boxes -> swipe to wipe (3x)
-Go back one menu -> Swipe to factory reset (1x)
I did all of that, went back to Install in TWRP, and none of my zips are at the bottom of the list anymore oops. Now what ?
Looks like you either have to download the factory image and flash it or use adb to push a rom to /sdcard/ in order to flash it with twrp.
I didn't realize that TWRP could load zip's now ? That's super cool .
I went to the Mount section in TWRP, and then plugged in my USB-C cable connected to the computer to the phone, and it recognized it, and allowed me to throw the ROM + GAPP files back onto the phone, I then rebooted Recovery, and they they were, F'ing amazing
Zorachus said:
Stupid me, I think I made a boo boo, and need some help please.
I followed these instructions before installing a new ROM I wanted to test out;
Wipe In Recovery
-Wipe -> Swipe to factory reset (3x)
-Format data -> yes (3x)
-Advanced wipe -> check all boxes -> swipe to wipe (3x)
-Go back one menu -> Swipe to factory reset (1x)
I did all of that, went back to Install in TWRP, and none of my zips are at the bottom of the list anymore oops. Now what ?
Click to expand...
Click to collapse
What instructions were you following there? Oh so much wrong about that. You don't need to wipe anything three times, there's no point. You only need to go into advanced wipe, select only system, data, cache, dalvik cache, and wipe those. Then just flash your ROM. I have a guide here that you might find helpful:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Guys I am in need of help. I did not fully understand step 10 in TWRP installation guide and just skipped originally. I did notice I could not wipe anything but thought I would be fine so I just dirty flashed custom ROM assuming wipe would work afterwards and I can clean install after.
I am obviously stuck now with 0MB internal storage shown along with no access to phone since it says upon boot that verification has failed and that I need to reset my phone.
Now, I do have important photos/datas which are invaluable and thus do not want to lose... I did hear other guys restored their nandroid backup and were fine.
My question is, is there any way for me to access and back up my internal data somehow? I did hear something like flashing a stock firmware via Odin without the cache inside. Could someone confirm that this would work please? Would really appreciate a response. Thanks guys.
I did try this:
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
But TWRP would not allow me to flash because it said it could not mount storage. I presume this is because I exited TWRP...
Please, any guidance would be much appreciated.
Do a wipe, system, data/ dalvic , and cache . Do NOT check internal storage and SD card...reflash your rom
Player04 said:
Do a wipe, system, data/ dalvic , and cache . Do NOT check internal storage and SD card...reflash your rom
Click to expand...
Click to collapse
Thanks for the reply but I cannot do that since the phone does not let me wipe from TWRP due to the encryption issues I believe.
jay_993 said:
Thanks for the reply but I cannot do that since the phone does not let me wipe from TWRP due to the encryption issues I believe.
Click to expand...
Click to collapse
Could this help:
"Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery]."
or
"If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP."
Source: http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
FinKing said:
Could this help:
"Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery]."
or
"If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP."
Source: http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
Thanks man. I am aware of this but have not done so which is my problem haha. Does anyone know of this set PIN before flashing stock rom on ODIN please? I obviously cannot since I cannot boot to system but I do not want to make assumptions like before, go ahead and cause myself more stress...
Hold up, have you flashed SuperSU? That should be the only thing stopping you from being able to boot up. After flashing TWRP and a custom rom you need to install SuperSU to be able to boot.
Either try to flash SuperSU using TWRP built in ADB or buy an external sd card and flash from there. You don't need to disable encryption and in fact, that zip you tried to use actually wipes your internal storage anyway so don't try it again.
I followed the following steps to flash oos 5.0.1 :
1. Update TWRP to the latest Codeworkx TWRP from the link posted
2. Reboot Recovery and Take a Nandroid of your existing ROM just in case you need it
3. Wipe > Advance Wipe > Select Dalvik & Cache > Swipe to Wipe
4. Install Menu > Select OOS 5.0.1 Full Rom Zip > Swipe to Flash
5. Flash Magisk 15.2 (Recommended for Root)
6. Wipe Dalvik & Cache
7. Reboot Recovery to make sure TWRP stays
8. Reboot System once recovery boots again.
i did this on my op5 rooted and encrypted .
so i followed all the steps precisely but in the end when i tried to boot into system it bootlooped (waited for hours to see if it really takes time on first boot). also when i open file manager in twrp it just shows weird long file names .
Yes I experienced the same thing too. I presume it's a problem with decryption after the update. I had removed all lockscreen security before updating (for nandroid). Maybe it was due to that? Would like someone to elaborate too.
r.sharma said:
I followed the following steps to flash oos 5.0.1 :
1. Update TWRP to the latest Codeworkx TWRP from the link posted
2. Reboot Recovery and Take a Nandroid of your existing ROM just in case you need it
3. Wipe > Advance Wipe > Select Dalvik & Cache > Swipe to Wipe
4. Install Menu > Select OOS 5.0.1 Full Rom Zip > Swipe to Flash
5. Flash Magisk 15.2 (Recommended for Root)
6. Wipe Dalvik & Cache
7. Reboot Recovery to make sure TWRP stays
8. Reboot System once recovery boots again.
i did this on my op5 rooted and encrypted .
so i followed all the steps precisely but in the end when i tried to boot into system it bootlooped (waited for hours to see if it really takes time on first boot). also when i open file manager in twrp it just shows weird long file names .
Click to expand...
Click to collapse
As your device is encrypted so first you need to decrypt it so for that just boot into twrp select wipe and select format data and type yes as it will for format your entire data including internal storage... the most first step is to backup your internal storage in pc and apps through titanium backup and save that in pc and later decrypt it once your device is decrypted just enable MTP in twrp and copy files in storage and flash it.
---------- Post added at 04:51 AM ---------- Previous post was at 04:45 AM ----------
r.sharma said:
I followed the following steps to flash oos 5.0.1 :
1. Update TWRP to the latest Codeworkx TWRP from the link posted
2. Reboot Recovery and Take a Nandroid of your existing ROM just in case you need it
3. Wipe > Advance Wipe > Select Dalvik & Cache > Swipe to Wipe
4. Install Menu > Select OOS 5.0.1 Full Rom Zip > Swipe to Flash
5. Flash Magisk 15.2 (Recommended for Root)
6. Wipe Dalvik & Cache
7. Reboot Recovery to make sure TWRP stays
8. Reboot System once recovery boots again.
i did this on my op5 rooted and encrypted .
so i followed all the steps precisely but in the end when i tried to boot into system it bootlooped (waited for hours to see if it really takes time on first boot). also when i open file manager in twrp it just shows weird long file names .
Click to expand...
Click to collapse
Here is the simplest one for you
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygen-os-5-0-problems-rooted-t3724616
Format data is must required for booting.
I was also rooted and encrypted using 4.5.15 and this is the method I followed and it worked:
Downloaded OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5. zip, twrp-3.2.1-0-universal-codeworkx-cheeseburger.img and Magisk-v15.3.zip.
Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP.
Rebooted to TWRP again to make sure that my TWRP was updated.
Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
This deleted my Internal Storage so I had to backup everything beforehand.
Then used advanced wipe to wipe Cache and Dalvik.
Mounted the internal storage by using the Mount option from TWRP main menu.
I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
Copied the OnePlus full update and Magisk zip file.
Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots.
Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
Booted into TWRP and flashed Magisk.
I am now on Oreo and I hate the way Ambient Display looks right now.
Hi!
Could someone please give a step-by-step guide as to how one would go about installing a GSI ROM on the Realme 2 Pro (4GM RAM version)?
And which ROM do I download, A only, or A/B? Is it ARM 64?
I had tried once before, and messed up.
Hoping someone is able to help me out here.
Thanks!
Now only mid stable rom Havoc-OS-v2.0-20181027-GSI-ARM64-Aonly
Use only Arm64-Aonly
0.Always Make Backup System,Efs,Data & Vendor partition
1.first boot twrp
2.swipe factory reset
3.Twrp advanced option Format System,Data,Delvik Cache & Cache
4.Now Install System image of havoc gsi arm64-aonly image to system
5.When install completed then wipe cache & delvvik cache
6.Then swipe to reboot
7.Ready to go
8.but this rom not for daily use,many bug present,Fingerprint not working
galibalmasanick said:
Now only mid stable rom Havoc-OS-v2.0-20181027-GSI-ARM64-Aonly
Use only Arm64-Aonly
0.Always Make Backup System,Efs,Data & Vendor partition
1.first boot twrp
2.swipe factory reset
3.Twrp advanced option Format System,Data,Delvik Cache & Cache
4.Now Install System image of havoc gsi arm64-aonly image to system
5.When install completed then wipe cache & delvvik cache
6.Then swipe to reboot
7.Ready to go
8.but this rom not for daily use,many bug present,Fingerprint not working
Click to expand...
Click to collapse
So I decided to try this out. And once I swiped to reboot, it showed "No OS installed. Do you want to continue?". When I restored from my backup, it would boot up, reach the homescreen, and the immediately restart. I have no idea what more I can do now.
Do you flow these script carefully?just extract havoc os zip,you will get havoc system img then just flash image file to system,then install nano gapps,then wipe cache & delvik cache with data just swipe for reboot,you can go perfect.
Get any ARM64 a only GSI rom. Our device only support ARM64 a format.
1 Put system image wherever sutable to you.
2. Take a full system backup.
3. Go to wipe and just swipe to factory reset.
4. Click on install and select system image and flash that image in system partition.
5. After flashing just reboot.
Process is simple.
Brother do you try bliss rom link - https://forum.xda-developers.com/pr.../rom-blissroms-9-0-official-4-4-2019-t3918303
i tried this.here is some screenshot
https://imgur.com/rBKNRQQ
https://imgur.com/Q7g68mR
https://imgur.com/bEKYvS8
https://imgur.com/nDkrhiH
https://imgur.com/mddj5yk
https://imgur.com/xfN23Yp
Ashwinrg said:
Get any ARM64 a only GSI rom. Our device only support ARM64 a format.
1 Put system image wherever sutable to you.
2. Take a full system backup.
3. Go to wipe and just swipe to factory reset.
4. Click on install and select system image and flash that image in system partition.
5. After flashing just reboot.
Process is simple.
Click to expand...
Click to collapse
Any twrp can be used ?
No need to flash vendor.zip ?
Ashwinrg said:
Get any ARM64 a only GSI rom. Our device only support ARM64 a format.
1 Put system image wherever sutable to you.
2. Take a full system backup.
3. Go to wipe and just swipe to factory reset.
4. Click on install and select system image and flash that image in system partition.
5. After flashing just reboot.
Process is simple.
Click to expand...
Click to collapse
So I tried this, and still did not manage to get it working. In fact I somehow managed to completely brick my phone, where I could neither access the OS, nor the bootloader. I had to take it to the service centre.
I even tried flashing the vendor zip file. But to no avail.
Is there perhaps a video which show the steps from top to bottom, starting at the bootloader unlock? (I want to make sure I'm not really messing that up either)