Database Info

No OS, TWRP fails to flash .ZIPs

Hey guys,
I'm having some trouble with flashing a new ROM and now I've soft-bricked my device.
I was trying to flash from CROMi to CM11 so I wiped data, cache, dalvik using TWRP. But when i tried to flash CM11 M9, i would get the "failed" error. I tried flashing other ROMs but same result - "FAILED".
So I thought maybe it was the recovery. I downloaded a CWM recovery (in .zip) and tried to flash it. FAILED!
I tried to restore my device using the "Recover /Downgrade from Jelly Bean to ICS/Clean Factory Restore with custom recovery" method from this post. Since it is basically flashing the stock ROM, naturally it fails.
Now I'm out of ideas. How can I save my tablet?
Thanks for your help guys!
PS: I'm trying to install CMW via fastboot. When I press power + vol down, I get to the screen with "RCK, Android, Data Wipe"; I dont see the USB icon. How do i boot into fastboot?

You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....

berndblb said:
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
Click to expand...
Click to collapse
Hey bern,
Thanks for the reply.
My tablet got really slow so I decided to flash CM 11 M9, which is what I use on my Note 3.
I'm running TWRP 2.6.1.0. Not sure which CROMi I was running because I can't boot into Android. I did a data wipe prior to (attempting to) flashing CM11 and now it boots straight to recovery.
I read that TWRP is not compatible with CM11 and that I should flash CWM. But TWRP fails when I try to flash anything so I'm thinking I should attempt ADB sodeload or terminal command and load that way?
Thanks again
Edit: I downloaded CM11 M9 for tf700. I also tried various nightlies in case my original download was corrupt. It ends in failure

berndblb said:
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
Click to expand...
Click to collapse
Hi berndblb!
I'm also having this problem and I see that you're quite active in the TF700 forum that you could help me out. I wouldnt say I'm an expert but I have tinkered with phones (mostly Samsung and Nexus devices) in the past so I am familiar with ADB, terminal commands, flashing ROMs, etc.
I'm running TWRP 2.6.1. I was running CROMi-X (not sure which version) and wanted to flash OmniROM. However, TWRP would show "error flashing zip" and "failed" in red. I tried flashing a few other zips including TWRP 2.7.1.1 and CWM (I readTWRP is not compatible with some ROMs) and I would still get the error and "failed".
So now, I can't boot into the OS to flash a recovery via fastboot or via CWM Rom Manager, nor can I flash anything in TWRP. I also attempted to flash TWRP 2.7.1.1 via terminal command
HTML:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4[HTML]. I loads but it doesnt install when i restart my device.
What do you think I should try next? I'm getting pretty desperate at this point. Is my device bricked-bricked or can i salvage it?
Thanks!

oh.herro said:
Hi berndblb!
I'm also having this problem and I see that you're quite active in the TF700 forum that you could help me out. I wouldnt say I'm an expert but I have tinkered with phones (mostly Samsung and Nexus devices) in the past so I am familiar with ADB, terminal commands, flashing ROMs, etc.
I'm running TWRP 2.6.1. I was running CROMi-X (not sure which version) and wanted to flash OmniROM. However, TWRP would show "error flashing zip" and "failed" in red. I tried flashing a few other zips including TWRP 2.7.1.1 and CWM (I readTWRP is not compatible with some ROMs) and I would still get the error and "failed".
So now, I can't boot into the OS to flash a recovery via fastboot or via CWM Rom Manager, nor can I flash anything in TWRP. I also attempted to flash TWRP 2.7.1.1 via terminal command
HTML:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4[HTML]. I loads but it doesnt install when i restart my device.
What do you think I should try next? I'm getting pretty desperate at this point. Is my device bricked-bricked or can i salvage it?
Thanks![/QUOTE]
Can you enter fastboot at all ?
Thx Josh
Click to expand...
Click to collapse

r3dal3rt said:
Hey bern,
Thanks for the reply.
My tablet got really slow so I decided to flash CM 11 M9, which is what I use on my Note 3.
I'm running TWRP 2.6.1.0. Not sure which CROMi I was running because I can't boot into Android. I did a data wipe prior to (attempting to) flashing CM11 and now it boots straight to recovery.
I read that TWRP is not compatible with CM11 and that I should flash CWM. But TWRP fails when I try to flash anything so I'm thinking I should attempt ADB sodeload or terminal command and load that way?
Thanks again
Edit: I downloaded CM11 M9 for tf700. I also tried various nightlies in case my original download was corrupt. It ends in failure
Click to expand...
Click to collapse
Right now the most important thing is the bootloader version ....
On the bootloader screen upper left there is a bootloader version in really small print ...
This is what we need to know ...
Thx Josh

lj50036 said:
Right now the most important thing is the bootloader version ....
On the bootloader screen upper left there is a bootloader version in really small print ...
This is what we need to know ...
Thx Josh
Click to expand...
Click to collapse
Exactly.
I also would like to know how you performed the wipe you mentioned. The tablet booting only and straight to recovery would indicate that you used 'Wipe Data' from the bootloader???
Also, do not use ROM Manager. It does not work well with the Transformers and can cause a lot of problems.
I have a feeling another user is going to benefit from your excellent unbrick guide, Josh...
Aren't you glad you wrote it?? [emoji12]

lj50036 said:
Can you enter fastboot at all ?
Thx Josh
Click to expand...
Click to collapse
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.

oh.herro said:
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
Click to expand...
Click to collapse
No boot to recovery ?
No bootloader ?
No nvflash blob backups ?
If that is the case then you are not looking good ...
There is no way out of this one ...
We need fastboot or recovery one or the other ..
Sorry for the bad news ....
Thx Josh

oh.herro said:
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
Click to expand...
Click to collapse
I agree with lj - not looking good. [emoji17]
Do you have adb access when it boots to the Asus splash screen?

[Q] Bricked My Moto G, Please Help!

Hey everyone,
Yesterday i tried flashing the latest CM12 nightly straight onto my Moto G over stock KitKat. After i flashed the ROM, i tried booting and noticed it was taking a lot longer than normal to boot. Ten minutes had gone past so i tried rebooting it again and the same thing happened, just got stuck booting for ages.
So i decided to boot into recovery and do a factory reset to see if this would make any difference. But even after doing this the phone still wouldn't boot, so i decided to just flash the stock KitKat ROM back onto the phone and forget about all the Lollipop stuff.
The KitKat ROM wasn't on my phones storage so i downloaded it from the internet and flashed it via fastboot using and included Windows batch file. I've used this method numerous times to get me out of situations like this and it's always worked, but this time no!
Tried booting after flashing the new stock ROM and now it just keeps going to the 'Warning, bootloader unlocked' screen and then booting back in a loop.
When i boot into ClockworkMod recovery it gives me these errors:
Can't mount /cache/recovery/log
Can't open /cache/recovery/log
Can't mount /cache/recovery/last_log
Can't open /cache/recovery/last_log
Can't mount /cache/recovery/last_install
Can't open /cache/recovery/last_install
And if i attempt to format /data, it says this:
Error mounting /data
Error formatting /data
I hate asking for help like this but unfortunately i don't have much option this time, no idea what to do despite searching forums for many hours.
Please help, any advice would be greatly appreciated!

Bump

You can try getting into fastboot and run commands fastboot erase userdata and fastboot erase cache from your computer to pretty much factory reset the phone.
Sent from my Moto X 2014 Pure Edition

Pursain said:
You can try getting into fastboot and run commands fastboot erase userdata and fastboot erase cache from your computer to pretty much factory reset the phone.
Sent from my Moto X 2014 Pure Edition
Click to expand...
Click to collapse
Thanks for the response. I tried entering the commands you suggested but the problem is still the same, phone stuck in the 'Warning, bootloader unlocked' loop. Does anyone have any other ideas? Really need some help with this, my little Moto has been dead for days!
And just an update on the situation, i noticed that if i go into CWM and select 'Wipe and Format Options' then 'Custom Format Options', choosing to format the cache and /data/media (/sdcard) options will stop the errors stated in the original post, but when i try flashing the ROM again the errors come straight back!

V3-571G said:
Thanks for the response. I tried entering the commands you suggested but the problem is still the same, phone stuck in the 'Warning, bootloader unlocked' loop. Does anyone have any other ideas? Really need some help with this, my little Moto has been dead for days!
And just an update on the situation, i noticed that if i go into CWM and select 'Wipe and Format Options' then 'Custom Format Options', choosing to format the cache and /data/media (/sdcard) options will stop the errors stated in the original post, but when i try flashing the ROM again the errors come straight back!
Click to expand...
Click to collapse
So sad to hear your Moto dead for the last days. Could you tell me more about your Moto? Can it turn off? Get into fastboot? Do you have recovery (stock or custom? Etc.
Sent from my Moto X 2014 Pure Edition

Pursain said:
So sad to hear your Moto dead for the last days. Could you tell me more about your Moto? Can it turn off? Get into fastboot? Do you have recovery (stock or custom? Etc.
Sent from my Moto X 2014 Pure Edition
Click to expand...
Click to collapse
Yeah it sucks having a pretty much lifeless Moto, kinda scary as well not knowing if i'll be able to get it working again! But in response to your questions, i can turn it off and get into fastboot, i'm also able to boot into my recovery which is Philz Touch (ClockworkMod). If you take a quick look at the original post, i updated it a short while ago to show more details about the errors which are displayed.

Bump, still dead!

V3-571G said:
Bump, still dead!
Click to expand...
Click to collapse
If you can get into fastboot you can flash the stock firmware (not backup) back onto your phone that way. I have used fastboot many times to restore my xt1028 Moto G many times after seemingly bricking it. You will need the stock firmware for your phone to do this.
Here is a tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
and here is a link to moto firmwares:
http://motofirmware.com/
Hope this helps.

classic757 said:
If you can get into fastboot you can flash the stock firmware (not backup) back onto your phone that way. I have used fastboot many times to restore my xt1028 Moto G many times after seemingly bricking it. You will need the stock firmware for your phone to do this.
Here is a tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
and here is a link to moto firmwares:
http://motofirmware.com/
Hope this helps.
Click to expand...
Click to collapse
Thanks for taking the time to respond to my request for help. I have already tried flashing the stock ROM via fastboot mode but it makes no difference to the situation, even though the new ROM flashes perfectly without error, when i try to boot it just gets stuck in the reboot loop on the 'Warning, bootloader unlocked' screen. I have no idea what to do now!

V3-571G said:
Thanks for taking the time to respond to my request for help. I have already tried flashing the stock ROM via fastboot mode but it makes no difference to the situation, even though the new ROM flashes perfectly without error, when i try to boot it just gets stuck in the reboot loop on the 'Warning, bootloader unlocked' screen. I have no idea what to do now!
Click to expand...
Click to collapse
I would suggest you try to install a custom recovery through fastboot (I use TWRP 2.7.1.0)
Just replace the stock recovery with TWRP in the fastboot file and use the command "flash recovery recovery.img" then reboot into recovery(hold power and volume down button down together for about ten seconds, release and you should see the fastboot screen. Then press recovery and then wipe>advanced>wipe ONLY cache and dalvik and then reboot)
See if that does the trick.

Try this: http://forum.xda-developers.com/showpost.php?p=58116154&postcount=14
You have not stated your model. Don't use batch files to fastboot flash the firmware. Make sure the image is 4.4.4.

classic757 said:
I would suggest you try to install a custom recovery through fastboot (I use TWRP 2.7.1.0)
Just replace the stock recovery with TWRP in the fastboot file and use the command "flash recovery recovery.img" then reboot into recovery(hold power and volume down button down together for about ten seconds, release and you should see the fastboot screen. Then press recovery and then wipe>advanced>wipe ONLY cache and dalvik and then reboot)
See if that does the trick.
Click to expand...
Click to collapse
lost101 said:
Try this: http://forum.xda-developers.com/showpost.php?p=58116154&postcount=14
You have not stated your model. Don't use batch files to fastboot flash the firmware. Make sure the image is 4.4.4.
Click to expand...
Click to collapse
Thanks very much for the responses. Unfortunately i already had Philz ClockwordMod recovery installed on the phone and had attempted the various wipe options a number of times without any success. However, i thought that as i'd only tried flashing the UK ROM to the device, i would attempt flashing a different ROM just to ensure there wasn't an issue here somewhere. I downloaded the stock US ROM and after extracting the archive i ran the Windows batch file to flash the files onto the phone. After the process had completed i rebooted the phone (Didn't bother going into recovery and wiping/formatting cache) and to my surprise the phone booted up completely fine! So weirdly it seems that just flashing a different ROM did the trick. But anyway, my Moto is alive again now, i'm very pleased to say the least!

[Q] I just can't make my phone work!!PLEASE HELP!!

Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english

pedrocarboni said:
Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english
Click to expand...
Click to collapse
Bad idea, never try to downgrade... If you can still access fastboot you are VERY luck that your phone did not end up in a hard brick. :fingers-crossed:
Try and flash stock 5.0 from fastboot mode. And wipe everything including userdata.
Goodluck!

skyguy126 said:
Bad idea, never try to downgrade... If you can still access fastboot you are VERY luck that your phone did not end up in a hard brick. :fingers-crossed:
Try and flash stock 5.0 from fastboot mode. And wipe everything including userdata.
Goodluck!
Click to expand...
Click to collapse
Thanks for Helping!!! Just one question: How can i pass the stock zip to the phone to flash it if mtp is not working?Any suggestions? Because i think its not possible to flash 5.0 using fastboot, just on the stock recovery
update: I have just figured out that adb is working with CWM, which i have installed right now Yay!now I can push files from my computer!!
https://androidxda.net/how-to-unbrick-moto-g-1st-gen-2013-after-lollipop-5-0-android-update/ :laugh::laugh:

pedrocarboni said:
Thanks for Helping!!! Just one question: How can i pass the stock zip to the phone to flash it using if mtp is not working?Any suggestions? Because i think its not possible to flash 5.0 using fastboot, just on the stock recovery
Click to expand...
Click to collapse
If you have unlocked boot loader then go into fastboot mode and run "fastboot boot customrecovery.img" where customrecovery.img is CWM or TWRP. I recomment TWRP. From there you can adb sideload the zip. Only flash it if you know exactly what you are doing or you may end up in a hard brick.

skyguy126 said:
If you have unlocked boot loader then go into fastboot mode and run "fastboot boot customrecovery.img" where customrecovery.img is CWM or TWRP. I recomment TWRP. From there you can adb sideload the zip. Only flash it if you know exactly what you are doing or you may end up in a hard brick.
Click to expand...
Click to collapse
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!

pedrocarboni said:
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!
Click to expand...
Click to collapse
Do this at your own risk:
Your system partition is corrupt, you need to enter adb shell and format /system into ext4s. Search on google for the command as I do not have it on the top of my head. I believe it has something to do with make_ext4s function.

pedrocarboni said:
Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english
Click to expand...
Click to collapse
Pedro, I have the same problem.
I can only access bootloader and recovery, but using adb sideload I can't flash any image (and version) that works.
I just get boot looping as you, and gpt.bin and motoboot.img files can't be flashed.
I've found that with Lollipop bootloader we can't install an older Android version.
My Moto G is now a paperweight, until the final stock Lollipop comes.

pedrocarboni said:
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!
Click to expand...
Click to collapse
Hi, I experienced the same problem. Have you fixed your phone? Please give me some suggestion. Thank you.

Same problem with my Moto G 2013.
I've tried to downgrade and got problem. Now I can't flash an older motoboot.img and gpt.bin.
I'm using CyanogenMod 12, but every time when I boot, there is a line going down over the screen.
This line only disappear when I turn off and on the screen. Then everything backs to normal.
Is there a way to solve this?

This happened to me yesterday, i wento from my US Retail 4.4.4 to BR Retail 4.4.4 then via stock recovery flashing the OTA of 5.0, installed Xposed but gave me slow boots, like 5 min per boot, so i decided to downgrade, flashed 4.4.4 BR but after boot a black screen comes and doesn't go, think of flashing 4.4.2 US but the same isue, then decided to update again to 5.0 BR but stock recovery don't let me flash because an error, i flashed philz touch and do a factory reset, wipe data, cache, and everything, then flashed flashing 4.4.4 BR and then 4.4.2 US, the line down problem is nothing, only appears when you boot and, if you lock your phone for about 2-3 seconds, it dissappear (until you boot again), hope it helps, sorry for bad english

For all with bootloops, there is a major issue caused with a boot animation memory leak. Search on the forum to find the fix. You may need to delete the bootanimation binary.

skyguy126 said:
For all with bootloops, there is a major issue caused with a boot animation memory leak. Search on the forum to find the fix. You may need to delete the bootanimation binary.
Click to expand...
Click to collapse
skyguy126, I've not found any solution for this on forum.
Could you please show me a way?

For those that have problems downgrading, download this and follow this steps.
Once finished flash TWRP recovery and restore your nandroid.

Moto G not Booting, HELP
Hi everyone, I really need help with my moto G, it´s not booting into android after pressing the power button the moto logo comes up and the phone goes directly into fastboot displaying a message in pink color: version downgrade for boot
Failed to validate boot image.
I have been hours checking around for a solution and working now for the third day trying to solve the problem with no luck.
I have downloaded the original firmware for the device, tried to flash it and it doesn´t work, tried other countries firmware and they doesn´t work either.
The process will be partially ok but as it goes to flash the boot.img, recovery and system files it will give an error.
I also tried bootloader refresh, bootloader bricker and blankflash to try fix any possible bootloader issues.
The device has a locked bootloader since it is a moto g from AIO.
Please Help, It´s my only device and I cannot afford another one at this time.
There´s a few images from the flash process and device info
:crying:

You need to unlock your bootloader in order to flash various ROMs.

but in this model the bootloader cannot be unlocked it is CID 0X0010

How did this happen to your phone? What model phone do you have?

It´s a Moto G 2013, xt1032
It all begin trying to install a signed stock firmware that was supposed to be for that specific model: AIO_XT1032_4.4.2-KXB20.9-1.10-1.9_CFC_1FF.xml
During the flash process it send some error messages but the process keep running until it finishes, once the device reboot it went straight to fastboot and since then I haven´t been able to get it back working.

Are you manually flashing each partition?
Maybe try a 4.4.4 ROM.

Yes, I have. I´ve also tried other signed firmware that have a .bat file that run all by itself but neither way it worked. It comes up with the error message: Invalid signed Image and below Preflash Validation Fail

Stock recovery corrupted. Red triangle. Android broken

Hello guys. I think I have a very particular problem since Noone on the forum has mentioned/solved this problem before. Basically I have my old tablet replaced with b01 battery. It came with lollipop os 2.2.2 (I think) I rooted it like I did before with flammable y01 with twrp so no problem on that hand.
Now I'm selling it and I need to get it back to the stock os with stock recovery. But as is seems this turns into something impossible :
Every time I try to flash stock image the red triangle appears when I try to boot into recovery no matter what I do :tried to flash Via fastboot many times, tried different fastboot drivers (one from Nvidia, another one from Google) tried to mess with flashing sequence - staging - reboot - boot.img - recovery.img - reboot - system. Img, userdata.img - dtb - oem lock - reboot and still the red triangle with broken Android. Tried flashing it from 2 different notebooks, with clean win 7 and clean installation of Nvidia drivers. Still no luck, as soon as I finish flashing staging and booting into recovery with volume keys I always get the red triangle. However when I try to install a twrp it boots into recovery instantly. I even tried erasing all partitions before flashing :fastboot erase recovery, erase boot system ecc without result, tried even to flash staging, boot and recovery partitions from older os versions keeping the system and userdata from 2.2.2 and no luck.. Can please some one explain why the original recovery doesn't want to stick?? The cwm recovery like twrp work like charm whenever I try to flash them... So it's not up to hardware.. Please help me guys

Maybe have to relock the bootloader. Why can't you sell it with a custom recovery and rom?

gqukyo said:
Maybe have to relock the bootloader.
Click to expand...
Click to collapse
Why would you ever suggest that?
sighline said:
Can please some one explain why the original recovery doesn't want to stick?? The cwm recovery like twrp work like charm whenever I try to flash them... So it's not up to hardware.. Please help me guys
Click to expand...
Click to collapse
Stock recovery doesn't really have a user interface like TWRP or CWM so I wouldn't worry about the red triangle. Is there any reason you can't sell it with the custom recovery?

You can easily lock and unlock the bootloader so what's the issue with trying that? And if you want it to be 100% retail stock, the bootloader would be locked.
You can also try to re download the stock restore files again and try again. I don't recall the stock recovery giving you any options anyways so that screen you're getting should be fine.

XZP Wont Boot after Flashing Standard Rom

Hi All,
I've been trying to install TWRP, Root etc on my XZP since yesterday. I've done something wrong at some point, and now my phone will not boot at all.
I had no troubles unlocking bootloader, installing TWRP etc initially. I then tried to install a custom rom from these forums and that's where things spiraled downwards for me.
As part of that procedure, I needed to flash the latest sony firmware first. That went fine.
However, now TWRP is not able to decrypt storage, so I'm not able to flash anything else. Perhaps this is because I booted into the new sony firmware and forgot change the pattern/fingerprint to pin/fingerprint.
So I'm not able to unlock the storage via TWRP by entering a password.
I tried to reflash the same firmware again using newflasher. But the phone won't boot at all. It turns off immediately after the Unlocked bootloader warning. It's not going into a boot loop. Just turns off.
I then tried to flash the TWRP recovery image using adb fastboot command, and the flash seemed to execute properly, but I still can not boot into recovery.
Is it possible the main storage is still encrypted, so nothing can flash to it? Bricked? If so, how do I proceed?
I read something about reformatting partitions? But I'm not able to get into TWRP recovery menu to do this.
*EDIT: I reflashed trwp recovery image, and am not able to boot into recovery. I still can not unlock (unencrypt) the main storage though.
*2nd EDIT: I followed the instructions here:https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
I was then able to flash the stock ROM back onto my device, and I'm able to boot my phone up. I'll look at installing a custom ROM at a later date.

Thread closed at OP request