error 7 on Twrp - LeEco Le 2 ROMs, Kernels, Recoveries, & Other Deve

When i try to flash a ROM on my leeco, appears in twrp the error 7 what means???
Have a solution for this error??
And custom ROM android 7 or lineage os, aosp, resurrection remix ROMs
for leeco le s3

A some GuY said:
When i try to flash a ROM on my leeco, appears in twrp the error 7 what means???
Have a solution for this error??
And custom ROM android 7 or lineage os, aosp, resurrection remix ROMs
for leeco le s3
Click to expand...
Click to collapse
My dear Friend
Do not put everything here on XDA, do some exercise and search on google, you will get your answer. i request you to please close this thread.:good:

Error 7 in TWRP-Recovery means that the ROM-Image (zip file) doesn't match your phone. In our case there exist several models for the S2 (SD652): X520, X522, X526 and X527.
If you want to avoid Error 7, you need to open the zip-file (maybe 7zip):
- go to directory META-INF \ com \ google \ android
- open the file "updater-script" with an editor like notepad++
- place a # at the beginning of the first two lines, looks like this:
# (!less_than_int(....
# get_device_compatible...
- save the modifications in the zip-file and put it into the phone
- now update your phone via twrp

A some GuY said:
When i try to flash a ROM on my leeco, appears in twrp the error 7 what means???
Have a solution for this error??
And custom ROM android 7 or lineage os, aosp, resurrection remix ROMs for leeco le s3
Click to expand...
Click to collapse
It is possible to make a screen shot of the whole error message in TWRP.
There is more than one Error 7.
Provide the screen shot, to be sure you'll get the correct answer.

JamBax said:
It is possible to make a screen shot of the whole error message in TWRP.
There is more than one Error 7.
Provide the screen shot, to be sure you'll get the correct answer.
Click to expand...
Click to collapse
Ok i send a print and thx to try to help me

Andy_04 said:
Error 7 in TWRP-Recovery means that the ROM-Image (zip file) doesn't match your phone. In our case there exist several models for the S2 (SD652): X520, X522, X526 and X527.
If you want to avoid Error 7, you need to open the zip-file (maybe 7zip):
- go to directory META-INF \ com \ google \ android
- open the file "updater-script" with an editor like notepad++
- place a # at the beginning of the first two lines, looks like this:
# (!less_than_int(....
# get_device_compatible...
- save the modifications in the zip-file and put it into the phone
- now update your phone via twrp
Click to expand...
Click to collapse
Ok dude, i can try do this your help, thx man

Andy_04 said:
Error 7 in TWRP-Recovery means that the ROM-Image (zip file) doesn't match your phone. In our case there exist several models for the S2 (SD652): X520, X522, X526 and X527.
If you want to avoid Error 7, you need to open the zip-file (maybe 7zip):
- go to directory META-INF \ com \ google \ android
- open the file "updater-script" with an editor like notepad++
- place a # at the beginning of the first two lines, looks like this:
# (!less_than_int(....
# get_device_compatible...
- save the modifications in the zip-file and put it into the phone
- now update your phone via twrp
Click to expand...
Click to collapse
Thanks....
Do I have to add space after the #?
# (!less_than_int(1513360281, getprop("ro.build.date.utc"))) || abort("Can't install this package (Sat Dec 16 01:51:21 CST 2017) over newer build (" + getprop("ro.build.date") + ").");
# getprop("ro.product.device") == "le_x6" || abort("This package is for "le_x6" devices; this is a "" + getprop("ro.product.device") + "".");

Related

[HOW TO][N00B][w/oPC]How to make a flashable.zip[No PC needed!]

This is my most favourite topic!
I will enlight you all how to create your own flashable zip file. I'm trying to make it as n00bfriendly as I can.
Code:
DISCLAMER
Follow this guide step by step so nothing can happen. Anyway I'm not responsible for any damage caused because of me or this thread. If you have any questions or problems, don't be shy and
[B]ask me I will help or create it for you![/B]
So here we go:
There are two ways how to do it:
WAY ONE (PC):
What you need:
*brain (for those who don't know...)
*your pc
*notepad++
*7zip
*FlashGuide.zip (can be found in attachments)
WAY TWO (I9001):
*brain (yes, here too...)
*your I9001 (you don't need root)
*FlashGuide.zip (can be found in attachments)
*Explorer or RootExplorer app
******************************
WAY ONE (PC):
1.download the files for your pc and install them
2.open 7zip and unzip FlashGuide.zip
3.In the folder FlashGuide you will see two sub-folders which are as "META-INF" and "system"
4.see: META-INF
5.see: SYSTEM
WAY TWO (I9001):
1.download the files for your I9001
2.open the app and unzip FlashGuide.zip
3.In the folder FlashGuide you will see two sub-folders which are as "META-INF" and "system"
4.see: META-INF
5.see: SYSTEM
-----------------------------
META-INF​
Go back to the root of the folder and open up"META-INF". leave those files untouched and open "com" and then "android".
Inside the android folder, you will see two files named as "update-binary" and updater-script.
WAY ONE (PC):
Open the "updater-script" file with "notepad++".
You are free now to type some code you want just press HERE
WAY TWO (I9001):
Open the "updater-script" file by longpress it and choose "Text Editor".
You are free now to type some code you want just press HERE
-----------------------------
SYSTEM​
Concentration! It's nearly finished. Let's see, what you have to do with the "system" folder. It's in the root of the FlashGuide folder.
You should add your MOD now, HOW TO:
ADD an APP
If you want to add an apk file then create a folder named "app" and that "app" folder contains the apk file(s) that you want to put in the system partition of the ROM.
FRAMEWORK
If you want to add framework-mods then add a folder named "framework" into the "system" folder.put your framework mods into that folder. (in the most cases the Framework mods are in a Framework-res.apk file.)
LIBS
If you want to change libs then create a folder named "lib" and put the libs in there.
BIN
If you want to put bin files then the subfolder in the system subfolder will be "bin" and it will contain the bin files.
SCRIPTS
If you want to add scripts then name a folder in the system "etc", create there a folder named "init.d" and put the scripts in there.
NOW CHECK THIS LIST:
I updated the UPDATER-SCRIPT
√
I updated SYSTEM
√
IF NOT BOTH BOXES ARE TICKED, THEN YOU HAVE TO GO BACK!
After doing all that:
WAY ONE (PC):
open 7zip, go to the directory where the FlashGuide folder is located and zip it
WAY TWO (I9001):
After you modded the "Updater-Script" a backup had automatically been created. In this case it's the Updater-Script.bak data. Just delete it. Then go back to the directory where the FlashGuide folder is located, do long press the FlashGuide folder, scroll down, select "zip this folder" and follow further instructions.
Now you can rename the .zip to whatever you want!
THAT's ALL FOLKS!
PRESS HELP IF I THANKED YOU!
-----------------------------
HOW TO EDIT THE UPDATER- SCRIPT:
So once the updater-script has been opened with text editor (notepad++/Explorer), you will have to type some codes or you will get no reaction.
1​
To Display the information of the particular Mod when you select to flash it in CWM Recovery
Code:
ui_print("***The Text you want to display***");
2​
To mount the /system partition
Code:
run_program("/sbin/busybox", "mount", "/system");
3​
To add the apps in the /system partition
Code:
package_extract_dir("system", "/system");
4​
To unmount the /system partition
Code:
run_program("/sbin/busybox", "unmount", "/system");
5​
To delete some apps, frameworks,...
Code:
delete("/system/app/XY.apk");
or
delete("/system/framework/franework-res.apk");
6​
To show progress
Code:
e.g.:
show_progress(0.500000, 0);
show_progress(0.500000, 20) show_progress(0.500000, 40) show_progress(0.500000, 60) show_progress(0.500000, 80) show_progress(1.000000, 0)
Basically the show_progress command indicates the progress of the installation of the MOD.
an example how to use it: [HIDE]
after writing the name/info of the mod write:
show_progress(0.500000, 0);
after writing the code to mount the system partition,you can write the next one:
show_progress(0.500000, 20);
extracting the package from the system partition: show_progress(0.500000, 40);
unmount system partition show_progress(0.500000, 60);
after writing the "happy ending" of installing this zip, write: show_progress(0.500000, 80);
maybe a "reboot system" or "thanks for flashing" phrase, write: show_progress(1.000000, 0)[/HIDE]
Basically the show_progress command indicates the progress of the installation of the mod.
In this case the progress bar fill up in increments of 10, with a 0.5 second delay. What is actually being done by these lines, however, is to keep adding 0.5.
If the progress commands had enough time, this would also mean that each chunk would fill at a slower pace (since the duration is increasing), but the script moves fast enough that the user never sees this.
None of this actually changes the functionality of the script, hence my earlier declaration that this was somewhat POINTLESS to learn. This is strictly an aesthetic issue for the user, but if you are going to write scripts, I hope this comes in handy.
NOTE:
If you are using CM, you have to mount your "system" manually, using the option "mount and storage" in CWM
PRESS HELP IF I THANKED YOU ;D
IF YOU WANT TO LET ME CREATE YOUR FLASHABLE ZIP, TELL ME.
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
very detailed, well done :good:
Sent from my Galaxy Nexus using xda app-developers app
tomixdev said:
very detailed, well done :good:
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot! you know, it's my first Tutorial! Cheers
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
yeah, thanks man now i don't have to use my pc (which hangs even for a windows 7) to make a zip
I've juste tried this and at the flash, it show me an error ...
In the zip there was just root browser in app and the modded update-script !
Sent from my GT-I9001 using xda premium
LiiQuoR said:
I've juste tried this and at the flash, it show me an error ...
In the zip there was just root browser in app and the modded update-script !
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
please tell me what you wanted to do and upload the file. i will correct it for you
EDIT: have you deleted the updater-script.bak file?
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
Its ok i'm an idiot ! But when i flashed the zip i had a bootloop !
It's just a test but here is my zip : http://depositfiles.com/files/psp2rs2op
Can you put the show_progress in it and can you explain the "(0.500000, 20);" in the command plz !
Sent from my GT-I9001 using xda premium
LiiQuoR said:
Its ok i'm an idiot ! But when i flashed the zip i had a bootloop !
It's just a test but here is my zip : http://depositfiles.com/files/psp2rs2op
Can you put the show_progress in it and can you explain the "(0.500000, 20);" in the command plz !
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
of course i can do. but not now, tomorrow i'm all yours
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
outerh3aven said:
of course i can do. but not now, tomorrow i'm all yours
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
Click to expand...
Click to collapse
K ! Thanks :thumbup: and good night !
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
LiiQuoR said:
K ! Thanks :thumbup: and good night !
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
Click to expand...
Click to collapse
Sorry, really well done .zip! Just forgot to add the delete section (If you have an app, etc. already installed) should work now.
will add delete section, permission section and set_progress section right after school.
:thumbup: really well done LiiQuouR!
EDIT: if you are on a Cyanogenmod, aosp or anything what isn't stock 2.3.6 rom, you have to mount system manually
In CWM go to mounts and storage and choose system
, might be the mistake too...
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
I'm on UltraGen 1.6 with twrp!
Thx ! Can you just explain the comand show_progress now^^?
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
LiiQuoR said:
I'm on UltraGen 1.6 with twrp
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
Click to expand...
Click to collapse
UltraGen is CM9 based, so you have to mount manually
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
Ok in the command for unmount system you have written "umount" its "unmount" no?
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
LiiQuoR said:
Ok in the command for unmount system you have written "umount" its "unmount" no?
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
Click to expand...
Click to collapse
I don't know how it's in TWPR, I'm using CWM. usually the system is not mounted
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
Are you sure of your zip ?
Because i've mounted /system , i've flashed the zip and it failed and when i reboot the phone , it bootlooped... can you please review my zip? (Yours)
Sent from my GT-I9001 using xda premium
LiiQuoR said:
Are you sure of your zip ?
Because i've mounted /system , i've flashed the zip and it failed and when i reboot the phone , it bootlooped... can you please review my zip? (Yours)
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
sorry, today I'm totally retarded, got a 3hour nostop test and i'm exhausted as hell... will do it some time later at home.
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
In the end line of update script you.should put an empty line and after mounting system you should unmount it and be sure your premissions are fixed!
If you do that rules you will never have a bootloop!
alireza7991 said:
In the end line of update script you.should put an empty line and after mounting system you should unmount it and be sure your premissions are fixed!
If you do that rules you will never have a bootloop!
Click to expand...
Click to collapse
wrong, but thanks for your try. worked for me every time without this empty line.
finally got my mistake (today was not my day). used the gb meta-inf files to make a ics zip
can be downloaded here LiiQuoR
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
outerh3aven said:
wrong, but thanks for your try. worked for me every time without this empty line.
finally got my mistake (today was not my day). used the gb files to make a ics zip
can be downloaded here LiiQuoR
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
Click to expand...
Click to collapse
Ok ! But link doesn't work ! Always a problem not your day as you said
Sent from my GT-I9001 using xda premium

[ToolKit] Acer Iconia v0.9.4 ***New: Supporting Acer Liquid S1***

The Acer Iconia Toolkit is supporting following devices at the moment:
B1-A71
B1-710
B1-A710
B1-711
B1-720
A1-810
A1-811
A3-A10
Liquid S1
Only use these methods if you are sure the device cannot be rooted using a custom recovery from the following thread:
http://forum.xda-developers.com/andr...ax-b1-t2875894
Intel based devices will not be supported ever by this toolkit! Only Mediatek chips are supported!
At the moment the following features are available:
Root from scratch (Unix only / recommended)
Root with prerooted Image (see Download links at the bottom)
Unroot
Swap External <-> Internal SD
Odex ROM
Pull system.img.gz off your device
Download Acer Iconia Toolkit Latest Version
Older Versions:
v0.9.0
v0.8.5
v0.8.4
v0.8.3
v0.8.2
Thank you goes to:
FireDiamond, bullbrand, pawitp, alba81, sodaFR, MatrixDJ96, ak6, min-dfreak, Gilly10, agentdeep, nick_1964, sampod
and the testers
Acer Iconia B1-A71:
Unlock Bootloader
CWM update, that removes bloat
thx to FireDiamond
Apply the "Invalid Partition Error" fix before rooting!!!
To avoid unfixable bootloop, first apply this patch from Acer.
Install the APK, start it, click on FixG1PMT (no feedback) and uninstall afterwards. Good luck!
If you're rooting with prerooted system.img.gz here are the Downloads. Pick the one, fitting to the firmware installed on your tablet, otherwise you will get into bootloop!
RV03RC05:
Acer Firmware Update [mirror] [mirror + md5]
RV04RC04:
[system.img.gz] [mirror]
RV05RC05:
Acer Firmware Update [mirror1] [mirror2] [mirror3] [mirror4 + md5] [mirror5 + md5]
[system.img.gz]
RV02RC12:
system.img.gz
Acer Iconia B1-710 / B1-A710:
Unlock Bootloader (thx to FireDiamond and abstrkt1337)
RV04RC01:
system.img.gz [mirror1] [mirror2]
Stock system Images for B1-710 RV04RC01
Hamza91: stock, rooted
RV04RC01_PA_CA:
Stock and Rooted system image
Acer Iconia B1-711:
RV01RC04_WW_GEN1:
system.img.gz
Acer Iconia B1-720:
RV03RC01_WW_GEN1:
system.img.gz (thx to Hayastan)
RV07RC01_WW_GEN1:
system.img.gz (thx to Hayastan)
Acer Iconia A1-810:
Acer Firmwares
Modified XPosed Installer
RV03RC08:
system.img.gz
RV18RC07_WW_GEN1:
update.zip (about 4MB)
system.img.gz with /system RW workaround (MD5 = 214db984aee42ef0c05d1cfa43d193c1) (needs extra config and SuperSU instead of Superuser) [torrent] (see this post also)
RV21RC02_WW_GEN1:
update.zip
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV21RC03_TWN:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV27RC02_PA_CA:
stock system.img.gz (rename to system.img.gz first!)
system.img.gz (rename to system.img.gz first!)
RV27RC03_WW_GEN1:
system.img.gz
stock system.img.gz
update.zip
RV18RC10_PA_CA:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV26RC06_PA_CUS1:
system.img.gz
Stock Images: (Workaround to unroot: Put the system.img.gz of your version into system_image and choose root option in toolkit)
RV03RC08:
system.img.gz
RV18RC07:
system.img.gz ( MD5=550ECDB192F5668264B11B1070F4B932 )
How to root from scratch
Acer Iconia A1-811:
RV01RC11_WW_GEN1:
Acer Firmware Update
RV02RC20:
system.img.gz rooted and stock (including xposed) (thx to konsolen!!)
RV02RC22_TWN_GEN1:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
Unbrick:
Stock Firmware RV01RC11 (copy on SD and flash from recovery)
Acer Iconia A3-A10:
A3-A10_RV05RC01_PA_CA:
stock system image
Your device not listed above?
Help us getting your device to work with the toolkit.
See this post how you can help.
Common
B1-A71 / B1-710 / B1-A710: Install this after rooting: Superuser App on Google Play Store
A1-810 / A1-811 / B1-711: Install this after rooting: SuperSU App on Google Play Store
Verify your root: Root Checker on Play Store
FAQ
Q: I'm stuck inside a bootloop after rooting!!!11
A1: The system.img.gz you applied, wasn't suiting to the firmware version installed on your tablet. Download latest Acer firmware update ( !!! if available !!!), copy it on a micro sd card, plug it into your Iconia, go to recovery by holding Volume up and Power button while device is turned off. Then choose apply update from sd card.
A2: If you cannot apply any Acer firmware, because you always get a partition error while installing, you should do a reboot after you get the error. A user reported that this made her/his device boot into Android again, showing the new version in settings -> info. Good luck
A3: If your device is really bricked you could try bring it back to life. Here you find help: link1, link2, link3, link4 (many thanks to Gilly10, drmad and Hamza91)
A4 (B1-A71, B1-710, B1-711 only): Unbrick
A5: If the A1 - A4 didn't help. Send back the device to Acer. Tell them you tried to apply an update from sd card and ended up in this bootloop. Sending device back to Acer over UPS is free. Good luck!
Q: Successfully rooted, but still no root after rebooting!
A: Have you installed Superuser App from Google Play Store?
(B1-A71 only)Q: Cannot update, always getting ERROR: - Invalid partition setting; 17: fat 238e8000:888e8000; Instalation aborted.
A: Download "Invalid Partition Error" Patch.
(B1-A71 only)Q: I applied update from RV05RC05 to RV05RC06 but still it shows RV05RC05.
A: There is no RV05RC06. It is the RV05RC05. It got on Acers Download section with a RV05RC06 named zip file. But the content is 100% equal to RV05RC05.
Q: Toolkit fails or crashes for any reason and I don't know what to do.
A: Run it again with parameter -d, e.g.: toolkit.exe -d and post the entire output here.
Q: Root from scratch on Linux doesn't work because of Error message: 'No such file or directory bin/posix/64/adb'
A: sudo apt-get install ia32-libs libstdc++6 libgcc1 zlib1g libncurses5 libsdl1.2debian
Q: Can i flash a custom recovery?
A: No, because bootloader is locked. You would brick your tablet.
Q: Are there Custom ROMs?
A: No, see answer above.
Q: Is my data wiped during root?
A: No.
Q: Do i lose root after factory reset or wipe date?
A: No.
Q: I get an error in Engineer mode entering telnet command.
A: If Swiftkey is installed / enabled try settings Google AOSP Keyboard as default.
Q: How can I start telnet server manually?
A: Try this.
What you can do with root:
Apply Supercharger V6 by zeppelinrox and significally speed up your tablet! [My small How-To]
Install Adaway, an ad-blocker for webbrowsers and apps containing ads.
Install ROM Toolbox and customize boot screen and other funny things.
Install Titanium Backup to Backup, Freeze, Uninstall any App and more.
Install Datasync to sync app data like save states between rooted devices.
What you can NOT do with root on these devices:
Change DPI
Flash Custom Recoveries
Flash Custom ROMs
Sources and Changelos @ github (thanks to nikagl)
Changelog:
v0.9.4
======
- Updated SuperSU to 2.46
- Removed Xposed APK
- Added Liquid S1 support!
v0.9.3
======
- Fix Xposed removal
- Wait longer for MTKLogger to press settings
- Add 811 and KK 810 and 811 to root from system.img
v0.9.2
======
- Removed Xposed till it works
- Add global for allatonce
v0.9.1
======
Added option to enable write access to external sdcard
Added comment for Xposed not working
Removed su delete command in invalid section
v0.9.0
======
- A1-811: Kitkat Support
- A1-xxx: Added proper su-binary
- Added timestamps
- Added descision for Superuser/Supersu
- Added selection for Xposed **not working yet**
- Added option to enable write access to external sdcard
- Added selection to continue automatically (also import the system instead of waiting for enter)
- Removed invalid quote and double exit command
- Added forward delete of characters to make sure Run command is empty
- Added some additional messages during the root process
v0.8.5
======
- A1-810: Fixed target directory for system image (no permissions for /cache directory since Kitkat)
- A1-810: Fixed root from scratch for Kitkat versions (thanks to Just_Another_N00b)
v0.8.4
======
- A1-810: Fixed root for Android Kitkat >= 4.4.2
- A1-810: Fixed abd devices id, changed sind Kitkat update
v0.8.3
======
- Fixed pulling system.img.gz from Windows
v0.8.2
======
- New: Supporting B1-720
v0.8.1
======
- A1-81x: Fixed missing read/write permissions for /system partition (thanks
to twu2!)
- All other devices: fixed missing path to su binary (thanks to arzakon.nn)
v0.8.0
======
- New: Pull system.img.gz from your tablet
- New: Supporting A3-A10
v0.7.8
======
- fixed Swap Internal to External for A1 and B1-710
v0.7.7
======
- Supporting Swap Internal to External for A1 and B1-710
- fixed bug in root from scratch: checking for /bin/su although it's not there
Full Changelog inside the Download.
Error "Permision denied"
entonjackson said:
Changelog:
v0.2.1
======
- Windows: Providing an .exe, so Python is no more needed for Windows users. But you could still use the Python script.
- Unix: Python3 compatibility fixes
v0.2.0
======
- supporting windows 64 and 32 bit (only for rooting with prerooted system.img.gz)
- Linux: added option to choose between 'Root from scratch' and 'Root from prerooted image'
- supporting all versions between python 2.7.4 and 3.3
v0.1.1
======
- supporting linux 64 AND 32bit
- instructions at the beginning
- make compatible to python 3.3
v0.1.0
======
- initial release, only supporting linux 64bit
Click to expand...
Click to collapse
Hi Thanks for your effor and sharing with us.
I got error "failed to copy system._image\system.image.gz to cache/system.image.gz , permission denied
can you give me solution.
thanks very much
cakadut said:
Hi Thanks for your effor and sharing with us.
I got error "failed to copy system._image\system.image.gz to cache/system.image.gz , permission denied
can you give me solution.
thanks very much
Click to expand...
Click to collapse
Windows or Linux?
edit: Ok i found the issue, I just fixed it and going to upload a new version this evening.
New version v0.2.2 is up.
entonjackson said:
New version v0.2.2 is up.
Click to expand...
Click to collapse
I thanks for your work.
I have one problem
failed to copy 'system_image\system.img.gz' to '/cache/system.img.gz': Permissio
n denied
Traceback (most recent call last):
File "easy_root_iconia_b1.py", line 724, in <module>
else:
File "easy_root_iconia_b1.py", line 26, in main
win_main(python3)
File "easy_root_iconia_b1.py", line 642, in win_main
out = p.stdout.readline()
File "subprocess.pyc", line 575, in check_output
subprocess.CalledProcessError: Command ' bin\windows\32\adb.exe push system_imag
e\system.img.gz /cache' returned non-zero exit status 1
Thanks for your futur help
sorry for my english
V0.2.2 still Error
entonjackson said:
New version v0.2.2 is up.
Click to expand...
Click to collapse
Dear Eaton,
after dowbload and run v0.2.2 , still found same problem.
No Progress bar during copy image.
and system shown
failed to copy 'system_image\system.img.gz' to '/cache/system.img.gz': Permissio
n denied
Traceback (most recent call last):
File "easy_root_iconia_b1.py", line 724, in <module>
else:
File "easy_root_iconia_b1.py", line 26, in main
win_main(python3)
File "easy_root_iconia_b1.py", line 642, in win_main
out = p.stdout.readline()
File "subprocess.pyc", line 575, in check_output
subprocess.CalledProcessError: Command ' bin\windows\32\adb.exe push system_imag
e\system.img.gz /cache' returned non-zero exit status 1
Note I am using windows 7.- 64 Bit
Regards,
I uploaded a new version where I added some commands that hopefully resolve the permissions issues.
The problem is, that I can't reproduce it.
Are you rooting the Iconia the first time? or did you already have root before?
Regarding the progress bar. It only appears when writing the system.img.gz
I have Windows 7 64 bit, btw.
entonjackson said:
I uploaded a new version where I added some commands that hopefully resolve the permissions issues.
The problem is, that I can't reproduce it.
Are you rooting the Iconia the first time? or did you already have root before?
Regarding the progress bar. It only appears when writing the system.img.gz
I have Windows 7 64 bit, btw.
Click to expand...
Click to collapse
Dear Enton,
Yes this is the first time B1 will rooting,
I will try again, and report to you,
Regards
cakadut said:
Dear Enton,
Yes this is the first time B1 will rooting,
I will try again, and report to you,
Regards
Click to expand...
Click to collapse
Dear Enton,
The Messages still same, I Attached the Error Pic.
Note :
Iconia B1-A71
ROM 16 GB
RAM 512 MB
Android Version : 4.1.2
Kernel Version : 3.4.0
Image Version : Acer_AV051_B1-A71_RV05RC05_WW_GEN1
Build Number : Acer_AV051_B1-A71_1.258.00_WW_GEN1
Regards,
cakadut said:
Dear Enton,
The Messages still same, I Attached the Error Pic.
Note :
Iconia B1-A71
ROM 16 GB
RAM 512 MB
Android Version : 4.1.2
Kernel Version : 3.4.0
Image Version : Acer_AV051_B1-A71_RV05RC05_WW_GEN1
Build Number : Acer_AV051_B1-A71_1.258.00_WW_GEN1
Regards,
Click to expand...
Click to collapse
I will try to fix it asap. The problem is, that I cannot reproduce it.
I assume that the chmod 777 /cache command that I do, before the adb push command fails with "Operation not permitted."
But this I still don't know how to fix. If someone knows, tell me!
error in v.0.2.3
Dear entonjackson,
thanks for your work and for the time you spend on it.
Unfortunately, I too have problems with the tool for Windows since version 0.2.0 and also with the latest version (0.2.3).
The error messages that I receive are identical (with the same line numbers) to those receiving cakadut in his last post.
I am trying to root Iconia for the first time.
I tried with Windows 7-32bit and Windows 7 64-bit.
My configuration:
Iconia B1-A71 8GB ROM, 512Mb ram
Android 4.1.2
kernel 3.4.0
Image version: Acer_AV051_B1-A71_RV04RC04_WW_GEN1
Build Number: Acer_AV051_B1-A71_1.174.00_WW_GE
I hope you can find the solution.
Thank you for sharing your work with us.
Just uploaded a new version. Could you please try again?
It's hard to fix for me, because I don't have the problem, so all I can do is try. Thanks for the patience!
****, I think i found the bug. Don't try 0.2.4 it won't work also.
foxterrier said:
Dear entonjackson,
thanks for your work and for the time you spend on it.
Unfortunately, I too have problems with the tool for Windows since version 0.2.0 and also with the latest version (0.2.3).
The error messages that I receive are identical (with the same line numbers) to those receiving cakadut in his last post.
I am trying to root Iconia for the first time.
I tried with Windows 7-32bit and Windows 7 64-bit.
My configuration:
Iconia B1-A71 8GB ROM, 512Mb ram
Android 4.1.2
kernel 3.4.0
Image version: Acer_AV051_B1-A71_RV04RC04_WW_GEN1
Build Number: Acer_AV051_B1-A71_1.174.00_WW_GE
I hope you can find the solution.
Thank you for sharing your work with us.
Click to expand...
Click to collapse
Ok, people. With pawitp's help I hopefully fixed the permissions bug.
The problem was, that i was trying to chmod the /cache directory directly from adb shell, which isn't possible. I forgot, that this needs to be done from telnet. So in 0.2.6 I'm setting permission with telnet. This should fix it!
Please report!
Good luck :fingers-crossed:
Dear ethon
hi ethon can u do tutorial video cause i can't found the directory for the "step 6 : go to go to connectivity -> CDS Inforamtion ->Network Utility " and Thnk You :good:
diskenz said:
hi ethon can u do tutorial video cause i can't found the directory for the "step 6 : go to go to connectivity -> CDS Inforamtion ->Network Utility " and Thnk You :good:
Click to expand...
Click to collapse
I will try to do a video tutorial, but it's very easy to do.
Download and install Ex Dialer & Contacts.
Launch the app.
Dial *#*#ENGMODE#*#*.
Swipe from right to left (to Connectivity). Then choose CDS Information and Network Utility.
There you paste this command: /data/local/tmp/busybox telnetd -l /system/bin/sh -p 1234
stell no thing happen maybe i must upgrade to pro version ???
diskenz said:
stell no thing happen maybe i must upgrade to pro version ???
Click to expand...
Click to collapse
No.
Try to dial *#*#3646633#*#*
Else I don't know... this should work in any case...
entonjackson said:
Ok, people. With pawitp's help I hopefully fixed the permissions bug.
The problem was, that i was trying to chmod the /cache directory directly from adb shell, which isn't possible. I forgot, that this needs to be done from telnet. So in 0.2.6 I'm setting permission with telnet. This should fix it!
Please report!
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks entonjackson,
unfortunately with version 0.2.6 I can not get the ADB connection with the tablet. The message it gives me is:
"Trying to Establish ADB Connection (If this hangs, ADB Connection failed. CMD Shell Close and open a new one) ..."
and remains so without making the connection.
If I run the command 'adb devices' in another command line session, the device is seen correctly (0123456789ABCDEF device),
but when I run the new version (0.2.6) of the tool, the message is what I wrote above.
Thank you for your patience.

[ROM] Official LineageOS 14.1 for GT-I9305

Official LineageOS 14.1 for Samsung Galaxy S III LTE GT-I9305
1 _
_ download odin for windows
# odin
http://forum.xda-developers.com/showthread.php?t=2711451
2 _
_ flash the latest stock rom with odin (ap button)
# I9305XXUFQG1
http://updato.com/firmware-archive-select-model?record=65E064847BE811E7963AFA163EE8F90B
3 _
_ flash twrp recovery with odin (ap button)
# twrp
https://twrp.me/devices/samsunggalaxys3internationallte.html
4 _
_ flash the os with twrp
# unofficial daily build by @walter79
http://buildyourownandroid.selfhost.eu/smartphone/daily-builds/
# official weekly build
https://download.lineageos.org/i9305
5 _
_ you can also flash gapps
# OpenGApps
http://opengapps.org/
Thanks a lot to @BlueFlame4 and @walter79 for offering their build server !
XDA:DevDB Information
[ROM] Official LineageOS 14.1 for GT-I9305, ROM for the Samsung Galaxy S III I9300
Contributors
rgib
Source Code: https://github.com/LineageOS/android_kernel_samsung_smdk4412
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Created 2017-01-20
Last Updated 2017-11-11
Great let me be the first one to thank you.
Keep Up the good work
Hi rgib, in this list of ROMs wich one is the nougat latest version for the i9305? I'm sorry I don't know the denomination.
Thanks
mop09737 said:
Hi rgib, in this list of ROMs wich one is the nougat latest version for the i9305? I'm sorry I don't know the denomination.
Thanks
Click to expand...
Click to collapse
Hi @mop09737,
the denomination is still i9305 but the build wasn't available until recently
https://visi0nary.de/builds/full/lineage-14.1-20170121-UNOFFICIAL-i9305.zip
@rgib, to build it myself, do I just have to:
repo init -b cm-14.1
repo sync --force-sync
brunch i9305
Or is there something else I have to do (maybe install some new dependencies?). I just had an error (I'm currently looking where from).
EDIT:
Found the error, attached a screenshot. Has to do with Wifi I guess.
i9305 blobs missing. check github/themuppets
JUX84 said:
Hi @mop09737,
the denomination is still i9305 but the build wasn't available until recently
https://visi0nary.de/builds/full/lineage-14.1-20170121-UNOFFICIAL-i9305.zip
@rgib, to build it myself, do I just have to:
repo init -b cm-14.1
repo sync --force-sync
brunch i9305
Or is there something else I have to do (maybe install some new dependencies?). I just had an error (I'm currently looking where from).
EDIT:
Found the error, attached a screenshot. Has to do with Wifi I guess.
Click to expand...
Click to collapse
Thanks
walter79 said:
i9305 blobs missing. check github/themuppets
Click to expand...
Click to collapse
Isn't it enough to have it in my local roomservice ?
EDIT: Just checked with 'git status' and I'm at the last commit.
Is there a way to clean up the builds files since I switched from cm-13.0 to cm-14.1, maybe there's some sort of cache or something
Hello
I try to install rom but i have a problem
In recovery during the flash of rom I have two red errors:
"Patching system image unconditionnaly:
E:unknown command [log]
E:unknown command [log]"
If i reboot after flash, phone bootloop
Did i make something wrong?
buscagoule said:
Hello
I try to install rom but i have a problem
In recovery during the flash of rom I have two red errors:
"Patching system image unconditionnaly:
E:unknown command [log]
E:unknown command [log]"
If i reboot after flash, phone bootloop
Did i make something wrong?
Click to expand...
Click to collapse
no, let's flash tomorrow's build.
JUX84 said:
Isn't it enough to have it in my local roomservice ?
EDIT: Just checked with 'git status' and I'm at the last commit.
Is there a way to clean up the builds files since I switched from cm-13.0 to cm-14.1, maybe there's some sort of cache or something
Click to expand...
Click to collapse
I completely deleted the folder contents and did a new repo init + repo sync, and apparently it just werks.
I guess some extra steps are needed when one wants to switch branches.
Is your personal build booting?
rodman01 said:
Is your personal build booting?
Click to expand...
Click to collapse
yes. let's download lineage-14.1-20170122-UNOFFICIAL-i9305.zip
thanks and ok, will try this...I finished also a build yesterday (all sources from leos 14.1), but it doesn't boot.
Stucks on leos bootanimation. Was/is there a fix on github today? Haven't seen seen changes related to smdk or i9305. Additional I got build errors with smdk-gps. I solved it with copying some files or lines from another working rom.
the new version 20170122 is still cant boot, pls help
Looks like exactly the problem I mentioned in the official cm-13.0 thread.
For me previous build booted fine, but i've must wait more time for it than usual. Didn't test latest build.
I had also bootloops with yesterdays build: 20170122. But after flashing the UPDATE-SuperSU-v2.71.zip, it boots now. So it seems, bootloop is happening because of the, from lineaos, currently removed root....
Hi, i a great pleasure to see lineage OS experiment on this device.
Do you think it will be possible that an official build coming soon?
And why this phone (better than I9300) was not fully support by cyanogen team?
Best
Optrolight
I flash 20170124 build:
Boot after flash is very, very long
I can't set up my gmail accompt only with "tap and go" method and i must connect a second phone to access the email set up
No connection data
wifi is ok
Call ok but I listen nothing and nobody hears me
No acces to my sd card with file manager
buscagoule said:
I flash 20170124 build:
Boot after flash is very, very long
I can't set up my gmail accompt only with "tap and go" method and i must connect a second phone to access the email set up
No connection data
wifi is ok
Call ok but I listen nothing and nobody hears me
No acces to my sd card with file manager
Click to expand...
Click to collapse
So why there are lot of differences between I9300 and I9305?
It's a very good question for me!!

[DEV][TOOL][Linux]Android System Extraction and Repack Tool

Introduction
You probably know already that starting from Android 5.x (Lollipop) compiled roms (aosp,cm,stock) are not compressed anymore the way they used to be on previous android versions. On previous versions all content inside /system folder that has to be extracted within our device was either uncompressed (simple /system folder inside our flashable zip) or compressed in a system.img file, which it is a ext4 compressed file; both of these, anyway, were readable and we could see all system files (app,framework, etc).
The problem comes in >=5.0 versions, this method is not used anymore. Why? Because roms started to be always larger, so it is necessary to compress them even more.
Note : Introduction was taken from here : https://forum.xda-developers.com/an.../how-to-conver-lollipop-dat-files-to-t2978952 by @xpirt so thanks to him
So in order to save myself and others who most port Custom & Stock Roms, i decided to use some part of my time to write this script for easy work done.
What this script does :
It basically Unpack and Repack system.new.dat alongside with file_context.bin convertion which is seen in android 7.0/7.1
ITS USAGE:
NOTE
First Clone the repo.
Make sure that Android_System_Extraction_and_Repack_Tool is located at Desktop
Run "Xtrakt" from it's location in terminal
Copy "file_contexts.bin" from your Rom to "file_context_zone" folder
Use "f" from menu to convert "file_contexts.bin" to text readable "file_contexts"
Copy : system.new.dat, system.transfer.list & file_contexts to "convert-dat" folder.
Use "i" from menu to unpack, which the output will be name as "rom_system" for modifications of apks & files.
Use "y" from menu to repack, which the complete new "system.new.dat", "system.patch.dat" & "system.transfer.list" will be located at "Finish-new.dat" folder
Done !
EXAMPLE:
Again , Make sure that Android_System_Extraction_and_Repack_Tool is located at Desktop
In your terminal, type the following to start the script:
Code:
git clone https://github.com/iykequame/Android_System_Extraction_and_Repack_Tool.git
mv android_system_extraction_and_repack_tool ~/Desktop/
cd ~/Desktop/android_system_extraction_and_repack_tool/
./Xtrakt
OR
Code:
Double-click the Xtrakt file and choose "Run in Terminal" if your OS supports it.
##ALERT!!!##
sudo is requested in the script.
How To Get It {Tool]
Clone from one of the below ;
From GITHUB :
Code:
git clone https://github.com/iykequame/Android_System_Extractrion_and_Repack_Tool.git
From BITBUCKET :
Code:
git clone https://[email protected]/zac6ix/android_system_extraction_and_repack_tool.git
Or
Download zip
AFH
GIT-RELEASE
Sources :
Android_System_Extraction_and_Repack_Tool
GITHUB
BITBUCKET
Threads :
sdat2img 1.0 - img2sdat 1.2
For file_context.bin conversion by: Pom Kritsada @ MTK THAI Developers.
Credit to :
@xpirt
@SuperR.
-all xda threads which helped
-Android Matrix Development - here
-Nana Yaa for her time.
hi, your tool sounds good but it seems it doesnt work.
i press f and nothing happen ..
Use "f" from menu to convert **"file_contexts.bin"** to text readable **"file_contexts"**
Blackball said:
hi, your tool sounds good but it seems it doesnt work.
i press f and nothing happen ..
Use "f" from menu to convert **"file_contexts.bin"** to text readable **"file_contexts"**
Click to expand...
Click to collapse
Sorry for the Late reply !
Directories linking has been fix .
You can go ahead and try again
Thanks for sharing!
Don't work
When i press i ..Don't work.say file missing.but i already put all file..Please help meView attachment 4249470
Doesn't do anything with file_context.bin, doesn't even check if file is there.
oreo supported???
I am getting this error on repacking:-
Code:
WARNING! WARNING!! WARNING!!!
Please Check & Trace Where Errors.
There Is NO rom_system found
file_contexts -->> Missing !
Android SDK -->> not detected !
Please help.
Black_J said:
I am getting this error on repacking:-
Code:
WARNING! WARNING!! WARNING!!!
Please Check & Trace Where Errors.
There Is NO rom_system found
file_contexts -->> Missing !
Android SDK -->> not detected !
Please help.
Click to expand...
Click to collapse
I see that this thread is not supported.
Anyways, I observed that the tool works for file_contexts.bin but not for other options.
So , I followed the other link in the thread for individual commands and was successful.
Works perfectly on Android Pie! Have to do some tweaks, PM me if anyone wants to make this work for Android Pie.

Problem with building a Lineage OS Image (brunch zerofltexx)

Device: SM-G920
Lineage OS installable zip: lineage-17.1-20200606-UNOFFICIAL-zerofltexx (found on https://www.los-legacy.de/17.1/zerofltexx)
I follow the step by step guide on this website: https://wiki.lineageos.org/devices/zerofltexx
I extracted proprietary blobs from block-based OTAs from the zip obtained from the link: https://www.los-legacy.de/17.1/zerofltexx
The OTA doesn't include vendor.transfer.list and vendor.new.dat.br or vendor.new.dat.
During the building step I get this error:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'vendor/samsung/zero-common/proprietary/lib/libcamera_metadata.so', needed by '/home/louloulou/android/lineage/out/target/product/zerofltexx/system/lib/libcamera_metadata.so', missing and no known rule to make it
make: *** [build/core/ninja.mk:152 : ninja_wrapper] Erreur 1
make : on quitte le répertoire « /home/louloulou/android/lineage »
Do you have an idea of how to arrange this please?
Thanks a lot!
Cheers!
looks like it is missing some vendor LIB files, try to pull them from stock or AndroidDumps repository, then paste them in the libs folder
Tsumetaay said:
looks like it is missing some vendor LIB files, try to pull them from stock or AndroidDumps repository, then paste them in the libs folder
Click to expand...
Click to collapse
Thanks for the answer Tsumetaay!
Do you know a website where I can get them from?
(They weren't included in the installable zip)
louloui said:
Thanks for the answer Tsumetaay!
Do you know a website where I can get them from?
(They weren't included in the installable zip)
Click to expand...
Click to collapse
you can get it from AndroidDumps repo
some of them are in System/Vendor/Lib, Vendor/Lib or System/Lib, i made things easy to you, so here is the libs you need: https://dumps.tadiphone.dev/dumps/s...-NRD90M-G920FXXS6ETI6-release-keys/system/lib
also if you want to search for another phone just go to the root dir and search for the specific device.
louloui said:
Device: SM-G920
Lineage OS installable zip: lineage-17.1-20200606-UNOFFICIAL-zerofltexx (found on https://www.los-legacy.de/17.1/zerofltexx)
I follow the step by step guide on this website: https://wiki.lineageos.org/devices/zerofltexx
I extracted proprietary blobs from block-based OTAs from the zip obtained from the link: https://www.los-legacy.de/17.1/zerofltexx
The OTA doesn't include vendor.transfer.list and vendor.new.dat.br or vendor.new.dat.
During the building step I get this error:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'vendor/samsung/zero-common/proprietary/lib/libcamera_metadata.so', needed by '/home/louloulou/android/lineage/out/target/product/zerofltexx/system/lib/libcamera_metadata.so', missing and no known rule to make it
make: *** [build/core/ninja.mk:152 : ninja_wrapper] Erreur 1
make : on quitte le répertoire « /home/louloulou/android/lineage »
Do you have an idea of how to arrange this please?
Thanks a lot!
Cheers!
Click to expand...
Click to collapse
use the trees from here or here . That guide is out dated. Just clone the local manifest, to .repo/local_manifests and repo sync and you will have all the vendor files, device trees, and kernel.

Categories

Resources