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

Status
Not open for further replies.
LOL I was afraid you'd say that. I just went through hell getting my data back after forgetting which recovery I was on and using ##RTN#. and I got back to where everything works, and I was able to update PRL and data, but I had used the LG update tool to go to VD so I was being told there was a sprint update still which I know won't work now that I have a custom recovery, so I nandroid restored my previous 1.8 backup. Maybe that is my problem though. I am going to restore back to my unromed VD and if update profile and PRL seems to work I will just reflash 1.8 anew and just have to deal with setting up everything again. Especially since doing ##RTN# once your on a custom rom just seems to completely bork everything up.

Edit: Going back to stock VD seems to have fixed PRL update for me, so I think somehow my backup of thunderom 1.8 messed something up. I am trying a fresh flash now.
 
Especially since doing ##RTN# once your on a custom rom just seems to completely bork everything up.
Yeah, I read about your SNAFU.

I mostly do my ##RTN# resets using stock LG ROM and stock LG recovery. I do it quite often when testing things out and never have an issue. I recently started testing it some with CWMA and also did not have any issues.

However, I'm very cautious about running it in new situations as it is dealing with low-level phone resets so things can get messed up and I can't depend on every ROM developer to test this area out.
 
Download the regular hotspot widget from the market by harald mueller and try it. With 1.8 i was trying to make the default hotspot work like it always did and in my tests i had very inconsistent results. With that said, i was testing right after switching to the VD radio and my phone was acting funky. It would connect to the sprint network then disconnect, then be on 1xrtt, then say it couldn't find a network. Real crazy. In addition to upgrading my radio, i was also reactivating my phone on the network because i was testing/playing with a different device :p .... back to my point... it was during this 3 hour period i was testing to see if i could get the hotspot widget working and i thought it was a fail. Now that my phone has normalized after being reactivated, i actually think it did work afterall and my radio issues skewed my testing.

I just used the hotspot widget several times and it worked no problem. In fact, this was typed on my nook color tethered to my optimus running ThundeROM 1.8 using only the wifi hotspot widget. Give it a try but i think it actually worked :)

EDIT- more testing, more working fine. Im sorry about the confusion but at the same time, a bit mad at myself for not connecting the dots during the testing phase. Oh well, download the widget for now and the next version will include it.
Yep. works perfectly on mine - A tethered Galaxy Tab (Sprint). Thanks-a-million!
 
Well, as of now my PRL update says up to date (I'm on 60765 which I guess is the one for this area), but when I go to update profile, it says "The profile update could not be completed. Please try again later" which I guess is better then Could not contact server(DM) I was getting before.
and my data works again!
 
Well, as of now my PRL update says up to date (I'm on 60765 which I guess is the one for this area), but when I go to update profile, it says "The profile update could not be completed. Please try again later" which I guess is better then Could not contact server(DM) I was getting before.
and my data works again!
60676 is the latest, but I wouldn't worry much about PRL. Update Profile is the important one. PRL can be loaded in other ways and HFA can be done by hand also. Update profile is a pain to do by hand.
 
60676 is the latest, but I wouldn't worry much about PRL. Update Profile is the important one. PRL can be loaded in other ways and HFA can be done by hand also. Update profile is a pain to do by hand.
I've had times even on stock phones where I will get a PRL update and my wife won't on her stock moment, and vice versa. it seems like they roll them out kind of like they roll out regular updates. Right now they seem to both be working though I think my profile update won't work because sprint was messing around trying to reset my stuff. At least its not telling me it can't connect to the server anymore it just says try again later.
 
So can we flash the updated xionia kernel yet? The main reason I ask is I need the tun.ko module installed. I had a pain trying to install it by itself last time and I know its part of the newer xionia releases.
 
Hi,

I am a Thunderom 1.7 user (love the ROM!) and I just bricked my phone (possibly reversibly). I turned my phone off to go into custom recovery and to flash it to 1.8 and now it appears to be bricked with the LG logo on boot. I managed to get into the emergency mode but I don't know how to proceed now. adb does not seem to recognize the phone (though I may not be using it right).

[this is probably way more detail than necessary, but maybe this will help someone figure out a solution]

I am currently running Thunrderom 1.7 and have Thunderc 1.1.0 recovery. I never had any problems with the LG logo. When I originally flashed to 1.7 from 1.6, I did it by going back to my backed-up version of rooted stock V9, running LG updater, backing that up and flashing 1.7 on top of that. Yesterday I was having some strange problems with repeated text messages so I flashed back to the backed up stock VC, found that didn't help, flashed back to 1.7. This morning I thought I'd try 1.8. I turned the phone off through pressing the power button and selectin Power Off. I've done this type of power-off, power-on many times before from 1.7. And now I'm bricked.

I have tried the standard solutions I've read about:
- powering up (press power)
- going to custom recovery (home+vol down+power)
- going to emergency mode (search+camera+vol down, followed by power+usb insert)
- pulling the battery, plugging in (Battery Required screen comes on), plugging the battery in (goes to LG logo and gets stuck)

as well as some variations:
- pull battery, home+vol down+power, insert battery (with and without usb plugged in)
- pull battery, plug laptop into usb, (search+camera+vol down+power), slide battery in

The last one actually worked! The screen says "Download is in progress. Do not disconnect cable." and "Emergency Mode" in big red letters.

Now I have a problem with the phone connecting and disconnecting from the laptop every 30 seconds or so. In Device Manager, I see "LG CDMA USB Modem", and it keeps connecting and disconnecting.

I tried using adb to flash back to stock v9, but it cannot find the phone (I tried running it when the phone is connected).

Does anyone have any advice on how I can bring my phone back to life from here? I am a novice at this, and I hardly remember the exact steps I took to root the phone, so I may not be using adb correctly.

Thanks,

Michal
 
The widget is called calendar widget and is not available in the market. Give me a couple minutes to boot up my pc and I'll get you a signed copy to install on her phone.

Edit - HERE you go.

Hey KSmith can you repost the CalendarWidget you posted in the above link. I'd love to use it when I use an ASOP rom on my EVO.
 
Hi,
Does anyone have any advice on how I can bring my phone back to life from here? I am a novice at this, and I hardly remember the exact steps I took to root the phone, so I may not be using adb correctly.

Thanks,

Michal

I pulled battery and waited 15 minutes, then booted into recovery. It's the VC firmware that is buggy with LG logo bootlock. It messes up the NVRAM.

If you can get to recovery then forceflash the V9 ROM and recovery.

http://forum.androidcentral.com/lg-...alling-ota-ls670vc-using-kp500-diag-mode.html
 
Thanks telemike. I never thought of being patient :)

I am affraid to reboot my phone now, in case there is something I can do from Emergency Mode and I may not be able to get back into it. That would suck... I'll try the patient approach in the evening, absent other suggestions.

For the record, I have not been able to get into recovery mode through any of my attempts. If I could, I would flash to Thunderom 1.8, which apparently does not suffer from this problem.

Also, when I run the LG updater tool, it finds the phone just fine. Should I just try flashing to VD? I'm affraid of what could happen the phone disconnected while flashing...

Thanks!

Michal
 
I went back to total sotck V9 recovery/rom then rooted with Z4root. Installed CWM and then used LG updater to go VD and then TR1.8
 
Thanks telemike. I never thought of being patient :)

I am affraid to reboot my phone now, in case there is something I can do from Emergency Mode and I may not be able to get back into it. That would suck... I'll try the patient approach in the evening, absent other suggestions.

For the record, I have not been able to get into recovery mode through any of my attempts. If I could, I would flash to Thunderom 1.8, which apparently does not suffer from this problem.

Also, when I run the LG updater tool, it finds the phone just fine. Should I just try flashing to VD? I'm affraid of what could happen the phone disconnected while flashing...

Thanks!

Michal

Here is what worked for me after struggling with the LG Logo hang. As long as my phone was connected to my computer via USB, I had no problem rebooting on VC. I then reverted back to V9 using the "diag method", which still kept my custom recovery intact. I flashed a V9 rom (e.g. ThundeROM 1.6.2), which I used until the VD update came out. During this time the LG Logo hang problem disappeared. Once the VD update came out, I essentially followed the "Chaos" method to upgrade to VD and flash a rooted VD ROM, e.g. ThundeROM 1.8. No problems since then. Hope this helps.
 
Thanks telemike. I never thought of being patient :)

I am affraid to reboot my phone now, in case there is something I can do from Emergency Mode and I may not be able to get back into it. That would suck... I'll try the patient approach in the evening, absent other suggestions.

For the record, I have not been able to get into recovery mode through any of my attempts. If I could, I would flash to Thunderom 1.8, which apparently does not suffer from this problem.

Also, when I run the LG updater tool, it finds the phone just fine. Should I just try flashing to VD? I'm affraid of what could happen the phone disconnected while flashing...
I would suggest you read through the unbrick thread, paying special attention around the section where it talks about emergency mode.

I would suggest *not* flashing VD. If you want to flash anything, flash V9. VD isn't something you want to get near when you have a boot problem because it reduces your rooting options. You can get back to VD after you resolve your boot problem.

http://forum.androidcentral.com/lg-...s/59781-un-brick-method-some-forms-brick.html
 
Thanks sfhub. I started reading the "Unbrick your phone using KDZ" thread before, but missed the part about Emergency Mode. I got discouraged when it talks about going into recovery mode (which I couldn't because it was bricked). I read it again and figured out that I just needed to start much later.

My phone is now unbricked, but I went a different way, because proper unbricking seemed involved. I figured that I could try flashing the VD update without worry. The reason is that I have custom recovery and the LG updater does not mess with recovery so I could go into recovery after updating and reflash anything I wanted. LG updater examined the phone for a little bit and popped up a window that said to disconnect the cable, remove and replace the battery, plug the phone back in and press the RESET button on the window. I did all that (except the last part, and I'm not sure if I connected it to the computer first or installed the battery first) and the phone popped up the "charging battery" screen. I knew this was a very good sign, so I pressed the power button and lo and behold I was booting. I used quick boot to go into recovery (not risking a bricking again!) and now I'm going to install Thunderom 1.8.

Thanks everyone. Without the help of so many people on these forums (I did quite a bit of reading to come up with different variations of things that might work) I would at the very least need to go to a Sprint store and exchange the phone (which would feel dirty, since I actually did violate the warranty and the $35 they charge does not make up for that).
 
does this:

"Only power button wakes phone when screen off to prevent pocket dialing/texting"

still apply to ThundeROM 1.8 ?

If so, is it easy to get used to? because I always wake the screen with 4 buttons below screen, I hardly ever use the power to turn on the screen. I only use the power button to turn off the screen.
 
does this:

"Only power button wakes phone when screen off to prevent pocket dialing/texting"

still apply to ThundeROM 1.8 ?

If so, is it easy to get used to? because I always wake the screen with 4 buttons below screen, I hardly ever use the power to turn on the screen. I only use the power button to turn off the screen.

Yeah, it still applies. There's something you can flash to use the 4 buttons to turn on the screen. The link is included at the bottom of post #2 of this thread.
 
does this:
"Only power button wakes phone when screen off to prevent pocket dialing/texting"still apply to ThundeROM 1.8 ?
If so, is it easy to get used to? because I always wake the screen with 4 buttons below screen, I hardly ever use the power to turn on the screen. I only use the power button to turn off the screen.

Yes it applies to 1.8. I didn't notice it first in the change log, so it took me by surprise at first. Before 1.8 I always used the bottom buttons to wake the phone as well, but after maybe 2 days I'm used to it now, it's no biggie at all. I actually appreciate it because before I would wake my phone often by mistake from the bottom buttons getting pressed in my pocket.
 
Once again I followed the "Robchaos" method to upgrade to VD and TR1.8. Went flawless, everything works. Updated PRL, firmware and did a cold boot. No LG boot hang.

Thanks to TR makers and Robchaos.
 
Last edited:
Status
Not open for further replies.

Latest posts

Trending Posts

Forum statistics

Threads
957,078
Messages
6,971,373
Members
3,163,708
Latest member
Ariwenni15