I am trying to root my tecno f1 pro with magisk manager soon i was flashing the magisk_patched.img renamed boot.img i got an error
code:
C:\Program Files\platform-tools>fastboot flash boot boot.img
fastboot: error: boot partition is smaller than boot image
How can I fix this?
Re-partition Android of your phone so the boot.img fits.
jwoegerbauer said:
Re-partition Android of your phone so the boot.img fits.
Click to expand...
Click to collapse
How do I do that? My boot partition is 233kb and my Magisk patched image is 32mb.
Beelzebub6 said:
How do I do that? My boot partition is 233kb and my Magisk patched image is 32mb.
Click to expand...
Click to collapse
You have a wrong file patched. Normally the patched file can with 10MB or more.
Since you wrote the patched file have ONLY 233KB so never you can flash that!
DragonPitbull said:
You have a wrong file patched. Normally the patched file can with 10MB or more.
Since you wrote the patched file have ONLY 233KB so never you can flash that!
Click to expand...
Click to collapse
lol, my phone has updated since then, your right.
But then I downloaded my new stock rom which is android 11 and tried to continue with that but it still says the boot partition is too small. How would I re-partition so then my patched file can fit?
And also the original boot file straight outta boot.img.lz4 is 32.0mb same as patched but inside the .lz4 file it says that it is 16 bytes, should I worry about that?
Beelzebub6 said:
lol, my phone has updated since then, your right.
But then I downloaded my new stock rom which is android 11 and tried to continue with that but it still says the boot partition is too small. How would I re-partition so then my patched file can fit?
And also the original boot file straight outta boot.img.lz4 is 32.0mb same as patched but inside the .lz4 file it says that it is 16 bytes, should I worry about that?
Click to expand...
Click to collapse
I think thats just compression saying that but if u need try backup the boot partition via another method
Related
Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the T285, but should work on the T280.
If in doubt, check to see if your PARAM partition is mmcblk0p16.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Tab A (SM-T285).
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy TAB A (SM-T285) display is 720x1280.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select TAB-A-T285-LogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: T285 Boot Logo Changer
Mega: T285 Boot Logo Changer
device soft bricked but can enter download mode (Vol Up + PWR + Home). I did a:
# dd if=/dev/mmcblk0p16 of=/storage/emulated/0/param.lfs
before flashing the custom param. I restored the device using heimdall (GNU/Linux PC)
$ sudo heimdall flash --PARAM param.lfs
device rebooted and worked
gian20 said:
device soft bricked but can enter download mode (Vol Up + PWR + Home). I did a:
# dd if=/dev/mmcblk0p16 of=/storage/emulated/0/param.lfs
before flashing the custom param. I restored the device using heimdall (GNU/Linux PC)
$ sudo heimdall flash --PARAM param.lfs
device rebooted and worked
Click to expand...
Click to collapse
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
gcrutchr said:
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
Click to expand...
Click to collapse
the logo.jpg I used is about 600KB in size it may be the problem. What must be the right size so I do not overwrite anything?
I have dumped the partition /dev/block/mmcblk0p16 to a param.lfs
then the param.lfs appears to be a POSIX TAR Archive (GNU) can we just repack the file and modify only the logo.jpg? (the recovery script will repack the tar archive)
after modifying can we just write it with dd?
# dd if=./paramodified.tar of=/dev/block/mmcblk0p16
gian20 said:
the logo.jpg I used is about 600KB in size it may be the problem. What must be the right size so I do not overwrite anything?
I have dumped the partition /dev/block/mmcblk0p16 to a param.lfs
then the param.lfs appears to be a POSIX TAR Archive (GNU) can we just repack the file and modify only the logo.jpg? (the recovery script will repack the tar archive)
after modifying can we just write it with dd?
# dd if=./paramodified.tar of=/dev/block/mmcblk0p16
Click to expand...
Click to collapse
The original logo.jpg is under 100kb, so a 600kb file would be too big.
I would keep the file under 150kb just to be safe.
Yes, you can use dd to write the modified param file...that is what the logo changer script does.
gcrutchr said:
The original logo.jpg is under 100kb, so a 600kb file would be too big.
I would keep the file under 150kb just to be safe.
Yes, you can use dd to write the modified param file...that is what the logo changer script does.
Click to expand...
Click to collapse
The script works now, I've reduced the jpeg to 50KB but it is blurry. Thank You
I have uploaded my param.lfs (it is compressed with 7z to reduce size from 2MB to 420KB, 26193062 is a CRC32 hash checksum of the file to verify that it is not corrupt) from mmcblk0p16 that can be flashed with heimdall ($ sudo heimdall flash --PARAM param_26193062.lfs) if someone else messes up.
1. download param_26193062.lfs
2. decompress with 7z (7z x param_26193062.lfs.7z)
3. flash with device ($ sudo heimdall flash --PARAM param_26193062.lfs)
Unable to change Boot Logo
Hi,
I tried to change boot logo but failed. When i change mmcblk0p16 partition file with modified version of partition with my logo it doesn't work. I dig in to find out issue. I saw when ever devices restarts it have fresh copy of all partition files in /dev/block/ folder. I check modified dates of all partition files it always have last date when it was restarted. i don't know what is issue can you help out.
any help would be appreciated.
Thanks.
gcrutchr said:
Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the T285, but should work on the T280.
If in doubt, check to see if your PARAM partition is mmcblk0p16.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Tab A (SM-T285).
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy TAB A (SM-T285) display is 720x1280.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select TAB-A-T285-LogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: T285 Boot Logo Changer
Mega: T285 Boot Logo Changer
Click to expand...
Click to collapse
SM T285 flash wrong bootlogo.zip
Sir, I have Samsung Galaxy TAB A SM T285 ,I have a zip file of boot logo changer ...so i flash via TWRP Recovery .. and it works fine.. then some day later, I make a change in the zip file, I replace logo.jpg to another image then I flash the zip... and it"s flash successfully no error.. but then I reboot the system.. it shows black nothing will happen.. only download mode is in working condition.. so I flash stock rom via Odin but nothing will happen.... the TAB don't start Sir please help me....:crying::crying::crying::crying::crying::crying::crying::crying::crying:
hassansys2 said:
Hi,
I tried to change boot logo but failed. When i change mmcblk0p16 partition file with modified version of partition with my logo it doesn't work. I dig in to find out issue. I saw when ever devices restarts it have fresh copy of all partition files in /dev/block/ folder. I check modified dates of all partition files it always have last date when it was restarted. i don't know what is issue can you help out.
any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
soaib333 said:
Sir, I have Samsung Galaxy TAB A SM T285 ,I have a zip file of boot logo changer ...so i flash via TWRP Recovery .. and it works fine.. then some day later, I make a change in the zip file, I replace logo.jpg to another image then I flash the zip... and it"s flash successfully no error.. but then I reboot the system.. it shows black nothing will happen.. only download mode is in working condition.. so I flash stock rom via Odin but nothing will happen.... the TAB don't start Sir please help me....:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
gcrutchr said:
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
Click to expand...
Click to collapse
yes sir the jpg file is around 600 kb..... sir please help me..... :crying::crying::crying::crying::crying::crying:... please tell me sir what can i do for recover my device... sir please...... please sir :crying::crying::crying::crying::crying::crying::crying:
gcrutchr said:
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
Click to expand...
Click to collapse
sir please, can you send me stock boot logo tar.md5 file for SM-T285 ...... beacuase my phone is bricked.. only download mode is working...... if i flash the orignal bootlogo.tar.md5 i hope it will recover please sir help me.... i request you sir please :crying::crying::crying::crying::crying::crying:
I have a huge problem. I made the .jpg file too big and now the tablet won't boot except for DOWNLOAD MODE. I wasn't able to backup so I just downloaded the param.ifs from this reply.
gian20 said:
The script works now, I've reduced the jpeg to 50KB but it is blurry. Thank You
I have uploaded my param.lfs (it is compressed with 7z to reduce size from 2MB to 420KB, 26193062 is a CRC32 hash checksum of the file to verify that it is not corrupt) from mmcblk0p16 that can be flashed with heimdall ($ sudo heimdall flash --PARAM param_26193062.lfs) if someone else messes up.
1. download param_26193062.lfs
2. decompress with 7z (7z x param_26193062.lfs.7z)
3. flash with device ($ sudo heimdall flash --PARAM param_26193062.lfs)
Click to expand...
Click to collapse
Now I am using Windows 7 Heimdall to flash this. Except with this I am unable to flash because it's showing "Error: Failed to retrieve config descriptor."
Need help ASAP
Update: After a few tries, now it says
"Initializing Protocol...
Error: Failed to send data!Releasing device interface...
Solution: Used Odin. Basically, using 7zip, packed the param.lfs to a tar file, then packing that to a gzip file, then prooding to flash via ODIN
Any one have stock param.tar file for flashing on sm-t285?? Plz help me? ? ?
Can anyone help me i have installed that zip that u said using twrp and i thought when u said follow recovory install prompts i thought it will tell me to chose an image for boot logo and i have to select it so i prepared an image but i didnt know i have put the image in that zip so i have a boot logo of minions so after that i again installed the zip with the correct image but at the top it said fail and the boot logo is still minions and i dont know how to change back and tablets still working
Darksnite said:
Can anyone help me i have installed that zip that u said using twrp and i thought when u said follow recovory install prompts i thought it will tell me to chose an image for boot logo and i have to select it so i prepared an image but i didnt know i have put the image in that zip so i have a boot logo of minions so after that i again installed the zip with the correct image but at the top it said fail and the boot logo is still minions and i dont know how to change back and tablets still working
Click to expand...
Click to collapse
How big is the image you are trying to install?
gcrutchr said:
How big is the image you are trying to install?
Click to expand...
Click to collapse
Below 150 kb i dont have it now but i can get it again but i did make sure the picture was below 200 kb
And when i factory data reseted the phone it still have the same logo
gcrutchr said:
How big is the image you are trying to install?
Click to expand...
Click to collapse
Below 200 kb and i factory data reset the tablet but still the logo is there and i think my twrp is broken thats why because when i flash a file it says cant find e partion some thing but idk cuz i flashed super su again after flashing its firmwate and it worked
Darksnite said:
Below 200 kb and i factory data reset the tablet but still the logo is there and i think my twrp is broken thats why because when i flash a file it says cant find e partion some thing but idk cuz i flashed super su again after flashing its firmwate and it worked
Click to expand...
Click to collapse
You need yo rename your image to: logo.jpg
Then use 7zip or winrar to open bootlogochanger. replace the logo.jpg in the zip file with your logo.jpg
Hi There will be a root release or twrp? Thanks you xda. All is in the title.
Magisk by default should have the ability to root this. Follow the instructions for the Tab S6 and you should be good to go
Hi,
trying to root with Magisk SM-P610 (S6 Lite Exynos) but it failed with :
vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED (3)
vbmeta: VERIFICATION_DISABLED bit is set.
Doing wrong or not yet supported ?
Thanks
Try patching only boot.img
I think the same method for A51 and A71 should work here as well.
1) Download Firmware
2) Flash Using Odin
3) Unzip AP and copy boot.img.lz4 to your computer.
4) If you have LZ4 Decompress Tool use that to convert boot.img.lz4 to boot.img otherwise use ZArchiver. Anyway you need boot.img.
5) Patch boot.img using Magisk Manager Latest One.
6) Copy the patched file and rename it to boot.img and then use 7Zip to convert it into boot.tar.
7) Restart the phone to recovery and then boot to bootloader.
8) Uncheck Auto Reboot option in Odin and then flash boot.tar. Once it's successful then boot into recovery and then Wipe Data and Cache.
9) reboot into system and then use Magisk Manager to check if your device is rooted.
Change img file to .tar first
arjun_m4 said:
I think the same method for A51 and A71 should work here as well.
1) Download Firmware
2) Flash Using Odin
3) Unzip AP and copy boot.img.lz4 to your computer.
4) If you have LZ4 Decompress Tool use that to convert boot.img.lz4 to boot.img otherwise use ZArchiver. Anyway you need boot.img.
5) Patch boot.img using Magisk Manager Latest One.
6) Copy the patched file and rename it to boot.img and then use 7Zip to convert it into boot.tar.
7) Restart the phone to recovery and then boot to bootloader.
8) Uncheck Auto Reboot option in Odin and then flash boot.tar. Once it's successful then boot into recovery and then Wipe Data and Cache.
9) reboot into system and then use Magisk Manager to check if your device is rooted.
Click to expand...
Click to collapse
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
shark2003 said:
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
So it’s working for you finally?
**Snobilik** said:
So it’s working for you finally?
Click to expand...
Click to collapse
yup
---------- Post added at 06:12 PM ---------- Previous post was at 06:06 PM ----------
shark2003 said:
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
All these rooting instructions for the S6 Lite need to be corrected to save people from a headache. Why would people post instructions that are wrong. If they had did the steps themselves they would know and shouldnt post or copy someone elses instructions that are wrong.
shark2003 said:
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
Sorry I think I messed up some steps. I used the same method for new Tab S7
arjun_m4 said:
Sorry I think I messed up some steps. I used the same method for new Tab S7
Click to expand...
Click to collapse
Yeah I tried the AP and wiped out my os quite a few times until I got this right. It wasn't just your post its all over the internet and none of them mention that it has to be done in that order.
shark2003 said:
Change img file to .tar first
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
I might add, that this is probably a false positive information
Just because I had the same errors over and over, until I stumbled upon another thing: Creating the .tar was my problem. Using an (old) 7-Zip created a boot.tar which gave me "unassigned file" errors. When patching the whole AP, I got vbmeta errors.
So I started from scratch with a fresh Odin flash and transferred the boot.img.lz4 to my phone and worked with ZArchiver which extracted the .img and created the .tar - and this was flashed with Odin without any errors, finally.
PATCHED VBMETA.IMG for MERLIN by VD171
For what do I need it ?
If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once only. Once flashed, you don't need to flash vbmeta again.
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (Engineering) AL2522-Merlin-V039-Q-0513
- (Engineering) AL2522-Merlin-V044-Q-0920
- V12.5.1.0.RJOMIXM
- V12.0.1.0.RJOMIXM
- V12.0.8.0.QJOMIXM
- V12.0.7.0.QJOMIXM
- V12.0.6.0.QJOMIXM
- V12.0.5.0.QJOMIXM
- V12.0.4.0.QJOMIXM
- V12.0.3.0.QJOMIXM
- V11.0.5.0.QJOMIXM
- V11.0.4.0.QJOMIXM
How to flash it?
Code:
fastboot flash vbmeta vbmeta_vd171.img
MD5 hashes:
AL2522-Merlin-V039-Q-0513: ca9ccb577b5a1efd348949f9ed99409f
AL2522-Merlin-V044-Q-0920: dccbc87dbedc7f758120feac72e6c6cf
V12.5.1.0.RJOMIXM: 9d052f5fd4a7df3b5ad39c07b9330d75
V12.0.1.0.RJOMIXM: 9d052f5fd4a7df3b5ad39c07b9330d75
V12.0.8.0.QJOMIXM: 4a59b0481aa2a3bd5381fd51d2da3184
V12.0.7.0.QJOMIXM: 64fa528e39ebcd4838b92d5b120b0035
V12.0.6.0.QJOMIXM: 974e9c3462b4346a70ff370f6c28527b
V12.0.5.0.QJOMIXM: 7c68fe2373188e20abd4f1c68cb949b1
V12.0.4.0.QJOMIXM: 39ef5250fd562e20b6530cf8a0a96943
V12.0.3.0.QJOMIXM: 13c896c8dc4924bed5b63673a0a38a1a
V11.0.5.0.QJOMIXM: 2323b64102370a98f1641bc4d8227c52
V11.0.4.0.QJOMIXM: 666c0fbbd4d329001290277fcfd052d8
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Hi Broather , help me patched boot + vbmeta for this rom . I want to root it but after flash patched boot and disable vbmeta my devices hang on logo
https://bigota.d.miui.com/V12.5.3.0...JCNXM_20210429.0000.00_11.0_cn_1084bb7a7f.tgz
- Boot : https://drive.google.com/file/d/12Ne1FYZL_Mn9K2KP-VwHqO3Z3ACLti62/view?usp=sharing
- Vbmeta : https://drive.google.com/file/d/1LX7fbupDePK4aRY2CYZyRNmS4uf_BOZe/view?usp=sharing
thank so much
@VD171
empty.cad said:
Hi Broather , help me patched boot + vbmeta for this rom . I want to root it but after flash patched boot and disable vbmeta my devices hang on logo
https://bigota.d.miui.com/V12.5.3.0...JCNXM_20210429.0000.00_11.0_cn_1084bb7a7f.tgz
- Boot : https://drive.google.com/file/d/12Ne1FYZL_Mn9K2KP-VwHqO3Z3ACLti62/view?usp=sharing
- Vbmeta : https://drive.google.com/file/d/1LX7fbupDePK4aRY2CYZyRNmS4uf_BOZe/view?usp=sharing
thank so much
@VD171
Click to expand...
Click to collapse
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. (Attention: TAR and NOT tgz. You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file and wait until it finish.
6. Open the folder "Downloads" and uncompress the file magisk_patched.tar to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img. (You need to flash patched vbmeta because vbmeta verifies if any partition was changed.)
Done, you got patched boot.img and patched vbmeta.img files.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
VD171 said:
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. ( You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file.
6. Open the folder "Downloads" and extract the magisk_patched.TAR to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img.
Done.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
Click to expand...
Click to collapse
Thank broather
VD171 said:
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. ( You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file.
6. Open the folder "Downloads" and extract the magisk_patched.TAR to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img.
Done.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
Click to expand...
Click to collapse
Thank broather , but my devices still hang on logo after flash patched boot and patched vbmeta . Too dificult to root it
empty.cad said:
Thank broather , but my devices still hang on logo after flash patched boot and patched vbmeta . Too dificult to root it
Click to expand...
Click to collapse
Did you unlock the bootloader?
The patched boot and patched vbmeta are enough to root it, but it requires unlocked bootloader.
Hey bro, can you help me root this device. My device is unlocked but none of the fastboot commands work , it just freezes and doesnt move ahead at all.
bismeet said:
Hey bro, can you help me root this device. My device is unlocked but none of the fastboot commands work , it just freezes and doesnt move ahead at all.
Click to expand...
Click to collapse
Try to flash the whole MIUI again and try to root again following properly the steps.
VD171 said:
Try to flash the whole MIUI again and try to root again following properly the steps.
Click to expand...
Click to collapse
Well, i havent changed anything really except the bootloader unlock so I dont understand why that should be the case.
bismeet said:
Well, i havent changed anything really except the bootloader unlock so I dont understand why that should be the case.
Click to expand...
Click to collapse
Did you mean the device froze at fastboot or boot?
Did you try USB 2.0 or USB 3.0 ?
Did you try other usb ports and other usb cables?
VD171 said:
Did you mean the device froze at fastboot or boot?
Did you try USB 2.0 or USB 3.0 ?
Did you try other usb ports and other usb cables?
Click to expand...
Click to collapse
The device isnt frozen. The commands freeze and dont do anything. fastboot devices works but other commands do not do anything. Yes, I tried both 2.0 and 3.0.
bismeet said:
The device isnt frozen. The commands freeze and dont do anything. fastboot devices works but other commands do not do anything. Yes, I tried both 2.0 and 3.0.
Click to expand...
Click to collapse
I know. You need keep trying other usb ports and usb cables.
VD171 said:
I know. You need keep trying other usb ports and usb cables.
Click to expand...
Click to collapse
Tried all. Guess I need to add new ports to my phones and laptops.
bismeet said:
Tried all. Guess I need to add new ports to my phones and laptops.
Click to expand...
Click to collapse
If you can, try in another computer too.
I had same problem with USB 2.0 and everything is fine now with USB 3.0.
VD171 said:
If you can, try in another computer too.
I had same problem with USB 2.0 and everything is fine now with USB 3.0.
Click to expand...
Click to collapse
Okay.
I guess this phone is not rootable.
Never buying mtk device again.
bismeet said:
Okay.
I guess this phone is not rootable.
Never buying mtk device again.
Click to expand...
Click to collapse
What is your device?
VD171 said:
What is your device?
Click to expand...
Click to collapse
Redmi note 9 mtk version from India/
bismeet said:
Redmi note 9 mtk version from India/
Click to expand...
Click to collapse
Everyone has already rooted it.
VD171 said:
You can patch BOOT + VBMETA using the magisk app !
Yes, magisk app will patch VBMETA too !
Just follow this:
1. Download the full stock rom.
2. Extract these two files: boot.img and vbmeta.img.
3. COMPRESS those two files to TAR. ( You can use 7-Zip: https://7-zip.org )
4. Open the magisk app and click on "install to file".
5. Select the COMPRESSED TAR file.
6. Open the folder "Downloads" and extract the magisk_patched.TAR to get the patched boot.img and the patched vbmeta.img.
7. Flash the patched boot.img and the patched vbmeta.img.
Done.
Warning: magisk app will ignore if you try to patch ONLY the vbmeta.img, you need to patch vbmeta.img together boot.img compressed in only one file.
Click to expand...
Click to collapse
Thank you so much for this guide bro!
I tried the same on my OPPO, but with Bootloader locked and flashed through SP Flash Tool. My phone detects a patched vbmeta (coz I tested flashing the patched vbmeta alone.)
llxxVENOMxxll said:
Thank you so much for this guide bro!
I tried the same on my OPPO, but with Bootloader locked and flashed through SP Flash Tool. My phone detects a patched vbmeta (coz I tested flashing the patched vbmeta alone.)
Click to expand...
Click to collapse
Yes, you can't flash patched vbmeta while bootloader is locked.
You need to unlock bootloader first if you want to apply any change to any partition.
Hi,
I'm trying to flash Samsung Galaxy A8s (SM-G8870) with plain AOSP GSI. When I retrieve the ROM from https://samfw.com/firmware/SM-G8870/TGY/G8870ZHU5CUA1 I realized that there are no vbmeta.img file inside. Inside it, there is the AP file, as usual. It consists only of these files:
meta-data
boot.img.lz4
persist.img.ext4.lz4
recovery.img.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vendor.img.ext4.lz4
Click to expand...
Click to collapse
When I tried to add vbmeta and re pack AP file and flash it using Odin, Odin throws Unassigned file error, which I think is due to newly added vbmeta.img. When I tried to flash the image without vbmeta.img, Odin completes successfully, but the phone then stuck in Download mode (every time it reboots, it returns to Download mode). This is the image that I use: https://github.com/phhusson/treble_...nload/v222/system-quack-arm64-ab-gapps.img.xz
I also tried Android GSI from official Android page, but get a write error when copying system.img.ext4. Can somebody help me? Is vbmeta.img is really needed? If so, why does the original firmware does not include one? This phone was released in 2018 with Android 10 preinstalled.
I already have this phone OEM unlocked, it is ON in developer options. I am not using TWRP. I also left bootloader file as is (I only repacked the AP file), as I do not need root.
AFAIK the AOSP GSI doesn't include a verify boot solution (such as AVB 1.0 or AVB 2.0 ).
Look also inside here:
Generic system images | Android Open Source Project
source.android.com
jwoegerbauer said:
AFAIK the AOSP GSI doesn't include a verify boot solution (such as AVB 1.0 or AVB 2.0 ).
Look also inside here:
Generic system images | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Can you explain more? Does that means Samsung A8s has verified boot and cannot be turn off? Or it does not have verified boot at all thus no vbmeta at all?
after the latest apdate 13.0.3 i lose my magisk
and when i want to install it using adb it gives me a boot loop and i shoold to flash the original boot.img
Nb : ramdisk yes
Uninstall it thn flash it using Twrp
twrp can't read internal storage
but when i use the memory card then i click install the recovery restart directly
also by using adb the installation fail in 3%
souhail39 said:
twrp can't read internal storage
but when i use the memory card then i click install the recovery restart directly
also by using adb the installation fail in 3%
Click to expand...
Click to collapse
First flash the original boot image into your phone and make sure your phone can boot after you flash the original boot image.
fastboot flash Magisk-patched-boot.img
Patched boot image can be made on another phone.
https://forum.xda-developers.com/t/4288121/post-85137963
pl1992aw said:
First flash the original boot image into your phone and make sure your phone can boot after you flash the original boot image.
fastboot flash Magisk-patched-boot.img
Patched boot image can be made on another phone.
https://forum.xda-developers.com/t/4288121/post-85137963
Click to expand...
Click to collapse
This is what i did
The original boot run finely but the patched one give me a boot loop
Miui 13 doesn't support yet unless you patch the boot img. Just revert to 12.5.9
souhail39 said:
This is what i did
The original boot run finely but the patched one give me a boot loop
Click to expand...
Click to collapse
The safe way is to not flash boot image with TWRP or Orangefox custom recoveries. Flash with fastboot mode with PC is better to prevent issue.
What version of Magisk?
If you are using the latest Magisk v24.X but it bootloop, you may report issue to Magisk author in his github.
If you used Magisk v23, it is said not working on Android 12, so will not work on MIUI 13.
1. Download stock MIUI rom.
2. Extract two files: boot.img and vbmeta.img.
3. Compress the two files to a TAR file, like: boot_and_vbmeta.tar
4. Copy the TAR file to the device.
5. Open magisk app.
6. Choose "Install magisk to file" and select the TAR file. It will create the file magisk_patched.tar
7. Copy the magisk_patched.tar file to the PC.
8. Extract magisk_patched.tar to get boot_patched.img and vbmeta_patched.img
9. Enter in fastboot in device.
10. Flash boot_patched.img and vbmeta_patched.img to the device:
Code:
fastboot flash boot boot_patched.img
fastboot flash vbmeta vbmeta_patched.img
VD171 said:
1. Download stock MIUI rom.
2. Extract two files: boot.img and vbmeta.img.
3. Compress the two files to a TAR file, like: boot_and_vbmeta.tar
4. Copy the TAR file to the device.
5. Open magisk app.
6. Choose "Install magisk to file" and select the TAR file. It will create the file magisk_patched.tar
7. Copy the magisk_patched.tar file to the PC.
8. Extract magisk_patched.tar to get boot_patched.img and vbmeta_patched.img
9. Enter in fastboot in device.
10. Flash boot_patched.img and vbmeta_patched.img to the device:
Code:
fastboot flash boot boot_patched.img
fastboot flash vbmeta vbmeta_patched.img
Click to expand...
Click to collapse
thx for your answer but always the same problem with patched img files