Hi I've flashed my M9 Pro (Rk3188 rom) with an RK3066 rom in error. Now it continually loops in a CWM screen offering options to install rom from Sd card etc. When I try it cannot find the sd card, Using Adb I can see all the filesystems but when I sideload or push recovery files to the device it cant mount any of the filesystems. /cache /sdcard etc. I think the firmware cannot see any of the partitions. Can anyone pease help me in finding a way to rebuild the partitions via Adb or something similar as I can do nothing with the tablet itself.
Related
I am following the steps of rooting to a "T". I successfully got CWM Recovery installed. However, when I go to backup & Restore in Recovery it will not allow me to create a backup because it "can't mount /sd card".
Since this phone has internal storage and not an SD card, is there any way for me to fix this?
There is a slot in the phone for a MicroSDCard, most versions of CWM do however default to the internal memory for that option though.
But not all versions, it's possible you're using one of the few that tries to mount the MicroSD as /sdcard.
Maybe try flashing the Siyah kernel via Odin, it's compatible with all(?) SGS2 firmwares as far as I'm aware. It has a different version of CWM built in.
You could use an adb shell to see what's going on but most folks don't seem to know what adb is any more.
i yesterday install a new rom to my rooted s3(intl) today i try to reboot another rom i was stuck in cwm recovery...i wanted to install another rom from my sd card. but it says cant find any file in sdcard.... i cant back restore cz i dnt have back up file in phone as i moved my back up to laptop...when i search abt thz i found out this hapn because my sd card having some issue.
You most probably have an unpartitioned sdcard, clockworkmod however assumes that is partitioned and wants to mount the first partition (/dev/block/mmcblk0p1).
You can fix this by repartitioning your sdcard so that it has a mountable fat-formatted first volume and then retry.
If you don't mind using the commandline, boot to recovery and connect via adb shell to it, then mount your sdcard manually: mount /dev/block/mmcblk0 /sdcard and retry.
Technical explanation:
cat /proc/partitions lists:
/dev/block/mmcblk0 is your FAT formatted volume (no more partitions at all)
should be:
/dev/block/mmcblk0 (whole device)
/dev/block/mmcblk0p1 (1st partition, FAT formatted)
/dev/block/mmcblk0p2 (sd-ext partition, only for those that use SD2ext and such)
im new to rooting and these stuffs plz explain what is adb shell and how i can mount my sd card....
btw i also tried factory reset it didnt wrk too....i dnt want any files i just want my phone back cz i badly need it....plz help me on this guys :crying: plzzz :crying:
In cwm under mounts and storage there should be the option to format sd card...
Adb is android debugging, it's used to connect to, pull/push files, get logs and more from your phone using a terminal or command prompt window.
http://developer.android.com/tools/help/adb.html this site shows the adb commands available including shell which is connecting to your phone via the terminal to allow you to enter commands.
Also maybe try mount USB storage through cwm and see if you can connect you phone to your pc and transfer the files needed.
If I helped you in some way, take a second to hit the Thanks button.
I have a Nook Tablet 16GB. It won't even power on to the "n" logo screen unless there is a CWM SD Boot card installed. I get mount errors once inside CWM.
E:Can't mount / cache/recovery/command/
E:Can't mount / cache/recovery/log/
E:Can't open / cache/recovery/log/
E:Can't mount / cache/recovery/last_log/
E:Can't open / cache/recovery/last_log/
I've tried the Factory Restore (repart.img) and it runs through and tells me the device will shutdown in 5 seconds. (The other times I've used this it sits at a green check mark until I shut it down manually) This doesn't resolve the issue or make any changes at all.
I've tried Adam's Ubuntu method and the device boots to the SD card but sits at a blank screen after a few seconds and does nothing, even when left on over night. This doesn't resolve the issue or make any changes at all either.
I can connect to the device in ADB and the plan was to use parted to fix some partitions using Veronica's methods, but when I run the parted /dev/block/mmcblk0 print command no partitions are found at all on the device. I'm never prompted to fix any partitions either. The only thing it sees in the ext sd card partition. In the past when I've done this it shows 11 partitions with some details. This time it shows nothing. I am unable to find any information anywhere as to what to do next.
It is as though the internal SD Card (memory/hard drive whatever you call it) isn't working or detected by the system any longer.
Does anyone have any recommendations on what to try next? Please help!
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
digixmax said:
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
Click to expand...
Click to collapse
I made an SDCard using Succelent's repo and was able to boot to the Cyanoboot Bootloader but a few seconds later it just went to a blank screen. I rebooted and could get into recovery by holding the "n" button and selecting that. When I select to boot from SDC it just goes to Bootloader and then goes blank. It never boots into the OS.
I never mess around with partitions and I'm not sure how this thing got this way. I purchased it from eBay as a tablet for my daughter. It did say the device was bricked but that the hardware was okay. I've seen bricked devices in the past and the repart.img (Factory Reset) has always resolved the problem. I have a Nook Tablet that my son has been using so I've become pretty familiar with the basics of rooting, loading CWM, TWRP, Cyanogenmod, etc. But I've never seen it were I get mounting errors inside of CWM and am unable to flash anything. It won't even mount the external SDCard once inside CWM.
Not sure what to do and I hate to give up on this. Any help would be greatly appreciated.
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
This happened to me last year. There is a post in development section about fixing partition table by So****e. It's the last resort, but worked for me.Also, Adam Outlers Ubuntu method loses your serial number, gone forever. Good luck
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
DEjaVu
Happened to my first nookT not to long ago....It died but the best advice I can give has already been given try not to erase more stuff. Digimax helped me not to long ago. Make sure you format your sdcards correctly and if you can flash a recovery or boot into it you should be able to use one of Succulents cards. Good luck
digixmax said:
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
Click to expand...
Click to collapse
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found. I also tried wiping my cache partition again from inside cwm, but no luck. Still getting the mount errors.
I believe the real issue is that my device doesn't see /dev/block/mmcblk0 (or rather is sees it as the external SD card). there is no /dev/block/mmcblk1 either. I thought perhaps the internal and external were swapped, but that doesn't appear to be the case. So since the device can't recognize the internal SD card I don't think I will be able to get anything to flash until I get that resolved first. I'm certain that is why Adam Ubuntu fix and Meg's reprt.img aren't working.
Probably the only way to do that, if it is even possible, is to do it through ADB. Veronica has a thread that shows how to recreate all of the partitions, but when I attempt to do that it doesn't see the internal storage at all so I can't even get started.
I really hate giving up on anything so I will keep trying as long as it takes if I know it is possible to fix this, but I'm not sure what steps to take next to try and get the internal storage recognized.
For all I know it could be a permission issue.
Do you know any commands I can run from ADB Shell to try and get the internal storage recognized?
When I run a list command from ADB shell I get the following:
~ # ls
ls
boot fstab.acclaim sd-ext
bootdata init sdcard
cache init.rc sys
data internal_sd system
datadata proc tmp
default.prop recovery ueventd.acclaim.rc
dev res ueventd.goldfish.rc
emmc rom ueventd.rc
etc root
external_sd sbin
~ #
So it looks like the internal storage is working after all and I can get into some of these directories and files and CAT or TAIL them. Perhaps the MBR is messed up or something?
skelnik said:
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found.
...
Click to expand...
Click to collapse
You can try one of Succulent's more recent 10.2 builds listed at http://iamafanof.wordpress.com/2013...id-4-3-for-nook-tablet-imgsdc-boot-09aug2013/ which he uploaded onto Media Fire: "cm_acclaim_10.2.0-RC0_13OCT2013_HD_SDC_IMG.7z (mirror)".
You might also want to take a look at Succulent's recovery tools (in particular flash_stock_1.4.2.zip) at https://github.com/succulent/acclaim_recovery_sdcard.
Hello guyz, i'm trying to install int2ext script on my phone, but without success. I've got a Samsung S4 Clone with J.B 3.1, stock rom and stock recovery. I managed to create an ext2 partition through windows and enable init.d scripts with an googlestore app. Using a script named 05mountsd, the system manages to mount the ext2 partition and i'm able to browse it with root explorer. But when i copy any of the int2ext/int2ext+ scripts in the init.d folder (remember, i dont have cwm recovery to install from zip) the phone boots normaly and 5secs after i see my background, the phone goes back in loading android screen.
I have to delete the 40int2ext script from init.d through adb shell, for the phone to boot up normally again. Then inside the ext2 partition i am able to see that the script has managed to create some files and folders! But i cant install apps in there. Also link2sd app gives a message that the partition cannot be mounted and that i should try fat.
Any ideas how to get int2ext or any other storage script to work?
Bump!!!
I managed to install a cwm recovery that supports my phone's UBIFS format.
Still can't get any script that links apps to sd to work.
When i try to install CronMod_int2ext.zip through recovery i get an error. Also i cant mount or format the sd-ext partition in the recovery, though i tried partitioning the sd inside the recovery as well as from windows. Both attempts fail to mount in recovery.
With Mounts2sd app, i get bootloop problem.
Anyone!?
bump
931 6923243
bump!
SOLVED! See 2nd Post
Hi,
Galaxy S II 16GB 2.5 Years old.
I friend came to me with a problem : Waze can't start because it complains no access to sdcard (internal, no external present)
A bit fiddling and I see /storage/sdcard0 is mounted as RO!
I remount as RW, and I can now start waze, but as soon as I use the phone further, the mount reverts to RO.
I try to format it via recovery (philz) but it fails deleted odd named files in DCIM/Camera/cache.
So I try to delete the files myself but it fails.
Next up, I mount usb storage in recovery, and run windows Checkdisk, it finishes while fixing some stuff, the format still doesn't work.
Eventually using Minitool I am able to format it. BUT, now, when I boot android, it says the internal storage is damange, and attempt to format it via Android fails always.
Still, when I boot into philz, and mount usb storage, i can browse it via my W7 PC, copy and delete files freely. So I guess something is not mounted or formatted correctly. I decide to reinstall stock rom with Odin + repartition.
So I take pit file from a thread that aims to increase /data at the expense of internal storage, and I find the stock pit there and use it.
Rom flashes fully, but sdcard still not working.
What I want to do is :
Boot into Recovery and use Android commands to properly mount/map this so the phone recognizes it.
I have linux knowledge, I know how to get around a linux shell and use VI and permissions etc. I also messed sometimes with fstab on a pc to set up mount points, so I am not a complete stranger. I am rooted and need help
Any help would be appreciated.
So, I searched the net for quite a few hours, and found this post :
http://forums.whirlpool.net.au/forum-replies.cfm?t=2147315&p=-1&#bottom
Which solved my problem
I registered on that forum to thank the dude!
This command solve my problem :
newfs_msdos /dev/block/vold/259:3
I knew it will work the moment I saw the 259:3 which I saw in logcat that android cannot format.
Good work finding a fix yourself Hopefully other people in the same situation will find it useful