Database Users

x720 partial unlocked bootloader? [SOLVED]

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!

TWRP not booting system

I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.

Hi
Bibi if you’re still active on xda reply to this

Help me i got same issue with you. Can provide me with ur stock rom and stock recovery? And how to do. Thanks very much.
Bibicp said:
I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.
Click to expand...
Click to collapse

Bibicp said:
I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.
Click to expand...
Click to collapse
can you put a link where you find the stock recovery, cos i've restore stock recovery on twrp but my device keep booting to twrp

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 ?

Bricked but still have twrp

Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.

almost looks like it can't mount the system

IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.

I have no idea how it happened but I got my system mounted again that was my problem. I'm back.
thread can be closed

keeganjk said:
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
Click to expand...
Click to collapse
thanks for the reply mate

snipeez1987 said:
thanks for the reply mate
Click to expand...
Click to collapse
yw

snipeez1987 said:
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
Click to expand...
Click to collapse
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.

ipredatorv said:
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
Click to expand...
Click to collapse
Awesome. I'll keep that in mind. I'm sure I'll mess it up again lol. Hopefully not though.

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