x720 partial unlocked bootloader? [SOLVED] - LeEco Le Pro3 Questions & Answers

So I got my 6GB/64GB x720 yesterday. It had Google Play Store already installed (ordered it from HonorBuy) and asked me to install a 7MB OTA, so it seems it had a recent version of EUI on it. My idea was to put LineageOS 14.1 on it or if it wasn't stable enough for me, at least a debloated and rooted stock. So searched XDA and followed this HowTo. No Errors, flashboot oem device-info said, bootloader unlocked, perfekt. Installed TWRP, downloaded recent LineageOS and followed the guides to flash (wipe, ...). Unfortunately flashing never finished, I always had a full progress-bar and it stayed there without doing anything (ok, the device got hot). Thinking of a broken download, I redownloaded the ROM but same problem. So I started downloading other ROMs from XDA: Resurection Remix and OmniROM. Flashing-process went thru, but couldn't flash gapps and ROMs didn't boot at all. I was always only getting to the LeEco-Bootlogo with the chinese writings. So next thought was, maybe for some reason I can't install Lineage-based ROMs, let's figure out later and get a debloated stock ROM. So I downloaded MAURO V2.2_Free and gave it another try. Looked more promising, as the bootlogo was a little different, no more chinese writing but english. Unfortunately this was all I could see of MAURO as I only got a bootloop... so again reflashed MAURO and this time a single line in TWRP-output came to my eye "boot.img could not be written". I checked flashboot oem device-info after every flash and it always told me, bootloader is unlocked, but there seems to be something else that I'm missing that obviously still keeps the bootloader locked. I wiped the phone several times, even sdcard... nothing helped. The only method that worked for me to get a working rom running was by this guide, manualy flashing every bit of stock ROM with flashboot. With MAURO-ROM, I also tried to flash boot.img manually with flashboot, but that didn't work, either.
Anyone of you experienced the same? What am I missing? Or is this some new protection implemented by LeEco for the most recent devices? Any help really appreciated!
regards
CDFS

I have the same phone from Honorbuy, I flashed twrp using the tool by Mauronofrio and from the twrp wiped all and flashed the custom rom, all went ok, no errors at all! Glad to see you have solved anyway!

Thanks for the answer... no, it's not solved for me... still a lot of bloat on the phone I can't get rid of. Do you have a link for the tool you mentioned? Could be worth a try...

Hi! I've used this tool installing it on a Windows 7 64 system:
https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
Then turned ON the (original LeEco stock rom) usb debug option by the rom's developer options, then downloaded the LineageOS 14.1 by Team Superluminal in the phone's internal SD (the only SD it have!) + Arm64 nano Gapps, then with the tool gave a reboot in sideload mode. Then flashed the twrp recovery by the tool, restarted in recovery mode then executed a backup of ALL the "backupable" stuff (all the original rom and data and efs), then in wipe/advanced options I wiped dalvik, system, cache, data. Then in Advanced/file manager I wiped all the SD files with a dot ( . ) at the beginning of their names, then flashed the custom rom + gapps, reboot system, wait some minutes, done!

No luck with this tool, it doesn't even find my device. Any other ideas? I've read something for the x727, where they had to flash a 19s bootloader first, but I don't want to fiddle with flashing files that are not 100% meant for the x720...
CDFS

Solved! As I could install TWRP I just went the next step and installed SuperSU (rooted the phone) in order to at least debloat stock rom. During the installation of SuperSU I saw, that SuperSU obviously patches somehow the bootloader. After checking that SuperSU worked in the ROM, I was curious if this could be the missing part I was searching for. I tried to install a LineageOS-based ROM and BINGO! it just went straight through! From my previous phones I was used to just install TWRP, wipe anything and flash desired ROM. This seems to be different on this device... so the proper procedure to be able to flash any ROMs is: Install TWRP, root stock ROM, reboot so SuperSU is fully functional, then go back into TWRP, wipe, flash what you want.
CDFS

I hate to say it, but it's still not solved. After testing Resurrection Remix, I wanted to test turbos ROMs, so went to TWRP, wiped and flashed... and got the same behaviour as before, ROM not booting. Also installing SuperSU via TWRP again didn't help, so brought back the phone to stock 023S manualy with the guide by Presterin, installed TWRP again and also SuperSU. No Errors, but flashing a different ROM didn't worked. So for now I'm back to stock, rooted it and tried to debloat it by myself. The only difference between the successful flashing and the failed was the stock version: I had the 026S-update when I rooted the phone and successfuly could flash another ROM. My guess would be that LeEco changed something in the bootloader, but I have no chance to verify this. Anyone from the devs maybe who could look into this? If you need dumos, logs or anything like that, I would be happy to help.
CDFS

This seems unrelated to bootloader.
Anyway:
1. Make sure you got the latest firmware, if not sure:
1.1. Download latest OFFICIAL ROM
1.2. Rename the rom to a 'update.zip' and place it on phone's root directory.
1.3. Reboot to fastboot and flash STOCK RECOVERY
1.4. Reboot to recovery and flash, also check wipe data.
DO NOT FLASH STOCK ROM WITH TWRP! THIS WILL NOT WORK!
That's it, you should have the latest firmware now.
After booting to stock rom, reboot a few times is recommended.
2. Download latest OFFICIAL TWRP
2.1. Flash TWRP with fastboot.
2.2. Reboot to TWRP.
2.3. Download any custom rom of your choice.
2.4. Wipe.
2.5 Flash.
Done.

You can try to flash a stock, old rom using the "Qfil/FlashOne" way as suggested by Tryzex (read his thread and other related threads), then once you have got a stable, full working phone, you can (hopefully!) wait for a LeEco OTA automatic update that can "repair" the file system/partition structure (also bootloader I hope!).
Btw, to debloat it isn't necessary to root the phone, you can keep the phone unrooted & debloated using the file manager embedded in twrp recovery to delete/replace any file/app you want. I'm sorry I can't help you better, cheers and... good luck!
PS
I see now the post from Voron00, it's a good hint!

@voron00 thx for the steps described. I'm using the most recent, official TWRP (3.1.1). Latest Official Stock seems to be 023S on their site, even though there is a 026S update. However, I did this 026S-update and rooted again, but was to cusious if flashing would work now... so I tried flashing turbos MIUI... guess what? It worked. So for whatever reason I seem to have trouble when flashing from a 023S, but no problems when flashing from 026S. I don't quite understand why you think that my problem is not related to the bootloader? As mentioned in the OP, I could see in the logs that while flashing, some roms had thrown errors regarding writing the bootpartition.
CDFS

Seems as I found the culprit, somehow. At least I could flash two other ROMs without any problems. Obviously I mixed and partly missinterpreted some steps found in different threads and howtos. I had "rm -rf for formating" ticked all the time in TWRP. My flashing procedure is now as follows:
1. in TWRP settings check that "rm -rf instead of format" is NOT ticked
2. wipe Cache, System and Data
3. repair filesystem for Cache, System and Data and check that no errors occur
4. in TWRP settings tick "rm -rf instead of format"
5. flash ROM
6. wipe Dalvik
CDFS

"rm -rf" clears all the files and directories without formatting the partition. If your partition is damaged you need a real format to obtain a reliable partition (if the "disk" isn't faulty). Perhaps in your case a real format was required to solve the problem! I always used the real format and assumed other users even so. I see you finally solved the problem!

Related

Moto x pure XT1575 What am i doing wrong?!

I bought this phone used and the person who had it before me it rooted and installed some of different ROMs on it. After getting my used moto x pure 2015 running android 6.0. I booted it up and tested all the functions (including downloading a few apps) Wi-Fi, camera, audio/charging jacks ext. Everything worked fine. So did normal factory reset (not using TWRP) just to make sure everything was clean before using it as my daily. Then, (BUM BUM BUM!) when I tried to start downloading all my apps. None of them would download even though the Wi-Fi was working. Error 492 I think.
I started trying custom ROMs because I was having two big issues (apps not downloading and incoming call not bringing up accept/decline screen) with my stock rom. and wanted to fix those issues with a fresh stock image.
This is all new to me and has not been as easy as anticipated. If anyone knows a clean factory image I could flash or a fail proof fix to error 492 that would be helpful. I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise, maybe you can help me with my flashing method, and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
cont.
I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise maybe you can help me out with my flashing method and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
I think this thread will help you: https://forum.xda-developers.com/showthread.php?t=3489110
Sent from my XT1572 using Tapatalk
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
RK2116 said:
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
Click to expand...
Click to collapse
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
cdiaz8 said:
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
Click to expand...
Click to collapse
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
RK2116 said:
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
cdiaz8 said:
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
Click to expand...
Click to collapse
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
RK2116 said:
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
Click to expand...
Click to collapse
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
cdiaz8 said:
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
Click to expand...
Click to collapse
Just a stock one, if Motorola have one use that.
RK2116 said:
Just a stock one, if Motorola have one use that.
Click to expand...
Click to collapse
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
cdiaz8 said:
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
Click to expand...
Click to collapse
Yes.

How can I revert to factory state in my Leeco Le s3 (x522 US variant)

Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Nikodominiko said:
Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Click to expand...
Click to collapse
So I managed to fix the problem. When you root this phone or in fact just flash a custom recovery like TWRP, it changes the model of the phone, If you unroot the phone you won't be able to receive OTAs anymore even if you are on stock ROM, you'll always get an error at the end of the update even if you do it manually, if you are dumb like me and didn't make a backup of your stock system, you won't find any help on the internet more than to install a custom ROM and learn to live with the errors and bugs. I did not want that so to be able to get the phone to its factory state, what I did was this:
1. Download: stock recovery image for Le s3 x522 (official, you can find it anywhere), LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip, twrp_s3.img (the chinese TWRP recovery) and S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
2. Save those zips to the root of the phone, obviously the .img files you are going to flash them through your PC
3. Put the phone in bootloader mode. command: fastboot flash recovery recovery.img (the official recovery)
4. fastboot boot twrp (the chinese one)
5. From this step what I did was pure luck
6. wipe cache and dalvik and install LeEco_X522_5.8.019S_OTA.zip
7. wipe cache and dalvik and install bootloader-20S-s2.zip
8. wipe cache and dalvik and install S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
9. Reboot
How and Why did this worked I don't know, I am a noob but please try if you find yourself in the same situation as I was, you don't lose anything with trying, if this doesn't work don't blame me, this worked for my phone.
Greetings friends!
Thanks for putting this guide together, I am in a similar situation in that I reverted to stock everything (1. Installed YDSS chinese twrp, 2. Installed S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip. This flash was supposed to have installed the stock recovery and overriden the ydss twrp, but didn't, I had to manually flash that after. Everything came back smooth but my updates also failed at recovery.
I am wondering where you got the LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip & twrp_s3.img from?
Nice to hear you finally got it to work ! Aren't the X520 and the X522 the same phone ? Why official ROMs are not compatible ?

flashing firmware zip fails every time

I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Use Unbrick Tool and Restore
Hey,
You can Flash your Mobile using the Unbrick tool at - https://androidfilehost.com/?w=files&flid=204903
Use the Latest file which I guess comes with OOS 5.1.3 - https://androidfilehost.com/?fid=962339331458999196
If you try to Go to Open Beta ROM First Flash Open Beta 12--> Open Beta 13 --> Open Beta 17
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Flashing newest oos doesn't always work l have had this sometime l have had to go back 3 oos versions then flash them in order to flash the latest release.
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Hi ! Do you have some news about it ? I have the same issue since Monday...
I've tried like anything i've found and even more, but nothing did the job ...
The only way to have my OP5 working is downgrade to an old version running Android 7.1.1

.

.
HMSS013 said:
Had my new OP5 rooted and almost everything was right in the world, but i flew too close to the sun by uninstalling a few apps I thought were expendable and eventually Google Play Services started crashing. When all troubleshooting failed I ended up flashing a fresh copy of OxygenOS (5.1.7) to my device, but every attempt to re-root the device has failed.
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
My next issue was that TWRP returned Error 7 when attempting to flash the stock OOS rom... after some digging I was able to clean the 'asserts' line from the updater-script file and now the rom will flash.
The headache has been getting the device re-rooted, and I feel like I've tried everything. I have to flash the SuperSU or Magisk zip (both fail to root the device) before reboot because the dm-verity encrypts on first boot and after that I can't access any storage to flash from internal memory. The three different dm-verity patches I've found don't prevent it. I also tried 'fastboot oem disable_dm_verity' to try and stop it but after talking with the device fastboot returns 'unknown command'.
My final effort to get around it was to flash a kernel that didn't force dm-verity (blu_spark kernel) but that returns Error 1: 'Unsupported Android Version' when I attempt to flash it.
I've tried dozens of variations on this, including a Lineage OS rom instead and also trying to sideload certain zips, but still no dice. Any and all help would be appreciated.
Click to expand...
Click to collapse
Which rom do you want to install?
HMSS013 said:
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
Click to expand...
Click to collapse
Hi, this one is because of your TWRP. Please flash Codework's TWRP and try that with it. It should solve your issue for sure. (same thing happened to me while I tried installing custom roms and every time I needed to wipe everything to see my internal storage again)
This guide can help you out with Error 7 on TWRP https://forum.xda-developers.com/showthread.php?t=2522762
I do believe your this issue you're having caused by TWRP. Also after rooting the phone, install magisk app. (you don't need to install supersu, it comes with magisk). After rebooting into system reboot your phone again once more it should show up on magisk app that you've successfully rooted your phone. Remember after flashing magisk you need to reboot twice in order for phone to realize it. Please try the steps I told you and let me know.
Also you don't need to flash dm-verity patch at all.
Try clean flash instructions with Codework's TWRP and root it with latest Magisk.
.
.
HMSS013 said:
I actually really like the Oreo version of OxygenOS, so when I had to resort to re-flashing to fix this mess I dug up one of the stock (5.1.7) roms, it served me well (assuming I can get it rooted, lol).
I'd be willing to move to Lineage if I absolutely have to, but if not, I'd really like to keep Oreo if at all possible.
Click to expand...
Click to collapse
For 5.1.7 try this twrp https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk along with magisk 17.1.
Clean flash is recommended. If it didn't help, please list your steps again(detailed).
Don't use supersu and skip the other suggestions for now please.
.

What's the REAL method to successfully install a working TWRP, root and custom ROM?

Hi All, I have been reading various threads here and searching on Google for finding a method that truly works for successfully installing a custom ROM, getting TWRP installed and rooting with Magisk. So far, all I have found are numerous and usually contradictory methods and about 7 or 8 different versions of TWRP (so which one is completely stable and working properly?). I have tried several methods over the past two weeks and none of them are working completely.
Sometimes, I'll get a version of TWRP installed, but then trying to reboot to recovery results in a "system has been destroyed" image. Or I'll succeed in getting a custom ROM installed, but Gapps will fail with error 20 or error 70 or there's not enough space on the system partition (and I'm just trying to install the Pico version). Even I double check that the Gapps version matches the ROM version I've used, but still get an error 20 displayed.
From what I had read on numerous threads, it seemed like CosmicDans TWRP would be the one I should go with. I downloaded both of his files (the fastboot image and the zipped installer) and fastboot his "boot-recovery.img" that was specifically for fastboot only and from that recovery, I installed his "TWRP-Installer-3.2.1-with-Tissot-Manager-2.5.zip". Everything appeared as if successfully installed as per the logs, but immediately upon attempting to reboot to recovery, I get the "system has been destroyed" image.
What I want to do is:
Get a working custom ROM (preferably Pie) installed
Install Gapps
Install a working TWRP (that will not display "system has been destroyed" whenever trying to boot to recovery)
Finally, install Magisk and root my phone
Can anyone suggest a site or link or a post somewhere that would explain everything correctly and is actually working? This has been a very frustrating experience. I'm almost sorry that I even bought the Mi A1. Never had any problems installing custom ROMs or rooting the OnePlus devices. All I'm left with currently is an expensive paperweight.
Thanks so much!
Cheers
From your description, I'm certain that you do this on a Pie stock rom right? the installer never work on Pie stock and will cause system destroy. Just hotboot TWRP. And for the Gapps, I think it's due to the time you install it. From my experience, install Gapps after rom and before Magisk usually work. Install after magisk or custom kernel will somehow cause the same issue that you described.
Oh, in case you want to install LineageOS, you have to come to the LOS16 thread and download the TWRP from there, it's the only TWRP that can install LOS16.
Never_Sm1le said:
From your description, I'm certain that you do this on a Pie stock rom right? the installer never work on Pie stock and will cause system destroy. Just hotboot TWRP. And for the Gapps, I think it's due to the time you install it. From my experience, install Gapps after rom and before Magisk usually work. Install after magisk or custom kernel will somehow cause the same issue that you described.
Oh, in case you want to install LineageOS, you have to come to the LOS16 thread and download the TWRP from there, it's the only TWRP that can install LOS16.
Click to expand...
Click to collapse
Thank you for your reply. When I first started the process to change to a custom ROM, I was on stock Pie. But one of the times I was wiping the device after one more problem, I accidentally also wiped Internal Storage as well. I didn't have much there since I had already backed some things up in advance. Now it's virtually empty. The steps I take are:
1. Hotboot TWRP
2. Install Custom ROM
3. Hotboot TWRP again
4. Install Gapps
This is where I usually have some problem. It's the process of installing Gapps that creates some error.
I also did attempt to install LineageOS 16 using the TWRP recovery that was linked in the post. Follow the instructions precisely I believe and now when it's time to install Gapps, I get error 64. I can't understand why. I am attempting to install "open_gapps-arm64-9.0-nano". This should be compatible with the Mi A1 with LineageOS 16 from what I am able to tell.
No matter what TWRP version I use, no matter what custom ROM I try, no matter what steps I take, there is always some issue that prevents me from completing any installation. But the abundance of so many conflicting posts don't help either. One post will state to use a specific TWRP and certain steps; another post will suggest completely different steps using another TWRP; and yet another post will provide different steps still. In some instances, there will be steps listed in the script on the phone regarding the next steps after the ROM installation that are completely different then the steps provided in the post for that ROM in the forum.
It would just be tremendously helpful to get some instructions that actually do work. As of now, I'm about ready to dump this phone in the trash bin. It's horrible. I can't even tell if it might be decent eventually since I never can get anything installed.
Thanks again for your reply Never_Sm1le.
Cheers.
There is no permanent TWRP install for android 9 on MiA1 as far as i know.
Hotboot works just perfect.
Brianne8 said:
Thank you for your reply. When I first started the process to change to a custom ROM, I was on stock Pie. But one of the times I was wiping the device after one more problem, I accidentally also wiped Internal Storage as well. I didn't have much there since I had already backed some things up in advance. Now it's virtually empty. The steps I take are:
1. Hotboot TWRP
2. Install Custom ROM
3. Hotboot TWRP again
4. Install Gapps
This is where I usually have some problem. It's the process of installing Gapps that creates some error.
I also did attempt to install LineageOS 16 using the TWRP recovery that was linked in the post. Follow the instructions precisely I believe and now when it's time to install Gapps, I get error 64. I can't understand why. I am attempting to install "open_gapps-arm64-9.0-nano". This should be compatible with the Mi A1 with LineageOS 16 from what I am able to tell.
No matter what TWRP version I use, no matter what custom ROM I try, no matter what steps I take, there is always some issue that prevents me from completing any installation. But the abundance of so many conflicting posts don't help either. One post will state to use a specific TWRP and certain steps; another post will suggest completely different steps using another TWRP; and yet another post will provide different steps still. In some instances, there will be steps listed in the script on the phone regarding the next steps after the ROM installation that are completely different then the steps provided in the post for that ROM in the forum.
It would just be tremendously helpful to get some instructions that actually do work. As of now, I'm about ready to dump this phone in the trash bin. It's horrible. I can't even tell if it might be decent eventually since I never can get anything installed.
Thanks again for your reply Never_Sm1le.
Cheers.
Click to expand...
Click to collapse
Your reply makes me want to stay on LOS 15.1 even more. So many weird problems happen in LOS 16
I followed all the instructions of Resurrection Remix and TWRP is installed and magisk works perfect.
Hello friend, I am currently on Lineage OS 16.0 with Magisk, Opengapps and TWRP installed. I can boot to recovery with no problems at all; in fact, I used the flashed TWRP to install Magisk.
Here are the steps I took:
Download the TWRP boot img and TWRP installer by CosmicDan (Link below)
Copy the custom rom ZIP, TWRP installer, Magisk installer and Gapps into your SD card
Reboot your device to bootloader
Boot into TWRP using
Code:
fastboot boot boot-recovery.img
do NOT flash via fastboot
Go to Wipe>Advanced Wipe and wipe System, Dalvik, Data, Internal Storage
Press the home button and proceed to flashing the custom rom ZIP
After flashing, reboot to BOOTLOADER then do step 4 again
Flash Gapps, TWRP Installer, then Magisk Installer. You should flash TWRP first before Magisk
Reboot to system and you're good to go
Note that if you are installing Lineage OS and wish to receive nightly OTA updates, having an installed TWRP as your recovery might result in a bootloop after updating. Also, if you want to manually flash the nightly update, you need to boot to the TWRP variant of @flex1911 as flashing lineage using other TWRP will result in an error. I suggest not installing TWRP when using Lineage OS.
(Source: [ROM][OFFICIAL] LineageOS 16.0 for Xiaomi Mi A1)
Regarding your problem with flashing, try to check which slot you are currently in by going to TWRP>Reboot. Keep in mind that when you install a rom, it will always be installed to the inactive slot. For example if you are in slot A, your rom will be installed in slot B. After rebooting, your current active slot will be where the rom is installed. When installing Gapps or any addons, check the slot first. However, when flashing TWRP installer, it will patch both boot_a and boot_b and this is the reason why you need to install twrp first before magisk as TWRP also modifies the boot image.
Download:
Bootable TWRP
TWRP Installer
(Both files by @CosmicDan)
Cheers mate!
rexendz said:
Here are the steps I took:
Download the TWRP boot img and TWRP installer by CosmicDan (Link below)
Copy the custom rom ZIP, TWRP installer, Magisk installer and Gapps into your SD card
Reboot your device to bootloader
Boot into TWRP using
Code:
fastboot boot boot-recovery.img
do NOT flash via fastboot
Go to Wipe>Advanced Wipe and wipe System, Dalvik, Data, Internal Storage
Press the home button and proceed to flashing the custom rom ZIP
After flashing, reboot to BOOTLOADER then do step 4 again
Flash Gapps, TWRP Installer, then Magisk Installer. You should flash TWRP first before Magisk
Reboot to system and you're good to go
Click to expand...
Click to collapse
Thanks for the lengthy reply. However, those steps do not work as you have described. Since, if I wipe Internal Storage (as per your step 5), I just deleted all the files I copied previously in Step 2. What I did, was wipe everything, *then* copied all the files and tried to install. As soon as it try to install Gapps, I get Error 64 again. I am absolutely using "open_gapps-arm64-9.0-nano" and it always fails. I have attempted 11 or 12 times already, using different slots, using different dates of "open_gapps-arm64-9.0-nano" and ALWAYS Error 64. I don't know any other version of Gapps I should be trying. The arm64 versions never will work for me.
I give up. I'll just have to stick with stock ROM. No custom ROMs will work for me no matter which one I use or which version of TWRP I use. I already wasted too much of my life with this garbage phone.
ccalixtro said:
I followed all the instructions of Resurrection Remix and TWRP is installed and magisk works perfect.
Click to expand...
Click to collapse
Hi,
Which version of TWRP did you use? There's too many. I don't know which one is considered to be the right one.
Brianne8 said:
Thanks for the lengthy reply. However, those steps do not work as you have described. Since, if I wipe Internal Storage (as per your step 5), I just deleted all the files I copied previously in Step 2. What I did, was wipe everything, *then* copied all the files and tried to install. As soon as it try to install Gapps, I get Error 64 again. I am absolutely using "open_gapps-arm64-9.0-nano" and it always fails. I have attempted 11 or 12 times already, using different slots, using different dates of "open_gapps-arm64-9.0-nano" and ALWAYS Error 64. I don't know any other version of Gapps I should be trying. The arm64 versions never will work for me.
I give up. I'll just have to stick with stock ROM. No custom ROMs will work for me no matter which one I use or which version of TWRP I use. I already wasted too much of my life with this garbage phone.
Click to expand...
Click to collapse
Copy the files to your external SD card not internal storage. But if you don't have an ext SD card, don't wipe internal storage.
Also try to check if system is properly mounted when installing gapps.
May I ask what custom rom you are trying to install?
I suggest you try Pixel Experience as it already has a builtin Gapps so you dont have to flash opengapps.

Categories

Resources