Database Info

How do you make sure there's no evidence that you ever rooted your G1?

So earlier today I decided I wanted to take my phone off root because it had become really buggy so I followed these instructions from another thread:
"download this http://koushikdutta.blurryfox.com/G1/DREAIMG-RC29.zip unzip it and load it to the root of your sd card and reboot the phone holding down the camera and power key then follow the instructions in screen then reboot and wait for the update. how many more times must i type this? can you people not see the search button."
SOURCE: http://forum.xda-developers.com/showthread.php?t=478856&highlight=original+firmware
After doing this, my phone was working fine. Everything worked. For some reason like 2 hours later, my threaded txt messages started showing up in the wrong order. I called T-Mo and they had no solution so they're going to sen me a new one. I wanna make sure there is no evidence on the phone that it was ever rooted. How do I make sure? Thank you so much!

just make sure you updated to original firmware after you changed your fastboot images... that is... if you changed the fastboot images... then you are good to go.

I never messed with fast boot and all that, after I rooted it, I updated JF1.41 with auto rotate and multi touch. thats it. when I went to original firmware, literally I did exatly what he said with the DREAIMG.nbh file, and rebooted. ( Copied the DREAIMG.nbh file to root of SD, restarted with camera+power, ran the update, rebooted) Was there a step I missed?
The problem now is, I dont wanna change much at this point bc if it fixes the threaded txt issue, then theyll prob charge me for the new phone if the txt problem is fixed.

find the SPL thread(sticky) and make sure that your bootloader screen looks like the stock one and you should be fine as well, RC29 already wipes everything else

my threaded txt messages were going in a crazy order last night. but i assumed it was cuz of daylight savings time lol. my g1 to g1 messages would show up in correct order. but everyone else' messages were in screwy order.

yeah its because of DST. T-mobile changed the clocks to early lol. Either that or the g1 screwed something up.

we will see what happens
I posted this in another thread so ill be brief ...
due to a hardware error I returned a white g1 which I had rooted and tricked out with JF's RC33 a theme and the dev BL... I was feeling lazy so I just wiped it and made sure it was back to the stock theme and sent it off with a flat battery, I dont think they will scrutinize them much, we will see, most of the time you play stoopid say you took it to a store and they did some stuff, whatever, PROVE IT, pry my replacement from my cold dead hand.
ill post if I get some response to my tricked out g1 returned due to a bad bt radio
bhang

is it ahome????????????????

after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42

Oh. Ok. Thanks for telling us.

nabzilla1990 said:
after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42
Click to expand...
Click to collapse
First of all... let me address this before someone rips you apart here. Your question (if it is one) is a bit difficult to read. I am certainly not an english teacher but maybe a period here and there would make it easier to understand. Because I honestly don't know if you are asking a question, stating that you're having a problem with reflashing, going back to factory settings or other. I mean I had to read it 5 times!
Secondly... if you do a factory restore from the settings and you get the flashing android on boot you should let it keep flashing for a few minutes. You need to be patient because it is wiping all of your previous data/settings and restoring them to default.
Third. If it stays on the flashing android for longer then say three to five minutes (depending on how much you need to wipe) then go ahead and boot up in recovery mode and do a wipe from there. If you still get stuck on the flashing android then yes... reflash.
Fourth. Do not assume it is an app that causes this problem unless you are CERTAIN of it. Hundreds if not thousands of people have downloaded this app (including myself) and have not had a similar problem. Maybe do a search for the app name and read what people are saying about it. If it is the app then believe me you won't be the only one commenting. If you're lucky there will be a fix so you won't have to wipe or reflash.
Finally... every so often (especially before making a major change like apps to sd, themes, etc) it'll be a good idea to do a backup with Nand so even if you do end up messing something up (by app or user error) you can always reflash your image to your phone.
Good luck!

EDIT: Whoops! Wrong thread!

I'm very sorry for my poor English but my story is after installing ahome
everything was fine until I rebooted my phone. After rebooting the phone I
tried dialing a number and when I pressed a number once the it would dial
the number twice for example when dialing 7 instead of only dialing the
number 7 it would dial 77, or when using useful switchers turning off the wifi I
would try to check the wifi on but with one push it would check and uncheck
the wifi. Later I did a factory data reset and rebooted the phone I couldn't get
past the flashing android. I reverted back to stock rc33 just in case its a
hardware problem I can let t-mobile know thanks for the replies

i doubt it's a hardware problem.
i had the same problem, coincidentally after installing aHome; i was unable to get past the "flashing android" screen. The first reboot that i did, though, was after using the JF auto-updater app, so i'm not entirely sure where the problem lies.
long story short, i wiped my system, and am now in the process of installing Windows and the Android SDK to my system so i can do a restore.

thanks im gonna go back to root then

yeah, aHome still has lots of thigns to be fixed specially that force close issue every time u return to home :/ i liek dxtop better dont feel like scrolling tru 10 pages like the iphone..

Wake issues with newer ROMS

I am posting a new thread because I'm experiencing the issue with several diffrent ROMs so obviously it's a general issue not a ROM specific one. Also I have read through countless pages of posts with no luck so hopefully someone can shed some light. Over the past few days I've flashed (forgive my spelling) dude's .5, ravenge, cynogen 3.4 and I have been having issues with the phone not waking after either I put to standby myself or the screen times out. I know it's not an issue with my phone or card because I go back to virtudude's ROM without the issue. I have tried everything, formatting my partition, ext2, ext3, wipe, no wipe, everything I can think of and still have the issue accross mutiple ROMs. I know it's not just me because my friend with a G1 is having the same issue, as well as many people posting in the threads. Can someone please point me in the right direction to fix this issue please?
My phone:
G1 with JF 1.42
Newest SPL 2005
Newest 26I radio
8gb SD card, class6, ext2 or ext3 partition (same issue on either)
Thanks in advance for any help!

me too
I noticed this same problem, its related to wifi, when I disable wifi my phone wakes up, also I have searched everywhere too for a solution. I think the compiled wifi deiver in these roms are not compiled right. So its either this or some other problem.

Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.

I am doing a test, im leaving wifi on while the screen is off in settings, will report back

This happens to me also but its only with hero I also have the new radio and spl. I can run hero with no problems as long as I don't use apps to sd or lucids txt. The wired thing is that after I use any apps to sd it works great but only for a day sometimes a few hours. Then I will start to see freezing up or it won't wake up at all, unless I reboot or pull battery. I've tried to reformat my card, resize my partition I'm also lost on this one fresh out of ideas.

Do you guys think it might have somthing to do with the sdcards? Im useing a 4g class 6 transcend micro SD, its only about 2 weeks old. Jason what other roms gave you these problems?

defconoi said:
Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.
Click to expand...
Click to collapse
I personnally don't see the correlation between locking and WiFi, I was at work the other day and flashed a ROM and it was doing it. I have my WiFi off at work so that wouldn't have been the case that day. I do notice the bottom of the phone getting hot though.
In response to the other person with the sd card question I really don't think it's that as I have a class 6, have formatted every way possible. Unless the issue has to do with apps2sd, I use apps2sd on every ROM.
Glad to see I'm not the only crazy one on xda!

joe v said:
Jason what other roms gave you these problems?
Click to expand...
Click to collapse
Almost every ROM to come out in the last couple weeks has done it. TheDude's .5, Ravenge's ramjet, Cyanogen's 3.4.1, and the Cyanogenized Rogers ROM.
You know looking at these the one thing these all have in common is being Cyanogenized. And the only ROM to come out in the past few weeks that hasn't had that issue is Virtuedude's Rogers ROM, which isn't Cyanogenized.
If any devs are reading this thread if you can make a version of your most recent ROM without Cyan's build kernel and boot and see if that helps. I'd be happy to test it for you to try and get to the bottom of this. If you wanna shoot me an email hit up jasonsyn at gmail.

I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.

indiekid97 said:
I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.
Click to expand...
Click to collapse
Yeah but I've had the new SPL and Radio for a month and this just started a week or so ago...

I am having the exact same issue. I usually have wifi bluetooth and 3g disabled (saves battery) I noticed this started after grabbing the new spl, ever since it's been freezing in standby randomly. I'm going to try Virtudude's rogers rom to see if the combination of Cyanogen's boot image and the new spl is causing the freezing. Hopefully seeing as Virtududes rom isn't based on Cyanogen's boot image it won't freeze. I'll report back with my results.

I thought my button got worn out. I never had the symptoms on rc33. When I switched to cupcake back during hatkuros prime just before dudes first releases I noticed it. I thought if it wasn't my button it might be somehow related to jf kitchen since almost all my roms touch it at some point. Just speculation though, donno what causes it.

Hey what recovery image are you all running?
I'm gonna flash the new Cyanogens 1.2 Recovery image and see if that's the issue.

Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.

Jason Syn said:
Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.
Click to expand...
Click to collapse
try holding down menu or the power button...i had this issue and my sd card would "unmount unexpectedly" and then this ended up into my sd bein fried

for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.

dbhatesyou said:
for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.
Click to expand...
Click to collapse
Ok I'll be happy to but I'm a linux virgin...would you mind giving me step by step in adb and I'll give whoever the log that can make sense of it.

This happens to me also on The Dudes Roger built. I don't have WiFi enabled so it isn't that it seems pretty random and just I get no response from the phone and have to so the soft reset (Call Menu Power) and then it'll work again. Normally only happens like once a day though so I can live with it but it is a inconvenience and can be annoying if it does it when you actually need to use your phone for something with some importance.

well if you're on linux and have it to where adb runs from terminal , just type
Code:
adb shell reboot
but before all that ddms (dalvik monitor) just type ddms in terminal it will boot up and show everything your phones basically working with.. and issues,
now if your linux terminal doesnt work well with adb (cant get it to work , google "50-android.rules" and "51-android.rules" n see if those help, and also set your echo path right )
now if you're on windows just hit windows key + r type cmd , and set yourself into the sdk/tools directory, then type ddms that will start the dalvik monitor (try and save a log) make sure the log saves before rebooting the phone, when you're done you can just ctrl+c and type adb shell reboot, and your phone should reboot.
[just the basic]

i've ran into this intermittently...most of the time while using the browser or using the onscreen keypad during a phone call.
I'm on JF CRB43(which is 1.51 i think) with the Hard SPL and JF Recovery.
Only thing I've been able to do to get the phone to wake up is wait. eventually it'll come around. or pull the battery, which i try not to do.

Anybody want to be a guinea pig

http://forum.xda-developers.com/showthread.php?t=743506
I was wondering if anybody was willing to try this on their captivate and see if it worked for us or any dev's willing to try and port this over to our side.
seems to be working fairly well for them
edit: their hitting 1400+ Quadrant scores and all functions work on their phone from what I see
UPDATE 3:
Tutorial:
-1. Download VibrantDeodexed.zip from thread posted.
1a. Flash stock Odin3 rom. (For the Captivate).
1b. Root
2. Download ROM Manager from Market.
3. FlashClockworkRecovery for Captivate in ROM Manager.
4. Transfer the VibrantDeodexed.zip to /sdcard/ root.
MAKE SURE YOUR ext3 PARTITIONED SDCARD IS INSERTED
5. Reboot to Recovery (in ROM Manager)
6. Install zip from sdcard>choose zip>VibrantDeodexed.zip
7. After it finishes, reboot and be patient. The initial startup takes some time...
Added Fortune090 instructions on how to get this on our captivates. KUDOS to him for testing it out for us
Please note this is still very EARLY and major problems could happen if you do this wrong.
We're not responsible. This is beta
UPDATE 4: I updated the tutorial to a more extensive one, but there is another thread
http://forum.xda-developers.com/showthread.php?t=747397
that is more promising, no gps problem. Waiting for an update version for easier install

The Captivate and Vibrant function completely differently as far as those speed fixes go.
Read this:
http://forum.xda-developers.com/showthread.php?t=740747
I was hitting around 1800 in Quadrant, but the fix wasn't showing any real-world speed increases, and had some bad issues regarding the mic and voice calls, along with wake up lag.
I'm not saying this won't work, but I'm assuming it won't work well or function the same way...
EDIT: Guess I can try it though, seeing as no one else has. Glad my phone's finally communicating with Odin properly so I don't have to worry about the brick I did before... I'll update with any issues.
UPDATE1: Rebooted into recovery and tried to reinstall packages to install the update, and it failed. Trying another one of the methods described to see if they'll work.
UPDATE2: Got it installed (I think), but it seemed to go way too fast and kept going between recovery and rommanager. Phone's loaded and it's running Quadrant now to see if there's any change.... Didn't think so. Still getting in the 900's. Time to continue trying... haha. I originally used Clockwork for Captivate, so that could have been the problem trying Vibrant to see if that'll make a difference...

thanks for the try, I guess we'll just have to wait until something more substantial gets worked up for our side

nammyczc said:
thanks for the try, I guess we'll just have to wait until something more substantial gets worked up for our side
Click to expand...
Click to collapse
I'm guessing that you'd have to flash the Vibrant ROM first, and I've known that's caused issues for Captivate users. I'm still trying with the Captivate stock Odin ROM though... Will definitely post if I have any success...
EDIT: I actually think I found my mistake... hold on...
EDIT2: Yes... definitely was a dumb mistake. It's copying the files now. Waiting for it to boot. Was told it takes awhile for the initial boot...
UPDATE: Ok, everything booted up fine, and I can tell this is the Vibrant ROM. The speed fix wasn't applied though. Might be because my external is partitioned with ext4. Could that be the problem? I didn't see any script load that didn't before...
UPDATE2: Reformatted my external to ext3 and got results!!! Quadrant got to 1446! Time to check some real world applications now. (phone call, bluetooth, I know wi-fi works, etc) I'll update with news.

Keep us updated. I don't know if the ROM includes the radio firmware, so make sure to have the stock captivate radio.

I'd love to see a speedtest.net to see if HSUPA works correctly!

Ok wow. I'm impressed. I'm seeing actual speed increases and so far everything is working perfect. No wake up lag, no static in phone calls, Quadrant scores are way up, plus you get some of the advantages of the Vibrant rom without having to flash it. (ie. OPTION to allow non-market apps, unlocked Market...)
So far it's a thumbs up all the way!
Tutorial:
1. Flash stock Odin rom (For the Captivate).
2. Download ROM Manager from Market.
3. Install the Captivate Clockwork for Captivate
4. Transfer the VibrantUpdate.zip to /sdcard/ root.
MAKE SURE YOUR ext3 PARTITIONED CARD IS INSERTED
5. Reboot to Recovery (in RM)
6. Install zip from sdcard>choose zip>VibrantUpdate.zip
7. After it finishes, reboot and be patient. The initial startup takes some time...
8. ENJOY!
Currently working on getting rid of the T-Mobile startups and shutdowns, but that takes no time at all. Thanks for this!!!
EDIT: Problem. GPS no longer functions at all from what I'm seeing. When using my location in Maps, the application freezes... Going to check the *#*#1472365#*#* settings to see if anything there's causing the problem...

madjsp said:
I'd love to see a speedtest.net to see if HSUPA works correctly!
Click to expand...
Click to collapse
Did a speed test...
1898 dl
341 ul
Is that HSUPA ratings or standard? I'm not sure...

Sorry for the triple post, but another thing I noticed... Titanium Backup is not recognizing all of the T-Mo bloatware or ANY of the installed applications... Anyone have any idea why?
Also, Swype FC's after about 3 seconds, but I'm assuming a reinstall will solve the problem... Haven't checked quite yet. Still testing a bunch of things.
EDIT: TB problem solved. Go to Problems? from the main menu, Yes do it. Everything showed up after it updated BusyBox.
Still trying to figure out the GPS problem...

Fortune090 said:
Sorry for the triple post, but another thing I noticed... Titanium Backup is not recognizing all of the T-Mo bloatware or ANY of the installed applications... Anyone have any idea why?
Also, Swype FC's after about 3 seconds, but I'm assuming a reinstall will solve the problem... Haven't checked quite yet. Still testing a bunch of things.
Click to expand...
Click to collapse
I believe you have to click on "problems?" in T.B , its the middle button on the main screen i believe it say problems or in the menu

mykenyc said:
I believe you have to click on "problems?" in T.B , its the middle button on the main screen i believe it say problems or in the menu
Click to expand...
Click to collapse
Yeah, got it.
GPS, GPS, GPS...
Changed the settings in the 1472365 menu, and nothing worked. Anything that involves GPS crashes the second you tell it to use it. Phone doesn't freeze though.
QUICK: Can someone post the STOCK shutdown files? Sound: /system/media/audio/ui/shutdown.ogg Video (folder of .pngs): /system/media/shutdown
Would be greatly appreciated. Want to get rid of the T-mo branding the update applied...

WOW, I'm amazed that it works, thats great to here there have been little problems except GPS function. It could be the drivers for vibrant are different for captivate? I'm not really sure I dont know much software but that seems like the most basic explanation I can think of.
EDIT: Did you try deleting the GPS data and starting over from scratch? or gps test from the market? its possible that GPS just needs to reset itself? or something...

nammyczc said:
WOW, I'm amazed that it works, thats great to here there have been little problems except GPS function. It could be the drivers for vibrant are different for captivate? I'm not really sure I dont know much software but that seems like the most basic explanation I can think of.
EDIT: Did you try deleting the GPS data and starting over from scratch? or gps test from the market? its possible that GPS just needs to reset itself? or something...
Click to expand...
Click to collapse
Hmmm... ill try that. Thanks! I'll update with what happens.
UPDATE: Nothing... froze again and GPS Test crashes at startup...
Sent from my Captivate

Thanks for your work, looking forward to what comes from this
sidenote I would upload the sound for you but not sure where its located through astrofile...
EDIT2: http://www.mediafire.com/?tcyzaykkkfphxtg that rar is shutdown picture file and sound

Hm, could be possible we need to get the gps stuff from the captivate kernal and not the vibrants?
EDIT: so I emailed the OP from the vibrant one, for the original mod, seeing if he can help us out with ext4 problem and the GPS problem as well. Hope we can get this fully up and running

nammyczc said:
Hm, could be possible we need to get the gps stuff from the captivate kernal and not the vibrants?
EDIT: so I emailed the OP from the vibrant one, for the original mod, seeing if he can help us out with ext4 problem and the GPS problem as well. Hope we can get this fully up and running
Click to expand...
Click to collapse
Alright sweet. Hopefully we see this completely take off. Not using the GPS at all, I'm seriously enjoying it, but I know it's a problem for everyone else.
Sent from my Captivate.

question for reverting back to stock is the same method in the forums? or will it be different

Can you use ROM manager's backups to undo the ROM flash? I want to make sure that I can go back to my stock AT&T ROM after I test out this vibrant ROM.

thats pretty sweet.
just gotta get the gps up and going now.

I'm not sure... When I flash I use Odin.
Another minor bug I've noticed is that with texts, the notification doesn't go away until you clear all notifications. Not TOO big a deal, but it didn't happen with my stock firmware. Might be a Vibrant thing... idk...

[Q] Lag

I have the charge running FP5 firmware and the Tweaked ROM 3.0.
I've run into a situation where the phone has become rather laggy and buggy.
Example: Click the notification for voicemail...wait 30 seconds and phone dials. or Phone battery dies. I plug it in and it charges up to 30%, then starts getting very laggy and non responsive. I reboot and am told battery power is really 50% and phone is good to go.
I'm used to rebooting the phone at least once a day or more. I'm looking for a way to correct the problems and bring the phone back to how it was when I last upgraded and and loaded the ROM... too bad I didn't backup the phone at that point. Anyways...I know that if I reload the firmware and apply the ROM, everything will work correctly again but I'll spend hours tweaking the settings to add custom ringtones and photos to contacts.
Is there some cache or data I can clear to fix this without clearing everything and starting over?
Mike
P.S. I'm keeping this phone until Verizon allows me to upgrade and keep unlimited data or the phone dies and I have to get another.

beavermjr said:
I have the charge running FP5 firmware and the Tweaked ROM 3.0.
I've run into a situation where the phone has become rather laggy and buggy.
Example: Click the notification for voicemail...wait 30 seconds and phone dials. or Phone battery dies. I plug it in and it charges up to 30%, then starts getting very laggy and non responsive. I reboot and am told battery power is really 50% and phone is good to go.
I'm used to rebooting the phone at least once a day or more. I'm looking for a way to correct the problems and bring the phone back to how it was when I last upgraded and and loaded the ROM... too bad I didn't backup the phone at that point. Anyways...I know that if I reload the firmware and apply the ROM, everything will work correctly again but I'll spend hours tweaking the settings to add custom ringtones and photos to contacts.
Is there some cache or data I can clear to fix this without clearing everything and starting over?
Mike
P.S. I'm keeping this phone until Verizon allows me to upgrade and keep unlimited data or the phone dies and I have to get another.
Click to expand...
Click to collapse
You mean Tweaked 3.2, right... if not first upgrade to the 3.2 version of the ROM... it is the current FP5 option.
There is a build.prop thing commented out at the bottom that should force launcher into memory (supposed to help with screen redraw issues, but might also help with general responsiveness). I think you could do it from root explorer, just edit the file, scrool down, read comments, when you find one that sounds like what I said just remove the "#" from the line below it.
re-installing tweaked might really help...
but you might try going into CWM and wiping cache only... NOT data & cache... JUST CACHE... that helped me when i had "funky" things going on on a different device/ROM worth a try.
Finally, you should always take a CWM backup, Nandroid, before poking around....
Also... check swappa for relatively cheap phones with no ties to VZW contract it is where i picked up the GN2 (if it is rooted and you don't want to show it off at the corp store, just call customer support say you are too busy store hours. They will send you the micro/mini SIM via FedEx.
Of course take what I say with a grain of salt... I am just a crazy guy from the internet
(oh great XDA... please correct me if I've misspoken)

Thanks for the info. I never did load Tweaked 3.2. I will put that on the back burner as I don't want to reload all the settings. Maybe I can load it without wiping data. Do you know? For now I will try wiping the cache and see if the phone improves.
Someday I'm gonna have to explore the latest OTA and a new ROM. I'm getting tired of ignoring the update message. either that or learn how to shut the message down. any recommendations on a ROM for the new OTA?

beavermjr said:
Thanks for the info. I never did load Tweaked 3.2. I will put that on the back burner as I don't want to reload all the settings. Maybe I can load it without wiping data. Do you know? For now I will try wiping the cache and see if the phone improves.
Someday I'm gonna have to explore the latest OTA and a new ROM. I'm getting tired of ignoring the update message. either that or learn how to shut the message down. any recommendations on a ROM for the new OTA?
Click to expand...
Click to collapse
I will never tell someone "don't say it click the button"... However, I'm like pavlov's dog clicking the button is appreciated...
Not sure about a dirty flash... Never tried it. I got turned on to Root and Such well after FP5 and Tweaked 3.2 came out.
If you give it a go... You could retain much via Titanium Backup. Or just send a CWM Backup/Nandroid on the SD Card before playing around.
Either way...
There has to be a proper stop notification how to thread around here somewhere!
Cliffs Notes:
From a Root Friendly File Explorer (Like Root Explorer HERE, it is worth the $)
edit a line in "/system/build.prop"
Find
ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/FP5:user/release-keys
replace the FP5 with FP8 so it reads:
ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/FP8:user/release-keys
NOTE: BE VERY CAREFUL NOT TO HOSE THE PERMISSIONS (If I recall some of the other "freebie" root file explorers break the permissions... Best to find that a real thread with all the details if you are not 100% confident.)
Also feel free to double check my facts... I'm just a crazy guy from the internet!
Good luck!
Edit Alert:
PS. While poking around at the tweaktools back-end, I noticed there were some mods that specifically addressed lag (I have little to no experience with them though... Just FYI...

beavermjr said:
Thanks for the info. I never did load Tweaked 3.2. I will put that on the back burner as I don't want to reload all the settings. Maybe I can load it without wiping data. Do you know? For now I will try wiping the cache and see if the phone improves.
Someday I'm gonna have to explore the latest OTA and a new ROM. I'm getting tired of ignoring the update message. either that or learn how to shut the message down. any recommendations on a ROM for the new OTA?
Click to expand...
Click to collapse
yes, you can flash tweak 3.2 over 3.0 without wiping data. not sure if it comes with the updated kernel, but I would certainly do that as well.
in terms of lag, try the crossbreeder mod on XDA - worked for my charge!