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!
Related
Hi all,
So coming from a Samsung craptivate, Im having a little bit of trouble flashing CM 6.1.1 on my new N1
so far starting from stock I have
- Unlocked the bootloader
- used fastboot to flash the latest clockworkmod
now I am trying to boot into recovery to flash the CM zip on my SD and I keep getting to a screen with the android guy and an exclamation point, and have to do a battery pull to reboot, I have tried using adb and 3 button combo to get into clockwork,
so, what idiotic thing am I doing wrong?
You're booting in between installing the recovery and booting into recovery.
There are two files that restore the stock recovery upon a system boot (which is what you are seeing). If you go straight to recovery after flashing, the stock recovery won't be restored, then you can install a custom ROM.
The two files are missing from custom ROMs, so you won't have this problem again.
Typically, people remove these files once they have root access, but since you don't have root yet, that isn't an option...
Sent from my Nexus One using XDA App
thanks very much for your help, got it working
Reading the Wiki guides for installing recovery should have solved your question before you wrote it.
So, I just flashed the latest CyanogenMod nightly. All went according to plan until the phone rebooted. Now I can't boot into anything. Neither the mod nor recovery. When I press "X" and Power to boot into recovery I just get stuck on the triangle screen and when I power up normally I get suck on the "M" logo.
I have no idea how to flash the SBF from here. Thoughts?
Same Problem!
I flashed the latest CM7 from the website. I can get to the standard recovery and to the bootloader, but have no idea how to get my phone back to a working condition. I already flashed the Droid bootstrap recovery, but can't seem to boot to it to install another ROM. Anyone help?
did you try wiping cache and data in android recovery?
edit: if that doesn't work, try
http://www.droidforums.net/forum/droid-2-global-hacks/184272-bootloop-help-tutorial.html
or the ABD boot to revovery in the FAQs
I did format the Data and Cache with the recovery tool. I ended up following the instructions at the CM7 Wiki to reinstall the factory image, now it's working OK.
I think the reason you were having trouble with the recovery was because its a different method on gingerbread. On froyo you just press the search key and it boots you into recovery, on gingerbread you have to hit both volume keys at the same time. I know this is a mute point to you know but maybe someone else has a similar issue.
no he said
I can get to the standard recovery... I did format the Data and Cache with the recovery too
Click to expand...
Click to collapse
and that didn't fix it, so he got into recovery ok
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Beast84 said:
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Click to expand...
Click to collapse
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
PrizmaticSmoke said:
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
Click to expand...
Click to collapse
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Bumping to see if anyone else can help...
Beast84 said:
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Click to expand...
Click to collapse
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Paramesh96 said:
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Click to expand...
Click to collapse
Ok so that worked to flash cm but will this continue to happen if I try flashing the official lollipop update? I'm trying to return to stock so I can give the tablet to my nephew. I don't want him jumping into recovery or bootloader & wrecking it for good
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
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje