EDIT: This root method has been outdated, see the newer guide instead https://forum.xda-developers.com/android/general/tutorial-root-oppo-f1s-flashtool-6-0-t3651220
Why I made this tutorial:
Recently some members claimed that KingRoot is not working for Oppo F1s(A1601) anymore, I assume it's because Kingroot uses cloud based root method, means Kingroot downloads root package and command from cloud and execute on your phone. Maybe the problem was caused by the change of their server, some configuration has been replaced? At this time, I still have a working root method working now, so I would like to share it with everyone Also, you can follow this guide to get rid of the superuser App from those android root exploit app and use SuperSU.
In short, this tutorial tells:
1.How to Root Oppo F1s(A1601) with KingoRoot.(Though cloud based root App Kingroot is not working at this period but KingoRoot the offline one is still working)
2.Though KingoRoot prevent you to switch to other superuser App, we can still replace it with SuperSU with few steps, no custom recovery needed.
****NOTE****
There're various version of KingoRoot apk over the Internet, use the APK version I provided at attachment can guarantee there're no unexpected errors.
The script to replace kingo root was based on the one here but with a little modification, I've added a infinite loop for the script because KingoRoot cause a force reboot(soft reset) right after you delete root from the app, I assume its because KingoRoot want to prevent you to replace it. A infinite loop can make sure the file copying action has been done before your phone reboot.
Steps to Root F1s and Install SuperSU:
1.Install android terminal from Google Play: https://play.google.com/store/apps/details?id=jackpal.androidterm
2.Download the attachment, extract the zip archive, you get an APK "KingoRoot.apk" and a folder "rmkingo", copy the APK and the folder to your Internal storge(Sdcard)
3.Use any file management App to open KingoRoot.apk and install KingoRoot.apk
4.Open KingoRoot and click "one click root" then wait it to obtain root
5.After root succeeded, Open previous installed "Terminal Emulator for Android" and type
Code:
su
. Now KingoRoot's Superuser should pop up and ask you if you want to grant root access, allow it.
6.Now change terminal directory to the script folder, terminal type
Code:
cd /sdcard/rmkingo
7.Now execute the first script, terminal type
Code:
sh step0.sh
8.If there's no error on the previous action, Now proceed to execute the second script which is an infinite loop, you might see infinite error message after you executed it, terminal type
Code:
sh step1.sh
9.Now make sure the Terminal emulator is still open and the script is still running in background, just open SuperUser(installed by KingoRoot), find and click "Remove root" in the option of the App.
10.Your phone should be forced reboot now, after reboot, install SuperSU from google play: https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=zh_TW
11.Open SuperSU and update su binary file with normal mode and wait, it should finish in 2-3 minutes.
12.Hit thanks(My pleasure)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
above method has been confirmed working with the latest rom from my region,(date 2017/02/12 still working)
Rom: A1601_TW_11_A.17_161003
I am on build a1601ex_11_a27_170111
its currently letest update in india
sagargjasani264 said:
I am on build a1601ex_11_a27_170111
its currently letest update in india
Click to expand...
Click to collapse
Wow, Taiwan haven't receive any update since October........Looks like the rom of our region is terribly outdated,lol
A lot of people complaint on oppo forum of our region why there're no updates........
Is it method work for the rom from india?
evilhawk00 said:
wow, taiwan haven't receive any update since october........looks like the rom of our region is terribly outdated,lol
a lot of people complaint on oppo forum of our region why there're no updates........
Is it method work for the rom from india?
Click to expand...
Click to collapse
kingoroot is on 90% since last 20min
---------- Post added at 12:22 PM ---------- Previous post was at 12:10 PM ----------
sorry bro but kingoroot faild...
Sorry kingoroot failed error code : 0x196514
Lyes2 said:
Sorry kingoroot failed error code : 0x196514
Click to expand...
Click to collapse
Hi, I assume you have to downgrade your rom. Find a older version of your rom, flash it via OPPO stock recovery and this method will work.
In my region, Taiwan's newest rom date is 2016 October, so this method work. OPPO might fixed this CVE exploit in their new rom.
The rom I currently use can be downloaded from OPPO Taiwan website, however I'm not sure if it can work on your device, so you might need to find an older version of your region
You can try to get root with older firmware, flash twrp recovery with root app, such as rashr,then once you have twrp recovery, you can flash the new OTA update package, but be sure to modify the update package so you will not loose root after update. However, I think just stick with older firmware will be easier
Failed
Directory not found bro
evilhawk00 said:
Hi, I assume you have to downgrade your rom. Find a older version of your rom, flash it via OPPO stock recovery and this method will work.
In my region, Taiwan's newest rom date is 2016 October, so this method work. OPPO might fixed this CVE exploit in their new rom.
The rom I currently use can be downloaded from OPPO Taiwan website, however I'm not sure if it can work on your device, so you might need to find an older version of your region
You can try to get root with older firmware, flash twrp recovery with root app, such as rashr,then once you have twrp recovery, you can flash the new OTA update package, but be sure to modify the update package so you will not loose root after update. However, I think just stick with older firmware will be easier
Click to expand...
Click to collapse
what kind of modification do you exactly need to do to the update package to not loose root after update?
ngoralph said:
what kind of modification do you exactly need to do to the update package to not loose root after update?
Click to expand...
Click to collapse
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment OPPO_F1s_twrp3.0_modified_devicemodel.zip
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
Can you send me a stock recovery for Oppo F1s or Color Os 3.0 version
[email protected]
I want ask to my friend to build the custom rom with latest version of TWRP.
Ananaqil12 said:
Can you send me a stock recovery for Oppo F1s or Color Os 3.0 version
[email protected]
I want ask to my friend to build the custom rom with latest version of TWRP.
Click to expand...
Click to collapse
If you want stock recovery image, check my reply here https://forum.xda-developers.com/showpost.php?p=71006625&postcount=26
evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment 4137856
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
View attachment 4137905
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
There are no lines that say apply patch
diosdetiempo said:
[/HIDE]
There are no lines that say apply patch
Click to expand...
Click to collapse
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root
evilhawk00 said:
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root
Click to expand...
Click to collapse
It worked!
Here's a little guide
1) Put your TWRP, SuperSU and Android 6.0 Oppo F1S ROM onto SD card
2) Use Flashify to flash TWRP
3) Reboot into TWRP recovery
4) Flash Android 6.0 F1S ROM
5) Flash SuperSU
6) Reboot phone and you should be good to go
evilhawk00 said:
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root
Click to expand...
Click to collapse
update: the only issue i find is that SIM card isn't recognized
diosdetiempo said:
update: the only issue i find is that SIM card isn't recognized
Click to expand...
Click to collapse
sim card not recognized!? Sorry I can't really understand the reason of that because I don't have this problem.
Just a thought, maybe you lost baseband? Can you see your phone's IMEI number in settings? If you found null IMEI, that means you have lost your baseband, otherwise that's just something else maybe a small unknown issue, may also be the access point and protocol was not included in the 6.0 rom
If you lost your IMEI, I assume you already did the nandroid backup before, in twrp backup of NVRAM is the IMEI part, you should be able to recover your IMEI with that nvram backup
evilhawk00 said:
sim card not recognized!? Sorry I can't really understand the reason of that because I don't have this problem.
Just a thought, maybe you lost baseband? Can you see your phone's IMEI number in settings? If you found null IMEI, that means you have lost your baseband, otherwise that's just something else maybe a small unknown issue, may also be the access point and protocol was not included in the 6.0 rom
If you lost your IMEI, I assume you already did the nandroid backup before, in twrp backup of NVRAM is the IMEI part, you should be able to recover your IMEI with that nvram backup
Click to expand...
Click to collapse
have you tested with 6.0?
evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment 4137856
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
View attachment 4137905
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
ok got it to work for a full firmware package here's what i did
1 . downloaded a27 (still 5.1 since 6.0 is not stable according to some)
2. using the twrp above flashed a27
3. flashed magisk
4. flash the twrp image again to make sure that incase it was overwritten by the update
NOTE: i did get an error like unable to mount dev/block/platform/...... it was fine for me
ngoralph said:
ok got it to work for a full firmware package here's what i did
1 . downloaded a27 (still 5.1 since 6.0 is not stable according to some)
2. using the twrp above flashed a27
3. flashed magisk
4. flash the twrp image again to make sure that incase it was overwritten by the update
NOTE: i did get an error like unable to mount dev/block/platform/...... it was fine for me
Click to expand...
Click to collapse
6.0 would work if the sim card issue could be fixed. i can't work it out :/
diosdetiempo said:
6.0 would work if the sim card issue could be fixed. i can't work it out :/
Click to expand...
Click to collapse
did you try restoring the nvram using twrp as stated before?
and did you wipe your data before flashing?? i think the transition from 5.1 to 6.0 may have broke some things read about it somewhere that wiping was necessary for LP to MM
BeyondRom V5.8
Based on Android 9.0 - G975FXXU3ASK1
Devices Supported: G973F(D), G975F(D)
ROM Features
<*>Aroma choices: full/dirty wipe, debloating, Bixby key remapping, Emoji</*>
<*>Supports G973F(D) and G975F(D)</*>
<*>Base SM-G975F G975FXXU3ASK1 odex/deodex November 2019 patch level</*>
<*>CSC features (camera sound menu, call recording, LTE only mod, camera during call, etc)</*>
<*>Knox removed, 1170 fonts by Winb33, AppLock</*>
<*>Included the security bypass from Ian’s multidisabler</*>
<*>build.prop tweaks: multiuser, Bluetooth Aptx driver, call ring delay, SHealth fix, WiFi and BT passwords remember</*>
<*>Dual SIM + SD Card, allow ss in secure apps, disable sig verification, SecureFolder</*>
<*>Reboot directly into rooted system from power menu, disable high volume warning</*>
<*>Possibility to choose in aroma to remove the boot warning</*>
Added/fixed in v5.8
<*>November ASK1 sw level</*>
Credits
- John Wu for Magisk
- Ianmcd for his multidisabler
- Ianmcd & Geiti for the TWRP
- Winb33for the fonts app
- SuperR for his kitchen
- fOmey for his smali patcher
- Khongloi for Secure Folder fix
- Corsicanu for his help and advices
- Sannoc for his help and support
- All people from Telegram group for testing (especially Nathan, Carlos, Raphael, Jay, Alan
Download Link
Google Drive
Digi Link
Flashable patched TWRP S10 (G973F)
Flashable patched TWRP S10+ (G975F)
Installation procedure for upgrade from BeyondROM v5.4 / v5.5
- Take a full TWRP backup
- Dirty flash or clean flash is ok
Installation procedure for upgrade from BeyondROM less than v5.4
- If you are on stock ROM, follow the attached guide
This ROM version needs minimum ASIG BL and ASIG TWRP/recovery or it won't boot !!!
1. Boot in TWRP and take a full backup before flashing BeyondRom 5.8 ROM zip
2. Copy the ROM zip to your phone (Ext SD preferably)
3. Download Ian’s Multidisabler v1.6 or higher and copy it to your phone
4. Download Ian’s TWRP 3.3.1-11, copy it to your phone and patch it with Magisk Manager or use the patched TWRP from gdrive folder
5. Download the stock FW for your device (S10 or S10+) – Frija is a good tool to use
6. Extract the AP from stock FW, copy it to a temp folder on your internal SD
7. Patch in Magisk Manager the AP
8. Copy the patched AP to your PC and replace the recovery.img inside the AP with the patched TWRP from point 4. Rename the patched TWRP to recovery.img before replacing it into the patched AP
9. Open Odin 3.13.1 or 3.13.3 and fill all slots with: patched AP, BL, CP and HOME_CSC. Uncheck the automatic restart and start flashing.
10. Once flashing completed, long press VOL DOWN + POWER until screen becomes black. IMEDIATELY the screen gets black, press VOL UP + BIXBY + POWER BUTTON to enter to TWRP recovery.
11. Once in TWRP, flash the Multidisabler v1.6 and right after flash BeyondROM v5.8 No need to reboot in between.
12. After flashing the ROM zip, save the aroma log, go back to TWRP root menu and select Reboot --> Recovery
13. Wait for the boot up (5-7 minutes) and setup your ROM to your liking
14. Enjoy the release of BeyondROM
Advises
1. Clean install if you have issues with dirty flash; don't start flashing BR5 without a twrp backup of your existing rom
2. If you have flashing issues: check rom zip MD5 hash
3. If you consider that the moded services are the culprit for your SnapChat ban, use stock services.jar provided in the download folder
4. If you like my work, consider buying me a coffee (PayPal link)
Helpful links
Telegram chat
Happy flashing good people!
Always good to see a new rom for the S10(+)
:good::good:
i dont have LTE, only 4G.
what CSC should I chose when flashing?
mcn1970 said:
i dont have LTE, only 4G.
what CSC should I chose when flashing?
Click to expand...
Click to collapse
They're the same thing. It's just the way your phone is reporting the connection.
Regards,
Nathan
sevsman said:
They're the same thing. It's just the way your phone is reporting the connection.
Regards,
Nathan
Click to expand...
Click to collapse
features of the ROM presents LTE instead of 4G mod.
this is what I mean
mcn1970 said:
features of the ROM presents LTE instead of 4G mod.
this is what I mean
Click to expand...
Click to collapse
You have to choose it in the aroma. You may well have missed the option and a dirty flash will fix it.
Regards,
Nathan
sevsman said:
You have to choose it in the aroma. You may well have missed the option and a dirty flash will fix it.
Regards,
Nathan
Click to expand...
Click to collapse
i don't have this in Aroma
another one
??? Good luck with flashing it guys!
I can confirm it is working well on S10 G973F.
Thanks a lot @Andrei1973 @starbucks2010
Thank you for the update! :good::good::good:
Wow July update. !!!
:fingers-crossed::fingers-crossed::fingers-crossed:
Installed. So far working fine. Thanks OP.
how can I install TWRP for Galaxy S10+
and kernel?
tried this at least half a dozen times and get stuck at the same spot. I can root and get Magisk and be fine. Then I patch the appropriate TWRP file for my kernel (S10+ twrp-beyond2lte-3.3.1-3.1_ianmacd.img) and then I open the .tar file. I exchange out the recovery.img with the newly patched one. Then I repackage as a tar using B1 free archiver (this may be the issue, but it seems fine). It creates a new AP file. I insert that into Odin (the same version that worked previously) along with the corresponding BL, CP, and CSC files (I have tried both CSC and Home CSC). I boot into download, hook up my phone, hit flash and VOILA...NOTHING!!!! It says, "file analysis" and crashes every time. After a while I got sick of trying so I made an attempt to flash the recovery.img file straight through TWRP app by itself. All that did was cause an infinite boot loop. Can anyone please help me? Here are my rom file names.
AP_G975FXXU1ASE7_CL16003457_QB24029035_REV01_user_low_ship_meta_OS9.tar.md5
BL_G975FXXU1ASE7_CL16003457_QB24029035_REV01_user_low_ship.tar.md5
CP_G975FXXU1ASE5_CP12748354_CL16003457_QB23792291_REV01_user_low_ship.tar.md5
CSC_OMC_OXM_G975FOXM1ASE5_CL16003457_QB23792291_REV01_user_low_ship.tar.md5
HOME_CSC_OMC_OXM_G975FOXM1ASE5_CL16003457_QB23792291_REV01_user_low_ship.tar
MM Pre-patched AP + TWRP name is "magisk_patched + TWRP.tar."
The TWRP file I downloaded was: twrp-beyond2lte-3.3.1-3.1_ianmacd.img which I of course renamed to recovery.img.
THEN AFTER I GET THIS WORKING, DO I JUST FLASH STRAIGHT THE ZIP FOR THE CUSTOM ROM INSIDE TWRP AND THAT'S IT?
TIA
I just noticed that every time I create the tar file it eliminates the .MD5 extension. Can I just edit the file name to include the .MD5 or do I have to do something special to actually modify the file? Thank you.
kevinjmoore said:
I just noticed that every time I create the tar file it eliminates the .MD5 extension. Can I just edit the file name to include the .MD5 or do I have to do something special to actually modify the file? Thank you.
Click to expand...
Click to collapse
I think your archive editor isn't up to scratch, install 7zip from here Download
Try using this recovery, its a working pre magisk patched image G973F_magisk_patched3.3.1-3.1.img
Rename it to recovery.img and replace the one inside your magisk patched version of AP_G975FXXU1ASE7_CL16003457_QB24029035_REV01_user_ low_ship_meta_OS9.tar.md5 using 7zip. Then flash with odin.
Hope this helps
kevinjmoore said:
I just noticed that every time I create the tar file it eliminates the .MD5 extension. Can I just edit the file name to include the .MD5 or do I have to do something special to actually modify the file? Thank you.
Click to expand...
Click to collapse
Just delete md5 extension, you don't need that. Odin will flash *.tar file without any problems
Thank you for the reply. There are three things that I'm not sure about. All the versions of 7zip that I have used can't create or edit tar files. The second is my device is 975F not 973. Finally, what are the exact steps to replace the recovery file in 7ZIP? That seems to be where it's having the hangup.
@oggi21 I only added that extension as a last resort. It won't flash the regular tar file once I add the patched AP with TWRP recovery using the B1 archiver. Any help would be appreciated.
Any chance of US CSC's like TMB could be implemented?
kevinjmoore said:
Thank you for the reply. There are three things that I'm not sure about. All the versions of 7zip that I have used can't create or edit tar files. The second is my device is 975F not 973. Finally, what are the exact steps to replace the recovery file in 7ZIP? That seems to be where it's having the hangup.
@oggi21 I only added that extension as a last resort. It won't flash the regular tar file once I add the patched AP with TWRP recovery using the B1 archiver. Any help would be appreciated.
Click to expand...
Click to collapse
The best way is to take any tar file (AP or whatever) and open it in 7zip. Then put yours files in it and delete all others that was inside
Hi all
I'm trying to flash and old kernel (boot.img) and system (super.img) to a S20 z1s exynos - SM-G980F/DS with a SW REV. higher than I would like...
I flashed TWRP sucessfully, this tripped knox, so I don't care at all about unsigned code running.
So I tried to:
1. disable AVB using a prebuilt vbmeta.img from here: https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. unpacking and then re-packing the stock firmware using "superr"s kitchen, but this produced a zip with which twrp was not happy with, even fixing a lot of updater-script errors... then again I think it does not help that my TWRP thinks the device is a z3s (no other twrp build available)...
3. flashing via ODIN obviously failed due to the device vs binary SW REV. difference.
4. flashing boot and super "by hand" in twrp -> error about SW REV. mismatch (DEVICE: X BINARY: X-1)
I have so many Questions to which I am unable to find answers, just suspicions/opinions....
Qs:
1. Can I simply disable all boot verification somehow?
2. how are vbmeta images created? do I need to fakesign my images? (vbmeta.img and vbmeta_samsung.img)
Thanks a lot for some clarifications
Defekkt said:
Hi all
I'm trying to flash and old kernel (boot.img) and system (super.img) to a S20 z1s exynos - SM-G980F/DS with a SW REV. higher than I would like...
I flashed TWRP sucessfully, this tripped knox, so I don't care at all about unsigned code running.
So I tried to:
1. disable AVB using a prebuilt vbmeta.img from here: https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. unpacking and then re-packing the stock firmware using "superr"s kitchen, but this produced a zip with which twrp was not happy with, even fixing a lot of updater-script errors... then again I think it does not help that my TWRP thinks the device is a z3s (no other twrp build available)...
3. flashing via ODIN obviously failed due to the device vs binary SW REV. difference.
4. flashing boot and super "by hand" in twrp -> error about SW REV. mismatch (DEVICE: X BINARY: X-1)
I have so many Questions to which I am unable to find answers, just suspicions/opinions....
Qs:
1. Can I simply disable all boot verification somehow?
2. how are vbmeta images created? do I need to fakesign my images? (vbmeta.img and vbmeta_samsung.img)
Thanks a lot for some clarifications
Click to expand...
Click to collapse
For these and other reasons, I quickly grew frustrated with SuperR's Kitchen and ultimately ended up rolling my own purpose-built solution that peels the layers of the onion of the Samsung package, gets to the point of mountable filesystem images, performs the desired transforms, and then packs everything back up into Odin-flashable .tar.md5 files. It's rough and minimalistic, but it works.
I'm not familiar with the error you mention, but usually those sorts of errors come from flashing a bootloader in Odin that is below the level of the one residing on the device. I haven't done much flashing via TWRP since I'm producing Odin-flashable output and I don't know why you'd have issues on boot.img or super.img. For my own sanity I don't regularly flash bootloader images. boot.img doesn't contain the booatloader though: it's the kernel and initramfs.
vbmeta.img files are generated with avbtool. I created one with a null signature which is identical to the ones floating around on the forum. I also cleaned up my fstab and manifests using the techniques of ianmacd's multidisabler.
sjevtic said:
For these and other reasons, I quickly grew frustrated with SuperR's Kitchen and ultimately ended up rolling my own purpose-built solution that peels the layers of the onion of the Samsung package, gets to the point of mountable filesystem images, performs the desired transforms, and then packs everything back up into Odin-flashable .tar.md5 files. It's rough and minimalistic, but it works.
I'm not familiar with the error you mention, but usually those sorts of errors come from flashing a bootloader in Odin that is below the level of the one residing on the device. I haven't done much flashing via TWRP since I'm producing Odin-flashable output and I don't know why you'd have issues on boot.img or super.img. For my own sanity I don't regularly flash bootloader images. boot.img doesn't contain the booatloader though: it's the kernel and initramfs.
vbmeta.img files are generated with avbtool. I created one with a null signature which is identical to the ones floating around on the forum. I also cleaned up my fstab and manifests using the techniques of ianmacd's multidisabler.
Click to expand...
Click to collapse
Thank you for your reply!
1. any chance you could list the steps you used to re-package a samsung rom?
2. is there a guide on how to create null-sigged vbmetas? can you use avbtool or do I need to manually edit the vbmeta file(s) ?
I did not try to downgrade the bootloader, just boot.img (kernel) and super (system, etc.).
Thanks in advance and best regards!
Sorry for the delay. I am on vacation and have not been regularly checking the forum.
To give you a conceptual overview of the workflow, here is the debug output my script generates for each step when trivially unpacking/repacking a Samsung firmware archive:
Extracting source zip.
Extracting .tar.md5 files.
Unlz4ing, unsparsing, and copying images.
Unpacking super.img.
Unpacking boot.img and up_param.bin.
Mounting filesystem images.
Applying main transforms.
Unmounting and checking filesystem images.
Repacking up_param.bin and boot.img.
Repacking super.img.
Sparsing, lz4ing, and copying images.
Archiving .tar.md5 files.
The real magic, of course, is in the transforms that are performed along the way, of which there are many. Most (notably those that are operations against the filesystem images) are performed during step 7, though some are performed before or after other steps by necessity. At some point I'll probably document this process a bit more and release the scripts since it is nontrivial.
Here is how I created my null vbmeta image:
Code:
avbtool make_vbmeta_image --flags 2 --padding_size 256 --output "${STEP_03_DIR}/BL/vbmeta.img"
I downloaded a samsung galaxy s22 Odin firmware and unpacked the zip and the AP tar file and then I un lz4'd the super.img, unsparsed it and then I ran lpunpack on the unsparsed image to get unreadable images
Have you used one of the following?
Extract system.img,vendor.img and product.img from super.img
After lots of search i found a way to extract those img file from super.img What is need? 1.Computer with linux os. extract zip file from this post and place your super.img in same location where you extract.. then run below cmd... simg2img...
forum.xda-developers.com
super_img_lpmake_lpunpack.zip | by MrWaehere for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
ze7zez said:
Have you used one of the following?
Extract system.img,vendor.img and product.img from super.img
After lots of search i found a way to extract those img file from super.img What is need? 1.Computer with linux os. extract zip file from this post and place your super.img in same location where you extract.. then run below cmd... simg2img...
forum.xda-developers.com
super_img_lpmake_lpunpack.zip | by MrWaehere for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
I have. I can get system.img out but I can't open it. I think it's a f2fs partition but I haven't found any tools that can extract files from it
It seems on newer firmware this method of unpacking and extracting system.img out of super.img no longer works. It seems now that when you extract system.img from super.img.raw it gives you a file that reads just as data and does not have the ext4 filesystem magic header bytes.
Have uploaded two screenshots to show how super.img.raw looks and how system.img looks after extraction from super.img. Any thoughts on this?
This firmware is being pulled from latest tar files for SM-S901U
Update, am working on a way and almost got it now. Will probably create a post on this once done and link from here. If you dont hear back from me, i failed. :'(
UPDATE: had some luck following this guys tutorial although a little different was able to extract files. Still cant mount but much closer. Device is f2fs file system. The reason it's not working is most methods on xda are for ext4
How to Extract F2FS Image from Android Device Flash - Baremetallics
How to Extract F2FS Image from Android Device Flash
baremetallics.com
kalexander7 said:
Update, am working on a way and almost got it now. Will probably create a post on this once done and link from here. If you dont hear back from me, i failed. :'(
UPDATE: had some luck following this guys tutorial although a little different was able to extract files. Still cant mount but much closer. Device is f2fs file system. The reason it's not working is most methods on xda are for ext4
How to Extract F2FS Image from Android Device Flash - Baremetallics
How to Extract F2FS Image from Android Device Flash
baremetallics.com
Click to expand...
Click to collapse
Is this also work for other's like erofs?
Mr Hassan said:
Is this also work for other's like erofs?
Click to expand...
Click to collapse
I doubt it although it may be alike using same linux tools like fsck. Erm I'm still stuck on trying to get this f2fs image too mount. It seems corrupt and although I was able to extract libs and apks they're coming out corrupted. Anyone in the community have any knowledge in this area?
kalexander7 said:
I doubt it although it may be alike using same linux tools like fsck. Erm I'm still stuck on trying to get this f2fs image too mount. It seems corrupt and although I was able to extract libs and apks they're coming out corrupted. Anyone in the community have any knowledge in this area?
Click to expand...
Click to collapse
Bro samsung have many dev's to mount fsf2 and already many dude done
The erofs not possible
Mr Hassan said:
Bro samsung have many dev's to mount fsf2 and already many dude done
The **** is erofs
Click to expand...
Click to collapse
what?