Hi,
i'm trying to customize the system.img for my own purpose and flash it via Odin.
i'm running Ubuntu 14.04 TLS.
i did some tests and non of them worked, the flash was succeeded but i get soft brick (bootloop)
so, what is did?
these steps, please correct me if i did something wrong.
1)simg2img on the extracted system.img from the stock tar.
2)mount ext4 type the converted system.raw using the following command: mount -t ext4 -o loop img.raw /mnt/
now i want to repack it without making changes (for tests), using the following commands:
1)make_ext4fs -s -l 3145728000 -a system system_nonbloat.img /mnt
2)sgs4ext4fs --bloat system_nonbloat.img system.img
the sizes are not equals. (~30mb less than the original system image).
someone know's what i'm doing wrong?
thanks!
Try it without the - a system variable.
ashyx said:
Try it without the - a system variable.
Click to expand...
Click to collapse
Thanks for your quick reply,
i just tried this, and now i have only few mb missing,
system_out.img -> 2611942608
system_original.img -> 2644169200
can you explain why the sizes are not equals?
and still, not working.
Amit Abitbul said:
Thanks for your quick reply,
i just tried this, and now i have only few mb missing,
system_out.img -> 2611942608
system_original.img -> 2644169200
can you explain why the sizes are not equals?
and still, not working.
Click to expand...
Click to collapse
Where did you get make_ext4fs from?
ashyx said:
Where did you get make_ext4fs from?
Click to expand...
Click to collapse
I compiled the tools from this git
github.com /ASdev/android_img_repack_tools/tree/android-5.0.2
Amit Abitbul said:
I compiled the tools from this git
github.com /ASdev/android_img_repack_tools/tree/android-5.0.2
Click to expand...
Click to collapse
Compile from branch 5.1.1 and try again.
ashyx said:
Compile from branch 5.1.1 and try again.
Click to expand...
Click to collapse
i have the same result.
still missing few megabytes.
Amit Abitbul said:
i have the same result.
still missing few megabytes.
Click to expand...
Click to collapse
I wouldn't worry about the packed size difference. Convert your output image to raw and see if the size matches the original raw image.
Also you probably need to patch the boot.img to remove dm-verity.
Supersu can do this for you.
ashyx said:
I wouldn't worry about the packed size difference. Convert your output image to raw and see if the size matches the original raw image.
Also you probably need to patch the boot.img to remove dm-verity.
Supersu can do this for you.
Click to expand...
Click to collapse
Yes, the raw image is the same,
What do you mean about the boot.img and dm-verity?
I'm kind of new in this world.
If I repack without making any change I need to do something with the boot image?
Amit Abitbul said:
Yes, the raw image is the same,
What do you mean about the boot.img and dm-verity?
I'm kind of new in this world.
If I repack without making any change I need to do something with the boot image?
Click to expand...
Click to collapse
Dm-verity is part of a chain of trust which does an integrity check on the system partition.
If it is modified the device won't boot.
This is why supersu patches the boot.img to disable it.
Try installing the latest supersu it should disable dm-verity then see if it boots.
ashyx said:
Dm-verity is part of a chain of trust which does an integrity check on the system partition.
If it is modified the device won't boot.
This is why supersu patches the boot.img to disable it.
Try installing the latest supersu it should disable dm-verity then see if it boots.
Click to expand...
Click to collapse
And if I don't want to root the device, what I need to do?
I really appreciate your help, thank you!
Amit Abitbul said:
And if I don't want to root the device, what I need to do?
I really appreciate your help, thank you!
Click to expand...
Click to collapse
If you've already modified the system partition what difference does it make?
Flash this zip in twrp
https://www.androidfilehost.com/?fid=24459283995297893
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
If you've already modified the system partition what difference does it make?
Flash this zip in twrp
https://www.androidfilehost.com/?fid=24459283995297893
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
I will flash it in users tablets, I don't want them to have root access,
And i dont want to disable knox.
Amit Abitbul said:
I will flash it in users tablets, I don't want them to have root access,
And i dont want to disable knox.
Click to expand...
Click to collapse
Which version of TAB S2?
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
Which version of TAB S2?
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
SM-T810 WiFi Version.
Running android 5.0.2.
Amit Abitbul said:
SM-T810 WiFi Version.
Running android 5.0.2.
Click to expand...
Click to collapse
The problem is to patch the boot.img and disable dm-verity you need to unpack the boot.img make the modifications then repack.
This leaves you with an unsigned image that may trip knox.
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
The problem is to patch the boot.img and disable dm-verity you need to unpack the boot.img make the modifications then repack.
This leaves you with an unsigned image that may trip knox.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
boot.img modifications? what i need to do there? maybe unpack and repack without making changes?
ashyx said:
The problem is to patch the boot.img and disable dm-verity you need to unpack the boot.img make the modifications then repack.
This leaves you with an unsigned image that may trip knox.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
do you have a tutorial how to build my own based stock rom?
And how to make the final file, so I can flash it?
I don't know what I missing here, and it still not working.
Stuck on "Samsung Tab S2"
Amit Abitbul said:
do you have a tutorial how to build my own based stock rom?
And how to make the final file, so I can flash it?
I don't know what I missing here, and it still not working.
Stuck on "Samsung Tab S2"
Click to expand...
Click to collapse
None of it going to work unless you're prepared to patch the boot.img and remove dm-verity.
ashyx said:
None of it going to work unless you're prepared to patch the boot.img and remove dm-verity.
Click to expand...
Click to collapse
I flashed your zip file and the cf auto root via twrp,
And still... Nothing, what I need to do to boot.img?
Related
Thanks goes to @nilezon for giving me the rundown, as it is all from his repos, save for a couple of things to make it work for the Z5 instead.
(Yes, your bootloader has to be unlocked)
Kernel is based on firmware version 32.0.A.6.152
There is two versions of the kernel: one with a recovery script, and one without.
The one with the recovery script will allow you to boot into recovery during your phone's startup process.
To enter recovery:
Boot up your phone like normal. Wait for the LED status light to turn amber. Once that happens, start pressing the volume buttons a few times. This will take you into the recovery menu.
The one without the recovery script does not have this option. This means that your phone will boot up a few seconds faster than the one with it.
Xposed: The Camera 2.0.apk plays nicely with Xposed now. No need to deoxed it manually!
Anyways:
TWRP
https://goo.gl/k9PiFV - TWRP 2.8.7.0
KERNELS
https://goo.gl/wzUAv4 - With recovery script, flashable zip file
https://goo.gl/8LTc9l - No recovery script, .img file that must be flashed through fastboot
For the recovery:
Code:
fastboot boot recovery.img
to just boot into it to flash a zip
OR
Code:
fastboot flash recovery.img
to flash it (although, you will need to do fastboot boot recovery the first time to get into it)
Kernel:
Code:
fastboot flash boot z5_stock_fixed_fixed.img
- For the .img file
The blues are oranges instead, like his, but it is kinda cute.
Have fun.
For unlocked bootloaders?
Sent from my Sony Xperia Z5
Snaqejack said:
For unlocked bootloaders?
Sent from my Sony Xperia Z5
Click to expand...
Click to collapse
Yes.
Technically you can flash the boot.img in the recovery ?
bazhip said:
This isn't flashable, only bootable:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
nilezon said:
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
Click to expand...
Click to collapse
I saw that at the bottom of your post right afterwards I'll modify it in a bit here, but I wanted to make sure it was going first. Thanks for making that script!
Thanks, bazhip.
Can you provide the modified source and a quick run through on how to compile it on github?
yannik~ said:
Thanks, bazhip.
Can you provide the modified source and a quick run through on how to compile it on github?
Click to expand...
Click to collapse
The kernel or TWRP? I'm kinda busy though so I'm not sure when I'll get around to it. If you want, look at the dirty ROOT thread for nizelion and my posts. I was pretty vocal about the process and what I was doing, as it was my first time ever doing it. You should be able to follow it, I think.
Were the only changes you made disabling SONY_SECURITY_RIC and DM_VERITY in the defconfig?
zwliew said:
Were the only changes you made disabling SONY_SECURITY_RIC and DM_VERITY in the defconfig?
Click to expand...
Click to collapse
That, and ro.secure disabled and ro.debuggable enabled. As close to stock as possible.
bazhip said:
Thanks goes to @nilezon for giving me the rundown, as it is all from his repos, save for a couple of things to make it work for the Z5 instead.
(Yes, your bootloader has to be unlocked)
Anyways:
https://goo.gl/k9PiFV - TWRP 2.8.7.0
https://goo.gl/8LTc9l - Kernel that I compiled that allows root
This isn't flashable, only bootable:
Code:
fastboot boot recovery.img
Kernel:
Code:
fastboot flash boot z5_stock_fixed_fixed.img
The blues are oranges instead, like his, but it is kinda cute.
Have fun.
Click to expand...
Click to collapse
Can it be use on E6683
Build no - 32.0.A.6.152
winkhant said:
Can it be use on E6683
Build no - 32.0.A.6.152
Click to expand...
Click to collapse
It's built for the 6653, but I think it should work for the 6683. Give it a shot. If it doesn't, just flash back the stock kernel.sin from the ftf.
winkhant said:
Can it be use on E6683
Build no - 32.0.A.6.152
Click to expand...
Click to collapse
I've applied this on my E6683. All looks good :good:
magadaner said:
I've applied this on my E6683. All looks good :good:
Click to expand...
Click to collapse
Awesome! That's what I figured, but good to have confirmation. I'll edit accordingly.
nilezon said:
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
Click to expand...
Click to collapse
Is there anything that needs to be changed with the recovery script to work on the Z5? I threw it into my kernel and followed the directions to a tee and I get a bootloop. I saw @AndroPlus made a kernel too using your script, so I flashed it to see if it worked and it was fine. I unpacked his boot.img and looked at it and the structure was the exact same. After hitting my head against a wall for a while, I tried repacking his just to make sure I wasn't crazy. The file size between his initial boot.img and the repacked one was a few KB different, and when I repack his, it bootloops too. So then I made sure mkboot tools were working fine and I unpacked/repacked my initial kernel, and it boots just fine.
Then I tried breaking it down:
I took my kernel, unpacked/repacked and it was fine. Then I copied over the bootrec folder, repacked, and it was fine. Then I made sure the symlink was working, so I:
Code:
mv init init.real
ln -s init.real init
and it booted just fine.
Then I did the final
Code:
rm init
ln -s /bootrec/init.sh init
and repacked, and it bootloops forever Any ideas about what is happening?
The only thing I can think of is that I messed up the symlink some how, but I dont know why AndroPlus's works before repacking and not after. Bleh :/
EDIT: **** everything. I ended up using SuperRs kitchen instead. That worked just fine. Noooo idea why mkbootimg_tools failed me.
External SD card is not detected on E6683.
Masa. T said:
External SD card is not detected on E6683.
Click to expand...
Click to collapse
Once I get my Z5 dual (E6683) in I may try to build a kernel specifically for the E6683's. I need to figure out how much I'll lose from losing the DRM keys.
Masa. T said:
External SD card is not detected on E6683.
Click to expand...
Click to collapse
In the kernel or TWRP?
EDIT: My bad, I spaced on the variants. I thought the 6683 was the baseband variant, not the dual sim. Yeah, I wouldn't roll with this on there.
And this is confirmed as working on the Z5 ?. because I have waited for root for this for some time now, and if it works I will be a happy man.
MeX_DK said:
And this is confirmed as working on the Z5 ?. because I have waited for root for this for some time now, and if it works I will be a happy man.
Click to expand...
Click to collapse
This is not an exploit, if that is what you are asking. As stated in OP, you need to unlock your bootloader first. The kernel is merely the stock kernel with the security features disabled, which allows you to be able to flash SuperSU. But yes, it works.
I DIRECT YOUR ATTENTION TO THIS THREAD INSTEAD: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
It's easier as you don't need to get a decrypted boot image.
Thank you ajsmsg78 for your work on this.
If you rooted using this method you don't need to re-root. Only difference is that SuperRoot patches boot image to "decrypt" automatically.
Perfect. Will try this later and report back. Thank you!
Just a tip, wipe dalvik & cache after flashing, fixed some small bugs for me (Not being able to get into developer options)
Also, RSA breaks if you flash the wrong boot image (165 on 138) so no adb
Yes!!!!
ante0 said:
Just a tip, wipe dalvik & cache after flashing, fixed some small bugs for me (Not being able to get into developer options)
Also, RSA breaks if you flash the wrong boot image (165 on 138) so no adb
Click to expand...
Click to collapse
So does this work if RSA break...Sorry I'm a noob. Is this process safe to root? Which one should image should I flash
..The latest one I'm assuming.
Sent from my MHA-L29 using XDA-Developers Legacy app
Ckao said:
So does this work if RSA break...Sorry I'm a noob. Is this process safe to root? Which one should image should I flash
..The latest one I'm assuming.
Sent from my MHA-L29 using XDA-Developers Legacy app
Click to expand...
Click to collapse
What model are you using?
Check Settings - About - Build number
MHA-L29...
About safeness, worst case you can use FunkyHuawei to restore (Unless you're using the US C567, and it's not a free service). But restoring stock boot using fastboot should be enough, and you would do a data wipe in vain.
ante0 said:
What model are you using?
Check Settings - About - Build number
MHA-L29...
About safeness, worst case you can use FunkyHuawei to restore (Unless you're using the US C567, and it's not a free service). But restoring stock boot using fastboot should be enough, and you would do a data wipe in vain.
Click to expand...
Click to collapse
Sent from my MHA-L29 using XDA-Developers Legacy app
*in that way we don't need to have the boodloader unlocked ??
Ckao said:
View attachment 4041592
Sent from my MHA-L29 using XDA-Developers Legacy app
Click to expand...
Click to collapse
So... To be clear for the folks that need clarity (me) to prevent messing up a device without a downloadable full ROM (though I'll do a full TWRP Backup to the best of my ability post step one), the current US only build appropriate boot image is B138?
Thank you for the screenshot. Ready to pop open the new device box and unlock the bootloader and fastboot. This helps so I'm flashing the correct modified boot.img in recovery.
talstar said:
*in that way we don't need to have the boodloader unlocked ??
Click to expand...
Click to collapse
Yes you must unlock your bootloader in order to flash TWRP and install root.
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
---------- Post added at 07:33 PM ---------- Previous post was at 07:32 PM ----------
Time to break my mate 9 back out and root it again. Thank you!
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
@ajsmsg78 the boot images cause a bootloop for MHA-L29C185 could you please make a special boot file for it, here is the link for C185B138
https://mega.nz/#!PsxGhJ7R!iN7g1OaEbaw-4jXvj9cXhA_wfXwoaDN8Fgs8X7PrTCc
Will you be supporting M9P ?
This boot looped my MHA-L29C636B138.
Blue.Ember said:
@ajsmsg78 the boot images cause a bootloop for MHA-L29C185 could you please make a special boot file for it, here is the link for C185B138
https://mega.nz/#!PsxGhJ7R!iN7g1OaEbaw-4jXvj9cXhA_wfXwoaDN8Fgs8X7PrTCc
Click to expand...
Click to collapse
Yeah when I get home I'll take care of it. Make sure your data is decrypted before you flash the boot.img. I had no issues with any boot images on my C567 US version.
ante0 said:
Just a tip, wipe dalvik & cache after flashing, fixed some small bugs for me (Not being able to get into developer options)
Also, RSA breaks if you flash the wrong boot image (165 on 138) so no adb
Click to expand...
Click to collapse
I'm gonna fix that in the boot.img. I had issues with adb being unauthorized but realized what the issue was.
samnahata said:
Will you be supporting M9P ?
Click to expand...
Click to collapse
No I can only support the phone that I own. However, if you need a boot.img decrypted send me the file and I'll do it.
ajsmsg78 said:
No I can only support the phone that I own. However, if you need a boot.img decrypted send me the file and I'll do it.
Click to expand...
Click to collapse
Sure, i would love to help the community. Could you kindly explain to me how i can extract this boot.img?
samnahata said:
Sure, i would love to help the community. Could you kindly explain to me how i can extract this boot.img?
Click to expand...
Click to collapse
In TWRP do a backup of you rom then go into your sdcard then into TWRP, then backups, then the next folder with all the numbers then into the name of your backup then send me the boot.emmc.win file.
ajsmsg78 said:
In TWRP do a backup of you rom then go into your sdcard then into TWRP, then backups, then the next folder with all the numbers then into the name of your backup then send me the boot.emmc.win file.
Click to expand...
Click to collapse
Thank you. I will get on it and send it to you ASAP.
Fixed adb on B365.
Here are stock Mate 9 boot images that are modified to not force encryption. You can flash these in fastboot or TWRP, just select Image in TWRP then flash. An insecure boot image lets you use adb remount, and adb push or adb pull etc. to /system and its contents. Basically it's using ADB as root. I'll modify more upon request provided you link me to the boot you want modified.
ALL VERSIONS:
https://www.androidfilehost.com/?w=files&flid=152685
*To remove encryption after flashing to stock , boot into TWRP, format data, reboot recovery then flash a decrypted boot.img. If you're running a stock modified kernel, formatting data alone will not remove encryption. The idea is to always be decrypted. Never boot the system with a stock unmodified boot.img or it will encrypt your internal storage. So if you're fastboot flashing back to stock from another rom, flash a modified boot.img instead of the stock one*
In the full root thread it was advised to format data first and then flash modified boot image. In this OP it says to flash modified boot image and then format data. Does the order matter or can you do it both ways? Thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
JATCHUHAN said:
In the full root thread it was advised to format data first and then flash modified boot image. In this OP it says to flash modified boot image and then format data. Does the order matter or can you do it both ways? Thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
Click to expand...
Click to collapse
The order doesn't matter as long as you Format Data and have the Decrypted boot.img installed you're good. I updated the OP with the same directions as the full root thread so there is no confusion. Thanks for pointing this out.
Ok thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
JATCHUHAN said:
Ok thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Just to clarify. After you Format Data your data partition gets decrypted until first boot.
That's why you have to flash the decrypted boot.img before booting.
ante0 said:
Just to clarify. After you Format Data your data partition gets decrypted until first boot.
That's why you have to flash the decrypted boot.img before booting.
Click to expand...
Click to collapse
Yes I format data and flash decrypted boot before booting the phone. All is OK
Also aj could you decrypt the boot for L09C432B156 please, the link is below
https://drive.google.com/file/d/0B-qepxzncI0DSVpQN1RMTGZOX00/view?usp=drivesdk
Many thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
Do you think in next days it will be possibile to get boot images also for Pro/ PD Mate 9? Thanks.
lukemo said:
Do you think in next days it will be possibile to get boot images also for Pro/ PD Mate 9? Thanks.
Click to expand...
Click to collapse
What's your full build number (Settings-About)?
ante0 said:
What's your full build number (Settings-About)?
Click to expand...
Click to collapse
LON-L29C721B138...is the last firmware for porsche design mate 9...
lukemo said:
LON-L29C721B138...is the last firmware for porsche design mate 9...
Click to expand...
Click to collapse
I can decrypt when I get home in 2 hourish.
lukemo said:
Do you think in next days it will be possibile to get boot images also for Pro/ PD Mate 9? Thanks.
Click to expand...
Click to collapse
Just send me a link to the boot image you need done
ajsmsg78 said:
Just send me a link to the boot image you need done
Click to expand...
Click to collapse
Thanks a lot. Tomorrow I'll be back to Milan and I'll download the ROM and extract the boot.img file.
ajsmsg78 said:
Just send me a link to the boot image you need done
Click to expand...
Click to collapse
Here you can find the boot.img for Porsche Design B138. Thanks.
https://www.dropbox.com/s/45adneap6dduab5/BOOT.img?dl=0
lukemo said:
Here you can find the boot.img for Porsche Design B138. Thanks.
https://www.dropbox.com/s/45adneap6dduab5/BOOT.img?dl=0
Click to expand...
Click to collapse
https://www.dropbox.com/s/tgfdprba4ikuaah/decrypted-boot-MHA-L29C721B138.img?dl=0
And sorry, totally forgot it yesterday
ante0 said:
https://www.dropbox.com/s/tgfdprba4ikuaah/decrypted-boot-MHA-L29C721B138.img?dl=0
And sorry, totally forgot it yesterday
Click to expand...
Click to collapse
Why to be sorry? You're so kind, thanks, I'll try it in the next few days. Only a question: you called the decrypted boot MHA-L29, obviously it's my LON-L29C721B138 decrypted I think...
lukemo said:
Why to be sorry? You're so kind, thanks, I'll try it in the next few days. Only a question: you called the decrypted boot MHA-L29, obviously it's my LON-L29C721B138 decrypted I think...
Click to expand...
Click to collapse
Oh, the filename is just incorrect. It's the same Boot you posted
https://www.dropbox.com/s/tgfdprba4ikuaah/decrypted-boot-LON-L29C721B138.img?dl=0
Updated file name.
How come there's no US C567 decrypted boot image?
posydon1 said:
How come there's no US C567 decrypted boot image?
Click to expand...
Click to collapse
Was wondering the same thing, haven't seen anything for it. I just want adb to free up wifi hotspot on my unlimited plan
posydon1 said:
How come there's no US C567 decrypted boot image?
Click to expand...
Click to collapse
erikclaw said:
Was wondering the same thing, haven't seen anything for it. I just want adb to free up wifi hotspot on my unlimited plan
Click to expand...
Click to collapse
Because there is no Firmware update for it yet.
If you have TWRP, please backup boot and post here
ante0 said:
Because there is no Firmware update for it yet.
If you have TWRP, please backup boot and post here
Click to expand...
Click to collapse
I can do that
Edited: https://db.tt/ke4c3m3tr1
Here's System dump from nokia 5, enjoy.
Link
note: this will be quite useless for now but once the bootloaders are unlocked and i can port TWRP if someone will send me the update.zip that is for Nokia 5.
aboot
Dude, can you modify aboot partition to enable adb and turn off dm-verity and flash using QFIL?
wolfyapl said:
Dude, can you modify aboot partition to enable adb and turn off dm-verity and flash using QFIL?
Click to expand...
Click to collapse
you know modifying aboot could end up bricking your device
Yeah, but that's the only way to modify the bootloader, am I right? Btw can ya tell me the difference between aboot and boot.img?
wolfyapl said:
Yeah, but that's the only way to modify the bootloader, am I right? Btw can ya tell me the difference between aboot and boot.img?
Click to expand...
Click to collapse
Boot.img contains your kernel & Ram Disk
SpamMachine said:
Here's System dump from nokia 5, enjoy.
Link
note: this will be quite useless for now but once the bootloaders are unlocked and i can port TWRP if someone will send me the update.zip that is for Nokia 5.
Click to expand...
Click to collapse
Could you please upload the media folder alone?
Ota 7.1.2 for TA-1024 is live
To those wo have trouble to root their phones!
Try to use a command line lz4 tool, to extract the boot.img from boot.img.lz4. I tried before with 7Zip and it didn't worked. After I tried a command line tool, even the sizes of the boot images were different. This did the trick for me
best regards
nebkas
nebkas said:
To those wo have trouble to root their phones!
Try to use a command line lz4 tool, to extract the boot.img from boot.img.lz4. I tried before with 7Zip and it didn't worked. After I tried a command line tool, even the sizes of the boot images were different. This did the trick for me
best regards
nebkas
Click to expand...
Click to collapse
which one? could u please link to that tool or share here your using?
an-_-dro said:
which one? could u please link to that tool or share here your using?
Click to expand...
Click to collapse
I used that one. Just drop off the boot.img.lz4 on the .exe file.
nebkas said:
I used that one. Just drop off the boot.img.lz4 on the .exe file.
Click to expand...
Click to collapse
i also used that but still not successful >_<
i thought different tool, but anyway thanks.
an-_-dro said:
i also used that but still not successful >_<
i thought different tool, but anyway thanks.
Click to expand...
Click to collapse
I'm sorry. I also flashed the complete downloaded firmware(all files) before I extracted the boot.img.lz4 from it. maybe thats why it worked?
nebkas said:
I'm sorry. I also flashed the complete downloaded firmware(all files) before I extracted the boot.img.lz4 from it. maybe thats why it worked?
Click to expand...
Click to collapse
maybe 4 or 5 attempts with different patched img but i never make it hahaha of course i also flashed complete downloaded firmware after and wait 7 days between each attempt.
I struggled a lot too yesterday(got my device yesterday ). I used also this one to repack the .img and flashed it with the odin version in the bin directory.
7zip is enough to wrap img file to tar
an-_-dro said:
7zip is enough to wrap img file to tar
Click to expand...
Click to collapse
yes, maybe. But who knows what all the apps are doing. that file makes it to a tar.md5.
Thanks OP... it worked on my A605FN.
I was unable to patch the boot image in Magisk Manager as it returned error.
I tried your tool and it patched.
Wouldn't it be simpler to just flash the last Asphyx twrp build, and then flash magisk from twrp?
Sent from my SM-A605FN using Tapatalk
pr1jker said:
Wouldn't it be simpler to just flash the last Asphyx twrp build, and then flash magisk from twrp?
Sent from my SM-A605FN using Tapatalk
Click to expand...
Click to collapse
Sure, but there wasn't any twrp working when I started the Thread
Hello. I am having an issue getting my oem unlock option back. I have followed every tutorial that I could find trying to get rmm back to normal status and have had my a600t1 on for 39 days nonstop. If anyone could give advice or just point me in the right direction I would greatly appreciate it. I'm at a loss. Thanks in advance for any help
guess maybe nobody can help with my issue. i dont know about you all but its polite to answer even if the answer is no.
Just share I have rooted my Samsung Galaxy A6 2018 SM-A600G Android 9 Pie with Magiskm you can watch this video https://youtu.be/1y1p7-Hzm_o
for rooting it, I have to install Magisk twice, one for prevent boot loop after install TWRP and second for rooting after install MagiskManager.
I have a problem with root. I can't set fingerprint because the System crash. After crash i have to install over again. I have notice that twrp recovery have an error when i go in internal storage It have 0mb and i must format
SubGenius said:
Thanks OP... it worked on my A605FN.
I was unable to patch the boot image in Magisk Manager as it returned error.
I tried your tool and it patched.
Click to expand...
Click to collapse
did you have boot.img for this devise but for 9.0 thx