[Q] soft bricked verizon non-dev moto x - Moto X Q&A

I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.

slappydj1 said:
I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2635366

slappydj1 said:
I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
Click to expand...
Click to collapse
Are you still able to enter the Bootloader menu?

jpd_ said:
Are you still able to enter the Bootloader menu?
Click to expand...
Click to collapse
yes, I just cant boot into recovery or android.

slappydj1 said:
yes, I just cant boot into recovery or android.
Click to expand...
Click to collapse
Go ahead and flash the stock recovery img then follow the instructions from here:
http://forum.xda-developers.com/showthread.php?t=2639102
Also, they may be posting the OTA specifically made for verizon soon:
http://support.verizonwireless.com/dam/support/pdf/system_update/moto-x.pdf
Very helpful link here as well on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=2603358
If you made a back up through TWRP, you can try restoring your phone from there too.

jpd_ said:
Also, they may be posting the OTA specifically made for verizon soon:
http://support.verizonwireless.com/dam/support/pdf/system_update/moto-x.pdf
Click to expand...
Click to collapse
The Verizon OTA is out. That is what got him in the situation he is in.

I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?

slappydj1 said:
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
Click to expand...
Click to collapse
They generally seem to show up 1 week to 1 month from when the OTA is released.

slappydj1 said:
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
Click to expand...
Click to collapse
That is because you need to use mfastboot, not fastboot.
mfastboot.exe
fastboot can't handle file sizes that large; mfastboot can.

Cozume said:
That is because you need to use mfastboot, not fastboot.
mfastboot.exe
fastboot can't handle file sizes that large; mfastboot can.
Click to expand...
Click to collapse
Just tried it, got this message:
sending 'recovery' (10240 KB)... OKAY [ 0.876s]
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure)

slappydj1 said:
Just tried it, got this message:
sending 'recovery' (10240 KB)... OKAY [ 0.876s]
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
If you are on the 4.4.2 bootloader, I don't think you can use the 4.4 recovery.
http://forum.xda-developers.com/showthread.php?t=2635366
Also what are you doing to try to boot into recovery?

Cozume said:
If you are on the 4.4.2 bootloader, I don't think you can use the 4.4 recovery.
http://forum.xda-developers.com/showthread.php?t=2635366
Also what are you doing to try to boot into recovery?
Click to expand...
Click to collapse
I tried to boot into recovery using the fastboot menu on the phone.

slappydj1 said:
I tried to boot into recovery using the fastboot menu on the phone.
Click to expand...
Click to collapse
So you hold the Volume Down + Power to get into fastboot menu and then you hit Volume Down to highlight Recovery and then you hit Volume Up to select Recovery. Then you get the Android on its back with the red triangle. Then you Hold the Volume Up + Volume Down for about 5 seconds and press the Power button once. This is what you did? What does it do?

Cozume said:
So you hold the Volume Down + Power to get into fastboot menu and then you hit Volume Down to highlight Recovery and then you hit Volume Up to select Recovery. Then you get the Android on its back with the red triangle. Then you Hold the Volume Up + Volume Down for about 5 seconds and press the Power button once. This is what you did? What does it do?
Click to expand...
Click to collapse
I can get to the fastboot menu fine, it just doesnt enter recovery. I dont get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed

slappydj1 said:
I can get to the fastboot menu fine, it just doesnt enter recovery. I dont get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed
Click to expand...
Click to collapse
Ok, got it. I think the problem is that you can't have a 4.4.2 bootloader with a 4.4 recovery. So what it is telling you is that your recovery is downgraded because it is the version below your bootloader. I think you need the 4.4.2 recovery with the 4.4.2 bootloader. And there is no way to downgrade the 4.4.2 bootloader.
I read through the threads and I don't see where you can have the newer bootloader with the older recovery. You can have the older system with the newer bootloader.
I will post that question by itself and see if anyone can tell me if I am right or wrong on that.

Cozume said:
Ok, got it. I think the problem is that you can't have a 4.4.2 bootloader with a 4.4 recovery. So what it is telling you is that your recovery is downgraded because it is the version below your bootloader. I think you need the 4.4.2 recovery with the 4.4.2 bootloader. And there is no way to downgrade the 4.4.2 bootloader.
I read through the threads and I don't see where you can have the newer bootloader with the older recovery. You can have the older system with the newer bootloader.
I will post that question by itself and see if anyone can tell me if I am right or wrong on that.
Click to expand...
Click to collapse
I just tried flashing the system with mfastboot and got this message:
sending 'system' (262144 KB)... OKAY [ 17.113s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)

slappydj1 said:
I just tried flashing the system with mfastboot and got this message:
sending 'system' (262144 KB)... OKAY [ 17.113s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Ok, sorry I am getting confused. It is the 4.4.2 system that will work with the 4.4 bootloader.
So I think the bottom line from all I have read is that you need the 4.4.2 stock recovery.img file.
How did you get to this point again? You took the OTA but for some reason it only upgraded the bootloader?

Cozume said:
Ok, sorry I am getting confused. It is the 4.4.2 system that will work with the 4.4 bootloader.
So I think the bottom line from all I have read is that you need the 4.4.2 stock recovery.img file.
How did you get to this point again? You took the OTA but for some reason it only upgraded the bootloader?
Click to expand...
Click to collapse
So Ill have to wait until the factory image is released?

slappydj1 said:
So Ill have to wait until the factory image is released?
Click to expand...
Click to collapse
I don't see any other option if the 4.4.2 bootloader won't work with the 4.4 recovery. I believe that is what those error messages are saying.
So what exactly did you do that resulted in this situation? Explaining that might be helpful to others who may be able to help you.

Cozume said:
I don't see any other option if the 4.4.2 bootloader won't work with the 4.4 recovery. I believe that is what those error messages are saying.
So what exactly did you do that resulted in this situation? Explaining that might be helpful to others who may be able to help you.
Click to expand...
Click to collapse
I was going to do a factory reset using fastboot, and I flashed the gpt.bin. after that I could not flash anything. Later I learned that wasnt the factory image but the OTA update, so I realized I messed up then.

Related

Will I be forever stuck at 4.2.2 if I cant flash recovery?

I have tried everything I have read on here and I cant seem to flash recovery. I used pwnmymoto to gain root when I first received my moto x. When the camera update came I thought I unrooted and flashed back to stock becasue I was able to get the OTA. Yesterday I could not install the OTA 4.4 because it gave me a error sign. I tried to flash recovery using fastboot but everytime now matter what I do this shows up:
colins-air:Android Tools colinj22$ ./fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.798s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.848s
colins-air:Android Tools colinj22$
Can someone please help me. I am fairly new to fastboot and I am on a Mac and I have read everything in these threads and nothing seems to help. Can I erase everything and somehow start from scratch?
Thank you all!
colinj22 said:
I have tried everything I have read on here and I cant seem to flash recovery. I used pwnmymoto to gain root when I first received my moto x. When the camera update came I thought I unrooted and flashed back to stock becasue I was able to get the OTA. Yesterday I could not install the OTA 4.4 because it gave me a error sign. I tried to flash recovery using fastboot but everytime now matter what I do this shows up:
colins-air:Android Tools colinj22$ ./fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.798s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.848s
colins-air:Android Tools colinj22$
Can someone please help me. I am fairly new to fastboot and I am on a Mac and I have read everything in these threads and nothing seems to help. Can I erase everything and somehow start from scratch?
Thank you all!
Click to expand...
Click to collapse
try using a different fastboot besides the one you are using. also make sure you are trying to flash the right FW version. you can't downgrade FW so it needs to be the FW version that is currently on the device.
try the second link in the OP of this thread for a different fastboot
http://forum.xda-developers.com/showthread.php?t=2489249
Flashing recovery requires a unlocked boot loader, you're obviously on Verizon and unless you have a DE moto you can't flash recovery due to your boot loader being locked
Sent on my Moto X
Incorrect^
Sent from my XT1060 using Tapatalk

Trouble restoring PE to stock KitKat

Unfortunately I loaded the leaked Lollipop build to my PE and it was working great, but I wanted to get on the soak test build. I downloaded the stock KK 4.4.4 system image from Motorola in order to restore before updated to soak test. All but one of the files flashes fine, the exception being motoboot.img. I get Preflash validation failed error for that file.
The phone boots and runs but the missing file means the update won't install. Does anyone have any thoughts on how to restore this file?
TMO_21.21.42.victara_tmo.tmo.en.US>mfastboot flash boot motoboot.img
target max-sparse-size: 256MB
sending 'boot' (2022 KB)...
OKAY [ 0.089s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.109s​
samabuelsamid said:
Unfortunately I loaded the leaked Lollipop build to my PE and it was working great, but I wanted to get on the soak test build. I downloaded the stock KK 4.4.4 system image from Motorola in order to restore before updated to soak test. All but one of the files flashes fine, the exception being motoboot.img. I get Preflash validation failed error for that file.
The phone boots and runs but the missing file means the update won't install. Does anyone have any thoughts on how to restore this file?
TMO_21.21.42.victara_tmo.tmo.en.US>mfastboot flash boot motoboot.img
target max-sparse-size: 256MB
sending 'boot' (2022 KB)...
OKAY [ 0.089s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.109s​
Click to expand...
Click to collapse
try:
Code:
mfastboot flash motoboot motoboot.img
holtenc said:
try:
Code:
mfastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Sorry, copy/paste error there.
I actually tried the motoboot motoboot.img too and get the same error.
well I'm not sure then man. I guess all I can suggest is follow THESE instructions to a T.
also if you have flashed any of the radios floating around these forums insert "fastboot flash modem radio.img" in there somewhere.
And of course make sure your bootloader is unlocked.
holtenc said:
well I'm not sure then man. I guess all I can suggest is follow THESE instructions to a T.
also if you have flashed any of the radios floating around these forums insert "fastboot flash modem radio.img" in there somewhere.
And of course make sure your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks, those are precisely the instructions I used. I haven't done anything with the radios. I flashed the leaked lollipop rom and then used the official image files to try to go back. The bootloader was initially not unlocked, I unlocked it only in an attempt to get the motoboot file to flash. Now I can't relock it because this part of the image is missing.
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
holtenc said:
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
Click to expand...
Click to collapse
Only thing I did with bootloader locked was the partition. As soon as I got to the motoboot and it failed, I figured I would need to unlock and did that. Since then, I've tried the whole process a couple of times with the same result. I will however, give it another shot.
You don't need motoboot to update. Go use the script and it will do everything for you.
tw1tch175 said:
You don't need motoboot to update. Go use the script and it will do everything for you.
Click to expand...
Click to collapse
Which script is that?
samabuelsamid said:
Which script is that?
Click to expand...
Click to collapse
My multitool in development section has stock restore included
holtenc said:
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
Click to expand...
Click to collapse
bhp090808 said:
My multitool in development section has stock restore included
Click to expand...
Click to collapse
Downloading V4.1 now, thanks
bhp090808 said:
My multitool in development section has stock restore included
Click to expand...
Click to collapse
I flashed with the multitool and was able to get back where I started with the leaked PE lollipop version but something is still missing because I can't relock the bootloader.

[Q] Questions regarding un-rooting.

Verizon Moto X (2013) 4.2.2 Build number: 13.11.1Q2.X-69-3
Hey guys, for the past week I have been trying to un-root my moto x and have been unable to with several different methods.
I first tried RSD Lite, but no matter what I try over and over RSD Lite is not detecting my phone and I havent come across a way to fix that
I then moved on and tried to un-root using Fastboot following this tutorial. For some reason when my when I try, gpt.bin fails.
I then moved on to the Moto X Toolkit. Since this is basically just an automated way of doing fastboot I wasnt to hopeful, and of course it too failed.
Here is what i get when the process fails
Code:
writing 'recovery' ...
Preflash validation failed
FAILED <remote failure>
writing 'system' ...
Preflash validation failed
FAILED <remote failure>
writing 'boot' ...
Preflash validation failed
FAILED <remote failure>
What can I do to fix this? Any help is greatly appreciated!!
paradoxfreq;56816079I then moved on and tried to un-root using Fastboot following [URL="https://www.youtube.com/watch?v=ZtRSrQrzIPI&list=UUVLBNAjddTt6AAPL5141Ybg" said:
this tutorial[/URL]. For some reason when my when I try, gpt.bin fails.
Click to expand...
Click to collapse
Start the phone in FastbootAP/Bootloader mode
Either post a picture of it, or tell me what the number on the second line is.
Also boot normally, Go App Drawer -> Settings -> About... and post the number that SYSTEM VERSION starts with.
KidJoe said:
Either post a picture of it, or tell me what the number on the second line is.
Also boot normally, Go App Drawer -> Settings -> About... and post the number that SYSTEM VERSION starts with.
Click to expand...
Click to collapse
System Version: 140.45.5.
In the command window.
Code:
C:\adb>fastboot devices
T062801FWT fastboot
C:\adb>fstboot flash partition gpt.bin
<bootloader> Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' <32 KB>...
OKAY [ 0.247s]
writing 'partition' ...
FAILED <remote failure>
finished. total time: 1.078s
On my phone.
Code:
getvar partition-type: partition
downloading 32768 bytes
done
[COLOR="Red"]downgraded security version
update gpt_main version failed
preflash validatoin failed for GPT[/COLOR]
Thank you for the Reply!
I asked you to boot into FastbootAP/Bootloader and tell me the number on the second line. (its the bootloader version and it IS EXTREMELY important in this case).
You didn't tell me that. Why?
KidJoe said:
I asked you to boot into FastbootAP/Bootloader and tell me the number on the second line. (its the bootloader version and it IS EXTREMELY important in this case).
You didn't tell me that. Why?
Click to expand...
Click to collapse
Oh okay, sorry I didnt realize that was what you meant.
So this is what youre looking for correct?
AP Fastboot Flash Mode (S)
30.B2 (sha-0086aae, 2013-10-17 15:07:32)
paradoxfreq said:
Oh okay, sorry I didnt realize that was what you meant.
So this is what youre looking for correct?
AP Fastboot Flash Mode (S)
30.B2 (sha-0086aae, 2013-10-17 15:07:32)
Click to expand...
Click to collapse
Ok, you have some conflicting info posted.
Post 1 you say you have 4.2.2 Build number: 13.11.1Q2.X-69-3. (I thought 13.11.1Q2.X-69-3 was 4.4)
But in Post 3 you say System Version: 140.45.5. (which is 4.4)
Now, the bootloader version being 30.b2 goes along with 4.4.
the GPT.BIN failing to flash usually indicates that you are trying to DOWNGRADE. There are warnings everywhere saying you shouldn't, The only time its safe to downgrade is if you have 4.4 on your phone and are following the SlapMyMoto process. But since you're trying to un-root, you shouldn't be following SlapMyMoto.
So what are you trying to flash exactly?
At this point, DO NOT ATTEMPT to flash anything but 4.4, 4.4.2 or 4.4.4 on your phone! You need to do a FULL flash, and I would suggest manually using mFastboot, with the extra commands (see option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html ). Because of the GPT.BIN downgrade failures at this point, I would suggest 4.4.2 or 4.4.4 and NEVER try to flash anything older.

I think I soft bricked my phone. flashing "no command"

I've got a moto x '14 verizon XT1096. Tried to use fastboot to load twrp to eventually get to install Cm13. However, it threw this message:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (0 KB)...
OKAY [ 0.006s]
writing 'recovery'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.024s
Dumbass me thought it would be a good idea to unplug the device and simply try again. Well, what a bad decision. The phone now flashes the "no command" robot on it's back. yes, flashes. i can get back to fastboot, but after this i'm not sure what to do.
Thanks in advance. I'm fairly new at this, be easy on me.
Try this. This is my mini guide I wrote in another thread.
Well, at first I tried to flash twrp through fastboot but the original recovery override the twrp recovery.
So, what I did, instead of flashing, I just temporary booted into twrp.
adb reboot bootloader
fastboot boot twrp.img (and not fastboot flash recovery twrp.img)
Then phone booted into twrp, I flash supersu 2.46.
Then I easily downloaded twrp manager from google play and installed twrp recovery to my xt1096.
Have fun
Use this https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse

Restore Stock Recovery - Amazon Fire 7 5th Gen (Ford)

IF YOU PLAN ON INSTALLING ANY CUSTOM ROM CHECK THAT YOUR RECOVERY IS ACCESSABLE!!!
If you have lost access to your stock recovery on your Amazon Fire 7 5th Gen (Ford) for whatever reason I would highly recommend restoring your recovery before doing any further customization to your device. Without recovery you have absolutely nothing to fall back on if your device becomes inoperable. If you have tried flashing any type of custom recovery directly to your device its more then likely you have lost access to your stock recovery. Hopefully youv made it to this thread before it was too late and luckily its a pretty simple process to restore your access.
Before we begin you must have a working OS for this process to work. If your device will not successfully boot then you can not complete the steps necessary to restore access to your recovery.
First lets
• Download Fire 7 Stock Recovery Image https://app.box.com/s/tjju5dptvsmsfjienf37siip8j6ch7wo
• Download and install the Flashfire App http://download.chainfire.eu/950/FlashFire/FlashFire-v0.30-20160331135212.apk
Next we'll
• Open the Flashfire App and allow it root access
• Press the red "+" button and select "Flash Firmware Package"
• Browse to the folder containing the Fire 7 Stock Recovery Image you previously downloaded and select it then press the "√" in the upper right corner
• Change Reboot option from "Normal" to "Recovery"
• Press the "FLASH" then "OK"
• Flashfire will reboot into recovery when its complete (Usually only takes a couple mins but its possible it may run for more)
It is also possible to restore access to recovery using Flashify
• Download and install Flashify
http://www.apkmirror.com/apk/christian-gollner/flashify/
• Press "Select Recovery Image" then choose file
• Browse to the Fire 7 Stock Recovery Image you downloaded earlier, select it and choose "Yup"
• Once complete reboot to recovery to confirm
That's it now you're back in action!!!
Has any one try flashing in fastboot mode?
Sent from my XT1080 using XDA Labs
sd_shadow said:
Has any one try flashing in fastboot mode?
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Thought about that this morning as well. If no one else confirms before I get off work here shortly I will try then. (Especially like to see someone with a hard brick attempt it) In theory it seems it should work since the image seems to carry the signature from Amazon. Well at least that's what I picked up from researching for a fix to restore access to recovery on two of my fires.
Doesn't appear to work. My recovery randomly stopped working while I was trying to get SlimLP to install (unsuccessfully). Details Here
If I try to flash it:
sending 'recovery' (16384 KB)...
OKAY [ 0.474s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.480s
Click to expand...
Click to collapse
If I try to boot to it, same error as if you try to boot to TWRP:
D:\Downloads\android-sdk-windows\platform-tools>fastboot boot fire7-stock-recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.535s
Click to expand...
Click to collapse
knicknut said:
Doesn't appear to work. My recovery randomly stopped working while I was trying to get SlimLP to install (unsuccessfully). Details Here
If I try to flash it:
sending 'recovery' (16384 KB)...
OKAY [ 0.474s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.480s
If I try to boot to it, same error as if you try to boot to TWRP:
D:\Downloads\android-sdk-windows\platform-tools>fastboot boot fire7-stock-recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.535s
Click to expand...
Click to collapse
used ?
Code:
fastboot -i 0x1949 flash fire7-stock-recovery.img
Sent from my XT1080 using XDA Labs
sd_shadow said:
used ?
Code:
fastboot -i 0x1949 flash fire7-stock-recovery.img
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Took me a minute to realize I had to put "recovery" after flash, but even after I did, I sadly got the same result:
sending 'recovery' (16384 KB)...
OKAY [ 0.534s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.541s
Click to expand...
Click to collapse
knicknut said:
used ?
Took me a minute to realize I had to put "recovery" after flash, but even after I did, I sadly got the same result:
sending 'recovery' (16384 KB)...
OKAY [ 0.534s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.541s
Click to expand...
Click to collapse
yes, my bad
Sent from my XT1080 using XDA Labs
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
vuvious said:
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
Click to expand...
Click to collapse
Unfortunately I don't believe so. We need a key to unlock the actual ability to flash via Fastboot. As far as I know at least
vuvious said:
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
Click to expand...
Click to collapse
I suspect that capability is coming (foundation is in v0.32) but probably not for this device due to fastboot restrictions I posed by Amazon.
Sorry cross posted removed
Robin Son said:
stuck with 5.1 will not boot to stock recovery
was going to try using fastboot with 5.3.1 stock img.file but can't find one
TGT123 super tool will reboot my A-fire but will not install stock recovery
O yeah and i lost root and no playstore
Anyone had this problem and fixed???
Click to expand...
Click to collapse
Please don't cross post. Answered here: http://forum.xda-developers.com/ama...stom-rom-fireos-5-3-1-0-t3418541/post70006008

Categories

Resources