Database Users

[Q] TWRP nor CWM will successfully wipe/format data

First, I searched and read all relevant threads concerning this issue. The five threads that showed up in the search did not help me solve my issue.
So on to my problem. I can no longer flash any rom onto my device. I attempted to flash the first official CM10 nightly (which I recently found out was not flashing properly for others) and had no success. I simply got a black screen and nothing more. I eventually got back into TWRP (v2.2.1.4) to try and Nandroid restore, but I noticed that /data was not formatting and the restore failed. Every time I would slide the bar across to confirm the restore TWRP would reboot itself. I then flashed CWM (v6.0.1.0) and the same problems were there. After that I flashed an earlier version of TWRP and successfully restored the backup. I'm not 100% sure how it was successful. So I decided to try flashing another ROM and no go. Same problems. Anyone have any ideas? When I was using CWM I got the error message below.
Code:
E: unable to locate volume information
E: unable to open ums lunfile '/sys/devices/platform/usb_mass_storage/lun0/file'
E: unable to format data
I'm running Bugless Beast with Motley #219

I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app

aznxk3vi17 said:
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What rom did you attempt to flash?

elementur said:
What rom did you attempt to flash?
Click to expand...
Click to collapse
So do I.I attempted to flash the first official CM10 8.18 nightly and had no success. I just got a black screen.Even more I boot into bootloader and choose to boot into recover but just stay at google logo.I try to flash recover once more,but just can't boot into recover!!

I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.

Shano56 said:
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Click to expand...
Click to collapse
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?

phiracle said:
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
Click to expand...
Click to collapse
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).

android1234567 said:
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
Click to expand...
Click to collapse
Thank You Very Much!!!

I am having much the same problem as the OP. I finally rooted my Nexus 7 using WugFresh's Nexus Root Toolkit. It seemed all went well. I chose to use TWRP in a first attempt to install a ROM (I was on rooted stock), and following the instructions for installing my chosen ROM I went into it to wipe cache, Dalvic Cache and data. Both cache and dalvic cache wiped without issue, but when I attempted to wipe /data TWRP simply reported that it failed. With that failing, I did not attempt to install a rom. I was still able to boot out of recovery, but even with repeated attempts wiping data always failed. Is any one aware of any solution or have any suggestions. Thank you!

Can't boot into custom recovery

hi all,
I flashed the 4.3 factory image today and intalled TWRP recovery using Goo Manager and then successfully booted into it and flashed the SuperSU zip...but now i cant boot into it again to flash other things
whatever the method i try, it returns the android lying on with a red exclamation mark
anybody know a solution??

IKnowIRock! said:
hi all,
I flashed the 4.3 factory image today and intalled TWRP recovery using Goo Manager and then successfully booted into it and flashed the SuperSU zip...but now i cant boot into it again to flash other things
whatever the method i try, it returns the android lying on with a red exclamation mark
anybody know a solution??
Click to expand...
Click to collapse
try clearing cache and dalvick cache..
have you taken any nandroid backup??

IKnowIRock! said:
hi all,
I flashed the 4.3 factory image today and intalled TWRP recovery using Goo Manager and then successfully booted into it and flashed the SuperSU zip...but now i cant boot into it again to flash other things
whatever the method i try, it returns the android lying on with a red exclamation mark
anybody know a solution??
Click to expand...
Click to collapse
Rohit02 said:
try clearing cache and dalvick cache..
have you taken any nandroid backup??
Click to expand...
Click to collapse
Lulz. The reason why this is happening is because stock nexus roms will ALWAYS try to flash back a normal recovery.
You need to try and find a way to flash back a custom recovery (ahem, fastboot flash recovery recovery.img)
and there should be a notification when you're about to reboot that says something like disable stock recovery?
Not sure if that was TWRP or CWM.

stock rom will replace your custom recovery with stock recovery.
Use Flashify app to flash img on phone
Sent from my Nexus 4 using Tapatalk 4

Lack of recovery

Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.

Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0

Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?

THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0

That did it. thanks alot ffejy462!

TWRP recover unresponsive after OTA update

I'm running Optimized CyanogenMod 12.1 rom from the Jflte DevConnection Team.
After trying to flash the last OTA update for the rom my TWRP recovery has become unresponsive, stuck on its boot screen (TWRP logo).
What happen was that I downloaded the update via the OTA app and then pressed the Install button to reboot the device and flash the update.
But after the device booted into the recovery TWRP never opened up a process window or its menu but just stayed on the boot screen appearing to do nothing. It did not respond to any commands (buttons or touch). I waited half an hour before forcing a shot down.
But at this point I was in a manual boot loop, the device would boot into recovery instead of the Rom and I was unable to use the phone.
I managed to flash TWRP again using Heimdall which allowed me to boot again into the Rom, but if I tried manually going into recovery it was still unresponsive.
I tried flashing older version of TWRP using Flashy app, I clicked on a option in the app to reboot into recovery. This cost the origin boot loop problem again.
I than flashed CyanogenMod Recovery and was able to boot into that.
Tried once more to flash TWRP but the problem persists.
Anybody that could know what is going on or how to fix this issue. I'm hoping not to have to format the phone to Stock to fix this.

I had same issue with TWRP in the past and never found a solution, to run into the ROM directly and escape the loop thing try
Power Button and volume -
Then continue and it will boot up normally.
I had to change to Clockwork-mod recovery after this.

einsiol said:
I'm running Optimized CyanogenMod 12.1 rom from the Jflte DevConnection Team.
After trying to flash the last OTA update for the rom my TWRP recovery has become unresponsive, stuck on its boot screen (TWRP logo).
What happen was that I downloaded the update via the OTA app and then pressed the Install button to reboot the device and flash the update.
But after the device booted into the recovery TWRP never opened up a process window or its menu but just stayed on the boot screen appearing to do nothing. It did not respond to any commands (buttons or touch). I waited half an hour before forcing a shot down.
But at this point I was in a manual boot loop, the device would boot into recovery instead of the Rom and I was unable to use the phone.
I managed to flash TWRP again using Heimdall which allowed me to boot again into the Rom, but if I tried manually going into recovery it was still unresponsive.
I tried flashing older version of TWRP using Flashy app, I clicked on a option in the app to reboot into recovery. This cost the origin boot loop problem again.
I than flashed CyanogenMod Recovery and was able to boot into that.
Tried once more to flash TWRP but the problem persists.
Anybody that could know what is going on or how to fix this issue. I'm hoping not to have to format the phone to Stock to fix this.
Click to expand...
Click to collapse
look at the twrp thread... i posted a fixed twrp there (look at last 2 pages)
try that one
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
look at the twrp thread... i posted a fixed twrp there (look at last 2 pages)
try that one
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
All I could find was recovery for I9305, is that one you ment? I tried it out but was not able to reboot into that.
But I tried now using the dd to flashed version 2.8.4 and got it to work finally.
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p21
Found this option on the TWRP page for I9505

einsiol said:
All I could find was recovery for I9305, is that one you ment? I tried it out but was not able to reboot into that.
But I tried now using the dd to flashed version 2.8.4 and got it to work finally.
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p21
Found this option on the TWRP page for I9505
Click to expand...
Click to collapse
i meaned the one i posted in s4 twrp page :-O NOT i9305 (wich is s3lte not s4)
Sent from my Xperia T using XDA Free mobile app

A6000 rom and Gapps problems

Hey folks I'm new here and I recently rooted my phone and flashed a z5 rom from the XDA rom thread. Link below
http://forum.xda-developers.com/len.../rom-xperia-z5-rom-lenovo-a6000-plus-t3393251
And flashed this nano pack of this gapps Link below
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
So it all went fine but now I'm incurring some problems.
Firstly I didn't notice that the Gapps is closed for updates I don't know if that affected the issue but the Google play is not working and some other Google stuff as well.
And I thought I'll flash new Gapps which are being kept up to date but my phone won't connect with the PC with the usb now so I don't know how do I flash the Gapps now.
I have re Rooted my phone using the Kingo app but it still won't reconnect.
So any help on these issues would be really helpful!
One last question that if I do find a way to flash the Gapps will I have to reflash the rom again?
Thanks

Parvarsingh said:
Hey folks I'm new here and I recently rooted my phone and flashed a z5 rom from the XDA rom thread. Link below
http://forum.xda-developers.com/len.../rom-xperia-z5-rom-lenovo-a6000-plus-t3393251
And flashed this nano pack of this gapps Link below
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
So it all went fine but now I'm incurring some problems.
Firstly I didn't notice that the Gapps is closed for updates I don't know if that affected the issue but the Google play is not working and some other Google stuff as well.
And I thought I'll flash new Gapps which are being kept up to date but my phone won't connect with the PC with the usb now so I don't know how do I flash the Gapps now.
I have re Rooted my phone using the Kingo app but it still won't reconnect.
So any help on these issues would be really helpful!
One last question that if I do find a way to flash the Gapps will I have to reflash the rom again?
Thanks
Click to expand...
Click to collapse
First dowload the gapps from opengapps.org. Go here choose ARM>>5.1.1>>nano/pico.
Then, boot into recovery, wipe system, data, cache, dalvik and then flash the ROM again and the gapps. All done...!!!

sasukay said:
First dowload the gapps from opengapps.org. Go here choose ARM>>5.1.1>>nano/pico.
Then, boot into recovery, wipe system, data, cache, dalvik and then flash the ROM again and the gapps. All done...!!!
Click to expand...
Click to collapse
That's the prob right. I cant reach the custom bootloader I don't know why. Do you think its because of the new rom ill have to use some different recovery? I am usin twrp right now and even I used it to flash this rom. Please help

Parvarsingh said:
That's the prob right. I cant reach the custom bootloader I don't know why. Do you think its because of the new rom ill have to use some different recovery? I am usin twrp right now and even I used it to flash this rom. Please help
Click to expand...
Click to collapse
""usin twrp right now"" -- can you boot into it..??
You press vol up + vol down along with power key and release the power key once the lenovo logo shows up, to boot into twrp

sasukay said:
""usin twrp right now"" -- can you boot into it..??
You press vol up + vol down along with power key and release the power key once the lenovo logo shows up, to boot into twrp
Click to expand...
Click to collapse
no cant boot into it.
I go into the fast boot mode enter recovery commands in the command window. Then try to boot into recovery but it doesn't go into recovery. The Lenovo screen stays there or it boots straight into the phone
This method worked before like I used this way to flash the rom but now its not working.
Any help?

Parvarsingh said:
no cant boot into it.
I go into the fast boot mode enter recovery commands in the command window. Then try to boot into recovery but it doesn't go into recovery. The Lenovo screen stays there or it boots straight into the phone
Click to expand...
Click to collapse
Brother, you have made it really confusing for me. Earlier you said that you can't boot into bootloader, but now you can boot into fastboot..!!
Also, your phone, instead going to recovery, boots directly to system. That means your phone is in working condition(Is it..?), which you didn't told me earlier.
So, if you can boot into system (normal boot). Download Rashr from play store (or from any other source) and flash this TWRP 3.0.2. (First extract this zip and then choose recovery from storage option in Rashr to flash).