Anyone have a root method for the BLU V50? Thanks in advance
Look inside here:
Root Spreadtrum Devices via Magisk Patched boot.img
This guide will show you the steps to root your Spreadtrum device via Magisk patched boot.img file, which we will extract from PAC firmware.
www.droidwin.com
jwoegerbauer said:
Look inside here:
Root Spreadtrum Devices via Magisk Patched boot.img
This guide will show you the steps to root your Spreadtrum device via Magisk patched boot.img file, which we will extract from PAC firmware.
www.droidwin.com
Click to expand...
Click to collapse
jwoegerbauer said:
Look inside here:
Root Spreadtrum Devices via Magisk Patched boot.img
This guide will show you the steps to root your Spreadtrum device via Magisk patched boot.img file, which we will extract from PAC firmware.
www.droidwin.com
Click to expand...
Click to collapse
I managed to find a way. Lol I'm just going to have to squeeze the old brain to to get this done it looks like. Thanks for the tip. The methods provided all require a system dump of stock firmware to patch TWRP for the phones recovery partition. I may have to cross my fingers and flash the generic unofficial boot image TWRP for android 10 and hope it fits lol. There are absolutely no custom fits at the moment. Of course I accepted the security patch update which made this a bit more tricky. QP1A.190711.020. I found a thread talking about almost the same update except it was two digits more than the version I got. It's been 6 or 7 years since I stopped theming for the galaxy s3. Course I was only changing xmls and pngs for custom roms back then. None of my old team are active anymore. Team Venum and team nOObz are long history. I even lost my log in info for my old profile. Anyways. Wish me luck. I'm going to learn how to port and develope this time around.
jwoegerbauer said:
Look inside here:
Root Spreadtrum Devices via Magisk Patched boot.img
This guide will show you the steps to root your Spreadtrum device via Magisk patched boot.img file, which we will extract from PAC firmware.
www.droidwin.com
Click to expand...
Click to collapse
Hello. Thanks again in advance. I've tried several command prompt methods to unlock this boot loader with no luck including the Magisk method. I have however managed to patch the TWRP file.
jwoegerbauer said:
Look inside here:
Root Spreadtrum Devices via Magisk Patched boot.img
This guide will show you the steps to root your Spreadtrum device via Magisk patched boot.img file, which we will extract from PAC firmware.
www.droidwin.com
Click to expand...
Click to collapse
I managed to patch the TWRP boot image using the Magisk apk and patch tools but I have no luck unlocking the boot loader..
1. find your firmware file by searching this forum for blu stock firmware repository
2. extract your boot/recovery img file using spd flash tool
3. patch img file with magisk, re-sign it with avbtools
4. patch vbmeta file with avbtools
5. re-flash both vbmeta and boot/recovery using spd research tool
rooted my blu advance l5 with these steps learned from hovatek. ymmv
luridphantom said:
1. find your firmware file by searching this forum for blu stock firmware repository
2. extract your boot/recovery img file using spd flash tool
3. patch img file with magisk, re-sign it with avbtools
4. patch vbmeta file with avbtools
5. re-flash both vbmeta and boot/recovery using spd research tool
rooted my blu advance l5 with these steps learned from hovatek. ymmv
Click to expand...
Click to collapse
Can anyone quickly tell me the easiest way to brick this device? My wife will buy me a new phone "when this one stops working"
Did anyone manage to root this device without bricking it? Firmware is not available in the Blu Repo (at least not yet). Our team would love to find a workable method for this phone. We have access to a bunch and want to be able to run Linux Deploy on them and also write app to automatically reboot the phone if the network connectivity is loss.
Hey, I was able to figure out how to deal with this bootloader stuff after many hours of work
Give this thread a look, it pretty much details every step needed to unlock the bootloader: https://forum.hovatek.com/thread-32287.html
Keep in mind that the OP of that thread is using a way older version of fastboot. For me, r26.0.1 worked best:
Windows: https://dl.google.com/android/repository/platform-tools_r26.0.1-windows.zip
Mac: https://dl.google.com/android/repository/platform-tools_r26.0.1-darwin.zip
Linux: https://dl.google.com/android/repository/platform-tools_r26.0.1-linux.zip
The above step is essential as newer versions of fastboot do NOT have the "fastboot flashing unlock_bootloader <bin>" step
again YMMV, but good luck
Me again, 6 hrs after the fact
Trial and Error enabled root on the V50 - follow these steps
1. Unlock bootloader as above
2. Create a custom signed vbmeta https://forum.hovatek.com/thread-32664.html (I used the same .pem from https://forum.hovatek.com/thread-32287.html to do this) - Make sure the VBMETA IS ANDROID 10 despite G0350WW firmware saying it's Android 9
3. Create custom boot with magisk (plenty of instructions to do this online, go with the github instructions)
4. Sign the custom magisk boot with THE SAME PUB KEY FROM STEP 2
5. Flash your new vbmeta and boot onto your phone via fastboot
6. Reboot, hope and pray it turns on
This is what worked for me, but again YMMV.
njoaquin said:
Me again, 6 hrs after the fact
Trial and Error enabled root on the V50 - follow these steps
1. Unlock bootloader as above
2. Create a custom signed vbmeta https://forum.hovatek.com/thread-32664.html (I used the same .pem from https://forum.hovatek.com/thread-32287.html to do this) - Make sure the VBMETA IS ANDROID 10 despite G0350WW firmware saying it's Android 9
3. Create custom boot with magisk (plenty of instructions to do this online, go with the github instructions)
4. Sign the custom magisk boot with THE SAME PUB KEY FROM STEP 2
5. Flash your new vbmeta and boot onto your phone via fastboot
6. Reboot, hope and pray it turns on
This is what worked for me, but again YMMV.
Click to expand...
Click to collapse
to be clear, the v50 uses the same firmware as the g50 plus?
dtingley11222 said:
to be clear, the v50 uses the same firmware as the g50 plus?
Click to expand...
Click to collapse
Correct, you can see it when you go to the firmware details of the v50 itself. You can get the firmware files when you search this forum for blu stock firmware repository
V50 is essentially a re-wrapped g50
njoaquin said:
Correct, you can see it when you go to the firmware details of the v50 itself. You can get the firmware files when you search this forum for blu stock firmware repository
V50 is essentially a re-wrapped g50
Click to expand...
Click to collapse
Hey, is there any way you could get me a rooted image and signed vbmeta? I have all the information that you would need, I just can't do the steps because im stupid. I would pay you to do it if you wanted
If the BLU V50 uses the same stock rom as the blu g50, if someone were to give out their patched vb meta and boot img, wouldn't it work for anyones BLU V50 if they just flashed it?
dtingley11222 said:
If the BLU V50 uses the same stock rom as the blu g50, if someone were to give out their patched vb meta and boot img, wouldn't it work for anyones BLU V50 if they just flashed it?
Click to expand...
Click to collapse
you need to patch recovery flash it back using the spreadtrum research tool and use the key combo to boot into root
luridphantom said:
you need to patch recovery flash it back using the spreadtrum research tool and use the key combo to boot into root
Click to expand...
Click to collapse
If I unlock the Bootloader, could I just flash it back with Fastboot?
Just tried flashing recovery and it bricked my phone
dtingley11222 said:
If I unlock the Bootloader, could I just flash it back with Fastboot?
Click to expand...
Click to collapse
you cant unlock the bootloader. follow this tutorial or you'll keep bricking your v50
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your p
forum.hovatek.com
luridphantom said:
you cant unlock the bootloader. follow this tutorial or you'll keep bricking your v50
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your p
forum.hovatek.com
Click to expand...
Click to collapse
Actually you can unlock the Bootloader. I already did. I don't know how to follow that tutorial. If I gave you my boot and vbmeta could you do it for me?
https://drive.google.com/file/d/1q1vt6f6-0Wg6iF4prOJS2o9ZauWM4qNy/view?usp=sharing : vbmeta
https://drive.google.com/file/d/1gEV2jxhnmmjKuUaqVhqPnH9oZNmzZBGi/view?usp=sharing : boot
dtingley11222 said:
Actually you can unlock the Bootloader. I already did. I don't know how to follow that tutorial. If I gave you my boot and vbmeta could you do it for me?
Click to expand...
Click to collapse
oh weird i thought blu doesnt even support bootloader unlocking
can you access fastboot? with an unlocked bootloader you can flash an empty vbmeta and dont have to go through the above steps
Related
WARNING:
Please do every preparation that could fix your phone to original state before doing this trick.
DOING THIS MAY VOID YOUR WARRANTY, DO IT AT YOUR OWN RISK
I managed to unpack the official firmware of Nokia 7 and 8, and patched their boot.img with SuperSU Systemless Root.
But I don't know if it works on them.
Patched boot.img can be downloaded at:
https://mega.nz/#F!igsBmarT!3rIjD4ZaZN8ueOTVmciGwg
Here's the method you need to do:
1. Install OST LA and patch it, and OPEN IT FROM INSTALLATION DIRECTORY DIRECTLY.
2. Flash required firmware before proceed. If you don't do that, you won't be able to access Wi-Fi after the boot.img flashed.
For Nokia 7, you need to use the firmware "C1N-0430-0-00CN-B05" which I haven't released to public for some reason.
For Nokia 8, you need to use the firmware "NB1-435J-0-00WW-B01" which released in this topic: https://forum.xda-developers.com/showthread.php?t=3678487
If you've already flashed required firmware before proceed, you can skip this part.
Click to expand...
Click to collapse
3. Use the Service Purposed Bootloader trick I've mentioned in the Nokia 6 Root Guide: https://forum.xda-developers.com/showthread.php?t=3702354
4. Type these commands:
Code:
fastboot-android flash boot_a E:\NB1-435J-Boot-Patched.img
fastboot-android flash boot_b E:\NB1-435J-Boot-Patched.img
fastboot-android reboot
For Nokia 7, use C1N-0430-Boot-Patched.img instead. I've attached the Firehose, rawprogram0 and patch0 for Nokia 7 in case you want to use EDL Mode on Nokia 7.
Click to expand...
Click to collapse
5. If it's accepted by the system, the phone will reboot twice, and you'll see SuperSU appeared.
However, if "Verification Failed" appeared on your phone, then the trick failed. You have to flash original firmware to restore your phone to factory state.
If anyone know how to fix that in boot.img, that's a breakthrough of Nokia Android Devices.
You may want to use Flashfire to flash Xposed Framework or something else, but DO NOT RECEIVE ANY OTA UPDATES after your phone rooted.
I'm looking forward to a boot.img manual patcher on PC or Phone available, which could patch boot.img to achieve Systemless Root either SuperSU or Magisk and bypass Verification Boot.
This looks exciting. I have to look deeper into recovery options before I dare this kind of experiment...
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Update: Can't install 4390 even when I download the update multiple times. Flashed 435J using OST and tried flashing the kernel again but still no root.
ansonscleung said:
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Click to expand...
Click to collapse
Thanks for feedback.
I'll check if anything wrong.
Can you check if you can install SuperSU manually from Google Play?
After you installed it, is root available?
hikari_calyx said:
Thanks for feedback.
I'll check if anything wrong.
Can you check if you can install SuperSU manually from Google Play?
After you installed it, is root available?
Click to expand...
Click to collapse
Nope. SuperSU said "Root not available"
Many thanks for your efforts on this patch, I would love to be able to root my Nokia 8.
Having an unlocked bootloader I am not really worried about, but having root access is a big feature for me.
Any chance this patch will become available to firmware version 00WW_4_390 which is the current latest? (And what my phone is currently running)
Not sure if I can downgrade it to NB1-435J-0-00WW-B01 or not, but I can try that if it is not able to be patched to the latest firmware image.
Thnx hikari_calyx for your hard work!
ansonscleung said:
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Update: Can't install 4390 even when I download the update multiple times. Flashed 435J using OST and tried flashing the kernel again but still no root.
Click to expand...
Click to collapse
Did anyone else but ansoncleung tried this meanwhile?
@hikari_calyx I have a self prepatched boot. IMG for TA1012, flashed via fastboot now I have root with Magisk, but WLAN won't work.
Powered by Nokia 8
2WildFirE said:
@hikari_calyx I have a prepatched boot. IMG for TA1012, flashed via fastboot now I have root with Magisk, but WLAN won't work.
Powered by Nokia 8
Click to expand...
Click to collapse
Log
Op please pm me i am developer too we can do this together.
TheKsM said:
Op please pm me i am developer too we can do this together.
Click to expand...
Click to collapse
Hey we need developers here on Nokia!
And what we need to is a dev who build twrp for Nokia8. The recovery is inside the boot. IMG.
If you want build a one for the community. Thanks
Powered by Nokia 8
I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?
https://forum.xda-developers.com/showpost.php?p=79548858&postcount=6
I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.
ozfive said:
I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?
Click to expand...
Click to collapse
1)Download payload dumper.
2)Extract payload file from rom zip.
3)Put payload file in payload_input folder.
4)Run exe file.
5)After process complete check payload_output folder. All extracted there.
Download payload dumper from here :- https://forum.xda-developers.com/attachment.php?attachmentid=4760222&d=1558078935
Patched boot images are irrelevant and only necessary for devices without a working TWRP recovery. If you want to root, either boot TWRP once or boot and install TWRP (recommended) and then install the magisk zip from there.
larsdennert said:
I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.
Click to expand...
Click to collapse
How do you extract the boot.img from the phone? I have the tmo version and would like to say on the stock room with root.
Sent from my GM1915 using Tapatalk
You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.
larsdennert said:
You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.
Click to expand...
Click to collapse
Not rooted yet, but everything I have read so far is that you need a patched boot.img to root, or you can create one from the boot.img in an oos package with magisk manager. The problem is, there isn't a tmo oos package out there yet, so it looks like rooting the tmo software isn't possible at the moment. Is this correct?
Sent from my SM-T550 using Tapatalk
Is your bootloader unlocked? That would be step one. Read up on the thread for that.
Not yet, but will be....trying to get my research done before I go for it... don't want to mess it up, been a few years since I rooted a phone.
Sent from my GM1915 using Tapatalk
Xiaomi Mi A2 Lite 11.0.18.0 / Magisk 21.4
or
Hi, big thanks for this. I'd rather patch the image myself, using a tutorial like this one – https://www.thecustomdroid.com/root-xiaomi-mi-a2-a2-lite-android-pie-magisk/. Where do you get the stock images?
Is this the right place? https://c.mi.com/oc/miuidownload/detail?guide=2 (search for "Mi A2 Lite")
Or this one? https://c.mi.com//miuidownload/detail?device=1700354
Thanks, I figured it out. The newest version can be downloaded at https://c.mi.com/oc/miuidownload/detail?guide=2, extract it using `tar xvzf daisy_global_images_V11.0.18.0.QDLMIXM_20210126.0000.00_10.0_286d778cee.tgz` on Linux and the boot.img is located in the images/ directory. Then you can follow the guide at https://www.thecustomdroid.com/root-xiaomi-mi-a2-a2-lite-android-pie-magisk/ to create the patched image and boot from it.
mariansam said:
Hi, big thanks for this. I'd rather patch the image myself, using a tutorial like this one – https://www.thecustomdroid.com/root-xiaomi-mi-a2-a2-lite-android-pie-magisk/. Where do you get the stock images?
Is this the right place? https://c.mi.com/oc/miuidownload/detail?guide=2 (search for "Mi A2 Lite")
Or this one? https://c.mi.com//miuidownload/detail?device=1700354
Click to expand...
Click to collapse
you can find updates here https://xiaomifirmwareupdater.com/miui/daisy/
depends how everyone uses to update his phone, but i always use fastboot file with xiaomiflash, it's only 2 clics and avoids me to care about uninstall magisk.
also the original boot.img is inside so just copy it on phone, magisk patch the file and then i fastboot boot the patched
hi! thanks for your work!
I've tried to update my phone, like I always do, restoring 11.0.17 boot stock image first, but I get an update error.
Any suggest?
u can try as i use to do, explained in message above
I tried but Xiaomi Flash doesn't work properly on my PC, I am afraid of losing data on phone.
Why am i unable to update after flashing stock boot image, like I always do??
Anyone having trouble?
hey guys!
I recently bought a phone name Micromax in2b. in my country this phone name is symphony z33. I want to root it. I tried every single methods I found on Google/xda/hovatek. By mygisk method my phone got bootloop!
I tried my best! but I can't root it!
so I need help of any expert developers!
I can provide you any type of files!
please can anyone help me?
Thanks in advance!
Basic Information- It's cpu is Unisoc T610
so many phones
use this soc!
so
we need this soc devolopment
Saifulsumaiya71 said:
hey guys!
I recently bought a phone name Micromax in2b. in my country this phone name is symphony z33. I want to root it. I tried every single methods I found on Google/xda/hovatek. By mygisk method my phone got bootloop!
I tried my best! but I can't root it!
so I need help of any expert developers!
I can provide you any type of files!
please can anyone help me?
Thanks in advance!
Basic Information- It's cpu is Unisoc T610
Click to expand...
Click to collapse
Hey... Have you been able to Root Your Device? If not I Can Help You Rooting. You can contact me over telegram using the user name @trippyadive
Saifulsumaiya71 said:
hey guys!
I recently bought a phone name Micromax in2b. in my country this phone name is symphony z33. I want to root it. I tried every single methods I found on Google/xda/hovatek. By mygisk method my phone got bootloop!
I tried my best! but I can't root it!
so I need help of any expert developers!
I can provide you any type of files!
please can anyone help me?
Thanks in advance!
Basic Information- It's cpu is Unisoc T610
Click to expand...
Click to collapse
Hey bro I am using In 2B as well you getting into bootloop make me feel u have bootloader oem unlock & at the same time you were trying to apply custom recovery & you got stuck in boot loop was that the case? Because in that case you will be needing a stock recovery with scatter file & sp flash tool.
Exactly same thing happened with me yesterday when I was trying to root my Micromax Canvas Tab p681 at evening i got into bootloop & till night I fix it by flashing stock recovery & reflashing custom from after factory reset but in my case my rom was stock & boot.img was stock only recovery file was messed up & I had stock recovery handy.
Before getting stuck in bootloop I had did below silly mistake:
1) perform oem unlock
2) flash recovery right after performing oem unlock
What actually happens after performing oem unlock (in lay man's language), when you perform oem unlock a factory reset is performed from your stock recovery, before performing factory reset bootloader verify previous version of recovery before booting to recovery. When you perform oem unlock you instruction bootloader to perform factory reset but when you flash custom recovery immediately after performing oem unlock (without allowing factory reset) your bootloader verify your previous recovery when it detect previous version is different than that of current version you end up in bootloop. Solution is to flash stock recovery via sp flash tool but your scatter file should be correct. There are step I can guide you.
I had been root my Android seens Android 1.6 I have plenty of experience with bootloops .
But before suggesting you any further & try anything out of desperation answer my questions point wise in detail:
1) What were you exactly doing when you stuck in bootloop?
2) Do you have stock recovery file?
3) From which site you downloaded your resources for flashing (link)
4) Does your hardware specs match with my hardware specifications attached?
Unisoc root is easy and there is no need to unlock the bootloader.
You need to sign boot.img if you have applied the Magisk patch and custom vbmeta.img, flash with SPD Research Tool.
straightcore said:
Unisoc root is easy and there is no need to unlock the bootloader.
You need to sign boot.img if you have applied the Magisk patch and custom vbmeta.img, flash with SPD Research Tool.
Click to expand...
Click to collapse
satanic666 said:
plenty of experience with bootloops .
But before suggesting you any further & try anything out of desperation answer my questions point wise in detail:
1) What were you exactly doing when you stuck in bootloop?
2) Do you have stock recovery file?
3) From which site you downloaded your resources for flashing (link)
4) Does your hardware specs match with my hardware specifications attached?
Click to expand...
Click to collapse
Hey my device is also Micromax in 2b...I have rooted the device and flashed a gsi.. but there is a problem I have tried almost 4-5 gsi ROM but 3.5mm headset it's not getting detected like when I plug-in the headset sounds not coming from the headset but coming from phone speaker did you also faced this issue if yes, do you have a solution?
Crayon Shin-chan said:
Hey my device is also Micromax in 2b...I have rooted the device and flashed a gsi.. but there is a problem I have tried almost 4-5 gsi ROM but 3.5mm headset it's not getting detected like when I plug-in the headset sounds not coming from the headset but coming from phone speaker did you also faced this issue if yes, do you have a solution?
Click to expand...
Click to collapse
Hey I'm also using Micromax in 2b. I tried to root my device by flashing patched magisk boot.img via fastboot but I'm unable to root my device it was saying 'read write error' can you tell me the perfect method to root my Micromax in2b?
Praveen999 said:
Hey I'm also using Micromax in 2b. I tried to root my device by flashing patched magisk boot.img via fastboot but I'm unable to root my device it was saying 'read write error' can you tell me the perfect method to root my Micromax in2b?
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
Did I boot into fastboot "adb reboot-fastboot" or bootloader "adb reboot-bootloader" ?
You need to flash in fastbootd, not bootloader.
If you sign magisk patched boot.img and create a signed custom vbmeta, you can flash via the SPD Research Tool without an unlocked bootloader.
straightcore said:
Do you have an unlocked bootloader?
Did I boot into fastboot "adb reboot-fastboot" or bootloader "adb reboot-bootloader" ?
You need to flash in fastbootd, not bootloader.
If you sign magisk patched boot.img and create a signed custom vbmeta, you can flash via the SPD Research Tool without an unlocked bootloader.
Click to expand...
Click to collapse
Thank you so much, now I find my mistake. I tried in bootloader
straightcore said:
Do you have an unlocked bootloader?
Did I boot into fastboot "adb reboot-fastboot" or bootloader "adb reboot-bootloader" ?
You need to flash in fastbootd, not bootloader.
If you sign magisk patched boot.img and create a signed custom vbmeta, you can flash via the SPD Research Tool without an unlocked bootloader.
Click to expand...
Click to collapse
Can u show me how to create a signed custom vbmeta
How to extract public keys from a vbmeta image
How to extract public keys from a vbmeta image
This is a step by step guide showing how to extract public signing keys from a vbmeta image. This will come handy if you plan to make a vbmeta image and still retain the public keys for certain partit
www.hovatek.com
How to create a custom signed vbmeta.img for Unisoc using AVBtool
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your p
www.hovatek.com
How to use AVBtool and a private key to sign a Unisoc (SPD) image
How to use AVBtool and a private key to sign a Unisoc (SPD) image
This guide will explain how to sign Unisoc / Spreadtrum (SPD) images (e.g boot, recovery, system etc) using a private key and AVBtool. This guide is ideal for those with vbmeta-sign.img in their firmw
www.hovatek.com
C
Crayon Shin-chan said:
Hey my device is also Micromax in 2b...I have rooted the device and flashed a gsi.. but there is a problem I have tried almost 4-5 gsi ROM but 3.5mm headset it's not getting detected like when I plug-in the headset sounds not coming from the headset but coming from phone speaker did you also faced this issue if yes, do you have a solution?
Click to expand...
Click to collapse
Can you tell me how to root that device? I'm also using same device but I'm unable to root my device.
Praveen999 said:
C
Can you tell me how to root that device? I'm also using same device but I'm unable to root my device.
Click to expand...
Click to collapse
Contact me on telegram. Mod edit: TG link removed as per XDA's TG Chat Rules.
boot.img magisk patched, signed
custom vbmeta, signed
"no unlock bootloader needed"
"Micromax/E7544/E7544:11/RP1A.201005.001/50:user/release-keys"
File on MEGA
mega.nz
straightcore said:
boot.img magisk patched, signed
custom vbmeta, signed
"no unlock bootloader needed"
Click to expand...
Click to collapse
This is old version man don't use it it's have some bugs and I used Canary version the file you gave link from hovatek https://www.hovatek.com/forum/thread-42955.html is mine ...it is my post
straightcore said:
boot.img magisk patched, signed
custom vbmeta, signed
"no unlock bootloader needed"
"Micromax/E7544/E7544:11/RP1A.201005.001/50:user/release-keys"
File on MEGA
mega.nz
Click to expand...
Click to collapse
You no need to worry I have sent him everything he needed to do his work
Canary:
File on MEGA
mega.nz
straightcore said:
Canary:
File on MEGA
mega.nz
Click to expand...
Click to collapse
Ohh are you Gargoyle? From hovatek?
Latest Magisk v25.0 Micromax IN 2b
File on MEGA
mega.nz
Changelog
Magisk Changelog
The Magic Mask for Android
topjohnwu.github.io
straightcore said:
Latest Magisk v25.0 Micromax IN 2b
File on MEGA
mega.nz
Changelog
Magisk Changelog
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
not working bro!
can u patch my boot.img and vbmeta ?
plz bro
https://drive.google.com/file/d/1cV3o3suLcq4TnfJrOMpaIwzd8vJTW0Ce/view?usp=drivesdk here is my files
Hello all, I have found a method for T-Mobile users to easily download boot.img files from your device with MSM Readback Mode so you no longer have to wait for TWRP to work for A12 or can stay on Stock OOS if you only want root. I will also include a pre-patched boot.img for those who just want to flash and not go through the whole process, as well as an unpatched boot.img for c.19 if you want to patch it yourself.
Open the MSMDownloadTool for the T-Mobile version.
Login with "other" per usual.
Press F8 to open the Readback Menu select whichever partitions you want to copy. (if you want to backup whole system or just "boot").
In the password field the password is "oneplus".
The copied partitions will go to the root of your "C" drive.
Your all done now. Just patch the image and reboot.
Stock C.19 Boot.img
Pre-Patched Magisk 25.2 C.19 Boot.img
Yeah last week I pulled my modem and persist via this method, but I wasn't sure if those partitions were valid files or not since all the comments I've seen they mention needing to use Partition Manager via root. Either way, no one responded and I received my unlock toke, so I ended up just rooting and using Partition Manager
centifanto said:
Yeah last week I pulled my modem and persist via this method, but I wasn't sure if those partitions were valid files or not since all the comments I've seen they mention needing to use Partition Manager via root. Either way, no one responded and I received my unlock toke, so I ended up just rooting and using Partition Manager
Click to expand...
Click to collapse
The files are valid, they’re direct backups from an official tool.
Thank you for the confirmation
EtherealRemnant said:
The files are valid, they’re direct backups from an official tool.
Click to expand...
Click to collapse
Thank you for the confirmation
Phoenix47 said:
Which msm tool did you use ?
Click to expand...
Click to collapse
OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool
Oxygen OS 11.2.22.2.LE54CB (T-Mobile) Download: https://drive.google.com/file/d/1-5RC9f8es6ZrwpYKKQBMmw5gW-rzDSfZ/view?usp=sharing Size: 2.92 GB MD5: b6fc004c81d311109f66cceb3f375862
forum.xda-developers.com
Can we use this on oneplus pro 9
Phoenix47 said:
@MrNRod can you please share modem.img from oos 12 c.19 ?
Click to expand...
Click to collapse
Yeah I can I am at work right now but when I get home I will backup and upload.
Phoenix47 said:
I am stuck on OOS 11.2.8.8 after using this msmtool. Not getting oos12 ota update.
Any fix ??
Click to expand...
Click to collapse
Have you tried wiping data from recovery. Factory restore and they trying to see if that will trigger update next boot.
MrNRod said:
Hello all, I have found a method for T-Mobile users to easily download boot.img files from your device with MSM Readback Mode so you no longer have to wait for TWRP to work for A12 or can stay on Stock OOS if you only want root. I will also include a pre-patched boot.img for those who just want to flash and not go through the whole process, as well as an unpatched boot.img for c.19 if you want to patch it yourself.
Open the MSMDownloadTool for the T-Mobile version.
Login with "other" per usual.
Press F8 to open the Readback Menu select whichever partitions you want to copy. (if you want to backup whole system or just "boot").
In the password field the password is "oneplus".
The copied partitions will go to the root of your "C" drive.
Your all done now. Just patch the image and reboot.
Stock C.19 Boot.img
Pre-Patched Magisk 25.2 C.19 Boot.img
Click to expand...
Click to collapse
Vedio link how to apply??
MrNRod said:
Hello all, I have found a method for T-Mobile users to easily download boot.img files from your device with MSM Readback Mode so you no longer have to wait for TWRP to work for A12 or can stay on Stock OOS if you only want root. I will also include a pre-patched boot.img for those who just want to flash and not go through the whole process, as well as an unpatched boot.img for c.19 if you want to patch it yourself.
Open the MSMDownloadTool for the T-Mobile version.
Login with "other" per usual.
Press F8 to open the Readback Menu select whichever partitions you want to copy. (if you want to backup whole system or just "boot").
In the password field the password is "oneplus".
The copied partitions will go to the root of your "C" drive.
Your all done now. Just patch the image and reboot.
Stock C.19 Boot.img
Pre-Patched Magisk 25.2 C.19 Boot.img
Click to expand...
Click to collapse
hello please the files ddoesn't exist pls send me the files
MrNRod said:
Hello all, I have found a method for T-Mobile users to easily download boot.img files from your device with MSM Readback Mode so you no longer have to wait for TWRP to work for A12 or can stay on Stock OOS if you only want root. I will also include a pre-patched boot.img for those who just want to flash and not go through the whole process, as well as an unpatched boot.img for c.19 if you want to patch it yourself.
Open the MSMDownloadTool for the T-Mobile version.
Login with "other" per usual.
Press F8 to open the Readback Menu select whichever partitions you want to copy. (if you want to backup whole system or just "boot").
In the password field the password is "oneplus".
The copied partitions will go to the root of your "C" drive.
Your all done now. Just patch the image and reboot.
Stock C.19 Boot.img
Pre-Patched Magisk 25.2 C.19 Boot.img
Click to expand...
Click to collapse
Hi , I would like to see how you back up your phone image. Also I want to backup modem. I have oneplus 9 Le2117 A12 with bootloader unlocked. I want to root it withot problem. updated to C.23
MrNRod said:
Hello all, I have found a method for T-Mobile users to easily download boot.img files from your device with MSM Readback Mode so you no longer have to wait for TWRP to work for A12 or can stay on Stock OOS if you only want root. I will also include a pre-patched boot.img for those who just want to flash and not go through the whole process, as well as an unpatched boot.img for c.19 if you want to patch it yourself.
Open the MSMDownloadTool for the T-Mobile version.
Login with "other" per usual.
Press F8 to open the Readback Menu select whichever partitions you want to copy. (if you want to backup whole system or just "boot").
In the password field the password is "oneplus".
The copied partitions will go to the root of your "C" drive.
Your all done now. Just patch the image and reboot.
Stock C.19 Boot.img
Pre-Patched Magisk 25.2 C.19 Boot.img
Click to expand...
Click to collapse
jfernandezv said:
...I have oneplus 9 Le2117 A12 with bootloader unlocked. I want to root it withot problem. updated to C.23
Click to expand...
Click to collapse
Pardon Me, but what does "C.23" refer to ?
barguybrady said:
Pardon Me, but what does "C.23" refer to ?
Click to expand...
Click to collapse
Try to say Software Version LE2117_11_C23. But now is LE2117_11_24.
I being reading about OnePlus 9 5G lot. But no one can explain in detail how to root it without risk. I understand a little when you say extract boot.img. But I need to see how you do that with MSM tool. Last time I follow this method I got lost because the MSM tool have already a frimware to flash and install. I can't use that boot.img version. For what I understand, I need to get same boot.img version my phone have. Am looking for LE2117_11_24 (software version) Of Android 12, but I can't find it anywhere. I can downgrade to Android 11 but I need a good guide or video that explain everything. I have windows 11 with MSM tool for OnePlus 9 5G. Qualcomm driver installed, USB driver, and Adb. My phone can be detected with Adb and fastboot, but when I put the phone on Edl mode, MSM tool do not find the phone. Edl only last for 10 sec and reboot. I check divice manager on windows 11 and Qualcomm driver is working. Any Idea or help will be good me. I just don't want to brick the phone. Thanks for answering my question.
jfernandezv said:
Try to say Software Version LE2117_11_C23. But now is LE2117_11_24.
I being reading about OnePlus 9 5G lot. But no one can explain in detail how to root it without risk. I understand a little when you say extract boot.img. But I need to see how you do that with MSM tool. Last time I follow this method I got lost because the MSM tool have already a frimware to flash and install. I can't use that boot.img version. For what I understand, I need to get same boot.img version my phone have. Am looking for LE2117_11_24 (software version) Of Android 12, but I can't find it anywhere. I can downgrade to Android 11 but I need a good guide or video that explain everything. I have windows 11 with MSM tool for OnePlus 9 5G. Qualcomm driver installed, USB driver, and Adb. My phone can be detected with Adb and fastboot, but when I put the phone on Edl mode, MSM tool do not find the phone. Edl only last for 10 sec and reboot. I check divice manager on windows 11 and Qualcomm driver is working. Any Idea or help will be good me. I just don't want to brick the phone. Thanks for answering my question.
Click to expand...
Click to collapse
What I've just learned over the past 2 days, with MSM and such:
Yes, EDL mode will only be active for about 10 seconds with the MSM Tool, so you must be prepared to hit the "Start" button as soon as you see the connection is Active;
When talking about extracting the "boot.img" , it is discussed in this Post:
safely-convert-regions-includes-t-mobile-as-well-as-restore-the-ability-to-use-oos12-after-using-indian-msm-to-recover-from-a-brick-windows-only.4460859/
if that's what you are looking to do...? I am no expert, myself...