Database Users

Lg g2 no os at all

Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)

If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC

Spumpkin said:
Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)
Click to expand...
Click to collapse
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk

renzo090513 said:
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk
Click to expand...
Click to collapse
cm11 => jb bootloader
cm12, cm12.1 and cm13 => kk bootloader

klemenSLO said:
If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC
Click to expand...
Click to collapse
The current version is 2.8.7.3. Should I try other versions?

Did you solve the issue? Or is it still not allowing you to get into your F/W?

staylecrate said:
Did you solve the issue? Or is it still not allowing you to get into your F/W?
Click to expand...
Click to collapse
Hi!
I tried to install TWRP version 2.6.6.3, but it fails to flash it so I'm stuck with the version 2.8.7.3. All I'm able to enter is just the recovery mode. I can't enter the download mode so I can't flash the stock firmware.
Currently I'm out of ideas. I can't flash any OS, the TWRP fails everytime and creates errors.

Try flash bumped kernel like lp dorimanx then flash bumped bootstak then lp rom like cloudy or stock. Or google this: lg g2 unbrickable now xda ...that work for me

Asus Zenfone Selfie ZD551KL cannot flash any ROMs or restore recovery. TWRP installed

Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?

Did you fix your problem cause I fix mine my device can boot to fast boot mode if you
Did you fix your problem cause I fix mine my device can boot to fast boot mode if yours can I will send you the original recovery boot manger then download the latest firmware from the official webpage the go to bootloader and update the file it will work for sure but now have a software touch problems I tried to change theme and enable gloves mode it worked fine for a little time

Same issue..
Hey Lobstercat,
I am having the same problem as you..
I have tried TWRP (format /cache, /dalvik, /system and /data) with an unlock bootloader from an Asus Selfie. I have made a backup of it before trying the above. TWRP was able to restore the UL-Z00T-WW-1.12.40.382 OS fine.
But when install through TWRP, on UL-Z00T-WW-1.13.40.661-user.zip, it gives up on authentication, of which I also turned off with the same result.
In sideload mode it failed with the following message;
sudo adb sideload UL-Z00T-WW-1.13.40.661-user.zip serving: 'UL-Z00T-WW-1.13.40.661-user.zip' (~79%) E: fota_return_code 408
I have also tried "sudo fastboot flash system system.img" it failed, with the message "system.img was too large" this rendered my device unbootable and TWRP cannot restore the backup grrr..
I have the latest fastboot and adb from google went through the same above procedure with the same result, TWRP terminal shows files which I cannot be deleted with rm -rf command
I need to update with the OTA updates to UL-Z00T-WW-1.15 from Asus first before moving over to LOS.
Lobstercat said:
Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Click to expand...
Click to collapse

Resolved..
I was able to sort it out through this link.
https://forum.xda-developers.com/zenfone-2-laser/orig-development/rom-cyanogenmod-13-0-t3317515
"In order to update your firmware to MM one you can either flash ASUS MM rom in stock recovery or flash a package that will update your fw which you can download right here"
Download that link, sideload it with no issues and lineage OS 14 with no issues.
Now running Lineage OS 14. Damn its quick!

Getting failed to mount'/persist'(invalid argument) while flashing custom rom lineage
Lobstercat said:
Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Click to expand...
Click to collapse
I am on latest version of TWRP have done all the process
unlocked bootloader
Rooted my phone
On latest version of TWRP
Official lineage os 14.1
But all time getting failed to mount'/persist'(invalid argument)
Even not able to go back to stock recovery through back2stock.zip process
currently operating my phone through restoring backup
What I need to do please anybody have any solution of this please reply thanks in advance

Jayants susner said:
I am on latest version of TWRP have done all the process
unlocked bootloader
Rooted my phone
On latest version of TWRP
Official lineage os 14.1
But all time getting failed to mount'/persist'(invalid argument)
Even not able to go back to stock recovery through back2stock.zip process
currently operating my phone through restoring backup
What I need to do please anybody have any solution of this please reply thanks in advance
Click to expand...
Click to collapse
Excuses excuses, but bottom line just don't get around to things very fast very often. Did you ever figure it out? It was a long time ago now so I assume you did....

Boot loop on all roms URGENT HELP NEEDED

Help? Every rom seems to give me boot loop after install and a couple of roms get to 50 percent installing then TWRP reboots (mostly pixel rom and rr does this)
I also tried nougat and marshmellow stock roms and they both give drk check error, I flash super su like I used to do to fix drk check error and it just boot loops now
All the roms I used to be able to install fine now just boot loop
Pixel rom
Fast and famous rom
Infinity rom
Lineage os
Resurrection remix
All of these roms above I have had on my phone at some point and all worked fine now I just get boot loop after installing them.

14 views and no one can help me?

Still have no phone as I still cannot boot.

are you using a correct kernel or twrp for your device

blackbravo said:
are you using a correct kernel or twrp for your device
Click to expand...
Click to collapse
I'm not sure my device is G928F Can you link me to the correct kernel? And I think the TWRP is 2.7.8 or something like that

download twrp here: https://twrp.me/samsung/samsunggalaxys6edgeplus.html
flash over odin
and choose one rom with kernel included, because you must have the correct kernel for the rom you install

blackbravo said:
download twrp here: https://twrp.me/samsung/samsunggalaxys6edgeplus.html
flash over odin
and choose one rom with kernel included, because you must have the correct kernel for the rom you install
Click to expand...
Click to collapse
Okay so tried a couple roms and they all crash like sometimes at 10 percent sometimes around 50 but they always crash and TWRP restarts. Something to do with the aroma installer roms, tried multiple different TWRP versions and nothing likes the aroma installer roms, any suggestions? Also tried multiple nougat and marshmellow roms and I get drk check failed everytime.
I used to be able to flash SuperSU zip and it would fix drk check failed but it no longer does
Can someone please give me any suggestions at all as I would like to use my phone again

jacksskinz said:
Okay so tried a couple roms and they all crash like sometimes at 10 percent sometimes around 50 but they always crash and TWRP restarts. Something to do with the aroma installer roms, tried multiple different TWRP versions and nothing likes the aroma installer roms, any suggestions? Also tried multiple nougat and marshmellow roms and I get drk check failed everytime.
I used to be able to flash SuperSU zip and it would fix drk check failed but it no longer does
Can someone please give me any suggestions at all as I would like to use my phone again
Click to expand...
Click to collapse
And install stock ROM via Odin? Not working ?

blackbravo said:
And install stock ROM via Odin? Not working ?
Click to expand...
Click to collapse
It works but when booting I get DRK CHECK FAILED

blackbravo said:
And install stock ROM via Odin? Not working ?
Click to expand...
Click to collapse
Okay I've narrowed it down to system
When installing any rom it seems to crash when it gets to installing system and then TWRP reboots
I've checked that system is mounted which it is
Also it seems system is at EXT4 file system
Dunno if that's good or bad but either way every rom is crashing when it gets to installing system
Any ideas?

jacksskinz said:
Okay I've narrowed it down to system
When installing any rom it seems to crash when it gets to installing system and then TWRP reboots
I've checked that system is mounted which it is
Also it seems system is at EXT4 file system
Dunno if that's good or bad but either way every rom is crashing when it gets to installing system
Any ideas?
Click to expand...
Click to collapse
Can someone help please before I buy a new motherboard? Roms crash when it starts installing system

Download stock nougat, and flash it, but make sure csc is selected, and not home_csc, because csc will put phone to real stock settings.

Flash the latest stock firmware for your *correct variant*. Sammobile's downloads are kind of slow, but I've never had issues with any of their firmwares. Install that with Odin and your phone on download mode. I would recommend to use HOME CSC, just to make sure it is completely clean. After you set it up, flash your *correct variant's* TWRP via Odin. To save yourself some time, you can boot straight into TWRP when it finishes installing by pressing home + power + volume up when the screen goes out. From here you can load ROMs from a PC via USB. Good Luck and Happy Flashing!

Can' t update LOS 14.1 to newer nightly builds

Hello guys,
I wanted to try some stuff on my Axon 7 with LOS 14.1. So I made a TWRP backup, playing around with Magisk and some of it' s modules and didn' t liked it.
So I decided to restore my TWRP backup. After that the phone didn' t boot anymore. As I always wanted to try the LOS 15.1 unoffical build I decided "now or never".
So I installed it played around a bit but the battery lifetime was horrible. I decided to go back to LOS 14.1 then.
Ater reflashing all stuff for it and the ROM itself I landed in Android wich asks me for a password or a reset to factory. So I did the factory reset but landed always at the same screen again.
Reading through google posts I found some hints deleting the /system partition and reflash again. Doing this I was unable to flash the ROM as it couldn' t find /system.
Fixed that error in TWRP and installed again. Now I always get following error when flashing the ROM:
E1001: Failed to update system image.
Updater process ended with ERROR: 7
I have installed A2017X_B15_Universal_Bootloader, A2017G_N_Modem and TWRP 3.2.3. I also tried some older versions of TWRP but no luck.
I played a bit with the LOS zip and found that it gets stuck on the following line in system.transfer.list.
erase 80,75789,97792,135332,163328,200195,228864,263226,294400,328731,359936,361483,392704,394245,425472,428310,458240,459266,491008,492034,523776,524802,556544,557570,589312,590338,622080,623106,654848,655874,687616,688642,720384,721410,753152,754178,785920,786946,818688,852482,884224,918018,949760,950786,982528,983554,1015296,1016322,1048064,1049090,1080832,1081858,1113600,1114626,1146368,1147394,1179136,1180162,1211904,1212930,1244672,1245698,1277440,1278466,1310208,1311234,1342976,1344002,1375744,1376770,1408512,1409538,1441280,1442306,1474048,1475074,1506816,1507842,1539584,1540610,1572864
I deleted it but TWRP get stuck at around 85% of installing the zip.
As I at least wanted a running phone I remove the 'abort("E1001: Failed to update system image.")' in updater-script.
After a "successful" installation I restored the TWRP backup over the installed system. It runs now but I can' t update LOS anymore as it always get stuck on the error 7.
Any ideas how to make it install new versions again?
Thanks in advance,
Black-Dragon131

black-dragon131 said:
Hello guys,
I wanted to try some stuff on my Axon 7 with LOS 14.1. So I made a TWRP backup, playing around with Magisk and some of it' s modules and didn' t liked it.
So I decided to restore my TWRP backup. After that the phone didn' t boot anymore. As I always wanted to try the LOS 15.1 unoffical build I decided "now or never".
So I installed it played around a bit but the battery lifetime was horrible. I decided to go back to LOS 14.1 then.
Ater reflashing all stuff for it and the ROM itself I landed in Android wich asks me for a password or a reset to factory. So I did the factory reset but landed always at the same screen again.
Reading through google posts I found some hints deleting the /system partition and reflash again. Doing this I was unable to flash the ROM as it couldn' t find /system.
Fixed that error in TWRP and installed again. Now I always get following error when flashing the ROM:
E1001: Failed to update system image.
Updater process ended with ERROR: 7
I have installed A2017X_B15_Universal_Bootloader, A2017G_N_Modem and TWRP 3.2.3. I also tried some older versions of TWRP but no luck.
I played a bit with the LOS zip and found that it gets stuck on the following line in system.transfer.list.
erase 80,75789,97792,135332,163328,200195,228864,263226,294400,328731,359936,361483,392704,394245,425472,428310,458240,459266,491008,492034,523776,524802,556544,557570,589312,590338,622080,623106,654848,655874,687616,688642,720384,721410,753152,754178,785920,786946,818688,852482,884224,918018,949760,950786,982528,983554,1015296,1016322,1048064,1049090,1080832,1081858,1113600,1114626,1146368,1147394,1179136,1180162,1211904,1212930,1244672,1245698,1277440,1278466,1310208,1311234,1342976,1344002,1375744,1376770,1408512,1409538,1441280,1442306,1474048,1475074,1506816,1507842,1539584,1540610,1572864
I deleted it but TWRP get stuck at around 85% of installing the zip.
As I at least wanted a running phone I remove the 'abort("E1001: Failed to update system image.")' in updater-script.
After a "successful" installation I restored the TWRP backup over the installed system. It runs now but I can' t update LOS anymore as it always get stuck on the error 7.
Any ideas how to make it install new versions again?
Thanks in advance,
Black-Dragon131
Click to expand...
Click to collapse
I had the same problem. Solution was very simple. Install another EDL Package with a different TWRP like TWRP Treble/exclusive or any different one that has compatibility Android 7.x .
After that my Problem with "E1001: Failed to update system image. Updater process ended with ERROR: 7" was gone.

Voenix said:
I had the same problem. Solution was very simple. Install another EDL Package with a different TWRP like TWRP Treble/exclusive or any different one that has compatibility Android 7.x .
After that my Problem with "E1001: Failed to update system image. Updater process ended with ERROR: 7" was gone.
Click to expand...
Click to collapse
Thanks for your fast response. Do you have some links with instructions/ downloads for me? Never messed around with EDL before.

Anybody can guide me to do what Voenix said?

Djkuz has an Edl tool or you could try the Axon7 tool kit
Here is a link to Djkuz Edl tool
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Download your appropriate Edl package and unzip it.
Download twrp.
Boot your phone into edl mode by button combo or via the edl tool (instructions are on the Edl tool).

Syberclone said:
Djkuz has an Edl tool or you could try the Axon7 tool kit
Here is a link to Djkuz Edl tool
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Download your appropriate Edl package and unzip it.
Download twrp.
Boot your phone into edl mode by button combo or via the edl tool (instructions are on the Edl tool).
Click to expand...
Click to collapse
Hey Syberclone,
thanks for the link. Worked perfectly

black-dragon131 said:
Hey Syberclone,
thanks for the link. Worked perfectly
Click to expand...
Click to collapse
I'm glad you are up and running again

Flashing Custom rom i get stuck at fast boot but flashing xiaomi.eu works fine

Hi,
I've done countless steps and watched a ton of videos today but still can't answer this and it feels like I'm missing something simple.
I received my xiaomi 9t today and quickly unlocked the bootloader (no wait time possibly because I had a Mi8 before hand so I already had an account). I've since installed TWRP as well as tried OrangeFox Recovery and still can't get any custom roms to work, it goes directly to the fastboot screen. I can get back into TWRP and flash xiaomi.eu rom, no issue but as soon as I go to a custom rom I get fastboot.
I've flashed my Mi 8 countless times but I can't seem to get this to go. I've tried making sure the mounts were correct, I've flashed a disable forced encryption thing that I saw on some youtube videos and still nothing works.
Thanks in advance,
Joe

AbsoluteZero said:
Hi,
I've done countless steps and watched a ton of videos today but still can't answer this and it feels like I'm missing something simple.
I received my xiaomi 9t today and quickly unlocked the bootloader (no wait time possibly because I had a Mi8 before hand so I already had an account). I've since installed TWRP as well as tried OrangeFox Recovery and still can't get any custom roms to work, it goes directly to the fastboot screen. I can get back into TWRP and flash xiaomi.eu rom, no issue but as soon as I go to a custom rom I get fastboot.
I've flashed my Mi 8 countless times but I can't seem to get this to go. I've tried making sure the mounts were correct, I've flashed a disable forced encryption thing that I saw on some youtube videos and still nothing works.
Thanks in advance,
Joe
Click to expand...
Click to collapse
Hello, what OrangeFox version did you install?
You should try with R10.1_1 if you are using latest one.
If your phone is working with xiaomi.eu ROMs..., do you know xiaomi.eu ROMs are custom ROMs?
You generally only have to "Format Data" in TWRP before flashing another ROM (stock or custom).
Good luck!

Hi,
Thank you for the reply. I now have OrangeFox R10.1_1 installed. sorry I should've said other custom roms aren't working xiaomi.eu seems to be fine for some reason.
I just installed OrangeFox, reflashed xiaomi.eu and booted, worked fine. Then I went back, formatted data, rebooted back to recovery, flashed AOSPextended and gapps pico. Rebooted to system and it went to the fastboot screen again. I noticed it says during the AOSP install that "Root Status: Disabled" could that be a problem?
Thanks again for your help.

AbsoluteZero said:
Hi,
I've done countless steps and watched a ton of videos today but still can't answer this and it feels like I'm missing something simple.
I received my xiaomi 9t today and quickly unlocked the bootloader (no wait time possibly because I had a Mi8 before hand so I already had an account). I've since installed TWRP as well as tried OrangeFox Recovery and still can't get any custom roms to work, it goes directly to the fastboot screen. I can get back into TWRP and flash xiaomi.eu rom, no issue but as soon as I go to a custom rom I get fastboot.
I've flashed my Mi 8 countless times but I can't seem to get this to go. I've tried making sure the mounts were correct, I've flashed a disable forced encryption thing that I saw on some youtube videos and still nothing works.
Thanks in advance,
Joe
Click to expand...
Click to collapse
Use the official TWRP.

You should install latest stable xiaomi.eu rom or install latest China rom through MI flash, you need latest vendor partition for latest custom roms to boot properly.

jaggyjags said:
You should install latest stable xiaomi.eu rom or install latest China rom through MI flash, you need latest vendor partition for latest custom roms to boot properly.
Click to expand...
Click to collapse
I installed the latest Global Rom 11.0.5. via OrangeFox. I couldn't get it to go with Mi Flash. Not sure how to create the flash_all.bat and where to get all the files from. Is that the same? What are the steps from here?
Thank you

The same exact issue I am facing. Tried multiple custom roms and everything failed to boot only resulting in bricked or error. Even my previous budget phone redmi 3s was much better than this.