Hi all,
I need some help please. I have an ASUS zenfone 2 laser 6 ze601kl. Came with a CN rom. No Google play services, go them installed using a google services installer. Trouble is, Android Wear dropped out and lost the watch details, backup failed randomly, google play services randomly crashed, play store etc. Wife wasn't too happy with me. Plus the random chinese apps updating and popping up with who knows what.
Current ROM CN_1.16.40.1715_20160623
Goal was to install a new WW rom which hopefully had working and stable google play services. Cannot install WW rom as it's CN - recovery error.
* gained root with KingRoot
* Debug mode on
* Unlocked bootloader using ASUS boot unlocker. Tried recovery, selected update from SD, same fail.
* installed ADB and fastboot (1.43) on windows 10 - nope, ADB recognised but always said 'cannot load <filename>.zip. Didn't matter which ROM or version.
* Tried to fastboot a new recovery and boot img, almost bricked it. Recovered using a CN ROM recovery and boot.img from
I have now:
* installed TWRP v3.0.2-5, which doesn't let me update to any ROM at all (WW official, WW rooted, resurrection remix etc)
Current error with UL-Z00T-WW-1.16.40.1524-user.zip is
Device SKU:
OTA image SKU: WW
Please use the right SKU for updating...
Updater process ended with ERROR: 7
Error installing zip file 'path/filename.zip'
Can't install Marshmallow WW ROM - says
Can't install this M package (tues sep 27 <time>) L less than 20160426 build (date/time)
Can't install RR Rom
Comparing TZ version TZ.BF.3.0.C3-00025 to ZT.BF.3.0.R2-00064
assert failed: asus.verify_trustzone("TZ.BF.3.0.c3-00025") == "1"
Basically I'm stuck, I can't use ADB (I did reinstall Windows 10, ADB still can't read <filename.zip> on my PC), and I can't seem to install any rom and get rid of teh CN ROM which I really, really, really want to.
Help?
I still can't change ROM's, however I can flash nano GAPPS (anything bigger tells me theres not enough space in the system partition).
Does anyone else have this issue with changing CN rom to WW or other?
Z00T - can't install any custom ROM
Firmware issue: Solved:
https://forum.xda-developers.com/showpost.php?p=68328880&postcount=2291
Hi, I have the same or similar issue. Did you solve yours meanwhile?
Did I mess up an essential drive in my Z00T or do I have a problem with a version? Although the stock ROM came with the full load of google bloathware-**** - so it's likely not chinese.
What happened:
I tried to recover an old CM13 nandroid backup from a similar Z00T (ZD551KL) on a replacement device.
Unfortunatelly (?) I usedeach and every drive twrp offered me for this backup and I put the recovery it the same way. The rrecovery image is installed with no problems. However, when rebooting I end up in the bootloader mode. If only system or system and data are recovered, the device freeze at the ASUS logo.
Beforehand I made a nandroid backup of the stock android 5 system installed via twrp (i mixed several twrp, it could be 3.0.0-0 or max. 3.2.1-5) on my new replacement Z00T. I can easily go back to the stock-ROM backup - this works really fine - from each of above twrp after each and any failed other attempt.
Now, when trying to install either a lineage 14.1 (i still have two builds on my SD card) or a 15.1 I found somewhere the same error occurs: "Updater process ended with ERROR: 7 Error installing zip file 'path/filename.zip'". On my old device at least one of those 14.1 zips worked fine and the machine was updated to 14.1. So the ZIP is likely not corrupted.
I erased the device check in the install-ZIP by changing the "lineage-14.1-20180625-nightly-Z00T-signed-edit.zip\lineage-14.1-20180625-nightly-Z00T-signed-edit\META-INF\com\google\android\updater-script"
This however leads to the error message "Invalid zip file format" - nothing get's installed.
Any ideas what can help?
capt_bob74 said:
Hi all,
I need some help please. I have an ASUS zenfone 2 laser 6 ze601kl. Came with a CN rom. No Google play services, go them installed using a google services installer. Trouble is, Android Wear dropped out and lost the watch details, backup failed randomly, google play services randomly crashed, play store etc. Wife wasn't too happy with me. Plus the random chinese apps updating and popping up with who knows what.
Current ROM CN_1.16.40.1715_20160623
Goal was to install a new WW rom which hopefully had working and stable google play services. Cannot install WW rom as it's CN - recovery error.
* gained root with KingRoot
* Debug mode on
* Unlocked bootloader using ASUS boot unlocker. Tried recovery, selected update from SD, same fail.
* installed ADB and fastboot (1.43) on windows 10 - nope, ADB recognised but always said 'cannot load <filename>.zip. Didn't matter which ROM or version.
* Tried to fastboot a new recovery and boot img, almost bricked it. Recovered using a CN ROM recovery and boot.img from
I have now:
* installed TWRP v3.0.2-5, which doesn't let me update to any ROM at all (WW official, WW rooted, resurrection remix etc)
Current error with UL-Z00T-WW-1.16.40.1524-user.zip is
Device SKU:
OTA image SKU: WW
Please use the right SKU for updating...
Updater process ended with ERROR: 7
Error installing zip file 'path/filename.zip'
Can't install Marshmallow WW ROM - says
Can't install this M package (tues sep 27 <time>) L less than 20160426 build (date/time)
Can't install RR Rom
Comparing TZ version TZ.BF.3.0.C3-00025 to ZT.BF.3.0.R2-00064
assert failed: asus.verify_trustzone("TZ.BF.3.0.c3-00025") == "1"
Basically I'm stuck, I can't use ADB (I did reinstall Windows 10, ADB still can't read <filename.zip> on my PC), and I can't seem to install any rom and get rid of teh CN ROM which I really, really, really want to.
Help?
Click to expand...
Click to collapse
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
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Azyaan124 said:
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Click to expand...
Click to collapse
Most pie roms are base on the latest stock pie firmware, you probably need to flash that. Plus Ur twrp version is probably not the newest, all the links are available in the telegram group, and I'm not going to put them here out of respect for the devs. But .339 firmware is the Oreo firmware, I think the one u need to flash is the .050 firmware.
The telegram groups have them all and a little searching can give you all the links you need.
Azyaan124 said:
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Click to expand...
Click to collapse
The latest Pixel Experience works great!
So you are on the Stock Firmware then.
1) Unlock the bootloader by Unofficial method (It will help when you want to relock it in future.)
2) Flash the latest TWRP Recovery.
3) Download whatever ROM you want to install and read all the requirements first! The error 7 you mentioned was the Firmware issue and could have been fixed by flashing the Firmware first and then the ROM.
GApps are not required for Pixel Experience as it comes with all the necessary Google Apps.
Hello!
I'm trying to install some new Android on my old phone j3110.
(I can install an "ORIGINAL" ROM (4 files using odin, android 5.1)... so my phone still works.)
Here is what i tried so far:
Using odin3 3.14.1
Using LineageOS 17.1 - > lineage-17.1-20200214-UNOFFICIAL-j3ltekx.zip
Using Android 9 - > crDroidAndroid-9.0-20190915-j3lte-v5.8.zip
I tested 2 versions of each ROM above: the original downloaded and a MODIFIED version, where i deleted the line about "assert" with
instructions here . I tested several TWRP versions, since this usually can be a problem. Here are the results:
twrp-3.3.1-0-j3ltekx - installed, booted, this was the error (for the 4 ROMS tested):
E1001: failed to update system image.
Updater process ended with error: 7
TWRP_3.0.2-0_SM-J320F.tar.md5 - installed but dont booted
twrp_3.0.2-1_sm-j320h_261016 - didnt installed
twrp-3.0.2-0-j3lte.img.tar - installed, booted, this were the errors:
android 9 MODIFIED
E1001: failed to update system image.
Updater process ended with error: 7
lineage 17 MODIFIED
E1001: failed to update system image.
Updater process ended with error: 7
android ORIGINAL
E3004: this package is for device: j3lte; this device is .
lineage 17 ORIGINAL
E3004: this package is for device: j3ltekx; this device is .
twrp-3.5.0_9-0-j3lte.img - installed, booted, this were the errors:
android 9 MODIFIED
E1001: failed to update system image.
Updater process ended with error: 7
lineage 17 MODIFIED
E1001: failed to update system image.
Updater process ended with error: 7
android ORIGINAL
E1001: failed to update system image.
Updater process ended with error: 7
lineage 17 ORIGINAL
E3004: this package is for device: j3ltekx; this device is .
twrp-3.3.1-0-j3lte.image - installed, booted, this were the errors:
android 9 MODIFIED
E1001: failed to update system image.
Updater process ended with error: 7
lineage 17 MODIFIED
E1001: failed to update system image.
Updater process ended with error: 7
android ORIGINAL
E1001: failed to update system image.
Updater process ended with error: 7
lineage 17 ORIGINAL
E3004: this package is for device: j3ltekx; this device is .
twrp-3.4.0-0-j3lte.img - installed, booted, this were the errors:
android 9 MODIFIED
E1001: failed to update system image.
Updater process ended with error: 7
lineage 17 MODIFIED
E1001: failed to update system image.
Updater process ended with error: 7
android ORIGINAL (had problem with mkdir)
E1001: failed to update system image.
Updater process ended with error: 7
lineage 17 ORIGINAL
E3004: this package is for device: j3ltekx; this device is j3lte.
twrp-3.1.1-0-j3lte.img - installed, booted, this were the errors:
android 9 MODIFIED
E1001: failed to update system image.
Updater process ended with error: 7
lineage 17 MODIFIED
E1001: failed to update system image.
Updater process ended with error: 7
android ORIGINAL
E3004: this package is for device: j3lte; this device is .
lineage 17 ORIGINAL
E3004: this package is for device: j3ltekx; this device is .
As you can see, the ORIGINAL versions had the "device problem", which removing the "assert" had solved this particular issue....
I always wiped Dalvik, System, Data and Cache before installing.
The ONLY thing is that i do not have a microSD right now, so the ROMS are in the internal storage of the phone. BUT, as i can install the
Rom with android 5.1, i dont know if this is a problem.
Can anyone help me? I can provide more information if necessary. Thanks!!
Most files you mentioned are originally for the SM-J320F/...
Not for the SM-J3110.
Maybe that is why it's not working properly on your device.
I found something for the SM-J3110 ... But outside of xda. And I do not know if the sources are reliable.
So if you want, search with Google and try if the rooting guide is working.
But IDK if there is a working custom rom available for your device with recent Android version.
It_ler said:
Most files you mentioned are originally for the SM-J320F/...
Not for the SM-J3110.
Maybe that is why it's not working properly on your device.
I found something for the SM-J3110 ... But outside of xda. And I do not know if the sources are reliable.
So if you want, search with Google and try if the rooting guide is working.
But IDK if there is a working custom rom available for your device with recent Android version.
Click to expand...
Click to collapse
Thanks for the answer!
I looked for J3110 several times in the past, and never found anything for this model.
Could you share what you found? Don't worry, I already bought a new phone, so my J3110 will serve only to mess around.
If I follow some unreliable guide and the phone "breaks" for good, does not matter anymore.
rodrigofarias85 said:
Thanks for the answer!
I looked for J3110 several times in the past, and never found anything for this model.
Could you share what you found? Don't worry, I already bought a new phone, so my J3110 will serve only to mess around.
If I follow some unreliable guide and the phone "breaks" for good, does not matter anymore.
Click to expand...
Click to collapse
Here is what I found ... no guarantee that it works:
How to Root Samsung Galaxy J3 Pro SM-J3110 (j3xproltezc) Easily [Simple Steps] | Android Biits
Steps to root Samsung Galaxy J3 Pro SM-J3110 (j3xproltezc) without TWRP Recovery. Dear folks, you have to download CF-Auto-Root cfar j3xproltezc smj3110 zip
androidbiits.com
And this:
Guide To Root Samsung Galaxy J3 Pro J3110 Lollipop 5.1.1 Tested Method
trusted mobile latest firmwares for various brands, stay tuned.
www.freemobilefirmware.com
Hi,
I hope I post into the correct category.
I am trying to install on LineageOS on a Samsung A3 SM-A300FU a3xelte using twrp and start to be completely confused.
I try to explain "historically".
I purchased the unused device running Android 5.
Following the installation instructions under <https://wiki.lineageos.org/devices/a3xelte/install>I tried to install several versions of TWRP for Samsung Galaxy A3 2016 (Exynos) (twrp-3.5.2_9-a3xelte to twrp-3.2.1-0-a3xelte) using heimdall as well as odin.
Every attempt ended up in "image too large for recovery".
Searching a smaller compatible version I tried versions down to twrp-3.0.0 --> Same result "image too large for recovery".
Even lineageos recovery (lineage-17.1-20210411-recovery-a3xelte) could not be installed successfully.
In the meantime I installed a combination stock rom (COMBINATION_OXA_FA44_A300FUXXU1AOK1_OXAOK1_CL4447487_QB7014253_REV00) and the probably newest Stock Rom (Baseband version A300FUXXU1CPH3, Android 6.0.1) and repeated the installation attempts for twrp as mentioned earlier.
"USB debugging" was activated. This device does not have option "OEM unlock", but some research is telling me that this is most likely not the problem.
In order to proceed somehow I installed successfully "TWRP_2.8.7.0_A3_F-H-FU_5.0.2_v2" using Odin. I know, that this version should not be used on a3xelte
Nevertheless this version has only 12,8 MB.
I could boot into twrp. The installation of lineage-os failed - as expected - because of the "wrong" device. Therefore I deleted the leading "assert" lines from updater-script, packed the whole thing newly as zip and tried installing using "adb sideload" as well as twrp "Install".
Obviously these installations failed on line
block_image_update("/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") || abort("E1001: Failed to update system image.");
I examined the existence of /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM. This path in fact does not exist on my device, but only /dev/block/platform/soc.0/by-name/SYSTEM
I changed the update script again using that path without installation success.
What completely screwed me up: If I run in twrp "blockdev --getsize64" it shows for
system : 2575302656 (2,4GB ?)
recovery : 15728640 (ca. 15 MB)
This explains why I could not install the twrp-a3xelte versions. They are actually too large for the recovery partition.
But the system partition seems to be large enough and I wonder why I found different pathes than the update-script expects.
Has anyone any idea how to get lineage-os installed on this device ?
Thanks in advance for any hint.
honza1 said:
Hi,
I hope I post into the correct category.
I am trying to install on LineageOS on a Samsung A3 SM-A300FU a3xelte using twrp and start to be completely confused.
I try to explain "historically".
I purchased the unused device running Android 5.
Following the installation instructions under <https://wiki.lineageos.org/devices/a3xelte/install>I tried to install several versions of TWRP for Samsung Galaxy A3 2016 (Exynos) (twrp-3.5.2_9-a3xelte to twrp-3.2.1-0-a3xelte) using heimdall as well as odin.
Every attempt ended up in "image too large for recovery".
Searching a smaller compatible version I tried versions down to twrp-3.0.0 --> Same result "image too large for recovery".
Even lineageos recovery (lineage-17.1-20210411-recovery-a3xelte) could not be installed successfully.
In the meantime I installed a combination stock rom (COMBINATION_OXA_FA44_A300FUXXU1AOK1_OXAOK1_CL4447487_QB7014253_REV00) and the probably newest Stock Rom (Baseband version A300FUXXU1CPH3, Android 6.0.1) and repeated the installation attempts for twrp as mentioned earlier.
"USB debugging" was activated. This device does not have option "OEM unlock", but some research is telling me that this is most likely not the problem.
In order to proceed somehow I installed successfully "TWRP_2.8.7.0_A3_F-H-FU_5.0.2_v2" using Odin. I know, that this version should not be used on a3xelte
Nevertheless this version has only 12,8 MB.
I could boot into twrp. The installation of lineage-os failed - as expected - because of the "wrong" device. Therefore I deleted the leading "assert" lines from updater-script, packed the whole thing newly as zip and tried installing using "adb sideload" as well as twrp "Install".
Obviously these installations failed on line
block_image_update("/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") || abort("E1001: Failed to update system image.");
I examined the existence of /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM. This path in fact does not exist on my device, but only /dev/block/platform/soc.0/by-name/SYSTEM
I changed the update script again using that path without installation success.
What completely screwed me up: If I run in twrp "blockdev --getsize64" it shows for
system : 2575302656 (2,4GB ?)
recovery : 15728640 (ca. 15 MB)
This explains why I could not install the twrp-a3xelte versions. They are actually too large for the recovery partition.
But the system partition seems to be large enough and I wonder why I found different pathes than the update-script expects.
Has anyone any idea how to get lineage-os installed on this device ?
Thanks in advance for any hint.
Click to expand...
Click to collapse
Hm ... unused device?
So it should be on stock firmware with original partition sizes.
Have you check to boot into stock recovery before?
Maybe there is something wrong with this "unused" device.
You can try to flash a recent stock firmware with original pit file to re-partition to stock partition sizes.
On windows pc use Odin for flashing.
When on stock Samsung firmware, try to flash twrp recovery again.