Develop Bugs

CWM recovery and Jelly Bean

I was one of the ones with problems with trying to restore nandroids and wiping data. I got stuck going from vicious JB v1 to V2 then back to v1. Somehow, after attempting to restore numerous nandroids of ICS and my nandroid of V1 I somehow got it to boot.
Now, I've noticed that whenever I boot into recovery if I go to "mounts and storage" I see cache is mounted. I can unmount it and make a nandroid. Then if I go back to "mounts and storage" I see data is mounted and wont unmount so when trying to restore a nandroid it hangs at the data part.
He is what I do that has been working for me.
Once in recovery, I go to mounts and storage and unmount cache. Make a nandroid. Go back to mounts and storage and see data is mounted and won't unmount. I then go to "advanced" and select reboot recovery. Once it reboots into recovery I go back to mounts and storage and see that data is unmounted. I then can restore a nandroid. I've done this successfully going from vicious v3 to BAMF v2 then back to vicous v3.
I just wanted to share this and hope it helps someone.
Thanks

Ddaaaaammmnnnn......I really wish I would have seen this earlier. Blew my phone up just to get it working again. Thanks for the info. I will know what to do next time.
Sent from my Galaxy Nexus using xda app-developers app

Sorry, left out a step. After returning to recovery and finding data unmounted, I can then wipe data, system, and cache. I believe data is again mounted so go to advanced and reboot recovery again, go to mounts and storage and make sure everything is unmounted then restore your nandroid or install a new ROM.
I'm using CWM touch by the way.
Sent from my DROID RAZR using xda app-developers app

If you have adb access when in recovery, see if you can run the following and have /data unmount
Code:
umount -l /data
You'll need to be root, and if you're already in the mounts and storage screen, you'll need to go back one, and then select mounts and storage again for it to refresh. Could be something is still being accessed when it attempts to unmount /data causing the issues.

imnuts said:
If you have adb access when in recovery, see if you can run the following and have /data unmount
Code:
umount -l /data
You'll need to be root, and if you're already in the mounts and storage screen, you'll need to go back one, and then select mounts and storage again for it to refresh. Could be something is still being accessed when it attempts to unmount /data causing the issues.
Click to expand...
Click to collapse
I've finally got Vicious v3 set up to the way I like. I'll try that next time. Maybe somebody else will see this post and try it if they are stuck.
It's strange, I've flashed many ROMs in CWM touch with ICS with no issues. I saw one post where someone believed it had to do with a new "storage" folder that is created in JB. If you use a file explorer you'll see a "storage" folder and inside it it is linked to the sdcard.
Should cache be mounted when I first boot into recovery? I've never noticed that before but I haven't had a need to check until now.
Thanks for your response.

guide based on your post
hobby31 said:
I was one of the ones with problems with trying to restore nandroids and wiping data. I got stuck going from vicious JB v1 to V2 then back to v1. Somehow, after attempting to restore numerous nandroids of ICS and my nandroid of V1 I somehow got it to boot.
Now, I've noticed that whenever I boot into recovery if I go to "mounts and storage" I see cache is mounted. I can unmount it and make a nandroid. Then if I go back to "mounts and storage" I see data is mounted and wont unmount so when trying to restore a nandroid it hangs at the data part.
He is what I do that has been working for me.
Once in recovery, I go to mounts and storage and unmount cache. Make a nandroid. Go back to mounts and storage and see data is mounted and won't unmount. I then go to "advanced" and select reboot recovery. Once it reboots into recovery I go back to mounts and storage and see that data is unmounted. I then can restore a nandroid. I've done this successfully going from vicious v3 to BAMF v2 then back to vicous v3.
I just wanted to share this and hope it helps someone.
Thanks
Click to expand...
Click to collapse
Based on your post and some testing, I made a guide for people... kind of a step by step thing. Let me know if this captures the jist of your experience. http://forum.xda-developers.com/showthread.php?t=1749322

Thanks I was totally baffled yesterday when I did a full wipe and reflashed the rom only to find that my phone booted normally and all my apps and data were there. Whats the deal with getting stuck on the google screen though? Does it just take a long time? I needed my phone for work last night and couldnt wait, which is why I tried flashing a nandroid...

Step by Step
How to restore a Nandroid or flash new ROM with CWM Touch
In CWM Touch Recovery
1. Go to mounts and storage and unmount cache.
2. Make a nandroid. (Going back to mounts and storage, you will see data is mounted and will not unmount.)
3. Go to "advanced" and select reboot recovery.
4. Once phone reboots into recovery, go back to mounts and storage and see that data is unmounted. You may now wipe data, system, and cache.
5. You may now restore a nandroid or flash a new rom.
If this helped you, hit thanks. Also, thank hobby31.

Confirmed working going from vicious v1, back to a 4.04 nandroid.
Sent from my Galaxy Nexus using xda app-developers app

I have been having a similar issue
I have tried several of the JB roms, and haven't found one that will let me reboot the phone. Every one get to the google screen and never past, and I ended up having to flash the stock rom before I can get anywhere. Anyone else having this issue or found a fix?

richiewrt said:
I have tried several of the JB roms, and haven't found one that will let me reboot the phone. Every one get to the google screen and never past, and I ended up having to flash the stock rom before I can get anywhere. Anyone else having this issue or found a fix?
Click to expand...
Click to collapse
If it is what was happening to me and a few others it has something to do with the data not unmounting in CWM. I went through all the boot looping, stuck on the google screen, battery pulls and pulling my hair out. After some digging I noticed that data would not unmount in CWM so when I rebooted I quess it would hang somewhere while trying to load data. Essentially, when I was wiping data in CWM it looked like it was doing something but really wasn't.
My fix is what is in this post. Basically, going to "advanced" in CWM and "reboot recovery" usually unmounts the data then you can wipe it. Then reboot recovery again as it seems to get stuck mounted again after wiping. Then reboot the phone after making sure nothing is mounting in "Mounts and storage".

hobby31 said:
I was one of the ones with problems with trying to restore nandroids and wiping data. I got stuck going from vicious JB v1 to V2 then back to v1. Somehow, after attempting to restore numerous nandroids of ICS and my nandroid of V1 I somehow got it to boot.
Now, I've noticed that whenever I boot into recovery if I go to "mounts and storage" I see cache is mounted. I can unmount it and make a nandroid. Then if I go back to "mounts and storage" I see data is mounted and wont unmount so when trying to restore a nandroid it hangs at the data part.
He is what I do that has been working for me.
Once in recovery, I go to mounts and storage and unmount cache. Make a nandroid. Go back to mounts and storage and see data is mounted and won't unmount. I then go to "advanced" and select reboot recovery. Once it reboots into recovery I go back to mounts and storage and see that data is unmounted. I then can restore a nandroid. I've done this successfully going from vicious v3 to BAMF v2 then back to vicous v3.
I just wanted to share this and hope it helps someone.
Thanks
Click to expand...
Click to collapse
Had a similar issue but my system was not mounted, remount system and I could restore nandroid.
Sent from my Galaxy Nexus using xda app-developers app

Don't use touch cwm; use normal cwm
Sent from my i9250

bk201doesntexist said:
Don't use touch cwm; use normal cwm
Sent from my i9250
Click to expand...
Click to collapse
Not necessarily. I have tried both TWRP and CWM, and even CWM normal, and I am still screwed. Everytime I try to restore, I get an error restoring /data. Looks like I may be going back to stock.... This whole JB thing has made my Nexus feel like a Droid Bionic! :crying:
EDIT: Used the Gnex Toolkit, got back to stock, rooted and recovery installed and right back to AOKP 40. I think I will wait until this gets ironed out. Bit more work than I would like to crack flash. :laugh:

Thanks for this!

PLEASE HELP! Can't boot or use CWM

I'm on the latest AOKP Jelly Bean build. Everything was working perfectly fine until I rebooted by phone after a charge. It gets stuck at the Google screen for about 4 or 5 minutes then just goes black. I can get into Clockworkmod, but it's showing a whole bunch of errors every time I try to do anything "E: Can't open cache/recovery/log, E: Can't mount cache/recovery/log". It also will not mount the SD card.
Please help!!!

I had this problem when I first unlocked the bootloader and rooted. Do a search for returning your phone to stock. You only need to do the last step that flashes the system partition. You will lose your data, but your phone should work.
This is the site I used, step 6 only:
http://androidtobe.blogspot.com/2011/12/galaxy-nexus-installing-ics-402-from.html?m=1
Sent from my Galaxy Nexus using Tapatalk 2

Use Odin http://db.tt/PVsnbLIM
And flash this https://dl.google.com/dl/android/aosp/mysid-imm76k-factory-98d21321.tgz
If you want to attempt to save ur data boot into recovery and with using adb from a PC run
adb pull data/media.. and see if it works. try to mount /data first but I have a feelin its gone

Recovery Options
If you can get into CWM, what happens if you do a wipe of system, data and dalvik then reboot?
If that fails, your next step is to try and reflash a new ROM image, but that could be tricky if you don't already have a ROM image on the sdcard partition on the phone. I don't know how you can copy a new image over to the phone if you can't boot to Android. If anyone knows how to do that, it would be useful to know...

CMW > mounts and storage > mount /data
adb push NAME OF File.zip /sdcard/
unmount /data

[Q] all actions within clockworkmod recovery freeze on first action

i downloaded CM 10.1 RC 2 and attempted to flash and got the unlimited loader, so i went back into cwmod and whether it's flashing another rom, deleting cache using built in cache deletion, or using dark swipe cache deletion, it only ever performs the first action and freezes at that screen.
for example, 15 minutes ago i tried flashing SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip and all it has the screen has displayed for the past 15 minutes is:
ClockworkMod Recovery v6.0.1.5
-- Installing: /sdcard/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip
using the "wipe cache partition" option shows:
ClockworkMod Recovery v6.0.1.5
-- Wiping cache...
Formatting /cache...
and the screen stays on that until i take out the battery. any thoughts?

Same boat
I think I am in the same boat as you, but with CMR v6.0.3.1. Bonus is I haven't figured out how to get my computer to see my phone on USB in order to reflash stock using Odin.
One thing my previous searches turned up is INFAMOUS super wipe, which I believe is what we need to use with CM10.1 rather than DARKSIDE. Can any more experienced people confirm or deny?
Thanks
ixxalnxxi said:
i downloaded CM 10.1 RC 2 and attempted to flash and got the unlimited loader, so i went back into cwmod and whether it's flashing another rom, deleting cache using built in cache deletion, or using dark swipe cache deletion, it only ever performs the first action and freezes at that screen.
for example, 15 minutes ago i tried flashing SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip and all it has the screen has displayed for the past 15 minutes is:
ClockworkMod Recovery v6.0.1.5
-- Installing: /sdcard/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip
using the "wipe cache partition" option shows:
ClockworkMod Recovery v6.0.1.5
-- Wiping cache...
Formatting /cache...
and the screen stays on that until i take out the battery. any thoughts?
Click to expand...
Click to collapse

rhoegg said:
I think I am in the same boat as you, but with CMR v6.0.3.1. Bonus is I haven't figured out how to get my computer to see my phone on USB in order to reflash stock using Odin.
One thing my previous searches turned up is INFAMOUS super wipe, which I believe is what we need to use with CM10.1 rather than DARKSIDE. Can any more experienced people confirm or deny?
Thanks
Click to expand...
Click to collapse
While you are in download mode hook your phone up to the computer and see if it starts trying to download an odin driver or not. Mine did that one time for me. As soon as you go into download mode plug it in to see. If not redownload the adb drivers and while they are installing keep phone plugged in to usb. As far as darkside wipe you do not need that anymore and yes infamous wipe is better suited for your needs. In recovery can you access mount and storage option? if so, format data, format system. format cache, then flash new rom or recovery if possible. I do not ever dirty flash even though you can do it. I like to make sure every rom I install is clean so I always wipe cache, wipe dalvik, format data, format system, format cache, etc. Might seem like a lot to do but it always works for me.

richardlibeau said:
While you are in download mode hook your phone up to the computer and see if it starts trying to download an odin driver or not. Mine did that one time for me. As soon as you go into download mode plug it in to see. If not redownload the adb drivers and while they are installing keep phone plugged in to usb. As far as darkside wipe you do not need that anymore and yes infamous wipe is better suited for your needs. In recovery can you access mount and storage option? if so, format data, format system. format cache, then flash new rom or recovery if possible. I do not ever dirty flash even though you can do it. I like to make sure every rom I install is clean so I always wipe cache, wipe dalvik, format data, format system, format cache, etc. Might seem like a lot to do but it always works for me.
Click to expand...
Click to collapse
Apologies if I am hijacking the OP, maybe you can try these things too and tell us if you have different results?
Under mounts and storage, I was able to format /data and format /system, but the phone froze up while formatting cache:
ClockworkMod Recovery v6.0.3.1
Formatting /data...
Done.
Formatting /system...
Done.
Formatting /cache...
Click to expand...
Click to collapse

rhoegg said:
Apologies if I am hijacking the OP, maybe you can try these things too and tell us if you have different results?
Under mounts and storage, I was able to format /data and format /system, but the phone froze up while formatting cache:
Click to expand...
Click to collapse
I am not using cwm 6.0.3.1 so I don't know. I use a custom cwm by sk8terwitskilhttps://www.dropbox.com/s/d5zpq8tg5sznegg/cwm6027touch_v14.4.6_hercules.zip

You cannot use Darkside Superwipe on CWM6. It is compatible with CWM5.
Sent from Evils Cradle of Filth T999

alloycowboy said:
You cannot use Darkside Superwipe on CWM6. It is compatible with CWM5.
Sent from Evils Cradle of Filth T999
Click to expand...
Click to collapse
So how does he recover if he already made the mistake?

rhoegg said:
So how does he recover if he already made the mistake?
Click to expand...
Click to collapse
He has to re-flash a recovery with Odin. If that doesn't work, re-flashing a stock ROM with Odin will work.
It sounds like you have a problem with your USB port though, so I am not sure what you can do to fix your phone.

[HELP] E: Unable to mount /data in Recovery.

So tonight I decided to wipe my tab pro 10.1 wifi (SM-T520) and flash the same ROM I've been using for ages (GraveDs 3.0). I just boot into recovery (TWRP 2.7.0.1) like I always have, start wiping everything except extSD. It hangs during wipe and automatically reboots into a bootloop. I get a mild heartattack and now my tab is bricked. I can still get into recovery but can basically do nothing in it because it can't mount data. At first it couldnt mount cache only, but now it can mount cache but not data.
Is there any manners of ways I can unbrick this? I've never really had any issues before
I've read somewhere that you can use the TWRP Terminal to manually format your partitions, but I wouldn't even know where to begin to find the commands that work with my specific tablet. I've been Googleing all day and can't find anything relevant to SM-T520 I also have no nandroid backup because idiocy.
Any help, anything at all, is greatly appreciated.

Fixed it by flashing newest version of TWRP (v2.8.7.0) using Odin 3.07, then I used the new feature under wipe in TWRP to format my data partition into a different file format then back to the original file format and it was finally mountable and flashable again. Thank the lord for that!

Glad to hear you fixed it quickly

Phone stuck in bootloop. Tried tons of things.

So, I have an N7100. I have rooted my phone a few times. The last time was over a year ago and it worked fine. Yesterday, suddenly (I haven't attempted to flash anything) it restarted on its own and won't boot. I tried to go into the TWRP recovery I had installed over a year ago, but TWRP will only load for a second and then disappear and the phone would restart again and go into the bootloop. As a result, I can't wipe cache partition.
I can confirm that I can connect successfully to ODIN and flash a different version of TWRP. I have failed to flash CWM so far... maybe I couldn't find a correct version since my phone has knox???
I tried flashing a different kernel, but that didn't work either. Do I need a specific kernel?
The only thing I need to do is recover my files, whether it is through recovering the phone, or accessing the internal storage.
Can someone please help me? I don't want to do a complete wipe.
And in case this is relevant, my ROM is the custom OMEGA rom, I'm not sure which version though. Either 31, or 26, which is either for android 4.3 or 4.4.2.
Thanks

Hey,
I have the same problem, the phone just restarted on it's own yesterday, restarted again and is now stuck at the bootlogo.
Wiping Cache and Dalvik on it's own doesn't suffice, Wiping the system partition too (TWRP) gets the phone to boot, but it will restart again after a couple of minutes, again stuck at the boot logo.
I'm using the limbean ROM.
shadnixx, wiping the system partition does not mean that you're going to loose your data - you should try that, after the factory reset the phone is usable for a couple of minutes, I will now try to flash a newer ROM and gapps, maybe the problem will go away with that.

quickhash said:
Hey,
I have the same problem, the phone just restarted on it's own yesterday, restarted again and is now stuck at the bootlogo.
Wiping Cache and Dalvik on it's own doesn't suffice, Wiping the system partition too (TWRP) gets the phone to boot, but it will restart again after a couple of minutes, again stuck at the boot logo.
I'm using the limbean ROM.
shadnixx, wiping the system partition does not mean that you're going to loose your data - you should try that, after the factory reset the phone is usable for a couple of minutes, I will now try to flash a newer ROM and gapps, maybe the problem will go away with that.
Click to expand...
Click to collapse
Thanks for replying. I can't wipe the partition. That requires that I get into recovery, right? I can't even get into recovery. TWRP loads for just 1 second and then the phone reboots.

shadnixx said:
Thanks for replying. I can't wipe the partition. That requires that I get into recovery, right? I can't even get into recovery. TWRP loads for just 1 second and then the phone reboots.
Click to expand...
Click to collapse
have you tried to reinstall TWRP recovery? Maybe yours is corrupted, try to flash the latest version again. If that help you boot in recovery, things will be easier to haddle after.
https://dl.twrp.me/t03g/twrp-3.0.2-0-t03g.img.tar.html
also see this if it can help you
http://techbeasts.com/install-latest-twrp-recovery-on-samsung-galaxy-note-2-all-variants/

logosA said:
have you tried to reinstall TWRP recovery? Maybe yours is corrupted, try to flash the latest version again. If that help you boot in recovery, things will be easier to haddle after.
also see this if it can help you
Click to expand...
Click to collapse
Yeah I already tried that. Thanks though

@shadnixx Well use every possible way to flash and enter custom recovery. Try Philz, TWRP, CWM, everything...
If everything fails you'lll have to reflash Stock ROM using Odin. I've heard is wipes data but not internal storage but I'm not sure and don't balme me if it happens. Search xda a little.
See these threads: http://forum.xda-developers.com/showthread.php?t=2583588
http://forum.xda-developers.com/showthread.php?t=1121817
If that fails then the phone has hardware damage I think. Needs to go to service.

Option58 said:
@shadnixx Well use every possible way to flash and enter custom recovery. Try Philz, TWRP, CWM, everything...
If everything fails you'lll have to reflash Stock ROM using Odin. I've heard is wipes data but not internal storage but I'm not sure and don't balme me if it happens. Search xda a little.
See these threads: http://forum.xda-developers.com/showthread.php?t=2583588
http://forum.xda-developers.com/showthread.php?t=1121817
If that fails then the phone has hardware damage I think. Needs to go to service.
Click to expand...
Click to collapse
Thanks for your reply. That's what I'm trying to do. One question... do I have to have a specific CWM version that is compatible with my ROM?

Progress
OK, while flashing TWRP failed to help, flashing Philz Touch enabled me to get into recovery. I was able to mount the external SD card and browse the files, but the real problem is with the internal storage, since the SD card is removable. I couldn't manage to mount it. Can someone help with that?
Wiping the cache partition didn't help either.

You tried different tar versions of twrp?
What is the error message in Odin when trying to flash twrp?
Tried flashing twrp with different USB cables and USB ports?

audit13 said:
You tried different tar versions of twrp?
What is the error message in Odin when trying to flash twrp?
Tried flashing twrp with different USB cables and USB ports?
Click to expand...
Click to collapse
I'm sad to report, after I wiped the cache and restarted my phone, Philz would behave like TWRP did, which is to load for 1 second then reboot. Yes, I tried 4 different versions of TWRP, same result. Odin doesn't give any errors. It says that flashing was successful. Tried different cables and ports too, yes.

Possible power button or battery problem?

audit13 said:
Possible power button or battery problem?
Click to expand...
Click to collapse
Don't think so. I just replaced the battery... still same problem. And when I enter Odin "Download" mode, it doesn't keep restarting, so I don't think it's the power button.
I got a small update though...
Flashed another version of philz, which works every time I boot to recovery. A few problems though...
1. I can wipe cache partition, no problem. But When I try to wipe Dalvik, the phone reboots as soon as I try.
2. Aroma file explorer doesn't show any files.
3. I can mount external SD, but I can't mount internal storage
4. When using ADB, it could finally initiate pulling files from the internal storage (or that's what it appears to be doing), but only while on recovery mode. A few seconds after it says "listing files" or something, the phone reboots and the ADB operation aborts. It doesn't behave like this when I access other sections of philz recovery.
Any thoughts?

Another small update...
While using philz, I clicked the "install zip from sdcard" and it showed my folders. I think my files are intact, but I guess I can't be certain.

Small update again...
I flashed Aroma File Explorer from Philz, I managed to enter my internal storage browse around for a bit, but then the phone rebooted again. I tried to repeat so I could copy my internal storage, but now my internal storage says symlink error.

shadnixx said:
OK, while flashing TWRP failed to help, flashing Philz Touch enabled me to get into recovery. I was able to mount the external SD card and browse the files, but the real problem is with the internal storage, since the SD card is removable. I couldn't manage to mount it. Can someone help with that?
Wiping the cache partition didn't help either.
Click to expand...
Click to collapse
Listen up - Transfer any ROM to your external SD card, touchwiz based to avoid any complications if you can.
When you get into recovery (at least on TWRP 3 on my Galaxy Note 2 LTE this works) you can connect your phone to PC and transfer all the files, it just gets recognised.
If that fails then wipe /data and /cache partition and see if it boots. If that fails/succeeds then try to flash new ROM and wipe /data and see if it will boot. Data is not the same as internalSD. Data is your apps and settings, you can reinstall that later. InternalSD is your pictures and all. You want your pictures, not your apps, right? It is different.
But who knows what happened here. Malware? Corrupt partition? Hardware failure of some kind? Don't blame me if flashing a new ROM breakes everything even more.

Option58 said:
Listen up - Transfer any ROM to your external SD card, touchwiz based to avoid any complications if you can.
When you get into recovery (at least on TWRP 3 on my Galaxy Note 2 LTE this works) you can connect your phone to PC and transfer all the files, it just gets recognised.
If that fails then wipe /data and /cache partition and see if it boots. If that fails/succeeds then try to flash new ROM and wipe /data and see if it will boot. Data is not the same as internalSD. Data is your apps and settings, you can reinstall that later. InternalSD is your pictures and all. You want your pictures, not your apps, right? It is different.
But who knows what happened here. Malware? Corrupt partition? Hardware failure of some kind? Don't blame me if flashing a new ROM breakes everything even more.
Click to expand...
Click to collapse
I'll try that, thanks.