TWRP and Custom Rom Detailed Guide For F320* korean G2 - G2 General

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);

Related

[Q] Restoring stock ICS fonts via update.zip in Android System Recovery <3e>

Hi you all!
I'v recenty got chineese tablet (one of those without brand/name) with ICS 4.0.4 on board. I'v found it have root permissions so i'v decided to change fonts. I was aware of knowledge that ICS need to have fonts with precise classifications and permissions - so i put my tablet into bootloop... I'v extracted original-stock ICS fonts from Google Nexus disc image (with sgs2toext4) and trying to make update.zip (with update zip packager - my Android System Recovery <3e> can open and operate on zip) to restore them.
I'v got write this in my updater-script:
Code:
ui_print(" ");
ui_print("Mounting...");
mount("yaffs2", "MTD", "system", "/system" );
ui_print("Extracting fonts");
package_extract_dir("system", "/system");
ui_print("Repairing Permissions");
set_perm_recursive(0, 0, 0755, 0644, "system/fonts");
unmount("/system");
ui_print("Finish !");
I believe it just prints text out becouse i'm still in bootloop state - there is more than 6MB in 31 font files and script prints all messages almost instantly.
I'v try to use syntax:
Code:
ifelse(mount("yaffs2", "MTD", "system", "/system") == "system", ui_print("Successfully Mounted!"), ui_print("Mount Failed!");
but after try to apply patch recovery utility prints error message
Code:
E:Error in /tmp/sideload/package.zip (Status 6)
and abort.
In attachment is my update.zip for <3e> with ICS stock fonts.
Do You know how to change the script so I be able to restore stock fonts? - update.zip is the only option, I don't have ADB.

No incoming calls on recent CM12/other 5.x ROMs

Wondering if anyone else is having problems with incoming calls not arriving on Lollipop nightlies over the last few weeks.
I have been updating official CM12 nightlies every week or two, so sometime around 3/15 I would have installed a nightly and could still receiving calls, just as I had been before. Then I installed the 3/29 nightly (based on files in my Downloads folder) and since then I have not received a single incoming call (evidenced by call logs showing last incoming call on 3/27). I can make outbound calls fine, but incoming calls don't even show up on my phone; it is like the call never happened, but I get the voicemail notification if they choose to leave one. The callers say the call rings 4-6 times then goes to voicemail as if I just didn't answer, and it happens with every caller, not just certain ones.
I tried wiping data with no luck, also tried clean-flashing a few other nightlies from the last two weeks including 4/14 and it still doesn't work. Swapped SIMs with my wife (we both have i605's being used on T-Mobile) and incoming calls to my SIM worked on her phone, calls to her did not ring on my phone so it is something phone-related, not network related. Nightlies from before 3/29 seem to be deleted from the CM Downloads page so I can't go back and test CM12 nightlies that I know worked, but I installed the CM11 M10 (KK) snapshot and can receive calls, so I know it has to do with recent Lollipop builds - the problem is that nobody else has issues (other than a few issues with certain OPO nightlies a while back) so I can't find a fix.
I thought maybe it was just CM12 but other ROMS (PAC-MAN 4/8 and CyanideL 4/14) still have problems, presumably because they pull code from CM. I checked logcats and the phone doesn't give any indication that the call is even coming through the network, but the SIM swap shows that it isn't a network issue.
Is anyone else experiencing any of these problems? I don't want to go back to KK if I can get this working, but it seems to be leaving me no choice.
Yes I have a Verizon Note 2 unlocked using a net 10 At&t service sim card and after cm12 build 3/26
all calls go straight to voice mail with out notification or ringing. Other people are having this same problem on other phones too. I believe its in the telephone stack with the changes that were made. I believe we can revert the changes that were made and or flash the few files affected over the new builds. I cant get the rom to extract fully under windows the exe is giving my a python error and I have not had time to try it on my Linux machine.
Any one interested in helping figure this out, message me. I let you know How you can help and then we can post back in here
opalelement said:
Wondering if anyone else is having problems with incoming calls not arriving on Lollipop nightlies over the last few weeks.
Click to expand...
Click to collapse
I have the same problem on my i605. I've done factory reset, wiped everything, flashed the latest nightly (cm-12.1-20150511-NIGHTLY-flo.zip) and pa_gapps-stock-5.1-20150418-signed.zip to no avail.
Incoming calls still ring several times and then go to voicejail. Another anomaly is that outgoing calls don't want to hang up. Calling my bank's voice menu system or leaving a voice mail requires me to power-off or reboot the phone to terminate the call. Calls will end if the other end hangs up.
I've reverted to cm-12-20150130-NIGHTLY-i605.zip via a ROM copy found on AndroidHost at which does have a working phone section. I can't post a link as yet, but searching for "cm-12-20150130-NIGHTLY-i605.zip" will lead you to it.
Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||
Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.
jobren said:
Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||
Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.
Click to expand...
Click to collapse
Thank you ever so much! It worked to get my i605 back on the air as a CM 12.1 phone. There are some oddities such as the Settings->Security page missing Screen lock and the Owner info bits. Hopefully the developers will find and fix the phone issues in the i605 nightlies. For now my plan is to try the latest nightly every two weeks and revert back if there's no joy.
wiitwd said:
Thank you ever so much! It worked to get my i605 back on the air as a CM 12.1 phone. There are some oddities such as the Settings->Security page missing Screen lock and the Owner info bits. Hopefully the developers will find and fix the phone issues in the i605 nightlies. For now my plan is to try the latest nightly every two weeks and revert back if there's no joy.
Click to expand...
Click to collapse
Any good news? I noticed lots of updates going on in the nughtlies. I myself didn't get much luck with the nightly one week before.
jobren said:
Any good news? I noticed lots of updates going on in the nightlies. I myself didn't get much luck with the nightly one week before.
Click to expand...
Click to collapse
As of last night telephony is still broken in the i605 nightlies. I've gotten used to modifying the t0lte nightly to work on the i605.
I am in the same boat. Any way other than described to get back to calling abilities? Like downgrading to KK maybe? I am in baseband MJ9
harjotsandhu said:
I am in the same boat. Any way other than described to get back to calling abilities? Like downgrading to KK maybe? I am in baseband MJ9
Click to expand...
Click to collapse
wiitwd said:
As of last night telephony is still broken in the i605 nightlies. I've gotten used to modifying the t0lte nightly to work on the i605.
Click to expand...
Click to collapse
I tried the given method with 13 July 2015 nightly and it works. Saved my life. I upgraded my MJ9 baseband to ND7 with no effect. Only the given around is working.
jobren said:
Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||
Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.
Click to expand...
Click to collapse
I must be doing something Wrong, I copy the lines above and paste them into the appropriate file updater-script. just add the line in with the other very similar ones. Save the file and rezip it and flash using latest TWRP but It always fails. I tried blisspop and Cyanide L. from note 2 ATT forum. Does this only work with CM nightly s? any information would be appreciated
RJ
wiitwd said:
As of last night telephony is still broken in the i605 nightlies. I've gotten used to modifying the t0lte nightly to work on the i605.
Click to expand...
Click to collapse
I have some new information. When using the i605 nightlies, telephony fails to hang up calls or to receive incoming calls while in a GSM service area, e.g., Guam. Now that I'm back stateside in CDMA/LTE land, the i605 nightlies work great. I offer as a working hypothesis, therefore, that GSM telephony is broken in the i605 nightlies. When I go back in October I'll bring the latest modified t0lte nightly as well as my GTA SIM card.
RJ803 said:
I must be doing something Wrong, I copy the lines above and paste them into the appropriate file updater-script. just add the line in with the other very similar ones. Save the file and rezip it and flash using latest TWRP but It always fails. I tried blisspop and Cyanide L. from note 2 ATT forum. Does this only work with CM nightly s? any information would be appreciated
RJ
Click to expand...
Click to collapse
I have not tried with other ROMs. It definitly works.
Might worth it to have a look at the file in I605 and check the difference.
Sorry I couldnt upload my file. It seems that I do not have the rights to upload files yet. :silly:
jobren said:
Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||
Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.
Click to expand...
Click to collapse
I've tried this a couple of times and the flash always fails quickly at "updating partition details." I've downloaded the cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte.zip, found the updater-script (in \cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte\META-INF\com\google\android) edited the file by adding in the getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || (added it right after the getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" || entry. Saved the file and zipped the folder. Transfered back to the phone and tried to flash from recovery (TWRP v2.8.1.0), which is where things failed.
I'm pretty much a complete noob at this. I've only flashed my phone one time previously, and that was after a lot of false starts. So it is very likely I'm making a very basic error, but I'd appreciate any guidance given.
dmcgregor said:
I've tried this a couple of times and the flash always fails quickly at "updating partition details." I've downloaded the cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte.zip, found the updater-script (in \cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte\META-INF\com\google\android) edited the file by adding in the getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || (added it right after the getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" || entry. Saved the file and zipped the folder. Transfered back to the phone and tried to flash from recovery (TWRP v2.8.1.0), which is where things failed.
I'm pretty much a complete noob at this. I've only flashed my phone one time previously, and that was after a lot of false starts. So it is very likely I'm making a very basic error, but I'd appreciate any guidance given.
Click to expand...
Click to collapse
Any chance that someone who has successfully done this could upload their updater-script file? I've tried a few different variations without any luck getting it to flash. Right now I'm stuck between going back to a known insecure version of Android, or not being able to receive calls, hoping for a 3rd option.
dmcgregor said:
Any chance that someone who has successfully done this could upload their updater-script file? I've tried a few different variations without any luck getting it to flash. Right now I'm stuck between going back to a known insecure version of Android, or not being able to receive calls, hoping for a 3rd option.
Click to expand...
Click to collapse
OK. Let's try this.
The following is the content of my script file. Copy it into a empty txt file and rename it as 'updater-script'.....Here we go.
assert(getprop("ro.product.device") == "t0lte" || getprop("ro.build.product") == "t0lte" || getprop("ro.product.device") == "t0ltexx" || getprop("ro.build.product") == "t0ltexx" || getprop("ro.product.device") == "GT-N7105" || getprop("ro.build.product") == "GT-N7105" || getprop("ro.product.device") == "t0ltedv" || getprop("ro.build.product") == "t0ltedv" || getprop("ro.product.device") == "GT-N7105T" || getprop("ro.build.product") == "GT-N7105T" || getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" || getprop("ro.product.device") == "SGH-I317" || getprop("ro.build.product") == "SGH-I317" || getprop("ro.product.device") == "t0ltetmo" || getprop("ro.build.product") == "t0ltetmo" || getprop("ro.product.device") == "SGH-T889" || getprop("ro.build.product") == "SGH-T889" || getprop("ro.product.device") == "t0ltecan" || getprop("ro.build.product") == "t0ltecan" || getprop("ro.product.device") == "t0ltevl" || getprop("ro.build.product") == "t0ltevl" || getprop("ro.product.device") == "SGH-I317M" || getprop("ro.build.product") == "SGH-I317M" ||getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || abort("This package is for device: t0lte,t0ltexx,GT-N7105,t0ltedv,GT-N7105T,t0lteatt,SGH-I317,t0ltetmo,SGH-T889,t0ltecan,t0ltevl,SGH-I317M; this device is " + getprop("ro.product.device") + ".");
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/dw_mmc/by-name/SYSTEM", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/USERDATA", "/data", "");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/dw_mmc/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/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/dw_mmc/by-name/BOOT");
show_progress(0.200000, 10);
A belated thanks as I'm just now seeing this. After struggling to get this to work for a few weeks I ended up rolling back to CM 11. But I'll give another try with CM 12.1 today and let you know how it goes. Either way I greatly appreciate you taking the time to post this.
No dice. Copied the text above into notepad. Saved it over the original updater script. Zipped everything back up and tried to flash, but it failed right away on "updating partition details." No clue what I'm doing wrong. Could it be my recovery? I'm using TWRP 2.8.1.0, which seems to work fine for flashing the i605 version.
Emmm…i really don't know now. I have been using this file for several months without any issue. I dont think it is the recovery, either…Could be some details in the formating of the script…or our phones are actually different…
BTW…how many posts it needs to unlock the attachments feature?
With the rom zip on your phone download and use ES file explorer. Locate your zip long press it then click the more button. then click extract and press ok. Navigate to the the META-INF\com\google\android\ folder and then long press on the file updater-script and then click rename and then ad .txt to the end so the file is now called updater-script.txt then click ok.
then click on updater-script.txt and open with es file editor. click the pencil in the top right corner to edit text. Then select the text I have shown here
Code:
assert(getprop("ro.product.device") == "epic4gtouch" ||
getprop("ro.build.product") == "epic4gtouch" ||
getprop("ro.product.device") == "SPH-D710" ||
getprop("ro.build.product") == "SPH-D710" ||
getprop("ro.product.device") == "d710" ||
getprop("ro.build.product") == "d710" ||
getprop("ro.product.device") == "smdk4210" ||
getprop("ro.build.product") == "smdk4210" ||
getprop("ro.product.device") == "SPH-D710VMUB" ||
getprop("ro.build.product") == "SPH-D710VMUB" ||
getprop("ro.product.device") == "SPH-D710BST" ||
getprop("ro.build.product") == "SPH-D710BST" ||
abort("This package is for device: epic4gtouch,SPH-D710,d710,smdk4210,SPH-D710VMUB,SPH-D710BST; this device is " + getprop("ro.product.device") + "."););
you want to sop at the ) + ".");
and right before the ifelse mount statement. delete the code above.
then press your back button once and then click save. Then RENAME updater-script.txt back to updater-script. press your back button a couple of time till you get back to the folder that has all the extracted files and then LONG PRESS and select all the files once they are highlighted then pres the bottom that says more and then click compress. then you can a -modded to the end of the file so you can tell them apart.
after it is done compressing you can delete the other files and keep your new zip.
after you get the hang of this you can do it in under 30 seconds, not including the time to extract and compress the rom.
WARNING THE ASSERT CHECK IS THERE SO YOU CAN NOT ACCIDENTALLY FLASH THIS TO THE WRONG PHONE AND PERMA BRICK YOUR DEVICE.
DELETING THE ASSERT TEXT WILL ALLOW YOU TO FLASH THE NEWLY MODDED ZIP
---------- Post added at 08:40 PM ---------- Previous post was at 08:33 PM ----------
Stay off TWRP and philz cutom recovery I have never had a successfully boot, zips would fail halfway through flashing other phone would boot loop. this is back when i was flasinh I605 custom roms of 4.x.x and even cm 11.
I'm on cm 12.1 t0lte Nightly's now and I am using the actual Version I605 Clockword mode recovery with no problems. https://download.cyanogenmod.org/get/jenkins/139629/cm-12.1-20151217-NIGHTLY-i605-recovery.img
I just installed the latest nightly 12-22-15 and made a couple of calls and it rang every time, I am using VZW, so is this not a problem with this carrier, or will it eventually stop working?

FIRMWARE Padfone S UL-ASUS_T00N-WW-12.2.2.37 TWRP

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 !

[Oneplus 3] Any Guides on creating an Update-Binary File ? (my Rom is stuck flashing)

Hey Guys,
I think I am the 20th guy that asks a Question similiar to this but I found nothing and yes I used Google .
My Goal is to build a Custom Rom for my Oneplus 3 based on OxygenOS sadly I am a total noob so I thought I could steal some parts from FreedomOS (based on Aroma).XD
The Aroma Installer is very annoying for me (imho) so I modified the Script that it should just flash through without opening the Aroma Installer....
Sadly this isn't the Case:
It flashes until it should extract the system.new.dat File and there TWRP loads to infinity :/,
because I found no Solution I removed this Part and flashed it over again...(the next thing that came up was "Starting Aroma Installer" and then it errored.... -> It reads the Update-Binary ?)(the Error was something like failed to start Aroma exiting now...)
I already opened Update-Binary in Notepad++ but there is just a lot of crap that no Human can read......
Is the Update-Binary unique to every Device or is there a Solution that works for everything like the updater-script ?
Can someone help me getting this Rom to work ???
:crying:
Thank in advance for reading my crappy English
Lucas
PS: My Script: https://pastebin.com/y04Zzhzi
My "Rom": https://mega.nz/#!eBgmzKzT!xyLManD0AxPtsuSLUymuiQhqlnyMQLcnhcO8lihi7NU
I fixed it ^^
Luro02 said:
I fixed it ^^
Click to expand...
Click to collapse
Please share your result:
1. Is the `update-binary` dependent on the device?
2. Is there any `update-binary` available to work with adb sideload feature of the device with no custom recovery.
3. Is it will work if device has bootloader unlocked but it is not rooted?
4. Is following script is valid :
Code:
format("yaffs2", "MTD", "system", "/system");
ui_print("Format Completed");
mount("yaffs2", "MTD", "system", "/system");
package_extract_file("system.img", "/system");
unmount("/system");
I will be very thankful to you if you can answer any of the question :angel:.

TWRP 3.3.0+ for SGP621?

Been looking all over the forums and run into some dead ends and old threads, so I though I'd straight up ask instead. Is there a TWRP 3.3.0 (or at least newer than 3.0.2) for the SGP621 (LTE variant) available somewhere? Or do I have to tweak the ROM zips somehow to make them flash using the official TWRP 3.0.2 for SGP611?
Specifically, I'm trying to install the LOS15.1 ROM, coming from Floko ROM. SO I must have had a working TWRP at one point, but I seem to have lost the files and LOS15.1 flashed over the one on the device...
Me too. The whole Internet has nothing available
It works with 3.0.2.0 - 3.3.0.0 does not exist for scorpion windy
Step1: Flash the TWRP in the boot partition, as reported in the quoted message (unlocked bootloader necessary).
Enter Fastbook mode by pressing VOL down and plugging in USB cable to your PC.
Code:
fastboot flash boot twrp-3.0.2-0-scorpion_windy.img
Step 2: Edit LineageOS zip file
Trying to flash the lineage15.1-20190922-unofficial-z3tc.zip indeed outputs ERROR 7 in TWRP, failing the installation. I solved this issue. (Edit the contents of /META-INF/com/google/android/updater-script to the text pasted below this instructions. Try to edit within the zip wothout expanding)
This solves the issue reported in the quoted message, which was solved mentioning the use of TWRP 3.3.0-0 which actually does not exist for this device.
Step 3: Final installation process
Reboot to recovery mode:
Code:
fastboot reboot recovery
Flash the edited .zip file of LineageOS
Flash GApps and SuperSU or Magisk (v18 worked in TWRP, not 22, but you can update later from Magisk Manager)
Step 4: Fix Recovery partition
After OS installation, you will not be able to reach the recovery again, as it was installed in the boot partition. Hence, reboot in fastboot mode, connect to the computer and run:
Code:
fastboot flash recovery twrp-3.0.2-0-scorpion_windy.img
updater-script. Replace existing content with this:
ui_print("Target: Sony/SGP611/SGP611:6.0.1/23.5.A.1.291/3706784398: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);
lunaboy73 said:
It works with 3.0.2.0 - 3.3.0.0 does not exist for scorpion windy
Step1: Flash the TWRP in the boot partition, as reported in the quoted message (unlocked bootloader necessary).
Enter Fastbook mode by pressing VOL down and plugging in USB cable to your PC.
Code:
fastboot flash boot twrp-3.0.2-0-scorpion_windy.img
Step 2: Edit LineageOS zip file
Trying to flash the lineage15.1-20190922-unofficial-z3tc.zip indeed outputs ERROR 7 in TWRP, failing the installation. I solved this issue. (Edit the contents of /META-INF/com/google/android/updater-script to the text pasted below this instructions. Try to edit within the zip wothout expanding)
This solves the issue reported in the quoted message, which was solved mentioning the use of TWRP 3.3.0-0 which actually does not exist for this device.
Step 3: Final installation process
Reboot to recovery mode:
Code:
fastboot reboot recovery
Flash the edited .zip file of LineageOS
Flash GApps and SuperSU or Magisk (v18 worked in TWRP, not 22, but you can update later from Magisk Manager)
Step 4: Fix Recovery partition
After OS installation, you will not be able to reach the recovery again, as it was installed in the boot partition. Hence, reboot in fastboot mode, connect to the computer and run:
Code:
fastboot flash recovery twrp-3.0.2-0-scorpion_windy.img
updater-script. Replace existing content with this:
ui_print("Target: Sony/SGP611/SGP611:6.0.1/23.5.A.1.291/3706784398: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);
Click to expand...
Click to collapse
Hello, sorry that my language is translated by Google. I have successfully installed LineageOS ROM, but I found that there is no Google component. Therefore, I plan to rewrite Google-related components (GApps) through TWRP. The current situation is that I can only open TWRP but cannot enter ROM. At the same time, I don't know why, the TWRP installation directory shows that my storage and SD card storage are 0MB. Therefore, my Z3TC is currently unavailable. Is there any solution? Because I am trying for the first time, it may be a very elementary question.
Regarding other issues, currently my Z3TC cannot enter the green light mode, nor can it be connected to the computer to drag and drop files and only displays an icon. Therefore, I have no way to write to the official ROM.

Categories

Resources