Hi guys! How are you? I hope you are fine, because I'm not lol.
Well, I'm new in this things, but I can install CM9 and 7 in my old devices thanks to your guides and tutorials, I really apreciated!.
But now, I'm stucking with my new phone, because I flashed wrong and I don't know what to do.
Ok let's start to explain my problem:
My phone is stucked in the fastboot screen and no advance. When I press "pwr vol+-" and select Recovery, nothing happens, only showme the "Motorola Dual Core Technology logo" and returns to fastboot.
...........................................................................
AP FastBoot Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
FastBoot Reason: Sticky bit factory_fastboot
...........................................................................
Ok, and when try to enter to recovery screen "pwr, vol+-" it's show me:
...........................................................................
Invalid Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
...........................................................................
Sometimes, indicate "Batery Low"...its very frustrating because I love my ohine but I can't make work and I don't know what is happend...
I see some tutorials, specialy from @sleevydude, to unlock the bootloader, but the "fastboot.exe" appears and dissapears, and I can't acces to program tools...
Another big problem, I'm from Argentina, and my language is spanish, after all, my english is good, and I can understand 90% if you say something...sorry if that is offtopic or something.
I've tryed with the metod from TheMythTeam, but doesn't work...keep stucked...
Ok guys, I hope you help me...miss my phone so much
Well you can't open the fastboot.exe because it's not a regular program. You just open a command Window in the folder it's located in.
Sent from my PACMAN MATRIX HD MAXX
It looks to me like your device has a locked bootloader.
What rom did you try to flash? What did you use to flash it?
deeje00 said:
Well you can't open the fastboot.exe because it's not a regular program. You just open a command Window in the folder it's located in.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Thanks mate, I'm testing the commands, but maybe I'll look at the tutorials carefully!
Soon I will have them new, wishing luck! :good:
audit13 said:
It looks to me like your device has a locked bootloader.
What rom did you try to flash? What did you use to flash it?
Click to expand...
Click to collapse
Hi! this ROM..
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml
I've used RSD Lite...but I think the problem is the bootloader locked...like you said!
Ok, I trying again...let's see what I can do.
Thanks for answer :good:
Ok...I found a new problem, and suspect this is the big problem of all problems!
My computer can't recognize the device, I successfully installed Motorola USB drivers (2.3.9 version) and when I trying to unlock the bootloader ussing Motopocalypse by Dan, doesn't happens...shows the follow message:
Waiting for device...
* daemon not running. starting it now in port 5037 *
* daemon started successfully *
And then, nothings is happens!...not show anything more....
Any suggestions?
Please hel me! :crying:
What OS was originally on the phone? Without an unlocked bootloader, I don't think you can flash an earlier rom version if the original rom version was higher.
I think those zip files needs to flashed via cwm, but I'm not 100% sure. I think that's how I got the Mexico Retail onto my Atrix HD.
You could try this: http://forum.xda-developers.com/showthread.php?t=2299113 or http://forum.xda-developers.com/showthread.php?t=2259661
Stock roms: http://forum.xda-developers.com/showthread.php?t=2209660
audit13 said:
What OS was originally on the phone? Without an unlocked bootloader, I don't think you can flash an earlier rom version if the original rom version was higher.
I think those zip files needs to flashed via cwm, but I'm not 100% sure. I think that's how I got the Mexico Retail onto my Atrix HD.
You could try this: http://forum.xda-developers.com/showthread.php?t=2299113 or http://forum.xda-developers.com/showthread.php?t=2259661
Stock roms: http://forum.xda-developers.com/showthread.php?t=2209660
Click to expand...
Click to collapse
I try manually, but I keep getting the same errors as the automatic method, and not to do, should I throw it away and buy a new motherboard or buy on eBay?
As the phone is AT & T USA, I have no warranty here in Argentina ...
I'm really frustrated .....
Here are the errors:
> fastboot flash system system.img.ext4
sending 'system' (262144 KB) ...
OKAY [19.854s]
writing 'system' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 20.155s
> fastboot flash boot boot.img
sending 'boot' (10240 KB) ...
OKAY [0.865s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 1.137s
if anyone knows anything more, or want help clarify that this LOCKED BOOTLOADER
Wipe and Restore
Checkout my post on this thread. Just skip making a backup.
http://forum.xda-developers.com/showthread.php?t=2394238
PM me and click Thanks if I helped.
lucasantarella said:
Checkout my post on this thread. Just skip making a backup.
http://forum.xda-developers.com/showthread.php?t=2394238
PM me and click Thanks if I helped.
Click to expand...
Click to collapse
Thanks! I would try and let's see what happens!
**sorry for my bad english**
Reactorzero said:
I try manually, but I keep getting the same errors as the automatic method, and not to do, should I throw it away and buy a new motherboard or buy on eBay?
As the phone is AT & T USA, I have no warranty here in Argentina ...
I'm really frustrated .....
Here are the errors:
> fastboot flash system system.img.ext4
sending 'system' (262144 KB) ...
OKAY [19.854s]
writing 'system' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 20.155s
> fastboot flash boot boot.img
sending 'boot' (10240 KB) ...
OKAY [0.865s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 1.137s
if anyone knows anything more, or want help clarify that this LOCKED BOOTLOADER
Click to expand...
Click to collapse
Try using fastboot binaries from skeevy 's thread..
Sent from my MB886 using xda app-developers app
Reactorzero said:
Hi guys! How are you? I hope you are fine, because I'm not lol.
Well, I'm new in this things, but I can install CM9 and 7 in my old devices thanks to your guides and tutorials, I really apreciated!.
But now, I'm stucking with my new phone, because I flashed wrong and I don't know what to do.
Ok let's start to explain my problem:
My phone is stucked in the fastboot screen and no advance. When I press "pwr vol+-" and select Recovery, nothing happens, only showme the "Motorola Dual Core Technology logo" and returns to fastboot.
...........................................................................
AP FastBoot Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
FastBoot Reason: Sticky bit factory_fastboot
...........................................................................
Ok, and when try to enter to recovery screen "pwr, vol+-" it's show me:
...........................................................................
Invalid Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
...........................................................................
Sometimes, indicate "Batery Low"...its very frustrating because I love my ohine but I can't make work and I don't know what is happend...
I see some tutorials, specialy from @sleevydude, to unlock the bootloader, but the "fastboot.exe" appears and dissapears, and I can't acces to program tools...
Another big problem, I'm from Argentina, and my language is spanish, after all, my english is good, and I can understand 90% if you say something...sorry if that is offtopic or something.
I've tryed with the metod from TheMythTeam, but doesn't work...keep stucked...
Ok guys, I hope you help me...miss my phone so much
Click to expand...
Click to collapse
I just realized that your system image says ".ext4" Fastboot does not normally format a partition as ext4 by default, maybe never at all. Make sure you have the correct Fastboot files.
Best of luck!
---------- Post added at 10:40 AM ---------- Previous post was at 10:31 AM ----------
Reactorzero said:
Thanks! I would try and let's see what happens!
**sorry for my bad english**
Click to expand...
Click to collapse
Just to try, flash this Fastboot package with RSD Lite 6.1. I have a feeling this will work.
Package: http://sbfdownload.droid-developers..._FFW-20-27-release-keys-ATT-US_BuildA.xml.zip
** I take no responsibility for any damage done to your phone. **
---------- Post added at 10:49 AM ---------- Previous post was at 10:40 AM ----------
The reason I believe my blast post will work is because your error while trying to flash says
.................................................. .........................
Invalid Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
.................................................. .........................
Click to expand...
Click to collapse
You are flashing a downgraded version of the boot image. If you came from 4.1.1 and are now trying to flash a 4.0.4 boot image, it will fail. Try to flash the package in my last post
lucasantarella said:
I just realized that your system image says ".ext4" Fastboot does not normally format a partition as ext4 by default, maybe never at all. Make sure you have the correct Fastboot files.
Best of luck!
---------- Post added at 10:40 AM ---------- Previous post was at 10:31 AM ----------
Just to try, flash this Fastboot package with RSD Lite 6.1. I have a feeling this will work.
Package: http://sbfdownload.droid-developers..._FFW-20-27-release-keys-ATT-US_BuildA.xml.zip
** I take no responsibility for any damage done to your phone. **
---------- Post added at 10:49 AM ---------- Previous post was at 10:40 AM ----------
The reason I believe my blast post will work is because your error while trying to flash says
You are flashing a downgraded version of the boot image. If you came from 4.1.1 and are now trying to flash a 4.0.4 boot image, it will fail. Try to flash the package in my last post
Click to expand...
Click to collapse
Hi mate, many thanks! I would try your way of flashing, I'm nothing to loose in this point...let's see what happens now and I tell you later, thanks again for your answer
Aingaran said:
Try using fastboot binaries from skeevy 's thread..
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
It doesn`t works in this case...flashing with snapdragon's fastboot :crying:
Did my RSD method work? Have you attempted it yet?
Sent from my Atrix HD
Hello
I have the same problem...
The bootloader is locked, the phone not rooted. I try to flash with RSD lite and Mexico Retail rom, but RSD give an error.
And the message is:
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
Thank your for help!
First try and get to stock. Then get Mexican retail.
Sent from my GT-P3110 using xda app-developers app
lucasantarella said:
First try and get to stock. Then get Mexican retail.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
When I try go back to stock, the phone (and RSD) get a message:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
RSD:
"Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL.
tomchy said:
When I try go back to stock, the phone (and RSD) get a message:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
RSD:
"Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL.
Click to expand...
Click to collapse
Make sure you are using the 4.1.1 fastboot package for RSD Lite. Also make sure you are using RSD Lite 6.1.
tomchy said:
When I try go back to stock, the phone (and RSD) get a message:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
RSD:
"Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL.
Click to expand...
Click to collapse
Unzip the rom zip and open .xml file and remove the line having flash partition gpt_main0.bin and save it, zip again using red, you will be able to flash now..
Related
Hello dear friends!
I have a problem with my Atrix HD. I have problems to flash the boot.img and the system.img.
I tried with RSD Lite, Myth Tools - AHD, Fastboot flash and none have been able to flash it. I downloaded all drivers!
may be permanent brick?
The only thing I shows Battery Low, Battery OK sometimes.
I saw on some forums that the "Factory Cable" has the possibility to flash my phone.
What are the chances of coming back to life my MB886?
Here the details of what I show!
AP Fastboot Flash Mode (s)
10.9b (*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED, Status code: 0
Low Battery
USB Connect
Data Cable
Partition (boot) Downgraded Security Version
Fastboot Reason: Boot Failure.
Waiting for your prompt help
Thank you.
Greetings!
adal_elfather said:
Hello dear friends!
I have a problem with my Atrix HD. I have problems to flash the boot.img and the system.img.
I tried with RSD Lite, Myth Tools - AHD, Fastboot flash and none have been able to flash it. I downloaded all drivers!
may be permanent brick?
The only thing I shows Battery Low, Battery OK sometimes.
I saw on some forums that the "Factory Cable" has the possibility to flash my phone.
What are the chances of coming back to life my MB886?
Here the details of what I show!
AP Fastboot Flash Mode (s)
10.9b (*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED, Status code: 0
Low Battery
USB Connect
Data Cable
Partition (boot) Downgraded Security Version
Fastboot Reason: Boot Failure.
Waiting for your prompt help
Thank you.
Greetings!
Click to expand...
Click to collapse
nothing to panic... hold power+vol up+vol down to power your device off and put it to charge (do not charge with pc/laptop, use a AC power source)
after an hour, follow these steps..
1)download the required firmware from here and fastboot binaries
2)extract the zip and place downloaded fastboot binaries in the extracted directory and open terminal in this directory.
3)type the following commands in order
fastboot flash modem NON-HLOS.bin
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Many Thanks for your help.
I tried to, but I have always problems with Flash.
when flashing the NON-HLOS, there is no problem.
but when I'm flashing the boot.img always gives me this problem.
sending 'boot' (10240 KB) ...
OKAY [0.833s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 1.124s
and when I try the system.img
sending 'system' (30720 KB) ...
OKAY [2.506s]
writing 'system' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 2.842s
and on the phone adds the following:
Partition (Boot) Security Version Downgraded
preflash validation failed for boot
Partition (System) Security Version Downgraded
PIV validation for system block failed
Invalid PIV image: system
What is Security Version Downgraded?
What is PIV?
Again, thank you very much for the help.
waiting for comments
regards
adal_elfather said:
Many Thanks for your help.
I tried to, but I have always problems with Flash.
when flashing the NON-HLOS, there is no problem.
but when I'm flashing the boot.img always gives me this problem.
sending 'boot' (10240 KB) ...
OKAY [0.833s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 1.124s
and when I try the system.img
sending 'system' (30720 KB) ...
OKAY [2.506s]
writing 'system' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 2.842s
and on the phone adds the following:
Partition (Boot) Security Version Downgraded
preflash validation failed for boot
Partition (System) Security Version Downgraded
PIV validation for system block failed
Invalid PIV image: system
What is Security Version Downgraded?
What is PIV?
Again, thank you very much for the help.
waiting for comments
regards
Click to expand...
Click to collapse
What firmware are you trying to flash?
Sent from my MB886 using xda app-developers app
Aingaran said:
What firmware are you trying to flash?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help.
I tried with all 3 of ATT & T. Currently I am trying to "MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip"
Jelly Bean 4.1.1
but with the other 2 (ICS) always send me the same error.
Waiting for your comments
thanks
regards
adal_elfather said:
Thanks for the help.
I tried with all 3 of ATT & T. Currently I am trying to "MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip"
Jelly Bean 4.1.1
but with the other 2 (ICS) always send me the same error.
Waiting for your comments
thanks
regards
Click to expand...
Click to collapse
Try Mexican retail... Last hope... Is your boot loader locked? If so, that may be the reason... Is your phone working... Any ROM inside it?
Sent from my MB886 using xda app-developers app
Aingaran said:
Try Mexican retail... Last hope... Is your boot loader locked? If so, that may be the reason... Is your phone working... Any ROM inside it?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help.
My phone is AT&T and had no unlocked bootloader or modified roms.
regards
adal_elfather said:
Thanks for the help.
My phone is AT&T and had no unlocked bootloader or modified roms.
regards
Click to expand...
Click to collapse
Is your phone working with that att ROM now? Or have you messes up with anything...
Sent from my MB886 using xda app-developers app
Aingaran said:
Is your phone working with that att ROM now? Or have you messes up with anything...
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Not work.
Fastboot load only. that's all it does
adal_elfather said:
Not work.
Fastboot load only. that's all it does
Click to expand...
Click to collapse
what happend to the stock rom? what did you do?
Aingaran said:
what happend to the stock rom? what did you do?
Click to expand...
Click to collapse
I tried to install ZIP from SD card and this was the result.
I already tried flash the 3 firmware stock from AT&T and the Mexican. With all is same result.
Can you get to fastboot mode? Unlock the bootloader and flash stock.
Sent from my PACMAN MATRIX HD MAXX
adal_elfather said:
I tried to install ZIP from SD card and this was the result.
I already tried flash the 3 firmware stock from AT&T and the Mexican. With all is same result.
Click to expand...
Click to collapse
What ROM is that? That you flashed from stock recovery?
Sent from my MB886 using xda app-developers app
---------- Post added at 10:53 PM ---------- Previous post was at 10:46 PM ----------
adal_elfather said:
Not work.
Fastboot load only. that's all it does
Click to expand...
Click to collapse
deeje00 said:
Can you get to fastboot mode? Unlock the bootloader and flash stock.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
how will you unlock your bootloader only with fastboot?!! if that is possible, please give that link, it will help him a lot
deeje00 said:
Can you get to fastboot mode? Unlock the bootloader and flash stock.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Yes, I can get Fastboot mode.
How to unlock the bootloader in fastboot?
Thanks!
Well with any luck your computer might find your phone in the root program so you can root and then unlock.
Sent from my PACMAN MATRIX HD MAXX
Aingaran said:
Try Mexican retail... Last hope... Is your boot loader locked? If so, that may be the reason... Is your phone working... Any ROM inside it?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I tried, but the result is no longer the same.
Try using this to root and then unlock.
http://forum.xda-developers.com/showthread.php?t=2262726
Make sure to install the drivers first.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
Well with any luck your computer might find your phone in the root program so you can root and then unlock.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
I saw that to unlock the bootloader need to be root, you got marked unknown sources. and that I can not do with the phone bricked.
Could you please send me a program or application with which I can do with the phone brick?
Thanks for the help.
deeje00 said:
Try using this to root and then unlock.
http://forum.xda-developers.com/showthread.php?t=2262726
Make sure to install the drivers first.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Ok, thanks, I will try.
Then I notify
deeje00 said:
Try using this to root and then unlock.
http://forum.xda-developers.com/showthread.php?t=2262726
Make sure to install the drivers first.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
I tried to unlock the bootloader, but I can not do it.
I get the following message in the application and nothing happens!
Hey guys, I did something really stupid.
I acquired an Atrix HD through a third party, network/sim unlocked it to work on T-Mobile, and tried to flash 4.1.2 Mexican Retail (MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX) through RSD Lite 6.1.5 after removing the getvar command and.. it failed half way. I forgot to unlock the bootloader before flashing.
Now I'm stuck and I've tried almost everything to fix it. I've searched Google and XDA, in the process I have downloaded Myth Tools, sirhoover_atrixhd_utility, motochopper, motopocalypse, and moto-fastboot, tried them all to the best of my knowledge and nothing is working. I've even edited the XML file to exclude the files it fails on.
Common errors I encounter:
Fastboot reason: Boot failure
Fastboot reason: Flash failure
Partition (boot) Security Version Downgraded
Preflash Validation Failed for boot
Partition (system) Security Version Downgraded
PIV black validation for system failed
Invalid PIV image: system
Worst part is, I can't unlock my bootloader because I need ADB to do so! Recovery will give me ADB but only to sideload (available on certain recoveries I've managed to flash). If you have any ideas or information that could assist me in getting my phone back to normal, whether that's unlocking the bootloader through fastboot or flashing a stock rom sucessfully, I would greatly appreciate it! :good:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
DaveTheRave said:
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
Click to expand...
Click to collapse
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
audit13 said:
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
Click to expand...
Click to collapse
Just tried re-downloading everything on a brand new Windows install on a different computer, still having problems.
No matter how hard I try, I cannot get boot.img or system.img to flash from any Stock firmware, whether it's AT&T, Mex, or Bell
Using snap-fastboot:
snap-fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.788s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
snap-fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.343s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
I'm going to try making a Motorola Factory cable in the meantime. Any other suggestions?
EDIT: Factory cable didn't help.. is there a way to generate a higher security version? No matter what, the bootloader always displays Partition (boot/system) Security Version Downgraded
I really don't want this to end up being a paperweight
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
I just got a new Atrix HD replacement and its showing firmware of 9.8.0Q-97_MB886_FFW-20 . Its not the same as the firmware available here: http://sbf.droid-developers.org/ .... I get the same error even after modifying the XML file in the SBF. Wonder if the last update caused an issue. Running into some similar issue with the replacement. Its not wanting to bootloader unlock.
Did you mount the system before installing?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Sorry I've been MIA, been busy with work.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
Thanks for the reply! I wished this worked for me. After completing the steps successfully, I get:
Partition (boot) Security Version Downgraded
Fastboot Reason: Boot Failure
Code:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
fastboot oem fb_mode_set
...
OKAY [ 0.006s]
finished. total time: 0.006s
fastboot oem fb_mode_clear
...
OKAY [ 0.005s]
finished. total time: 0.005s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.095s]
finished. total time: 3.095s
fastboot erase cache
erasing 'cache'...
OKAY [ 1.669s]
finished. total time: 1.669s
fastboot reboot
rebooting...
finished. total time: 0.005s
audit13 said:
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
Click to expand...
Click to collapse
That's exactly where I got my firmwares from. And to answer your question, I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
DaveTheRave said:
...I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
Click to expand...
Click to collapse
Try logging off and back on to see what happens. For me, using fastboot/adb commands on an x86 Win7 machine works more consistently than using an x64 Win7 machine.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
When I run fastboot oem fb_mode_set, it just says "< waiting for any device >"
Sorry for the late reply. make sure you have adb installed and the drivers for the Atrix. Also,if possible and not in a boot loop or stuck in fastboot, device debugging should be enabled.
Boot problem
Hello here I have a problem and I made everything from my knowledge but It's not fixed.
I have a Motorola Droid Maxx X8 verison XI1080, version 4.4.4, built number SU4.21,
If I install or do something and I switch off and I turn on my phone it disappears as if it is never done and if I try to reinitialize the phone I have a error Fastboot Reason: Boot Failure
If I get the fastboot and I take recovery its said Boot up failed.
I did everything I flashed with RSD and I update it with Motorola update but still nothing we see that the flashing and the update works but on reboot Its has no effect on the phone its stays as if you did nothing.
Please help me! I look forward to a solution, I thank you more.
have u solved the problem
Please explain how u have solved the problem ,my moto g4 plus in same problems
hi guys,
i have with 4.4.2 brasil retail, bootloader unlocked and root
when i try to update with OTA, the phone download the update and when start to install and error
when i try with fastboot
(bootloader) variable not supported!
target max-download-size: 768MB
sending 'partition' (32 kb)...
OKAY [ 0.245s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.099s
and on moto x appears
getvar max-sparse-size
getvar max-download-size
downloading 32768 bytes
done
downgraded security versiong
update gpt-main version failed
preflash validation failed for gpt
You need unroot it!!!! The ota can't be installed using root or custom recovery !!!
I recommend you that intall 4.4.2 retal brasil stock rom again ..... Then you can receive OTA and install it [emoji6]
i already unroot, reset all the phone, and still can't update
Maybe you have custom recovery
Enviado desde mi XT1053 mediante Tapatalk
i reinstall stock recovery and still the same error
and i using rsd i can't install too
Your moto shows gpt error.... that error showed during a downgrade error in my moto x (recovery error) [emoji53]
flash full 4.4.2 using RSD.
when i try using rsd shows to me
failed flashing process. 2/16 flash partition "gpt.bin" -> Phone returned FAIL.
and in moto the same error I had before
mgoliver said:
when i try using rsd shows to me
failed flashing process. 2/16 flash partition "gpt.bin" -> Phone returned FAIL.
and in moto the same error I had before
Click to expand...
Click to collapse
A couple suggestions:
If possible, use a USB 2.0 port, and NOT a USB 3.0 port.
Try on a different PC, if possible
mgoliver said:
when i try using rsd shows to me
failed flashing process. 2/16 flash partition "gpt.bin" -> Phone returned FAIL.
and in moto the same error I had before
Click to expand...
Click to collapse
did you flash a different recovery or fastboot/bootloader ????
I recognized that error..... occurs when you trying to downgrade recovery stock or fastboot/bootloader. [emoji6]
Enviado desde mi XT1053 mediante Tapatalk
samwathegreat said:
A couple suggestions:
If possible, use a USB 2.0 port, and NOT a USB 3.0 port.
Try on a different PC, if possible
Click to expand...
Click to collapse
i already try
are you sure that you are flashing 4.4.2 ????
check it..... maybe is 4.2.2 [emoji53]
gpt. bin error is about downgrades
maybe you did manual flash using wrong gpt.bin.
---------- Post added at 02:55 AM ---------- Previous post was at 02:38 AM ----------
maybe you installed/flashed in manual mode the 4.4.3 gpt.bin (bootloader). and now you are trying to install 4.4.2 gpt.bin and the system shows gpt.bin error (downdrade error)
THANK YOU GUYS
i was forgetting to delete one line of code, i delete this line and flash using rsd
but THANK YOU
mgoliver said:
THANK YOU GUYS
i was forgetting to delete one line of code, i delete this line and flash using rsd
but THANK YOU
Click to expand...
Click to collapse
the gpt.bin line ???!!!!!!
I hope your moto x don't get bricked after ota update [emoji20]
omias said:
the gpt.bin line ???!!!!!!
I hope your moto x don't get bricked after ota update [emoji20]
Click to expand...
Click to collapse
Probably the getvar max-download-size (Step 4 in the Return to Stock thread)
I've seen several people overlook that step somehow...
Just another reason I try to push the manual method instead of using RSD Lite. You don't need to edit the XML file when you use the manual method, and less can go wrong.
Long story short, woke up with my N6 stuck at the bootloader screen and cannot do anything at it. I can only see my serial number and if I try anything else, it reloads bootloader. I am trying to flash back to a stock 6.0.1 image, however I keep getting this error while trying to do so.
C:\Program Files (x86)\Android\android-sdk\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.332s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 11.542s
I have tried Nexus Root Toolkit, tried flashing all and tried flashing each image one by one but I still get this "(bootloader) Failed to flash partition FAILED (remote failure)" on all attempts. Phone does show up if I try fastboot devices, and I have tried this on two different computers. Device is also unlocked as well, and I even tried flashing older versions of Lolipop but they all give me the same error. Drivers work fine, and I have everything up to date in terms of bootloader and Andriod SDK. I am starting to think that there is physical damage inside the phone, however I do not know how or why this occurred randomly. Any help would be awesome, as I am very new to flashing images onto my phone and frankly I am 99% sure that my warranty is out, and I really don't want to pay $175 cost .
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
coremania said:
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
Click to expand...
Click to collapse
I've already tried method 2 before so I tried method 1 with the program, and it gives me the same exact error as before. Thanks for the help though, it was worth a shot!
Are you able to enter twrp ? Try to reflash Bootloader through twrp
coremania said:
Are you able to enter twrp ? Try to reflash Bootloader through twrp
Click to expand...
Click to collapse
I did not have TWRP installed on my phone since I had it completely stock and unrooted, so I tried installing it in the hopes of that some chance it would work and I could access it. Still getting the same error as before (grumble grumble). It is starting to look like more of a physical problem to me, but thanks for the advice. Here is what I got...
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11585 KB)...
OKAY [ 0.468s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 6.380s
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
This was going to be my suggestion!!
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Click to expand...
Click to collapse
Any image I even try to flash I get the error with, no matter what order or which one I pick. I redownloaded the image again and still nothing, so I don't think it's a corrupt download. What is the unlock command? Sorry for being a noob, never heard of it since all my knowledge is from reading tons of flashing guides on the internet lol.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
Alright, I downloaded the OTA file and got the process to about 47% when suddenly I keep running into the error of "E:Can't open /cache/recovery/log" then followed by more things it can't open. I tried the OTA twice and it gets stuck on that same exact spot. I tried the wipe data/factory reset option from the recovery mode and I get a similar error of "Can't mount", "Can't open", "failed to mount" the recovery log. It seems like there is a problem with the recovery log files (or the folder) on my phone, but I have no idea what that means. I will mess around with some more and try Googling the source of error, but thank you for the help.
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Click to expand...
Click to collapse
Oh yes, my device has already been unlocked from the start so that wasn't a problem. I still get the same error when I try to flash anything, including TWRP which means I have to install the OTA. The problem is a get a separate error when I try to install the OTA, which the only solution being to flash my device (or at least that is what most people have been saying when I googled the can't open cache recovery error) so this is a giant goose chase which leads me back to the start :/. I will keep trying however, I refuse to give up after going this far!
holeindalip said:
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Should I try fastboot erase cache and then fastboot format cache? Would refresh the cache on there? I only just learned the erase command so I am not exactly sure what I should try.
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
holeindalip said:
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I get the same failure error while trying to format and erase, so I am guessing something is really wrong with my phone or the bootloader is messed up beyond repair. I guess it could be the cable I am using as well, that is one thing I did not take into factor so I will try with another cable if I find a spare. Flashing might be beyond my solution at this rate though... Thanks anyways for the help.
blanco2701 said:
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
Click to expand...
Click to collapse
I really should have had TWRP installed before I guess lol, but I still get the same failure error. My phone has more problems than a teenager going through puberty I swear, thanks for the help though.
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
coremania said:
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
Click to expand...
Click to collapse
I tried it with another wire and nothing changed, and then I tried taking out my sim card and trying it.... and it worked! It flashed everything normally and loaded up just fine. I don't know whether I should be furious or happy but thank you and everyone who helped. Who would have known just taking out the sim card could have saved me 2+ days of stressing and trail and error. Once again thanks, you really saved me lol.
You're welcome, nice your phone works again !
Don't forget to activate oem unlock and debugging in the Developer options, and flash twrp, so maybe more save for upcoming problems
skipsoft android toolkit maybe help you in future
I tried to force update to b170, resored the backup from howtoroot thread and flashed stock recovery from within twrp, rebooted and my devicve is stuck on
ERROR MODE
err no11 recovery image
errror no 2 load failed
doesnt boot to fastboot, cant be seen by pc
cant even turn it off... it is infinite loop if i hold power button it boots "huawei logo for 1 second and again error mode"
Please help me to recover my device :/
Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect
aciupapa said:
Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect
Click to expand...
Click to collapse
How to boot into TWRP when after flashing it reboot infinitely on error mode and can't shutdown it.
Pressing VolumeUp for eRecovery go to error mode
aciupapa said:
Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect
Click to expand...
Click to collapse
HI man I have the some problem error mode screen but in oreo update p8 lite 2017 any solution plz
p181153 said:
How to boot into TWRP when after flashing it reboot infinitely on error mode and can't shutdown it.
Pressing VolumeUp for eRecovery go to error mode
Click to expand...
Click to collapse
If you solved your problem tell me plz plz plz
jalel25 said:
If you solved your problem tell me plz plz plz
Click to expand...
Click to collapse
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community
p181153 said:
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community
Click to expand...
Click to collapse
I hope one of them help me ?
jalel25 said:
I hope one of them help me
Click to expand...
Click to collapse
Wait for moment when battery is at 0% and phone will shut down. Boot into fastboot and flash TWRP recovery, create backup, wipe all on device and reboot it.
mijanto313 said:
Wait for moment when battery is at 0% and phone will shut down. Boot into fastboot and flash TWRP recovery, create backup, wipe all on device and reboot it.
Click to expand...
Click to collapse
I tried that. My phone has been in this state for probably a month already. I heard the only solution is DC Phoenix via testpoint method.
Try Firmware finder for huawei + erecovery method , which is :
- download firmware finder on *another android phone* and search for exact phone model (ex : PRA-LA1C185)
- choose the very first firmware down the list
- Get an update thorugh dns >> Manually >> Register update
- After that , reboot your bricked phone into erecovery by ( power + volume*+*)
- press download recovery and last firmware
- wait till getting package
- by now should firmware start downloading
- let phone complete it's work and reboot
Hope that's work for you ?
p181153 said:
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community
Click to expand...
Click to collapse
About your problem - If your phone throws errors when you try to boot into TWRP, then something is wrong with TWRP (for example you flashed incompatibile version). Boot into bootloader aka fastboot mode and try to flash TWRP again from there.
Off-topic part: In my opinion, this is the most helpful & best community about Android phones. Noone is going to help you if you keep spamming. Just be patient, we are humans, not robots
Botar230 said:
About your problem - If your phone throws errors when you try to boot into TWRP, then something is wrong with TWRP (for example you flashed incompatibile version). Boot into bootloader aka fastboot mode and try to flash TWRP again from there.
Off-topic part: In my opinion, this is the most helpful & best community about Android phones. Noone is going to help you if you keep spamming. Just be patient, we are humans, not robots
Click to expand...
Click to collapse
Hi,i bricked yesterday but today I installed the wrong TWRP as you said and I do not have access to anything .. Do you have a solution? Some say the bootloader is locked..
thank's !
Freysheur said:
Hi,i bricked yesterday but today I installed the wrong TWRP as you said and I do not have access to anything .. Do you have a solution? Some say the bootloader is locked..
thank's !
Click to expand...
Click to collapse
Bootloader can't be locked if you managed to flash TWRP. Do the following:
1. Make sure the phone is turned off
2. Hold Vol- and plug the usb cable in
3. You should be in bootloader aka fastboot mode
4. Flash TWRP using (p8 lite 2015) fastboot flash recovery <path>.img
5. fastboot reboot
Botar230 said:
Bootloader can't be locked if you managed to flash TWRP. Do the following:
1. Make sure the phone is turned off
2. Hold Vol- and plug the usb cable in
3. You should be in bootloader aka fastboot mode
4. Flash TWRP using (p8 lite 2015) fastboot flash recovery <path>.img
5. fastboot reboot
Click to expand...
Click to collapse
Hi bro', i love you :silly: I did not know the technic for enter in fastboot without volume "-" .
Okay, the bootloader and FRP is unlocked but before i'am on Nougat and i have passed on Oreo. For flashed the TWRP my commands are " fastboot flash recovery_ramdisk recovery.img ".
And i have a error message when i flash the ROM Stock or TWRP with the normal commands as " fastboot flash recovery recovery.img ".
My error message it's :
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (11204 KB)...
OKAY [ 0.290s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.305s
Thank's for your reponse, sorry for my english, i'm french !
Freysheur said:
Hi bro', i love you :silly: I did not know the technic for enter in fastboot without volume "-" .
Okay, the bootloader and FRP is unlocked but before i'am on Nougat and i have passed on Oreo. For flashed the TWRP my commands are " fastboot flash recovery_ramdisk recovery.img ".
And i have a error message when i flash the ROM Stock or TWRP with the normal commands as " fastboot flash recovery recovery.img ".
My error message it's :
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (11204 KB)...
OKAY [ 0.290s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.305s
Thank's for your reponse, sorry for my english, i'm french !
Click to expand...
Click to collapse
Use fastboot flash recovery only on 2015 variant. You need to use recovery ramdisk on 2017 variant
Sent from my LG-K220 using XDA Labs
Botar230 said:
Use fastboot flash recovery only on 2015 variant. You need to use recovery ramdisk on 2017 variant
Sent from my LG-K220 using XDA Labs
Click to expand...
Click to collapse
Why before i used the flash recovery and it worked ?
Do you have an answer to the error " FAILED (remote: partition length get error) " ?
---------- Post added at 11:25 AM ---------- Previous post was at 10:40 AM ----------
Ok, i try install ROM via TWRP..
I have no errors but i bootloop again.. and he puts me in the menu Huawei eRecovery..
---------- Post added at 11:39 AM ---------- Previous post was at 11:25 AM ----------
I try install ROM via Fastboot CMD.
C:\Users\Alban\Desktop\fastboots>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.011s
C:\Users\Alban\Desktop\fastboots>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15524 KB)...
OKAY [ 0.389s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.413s
Hmmmm, i installed MorfuZ rom, he boot but he restart alone..
So I do not have a rom ...
jalel25 said:
I hope one of them help me
Click to expand...
Click to collapse
Everyone, I made a guide on my website to unbrick the device.
Here is the link:
http://mrviking.simplesite.com/440246066