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
Related
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..
Hi XDA guys, so i have this trouble and i don't know what to do, the problem is that my phone get bricked after updating whatsapp and now i can only boot the phone into fastboot an when i try to unlock the bootlader i get this, so help me please!!
Code:
(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.603s
Victor Gtz said:
Hi XDA guys, so i have this trouble and i don't know what to do, the problem is that my phone get bricked after updating whatsapp... [/CODE]
Click to expand...
Click to collapse
Hi, maybe you could give us some more clear infos of what you have done exactly...
Why you want to unlock your bootloader?
Try to reflash an original firmware with RDS and if you want root use "TwerkMyMoto"...
5m00v3 said:
Hi, maybe you could give us some more clear infos of what you have done exactly...
Why you want to unlock your bootloader?
Try to reflash an original firmware with RDS and if you want root use "TwerkMyMoto"...
Click to expand...
Click to collapse
Well mi phone was working fine with stock firmware and locked bootlader, so i recive this whatsapp update and after this installation the phone shut down and get on again but with the boot logo of motorola and get stuck in it, and if i enter in fastboot non of the options work only the phone gets frized, so i was triyin to unlock the bootloader, for a chance to fix the problem with an update via RSD, but when i try to unlock the bootlader it gives me the error as i mention in the first post and i dont know what do
Victor Gtz said:
...so i was triyin to unlock the bootloader, for a chance to fix the problem with an update via RSD...
Click to expand...
Click to collapse
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
I got yesterday also an Update-Information from whatsapp. I will NOT install until it is confirmed as non-bricking. Thx for your info/warning!
5m00v3 said:
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
I got yesterday also an Update-Information from whatsapp. I will NOT install until it is confirmed as non-bricking. Thx for your info/warning!
Click to expand...
Click to collapse
i Just try using RDS Lite but in the step 4 the reboot never boot and the flash fail
Can you enter recovery? Selecting it in the fastboot menu, what happens? In RSD does it flashes and only in the reboot portion it fails? Did you try to turn it on without the external SD card?
As far as i can tell the device is trying to use the linux discard command, it seems like a wipe that gone wrong.
regnotp synagogue
thiagomtl said:
Can you enter recovery? Selecting it in the fastboot menu, what happens? In RSD does it flashes and only in the reboot portion it fails? Did you try to turn it on without the external SD card?
As far as i can tell the device is trying to use the linux discard command, it seems like a wipe that gone wrong.
Click to expand...
Click to collapse
Hi thiagomtl let me answer your questions, when i try to enter in recovery the phone gets stuck again with the motorola boot logo and after a while returns to fastboot mode, and when i try to flash whit RSD in the step 4 that is reboot, on the phone stays a command that says Rebooting Droidboot and nothing happens, and yeah when i do this operaions i always remove the sim card and the sd card , so if you now something ill appreciate a lot it!!
Try those in fastboot:
fastboot erase data
fastboot erase cache
After try RSD again.
5m00v3 said:
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
Click to expand...
Click to collapse
Are you sure about that ?
For original firmware there is no need to unlock
thiagomtl said:
Try those in fastboot:
fastboot erase data
fastboot erase cache
After try RSD again.
Click to expand...
Click to collapse
I already do that but im still getting this error
BLKDISCARD ioctl /dev/block/mmcblk0 fail
I am guessing that is an error in the emmc, the problem is that i don't know how to fix it
Victor, I'm having the exact same problem. Did you find any solution?
I'm having the exact same problem!!
What I did was that when it gets stuck waiting for reboot I did reboot it manually into fastboot mode again and process continues. The problem is that it gets stuck again when flashing the system partition. Bootloader won't let me erase the partition nor flash it.
Tried unlocking the bootloader and:
(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: 9.666s
Is there a way to know the original provider of the phone, to make sure I'm using the correct firmware?
ismael_mj23 said:
I'm having the exact same problem!!
What I did was that when it gets stuck waiting for reboot I did reboot it manually into fastboot mode again and process continues. The problem is that it gets stuck again when flashing the system partition. Bootloader won't let me erase the partition nor flash it.
Tried unlocking the bootloader and:
(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: 9.666s
Is there a way to know the original provider of the phone, to make sure I'm using the correct firmware?
Click to expand...
Click to collapse
You got a serious bug. There is a huge change your device is now broken beyond repair, i hope not. But can u access the recovery partition? Can u flash a custom boot image?
Hazou said:
You got a serious bug. There is a huge change your device is now broken beyond repair, i hope not. But can u access the recovery partition? Can u flash a custom boot image?
Click to expand...
Click to collapse
I also having the same problem after force power on/off when hang during TWRP format. Now the unit in hard brick. If able to force temporary boot into recovery using ram instead of rom, might have some hope. But it looks like no way to boot from ram. :crying:
same prob as victor gtz
fsd lite freezes at step 4, unlock bootloader doesnt work and so on and so forth, so anybody got a clue what to do?
Dudes
Same problem here, rsdlite didnt work for me and the bootloader cant be unlocked with the same error message. Theres any way to solve this? i read once that you can recover the android from the dead even if the boot isnt working, maybe thats not true at all.....
Neyzik said:
Dudes
Same problem here, rsdlite didnt work for me and the bootloader cant be unlocked with the same error message. Theres any way to solve this? i read once that you can recover the android from the dead even if the boot isnt working, maybe thats not true at all.....
Click to expand...
Click to collapse
It's true, but not for all devices. And if u have the above, the nand memory is broken. That can only be repaired by some kind of powercycle on chip level or anything.
I Can't flash recovery for my moto x, I have unlocked the bootloader and appears to me on fastboot: Device is UNLOCKED. Status Code:3
I don't know if this is right, but I can't flash a recovery in it.
Error:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8030 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.116s
I tested various recovery's but don't work.
Sorry for my bad english
Murilo900 said:
I Can't flash recovery for my moto x, I have unlocked the bootloader and appears to me on fastboot: Device is UNLOCKED. Status Code:3
I don't know if this is right, but I can't flash a recovery in it.
Error:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8030 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.116s
I tested various recovery's but don't work.
Sorry for my bad english
Click to expand...
Click to collapse
Are you using mfastboot? You should be..
Sent From Droid Ultra
In addition to mFastboot, make sure your battery is charged more than 80%
Caseyk621 said:
Are you using mfastboot? You should be..
Sent From Droid Ultra
Click to expand...
Click to collapse
KidJoe said:
In addition to mFastboot, make sure your battery is charged more than 80%
Click to expand...
Click to collapse
Yes,
I did on mfastboot and appears the same thing, and the battery is full, when I try to flash on moto x appears : getvar-download-size
Murilo900 said:
Yes,
I did on mfastboot and appears the same thing, and the battery is full, when I try to flash on moto x appears : getvar-download-size
Click to expand...
Click to collapse
What ROM is on your phone right now? Which recovery are you trying to flash?
What state was your phone in when you started trying to flash recovery?
KidJoe said:
What ROM is on your phone right now? Which recovery are you trying to flash?
What state was your phone in when you started trying to flash recovery?
Click to expand...
Click to collapse
The ROM on my phone is 4.4.2 KitKat, I tried to flash twrp recovery 2.6.3.1 and cwm recovery for motox
The state was the same, I unlocked bootloader, following tutorials on internet but I'm stuck on flash the recovery because this problem, I get this error and on my phone appears getvar-download-size, and Download Failed.
Murilo900 said:
The ROM on my phone is 4.4.2 KitKat, I tried to flash twrp recovery 2.6.3.1 and cwm recovery for motox
The state was the same, I unlocked bootloader, following tutorials on internet but I'm stuck on flash the recovery because this problem, I get this error and on my phone appears getvar-download-size, and Download Failed.
Click to expand...
Click to collapse
Ok.
Try the mfastboot from inside -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip (will have to rename fastboot.exe to mfastboot.exe).. or from -> http://mark.cdmaforums.com/X-STUFF/ADB-MFASTBOOT.zip they are the ones I use and they have worked for me.
and is this the twrp you are using? -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Oh god! Thanks, this mfastboot you just send works!, I don't know if the problem was my mfastboot that I have here, but finally I flashed! Leveraging the topic can you suggest me some roms for moto x, and if you know some way to take off the boot the sign that the bootloader is unlocked blablabla, Anyway thank you.
Murilo900 said:
Oh god! Thanks, this mfastboot you just send works!, I don't know if the problem was my mfastboot that I have here, but finally I flashed! Leveraging the topic can you suggest me some roms for moto x, and if you know some way to take off the boot the sign that the bootloader is unlocked blablabla, Anyway thank you.
Click to expand...
Click to collapse
I run stock, unlocked and rooted, so I can't suggest an alternate roms.
As for the unlocked bootloader warning message... sure. there is a big thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961 start around post 150 of that thread for how to make your own... in a couple of hours I'll refresh this file -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip adding even more logo.bin files (i have about 7 or 8 more to test before I can re-zip and upload it)
HELP!!
I am at a loss. No matter what fastboot/mfastboot I use, no matter what YouTube video I follow, I can not flash recovery.
I get the same error as the OP. I tried the links posted a few posts up, it wont work.
I type the commands, I get the top error message (among others depending on the mfastboots I try) and then nothing.
I am truly at a loss.
Verizon Developer Moto X
4.4.2
Device is: Unlocked
Status Code: 3
In one video I watched it said that I needed to have it say Status Code:1. Is that where I am going wrong?
Any help would be greatly appreciated.
Thanks!!
n99hockey said:
I am at a loss. No matter what fastboot/mfastboot I use, no matter what YouTube video I follow, I can not flash recovery.
I get the same error as the OP. I tried the links posted a few posts up, it wont work.
I type the commands, I get the top error message (among others depending on the mfastboots I try) and then nothing.
I am truly at a loss.
Verizon Developer Moto X
4.4.2
Device is: Unlocked
Status Code: 3
In one video I watched it said that I needed to have it say Status Code:1. Is that where I am going wrong?
Any help would be greatly appreciated.
Thanks!!
Click to expand...
Click to collapse
What recovery are you trying to flash? Stock or other? Unlocked Status Code 3 is needed to flash an alternate or 3rd party recovery.
Besides the error listed in the first post, exactly what "others" do you see as error codes?
Things to try... (in no special order)
this mfastboot -> mfastboot-442.zip
re-download the recovery you are trying to flash
update your ADB and Platform Tools
There are several versions of TWRP that can work.
Unofficial TWRP 2.6.3.1 for 4.4 -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Unofficial TWRP 2.7.0.0 -> http://androidhosting.org/Devs/Dhacker29/MotoX/TWRP-2.7.0.0-moto_msm8960dt.img
Official TWRP 2.7.1.1 -> http://techerrata.com/browse/twrp2/ghost
of those, I've only used the 2.6.3.1 on my VZW Dev X with 4.4.2 and below.
KidJoe said:
What recovery are you trying to flash? Stock or other? Unlocked Status Code 3 is needed to flash an alternate or 3rd party recovery.
Besides the error listed in the first post, exactly what "others" do you see as error codes?
Things to try... (in no special order)
this mfastboot -> mfastboot-442.zip
re-download the recovery you are trying to flash
update your ADB and Platform Tools
There are several versions of TWRP that can work.
Unofficial TWRP 2.6.3.1 for 4.4 -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Unofficial TWRP 2.7.0.0 -> http://androidhosting.org/Devs/Dhacker29/MotoX/TWRP-2.7.0.0-moto_msm8960dt.img
Official TWRP 2.7.1.1 -> http://techerrata.com/browse/twrp2/ghost
of those, I've only used the 2.6.3.1 on my VZW Dev X with 4.4.2 and below.
Click to expand...
Click to collapse
Thanks for the reply.
However I should have known better, I changed the USB port and it worked just fine with the mfastboot I downloaded longer than I would like to admit before I posted my question.
</sigh>
Still can't flash custom recovery
I have a Verizon XT1060 Developer Edition. Unlocked bootloader. Drivers seem to be installed correctly, "Fastboot devices" identifies the phone. Battery is 90%+. Fastboot menu says "Device is unlocked. Status Code 3". I have tried different USB ports on the PC, different cables to connect the phone and just about every other variable that I can think of.
I have followed all of the suggestions listed in this post and I still cannot flash a custom recovery. I have tried multiple versions of TWRP, Fastboot, Mfastboot etc.. Here is the error message...
(bootloader) Variable not supported!
error: cannot open 'twrp-2.6.3.1-ghost-4.4.img'
Actually depending on the method I am trying at the time, fastboot mfastboot etc., I may get a couple of additional lines that mention Max download size etc. but it always starts with the bootloader comment and ends with "Cannot open......"
Searching for "(bootloader) Variable not supported!" returns a lot of hits but I have not found anything to clear the issue. Any help would be appreciated.
Ric214 said:
....Here is the error message...
(bootloader) Variable not supported!
error: cannot open 'twrp-2.6.3.1-ghost-4.4.img'
...
Click to expand...
Click to collapse
That usually means that mFastboot (or fastboot) can't find the IMG file on your PC.
My first question would be... does that file exist in your current directory/folder?
i.e... at the command prompt.. type dir *.img is the twrp file listed there? If no, that is your issue. change to the folder (directory) where the TWRP IMG file is, and try it.
It is there. Here is what I got.
C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86
_64-20140321\sdk\platform-tools>dir *.img
Volume in drive C is OS
Volume Serial Number is 76F9-C97B
Directory of C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bund
le-windows-x86_64-20140321\sdk\platform-tools
06/13/2014 10:54 PM 8,417,280 openrecovery-twrp-2.7.1.1-ghost.img
06/03/2014 11:10 PM 10,090,496 twrp-2.6.3.1-ghost-4.4.img
2 File(s) 18,507,776 bytes
0 Dir(s) 426,324,336,640 bytes free
Since this has been driving me crazy for a couple of days I have several folders with different versions of Fastboot and Mfastboot in them along with some different versions of TWRP and CWM and I am getting the same error with all of them. This last time I just stuck the TWRP file in my platform -tools folder to try and make sure I had a good Fastboot file.
Thanks for the reply. If you have any other ideas I am eager to hear them.
Ric214 said:
It is there. Here is what I got.
C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86
_64-20140321\sdk\platform-tools>dir *.img
Volume in drive C is OS
Volume Serial Number is 76F9-C97B
Directory of C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bund
le-windows-x86_64-20140321\sdk\platform-tools
06/13/2014 10:54 PM 8,417,280 openrecovery-twrp-2.7.1.1-ghost.img
06/03/2014 11:10 PM 10,090,496 twrp-2.6.3.1-ghost-4.4.img
2 File(s) 18,507,776 bytes
0 Dir(s) 426,324,336,640 bytes free
Since this has been driving me crazy for a couple of days I have several folders with different versions of Fastboot and Mfastboot in them along with some different versions of TWRP and CWM and I am getting the same error with all of them. This last time I just stuck the TWRP file in my platform -tools folder to try and make sure I had a good Fastboot file.
Thanks for the reply. If you have any other ideas I am eager to hear them.
Click to expand...
Click to collapse
Had you made ANY prior modifications to your unit before now? Any possibility you used one of the previous root/write protect disable exploits, and THEN got the bootloader unlocked?
I've seen alot of users in this situation recently -thanks to middleman
I suggest you follow the 'return to stock' thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You should flash the 4.4.2 VZW SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
SBFing back to stock is very different from a Factory Reset in that it can actually repair a damaged filesystem, and even un-do any previous exploits you may have used.
There are 2 methods - many report that the "Manual Method" is easier than using RSD Lite. Either should work equally well, but pay close attention to the steps.
You will want to do a couple of things just a little bit differently. First, use mfastboot as suggested by KidJoe for ALL flashing commands.
Second, once your phone has been placed into bootloader mode (AP Fastboot), before you proceed with the fastboot commands listed under Manual Method, do this first:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Your device should reboot back to the bootloader. NOW, proceed with the entire list of commands (using mfastboot for all of them). Yes, you will be flashing partition and motoboot again...don't worry. It is intentional.
After you have completed the rest of the steps, you will likely be able to flash TWRP (or custom recovery of your choice) without issue.
Let us know if this fixes your issues.
samwathegreat said:
Had you made ANY prior modifications to your unit before now? Any possibility you used one of the previous root/write protect disable exploits, and THEN got the bootloader unlocked?
I've seen alot of users in this situation recently -thanks to middleman
I suggest you follow the 'return to stock' thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You should flash the 4.4.2 VZW SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
SBFing back to stock is very different from a Factory Reset in that it can actually repair a damaged filesystem, and even un-do any previous exploits you may have used.
There are 2 methods - many report that the "Manual Method" is easier than using RSD Lite. Either should work equally well, but pay close attention to the steps.
You will want to do a couple of things just a little bit differently. First, use mfastboot as suggested by KidJoe for ALL flashing commands.
Second, once your phone has been placed into bootloader mode (AP Fastboot), before you proceed with the fastboot commands listed under Manual Method, do this first:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Your device should reboot back to the bootloader. NOW, proceed with the entire list of commands (using mfastboot for all of them). Yes, you will be flashing partition and motoboot again...don't worry. It is intentional.
After you have completed the rest of the steps, you will likely be able to flash TWRP (or custom recovery of your choice) without issue.
Let us know if this fixes your issues.
Click to expand...
Click to collapse
I had not done any modifications prior to unlocking the bootloader but going back to stock is about the only thing that I could think of that I have not already tried. I will give this a shot tomorrow night and let you know how it went. Thanks for your help.
Ric214 said:
I had not done any modifications prior to unlocking the bootloader but going back to stock is about the only thing that I could think of that I have not already tried. I will give this a shot tomorrow night and let you know how it went. Thanks for your help.
Click to expand...
Click to collapse
One last thing I can suggest before return to stock:
Are you trying to flash the recovery -while booted into Android-? If so, you have to have USB Debugging enabled. Some users have experienced difficulty using fastboot while booted into Android even with USB debugging enabled.
----------------
You can try flashing from bootloader (AP Fastboot Mode) instead.
To do this, unplug the phone from USB. Power off the phone. Hold down VOL DOWN and power the phone back on. You should now be booted into bootloader.
Now plug the USB back in, and try:
mfastboot flash recovery twrp_filename.img
samwathegreat said:
One last thing I can suggest before return to stock:
Are you trying to flash the recovery -while booted into Android-? If so, you have to have USB Debugging enabled. Some users have experienced difficulty using fastboot while booted into Android even with USB debugging enabled.
----------------
You can try flashing from bootloader (AP Fastboot Mode) instead.
To do this, unplug the phone from USB. Power off the phone. Hold down VOL DOWN and power the phone back on. You should now be booted into bootloader.
Now plug the USB back in, and try:
mfastboot flash recovery twrp_filename.img
Click to expand...
Click to collapse
Thanks for the advice but I am not booted into Android. I started with the phone off and got into the bootloader exactly as you suggested. I will have some time over the next few days to flash back to stock and start over again. I will post the results. In the meantime if you think of anything else, let me know. Thanks for your help.
Ric214 said:
Thanks for the advice but I am not booted into Android. I started with the phone off and got into the bootloader exactly as you suggested. I will have some time over the next few days to flash back to stock and start over again. I will post the results. In the meantime if you think of anything else, let me know. Thanks for your help.
Click to expand...
Click to collapse
try shortening the path the IMG resides in...
i.e. make a folder off the root of drive C call it FLASH... drop the TWRP.img into c:\flash and try flashing it from there.
DL'ed 5.0.1 and went to flash as I have done dozens of times. Always perform a manual fastboot flash ... I've had issues in the past nothing big. This time I'm kind of stumped. I have ATT N6, rooted, TWRP and the only single mod was the tap2wake. When I got to system.img I got (bootloader) Data size exceeds download buffer
I didn't 1st flash my TWRP, but then I did after this issue.
Thoughts ? I did roll back to my nandroid, but I would like to know what happened and why. Thanks!!
Are you using the latest fastboot version from the SDK?
El Daddy said:
Are you using the latest fastboot version from the SDK?
Click to expand...
Click to collapse
Yes, I made sure to dl the latest.
Here is what I'm getting;
fastboot flash system system.img
sending 'system' (1640247 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
Don't use the flash-all script. Do it manually line by line.
Nucleonic said:
Don't use the flash-all script. Do it manually line by line.
Click to expand...
Click to collapse
Thats exactly what I'm doing.
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.177s]
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) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.415s]
finished. total time: 0.592s
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
sending 'radio' (67169 KB)...
OKAY [ 2.619s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.948s]
finished. total time: 3.568s
fastboot flash system system.img
sending 'system' (1640247 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.002s
j
I flashed it earlier today and it worked fine. I haven't updated my SDK in about 2 weeks and everything worked just fine. I manually sent over each package before flashing another ROM.
I've never had this issue before. I'm wondering if it has anything to do with this being an ATT phone? Besides that I have no idea. I've searched and searched and no good answer. I may drop the factory 5.0 in if I can't find an answer.
I had a problem like this when I thought I bricked my phone in an earlier thread. Try doing this first:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then flash the individual line items one at a time again. It worked for me.
Thanks for all the advice, this is what ultimately worked;
Ahem, I used a freaking Win7 PC!
Are you kidding me? I live and breath by my MacAir. I've never had an issue like this before. I finally decided to pull out my work PC, made sure it had the newest fastboot, extracted the .imgs and it worked.
So, XDA masters, why? I don't understand it. I made sure I dl'ed the newest SDK, pulled out the adb folder that included fastboot. Yet it would not break up the system.img.
jackpollard said:
Thanks for all the advice, this is what ultimately worked;
Ahem, I used a freaking Win7 PC!
Are you kidding me? I live and breath by my MacAir. I've never had an issue like this before. I finally decided to pull out my work PC, made sure it had the newest fastboot, extracted the .imgs and it worked.
So, XDA masters, why? I don't understand it. I made sure I dl'ed the newest SDK, pulled out the adb folder that included fastboot. Yet it would not break up the system.img.
Click to expand...
Click to collapse
I was getting ready to recommend you run the fastboot reboot bootloader command a few times in between some of those flashes. Some of the guides recommend you do that. Because of buffer overflow maybe? idk.
crashercarlton said:
I was getting ready to recommend you run the fastboot reboot bootloader command a few times in between some of those flashes. Some of the guides recommend you do that. Because of buffer overflow maybe? idk.
Click to expand...
Click to collapse
Hummm, that is a good suggestion, I wonder if rebooting my Mac would of done anything. I had an older fastboot, when I updated it to the newest one I didn't close terminal, i wonder if maybe it didn't release it. Very odd, I would like to know why this happened. I'm going to check the logs to see if they say anything. I suppose if doing it from a Win machine worked, I would lean towards driver, fastboot/adb. Thanks for all the feedback!
Please note they recently released a new copy of fastboot and adb, about the same time as the N6. Updating it for me helped.
Sent from my Nexus 6 using XDA Free mobile app
jackpollard said:
DL'ed 5.0.1 and went to flash as I have done dozens of times. Always perform a manual fastboot flash ... I've had issues in the past nothing big. This time I'm kind of stumped. I have ATT N6, rooted, TWRP and the only single mod was the tap2wake. When I got to system.img I got (bootloader) Data size exceeds download buffer
I didn't 1st flash my TWRP, but then I did after this issue.
Thoughts ? I did roll back to my nandroid, but I would like to know what happened and why. Thanks!!
Click to expand...
Click to collapse
you need to install and use mFastboot for things like that and edit the flash all to mFastboot
bkjolly said:
you need to install and use mFastboot for things like that and edit the flash all to mFastboot
Click to expand...
Click to collapse
Interesting, I grabbed this from the mfastboot site; "Unfortunately, that standard fastboot is limited on how big of files it can properly flash. In recent android devices, Motorola has surpassed the limits of fastboot, as such they have an "upgraded" or "tweaked" fastboot" certainly sounds like my issue. Thanks all.
bkjolly said:
you need to install and use mFastboot for things like that and edit the flash all to mFastboot
Click to expand...
Click to collapse
I use the sdk on my MacAir all the time and never have issues, just keep it updated, works for me.
I'm getting the same error on my mac when trying to fastboot system.img
any thoughts? or guidance on how to update the fastbook or sdk?
AceKingNYC said:
I'm getting the same error on my mac when trying to fastboot system.img
any thoughts? or guidance on how to update the fastbook or sdk?
Click to expand...
Click to collapse
The only thing that worked for me was to use a PC. I hate to say that, but nothing I did on my Mac worked. I have both a Win7 and Win8 setup, I used the Win8 for the N6. It seems that for some reason the fastboot on the PC will parse out the system.mg and flash it. I tried the mfastboot from Motorola, but it was not for the Mac.
I did make sure I had the new sdks and all the new tools on my Mac, all other .img's flashed just fine.
Anyway, my only suggestion is to use a PC, sorry.
jackpollard said:
The only thing that worked for me was to use a PC. I hate to say that, but nothing I did on my Mac worked. I have both a Win7 and Win8 setup, I used the Win8 for the N6. It seems that for some reason the fastboot on the PC will parse out the system.mg and flash it. I tried the mfastboot from Motorola, but it was not for the Mac.
I did make sure I had the new sdks and all the new tools on my Mac, all other .img's flashed just fine.
Anyway, my only suggestion is to use a PC, sorry.
Click to expand...
Click to collapse
Thanks for the info! I think I updated my SDK stuff yesterday - was my first time doing so but I saw there were updates and installed them. Going to give it a go later today and see if it made a difference. if not, going to have to find a Win8 computer to try this on
Update: I updated my fastboot file, and was able to install 5.0.1 and flash CF Auto Root without losing any data whatsoever. When i updated the SDK files, I took the updated fastboot file and dropped it into the folder where all the 5.0.1 files were, and obviously, removed the outdated fastboot one so that there were no mixups.
Hope this helps anyone running into this error!
Thanks for that follow-up, I'm going to go thru the sdk update again, I was rushing and maybe I messed something up. If it worked for you, I'm going to hope it works for me.
Hi all, hope you're doing fine.
I came here looking for help since I seem to have bricked my One Plus 7 Pro.
I was root user with unlocked bootloader and installed OOS 11 OTA through OonePlus' updater app, then tried to flash magisk using it's same app but since I'm a little bit un-updated about how it works and couldn't get it to flash I went into recovery just to find out the stock recovery.
Confused I wipped out ADB and tried flashing TWRP. I now know that my problem was not using the correct version of TWRP for A11 but during the attept at flashing TWRP something went wrong (I remeber doing something with the partition where I flashed the recovery.img but cant precise what, was late in the night) and the phone doesn't boot up to OS or recovery, I can just get into fastboot mode.
I can access fastboot and the bootloader is still marked as unlocked. I started reading how to install a clean image of OOS11 form this state and found this guide: LINK
I went all the way up to having the filles from the .bin unpacked and when I try to flash one by one the archives I get the error:
Sending 'aop_a' (200 KB) OKAY [ 0.012s]
Writing 'aop_a' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
Click to expand...
Click to collapse
But when trying "Fastboot flashing unlock" or "fastboot flashing unlock_critical" I get the message saying that it failed since the device is alredy unlocked
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Click to expand...
Click to collapse
I've also tried to use one of those "flash all .bat" roms I saw here on the forums but that didn't work, I'm also trying to use the MSNtool but to be quite frank the tutorials I've found so far are not noob friendly, since I can't seem to get the correct drivers isntalled and the phone properly recognized ( as it is now it shows as "QUSB_BULK_CID:0404_SN:36EDE735" ).
So that's my current state:
I can enter fastboot with suppousedly unlocked bootloader but cant seem to flash things
Can't seem to get the support files/drivers for the MSN method
I would greatly apprciate help getting back into ANY version of OOS working since as it is now the phone's paperweight. If directed to comprehensible guides I beieve I can keep going, I don't mind with wich method.
Thanks in advance and please excuse the inconveniences,
LUCAS
PS: Mod please feel free to move this thread to a more appropiate board if you think I didn't choose the right one
I feel you, i hate the MSMTool. I won't use it unless i absolutely HAVE TO.
Download Mauronofrios All in one tool. You can find that here on xda.
As long as you are able to get into fastboot, that tool will help you.
Good luck