Develop Bugs

[Q] - Error mounting SDcard in CWM [SOLVED]

Hello I'm new to the nexus line and recently upgraded form a SGS. my phone is Rooted, unlocked boot loader and running the most recent version of CWM 5.5.0.4. I'm running the GSM version of the Nexus.
My question is how do I flash the my first rom? When I boot into recovery and click install zip from SDcard i get "E: Can't mount /sdcard/" I am also unable to mound the data partition within. windows drivers are installed for both fastboot and adb so I can flash that way, i'm just wondering what the exact steps are and if that error mounting data is normal.
I also downloaded the most recent franco.Kernel as I want to run that, I know how to flash that with fastboot but wasnt' sure if that is how you would flash a rom with the nexus, on the SGS i used to use odin.
Thanks and sorry for the noobness.

How did you "unlock fastboot" and "root" and "install CWM"? Did you use one of the "Tool Kits"?
Do you have ROM Manager installed on your device?

yiannisthegreek said:
How did you "unlock fastboot" and "root" and "install CWM"? Did you use one of the "Tool Kits"?
Do you have ROM Manager installed on your device?
Click to expand...
Click to collapse
Sorry, Yes I have ROM Manager installed and its' paid for.
I unlocked my boot loader using fastboot oem unlock, I rooted by using an app because I couldn't mount the data partition in recovery so had to use some app some guy made that downloaded the su.zip from clockwork and flashed on it's own.
I installed CWM using fastboot.
fastboot flash recovery recovery.img
it's the dam data partition that i'm really having trouble with, i'm just wondering if this is normal, all the posts on the web say to flash a zip by choosing "choose zip from scard" but mine wont mount???
I should also mention that my entire device is encrypted.....that is whats causing it isn't it?

I'm not 100% sure but it could be that you flashed the wrong recovery.
According to this thread
http://forum.xda-developers.com/showthread.php?t=1357642
the recovery for the GSM version is 5.5.0.2 and not 0.4.
I would flash the correct recovery then try again.

You can not mount sdcard from CWM recovery (don't ask me why, I don't know.. maybe because it is not supported yet ..)
anyway, do like me, use CWM 5.5.0.2 and then try again toflash zip files .. It works for me

P4p3r1n0 said:
You can not mount sdcard from CWM recovery (don't ask me why, I don't know.. maybe because it is not supported yet ..)
anyway, do like me, use CWM 5.5.0.2 and then try again toflash zip files .. It works for me
Click to expand...
Click to collapse
He posted it on his Google+ account here:
https://plus.google.com/112476065271141473049/posts
I'm starting to think it's my encrypted phone, technically when I boot I have to decrypt the device before it boots into android.
I'm going to factory reset and see if that helps. I have a feeling that is what my problem is

OK so that was the problem, the data partition was encrypted (now that I think of this it makes sense that it wouldn't mount) anyways, for whatever reason a factory reset from android wouldn't work. I removed the "recovery-from-boot.p" file from my system folder originally so the CWM image would remain in tact.
anyways, I flashed the original recovery over the CWM recovery, preformed a factory wipe (which is the only way to decrypt your phone) then flashed CWM back on and now I can mount the data partition
what a pain in the ass, guess I wont be encrypting the phone any time soon, I wish there was an option to decrypt the drive and then get into recovery....wouldn't have this issue.

spectre85 said:
OK so that was the problem, the data partition was encrypted (now that I think of this it makes sense that it wouldn't mount) anyways, for whatever reason a factory reset from android wouldn't work. I removed the "recovery-from-boot.p" file from my system folder originally so the CWM image would remain in tact.
anyways, I flashed the original recovery over the CWM recovery, preformed a factory wipe (which is the only way to decrypt your phone) then flashed CWM back on and now I can mount the data partition
what a pain in the ass, guess I wont be encrypting the phone any time soon, I wish there was an option to decrypt the drive and then get into recovery....wouldn't have this issue.
Click to expand...
Click to collapse
It is possible now on 4.1.2 to decrypt the device. You must provide a password for dectypting (chane from unlock pin to passw).

information on any Clockwork recovery that can load via extSD

USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....

So far i got ahold of the previous Clockwork before the touch came out but it doesnt have options for external and internal im still allowed to mount externalSD card but whats the for if you cannot ADB with clockwork nor install from exernal SD?
Thanks for your time guys
xgp0006 said:
USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
Click to expand...
Click to collapse

You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?

I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
B-Naughty said:
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
Click to expand...
Click to collapse

xgp0006 said:
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
Click to expand...
Click to collapse
If you're already running CWM, try the wiping and fix permissions before ODIN flash to stock with the TMobile image

Can´t flash ROM´s by CWM

Hi,
I need serious help.
I tried to install Vanilla RootBox rom on my Ace 2 NFC (i8160P) CZ.
So i did wipe data, cache, dalvik.
Then i add my Tee folder into rom (tee hack for P version) and i deleted the device model verification from updater-script because it is for non P version.
But when i try to flash the rom via cwm temporary, i stuck at this errors:
cant format unknown volume: /external_sd
cant partition unsafe device: /dev/block/mmcblk0p8
Click to expand...
Click to collapse
But my sdcard is working good (adata microsdhc class10 32GB)
Any solutions?
EDIT: I am using this http://forum.xda-developers.com/showthread.php?t=2389395 patch but not Version 2, but V1 flashed from CWM. This could be the problem. Or not?
EDIT2: I am doing downgrade with repartition to GB an then flash JB... Nicely Done.. but when i try to flash other ROM, still gets the error. OMFG.
EDIT3: So it looks like i need to repartition or do something with mmcblk0p8 partition but what? OMFG, help me please!!!

...
it seem great problem ask from rom creater i thinck they can help you

majid92 said:
it seem great problem ask from rom creater i thinck they can help you
Click to expand...
Click to collapse
Supposedly the mmcblk0p8p partition is the internal storage, named UMS --> Usb Mass Storage
So best check if that reads properly in android (file explorer) and/or when u connect it to your computer.
Seeing as your external SD works good and it complains about that too tho, I don't expect your internal SD to be faulty either.
As for the memory fix you flashed, when u reverted back to GB and then re upgraded to JB, was there a param.lfs.md5 file present in the package (assuming u used odin, u should be able to verify this by opening the tar.md5 in 7zip or winrar)
If yes, then any harm caused by the memory fix will have been undone and that isn't the cause either.

Carpe-Dimi said:
Supposedly the mmcblk0p8p partition is the internal storage, named UMS --> Usb Mass Storage
So best check if that reads properly in android (file explorer) and/or when u connect it to your computer.
Seeing as your external SD works good and it complains about that too tho, I don't expect your internal SD to be faulty either.
As for the memory fix you flashed, when u reverted back to GB and then re upgraded to JB, was there a param.lfs.md5 file present in the package (assuming u used odin, u should be able to verify this by opening the tar.md5 in 7zip or winrar)
If yes, then any harm caused by the memory fix will have been undone and that isn't the cause either.
Click to expand...
Click to collapse
So, yes it is the USB storage, and its working well too. param.lfs.md5 was there. I dont know what to do now.

you are using the temporary CWM tho right? which needs to be flashed via stock recovery? and stock recovery doesn't complain about your mmcblk0p8 partition?
if this is the case, then you can root the stock rom via stock recovery --> http://forum.xda-developers.com/showthread.php?t=2139263
download this kernel for stock rom --> http://forum.xda-developers.com/showthread.php?t=2171054 -extract the zip and place the kernel.bin.md5 file on the root of your internal sdcard
install any terminal emulator, open it and and enter/type su -click accept when prompted for superuser permissions
with that all done enter "dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15" make no typo's on that one, it's lethal.
If done right, it will replace stock kernel with D kernel. which will contain the same version of cwm as in the temporary cwm zip, but with a bit of luck it will not return the error anymore then
if the problem does persist tho, you can also try both touch and regular versions of this kernel -> http://forum.xda-developers.com/showthread.php?t=2424964
extract and rename to kernel.bin.md5, place on internal sd and flash them the same way again via terminal emulator.
there is more hope for this kernel as both versions run different versions of cwm than D-kernel (and eachother), but if this does not solve the problem, you will not be able to boot as that kernel is incompatible with stock rom and you will have to reflash via odin.

Carpe-Dimi said:
you are using the temporary CWM tho right? which needs to be flashed via stock recovery? and stock recovery doesn't complain about your mmcblk0p8 partition?
if this is the case, then you can root the stock rom via stock recovery --> http://forum.xda-developers.com/showthread.php?t=2139263
download this kernel for stock rom --> http://forum.xda-developers.com/showthread.php?t=2171054 -extract the zip and place the kernel.bin.md5 file on the root of your internal sdcard
install any terminal emulator, open it and and enter/type su -click accept when prompted for superuser permissions
with that all done enter "dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15" make no typo's on that one, it's lethal.
If done right, it will replace stock kernel with D kernel. which will contain the same version of cwm as in the temporary cwm zip, but with a bit of luck it will not return the error anymore then
if the problem does persist tho, you can also try both touch and regular versions of this kernel -> http://forum.xda-developers.com/showthread.php?t=2424964
extract and rename to kernel.bin.md5, place on internal sd and flash them the same way again via terminal emulator.
there is more hope for this kernel as both versions run different versions of cwm than D-kernel (and eachother), but if this does not solve the problem, you will not be able to boot as that kernel is incompatible with stock rom and you will have to reflash via odin.
Click to expand...
Click to collapse
Ok, Yes I have rooted stock ROM and temporary CWM, so i am going to try the D-kernel. Hope is compatible with P version.
EDIT:I did the steps, and now, succesfully hardbricked Lol Checksum was ok, command too. OMFG
PC is showing "U8500 USB ROM" in device manager when I connect the USB cable so.. thanks
mybe there is problem that the kernel is build on the me7 or mf1 software.
Guys for everyone who has P version Never flash normal version officiel fw like me7 mf1 via odin on P version of ace 2 it will hardbrick you device that they have to change the motherboard so be carefully
Click to expand...
Click to collapse
EDIT2: LOL i putted battery out for a while and now can go to download mode. But i am at school so now i´ll go home and try odin... AGAIN
EDIT3: I am online again, phone is running well on the stock rooted JB again.. still cannot flash roms, but whatever...

Heya, sorry for the lack of response I've been a lil busy.
I thought that kernel would work on P version as well tho, sorry about that :crying:
Glad to see that you recovered your phone from that atleast.
Last thing i can think of then is to use this kernel --> http://forum.xda-developers.com/showthread.php?t=2072872
It's built for gingerbread, so your phone will again not boot after flashing, but the 8160Pxxlk3 version will for sure be compatible with your phone, and it has yet another version of CWM you might be able to use for flashing
If that doesn't work tho, I really am out of options

gapps-jb-20131011
Hi. I am using Sony Xperia NEO L and managed to upgrade to JB. I followed the steps until i hot a noticed saying that the Installation aborted. What went wrong? Please help! I'm stuck here and cannot going anywhere :crying:

[Q][DEVIL2 KERNEL] Problem after F2FS Formatting

Hi, This is my first forum after study here for some time.
And I need a little help from my fellow XDA members here.
My issue happens when I flashed Devil 2 Kernel and managed to
formatted to F2FS file system with his instruction.
Then I decided to try another kernel, so I try to re-formatted file system back to ext4
which is worked fine until I reach the last step of formatting (I am not very sure about the text
but it seems like "format /sdcard and ...something i can't remember...")
and it just restarted itself and got stuck in a bootloop
Now I tried to fix that by..
- Installing another recovery, TWRP, it just shows splash screen in a loop. No Luck
- Try to make Devil Recovery zip file to be flashed by Odin. No Luck
...I have this error message...
$ tar -H ustar -c recyovery.img > recovery.tar
tar: recovery.img: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
- Force-flashed whole stock rom that I downloaded from sammobile.com via Odin. No Luck
It just stuck at "Getting PIT for mapping" forever.
All of them are just don't work for me.
So I kindly as XDA members here what I can do with this situation.
or at least.. How can I (properly) convert .zip file to .tar.md5 ??
Thank you very much.

not sure why would you want to convert zip to tar ? why do you need that ?
Have you considered reformatting the device partitions through adb ? I have never done this before but I think it should be possible
edit : you need to use the latest TWRP, anything before 2.7.0.0 had problems with f2fs, just in case you were trying an older version.

ticktock666 said:
not sure why would you want to convert zip to tar ? why do you need that ?
Have you considered reformatting the device partitions through adb ? I have never done this before but I think it should be possible
edit : you need to use the latest TWRP, anything before 2.7.0.0 had problems with f2fs, just in case you were trying an older version.
Click to expand...
Click to collapse
I don't know why, but I can't flash both TWRP 2.7.0.0 or Devil Recovery itself via recovery mode.
So I wanted to try if the result is the same if I flash it via Odin
But I interested in formatting my device through ADB. How ?
Because I can't enter recovery mode, and I have no system to boot into.
Sorry for this seems-to-be-noob question, but I really can't find the way.
PS. From my little understanding, PIT file can be used to partition my phone in Odin, right?
But will it play any role in this situation? Just curious...

download the tar version of twrp from their site and flash it through odin, see if that works

Wiped my os need help.

today i was trying to wipe my phone in twrp to re start everything. i was inside wipe/advance wipe and i click all the check boxes. System cache micro sd internal storage all of em. i did not no that it would wipe my os. now im stuck without an os and ive tryed to flash a stock rom onto it with odin but it just tells me Nand write failed on it so idk what im doing or what i am doing wrong.

Here's what I would do to at least get a working ROM on the phone:
1) copy the latest version of d2lte cm11 to your external SD card: https://download.cyanogenmod.org/?device=d2lte;
2) flash the latest tar.md5 version of Philz Touch from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/ in the PDA box of Odin;
3) reboot to recovery and flash CM11.

audit13 said:
Here's what I would do to at least get a working ROM on the phone:
1) copy the latest version of d2lte cm11 to your external SD card:
3) reboot to recovery and flash CM11.
Click to expand...
Click to collapse
thank you for the response. only thing is. i dont have a sd card.
how do i no what rom i need to flash with odin?
and what pit file i need to use?
i have a file but in odin i just get write failed

also i downloaded the phils touch thing and there is no md5.tar file in it so i cannot find anything on the odin pda

Use Odin 3.07 to flash Philz Touch in the PDA box. Philz is a custom recovery for the d2lte (North American s3). The file you need is d2lte/philz_touch_6.48.4-d2lte.tar.md5
You flash CM11 (the ROM) in recovery mode, not with Odin.
There is no need for a pit file.
Without a microsd card, you would need to push a ROM to your phone via ADB commands which is rather complicated for beginners.

ok im downloading that version and i have that version of odin. i also got my hands on a sd card. just cant get this odin to do what is needed.

Are you putting the phone in download mode before connecting to Odin? What errors are you getting?

it worked thanks, well the odin part worked. im still waiting on the cm11 to finish downloading so i can flash it. how did you no what i needed. ive been researching for hours man and i couldent find anything that would help me.
i have this file root66_ATT_I747UCDLK3.tar and i downloaded a file it was like i747cuem some other letters i cant find the file now just have all that was inside it.

also in the phils touch it tells me that i cannot mount /data to setup /data /media path! and i dont no how to fix that cause my phone wont open up on my computer so i cant put the files in it

It's been a while for me but you need to install a zip from external SD card.
The nand write failure you got in Odin was probably due to the fact that you have a 4.3 or 4.4 bootloader on your phone. The LK3 file has a 4.1.1 bootloader. Once you have a 4.3 or 4.4 bootloader on your phone, you cannot load a file with a 4.1.1 bootloader.

i cant get it to even open on my computer to put the files on it >.<

hopefully gott it to work, flashed cm on it now im waiting with the little head and the arrow spinning around him been doing so for like 3 minites thou...

yeah idk its just stuck on the cyanogenmod boot screen ig uess it wont go anywhere from there

Boot back into recovery and factory reset. Then reboot. It'll appear to hang for a few minutes, this is normal as it is rebuilding dalvik-cache.
Sent from my SAMSUNG-SGH-I747 using Tapatalk