Develop Bugs

Accidentally formatted ex sd card in cmw !!

Hello All,
This is my first thread! I recently rooted my tmo sgs2 in order to get the full potential out of my phone. I loved it and was going flash crazy. Everything seemed to be going well until i accidentally formatted my external sd card in CMW. I was on Jug 5.0 Ultimate ICS edition and now im on the blackedition. Now all my backups are gone and some things on the phone dont seem to be working properly. Any suggestions? I tried looking through other threads but none seemed to help. Any feedback would help.
Thank you
-From a noob that just wants the best out of his phone

how important is recovering the data? typically a 'deletion'/'format' just dereferences the blocks from the memory allocation table so the data is still there. and thus you can use recovery software to get most of it back. but i'm basing this off experience with hdds and ntfs not flash memory (and probably fat32).
and formatting it shouldn't affect how your phone runs unless you moved app installations to it...

Either don't copy anything to the SD, and use a program like undelete I think is the name, wouldnt flash anythig from this method anyways, or dl a new ROM to the SD card and reflash, wiping he SD is wiping the SD, that's ur own bad and no way to actually "restore"

OK well i didnt move any of my apps to my sd so im guessing the rom is just kind of buggy then. But now when im in the process of wiping dalvik code it says
E:unknown volume for path [/sd-ext] ?!?!?

henryvutran14 said:
OK well i didnt move any of my apps to my sd so im guessing the rom is just kind of buggy then. But now when im in the process of wiping dalvik code it says
E:unknown volume for path [/sd-ext] ?!?!?
Click to expand...
Click to collapse
It says that when i wipe dalvik as well but ive never wiped my sd so i don't think that's why
Sent from my SGH-T989 using Tapatalk 2 Beta-5

Did a little googling,
/sd-ext is the mount point for Linux EXT-type partitions used with Apps2SD. It was a clever gludge from before Android supported moving apps natively; supported ROMs moved all installed apps to this new partition and symlinked them back to /data/app, so tricking the OS. Subsequent installations went to this partition also.The error is perfectly normal on devices with no EXT partition and is simply a result of the CWM code supporting a huge range of devices.
Sent from my SGH-T989 using Tapatalk 2 Beta-5

[Tool][Port][Blackhole Nullifier & Wipe][1.5a][6.3.12] Discontinued

I've been working on this port for personal use, but I figured others may find this useful.
What is it?
It's a script flashed through recovery, same as when you flash a ROM, that wipes for you in one simple step!
What does it do? (Wipe)
Depending on which version you choose, it calls on mke2fs and e2fsk to format /cache /data /system, then check the partition afterwards.
It will wipe /cache for the cache only, or system, cache and data for the full wipe. It does not do the external SD card, but it WILL FORMAT INTERNAL SD!
What does it do?(Nullify)
Same as the wipe, however this first calls on DD to zero out the partition, leaving NO DATA behind. Its a full overwrite of all data in the partition, with no way to salvage after running. The chances of anyone being able to recover any data after this is run is pretty slim outside of extreme power users and like..the CIA or something. Even then the data would be so corrupted I doubt anything usable could be rebuilt. Best used when bugs come up regardless of wiping multiple times, or prepping the tab for sale, no personal data can be retrieved from the internal SD.
How do I use it?
This is assuming you run a custom recovery!
System Wipe:
Reboot into recovery (this has been tested on my personal device with CWM and TWRP).
Make a full backup.
Install from SD, pick the system wipe zip.
Install the zip.
Wait a bit, it should take a minute for full wipe.
You can either restore a backup or flash a new ROM zip.
OPTIONAL: Fix permissions
Reboot system
NOTE even on a restore first boot will take longer then normal.
Cache Wipe:
Reboot into recovery.
Make a full backup, just in case.
Install from SD, pick Cache Wipe zip.
It'll take a second.
OPTIONAL: Fix permissions
Reboot system
NOTE boot will take a little longer then normal.
Nullifier:
Make sure you have at LEAST 50% battery or are plugged in.
Copy all information and files you want to save from Internal SD to PC or external SD card (the slot one).
Reboot into recovery.
Make a nandroid backup.
Install zip from SD, pick the nullifier zip you want to run.
Cache nullify takes about 9 minutes, full system takes about 35-40.
Check if you can mount /system /data and /cache, if you can, proceed, if not, reboot recovery (recovery not system!)
Install from zip, pick your ROM zip, or restore a nandroid.
Reboot system, and do whatever the DEV suggests.
NOTE Boot will take longer then usual.
What's this ported from?
This is based on work by Volk's Nullifier script for the G2x, and based directly on the Hellfire Nullifier. It's no longer really even close, but the concept and work is still based on their work.
What does each version do?
Cache Wipe: Formats /cache and deletes /data/dalvik-cache.
System Wipe: Formats /cache /system and /data. Recovery mounts INTERNAL SD to /data/media, so THIS DELETES INTERNAL SD!
Please backup your INTERNAL SD before running this or you will lose everything on it!
Cache Nullify: Nullifies /cache and deletes Dalvik-cache.
System Nullify: Nullifies /cache /data /system. THIS DELETES INTERNAL SD!
Cache Wipe\Nullify is meant for cleaning up when things get buggy.
System Wipe is meant to format everything for a new rom install or nandroid backup restore. The recovery will remove directories around /media, not format, this will format /data completely in preparation for new data.
System Nullify is meant to destroy all data in /system /cache /data, including your internal SD, by zeroing out the partitions. In other words, writes 0s from start to end.
Who should we thank?
Volk, who created the initial concept and script Nullifier, which this is based roughly on.
x0hell0x who ported it to the Hellfire Kindle Series, which this is based directly on.
da-pharoah, who helped me through the process and dealing with different device IDs in different recoveries. If it weren't for him I'd have given up and made seperate zips for each recovery.
What's coming up?
Right now I think this is complete! I'm unsure of how it handles CWM, so I may need to create CWM versions.
Things to note! READ THIS!
This is intended to run on the Acer Iconia Tab A100 ONLY! I have not set this up to run on any other device, and doing so may result in a brick! This wipes partitions, and could wipe boot, recovery, or any number of other partitions if run on a different device!
This was created and tested on my personal device using TWRP recovery! Using any other recovery may or may not prevent the script from running correctly! System wipe\nullify erases internal SD please backup data and ensure your ROMs and Nandroids are stored on EXTERNAL SD CARD!
The wipes are meant for every flash, the nullifiers are NOT meant for every flash! They are meant for changes from one ROM to another rom, or every few flashes, say 10. Otherwise use manual wipes or my wipe scripts!
Porting:
I'll consider porting to other devices if I have time, please PM me if interested.
I am not responsible for any damage that may occur from use of this script! If you choose to use this, that is your choice. As with anything else, flashing can cause problems including data loss, hair loss, bricking, brick laying, and magical fairies cracking your screen.
Changelog:
5.25.12 v0.1
Initial attempt at porting over, full of fail.
5.26.12 V1.0
Wipe Cache only version completed and successfully run on my device in CWM and TWRP.
5.27.12 V1.0a
Minor changes to the script for cache only version.
5.28.12 V1.1
More changes, changed handling of device ID from recovery to handle both types of recovery reporting (thanks da-pharoah)
Adjusted the status bar indicator to better reflect where in the operation the script is (thanks da-pharoah)
5.30.12 V1.1a
Created post, minor clean up of spelling errors.
5.30.12 V1.3
System Wipe finished after some major changes to command arguments. Cache wipe getting updated as well to 1.3 with a fix to rm argument.
6.1.12 V1.4
Cleaned up an error with the cache being formatted and throwing errors. Updated and cleaned up Cache Nullifier, all scripts updated to 1.4.
6.1.12 V1.5a
I made a mistake and updated the wrong script versions, resulting in nothing being formatted due to the system not unmounting before carrying on with the script. My apologies, I hadn't noticed the issue until I attempted to use it today for a rom install. For now, use only 1.5a versions, updating them all now with the fix. Slight changes to output to help see what it's saying. Working on getting the status bar timing correct.
6.3.12 V1.5a Final
Rechecked each script, and should ALL now be FULLY working in TWRP. CWM may or may not handle the script correctly, if you run into issues like it not working, send me a PM or Email with /cache/recovery/last_log and if there dmesg. System Nullifier added finally!
Please bear with me, I'm finishing my High School course and only have limited time on any given day, and it mostly goes to schoolwork, I will update when I can, and I really hope to have the full wipe completed within a few days. Nullifier may take longer as I'm not sure why DD hangs.
Downloads: These are on my drop box for now, it's small so it shouldn't cause issues.
Blackhole System Wipe 1.5a A100
Blackhole Cache Wipe 1.5a A100
Blackhole Cache Nullifier 1.5a A100
Blackhole System Nullifier 1.5a A100

does this actually "wipe" data so that is can not be recovered? or just erase it?

joeyjojojjjjjj said:
does this actually "wipe" data so that is can not be recovered? or just erase it?
Click to expand...
Click to collapse
Right now all it does is format, or wipe, with mke2fs to whatever FS that partition uses, EXT4 or EXT3. Its not much different from using CWM wipe/format commands, just does it all for you. Once I figure out why DD hangs, it will then Nullify the partitions, complete and utter destruction of data by overwriting the partitions with 0s, leaving no traces behind at all. I'm currently hammering out the full system wipe script, which will do /cache /system /data and /data/dalvik-cache, the /cache/dalvik is done when /cache is formatted. The problem I ran into is for some strange reason, internal SD is mounted to /data/media in recovery, meaning formatting /data directly will erase the internal SD card as well. The recovery gets around this by deleting directories around it, but never formats it, which IMO can lead to issues and bugs down the line. I have only 1 method of dealing with this, and that's moving /data/media to the external SD card (SDC), formatting (or nullifying) then moving it back. As this can mean moving up to 8 GB, its not a liable method as it will take a LONG time to move it there and back.
I'm hoping to have the first full system wipe available tonight, however it WILL erase the internal SD, this is only to be used if you don't care what's there, or are having alot of bugs, and copy your stuff off before running. I can't test it since the wife is using the tab now, and I'm not gonna put it online without testing it first.
TL;DNR: It just erases it.

Updates
1.4 versions are up.
Now includes Cache only Nullifier! This is the wiping that I think joeyjojojjjjjj was looking for. Unrecoverable data destruction. Currently DDs /cache, then formats and checks, then deletes dalvik-cache. Overwrites the partition with 0s from beginning to end, leaving nothing but ZERO behind, hence blackhole nullifier.
Hoping to finish up System Nullifier tonight some time.

1.5a Final is done
Scripts are now up to 1.5a Final. The zips are still labeled as 1.5a but they are all updated. Added system nullifier! Please use caution with the wipes and nullifiers, and ensure internal SD is backed up and your nandroids and roms are stored on external SD card before using!
Tested working on TWRP Recovery, YMMV on CWM recoveries.

pio_masaki said:
Scripts are now up to 1.5a Final. The zips are still labeled as 1.5a but they are all updated. Added system nullifier! Please use caution with the wipes and nullifiers, and ensure internal SD is backed up and your nandroids and roms are stored on external SD card before using!
Tested working on TWRP Recovery, YMMV on CWM recoveries.
Click to expand...
Click to collapse
So I finally came upon this thread! Well done bro! Great work and keep it up! makes me wish I had an a100 just to test it

da-pharoah said:
So I finally came upon this thread! Well done bro! Great work and keep it up! makes me wish I had an a100 just to test it
Click to expand...
Click to collapse
It works lol it's based on your work after all

pio_masaki said:
It works lol it's based on your work after all
Click to expand...
Click to collapse
Lol I know but still u got it rockin for the a100 so that's what I meant..
Sent from my LG-P999 using xda premium

Wipes with Crossix Memory Swap?
I am using the Crossix memory swap.
If I use the system wipe script, will it erase the data on my *actual* internal sd (i.e the 5gb partition that I largely don't use). Or will it erase the data on my *tricked* internal (my 32gb microsd card)?
Thanks, I can't wait to try this stuff out!

conorkickass said:
I am using the Crossix memory swap.
If I use the system wipe script, will it erase the data on my *actual* internal sd (i.e the 5gb partition that I largely don't use). Or will it erase the data on my *tricked* internal (my 32gb microsd card)?
Thanks, I can't wait to try this stuff out!
Click to expand...
Click to collapse
Internal SD only. It will never touch your external SD card. And the reason is....
The crossix mount swap is only active when android runs from /system. This is run from recovery, so any system mods don't affect anything running in recovery.
So you're safe, only the included internal SD is wiped, regardless of crossix's mount swap.
Tapatalked from my Galaxy S II.

This is sick. Nice work.
Sent from my SGH-I777 using xda premium

could you make a port of the babsector utility ? A lot of bricks can come back to live with i believe
http://forum.xda-developers.com/showthread.php?t=1624645

Presko said:
could you make a port of the babsector utility ? A lot of bricks can come back to live with i believe
http://forum.xda-developers.com/showthread.php?t=1624645
Click to expand...
Click to collapse
This has nothing to do with these tools lol.
Anyways I can port it but its useless without the sbk, so not really a point until Acer releases it.
Sent from my Nexus 7 using Tapatalk 2

Excuse me but after a couple of days reading about this problem , what is sbk ?
What ever it is , I doubt that they are going to release even a windows 8 driver for this tablet
Btw I have contacted the Russian author via 4pda and he says to give a straight shot and to send him a screen shot
Tomorrow at work will have time to try
Is there something specific to put in the start command at prima vista ?

Presko said:
Excuse me but after a couple of days reading about this problem , what is sbk ?
What ever it is , I doubt that they are going to release even a windows 8 driver for this tablet
Click to expand...
Click to collapse
Its the encryption key for the boot loader, specifically to use nvflash in apx mode. Its covered in the brick thread.
Sent from my Galaxy Nexus using Tapatalk 2

pio_masaki said:
Its the encryption key for the boot loader, specifically to use nvflash in apx mode. Its covered in the brick thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
well that's a chance to ps my post while you aswer it
btw is there a petition or something that I can contribute with ?

Presko said:
well that's a chance to ps my post while you aswer it
Click to expand...
Click to collapse
Huh?
Sent from my Galaxy Nexus using Tapatalk 2

pio_masaki said:
Huh?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
not again I will stop editing previous posts

Presko said:
not again I will stop editing previous posts
Click to expand...
Click to collapse
Oh OK I didn't see the edits.
Anything using nvflash or apx mode needs the sbk, no way around it. It may yet be cracked like the a500s, but so far no.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Sd card issue (CM 10)

Hello folks,
Recently I have flashed CM 10 via CWM 6.0.3.2 on my Samsung Galaxy W. (I followed this procedure: http://forum.xda-developers.com/showthread.php?t=1990795)
Everything worked out fine (yay) exept for two issues I have:
1. My SGW doesn't recognize my Sd card (internal) at all. (though internal is mounted in cwm menu)
I have several folders regarding my sd and external sd:
- sdcard> tells me it is "unplugged" (in German> translation might differ) when I enter via file manager
- mnt/sdcard> here it tells me my sd card is unplugged as always
- storage/sdcard0> unplugged
- external_sd> it tells me sd card unplugged if I enter
- mnt/external_sd >here I can enter all of my folders
- storage/sdcard1> here I can enter again
2. My SGW can't mount my external sd anymore. I can clearly enter my external sd's files, but apparently I cannot mount my PC. Especially not with Multimount because it requests me to mount my internal sd (issue 1).
So how do I get it to work properly? - is it possible to do it via Terminal Emulator?
Specifications:
- Samsung Galaxy W
- Android Version 4.1.2.
- Kernel Version: 3.0.80-cyanogenmod-gc689589
[email protected] #1
- Cyanogenmod Version: 10-20130605- UNOFFICIAL-ancora
Thanks a lot in advance

Hi, I have similar issues with internal storage after flashing to 4.2.2 and also 4.1.2. Model is galaxy W previously 2.3.6 stock.
At root, i have
/data, which seems to be my internal storage as the FX file explorer show it has a storage of 1.07gb
/external_sd, which contains my files in micro sd card
/sdcard, which ES say SDCard unmounted
/storage, which contains sdcard0 (SDCard unmounted), sdcard1 (micro sd), usbdisk (SDCard unmounted)
In the andriod settings > storage, I can see internal storage with total space 1.07gb, but unable to mount it.
My camera and gallery says "No external storage available".
What should I do? Please help

Have You Try To Change Your Rom?!

ElGzzar said:
Have You Try To Change Your Rom?!
Click to expand...
Click to collapse
Hi, yes actually i did. I've tried 4.2.2, 4.1.2, then 4.0.4. All gave me the same problem.

lennnostra said:
Hi, yes actually i did. I've tried 4.2.2, 4.1.2, then 4.0.4. All gave me the same problem.
Click to expand...
Click to collapse
Try To Format Your SD On Your PC With FAT32 Mod?!
Then Try 10.1 (4.2.2) Rom
Done :good:

ElGzzar said:
Try To Format Your SD On Your PC With FAT32 Mod?!
Then Try 10.1 (4.2.2) Rom
Done :good:
Click to expand...
Click to collapse
This can be done for the SDcard you can unplug and plug directly to an other device like an PC, but not with the internal.
So better try the following. Secure your files if you can. Reboot into recovery and format there both. Rebooot into CM10 or whatever ROM you are using and change your USB operation mode from MTP to Mass Storage.

honeyx said:
This can be done for the SDcard you can unplug and plug directly to an other device like an PC, but not with the internal.
So better try the following. Secure your files if you can. Reboot into recovery and format there both. Rebooot into CM10 or whatever ROM you are using and change your USB operation mode from MTP to Mass Storage.
Click to expand...
Click to collapse
If The Internal Is The Problem Then You Must Back To The Main Software 2.x.x
Then Back To The Edited Mods And Rom's
The Internal Storage Will Work
...............................
When That Happen To Me ... That What I Have Done
Sorry For Bad English
Over :good:

ElGzzar said:
If The Internal Is The Problem Then You Must Back To The Main Software 2.x.x
Then Back To The Edited Mods And Rom's
The Internal Storage Will Work
...............................
When That Happen To Me ... That What I Have Done
Sorry For Bad English
Over :good:
Click to expand...
Click to collapse
You probably mean back to stock Samsung ROM. But how will this fix corrupted partitions? And why "must" if there are probably more simple ways to fix it rather than flashing roms forth and back?
First of all he should format both and switch to Mass Storage mode to see if this fixes his issue. Flashing ROMs still can be tryied as a last resort.

honeyx said:
You probably mean back to stock Samsung ROM. But how will this fix corrupted partitions? And why "must" if there are probably more simple ways to fix it rather than flashing roms forth and back?
First of all he should format both and switch to Mass Storage mode to see if this fixes his issue. Flashing ROMs still can be tryied as a last resort.
Click to expand...
Click to collapse
Yeah I Mean (back to stock Samsung ROM) And That This Makes The Phone Due To His Condition Also Came From Its Supplier ..
And That's Fix All Internal Storage Problem's .... By Format The Internal Storage With Force From stock Samsung ROM ...
And I Think He Can't access The Internal Storage To Format It By Him Self ...
I Have Tried That Problem Whin I Have Got My Mobile New .. I Haven't Found Solve For It , So I Have Back To The stock Samsung ROM
..
And Found Every Thing Work Fine Then I Have Back To CM Mod Again... :victory:
If You Have Another Simple Way For That Problem Tell Him ,Please ...
Over :good:

ElGzzar said:
Yeah I Mean (back to stock Samsung ROM) And That This Makes The Phone Due To His Condition Also Came From Its Supplier ..
And That's Fix All Internal Storage Problem's .... By Format The Internal Storage With Force From stock Samsung ROM ...
And I Think He Can't access The Internal Storage To Format It By Him Self ...
I Have Tried That Problem Whin I Have Got My Mobile New .. I Haven't Found Solve For It , So I Have Back To The stock Samsung ROM
..
And Found Every Thing Work Fine Then I Have Back To CM Mod Again... :victory:
If You Have Another Simple Way For That Problem Tell Him ,Please ...
Over :good:
Click to expand...
Click to collapse
I think you are mixing something up. First of all he didn´t say he can´t mount / access it from CWM Recovery but from a running ROM. This is two different things so it still should be possible to access both in CWM Recovery and to do a format.
Secound. Flashing a ROM will not format the internal Storage but only the partition where the ROM will be flashed to. They are not the same, so this is also two different things. So even if you flash a ROM but are having corrupted SDcards (Internal and external) they will stay corrupted till you fix this.
And this is why I suggested to first boot into RECOVERY, format both and finally after rebooting change to Mass Storage as the MTP Mode is not always working very well. If this doesn´t help he still can flash back to stock ROM.
However now I´m just repeating what I already said before. If you can´t get it, then I´m sorry for you.

honeyx said:
I think you are mixing something up. First of all he didn´t say he can´t mount / access it from CWM Recovery but from a running ROM. This is two different things so it still should be possible to access both in CWM Recovery and to do a format.
Secound. Flashing a ROM will not format the internal Storage but only the partition where the ROM will be flashed to. They are not the same, so this is also two different things. So even if you flash a ROM but are having corrupted SDcards (Internal and external) they will stay corrupted till you fix this.
And this is why I suggested to first boot into RECOVERY, format both and finally after rebooting change to Mass Storage as the MTP Mode is not always working very well. If this doesn´t help he still can flash back to stock ROM.
However now I´m just repeating what I already said before. If you can´t get it, then I´m sorry for you.
Click to expand...
Click to collapse
Yeah Yeah I See Now Thank's For Teaching Me .. :victory:
And I'm Sorry That is My Missd
Sorry For Bad English ToO ..
Over XD

Thanks
honeyx said:
This can be done for the SDcard you can unplug and plug directly to an other device like an PC, but not with the internal.
So better try the following. Secure your files if you can. Reboot into recovery and format there both. Rebooot into CM10 or whatever ROM you are using and change your USB operation mode from MTP to Mass Storage.
Click to expand...
Click to collapse
Thanks man,
your knowledge regarding this issue immediately solved my problem. My girlfriend's very happy now
Maybe I ll get lucky tonight Just kidding, I get lucky whenever I want
Greetings,
Max

Internal Storage Not Mounting with CM 10.1

Hello all. I did make a post in the 4.2.2 thread regarding issue with CM 10.1 but still wasn't able to find a solution to this issue. My problem is after flashing from 10.0 > 10.1 (stable) it seems that the device is unable to automatically mount the internal storage and crashes. It does open after initial flashing but after rebooting the phone, internal storage goes away. After flashing again and again, the issue still occurs. I have tried reformatting the internal storage but that also seems to not work. If anyone can please help it'd be much appreciated. Thank you

brendyh said:
Hello all. I did make a post in the 4.2.2 thread regarding issue with CM 10.1 but still wasn't able to find a solution to this issue. My problem is after flashing from 10.0 > 10.1 (stable) it seems that the device is unable to automatically mount the internal storage and crashes. It does open after initial flashing but after rebooting the phone, internal storage goes away. After flashing again and again, the issue still occurs. I have tried reformatting the internal storage but that also seems to not work. If anyone can please help it'd be much appreciated. Thank you
Click to expand...
Click to collapse
This thread seems relevant but I tried the script to see if I could tell you what mine is called but got "permission denied".
http://forum.xda-developers.com/showthread.php?t=1854087
T989D
latest CM10.1 nightly
latest Uber nightly

brendyh said:
Hello all. I did make a post in the 4.2.2 thread regarding issue with CM 10.1 but still wasn't able to find a solution to this issue. My problem is after flashing from 10.0 > 10.1 (stable) it seems that the device is unable to automatically mount the internal storage and crashes. It does open after initial flashing but after rebooting the phone, internal storage goes away. After flashing again and again, the issue still occurs. I have tried reformatting the internal storage but that also seems to not work. If anyone can please help it'd be much appreciated. Thank you
Click to expand...
Click to collapse
When you say you're reformatting the internal storage, are you talking about just the "/sdcard" bit (from inside Settings while the phone's running) or full wipe (from CWM or whatever recovery you use)?
There was a known bug a few months back which caused an issue mounting the internal storage (i.e. the "/sdcard" bit) which did get fixed, but some people were saying they still had continued problems from a mount command left behind in "/data/local/userinit.sh". I saw some comments saying deleting this fixed the problem. If you're doing a full wipe (from recovery) before flashing CM, it would get rid of that file anyways.

noob41 said:
This thread seems relevant but I tried the script to see if I could tell you what mine is called but got "permission denied".
http://forum.xda-developers.com/showthread.php?t=1854087
T989D
latest CM10.1 nightly
latest Uber nightly
Click to expand...
Click to collapse
I also was unable to get the script.
GaidinBDJ said:
When you say you're reformatting the internal storage, are you talking about just the "/sdcard" bit (from inside Settings while the phone's running) or full wipe (from CWM or whatever recovery you use)?
There was a known bug a few months back which caused an issue mounting the internal storage (i.e. the "/sdcard" bit) which did get fixed, but some people were saying they still had continued problems from a mount command left behind in "/data/local/userinit.sh". I saw some comments saying deleting this fixed the problem. If you're doing a full wipe (from recovery) before flashing CM, it would get rid of that file anyways.
Click to expand...
Click to collapse
I formatted the internal storage via recovery by mounting the usb storage and formatting from there. I did try to delete the command and doing a full wipe but both did not help. Full wipe allowed the internal storage to be mounted on initial flash but after rebooting, the internal storage disappears.
Edited:
After spending the morning figuring out what went wrong I may have got it to work. For starters, I rebooted and waited 2 minutes before using my phone and found that it worked around 50% of the time for the i.s. to mount. When it failed I put in commands seen from another thread and that also worked roughly 60-75% of the time. I also deleted the actual userinit.sh and it helped along with the previous two actions. It's a hit or miss so far but as of right now, I am able to go into the internal storage.

I can't even get to my internal storage via CWM. Won't mount it, won't format... nothing. Help?
edit - figured it out.

[Q] First time root/custom ROM for this phone - How? Walkthrough guide please?

Can anybody here please help?
A friend of mine has this phone (Wildfire S) and I has become frustrated at the very limited storage for apps.
I have rooted phones previously myself (Xperia X10 and Xperia S) and used custom ROMs on them, but I don't have a clue how to do this on the HTC Wildfire S, OR which custom ROMs are decent. Are the KitKat 4.4 ROMs good/speedy enough for daily use?
If anyone could provide a simple way of rooting and using a custom ROM on this phone which allows more app storage space (such as on the SD card) that would be fantastic!
Many thanks

Sorry for responding to my own post, but I've now successfully unlocked the bootloader and rooted the phone, but I was left confused by some issues that I can't find the answers to:
With my own previous phones, Sony Xperia X10 and Xperia S, I have rooted those and run custom ROMs and kernels. However, when looking for a custom ROM for the Wildfire S, there don't seem to be any kernels. Does this mean I can use any custom ROM, be it Gingerbread 2.3 to KitKat 4.4 with the same CWM Recovery that I have on the phone right now when I rooted it? Are the kernels built in to the ROMs that are downloaded?
Also another question is how do I go about increasing the storage space on the phone now that I have rooted (be it on either the stock ROM or a Custom ROM)? My friend has a 2GB MicroSD card in the phone. If I was to install a KitKat ROM for example, how could I make sure the apps could be installed and run from the SD Card? What's an easy way to allocate a portion of the 2GB for apps??
Finally, which ROM would you recommend trying on the phone rather than the stock ROM, which is not sluggish but also very functional?
So basically to sum up:
Do I need to flash kernels to use custom ROMs?
How do I increase the storage size so that many more apps can be installed?
What is a nice, fast custom ROM that you would recommend?
I'd appreciate any information to help me on this one. Like I said, with my own personal phones, which have always been Sonys, I've got used to the rooting methods on those, but I had a lot of questions with this phone so would be grateful if somebody could help get this phone to a more functional standard.
Thanks

alex_ncfc said:
Do I need to flash kernels to use custom ROMs?
How do I increase the storage size so that many more apps can be installed?
What is a nice, fast custom ROM that you would recommend?
Thanks
Click to expand...
Click to collapse
No you don't need to flash any kernels if you don't want to.
Use int2ext or Link2SD. Search about them.
The answer to the last question depends on your needs and you will have to try a bit yourself. You can start with CM10.

Thanks very much for the response aWFSuser.
1) Thanks, that's one thing I don't need to worry about then! (although, just thought, it might be nice to OverClock the CPU to 800Mhz - can I do this as standard or will I need another Kernel?)
2) I will have a read up about these, although from your experience, of the two tools you have listed, which would you say is easiest to configure? I've read before about setting up partitions on the SD card for extra app storage, but have never had to do it on my own phones
3) I will have a look around! Tempted to try some of the KitKat ROMs that I can see for download on the Development thread. If I don't have to mess around with flashing kernels, it's quite good to know that I can have many custom ROM zips on the SD card and install them without having to worry about hooking it up to the USB to flash a kernel.
Thanks again, hoping I can get some joy with this. My friend's absolute main needs with this phone is extra storage for apps - he is constantly getting "Not enough storage" errors, but I looked in his Google Play "installed list" and there was only 4 or 5 apps installed, and they were small ones!!

alex_ncfc said:
Thanks very much for the response aWFSuser.
1) Thanks, that's one thing I don't need to worry about then! (although, just thought, it might be nice to OverClock the CPU to 800Mhz - can I do this as standard or will I need another Kernel?)
2) I will have a read up about these, although from your experience, of the two tools you have listed, which would you say is easiest to configure? I've read before about setting up partitions on the SD card for extra app storage, but have never had to do it on my own phones
3) I will have a look around! Tempted to try some of the KitKat ROMs that I can see for download on the Development thread. If I don't have to mess around with flashing kernels, it's quite good to know that I can have many custom ROM zips on the SD card and install them without having to worry about hooking it up to the USB to flash a kernel.
Thanks again, hoping I can get some joy with this. My friend's absolute main needs with this phone is extra storage for apps - he is constantly getting "Not enough storage" errors, but I looked in his Google Play "installed list" and there was only 4 or 5 apps installed, and they were small ones!!
Click to expand...
Click to collapse
Every ROM comes with its own kernel and most of them are overclockable. But overclocking to 800 MHz will not be a good idea if you don't want random reboots. Overclocking upto 768MHz is probably fine.
Int2ext is a script and you can flash it and forget. But Link2SD is an app which has an interface. Though it requires more configuring, it gives control on what to move and not to move and also it works in every rom I tried. I personally use Link2SD.

aWFSuser said:
Every ROM comes with its own kernel and most of them are overclockable. But overclocking to 800 MHz will not be a good idea if you don't want random reboots. Overclocking upto 768MHz is probably fine.
Int2ext is a script and you can flash it and forget. But Link2SD is an app which has an interface. Though it requires more configuring, it gives control on what to move and not to move and also it works in every rom I tried. I personally use Link2SD.
Click to expand...
Click to collapse
Perfect.
Thanks for that information. Good to know that I shouldn't overclock to the "max" 800mhz!
Also, after reading around guides on flashing the ROMs, it seems I will still have to use the USB cable in order to flash each ROMs "boot.img" file, but that's not a major problem.
I will have a look at Link2SD. Is it something you do after you have installed and configured a ROM?
Thanks very much for your advice and informative replies :good:

alex_ncfc said:
Perfect.
Thanks for that information. Good to know that I shouldn't overclock to the "max" 800mhz!
Also, after reading around guides on flashing the ROMs, it seems I will still have to use the USB cable in order to flash each ROMs "boot.img" file, but that's not a major problem.
I will have a look at Link2SD. Is it something you do after you have installed and configured a ROM?
Thanks very much for your advice and informative replies :good:
Click to expand...
Click to collapse
No, you don't have to flash the boot.img files. They are inside the ROM zips that you will download. You will just need to flash the rom via recovery (ofcourse after wiping).
Link2SD is just an application, you can install it any time but you still have to partition your memory card.

aWFSuser said:
No, you don't have to flash the boot.img files. They are inside the ROM zips that you will download. You will just need to flash the rom via recovery (ofcourse after wiping).
Link2SD is just an application, you can install it any time but you still have to partition your memory card.
Click to expand...
Click to collapse
Thanks for the heads-up, I have since figured out I do not need to flash boot.img.
Am I able to use the 2GB card with INT2EXT? I can't quite figure out how to set up a partition.
Thank you

alex_ncfc said:
Thanks for the heads-up, I have since figured out I do not need to flash boot.img.
Am I able to use the 2GB card with INT2EXT? I can't quite figure out how to set up a partition.
Thank you
Click to expand...
Click to collapse
Format the 2GB card into two partitions. The first one should be FAT32 and the 2nd one ext2. Then flash the int2ext script right after flashing the rom.

aWFSuser said:
Format the 2GB card into two partitions. The first one should be FAT32 and the 2nd one ext2. Then flash the int2ext script right after flashing the rom.
Click to expand...
Click to collapse
Thanks - I have just formatted the SD card in CWM Recovery, as I don't have a MicroSD reader in order to format on my PC. Will this format it correctly so that FAT32 is the first partition and the second EXT2?
Many thanks

aWFSuser said:
Format the 2GB card into two partitions. The first one should be FAT32 and the 2nd one ext2. Then flash the int2ext script right after flashing the rom.
Click to expand...
Click to collapse
I must be doing something wrong, but not sure what!!
I have partitioned the SD card using multiple different CWM recoveries and formatted the SD-EXT partition. However, whenever I flash any INT2EXT through CWM Recovery, the ROM I am using is always messed up. One ROM I try for example, after a long bootup, just has endless FCs, starting with .com.android.phone.
If I don't flash INT2EXT, it works but obviously I have very little storage.
Don't know where I am going wrong on this one. Any ideas?

alex_ncfc said:
I must be doing something wrong, but not sure what!!
I have partitioned the SD card using multiple different CWM recoveries and formatted the SD-EXT partition. However, whenever I flash any INT2EXT through CWM Recovery, the ROM I am using is always messed up. One ROM I try for example, after a long bootup, just has endless FCs, starting with .com.android.phone.
If I don't flash INT2EXT, it works but obviously I have very little storage.
Don't know where I am going wrong on this one. Any ideas?
Click to expand...
Click to collapse
Are you sure you have really two partitions on the sd-card? I have never partitioned through cwm so don't know the exact procedure. You can mount the sdcard to computer via the usb cable. BTW you have to flash the script right after flashing rom. And have you tried link2sd?

aWFSuser said:
Are you sure you have really two partitions on the sd-card? I have never partitioned through cwm so don't know the exact procedure. You can mount the sdcard to computer via the usb cable. BTW you have to flash the script right after flashing rom. And have you tried link2sd?
Click to expand...
Click to collapse
I am as sure as I can be that I have two partitions, because when I mount the USB storage so I can access it in Windows, the partition size is much smaller (i.e - if I create a 512MB EXT partition through CWM, Windows shows the 2GB capacity as 1.4-ish GB) However, CWM doesn't give me any indication on which type of EXT partition I am creating. I would like to create an EXT4 one, but it doesn't seem to give me the option. I can't seem to be able to see the partitions in Windows when I mount the USB storage either. I just see the FAT32 partition in Windows Disk Management.
As another update, I tried Link2SD instead of INT2EXT this morning. It picked up the fact I have another partition, but it asks me which type it is (EXT2, EXT3, etc) and as I do not know, I may be picking the wrong options. Anyway I think I managed to get apps installed into the EXT partition, but in Android's storage settings, it still shows 150MB internal storage - is this correct? When I see screenshots of others using tools like INT2EXT or Link2SD, their Storage settings seems to show the new storage size. So maybe it isn't working? Also, when I tried to install the Facebook app, although the app installed (and Link2SD said it was on the SD card) when I tried to start the app and it reads "Setting up Facebook", the system runs out of storage.
Thanks for all your help so far

alex_ncfc said:
I am as sure as I can be that I have two partitions, because when I mount the USB storage so I can access it in Windows, the partition size is much smaller (i.e - if I create a 512MB EXT partition through CWM, Windows shows the 2GB capacity as 1.4-ish GB) However, CWM doesn't give me any indication on which type of EXT partition I am creating. I would like to create an EXT4 one, but it doesn't seem to give me the option. I can't seem to be able to see the partitions in Windows when I mount the USB storage either. I just see the FAT32 partition in Windows Disk Management.
As another update, I tried Link2SD instead of INT2EXT this morning. It picked up the fact I have another partition, but it asks me which type it is (EXT2, EXT3, etc) and as I do not know, I may be picking the wrong options. Anyway I think I managed to get apps installed into the EXT partition, but in Android's storage settings, it still shows 150MB internal storage - is this correct? When I see screenshots of others using tools like INT2EXT or Link2SD, their Storage settings seems to show the new storage size. So maybe it isn't working? Also, when I tried to install the Facebook app, although the app installed (and Link2SD said it was on the SD card) when I tried to start the app and it reads "Setting up Facebook", the system runs out of storage.
Thanks for all your help so far
Click to expand...
Click to collapse
Link2SD would not show the internal memory as increased, you can see that from the app itself (menu->storage info). You can enable auto-linking in settings. By the way if the app is on sdcard, then its not on the 2nd partition. To move it to the 2nd partition you have to link it. Make sure to link apk,dex and lib. If you have paid version then you can also link data. As for facebook, I have not used it in a while but it may have large amount of dex files that have to be linked. Also the data may be large. And remember to reboot if storage space runs out.
Also which rom are you on?

aWFSuser said:
Link2SD would not show the internal memory as increased, you can see that from the app itself (menu->storage info). You can enable auto-linking in settings. By the way if the app is on sdcard, then its not on the 2nd partition. To move it to the 2nd partition you have to link it. Make sure to link apk,dex and lib. If you have paid version then you can also link data. As for facebook, I have not used it in a while but it may have large amount of dex files that have to be linked. Also the data may be large. And remember to reboot if storage space runs out.
Also which rom are you on?
Click to expand...
Click to collapse
Thanks to your post two posts earlier, I think I have cracked the storage thing
When it wasn't working previously, like I said, I had been doing the partitioning in CWM.
However, I managed to get the system mounted under Windows so that I could do the partitioning in Mini Partition Wizard as many recommend. Now when I install a ROM and then install Int2Ext4 straight after, the extra storage shows up in settings once the ROM is booted
ROM-wise, I have just been messing around with any I can get my hands on from the development thread, to see if I could get the storage problem sorted first and foremost, as this is the most important part for me (well, for my friend!) However, is there a favourite ROM of yours you'd recommend? I've tried so many over the last 2 days that I'm forgetting which does what! I tried a KK ROM which I thought was very slow, but also I tried an OWL 2013 ROM which was performing very well - but there is no keyboard! And I can't seem to be able to install one. If there's one you could recommend which is quite speedy, that'd be great
Thanks

alex_ncfc said:
Thanks to your post two posts earlier, I think I have cracked the storage thing
When it wasn't working previously, like I said, I had been doing the partitioning in CWM.
However, I managed to get the system mounted under Windows so that I could do the partitioning in Mini Partition Wizard as many recommend. Now when I install a ROM and then install Int2Ext4 straight after, the extra storage shows up in settings once the ROM is booted
ROM-wise, I have just been messing around with any I can get my hands on from the development thread, to see if I could get the storage problem sorted first and foremost, as this is the most important part for me (well, for my friend!) However, is there a favourite ROM of yours you'd recommend? I've tried so many over the last 2 days that I'm forgetting which does what! I tried a KK ROM which I thought was very slow, but also I tried an OWL 2013 ROM which was performing very well - but there is no keyboard! And I can't seem to be able to install one. If there's one you could recommend which is quite speedy, that'd be great
Thanks
Click to expand...
Click to collapse
CM10.1 (probably owl that you mention) is good. Keyboard is probably with Gapps and you need to install it. Anyway I usually use Touchpal Keyboard which works great. KK is slow but CM10 and CM10.1 are good. For best speed use gingerbread based roms.

aWFSuser said:
CM10.1 (probably owl that you mention) is good. Keyboard is probably with Gapps and you need to install it. Anyway I usually use Touchpal Keyboard which works great. KK is slow but CM10 and CM10.1 are good. For best speed use gingerbread based roms.
Click to expand...
Click to collapse
Yes I agree, the OWL has been my stable ROM for almost 2 years.. Now I am moving towards the latest CM, the Olivier's one.. Give it a look!

Thanks for the responses guys.
Which Android version/CM is Olivier's latest based on? Have you got a link to the thread?
I agree that GB ROMs will be best for speed, but I've tried a few based on JellyBean 4.2.2 and they seem very quick, I am actually shocked (for a phone with such a low processor speed etc, it runs these modern ROMs so much better than my old Sony Xperia X10)
However, one thing I notice is, despite installing GAPPS on any of the JB/KK ROMs, there are certain Google Apps missing, and I can't install them from the market either. For example, Google Search - when I look for it in the market, it says that the app is not compatible with the Android version I am running. However, I know for sure that Google Search runs on any Android version. It let me download the new Google Now Launcher, but I can't run it because it needs Google Search installed, but I can't install it from the market.

alex_ncfc said:
Thanks for the responses guys.
Which Android version/CM is Olivier's latest based on? Have you got a link to the thread?
I agree that GB ROMs will be best for speed, but I've tried a few based on JellyBean 4.2.2 and they seem very quick, I am actually shocked (for a phone with such a low processor speed etc, it runs these modern ROMs so much better than my old Sony Xperia X10)
However, one thing I notice is, despite installing GAPPS on any of the JB/KK ROMs, there are certain Google Apps missing, and I can't install them from the market either. For example, Google Search - when I look for it in the market, it says that the app is not compatible with the Android version I am running. However, I know for sure that Google Search runs on any Android version. It let me download the new Google Now Launcher, but I can't run it because it needs Google Search installed, but I can't install it from the market.
Click to expand...
Click to collapse
Current Google Search has official support for only armv7 devices, but our phone's processor is armv6. You can still download the apk and install but voice recognition will not work.
By olivier's latest he probably meant CM11 that you used earlier but it is slower tham 4.2.2 roms.