On my 4th G2x. Same problems as the others. Reboots on its on, sleep of death. In fact this morning I was talking on phone and it shut down. I had to remove battery and reboot.
I called Customer Service that has always been super nice. This time they said, oh, since this is your 4th and this one just in 6 days I can't help you I have to send you to Tech. The Tech guy basically said "known software problem, sending replacement won't do any good. Can't give you different phone. Maybe it is your SD card and apps you have loaded. He actually told me Facebook app could cause it to shut down. Said to reset to factory, remove SD card and use it for 3 days with no apps. After 3 days if all is well then start adding apps. I asked what if it has problems during the 3 days? He said, 'there is nothing we can do. I will report this to LG and they will send out an update. I don't know when but they will update the software".
WTH?! So I am done. I will do the root. Now i just need to read all these great threads to figure out how and which version! Wish i could just pay one of you to do it for me!
Thanks for letting me rant.
I've been running stock since August with no issues but I really wanted the LG Camera app so I installed CWR and flashed the WeaponX rom with no issues. Everything works and it's even smoother then stock Gingerbread. Just follow the directions to the T and the process should take less than fifteen minutes if you have all your files ready to go.
Enjoy!
seangprice said:
I've been running stock since August with no issues but I really wanted the LG Camera app so I installed CWR and flashed the WeaponX rom with no issues. Everything works and it's even smoother then stock Gingerbread. Just follow the directions to the T and the process should take less than fifteen minutes if you have all your files ready to go.
Enjoy!
Click to expand...
Click to collapse
Thanks! Which directions did you follow? There are a number of threads here.
The directions are a bit confusing as they reference other threads and then have comments stating this step is now obsolete. etc. Seems like I first need to get the ROM Manger?
https://market.android.com/details?id=com.koushikdutta.rommanager.license&feature=search_result
Correct?
i followed this http://forum.xda-developers.com/showthread.php?t=1060715 and was fine. this was my first root as well.
http://forum.xda-developers.com/showthread.php?t=1056847
I used this method to NvFlash and install Clockwork recovery which is the basic software you need in order to flash ROMs. You do not need ROM Manager. Once you've done the NvFlash and installed CWR you can copy your ROMs to the SD card or phone storage and flash through Clockwork Recovery. Make sure you backup your stock install through CWR prior to flashing anything new so you can return the phone to a usable state.
As always follow the directions verbatim, some steps take time as well. Also make sure your battery is 100% charged... If it dies during any portion of the process bad things can happen.
I had all of those issues until I flashed cm7... then the issues became very minimal... I once had 8 reboots in a day on stock rom, during phone calls and everything... You are definitely taking a step in the right direction
P.S. my wife has completely stock phone on stock rom and has Facebook app with no issues, she just got lucky I guess
To OP: do you have 2.2 or 2.3 installed as your stock rom... read carefully there are different instructions for both
Never use ROM Manager. Even if it worked perfectly on our phone I still would never recommend it. I've seen it cause more harm than good.
Anyways, you don't even technically need root to flash a ROM.
Just NVFlash CWM. After that you can upgrade to the latest CWM via ADB. Then flash your desired ROM. I suggest CM7.
yeah, you know ROM manager... now forget it. Use NVflash and clockwork
I got myself in trouble!
I followed instructions and all went well. I installed the GB, no problems. No I was brave so I thought I would try the Cyanogen mod. It too installed fine. I don't like it. Now i can't get rid of it! I tried reinstalling the GB and the cyanogen won't go away! i tried restore to factory, but it won't go away!!
Please lend me your advice on how to remove Cyanogen mod!
donbeth said:
I got myself in trouble!
I followed instructions and all went well. I installed the GB, no problems. No I was brave so I thought I would try the Cyanogen mod. It too installed fine. I don't like it. Now i can't get rid of it! I tried reinstalling the GB and the cyanogen won't go away! i tried restore to factory, but it won't go away!!
Please lend me your advice on how to remove Cyanogen mod!
Click to expand...
Click to collapse
Then just wipe and flash a new ROM.
Make sure you wipe data, cache, dalvik then format system before flashing new ROM.
Clearly I am a dunce.
I uninstalled the driver on pc. Did a reinstall. Flashed ROM again. Installed GB zip. rebooted and the dang Cyanogen MOD is still there!
I even went over all steps again, this time flashing back to stock. Still Cyanogen MOD is boots up
donbeth said:
Clearly I am a dunce.
I uninstalled the driver on pc. Did a reinstall. Flashed ROM again. Installed GB zip. rebooted and the dang Cyanogen MOD is still there!
I even went over all steps again, this time flashing back to stock. Still Cyanogen MOD is boots up
Click to expand...
Click to collapse
Yes yes you are when you flash a new rom wipe data wipe cache wipe dalvik and wipe system
Sent from my LG-P999 using XDA App
i remember, I followed this video.
http://theunlockr.com/2011/05/03/how-to-load-a-custom-rom-on-the-t-mobile-g2x/
to install a new rom
remember: (once you've copied the zip on sd card, power the phone to enter into clockwork and steps)
1. back up and restore
2. wipe data/ factory reset
3. install zip from sd card
so far, it hasn't failed me
you can skip the first one, but shouldn't
Just download Weapon if you want to go back to stock. Its Stock with a few needed tweaks and fixes. Very stable and no issues.
G2x - 2.3.7 CM7
Transformer - 3.2 Revolver OC/UV
The reboot issue were in all my G2X(3). Only rom that fixed that was Weapon G2X. Running a custom rom is the way to go with this phone, otherwise you'll go through 100 replacements with same issues.
Today I did an exchange for my brother's line which he has the G2X and the rep told me I could get a brown color G2X because they no longer carry original color or a Sensation. (Not sure what he was talking about brown color because I thought all G2X were the same color other than the white floating around)
So I decided to just get the Sensation, I know it's got issues of it's own, but will give it a shot because I want the G2X to just be a memory of the past.
This phone could have been a beast, but will never live to it's full potential.
Good luck and if you need to exchange again and you don't mind getting a Sensation I would suggest bringing that up to the rep.
Hercules Hercules!!
I'm a little confused...I've been using ROM Manager just fine...?
Neejay said:
I'm a little confused...I've been using ROM Manager just fine...?
Click to expand...
Click to collapse
If you screw up and can't boot up, ROM manager cannot get you into recovery. Only an NV flashed clockworkmod recovery will boot up in the event of a boot loop.
Sent from my LG-P999 using xda premium
Neejay said:
I'm a little confused...I've been using ROM Manager just fine...?
Click to expand...
Click to collapse
You don't have recovery with Rom Manager, yeah it flashes all the roms but if you get into a bootloop or worse then you are SOL.
Hercules Hercules!!
Neejay said:
I'm a little confused...I've been using ROM Manager just fine...?
Click to expand...
Click to collapse
Rom manager works just fine. However, like previously said, you just need to NVFlash first for safety reasons.
From a complete stock G2x, NVFlash, Nandroid Backup, and flash a previously downloaded rom (Weapon or CM7 or MIUI or Eaglesblood or any of the other wonderful roms). Custom roms have root so THEN you can go to town with Rom Manager.
I use Rom Manager as my primary flashing service because it not only downloads them, but will automatically reboot into recovery, perform your desired wipe options, and flash. With CM7 it will automatically check for the latest GAPPS and flash it too in one fowl swoop.
Just have to NVFlash first.
I NVFlashed my neighbors G2x the day he got it and, while he didn't want to try custom roms just yet, we did a Nandroid Backup just for laughs. Now he's running MIUI.
Related
Need anybody's help!
I rooted back in June, so here's what I had (from memory),
PBJ kernel, voodoo lagfix, and CWM recovery (might be old).
Anyway, I edited the secgps.conf in another post about fixing GPS. I made
a back-up of the original. Anyway, in the other post, he states to reboot,
then it will take awhile but after the first GPS lock, it should work faster.
Well...I rebooted, and it was still way-off...even worse than before. After 10 minutes, I rebooted...then got stuck with the Red Eye at boot.
I took out the battery, plugged back in, etc. Still stuck at Red Eye...even plugged into outlet...letting it go...still that way for over an hour.
Any method of getting in, and just replacing the secgps.conf with the original, then try rebooting? What are my options? Don't want to wipe out everything, especially if I have the voodoo lagfix?
Help! Thanks in advance,
Sara :$
Sara100 said:
Need anybody's help!
I rooted back in June, so here's what I had (from memory),
PBJ kernel, voodoo lagfix, and CWM recovery (might be old).
Anyway, I edited the secgps.conf in another post about fixing GPS. I made
a back-up of the original. Anyway, in the other post, he states to reboot,
then it will take awhile but after the first GPS lock, it should work faster.
Well...I rebooted, and it was still way-off...even worse than before. After 10 minutes, I rebooted...then got stuck with the Red Eye at boot.
I took out the battery, plugged back in, etc. Still stuck at Red Eye...even plugged into outlet...letting it go...still that way for over an hour.
Any method of getting in, and just replacing the secgps.conf with the original, then try rebooting? What are my options? Don't want to wipe out everything, especially if I have the voodoo lagfix?
Help! Thanks in advance,
Sara :$
Click to expand...
Click to collapse
well if it won't boot you can't replace the original file, unless you know about ADB and how to use it... you may need to go back to stock with the PIT file and start over, its not a huge deal and doesn't take long plus the roms out now are way better than the older ones
Dear anoninja118,
I actually let the phone sit for an 3 hours while I worked...it finally got through boot.
However, I thought I had lost root... most of my apps were gone...bloatware came back that I had frozen.... getting force closures on all the apps.
I went into ADB and I still have root (although Superuser app shows no listing ).
I put back that original GPS file rebooted...but nothing..things remained the same as previously stated.
All my files are all intact, have CWM, but it states no voodoo lagfix. Any ideas on how to repair? Can I just switch to another ROM? Keep my files/data?
Thanks,
Sara
Sara100 said:
Dear anoninja118,
I actually let the phone sit for an 3 hours while I worked...it finally got through boot.
However, I thought I had lost root... most of my apps were gone...bloatware came back that I had frozen.... getting force closures on all the apps.
I went into ADB and I still have root (although Superuser app shows no listing ).
I put back that original GPS file rebooted...but nothing..things remained the same as previously stated.
All my files are all intact, have CWM, but it states no voodoo lagfix. Any ideas on how to repair? Can I just switch to another ROM? Keep my files/data?
Thanks,
Sara
Click to expand...
Click to collapse
well what rom were you running? you could just reflash it (shouldn't need to wipe) to return it to 'normal'... also if root was lost I can upload superuser.apk, just flash it and you'll get root back
Sent from my SCH-I510 using XDA App
Yikes...being new to all this stuff, and I did it a few months back, I don't believe I flashed a ROM. I think I did jt1134's kernel (Root / Voodoo Lagfix / CWM Recovery), then I might flashed the PBJ kernel that was available at that time.
Ironically, I've been having many issues with bluetooth and GPS problems recently, and heard that there was a new Gingerbread update. I wanted to wait for the official release, then have one of the programmer gods make a new kernel/ROM. I am not ready to jump to GB yet, and I want to keep all my files. I backed-up many of my apps with Titanium back-up, and saved via DropBox.
Anyway, I thought about reflashing...but if I do the jt1134 scenario...it's via Odin..won't that erase everything. I guess all my stuff is on the SD card, right?
Thanks so much for helping out a damsel in distress,
Sara
Sara100 said:
Yikes...being new to all this stuff, and I did it a few months back, I don't believe I flashed a ROM. I think I did jt1134's kernel (Root / Voodoo Lagfix / CWM Recovery), then I might flashed the PBJ kernel that was available at that time.
Ironically, I've been having many issues with bluetooth and GPS problems recently, and heard that there was a new Gingerbread update. I wanted to wait for the official release, then have one of the programmer gods make a new kernel/ROM. I am not ready to jump to GB yet, and I want to keep all my files. I backed-up many of my apps with Titanium back-up, and saved via DropBox.
Anyway, I thought about reflashing...but if I do the jt1134 scenario...it's via Odin..won't that erase everything. I guess all my stuff is on the SD card, right?
Thanks so much for helping out a damsel in distress,
Sara
Click to expand...
Click to collapse
yes any Odin flash will wipe all data thats not backed up, if you use titanium backup for apps, export a contact list to your sd card that you can import later and you should be fine you'll just lose settings and things like login info for apps which you will have to set up again after... and yes you could do jt1134's method again or you could just flash debloated rooted stock EE4 in CWM (which will be exactly like what you're using) as well as one of the newer kernels, if you want to go the Odin route I would suggest Gummy FE 2.0 or Humble 1.6 as they are both very stable and tweakable/themeable plus come with all the goodies like root, CWM, custom rom and kernel (however if you wiped data and both caches in CWM you could also just flash the rom .zips right over what you're using instead)
Thanks for helping again. So, if I understand correctly, I could use CWM to get debloated rooted stock EE4, and I would still have my data?
Sorry I got confused with "(however if you wiped data and both caches in CWM you could also just flash the rom .zips right over what you're using instead)". So instead of Odin, I could just use CWM with wipe data and cache to flash a new ROM, correct?
That's what confuses me...when to use CWM and when to use Odin? Oh, should I update to the newest CWM (I hope that's easy) first?
Thanks so much...hate to bug you on the weekend, but I need to get this fixed before Monday for work!
Sara
Sara100 said:
Thanks for helping again. So, if I understand correctly, I could use CWM to get debloated rooted stock EE4, and I would still have my data?
Sorry I got confused with "(however if you wiped data and both caches in CWM you could also just flash the rom .zips right over what you're using instead)". So instead of Odin, I could just use CWM with wipe data and cache to flash a new ROM, correct?
That's what confuses me...when to use CWM and when to use Odin? Oh, should I update to the newest CWM (I hope that's easy) first?
Thanks so much...hate to bug you on the weekend, but I need to get this fixed before Monday for work!
Sara
Click to expand...
Click to collapse
you can use either one CWM or Odin, unfortunately you will lose data no matter what... I only said that you could use CWM instead since you already have it and it might be a little easier that way, but both ways will work
okay..thanks for helping. No matter what I choose...I'll cross my fingers!
Sara100 said:
Thanks for helping again. So, if I understand correctly, I could use CWM to get debloated rooted stock EE4, and I would still have my data?
Sorry I got confused with "(however if you wiped data and both caches in CWM you could also just flash the rom .zips right over what you're using instead)". So instead of Odin, I could just use CWM with wipe data and cache to flash a new ROM, correct?
That's what confuses me...when to use CWM and when to use Odin? Oh, should I update to the newest CWM (I hope that's easy) first?
Thanks so much...hate to bug you on the weekend, but I need to get this fixed before Monday for work!
Sara
Click to expand...
Click to collapse
You shouldn't have rooted your phone. Sounds like you don't know what you are doing at all. So I would google "how to flash with odin", then go back to totally stock.
Masterpiece Finishes said:
You shouldn't have rooted your phone. Sounds like you don't know what you are doing at all. So I would google "how to flash with odin", then go back to totally stock.
Click to expand...
Click to collapse
you gotta learn sometime, its trial and error... I was in the same position asking the same questions when I got my first android phone over a year ago
blazing through on my 4G Droid Charge
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Thanks on Gummy Charge FE 2.0. GPS works too!
Got the kinks out... my data was saved.
OG was a lot easier to root back in the day...
Thanks for your help and kind words!
Sara
Sara100 said:
Thanks on Gummy Charge FE 2.0. GPS works too!
Got the kinks out... my data was saved.
OG was a lot easier to root back in the day...
Thanks for your help and kind words!
Sara
Click to expand...
Click to collapse
glad to hear you got it working, you'll like it
blazing through on my 4G Droid Charge
I NEED YOUR HELP!!!
I have a Shift that is making me sick
Here is the dilema:
I am able to perm root the phone but I cannot for the life of me get it to take a custom rom. I also cannot get the phone to revert to stock. I have tried RUU, I have tried PG06IMG.ZIP ... I have searched left and right, day and night .. I am ready to chuck this phone at the next person I see walking down the street!!!
I don't know what to do I just want to be able to flash custom roms and if I need to return to stock .. but I can't. All it does is go back to stock rom but it does not wipe any of my data, it stays unlocked and my banner stays the same. I have noticed my PRL keeps changing from what I have flashed, which is fine this one seems to be better.
Also it seems as if my recovery is not wiping dalvic and there is no stock recovery .. which maybe normal. I have tried everything I can think of .. any suggestions besides blind siding an innocent bystander with this hunk of junk!!??
Running 2.2 on 1.17.651.1
I just want to return to stock so I can start all over and try to get this to run customs.. at least. But before you say flash this PG06IMG.ZIP (234mbs) or RUU .. please note that I have tried. Unless yours has magical powers I have flashed it. It won't work.. I have tried factory reset, format all except sd card... I might just try that for the hell of it. Please help
***UPDATE****
I WAS ABLE TO FIGURE OUT WHAT WAS WRONG WITH MY SETUP ... IF YOU ARE HAVING THIS SAME PROBLEM AND ARE HAVING TROUBLE LIKE I WAS.
HERE IS THE SOLUTION:
Make sure you have the latest recovery. I had clockwork 2.0.5 I think was the version, it was not wiping dalvic or something this is what was causing all my hair to fall out.
I downloaded Rom manager and flashed clockwork recovery, the recovery now is updated to version 5.0 or something like that. I can now say it works and saved some poor innocent person from being pegged in the back of the head from a flying shift .. XD
Sent from my PG06100 using Tapatalk
In the future you can read this thread for exact instructions:
http://forum.xda-developers.com/showthread.php?t=1273867
tech-9 said:
***UPDATE****
I WAS ABLE TO FIGURE OUT WHAT WAS WRONG WITH MY SETUP ... IF YOU ARE HAVING THIS SAME PROBLEM AND ARE HAVING TROUBLE LIKE I WAS.
HERE IS THE SOLUTION:
Make sure you have the latest recovery. I had clockwork 2.0.5 I think was the version, it was not wiping dalvic or something this is what was causing all my hair to fall out.
I downloaded Rom manager and flashed clockwork recovery, the recovery now is updated to version 5.0 or something like that. I can now say it works and saved some poor innocent person from being pegged in the back of the head from a flying shift .. XD
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
The problem is all newer ROMs use Amend scripting which CWM prior to 3.0 doesn't support.
I am posting this as somewhat of a noob...
I went from ROM after ROM after ROM with no problem. Then I installed Dlev GB (WICKED SWEET!!!!) and reinstalled my all my apps with TiBu; but upon getting every thing I wanted set up, restarting, I lost ALL of my apps over and over. I then started to Data wipe and Dalvik wipe and install repetedly trying to get it working. NO SUCCESS... Then went back to stock using gtg's "Returne to Stock" (Always a HUGE THANK YOU!!!!) and started from scratch as it were. Installed Modded CWM again gtg, and then installed Dlev one more time... Come to find out that i REALLY screwed things over before doing the return to stock. What also was happening was that each time that I would use TiBu, it would throw EVERYTHING into my System Partition instead of just installing it in the USB/Internal SD.
So if you are running across this also... Here is the way I worked it out. It doesnt take all that long, just get all your tools infront of you before going forward.
Tools list:
[ODIN][UCKD5] GTG's Ultimate Unbrick - Return to stock - Working PIT included (gtg465x)
[RECOVERY] 100% working ClockworkMod Recovery for Infuse 4G (gtg465x)
USB Cable
What ever ROM you would like to install
And that is it!! Just start going step by step and you will be on your way to a clean slate. Enjoy! But don't come back to me if you do something wrong and Brick the Junk out of your Infuse! I'm just stating what helped me and hopefully it will for you if your in the same boat.
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
At this point, i would suggest to do a full wipe (clear data/factory reset, caches and also format system under storage and mounts). Then flash your flavor of CM7 and while still in CWM, flash the kernel of your choice, DON'T REBOOT, but clear cache/dalvik. Reboot, let it sit for a while and you should be good.
Sent from my LG-P999 using xda premium
Luriden said:
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Click to expand...
Click to collapse
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after that you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Instaling custom kernel instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
ratza66 said:
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Click to expand...
Click to collapse
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Make sure you downloaded his CM7 version and not Stock kernel.
Luriden said:
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Click to expand...
Click to collapse
You welcome, I've added info on how to install custom kernel too
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Luriden said:
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Click to expand...
Click to collapse
You can't install custom kernel on nightly release. Use RC 7.2 and yes do the rom recovery and back it up so the next time you can just restore to any rom that works on your phone.
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Luriden said:
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Click to expand...
Click to collapse
I Think you are missing a one step, Wipe Dalvik. Ok let start from the begining,
First restore your phone to stock, let it boot. Root your phone and install CWM. Install CM7.2 RC rom and let it boot. Go back to the CWM and follow this instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
all these steps are important. I was using CM 7.2 RC with Faux's kernel without any problem and it worked flawlessly
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Luriden said:
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Click to expand...
Click to collapse
Follow this guy on YT, you will find everything there
http://www.youtube.com/watch?v=fxMnnarHaOU
Installing CM7 tutorial
http://www.youtube.com/watch?src_vi...id=annotation_334516&feature=iv&v=Cy9on64jAZs
This one is even better
http://www.youtube.com/watch?v=vUaWXM8GwUI
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Luriden said:
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Click to expand...
Click to collapse
No chance. Nothing will be left over when you wipe your phone. Your SD card is only accessed when you tell CWM to do so. Take your phone back to stock. Do it again this time try either a froyo rom or ICS rom. Then go back wipe everything and install CM7. Sometimes you have to take the long way. after flashing my phone a bazzilion time I learned this the hard way when I couldnt load EB ICS anymore. Had to run GB to get to ICS. Try it in reverse or from a step below and it should go through fine. IF it doesn't, you might have to use ICS instead, which may be stuttery, but works damn well.
DupleX01 said:
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
Click to expand...
Click to collapse
I'm wondering why he still has the issue. YOU CLEAN CACHE BEFORE FLASHING KERNEL/ROM UPDATES!!!
Sent from my LG-P999 using xda premium
For God sake, just flash a random ROM to get access to inside your phone.
1. DIAG your phone OFFLINE with v21e baseband (phone will automatically restart)
2. Let it stay for 5mins after that
3. Use your phone for 15mins
4. Root using 1Click
5. Install CWM
6. Install your ideal ROM + GAPPS (if needed) via CWM
7. Reboot
8. Go outside your living room and watch TV for at least 15mins
9. Reboot your phone into CWM and flash your ideal kernel
10. Enjoy!!!
You better know which ROM/kernel to choose from. Period.
How to upgrade/downgrade your baseband? Do some search, please!
Sent from my LG-P999 using xda premium
I'll do a flash of Froyo or ICS and possibly some baseband research tomorrow. Considering my luck getting a simple rom flash to work, I don't feel too comfortable dealing with the baseband.
A friend was brave enough (somehow) to let me root and install CM7 on his phone, he has the same phone as mine. I got CM7 7.2 RC and Faux's DM UV working like a dream on my first try. Tried it on my phone after recovering it, same problem. So it's a problem that exists deeper on my phone, not with my methods.
The NAND restores for GB and Froyo give me MD5 checksum errors, and the stock zipped rom of GB gives me an installation failed error, so I'm thinking a zipped Froyo rom won't work either, but it might be worth a shot.
Tried Weapon and MIUI too. No go. If I don't get stuck at the blue LG logo, then I'm stuck in a loop between the two LG logos or stuck at a flashing black screen. 8/10 times though it's the blue LG, I think the other errors may have actually been me forgetting to wipe my cache when I was flustered.
I'll try ICS, and hopefully won't get to a point where I have problems installing things I used to be able to, since that seems to be the pattern. After that I finally give up.
I FIGURED IT OUT! Well, sort of. For the hell of it, I downloaded CM7 7.1.0.1 through Rom Manager and it installed fine. It downloaded it to my internal SD, so I hooked it up to my PC to copy the 7.2.0 RC1 to my internal SD and tried installing. No go.
So I went on my phone's web browser and redownloaded 7.2.0 RC1 that way directly to the phone. It works. So somehow, roms I copy from my PC to the phone appear to not work, yet apps and kernels still do. I'm running CM7 7.2.0 RC1, downloaded through my phone's web browser, with Faux's DS UV kernel, copied from my computer. After four days, I finally found a workaround, so I'll stick to it. Whatever works, I guess. I can try reinstalling my USB drivers, but I can probably get by with a combination of the phone's web browser and ES File Manager w/ LAN if need be.
So I left Apple, came to Android, rooted my VZW GS3. First time I've ever done anything like this, so I'm new to it. I backed up EVERYTHING using TiBu, did the IMEI backup, Full system/image backup using CWM, unlocked bootloader, etc. Then I flashed to Synergy r46 (august 20th - yesterday's release).
Now I'm at work and my back-up pulled my contacts via Verizon's server, but how do I get back EVERYTHING else? SMS/MMS logs, call logs, apps, app data, etc? Do I need to download TiBu again (fresh from google market) and then load my backups off my Ext-SD card, or what? I guess I'm a bit confused as to where my TiBu items were even stored/saved...I assume it was the ExtSD card, otherwise I would have lost them all upon flashing to Synergy, correct?
Any help to get all my apps and data back on my newly Synergized phone would be awesome!!!! Thanks in advance!!!
Yes download titanium and then point it to the directory you had your back ups saved to (its sd card by default, and which is your phone storage btw) then tab to backup/restore click the check, then once your app data populates, and select run next to restore apps and data.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Sent from my SCH-I535 using Tapatalk 2
I used titanuium backup pro to back up all my Apps and system data. And when I flash a new rom I just redownload titanium pro and it automatically restores all my Apps and system data. It is the easiest app I have used. So to answer ur question.....back up ur apps with titanium then after flashing a new rom go and redownload titanium and restore your system data and apps or just apps alone if that's what u prefer? Does that answer ur question or would u like more detailed instructions?
Sent from my SCH-I535 using xda app-developers app
Welcome to android!
Sent from my SCH-I535 using Tapatalk 2
Another very nice feature of Titanium Backup is its ability to pull data from CWM nandroids. There have been a few times where I was quick to flash a new rom without doing a backup of my apps. This has saved me much time from having to re-flash the nandroid backup, backup via TB, then re-flash to the new rom.
voodoomanx said:
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Click to expand...
Click to collapse
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Weioo said:
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Click to expand...
Click to collapse
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
dan_joegibbsfan said:
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Click to expand...
Click to collapse
I'm fairly certain I did "wipe data/factory reset," I just wasn't sure how it was labeled when I typed that out, but that's really ringing a bell. I think I may have gotten the errors before (using ROM Manager) because I hadn't factory reset? Seems to me I'm good to go! However, my question regarding TiBu still remains.
Edit: In regards to informing you about r46, I'm not sure what to report as I've never used a previous Synergy and have no idea how to compare, other than to the rooted stock ROM. I have heard reports of battery life being worse than the stock ROM, and I can confirm this. I've barely used the phone since I flashed to Synergy and it's dropped 15% battery life in ~3 hours. Seems faster than before but I'm unsure.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
dan_joegibbsfan said:
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
Click to expand...
Click to collapse
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I used the EZ-unlock app in the play store. I did see that a custom kernel was loaded however when i flashed back to my nandroid (stock rooted) I am back on the orignal kernel. Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I agree I have yet to have Synergy boot loop although I'm still on 1.7. I would try to wipe cache and dalvik cache and see if that helps or you could be over clocking to high.
Sent from my Transformer TF101 using xda premium
nguyenvn said:
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
Click to expand...
Click to collapse
I don't know the answer to that specifically. All I know was that I was stable before another modification I made (that said it wouldn't work but I tried it anyway). Since restoring from backup and reloading Synergy and theme I have not seen any weird rebooting anymore.
nguyenvn said:
Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
Click to expand...
Click to collapse
I'm not familiar with that method. I've only used Odin, even when I did have to redo everything I used Odin to stock de-bloated rooted .md5 then CWM'd from there.
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
nguyenvn said:
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
Click to expand...
Click to collapse
That may very well be the issue. 1.9ghz is a very aggressive overclock, and i wouldn't be surprised if was unstable on a good number of phones. Synergy's supposed to boot at 1.5ghz max by default - I don't know whether that was successfully implemented. I personally think it's silly to OC such a capable phone, anyway. Back in the days of the Droid 1, an overclock from the stock 550mhz to 800mhz-900mhz was an enormous improvement. Today, the only thing OCing the S3 gets you is a <10% improvement in Quadrant, more heat, possible instability, and no perceptible difference outside of those silly synthetic benchmarks.
Anyway, in this thread, there seems to be a fair bit of confusion as far as what's what in the android partitions. I'll give you a short rundown.
"aboot" is what's referred to here as the bootloader. It checks to see whether the next partition in the boot sequence, "boot", is authorized. When you unlocked your bootloader, you overwrote aboot with a version that does not perform that check.
"boot" contains your kernel. If your ROM has a custom kernel, it contains a boot.img to overwrite boot.
"system" is the meat of the OS. This is primarily what ROMs flash.
"data" contains all of your apps and settings. When you perform a factory reset, you're reformatting data. If you're flashing a ROM that is significantly different from what you're on now, some of those old settings and data can cause errors, force closes, random reboots, and boot loops. When in doubt, wipe data before flashing a new ROM. When going from one version of a ROM to a newer, very similar version of the same ROM (nightly to nightly), you probably don't need to wipe data, but make a backup just in case. dalvik-cache is also in data; if you wipe data, you've automatically wiped the dalvik cache. It's redundant to wipe data and then wipe dalvik cache.
"cache" is just that, the cache partition. Clearing it won't make you loose anything, at least not anything Android won't silently replace.
So far it seems to be pretty stable on r50. I installed system tuner and brought it down to 1.5 Ghz. I'm not sure why 1.9 is set to default. Doesn't seem like a good idea to me. Thanks all for the help/advice.