Hello all,
I extracted the new firmware from stock Asus UL-ASUS_T00N-WW-12.2.2.37 Rom. This Zip can be flashed with TWRP coming from Stock WW 12.2.2.27.
Keep in mind this is not a fota (update) for your Android System to version 12.2.2.37. This Zip includes only the firmware for Padfone S WW.
http://www21.zippyshare.com/v/Cin9SgXj/file.html
Sent from my ASUS_T00N using XDA Free mobile app
Sirius-3R said:
Hello all,
I extracted the new firmware from stock Asus UL-ASUS_T00N-WW-12.2.2.37 Rom. This Zip can be flashed with TWRP coming from Stock WW 12.2.2.27.
Keep in mind this is not a fota (update) for your Android System to version 12.2.2.37. This Zip includes only the firmware for Padfone S WW.
http://www21.zippyshare.com/v/Cin9SgXj/file.html
Sent from my ASUS_T00N using XDA Free mobile app
Click to expand...
Click to collapse
Can you help me to extracted the new firmwate from TW_12.2.2.37......
michliu said:
Can you help me to extracted the new firmwate from TW_12.2.2.37......
Click to expand...
Click to collapse
Yes I can but I need a bit more spare time to write an easy tutorial until Friday this week.
Sent from my ASUS_T00N using XDA Free mobile app
Sirius-3R said:
Yes I can but I need a bit more spare time to write an easy tutorial until Friday this week.
Sent from my ASUS_T00N using XDA Free mobile app
Click to expand...
Click to collapse
Thanks..... waiting your tutorial...
TUTORIAL How to extract firmware from stock rom
Prerequisites:
7-Zip
Text Editor
Read this tutorial completely bevor you begin
Content:
1. Download your rom
2. Make a copy
3. Modifiy its content
4. Repack your rom
5. Profit
1. Download your Rom
Download your Stock Rom from Vendor, for example mine is
UL-ASUS_T00N-WW-12.2.2.37-user.zip
2. Make a copy
Make a copy of your downloaded rom, if something goes wrong and you have to start over again
3. Modifiy its content
OPEN with 7-zip (DO NOT UNZIP it)
UL-ASUS_T00N-WW-12.2.2.37-user.zip
DELETE
system.transfer.list
system.new.dat
system.patch.dat
DOUBLE CLICK on folder
META-INF
com
google
android
and UNZIP the file
updater-script
or drag and drop the file on your desktop
OPEN
updater-script
with a Text Editor, it's content will look like this
Code:
getprop("ro.product.device") == "ASUS_T00N" || abort("This package is for \"ASUS_T00N\" devices; this is a \"" + getprop("ro.product.device") + "\".");
show_progress(0.750000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
ui_print("installing rpm");
package_extract_s_file("firmware-update/rpm.mbn", "/dev/block/platform/msm_sdcc.1/by-name/rpm");
ui_print("installing sbl1");
package_extract_s_file("firmware-update/sbl1.mbn", "/dev/block/platform/msm_sdcc.1/by-name/sbl1");
ui_print("installing aboot");
package_extract_s_file("firmware-update/emmc_appsboot.mbn", "/dev/block/platform/msm_sdcc.1/by-name/aboot");
ui_print("installing tz");
package_extract_s_file("firmware-update/tz.mbn", "/dev/block/platform/msm_sdcc.1/by-name/tz");
), "");
ifelse(msm.boot_update("backup"), (
ui_print("installing rpmbak");
package_extract_s_file("firmware-update/rpm.mbn", "/dev/block/platform/msm_sdcc.1/by-name/rpmbak");
ui_print("installing sbl1bak");
package_extract_s_file("firmware-update/sbl1.mbn", "/dev/block/platform/msm_sdcc.1/by-name/sbl1bak");
ui_print("installing abootbak");
package_extract_s_file("firmware-update/emmc_appsboot.mbn", "/dev/block/platform/msm_sdcc.1/by-name/abootbak");
ui_print("installing tzbak");
package_extract_s_file("firmware-update/tz.mbn", "/dev/block/platform/msm_sdcc.1/by-name/tzbak");
),"no backup partition");
msm.boot_update("finalize");
ui_print("installing DDR");
package_extract_file("firmware-update/DDR.img", "/dev/block/platform/msm_sdcc.1/by-name/DDR");
ui_print("installing modem");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem");
ui_print("installing asusfw");
package_extract_file("firmware-update/asusfw.img", "/dev/block/platform/msm_sdcc.1/by-name/asusfw");
REMOVE the two lines
Code:
getprop("ro.product.device") == "ASUS_T00N" || abort("This package is for \"ASUS_T00N\" devices; this is a \"" + getprop("ro.product.device") + "\".");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
and save your file
4. Repack your rom
Drag and drop your modified
updater-script
in your already opened 7-zip rom archive and overwrite the included one with your version
5. Profit
Close 7-zip and copy your firmware only rom to your Android device.
Use CWM or TWRP to make a backup of your boot partition (Kernel)
Now install your zip and reboot your phone
May I flash (system) to my padfoneS by TWRP ?
system.transfer.list
system.new.dat
system.patch.dat
Yes, flash success by TWRP ! upgrade to 12.2.2.37 !
Related
Hey - I'm looking for a stock, unrooted image of the original BN software. I'd like to restore the image via CWM as mine is screwed up with GApps - a factory reset does not get rid of it.
Thanks!
Just for the gapps there is no need to flash images. btw you don't mention for what model if 8GB or 16GB.
Here's a trick that might work... the gapps zip (most of well done zips) contains a script named updater-script within META-INF >> com >> google >> android >> updater-script which contains the following code:
* Uncompress the gapps zip e.g: gapps-gb-20110828-signed.zip in another folder to get access to updater-script file
ui_print("GApps 20110828");
ui_print(" For Android 2.3.5");
ui_print("Mounting system...");
run_program("/sbin/busybox", "mount", "/system");
show_progress(1, 15);
ui_print("Deleting old APKs...");
delete("/system/app/Books.apk",
"/system/app/BooksPhone.apk",
"/system/app/CarHomeLauncher.apk",
"/system/app/CarHomeGoogle.apk",
"/system/app/FOTAKill.apk",
"/system/app/GenieWidget.apk",
"/system/app/Gmail.apk",
"/system/app/GoogleBackupTransport.apk",
"/system/app/GoogleCalendarSyncAdapter.apk",
"/system/app/GoogleContactsSyncAdapter.apk",
"/system/app/GoogleFeedback.apk",
"/system/app/GooglePartnerSetup.apk",
"/system/app/GoogleQuickSearchBox.apk",
"/system/app/GoogleServicesFramework.apk",
"/system/app/googlevoice.apk",
"/system/app/kickback.apk",
"/system/app/LatinImeTutorial.apk",
"/system/app/Maps.apk",
"/system/app/MarketUpdater.apk",
"/system/app/MediaUploader.apk",
"/system/app/NetworkLocation.apk",
"/system/app/OneTimeInitializer.apk",
"/system/app/SetupWizard.apk",
"/system/app/Provision.apk",
"/system/app/QuickSearchBox.apk",
"/system/app/soundback.apk",
"/system/app/Street.apk",
"/system/app/Talk.apk",
"/system/app/Talk2.apk",
"/system/app/talkback.apk",
"/system/app/Vending.apk",
"/system/app/VoiceSearch.apk",
"/system/app/YouTube.apk",
"/system/etc/permissions/com.google.android.maps.xml",
"/system/etc/permissions/features.xml",
"/system/framework/com.google.android.maps.jar",
"/system/lib/libmicrobes_jni.so",
"/system/lib/libtalk_jni.so",
"/system/lib/libvoicesearch.so");
ui_print("Copying new APKs...");
package_extract_dir("system", "/system");
ui_print("Unmounting system...");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Installation complete!");
Click to expand...
Click to collapse
You could modify it with Notepad or Notepad++(Highly recommended) and for example remove the line "/system/app/YouTube.apk", if you have it installed and don't want the script "delete" it because it is under ui_print("Deleting old APKs..."); section so it will delete all the apps stated after that piece of code.
Then you could remove this part:
ui_print("Copying new APKs...");
package_extract_dir("system", "/system");
Click to expand...
Click to collapse
Because you are modifying the code to be your uninstaller so no apk's will be installed. Once done save changes and replace the original file with your modified by drag and dropping it while you have gapps-gb-20110828-signed.zip opened with WinRAR or 7ZIP.
One more and obvious thing is that you must delete the system folder of the gapps-gb-20110828-signed.zip file or leave the system folder empty (probably is better to keep system folder but empty)
~ Veronica
Sent from XDA premium using my Nook Tablet
lavero.burgos said:
Just for the gapps there is no need to flash images. btw you don't mention for what model if 8GB or 16GB.
Here's a trick that might work... the gapps zip (most of well done zips) contains a script named updater-script within ....
I'LL CONTINUE THIS POST SOON
~ Veronica
Sent from XDA premium using my Nook Tablet
Click to expand...
Click to collapse
I think I fixed the issue, but I'd like to see the rest of your post
PS - 16GB
[EDIT] Ok, I totally fixed it thanks to a couple of users! Here's what I did:
I used cobrato's 1.4.1 zip which I flashed via CWM - this got rid of the Google Setup Wizard, but added extras I did not want. Then I used Indirects One Click Unroot, which performed a factory software install. So now I'm back to 1.4.2 and COMPLETELY stock.
Time to back up this image! That being said, I would sure help some folks if we had totally stock, unrooted images that can be installed via CWM.
Finished my post...
~ Veronica
I am not responsible for your actions so do at your own risk
Now for TWRP ( Only for F320*)
If you are on Lollipop 5.0.1 stock you need to use
SRKtool_2.1_droidth to reroot your device and this tool will also flash twrp (please choose options carefully) otherwise you may be ended with bootloop or soft bricked device
https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
(Note : Please Don't use LG root tool otherwise you won't be able to flash Twrp )
and it is easy to use ,just make sure you have LG drivers installed in PC and adb enabled
if you have Stock rom of kitkat then
1 use towel root apk to get root access
2 download SuperSu app from play store
3 and please do not update SU binary (important)
4 install F320L_ AutoRec for F320L (Note: if you are on F320K or F320S you need to download your AutoRec)
5 flash you recovery and reboot into recovery
6 when you get there recovery will hang when u use ( don't panic)
7 just flash latest twrp using this of you model f320*
https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
now you are ready to install custom Rom for F320*
1 Download any Rom you want Of D802 (marshmallow or Nougat)
2 download bootstack-f320*-CAF-signed using this
(Note : Not recommended to flash this if you came from Stock Lollipop and If you do, this will change your bootloader to kitkat )
https://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
3 download Poly (Note: To use your external SD)
https://forum.xda-developers.com/lg-g2/development/f320x-polymorph-t3439668
4 Now download Kernel for F320*(Important)
https://forum.xda-developers.com/lg-g2/development/kernel-lambda-kernel-t3270424
5 download Gapps (use opengapps)
Now prepare Rom to Use
1 Extract D802 Rom to pc using winrar or winarchiver
2 open rom and go to Folder META-INF/com/google/android
3 open file (updater-script) using Notepad++ (Download NP++ from google )
4 Hit Ctrl + F and switch to replace tab
Code:
Find What : d802
Code:
Replace with : f320
5 Click replace all
6 save it
7 Repack rom.zip with winrar
Please backup you Important data First
Now to Install Rom
1 Copy Rom (modiified) and other stuff downloaded earlier
2 boot into recovery (for F320L power off first then hold vol down + power until Lg logo and release it for a second and hold vol up + down until factory restore screen showed then choose yes)
3 perform wipe to these only
-Data only (no need to wipe internal)
-system
-cache
3 Now Install zip with this pattern
-Flash bootstack-f320*-CAF-signed ( you can skip this if you came from stock lollipop)
-install Rom moddified
-install lambda-kernel (Important)
-install poly.zip
-install gapps (use open gapps)
now reboot your device
Dear waseemrazajafri,
Thanks a million for this detailed tutorial. I had my G2 F320s flashed in to CM 13. Thanks bro!
I'm on 5.0.1 Stock Rom on my F320L
It says here it is not recommended for a bootstack to be flashed if on 5.0.1 Lollipop stock ROM but when I checked on other people, they say to flash the Hybrid Bootstack for the F320L instead even if I'm on 5.0.1? Is it correct? Should I still flash the Hybrid Bootstack?
ClarkOwen said:
I'm on 5.0.1 Stock Rom on my F320L
It says here it is not recommended for a bootstack to be flashed if on 5.0.1 Lollipop stock ROM but when I checked on other people, they say to flash the Hybrid Bootstack for the F320L instead even if I'm on 5.0.1? Is it correct? Should I still flash the Hybrid Bootstack?
Click to expand...
Click to collapse
This bootstack is not important if you came from stock lolipop rom
bootstack will only change your bootloader to kitkat version and nothing else
I'm using f320L too
Hi, i followed ur guide and it worked. Thank u for that!!
But know i have this problem. I flashed rr rom, but rom is not rooted. Magisk app shows non rooted. App came pre installed with rom. So then i installed the zip (magisk 14.0???.zip) through recovery and after reboot i get fast boot mode. I dont know what i Did wrong. I had to flash the whole rom + other steps again to boot after i finally got into recovery, because i didnt installed/flashed the uninstaller. Even if Did, how the hell would i be allowed to use uninstaller after stuck in fast boot mode???? I saw the image file magisk creates through filemanager in recovery, but didnt know how to decrypt/restore. Can u pls help me get the rom rooted? Thanks in advance
Verstuurd vanaf mijn ME173X met Tapatalk
blanxlr said:
Hi, i followed ur guide and it worked. Thank u for that!!
But know i have this problem. I flashed rr rom, but rom is not rooted. Magisk app shows non rooted. App came pre installed with rom. So then i installed the zip (magisk 14.0???.zip) through recovery and after reboot i get fast boot mode. I dont know what i Did wrong. I had to flash the whole rom + other steps again to boot after i finally got into recovery, because i didnt installed/flashed the uninstaller. Even if Did, how the hell would i be allowed to use uninstaller after stuck in fast boot mode???? I saw the image file magisk creates through filemanager in recovery, but didnt know how to decrypt/restore. Can u pls help me get the rom rooted? Thanks in advance
Verstuurd vanaf mijn ME173X met Tapatalk
Click to expand...
Click to collapse
for rooting try SuperSU 2.46.zip
and magisk actually patched you boot.img (kernel)
just flash Lambda-Infinito-Beta (kernel) from above Post all will work fine
So, if i did all the previous steps and still no root, i just have to flash the kernel to get root acces or what?
Verstuurd vanaf mijn LG-F320 met Tapatalk
blanxlr said:
So, if i did all the previous steps and still no root, i just have to flash the kernel to get root acces or what?
Verstuurd vanaf mijn LG-F320 met Tapatalk
Click to expand...
Click to collapse
kernel is used to boot up rom but unfortunately G2 has its bootloader locked that's why we used bumpped kernel if you flash magisk or SuperSU new version this will patch your ramdisk in kernel
your kernel will no longer bumpped And you will get security error
TRY SuperSU v2.46 I have already tested
or TRy Magisk-v13.1 I have tested this too and found working to get root
Thanks a million dude ,i successfully installed crDroid Rom with this tutorial :good:
stock lollipop f320s
everytime i flash custom roms, let's say nougat, the boot logo is always looping everytime i charge it when it's powered off. isn't there a charging animation? is it normal for f320? i am on stock lollipop. this is what i've been doing: root+twrp (srktool)>flash blastagator twrp>wipe cache, data, system, dalvik>flash nougat rom>flash gapps>flash lambda kernel. i've tried everything. i've tried flashing with/without the hybrid bootstacks and it's still the same. what am i doing wrong?
it gives error at flashing the rom .i have downloaded d802 rom lineage os 14.1 for my f320l
Also replaced the d802 with f320 in update script but still no luck...i am on lollipop
netcracker said:
it gives error at flashing the rom .i have downloaded d802 rom lineage os 14.1 for my f320l
Also replaced the d802 with f320 in update script but still no luck...i am on lollipop
Click to expand...
Click to collapse
Sorry for late reply .
Are you using np++ for editing the script?
ThatPlaysAlot said:
everytime i flash custom roms, let's say nougat, the boot logo is always looping everytime i charge it when it's powered off. isn't there a charging animation? is it normal for f320? i am on stock lollipop. this is what i've been doing: root+twrp (srktool)>flash blastagator twrp>wipe cache, data, system, dalvik>flash nougat rom>flash gapps>flash lambda kernel. i've tried everything. i've tried flashing with/without the hybrid bootstacks and it's still the same. what am i doing wrong?
Click to expand...
Click to collapse
Follow pattern i mentioned in post
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
[/COLOR]
waseemrazajafri said:
Sorry for late reply .
Are you using np++ for editing the script?
Click to expand...
Click to collapse
Yes sir I'm using Notepad ++
[deleted]
@waseemrazajafri
1. Should I install the kernel and polymorph each time to update my rom via TWRP?
2. Can I use lamda kernel to install the d802 oreo rom on f320l?
Thank you for your hard work
kegang said:
@waseemrazajafri
1. Should I install the kernel and polymorph each time to update my rom via TWRP?
2. Can I use lamda kernel to install the d802 oreo rom on f320l?
Thank you for your hard work
Click to expand...
Click to collapse
1. Should I install the kernel and polymorph each time to update my rom via TWRP?
ans: yes,you have too install kernel and polymorph, kernel to boot rom otherwise rom will not boot up! and polymorph to use exSD card otherwise card will not work
2. Can I use lamda kernel to install the d802 oreo rom on f320l?
ans : No ,only Android 5.1, 6.0, 7.0 and 7.1 are supported by lamda officially see Q&A section but you can try at your own risk
https://forum.xda-developers.com/lg-g2/development/kernel-lambda-kernel-t3270424
netcracker said:
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
[/COLOR]
Yes sir I'm using Notepad ++
Click to expand...
Click to collapse
upload your script and send me
waseemrazajafri said:
kernel is used to boot up rom but unfortunately G2 has its bootloader locked that's why we used bumpped kernel if you flash magisk or SuperSU new version this will patch your ramdisk in kernel
your kernel will no longer bumpped And you will get security error
TRY SuperSU v2.46 I have already tested
or TRy Magisk-v13.1 I have tested this too and found working to get root
Click to expand...
Click to collapse
I've known that in order to install TWRP, the bootloader should be unlocked. I successfully installed TWRP on my f320l.
And then, should I use the bumped kernel to install Lineage OS on my device?
waseemrazajafri said:
upload your script and send me
Click to expand...
Click to collapse
Hello Sir, Sorry for the late reply.
My Device is F320l and downloaded rom is for D802..
I'm attaching the script files of lineageos 15.1 which i have edited with notepad++ but at flashing it says invalid zip format.
I know lamba kernel only support upto nougat but lineageos14.1 is not available anymore to download that's why i am using this .
Click to expand...
Click to collapse
One other thing to mention that there are two updat-script files inside the extracted folder under this structure:
HTML:
"LG G2-F320L\lineage-15.1-20190119\META-INF\com\google\android\updater-script"
HTML:
"LG G2-F320L\lineage-15.1-20190119\lineage-15.1-20190119\META-INF\com\google\android\updater-script"
Please help me to install this rom. I'm waiting for your answere.
Script Files::
1 of 2.
Code:
assert(getprop("ro.product.device") == "f320" || getprop("ro.build.product") == "f320" ||
getprop("ro.product.device") == "g2" || getprop("ro.build.product") == "g2" ||
getprop("ro.product.device") == "galbi" || getprop("ro.build.product") == "galbi" ||
getprop("ro.product.device") == "d800" || getprop("ro.build.product") == "d800" || abort("E3004: This package is for device: f320,g2,galbi,d800; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: lge/g2_open_com/g2:5.0.2/LRX22G/151061918340a:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
2 of 2.
Code:
assert(getprop("ro.product.device") == "f320" || getprop("ro.build.product") == "f320" ||
getprop("ro.product.device") == "g2" || getprop("ro.build.product") == "g2" ||
getprop("ro.product.device") == "galbi" || getprop("ro.build.product") == "galbi" ||
getprop("ro.product.device") == "d800" || getprop("ro.build.product") == "d800" || abort("E3004: This package is for device: f320,g2,galbi,d800; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: lge/g2_open_com/g2:5.0.2/LRX22G/151061918340a:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
Hello community!
I was wondering if anybody can help me integrate GAPPS in a ROM.
Some ROMS have them inbuilt and don't require a seperate GAPPS installation.
So yeah, is it possible and if yes, what is the procedure?
Device is Note 8 (N950F).
ROM I'm working on currently is stock based but debloated.
Thanks in advance!
SaadatM said:
Hello community!
I was wondering if anybody can help me integrate GAPPS in a ROM.
Some ROMS have them inbuilt and don't require a seperate GAPPS installation.
So yeah, is it possible and if yes, what is the procedure?
Device is Note 8 (N950F).
ROM I'm working on currently is stock based but debloated.
Thanks in advance!
Click to expand...
Click to collapse
Hi ....
first flash gapps after flashing your stock debloated rom and after booting find what apps and files are added by using sort options according to time desending in any file manager like mix and include those files in the same folders in your stock rom........Thats it......
Note: You dont have to update your update-script afterwards.....
Hope this helps
Add this code in the end of your updater script and rename your gapps file to gapps and place it inside your meta-inf folder
Code:
ui_print("Installing GAPPS...");
package_extract_dir("META-INF/gapps", "/tmp/install/bin/gapps");
run_program("/sbin/busybox", "unzip", "/tmp/install/bin/gapps/gapps.zip", "META-INF/com/google/android/*", "-d", "/tmp/install/bin/gapps");
run_program("/sbin/busybox", "sh", "/tmp/install/bin/gapps/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/install/bin/gapps/gapps.zip");
Trex2017 said:
Add this code in the end of your updater script and rename your gapps file to gapps and place it inside your meta-inf folder
Code:
ui_print("Installing GAPPS...");
package_extract_dir("META-INF/gapps", "/tmp/install/bin/gapps");
run_program("/sbin/busybox", "unzip", "/tmp/install/bin/gapps/gapps.zip", "META-INF/com/google/android/*", "-d", "/tmp/install/bin/gapps");
run_program("/sbin/busybox", "sh", "/tmp/install/bin/gapps/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/install/bin/gapps/gapps.zip");
Click to expand...
Click to collapse
Thanks, exactly what I was looking for!
Trex2017 said:
Add this code in the end of your updater script and rename your gapps file to gapps and place it inside your meta-inf folder
Code:
ui_print("Installing GAPPS...");
package_extract_dir("META-INF/gapps", "/tmp/install/bin/gapps");
run_program("/sbin/busybox", "unzip", "/tmp/install/bin/gapps/gapps.zip", "META-INF/com/google/android/*", "-d", "/tmp/install/bin/gapps");
run_program("/sbin/busybox", "sh", "/tmp/install/bin/gapps/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/install/bin/gapps/gapps.zip");
Click to expand...
Click to collapse
Hi, I would like to ask putting gapps-config in the same meta-inf folder will work or not??
MrMoon said:
Hi, I would like to ask putting gapps-config in the same meta-inf folder will work or not??
Click to expand...
Click to collapse
yes , but you have to grep and change all paths to the cnfg file i other files
Can you tell me how you add play store in ROM while editing. I want to do this all step in Android Oreo 8.1 Please help me.
Zip file is corrupt error pops up when I try flashing.
Didn't work
Little more help, please.
Trex2017 said:
Add this code in the end of your updater script and rename your gapps file to gapps and place it inside your meta-inf folder
Code:
ui_print("Installing GAPPS...");
package_extract_dir("META-INF/gapps", "/tmp/install/bin/gapps");
run_program("/sbin/busybox", "unzip", "/tmp/install/bin/gapps/gapps.zip", "META-INF/com/google/android/*", "-d", "/tmp/install/bin/gapps");
run_program("/sbin/busybox", "sh", "/tmp/install/bin/gapps/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/install/bin/gapps/gapps.zip");
Click to expand...
Click to collapse
hey there pal, I have unpacked the whole ROM package and then I've replaced all the stock apks with the google ones. But once I repack and I install the zip, Android Setup crashes.
I'm on Android 11. Any help?
I would really appreciate it.
Hi guys
Is it possible to make a fresh 'update-binary' file that is located in 'META-INF/com/google/android' or will an existing file previously downloaded from these forums work?
I am simply making a zip that debloats some app from the Lineage OS ROM and also installs some APK's to the system partition but would like to know if I should be using the latest 'update-binary' as I've already got two on my PC but they differ in size and when opened up with a file archive viewer, one does contain more file/directories than the other.
Many thanks
Will
willowen100 said:
will an existing file previously downloaded from these forums work?
Click to expand...
Click to collapse
Both will work if those are worked in past......
If you see ZipMe update binary it is only 186kb...but works well....
HemanthJabalpuri said:
Both will work if those are worked in past......
If you see ZipMe update binary it is only 186kb...but works well....
Click to expand...
Click to collapse
Will it work on my Samsung S10 5G (Qualcomm) device with following things:
1. Not rooted.
2. Bootloader unlocked.
3. Created following script to flash `system.img` file on `system` partition:
Code:
format("yaffs2", "MTD", "system", "/system");
ui_print("Format Completed");
mount("yaffs2", "MTD", "system", "/system");
package_extract_file("system.img", "/system");
unmount("/system");
??
Vats12 said:
Will it work on my Samsung S10 5G (Qualcomm) device with following things:
1. Not rooted.
2. Bootloader unlocked.
3. Created following script to flash `system.img` file on `system` partition:
Code:
format("yaffs2", "MTD", "system", "/system");
ui_print("Format Completed");
mount("yaffs2", "MTD", "system", "/system");
package_extract_file("system.img", "/system");
unmount("/system");
??
Click to expand...
Click to collapse
Update binary have to be choosed according to your arch arm, x86, mips.
Also system.img is need to be a raw image instead of sparse one.
You need to flash that system.img to partition block location only, not to /system.
HemanthJabalpuri said:
Update binary have to be choosed according to your arch arm, x86, mips.
Also system.img is need to be a raw image instead of sparse one.
You need to flash that system.img to partition block location only, not to /system.
Click to expand...
Click to collapse
I was trying to flash it with the `adb sideload` feature which requires signing a zip. So, I can't run this update-script.
Do this at your own risk.
It's not my fault if you brick your phone.
Don't do this with kernels.
This won't work on G531X phones because they have a different chipset.
Don't go to the thread of the rom you did this to for bug reports.
Some roms you can just flash but others need to be slightly modified.
PRO-TIP: Install PBRP recovery. You can change phone codename there which skips this entire tutorial.
My phone model: gprimeltedx (G530F)
Example ROM: Superior OS by itexpert.120 for fortuna3g (https://forum.xda-developers.com/t/...sis-fortuna3g-fortunave3g-26-12-2019.4025365/)
How to "slightly modify" the rom:
1- First try flashing the ROM. If you get an error about your model then continue
2- Download a text editor for Android or use Notepad++ for PC (Notepad works too but its harder)
3- Extract the ROM zip to a folder
4- Go into the folder you extracted the rom to
5- Go to /META-INF/com/google/android
6- Open updater-script with your text editor
7- At the top or near the top there should a line that goes like this.
Code:
assert(getprop("ro.product.device") == "fortuna3g" || getprop("ro.build.product") == "fortuna3g" ||
getprop("ro.product.device") == "fortuna3gxx" || getprop("ro.build.product") == "fortuna3gxx" || abort("E3004: This package is for device: fortuna3g,fortuna3gxx; this device is " + getprop("ro.product.device") + "."););
8- Delete it and save the file
9- Go back to the folder you extracted the rom to and select all of the files and folders, not the folder itself.
10- Compress the files to a zip and flash it with your recovery
will try. thx
zer0_Clover said:
Do this at your own risk.
It's not my fault if you brick your phone.
Don't do this with kernels.
This won't work on G531X phones because they have a different chipset.
Don't go to the thread of the rom you did this to for bug reports.
Some roms you can just flash but others need to be slightly modified.
PRO-TIP: Install PBRP recovery. You can change phone codename there which skips this entire tutorial.
My phone model: gprimeltedx (G530F)
Example ROM: Superior OS by itexpert.120 for fortuna3g (https://forum.xda-developers.com/t/...sis-fortuna3g-fortunave3g-26-12-2019.4025365/)
How to "slightly modify" the rom:
1- First try flashing the ROM. If you get an error about your model then continue
2- Download a text editor for Android or use Notepad++ for PC (Notepad works too but its harder)
3- Extract the ROM zip to a folder
4- Go into the folder you extracted the rom to
5- Go to /META-INF/com/google/android
6- Open updater-script with your text editor
7- At the top or near the top there should a line that goes like this.
Code:
assert(getprop("ro.product.device") == "fortuna3g" || getprop("ro.build.product") == "fortuna3g" ||
getprop("ro.product.device") == "fortuna3gxx" || getprop("ro.build.product") == "fortuna3gxx" || abort("E3004: This package is for device: fortuna3g,fortuna3gxx; this device is " + getprop("ro.product.device") + "."););
8- Delete it and save the file
9- Go back to the folder you extracted the rom to and select all of the files and folders, not the folder itself.
10- Compress the files to a zip and flash it with your recovery
Click to expand...
Click to collapse
btw can something dont work like camera or some?
wojtaszz said:
btw can something dont work like camera or some?
Click to expand...
Click to collapse
the only problem i had was internet not working on modded stock rom. Aosp roms should work np. I dont use gapps so i dont know if there will be any bugs with gapps
zer0_Clover said:
Do this at your own risk.
It's not my fault if you brick your phone.
Don't do this with kernels.
This won't work on G531X phones because they have a different chipset.
Don't go to the thread of the rom you did this to for bug reports.
Some roms you can just flash but others need to be slightly modified.
PRO-TIP: Install PBRP recovery. You can change phone codename there which skips this entire tutorial.
My phone model: gprimeltedx (G530F)
Example ROM: Superior OS by itexpert.120 for fortuna3g (https://forum.xda-developers.com/t/...sis-fortuna3g-fortunave3g-26-12-2019.4025365/)
How to "slightly modify" the rom:
1- First try flashing the ROM. If you get an error about your model then continue
2- Download a text editor for Android or use Notepad++ for PC (Notepad works too but its harder)
3- Extract the ROM zip to a folder
4- Go into the folder you extracted the rom to
5- Go to /META-INF/com/google/android
6- Open updater-script with your text editor
7- At the top or near the top there should a line that goes like this.
Code:
assert(getprop("ro.product.device") == "fortuna3g" || getprop("ro.build.product") == "fortuna3g" ||
getprop("ro.product.device") == "fortuna3gxx" || getprop("ro.build.product") == "fortuna3gxx" || abort("E3004: This package is for device: fortuna3g,fortuna3gxx; this device is " + getprop("ro.product.device") + "."););
8- Delete it and save the file
9- Go back to the folder you extracted the rom to and select all of the files and folders, not the folder itself.
10- Compress the files to a zip and flash it with your recovery
Click to expand...
Click to collapse
I tried it with maxicm 12.1 on FZ and touch didnt work
katruisya said:
I tried it with maxicm 12.1 on FZ and touch didnt work
Click to expand...
Click to collapse
I did say there could be bugs. Also why do you even need lolipop
zer0_Clover said:
I did say there could be bugs. Also why do you even need lolipop
Click to expand...
Click to collapse
I just wanna test stock cyanogenmod too