hi, I tried to root my nexus 7, and all ok, but when I tried to exec flash google factory image, I've the following output
Downloading Factory Image...
--2013-01-24 02:07:53-- URL rejected
Resolving dl.google.com (dl.google.com)... 74.125.225.238, 74.125.225.224, 74.125.225.230, ...
Connecting to dl.google.com (dl.google.com)|74.125.225.238|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 291197311 (278M) [application/x-tar]
Saving to: `factory.tgz'
100%[===================================================================================>] 291.197.311 365K/s in 16m 6s
2013-01-24 02:24:00 (294 KB/s) - `factory.tgz' saved [291197311/291197311]
< waiting for device >
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.128s]
finished. total time: 0.129s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.238s]
finished. total time: 0.238s
erasing 'recovery'...
OKAY [ 0.136s]
finished. total time: 0.137s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.217s]
finished. total time: 0.218s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 3.612s]
finished. total time: 3.612s
sending 'bootloader' (2096 KB)...
OKAY [ 0.280s]
writing 'bootloader'...
OKAY [ 1.952s]
finished. total time: 2.232s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
sending 'radio' (16384 KB)...
OKAY [ 2.071s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.086s
rebooting into bootloader...
OKAY [ 4.012s]
finished. total time: 4.012s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 488804800 bytes
error: update package missing system.img
Press ENTER to return to the main menu...
I tred using another USB port, and cable, moving the app to another folder and re-run, but I've the same output.
This is awfull cause I can't boot my nexus, only re-flashing the recovery, I can boot it, but the O.S. not. My nexus is dead, what I can do?
My, OS, is Linux Mint Nadia
Hi,
my NSdoesnt boot and I cant flash another ROM because my NS cant mount SD anymore, so I tryed to restore it back to stock and flash the .imgs with fastboot. Boot.img, recovery.img, userdata.img, without problems, but the system.img gives me the message "write failed" or something. Tryed it multiple times with the Gingerbread system.img, and ICS system.img, same problem.
I can boot into recovery, but the phone doesnt recognize the SD and also the system partition.
Any solutions?
Sorry for my english.
What recovery you using?
Sent from my Nexus S using xda app-developers app
Tried 2 different CMW Recoveries, it's not a recovery problem. My System and SD storage is corrupt or something, I think.
It can't be all that corrupt as you are able to install boot loader and recovery. Try and adb sideload CyanogenMod 10.1. Once you got a booting phone, things tend to play nicely.
Sent from my Nexus S using xda app-developers app
Just tried the adb sideload method.
"Installing update..." for 5 Minutes now. I think it cant write on /system.
I've also tried to erase /system partition via fastboot it gives me also the "failed" message.
system.img write fail error
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...
I've had a similar experience when installing stock ROMs after installing cwm and cm 10. Can you guys not even install cm10?
Sent from my Nexus S using xda app-developers app
Deus Tempestas said:
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...
Click to expand...
Click to collapse
Same problem here! Did u find solution?
My Nexus 5 recently had some hardware issue and I requested an RMA. The following error comes up when I try to flash the stock recovery system back. Is it okay if I send the Nexus 5 with TWRP installed?
sending 'bootloader' (2508 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.479s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (42049 KB)...
OKAY [ 1.520s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.741s
rebooting into bootloader...
OKAY [ 0.123s]
finished. total time: 0.124s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 07219a4613c86dd0
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8628 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.728s]
sending 'recovery' (9210 KB)...
OKAY [ 0.541s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.641s
I hate to be the bearer of bad news, but it appears the flash memory is bad on your N5. See here. As for whether it's okay to send it with TWRP installed...hmm. I dunno. I don't think an eMMC failure could be caused by installing TWRP so it shouldn't be considered your fault, but they might make you pay for the repair because of it.
Brushstroke said:
I hate to be the bearer of bad news, but it appears the flash memory is bad on your N5. See here. As for whether it's okay to send it with TWRP installed...hmm. I dunno. I don't think an eMMC failure could be caused by installing TWRP so it shouldn't be considered your fault, but they might make you pay for the repair because of it.
Click to expand...
Click to collapse
Okay, I will post back when I get told about paying for the repair. Thanks.
Wellin said:
Okay, I will post back when I get told about paying for the repair. Thanks.
Click to expand...
Click to collapse
How did you fare with Google and this issue?
I've had my nexus 5 for awhile now and decided that I should try to root it. So I followed a guide and youtube and it worked. I then followed a guide to install the android M developer preview, just to check out what had changed. From there I decided to install Cyanogenmod 12.1 . So I was looking at this guide when all of a sudden i noticed my root was gone for some reason. (im new to all this, not sure if that was supposed to happen). So then I followed the same rooting steps I used for the first youtube guide I watched. everything seemed to go fine until i realized that i was in a boot loop. I then decided to go ahead and install Cyanogenmod 12.1 anyway. It worked and my phone was fine. Until i woke up this morning and saw that it was in a boot loop again, but now I can't even get into my custom recovery (TWRP). I dowloaded this program to completely return my phone to stock but every time it tries to flash something to my phone, it gets this "flash write failure" message. Now I'm really lost and do not know what to do. I really rather not buy a new phone.
If anyone can help it would be really appreciated!!! If you do, I will need you to assume I do not know anything, as I'm not very familiar with everything.
Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk
ldubs said:
Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This is what happens when I tried to flash it.. After trying to turn my phone back on, it tries to load up with the cyanogenmod logo still there.
Mathieus-MacBook-Pro:hammerhead-lmy48i mathieulaflamme$ ./flash-all.sh
sending 'bootloader' (3119 KB)...
OKAY [ 0.202s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.403s
rebooting into bootloader...
OKAY [ 0.110s]
finished. total time: 0.110s
sending 'radio' (45425 KB)...
OKAY [ 1.535s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.759s
rebooting into bootloader...
OKAY [ 0.104s]
finished. total time: 0.104s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: 06ed88372115a3f5
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8980 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.752s]
sending 'recovery' (9696 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.592s
I found the hardware is different
US retail is 6/256
T-Mobile/Metro is 4/128
It may have negative impact if you cross flash ROM
I bit the bullet and attempted the flash...
It won't work, the vbmeta_system.img flashes fine with no issues (which is needed to flash an image to the system partition). It seems the ROM wont fit in the system ROM space completely, leading to corruption of the system partition. I'd definitely advise against trying this yourself.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRES31.Q2-11-103-2_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.001s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' OKAY [ 0.161s]
Finished. Total time: 0.167s
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_a' OKAY [ 0.004s]
Finished. Total time: 0.008s
Sending 'super' (459104 KB) OKAY [ 12.920s]
Writing 'super' OKAY [ 0.079s]
Finished. Total time: 13.008s
Sending 'super' (507816 KB) OKAY [ 14.361s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 16.088s
Sending 'super' (513096 KB) OKAY [ 13.386s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.285s
Sending 'super' (515124 KB) OKAY [ 12.993s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.627s
Sending 'super' (502664 KB) OKAY [ 12.930s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.175s
Sending 'super' (512856 KB) OKAY [ 13.320s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.476s
Sending 'super' (461208 KB) OKAY [ 11.963s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 13.153s
Sending 'super' (524244 KB) OKAY [ 13.649s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.510s
Sending 'super' (524240 KB) OKAY [ 13.687s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.586s
Sending 'super' (524256 KB) OKAY [ 12.149s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 12.994s
Sending 'super' (524208 KB) FAILED (remote: 'Error: Last flash failed : Invalid Parameter')
fastboot: error: Command failed
Another thing... when trying to install an older version of the RETUS stock image on my TMO variant, I got a rollback warning.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRE31.Q2-11-66_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC_R3_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 3 vs 5
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
After a restore my device works just fine
DENVER_GLOBAL_RRE31.Q2-11-52-4_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_cid50_CFC
ArtiicPanda said:
I bit the bullet and attempted the flash...
It won't work, the vbmeta_system.img flashes fine with no issues (which is needed to flash an image to the system partition). It seems the ROM wont fit in the system ROM space completely, leading to corruption of the system partition. I'd definitely advise against trying this yourself.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRES31.Q2-11-103-2_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.001s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' OKAY [ 0.161s]
Finished. Total time: 0.167s
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_a' OKAY [ 0.004s]
Finished. Total time: 0.008s
Sending 'super' (459104 KB) OKAY [ 12.920s]
Writing 'super' OKAY [ 0.079s]
Finished. Total time: 13.008s
Sending 'super' (507816 KB) OKAY [ 14.361s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 16.088s
Sending 'super' (513096 KB) OKAY [ 13.386s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.285s
Sending 'super' (515124 KB) OKAY [ 12.993s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.627s
Sending 'super' (502664 KB) OKAY [ 12.930s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.175s
Sending 'super' (512856 KB) OKAY [ 13.320s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.476s
Sending 'super' (461208 KB) OKAY [ 11.963s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 13.153s
Sending 'super' (524244 KB) OKAY [ 13.649s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.510s
Sending 'super' (524240 KB) OKAY [ 13.687s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.586s
Sending 'super' (524256 KB) OKAY [ 12.149s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 12.994s
Sending 'super' (524208 KB) FAILED (remote: 'Error: Last flash failed : Invalid Parameter')
fastboot: error: Command failed
Another thing... when trying to install an older version of the RETUS stock image on my TMO variant, I got a rollback warning.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRE31.Q2-11-66_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC_R3_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 3 vs 5
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
After a restore my device works just fine
DENVER_GLOBAL_RRE31.Q2-11-52-4_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_cid50_CFC
Click to expand...
Click to collapse
If all of that works fine then will flashing Cricket firmware with TMO firmware work?
NonStickAtom785 said:
If all of that works fine then will flashing Cricket firmware with TMO firmware work?
Click to expand...
Click to collapse
Bootloader must be unlocked if you want to cross flash
mingkee said:
Bootloader must be unlocked if you want to cross flash
Click to expand...
Click to collapse
What if you had a blankflash file? Doesn't the EDM for Qualcomm allow flashing new everything onto a device? Including bootloader? I might be wrong. But this is the method I was going to take when I first began trying to root this phone.
It doesn't matter it will cross flash I did it with mine there were no system errors no none of that
Gave it a go and oddly enough, while I am now unable to flash to the Metro ROM, the RETUS ROM seems to work almost flawlessly. 5G works as intended too.
I just wish I was able to use this phone on Cricket Wireless.
DragonfireEX402 said:
Gave it a go and oddly enough, while I am now unable to flash to the Metro ROM, the RETUS ROM seems to work almost flawlessly. 5G works as intended too.
I just wish I was able to use this phone on Cricket Wireless.
Click to expand...
Click to collapse
I flashed RETUS as well on my Boost Mobile variant. However, it looks like gyroscope and accelerometer don't work for me. Are you having issues?
itzimeow said:
I flashed RETUS as well on my Boost Mobile variant. However, it looks like gyroscope and accelerometer don't work for me. Are you having issues?
Click to expand...
Click to collapse
Never actually tried to use either of those things, so I don't know yet.
Hello, I have a concern. Looking to unlock my MetroPCS network cell phone, I flashed the original firmware it came with, for the RETUS one. I have tried to go back to the TMO rom but it stays in the logo, is there any way to go back?
ArtiicPanda said:
I bit the bullet and attempted the flash...
It won't work, the vbmeta_system.img flashes fine with no issues (which is needed to flash an image to the system partition). It seems the ROM wont fit in the system ROM space completely, leading to corruption of the system partition. I'd definitely advise against trying this yourself.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRES31.Q2-11-103-2_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.001s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' OKAY [ 0.161s]
Finished. Total time: 0.167s
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_a' OKAY [ 0.004s]
Finished. Total time: 0.008s
Sending 'super' (459104 KB) OKAY [ 12.920s]
Writing 'super' OKAY [ 0.079s]
Finished. Total time: 13.008s
Sending 'super' (507816 KB) OKAY [ 14.361s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 16.088s
Sending 'super' (513096 KB) OKAY [ 13.386s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.285s
Sending 'super' (515124 KB) OKAY [ 12.993s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.627s
Sending 'super' (502664 KB) OKAY [ 12.930s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.175s
Sending 'super' (512856 KB) OKAY [ 13.320s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.476s
Sending 'super' (461208 KB) OKAY [ 11.963s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 13.153s
Sending 'super' (524244 KB) OKAY [ 13.649s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.510s
Sending 'super' (524240 KB) OKAY [ 13.687s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.586s
Sending 'super' (524256 KB) OKAY [ 12.149s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 12.994s
Sending 'super' (524208 KB) FAILED (remote: 'Error: Last flash failed : Invalid Parameter')
fastboot: error: Command failed
Another thing... when trying to install an older version of the RETUS stock image on my TMO variant, I got a rollback warning.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRE31.Q2-11-66_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC_R3_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 3 vs 5
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
After a restore my device works just fine
DENVER_GLOBAL_RRE31.Q2-11-52-4_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_cid50_CFC
Click to expand...
Click to collapse
Hi friend, could you provide the ROM DENVER_GLOBAL_RRE31.Q2-11-52-4_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_cid50_CFC to return the firmware from RETUS to TMO, please.
NonStickAtom785 said:
What if you had a blankflash file? Doesn't the EDM for Qualcomm allow flashing new everything onto a device? Including bootloader? I might be wrong. But this is the method I was going to take when I first began trying to root this phone.
Click to expand...
Click to collapse
Dude, how did that work out for you? I flashed RETUS on the TMO ROM, and now I need to switch to the original (TMO), I thought about using the blankflash that appears on lolinet servers, you did the test and could you switch?
I want to flash the TMO rom on my AT&T device.
I have a guess that possibly if I can do that, it will give me a bootloader unlock code that Motorola will accept.
@ArtiicPanda do you think that could work?
@itzimeow do you think it could work?
mingkee said:
I found the hardware is different
US retail is 6/256
T-Mobile/Metro is 4/128
It may have negative impact if you cross flash ROM
Click to expand...
Click to collapse
That may be because the US retail is Mediatek and the TMo version is Qualcomm.
I have the mediatek version and I flash retail just fine.
Wow all you guys are scarring me
All xt2131-1,2,3,4,DL are Qualcomm driven
And RETUS firmware (REtailUS) loaded and CID unlocked are preloaded with US and Canada carrier programs and will work with all north American carrier.
XT2131-3 is ATT firmware and -4 is cricket, all others use -1 firmware as stock.
With the exception of Verizon and ATT branded phone can be reflashed with same or newer RETUS firmware.
Blankflash is akin to a reformat and should only be used if the phone has been corrupted.
Articul8Madness said:
That may be because the US retail is Mediatek and the TMo version is Qualcomm.
I have the mediatek version and I flash retail just fine.
Click to expand...
Click to collapse
Not sure why you guys say T-Mobile/Metro is 4/128. Both T-Mobile and Metro's website list the Moto G Stylus 5G 2022 as 6/128.
Motorola moto g stylus 5G (2022) | 1 color in 128GB | T-Mobile
Meet the moto g stylus 5G featuring a built-in stylus, a 50 MP camera system, a massive 6.8" FHD+ display, and much more. Order today at T-Mobile.
www.t-mobile.com
nookin said:
Not sure why you guys say T-Mobile/Metro is 4/128. Both T-Mobile and Metro's website list the Moto G Stylus 5G 2022 as 6/128.
Motorola moto g stylus 5G (2022) | 1 color in 128GB | T-Mobile
Meet the moto g stylus 5G featuring a built-in stylus, a 50 MP camera system, a massive 6.8" FHD+ display, and much more. Order today at T-Mobile.
www.t-mobile.com
Click to expand...
Click to collapse
This post is about the 2021 model XT2131.
Then the thread should be moved to G Stylus 2021.
nookin said:
Then the thread should be moved to G Stylus 2021.
Click to expand...
Click to collapse
Yeah, right here is where's at.