Related
****** USE AT YOUR OWN RISK *******
This is NOT SUPPORTED SOFTWARE. This is purely for my amusement and entertainment. I'm making it available to download for those who might like to examine my work, but if you install it, you are on your own. I can't even test this myself. (I don't have a GT-P6200.)
Seriously - this has not been tested enough for me to be happy with it, and I'm unable to test it myself. Please read the thread for the GT-P6210 for instructions, known issues, warnings, etc.
If you do decide to install this anyway, please let me know how it works out for you. If no one is using it, I WILL NOT MAINTAIN IT AND WILL DROP IT.
If people do start using it, and the reports are that everything is working okay, then it'll get merged into what I'm already doing with the other two 7 plus models (meaning it'll get updated as needed when they do.)
Again, PLEASE READ the thread for the 6210 for everything you need to know: http://forum.xda-developers.com/showthread.php?t=1379532
..and here's a link for a CWM recovery.
Link: http://www.mediafire.com/download.php?do5jkna3dpas1tq
Take care
Gary
Hi! I'm a placeholder.
garyd9 said:
Hi! I'm a placeholder.
Click to expand...
Click to collapse
Hi, Placeholder. I'm a placeholder, too. Good meeting you here.
Pm'ed you. went straight in CWM, looks nice. able to make a full backup and md5. fails to restore in the middle of restoring /data
also getting UDIDs are inconsistent , fixing permission is supposed to take care of this.
and Im pretty much factory reset after reboot.
EDIT: appears as if Location cache map app by remy in market I had set to block wifi and cell caches. restoring a backup in CWM got permissions error, trestoring /data fails and Im left with pretty much a factory reset. went back to market and reinstalled suspicious app, installed and still says caches blocked removed app, rebooted, made back up and successful restore! woo hoo! Thank You Gary!
Note: should we make a note for 7+ CWM users beware blocked location caches, or re-write recovery to take care of this, and/or email the app dev?
anyways, pretty excited. Thanks so much Gary.
Anyone else want to help test the CWM Recovery for this tablet? (GT-P6200 only)
The current tester has had mixed results, but it _may_ have been the result of a third party app causing problems. I'd like to get someone else to test in addition to ensure there aren't any other issues.
In order to test, I need someone who has "adb" installed on their PC, is comfortable with linux commands, already knows how to use adb for commands such as "adb shell, adb push, and adb pull", doesn't mind using ODIN to restore their tablet to a factory state if it soft-bricks, and already knows how to use ODIN and CWM Recovery.
As a side-note; the third party app that MIGHT have been causing the problem is "Location Cache" by "remydemy." I don't use this app myself, but apparently it has some function to block the google/android location caches and it appears to do that by messing with the permissions on the files... which is somehow causing an error when the recovery tries to clean the /data directory in order to restore.
Thanks
Gary
link posted for testing.
thanks again gary loving it.
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
So i just used root ecplorer to delete entire contents of folder. : )
is this not linked properly or CWM issue, or is this normal function?
thanks so much for your help.
chrisrotolo said:
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
Click to expand...
Click to collapse
I'll look into it. Please try this alternative to test that function: Boot your phone normally, and then reboot into recovery. Using the recovery menu, mount the /data partition. Then use 'adb shell' to shell into the device and manually look in the /data/dalvik-cache directory. Then "cd /" and from within recovery choose the advanced->wipe dalvik-cache. Then look in /data/dalvik-cache directory again to see if it did what it should have done.
It's possible, based on the ordering of your above description, that the dalvik cache rebuilt after you wiped it (during the reboot) but before you removed your bloatware.
Take care
Gary
thank you. Gary tried not to get Banned OK? we need you buddy. lol
chrisrotolo said:
thank you. Gary tried not to get Banned OK? we need you buddy. lol
Click to expand...
Click to collapse
Where you able to run those tests yet?
thanks
Gary
not as of yet, sometime today though.
---------- Post added at 03:13 PM ---------- Previous post was at 02:23 PM ----------
so yeah, you must be right. dalvik-cache was full with /data mounted. cd / then wiped dalvik from CWM, which finishes in a split second; a list (ls) shows no dalvik-cache folder after wiping, completly gone.
Answers my question.
One other issue I ran into, that you're may be aware of is somehow I disabled the power button in CWM, it said something about back button disabled. I think I had to hold power for 10 sec. to reset device.
Thanks.
chrisrotolo said:
...somehow I disabled the power button in CWM, it said something about back button disabled.
Click to expand...
Click to collapse
That one I'm not sure of and really can't help much with. No 'power' button means you can't select anything which would really be annoying.
it works great! instant root and cwm within 2 minutes! i highly recommend gary's method than the other one. i also don't seem to lose root access by clearing ram memory. SWEET.
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
lvsw said:
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
Click to expand...
Click to collapse
formatting the internal SDCard isn't going to happen with this version of CWM (that's designed for GB.) Honeycomb devices don't have a seperate /sdcard partition to format. Formatting the "internal sdcard" can be done from within the settings menu via a factory reset.
The other two items aren't broken - they simply don't exist in CWM recovery, and probably never will... Is having the pre-loaded samsgung sample video and music files repushed to your device over and over actually more important to you than the ability to do a nandroid backup? Do you even know what the CSC is that isn't being updated?
Have you bothered to seach around BEFORE installing this? Have you bothered to search around AFTER installing it to find out how to restore to factory?
I'm NOT going to answer your specific question on the basis that it's been answered already and I honestly feel that a user of XDA needs to have the ability to SEARCH before posting.
Take care
Gary
worked like a charm...backup and restore works perfectly...
thanks gary !!!
Hey Gary-
Question -
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
I could just flash a new recovery from ROM Manager, but I don't want to screw anything up.
Thanks!
Sent from my Galaxy Tab Plus using Tapatalk
jeffcavicchi said:
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
Click to expand...
Click to collapse
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
garyd9 said:
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
Click to expand...
Click to collapse
Got it - sort of what I figured.
Am I wrong that Recovery still sees the external SD card as an internal SD card? I thought the last time I flashed a zip (boot animation) Recovery showed it as being on the internal card, even though it was actually on the external card. I could be wrong, though - and I don't have the device in front of me to check.
Not a big deal either way - thanks for the response, and your hard work!
*Edit*
Just realized I posted this in the wrong thread like an idiot - I have a P6210. guess that's what happens when you start posting things bc (before coffee).
If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.
was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.
The zip file seems to be corrupt. Could you re-upload plz
worked great on my end, no problems.
khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .
wow this method really blaze hellfire much thanks to your( you) & (rom dev)
Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .
thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid
dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA
Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium
It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.
Should be working fine but it's thoroughly untested so expect errors at some point.
It's for cyanogenmod installations where /custpack is mounted to /system/app, if there is a request i'll make a version that mounts /custpack to /custpack but for now this is it.
I take no responsibility for what this will do to your phone, it's entirely possible that it will kill your phone and even cause a rift in the space time continuum which will kill us all.
Anyway, here it is, flashable via fastboot as usual, if it goes to stable i'll make an installer for it to install via CWM.
For those not comfortable with flashing via fastboot or who don't have access to a computer at this time, use flash_image via terminal, it should work fine.
Latest version:
cwm_touch_cocktail_6.0.2.7-testing-V2.img
MD5: feb35010a527de42c6c68d6987b939e1
Old versions (kept but not recommended):
cwm_touch_cocktail_6.0.2.7-testing.img
MD5: da314f6eb6429bc3530539d8a0e9e20a
Changelog:
2013-01-09
* Fixed buttons, you can now scroll, select and go back using the buttons.
* Fixed backup, /custpack is now linked to /system/app, this should also make it compatible with older roms. (Remember, this is still testing)
* Added mountpoint for /sd-ext to fix nandroid backups for A2SD/S2E/Links2SD installed apps.
* Fixed some glitches and updated kernel code.
2013-01-08
* initial release
Just flashed it to my mobile and thus far it looks promising. Currently I am not planning to change my rom yet so I haven't confirmed if it is able to flash a rom I only saw it boot.
A little thing I noticed though.
When CWM boots and you are in the main menu the menu fills around 80% of the screen. But when you go to another menu lets say flash something from SDCard it only fills up 50% of the screen and you have to scroll a lot to reach the bottom.
Also the buttons are not working at all?
When you press some of the buttons it starts doing weird stuff..
It seems like the volume buttons and the power button work currectly but the buttons at the bottom of the screen are weird.
Hylix said:
Just flashed it to my mobile and thus far it looks promising. Currently I am not planning to change my rom yet so I haven't confirmed if it is able to flash a rom I only saw it boot.
A little thing I noticed though.
When CWM boots and you are in the main menu the menu fills around 80% of the screen. But when you go to another menu lets say flash something from SDCard it only fills up 50% of the screen and you have to scroll a lot to reach the bottom.
Also the buttons are not working at all?
When you press some of the buttons it starts doing weird stuff..
It seems like the volume buttons and the power button work currectly but the buttons at the bottom of the screen are weird.
Click to expand...
Click to collapse
I had completely forgotten about the bottom buttons TBH, i'll fix that in a future version.
Regarding the screen space, it's not much i can do about that ATM but i'll keep it in mind when and if it gets to stable.
Awesome looking good so far
Really cool. Just point and I'll help test.
Downloading and testing.
With this we can backup and restore CM/PA/PAC roms right?
Mrwargod said:
Downloading and testing.
With this we can backup and restore CM/PA/PAC roms right?
Click to expand...
Click to collapse
If you mount /system/app in mounts and storage it should work just fine.
I'm probably going to write a script and put it in the place of the nandroid/nanddump/nandwrite files so /system/app is mounted before the backup/restore is written.
Just added some stuff to it, partitioning sdcard and support for sd-ext (and swap).
Should work well with an init.d script and s2e for those interested in larger storage for apps.
(simple script to mount /dev/mmcblk1p2 to /sd-ext would work)
tumaini418 said:
Really cool. Just point and I'll help test.
Click to expand...
Click to collapse
Would be great it you have the opportunity.
When i use key test section, its dont back main screen and i need unplug battery.
You did great job thanks a lot...
master' said:
When i use key test section, its dont back main screen and i need unplug battery.
You did great job thanks a lot...
Click to expand...
Click to collapse
You are welcome.
Jinxxed said:
If you mount /system/app in mounts and storage it should work just fine.
I'm probably going to write a script and put it in the place of the nandroid/nanddump/nandwrite files so /system/app is mounted before the backup/restore is written.
Just added some stuff to it, partitioning sdcard and support for sd-ext (and swap).
Should work well with an init.d script and s2e for those interested in larger storage for apps.
(simple script to mount /dev/mmcblk1p2 to /sd-ext would work)
Click to expand...
Click to collapse
Yes, having that automated would be great. If i could backup/restore/install zip's all in one CWM that would be awssome and render it definitivelly daily usable. And way easyer for me to test more roms without the concern in loosing my previous rom.
Mrwargod said:
Yes, having that automated would be great. If i could backup/restore/install zip's all in one CWM that would be awssome and render it definitivelly daily usable. And way easyer for me to test more roms without the concern in loosing my previous rom.
Click to expand...
Click to collapse
Should work fine now, to check if it is, analyze the content of your /sdcard/clockworkmod folder.
Already on it to try the latest version of PAC.
I'll feed you on how it went.
---------- Post added at 11:39 AM ---------- Previous post was at 11:18 AM ----------
The link is dead Jinxxed, or is it still uploading?
Mrwargod said:
Already on it to try the latest version of PAC.
I'll feed you on how it went.
---------- Post added at 11:39 AM ---------- Previous post was at 11:18 AM ----------
The link is dead Jinxxed, or is it still uploading?
Click to expand...
Click to collapse
I mistyped the link. :silly: It's fixed now.
Sorry about that.
Yeah, i had already figured out the correct link anyway.
Thanks, testing!
Wipe battery stats is missing in advanced menu.
Backup / Restore - Not working properly - Some of my apps got lost in restore, namedelly all the gapps, some launchers (holoHD), some file explorers (root file explorer), google account, . . .
Flash zip - ROM flashed ok but gapps didn't flashed, neither did an aditional mod.
But it's really looking really good. And the hardware buttons are fixed.
Keep up the good work.
Mrwargod said:
Wipe battery stats is missing in advanced menu.
Backup / Restore - Not working properly - Some of my apps got lost in restore, namedelly all the gapps, some launchers (holoHD), some file explorers (root file explorer), google account, . . .
Flash zip - ROM flashed ok but gapps didn't flashed, neither did an aditional mod.
But it's really looking really good. And the hardware buttons are fixed.
Keep up the good work.
Click to expand...
Click to collapse
Thank you.
It's a weird result since that means that the backup has problems with both /data and /system/app (i assume since google account and launchers not installed via CWM are stored on /data). It really should be all or nothing, one would think...
There is a problem with mounting /system/app for some reason, that's why gapps isn't installed properly, i'll look into it.
It should be easy enough to fix though, expect a new version within the next couple of days.
Will post the same post here as in Benetnath his PAC rom cause maybe it has something to do with CWM?
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Just ran against a problem with doing the PAC update.
All my gapps seem to be broken and some apps crash on start up.
I had the first PAC rom running and flashed the newest over it while clearing my cache (tried flashing the gapps after this but still didn't fix it)
After this I did a complete reset and flashed it and now it seems to work.
Don't know if its the ROM or if its the new touch CWM which is still in testing..
NOTE: It seems like other people succeeded in flashing the updated rom over the previous rom.
I am not the only one with this problem and it seems like there are other people who have the same problem with the other CWM so ignore this all
trying to flash image in terminal in phone. i keep getting "error scanning partitionsfailed with error: -1
??????????
anyone?
nevermind i went ahead and did it the way i know how.
2nd Edit: just did a backup and restore. Seems to have worked fine.
I couldn't mount usb though.
Great work man. Between you and Benetnath we should be cooking with gas soon.
Thanks jinxxed.
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]LG Optimus One Device Family[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: How do I root my LG Optimus One?[/SIZE]Rooting can be accomplished with Gingerbreak.apk 1.20 for most devices running stock Froyo ( 2.2 ) and Gingerbread( 2.3 ). There is also Z4Root and SuperOneClick for those instances when GingerBreak doesn't work.
[SIZE=+1]Q2: How do I install a custom recovery?[/SIZE]This is too broad a topic to cover in detail in this FAQ. Please refer to any of the methods listed below...
Install recovery with 'flash_image' binary or LGMDP
All in one how-to for rooting, installing ADB, installing recoveries, etc...
Install ROM Manager from Play Store. To use ROM Manager you MUST be rooted. Use ROM Manager to install a custom recovery.
Most P500 and P505 models got their official updates. Choose the Optimus One item
The P506 and P509 did not get official updates. Choose the Optimus One (OldBB) item
Device models not mentioned, old baseband models choose the "Optimus One (OldBB)" item. New baseband models choose the "Optimus One" item.
There is also my utility Android Flash Recovery to flash a recovery via fastboot and fastboot mode.
[SIZE=+1]Q3: Why do I have to "trim" my ROMs?[/SIZE]
The allocated system partition on any of these devices is only 190 MB. Not really huge. However since Android 4.0, the space required for everything has increased to a point that it will almost completely fill the system partition only leaving a few KB free. OOne ROM Editor is a Windows utility designed specifically for this task.
[SIZE=+1]Q4: I've flashed ( any ICS or JB ) ROM and Google Apps. Why doesn't my Home and or Search button work?[/SIZE]Did you trim the ROM prior to installation? If not, see question #3 above.
Did you wipe your /cache and Dalvik cache prior to the ROM installation?
[SIZE=+1]Q5: Why doesn't Link2SD work with CM10+?[/SIZE]
There are several reasons. There is an actual procedure required in order to get Link2SD to work properly with these devices.
The ROM must be trimmed prior to installing or immediately after installing on to the device. See question #3 above.
The biggest issue with Link2SD is the lack of free space on the devices system partition. I recommend a minimum 1024 MB ( 1 GB ) partition on the sdcard, formatted as ext4.
Now install Link2SD. After it installs, open it and let it create it's mount scripts.
Reboot device. On this first boot Link2SD will create it's symlinks and move whatever files it needs to move.
Reboot device once more for good measure.
From here, assuming that you have removed enough from the ROM when trimming it, the Google Apps package should be installed via your preferred recovery.
Reboot. You should see a "Android is updating apps" notification as the ROM starts.
[SIZE=+1]Q6: How can I get rid of Link2SD before migrating to another *2SD script?[/SIZE]
Link2SD installs scripts etc. in 2 places
/system/etc/init.d
/system/etc/install_recovery.sh
Delete both mounting scripts and delete the /data/sdext2 folder to get rid of Link2SD. For credit and more details please see this post.
[SIZE=+1]Q7: I have installed CM10.1. What happened to the Developer Options?[/SIZE]
On the device, go to Settings -> About Phone. Scroll to and tap on the build number 7 - 8 times until you get a toast notification that states that Developer Options are enabled. Press the "Back" button. A Developer Options item should appear in the main settings list, usually just before About Phone. Press the Developer Options item and then enable Developer Options with the toggle at the top of the page.
[SIZE=+1]Q8: I'm running CM10.1. Where is the advanced power menu?[/SIZE]
If Developer Options are not enabled, see question #7 above. Go to Settings -> Developer Options and enable "Advanced Reboot".
[SIZE=+1]Q9: I just flashed a ROM and I have no network. What should I do?[/SIZE]
All ROMs from CM7 and newer are built for new baseband. This is more than likely because of the wrong baseband. The P509 and P506 are old baseband devices. P500 and P505 devices that didn't get the official update are also old baseband. You can flash the old baseband patch via CWM or any other recovery to remedy this problem. Please see post #8 for the old baseband patch.
It is also possible the the APN for your carrier is either not set up or is incorrectly set up.
[SIZE=+1]Q10: What is the best method for installing a ROM?[/SIZE]
In my opinion it is always best to perform all wipes, even when upgrading the same Android version, although it is not really required when upgrading. The following steps are assuming that you are using CWM.
Boot device in to Recovery. If you don't have a custom recovery, please see question #2 above.
Perform "Wipe data/factory reset". This will format the /data, /cache, /sdext, and .android_secure
Select the "Advanced" option and on the next screen select "Wipe Dalvik Cache". Confirm the wipe.
Not necessary but I do it anyway, in the "Advanced" screen select "Wipe battery stats" and the confirm that wipe
For a clean installation I recommend formatting the system partition too. From CWM home screen select "mounts and storage". On the next screen select "format /system" and then confirm the format.
Press the back button until you are back in the CWM home screen. Select "Install zip from sdcard" and then select "Choose zip from sdcard". Browse your sdcard for the ROM to install and select it. Confirm the installation. Now wait for the install to finish.
Go back to CWM's home screen. Select "reboot system now" option and let the device boot. The initial boot will take a couple of minutes. Don't panic.
If you intend to install any patches or Google Apps, reboot device into recovery and repeat step 6 for each additional package to install.
[SIZE=+1]Q11: How can I make Voice Search work with Google Now in JB roms?[/SIZE]
I have gathered links to several posts regarding this, and they can be found here
*
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to everyone who contributed to the production of this FAQ
Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread. More Frequenty Asked Questions and their answers are welcome here and I will add them to the OP.
Q: How can I get rid of Link2SD, before migrating to another *2SD script?
A: Link2SD installs in 2 places, /system/etc/init.d & /system/etc/install_recovery.sh
You need to delete them both mounting scripts, and also delete the /data/sdext2 folder to get rid of link2sd...
Credit here
Personally, I like Mounts2SD :good:
Let's see if we can get this into a sticky...
Q: Can changing baseband from Lgmdp brick my phone?
A: No.
Sent from my LG-P500 using Tapatalk 2
shinobisoft said:
It's in the Q&A forum
Click to expand...
Click to collapse
Found it! Oh, and they made it sticky too... great work!!
We need a list of working *2sd with cm10/10.1
Does this F.A.Q. meant to be only for cm10/10.1?
uf0999 said:
We need a list of working *2sd with cm10/10.1
Does this F.A.Q. meant to be only for cm10/10.1?
Click to expand...
Click to collapse
No. It's not meant for any specific Android version at all. This FAQ is still a WIP. This FAQ is intended to be a starting point for new members. It is not designed or intended to go in to too much detail about anything. Questions with lengthy answers are answered in short form when possible. If more explanation is needed, then a link or links will be included to direct the member to the correct thread.
As for what you have stated, I will see what I can come up with. Some of the *2SD scripts can be problematic setting up and require special details. Link2SD and Mounts2SD are two problematic ones right off the top of my head.
Thanks for the suggestion.
Old baseband patch
Here's the old baseband patch.
Q: How can I make Voice Search work with Google Now in JB roms?
A: I have gathered links to several posts regarding this, and they can be found here:
http://forum.xda-developers.com/showpost.php?p=39156799&postcount=169
sent from a jellybean sitting on an ice cream sandwich (and a 3.0 kernel)
Hey Bill, I just now figured out what dovidhalevi was talking about. The link that I posted above works. But the copied link that you posted does not. Gotta love this great software. Got no choice.
Yup. Your link in Q11 is to:
http://forum.xda-developers.com/show...&postcount=169
While it should be to:
http://forum.xda-developers.com/showpost.php?p=39156799&postcount=169
ibub said:
Hey Bill, I just now figured out what dovidhalevi was talking about. The link that I posted above works. But the copied link that you posted does not. Gotta love this great software. Got no choice.
Click to expand...
Click to collapse
post-mortem said:
Yup. Your link in Q11 is to:
http://forum.xda-developers.com/show...&postcount=169
While it should be to:
http://forum.xda-developers.com/showpost.php?p=39156799&postcount=169
Click to expand...
Click to collapse
Thanks
No sure how the URL error came about as I copied the link directly from ibub's post, but in any case link has been fixed in Q#11.
ibub said:
Q: How can I make Voice Search work with Google Now in JB roms?
A: I have gathered links to several posts regarding this, and they can be found here:
http://forum.xda-developers.com/showpost.php?p=39156799&postcount=169
sent from a jellybean sitting on an ice cream sandwich (and a 3.0 kernel)
Click to expand...
Click to collapse
will all roms will work on this baseband
That "oldbasebandfix.zip" is to make a new baseband rom work with a phone that has old baseband. Check the thread for the rom to check for baseband requirements.
sent from the p509 that I thought I killed again... no trouble at all
What is the most stable Jelly Bean ROM i can install on my P500? there are a lot of ROM. i tried CM10(Build 7) from Rashed97 but after a few weeks it crashes some (well most) of my application. Thanks in advanced!
mackoyskii said:
What is the most stable Jelly Bean ROM i can install on my P500? there are a lot of ROM. i tried CM10(Build 7) from Rashed97 but after a few weeks it crashes some (well most) of my application. Thanks in advanced!
Click to expand...
Click to collapse
reboot to recovery, clear cache once a couple of days.
mackoyskii said:
What is the most stable Jelly Bean ROM i can install on my P500? there are a lot of ROM. i tried CM10(Build 7) from Rashed97 but after a few weeks it crashes some (well most) of my application. Thanks in advanced!
Click to expand...
Click to collapse
I'm afraid that I cannot personally answer your question. One note, this is not a general discussion thread. Please read or reread the OP.
Ok so I have a couple of problems with my p500.
First of all my phone, doesn't want to connect to my pc. I don't have a clue why, I think it happened for the first time a long time ago while I was fidling with it (can't remember what) and once it connects, my computer says that the device got disconected when it is still connected! I've tried to factory reset but nothing happened still the same.
Secondly the problem that I have is that sometimes the phone boots into emergency mode for no good reason.
It is running on 2.3.3 android and it is not rooted or anything but stock!
Looking forward for your sollutions guys!
Gkikas said:
Ok so I have a couple of problems with my p500.
First of all my phone, doesn't want to connect to my pc. I don't have a clue why, I think it happened for the first time a long time ago while I was fidling with it (can't remember what) and once it connects, my computer says that the device got disconected when it is still connected! I've tried to factory reset but nothing happened still the same.
Secondly the problem that I have is that sometimes the phone boots into emergency mode for no good reason.
It is running on 2.3.3 android and it is not rooted or anything but stock!
Looking forward for your sollutions guys!
Click to expand...
Click to collapse
This is not a general help thread. Please reread the OP. In this case you should've started another thread. But in any case...
A partial answer to your question can be found here
Sounds like the drivers need to be reinstalled on your PC. They should be uninstalled, reboot PC, reinstalled, and reboot once more. Power off your device. Attach data cable to device assuming its already attached to a USB port that is not a hub. Now power on the device and let the driver installation do it's thing.
The above is assuming you've managed to get your device to properly boot.
Best of luck.
Hello everyone!
Since xda won't let me ask directly in the relevant thread (as I am a 'noob' here), I guess here's the correct place. So here we go:
Does anyone know how to enable a hardware video playback on P-500 with Evoking 2.1 ROM (Skydragon)? I use Mobo Player, and in several earlier versions of Evoking it simply did a software mode fallback. Tried V-Player, but it simply crashes (as well as 'Now playing' and some other media-related apps in this ROM).
-regards
-p
Hi,
Background:
I am a retired software engineer. I worked on the windows platform and focused on the Visual Basic family of code though I was familiar with many languages from assembly to C. I am very familiar with the programming jargon but find myself at a loss when reading to posts here, so bear with me if I don’t have a complete grasp on the terminology.
My Story:
I have an AT&T Samsung Infuse with android v2.3.6 and have been very happy with it. This is my first smartphone and didn’t pay much attention to how it worked until now. I bought an irrigation controller that has an app for the phone. After installing the controller, I found out the app only runs on v3.0 or newer (mine is v2.3.6). So, here I am trying to upgrade my phone to a newer version so the app will work (trying not to buy a new phone for this). My first goal was to back up everything, so I spent a number of days reading threads here trying to understand what I needed to do. I discovered that v3.0 is a tablet only OS (not completely sure about this). I researched the different version and thought that v4.3 or v4.4 would be the final goal. This lead me to finding a path that required going through v4.0 to get there (please correct me if I have drawn the wrong conclusion on this). I could not find a way to back up the OS without stumbling on the instructions to either root the phone and/or wipe the data and cache to install something.
What I have done so far:
1). I paid to have my phone rooted. The apps I installed would not back up the entire OS and my recovery did not have an option to do that.
2).I followed [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g instructions. I was able to back up the entire rom from the red recovery.
3).Next I followed the [Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G (07/28/2012) instructions. I was now up in the v4.0.4 OS but did not have any of my applications or any of my old data.
4). I redid step 2 and restored the backup I made and was back on v2.3.6 again.
5). I installed fx w/root, Easy Back, then step 3 and got some of what I wanted but no apps. So step 4 again. I did this again with My Backup Root (MBR). I had a backup of my apps this time but they would not install in v4.0.4. So I did step 4 once more.
And yes I have been bitten by a boot loop. I did something wrong after I got it to 4.0.4 once. Not sure what it was.
Questions:
1). Is (was) there a way to back up the OS(ROM) from my vanilla v2.3.6 so I had a true representation of my original phone? Seems like a bit of a catch 22.
2). When I was on v4.0.4, I could not find settings/application to change both my USB settings and Playstore options. This caused the restore to fail because it was not from the playstore. I was able to use fx to find the backup file, select an apk file and try to restore it that way. It told me it was not a playstore app, but gave me a link to settings/Application so I could change it. Then I restored the app successfully. Then I went back to MBR and tried to restore the data for that app, it failed. Now that the Playstore option was turned off, I tried to restore from MBR. This went successfully but the restore of the Data failed because the app was not installed. I am thinking that there is a difference in the folder structure that is causing this (maybe to do with MTD). I was not able to turn on the Setting/Application/Playstore option. Where did the Settings/Application option go in v4.0.4?
3) Is there a way to backup up applications from v2.3.6 and restore them to v4.0.4 (or any 4.0 + version)? I could do it one at a time from the MBR backup but not the applications data.
4). I noticed that in v4.0.4 there was a screen after the first Samsung one that said Galaxy S. Can this be changed?
5). After the Galaxy S screen (again in v4.0.4) came a screen with a stickman and real intense flashing. Can this be changed?
6). How can I find the most stable ROM to use? is there a list of available ROMs all the way to v4.4?
I am sure I will have more questions, Thanks
Shoraht said:
Hi,
Background:
I am a retired software engineer. I worked on the windows platform and focused on the Visual Basic family of code though I was familiar with many languages from assembly to C. I am very familiar with the programming jargon but find myself at a loss when reading to posts here, so bear with me if I don’t have a complete grasp on the terminology.
My Story:
I have an AT&T Samsung Infuse with android v2.3.6 and have been very happy with it. This is my first smartphone and didn’t pay much attention to how it worked until now. I bought an irrigation controller that has an app for the phone. After installing the controller, I found out the app only runs on v3.0 or newer (mine is v2.3.6). So, here I am trying to upgrade my phone to a newer version so the app will work (trying not to buy a new phone for this). My first goal was to back up everything, so I spent a number of days reading threads here trying to understand what I needed to do. I discovered that v3.0 is a tablet only OS (not completely sure about this). I researched the different version and thought that v4.3 or v4.4 would be the final goal. This lead me to finding a path that required going through v4.0 to get there (please correct me if I have drawn the wrong conclusion on this). I could not find a way to back up the OS without stumbling on the instructions to either root the phone and/or wipe the data and cache to install something.
What I have done so far:
1). I paid to have my phone rooted. The apps I installed would not back up the entire OS and my recovery did not have an option to do that.
2).I followed [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g instructions. I was able to back up the entire rom from the red recovery.
3).Next I followed the [Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G (07/28/2012) instructions. I was now up in the v4.0.4 OS but did not have any of my applications or any of my old data.
4). I redid step 2 and restored the backup I made and was back on v2.3.6 again.
5). I installed fx w/root, Easy Back, then step 3 and got some of what I wanted but no apps. So step 4 again. I did this again with My Backup Root (MBR). I had a backup of my apps this time but they would not install in v4.0.4. So I did step 4 once more.
And yes I have been bitten by a boot loop. I did something wrong after I got it to 4.0.4 once. Not sure what it was.
Questions:
1). Is (was) there a way to back up the OS(ROM) from my vanilla v2.3.6 so I had a true representation of my original phone? Seems like a bit of a catch 22.
2). When I was on v4.0.4, I could not find settings/application to change both my USB settings and Playstore options. This caused the restore to fail because it was not from the playstore. I was able to use fx to find the backup file, select an apk file and try to restore it that way. It told me it was not a playstore app, but gave me a link to settings/Application so I could change it. Then I restored the app successfully. Then I went back to MBR and tried to restore the data for that app, it failed. Now that the Playstore option was turned off, I tried to restore from MBR. This went successfully but the restore of the Data failed because the app was not installed. I am thinking that there is a difference in the folder structure that is causing this (maybe to do with MTD). I was not able to turn on the Setting/Application/Playstore option. Where did the Settings/Application option go in v4.0.4?
3) Is there a way to backup up applications from v2.3.6 and restore them to v4.0.4 (or any 4.0 + version)? I could do it one at a time from the MBR backup but not the applications data.
4). I noticed that in v4.0.4 there was a screen after the first Samsung one that said Galaxy S. Can this be changed?
5). After the Galaxy S screen (again in v4.0.4) came a screen with a stickman and real intense flashing. Can this be changed?
6). How can I find the most stable ROM to use? is there a list of available ROMs all the way to v4.4?
I am sure I will have more questions, Thanks
Click to expand...
Click to collapse
1. when updating unless you have a google account synced for contacts and apps....it all disappears when you jump from gb to ics to jb to kk
2.the only apps that will back up to the google account will be ones downloaded from the playstore..minus the data
3. that galaxy s screen will stay all the way to 4.4.3 kk
4.you can always change the bootanimation in custom roms (the stickman screen)
5.CarbonRom so far most stable 4.4.3 kk rom https://carbonrom.org/downloads/?device=infuse4g&type=nightly flash with these gapps http://forum.xda-developers.com/showthread.php?t=2397942
6. after a certain point you cant flash a GB backup on KK cwm cause it will cause brick so if you want to go back to stock use heimdall or odin to do so
7.most of the apps on a gb roms wont run on ics or higher same with ics apps and jb apps
6th_Hokage said:
5.CarbonRom so far most stable 4.4.3 kk rom https://carbonrom.org/downloads/?device=infuse4g&type=nightly flash with these gapps http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
Thanks for the reply
Can I go directly to 4.4.3 from 2.3.6 or do I need to step through 4.0.x like the others? I can't seem to find any specific instructions for them.
There are only nighty's at that link, no releases. How do I know what version they are (4.4.2/4.4.3)? I think it is the one dated 4/19/14.
Thanks again.
Shoraht said:
Thanks for the reply
Can I go directly to 4.4.3 from 2.3.6 or do I need to step through 4.0.x like the others? I can't seem to find any specific instructions for them.
There are only nighty's at that link, no releases. How do I know what version they are (4.4.2/4.4.3)? I think it is the one dated 4/19/14.
Thanks again.
Click to expand...
Click to collapse
go to the channel log https://docs.google.com/document/d/1Zcp6iVWVw_7iH-ErnKgkYy3r5QuqV8PHFoQMb8hoBwQ/pub if you look at it itll tell you updating to 4.4.3 no nightlys or something like that but right now all the latest nightlys are 4.4.3......sorry not linking you to that before and they may be nightlys but they are stable im running the latest one at the moment
---------- Post added at 01:57 PM ---------- Previous post was at 01:39 PM ----------
and som infuse phones have been able to jump to kk from stock with red cwm with lagfix turned off.....http://forum.xda-developers.com/showthread.php?t=2773833 look here for som more info
6th_Hokage said:
go to the channel log https://docs.google.com/document/d/1Zcp6iVWVw_7iH-ErnKgkYy3r5QuqV8PHFoQMb8hoBwQ/pub if you look at it itll tell you updating to 4.4.3 no nightlys or something like that but right now all the latest nightlys are 4.4.3......sorry not linking you to that before and they may be nightlys but they are stable im running the latest one at the moment
---------- Post added at 01:57 PM ---------- Previous post was at 01:39 PM ----------
and som infuse phones have been able to jump to kk from stock with red cwm with lagfix turned off.....http://forum.xda-developers.com/showthread.php?t=2773833 look here for som more info
Click to expand...
Click to collapse
Thanks,
I missed your update
Shoraht said:
Thanks,
I missed your update
Click to expand...
Click to collapse
have you been able to update?
6th_Hokage said:
have you been able to update?
Click to expand...
Click to collapse
I will try tomorrow. I will post the results
Thanks.
6th_Hokage said:
and som infuse phones have been able to jump to kk from stock with red cwm with lagfix turned off.....http://forum.xda-developers.com/showthread.php?t=2773833 look here for som more info
Click to expand...
Click to collapse
Got RiseFox to try my method and it work out for him also and probably work for others too.. Skip ICS and JB
scmfxt said:
Got RiseFox to try my method and it work out for him also and probably work for others too.. Skip ICS and JB
Click to expand...
Click to collapse
i went back to stock to see if your method would work and it did even jumping to 4.4.4 kk
scmfxt said:
Got RiseFox to try my method and it work out for him also and probably work for others too.. Skip ICS and JB
Click to expand...
Click to collapse
OK, I am about to try this but have a couple questions. In other instructions, the clear cache (step 6a,b and c) is done before the flash, yours is after. What is the difference between the two methods? In step 3 you say "DISABLE vodoo lagfix and /system lagfix". I have CWM v2.5.1.3. I can see the option for vodoo lagfix but not /system lagfix. What is /system lagfix and where can I find this option?
[UPDATE] I found /system lagfix. it shows after selecting the voodoo lagfix option.
I am also making the assumption that because I got CWM v2.5.1.3 through [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g instructions, that I can skip step 1 thru 2c and start at step 3
OK,
Everything went well. Even better than I hoped. I can't remember what setting I changed to make this happen, but all the apps in playstore have been restored to the phone, even the free ones. I used Titanium to backup all my apps and then used it to restore the data for some apps like color notes. There is a setting that tells it to use the new locations instead of the original locations. I am a happy camper.
It will take a while for all this to finish, but this is what I was expecting.
I still can't find the equivalent option for Settings/Application from v2.3.6. Like, let me chose what USB mode when I plug it in? Most of the time I just use it to charge the phone. And where can I change the permission to restrict installing only apps from playstore?
Thanks your input.
Shoraht said:
I still can't find the equivalent option for Settings/Application from v2.3.6. Like, let me chose what USB mode when I plug it in? Most of the time I just use it to charge the phone. And where can I change the permission to restrict installing only apps from playstore?
Thanks your input.
Click to expand...
Click to collapse
Glad you got most everything working. The option you are looking for is under Settings > Security > Device Administration (heading), and it should be called Unknown Sources. Hope this helps.
Ok,
Now I am having a new issue. I can't seem to get any of the apps that move apps to the external sd to work. The option to move is missing in the storage section. I am running out of space in the 2gb partition. AppMgr III and App to SD can show me a list of apps that can be moved, but when selected, there is no Move button present. Am I using the wrong app for 4.4.3?
It would be nice if that 2gb partition could be made bigger.
Thanks for any advice.
Shoraht said:
OK, I am about to try this but have a couple questions. In other instructions, the clear cache (step 6a,b and c) is done before the flash, yours is after. What is the difference between the two methods? In step 3 you say "DISABLE vodoo lagfix and /system lagfix". I have CWM v2.5.1.3. I can see the option for vodoo lagfix but not /system lagfix. What is /system lagfix and where can I find this option?
Click to expand...
Click to collapse
It doesn't hurt to clear them and safer for new rom to boot up w/o residual data from previous version. Flashing from odin would wipe all data from your phone.. not your Internal SD card. Reason I did it after is because of the installing of sgs kernel flasher to flash Synthesis GB Kernel. If you didn't install anything then just wipe cache partition and dalvik cache are good enough.
[UPDATE] I found /system lagfix. it shows after selecting the voodoo lagfix option.
I am also making the assumption that because I got CWM v2.5.1.3 through [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g instructions, that I can skip step 1 thru 2c and start at step 3
Click to expand...
Click to collapse
Yes skip them if you already reached that part. The rest is simple enough to do once lagfix is disabled.
joel.maxuel said:
Glad you got most everything working. The option you are looking for is under Settings > Security > Device Administration (heading), and it should be called Unknown Sources. Hope this helps.
Click to expand...
Click to collapse
Thanks,
That solves the Application install option. I still need to find the USB connect option so I can select at connect.
OK, New problem,
Everything was working just fine. Then I unplugged the USB cable and went for a ride. No Mobile Data (no Internet). I checked all the settings That I know about (They moved them all of course) and it looks like everything is set right (though I am not an expert). Can anyone help me with this?
Thanks again
Shoraht said:
OK, New problem,
Everything was working just fine. Then I unplugged the USB cable and went for a ride. No Mobile Data (no Internet). I checked all the settings That I know about (They moved them all of course) and it looks like everything is set right (though I am not an expert). Can anyone help me with this?
Thanks again
Click to expand...
Click to collapse
Well, I found out that the APN was changed, not sure how. It is a good think my wife has the same phone that I can check or I would be going back to my stock image to find this.
Thanks,