Nougat is working on almost all plus variatns.... in the telegram group is already confirmed working on XT1640-41-42-43-44... only for moto g4 plus.... on standard moto g4 you will get no ril nor wifi
1- Install full xt1643 lastest stock rom XT1643 Stock MM rom. You have a guide to flash here Flashing steps (oem lock command is not mandatory).
2-Reboot to system, copy this (ota nougat file) into the internal storage.
3- Turn off and start into bootloader. There choose recovery mode and hit power. If you get "no command" press power for 2 seconds and then push vol +. Select install ota from sdcard and choose the file that you downloaded. let the recovery do its job.
4. (OPTIONAL BUT RECOMMENDED) wipe data/cache.
5. reboot system. hope you can do it.
I am sure that this firmware will flash the wrong modem for the US version (XT1644).
SoNic67 said:
I am sure that this firmware will flash the wrong modem for the US version (XT1644).
Click to expand...
Click to collapse
It also was "the wrong" for Chile... But it totally works... Tried on all the variants
dhk.- said:
It also was "the wrong" for Chile... But it totally works... Tried on all the variants
Click to expand...
Click to collapse
XT1644 retus working
It's not working here on XT1644. It needs a MPJ24.139-63/64 target while my XT1644 is running MPJ24.139-64/65.
when i try to downgrade to stock marshmallow, i have some errors
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.065s
what can i do ? i only can install custom roms via twrp.
NOTIFICATIONS: 0 search plus
Home Moto G4 Plus Moto G4 Plus Guides, News, & Discussion NOUGAT for XT164* by dhk.-
View First Unread Reply Rate Thread
dhk.-
Yesterday, 09:31 PM |#1
OP Senior Member970 posts Thanks: 1,006
Nougat is working on almost all plus variatns.... in the telegram group is already confirmed working on XT1640-41-42-43-44... only for moto g4 plus.... on standard moto g4 you will get no ril nor wifi
1- Install full xt1643 lastest stock rom XT1643 Stock MM rom. You have a guide to flash here Flashing steps (oem lock command is not mandatory).
2-Reboot to system, copy this (ota nougat file) into the internal storage.
3- Turn off and start into bootloader. There choose recovery mode and hit power. If you get "no command" press power for 2 seconds and then push vol +. Select install ota from sdcard and choose the file that you downloaded. let the recovery do its job.
4. (OPTIONAL BUT RECOMMENDED) wipe data/cache.
5. reboot system. hope you can do it.
1 users say Thank You to dhk.- for this useful post Gift dhk.- Ad-Free
SoNic67
Yesterday, 10:07 PM |#2
Senior Member396 posts Thanks: 47
I am sure that this firmware will flash the wrong modem for the US version (XT1644).
dhk.-
Yesterday, 10:09 PM |#3
OP Senior Member970 posts Thanks: 1,006
Quote:
Originally Posted by SoNic67
I am sure that this firmware will flash the wrong modem for the US version (XT1644).
It also was "the wrong" for Chile... But it totally works... Tried on all the variants
dhk.-
Yesterday, 10:13 PM |#4
OP Senior Member970 posts Thanks: 1,006
Quote:
Originally Posted by dhk.-
It also was "the wrong" for Chile... But it totally works... Tried on all the variants
XT1644 retus working
Attached Thumbnails
Mercado_Negro
Yesterday, 11:13 PM |#5
Senior Member2,317 posts Thanks: 1,793
It's not working here on XT1644. It needs a MPJ24.139-63/64 target while my XT1644 is running MPJ24.139-64/65.
AokiAlan
Today, 04:11 AM |#6
Junior Member10 posts Thanks: 5
when i try to downgrade to stock marshmallow, i have some errors
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.065s
Downgrade from nougat ? Don't flash gpt and bootloader then flash other
dhk.- said:
It also was "the wrong" for Chile... But it totally works... Tried on all the variants
Click to expand...
Click to collapse
The LTE bands of Indian variant (XT1643) are different. Do you have LTE there in Chile with this firmware? What provider? Note that the 2G/3G bands are the same.
Since the modem is re-flashed too, I don't get how the LTE bands would not be affected.
Bands:
http://www.gsmarena.com/motorola_moto_g4_plus-8050.php
LTE in Chile:
https://en.wikipedia.org/wiki/List_of_LTE_networks#Americas
SoNic67 said:
The LTE bands of Indian variant (XT1643) are different. Do you have LTE there in Chile with this firmware? What provider? Note that the 2G/3G bands are the same.
Since the modem is re-flashed too, I don't get how the LTE bands would not be affected.
Bands:
http://www.gsmarena.com/motorola_moto_g4_plus-8050.php
LTE in Chile:
https://en.wikipedia.org/wiki/List_of_LTE_networks#Americas
Click to expand...
Click to collapse
I do have LTE on band 4 now... If you see in the list attached, band 4(1700/2100) is not available in India.
So your model is actually a XT1644 (the only one that has LTE band 4)?
Well it shouldn't mess with your bands as your bands are hardwared into the processor. BUT as this is a soak test build I wouldn't except everything to work
Sent from my Moto G4 Plus using XDA-Developers mobile app
i have a XT1641 that also have LTE band 4...
guys, if you don't wanna try, your business... I'm telling you that is working because i did it and it's working on my phone... my phone even still have the LATAM_DSDS baseband...
Hello first sorry my english.
Im new with moto phones. I came from note 4. So i dont understand yet the "moto terminology"
Add my screen capture.
Can I flash this nougat ROM?
Thanks un advance.
XT1641 (2gb RAM 32gb ROM)
Sent from my Moto G (4) using XDA-Developers mobile app
903tex said:
Well it shouldn't mess with your bands as your bands are hardwared into the processor. BUT as this is a soak test build I wouldn't except everything to work
Click to expand...
Click to collapse
Nope. The bands are a combination of non-volatile (NV) settings inside the Qualcomm modem and hardware bits. Good news is that it seems that Moto update didn't touch the NV, so even with the "wrong" firmware, the NV part of the modem that determines the bands remained the same. Don't know if any other issues might arise (like VoLTE functionality).
Info about the NV area:
http://forum.xda-developers.com/showthread.php?t=1954029
I can assure it's working on XT1641, bought in Personal, carrier of Argentina. It took 12 minutes to install the zip and 40 seconds for the first boot!
AokiAlan said:
when i try to downgrade to stock marshmallow, i have some errors
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.065s
what can i do ? i only can install custom roms via twrp.
Click to expand...
Click to collapse
Just a reminder. It is highly recommended when you go to make a change in your device to the first do NANDROID your current system. So you make sure that if something goes wrong you can restore a copy of your operating system. Someone asked the question of how to return to MM. I just restore my MM backup with TWRP and ready, all right.
I can confirm.. working great on XT1644! No issues seen so far.
dhk.- said:
I do have LTE on band 4 now... If you see in the list attached, band 4(1700/2100) is not available in India.
Click to expand...
Click to collapse
Flashed on XT1643 & using airtel 4G. Works fine
dhk.- said:
Nougat is working on almost all plus variatns.... in the telegram group is already confirmed working on XT1640-41-42-43-44... only for moto g4 plus.... on standard moto g4 you will get no ril nor wifi
1- Install full xt1643 lastest stock rom XT1643 Stock MM rom. You have a guide to flash here Flashing steps (oem lock command is not mandatory).
2-Reboot to system, copy this (ota nougat file) into the internal storage.
3- Turn off and start into bootloader. There choose recovery mode and hit power. If you get "no command" press power for 2 seconds and then push vol +. Select install ota from sdcard and choose the file that you downloaded. let the recovery do its job.
4. (OPTIONAL BUT RECOMMENDED) wipe data/cache.
5. reboot system. hope you can do it.
Click to expand...
Click to collapse
Two questions about this. First off, I am using a XT1641 version p2a from Canada running build MPJ34.139-23.3.
1) Your post says it works for 41-42-43-44 but your update link is specifically for XT1643. Is that correct? Should all these phones be updated to that firmware first or do you mean to say that you should just be on the latest build for your phone? My build is older than that but says there's no update.
2) I had to flash stock MM firmware before and needed to flash a specific carrier or else WiFi and network wouldn't work. With Nougat is there just one that will work for everything or do I need to wait for my specific carrier to have firmware released?
Thanks
*Edit*
Finally got around to the update, everything works perfect on my phone. Only odd thing is that my version in Hardware Information changed - went from p2a to PVTB. Not sure what that means (if anything at all), but either way it doesn't seem to affect anything.
micahbell said:
Two questions about this. First off, I am using a XT1641 version p2a from Canada running build MPJ34.139-23.3.
1) Your post says it works for 41-42-43-44 but your update link is specifically for XT1643. Is that correct? Should all these phones be updated to that firmware first or do you mean to say that you should just be on the latest build for your phone? My build is older than that but says there's no update.
2) I had to flash stock MM firmware before and needed to flash a specific carrier or else WiFi and network wouldn't work. With Nougat is there just one that will work for everything or do I need to wait for my specific carrier to have firmware released?
Thanks
Click to expand...
Click to collapse
1. Yeah, it's alright. I flashed it on my XT1641 and no problems, Baseband conserved. As you say, our variant was the only one without getting ANY security update. But flashing this one let you update to Nougat.
2. Truly, idk. I have only seen retail variants. But it didn't modified any network related thing on the cases that I know. So, make a backup and try
Related
So, last week I received the update to 4.4.4 on my Republic Wireless xt1031 (locked bootloader), then quickly realized that I preferred 4.4.2. After this, I downloaded the official republic wireless 4.4.2 firmware and attempted to flash it with fastboot, which didnt do anything but wipe my data. I then retried with mfastboot, which softbricked my phone. Whenever I try to flash any of the many stock firmwares I have found (tried Republic Wireless, Boost and a couple other firmwares, including a couple 4.4.4 firmwares), it seems that everything has been able to flash over and is working other than the system image files (system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 for the stock republic wireless firmwares). Whenever I try to flash any of the 3 over, I get an error on the phone:
hab check failed for system
Invalid PIV signed system image
and in my command prompt:
...\falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-key
s-cid6.xml>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (256840 KB)...
OKAY [ 8.056s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.464s
I've heard this can be an issue with a locked bootloader, but I've also read that people can flash stock roms with a locked bootloader as long as the firmware is specifically for your phone. Does anyone have any advice on this issue? I'm just about at my wit's end here. I have tried at least 6 different firmware, I've intentionally hardbricked it by destroying the bootloader, then reflashed it with blankflash and Motoflasher on two separate tries and still no luck. Currently, it goes through the boot process but just boots to a black screen. Any help would be greatly appreciated.
I had a nightmare with this problem, I think it is an issue with your partitions, do you have an unlocked boot loader? If so try installing twrp recovery and check the sizes of your partitions especially /system partition and post results, I never fixed the issue I eventually got it replaced by the store I bought the phone from.
PS unlocking boot loader will void your warranty so if possible try and get the store to replace device.
Sent from my XT1039 using XDA Free mobile app
jasond567 said:
I had a nightmare with this problem, I think it is an issue with your partitions, do you have an unlocked boot loader? If so try installing twrp recovery and check the sizes of your partitions especially /system partition and post results, I never fixed the issue I eventually got it replaced by the store I bought the phone from.
PS unlocking boot loader will void your warranty so if possible try and get the store to replace device.
Sent from my XT1039 using XDA Free mobile app
Click to expand...
Click to collapse
My bootloader is not unlocked and Republic Wireless does not allow the bootloader to be unlocked. One of the reasons I was trying to downgrade was because I was going to use sunshine to unlock the bootloader, but it doesn't work on 4.4.4. I got the gpt.bin from the official update for 4.4.4 on Republic Wireless that someone had posted here on xda, as it was the noly one that would flash successfully that I have found. According to the 4.4.4 debricking guide on here, you can flash the gpt.bin and motoboot.img from a 4.4.4 firmware, then after that flash the 4.4.2 files from the stock firmware of your choice.
Ahhh I see that's The same problem I had I followed most online suggestions from XDA and others and nothing worked for me so I got a replacement phone, is that possible for you to do, fingers crossed that if you do it will come with 4.4.2
Sent from my XT1039 using XDA Free mobile app
I am getting a replacement phone sent, hoping for 4.4.2!!!
Great news, I have my fingers crossed for you
Sent from my XT1039 using XDA Free mobile app
wulfep said:
I am getting a replacement phone sent, hoping for 4.4.2!!!
Click to expand...
Click to collapse
Did you get it unlocked?
wulfep, I am exactly in your situation. Were you able to find a workaround that allows you to flash the Republic Wireless Moto G 1stgen XT1031 phone with an alternate firmware, of the same Android Lollipop version but for other Spring-based MVNOs (i.e. Boost, US Cellular, Verizon etc)? And considering that the phone has the damn Motorola bootloader locked !?
Thanks.
Hi Guys,
I have rooted my moto g3 and unlocked the bootloader to install lineage OS.
Now I tried to roll back my original version and lock the bootloader.
Unfortunately, this error show ups in the command window.
D:\Softwares\Moto G3\ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.010s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.417s
Please help to retain my mobile
Regards,
Bharani
If you'd searched up a bit, you'd find that this is due to the current firmware on the phone being newer than the firmware you're trying to flash. Newer firmwares with security patches are not yet available (as of now). Searching before posting is highly appreciated.
Skip the gpt.bin and bootloader commands, rest should flash up fine. Make sure to do factory reset from the stock recovery. You can do a full flash after a newer or equal firmware is available.
Broadcasted from Zeta Reticuli
Hi,
Sorry for the late response
Thanks for the reply.
Please let mew know whether the new firmware is available now to solve this issue.
Regards,
Bharani Kumar B.
Bharani07 said:
Hi,
Sorry for the late response
Thanks for the reply.
Please let mew know whether the new firmware is available now to solve this issue.
Regards,
Bharani Kumar B.
Click to expand...
Click to collapse
currently it is not available .... and there is no harm keeping it unlocked ... u will still be able to receive the updates ...
So u have to wait for latest firmware to be released to relock ur bootloader :fingers-crossed:
This is a newest MIUI 9 China Beta "s TZ &Modem
Baseband:BO.2.6.c1.2-0818_1948_87b78d2
Link:https://yadi.sk/d/wdmLsruk3MSQJr
Flashable ZIP File
Please Use TWRP
more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: DO NOT flash this on official Lineage with Lollipop bootloader, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot which is also pretty useless, since your bootloader is locked
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (40704 KB)...
OKAY [ 1.343s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.362s
PeterMarkoff said:
more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: do not flash this on official Lineage, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Click to expand...
Click to collapse
kindly type, fastboot oem device-info on fastboot mode with phone pluged in,hope it didnt lock your bootloader.
yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data
PeterMarkoff said:
yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data
Click to expand...
Click to collapse
Have you unlocked your phone officially?
Because i flash this too and had no problem at all.
?
unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader
PeterMarkoff said:
unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader
Click to expand...
Click to collapse
YES,This is a Nougat Bootloader,you must unlock bootloader in official tools after you install this file in twrp
Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.
buktore said:
Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.
Click to expand...
Click to collapse
****ing ask before do something if you're not so sure about it.
Has anyone noticed any improvement with the new radio?
Hello. Has anyone got a link to the latest firmware available for a MI4C. I'm not after the official ROM, just firmware workable with ROMs. I think the last update I done was through andropax link https://androidfilehost.com/?w=files&flid=155424 is there a way I can also find out which firmware I have installed I forgot.
Is this the latest > https://androidfilehost.com/?fid=890278863836288705
fw_libra_miui_MI4c_V9.5.2.0.NXKCNFA_81f363e363_7.0
& will it run dev ROMs?
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
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.