yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] jseivers:
While trying to play around and learn Android, I ran a "partition sd card" via SafeStrap. I was thinking I could create a 4gb partition and use it to test ROM's. After I partitioned, I noticed that it appears all data that was on the SD card is gone. Every picture that I ever took of my lovely 4 year old twin daughters is now completely MIA. Have I totally blown them away or is there anyway I can get them back ? I had a 16gb SD card and after I did the partition, I only show a little over 10gb total space of the card.

Please help if you can.

Thanks,
[General Questions and Answers] songokuj5:
You can try recovery softwares like undelete 360.
[General Questions and Answers] a.cid:
No you won't be able to recover them...

Same had happened to me back in the days...

That's why there is a warning that you back up your sd data before you proceed..

Typed using a small touchscreen
[Continuum General] angryuserwhosephonehates.:
Is it possible to use my same number but on a different phone without upgrading or going through verizon?

Like can I use a Droid X2(for ex.) instead of my continuum if I have one with me?

Hope you understand my question,

Angryuser...
[Continuum General] angryuserwhosephonehates.:
so basically activate my number onto the other phone.
[Continuum General] DJMaj07:
When you say without going through verizon, do you mean not having to physically go to a verizon store or literally avoid any method involving verizon?

I ask because I know you can use MyVerizon online to activate a phone and transfer an existing line onto it. Pretty painless.
[Captivate Android Development] azunino:
* reserved *
[Captivate Android Development] JKelley103:
Thank you!!
[Captivate Android Development] visionlogic:
Perhaps this would be of some help?:

HOWTO: Unpack, Edit, and Re-Pack Boot Images
[Captivate Android Development] azunino:
Thanks, but I've tried that. It seems SGS devices use a slightly different format. I'll keep reading about it until I find a way to unpack/repack the images.
[Captivate Android Development] Fishmanzero:
I saw "Other kernel will not work" so it seems that you have compiled a modified kernel to change the mount points ? If so I think it's also very promising to be a solution to build a CM to use with broken internal storage...

I'm using stock-based roms with modified kernels but I couldn't manage to repack a working CM compatible kernel...
[Captivate Android Development] azunino:
That is correct. I modified the files that contain the mount points and the updater.sh. The problem with these files is that they are packed together in a ramdisk (ext2 filesystem image), recovery and with the kernel in a boot.img file. Therefore, it is not trivial to modify them to work with any kernel/ICS ROM.

Yesterday, after hours of reading hexadecimal boot.img files... I wrote a python script to unpack a boot.img file and extract from it the kernel, ramdisk and recovery ramdisk. These ramdisks are easy to modify (cpio format), so right now I'm testing a shell script that takes as input any ICS based ROM (or kernel) and modifies it to use /data as my modded CM9. In other words, things are getting interesting ;-)

Once I finish the script It would be very easy to change mount points as you wish because they will be no longer hardwired in each ROM/kernel. So... let your imagination fly.
[Captivate Android Development] azunino:
Updated OP. Now I can automatically convert CM9 and AOKP to use /data on the external SD.

I'm extending the script to handle kernel updates. BTW, some of them seem to use a different boot.img format.
[Captivate Android Development] manolis:
but we can not automatically convert CM9 and AOP to use / data on the external SD. instruction will be for us?
[Captivate Android Development] azunino:
I will post the scripts, but first I have to make them more user friendly and add some error handling code
[Captivate Android Development] manolis:
I wait impatiently, when will it be?
[Captivate Android Development] swayjd:
Just to clarify, to those that used this trick in the past (other phones) and got the encryption unsuccessful bug, what happened was, their external sd card got unusable by the phone, but formatting it with a card reader was all it took to bring it back.

I expect that a good look at these corrupt sd cards would bring good insight to solve the problem.
[Captivate Android Development] azunino:
during the weekend
[Captivate Android Development] TorqueWrench001:
nice :eek:
[Captivate Android Development] azunino:
Updated to the CM9 nightly that has some important fixes (WiFi, location)
[Captivate Android Development] manolis:
Thank you, you good man!
[Captivate Android Development] takeoutttt:
Question, if I use this and want to revert back, will I able to return to kk4 stock?
[Captivate Android Development] azunino:
Yes. You can revert to any ROM.
[Captivate Android Development] manolis:
When will the new NIGHTLY?

ROM and this can be done to install from external SD http://xdaforums.com/showthread.php?t=1625619
[Captivate Android Development] azunino:
The link to the cm9 nightly is in the first post.
[Captivate Android Development] azunino:
New Kernel Available

Uploaded a modified Devil3 kernel (download link available in the OP)
[Captivate Android Development] manolis:
day off, waiting for the script;)
[Captivate Android Development] azunino:
Here is the script (for Linux only):

https://docs.google.com/open?id=0B6FUCnJ94qQjV1I2a3p1SmNvMUk

convert2extsd.py takes as only argument a ZIP ICS ROM file (tested with CM9) and outputs the modified CWM flashable ROM on the directory ./dataExtSD/. It only works on Linux because the script relies on a tool for making kernel ramdisks (included in the tool/ directory) that is a part of the CM9 source tree. Besides, I do not have Windows on any of my computers.

The script is only for advanced flashers. It may soft brick your phone. Yo have been warned.

The script does the following:

- patches boot.img (ramdisk and ramdisk recovery)

- patches updater.sh and updater-script

- applies the reverse emmc/sdcard patch to vold.fstab

The script only supports CM9-like boot.img kernels (ramdisk and recovery ramdisk) such as CM9 and Glitch. On the other hand, kernels such as Devil, Semaphore and Slim, require minor source code modifications and recompilation so they are not supported.

--

IF I HAVE HELPED YOU IN ANY WAY, PLEASE THANK ME or DONATE: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=AQF82UCZ9AF6L
[Captivate Android Development] azunino:
AOKP b40 added to the OP
[Captivate Android Development] loserskater:
Both links (CM9 and AOKP) are dead.
[Captivate Android Development] azunino:
both work here using chrome (on a PC). Anyway, I'm uploading them to zippyshare
[Captivate Android Development] azunino:
OP updated with the latest CM9
[Captivate Android Development] cas0404:
thx for your work :)
[Captivate Android Development] azunino:
OP updated. Added Semaphore Kernel. Thanks stratosk!
[Captivate Android Development] azunino:
OP Updated with Devil Kernel 0.92
[Captivate Android Development] cas0404:
Hi, if i wanna use Devil Kernel, i just have to flash it? And i wont lost the /data link?
[Captivate Android Development] azunino:
Right. I modified it to use /data on the external sdcard. You won't lose anything. In fact I'm using it right now after Semaphore, Devil0.79, and CM9 stock without wiping.

BTW, CM9 updated.
[Captivate Android Development] azunino:
For ROM flashing addicts only

More super quick&dirty shell scripting... and the result is a script that fetches the latest CM9 nightly, patches it and uploads the patched rom (/data on ext sd and inverted emmc/sdcard) to my Dropbox account.

The link in the OP to CM9 points to a shared Dropbox folder with the most recent CM9 patched ROM.

It will be updated daily.

--

IF I HAVE HELPED YOU IN ANY WAY, PLEASE THANK ME or DONATE: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=AQF82UCZ9AF6L
[Captivate Android Development] cas0404:
hi, i saw that in dropbox is the file cm-9-20120707-NIGHTLY-captivatemtd.zip.md5 but there is not the rom, are you gonna update to cm-9-20120707?
[Captivate Android Development] azunino:
uploading right now. 5 minutes left. BTW, I've already flashed it and works great. Since mid week I've noticed a significant increase on battery life on CM9 (almost 2 days with medium usage)
[Captivate Android Development] manolis:
on which kernel to?
[Captivate Android Development] cas0404:
Hi, Just other question why in the kernel section says Devil3_092 but in the kernel thread says Devil3_079?

thx a lot.
[Captivate Android Development] azunino:
Default CM9
[Captivate Android Development] azunino:
Because the OP of devil kernel has not been updated. Anyway the default cm9 kernel works great
[Captivate Android Development] cas0404:
im so sad i couldn't install this ICS because when i try i get error like:

assert failed: getprop("ro.product.device)........ etc

what to do?

Pd: im on stock JW6 rom and recovery CWM v5.0.2.7
[Captivate Android Development] azunino:
Flash cm7.2 first and let it fully boot once before flashing this rom
[Captivate Android Development] cas0404:
thx for your help, but, i need more info plz, im downloading CM 7.2 like you said, but in the CM 7.2 thread says that i have to be on froyo Bootloaders before install it:

"Make sure you're running a Eclair/Froyo Firmware (2.1 or 2.2) and Eclair/Froyo Bootloaders!"

and in your thread says the following:

Now follow these steps:

1) Ensure you are on GB Bootloaders and you have a recent CWM recovery (tested with CM7)

so i dont know what to do... can i flash CM7.2 with GB Bootloaders?

thx again
[Captivate Android Development] visionlogic:
I finally got around to doing what is necessary to install azunino's modded CM9 in the last hour.

FYI, I was on a GB KK4 rom, with GB bootloaders. I downloaded CM7.2, placed it on my internal SD, and flashed without a problem. Then from CM7.2's recovery I flashed the modded CM9 and then gapps, following the instructions in the OP. All went smoothly
[Captivate Android Development] mechanical tool:
Yes, you can install CM 7 with GB bootloaders.

Additionally, I had this problem and had to install a captivate rom, reboot and then install CM7 to avoid the message.

---------- Post added at 07:14 PM ---------- Previous post was at 07:04 PM ----------

I have just installed this with the latest CM9 nightly, after cautiously staying away from ICS due to the EU bug. So far it seems good, the instructions were easy to follow, thanks.

I have kept fairly up to date on the issue, and the most likely cause seems to me to be the firmware/driver bug. If this is the cause, I would think that mounting the internal SD at all could cause the problem. If it is only mounted once (as the external) and then disabled (as this mod allows), it makes the risk very small.

Would it make more sense to remove the code that mounts the internal SD?

If the problem is the firmware/driver, it does not matter if it is mounted as /data but mounting it at all is a risk.

Anyways thanks for your work, it is running well on an Adata UHS-I 16GB card.
[Captivate Android Development] azunino:
I agree. Not mounting the internal SD might be the way to go to avoid any risk. However, all "user level" mods I've tried resulted in bootloops. DerTeufel1980, developer of the Devil kernel, has recently added a compilation flag for reversing int sd and ext sd, so I'll be compiling and testing it as soon as I have some free time.
[Captivate Android Development] azunino:
MIUI and AOKP m6

Hi,

I need testers for two patched ROMs: MIUIv4 2.7.6 (from miui.us) and AOKP m6.
[Captivate Android Development] manolis:
plz,update NIGHTLY!Thanks!
[Captivate Android Development] azunino:
Its updated till 20120709 (yesterday nightly). I'll upload todays nightly when I get home.

In the meantime you can test miui/aopk if you need to flash something

thanks
[Captivate Android Development] manolis:
ok!how to download?
[Captivate Android Development] sepherian:
Xda-DEVELOPERS, he can update this when he wants. And you can wait the extra day if he doesn't do it tonight. Unless you donated something to him, he does it for free on his own time, this is a development forum, Not a I-want-it-now forum... He doesn't need to do it nightly for you, he does it cause its a fun hobby for him and others.

Its not xda-users for a reason.

Read the OP. *sigh* some people...
[Captivate Android Development] manolis:
I asked, but did not make: (
[Captivate Android Development] cas0404:
Hi, i finally install CM9 :) so happy, but I'm realizing that CM9 has screen flickering, i heard that AOKP dosen't have this bug...
[Captivate Android Development] azunino:
Hi, I don't see any flickering. You cal also try AOKP b40 from the OP or AOKP m6: http://www17.zippyshare.com/v/54671573/file.html
[Captivate Android Development] azunino:
CM9 updated. gonna need a faster internet connection...
[Captivate Android Development] azunino:
OP updated: Devil Kernel (0.98.3)
[Captivate Android Development] :
Trying AOKP B6 on a MicroSD class 2 right now. Will report back.
[Captivate Android Development] anishz:
I flashed this in excitement and got the encryption unsuccessful screen.

It wasn't scary as it has happened to me numerous times. I then tried again from stock to find if it was something i did wrong before but i again got the encryption unsuccessful screen. Again this may be specific to my device as azunino has apparently flashed without problems.

I am in no way blaming or scaring anyone, just a fair word of caution.
[Captivate Android Development] :
The encryption should be on your external SD though, did you format it and try again? If you had this installed it shouldn't have been on your internal as the mount points are switched.

EDIT: Same thing happened just now. Got the encryption bug using your AOKP build, probably me screwing up. Anyways, flashed to stock using Apex's heimdall package. Everything is accesible and working fine. Probably just stay on GB to be safe.
[Captivate Android Development] anishz:
I was on CM9 when i flashed the miuiv4 from the link posted and got the bug, but i have been on other ICS roms and haven't faced the issue till now.

I tried it 2 times so for my device the build of miui posted is the culprit. I just pulled the battery and flashed back to stock, am on CM9 again and everything is fine as before.

I will be going back to MPD or Legend.
[Captivate Android Development] azunino:
My patches do not avoid the EU screen, as I said in the EU thread when I proposed this workaround, they just aim at avoiding frying the internal SD. In fact the EU screen in this case may indicate a problem with /data on the external SD, which is completely harmless and easily fixable. Format the external SD and try again. I'm on MIUI right now and works great.

Btw, my patched ROMs have not been tested from stock, but from cm7 as the OP says.
[Captivate Android Development] anishz:
Thanks for replying.But as i said before, not blaming you at all. Just wanted to caution, the miui still doesn't work for me, tried it from CM7, CM9 but same thing happens, so i guess its my device.

All good, Cheers.
[Captivate Android Development] azunino:
Yes, don't worry. All cool.

All the info we can get about how you got the EU screen may help, so if you did something differently, or the SD card has bad blocks, or the software you used to partition the SD, etc. Anything may help to at least learn more about the EU problem. I really hate not knowing the real cause of the broken SD cards. Call it professional curiosity, because since I'm a scientist, once I start working on a problem I do not stop until it is solved. For the sake of my sanity I won't be so stubborn with this bug... I hope...

For example, I got the EU screen several times when I was modifying kernels (Devil and Semaphore). In all cases the problem was that Android was not able to use /data, because in my case, I was not mounting the partitions correctly. There was no encryption at all. I was able to artificially generate the EU screen by writing zeros to several blocks of the /data partition on the external SD. In other words as soon as Android has problems mounting /data, the EU screen appears. As I suspected the EU screen is just a symptom.

I'm not saying "don't worry if you see the EU screen", because we all know the consequences it has had. However, in this mod, the most likely cause for the EU screen is a problem mounting the external SD /data partition. The causes for this can be many: wrong partitions, bad partition scheme (depends on the software used for partitioning), bad blocks, etc, but it has nothing to do with encryption.
[Captivate Android Development] anishz:
I wasn't changing kernels. i was changing roms when the bug happened. Also it happens only when i change to the specific Miui build posted. Hasn't happened after that.

I already flashed CM9, Aokp and gummy to try and replicate the problem but everything works and when i flashed the Miui again, i got the bug again.

So my guess is there is something in the rom that is causing this bug on my device.

My device is 1007 built, also i wiped everytime i changed roms.
[Captivate Android Development] anishz:
Ok, now i downloaded the Miui.us version of 2.7.6 rom. It is named wrong, but it is the 170 mb file.

And it worked fine, i am using it now and everything works. Will flash the miui version posted here (few posts back) now and report back.

EDIT: Same thing, again got the bug. Now i am sure when i say that the miui rom posted here is doing the encryption bug on my device.

Not your fault at all, just confirming for others with 1007 built device to take caution. We users are totally responsible for our devices and not developers or porters.
[Captivate Android Development] azunino:
Thanks for reporting. The miui rom has been working fine in at least 5 phones and is my current ROM, but with one significant difference: I am using devil kernel. Anyway, I've removed it.

Thanks again for testing it.
[Captivate Android Development] :
Alright, one last try before I go get a new Class 10 card instead of this class 2. It's CM9 time since AOKP was being weird.

EDIT: It works. Can I flash Semaphore 1.2.6c or do I need it modded?
[Captivate Android Development] azunino:
Great! No, you need it modded. I've been using devil with good results. The default CM9 is super stable.

BTW, if you are planning on buying a micro sd, take a look at this: http://xdaforums.com/showthread.php?p=12964262
[Captivate Android Development] :
Yep, it's working fine. My class 2 sandisk has no lag whatsoever, well on normal use (no games or anything). I might go with a class 10 sandisk.

Also this is probably placebo but it feels smoother than my usual setup...
[Captivate Android Development] :
Can I have access to the script?
[Captivate Android Development] azunino:
Yes. Remember: only for linux (tested on ubuntu 12.04)

BTW: it you're thinking on patching JB, it won't work. It is necessary to modify and recompile Devil kernel. I'll do it when I have some free time.
[Captivate Android Development] :
Alright thanks. Any idea if this will work on CM10 or no?
[Captivate Android Development] azunino:
I read your mind ;)

See my previous post (which I edited while you were replying)
[Captivate Android Development] :
Dang, you did! No rush, when you do that, I will be the happiest person ever.

I just installed CM9 coming from CM10. It booted with the switched mount points on the first flash. No bootloop or anything. Might have something to do with the new devil kernel?
[Captivate Android Development] azunino:
Updated Devil Kernel (1.0.0-rc3)

Working fine on CM9
[Captivate Android Development] :
Thanks! Maybe I'll install ubuntu and try using your script for CM10.
[Captivate Android Development] azunino:
Hi, uploading right now: https://www.dropbox.com/sh/8oc9we4xip1q0r4/Jo1_k8LF1m

It's untested because I'm super happy with cm9, so please be careful.

take care
[Captivate Android Development] manolis:
installed on top of the CM 9, then splash kernel will not turn on.

instructions can be how to properly install
[Captivate Android Development] azunino:
Same as cm10. Note that is not even an alpha... that's why I'm still on cm9
[Captivate Android Development] azunino:
Updated Semaphore Kernel (1.2.6)
[Captivate Android Development] 11sword11:
After installing the Semaphore Kernel (1.2.6), when the system starts, reboot occurs in the cwm. The system will not start.

At least someone is the kernel work?
[Captivate Android Development] azunino:
I'm using it right now:
[Captivate Android Development] 11sword11:
Flashed through the stock odin, after sm7.2, then stitch the latest nightly build cm9 and after the semaphore of the cap threads, the system restarts when you start to cwm

When I try to flash again cm9 from cwm semaphore kernel, get the message "Installation aborted" (status 7)

Suggested that the file is damaged during the download, downloaded again, but nothing has changed, the kernel does not work.

In the end, set the kernel Devil, with the phone for at least works. Do without Semaphore Kernel ((
[Captivate Android Development] azunino:
You should use the kernels of this thread (you said the cap threads so I assume you flashed the non patched kernel?).

Do this: flash CM9, flash gapps, reboot, wait 5mins, reboot, wait 5mins, reboot to cwm, flash semaphore, reboot

BTW, the kernel does work. See the screenshot several posts above.
[Captivate Android Development] 11sword11:
After installation, I downloaded sm9 system, then restarted in cwm, flash gapps again loaded the system and after reboot and flash the kernel.

In fact everything is correct there is no doubt, but the kernel does not work anyway
[Captivate Android Development] azunino:
ok, I'm removing it
[Captivate Android Development] 11sword11:
Perhaps the file was corrupted during upload to the server dropbox. Or by mistake uploaded another file.

It was necessary, to check the checksums, but if you're offended ... so be it
[Captivate Android Development] azunino:
No, I'm cool. Don't worry. Thanks for the feedback.

Bugs in software do exist, and in this particular case considering there are patches over hacks, mods, ported drivers, backported code, etc, nasty bugs are very likely.

I think the safest choice we have here is to use CM9 with the stock kernel, because it can be modded without recompiling the kernel. The problem with the other kernels is that there are many variables such as ARM compiler version, linux OS, configuration options, ramdisks, etc etc etc, so it is very difficult to reproduce the same exact compilation conditions the developers use (and change very often).
[Captivate Android Development] Thunder22:
Rc3 devil.1.0 kernel doesnt work for me either. devil 3 .99 is where its at hasnt stopped working. Jumpimg on the computer to upload to azunino.
[Captivate Android Development] visionlogic:
+1 Absolutely :good:
[Captivate Android Development] azunino:
OP updated. CM9 rc2. Tested and running fine on 5 phones.
[Captivate Android Development] :
Can you please at least link me to devil kernel rc, the stock kernel is too slow for gaming, and it worked perfectly for me with no issues.
[Captivate Android Development] azunino:
The one I use (1rc3):

https://www.dropbox.com/s/dqhp244cg77k11r/Devil3_1.0.0-Rc3_cappy_CFS_BLN_CMC_20120716.zip

This one was compiled by Thunder22 (0.99), so thank him:

https://www.dropbox.com/s/75mm90lzpv073dw/Devil3.0.99.cappy.dataswap.20120708.zip
[Captivate Android Development] Thunder22:
All credits for devil3 .99 goto derteufel1980. Thanks again for sending it to me.
[Captivate Android Development] mechanical tool:
I have been running CM9 nightly 20120707 for a few weeks now and it is running well. It is installed on a 16gb adata uhs microsd card. As per the instructions, I disabled the internal SD by unmounting it in the system storage settings as soon as it first booted up.

Problem: I just realized, the internal SD was currently mounted. Does it re-mount after each reboot? I reboot more often because I have multiple batteries that I swap between.

Is there any way to disable automatic mounting of the internal SD? Any time it is mounted is a risk for corruption.