Phone not booting after OTA - G 2014 Q&A, Help & Troubleshooting

So today I got an update for a new firmware, it was a small 125 mb patch, no big deal. I downloaded it and installed it a couple of hours later, I leave it to install and when I'm back my phone is frozen on the Motorola logo and the "Powered by android" text written below, but it won't get past that. I left it for almost an hour and it won't boot, I tried forcing a reboot and it gets me back to the same screen.
Is there any way I could fix it, preferably while keeping my data? Especially the what's app gallery.
Thanks a lot guys, I'm kinda panicking here.
Ps. I'm not rooted, everything is completely stock.

it's Stuck on Moto Boto logo ?

Yes. I tried doing a factory reset and that doesn't work either, it sends me right back to the boot logo.

Sorry to not have any solutions but my girlfriends phone has probably had the exact same thing happen. At about 10PM tonight she got an update notification and told it to install. almost two hours later she checked the phone again to see it stuck on the boot logo and incredibly hot. She restarted it and same thing, stuck on the boot logo. Same as you, completely stock phone. Never been modified in anyway.
I had her go into recovery and wipe cache, no change at all. I've now had her do a factory reset twice as some similar problems mentioned that as a solution. No change, still just gets stuck on the boot screen.
My assumption at this point is that this update has completely trashed the phone and it's completely unrecoverable on the device at least.

I'm willing to learn how to install a new rom from scratch if that would help, preferably a stock one. The problem is that Motorola doesn't have any stores where I live, I ordered my phone off amazon.
So is there any method to fix it? You can instruct me if you could or at least tell me what to look for on google.
Thanks a lot man.

darthlawl said:
I'm willing to learn how to install a new rom from scratch if that would help, preferably a stock one. The problem is that Motorola doesn't have any stores where I live, I ordered my phone off amazon.
So is there any method to fix it? You can instruct me if you could or at least tell me what to look for on google.
Thanks a lot man.
Click to expand...
Click to collapse
I didn't think that you have any way to install urself stock without voiding warranty so u have 2 choices u can go for service or unlock and install any rom u want

vaisakmct said:
I didn't think that you have any way to install urself stock without voiding warranty so u have 2 choices u can go for service or unlock and install any rom u want
Click to expand...
Click to collapse
My warranty is already over, I just want stock because I like it.
Are you sure a rom installation would work?

Ps. I can't unlock the bootloader since I can't access the OS

Unlock boot loader does not acess to os it is simple
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
Just go to fastboot mode and unlocking can done from pc and install twrp then u can flash roms

vaisakmct said:
Unlock boot loader does not acess to os it is simple
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
Just go to fastboot mode and unlocking can done from pc and install twrp then u can flash roms
Click to expand...
Click to collapse
What do you mean?

I'm a total beginner when it comes to android, I'm more of a windows guy. Can you walk me through the steps?

It´s not that easy to guide someone through all the steps. First thing you have to do is unlock your bootloader,described here: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728. Read all the steps,it´s not that difficult.
You need all the drivers,by motorola and android, linked in the tutorial. I recomend Minimal ADB and Fastboot instead of Android SDK, it´s easier. Install it in the root of your windows partition,like C:\Minimal ADB and Fastboot. So if you open a command prompt the path is short and you know it.
After the unlock process you´ll need to flash a custom recovery, you can read how to do that here: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818.
There´s a part called Flashing TWRP Recovery . You don´t need to do that with Flashify (you surely can if you want but I think this way is easier to do), just download the custom recovery TWRP from here: https://dl.twrp.me/titan/.
Place the .img file in the Minimal ADB and Fastboot folder and connect the phone to the PC. After that you open a command prompt again from the Minmal ADB and fastboot folder (open the folder and hold Shift and right click and press "open command window here".
Now type the command
Code:
adb reboot bootloader
When the phone has booted to bootloader type
Code:
fastboot devices
A string of numbers should appear,that means your phone is connected.
Now type
fastboot flash recovery "name of the downloaded TWRP .img file", in your case that should be
Code:
fastboot flash recovery twrp-2.8.6.0-titan.img
Now everytime when you boot to recovery you´ll see a menu with a lot of features like install,wipe,backup,restore etc.
From here you can flash any rom you like, a stock rom, a stock based rom or any other like cyanogen or AOSP.
If you want to flash stock again you´ll need to know the name of your firmware,it differs from country and version. You can search for it here: http://forum.xda-developers.com/moto-g-2014/development/original-motorola-firmware-collection-t3153533.
It´s late now here, if you are at this point and have decided what rom to flash post again or pm me.
I hope my exclamation is understandable and I´ve made no faults, everyone else please correct me then!

Wolfcity said:
It´s not that easy to guide someone through all the steps. First thing you have to do is unlock your bootloader,described here: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728. Read all the steps,it´s not that difficult.
You need all the drivers,by motorola and android, linked in the tutorial. I recomend Minimal ADB and Fastboot instead of Android SDK, it´s easier. Install it in the root of your windows partition,like C:\Minimal ADB and Fastboot. So if you open a command prompt the path is short and you know it.
After the unlock process you´ll need to flash a custom recovery, you can read how to do that here: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818.
There´s a part called Flashing TWRP Recovery . You don´t need to do that with Flashify (you surely can if you want but I think this way is easier to do), just download the custom recovery TWRP from here: https://dl.twrp.me/titan/.
Place the .img file in the Minimal ADB and Fastboot folder and connect the phone to the PC. After that you open a command prompt again from the Minmal ADB and fastboot folder (open the folder and hold Shift and right click and press "open command window here".
Now type the command
Code:
adb reboot bootloader
When the phone has booted to bootloader type
Code:
fastboot devices
A string of numbers should appear,that means your phone is connected.
Now type
fastboot flash recovery "name of the downloaded TWRP .img file", in your case that should be
Code:
fastboot flash recovery twrp-2.8.6.0-titan.img
Now everytime when you boot to recovery you´ll see a menu with a lot of features like install,wipe,backup,restore etc.
From here you can flash any rom you like, a stock rom, a stock based rom or any other like cyanogen or AOSP.
If you want to flash stock again you´ll need to know the name of your firmware,it differs from country and version. You can search for it here: http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533.
It´s late now here, if you are at this point and have decided what rom to flash post again or pm me.
I hope my exclamation is understandable and I´ve made no faults, everyone else please correct me then!
Click to expand...
Click to collapse
Its good guide follow these steps

If you want to go stock, I recommend you to go with the mfastboot method . . .
because it doesn't even need unlocked bootloader or any recovery,
The following link is having a mfastboot folder, in which, Moto G 2014(XT1068) stock 5.0.2 factory firmware is stored and, you just have to extract the folder and open it then pressing & holding shift + RMB and select "Open Command Window Here".
(Now press Power + Volume Down simultaneously, and you should go to the bootloader mode, if you don't know that )
Now in the command window, check your phone is connected with USB and type below code and press Enter.
Code:
fastboot devices
if any code(like for eg. ZDMJK2312) is shown, you're connected,
if not, try reconnecting the USB and try again.
Once properly connected, now you can flash the follwing commands one by one, to get your device to life.
Code:
Moto G 2014 Stock 5.0.2 Restore Script
------------------------------------------------------------------|
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
BTW this happened to me 6 months back and the same helped me.
mfastboot
Note : The above method is for only the model XT1068, because the firmware in the folder is for that model only, so plz make sure your model before proceeding.
And plz follow each and every step properly.
Thanks . . .

Alright thanks people! I'll try ArtRahul's method since it's easier and i was quite satisfied with stock. If that doesn't work I'll try Wolfcity's method.

Alright, so this is an update. ArtRahul's method works great and it's really easy. If anyone looks for a solution and finds this thread, just make sure you find the exact model of your phone and google the firmware. Here's where I found mine
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
It has links to other versions too. Good luck!

darthlawl said:
What do you mean?
Click to expand...
Click to collapse
if ur phone is going to fastboot mode u can install twrp, no os is needed for doing this

darthlawl said:
Ps. I can't unlock the bootloader since I can't access the OS
Click to expand...
Click to collapse
darthlawl said:
What do you mean?
Click to expand...
Click to collapse
you don't have to access to os in order to unlock the bootloader, go to android development section on this forum for moto g 2014 & follow any thread that guides about unlocking bootloader.

darthlawl said:
Alright, so this is an update. ArtRahul's method works great and it's really easy. If anyone looks for a solution and finds this thread, just make sure you find the exact model of your phone and google the firmware. Here's where I found mine
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
It has links to other versions too. Good luck!
Click to expand...
Click to collapse
did anything work?
my moto g2 was rooted .i got notification that update 5.1.1 is available .but after update it is stuck in bootloop::crying:
---------- Post added at 03:17 AM ---------- Previous post was at 03:03 AM ----------
it is giving me failed to validate system image error after first command mfastboot.exe oem lock begin

Related

endless bootloop after doing the OTA to 4.4.2

So one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.
AbstractXart said:
So one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.
Click to expand...
Click to collapse
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.
patspdaphone said:
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.
Click to expand...
Click to collapse
So to accept the OTA, did you go through the bootloader/recovery and flash it, or were you able to turn on your phone and accept it? Sorry I don't have his phone on me right now otherwise I would have done it .
Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...
KidJoe said:
Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...
Click to expand...
Click to collapse
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.
AbstractXart said:
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.
Click to expand...
Click to collapse
until the next time the OTA downloads and tries to install
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom
KidJoe said:
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom
Click to expand...
Click to collapse
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck
Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
samwathegreat said:
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck
Click to expand...
Click to collapse
any ideas?
I just checked device manager and it shows "ADB Interface" and then MOT Single ADB Interface.
But its not showing up under devices when running command "ADB Devices" in CMD
Globalrebel said:
Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
any ideas?
Click to expand...
Click to collapse
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.
samwathegreat said:
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.
Click to expand...
Click to collapse
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?
Globalrebel said:
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?
Click to expand...
Click to collapse
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck
samwathegreat said:
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck
Click to expand...
Click to collapse
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
No water damage, and the phone was literally working perfectly fine 15 minutes ago. Just all of a sudden stopped showing the screen
Globalrebel said:
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
Click to expand...
Click to collapse
Bummer. You appear to have used the correct procedure.
This looks to be a hardware failure :/
Sorry, I don't have any further troubleshooting techniques for you...
Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?
Globalrebel said:
Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?
Click to expand...
Click to collapse
If you unlocked the bootloader they know it. Technically your warranty is void... But they might replace/fix it anyways. Don't mention it and see what happens. Let us know.

[Q] Razr xt890i

Hi there
That's my first post, so please be understanding. Bought a Motorola phone as it is (no water damage) which comes to booting logo and after few minutes keep restarting and trying to booting with no results. I've started red some posts, already but i'm stuck. Reset doesn't work (Power button+volume control down), but when i press power button +camera button and plug in with computer, it shows black screen and green led. Already installed MEDFIELD drivers, RSD Lite and xFSTK-DLDR. tried already RSD Lite with no luck (i've downloaded CFC_signed_customer_8.7.1I-110_IFW-DE-31_RTEU.xml and CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml)
Can get to AP Fastboot Flash Mode, but when i tried to do Factory or Recovery gets:
Failed to enter Factory/Recovery mode. error code -18
No more error code, only some kind of "GETVAR" failed
Read here
http://forum.xda-developers.com/showthread.php?t=2166646
CWMR or TWRP install easy 19-Sep-13
Install and try again
Enviado desde mi GT-I8190L
jacbarahona72 said:
Read here
http://forum.xda-developers.com/showthread.php?t=2166646
CWMR or TWRP install easy 19-Sep-13
Install and try again
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
I'll give it go and let U know.
Thanks
Got such a message:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder and fastboot file(s) created.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
-----------------------------------.
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
How can i connect with Motorola, at the minute is on AP FASTBOOT
This time i paste .img files into Fastboot Commander folder nad gets:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 0x2025.
Radio version: failed.
Main software version: failed.
cid: 7.
cpld: failed.
product: smi.
getvar:mid failed (remote failure).
getvar:security failed (remote failure).
getvar:build-mode failed (remote failure).
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?
On phone i got Getvar build-mode
Fastboot command failed
If you came down those 2 firmware must know that one is ICS (8.7), the other JB (9.8) and if you wanted to install the ICS tending JB you've done a hardbrick, so I recommend you search for the thread "Unbrick for downgrading"
Sorry for my bad English
Enviado desde mi GT-I8190L
---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------
asgaard76 said:
I'll give it go and let U know.
Thanks
Click to expand...
Click to collapse
You bootloader is locked?
Only make if you have unlocked
Enviado desde mi GT-I8190L
---------- Post added at 08:31 AM ---------- Previous post was at 08:25 AM ----------
Read here for getvar problem
http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company
Enviado desde mi GT-I8190L
jacbarahona72 said:
If you came down those 2 firmware must know that one is ICS (8.7), the other JB (9.8) and if you wanted to install the ICS tending JB you've done a hardbrick, so I recommend you search for the thread "Unbrick for downgrading"
Sorry for my bad English
Enviado desde mi GT-I8190L
---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------
You bootloader is locked?
Only make if you have unlocked
Enviado desde mi GT-I8190L
---------- Post added at 08:31 AM ---------- Previous post was at 08:25 AM ----------
Read here forma getvar problem
http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
I don't know if it's unlocked as i bought when it won't pass booting screen
Quick update:
When i tried using Recovery.img through Fastboot commander got such a message (picture)
and on phone mostly gets Fastboot command failed
Invalid image size for partition recovery
asgaard76 said:
I don't know if it's unlocked as i bought when it won't pass booting screen
Quick update:
When i tried using Recovery.img through Fastboot commander got such a message (picture)
and on phone mostly gets Fastboot command failed
Invalid image size for partition recovery
Click to expand...
Click to collapse
SURELY NOT HAVE THE BOOTLOADER UNLOCKED
IMPORTANT
AS YOU AND I flashed HAS MARKED ERROR, YOU MUST CORRECTLY FASTBOOT FLASH FOR SOMETHING AS BOOT IMAGE ( LOGO_SIGNED ) , EXTRACT OF THE SAME FIRMWARE (ZIP )
1 - . DOWNLOAD ONE FASBOOT.EXE OF THE THREADS XDA
2 - . PLACE THE IMAGE FILE ( LOGO_SIGNED ) WITH THE FASTBOOT EXE FILE IN ONE FOLDER IN THE ROOT FOR EXAMPLE C:\ANDROID\ <---- YOU CREATE
3. - OPEN COMMAND WINDOW IN THE FOLDER FILES YOU HAVE MENTIONED IN THE PREVIOUS ITEM
4 - . RAZR I CONNECTED TO PC BY USB CABLE AND BE IN FASTBOOT MODE SCREEN
5 - . INDICATE THE FOLLOWING COMMAND " FASTBOOT FLASH LOGO LOGO_SIGNED "
IF YOU ARE FLASHING OK FOLLOW YOU'VE INDICATED BELOW
CASE 1
1 - . USE A FIRMWARE JB (9.8 )
2 - . DECOMPRESS , EDIT THE FILE WITH EXTENSION XML, and eliminate GETVAR LINES INDICATED IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company)
3 - . USE RSD LITE VERSION 6.14 MINIMUM TO FLASH THE STOCK XML EDITED ( WHICH YOU HAVE CLEARED THE LINES GETVAR )
CASE 2
1 - . UNLOCK YOUR BOOTLOADER
2 - . INSTALLING A CUSTOM RECOVERY VIA FASTBOOT COMMANDER
3. - INSTALL AN " AS CUSTOM ROM OF OMAR AVELAR " IN THE RECOVERY
FOLLOW THE INSTRUCTIONS IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company) IN THIS THREAD AS INDICATED UNLOCK BOOTLOADER ,
ALSO, THE RECOVERY IS TO INSTALL A CUSTOM ROM FOR EXAMPLE OF OMAR AVELAR AND YOU SHOULD HAVE UNLOCKED BOOTLOADER FOR THAT
jacbarahona72 said:
SURELY NOT HAVE THE BOOTLOADER UNLOCKED
IMPORTANT
AS YOU AND I flashed HAS MARKED DEFECTIVE, YOU MUST CORRECTLY FASTBOOT FLASH FOR SOMETHING AS BOOT IMAGE ( LOGO_SIGNED ) , extract SAME FIRMWARE (ZIP )
1 - . DOWNLOAD ONE OF THE THREADS FASBOOT.EXE XDA
2 - . PLACE THE IMAGE FILE ( LOGO_SIGNED ) FASTBOOT WITH THE EXE FILE
3. - OPEN COMMAND WINDOW IN THE FOLDER archvos YOU HAVE MENTIONED IN THE PREVIOUS ITEM
4 - . RAZR I CONNECTED TO PC BY USB CABLE AND BE IN FASTBOOT MODE SCREEN
5 - . INDICATE THE FOLLOWING COMMAND " FASTBOOT FLASH LOGO LOGO_SIGNED "
IF YOU ARE FLASHING OK FOLLOW YOU'VE INDICATED BELOW
CASE 1
1 - . USE A FIRMWARE JB (9.8 )
2 - . DECOMPRESS , EDIT THE FILE WITH EXTENSION XML, and eliminate GETVAR LINES INDICATED IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company)
3 - . USE RSD LITE VERSION 6.14 MINIMUM TO FLASH THE STOCK XML EDITED ( WHICH YOU HAVE CLEARED THE LINES GETVAR )
CASE 2
1 - . UNLOCK YOUR BOOTLOADER
2 - . INSTALLING A CUSTOM RECOVERY VIA FASTBOOT COMMANDER
3. - INSTALL AN " AS CUSTOM ROM OF OMAR AVELAR " FOR RECOVERY
FOLLOW THE INSTRUCTIONS IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company) IN THIS THREAD AS INDICATED UNLOCK BOOTLOADER ,
ALSO, THE RECOVERY IS TO INSTALL A CUSTOM ROM AVELAR AS OF OMAR AND YOU SHOULD HAVE UNLOCKED BOOTLOADER
Click to expand...
Click to collapse
Will give it go and keep U inform. Thanks
Once again:
1. I have to download Fastboot.exe (is it fasboot commander?)
2. Image file (do i have it?? which one is it?)
3. command window?? I'm lost
4.
asgaard76 said:
Will give it go and keep U inform. Thanks
Once again:
1. I have to download Fastboot.exe (is it fasboot commander?)
2. Image file (do i have it?? which one is it?)
3. command window?? I'm lost
4.
Click to expand...
Click to collapse
1. - Fastboot.exe
2. - logo_signed (must be obtained from the firmware, exploring the zip file) NO DOWNLOAD, draw your own "firmware ZIP (CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip <-- for example)"
sorry for my bad English
Donwload files
http://db.tt/tak1LsuU
note: NO DOWNLOAD logo_signed file is of the firmware: Brasil.en.BR (IS "ICS" NO WORK, YOU DAMAGED YOUR PHONE)
Procedure
1. - Put the downloaded files in a folder in the root "C" on your pc, (I call this folder "Android" for example)
2.- Put the phone in fastboot mode (power button and Vol - squeezing them a few seconds until the screen fastboot mode) and connect with USB the phone to pc
3.- Opening a cmd screen, we stand there, I'm in cmd C:\Android\
4. - cheking with command fastboot devices
5. - Performed the command fastboot flash logo logo_signed
6. - Conducted after ending command fastboot reboot and that's it
7.- enjoy
Warning: only share what I see written on a forum and I served, so I do not take responsibility for any damage this may cause to your phone
---------- Post added at 05:14 PM ---------- Previous post was at 04:56 PM ----------
AND YOU CAN NOT COME TO RECOVERY BECAUSE ERASED PARTITION,
AS YOUR PICTURE
WHERE RECEIVED INSTRUCTIONS TO CLEAR YOUR RECOVERY?
NO YOU ACCESS IT, TO RECOVERY BECAUSE YOU HAVE NO
AND YOU MUST FLASH THE STOCK RECOVERY FIRST TO SEE IF YOU ACCESS TO RECOVERY.
ALSO THAT WHAT TO DO WITH FASTBOOT COMMANDER
what was your firmware that you had installed before this happened to you?
As per picture
It looks like image was installed, what next steps should be done?
Yes, that's my fault. I've tried program and thought that it won't make any effects, because i got messages failed, so unfortunately i erase Recovery partition. Is there anything else what we can do?
Thanks
How can i flash stock Recovery and would it help?
jacbarahona72 said:
what was your firmware that you had installed before this happened to you?
Click to expand...
Click to collapse
I don't know as i bought that phone from someone who sell it cheap (already not working) and probably that person have no clue what version/name of Android was it there?
Ok, try this, it has nothing to do with the logo u just flashed
i dunno if u already done this. But we are gonna install the stock recovery again and see what happens. Installing a recovery cant kill your device
If by this methode u cant install the recovery, fastboot gives an error, your bootloader is locked.
1. In this thread, download the 1.6 zip version of the recovery flasher. (the flasher is an automated proces, but we do it manually)
2. Open de zip file and extract the "stock.img" to the folder with the fastboot.exe
3. now, reboot the device in fastboot mode (power and volume down) and linked with usb to your pc obviously
4. use the command "fastboot devices" and u get a list of attached devices. If ur device is one of them we are good.
5. use the command "fastboot flash recovery stock.img" to flash the stock recovery. If it works, your device has an unlocked bootlaoder. If it doesn't its locked.
If it is locked, we go through the next step with rsd lite and install the latest JB 4.1.2 image to your device.
Hazou
Hazou said:
Ok, try this, it has nothing to do with the logo u just flashed
i dunno if u already done this. But we are gonna install the stock recovery again and see what happens. Installing a recovery cant kill your device
If by this methode u cant install the recovery, fastboot gives an error, your bootloader is locked.
1. In this thread, download the 1.6 zip version of the recovery flasher. (the flasher is an automated proces, but we do it manually)
2. Open de zip file and extract the "stock.img" to the folder with the fastboot.exe
3. now, reboot the device in fastboot mode (power and volume down) and linked with usb to your pc obviously
4. use the command "fastboot devices" and u get a list of attached devices. If ur device is one of them we are good.
5. use the command "fastboot flash recovery stock.img" to flash the stock recovery. If it works, your device has an unlocked bootlaoder. If it doesn't its locked.
If it is locked, we go through the next step with rsd lite and install the latest JB 4.1.2 image to your device.
Hazou
Click to expand...
Click to collapse
had to make a correct flash because if you stay with an "incorrect flash", RSD LITE not work, and in many cases say error, reading the context, "directed to make a flash of SOMETHING" and that would be correct, then with RSD LITE flash the firmware and must not indicated error like before.
to the stock recovery you can flash with the same program that he used wrong
I do not have much that I left the Razr I but I've explained what ... . somewhere in all that I have written must match with you Master.
Sorry for my bad English
Enviado desde mi GT-I8190L
jacbarahona72 said:
had to make a correct flash because if you stay with an "incorrect flash", RSD LITE not work, and in many cases say error, reading the context, "directed to make a flash of SOMETHING" and that would be correct, then with RSD LITE flash the firmware and must not indicated error like before.
to the stock recovery you can flash with the same program that he used wrong
I do not have much that I left the Razr I but I've explained what ... . somewhere in all that I have written must match with you Master.
Sorry for my bad English
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
Don't get me wrong, if I gave you that idea, wasn't my purpose
U did great in presenting a solution for the problem, the only problem is that in my opinion your post wasn't very easy to read for a new guy with a problem. With all the lines/codes that were produces and not set in a container (/code) and with the big red lines that were in the post it wasn't very understandable.
Your English is fine, it is understandable, just the formatting of the post was in my opinion not very good. The solution is good though, maybe with a small sideway, but good.
Just keep it up and help those guys when ever u can. We need those folks like u that help others out!! :thumbsup:
Hazou
Verstuurd van mijn GT-P5110
Hazou said:
Don't get me wrong, if I gave you that idea, wasn't my purpose
U did great in presenting a solution for the problem, the only problem is that in my opinion your post wasn't very easy to read for a new guy with a problem. With all the lines/codes that were produces and not set in a container (/code) and with the big red lines that were in the post it wasn't very understandable.
Your English is fine, it is understandable, just the formatting of the post was in my opinion not very good. The solution is good though, maybe with a small sideway, but good.
Just keep it up and help those guys when ever u can. We need those folks like u that help others out!! :thumbsup:
Hazou
Verstuurd van mijn GT-P5110
Click to expand...
Click to collapse
Will post any update 2night.
OK. Folks short update
Friend of mine who's also on xda forum gave me few tips which i tried, but no luck. Will post them here:
1. CMD: fastboot oem get_unlock_data
fastboot oem get_unlock_data
...
(bootloader) 3A25150915586129#54413233373034
(bootloader) 48354100000000000000000000#1ACF
(bootloader) 4FDA6DCEE30F10CACA1F7FC1CBD39CB
(bootloader) 08BBF#DFF3ABAE76852954D805ED6EF
(bootloader) 3FA0000
OKAY [ 0.290s]
finished. total time: 0.290s
2. fastboot oem unlock PJYERHAJMZMPVYSRKIXN
fastboot oem unlock PJYERHAJMZMPVYSRKIXN
...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 8.390s
In Motorola phone it says
Unlock
Fastboot command failed
He said that partition table is faulty. It can be done only in Linux or JTAG.
Any advice on this?
We tried this as well:
CMD: fastboot format data
(bootloader) Variable not supported!
formatting 'data' partition...
(bootloader) Variable not supported!
FAILED (remote failure)
FAILED (remote failure)
finished. total time: 0.342s
He said that emmc is faulty that's why fastboot won't work.
Had that problem too... it was due to bad Emmc. Sorry for your loss bro.
It could be indeed an emmc problem, in that case a repair at motorola can only fix it, or u will need to replace the motherboard, that will set u back another 150 dollars.
But, u successfully flashed the logo, so a part of the emmc is still working correctly i assume. btw, my knowledge about emmc problems stops here..
The next steps i should take is the following, we will reformat/partition your device, as far as it goes. But I never done this, didn't need to i only know it is possible. Everything that happens now is on your own responsibility!!
1. Download your correct firmware, must be jellybean 4.1.2 from here(firmware)
2. Extract it content in a folder like "STOCKROM"
3. Download new fastboot files from here (mfastboot,xda)
4. Extract the new mfastboot files in the folder "STOCKROM" if u named it like that.
5. Connect your device with your pc, make sure all drivers are correctly installed, and boot in fastboot mode (power + volume down)
6. Flash each of the partitions in sequence using mfastboot (is like fastboot, but can install files larger then 100mb), you need to enter the following commands one-by-one checking that each one returns an [OKAY]. If it doesnt work, i am out of ideas. sry, but report anyway what happend
7.
Code:
mfastboot flash gpt gpt_signed
mfastboot flash motoboot motoboot
mfastboot flash boot boot_signed
mfastboot flash recovery recovery_signed
mfastboot flash motobp motobp
mfastboot flash system system_signed
mfastboot flash cdrom cdrom_signed
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Good luck with it, i will hear from you.
Hazou
btw, erasing 'data' is impossible, fastboot doesn't know 'data', only 'userdata'
Hazou said:
It could be indeed an emmc problem, in that case a repair at motorola can only fix it, or u will need to replace the motherboard, that will set u back another 150 dollars.
But, u successfully flashed the logo, so a part of the emmc is still working correctly i assume. btw, my knowledge about emmc problems stops here..
The next steps i should take is the following, we will reformat/partition your device, as far as it goes. But I never done this, didn't need to i only know it is possible. Everything that happens now is on your own responsibility!!
1. Download your correct firmware, must be jellybean 4.1.2 from here(firmware)
2. Extract it content in a folder like "STOCKROM"
3. Download new fastboot files from here (mfastboot,xda)
4. Extract the new mfastboot files in the folder "STOCKROM" if u named it like that.
5. Connect your device with your pc, make sure all drivers are correctly installed, and boot in fastboot mode (power + volume down)
6. Flash each of the partitions in sequence using mfastboot (is like fastboot, but can install files larger then 100mb), you need to enter the following commands one-by-one checking that each one returns an [OKAY]. If it doesnt work, i am out of ideas. sry, but report anyway what happend
7.
Code:
mfastboot flash gpt gpt_signed
mfastboot flash motoboot motoboot
mfastboot flash boot boot_signed
mfastboot flash recovery recovery_signed
mfastboot flash motobp motobp
mfastboot flash system system_signed
mfastboot flash cdrom cdrom_signed
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Good luck with it, i will hear from you.
Hazou
btw, erasing 'data' is impossible, fastboot doesn't know 'data', only 'userdata'
Click to expand...
Click to collapse
None of them are working. Anyway i was in few repair shops in Dublin and none of them can fixed as they stated Motorola isn't popular in Ireland. Mostly i heard "i have no clue" or "You have to send to manufacturer". One of them tried fixed (it takes roughly 3 hours), but also gave up. He said that it's nearly same story with chip which Samsung S3 had. Don't ask me what does it mean, cuz have no idea. Friend of mine who's also user on that forum will fix it as he stated, but don't know if i gonna send it to Poland. At this stage i have to stop any more tests with Motorola as i don't know what i have to do.
Thanks for all support and will keep You inform if something turn up.
Btw. one of Chinese "call him tech-e" broked back cover of Motorola (beside camera, cracked glass), but i noticed it when i left his repair centre.
Thanks
Okey, best of luck!
Hazou
Verstuurd van mijn XT890

[Q] MOTO X Bricked

My moto X has a problem , let me show you the log file first
-Unlocked using motorola's website
-Flashed TWRP recovery
-Created a backup
-[MISTAKE 1]Wiped using advanced wipe
-Everything including the backup I created got wiped ,with no OS
-Mounted and tried to install CyanogenMod 11
-[ERROR 1]This rom is supported by ghost xt1053(my model number) ,and your device is . (like just a dot) //Cannot install the zip file
-[BRICKED]
-Then I searched what to do ,downloaded "TMO_213.44.1.ghost_row.Retail.en.US" firmware
-Using fastboot ,I flashed the firmware using the following commands
After downloading the image for your device:
Unzip the image.
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock​
-It showed an error During locking the device
-The phone finally started working [UNBRICKED?]
-My sim card wasnt detecting
-So I searched more ,and checked my IMEI
-Dialed *#06# and got "IMEI 0"
-For confirmation ,I went again to settings->about->Status
-Everything was fine except "IMEI 0",and "IMEI SV 00"
-I couldnt find anything online except changing my IMEI ,which is ,one: illegal and two: not possible since I do not have Engineering mode app in my phone
-Headed over to the service center and they told me that my motherboard is gone ,you have to pay 291.050 US Dollars to change it
-But if the motherboard is gone ,how can my phone work ?
Here is my question to you guys ,what should I do ? Can I do anything to get my phone working again ? Please help me as I am not using a phone ,and I really need to use this one .
Thanks in advanced
Sorry for my bad English
I think there was a step you missed there when flashing:
fastboot flash modem NON-HLOS.bin
and it's better to use Motorola fastboot aka mfastboot instead of regular old fastboot. if you don't have it just Google for it.
for a more complete guide see option 5 on this site: http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Also there is absolutely no need for that last step you tried, fastboot oem lock... that will relock your bootloader which is totally unnecessary. you don't need it for otas or anything else, and as for warranty your phone is already flagged as unlocked and relocking it won't change that.
dtg7 said:
I think there was a step you missed there when flashing:
fastboot flash modem NON-HLOS.bin
and it's better to use Motorola fastboot aka mfastboot instead of regular old fastboot. if you don't have it just Google for it.
for a more complete guide see option 5 on this site: http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Also there is absolutely no need for that last step you tried, fastboot oem lock... that will relock your bootloader which is totally unnecessary. you don't need it for otas or anything else, and as for warranty your phone is already flagged as unlocked and relocking it won't change that.
Click to expand...
Click to collapse
Okay so I tried the whole process with "fastboot flash modem NON-HLOS.bin" ,and restarted ,but my IMEI is still showing 0 .
I was using mfastboot from the start. Any help ?
Guys please help me ,I know its torturous for you'll ,but I'm helpless right now
dkaushik95 said:
Guys please help me ,I know its torturous for you'll ,but I'm helpless right now
Click to expand...
Click to collapse
It's OK dude first step is to relax and realize that losing imei is not a new thing, it's happened to countless others. what that means is there should be a huge amount of info on what people have tried and what worked and didn't work. You'll find all the info by using Google search and changing keywords.
some keywords to try:
fastboot imei
Motorola recover imei
Restore imei
imei 0
recover imei
efs imei
and so on. if you read through them and feel you're not up to it, or if you try everything and nothing works, you have another option maybe:
Take it in / send it in for repair to Motorola or other (certified) repair shop
good luck.
BTW: The original box the phone comes in has your imei written on it. otherwise you can try the fastboot getvar method but that might or might not work.
Can you try to falsh using RSD lite it Completly safe and esay process . Try it once
MAhesh
Mahesh8348 said:
Can you try to falsh using RSD lite it Completly safe and esay process . Try it once
MAhesh
Click to expand...
Click to collapse
I tried everything including RSD Lite and several other methods ,and I've given it to Motorola . I hope they fix it
[UPDATE]
I sent my phone to the service center ,and they replaced the phone with a new one !
Everything is back to normal ,thanks for the support guys ,really appreciate it

Turbo firmware?

Hello need help tracking down stock turbo firmware. The Motofirmware website (http://motofirmware.center/files/category/23-droid-turbo/downloads) are corrupted. The links in this thread are all dead: http://forum.xda-developers.com/moto-maxx/general/quark-stock-firmware-moto-maxx-droid-t3063470. Does anyone know of another source for stock 5.1?
http://motofirmware.center/
Stanleywinthrop said:
Hello need help tracking down stock turbo firmware. Does anyone know of another source for stock 5.1?
Click to expand...
Click to collapse
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637
Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.
jalal-jap said:
http://motofirmware.center/
Click to expand...
Click to collapse
Thanks, classic, i'll give this a try.
classic757 said:
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637
Click to expand...
Click to collapse
Stanleywinthrop said:
Thanks, classic, i'll give this a try.
Click to expand...
Click to collapse
No problem. Please let me know how it turns out.
Stanleywinthrop said:
Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.
Click to expand...
Click to collapse
i have same problem. extract it whit "7ZIP" and no corrupted for me.
http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1
TheSt33v said:
http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1
Click to expand...
Click to collapse
I get this error:
http://i.imgur.com/EOPsxnB.png
dmginc said:
I get this error:
http://i.imgur.com/EOPsxnB.png
Click to expand...
Click to collapse
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.
Oh thanks. Good info. Is there a write up on using fastboot anywhere? These forums are pretty poorly maintained and no good stickies anywhere
Edit: Oh, you edited your post. Awesome. Thanks.
The root junky fxz is that for rsd lite when I look at the contents the system image is in several sections and says system.img sparsechunk and has 10 sections. I have never seen this in an fxz. Is this a new way of flashing the system image.
TheSt33v said:
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.
Click to expand...
Click to collapse
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.
When in fastboot, type "fastboot oem lock" (without the quotations"
Btrusa said:
When in fastboot, type "fastboot oem lock" (without the quotations"
Click to expand...
Click to collapse
Wouldn't that lock the bootloader?
Is it even possible to re-lock?
From what I understand he wants to avoid locking the bootloader...
Edit: nevermind I looked it up... Should have just done that the first time... ("I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.")
dmginc said:
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.
Click to expand...
Click to collapse
Nope
So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Sent from my XT1254 using Tapatalk
dmginc said:
So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Click to expand...
Click to collapse
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin
unhappybirthday said:
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?
dmginc said:
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?
Click to expand...
Click to collapse
I can only speak from my experience. I was on the KitKat bootloader and used mofo to flash lollipop. I unlocked with sunshine and installed twrp. Then I flashed the lollipop bootloader with the fastboot command . Still unlocked.
Sent from my DROID Turbo using Tapatalk.

I have a soft rocked Red Magic 3

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.

Categories

Resources