Ey guys! I really need you help, Im stucked with my Moto X.
I have a Moto X xt1053 with an unlockable bootloader, in the page of motorola says that my phone doesnt qualify to be unlocked.
So, the problem is that I was trying to upgrade to android kitkat 4.4 following the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2545775
All was going good until when I try to flash boot.img, I cant load that file into my phone, So im stucked in the fastboot screen of my phone, because now I cant even get into the TWRP recovery option, just fastboot, I cant load any boot.img file into my phone.
When Im trying to flash the boot.img file, the error that appears in my phone says:
Failed to hab check for boot: 0x56
preflash validation failed for boot
So, what can I do?
Any help?????
THANKS A LOT!!!
What error do you get?
Ctrl-Freak said:
What error do you get?
Click to expand...
Click to collapse
When Im trying to flash the boot.img file, the error that appears in my phone says:
Failed to hab check for boot: 0x56
preflash validation failed for boot
daritoca said:
When Im trying to flash the boot.img file, the error that appears in my phone says:
Failed to hab check for boot: 0x56
preflash validation failed for boot
Click to expand...
Click to collapse
I'm guessing your T-mobile xt-1053 will not accept the boot.img from a AT&T xt-1058 while the bootloader is locked.
First of all, I don't think you are in danger of a 'brick.' You should still be able to flash back to stock 4.2.2, and there are a few tutorials on this subject within this forum.
I have no idea if it would work, but if you want to proceed with an AT&T version of 4.4, you could try flashing the boot.img from the T-mobile 4.4 build. Download "TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip" from http://sbf.droid-developers.org/ghost_rcica/list.php, extract boot.img to your fastboot directory, then proceed. If you 'go this route', you should also use the modem (NON-HLOS.bin) and fsg.mbn from T-mobile.
I also do that, i downloaded the att 4.4 kitkat version and try to flash the boot.img but it doesnt work, no boot.img, no sistem.img
I've been trying with other versions and had same problem.
Sent from my XT890 using xda app-developers app
daritoca said:
I also do that, i downloaded the att 4.4 kitkat version and try to flash the boot.img but it doesnt work, no boot.img, no sistem.img
I've been trying with other versions and had same problem.
Sent from my XT890 using xda app-developers app
Click to expand...
Click to collapse
Just to be clear, did you download and try the T-mobile boot.img ?
Another random thought, are you using the correct motorola fastboot? (I used the "Motorola Fastboot Files" link from this post: http://forum.xda-developers.com/showthread.php?t=2406409, thanks mattlgroff)
No, i havent try the tmobile version.
Ill try in a few hours and tell you the result.
Thanks a lot!!
Sent from my XT890 using xda app-developers app
Cant flash any *.img file because my bootloader is locked, I cant flash any file becuase of that. As long as I know, to flash an *.img file I need to have my bootloader unlocked, Am I right?
daritoca said:
Cant flash any *.img file because my bootloader is locked, I cant flash any file becuase of that. As long as I know, to flash an *.img file I need to have my bootloader unlocked, Am I right?
Click to expand...
Click to collapse
Not exactly. A locked bootloader keeps you from flashing images that are not properly signed. So if you have a T-mobile phone, the bootloader will allow official T-mobile *.img files. An exception to this is that if you upgrade your bootloader to a newer version (by taking an OTA for example), sometimes the newer bootloader will now allow older T-mobile *.img files. That exception should not apply here, as we are discussing kitkat - the latest version of android.
But when I try to flash any boot.img I just cant flash it, I try with t-mobile and I couldnt, right now Im stucked, I dont know what else to do, my phone is dead and I just cant flash any image, right now Im working at night, so it takes me longer to answer and try to restore my phone.
What else I could do if I cant flash any image in my phone, and if in my phone I erased my boot.img file?
daritoca said:
But when I try to flash any boot.img I just cant flash it, I try with t-mobile and I couldnt, right now Im stucked, I dont know what else to do, my phone is dead and I just cant flash any image, right now Im working at night, so it takes me longer to answer and try to restore my phone.
What else I could do if I cant flash any image in my phone, and if in my phone I erased my boot.img file?
Click to expand...
Click to collapse
Flash the T-MOBILE SBF FILE COMPLETELY
Sent from my XT1058 using XDA Premium 4 mobile app
Ok, I'll do that this morning and tell you how it goes.
Thanks!
When Im flashing the T-mobile completely I have an error.
Failed to hab check for boot: 0x56
preflash validation failed for boot
Im doing with RSD Lite 6.1.5
It stops in step 5, cant flash boot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What else can I do?
daritoca said:
When Im flashing the T-mobile completely I have an error.
Failed to hab check for boot: 0x56
preflash validation failed for boot
Im doing with RSD Lite 6.1.5
It stops in step 5, cant flash boot.img
...
What else can I do?
Click to expand...
Click to collapse
I see you tried the T-mobile 4.4 SBF, and once again boot.img didn't work...
In your original post, you mention that you are on a xt-1053. Is that a US T-mobile and not a developer edition? I ask because the evidence suggests your phone is somehow different. If you are on a different version, you need to carefully pick the correct SBF from this list: http://sbf.droid-developers.org/ghost_rcica/list.php Then use RSD to flash it.
If you've flashed the wrong bootloader/partition table, you'll need to manually flash your proper gpt and motoboot and reboot before running the sbf.
Sent from my XT1060 using Tapatalk
arcanexvi said:
If you've flashed the wrong bootloader/partition table, you'll need to manually flash your proper gpt and motoboot and reboot before running the sbf.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Good tip.
Question:
I noticed that boot.img was "step 5" within the OP's RSD lite process, and the previous steps include motoboot.img and gpt.bin (at least they do on my AT&T SBF). I didn't think the bootloader would allow itself to be overwritten with a "wrong" version. Am I mistaken? If so then what, if not the the code within motoboot.img and gpt, checks the signatures of images to be flashed?
Ctrl-Freak said:
Good tip.
Question:
I noticed that boot.img was "step 5" within the OP's RSD lite process, and the previous steps include motoboot.img and gpt.bin (at least they do on my AT&T SBF). I didn't think the bootloader would allow itself to be overwritten with a "wrong" version. Am I mistaken? If so then what, if not the the code within motoboot.img and gpt, checks the signatures of images to be flashed?
Click to expand...
Click to collapse
It flashes them but doesn't reboot before trying to flash the rest usually. If the wrong info is currently loaded, it'll need a reboot first. This is really only an issue for unlocked devices as signature checks will stop you from borking yourself up this badly.
Sent from my XT1060 using Tapatalk
arcanexvi said:
It flashes them but doesn't reboot before trying to flash the rest usually. If the wrong info is currently loaded, it'll need a reboot first. This is really only an issue for unlocked devices as signature checks will stop you from borking yourself up this badly.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Gotcha.
The OP stated they had a locked bootloader. My question:
Is it possible, with a locked bootloader, to flash a "wrong signatured" motoboot and gpt? (I certainly have not tried it, and I assumed it was not possible.)
If the answer is no and the OP had the wrong SBF, then why did the OP's SBF attempt fail on step 5 instead of the earlier motoboot or gpt steps?
If the answer is no and the OP had the right SBF, then why did the SBF fail at all?
Ctrl-Freak said:
Gotcha.
The OP stated they had a locked bootloader. My question:
Is it possible, with a locked bootloader, to flash a "wrong signatured" motoboot and gpt? (I certainly have not tried it, and I assumed it was not possible.)
If the answer is no and the OP had the wrong SBF, then why did the OP's SBF attempt fail on step 5 instead of the earlier motoboot or gpt steps?
If the answer is no and the OP had the right SBF, then why did the SBF fail at all?
Click to expand...
Click to collapse
Some files aren't sig checked or share a sig with a different device. Others are. So it's possible to have a partial failure which leads to headaches.
Sent from my XT1060 using Tapatalk
Thanks a lot for your support, Im doing the flash with the original rom ( fastboot-ghost_amxmx-user-4.2.2-13.9.0Q2.X-116-LCX-26-29-release-keys-cid12-AmericaMovil-MX.tar.gz)
When Im trying to flash it, I got another error.
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
So, thats why I was no trying to flash the original rom, because in the first try to upgrade my phone, I try to upgrade to kit kat 4.4
Answering the question if my device is a developer edition, it isnt, thats one of the reasons I cant unlock my bootloader.
So, any other suggestion?
Related
I made the mistake of flash this file MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip in my AHD AT&T on JB 4.1.1, now when I try to flash, I get this error:
RSDLite: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL.
ATRIX HD: security downgraded version
gpt_main version update failed
preflash validation failed for GPT.
any ideas to fix this?
PD. Excuse my english
How is there a Mexican firmware for this phone??? I haven't seen this phone available in Mexico...
3z3-8917 said:
I made the mistake of flash this file MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip in my AHD AT&T on JB 4.1.1, now when I try to flash, I get this error:
RSDLite: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL.
ATRIX HD: security downgraded version
gpt_main version update failed
preflash validation failed for GPT.
any ideas to fix this?
PD. Excuse my english
Click to expand...
Click to collapse
+1
joel_sinbad said:
How is there a Mexican firmware for this phone??? I haven't seen this phone available in Mexico...
Click to expand...
Click to collapse
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
3z3-8917 said:
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
Click to expand...
Click to collapse
I learned YEARS ago never to flash an sfb\fastboot\odin\whatever if its not made specifically for your device+OS+carrier until the super smarts have determined if the signatures\values are compatible (or wait until a post like this shows up ). Motorola's notorious for setting up sbf's in a way that will brick you, prevent you from ever going back to stock, and\or downgrading. Knowing that, I made a rom from MR instead of flashing the fastboot.
ATRIX HD: security downgraded version -- that line worries me the most, especially if that's what it says if you're trying to flash AT&T now -- It could mean that MR has a higher CG value than AT&T. You'll never be able to install the AT&T fastboot again if that ends up being the case -- you've blown an efuse.
I'm gonna need some more details: Did the MR flash fully finish the first time used? If it fully finished and didn't boot or loops, do a factory reset in the stock reocovery. You could also try to unlock the bootloader (worth a shot at any rate) -- seems like you still have fastboot access so its at least worth trying -- it would be great if MR is the secret fastboot that unlocks us (I mean, the rom itself has no entitlement checking whatsoever, maybe its bootloader doesn't either...)
.
Can you still access SS or does it boot directly into fastboot\stock recovery? . If fastboot only, try flashing just the boot.img from the fastboot (probably won't work if an efuse has been blown). If you still have SS then we can put the boot.img in a zip and flash that -- its how we safely tested Defy sbf's without blowing an efuse.
After trying all of the above and if none of them work you should attempt flashing the Bell JB fasboot as a last ditch effort.
loading into fastboot only with error "flash failure"
marshok said:
loading into fastboot only with error "flash failure"
Click to expand...
Click to collapse
I'm not really sure what to tell you. You could try flashing just AT&T boot.img and devtree....Maybe make a hybrid fastboot, replace what fails during the AT&T flash with files from the MR fastboot (and modify the xml accordingly). Since it seems you're using the MR fastboot menu it, trying the unlock command is worth a shot.
All my other suggestions involve trying to connect directly to the nand and manually dd in the mbr and such -- I've never even tried connecting to my phone like that, so you'll have to search for those methods on your own, sorry. You'll also be diving in to full on brick territory too. You're just semi bricked, so you can still get lucky if you don't change that.
There is still hope (maybe) -- Apparently 4.2 is in testing and a fastboot should pop up for it before or after it's released. If its like every other major sbf\fastboot release I've seen it should have higher signatures\cg values and could possibly be a fix for you. That's all an assumption, but its based on credible rumor (a Mattlgroff post) and Motorola's past actions. The point is -- You still have access to fastboot, don't do anything to screw that up because your needed fix might not be available yet.
Or you could send in your phone for warranty; check Motorola's website to see if your still covered under factory warranty -- I am and my phone is a 99 cent refurbished model -- I still have 11 months left You get 12-24 months coverage when you register (length depends on New or Refurb). I was truthful on my Purchase Date, but I suppose you could lie and say you just recently bought it and it quit working when you started to upgrade it.
Did the MR flash fully finish the first time used?
Click to expand...
Click to collapse
no the flashing not completed, I got the error just flash boot.img
You could also try to unlock the bootloader (worth a shot at any rate) -- seems like you still have fastboot access so its at least worth trying -- it would be great if MR is the secret fastboot that unlocks us (I mean, the rom itself has no entitlement checking whatsoever, maybe its bootloader doesn't either...)
Click to expand...
Click to collapse
how I can do this? when my AHD is briked
Can you still access SS or does it boot directly into fastboot\stock recovery? . If fastboot only, try flashing just the boot.img from the fastboot (probably won't work if an efuse has been blown). If you still have SS then we can put the boot.img in a zip and flash that -- its how we safely tested Defy sbf's without blowing an efuse.
Click to expand...
Click to collapse
if boot directly into fastboot and I have acces stock recovery
After trying all of the above and if none of them work you should attempt flashing the Bell JB fasboot as a last ditch effort.
Click to expand...
Click to collapse
I try flash Bell JB fasboot and I get the same error
thanks for your help skeevy420
PD. Excuse my english
del
3z3-8917
How do you help skeevy420?
you have restored your phone after flashing on MB886_niimx-user-4.1.2-9.8.2Q-50_MB886?
In the same boat
Hey guys I'm in the same boat. I rooted my Atrix HD and was happy until I installed busy box 9.2, which managed to overwrite /system/bin and I don't know what else I could no longer mount/remount, change w/r in root, use the ls or many other commands and wifi, mobile data, bluetooth, or OS factory reset all gone.
I should have made a copy of my system before doing anything else but I went ahead and used the boot menu recovery, which didn't do anything to help the problem.
I then flashed the MR rom with RSD Light in an attempt to recovery my phone, it was 4.1.2 and seemed like a good (hindsight horrible) idea at the time.
Now I can fastboot flash recovery images from att JB but it does no good because the boot partition fails. The RSD Light MR boot flash failed but somehow the security version stuck, and the Bell 4.1.2, Att 4.1.1, and 7.7.1Q-144, roms boot.img all return Partition (boot) Security Version Downgraded. If anyone knows a way around this please let me know.
It seems kind of tragic that Dan's bootloader unlocking came out, pretty much the day after I got stuck in this locked bootloader loop
You have to use a special xml, unzip your stock-rom replace the old xml with this one: for ICS and this one for JB.
Then try to flash it again with https://www.box.com/s/cmoz84iachug77tghdlo version of rsd lite. Make sure you have these latest drivers.
3z3-8917 said:
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
Click to expand...
Click to collapse
it can fix?????? i did the same flash at my atrix hd
rorrito said:
it can fix?????? i did the same flash at my atrix hd
Click to expand...
Click to collapse
for the moment it's not possible, wait bootloader unlock tool for AHD briked....
Codex01 said:
You have to use a special xml, unzip your stock-rom replace the old xml with this one: for ICS and this one for
JB
Then try to flash it again with this version of rsd lite. Make sure you have these latest drivers.
Click to expand...
Click to collapse
Ok downloaded the JB you linked and upgraded from RSD Light 6.1.4 to 6.1.5, I edited the XML to remove getvar, and ran RSD Light but it still fails on step 1.
"Failed Flashing Process 1/23 "gpt_main0.bin -> Phone returned FAIL."
On the Phone "preflash validation failed for gpt_main0.bin"
The only stock rom that made it past step 1 has been the MR that bricked my phone, so I replaced the system.img, boot.img, and recovery.img of the MR with the JB 4.1.1 you linked but it still fails at step 15, flashing boot.img. Preflash validation falure
BRICK AHD
Exactly same situation here, Flashing Mexican Firmware.
Now i got Partition (Boot) Security Version Downgraded
Hope it can be fixed:crying:
fix fail on part 1 rsd
use the stickyboot fix from general got it from skeevydude it works, try using mythtools after!
ickysjazz said:
Exactly same situation here, Flashing Mexican Firmware.
Now i got Partition (Boot) Security Version Downgraded
Hope it can be fixed:crying:
Click to expand...
Click to collapse
Shame on me :S
Well, I just bricked an ATT AHD in the same manner, trying to flash the Mexican JB version (I bought 3 of this phones to sell here in Mexico and wanted them to look as the phones they sell here by replacing the broken digitizers with ones with no ATT logo and flashing local firmware) ...But yeah, I made a big mistake, I wasn't aware I had to unlock BL before flashing other carrier SBF's... :S At least I've learned from this and didn't made the same mistake with the other 2 AHD's I have (And I'm planning to go back to stock and deodex em' because Mex fw isnt working pretty well on this AHD's...)
Trying to repair this thing by reflashing ATT JB stock fw... RSD & Myth seem not to work;
-In RSD I can't even get past step 1/23 (flash partition "gtp_main0.bin" failed"); when trying to flash Mexican rom I got to step 15/23 till I got the error.
-In Myth It looks like some files get flashed (It even gets me to the "Load Recovery" option, I obviously choose Stock as I don't want to f'up the phone even more ) and then "finishes" but when rebooting, shows "Dual Core tech" bootscreen and sends me back to Fastboot (Reason: Sticky bit factory_fastboot), tried stickyboot solution on cmd and then reflash on myth, same result.
Also I get the messages "downgraded security version" and "Invalid PIV Image: System" in AHD Fastboot. I don't know what else to do now, I still haven't tried Bell rom as I think I'll mess things up even more so I've stayed away from it At this point I guess I'm pretty much f***ed...
@ickysjazz
@vananucho
You're using the wrong fastboot...I can tell that by the error code...use snapdragon fastboots...those are the only ones for us to use. Any other fastboot will result in errors.
So Download those
DL Mex Retail
Extract it
Open terminal to that extracted directory
Do the sticky_bit fix.
Do these commands in this order
Code:
fastboot flash partition gpt_main0.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash cdrom cdrom
fastboot erase cache
fastboot erase userdata
And that's how you manually flash a fastboot. I've never used MythTools or RSD. That is how I do it, always have done it, always will do it -- with the same fastboot linked above with same commands posted. Those are for Mex Retail, but should work on any JB fastboot...ICS fastboots need a few minor tweaks.
Do the fastboot commands as root on Linux or as a Windows Admin (set the admin privileges for the app in the right click properties menu)
Replaced the fastboot with the one provided by Skeevydude and still get the same error but I guess it's due to the fact that I'm running out of battery (Started showing low bat advice after 3rd failed attempt, using regular cable), I'll try this again as soon as I make a flashing cable, I'll keep updated!
Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
s code showed up in the picture.
Thanks for all,
Bruno Sastre.
BrunoX10 said:
Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
s code showed up in the picture.
Thanks for all,
Bruno Sastre.
Click to expand...
Click to collapse
Whoa buddy!!
As sad as this is, we have warnings posted in nearly every sub-forum in the Moto X section warning you not to downgrade.
Fortunately, you can still access fastboot so you MIGHT still have some hope, but it is hard telling.
Since the 4.4.3 full SBF for Brazil Retail has not been leaked it is going to be much trickier....
Here is my suggestion:
First, you say you tried to "downgrade" to 4.4.2, so this leads me to believe that you had the 4.4.3 Brazil Retail OTA on your phone.
Find a copy of the 4.4.2 brazil Retail OTA, and extract it. You will also need the entire 4.4.2 Brazil Retail SBF file (and VERIFY THE CHECKSUMS to make sure you do not have corrupted files).
I suggest you extract "gpt.bin" from the 4.4.3 OTA, and extract "motoboot.img" from the 4.4.2 OTA.
Now a little explaination: gpt.bin is "GUID Partition Table". Since we KNOW that you cannot attempt to downgrade gpt.bin OR Motoboot, we are using the MOST RECENT versions of both. The 4.4.3 OTA contained a new gpt.bin, but the most recent bootloader is still the 4.4.2 version.
The idea here is to flash JUST gpt.bin and motoboot.img, then immediately REBOOT, so that the bootloader can LOAD the new partition table BEFORE we flash any other partitions. Give it a shot:
mfastboot flash partition gpt.bin (USE GPT.BIN FROM THE 4.4.3 OTA FILE)
mfastboot flash bootloader motoboot.img
mfastboot reboot-bootloader
NOW, the following fastboot flash commands using the files from the 4.4.2 Brazil Retail SBF:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
now reboot, assuming you were even able to get this far..... Your X already appears to be in awful shape, so I don't see how any of this could hurt you, but it just MIGHT work....
If this works, and you are actually able to get booted into android, DO NOT ACCEPT THE OTA. Doing so will possibly brick you again.
Instead, just wait until the full leaked 4.4.3 SBF is released, and THEN, you can consider trying to flash the ENTIRE 4.4.3 SBF, if you want to upgrade.
samwathegreat said:
Whoa buddy!!
As sad as this is, we have warnings posted in nearly every sub-forum in the Moto X section warning you not to downgrade.
Fortunately, you can still access fastboot so you MIGHT still have some hope, but it is hard telling.
Since the 4.4.3 full SBF for Brazil Retail has not been leaked it is going to be much trickier....
Here is my suggestion:
First, you say you tried to "downgrade" to 4.4.2, so this leads me to believe that you had the 4.4.3 Brazil Retail OTA on your phone.
Find a copy of the 4.4.2 brazil Retail OTA, and extract it. You will also need the entire 4.4.2 Brazil Retail SBF file (and VERIFY THE CHECKSUMS to make sure you do not have corrupted files).
I suggest you extract "gpt.bin" from the 4.4.3 OTA, and extract "motoboot.img" from the 4.4.2 OTA.
Now a little explaination: gpt.bin is "GUID Partition Table". Since we KNOW that you cannot attempt to downgrade gpt.bin OR Motoboot, we are using the MOST RECENT versions of both. The 4.4.3 OTA contained a new gpt.bin, but the most recent bootloader is still the 4.4.2 version.
The idea here is to flash JUST gpt.bin and motoboot.img, then immediately REBOOT, so that the bootloader can LOAD the new partition table BEFORE we flash any other partitions. Give it a shot:
mfastboot flash partition gpt.bin (USE GPT.BIN FROM THE 4.4.3 OTA FILE)
mfastboot flash bootloader motoboot.img
mfastboot reboot-bootloader
NOW, the following fastboot flash commands using the files from the 4.4.2 Brazil Retail SBF:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
now reboot, assuming you were even able to get this far..... Your X already appears to be in awful shape, so I don't see how any of this could hurt you, but it just MIGHT work....
If this works, and you are actually able to get booted into android, DO NOT ACCEPT THE OTA. Doing so will possibly brick you again.
Instead, just wait until the full leaked 4.4.3 SBF is released, and THEN, you can consider trying to flash the ENTIRE 4.4.3 SBF, if you want to upgrade.
Click to expand...
Click to collapse
Since he's international, couldn't he unlock the bootloader and reflash the software image?
sivarticus85 said:
Since he's international, couldn't he unlock the bootloader and reflash the software image?
Click to expand...
Click to collapse
That's not what's at issue here. You don't even need to be unlocked to flash stock firmware because it is signed with release keys.
The issue is that he tried to downgrade. Read the stickies and you should understand.
samwathegreat said:
That's not what's at issue here. You don't even need to be unlocked to flash stock firmware because it is signed with release keys.
The issue is that he tried to downgrade. Read the stickies and you should understand.
Click to expand...
Click to collapse
I know he was trying to downgrade, but I didn't realize what had happened until I re-read his post. I get it now. I think what you suggested should do the trick.
Still working [I hope]
BrunoX10 said:
Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
s code showed up in the picture.
Thanks for all,
Bruno Sastre.
Click to expand...
Click to collapse
Hi Guys,
Master Samwathegreat!!!
I did flash gpt.bin from 4.4.3 OTA Retail BR and went fine but when I tryed motoboot.img - prompts says:
"(bootloader) Variable not supported!
target max-download-size: 768
sending 'bootloader' (1604 KB)...
OKAY [time]
writing 'bootloader' . . .
(bootloader) Permission denied
FAILED (remote failure)
finished. total time..."
So now I'm getting many firmwares to try flash motoboot.
Thanks for it man, I am still working on it and I ll send good news!! I hope.
BrunoX10 said:
Hi Guys,
Master Samwathegreat!!!
I did flash gpt.bin from 4.4.3 OTA Retail BR and went fine but when I tryed motoboot.img - prompts says:
"(bootloader) Variable not supported!
target max-download-size: 768
sending 'bootloader' (1604 KB)...
OKAY [time]
writing 'bootloader' . . .
(bootloader) Permission denied
FAILED (remote failure)
finished. total time..."
So now I'm getting many firmwares to try flash motoboot.
Thanks for it man, I am still working on it and I ll send good news!! I hope.
Click to expand...
Click to collapse
Try skipping that command. Can you run any of the other fastboot flash commands?
Definitely use caution. I recommend you don't try downgrading the bootloader.
Bad Feelings...
samwathegreat said:
Try skipping that command. Can you run any of the other fastboot flash commands?
Definitely use caution. I recommend you don't try downgrading the bootloader.
Click to expand...
Click to collapse
===================================================================================================
NOPE MAN!
Tryed others flash commands and no one hits.
at the same time, I got and tryed "TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml" too, but without sucess =///
RSD Lite + W8 sucks, cannot find device - and I m going to wallmart tomorow, one week stucked on it... no one desires...
Thank you Xda.
BrunoX10 said:
===================================================================================================
NOPE MAN!
Tryed others flash commands and no one hits.
at the same time, I got and tryed "TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml" too, but without sucess =///
RSD Lite + W8 sucks, cannot find device - and I m going to wallmart tomorow, one week stucked on it... no one desires...
Thank you Xda.
Click to expand...
Click to collapse
Can you tell me what error you get when you type, for instance:
fastboot flash system system.img
Good News - We made it!!!
samwathegreat said:
Can you tell me what error you get when you type, for instance:
fastboot flash system system.img
Click to expand...
Click to collapse
Yahh Man, you´r the one!
I´d just took a coffe [got high] and remake, prompt by prompt on new firmware downloaded from sbrf.
So we made it guys, the MX rebooted normaly and I really dont know how but worths as you said, skipping commands.
Thank you Samwathegreat!:good:
Thank you XDA Family.
BrunoX10 said:
Yahh Man, you´r the one!
I´d just took a coffe [got high] and remake, prompt by prompt on new firmware downloaded from sbrf.
So we made it guys, the MX rebooted normaly and I really dont know how but worths as you said, skipping commands.
Thank you Samwathegreat!:good:
Thank you XDA Family.
Click to expand...
Click to collapse
F-A-N-T-A-S-T-I-C !!!
I'm very glad you had success :highfive: (High-Five)
EDIT: @BrunoX10 can you read this post: http://forum.xda-developers.com/moto-x/moto-x-qa/request-twrp-backup-brazil-retail-t2817522
This user needs your help! He is also using Brazil Retail 4.4.3 and accidently erased /system
Can you help him by making a backup of /system and sharing?
Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.
jrmaiafs said:
Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.
Click to expand...
Click to collapse
You still have twrp right. So a easy way is to download a toolkit from the moto x 2014 thread onto your PC and install it. Then boot your phone into bootloader/fastboot and make sure you also install the moto drivers which the toolkit will ask you to do. Then just follow directions using the toolkit and you will be back up n running. Or you can sideload a rom onto twrp using the 1.0.3.2 version of adb drivers. I have done it successfully many times using Linux but with Linux you just have to type a ./ in front of adb sideload rom.zip for it to work. Just don't worry. As long as you have a bootloader then your phone is never bricked. Toolkit is below...
http://forum.xda-developers.com/showthread.php?t=2897819
im glad to know that "As long as you have a bootloader then your phone is never bric
skulldreamz said:
You still have twrp right. So a easy way is to download a toolkit from the moto x 2014 thread onto your PC and install it. Then boot your phone into bootloader/fastboot and make sure you also install the moto drivers which the toolkit will ask you to do. Then just follow directions using the toolkit and you will be back up n running. Or you can sideload a rom onto twrp using the 1.0.3.2 version of adb drivers. I have done it successfully many times using Linux but with Linux you just have to type a ./ in front of adb sideload rom.zip for it to work. Just don't worry. As long as you have a bootloader then your phone is never bricked. Toolkit is below...
http://forum.xda-developers.com/showthread.php?t=2897819
Click to expand...
Click to collapse
Thank you for your help, but i dont have anymore twrp, and my phone is xt 1097, im glad to know that "As long as you have a bootloader then your phone is never bricked." i have it still!!
Now RSD Lite recognizes my phone, but when i start to flash android 5.0 it says: version downgraded for primary_gpt
I flash this same rom (5.0) before using RSD Lite and it worked perfectly, but now gives this error. How can i fix it?
Have you got your factory image for your phone and mfastboot?
yes, i have it
orangestrawberry said:
Have you got your factory image for your phone and mfastboot?
Click to expand...
Click to collapse
I heard many people reporting this error, say they have posts here on xda that solves the problem but I could not find them . I have seen in a blog that the problem is in doing downgrading from 5.0 to 5.1. and they say that to solve it is necessary to change two lines of a file , but I do not know which file is this , and not how it's done
jrmaiafs said:
Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.
Click to expand...
Click to collapse
Can you get into bootloader mode (fastboot)? What version of the bootloader are you running (you can see this in bootloader mode)?
I have bootloader (fastboot)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JulesJam said:
Can you get into bootloader mode (fastboot)? What version of the bootloader are you running (you can see this in bootloader mode)?
Click to expand...
Click to collapse
these are the information appearing:
So I try to install the rom 5.0 with RSD Lite this error occurs :
And that's what the RSD Lite says :
I was using the soak test 5.1 V : 23:11:14 , and went back to retail by 5.0 RSD Lite 6.2.4 , and is giving the following error "version is downgraded primary- gpt "
jrmaiafs said:
I was using the soak test 5.1 V : 23:11:14 , and went back to retail by 5.0 RSD Lite 6.2.4 , and is giving the following error "version is downgraded primary- gpt "
Click to expand...
Click to collapse
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.
Thank you
JulesJam said:
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.
Click to expand...
Click to collapse
There was no time I try your solution because I was looking for other answers before I saw your comment , I found the solution in this blog , anyway thanks for the help . but it is in Portuguese
http://motox-brasil.blogspot.com.br...howComment=1433025924130#c6945390347560261007
jrmaiafs said:
There was no time I try your solution because I was looking for other answers before I saw your comment , I found the solution in this blog , anyway thanks for the help . but it is in Portuguese
http://motox-brasil.blogspot.com.br...howComment=1433025924130#c6945390347560261007
Click to expand...
Click to collapse
Ok but all that says to do is to flash the 5.0 firmware with RSDLite. I thought that was what you were trying to do and were getting an error?
JulesJam said:
Ok but all that says to do is to flash the 5.0 firmware with RSDLite. I thought that was what you were trying to do and were getting an error?
Click to expand...
Click to collapse
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk
3rdstring said:
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ah, got it.
So I am having this exact problem now and I think somewhere along the way I flashed files from the wrong version and now my phones seems to not recognize the system storage or doesn't know how to write to it. My bootloader is 60.18....I've tried the system files for 5.1 and 6.0 but nothing seems to work. After I enter all of the commands it just reboots over and over and says erasing...
really strange
JulesJam said:
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.
Click to expand...
Click to collapse
KB Smoka said:
So I am having this exact problem now and I think somewhere along the way I flashed files from the wrong version and now my phones seems to not recognize the system storage or doesn't know how to write to it. My bootloader is 60.18....I've tried the system files for 5.1 and 6.0 but nothing seems to work. After I enter all of the commands it just reboots over and over and says erasing...
really strange
Click to expand...
Click to collapse
Is your bootloader unlocked? Last I read you could get the Verizon Moto X 2014 bootloader unlocked.
You can get into bootloader mode and use fastboot commands, correct?
3rdstring said:
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Hi there 3rdstring, I don't suppose you could translate it to English for us, could you? Or I guess I can see if Google Chrome will do that.
Dangerous-Beans! said:
Hi there 3rdstring, I don't suppose you could translate it to English for us, could you? Or I guess I can see if Google Chrome will do that.
Click to expand...
Click to collapse
No worries, Chrome did the translating fine. )
Hey guys, for those of you who have bricked your phone by upgrading to Oreo then tried downgrading to nougat, I may have a fix for you. Also news that Android O can be installed on Sprint (and possibly locked bootloader variants too). I'm going to sleep now, I'll post a couple tutorials tomorrow when I get home from work but I wanted to give you guys a little sneak peak of what I've discovered.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: also, this is running buttery smooth for me. Which leads to believe those of you having performance issues with O it's probably due to some carrier apps/features, which would be in the OEM partition. Side note, this is a retail rom, which means no carrier bloat/features. This is as if you were to buy it unlocked straight from Motorola. This also means I have no VoWiFi on Sprint. If anyone could find a way to implement this in O that would be awesome.
Sent from my Moto Z (2) using Tapatalk
already flashed retail O on Sprint and now looking for root solution
HugeUFO said:
already flashed retail O on Sprint and now looking for root solution
Click to expand...
Click to collapse
Did flashing magisk not work?
donjuro said:
Did flashing magisk not work?
Click to expand...
Click to collapse
nope, I never tried Magisk before. And a complete backup needs root access, but to gain root access I need Magisk, which recommends a backup[emoji23]
通过我的 Moto Z (2) 上的 Tapatalk发言
donjuro said:
I'll post a couple tutorials tomorrow
Click to expand...
Click to collapse
Great, looking forward to it.
HugeUFO said:
nope, I never tried Magisk before. And a complete backup needs root access, but to gain root access I need Magisk, which recommends a backup[emoji23]
通过我的 Moto Z (2) 上的 Tapatalk发言
Click to expand...
Click to collapse
You don't need root access to backup with twrp
donjuro said:
You don't need root access to backup with twrp
Click to expand...
Click to collapse
Oh thanks, I will try to flash a twrp to backup.
donjuro Please come back to as if you will find moment. We are still waiting.
Hey guys, sorry I've been gone for so long. Life really kicks your ass sometimes
Anyways, it looks like just about every carrier is on 8.0 now except Sprint, but if you're on another carrier yet you still haven't been upgraded you could try this too.
So basically all you have to do is download NASH_RETAIL_8.0.0_OPX27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from one of these two mirrors.
https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/
https://mirrors.lolinet.com/firmware/moto/nash/official/
Unpackage the zip file, and inside the folder create a flashall.bat, here is what you will put in the bat file
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Save it, put your phone in fastboot mode, run it, and that should be it. You might want to make a backup of any valuable files first though as this WILL erase everything and will start you from scratch!
For those of you wanting to keep your carrier specific features, you can use your carrier specific files from any of these mirrors, but for stability purposes I highly recommend using the RETAIL version.
robdevil said:
donjuro Please come back to as if you will find moment. We are still waiting.
Click to expand...
Click to collapse
what is the issue you are having?
thanks mate, and wanna ask for twrp backup issue, anyone have issue for restore from twrp,
i've got bootloop after TWRP restore, (was working before backup)
once android O stable, I can upgrade to O asap, thanks again
ilovemeow said:
thanks mate, and wanna ask for twrp backup issue, anyone have issue for restore from twrp,
i've got bootloop after TWRP restore, (was working before backup)
once android O stable, I can upgrade to O asap, thanks again
Click to expand...
Click to collapse
If it is just restarting into TWRP over and over, you might just need to switch to a different slot. It is there in the reboot area of TWRP.
JAWheat411 said:
If it is just restarting into TWRP over and over, you might just need to switch to a different slot. It is there in the reboot area of TWRP.
Click to expand...
Click to collapse
hmm, not really restarting into twrp,
i pass the twrp, reboot itself before "hellomoto" screen appear
Are you able to reflash the stock boot image in bootloader?
Help Please.
donjuro said:
Hey guys, for those of you who have bricked your phone by upgrading to Oreo then tried downgrading to nougat, I may have a fix for you. Also news that Android O can be installed on Sprint (and possibly locked bootloader variants too). I'm going to sleep now, I'll post a couple tutorials tomorrow when I get home from work but I wanted to give you guys a little sneak peak of what I've discovered.
Edit: also, this is running buttery smooth for me. Which leads to believe those of you having performance issues with O it's probably due to some carrier apps/features, which would be in the OEM partition. Side note, this is a retail rom, which means no carrier bloat/features. This is as if you were to buy it unlocked straight from Motorola. This also means I have no VoWiFi on Sprint. If anyone could find a way to implement this in O that would be awesome.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
So i have a T-Mobile variant and I attempted to root and got a bootloop. SO i surfed the web and found this. Downloaded firmware from the 3nd site you linked, did everything else as well and I don't have wifi or mobile data. Please help
AsapJuno said:
So i have a T-Mobile variant and I attempted to root and got a bootloop. SO i surfed the web and found this. Downloaded firmware from the 3nd site you linked, did everything else as well and I don't have wifi or mobile data. Please help
Click to expand...
Click to collapse
What version does your baseband say?
Sent from my Moto Z (2) using Tapatalk
donjuro said:
What version does your baseband say?
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
It says unknown now
AsapJuno said:
It says unknown now
Click to expand...
Click to collapse
Well, you're kind of in for a bad time now... The "official" tmobile oreo zip that's out there flashes fine but then you end up with no baseband.
@MootNewt made a zip here: https://forum.xda-developers.com/z2-force/help/t-mobile-oreo-flashall-t3755086/post75810018
that will flash to the latest tmobile oreo (with feb update) but you'll end up not passing safetynet, even with Magisk.
You will have root via Magisk, though, so there's that.
This is where I am right now. :/
AsapJuno said:
It says unknown now
Click to expand...
Click to collapse
Also if it helps here is a T-Mobile flash all to the latest firmware. https://drive.google.com/file/d/153BdClEOK3ZzpgiM37Ti4Y8lkyXPcz0S/view?usp=sharing
Just run the flash all bat file while your phone is in bootloader mode. This will wipe everything, just a fair warning. I am using this now. No problems with safety net here.
JAWheat411 said:
Also if it helps here is a T-Mobile flash all to the latest firmware. https://drive.google.com/file/d/153BdClEOK3ZzpgiM37Ti4Y8lkyXPcz0S/view?usp=sharing
Just run the flash all bat file while your phone is in bootloader mode. This will wipe everything, just a fair warning. I am using this now. No problems with safety net here.
Click to expand...
Click to collapse
Are you saying that it's got the 27.1 update and it passes safetynet?
e: AND it doesn't eat your baseband?
Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.
androidyeah... said:
Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.
Click to expand...
Click to collapse
Did you try to recover your phone using HiSuite? Boot into fastboot mode and then repair phone via HiSuite. This will flash you back to latest official firmware for your model. Please be aware you will lose your data.
Sent from my SM-N960F via Tapatalk
zencooler said:
Did you try to recover your phone using HiSuite? Boot into fastboot mode and then repair phone via HiSuite. This will flash you back to latest official firmware for your model. Please be aware you will lose your data.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for replying. I've just tried that and it says 'Your system is not supported for recovery'.
Maybe try to flash via host otg.
Wysłane z mojego CLT-L29 przy użyciu Tapatalka
cielik said:
Maybe try to flash via host otg.
Wysłane z mojego CLT-L29 przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks, I've read about that method too, but the only download I have doesnt have a 'dload' folder when i extract it as required in this post (4 posts down)? Its the b270 firmware.
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085
I've just bought a pass with funky hauwei only to find out the tool doesn't work anymore
Some guy there suggested 'flashing every partition from the update.app and seeing if anything changes. Some will flash and others will fail but it’s a good first step'. I don't know what that means exactly, is that everything in the update.app? He hasn't replied yet....
androidyeah... said:
Thanks, I've read about that method too, but the only download I have doesnt have a 'dload' folder when i extract it as required in this post (4 posts down)? Its the b270 firmware.
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085
I've just bought a pass with funky hauwei only to find out the tool doesn't work anymore
Some guy there suggested 'flashing every partition from the update.app and seeing if anything changes. Some will flash and others will fail but it’s a good first step'. I don't know what that means exactly, is that everything in the update.app? He hasn't replied yet....
Click to expand...
Click to collapse
I have just spent my day off trying to fix this phone, never again!! I finally found a fix from this post
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085/page11#post79395575
I flashed cache, kernel, cust and system images from the update.app file and rebooted and the phone came back up good as new. Thanks for the replies, maybe this might help someone else in a simialar boat sometime. :victory:
Try to use the Flash TOOL of this post, it always works with me.
https://forum.xda-developers.com/hu...awei-p20-pro-charlotte-l29c432b131-8-t3809964
androidyeah... said:
Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.
Click to expand...
Click to collapse
Try to use OTG dload method.
If you need firmware and help tell me!
I had this problem on my EML-L29, tjis helped me:
factory reset
wipe cache
fastboot erase system
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
Yeah, similar to what I had to do. Factory reset wasn't possible for me, but flashing partitions worked.
Bricked P20 Pro
I also managed to brick my phone flashing twrp.
except I can't access adb or fastboot now.
Not really sure how to go from here to restore my phone.
Wrong section. Can this be moved please.
I thought there was a new ROM thread..
Rustyrobotguy said:
I also managed to brick my phone flashing twrp.
except I can't access adb or fastboot now.
Not really sure how to go from here to restore my phone.
Click to expand...
Click to collapse
You can always go into fastboot mode in emergency mode.
Just connect the phone to PC via USB cable and then press power key + Volume Down.
It will bring you into Fastboot Emergency.
Then you can play with fastboot commands.
I recommend you to extract RECOVERY_RAMDIS.img from UPDATE.APP (you can get it from update.zip file for your firmware) into a folder that keeps your fastboot exe file. Then do following command on your PC:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
It will give you stock recovery.
Then you can do command:
fastboot reboot
Immediately after this command disconnect USB cable and press Volume Up key.
On recovery you can do wiping your data partition and don't he factory reset.
If it not help and you are still on boot loop you can go again into fastboot emergency mode and do fastboot command:
fastboot -w
This will reformat your data partition and after this your phone will boot into erecovery to do factory reset again. It should help you to bring your phone into live.
Regards.
Sent from my SM-N960F via Tapatalk
androidyeah... said:
I have just spent my day off trying to fix this phone, never again!! I finally found a fix from this post
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085/page11#post79395575
I flashed cache, kernel, cust and system images from the update.app file and rebooted and the phone came back up good as new. Thanks for the replies, maybe this might help someone else in a simialar boat sometime. :victory:
Click to expand...
Click to collapse
How were you able to extract files from the update.app?
I'm using Huawei Update Extractor 0.9.9.5 (and 0.9.9.3) and I keep getting error: "Recovery_ramdisk.img: Invalid header crc - Expected:11007 Got 48874"
Update:
I figured out how to extract the files, but every time I try any fastboot commands I keep getting the below error, any ideas??
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.696s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
Finished. Total time: 1.729s
thoughtless22 said:
How were you able to extract files from the update.app?
I'm using Huawei Update Extractor 0.9.9.5 (and 0.9.9.3) and I keep getting error: "Recovery_ramdisk.img: Invalid header crc - Expected:11007 Got 48874"
Update:
I figured out how to extract the files, but every time I try any fastboot commands I keep getting the below error, any ideas??
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.696s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
Finished. Total time: 1.729s
Click to expand...
Click to collapse
Bootloader must be unlocked. Only then you can flash recovery.
But be careful and do not try to flash Oreo rom over the Pie because you can definitely brick your phone (even if you read somewhere that it's possible).
Sent from my SM-N960F via Tapatalk
zencooler said:
Bootloader must be unlocked. Only then you can flash recovery.
But be careful and do not try to flash Oreo rom over the Pie because you can definitely brick your phone (even if you read somewhere that it's possible).
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?
thoughtless22 said:
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?
Click to expand...
Click to collapse
Same Problem for me. cant find any way to get this to work.. my Phone is bricked 2 month now i miss it lol
does anyone have a Solution for this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thoughtless22 said:
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?
Click to expand...
Click to collapse
Try thoes command in fastboot:
HTML:
fastboot getvar rescue_phoneinfo
fastboot oem get-product-model
fastboot oem get-psid
fastboot getvar vendorcountry
fastboot oem get-build-number
if it returns something weird, then you are fvcked up.
mine messed up once, I had to get to Service Center to replace the motherboard.
Maybe, now there is some 3rd party way can save you phone, I don't know.