Database Info

Phone reboots-runtime reboot or soft reboot?

Hi all,
When I am browsing market then decide to press the back or home button. Sometimes my phone will reboot for no reason, this happens maybe 3/5 times when I'm browsing market. I'm running the bionix rom with 1.3ghz Trinity kernel. This happened while I was running bionic with 1.2 ghz Trinity kernel.
Thanks!
Sent from my Nexus S using XDA App

Ssunyoto said:
Hi all,
When I am browsing market then decide to press the back or home button. Sometimes my phone will reboot for no reason, this happens maybe 3/5 times when I'm browsing market. I'm running the bionix rom with 1.3ghz Trinity kernel. This happened while I was running bionic with 1.2 ghz Trinity kernel.
Thanks!
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Does it happen specifically with the market? Or does it also happen with other apps too? Also, are there any other common factors among your random reboots (the colloquial term for what you are referring to)? My best advice would be to wipe your dalvik cache, cache, and data and then reflash the rom and kernel. Restore your apps the long way and see if that solves your problem.
(the reason I'd recommend this is that it sounds like there is an issue with your flash and a clean flash might clear that up)

Hey thanks for the fast reply, I actually went to clockwork and wipes every single option avaible except dalvick. Also it only seems to happen while closing or switching from market. I have not experienced the reboot during calls issue like other users. So if I do wipe Dalvick cache, does it uulnable root? Sorry, my first android phone here.
Sent from my Nexus S using XDA App

Ssunyoto said:
Hey thanks for the fast reply, I actually went to clockwork and wipes every single option avaible except dalvick. Also it only seems to happen while closing or switching from market. I have not experienced the reboot during calls issue like other users. So if I do wipe Dalvick cache, does it uulnable root? Sorry, my first android phone here.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Its no problem man, everyone has "silly" questions when they start. =)
Basically, the Dalvik cache (found in advanced in Clockwork Recovery mod, aka CWM) is a list of things to boot. It speeds up the booting process but it also can cause issues during boot if there are conflicts between an old rom and a new one so wiping this is always good.
When you flash a new rom, you don't need to wipe everything, just wipe the Dalvik Cache (again found in the advanced section of CWM), Cache (found in mounts and storage and the actual action you'll be selecting will be "format cache"), and Data (found in mounts and storage and the actual action you'll be selecting will be "format data"). Once you do this flash your rom. Now if you're going to flash a kernel that you have never used before, I generally suggest allowing the phone to boot to make sure everything is fine, get myself all setup, to do a NANDroid backup before adding the kernel. That is my preference and is by no means necessary. Once you flash the kernel you can reboot and re-add your apps.
Now, I mentioned Titanium Backup and I'm still not sure you 100% know what that is so let me explain (as it is a very useful tool). It is a program that backs up your applications all with their data (IE preferences and the like). It does a great job (with the one exception that due to the way Android is built it cannot restore widgets) but it does require some work so it gets tedious when you have to use it a lot. I generally only use it the first time I'm flashing a new ROM. If you want to have a variety of roms you can easily access and switch between here is something I posted in another thread that can make it very, very easy to do:
kenvan19 said:
For reference to the OP, this is what I do. When I see a new rom I want to try I do a backup through Rom manager (it allows you to name Backups rather than just have a date/timestamp). Then I do a titanium back up of all my apps. Next I flash the rom and/or kernel I want to try and then do a titanium restore of my apps, get everything set up how I like it and then immediately do another NANDroid backup through Rom manager.
Right now I have these backups on my phone:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
CM714apps (CM7 rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
Bionixapps (Bionix rom, standard bionix kernel, rooted, with apps set up)
Bionix13apps (Bionix rom, trinity 1.3GHz OC kernel, rooted, with apps set up)
Bionix14apps (Bionix rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
On my wife's:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
BionixZuneApps (Bionix rom, standard bionix kernel, ZuneEvo theme, rooted, with apps set up)
If you see the pattern its basically ROMThemeKernelApps for easy reference when restoring. Its so simple that I told my wife this morning to put her phone back to stock and she was able to figure it out with only minimal help getting to the right screen (she is a complete techNOTphile)
Also, I have a backup on my computer of all of the backups. Unlike Simms, I only do backups when I make significant changes to apps, themes etc (by significant I include changing a shortcut on my launcherpro dock lol).
Click to expand...
Click to collapse
I apologize for the huge wall of text but I hope it helps! Always remember that we're here to help you (as long as you search before you post a question, not applicable to this but it makes everyone's lives easier hehe)

Woah thanks. I really don't mind not backing up haha. So I did what you said and wiped cache/data and dalvik but this time I used stock kernel with bionix. The problem I have now is that the rom manager bundled with bionix says I don't have clockwork installed and when I try to install from there, it just hangs and I have to force close, not a big deal but I can't even backup I guess.
Sent from my Nexus S using XDA App

Ssunyoto said:
Woah thanks. I really don't mind not backing up haha. So I did what you said and wiped cache/data and dalvik but this time I used stock kernel with bionix. The problem I have now is that the rom manager bundled with bionix says I don't have clockwork installed and when I try to install from there, it just hangs and I have to force close, not a big deal but I can't even backup I guess.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm. Try this: turn off your phone and then once its off hold the volume up button and then press the power. This should boot you into the bootloader. Now using the volume rocker to scroll and the power button to select, select recovery. Let it boot into that then tell me what color the text is in recovery.
Sent from my Nexus S

Fixed
Hey Kenvan,
Thanks for the help, I decided to revert back in to stock Android with no root and I have stopped having problems with anything! I also do not experience the rebooting during calls bug.
Thanks!

[Q]Reflashing s7 from cm7 and app install problems

So I flashed the unofficial cm7 build from the dev forum meaning I now have blue Cwm instead of red that I used with s7. What steps are required to reflash s7? Do ihave to use sgs kernel app to reflash kernel then flash s7?
Also I'm having issues restoring apps with titanium. The "stock" app installation screen doesn't allow me to choose install, only cancel. Does this issue stem from not having done a factory data wipe? The thread I read only mentioned to format the system disk but I don't think it was written from the perspective of having come from s7.
Mad props for any help
Sent from my SGH-I997 using XDA App

Yes you will eventually have to use SGS to flash a kernel. Maybe this is the long way around but when I flashed back from cm7 yesterday I used sgs kernel flasher and followed the instructions for infused gb. When I flashed the kernel it got stuck converting partitions to ext4 (probably because they were already in ext4). But I did a battery pull in the middle and was back in red cwm. After that I flashed infused again without hassle with infusion core b. That being said, as long as you have red cwm, you should theoretically be able to flash whatever rom you want.
So in short : just follow the FULL instructions to flash infused v2. Then flash s7. Hope this helps
Sent from my SGH-I997 using XDA App

Thaanks! Will try this if my reflash of cm7 doesn't fix issues....do you think my app install problems are stemming from a previous install?
Sent from my SGH-I997 using XDA App

Hmmm...well out of habit I always personally makes sure I format everything, wipe the dalvik cache, fix permissions and wipe the cache partition as well. A lot of the devs stress that this is necessary so I wouldn't doubt that your app install problems are from a previous install. Something tells me, and someone please correct me if I'm wrong, that when you are going from a voodoo enabled ROM like infused or s7 to a ROM like cm7 that doesn't use voodoo lagfix, you will have issues with trying to get your apps back because they were using a different (but still similar since they are both EXT4) file system. This is just my guess. If anyone could elaborate more on this please do.
I would highly suggest flashing back to stock if you still experience issues or even ultimate unbrick so that way you can get a clean slate. Maybe try using apps2sd. I own it and can verify that it works well. Many others have also praised it. Good luck!

stratatak7 said:
Hmmm...well out of habit I always personally makes sure I format everything, wipe the dalvik cache, fix permissions and wipe the cache partition as well. A lot of the devs stress that this is necessary so I wouldn't doubt that your app install problems are from a previous install. Something tells me, and someone please correct me if I'm wrong, that when you are going from a voodoo enabled ROM like infused or s7 to a ROM like cm7 that doesn't use voodoo lagfix, you will have issues with trying to get your apps back because they were using a different (but still similar since they are both EXT4) file system. This is just my guess. If anyone could elaborate more on this please do.
I would highly suggest flashing back to stock if you still experience issues or even ultimate unbrick so that way you can get a clean slate. Maybe try using apps2sd. I own it and can verify that it works well. Many others have also praised it. Good luck!
Click to expand...
Click to collapse
i went and did another install of cm7 before i ultimate unbrick back to stock. i figure out the app install problem; unknown sources wasn't checked...very noob. but the promt at the beginning of titanium caught me off guard and i cancelled before i could read it.
i, too, noticed that my app icons were intact on my desktop after the s7 to cm7 flash but most (if not all) those that did not require root would force close upon opening. reinstalling the app worked, but i had to get them from the market at the time as my unknown sources box was unchecked. also, i've noticed that widgets do not reload after reboot.
one more thing, after the second flash of cm7, i noticed that flashing gapps only provided me with the market. others such as email and talk were available for dl thru the market but weren't loaded from the gapps flash. i tried multiple times to no avail.
i'm about to ultimate unbrick and reflash cm7 from stock. one more last thing, i'm fairly comfortable with red cwm but have only encountered blue with cm7...how do i wipe the dalvik cache?
thanks for the help!

albee320 said:
i'm about to ultimate unbrick and reflash cm7 from stock. one more last thing, i'm fairly comfortable with red cwm but have only encountered blue with cm7...how do i wipe the dalvik cache?
thanks for the help!
Click to expand...
Click to collapse
When using TiBu, make sure and restore apps using the "restore all apps with data" option, just did it coming from S7 to MIUI and worked fine.
As far as Gapps go, I downloaded them from the Cm7 wiki and installed them manually from blue CWM just to make sure everything was added and it worked for me.
Dalvik is in advanced just like red CWM, just a different color.

xIC-MACIx said:
When using TiBu, make sure and restore apps using the "restore all apps with data" option, just did it coming from S7 to MIUI and worked fine.
As far as Gapps go, I downloaded them from the Cm7 wiki and installed them manually from blue CWM just to make sure everything was added and it worked for me.
Dalvik is in advanced just like red CWM, just a different color.
Click to expand...
Click to collapse
I've always heard it is a huge no-no to restore all apps with data.

EricNagel said:
I've always heard it is a huge no-no to restore all apps with data.
Click to expand...
Click to collapse
restoringing all USER apps with data is okay but dont include SYSTEM apps with data

EricNagel said:
I've always heard it is a huge no-no to restore all apps with data.
Click to expand...
Click to collapse
the "system data" is the no no, and "restore missing apps" is the preferred option, but I've always avoided system data and have been fine everytime I restore.

I give up! Ready to Root!!

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.

What Did I Do Wrong?

Ok so I have Vahalla Final flashed through Odin as my first ROM on this phone. Everything has been great for a few days and I flashed the lighting tweak today with no issues. Just a little while ago I made a backup and flashed the Linda voices and the Ki3 modem bc I saw where the KJ6 didn't allow long text messages. When I flashed the modem some blue words popped up really zoomed in on another screen then it was done. The phone was laggy so i tried to delete everything and restore like I had done numerous times on old phone.
I did a factory reset then cache then tried to format system. These are all steps i used to successfully take on other phone. It won't let me format the system though. Says: "format_volume failed to mount "/system" error formatting system!"
Where did I go wrong? Am I supposed to do some more wacky things on this phone for a restore? Everything else on it seems to take 20 more steps

aburn95 said:
Ok so I have Vahalla Final flashed through Odin as my first ROM on this phone. Everything has been great for a few days and I flashed the lighting tweak today with no issues. Just a little while ago I made a backup and flashed the Linda voices and the Ki3 modem bc I saw where the KJ6 didn't allow long text messages. When I flashed the modem some blue words popped up really zoomed in on another screen then it was done. The phone was laggy so i tried to delete everything and restore like I had done numerous times on old phone.
I did a factory reset then cache then tried to format system. These are all steps i used to successfully take on other phone. It won't let me format the system though. Says: "format_volume failed to mount "/system" error formatting system!"
Where did I go wrong? Am I supposed to do some more wacky things on this phone for a restore? Everything else on it seems to take 20 more steps
Click to expand...
Click to collapse
CWM versions prior to those in bhndven's Slightly Modified Stock kernels have a problem with mounting/unmouting the /system partition in GB. I believe you can backup and restore user data, but nothing on the /system partition.
Flashing the KI3 modem shouldn't have had an effect like you're describing, though. I can't say I've had an issue like that at all or heard of people having that issue after flashing the modem.

stephen_w said:
CWM versions prior to those in bhndven's Slightly Modified Stock kernels have a problem with mounting/unmouting the /system partition in GB. I believe you can backup and restore user data, but nothing on the /system partition.
Flashing the KI3 modem shouldn't have had an effect like you're describing, though. I can't say I've had an issue like that at all or heard of people having that issue after flashing the modem.
Click to expand...
Click to collapse
So everything should run fine after trying the actual restore of my backup even though i couldn't format the system? I have a backup but don't want to restore over data that wasn't deleted or whatever. If that's possible.

How the hell do i know which modem to use anyways? There's like 10 to choose from

Uh yeah I forget it tries to format system anyways when restoring... and it couldn't. So what do i do? Re-flash the GB starter pack way through Odin?

aburn95 said:
Uh yeah I forget it tries to format system anyways when restoring... and it couldn't. So what do i do? Re-flash the GB starter pack way through Odin?
Click to expand...
Click to collapse
As for the modem, I'm using KI3 on mine. You already did a factory reset so you should be able to just re-flash Valhalla.

Trying now. Does Vahalla automatically change all the mounts that the other roms require changing before flashing?

aburn95 said:
Trying now. Does Vahalla automatically change all the mounts that the other roms require changing before flashing?
Click to expand...
Click to collapse
I'm not sure about that one. Definitely go check the original Valhalla post to make sure you don't have to set the mounts.

Guess you don't have too. I'm using it now. thanks for the help

aburn95 said:
Guess you don't have too. I'm using it now. thanks for the help
Click to expand...
Click to collapse
No worries. Good luck

Hey I still have an issue. I reflashed Vahalla through CWM and it was fine at first all the way through setting everything up like it was before. Ran smooth. I went to the market this morning and checked for updates and Google Search, Maps and Superuser updated. Phone started acting really laggy again. Scrolls really slow, pulls up GO Launcher menu slowly, etc.
It seems to me that the re flash installed over the existing data that was left on the phone since i couldn't format my system.
My new question is, what's the best way to re do everything including formatting the system if I can't format through CWM? If I flash through Odin does that format everything? Or am I better of just going through the whole GB Starter Pack process again?? Or will that even work now since i've already done it?

aburn95 said:
Hey I still have an issue. I reflashed Vahalla through CWM and it was fine at first all the way through setting everything up like it was before. Ran smooth. I went to the market this morning and checked for updates and Google Search, Maps and Superuser updated. Phone started acting really laggy again. Scrolls really slow, pulls up GO Launcher menu slowly, etc.
It seems to me that the re flash installed over the existing data that was left on the phone since i couldn't format my system.
My new question is, what's the best way to re do everything including formatting the system if I can't format through CWM? If I flash through Odin does that format everything? Or am I better of just going through the whole GB Starter Pack process again?? Or will that even work now since i've already done it?
Click to expand...
Click to collapse
Did you restore your previous apps are do fresh installs?

Restored w titanium..... ugh.. Flashing a new zip doesn't wipe anything right? Just installs over whats already there right?

aburn95 said:
Restored w titanium..... ugh.. Flashing a new zip doesn't wipe anything right? Just installs over whats already there right?
Click to expand...
Click to collapse
If you flashed and "it was fine at first all the way through setting everything up"...
try reflashing as you did before. Do fresh installs on as much as you can ONE AT A TIME. And then restore ONE AT A TIME what you can't do fresh installs on. It sounds like one of your backups is not agreeing with the system. Install/Restore ONE AT A TIME and play with phone between each to see if you can determine which backup your system is not agreeing with.
Did that make sense??
EDIT: And make sure to wipe dalvik cache and cache partition before you reflash as is always recommended.

stephen_w said:
No worries. Good luck
Click to expand...
Click to collapse
lumin30 said:
If you flashed and "it was fine at first all the way through setting everything up"...
try reflashing as you did before. Do fresh installs on as much as you can ONE AT A TIME. And then restore ONE AT A TIME what you can't do fresh installs on. It sounds like one of your backups is not agreeing with the system. Install/Restore ONE AT A TIME and play with phone between each to see if you can determine which on your system is not agreeing with.
Did that make sense??
EDIT: And make sure to wipe dalvik cache and cache partition before you reflash as is always recommended.
Click to expand...
Click to collapse
Yeah it makes sense thanks. I will do this despite how impatient I am (see where that got me). I'm just got spoiled on another phone that was way way easier to work with. Weren't as many options to screw up either.
Any suggestions on how I can get my system to format for future reference?

I feel like it's Go Launcher for some reason. In cased you missed it though, I didn't start having lag issues until I flashed the Ki3 modem and linda voices one after another. I have a good backup but I can't format system to restore it.

aburn95 said:
Yeah it makes sense thanks. I will do this despite how impatient I am (see where that got me). I'm just got spoiled on another phone that was way way easier to work with. Weren't as many options to screw up either.
Any suggestions on how I can get my system to format for future reference?
Click to expand...
Click to collapse
I have never formatted my system nor read anybody wanting/needing to format their system. A factory reset is what people use to clean the gremlins along with wiping dalvik cache and cache partition. Bhundven has recommended flashing the same rom twice in a row I believe to help make sure all installs correctly (I think he was talking about bootloaders when he recommended that).
But a factory reset is what I think you are trying to accomplish with formatting your system.
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
aburn95 said:
I feel like it's Go Launcher for some reason. In cased you missed it though, I didn't start having lag issues until I flashed the Ki3 modem and linda voices one after another. I have a good backup but I can't format system to restore it.
Click to expand...
Click to collapse
I use GoLauncher on Vahalla Black with no problems. I think it has to do with your backup... not the app itself.

I wiped caches, did factory reset, tired to format system again with no luck and accidentally restarted before re-flashing Vahalla. Which, I guess I didn't really need to do anyways if it's an App causing the issue. I guess the factory reset would be enough. Smooth again so i will try some fresh reinstalls now. Thanks for the noob patience

lumin30 said:
I have never formatted my system nor read anybody wanting/needing to format their system. A factory reset is what people use to clean the gremlins along with wiping dalvik cache and cache partition. Bhundven has recommended flashing the same rom twice in a row I believe to help make sure all installs correctly (I think he was talking about bootloaders when he recommended that).
But a factory reset is what I think you are trying to accomplish with formatting your system.
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
I use GoLauncher on Vahalla Black with no problems. I think it has to do with your backup... not the app itself.
Click to expand...
Click to collapse
Ok cool. In another phones forum a system wipe is actually suggested a lot. I think... I did it every time on the G2x before installing any new roms or backups. I wasn't doing it at first but started after someone suggested it. But yeah I think the factoy reset is enough. Seems to be enough so far.

aburn95 said:
I wiped caches, did factory reset, tired to format system again with no luck and accidentally restarted before re-flashing Vahalla. Which, I guess I didn't really need to do anyways if it's an App causing the issue. I guess the factory reset would be enough. Smooth again so i will try some fresh reinstalls now. Thanks for the noob patience
Click to expand...
Click to collapse
I am a noob too. No worries. Vahalla Black is solid. Backups are tricky. Fresh installs are the way to go.

I think I broke it.

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.