Hey guys,
Can someone post a step by step "for dummies" guide to flashing the stock unbranded firmware to over right the UK Tesco firmware?
I've already downloaded the unbranded UK RETAIL firmware and unlocked my phone to use in other networks, that's as far as I've got.
Not looking to root or anything else, just to apply the stock unbranded firmware so that I can get future updates from Motorola and not Tesco.
Thanks.
You need to unlock the bootloader, then either use RSD Lite or fastboot flash the images in the archive.
Give that, from the FAQ, the 'adb' access seems to work with the Moto G would the 'adb sideload' method not work? I assume this would avoid the need to unlock the bootloader.
Rusty! said:
You need to unlock the bootloader, then either use RSD Lite or fastboot flash the images in the archive.
Click to expand...
Click to collapse
Any chance for a step by step? And is this a confirmed working method?
Ydnaroo said:
Give that, from the FAQ, the 'adb' access seems to work with the Moto G would the 'adb sideload' method not work? I assume this would avoid the need to unlock the bootloader.
Click to expand...
Click to collapse
No. Sideload is for OTA updates. Completely different scenario.
Rusty! said:
No. Sideload is for OTA updates. Completely different scenario.
Click to expand...
Click to collapse
Ah! Of course. Brain fade here.
failed system.img when flashing unbranded stock
I have attempted to flash the stock unbranded firmware but am having no succes
The fastboot instructions given by Motorola website are as follows:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
Click to expand...
Click to collapse
Although I'm guessing that may be for the motox as the .xml included in the MotoG zip is as follows:
<?xml version="1.0"?>
-<flashing>-<header><phone_model model="QC8x26_CFC"/><software_version version="falcon_retgb-user 4.3 14.10.0Q3.X-76-LGG-8 54 release-keysMSM8626BP_1032.3051.51.00R"/><sparsing max-sparse-size="268435456" enabled="true"/>-<interfaces><interface name="AP"/></interfaces></header>-<steps interface="AP"><step MD5="173f47c2b411e291f8b0f512b8935190" filename="gpt.bin" partition="partition" operation="flash"/><step MD5="a2a1c181283543186f7ef069a9f63374" filename="motoboot.img" partition="motoboot" operation="flash"/><step MD5="187908e994f5b42710d13dbb5126d6d2" filename="logo.bin" partition="logo" operation="flash"/><step MD5="c99ebf47655a7609f10a8673ea229b72" filename="boot.img" partition="boot" operation="flash"/><step MD5="f79ca6436a8214fc7728dd927bd16898" filename="recovery.img" partition="recovery" operation="flash"/><step MD5="28ed691836a16e09be1edb7736086a49" filename="system.img_sparsechunk.0" partition="system" operation="flash"/><step MD5="9a188eb562f2abf336b66d1db53ab1f1" filename="system.img_sparsechunk.1" partition="system" operation="flash"/><step MD5="6a6ca5174610c48a855a7d16be75f948" filename="system.img_sparsechunk.2" partition="system" operation="flash"/><step MD5="b298426137783b6163fcda3621bed159" filename="NON-HLOS.bin" partition="modem" operation="flash"/><step partition="modemst1" operation="erase"/><step partition="modemst2" operation="erase"/><step MD5="73941708b28eb41f54b7c2326feec38a" filename="fsg.mbn" partition="fsg" operation="flash"/><step partition="cache" operation="erase"/><step partition="userdata" operation="erase"/></steps></flashing>
Click to expand...
Click to collapse
This seems to work via fastboot untill I get to the system.img files, they all fail when I try to flash them in order, or if I just try to flash one system.img as a whole.
I have also tried using the RSD tool, the phone is recognised when plugged in & booted up normally, after you select the .xml & click start it reboots to fastboot then can no longer see the device so the flash fails.
Unable to get the tool to see the phone if I manually reboot to fastboot first.
Any Ideas? Im guessing that manually flashing via fastboot is the only way, but cant get that 3 part system.img to install
>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.047s
Click to expand...
Click to collapse
Have you gone through the bootloader unlock process?
Rusty! said:
Have you gone through the bootloader unlock process?
Click to expand...
Click to collapse
Yes by following the steps on the Motorola website.
I have that annoying white warning screen now every time I reboot
How about adb sideload? Shouldnt it work just like on nexus devices? Just guessing, dont own the phone... Yet
Sent from my LG-P760 using xda app-developers app
N00BY0815 said:
How about adb sideload? Shouldnt it work just like on nexus devices? Just guessing, dont own the phone... Yet
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
Coming from a nexus, I thought that also, but I'm sure on another thread it is mentioned that ADB sideload only applies to OTA update files.
I tried pushing the whole zip to the phone but as expected it did nothing.
Fastboot flash should work but the bootloader won't give permission so something isn't right.
Although on the instructions from motorola website it says not to use android fastboot, but use RSD tool instead. I have 2 potential issus with that #1 the software itself hasn't been updated to support the MotoG or #2 it wont work with my 64bit copy of windows 7.
You need too bit the phone into BP Tools mode from fastboot for RSD Lite if you haven't been
Rusty! said:
You need too bit the phone into BP Tools mode from fastboot for RSD Lite if you haven't been
Click to expand...
Click to collapse
Yep, tried that the 1st time you posted it, still no luck.
I have noticed that after every reboot the usb debugging has switched itself off, could this be causing the permission problem?
Paul over at Modaco has created a root tool (says so on his twitter).
not sure if that will be any help in applying a stock Retrail rom on the Tesco phones. he also says RSD should work?
hope you guys can figure it out .
TeamKilo said:
Hey guys,
Can someone post a step by step "for dummies" guide to flashing the stock unbranded firmware to over right the UK Tesco firmware?
I've already downloaded the unbranded UK RETAIL firmware and unlocked my phone to use in other networks, that's as far as I've got.
Not looking to root or anything else, just to apply the stock unbranded firmware so that I can get future updates from Motorola and not Tesco.
Thanks.
Click to expand...
Click to collapse
Where did you download it from?
he's in the process of uploading it. called Superboot?
The Jones said:
Where did you download it from?
Click to expand...
Click to collapse
Moto G aka Falcon aka Motorola G (XT1032, XT1033) firmwares
http://sbf.droid-developers.org/falcon/list.php
---------- Post added at 04:20 PM ---------- Previous post was at 03:35 PM ----------
seapoint said:
Moto G aka Falcon aka Motorola G (XT1032, XT1033) firmwares
http://sbf.droid-developers.org/falcon/list.php
Click to expand...
Click to collapse
Code:
Motorola G (XT1032, XT1033)
Back
Size MD5 Carrier File
382.6 MiB 2E5FADFE1F8DE917AF0ABE6B9610AEC1 O2 Germany O2-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
398.7 MiB 18394D6F7268A9D489CFCFAE3B63E803 O2 Great Britain O2SL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
382.6 MiB BD4BA4AE781BDB3DE20FD53D185E8C2C Retail Germany RETAIL-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
394.1 MiB DA99BD447878CDF35E7D2929E8E2A61E Retail French RETAIL-FR_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
397.9 MiB 2D45BDDDA22C46EF4C4023B78F9EE172 Retail British RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.xml.zip
398.7 MiB 1B5988BD4CDB676E217F87891AB4667F Tesco Great Britain TESCOSL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
382.6 MiB 12B83CD9B0F945C9D25881843AC50AC8 SFR France VODAFONE-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
396.7 MiB F69CE3807C2FEE310987F83144E8CABC SFR France VODAFONESL-FR_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_v2.xml.zip
409.2 MiB 9E782FA758557C526599F723E5A33F69 Claro Brazil fastboot_falcon_amxbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_43_release-keys-cid12-AmericaMovil_BR.tar.gz
409.1 MiB 3768338F742347A22DF8568B4B927449 Claro Brazil fastboot_falcon_amxbr_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-AmericaMovil_BR.tar.gz
403.4 MiB 1B4D1C455C16D2526D08D117B15C3EA6 Telcel Mexico fastboot_falcon_amxmx_user_4.3_14.10.0Q3.X-76-LCG-8-1_1_release-keys-cid12-AmericaMovil_MX.tar.gz
409.2 MiB AB46415C9D344B45F7954ADD834BC215 OI Brazil fastboot_falcon_oibr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_57_release-keys-cid12-Oi_BR.tar.gz
409.2 MiB 4C194E4FCBF508743EE7D5309281A0AE Retail Brazilian fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
409.1 MiB FA7B72E00EB3141E8B614C2022FBB9CB Retail Brazilian fastboot_falcon_retbr_user_4.3_14.10.0Q3.X-76-LCG-8_41_release-keys-cid12-Brasil_BR.tar.gz
396.6 MiB E8580CDCCB9E669D5CA1ECA8B6D4F9DF Movistar Chile fastboot_falcon_tefcl_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-Movistar_CL.tar.gz
396.6 MiB 38BE1E4EAA8A938CE78DB7B2678B0481 Movistar Peru fastboot_falcon_tefpe_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-Movistar_PE.tar.gz
We have 6.22 GiB of firmwares for Motorola Motorola G.
Actually, it seems the South American firmwares are pachaged , and named, differently. They're specifically labelled beginning with fastboot, and the archives let you expand to a directory giving you a single image for system.img The only one of interest to me is Brazil - I wonder will the Brazil system image work instead of the GB, FR or DE retail devices. If we get root I suppose we can edit build prop.
There has to be a way of concatenating the system images in the European retail images?
I wonder is this
jusumgeezer said:
Coming from a nexus, I thought that also, but I'm sure on another thread it is mentioned that ADB sideload only applies to OTA update files.
I tried pushing the whole zip to the phone but as expected it did nothing.
Fastboot flash should work but the bootloader won't give permission so something isn't right.
Although on the instructions from motorola website it says not to use android fastboot, but use RSD tool instead. I have 2 potential issus with that #1 the software itself hasn't been updated to support the MotoG or #2 it wont work with my 64bit copy of windows 7.
Click to expand...
Click to collapse
I am wondering if you need to use the Motorola version of fastboot which is different to the normal Android one. Sorry, I dont have a link to it, but I think it is in the Moto X section somewhere.
The Jones said:
I am wondering if you need to use the Motorola version of fastboot which is different to the normal Android one. Sorry, I dont have a link to it, but I think it is in the Moto X section somewhere.
Click to expand...
Click to collapse
The Motorola version is in a "Windows" folder in the Brazil firmware download!
heres root http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/
Related
So as you already know the KitKat update started rolling for our beloved Moto G - but sadly for the moment only for those with the US Global / US GSM firmwares.
So first thing first you need to do is UNLOCK THE BOOTLOADER (guide here) and download the following files:
Drivers: http://d-h.st/5j0 or install Motorola Device Manager
Firmware: http://sbf.droid-developers.org/download.php?device=14&file=127 (US Global) or http://sbf.droid-developers.org/download.php?device=14&file=121 (US GSM aka for T-Mobile aka for AWS networks)
Minimal ADB & Fastboot: https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
mfastboot: http://dc342.4shared.com/download/i...&dsid=3oh7jy.ce197763503e738750fd87149655184b
1. Enable USB Debugging on the device and Install the drivers accordingly to the OS version you have - either x86 for 32bits or x64 for 64bits
2. Install Minimal ADB and Fastboot
3. Extract mfastboot.exe to the folder where you installed Minimal ADB and Fastboot
4. Now in the same folder where you installed Minimal ADB and Fastboot extract files from the firmware folder.
5. Start Minimal ADB and Fastboot using shortcut created or py_cmd.exe
6. Connect the device via USB cable and in the cmd window that opens type
Code:
adb reboot-bootloader
7. Your device should reboot in Bootloader now.
8. While in Bootloader paste the following lines one by one, and be sure you get an OKAY after each one (some bootloader errors may appear, ignore them)
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk1
mfastboot.exe flash system system.img_sparsechunk2
mfastboot.exe flash system system.img_sparsechunk3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
9. You should now be rebooted in the official US firmware.
10. Wait for the OTA update to come OR flash the official OTA update.zip - US Global is here (thanks to @ZealotRush) and US AWS is here (thanks to @antiquezip) OR if you are rooted and with CWM you can flash the REPACK 4.4 KitKat system here (thanks to @josalaito)
my first guide, hopes everything goes well. I would love some feedback from those who tries this - as it worked perfect for me
Did mobile data still work after you flashed it ? Did you leave the UK radio
Sent from my XT1032 using Tapatalk
I had to unlock the bootloader of my Telcel Moto G to flash the US Retail, with the locked bootloader doesn't let me flash the boot and the system files...
kyler084 said:
Did mobile data still work after you flashed it ? Did you leave the UK radio
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Yes, my data connection works.
My device is a retail.de version.
joel_sinbad said:
I had to unlock the bootloader of my Telcel Moto G to flash the US Retail, with the locked bootloader doesn't let me flash the boot and the system files...
Click to expand...
Click to collapse
But did it worked? Si funciona con el bootloader desbloqueado?
Sent from my XT1032 using Tapatalk
thanks for the guide, did work like a charm on my European retail model. everything works perfectly, including FM-radio.
No OTA update yet, but the FW change worked.
Do you really need to unlock the bootloader?
xmattjus said:
If you want to change it back to default (in my case retail-uk) we just need to flash with the same process the previous firmware, right?
Click to expand...
Click to collapse
Even easier, as the European firmwares I tested all have a flash.bat that flash all the things automatically - you just need to reboot in bootloader and double-click a file in Windows
If i flash the us gsm firmware on the global us model will i get the other bands
Kfire21 said:
If i flash the us gsm firmware on the global us model will i get the other bands
Click to expand...
Click to collapse
US firmware presumably has the same config as the European ones. However, after flashing I can't get HSPA+ but only 3G.
darkeingel said:
US firmware presumably has the same config as the European ones. However, after flashing I can't get HSPA+ but only 3G.
Click to expand...
Click to collapse
But would it then work on T mobiles network aws 1700/2100
Kfire21 said:
But would it then work on T mobiles network aws 1700/2100
Click to expand...
Click to collapse
Theres an AWS retail firmware linked in the guide too, especially for T-Mobile
darkeingel said:
Theres an AWS retail firmware linked in the guide too, especially for T-Mobile
Click to expand...
Click to collapse
So you're saying if have the global gsm version and flash the t mobile firmware from the post, I can then use it on T-mobiles aws network
Kfire21 said:
If i flash the us gsm firmware on the global us model will i get the other bands
Click to expand...
Click to collapse
No you can't do that the phones have different model numbers.
Kfire21 said:
So you're saying if have the global gsm version and flash the t mobile firmware from the post, I can then use it on T-mobiles aws network
Click to expand...
Click to collapse
I can't confirm that, as I didn't try but it should be working.
The official specs says - Networks: GSM (850/900/1800/1900 MHz); UMTS (850/900/1700/1900/2100 MHz); CDMA (850/1900 MHz) the code numbers from T-Mobile version and Global US does not differ - so my guess that the firmware is the only thing that stands out between you and AWS network connection - I may be wrong tho'
darkeingel said:
I can't confirm that, as I didn't try but it should be working.
The official specs says - Networks: GSM (850/900/1800/1900 MHz); UMTS (850/900/1700/1900/2100 MHz); CDMA (850/1900 MHz) the code numbers from T-Mobile version and Global US does not differ - so my guess that the firmware is the only thing that stands out between you and AWS network connection - I may be wrong tho'
Click to expand...
Click to collapse
Someone test it out please, that would be fantastic if it works.
Can I do this in a Telcel(Mexico) motorola g?, Someone in Canada that already did this? (telus, bell bla bla bands are compatible with Mexico)
Thunderwrath said:
Can I do this in a Telcel(Mexico) motorola g?, Someone in Canada that already did this? (telus, bell bla bla bands are compatible with Mexico)
Click to expand...
Click to collapse
I can confirm this working on a Telcel Mexico Moto G
frijolito18 said:
I can confirm this working on a Telcel Mexico Moto G
Click to expand...
Click to collapse
Did you have to unlock the bootloader?
darkeingel said:
The official specs says - Networks: GSM (850/900/1800/1900 MHz); UMTS (850/900/1700/1900/2100 MHz); CDMA (850/1900 MHz) the code numbers from T-Mobile version and Global US does not differ - so my guess that the firmware is the only thing that stands out between you and AWS network connection - I may be wrong tho'
Click to expand...
Click to collapse
I think it should work on all the Single sim Moto Gs (Carrier locked too) since hardware is the same al across (including bands)
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Edit :Follow this thread for flashing http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Nice! Now we just need kernel source I believe then developers can get their hands dirty (well, after making a proper TWRP).
Hope so very soon
Thanks for the files.
@Devhux TWRP is already posted in original dev section.
Envoyé de mon XT1562 en utilisant Tapatalk
Fastboot Commands Full Path
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Fast link for xt1563 CA Default : https://mega.nz/#!qQZRDYAb!-W3iKudrm7xdxh2W6rdRSkDuc7142uP8zFRq8t2hPig
1st of all: thx for uploading!
secondly: the name of the original FW for the 1562 is called "XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12_cid7_subsidy-DEFAULT_CFC.xml.zip"
What about the "RETASIA" part, this kinda makes me wonder whether this might be intended for some kind of Asian version of the X. But I'm in Germany and also got the 1562. Will this work, regardless?
Best wishes derelektrischemoench
Which one of these is for the Wind variant XT1563?
noel_105 said:
Which one of these is for the Wind variant XT1563?
Click to expand...
Click to collapse
Flash the one i uploaded via mega works in all carriers,your in Canadian network right?
derelektrischemoench said:
1st of all: thx for uploading!
secondly: the name of the original FW for the 1562 is called "XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12_cid7_subsidy-DEFAULT_CFC.xml.zip"
What about the "RETASIA" part, this kinda makes me wonder whether this might be intended for some kind of Asian version of the X. But I'm in Germany and also got the 1562. Will this work, regardless?
Best wishes derelektrischemoench
Click to expand...
Click to collapse
im not 100 % sure if it will work
Hi @derelektrischemoench, I am based in France and got an X Play from retail and the original firmware does say RETASIA so I assume you should have no issue.
Full name is : 23.21.10.lux_retasia_ds.retasiaall.en.03 retfr
Build : LPD23.118-10
XMoDuLeSx said:
Flash the one i uploaded via mega works in all carriers,your in Canadian network right?
Click to expand...
Click to collapse
Thanks, yes Wind Mobile.
paugustin said:
Hi @derelektrischemoench, I am based in France and got an X Play from retail and the original firmware does say RETASIA so I assume you should have no issue.
Full name is : 23.21.10.lux_retasia_ds.retasiaall.en.03 retfr
Build : LPD23.118-10
Click to expand...
Click to collapse
Interesting, I've got my x play from retail as well here in Germany but mine says lux_reteu.reteu.en.EU reteu.
.... Whatever that means.
if you can help with stock firmware XT1563 DUAL SIM BRASIL, to with a rom stock not appear card slot !
amadeusmattos said:
if you can help with stock firmware XT1563 DUAL SIM BRASIL, to with a rom stock not appear card slot !
Click to expand...
Click to collapse
http://www.filefactory.com/file/5r5...D23.118-6.1_cid12_subsidy-DEFAULT_CFC.xml.zip
reflash this one and if it does't work flash this :
http://www.filefactory.com/file/4bi...D23.118-6.1_cid12_subsidy-MOVSTLA_CFC.xml.zip
XMoDuLeSx said:
http://www.filefactory.com/file/5r5...D23.118-6.1_cid12_subsidy-DEFAULT_CFC.xml.zip
reflash this one and if it does't work flash this :
http://www.filefactory.com/file/4bi...D23.118-6.1_cid12_subsidy-MOVSTLA_CFC.xml.zip
Click to expand...
Click to collapse
I tried and did not work! Does not work the slot! when I bought worked with the ORIGINAL STOCK ROM that came with unit , bought it in BRAZIL
can someone upload this to another place? i download at 24kbs from file factory.
Does anybody know why firmware for EU is missing? I guess I could use Asia one, but just in case I wanted to go back to stock.
I'm positive it was there before when thread was first posted. Maybe they were accidentally removed (just guessing)
Does anyone have a mirror for a XT1563 firmware ? Bandwith on FileFactory is horribly slow :/
vache said:
Does anyone have a mirror for a XT1563 firmware ? Bandwith on FileFactory is horribly slow :/
Click to expand...
Click to collapse
XMoDuLeSx said:
Fast link for xt1563 CA Default : https://mega.nz/#!qQZRDYAb!-W3iKudrm7xdxh2W6rdRSkDuc7142uP8zFRq8t2hPig
Click to expand...
Click to collapse
Was much faster for me. Filefactory was the worst download speed I've had since NetZero AOL dialup days.
First Make Your Nougat System ,Boot Partition Backup By TWRP.Load TWRP By fastboot boot twrp.img..Dont Flash TWRP recovery.Just Boot it From Fast Boot..My case TWRP recover file name is : twrp.img
1) Download Moto driver and adb and fastboot from above and install it on your PC.
2) Now Download the correct last Updated firmware for your device from above and extract it to the ADB installation directory.
3) Now go to adb and fastboot installation directory and open the command window there by pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
4) Now Reboot your phone into Bootloader mode by turning it off and press and hold ‘Power + Volume Down‘.
5) Now flash system partition and boot image only by issue the below commands one by one. (If you are using mfastboot then type ‘mfastboot‘ instead of ‘fastboot‘)
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot erase userdata
fastboot reboot
7) Done! Above steps will Downgrade Moto G4 Plus from Android Nougat to Marshmallow.
You Can able Receive future OTA update without any problem
prakash27091987 said:
First Make Your Nougat System ,Boot Partition Backup By TWRP.Load TWRP By fastboot boot twrp.img..Dont Flash TWRP recovery.Just Boot it From Fast Boot..My case TWRP recover file name is : twrp.img
1) Download Moto driver and adb and fastboot from above and install it on your PC.
2) Now Download the correct last Updated firmware for your device from above and extract it to the ADB installation directory.
3) Now go to adb and fastboot installation directory and open the command window there by pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
4) Now Reboot your phone into Bootloader mode by turning it off and press and hold ‘Power + Volume Down‘.
5) Now flash system partition and boot image only by issue the below commands one by one. (If you are using mfastboot then type ‘mfastboot‘ instead of ‘fastboot‘)
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot erase userdata
fastboot reboot
7) Done! Above steps will Downgrade Moto G4 Plus from Android Nougat to Marshmallow.
You Can able Receive future OTA update without any problem
Click to expand...
Click to collapse
Downgrading only boot and system caused messed up fingerprint. Used all commands except bootloader provided in other thread for downgrade and now everything's good.
I see that the bootloader is not being downgraded. Doesn't that mean OTAs might still brick your device?
Bootloader was not upgraded in N. And you won't be able to downgrade your bootloader once updated.
Update : Seems I am wrong about bootloader. rpm and sbl1 have been upgraded. Those are bootloader files.
http://cloud.tapatalk.com/s/581069a8d254a/Screenshot_20161026-135945.png?
Sent from my Moto G4 Plus using Tapatalk
this is not working means fingerprint problem comes
Silesh.Nair said:
Bootloader was not upgraded in N. And you won't be able to downgrade your bootloader once updated.
Update : Seems I am wrong about bootloader. rpm and sbl1 have been upgraded. Those are bootloader files.
http://cloud.tapatalk.com/s/581069a8d254a/Screenshot_20161026-135945.png?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
So are you saying that the bootloader was updated and if we do the OTA we might brick our phone?
I am not sure. Guys who got the soak test notification also have their bootloaders upgraded. They were officially handed out the soak test builds by lenovo. So they will have the same issues as those who flashed it manually, if at all there are issues.
I am not sure how this is gonna play out. If someone who is running the 139-63 build who has not upgraded to the N build can pull out the two files, we could compare them.
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
I am not sure. Guys who got the soak test notification also have their bootloaders upgraded. They were officially handed out the soak test builds by lenovo. So they will have the same issues as those who flashed it manually, if at all there are issues.
I am not sure how this is gonna play out. If someone who is running the 139-63 build who has not upgraded to the N build can pull out the two files, we could compare them.
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
The point about bricks is regarding downgrade. In previous phones, downgrading from L to K, but keeping the L bootloader and then getting official L OTA would brick phone. Motorola has never supported downgrade on any phone. So if you downgrade, and later take OTA you could brick. Especially if running M with N bootloader.
The whole title of this thread is wrong - no way can anyone 100% guarantee no future brick.
Silesh.Nair said:
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Taking OTA to official N from soak test N is not an issue, the issue arises when someone took the N soak test, downgrade to M, OTA to official N.
tl;dr if i'm not wrong:
M -> Official N = No brick
M -> Soak test N -> Official N = No brick
Soak test N -> Downgrade to M -> OTA to official N = Brick
When you downgrade from N to M, you are only changing the system/modem/oem partitons.
Official OTA will probably upgrade bootloader/system/modem/oem/gpt/tz partitions. There is a catch here. People for whom the soak test was released are on a different bootloader than the general public which means they can't patch the bootloader or check for a specific one. They just have to upgrade it without any checks.
My question is how you will brick the device when you won't be able to downgrade the bootloader?
But as someone said, nothing in life is certain.
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
When you downgrade from N to M, you are only changing the system/modem/oem partitons.
Official OTA will probably upgrade bootloader/system/modem/oem/gpt/tz partitions. There is a catch here. People for whom the soak test was released are on a different bootloader than the general public which means they can't patch the bootloader or check for a specific one. They just have to upgrade it without any checks.
My question is how you will brick the device when you won't be able to downgrade the bootloader?
But as someone said, nothing in life is certain.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
You can say what you want but go read the G And X2 communities. EVERY user that updated to M then rolled back to L and later took an OTA back to M bricked. The OTA doesn't take into a count that the bootloader was a newer version - I don't remember the mechanics, but the OTA expected a different version of the bootloader.
Search XDA or the Internet for "Blank flash files" . The problem is downgrade related. If you take any upgrade, be prepared to stay on it. Do NOT downgrade.
Well, it may be true. I don't just blindly flash files on my device. I go thru the zip file to see what files are patched to make sure that I don't get into trouble. That need not be the case with all users.
Let's wait for the official OTA to be released and then we'll see how it goes.
Sent from my Moto G4 Plus using Tapatalk
ok guys ive just done some testing and ive found that whilst on official android 6.0 my bootloader version was (moto-msm8952-b0.0e) (sha-4986429) with the date 2016-04-13
then after upgrading to 7.0 soak test the bootloader version changed to (moto-msm8952-b1.00) with the date 2016-06-24
so after i then did the downgrade back to 6.0 marshamallow and the bootloader version downgraded back to its original (moto-msm8952-b0.0e) (sha-4986429) with the date 2016-04-13 so moral of the story is the bootloader does infact downgrade too and doesnt stay with the new android 7.0 bootloader like many seem to claim on this thread if u guys want to try this for yourself run this command to get your bootloader versions before update and after u updateto 7.0 & then 1 last time when u downgrade to 6.0 u will need to run the below command via adb fastboot
fastboot getvar version-bootloader
The problem with X2 and G was a mismatch between partition table version and bootloader. If you can't downgrade gpt.bin, then you may be facing a brick with OTA. Keep in mind that this is just one possible path to brickdom. The Motorola update assumes certain things, and we don't know what may change in the future. I think there is a reason that Moto says they don't support downgrades: they are not going to check for modifications and any mismatch may cause problems.
If you downgrade, then don't take an OTA, it is that simple.
http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147
chromedome00 said:
The problem with X2 and G was a mismatch between partition table version and bootloader. If you can't downgrade gpt.bin, then you may be facing a brick with OTA. Keep in mind that this is just one possible path to brickdom. The Motorola update assumes certain things, and we don't know what may change in the future. I think there is a reason that Moto says they don't support downgrades: they are not going to check for modifications and any mismatch may cause problems.
If you downgrade, then don't take an OTA, it is that simple.
http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147
Click to expand...
Click to collapse
soo we cant take ota but we can install it manually that doesnt effect i think
does downgrading work if my device is brick??
does downgrading work if my device is brick??
sucssecfully downgraded from marshmallow after brick in nougat .........tons of thank
my device was brick while trying rooting in nougat with superuser su but stuck in bootloop..........
so i directly tried to install cm 14.1 but failed..
not able to reinstall nougat ota update also......
finally downgraded to marshmallow .......... but i guess fingerprint is not working.....
drdhaval1987 said:
my device was brick while trying rooting in nougat with superuser su but stuck in bootloop..........
so i directly tried to install cm 14.1 but failed..
not able to reinstall nougat ota update also......
finally downgraded to marshmallow .......... but i guess fingerprint is not working.....
Click to expand...
Click to collapse
dOWNGRADE process please
kemesh said:
dOWNGRADE process please
Click to expand...
Click to collapse
its already mentioned in this thread....simply follow the steps........
When I am trying to install the Nougat OTA zip file from within the stock recovery, it is giving me the following errors:
Code:
Verifying current system. . .
Mount count = 9
Last mount path = /system
Last mount time = 1479061757 -> Sun Nov 13 18:29:17 2016
Device was remounted R/W 9 times
Last remount happened on Sun Nov 13 18:29:17 2016
E1004: system partition fails to recover
E: unknown command [log]
E: unknown command [log]
E: Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I go about fixing this? I have followed your guide on how to downgrade and downgraded my XT1643 to -63 baseband.
Help please!
I take no credit for this, thank the Motorola-Firmware-Team on Android File Host, and you can follow any leaked firmware on their Twitter feed.
I no longer have a Moto X Pure Edition, so I can't personally vouch for this firmware, but it seems like it is a totally legit full factory firmware image of Nougat NPH25.200-22 for flashing in fastboot.
This is the "official" full factory image of Nougat NPH25.200-22 and NOT the OTA file. It can be used for a clean flash and to relock the bootloader which is recommended to pass SafetyNet API checks if you are planning on staying stock and not rooting.
Flashfile.xml shows: version="clark_retus-user 7.0 NPH25.200-22 21 release-keysM8992_1255331.29.01.88.09R", MD5 matches, and all dates are correct.
This is ONLY for the Moto X Pure Edition, Retail US (RETUS) variant. I have no information on any other firmware or device.
Tested and verified as official Nougat factory ROM image by @Andromendous
This image is NOT flashable in TWRP, like all factory images it is flashed with fastboot in the bootloader... How to flash:
Code:
fastboot oem lock begin (if wanting to re-lock bootloader, othewise use `fastboot oem fb_mode_set`)
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock (only if you used `fastboot oem lock begin`, otherwise end with `fastboot oem fb_mode_clear`)
fastboot reboot
See https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 for detailed instructions
Downloads
Original source: https://androidfilehost.com/?fid=889964283620765304
Google Drive mirror: [removed]
@acejavelin: Since you have been one of the guru's on this phone, can this file be flashed in fastboot directly if I am on stock MM android December update rooted with Magisk and TWRP installed? I just want to make sure that when I am ready to take the plunge, I can take the minimal work procedure since I factory wipe after all major updates anyway.
Does this mean people who haven't received 7.0 OTA can flash this ROM and get Nougat without any complications such as corrupted bootloader and stuff? Also read multiple times that downgrading to 6.0 and again upgrading to 7.0 via OTA corrupts the bootloader leading to hard brick (which is now solver using external SD), will flashing this would solve this too?
Yes... This is the pure stock factory image for Nougat, it can be flashed, used to lock the bootloader, fix the "preflash validation" issues, etc. like any factory image.
There should be no issue applying it over a downgraded version, as long as you flash the entire image.
acejavelin said:
Yes... This is the pure stock factory image for Nougat, it can be flashed, used to lock the bootloader, fix the "preflash validation" issues, etc. like any factory image.
There should be no issue applying it over a downgraded version, as long as you flash the entire image.
Click to expand...
Click to collapse
Great! I plan on holding on to this phone for about another 6 months or so and might as well get the update. Will probably go over to stock nougat in December. Custom ROMs just always seem to have at best some minor issue(s) that prevents me from sticking with them.
Dude Ace you are the f-ing man. Thanks for the find.
I flashed it manually while on Hashbangs LOS rom. I was stuck on 6.0 modem and tried to just flash the modem, which made me lose sim service. I then flashed the entire imagine manually and booted just fine.
Now I'm back to LOS with 7.0 modem and so far so good. Hashbang is doing a great job, he's already cleaned multiple bugs just today.
i am already on 7.0 but putting this away for the future. Can you flash the zipped XML or do you need to unzip and flash each piece individually? Thanks.
schneid said:
i am already on 7.0 but putting this away for the future. Can you flash the zipped XML or do you need to unzip and flash each piece individually? Thanks.
Click to expand...
Click to collapse
It's a factory image... Have to flash each piece manually with fastboot, this is not a flashable TWRP or other recovery image
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
andromobilogy said:
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
Click to expand...
Click to collapse
We don't know that for sure... NPH25.200-22 is what has been rolling out to Sprint, T-Mobile, and AT&T devices, but it seems that Verizon users are getting NPH25.200-23 according to one verified (via screen shot) report on Lenovo's official forum.
The issue is we know the Moto OTA server keeps track of what device get's what version, if you flash this it won't know you have it so if a future OTA update comes out, you might be offered it via push and will have to wait until it's available by pull.
andromobilogy said:
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
Click to expand...
Click to collapse
Yes. There's a huge difference. With this you wont brick your phone.
Can we Re-lock bootloader with this version?
AND...
If you flash this version NPH25.200-23, will you still be able to install a SIM from another carrier, say Sprint, T-Mobile, or AT&T, and not be pigeon holed into a specific wireless Plan from VZW with their own Propietary APPs like VZW Cloud?
CLETjB said:
Can we Re-lock bootloader with this version?
AND...
If you flash this version NPH25.200-23, will you still be able to install a SIM from another carrier, say Sprint, T-Mobile, or AT&T, and not be pigeon holed into a specific wireless Plan from VZW with their own Propietary APPs like VZW Cloud?
Click to expand...
Click to collapse
Yes, you can relock... unless you have already applied NPH25.200-23, otherwise you should be able to relock from ANY version out there currently.
We don't know what's up with NPH25.200-23 for sure though... recently Moto has been doing "different" versions for Verizon users that don't seem to get to anyone else, we also see it in the Moto G5+, and we don't know the differences either. Most likely it's just a minor VZW specific change and can be ignored. If the update does get pushed later, you should have no issues taking the OTA update when on this firmware, it is the official factory image.
@ acejavelin
I know that I'm a bit OT, but I think that this thread is the most suitable for my request: do you know if there is a nougat factory image available also for the xt1572?
Thanks in advance,
Gaetano.
Inviato dal mio XT1572 utilizzando Tapatalk
ghitus said:
@ acejavelin
I know that I'm a bit OT, but I think that this thread is the most suitable for my request: do you know if there is a nougat factory image available also for the xt1572?
Thanks in advance,
Gaetano.
Inviato dal mio XT1572 utilizzando Tapatalk
Click to expand...
Click to collapse
As I stated in the first post... no, I have idea or information about any other images for other variants and I suggest following MotoFirmware123 on Twitter as that is the best place to find leaked firmware. Motonovo has gotten very tight on letting firmware get out, but if it becomes available this is likely where it will come from, IF it ever gets leaked.
Just curious. I recently moved on to a Note 8 and want to give my son my Moto X Pure. Does this file put default recovery on the phone as well? I tried to factory reset it last night (had it rooted with TWRP installed) and now it will only boot into TWRP. I just want it all stock for him.
Thanks
Oaklands said:
Just curious. I recently moved on to a Note 8 and want to give my son my Moto X Pure. Does this file put default recovery on the phone as well? I tried to factory reset it last night (had it rooted with TWRP installed) and now it will only boot into TWRP. I just want it all stock for him.
Thanks
Click to expand...
Click to collapse
Yes, it is an official stock firmware image... if properly flashed with fastboot it will restore the device to 100% factory conditions, including recovery.
acejavelin said:
Yes, it is an official stock firmware image... if properly flashed with fastboot it will restore the device to 100% factory conditions, including recovery.
Click to expand...
Click to collapse
Thank you. His phone is now ready.
Finally !Thanks, man!
Now I just flash via fastboot and avoid all the OTA updates process.
you are the man!
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.