Related
Hi Guys,
I am a noob and tried to ulock bootloader and flash new rom, I now have an issue, please advise
I successfully flashed bootloader, I then rooted using RAZRI_Root_Windows. I then installed RSD 5.7, downloaded Retail GB rom from (http://sbf.droid-developers.org/smi/list.php), as I am currently on Orange branded and want unbranded. During the flash process I got an error when RSD was installing system_signed, stating it had failed. I then tried to reboot and now my phone can only go into fastboot and I cannot use any of the menus in fastboot. This is what I see in fastboot:
AP fastboot flash moide (secure boot)
20.00 (sha - oba4DF3)
IFWI info
eMMC info
battery (okay)
connect USB data Cable
ROM-key : motorola -key
Boot mode selection menu:
- normale powerup
- recovery
- factory
- BP tools
- switch console [default: null]
- power of "
And, it's written in yellow :
" fastboot reason : flash failure
fastboot : max download size: 100MB "
I think the problem is the max download size as when I try to manually flash the system_signed file in command I get the following error message. Sending system (795017)
(bootloader) data too large
failed remote failure
Can I resize the repartition manually??
Any help would be welcome
http://forum.xda-developers.com/showthread.php?p=36612151
Sent from my XT910
HSD-Pilot said:
http://forum.xda-developers.com/showthread.php?p=36612151
Sent from my XT910
Click to expand...
Click to collapse
Yeah thanks. I downloaded RSD 6.4.1 and i flashed a rom no problem :good::good:
ETA
grampsharry said:
Yeah thanks. I downloaded RSD 6.4.1 and i flashed a rom no problem :good::good:
Click to expand...
Click to collapse
hi guys, with RSD lite 6.1.4 and rom FW for XT890 from Argentina what is the time of the process, because stack in Flashing radio...
Thanks!
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!
Hey guys, I'm about to cry :crying: - hope somebody knows a fix :highfive:
To keep it short, what I've done:
Unlocked my bootloader and installed CWM Recovery.
Everything worked.
Then... lastly I wanted to remove the "Bootloader Unlocked message/image"... and flashed a different logo using following this guide http://forum.xda-developers.com/showthread.php?t=1980139 (which was not intended for the XT890 and JB - rolleyes)
Code:
fastboot flash logo [path to the logo.bin i downloaded]
and it returned
Code:
[B]"None signed image detected. Fastboot command failed.[/B]
Now my XT890 JB 4.1.2 EU stays at the "Bootloader Unlocked Screen" when i try to boot (choosing Recovery, Factory etc from AP).
I'm - as you probably can tell already - NOT an expert, but my hope is: I can "fix" it by flashing the logo again with the original/or compatible logo.bin. (incase this should be possible please provide me with a link to it)
Thanks in advance for any input.
Everything works again
I downloaded the proper stock firmware from here http://forum.xda-developers.com/showthread.php?t=2239706, extracted the logo_signed and ulogo_signed, and then "reflashed" the logo_signed using (again)
Code:
fastboot flash logo [path to the logo_signed file]
My next try would have been flashing the ulogo_signed file, but since everything worked out, I'll surely skip that.
PS: Unless someone suggests, that I also should flash the ulogo_signed file (which somehow I doubt)
Pinky-swear: From now on I'll read the whole threads before doing "anything" and I try to avoid doing "anything" on top
Cheers.
Yesterday my moto x alerted me that the KitKat update had been downloaded and was ready to install. I selected INSTALL and the installation began. About a minute into it, it kicked me to the bootloader with the message, "Failed to hab check for recovery: 0x56. Boot up failed".
Also see my post at androidcentral.com at forums.androidcentral.com/moto-x/336036-kitkat-crashed-my-moto-x-unrecoverable.html
Note that my moto x has never been rooted.
forums.androidcentral.com/attachments/moto-x/92779d1384906583-kitkat-crashed-my-moto-x-unrecoverable-kitkat_error.jpg
I selected "Recovery" and it rebooted and attempted to re-install, but then I was met with a image very similar to this except it said "ERROR":
forums.androidcentral.com/attachments/moto-x/92780d1384906685-kitkat-crashed-my-moto-x-unrecoverable-android-error.jpg
Then a few seconds later it rebooted again and now it just gets stuck at the Motorola logo:
forums.androidcentral.com/attachments/moto-x/92781d1384906724-kitkat-crashed-my-moto-x-unrecoverable-moto_x_boot_logo_featured_small.jpg
If I try any of the other options in the boot loader, the behavior is the same.. it gets stuck at the Motorola logo. Yesterday it sat that way for 4 hours before the battery died.
Today I tried connecting it to my computer via USB. My Mac doesn't appear to recognize that it's been connected even though the drivers have been installed. In a Windows VM with MDM it recognized the first time I connected it, but the MDM icon promptly disappeared from the status bar.
I spoke with Verizon tier 2 tech support yesterday and they didn't seem very knowledgeable - the person I spoke with didn't even know what KitKat is.
Surprisingly, I thought I had set up the Motorola data backup to the cloud, but verizon tech support said I must not have enabled it. So my biggest worry is that I've lost all my data (pictures/videos/contacts/etc...).
I'm hoping that somebody on this forum might have some advice for me.
Thanks,
Chris
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
cbridgers, that error happened to me while i was trying to flash through RSD Lite the leaked version of Kitkat. Because it was only to AT&T phones, it gave me that error cause i didnt have an unlocked bootloader. So what i did was flash back the 4.2.2 and for my surprise the phone was with all my config and data, nothing was erased.
Few suggestions...
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
OK, I got past the previous error by increasing the RAM allocated to my Windows VM. Now I get the following error when running "fastboot flash system system.img":
sending 'system' (850189 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.313s
cbridgers said:
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
Click to expand...
Click to collapse
Make sure you are using the newest fastboot files, the older ones do not chunk the system image and it is too large to flash.
New fastboot for Mac -- > http://www.teamblackhat.net/Downloads/Darwin.zip
New fastboot for Windows --> http://www.teamblackhat.net/Downloads/fastboot.zip
Use the house if moto save data option you can fxz using rsd or fastboot and it will not erase data at all. I have used it many times works great.
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
Click to expand...
Click to collapse
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
"/modem/image/dsps.b00" has unexpected contents.
Installation aborted
Click to expand...
Click to collapse
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Try this
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then take all the files from the first OTA sbf and flash them in order
does that work?
waiflih said:
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Click to expand...
Click to collapse
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
jimmydafish said:
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
Click to expand...
Click to collapse
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
waiflih said:
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
Click to expand...
Click to collapse
They are in the FXZ file named NON-HLOS.bin
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
waiflih said:
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
Click to expand...
Click to collapse
Well what are you trying to do? but if unlocked you can flash anything you want. I would stay far away from flashing any bootloader, tz, gpt, or sbl files though.
Only flash those files I named before.
Yes, i only flash the files i know are safe to flash, i dont like to use rsdlite. Thx again
Enviado desde mi XT1052
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
ekraincg said:
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
Click to expand...
Click to collapse
I'm having the same problem with my T-Mo moto x I received yesterday. I tried the fastboot erase cache method. It works to the extent that I can boot back into 4.2.2 but I can't update or perform a factory reset from the settings menu.
When I give the command to fastboot erase cache the bootloader says 'get-var partition type' and 'erasing cache' however the bootloader never says 'cache erased' or any other confirmation message. Fastboot on the desktop does say 'cache erased' though.
Finally, I would try to flash the stock images but I can't seem to find them anywhere. Can someone point me to them please?
Can anyone tell me what this (remote: Flashing is not allowed in Lock State).
What exactly is locked? Is my cell OEM unlocked?
I flashed the wrong TWRP (for the 2017 Red Magic-NX209J) and even though I have been able to unlock my cell via CMD commands; it remains permanently in fastboot mode?
If I send a CMD command to reboot it reboots straight back to fastboot mode.
No form of ADB connect seems to work an my windows PC cannot see/show the cell?
How the hell do I fix this? It's been in this state for a week.
Can anyone help?
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
xronaldx said:
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
Click to expand...
Click to collapse
Thanks for the suggestion. I have no recovery back up Is it possible to get past TWRP being locked and use CMD to flash the International or chinese ROM? Or recovery image?
Unless tools are developed to unbrick this device I am scared this problem might be permanent
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Secretcow said:
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Click to expand...
Click to collapse
Thanks but what do i do with it? Its all in an asain language?
Link not open bro
The TWRP does not work
Sorry. That link to the twrp does not result in a bootable twrp recovery for me.
I am starting to think my cell is not fixable.
I did not do that much wrong I just flashed the twrp for 2 models of red magic earlier. It only has a fastboot mode. I either get a boot screen then fastboot mode or a warning about the bootloader being unlocked.
Whatever is wrong with my cell prevents ADB connect an the cell is not able to be seen by windows.
This $1100 New Zealand dollar cellphone may be permanently bricked by my mistake.
I might just need to bin it an buy another one.
Lesson learned.
It confusing....
My cell acts like it has a softbrick (can turn off an on an has fastboot options and I have erased it an OEm an bootloader unlocked it)
And also behaves like a hard brick (resists every method of repair).
I just do not understand it or Nubia products. I am unfamiliar with this phone.
Does anyone have any clue how I can see this cell on my windows pc or ADB connect it an boot into TWRP?
Are there any Nubia repair software tools?
I already share nubia red magic 3 twrp check my all post
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Thanks for that. I'm talking about using CMD to totally wipe everything in the cell an reflash the Chinese ROM that came with it. Repair software. Might take months to develop software like that.
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Also it isn't a zip. It's some other kind of file. And does not boot into TWRP on my unit
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Sent from my NX629J using Tapatalk
terrapin4 said:
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Click to expand...
Click to collapse
Terrapin. Absolutely nothing worked. I am the 3rd person who has had this issue I know of. 2 other xda members had the same issue. One with TWRP like me an the other got stuck in fastboot mode after trying g to flash an apk of Gapps? I think these cells do not like tinkering. But your advice enabled me to be OEM and bootloader unlocked. But always.....straight back to fastboot mode no matter what I flash? My red magic 3 device is currently at a service center with a technician trying to solve the problem. I have 3 repayments left on my Xiaomi Mi9 that has zero flashing issues. O admit i.may be ignorant of the ways of Nubia ?
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
emmegitony said:
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
Click to expand...
Click to collapse
Thank God. Maybe the Chinese service guy I'm paying will get on xda an try your idea. I'm being lazy saying that lol. Thanks very very much. I will show your post to the service guy who has my red magic 3 or try it myself.
There's no way your a junior member working all this out. I'm a junior member listed as a senior member who makes rookie flashing errors with Chinese cellphones lol.
I will share if I can implement your ideas successfully. Thanks buddy my missus really loved this phone I felt really bad when I incapacitated it.
Fingers crossed.....
I have no idea how did you managed to flash the system.img
C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
LE: After this error, somehow it manages to continue and flash all partitions of the system, but after above tutorial, the phone still reboots in fastboot mode and cannot access recovery
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
sakilxda said:
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
Click to expand...
Click to collapse
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Bryceicle1971 said:
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Click to expand...
Click to collapse
Hane you fixed the phone or not?
JerryYin said:
Hane you fixed the phone or not?
Click to expand...
Click to collapse
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Bryceicle1971 said:
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Click to expand...
Click to collapse
My suggestions is, download a full sd card update package, unlock the bootloader temporarily,extract the update file and flash the vbmeta.img to vbmeta partion, then flash the recovery.img to recovery partition, after that, try to boot into recovery through bootloader. You have to make sure that you use all the same file from same package, if you are use a low version vbmeta file to boot a high version system (or recovery ) it will not boot. the vbmeta is very important on this phone.