Has anyone installed a custom rom successfully on a Moto G 5G model XT-2213-3?
The kiev build for Lineage 18.1 lists these variants as compatible:
Supported models
XT2113-2
XT2113-3
XT2113-5
This is the device's specs on GSM arena.
Moto G 5G (2022)
So apparently in moving from the 2020 kiev version to this phone, they replaced the qualcomm processor with a mediatek. Bad news for the custom rom future of it. It did easily bootloader unlock, so now I'm trying to see if root is a possibility.
Old_Mil said:
So apparently in moving from the 2020 kiev version to this phone, they replaced the qualcomm processor with a mediatek. Bad news for the custom rom future of it. It did easily bootloader unlock, so now I'm trying to see if root is a possibility.
Click to expand...
Click to collapse
Hello. Have you found any solution to root this device? I have the same model (2213-3 Austin), and unlocked the phone but could not root the device. No solution on the internet works for me.
enaykey said:
Hello. Have you found any solution to root this device? I have the same model (2213-3 Austin), and unlocked the phone but could not root the device. No solution on the internet works for me.
Click to expand...
Click to collapse
I was successfully able to root using this guide.
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
I've uploaded the patched boot.img for firmware G_S1SAS32.47_77_2 so you can save some time and skip step 1 and go straight to flashing the patched boot.img hope this helps.
I gave up on this handset as with it's Mediatek innards there won't be any future Custom ROM options.
traceroute87 said:
I was successfully able to root using this guide.
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
I've uploaded the patched boot.img so you can save some time and skip step 1 and go straight to flashing the patched boot.img hope this helps.
Click to expand...
Click to collapse
Oh thank you! I tried to do the same thing but i got an error each time. I'll try your boot.img
traceroute87 said:
I was successfully able to root using this guide.
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
I've uploaded the patched boot.img so you can save some time and skip step 1 and go straight to flashing the patched boot.img hope this helps.
Click to expand...
Click to collapse
I still get this error on fastboot:
sending 'boot' (40960 KB)...
OKAY [ 1.187s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 1.202s
enaykey said:
I still get this error on fastboot:
sending 'boot' (40960 KB)...
OKAY [ 1.187s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 1.202s
Click to expand...
Click to collapse
hmm.
try: fastboot flash boot_a boot.img
or: fastboot flash boot_b boot.img
traceroute87 said:
hmm.
try: fastboot flash boot_a boot.img
or: fastboot flash boot_b boot.img
Click to expand...
Click to collapse
Oh, it worked! Thank you so much. You saved my phone.
traceroute87 said:
I was successfully able to root using this guide.
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
I've uploaded the patched boot.img so you can save some time and skip step 1 and go straight to flashing the patched boot.img hope this helps.
Click to expand...
Click to collapse
This is awesome.
Would you happen to have a stock firmware for austin RETUS? I can't find one on lolinet.
slipchicken said:
This is awesome.
Would you happen to have a stock firmware for austin RETUS? I can't find one on lolinet.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmwar...RSU_QCOM_regulatory-DEFAULT_cid50_CFC.xml.zip
This is stock for XT2213-3
Old_Mil said:
I gave up on this handset as with it's Mediatek innards there won't be any future Custom ROM options.
Click to expand...
Click to collapse
I have a WIP lineage/aosp device tree up on github, still have a few small things to sort out on the device tree and probably another week or two away from a workable vendor tree. Motorola has released the source for the kernel along with the out of tree modules, currently trying to get them to release an aosp build readme since this is my first mediatek device and there isn't much info on porting roms to said soc, but there is always gsi's
damnthefall said:
https://mirrors.lolinet.com/firmwar...RSU_QCOM_regulatory-DEFAULT_cid50_CFC.xml.zip
This is stock for XT2213-3
Click to expand...
Click to collapse
Is this one valid for those that bought directly from Moto? It's stating subsidy for T-Mobile and not seeing a standard official release on lolinet . . .
zinjashike said:
Is this one valid for those that bought directly from Moto? It's stating subsidy for T-Mobile and not seeing a standard official release on lolinet . . .
Click to expand...
Click to collapse
This is just for the T-Mobile variant. The one bought directly from Moto has different specs IIRC
Okay, I thankfully remembered that one can get stock roms from Moto using the Rescue Smart Assistant so did that.
Now I'm just stuck waiting till Motorola tells me phone I can use the OEM Bootloader Unlock . . . so much for a fast upgrade >_<
zinjashike said:
Okay, I thankfully remembered that one can get stock roms from Moto using the Rescue Smart Assistant so did that.
Now I'm just stuck waiting till Motorola tells me phone I can use the OEM Bootloader Unlock . . . so much for a fast upgrade >_<
Click to expand...
Click to collapse
Mine only took like 24 hours before the option could be enabled. I just want to go back to a qcom soc because not having any bsp for this phone is killing me
damnthefall said:
Mine only took like 24 hours before the option could be enabled. I just want to go back to a qcom soc because not having any bsp for this phone is killing me
Click to expand...
Click to collapse
I'm not familiar, what is BSP?
Just want to make sure I'm not biting myself in the ass here keeping it. The only things I really need unlocked BL/root for is CF.Lumen, some tasker stuff, proper full backups, and call recording for work/business >_>
zinjashike said:
I'm not familiar, what is BSP?
Just want to make sure I'm not biting myself in the ass here keeping it. The only things I really need unlocked BL/root for is CF.Lumen, some tasker stuff, proper full backups, and call recording for work/business >_>
Click to expand...
Click to collapse
BSP=Board Support Package(makes custom ROM development much easier) you should be just fine doing the standard magisk root, it's what I did and I haven't had any issues with except that now whenever I reboot my phone it boots into Meta mode instead of back to system. So when I reboot I have to make sure to hold vol down to get the bootloader and then boot normally from there. I'm guessing it has something to do with verified boot because if I reflash the factory boot image it reboots normally, I tried flashing vbmeta with disable verity and verification, but after doing that the sim card reader stopped working lol
Anyone found a root for the moto g stylus 5G xt2131-1? Just purchased it factory unlocked.
Related
[ROOT] How to root with latest N firmware NPJ25.93-11 and NPJ25.93-14
Hello,
Because it seems that all previous root method don't work with this new release, here is a method with have be approved ok on XT6143.
Prerequisites:
- Unlocked bootloader
- Android debug enabled in dev options
- adb and fastboot usage
- Worked only on the NPJ25.93-11 or NPJ25.93-14build
> you can flash it with thoses tutos:
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Procedure:
- Download my file superboot-athene_NPJ25.93-11_eng-noverity.img
or superboot-athene_NPJ25.93-14_eng-noverity.img
on your PC
- Reboot your phone via combo key or adb into fastboot mode
Code:
adb reboot bootloader
- Boot the superboot with the command
Code:
fastboot boot superboot-athene_NPJ25.93-11_eng-noverity.img
or
Code:
fastboot boot superboot-athene_NPJ25.93-14_eng-noverity.img
- Go to Play Store, and install phh's SuperUser
- You should have root
Warning & attentions
- This is a temporary root, if you reboot your device, root will be lost (you have to boot the superboot img again)
- You can try to flash this superboot to get permanent root with
Code:
fastboot flash boot superboot-athene_NPJ25.93-11_eng-noverity.img
but it seems it doesn't work/the bootloader don't allow it on many variant
+1 booting the img file worked. Sadly flashing it didn't.
Hey guys, has anybody come up with a stable way of rooting the athene (Moto G4 Plus)? Wanna try the RR on it, but i am quite new to Motorola and the series of threads that i have read through doesn't actually give a specific guide to get done with it (seen many people ending up with a bootloop). And as i can see, there are not many posts on the latest NPJ25.93-11 build (i got my phone yesterday). Should i go with a guide and root it or wait some more time for a stable guide?
HawkEye said:
Hey guys, has anybody come up with a stable way of rooting the athene (Moto G4 Plus)? Wanna try the RR on it, but i am quite new to Motorola and the series of threads that i have read through doesn't actually give a specific guide to get done with it (seen many people ending up with a bootloop). And as i can see, there are not many posts on the latest NPJ25.93-11 build (i got my phone yesterday). Should i go with a guide and root it or wait some more time for a stable guide?
Click to expand...
Click to collapse
This is for last Nougat update, it's stable but you have to flash the root image every time you turn off you phone, it works like a temporal root.
champagne66601 said:
This is for last Nougat update, it's stable but you have to flash the root image every time you turn off you phone, it works like a temporal root.
Click to expand...
Click to collapse
Thanks for the reply. But can i install the Resurrection Remix ROM with a temporary root through flashify? as i understand with my little knowledge, it reboots to recovery to install the ROM and if the root is broken with that, does it affect the installation? I just don't want to end up with a fully bricked device on the second day xD so just making sure
HawkEye said:
Thanks for the reply. But can i install the Resurrection Remix ROM with a temporary root through flashify? as i understand with my little knowledge, it reboots to recovery to install the ROM and if the root is broken with that, does it affect the installation? I just don't want to end up with a fully bricked device on the second day xD so just making sure
Click to expand...
Click to collapse
Well you can try RR by flashing custom recovery (TWRP) . Root is not needed in that process.
I think waiting for stable version would be a better idea. Can you confirm about xposed on official Nougat, without xposed rooting is a waste for me?
srinivas_b said:
Well you can try RR by flashing custom recovery (TWRP) . Root is not needed in that process.
Click to expand...
Click to collapse
Just to confirm, i need to unlock bootloader to install TWRP and i can install RR directly.. and i don't need to root my phone to install a custom ROM?
EDIT: Googled, Figured it out *Feels Dumb* xD
---------- Post added at 12:30 PM ---------- Previous post was at 12:29 PM ----------
nice_guy75 said:
I think waiting for stable version would be a better idea. Can you confirm about xposed on official Nougat, without xposed rooting is a waste for me?
Click to expand...
Click to collapse
Currently, i just want to root my phone to install the resurrection remix rom.. if i don't need root for that, i might as well just skip the root part
EDIT: Googled, Figured it out *Feels Dumb* xD
HawkEye said:
Just to confirm, i need to unlock bootloader to install TWRP and i can install RR directly.. and i don't need to root my phone to install a custom ROM?
EDIT: Googled, Figured it out *Feels Dumb* xD
---------- Post added at 12:30 PM ---------- Previous post was at 12:29 PM ----------
Currently, i just want to root my phone to install the resurrection remix rom.. if i don't need root for that, i might as well just skip the root part
EDIT: Googled, Figured it out *Feels Dumb* xD
Click to expand...
Click to collapse
Yep need to unlock bootloader and install twrp. Unlocking it will erase data though.
Hi, does systemless magisk root work with the latest official build? I rooted the first soak test using this method.
Edit: Found answer elsewhere - causes bootloop for anyone wondering
FYI
How can I disable secure-mode from fastboot?
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot [B]flash[/B] boot superboot.img
target max-sparse-size: 256MB
sending 'boot' (12092 KB)...
OKAY [ 0.407s]
writing 'boot'...
FAILED (status read failed (Too many links))
finished. total time: 0.562s
Error 7
I've installed NPJ25.75-2 and now can't install this update from stock recovery.
Any suggestion how can I do so.......
Z-borg said:
I've installed NPJ25.75-2 and now can't install this update from stock recovery.
Any suggestion how can I do so.......
Click to expand...
Click to collapse
Flash the full firmware with fastboot
Can we flash it via twrp? Just a thought.
jyoti.id said:
Can we flash it via twrp? Just a thought.
Click to expand...
Click to collapse
I don't think you can
As Systemless Rooting modifies boot.img,
On stock boot.img it causes weird problem, so possible to root with Custom boot..?
I tried flashing Custom kernals available here, it cause bootloop, can you try making supported kernel for nougat and try root on it...?
I have no knowledge about how it works, it's just thought came in my mind...
titou4488 said:
Flash the full firmware with fastboot
Click to expand...
Click to collapse
Thanks but i'm not rooted also my OEM is still locked will it work......?
Z-borg said:
Thanks but i'm not rooted will it work......?
Click to expand...
Click to collapse
Yes. Follow this guidehttps://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
I used rsd lite, it works great.
titou4488 said:
Yes. Follow this guidehttps://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
I used rsd lite, it works great.
Click to expand...
Click to collapse
Thanks
Where do I find the new logo 7.0 in bin format? I want to remove the warning
This is a newest MIUI 9 China Beta "s TZ &Modem
Baseband:BO.2.6.c1.2-0818_1948_87b78d2
Link:https://yadi.sk/d/wdmLsruk3MSQJr
Flashable ZIP File
Please Use TWRP
more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: DO NOT flash this on official Lineage with Lollipop bootloader, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot which is also pretty useless, since your bootloader is locked
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (40704 KB)...
OKAY [ 1.343s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.362s
PeterMarkoff said:
more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: do not flash this on official Lineage, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Click to expand...
Click to collapse
kindly type, fastboot oem device-info on fastboot mode with phone pluged in,hope it didnt lock your bootloader.
yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data
PeterMarkoff said:
yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data
Click to expand...
Click to collapse
Have you unlocked your phone officially?
Because i flash this too and had no problem at all.
?
unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader
PeterMarkoff said:
unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader
Click to expand...
Click to collapse
YES,This is a Nougat Bootloader,you must unlock bootloader in official tools after you install this file in twrp
Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.
buktore said:
Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.
Click to expand...
Click to collapse
****ing ask before do something if you're not so sure about it.
Has anyone noticed any improvement with the new radio?
Hello. Has anyone got a link to the latest firmware available for a MI4C. I'm not after the official ROM, just firmware workable with ROMs. I think the last update I done was through andropax link https://androidfilehost.com/?w=files&flid=155424 is there a way I can also find out which firmware I have installed I forgot.
Is this the latest > https://androidfilehost.com/?fid=890278863836288705
fw_libra_miui_MI4c_V9.5.2.0.NXKCNFA_81f363e363_7.0
& will it run dev ROMs?
How to Flash Factory Firmware
Warning
You will loose all your data. Make sure to backup. You are doing this at your own risk. Neither me nor xda is responsible for any bricked devices.
Youtube Video :- https://www.youtube.com/watch?v=eCGB-yxC09w
Text Guide
HOW TO INSTALL STOCK ROM IN MOTO X4:
Download Moto X4 Stock Firmware from below (in factory firmwares section).
Extract factory firmware to a folder.
Install Motorola Driver and ADB Fastboot Driver on your PC.
Copy all contents of ADB fastboot folder and paste it in factory firmware folder.
Download flash-all.sh(Mac & Linux) or flash-all.bat (Windows)
Place flash-all.sh/flash-all.bat file in factory firmware folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt/terminal window, navigate to factory firmware folder.
Windows
Code:
fastboot devices
Mac & Linux
Code:
./fastboot devices
Make sure device is detected in fastboot mode.
Windows
Code:
flash-all.bat
Mac & Linux
Code:
./flash-all.sh
Once everything is flashed.
Windows
Code:
fastboot reboot
Mac & Linux
Code:
./fastboot reboot
Motorola Bootloader Unlock - https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Downloads
Motorola drivers for Windows & Mac :- https://support.motorola.com/us/en/drivers
Setup ADB and fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
flash-all.sh (Linux + Mac) - https://mega.nz/#!OYFiRKZC!2CjMLxpoEAqpFyB_q1Q1FncC9a1oNofh9Hjm99PwiGo
flash-all.bat (Windows) - https://mega.nz/#!DF1XwSjC!tkHhb9H9-1piNr1AbKaPJK_yLuv4rpIxw1AWicD1I94
Factory Firmwares
https://mirrors.lolinet.com/firmware/moto/payton/official/
US Retail Android 9.0 Pie :- https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Android One Android 9.0 Pie :- https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Twitter Account to Follow for latest firmware uploads
https://twitter.com/motofirmware123
you da man!
Your tutorials are very helpful .Thanks
When will you have the 28.2 firmware with the May update? Thats what version mine was on before I bricked it.
jpolster2005 said:
When will you have the 28.2 firmware with the May update? Thats what version mine was on before I bricked it.
Click to expand...
Click to collapse
you should be able to flash the latest firmware listed above as long as you can boot into fastboot.
but my locked boot loader says preflash validation failed
jpolster2005 said:
but my locked boot loader says preflash validation failed
Click to expand...
Click to collapse
unlock the bootloader.
I can't, because OEM UNLOCKING is set to off
Thanks for the simplified guide. Worked great, I was able to relock the bootloader and accept an OTA with no problem. Only issue is the device doesn't pass safety net - signature validation error, and when I boot up I get the device has been modified pop up.
michael28056 said:
Thanks for the simplified guide. Worked great, I was able to relock the bootloader and accept an OTA with no problem. Only issue is the device doesn't pass safety net - signature validation error, and when I boot up I get the device has been modified pop up.
Click to expand...
Click to collapse
rooted?
No -unrooted, stock rom from this thread, locked bootloader.
michael28056 said:
No -unrooted, stock rom from this thread, locked bootloader.
Click to expand...
Click to collapse
well, i never stay on stock long enough to check that ..sorry cant help with that.
guys PLEASE help me I have a $300 paperweight here. Best Buy wouldn't take it back so I NEED to get it fixed. I was already on the newest OTA when I bricked my phone on a locked boot loader, and when I try to flash 28.1 thru Fastboot, it says validation failed. is there anyone out there who has access to the Fastboot flashable 28.2? I need my phone back!
jpolster2005 said:
guys PLEASE help me I have a $300 paperweight here. Best Buy wouldn't take it back so I NEED to get it fixed. I was already on the newest OTA when I bricked my phone on a locked boot loader, and when I try to flash 28.1 thru Fastboot, it says validation failed. is there anyone out there who has access to the Fastboot flashable 28.2? I need my phone back!
Click to expand...
Click to collapse
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Neffy27 said:
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Click to expand...
Click to collapse
same peeps thread
aw man... well, I meant to post specifically to the last post in the thread but was on the mobile app.
:good::good: Just wanted to say thank you for this post, the links to the image files and the flash-all BAT file. This really saved my butt with a Project Fi Moto X4, which I had rooted using Magisk before checking on the availability of factory firmware images from Motorola. (of course there are not any available from Motorola ) The phone was continuously prompting for an OTA update, which would fail. I first tried the Magisk uninstaller, which ran successfully in TWRP, but the OTA update was still failing. After some digging on Google I found your post and used the Project Fi image to flash the phone, it worked perfectly! There was an OTA update available after flashing (The May 2018 security patches, "28.2") and it installed successfully. I love the Android community, the XDA community, and folks like yourself who take the time to write posts like this. Seriously, thank you!
g3m1n1 said:
I love the Android community, the XDA community, and folks like yourself who take the time to write posts like this. Seriously, thank you!
Click to expand...
Click to collapse
glad to be of help :highfive:
g3m1n1 said:
There was an OTA update available after flashing (The May 2018 security patches, "28.2") and it installed successfully.
Click to expand...
Click to collapse
Hello!
I understand you have Android One version. If that's the case, anyone catching the URL to OTA for the Android One 28.2 update? I've been looking for it for days, and the OTA link generator is not working (at least with the data I'm providing which should be correct).
Neffy27 said:
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Click to expand...
Click to collapse
how long before we see one. I have been relegated to using an iPhone 6 32GB! I really NEEEEEEED my phone to not be bricked. I tried to do the blank flash and boot off sd card and all that to no avail. none of it worked. meow I am getting so frustrated.
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
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