These packages contain the stock firmware as supplied by ZTE. You may want to use them to...
Return to stock after installing a custom ROM.
Upgrade from an older firmware to a newer one while on a custom ROM.
Recover from modifying stock /system in TWRP.
... etc ...
If you wish to return to stock, use the following procedure:
Boot into TWRP.
Wipe data and cache.
Flash boot stack.
Flash system and boot.
Flash recovery.
Reboot.
US model, version 1.2.0 b14 (Android 7.1.1)
Boot stack:
B2017G-US-v1.2.0-b14-bootstack.zip
md5=c8c3dc76737fc0ac0c719ee5a3dbd5d7
System and boot:
B2017G-US-v1.2.0-b14-stocksystem.zip
md5=58d5e5d80c18ec598c84a797761b8f2f
Recovery:
B2017G-US-v1.2.0-b14-stockrecovery.zip
md5=c78e1ed2cc1e40c978d9f5eaa1c35803
EU model, version 1.2.0 b12 (Android 7.1.1)
Boot stack:
B2017G-EU-v1.2.0-b12-bootstack.zip
md5=2f8e63896843e81be55c537d14dd1702
System and boot:
B2017G-EU-v1.2.0-b12-stocksystem.zip
md5=58a6d0104918fc0cfcfc048626eeb0b0
Recovery:
B2017G-EU-v1.2.0-b12-stockrecovery.zip
md5=35575108a8b89099ab489e1904a41690
tdm said:
these packages contain the stock firmware as supplied by zte. You may want to use them to...
return to stock after installing a custom rom.
upgrade from an older firmware to a newer one while on a custom rom.
recover from modifying stock /system in twrp.
... Etc ...
if you wish to return to stock, use the following procedure:
boot into twrp.
wipe data and cache.
flash boot stack.
flash system and boot.
flash recovery.
reboot.
us model, version 1.2.0 b14 (android 7.1.1)
boot stack:
b2017g-us-v1.2.0-b14-bootstack.zip
md5=c8c3dc76737fc0ac0c719ee5a3dbd5d7
system and boot:
b2017g-us-v1.2.0-b14-stocksystem.zip
md5=58d5e5d80c18ec598c84a797761b8f2f
recovery:
b2017g-us-v1.2.0-b14-stockrecovery.zip
md5=c78e1ed2cc1e40c978d9f5eaa1c35803
eu model, version 1.2.0 b12 (android 7.1.1)
boot stack:
b2017g-eu-v1.2.0-b12-bootstack.zip
md5=2f8e63896843e81be55c537d14dd1702
system and boot:
b2017g-eu-v1.2.0-b12-stocksystem.zip
md5=58a6d0104918fc0cfcfc048626eeb0b0
recovery:
b2017g-eu-v1.2.0-b12-stockrecovery.zip
md5=35575108a8b89099ab489e1904a41690
Click to expand...
Click to collapse
after install system b14 dump on my zte axon 7 mini b2017g stuck on zte logo (bootloader unlocked)
Hmmm... okay, sorry. I'll post a new zip to try shortly.
modorate said:
after install system b14 dump on my zte axon 7 mini b2017g stuck on zte logo (bootloader unlocked)
Click to expand...
Click to collapse
Please try this....
http://code.nwwn.com/files/android/axon7mini/B2017G-US-v1.2.0-b14-stocksystem-nopatch.zip
tdm said:
Hmmm... okay, sorry. I'll post a new zip to try shortly.
Click to expand...
Click to collapse
tdm said:
Please try this....
http://code.nwwn.com/files/android/axon7mini/B2017G-US-v1.2.0-b14-stocksystem-nopatch.zip
Click to expand...
Click to collapse
Sir, I will highly be appreciated if you guide me in this way...... actually i am new. i only can follow step by step instruction. Please write back....
Now i am downloading all package (Bootstack, Recovery, System Boot) of B12 and i will follow the above mentioned instructions, i dont know what will happen.
Okay, you mentioned downloading both b14 and b12 and I don't see any location information in your profile. So first I need to know your regional variant. I am aware of the following:
US (United States)
ES (Spain)
AT (Austria)
DE (German)
The current OP has firmware listed for US and EU.
The EU firmware is actually ES. I made it before I knew that there were separate builds for ES/AT/DE. I will be updating that soon, likely today. However, based on everything that I know, the ES firmware should work on the AT and DE models also.
The US firmware was made from a backup of my device, as there is no full OTA available for 1.2.0 b14. It is possible that the tool I used to make the "stocksystem" zip has an error, or I made a mistake. This is why I posted the "stocksystem-nopatch" version for you to try -- it is a direct copy of my device made without using the tool.
modorate said:
Sir, I will highly be appreciated if you guide me in this way...... actually i am new. i only can follow step by step instruction. Please write back....
Now i am downloading all package (Bootstack, Recovery, System Boot) of B12 and i will follow the above mentioned instructions, i dont know what will happen.
Click to expand...
Click to collapse
Sir.... I am using zte axon 7 mini b2017g US variant...
Actually i bought this phone for superior quality of headphone sound but i am very diapointed to know that EU model cant boost sound enough as compare to US and china variant.
As you know G model having volume limitation by EU law.
Iam trying all the method to root my phone to amendment in mixper.path.xlm. i have come to know there we can change the value to boost headphone sound.
Any shortcut or patcher is available???
If i cant this then i sold out....
Alright, so you have a US model that you are using in EU? And I assume you are able to boot TWRP. So try the systemimage-nopatch zip and see if that works.
I do not run stock, so I cannot help you root the device. But many others here do run stock and have rooted their device. You will find instructions for installing SuperSU in other parts of this forum.
modorate said:
Sir.... I am using zte axon 7 mini b2017g US variant...
Actually i bought this phone for superior quality of headphone sound but i am very diapointed to know that EU model cant boost sound enough as compare to US and china variant.
As you know G model having volume limitation by EU law.
Iam trying all the method to root my phone to amendment in mixper.path.xlm. i have come to know there we can change the value to boost headphone sound.
Any shortcut or patcher is available???
If i cant this then i sold out....
Click to expand...
Click to collapse
Boot message
So, I attempted to flash the zips to return to stock after encountering the echo in the previous AOKP Rom. Upon reboot, the device was stuck on the ZTE Logo. I then re-flashed TWRP and AOKP Rom, and now I am seeing the following after the ZTE Logo:
< More options
press VOLUME keys
Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device:
g.co/ABHg.co/placeholder
If no key pressed:
Your device will power off in 30 seconds
After the 30 seconds, the device reboots and works fine. I'd be grateful if you can advise me on how to get rid of this message. My device is US B14.
I am thinking that the handset recognized it was being tampered with and throw the message. I have not attempted to lock the bootloader. Please advise. Thanks.
I probably made a mistake. Try the nopatch zip linked above.
I'll look at the images later, I'm busy tonight.
harrydat said:
So, I attempted to flash the zips to return to stock after encountering the echo in the previous AOKP Rom. Upon reboot, the device was stuck on the ZTE Logo. I then re-flashed TWRP and AOKP Rom, and now I am seeing the following after the ZTE Logo:
< More options
press VOLUME keys
Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device:
g.co/ABHg.co/placeholder
If no key pressed:
Your device will power off in 30 seconds
After the 30 seconds, the device reboots and works fine. I'd be grateful if you can advise me on how to get rid of this message. My device is US B14.
I am thinking that the handset recognized it was being tampered with and throw the message. I have not attempted to lock the bootloader. Please advise. Thanks.
Click to expand...
Click to collapse
tdm said:
I probably made a mistake. Try the nopatch zip linked above.
I'll look at the images later, I'm busy tonight.
Click to expand...
Click to collapse
Excuse me sir but I do not have clear how can I back to stock ROM.
Can I only flash boot and system without problem. I mean that I don't want flash the recovery because my version is EU and I don't have keys combination to enter EDL. (Sorry for my English and thanks for your huge work)
Enviado desde mi ZTE B2017G mediante Tapatalk
Yes just boot and system should work.
You can use tuliptool to flash stock recovery if you wish.
bautog said:
Excuse me sir but I do not have clear how can I back to stock ROM.
Can I only flash boot and system without problem. I mean that I don't want flash the recovery because my version is EU and I don't have keys combination to enter EDL. (Sorry for my English and thanks for your huge work)
Enviado desde mi ZTE B2017G mediante Tapatalk
Click to expand...
Click to collapse
Perfect, thanks again.
Enviado desde mi ZTE B2017G mediante Tapatalk
I'm on lineage tulip
Are the link in 1st post right to return on stock??
Or I must to use the other link?
I'm not sure, nobody has reported back yet. Give it a try and let us know.
birrez said:
I'm on lineage tulip
Are the link in 1st post right to return on stock??
Or I must to use the other link?
Click to expand...
Click to collapse
tdm said:
I'm not sure, nobody has reported back yet. Give it a try and let us know.
Click to expand...
Click to collapse
I don't suppose you have a .img of the bootloader and such to flash in fastboot, tdm? after installing that zip from the man, nothing but fastboot seems to work.
also, I tried using the nopatch firmware through fastboot flash update, but i get the error:
Code:
#fastboot update nopatch.zip
archive does not contain 'android-info.txt'
error: update package 'nopatch.zip' has no android-info.txt
also this:
Code:
#fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3679000
(bootloader) variant:TULIP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x12c00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5ebb79e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x100000000
(bootloader) serialno:f5a9c626
(bootloader) kernel:lk
(bootloader) product:TULIP
all:
finished. total time: 0.047s
:laugh:
also also, I cannot access edl any longer... can literally feel a faint heartbeat-like "pulse" vibration when the fastboot screen isnt being displayed
edit: retrying after I use "#fastboot flash boot <recoveryimgname>" and the .img file from your post that I somehow overlooked; https://forum.xda-developers.com/axon-7-mini/development/stock-boot-images-verity-removed-t3685697
edit: retrying after I use "#fastboot flash boot <recoveryimgname>" and the .img file from your post that I somehow overlooked; https://forum.xda-developers.com/axon-7-mini/development/stock-boot-images-verity-removed-t3685697
Click to expand...
Click to collapse
Firstly, I respect and appreciate everything you've contributed to the community.
That said, the above attempt did not work. The stock zips from zte did not work. Interesting because it does read that there have been no tampers. I did make a backup, but its a .ab backup. (Perhaps I can dig into that and use fastboot to write the neccasary info into the bootloader...?)
Also tried every other ROM posted to this sub-forum. Tried various .img flashes through fastboot that seem to transfer without error but do nothing when attemptig to initiate them. fastboot .zip updates all give the above error regarding android-info.txt (assuming this is because the vendor and such are no longer present?).
I tried about 100 different combinations of the physical buttons as well as paying attention to how they (occasionally) affect the 'beep'/subtle vibration of the device that disappears
tl;dr: stuck in fastboot, no adb & edl seems to have stopped or the method of getting there has changed.
Willing to try pretty much whatever you advise if you have any ideas, feel free to message me if theres any possibility of working this out. I could probably manage to return it one way or the other but I'd much rather work through it. Its been about 18 hours of trying everything I can think of and Google-fu'ing to no avail.
My mini stuck At Bootloop
Hello my Mini is bricked Stuck at Bootloop. Have from Custom rom+ TWRP to back to Stock Rom and my Phone is bricked...
Link500 said:
Hello my Mini is bricked Stuck at Bootloop. Have from Custom rom+ TWRP to back to Stock Rom and my Phone is bricked...
Click to expand...
Click to collapse
Can you get into edl?
Does your device restart with a good solid vibration if you hold power button down for ~15 seconds?
I have been the same, and I can not enter EDL mode because it is the European model and the PC does not recognize me the phone when connecting
Related
hey guys.. i have moto g xt1033 indian dual sim version. recently my device was soft brick. and it was stuck on boot loop whenever i trying to reboot after booting complete it is shutdown automatically and then restart since two week. i tried everything. flashed cm11 rom but nothing happened. also tried to flash stock firware of indian version. but i got a warning...
preflash boot validation failed...... what should i do now?? i want to relock my device... so please guys suggest me. i need help...:crying: :crying:
There is a guide pinned in the troubleshooting section
--------------------------------------------------------------
Hit the thanks button if I helped you 8)
--------------------------------------------------------------
nothing happen.. also i got a error....
version downgraded for boot
version downgraded for tz :'(
manish.kunwal said:
hey guys.. i have moto g xt1033 indian dual sim version. recently my device was soft brick. and it was stuck on boot loop whenever i trying to reboot after booting complete it is shutdown automatically and then restart since two week. i tried everything. flashed cm11 rom but nothing happened. also tried to flash stock firware of indian version. but i got a warning...
preflash boot validation failed...... what should i do now?? i want to relock my device... so please guys suggest me. i need help...:crying: :crying:
Click to expand...
Click to collapse
Try at your own risk.
http://forum.xda-developers.com/showthread.php?t=2542219
manish.kunwal said:
nothing happen.. also i got a error....
version downgraded for boot
version downgraded for tz :'(
Click to expand...
Click to collapse
Ignore the error while flashing gpt.bin because you are downgrading... Just retry the process for other errors
Asian 4.4.4 stock firmware image now available:
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
lost101 said:
Asian 4.4.4 stock firmware image now available:
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
Click to expand...
Click to collapse
i flashed this and relock the bootloader but even all i still found some troubles. my device reboot automatically :crying:
manish.kunwal said:
i flashed this and relock the bootloader but even all i still found some troubles. my device reboot automatically :crying:
Click to expand...
Click to collapse
Please provide a full list of fastboot commands you used.
lost101 said:
Please provide a full list of fastboot commands you used.
Click to expand...
Click to collapse
Please have a look at the pinned posts in the troubleshoot section...They describe this full procedure in detail...
I said that because I wanted to make sure all commands where used.
lost101 said:
I said that because I wanted to make sure all commands where used.
Click to expand...
Click to collapse
Oh yes all commands are used...Just make sure you type the sparsechunk command correctly....The name of that file differs from firmware to firmware...
Could someone help me restore 4.4.2 stock firmware?
MY BOOT LOADER IS LOCKED
When I turn on my phone I get this:
version downgraded for boot
failed to validate boot image
Fastboot reason: fall-through from normal boot mode
ImAustin366624 said:
Could someone help me restore 4.4.2 stock firmware?
When I turn on my phone I get this:
version downgraded for boot
failed to validate boot image
Fastboot reason: fall-through from normal boot mode
Click to expand...
Click to collapse
Flash the 4.4.4 image.
pfufle said:
Flash the 4.4.4 image.
Click to expand...
Click to collapse
My moto g never received the 4.4.4 update so do you think it will still work? Where could I find the 4.4.4 firmware?
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
It's downloading now, will report back when i'm done Thanks for helping!
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
I will have to do this later in the day, my crappy satellite internet is acting up right now
I had this problem and sadly, after trying countless times with different firmwares the only solution I could find is to unlock the bootloader.
Then it stops giving you an error when you try to flash boot.img.
Your mileage may vary, but that is a potential fix, so keep that in mind.
ianxblog said:
I had this problem and sadly, after trying countless times with different firmwares the only solution I could find is to unlock the bootloader.
Then it stops giving you an error when you try to flash boot.img.
Your mileage may vary, but that is a potential fix, so keep that in mind.
Click to expand...
Click to collapse
The only way to unlock the bootloader with AIO moto g's is to use Jcases sunshine app and you have to be in the operating system for that
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My parents use the same exact phone as me on the same carrier, could I dump the firmware from their phones and then flash it onto mine?
You can take a system image via a nandroid backup and the flash it on your device
EDIT This was solved thanks to fc3211
I currently have no OS, and I can't boot into TWRP. I can boot into the stock Huawei Recovery, but that doesn't seem to do anything for me, as I can't download an image from the Huawei site. I can't seem to find the stock images for BLN-L24. All the links I saw on this site and Huawei's no longer work. I'm able to download the Honor 6X firmware from this site: http://consumer.huawei.com/us/support/phones/honor-6x/ but when I load the file into the sdcard, then follow the instructions and boot with both volume up+volume down pressed, it just hangs there.
Any advice on how I can proceed? What files I can flash? I really am not sure why I get a response saying I am not allowed to boot into a custom recovery. When I 'successfully' flash twrp, it still doesn't actually flash TWRP. My best guess is when I loaded an OS unsuccessfully, it locked FRP somehow and prevented flashing??
Code:
D:\Downloads\Honor 6X>fastboot boot twrp-3.2.1-0-berlin.img
downloading 'boot.img'...
OKAY [ 0.618s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.625s
D:\Downloads\Honor 6X>fastboot oem unlock
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.003s
D:\Downloads\Honor 6X>fastboot boot twrp-3.2.1-0-berlin.img
downloading 'boot.img'...
OKAY [ 0.625s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.632s
D:\Downloads\Honor 6X>
Search the forum for "FRP locked" and you will see my posts (I had same issue as you and was able to solve it) and posts from others with similar situation.
Basically you just need to use dload to load the stock firmware for the exact same model and the exact same build that you had before your phone stopped working.
https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
If you use the files from the wrong build or from the wrong model than you will get error at 5% over and over again.
Try flashing elitetwrp from the Elite ROM thread. I successfully flashed the regular openkirin twrp countless times but would only boot to stock recovery, then on a whim I flashed elitetwrp this morning and I'm able to boot to TWRP now.
Reading on the log that you attached, i see "boot twrp-3.2.1-0-berlin.img". You got that TWRP from official TWRP site? If yes, give a try to OpenKirin's TWRP; it works like a charm. https://forum.xda-developers.com/honor-6x/development/twrp-t3583413
fc3211 said:
Search the forum for "FRP locked" and you will see my posts (I had same issue as you and was able to solve it) and posts from others with similar situation.
Basically you just need to use dload to load the stock firmware for the exact same model and the exact same build that you had before your phone stopped working.
https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
If you use the files from the wrong build or from the wrong model than you will get error at 5% over and over again.
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU! I tried a bunch of the packages until finally the oldest one worked. I've been bricked for like 4 months, and finally tried to fix it again after I lost my S8 on Christmas =/
Great! And I am proud of you that you had the motivation to try each package one by one. It was because you did not give up, that is why you had victory in the end.
just add [SOLVED] in title of this thread so that its displayed on main page and we dont look it again to help
Help needed
shashank1320 said:
just add [SOLVED] in title of this thread so that its displayed on main page and we dont look it again to help
Click to expand...
Click to collapse
Help please
Sir I have Honor 6x indian varient on emui 5, past 2 months I have officially unlocked bootloader on my phone and flashed twrp successfully but when I restarted my phone into recovery, it just stucked at the bootloader unlocked page.
Then I found some ways to flash the original emui recovery through some Chinese application, but currently there is no recovery in my phone.
But thank to God that it still has its OS.
My doubt is if I again started to deal with my phone in the way you posted, will my phone can be repaired?? As there is no emui recovery that will install the zip by pressing and holding all three buttons(maybe).
Help me sirplzz
me.puneet8877 said:
Help please
Sir I have Honor 6x indian varient on emui 5, past 2 months I have officially unlocked bootloader on my phone and flashed twrp successfully but when I restarted my phone into recovery, it just stucked at the bootloader unlocked page.
Then I found some ways to flash the original emui recovery through some Chinese application, but currently there is no recovery in my phone.
But thank to God that it still has its OS.
My doubt is if I again started to deal with my phone in the way you posted, will my phone can be repaired?? As there is no emui recovery that will install the zip by pressing and holding all three buttons(maybe).
Help me sirplzz
Click to expand...
Click to collapse
Yes. Just use the dload method, it will bing back to full stock with stock recovery. in future as well, dload is the way to go for restoring till EMUI 5. dload method is in my signature.
Custom roms
shashank1320 said:
Yes. Just use the dload method, it will bing back to full stock with stock recovery. in future as well, dload is the way to go for restoring till EMUI 5. dload method is in my signature.
Click to expand...
Click to collapse
Thanks a lot Sir!!!!
lastly can you tell me about some stock android ROMs for this device, which are stable
me.puneet8877 said:
Thanks a lot Sir!!!!
lastly can you tell me about some stock android ROMs for this device, which are stable
Click to expand...
Click to collapse
wait for Oreo may be. thats a better option. for stable part, there are elite, RR, AOKP ROMs but seems elite is better among them but having the same EMUI look. wait for Oreo.
Thanks
shashank1320 said:
wait for Oreo may be. thats a better option. for stable part, there are elite, RR, AOKP ROMs but seems elite is better among them but having the same EMUI look. wait for Oreo.
Click to expand...
Click to collapse
Thank you sir of
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.
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.