Android 11 Stock Kernel with Magisk.
Based on SEA Firmware Version 59.1.A.0.485.
Download:
MEGA
Thanks! How did you make it? I did this:
* I downloaded XQ-AU52_Customized EU_59.1.A.0.485-R8B with xperifirm
* It was automatically extracted by xperifirm
* I didn't find anything looking like boot.img, but i saw boot_X-FLASH-ALL-E9C8.sin, which i unpacked with unsin
* The resulting .img (about 67.1 MB) i patched with magisk manager, logs looked positive
However, flashing that created a boot loop. I had to restore original firmware from sony's built-in recovery (back to android 10).
I tried extracting the 67.1 MB img with imjtool. Which results in 4 files: devicetree.dtb, kernelimage, kernel and ramdisk. I thought maybe I needed kernel, but that is only 15.4 MB.
cosmo_roel said:
Thanks! How did you make it? I did this:
* I downloaded XQ-AU52_Customized EU_59.1.A.0.485-R8B with xperifirm
* It was automatically extracted by xperifirm
* I didn't find anything looking like boot.img, but i saw boot_X-FLASH-ALL-E9C8.sin, which i unpacked with unsin
* The resulting .img (about 67.1 MB) i patched with magisk manager, logs looked positive
However, flashing that created a boot loop. I had to restore original firmware from sony's built-in recovery (back to android 10).
I tried extracting the 67.1 MB img with imjtool. Which results in 4 files: devicetree.dtb, kernelimage, kernel and ramdisk. I thought maybe I needed kernel, but that is only 15.4 MB.
Click to expand...
Click to collapse
Here:
Bootloop after installing the patched boot image on Android 11 on Sony Xperia 5 II (needed system_ext removed from fstab) · Issue #3752 · topjohnwu/Magisk
ISSUE DESCRIPTION After trying to install Magisk with the patched magisk_boot.img from the latest Canary (and Beta) version of the Manager, the device is unable to boot and goes into the bootloop. ...
github.com
Ah, turns out I'm far from the first one with this issue. Thanks for the link. I also found the general guide here on xda now. Unpacking boot.img and removing the system_ext did the trick.
cosmo_roel said:
Ah, turns out I'm far from the first one with this issue. Thanks for the link. I also found the general guide here on xda now. Unpacking boot.img and removing the system_ext did the trick.
Click to expand...
Click to collapse
Could you describe the complete procedure you did? Does this make possible to have root on stock ROM without unlocking bootloader?
Thanks in advance.
cosmo_roel said:
Ah, turns out I'm far from the first one with this issue. Thanks for the link. I also found the general guide here on xda now. Unpacking boot.img and removing the system_ext did the trick.
Click to expand...
Click to collapse
hi, i actually got the procedure myself. However, when editing the boot img in Android Kitchen, i can´t find the file "fstab.qcom". I have two fstab files, fstab.default and fstab.emmc.
Any suggestion?
Thanks in advance.
Supercharlie25 said:
hi, i actually got the procedure myself. However, when editing the boot img in Android Kitchen, i can´t find the file "fstab.qcom". I have two fstab files, fstab.default and fstab.emmc.
Any suggestion?
Thanks in advance.
Click to expand...
Click to collapse
Hi,
did you find a fix or a solution?
Thanks
EDIT: The fix is to comment the system_ext line inside the two fstab files
Just for reference there are two updates to this issue:
There is this tool by @entr0pia that automatically removes system_ext from the boot image
Magisk finally fixed the issue and it is now available in the latest canary builds!
Refs: Issue on Magisk repo - Commit that fixes the issue
Note: I haven't tested them yet!
Click to expand...
Click to collapse
Related
I have a working Kernel - http://forum.xda-developers.com/attachment.php?attachmentid=1743802&d=1361298599
but I need prepare a new one - compilation it is no problem, but how to prepare img file for taht?.
I heard that this is a Rockchip kernel image file - so I am a looking for information how to build this kind of kernel?
Procesor is RK3066.
mafamafa said:
I have a working Kernel - http://forum.xda-developers.com/attachment.php?attachmentid=1743802&d=1361298599
but I need prepare a new one - compilation it is no problem, but how to prepare img file for taht?.
I heard that this is a Rockchip kernel image file - so I am a looking for information how to build this kind of kernel?
Procesor is RK3066.
Click to expand...
Click to collapse
If that is a zImage, then you need to pack it into boot.img in order to flash.
There are many boot.img tools out there which can help you. But the thing is you will be needing your device's original boot.img (Which can be extracted from your device depending upon the partition) which contains the Ramdisk in order to be successful.
coolsandie said:
If that is a zImage, then you need to pack it into boot.img in order to flash.
There are many boot.img tools out there which can help you. But the thing is you will be needing your device's original boot.img (Which can be extracted from your device depending upon the partition) which contains the Ramdisk in order to be successful.
Click to expand...
Click to collapse
In fact it is a regular (no gziped) image not a zImage. The file after unpacking from RK3066 format starts with bytes d3 f0 21 (to unpack I'm using rkutils ).
But I don't understand why we need to make boot.img with this file and only after that, upload boot.img to the device. Normally it should be possible just to upload kernel.img to the partition where kernel is stored, no?
After kernel from the link above is uploaded to this partition, the device boots up without problem. But when we compile new kernel and upload it (after converting with rk-tools ) it is not even possible to boot the device.
Any idea what's going on? Is compiling a kernel, then converting to rk3066 format is enough ?
flowher said:
In fact it is a regular (no gziped) image not a zImage. The file after unpacking from RK3066 format starts with bytes d3 f0 21 (to unpack I'm using rkutils ).
But I don't understand why we need to make boot.img with this file and only after that, upload boot.img to the device. Normally it should be possible just to upload kernel.img to the partition where kernel is stored, no?
After kernel from the link above is uploaded to this partition, the device boots up without problem. But when we compile new kernel and upload it (after converting with rk-tools ) it is not even possible to boot the device.
Any idea what's going on? Is compiling a kernel, then converting to rk3066 format is enough ?
Click to expand...
Click to collapse
Ok, I just had a look at your link and yes, it contains the kernel.img file. So it should be the kernel image file which needs to be flashed. What you actually needed to do is, unpack that kernel image using the tools of your choice and you'll get the ramdisk, zImage etc when unpacking. If you have compiled kernel from Sources, then you need to replace the zImage with yours (Found in arch/arm/boot) if your compilation was successful without errors and repack it to form the kernel.img.
But that doesn't mean it should boot compulsorily, it may not boot depending upon various weird reasons. You may have to fix it by yourself. Nearest bet is using your device's config file (Found in /proc/config.gz) and use that to compile your kernel. You can find all infos regarding what I've mentioned in this thread:
http://forum.xda-developers.com/showthread.php?t=1748297
I have a system.img file, which I extracted from a 20J KDZ. I would now like to convert it into a flashable zip. I have 2 reasons for this. One, I dont want to have to use LGUP to revert my phone to a 100% stock system. It is much easier to just flash a zip of the system partition. Two, I would like to get into modding and ROM development. I believe that it is best to start from pure stock and make changes from there, instead of basing your work off of something that someone else has already modded.
I found these threads but they're a bit old (Lollipop):
1. http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
2. http://forum.xda-developers.com/tmobile-lg-v10/development/lg-h901-stock-images-device-restore-t3241170
In one of them a member provided img's for recovery, boot, and system. In the other thread flashable zips of these img's were posted. These are for the Tmo v10. So it's not a matter of whether it can be done, but how. What tools are needed?
I downloaded the zip from one of the aforementioned threads, deleted the boot.img, replaced his system.img with mine, edited updater-script, and zipped up the meta-inf and system.img files with 7zip. I also checked to be sure that the block to be flashed was correct, it is the same (even though my img is for MM). I tried flashing with TWRP, I immediately get an error code 6.
What should I do?
Just off the subject slightly...but Eliminater74 already has a flashable zip (thought TWRP) for the 20J release. Its a 2 Part System.
Eliminator74's zip is modified. I want to take a 100% pure stock system.img (extracted from stock firmware) and put it into a zip that can be flashed in TWRP. When I say stock, that's what I mean. No root, no Xposed, no BusyBox, nothing. This has already been done for Lollipop on the v10, but I have MM. I have already explained why I want to do this. I'm currently looking into whether Superr's Kitchen can accomplish this.
He has a Fully Stock 20J release..just gotta read the thread..
AnonVendetta said:
I have a system.img file, which I extracted from a 20J KDZ. I would now like to convert it into a flashable zip. I have 2 reasons for this. One, I dont want to have to use LGUP to revert my phone to a 100% stock system. It is much easier to just flash a zip of the system partition. Two, I would like to get into modding and ROM development. I believe that it is best to start from pure stock and make changes from there, instead of basing your work off of something that someone else has already modded.
I found these threads but they're a bit old (Lollipop):
1. http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
2. http://forum.xda-developers.com/tmobile-lg-v10/development/lg-h901-stock-images-device-restore-t3241170
In one of them a member provided img's for recovery, boot, and system. In the other thread flashable zips of these img's were posted. These are for the Tmo v10. So it's not a matter of whether it can be done, but how. What tools are needed?
I downloaded the zip from one of the aforementioned threads, deleted the boot.img, replaced his system.img with mine, edited updater-script, and zipped up the meta-inf and system.img files with 7zip. I also checked to be sure that the block to be flashed was correct, it is the same (even though my img is for MM). I tried flashing with TWRP, I immediately get an error code 6.
What should I do?
Click to expand...
Click to collapse
What tool did you use to extract the KDZ? I am trying to get a stock boot.img for the H901J build and I cannot seem to find it. I used the WindowsLGFirmwareExtract 1.2.5.0 release and all I see are a ton of .bin files and system.img. Is boot.img inside system.img?
@Sippi4x4man: I also used WindowsLGFirmwareExtract. Inside the KDZ there is a DZ and DLL file. Just extract the DZ, then you see lots of BINs. The system.img is split up (since it's around 4GB alone), but the tool can combine the pieces into one file. I was able to figure out how to manually flash the IMG, by running a dd command with TWRP's terminal emulator.
dd if=/external_sd/system.img of=/dev/block/platform/f9824900.sdhci/by-name/system
It takes a few minutes to finish, followed by a message that says no more space is available (I guess /system got filled up). I think when you dd anything you are copying both free and used space, since an IMG is usually just a (sometimes raw) disk image. TWRP will also initially say that no system is installed, I just ignored it, the device boots fine, everything is pure stock, no issues at all. System is mountable after subsequent boots into recovery. I used Magisk and the phh Superuser Magisk module to gain root without modding system partition, and the Magisk version of Xposed. But I would still like to create a flashable zip to automate this. If I figure it out I don't mind uploading it so the community can benefit.
As for the stock boot.img, I would imagine that the boot.bin inside the DZ is probably what you're after. The file size seems about right. However, I tried renaming boot.bin to boot.img and flashing from TWRP. Device wouldn't boot. So maybe there is some other conversion process that needs to be done. I can't think of any other way to obtain a pure stock boot image, extracting it from stock firmware seems like a sure way. If you ever figure it out then please provide a copy. Make sure it isn't patched by SuperSU, Xposed, Magisk, etc. I could maybe merge it into a stock zip.
AnonVendetta said:
@Sippi4x4man: I also used WindowsLGFirmwareExtract. Inside the KDZ there is a DZ and DLL file. Just extract the DZ, then you see lots of BINs. The system.img is split up (since it's around 4GB alone), but the tool can combine the pieces into one file. I was able to figure out how to manually flash the IMG, by running a dd command with TWRP's terminal emulator.
dd if=/external_sd/system.img of=/dev/block/platform/f9824900.sdhci/by-name/system
It takes a few minutes to finish, followed by a message that says no more space is available (I guess /system got filled up). I think when you dd anything you are copying both free and used space, since an IMG is usually just a (sometimes raw) disk image. TWRP will also initially say that no system is installed, I just ignored it, the device boots fine, everything is pure stock, no issues at all. System is mountable after subsequent boots into recovery. I used Magisk and the phh Superuser Magisk module to gain root without modding system partition, and the Magisk version of Xposed. But I would still like to create a flashable zip to automate this. If I figure it out I don't mind uploading it so the community can benefit.
As for the stock boot.img, I would imagine that the boot.bin inside the DZ is probably what you're after. The file size seems about right. However, I tried renaming boot.bin to boot.img and flashing from TWRP. Device wouldn't boot. So maybe there is some other conversion process that needs to be done. I can't think of any other way to obtain a pure stock boot image, extracting it from stock firmware seems like a sure way. If you ever figure it out then please provide a copy. Make sure it isn't patched by SuperSU, Xposed, Magisk, etc. I could maybe merge it into a stock zip.
Click to expand...
Click to collapse
It's been a while from this post... But I'm looking after the same goal you were and got the same error 6 trying the same things you described in your previous posts. Despite of these long 4 years, let me try: did you finally achieve to make the flashable zip with system.img?
I do not own an LG V10 anymore.....it is the most garbage phone I've ever had.
I now use SuperR's Kitchen to create flashable zip from system.img. Works like a charm every time. Downside is that you need a PC to use it. It works for all phones (but you must also have an unlocked bootloader and custom recovery, or you will not be able to flash the zip). There are both free and donate versions, both will work fine.
AnonVendetta said:
I do not own an LG V10 anymore.....it is the most garbage phone I've ever had.
I now use SuperR's Kitchen to create flashable zip from system.img. Works like a charm every time. Downside is that you need a PC to use it. It works for all phones (but you must also have an unlocked bootloader and custom recovery, or you will not be able to flash the zip). There are both free and donate versions, both will work fine.
Click to expand...
Click to collapse
Thank you for your reply. My device is Lenovo Z6 Pro but I thought this wouldn't make a difference.
Just to be sure, what you get with SuperR's Kitchen is a zip including system.img file and not the /system folder, right? Thank you in advance.
Edit: I had tried with other kitchen softwares with no success but SuperR's Kitchen did the job as you said, like a charm. Tons of thanks.
@descarao81: No, SuperR's Kitchen does not include system.img/boot.img, you must provide them yourself. They are device-specific. And system.img is a very large file, so it cannot reasonably be included in the Kitchen zip.
Yeah, maybe I wasn't clear, I meant if the resultant zip would include those raw image files being the original image files provided by the user. It's clear now. Thank you.
Here is how to do it...
1. Go to:
https://forum.xda-developers.com/tm.../lg-h901-stock-images-device-restore-t3241170
Download from the link he provided.
2. Extract the .zip file that you downloaded.
3. Make a new folder called "rom"
4. Copy the META-INF folder from the folder you extracted and place it into the "rom" folder.
5. Download any other flashable rom for your device. Extract it.
6. Go to {EXTRACTED_FLASHABLE_ROM}\META-INF\com\google\android\update-binary in your flashable extracted rom folder. Copy the "update-binary" . Got to the "rom" folder and go to META-INF\com\google\android. Delete the update-binary there and replace it with the one you have copied.
7. Now copy the boot.img from the other rom that is for your device. And place it into the "rom" folder.
8. Now Finally Compress the all the files.
9. Now you will have a flashable system.img.
10. Go to TWRP and flash the .zip that you have just made!
Upytry2 said:
Here is how to do it...
1. Go to:
https://forum.xda-developers.com/tm.../lg-h901-stock-images-device-restore-t3241170
Download from the link he provided.
2. Extract the .zip file that you downloaded.
3. Make a new folder called "rom"
4. Copy the META-INF folder from the folder you extracted and place it into the "rom" folder.
5. Download any other flashable rom for your device. Extract it.
6. Go to {EXTRACTED_FLASHABLE_ROM}\META-INF\com\google\android\update-binary in your flashable extracted rom folder. Copy the "update-binary" . Got to the "rom" folder and go to META-INF\com\google\android. Delete the update-binary there and replace it with the one you have copied.
7. Now copy the boot.img from the other rom that is for your device. And place it into the "rom" folder.
8. Now Finally Compress the all the files.
9. Now you will have a flashable system.img.
10. Go to TWRP and flash the .zip that you have just made!
Click to expand...
Click to collapse
Trying that exactly when im home! Thank you!
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
It could be missing metadata. Are you starting with this fimware? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
SuperR. said:
It could be missing metadata. Which firmware are you starting with? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
Click to expand...
Click to collapse
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
toknitup420 said:
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
Click to expand...
Click to collapse
You did not misread, i changed it I will check it out when I get a chance. No need to upload your project.
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
SuperR. said:
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
Click to expand...
Click to collapse
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
toknitup420 said:
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
Click to expand...
Click to collapse
I will build a rom and upload for you to try. Are you building with vendor included or without?
SuperR. said:
I will build a rom and upload for you to try. Are you building with vendor included or without?
Click to expand...
Click to collapse
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
toknitup420 said:
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
Click to expand...
Click to collapse
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
OK I'll try it now. Good looks.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
it flashes with no errors but it wont boot past splash screen.
toknitup420 said:
it flashes with no errors but it wont boot past splash screen.
Click to expand...
Click to collapse
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
SuperR. said:
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
Click to expand...
Click to collapse
flash went through without error but still boot looping at splash screen.
toknitup420 said:
flash went through without error but still boot looping at splash screen.
Click to expand...
Click to collapse
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
SuperR. said:
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
Click to expand...
Click to collapse
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
toknitup420 said:
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
Click to expand...
Click to collapse
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
SuperR. said:
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
Click to expand...
Click to collapse
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
toknitup420 said:
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
Click to expand...
Click to collapse
Can you send the original updater script that booted but did not have bluetooth?
SuperR. said:
Can you send the original updater script that booted but did not have bluetooth?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
toknitup420 said:
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
Click to expand...
Click to collapse
Did you convert the new one you just tried after swapping 00_project_files to update-binary? If not, try it please. If so, try without please
I have uploaded the OTApkg from my Verizon 10 downloaded 7/6/17. I have not been able to run it on my 10 because of customization issues.
I have also changed the suffix of the filename to "zip" so it could be uploaded. You may want to rename it before manipulating it. The default name is "OTApkg"
You can download it here and I welcome someone else's better ability to parse the file contents.
MD5 is: e684728237328c1a59c8c53ab2308467
I've now extracted the firmware.zip and created two update.zips, one without boot (but stock recovery) and one without both boot and recovery images. Someone reported to me that flashing the boot.img could be problematic -- I do not know the particulars, just reporting what I heard. I have not flashed these files, so you're on your own. If there are reports of problems, I'll pull the files.
2.41.605.20 firmware update (no boot) md5: 13b3461cbe2e1f9a8098d83115f501c8
2.41 605.20 firmware update (no boot; no recovery) md5: 97c1df3e7cbc9583b9916b4e1768f245
hgoldner said:
I have uploaded the OTApkg from my Verizon 10 downloaded 7/6/17. I have not been able to run it on my 10 because of customization issues.
I have also changed the suffix of the filename to "zip" so it could be uploaded. With past OTA's I've been able to extract the contents, but not so with this one. You may want to rename it before manipulating it. The default name is "OTApkg"
You can download it here and I welcome someone else's better ability to parse the file contents.
(Last OTA I actually ended up flashing with htc_fastboot partition-by-partition in download mode.)
Click to expand...
Click to collapse
I renamed mine also and was able to extract the contents. I have rezipped the files (Files only, not flashable) here is anyone wants them. Strange, 2gb ota but contents are 103mb. I did not install tho, just ran the update to pull the updated system img.
kc6wke said:
I renamed mine also and was able to extract the contents. I have rezipped the files (Files only, not flashable) here is anyone wants them. Strange, 2gb ota but contents are 103mb. I did not install tho, just ran the update to pull the updated system img.
Click to expand...
Click to collapse
NVM. Reread your post. Do you think the firmware would be flashable if renamed 2PS6IMG.zip?
hgoldner said:
NVM. Reread your post. Do you think the firmware would be flashable if renamed 2PS6IMG.zip?
Click to expand...
Click to collapse
I just tried it and it flashed. But remove the boot.img first. The. 20 boot.img won't work on. 18.
kc6wke said:
I just tried it and it flashed. But remove the boot.img first. The. 20 boot.img won't work on. 18.
Click to expand...
Click to collapse
Thanks, , my file may have been corrupted. Going to upload a file I could open on my workstation instead and re-link.
Original upload was corrupted; I've uploaded corrected file and added md5.
Added two firmware only update files, one without boot and one without boot or recovery.
Verizon getting Oreo ota
mattie_49 said:
Verizon getting Oreo ota
Click to expand...
Click to collapse
Yup.
hgoldner said:
Yup.
Click to expand...
Click to collapse
Can I now flash Maximum or Lee-Droid Oreo roms without having to do anything other than installing twrp first? That is correct isn't it?
mattie_49 said:
Can I now flash Maximum or Lee-Droid Oreo roms without having to do anything other than installing twrp first? That is correct isn't it?
Click to expand...
Click to collapse
I would go by the OP's in each of those ROM threads, but presumably you are now on Oreo firmware, so I don't see why not.
Maximus doesn't do vzw..
Hello,
This would be a short & sweet guide on how to install a custom ROM on your Samsung using ODIN. I'm going to tailored this guide for the S10e G9700 HK version (is the phone I own) I'm a linux user but Odin only runs on Windows so this works 100% on a Windows 10 VM an of course native on Windows.
1. Who is this for?
For people that can't or don't want to install TWRP on their devices. For example TWRP doesn't work with the S10E Snapdragon G9700 the HK/CHG version.
2. Will this method work on my bootloader locked phone?
NO!
Bootloader locked phones are locked in hardware there's no way to flash anything but carriers ROMs to them. If you can unlock the bootloader this guide will work for you.
https://www.getdroidtips.com/how-to-unlock-bootloader-on-samsung-galaxy-phones/
3. Can I use this only with the G9700 phone?
No you can use any device, but this guide is tailored to the s10e g9700; because the TWRP version for this phone doesnt work with Android10.
4. Why not use Heimdall and do the guide entirely on Linux?
I use Manjaro [Arch] linux and tried to get Heimdall to work but couldn't, so choose the path of least resistance, so ODIN and windows is what we got .
5. Recommended ROMs?
I'm not a fan of Google Apps so my recommendations are these (2) ROMs:
1. https://github.com/phhusson/treble_...ad/v219/system-quack-arm64-aonly-floss.img.xz (No bloat, Stock Android 10 with FOSS Apps replacements of Gapps, you can install your own on top, Like I use Google Maps (the only Gapp I use)
2. https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_bvN.img.xz/download (Lineage OS 17.1 - this is vanilla, you will have to install an App store like F-Droid or Aurora from the .apk files using ADB [FYI] - This is what I use as my daily driver!
note* the proximity sensor doesn't work with the S10E and PHH based ROMs - https://github.com/phhusson/treble_experimentations/issues/592#issuecomment-519853332
6. If using a PHH based ROM from phhusoon set this to get Bluetooth Audio working?
Under Developer Options - toggle ON "Disable Bluetooth A2DP hardware offload"
Credit goes to (for their work) @phhusson @AndyYan (Project Treble PHH & LineageOS PHH) & @mkh.mourad (CMD Script)
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Requirements
7zip - https://www.7-zip.org/
Odin - https://samsungodin.com/
CMD or PowerShell (Windows) - View attachment tar-md5-script-tool.zip
Step-by-Step Process
Get your phone Official Stock ROM - https://samfw.com/firmware/SM-G9700/TGY (this is the one for my phone)
Extract the downloaded file (you'll have the BL, AP, CP, CSC) .TAR.MD5 files
Using 7zip extract just the AP .tar.md5 (it'll have img.lz4 files: boot.img.lz4, vbmeta.img.lz4 & system.img.ext4.lz4)
Download a clean vbmeta.img file from Google - https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Now we need to compress the vbmeta.img file (just downloaded from google) using LZ4.
Go into the /bin folder inside the script zip file provided (or download LZ4 from https://github.com/lz4/lz4/releases)
Run this command
Code:
lz4.exe -B6 --content-size vbmeta.img vbmeta.img.lz4
Done with vbmeta.img (keep the vbmeta.img.lz4 file)
Now download your favorite Custom ROM (https://github.com/phhusson/treble_...ad/v219/system-quack-arm64-aonly-floss.img.xz)
Using 7zip extract the .img.xz file & Rename the file inside to system.img.ext4 (this is the system OS without lz4 compression)
Now we need to compress the system.img.ext4 file (just renamed) using LZ4.
Run this command
Code:
lz4.exe -B6 --content-size system.img.ext4 system.img.ext4.lz4
Done with system.img.ext4 (keep the system.img.ext4.lz4 file)
Want to Root the device? if yes continue on; if not skip to step 24
Take the boot.img.lz4 extracted from the stock ROM (the AP.tar.md5 file)
We need to decompress this file using LZ4.
Run this command
Code:
lz4.exe -d boot.img.lz4 boot.img
Transfer this boot.img file to a phone and run Magisk Manager (doesnt need to be a rooted phone) and patch the boot.img file
Take the patched file on your phone and transfer to your computer
Rename the patched Magisk file to boot.img
Now we need to compress the boot.img file (just renamed) using LZ4.
Run this command
Code:
lz4.exe -B6 --content-size boot.img boot.img.lz4
Done with the renamed Magisk patched (keep the boot.img.lz4 file)
Replace the stock boot.img.lz4, vbmeta.img.lz4 & system.img.ext4.lz4 with the new customize files
Extract the files from tar-md5-script-tool.zip
Copy or Move all files below to the tar-md5-script-tool folder
Files are: (we don't need the meta-data folder with fota.zip)
boot.img.lz4
dqmdbg.img.ext4.lz4
dtbo.img.lz4
persist.img.ext4.lz4
recovery.img.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vbmeta.img.lz4
vendor.img.ext4.lz4
Now we are going to build the AP file to use with Odin
Run the batch.bat file from the tar-md5-script-tool folder
Once it finishes go to the /tar-md5-script-tool/temp-folder/
Inside you will find the AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
Flash the BL, CP, CSC (use HOME_CSC) from your Stock ROM & AP (using AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5)
Done
Thanks to @Alberbeast for reaching out and encouragement to help the community and S10e G9700 owners :good:
note* the proximity sensor doesn't work with the S10E and PHH based ROMs - https://github.com/phhusson/treble_e...ment-519853332
Click to expand...
Click to collapse
This issue has actually been fixed a long time ago, you need to select "Enable extra sensors" in Treble settings though.
If someone knows or provides a place where to upload a complete ROM I can upload the Complete AP.tar.md5 ROM for LOS 17.1 OS Rooted with Magisk and the Android Stock FOSS image just to use with Odin. Let me know! Thanks
phhusson said:
This issue has actually been fixed a long time ago, you need to select "Enable extra sensors" in Treble settings though.
Click to expand...
Click to collapse
Oh thanks! I did had it enable and it didnt pair with my car radio; but I will try it and edit the post accordingly and let you know if theres a bug with the G9700 if it doesnt work
wow this is awesome:laugh: thank you so much @kkoo for the effort to create this guide, it's a life saver for those of us who can't use twrp and want to try aosp.
Thanks again bro!
I am new to Samsung
Following OP doesnt trip knox and other Samsung stuff , correct ? Which means, I can reflash with Samsung stock rom with losing samsung functionality like samsung pay.
Does it work with us or canadian version of the snapdragon?
pchetan2 said:
Following OP doesnt trip knox and other Samsung stuff , correct ? Which means, I can reflash with Samsung stock rom with losing samsung functionality like samsung pay.
Click to expand...
Click to collapse
You can always reflash back to Samsung Stock ROM. I don't use any Samsung App so never cared about knox, but I assume it does trip knox.
bilrage said:
Does it work with us or canadian version of the snapdragon?
Click to expand...
Click to collapse
No it doesn't work with any North America Galaxy S10 as those have the bootloader locked!
Do the Roms have gaps?
Diaze said:
Do the Roms have gaps?
Click to expand...
Click to collapse
Here
https://github.com/phhusson/treble_experimentations/releases
Get the one for your phone Arm64 probably with Gapps.
kkoo said:
If someone knows or provides a place where to upload a complete ROM I can upload the Complete AP.tar.md5 ROM for LOS 17.1 OS Rooted with Magisk and the Android Stock FOSS image just to use with Odin. Let me know! Thanks
Click to expand...
Click to collapse
You can upload your complete rom here https://androidfilehost.com/
Can you please explain why you use Aonly and ABonly both rom in this tutorial..? as I know only ABonly rom is for galaxy 10 series. maybe I am wrong but can you please explain it..
Thanks for your hard work Brother..
Nobin118960 said:
You can upload your complete rom here https://androidfilehost.com/
Can you please explain why you use Aonly and ABonly both rom in this tutorial..? as I know only ABonly rom is for galaxy 10 series. maybe I am wrong but can you please explain it..
Thanks for your hard work Brother..
Click to expand...
Click to collapse
Hey, sorry I already deleted the Windows VM with the complete ROM images.
Yes for my S10E Galaxy phone I use the Aonly ROM as this is what worked for me. Also I don't plan to use the functionality of an A/B ROM so to meet the extra things A/B gives are unnecessary. But like you probably assume, you can use any ROM or Phone you like. I based the tutorial on the Galaxy S10e because thats what I own.
Excited with this. I own a G9700 HK version, and I didn't even root it - been rooted since like 2012.
Miss custom roms and this thread completely encourages me to give it a shot for this device. Thank you.
Did you manage to get microg installed on LineageOs?
Will this work for the Snapdragon S9+ (SM-G965U1)?
Does it work with Exynos Devices?
Samsung Galaxy m11 ships with 32 bit os android 10 Snapdragon 450. So, which gsi should be used?
Litleck said:
Will this work for the Snapdragon S9+ (SM-G965U1)?
Click to expand...
Click to collapse
Similar quotations here... I have a N950U (ATT)
I really miss my GS2 and how easy it was too flash that device!
Nice, thanks for sharing.
I wonder if it trips Knox, if someone can check.
is it possible to flash an older firmware through this process?