[Q] Fix JP3 Write Protection? - Galaxy S I9000 Android Development

Me and a fair share of you using JP3 know that the external sd-card is write protected by default.
I know that with root explorer I temporarily can gain write access and move from the internal sd to the external.
The question:
Is there any fix to lift the write protection altogether? I mean it is to blame for a lot of problems.. not being able to move apps to SD and move things to it from your computer.
Please shed some light for me on this.

Having the same problem with the JP2 firmware...
Some applications/games want to download 'data' to external SD-card...this isn't working at all...write protection.
Someone a solution??
Thanks!

Yeah, I have this issue on Modaco Froyo ROM. Someone help please....

i don't think this will be fixed anytime soon by any users on XDA, it's an issue that Samsung needs to sort out and remember JP3 is an alpha FW, i think you should wait for the next branch or till the real deal comes out.

i guess the best solution...
wait till Froyo becomes official..is a pain cuz its like 2 months to go ..what is it end of Sept??

nandihno said:
i guess the best solution...
wait till Froyo becomes official..is a pain cuz its like 2 months to go ..what is it end of Sept??
Click to expand...
Click to collapse
i'm crying like a baby now...damn! I have rooted my phone today + I did the CFLagFix 1.6 today also...was a happy man, till I walked on this problem...
The JP1 firmware have this problem too? Someone known's? Or it is an Android 2.2 problem?

"with root explorer I temporarily can gain write access"
how can you do this? i mount the sd folder as rw in root explorer, but cannot modify the permissions...

i'm pretty sure all recent JP builds have this error. No point using these builds atm just wait, the only difference with Froyo is flash and a few UI changes anyway

Oke...ur right. I'm going to FW I9000XWJM5. No flash is not so important...

Related

Has anyone installed the OTA AFTER rooting?

I just got the notification for it, but I don't want to risk anything. Is it good to go?
no, before this gets moved, not good to go. don't flash it. you will lose root
seems like you will lose the root...
but some have posted that even after the ota update... the current root process will still work.
Strange. Thanks, guys.
You'd loose your root.
gabemeyers said:
seems like you will lose the root...
but some have posted that even after the ota update... the current root process will still work.
Click to expand...
Click to collapse
I rooted did OTA and still seemed to have root access. Just re-rooted and it seems cool flashing stock rom in a second I guess to confirm
Ok I didnt flash a rom but it is letting me do data wipes and all other functions it seems cool!
Flipz confirmed my successful Re-root looks like OTA is safe!
I rooted mine BEFORE the OTA upgrade.. and it stayed rooted after.. -m
I'm not taking any chances. The other dev team is supposed to release their root and it may be more complete than what we have now. No reason to take a chance on an update that isn't totally critical.
I just tried it.. it appears to fail, reboots, and you're still on 1.32.651.1.
sph33r said:
I just tried it.. it appears to fail, reboots, and you're still on 1.32.651.1.
Click to expand...
Click to collapse
What exactly does the this ota do anyway?
1wingangel said:
What exactly does the this ota do anyway?
Click to expand...
Click to collapse
It's supposed to fix the read/write permissions glitch with the MicroSD card.
diomark said:
I rooted mine BEFORE the OTA upgrade.. and it stayed rooted after.. -m
Click to expand...
Click to collapse
Let me correct this.. The OTA update did not work.. (I stayed at the old software version after trying to apply it.. but root stayed around..)
NOW has anyone managed to place the SD card fix on here manually?
-mark
Yes please. Just update.zip that goodness please. I am sure a complete SuperFresh Rom is on its way.
Well i guess I got this all backwards
I didnt know any better when I got the phone in the store, and I did the update...
then decided to root it.... did the process....
it worked.... but then I had the insufficient permissions on the SD card issue...
after reading a bunch of yea's and nay's on OTA update
I finally made the decision to just due the OTA update cuz I that SD card issue really bugged me...
I did the OTA update, the phone did this funny thing where its showing a green progress bar and then in the middle of it, a red question mark pops up as if it were saying " what the hell is this??" lol
it rebooted... and phone came back online, and now my SD card isnt having the same issue anymore...
UPDATE: Its back.... so now what do I do? Is there any way I can include all my info and settings and apps in a custom recovery cuz if i have to do this again im gonna freak. lol
lbheightsboy said:
I did the OTA update, the phone did this funny thing where its showing a green progress bar and then in the middidle of it, a red question mark pops up as if it were saying " what the hell is this??" lol
Click to expand...
Click to collapse
your having the same problem as me... the update failed.. which is why were waiting on a way to manually apply the update.
OTA worked perfectly. And I get root access
I still haven't gotten the OTA...no matter how many times I manually "check now" in HTC Software Updates, it does not show up. I don't know why this is happening, it's very odd. I'm waiting for someone to cook the update into a custom, or rather stock, ROM. It's driving me insane at the moment, not to mention a bunch of apps are missing from the market (a whole other issue in it's own right). If anyone has an update.zip I can flash or a way to fix this, please please please let me know. Thanks.
I wasn't getting the OTA notification either until I enabled WiFi, then restarted the phone. Worked perfectly after that. Didn't even have to go to system updates.
-------------------------------------
Sent via the XDA Tapatalk App

Froyo 2.2

Just a quick one, if you use the system.ext2 from here http://forum.xda-developers.com/showthread.php?t=509493
and the get the latest rootfs you can use 2.2 on the rhodium
Just been testing it out now, looks pretty good everything works on it nice and smooth only bit of an iffy area is when setting up for the first time (its abit laggy)
Nice it's work
But I search to install flash player 10.1 ^^ but the SdCard where I put the APK file feel not mounted
Damien50 said:
Nice it's work
But I search to install flash player 10.1 ^^ but the SdCard where I put the APK file feel not mounted
Click to expand...
Click to collapse
Yeah I have relised that mounting the sd card deosnt work
i cant get my data to work for some reason can you guys
blitzer320 said:
i cant get my data to work for some reason can you guys
Click to expand...
Click to collapse
Yeah mines working fine, downloaded stuff from the market place
odd im using at&t apn is setup right maybe ill restart android to see if that helps
EDIT: yep restarted now data's working
Trust me guys, I'm watching this like a hawk. JIT isn't even enabled on this 2.2 build yet, and like mentioned, the SD card doesnt mount. This is Alpha, not even Beta, so really it was never meant to be used. (yet) Soon as its usable, ill put together a download for it.
In it's current state, I feel it is quite usable. I have a Rhod210, and pretty much everything except the usual bits are there.
Now if I can only find a script to mount the sdcard...
Have I missed something here? Android 2.2 is already working (as good as 2.1) for TP2?
segadc said:
Have I missed something here? Android 2.2 is already working (as good as 2.1) for TP2?
Click to expand...
Click to collapse
Yeah you missed something lol. Been a month or so now, 2.2 is working even better than 2.1.
Wow lol!
Going to check it out now!

[Q] Problem with XDAndroid.

Hello, I have an AT&T Tilt 2 and when I want to boot off xdandroid 2.2.1 I did the .cab file, soft reset, startup.txt, went into the program, update, boot. It types a bunch of codes, and stops at misc_register(): OK. And it stays there as long as I can see! It won't go any further, however, when I restart the phone, it boots normally in to WinMo. I'm running the stock shipped ROM. Does that have anything to do with it? I'm not getting any errors or anything, just stuck at that. And I know it's not me not waiting, because I've sat it down for 2 hours straight! Please help I really want Android on my Tilt 2.
P.S. I've tried RAR and CAB, also the Reference & Froyo!
Try a clean bundle. Format the card using the HP tool. Full format, FAT32.
Also, try this bundle. It's the newest of the new.
thephoneguru said:
Hello, I have an AT&T Tilt 2 and when I want to boot off xdandroid 2.2.1 I did the .cab file, soft reset, startup.txt, went into the program, update, boot. It types a bunch of codes, and stops at misc_register(): OK. And it stays there as long as I can see! It won't go any further, however, when I restart the phone, it boots normally in to WinMo. I'm running the stock shipped ROM. Does that have anything to do with it? I'm not getting any errors or anything, just stuck at that. And I know it's not me not waiting, because I've sat it down for 2 hours straight! Please help I really want Android on my Tilt 2.
P.S. I've tried RAR and CAB, also the Reference & Froyo!
Click to expand...
Click to collapse
Greetings,
I too have a Tilt 2. In the past I've had many problems with xdandroid and other android ports. I personally prefer to use the manual installation, that way I can control what and where things are placed. I'm currently running the the latest FRX04 release on my Tilt2. Here is how I got it working.
1..Download the RAR package.
2..Format your SD Card (not a quick format)
3..Copy the andboot directory to your SD Card
4..Replace the startup.txt with the one attached here.
5..In WinMo run Haret and let it do it's thing.
6..Once in Android test all your apps.
This worked for me, but until I switched to a newer SD Card I would have random reboots and hang ups.
Post any more complications you have I may be able to help you.
dcmedic said:
Greetings,
I too have a Tilt 2. In the past I've had many problems with xdandroid and other android ports. I personally prefer to use the manual installation, that way I can control what and where things are placed. I'm currently running the the latest FRX04 release on my Tilt2. Here is how I got it working.
1..Download the RAR package.
2..Format your SD Card (not a quick format)
3..Copy the andboot directory to your SD Card
4..Replace the startup.txt with the one attached here.
5..In WinMo run Haret and let it do it's thing.
6..Once in Android test all your apps.
This worked for me, but until I switched to a newer SD Card I would have random reboots and hang ups.
Post any more complications you have I may be able to help you.
Click to expand...
Click to collapse
ooooooh!
I will try this startup for my tilt2!
I am having issues like screen landscaping wrong way sometimes etc.
I will report back. Perhaps we get them to pack your startup in the file under "Tilt 2 ATT GSM" or something!
What SD card did you end up getting?
Thanks!
Prodeje79 said:
ooooooh!
I will try this startup for my tilt2!
I am having issues like screen landscaping wrong way sometimes etc.
I will report back. Perhaps we get them to pack your startup in the file under "Tilt 2 ATT GSM" or something!
What SD card did you end up getting?
Thanks!
Click to expand...
Click to collapse
I already had multiple sd cards, Tiad brought it up to try and change my sd card in a conversation the other day, but I'm using a SanDisk 2GB. My SanDisk 4GB is about 4 years old and believe they do wear out. Older cards aren't good for what we need here, since they are basically or on board device storage.
As for the landscaping, sometimes if a hold the phone flat it will switch to landscape left or right, but I usually do not have a problem when I'm holding it in the orientation I'm needing.
That is the same startup file I have used through out 3 different builds. FRX03, FRX04, and FROYO X. I did have overclocking in there, but come to find out it didn't help, I feel that it probably was the cause of a few of my restarts.
I hope everything works out for you. Report back..
dcmedic said:
I already had multiple sd cards, Tiad brought it up to try and change my sd card in a conversation the other day, but I'm using a SanDisk 2GB. My SanDisk 4GB is about 4 years old and believe they do wear out. Older cards aren't good for what we need here, since they are basically or on board device storage.
As for the landscaping, sometimes if a hold the phone flat it will switch to landscape left or right, but I usually do not have a problem when I'm holding it in the orientation I'm needing.
That is the same startup file I have used through out 3 different builds. FRX03, FRX04, and FROYO X. I did have overclocking in there, but come to find out it didn't help, I feel that it probably was the cause of a few of my restarts.
I hope everything works out for you. Report back..
Click to expand...
Click to collapse
will do!
which exact package are you using now?
link appreciated if not already posted above.
Is it a good idea to delete the ts-calibration file as in XDAndroid2.2Froyo.012211 ?
Any other cleanup measures?
Prodeje79 said:
will do!
which exact package are you using now?
link appreciated if not already posted above.
Is it a good idea to delete the ts-calibration file as in XDAndroid2.2Froyo.012211 ?
Any other cleanup measures?
Click to expand...
Click to collapse
I'm using the same package as arrrrrgh posted in Post #2. I just left the touch screen calibration file that came with the package. No other clean up, other than full format to fat32 with your preferred utility.
dcmedic said:
I'm using the same package as arrrrrgh posted in Post #2. I just left the touch screen calibration file that came with the package. No other clean up, other than full format to fat32 with your preferred utility.
Click to expand...
Click to collapse
OK cool, I will give that load a shot tonight.
As of now I am using: XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACKAGE
My screen issues are gone now with those tweaks! thanks so much!!!
Although now this thing seems dog slow.
I took out my line "clock-7x00.a11=500" which I think is just stock anyway.
You do not use this command as you noted issues overclocking. Thus yours should be stock speed too right?
This thing is sloooooow now from earlier with my old 'incorrect' stock config in the RAR package.
I also have the weird typing issue in which I press c once (on the hard keyboard slideout), but cccc appears. I think if I type a word super slow, it works better.
So if i type cingular at a decent pace, it will type out 'ccccingularrr'
Any leads on that?
you may need to delete your data.img file and rebuild it with the new startup.txt. that way android is running at stock speed during the setup. shot in the dark.
Sent from my Tilt 2 using the XDA mobile application powered by Tapatalk
Prodeje79 said:
OK cool, I will give that load a shot tonight.
As of now I am using: XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACKAGE
My screen issues are gone now with those tweaks! thanks so much!!!
Although now this thing seems dog slow.
I took out my line "clock-7x00.a11=500" which I think is just stock anyway.
You do not use this command as you noted issues overclocking. Thus yours should be stock speed too right?
This thing is sloooooow now from earlier with my old 'incorrect' stock config in the RAR package.
I also have the weird typing issue in which I press c once (on the hard keyboard slideout), but cccc appears. I think if I type a word super slow, it works better.
So if i type cingular at a decent pace, it will type out 'ccccingularrr'
Any leads on that?
Click to expand...
Click to collapse
Holy crap dude... search. You've asked so many questions that have been answered previously, seriously.
With that said, all the issues you describe are all related to the system_server bug. Just make a call to voicemail (or any call really) and it'll clear up. We're looking into the cause and a potential solution.
dcmedic said:
Greetings,
I too have a Tilt 2. In the past I've had many problems with xdandroid and other android ports. I personally prefer to use the manual installation, that way I can control what and where things are placed. I'm currently running the the latest FRX04 release on my Tilt2. Here is how I got it working.
1..Download the RAR package.
2..Format your SD Card (not a quick format)
3..Copy the andboot directory to your SD Card
4..Replace the startup.txt with the one attached here.
5..In WinMo run Haret and let it do it's thing.
6..Once in Android test all your apps.
This worked for me, but until I switched to a newer SD Card I would have random reboots and hang ups.
Post any more complications you have I may be able to help you.
Click to expand...
Click to collapse
Hello, thank you for the quick response. I did exactly what you said. And once I tap Haret it codes and stops at misc_register(): OK still... Any other suggestions? Thank you agian.
it probably doesn't matter, but is your phone all unlocked etc and able to be flashed with any winmo rom?
using olipro?
just trying to think of any differences with our phones.
Prodeje79 said:
it probably doesn't matter, but is your phone all unlocked etc and able to be flashed with any winmo rom?
using olipro?
just trying to think of any differences with our phones.
Click to expand...
Click to collapse
What is unlocked? Isn't that where T-Mobile would be able to use it?? If not, please explain. Sorry for my stupidness. lol
Is it like jailbreaking and/or rooting?
You do not need to do hardSPL unlocking to use Android from the SD card.
I would imagine with NAND builds you would... but since this all runs off the SD card, no need for HSPL.
Assuming you're using that build that was posted in post #2, it should work just fine - did you make any changes to it, or just extract it to the root of your SD and hit haret.exe...?
thephoneguru said:
What is unlocked? Isn't that where T-Mobile would be able to use it?? If not, please explain. Sorry for my stupidness. lol
Is it like jailbreaking and/or rooting?
Click to expand...
Click to collapse
well mainly just the hard SPL unlocking. Not the sim.
very easy.
see the stickies here: http://forum.xda-developers.com/forumdisplay.php?f=490
mainly:
Hard-SPL Unlocker for Rhodium (AT&T Tilt 2) Released and Updated! New FAQ added!
http://forum.xda-developers.com/showthread.php?t=550131
and flashing...
[Resources] Flashing your First GSM Rhodium Rom (For Noobs)
http://forum.xda-developers.com/showthread.php?t=550540
if you do this don't forget to task 29!
http://forum.xda-developers.com/showthread.php?t=649191
I use the energy rom GTX:
http://forum.xda-developers.com/showthread.php?t=562773
I just backed up all my contacts on my SD card with pimbackup and restored them to the new rom....
Again, to thephoneguru - you do not need to do that ^^.
Only if you want to install a custom WinMo ROM, or if you're flashing to full Android (which is not recommended at the moment!) do you need to do HSPL.
arrrghhh said:
You do not need to do hardSPL unlocking to use Android from the SD card.
I would imagine with NAND builds you would... but since this all runs off the SD card, no need for HSPL.
Assuming you're using that build that was posted in post #2, it should work just fine - did you make any changes to it, or just extract it to the root of your SD and hit haret.exe...?
Click to expand...
Click to collapse
I did not make any changes at all I just put the androot directory on the root of my sd, went to the file explorer and tapped haret.exe. Also, the sd card was just formatted (non quick format) to FAT32.
arrrghhh said:
Again, to thephoneguru - you do not need to do that ^^.
Only if you want to install a custom WinMo ROM, or if you're flashing to full Android (which is not recommended at the moment!) do you need to do HSPL.
Click to expand...
Click to collapse
well we get the picture!
its the only difference I can think of in our phones.
I say give it a shot, it is so simple!
Prodeje79 said:
well we get the picture!
its the only difference I can think of in our phones.
I say give it a shot, it is so simple!
Click to expand...
Click to collapse
How is it so simple? Can you explain the procedure? Thank you.
thephoneguru said:
How is it so simple? Can you explain the procedure? Thank you.
Click to expand...
Click to collapse
He posted a lot of links on how to do it... Post #15?
It won't have any effect on your issue tho. It'll only enable you to flash custom ROMs if you so choose to do so.
Let's focus on your issue. Can you tell me where it stops? Does it always stop at the same place? Have you tried different kernels? Any different builds? Have you tried the newest FRX04 build?

[ROM]ROOTSide (In the Works. First Upload this week)

ROOTSide ROM
Base Flipside ROM with root/busybox/unknown sources enabled. Only thing different in this rom than rooting it yourself is you get to check/uncheck unknown sources. Yes, that means you can turn unknown sources ON and OFF! I have a clockworkmod recovery folder zipped up for distribution, but I want to post a full-fledged ROM zip file for the masses. PM me, and I will send you the ZIP file that I have right now.
What you get:
base install for the flipside (AT&T) with motoblur ready to set up. It is the exact same thing as doing a factory reset, but you get all the benefits of superuser with busybox and the addead feature of having unknown sources checkbox in the settings.
I will work towards a deoxed version this weekend as well.
No custom bootscreen (yet). No custom anything, really.
Almost There
I am currently in the middle of Deodexing the image. I have added in wifi tethering, and ensured it will have superuser and busybox pre-packaged. Next step is pushing this to my wife's phone and not having her get a pretty brick in return. If all goes well, I will be posting the image by morning light (CST).
Fingers Crossed!
Well
Things didn't go too well with my first build attempt. Appears to be a permission issue with the /system folder. I will sleep on it, and give it a second go in the morning. Sorry for the apparent "tease". If you want a faster build, I could use some other devs working with me.
Hey man, sounds like you're doing great! Keep it up...I already found a way to get the root with unknown sources checked, so i'm just gonna wait for the deoxed version! Hope it goes well as you try again.
Current Issues
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Me too...good luck!!
jonsjava said:
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Click to expand...
Click to collapse
Both of those files are att/moto bloat... just be rid of them
Sent from my MB508 using XDA App
Glad to see some work on this device, I love the form factor but it's obviously not very popular with devs...
Very interested to see this come around. I would like to streamline the wife's phone. Her battery life is a 1/3 of my rooted and flashed X10. Sadly though I am NOT a Dev nor even a cook.
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
so I was curious, I was able to get to unlock mode with an sqlite thing and it worked just fine for me, but have you been able to knock out the bloat and stuff? cause it sounds like the makings of a custom rom lol
you know what the turtle said.. slowly but surely I will win this race
jonsjava said:
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
Click to expand...
Click to collapse
Several ppl have said they have run into this problem...don't know what the deal is...
Is it possible to get CM7, or it's a problem with a locked kernel?
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
jonsjava said:
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
Click to expand...
Click to collapse
sounds good man, keep us posted on progress!!
So check this out...I messaged the guy at modmymobile and asked how things were going becuase I heard people were having problems getting an updated CMW and this is his response:
"been sittin on the updated cwm recovery binaries and been draggin my feet/takin a break the past week or 2. i'll throw something out soon, but cant commit to a timeframe, sorry."
Looks like things are on the up and up...stay patient everyone
GOOD JOB!!!,
We are waiting for the rom
Dukenukemx said:
Is it possible to get CM7, or it's a problem with a locked kernel?
Click to expand...
Click to collapse
I can't install CM7, it reboots and locks up, then I have to reinstall froyo. It never worked when I had eclair either.

Possible memory leak fix for 5.0.2

I've been poking around this morning trying to figure out why my phone keeps coming to a screeching halt every once in a while. We all know about this memory leak in pre 5.1 lollipop. Looking at github I tracked down ColorFade.smali in our firmware. I also found what needs to be changed to "fix" the issue. I made the edits for the regular S6 firmware which I'm almost positive you guys would be able to use as well. But, you have to be deodexed, or delete the services.odex files. I'll wait for some feedback from other FS6 owners, and if it's positive I'll get you guys fixed up too.
Forgive me as I am ignorant on the process, but I need to be rooted to delete services.odex files?
nviz22 said:
Forgive me as I am ignorant on the process, but I need to be rooted to delete services.odex files?
Click to expand...
Click to collapse
I believe so.. You'll need a file explorer with root access to edit any system files.. Root explorer is my favorite
Very interesting. Wanna see how this develops
mikeyinid said:
I've been poking around this morning trying to figure out why my phone keeps coming to a screeching halt every once in a while. We all know about this memory leak in pre 5.1 lollipop. Looking at github I tracked down ColorFade.smali in our firmware. I also found what needs to be changed to "fix" the issue. I made the edits for the regular S6 firmware which I'm almost positive you guys would be able to use as well. But, you have to be deodexed, or delete the services.odex files. I'll wait for some feedback from other FS6 owners, and if it's positive I'll get you guys fixed up too.
Click to expand...
Click to collapse
Would love to give this a try
Feedback has been good, unfortunately this only fixes one of the problematic memory leaks in lollipop.
I could use it? Atleast one is fixed

Categories

Resources