Hi, Devs!
i'm having problem with flashable zips. :crying:Every time i flash a zip in TWRP
which is not specially made for Zenfone 2 x86 devices it shows me an error
"updater process ended with error 255":crying:
I also changed the 'update-binary' file from METAF folder from the Zenfone to firmware. But again it shows me another error of "updatre process ended
with error 6".:crying:
Someone can please tell me how could i make zips X86 device compitable?
There is a TWRP available for the Zenfone 2. May not be the latest but it works, its in either Android Developement or Original Android Developement.
i have TWRP
But i have TWRP version 3.0.0.0?
But let me know that the above problem is becouse of TWPR or the ZIP file?
I was updating my phone and when i started again, i couldnt do that, i tried flashing stock rom and i get this problem "invalid spare file format at header magi..."
Note: i had to convert System.new.dat to imagen flashable, the file has a size of 3.9 Gb
Hello.
I bought a refurbished a3y17lte and expect it will run /e/ in GSI flavor (no official nor unofficial build yet).
- OEM unlock enabled > FRP LOCK: OFF in download mode,
- manual updated to latest 'Orange Télécom' version from device itself,
- then I flashed latest stock ROM with Heimdall (Debian Buster),
-
Code:
a3y17lte:/ $ getprop ro.treble.enabled
false
so I posted > there <.
I've got any more 'n00b' questions...
While unzipping stock image, Xarchiver just needs
Code:
~# apt install lz4
Then, in CSC folder I've got an A3Y17LTE_EUR_OPEN.pit file. May I flash it too ? Stock partitioning shows:
Code:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: -
FOTA Filename:
======I tried to flash TWRP and install LOS 16.0; 3.3.1 worked with difficulty (needs to choose 'Don't install' twrp as sytem app), 3.3.0 works, 3.4.0 return 'ERROR 7', so I went back to stock (heimdall flash). May I prefer OrangeFox recovery ?
Expecting this Exynos 7870 will run GSI, may I install 'Repartition' script or try H-Vendor (both by @Astrako ) ? I'm not sure to understand well how to use. What are the proper steps to avoid brick ?
Thanks a lot.
P.S.: I'm reading this (old) thread...
P.S.2: and this other one. I will become fan of @Astrako
Hello.
Well, well, well, I don't want 'another brick'... so fast replies on telegram Pruh 7870 don't match with my poor knowledge. I'm coming from Moto, easy to use with twrp and adb/fastboot...
My pit contains CARRIER instead of VENDOR (certainly why Shelter points a 'custom ROM'), so I probably need to flash europe_open.pit from stock ROM first. Then, I'm not sure what exactly do:
- flash custom recovery (twrp, orangefox, skyhawk?) first,
- universal-repartitioner_7870 (or older?),
- treble,
- a a_only gsi (e-pie-gsi),
- gsi_patch.
I will wait for advice and read again and again @starbright_ (#58) to understand how to proceed...
Note I want to try e-pie first (full build) then Q (light custom build).
Thanks.
P.S.: found last twrp custom 3.4.0-0-a3y17lte, thanks.
trefix said:
Hello.
Well, well, well, I don't want 'another brick'... so fast replies on telegram Pruh 7870 don't match with my poor knowledge. I'm coming from Moto, easy to use with twrp and adb/fastboot...
My pit contains CARRIER instead of VENDOR (certainly why Shelter points a 'custom ROM'), so I probably need to flash europe_open.pit from stock ROM first. Then, I'm not sure what exactly do:
- flash custom recovery (twrp, orangefox, skyhawk?) first,
- universal-repartitioner_7870 (or older?),
- treble,
- a a_only gsi (e-pie-gsi),
- gsi_patch.
I will wait for advice and read again and again @starbright_ (#58) to understand how to proceed...
Note I want to try e-pie first (full build) then Q (light custom build).
Thanks.
P.S.: found last twrp custom 3.4.0-0-a3y17lte, thanks.
Click to expand...
Click to collapse
What is a e-pie?
Custom Recovery (I thing which one is not important) is first. But isn't order explained in my post? All custom ROMs have some deficits. I try to modify a stock now, but I ma just facing some problems with location... (look for the deploat thread if you like). So frustrating....
Thanks.
Sorry, e-pie is /e/ OS based on LOS-Pie. No build for a3y17lte except a GSI one.
Your post (linked above) is fine, but I'm not sure about some details, as 'install just system' (about flashing GSI ROM)...
May I follow straight or adapt with new tools (H-Vendor, universal_repartitioner)? I don't already see what's happen at each step.
trefix said:
Thanks.
Sorry, e-pie is /e/ OS based on LOS-Pie. No build for a3y17lte except a GSI one.
Your post (linked above) is fine, but I'm not sure about some details, as 'install just system' (about flashing GSI ROM)...
May I follow straight or adapt with new tools (H-Vendor, universal_repartitioner)? I don't already see what's happen at each step.
Click to expand...
Click to collapse
Repartition is needed in both cases. Treble is for GSI Pie (A only) and H-ROM for A/B Q. Is this answering you question?
Hello.
Yes, thanks > two different combo so I need to choose first Pie or Q flavor. And clean flash from Pie to Q....
I will try, probably tomorrow. Thanks again.
Hello.
First of all, after 'Custom rom' message from Shelter, it seems I need to flash eur_open.pit (entries 24 to 27 are slightly different) to complete 'stock' flash. I have the right a3y17lte_eur_open.pit from Samsung stock rom, but didn't know how to flash safely the pit. I already extracted and saved on PC the 'factory' (Orange Telecom) pit with Heimdall...
I found on web, to flash the pit:
Code:
heimdall flash --repartition -- --pit my-samsung-file.pit
- Can I flash lonely, boot in download mode (buttons) then reboot system?
- May I add a new flash of all files extracted from Samsung's stock ROM (already flashed)?.
Thanks in advance.
.
P.S.: don't know where adv-env.img has to be flashed...
Hi.
Code:
heimdall flash --repartition --PIT A3Y17LTE_EUR_OPEN.pit --no-reboot
Code:
Uploading PIT
ERROR: Failed to receive PIT file part response!
ERROR: PIT upload failed!
Hello.
Back to 'seller' ROM (fr. Orange telecom) but still 'PIT upload failed' while flashing stock standard ROM and nor more buttons-mode recovery acces, with 'No command' response.
TWRP (unofficial from Pruh 7870) was running buggy, too...
'Orange' has a A3Y17LTE_EUR_OPEN_HIDDEN200M.pit (and ROM has a lot of bloatwares).
PS: same while launching command as root, with 'Can't open ---.pit file'
Édith used a w$ PC (with Odin 3.14.4) and then device now runs stock 'standard' ROM with repartition OK I will begin to flash treble...
Hello.
Well, trying 'pie' method, I've always have an issue during process: one or other partition falls 'unmountable', despite a reboot in Recovery after each successful flash.
- I'd first flash Disable_DM-verity_ForceEncrypt_03.04.2020.zip with twrp-3.3.1-0 (didn't work with twrp-3.4.0-0-astrako),
- when 'repartitioner' works (with /vendor seen 'mountable' in Advanced > Mount), treble's installation ends with " unable to mount '/vendor' ",
- installing only System (choose rom.img > 3 checkboxes Boot / Recovery / System) ends in a bootloop,
- flashing gsi-patch doesn't solve and ends in bootloop too...
Strange thing, despite a full wipe and format data, date/time remain after flashing stock ROM (with *.pit) and twrp-3.3.1-0 sometimes comes back by itself, replacing 3.4.0-0-astrako.
Now I presume this device (version needing to disable DM-verity) asks for an other flash sequence. Perhaps something like:
disable_DM > Repartitioner > GSI-patch > Treble > ROM.
???
Advises are welcome.
P.S.: Treble always return " failed to mount '/vendor' ", all tests went to bootloop.
PS2: two consecutive 'Repartition' whit reboot in Recovery, first 'failed... vendor', second OK but recovery 3.4.0-0 self downgrade to 3.3.1-0
PS3: twrp-3.4.0-0-astrako doesn't show re-partition (no more /vendor, from Advanced > Mount), 3.3.1-0 does I will try with another recovery, because it seems something isn't stable...
If you still need help with this, find me in Telegram @martinvalentine
Hi,
I am "building" (first had to fix the LCD etc.) a de-googled DAISY. I managed to unlock the bootloader, install TWRP, and root the original OS (Android One 10).
The problems started when I tried to install a custom ROM (at first Havoc, but other gave the same results). Just as instructed (YT, other pages, here...) I:
- formatted via TWRP
- REBOOT to TWRP
- wipe all except SD
- install ROM from zip
...and at this point I came across an error message
Error applying update: 7 (Error code: : kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Many solutions suggest flashing boot.img from the ROM package, but (WHY?!?) all ROM's ((Havos, crDroid etc.) for daisy have no such file, although other devices have boot.img in their package.
I'm pretty much clueless... :/
Help, and thanks in advance...
mothzart said:
Hi,
I am "building" (first had to fix the LCD etc.) a de-googled DAISY. I managed to unlock the bootloader, install TWRP, and root the original OS (Android One 10).
The problems started when I tried to install a custom ROM (at first Havoc, but other gave the same results). Just as instructed (YT, other pages, here...) I:
- formatted via TWRP
- REBOOT to TWRP
- wipe all except SD
- install ROM from zip
...and at this point I came across an error message
Error applying update: 7 (Error code: : kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Many solutions suggest flashing boot.img from the ROM package, but (WHY?!?) all ROM's ((Havos, crDroid etc.) for daisy have no such file, although other devices have boot.img in their package.
I'm pretty much clueless... :/
Help, and thanks in advance...
Click to expand...
Click to collapse
Error 1 usually means wrong install package or wrong TWRP.
Are you using TWRP by offain?
[SOLVED]
The whole problem was that TWRP was wrong (not even offain as far as I remember). But I got a HUUUUGE amount of help (MANY THANX!!!!) from opal06 (main maintainer for crDroid on daisy) on Telegram channel dedicated to crDroid on daisy.
So If anyone hase similar problems - go to Telegram group - they will help you!
After flashing right (modified) TWRP versions, evrthng went fine, although I got to admit it was pretty complicated for [unlock + TWRP + custom rom + root] combo. On lavender it was much easier
cya all, good luck!
I tried to install the evolution x rom on my Redmi 8A phone I can confirm that I downloaded the right file then proceed to flash it on orange fox recovery project (sideloaded it) then suddenly it throws back the error code
Updater process ended error : 255
Tried multiple times reflashed the recovery changing to twrp ( I used the official recovery) on my previous device I also experienced this problem and there was an unofficial twrp image that solved this they say it's because I tried to flash a 64 bit Rom on a 32 bit recovery plus I can't find any "64 bit" version for my device any help????
If you need any information comment it down I won't reply instantly but I will