Database Develop

[Q] Darktremor's app2sd?

Okay so my Droid is running okay, but I would like to have more memory for apps. So I figured, why not just use the app2sd script from DT after partitioning my card in CWM like I did my Ascend. I tried these steps:
1. In the CWM recovery (2.5.0.1 and 3.1.0.2) there is no option ANYWHERE to partition the SD card like in the 2.x.x.x CWM on my Ascend.
2. I partitioned in ROM Manager and chose 512 Partition with 128 MB Swap. The phone reboots and partitions the SD, and I checked in MiniTool Partition Wizard to make sure, there was a ext3 partition and a linux swap.
3. I move all apps to Internal memory, went in to CM Settings and allowed application moving.
4. Flashed DT's beta 4 script in recovery and it wouldnt boot, had to clear dalvik cache.
5. Get back in and found that the apps had moved no where. I check the sd-ext folder in Root Explorer and it said empty folder. a2sdgui does not work, if I change something, it just changes back.
6. Reflashed, tried S2E (simple2ext) and had the same issue, it isnt recognizing the ext partition.
7. Reflashed and tried various other settings with no luck.
What should I do? I really dislike having 15mb of internal memory free. Any help would be loved
Here is the info:
Was using the latest CM7 build but now I tried it on SteelDroid 9... same issue

Got view but no replies? Need some help here....

delete all previous scripts and try link2sd. i have been using it successfully.

[Q] Please help - can't boot into recovery mount error

(Please let me know if this is the correct forum!)
I have a Motorola Milestone 1 (A853) with Open Recovery 1.46 on a 16GB card. I've been using this to try new roms for over 2 years now. Everything was fine until I tried to create an ext 2 partition using MiniTool Partition Wizard, but things went sideways. Needless to say I wiped the card, created a new 10GB Primary Partition on it and a 4 GB ext2 for further usage. Then, I restored backup items on the card (pictures etc.) plus a fresh new version of Open Recovery. Now, every time I am at the Recovery menu and try to apply sdcard:update.zip I get this message:
E:Can't open cache/recovery/command (<-- this is nothing new - seen it many times before but still able to boot into open recovery)
-- Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted
.. any ideas what to do?

It seems like your phone dont mount the sdcard properly.
Try out a 2ndboot OR. (there is one from kabaldan and one from FuFu)

get a proper sdcard, and unzip to the root OpenRecovery from this url: http://forum.xda-developers.com/showthread.php?t=1897048
And voila! :good:

Thanks for the assistance guys.
The card is fine, It is seen in Windows perfectly with the 2 new partitions, but the phone is not seeing it. I was following MrTapa's guide here before the trouble started: http://forum.xda-developers.com/showthread.php?t=1750888 . When the card worked before, it was formatted using NTFS and both Windows and the phone could see it. Now, the 10 GB partition is NTFS and it has the additional 4 GB ext2 partition. Windows sees it, the phone does not.
Does Skrilax_CZ's note have anything to do with it? "If file "/system/etc/install-recovery.sh" exists on your Milestone, delete it (prior to flashing the SBF)" <-- from http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html

lezztor said:
Thanks for the assistance guys.
The card is fine, It is seen in Windows perfectly with the 2 new partitions, but the phone is not seeing it. I was following MrTapa's guide here before the trouble started: http://forum.xda-developers.com/showthread.php?t=1750888 . When the card worked before, it was formatted using NTFS and both Windows and the phone could see it. Now, the 10 GB partition is NTFS and it has the additional 4 GB ext2 partition. Windows sees it, the phone does not.
Does Skrilax_CZ's note have anything to do with it? "If file "/system/etc/install-recovery.sh" exists on your Milestone, delete it (prior to flashing the SBF)" <-- from http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
Click to expand...
Click to collapse
NTFS?
Replace it with FAT32. Then it should work.
In the link you provided check step 9 (though FAT32 should work fine even with 2GB cards)

Ok - so reformatted 10GB partition to Fat32 and loaded OpenRecovery again to root of sd card - same error. I might also mention that I tried Fat32 on another smaller (2GB) card with an ext2 partition and it gave the same error. I'm beginning to believe that this phone has a problem with multi-partition sd cards?

Just tried the original way - one partition using NTFS ... same error. Frustrating .. over 3 days on this now ...

NTFS and Android can not work.
Unless someone included ntfs-3g into the kernel - but that would be a madman's work...
Delete every partition off your sd card, boot up Android, it will prompt you to format it, do it.
Copy recovery (OpenRecovery directory + update.zip) to sd card, try booting to recovery.
If it works resize FAT partition created by android to make space for an ext partition, boot Android again to see if it's ok with the changes.

Solved - if anyone is trying create an additional ext2 partition remember that BOTH the FAT32 and EXT2 must be created as PRIMARY. The app I was using defaulted to logical ...

[Q] Link2SD and any PC utils not reading SD-EXT Partition.

Hi all,
As the title says, I'm having a heck of time get anything to read the EXT partition on my SD card. Doesn't matter which ROM or which tool I use to format it nothing will pick up th EXT partition at all. I've tried the mini partiton tool on pc, CWM Recovery, and PX Recovery to format it and no joy. None of the a2sd scripts/utils (link2SD, s2e, Android Commander, MOBOROBO) will recognize the second partition or allow me to use it. Do I need to mount it through recovery manager or something? Any Ideas?
Regards,
Gordo1701e

gordo1701e said:
Hi all,
As the title says, I'm having a heck of time get anything to read the EXT partition on my SD card. Doesn't matter which ROM or which tool I use to format it nothing will pick up th EXT partition at all. I've tried the mini partiton tool on pc, CWM Recovery, and PX Recovery to format it and no joy. None of the a2sd scripts/utils (link2SD, s2e, Android Commander, MOBOROBO) will recognize the second partition or allow me to use it. Do I need to mount it through recovery manager or something? Any Ideas?
Regards,
Gordo1701e
Click to expand...
Click to collapse
Normally you do not need to mount anything.
Just partition using CWM.
Strange.

help, problem with internal storage

Hi at all, I've a problem with my samsung galaxy note n7000, I have the latest 4.1.2 original samsung touchwiz , I've only rooted it,
the problem is that the android os doesn't mount the internal sd card, and get me a notification that say "blank usb memory or not supported file system", I tried to reboot custom recovery(philz recovery) and wipe data and cache, format sd card but nothing works, can anyone help me????

Did you format it to fat32? In recovery did you try formating the external storage?

diaboliko.hacker said:
Hi at all, I've a problem with my samsung galaxy note n7000, I have the latest 4.1.2 original samsung touchwiz , I've only rooted it,
the problem is that the android os doesn't mount the internal sd card, and get me a notification that say "blank usb memory or not supported file system", I tried to reboot custom recovery(philz recovery) and wipe data and cache, format sd card but nothing works, can anyone help me????
Click to expand...
Click to collapse
*bump
I'm facing the same problem right now. It occurred after I did a hard reset. In the best case scenario, this is just a partition table corruption, but in the worst, a physically damaged card.
On Linux, I have fixed partition tables with a nifty tool called gpart (not gparted). There is a similar utility available for Linux, Windows, Mac etc. called TestDisk. Unfortunately, these tools are not available on Android. However, there is something called aparted available on Play Store that supposedly fixes filesystems.
I have installed it, but it wants to install some browser addons too. I've tried to repair the filesystem that it shows as empty, but no luck so far. I will shortly check its online manual, but I hope we can get something like gpart on Android.

diaboliko.hacker said:
Hi at all, I've a problem with my samsung galaxy note n7000, I have the latest 4.1.2 original samsung touchwiz , I've only rooted it,
the problem is that the android os doesn't mount the internal sd card, and get me a notification that say "blank usb memory or not supported file system", I tried to reboot custom recovery(philz recovery) and wipe data and cache, format sd card but nothing works, can anyone help me????
Click to expand...
Click to collapse
Hi, I have been able to get the Internal SDCard (/storage/sdcard0) mounted again, albeit with loss of data. Look at my recent post http://forum.xda-developers.com/showpost.php?p=48595569&postcount=24
and the one from which I got the hint
http://forum.xda-developers.com/showpost.php?p=35726016&postcount=6
The step by step procedure is here: http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
but if you have only one partition damaged, you could just check it with e2fsck and then, if necessary, recreate it with mkfs.exfat or the other method in the referred post.
EDIT: link to parted and other files: http://forum.xda-developers.com/showpost.php?p=38598228&postcount=4
http://www.droidforums.net/forum/htc-droid-eris/78650-internal-storage-partitions-screwed-up.html
I don't know if you can recover your original data - I had tried formatting the partition, by mistake, to ext4 with mke2fs. You could avoid this, and see if you can back up your partition with dd before re-formatting it to fat32.

solved, I download latest frimware, and flash it throught odin and all are fixed

NookHD+ can't mount emmc; can't fully boot from SD recovery

Perhaps someone can help. I've read a lot of the great content here but I've hit a wall.
A few weeks ago my ovation device was running cm11+cwm but began random rebooting. Clearing the cache+dalvik only helped briefly.
I tried an upgrade with a twrp 3.0.0.0 (using the amazing multiboot recovery SD), but it hung formatting the cache partition (I waited about an hour). Tried again, same thing.
I used adb shell to fix a blank file system type on the cache partition but was only successful in creating an ext2 partition there. I got cm13 booting but it trebuchet kept crashing. I tried twrp again and flashing a different image and tried a factory reset. Big mistake.
Now when I try to boot any recovery SD it doesn't boot all the way. Using adb shell, my dmesg shows that umount is hanging. No emmc partitions seem to be mounted. The partition data exists in dmesg but calls to parted hang. Mkfs.ext4 also hangs (naturally).
So I've lost the ability to fully boot recovery SDs (they are probably hanging when they try to mount the emmc partitions). As such I can't flash a recovery. I have a clockwork backup that has a system.ext.tar file in it, but I don't know how to use it at this point.
I can't mount /rom so I'm worried.
Is my emmc shot? Is there any way to tell?
Thanks!

Would a noEMMC SD be safe?
I guess what I was hoping to do was use adb to completely wipe and restore the device to a sane state, which would include repartitioning and formatting the emmc partitions. Is that possible? Maybe not at this point.
I guess another question would be: if my NookHd+ emmc is technically working but currently unrecoverable, is it possible for me to safely use a NOemmc SD card? There seem to be some warnings about those wrecking emmc but I can't find any technical explanation as to why.

Based on further diagnostics, my emmc is one of the faulty Samsung models and so I think the crashes and ultimate recovery failures were the failure of the emmc.
I've successfully installed 10.1 noEMMC on one microsd. Runs Okay but a lot of apps I am interested in don't work on android from this vintage.
I tried to install 4.4.4/CM11 noEMMC but it can't mount the necessary partitions as per the install process on the iamafanof Wordpress page. I also see SELinux errors in the twrp recovery log. Does anyone know how to overcome this mount issue that apparently impacts some people.

Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks

Sorry to resurrect this thread, But it exactly speaks to my issue. You mention that the blk0 and blk1 devices need to be switched for cm11 image to mount partitions properly. Does anyone know specifically where this might be done. Can files of the existing nov4 cm11 image be altered to reverse these two devices?

CalculonsTalent said:
Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks
Click to expand...
Click to collapse
Could you please teach me how to mount EMMC partitions and retrieve data specially /factory partition with ADB?
I can only boot my Nook HD+ with with bootable SD card with TWRP or CWM.
Thanks.