ARCHIVED: [DEAD ROM] ThundeROM V1.8.3 4/5/2011

[tmeader]

Delete some apps? Move more apps to the SD? Clean out the cache of some of the programs?

Android "Low Storage" seems to be a warning for near filling of the phone flash memory. Though it seems to happen other times as a bug.

I didn't get your error, but then I just got the phone on Saturday so it's pretty empty. I was the first person to complain about 1.7, 6 hours before KSmith announced the release.

Yeah, I think in your case, you just might not have enough apps/data on the phone yet for it to be a problem. How much free space is your phone showing under "Settings->SD card and storage"? With a stock TR 1.7 install, you'll have around 161MB free. If it's considerably below that, I'd say you're seeing the problem, but your phone is empty enough not to trigger the low space warning. Prior to trying to use 008 kernel, I was ~97MB free. After rebooting from ONLY installing the 008 kernel, I'm down to ~4 and dropping (plus the missing Titanium backups).

 

[bugmage]

1.Read all peoples flashing instructions got all frustrated with having to go back to shell, so I said Meh

2.was in 1.6.2, took nandroid backup
3.flashed to 1.7 worked but no service, and sd apps weren't loading left it on that rom
4.restored back to 1.6.2 with nandroid
5.LG updater, shows lg rom now booted fine all my stuffs still there
6.flashed back to 1.7,looks like every things good in the world

-didn't clear any cache at any point
-no adb shell stuff
-left phone hooked to pc entire time
-played facebook games while waiting for phone update

Phone now reads:
VC software, thunderrom 1.7, no OC kernel

my apps were real buggy for a while and i had to remove/add some widgets, i think it was because i hit low space(159 kb free )

soon as a removed some crap was good 2 go

 

[jeffreynothing43]

Do we need to do a full wipe if we?re coming from 1.6.2? I?m just trying to see if I?m going to need to dedicate 15 minutes to this process or an hour or so for me to set everything up again. Thanks!

 

[ahope577]

Went the same route

1.Read all peoples flashing instructions got all frustrated with having to go back to shell, so I said Meh

2.was in 1.6.2, took nandroid backup
3.flashed to 1.7 worked but no service, and sd apps weren't loading left it on that rom
4.restored back to 1.6.2 with nandroid
5.LG updater, shows lg rom now booted fine all my stuffs still there
6.flashed back to 1.7,looks like every things good in the world

-didn't clear any cache at any point
-no adb shell stuff
-left phone hooked to pc entire time
-played facebook games while waiting for phone update

Phone now reads:
VC software, thunderrom 1.7, no OC kernel

my apps were real buggy for a while and i had to remove/add some widgets, i think it was because i hit low space(159 kb free )

soon as a removed some crap was good 2 go

I went the same route and had great results
Backup
LG Update utility
Shutdown phone after verifying upgrade via LG tool
Flash v1.7
Running without Issue for two days

 

[CarrieK]

Day Two and so far no issues reported here. Have completely turned off the phone and turned it on several times to test and all is well. This ROM is great...I'm having a blast customizing and playing

 

[sclarktay4]

Do we need to do a full wipe if we?re coming from 1.6.2? I?m just trying to see if I?m going to need to dedicate 15 minutes to this process or an hour or so for me to set everything up again. Thanks!

No need to do a wipe, just flash 1.7 on top of 1.6.2. all your apps and data will still be there and it will only take minutes

 

[jeffreynothing43]

Is it as fast as 1.6.2?

 

[gschuck]

Day Two and so far no issues reported here. Have completely turned off the phone and turned it on several times to test and all is well. This ROM is great...I'm having a blast customizing and playing

When I woke up this morning my sdcard was still mounted. That's a big plus. A WMA file sound problem that I was having with PowerAMP is also no more. Those two things are worth the price of admission to me. Everything else with the 1.7 ROM is gravy. It's only been 12 hours but no complaints here (except that I am not observant enough to notice all the new icons -- I feel like I am missing out on something!).

It makes me sad to think of all the people out there that are still running stock

 

[ccrs8]

Day Two and so far no issues reported here. Have completely turned off the phone and turned it on several times to test and all is well. This ROM is great...I'm having a blast customizing and playing

I wish I had your luck. When it is turned on, my phone running ThundeROM 1.7 and VC baseband works great, but I can not turn it off completely or it gets stuck at the LG icon when I turn it back on. I'm still not sure what exactly is wrong with it, as I first experienced the LG icon issue after I had already successfully done the whole unroot/return to v9 stock/LG Updater to VC/reroot/re-custom recovery/flash ThundeROM 1.7 process. Most people who had the LG icon issue saw it after coming out of custom recovery after flashing ThundeROM, if I'm not mistaken. Oh well...

 

[gschuck]

No need to do a wipe, just flash 1.7 on top of 1.6.2. all your apps and data will still be there and it will only take minutes

If you are going from V9 to VC you need to allow 30 minutes for the LG Updater Tool to run.

 

[CarrieK]

I wish I had your luck. When it is turned on, my phone running ThundeROM 1.7 and VC baseband works great, but I can not turn it off completely or it gets stuck at the LG icon when I turn it back on. I'm still not sure what exactly is wrong with it, as I first experienced the LG icon issue after I had already successfully done the whole unroot/return to v9 stock/LG Updater to VC/reroot/re-custom recovery/flash ThundeROM 1.7 process. Most people who had the LG icon issue saw it after coming out of custom recovery after flashing ThundeROM, if I'm not mistaken. Oh well...

I went directly from TR 1.6.2 v9, updated via LG Tool to VC, then flashed TR 1.7. So, it appears that we went about moving to 1.7 in a different fashion.

 

[ccrs8]

I went directly from TR 1.6.2 v9, updated via LG Tool to VC, then flashed TR 1.7. So, it appears that we went about moving to 1.7 in a different fashion.

Yeah, I guess my mistake was doing it the official way that all of the stickies advised. I was able to reboot in to recovery via Quickboot and then boot in to Android from recovery, but a normal shutdown is a no go. It doesn't seem that I'm alone, but I am not seeing a reliable fix out there.

So the LG tool updated your radio as well, even though you had ThundeROM and I'm assuming a custom recovery?

 

[gschuck]

Yeah, I guess my mistake was doing it the official way that all of the stickies advised. I was able to reboot in to recovery via Quickboot and then boot in to Android from recovery, but a normal shutdown is a no go. It doesn't seem that I'm alone, but I am not seeing a reliable fix out there.

So the LG tool updated your radio as well, even though you had ThundeROM and I'm assuming a custom recovery?

I just did a complete shutdown and got stuck at the LG screen on power-up. I had to pull the battery, boot to recovery, and boot to Android from there. I moved to 1.7 the same way that CarrieK did so this is not associated with the unroot/stock/update/reroot path.

It is not like I ever need to shut the phone off completely so this should not bother me in the real world. I can still warm-boot if the phone is on and pull the battery/boot from recovery if the phone is off so I am far from dead in the water. I offer this post as just another data point for K and B.

 

[CarrieK]

Yeah, I guess my mistake was doing it the official way that all of the stickies advised. I was able to reboot in to recovery via Quickboot and then boot in to Android from recovery, but a normal shutdown is a no go. It doesn't seem that I'm alone, but I am not seeing a reliable fix out there.

So the LG tool updated your radio as well, even though you had ThundeROM and I'm assuming a custom recovery?

Yes. I created a NAND backup, then went ahead and downloaded TR 1.7 and placed it at the root of my sd so that I could see it in Custom Recovery. I updated my phone via the LG Tool, then after a couple of attempts (I initially did not press the volume down, home, and power keys hard enough and long enough--VERY IMPORTANT so you can get to your Custom Recovery) I wiped my data, cache, and davlik. Then I unzipped TR 1.7 and voila...I had VC, root, and TR 1.7.

 

[ccrs8]

I just did a complete shutdown and got stuck at the LG screen on power-up. I had to pull the battery, boot to recovery, and boot to Android from there. I moved to 1.7 the same way that CarrieK did so this is not associated with the unroot/stock/update/reroot path.

It is not like I ever need to shut the phone off completely so this should not bother me in the real world. I can still warm-boot if the phone is on and pull the battery/boot from recovery if the phone is off so I am far from dead in the water. I offer this post as just another data point for K and B.

I can't get to recovery...I'm trying now and it just sticks on the LG logo. The only time I am able to get back in my phone is if I do a yet-to-be-determined number of attempts at pulling battery, trying to get in to recovery, pulling battery, plugging in, pulling cable out, and eventually I pretend to give up and go brush my teeth. When I get back the screen has turned from the LG logo to the battery charging icon. At that point I just hit the power button and it boots full in to ThundeROM. Seeing the big battery charging icon is the key, but I can't figure out how to get there reliably. If I could, I'd document it. So far it seems that the key is to be watching crappy TV while drinking beer and mindlessly pulling and unpulling the battery...leaving the phone unwatched while brushing your teeth also seems to be key.

Does your method work all the time...when you get the LG icon you pull battery, wait a few moments, pop it back in, and then use the key combination to get to recovery?

 

[tmeader]

I can't get to recovery...I'm trying now and it just sticks on the LG logo. The only time I am able to get back in my phone is if I do a yet-to-be-determined number of attempts at pulling battery, trying to get in to recovery, pulling battery, plugging in, pulling cable out, and eventually I pretend to give up and go brush my teeth. When I get back the screen has turned from the LG logo to the battery charging icon. At that point I just hit the power button and it boots full in to ThundeROM. Seeing the big battery charging icon is the key, but I can't figure out how to get there reliably. If I could, I'd document it. So far it seems that the key is to be watching crappy TV while drinking beer and mindlessly pulling and unpulling the battery...leaving the phone unwatched while brushing your teeth also seems to be key.

Does your method work all the time...when you get the LG icon you pull battery, wait a few moments, pop it back in, and then use the key combination to get to recovery?

Which recovery are you using? If it's CWM, I used to have some issues with that (been running fine for me the past few days now though), so you might want to flash the 1.2 Thunderc recovery instead. I was able to get into recovery with that one pretty much 100% of the time.

 

[ccrs8]

Which recovery are you using? If it's CWM, I used to have some issues with that (been running fine for me the past few days now though), so you might want to flash the 1.2 Thunderc recovery instead. I was able to get into recovery with that one pretty much 100% of the time.

I'm using CWM, so if I can figure out how to get my phone back up and running one final time, I'll switch to Thunderc (which I had been using up until about a week ago, I just figured I'd switch to the one that seemed to have a bit more active development so I could check out all the changes). Once I change recovery I'll turn my phone completely off again, verify that I still get the LG icon issue, and then see if I can get in to recovery a bit more reliably after pulling the battery.

 

[CarrieK]

Which recovery are you using? If it's CWM, I used to have some issues with that (been running fine for me the past few days now though), so you might want to flash the 1.2 Thunderc recovery instead. I was able to get into recovery with that one pretty much 100% of the time.

That is the recovery I use as well.

 

[ccrs8]

That is the recovery I use as well.

Which one? thunderc?

 

[CarrieK]

Which one? thunderc?

I'm sorry Thunder-c.