Phone Not Detected - AT&T LG Optimus G

Alright so my phone isn't being detected by any computer I plug it in to, recovery, bootloader, nothing.
Rom: 4.3 CM 10.2 by Dvhexer (same issues on other roms though so I don't think it's rom specific)
Kernel: hhouston's 4.3 kernel
Baseband: ATT-JB Stock
Bootloader: MAKOZ20i (I think this might be the issue)
I had converted to nex4 a LONG LONNNGGG time ago, but flashed the ICS tot to get back (again a lonnggg time ago) then updated to JB when it came out using a tot as well. Also attempted the JB camera fix... seemed to work since everything was working on RootBox.
Any help would be appreciated!

Jakeroxs said:
Alright so my phone isn't being detected by any computer I plug it in to, recovery, bootloader, nothing.
Rom: 4.3 CM 10.2 by Dvhexer (same issues on other roms though so I don't think it's rom specific)
Kernel: hhouston's 4.3 kernel
Baseband: ATT-JB Stock
Bootloader: MAKOZ20i (I think this might be the issue)
I had converted to nex4 a LONG LONNNGGG time ago, but flashed the ICS tot to get back (again a lonnggg time ago) then updated to JB when it came out using a tot as well. Also attempted the JB camera fix... seemed to work since everything was working on RootBox.
Any help would be appreciated!
Click to expand...
Click to collapse
No idea if the bootloader is your issue or not. But houstonn has posted links to the new 4.2 and 4.3 bootloaders in his root box thread. They should both be fairly near the end of the thread. I haven't updated to the 4.3 version yet, but 4.2 is working fine for me.
Sent from my Optimus G using Tapatalk 4

dandrumheller said:
No idea if the bootloader is your issue or not. But houstonn has posted links to the new 4.2 and 4.3 bootloaders in his root box thread. They should both be fairly near the end of the thread. I haven't updated to the 4.3 version yet, but 4.2 is working fine for me.
Sent from my Optimus G using Tapatalk 4
Click to expand...
Click to collapse
It's the 4.3 bootloader that I found on his thread
Does anyone have a link for the stock ATT JB bootloader?

Jakeroxs said:
It's the 4.3 bootloader that I found on his thread
Does anyone have a link for the stock ATT JB bootloader?
Click to expand...
Click to collapse
Doh. Guess that's not the answer then.
Sent from my Optimus G using Tapatalk 4

Bump still need help :/
Sent from my Optimus G using Tapatalk 4

Related

Take the OTA or stay on 4.1.1 for unlock/root?

Hi all, thanks for having such a helpful support forum. I just picked up a new Note 2 and it is on FW 4.1.1. I want to unlock and root/ROM and was wondering about the recommended sequence.
Should I first use Casual to unlock, or should I take the OTA (which I believe updates the bootloader) then unlock? Is there any benefit or detriment to using one way or the other? Thanks for any help.
Sent from my SCH-I605 using xda premium
Over in origional dev section adam has the new root,jailbreak, recovery for the new 4.1.2 ota. So if you want stock 4.1.2 with root and all that you would be safe to take the ota on stock then run CASUAL. I beleive either way your reallywanting 4.1.2 unlocked so you can have custom roms and ive seen some of the roms being updated for the vramc3 base anyhow. So if want you could run casual now with 4.1.1 that you have (you just picked it up so im assuming its all stock) and flash a cust9m rom that has 4.1.2 already implimented. cheak out the rooting/custom rom guide and the jailbreak thread and decide. In the end both paths will lead to the same place.
Just root/unlock 4.1.1 and flash a 4.1.2 VRAMC3 rom of choice in recovery...
Thanks for the help, I appreciate it. I thought it might be six of one half dozen of the other, but after recently going through OTA he11 on the DNA I'm really leery of any updates.
Sent from my SCH-I605 using xda premium
MunkinDrunky said:
Over in origional dev section adam has the new root,jailbreak, recovery for the new 4.1.2 ota. So if you want stock 4.1.2 with root and all that you would be safe to take the ota on stock then run CASUAL. I beleive either way your reallywanting 4.1.2 unlocked so you can have custom roms and ive seen some of the roms being updated for the vramc3 base anyhow. So if want you could run casual now with 4.1.1 that you have (you just picked it up so im assuming its all stock) and flash a cust9m rom that has 4.1.2 already implimented. cheak out the rooting/custom rom guide and the jailbreak thread and decide. In the end both paths will lead to the same place.
Click to expand...
Click to collapse
Yes, it was 4.1.1 stock. I took your advice and unlocked/rooted in 4.1.1. What is the difference in having a base of vrall4 vs. vramc3? I flashed Jelly Beans and am showing 4.1.2 on vrall4. If I went to a different ROM based on vramc3,would it cause any issues? Thanks for the help and sorry for the n00b questions or if they've been answered a lot, I haven't modded Samsung in a while.
Sent from my SCH-I605 using xda premium
eakeller said:
Yes, it was 4.1.1 stock. I took your advice and unlocked/rooted in 4.1.1. What is the difference in having a base of vrall4 vs. vramc3? I flashed Jelly Beans and am showing 4.1.2 on vrall4. If I went to a different ROM based on vramc3,would it cause any issues? Thanks for the help and sorry for the n00b questions or if they've been answered a lot, I haven't modded Samsung in a while.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Jelly Beans builds 15 and 16 are on the new base, VRAMC3, which is 4.1.2.
eakeller said:
Yes, it was 4.1.1 stock. I took your advice and unlocked/rooted in 4.1.1. What is the difference in having a base of vrall4 vs. vramc3? I flashed Jelly Beans and am showing 4.1.2 on vrall4. If I went to a different ROM based on vramc3,would it cause any issues? Thanks for the help and sorry for the n00b questions or if they've been answered a lot, I haven't modded Samsung in a while.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Many sites have a change log of all the changes that vramc3 brings to the Note 2. I flashed a stock vramc3 ROM that VZW pushed OTA. The only difference is that the Jelly Beans developer (beanstown106) rooted it, replaced the secure bootloader and made it flashable. So I've basically accepted the OTA but I'm still rooted and unlocked.
larry_thagr81 said:
Many sites have a change log of all the changes that vramc3 brings to the Note 2. I flashed a stock vramc3 ROM that VZW pushed OTA. The only difference is that the Jelly Beans developer (beanstown106) rooted it, replaced the secure bootloader and made it flashable. So I've basically accepted the OTA but I'm still rooted and unlocked.
Click to expand...
Click to collapse
Here's what I did: Stock 4.1.1 VRALL4 -> Unlocked/rooted with Casual --> Flashed Jelly Beans build 16
Now in my "About Phone" setup, i have this: Android version 4.1.2; Baseband version I605VRALL4; Build number JZO54K.I605VRAMC3
The build flashed just fine and it appears I'm on VRAMC3. However the baseband remains at VRALL4, I assume because JBeans doesn't update the baseband. Is there any reason to care about the "mismatch" between the baseband and the build? Should I go through the work to update the baseband, and if so what is the best method? I've been looking around the net and have found a bunch of conflicting answers to this question, so hopefully someone can straighten things out regarding the Note 2 specifically.
Thanks for the discussion.
Baseband is the modem. Just download and flash the zip.
Sent from my Note II using Tapatalk 2
eakeller said:
Here's what I did: Stock 4.1.1 VRALL4 -> Unlocked/rooted with Casual --> Flashed Jelly Beans build 16
Now in my "About Phone" setup, i have this: Android version 4.1.2; Baseband version I605VRALL4; Build number JZO54K.I605VRAMC3
The build flashed just fine and it appears I'm on VRAMC3. However the baseband remains at VRALL4, I assume because JBeans doesn't update the baseband. Is there any reason to care about the "mismatch" between the baseband and the build? Should I go through the work to update the baseband, and if so what is the best method? I've been looking around the net and have found a bunch of conflicting answers to this question, so hopefully someone can straighten things out regarding the Note 2 specifically.
Thanks for the discussion.
Click to expand...
Click to collapse
If you look at post #2 in the beans thread, there is a link to the new radio. Flash that and you will be completely up to date.
Sent from my SCH-I605 using Tapatalk 2
randy6675 said:
If you look at post #2 in the beans thread, there is a link to the new radio. Flash that and you will be completely up to date.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Thanks guys, found Scott's zip and flashed the baseband. Everything looks to be consistent, so I'm good.
Sent via Note2 with XDA Premium

[Q] roms

I have been running the snow jelly bean rom for months, its the only thing that has ever been done to phone the best i can remember. Everytime i try to install another rom other than that one or stock it soft bricks my phone. and help would be appreciated.
creed106 said:
I have been running the snow jelly bean rom for months, its the only thing that has ever been done to phone the best i can remember. Everytime i try to install another rom other than that one or stock it soft bricks my phone. and help would be appreciated.
Click to expand...
Click to collapse
Have you ever flashed teenybin or stock 4.1 with lgnpst or accepted the 4.1 OTA update? If not, and you are attempting to flash current 4.2 releases, that is your problem. You need to update to the current TZ. Read the teenybin thread.
Sent from my Optimus G using Tapatalk 4 Beta
roms
dandrumheller said:
Have you ever flashed teenybin or stock 4.1 with lgnpst or accepted the 4.1 OTA update? If not, and you are attempting to flash current 4.2 releases, that is your problem. You need to update to the current TZ. Read the teenybin thread.
Sent from my Optimus G using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok that has to be it I tried lgnpst with teenybin but when you have to select the .dsl nothing was in the menu and I couldn't find it so I gave up.

[Q] Installed AOSP 4.3 to Verizon SCH-i545

Well, I think I downloaded the wrong rom and flashed the wrong file. Here is what I downloaded and flashed:
http://forum.xda-developers.com/showthread.php?t=2348272
For whatever reason, I thought it would work. In my brilliance, I didn't perform a backup. I still have access to TWRP, so what do I do? Also, does 4.3 exist for the Verizon flavor that is Google Play edition?
Thats for the i9505 international version. Theres some 4.3 ports in the dev section. Since you didnt make a backup of stock youll have to odin back to stock and start over. All the odin images are in the dev section as well.
Sent from my SCH-I545 using Tapatalk 2
Did you think it would work because of the "guide" on how to run other carrier's ROMs?
And no one else I know is working on Google Edition 4.3. Mine's not done yet and I've been to focused on 4.2.2's build recently. I'll get back to it eventually.
As far as a fix:
Install another ROM. If you are desperate for SOMETHING 4.3, then install cyanogenmod 10.2(either of the 2 unofficial builds)
hexitnow said:
Thats for the i9505 international version. Theres some 4.3 ports in the dev section. Since you didnt make a backup of stock youll have to odin back to stock and start over. All the odin images are in the dev section as well.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
He said he still has recovery. All he needs to do is install a correct ROM
Dubbsy said:
Did you think it would work because of the "guide" on how to run other carrier's ROMs?
And no one else I know is working on Google Edition 4.3. Mine's not done yet and I've been to focused on 4.2.2's build recently. I'll get back to it eventually.
As far as a fix:
Install another ROM. If you are desperate for SOMETHING 4.3, then install cyanogenmod 10.2(either of the 2 unofficial builds)
He said he still has recovery. All he needs to do is install a correct ROM
Click to expand...
Click to collapse
Thanks gents. The only reason I'm itching for 4.3 is access to Bluetooth LE for my Fitbit. I used Cyanogenmod for a minute on 4.2 and it was amazing, but BT LE brought me back to stock. It lately started doing that Google Services using 70%+ of the battery, so I started hunting for a 4.3 rom.. in the wrong forum. WOOPS.
I'll probably go back stock until I can get 4.3 rom that has everything working.
Dubbsy said:
Did you think it would work because of the "guide" on how to run other carrier's ROMs?
And no one else I know is working on Google Edition 4.3. Mine's not done yet and I've been to focused on 4.2.2's build recently. I'll get back to it eventually.
As far as a fix:
Install another ROM. If you are desperate for SOMETHING 4.3, then install cyanogenmod 10.2(either of the 2 unofficial builds)
He said he still has recovery. All he needs to do is install a correct ROM
Click to expand...
Click to collapse
Good point, my bad. Thanks.
Sent from my SCH-I545 using Tapatalk 2

Better then custom Roms?

I am using the latest Pacman kitkat nightly and i am very satisfied with it.
I read the official KK rom is laggy. Is that true.
Any reasons for switching back to the original Rom?
Jequan said:
I am using the latest Pacman kitkat nightly and i am very satisfied with it.
I read the official KK rom is laggy. Is that true.
Any reasons for switching back to the original Rom?
Click to expand...
Click to collapse
mhl to hdmi does not work on custom roms (at least seems so..)
i'm planning to test a stock rom, maybe 4.3 since i can't find 4.4 for sgp311 and i can't update via pc companion since i unlocked bootloader.
apart from mhl issue i think ppls are very happy with custom roms so not many reasons to go back to stock.
Not finding much lag here, but YMMV. If you're happy with pacman stick with it. But, if you flash anyways you can always give stock 4.4.2 a try!
Sent from my SGP321 using XDA Free mobile app

at&t Optimus G roms vs international ?

Hey Guys I was just playing around with some roms since I got my phone and I was wondering can I flash a international LG Optimus g rom on my At&t version of the phone or will doing that brake it ?
They both use different kernels....I think it'll get stuck at boot.
Sent from my LG-E970 using Tapatalk
Rishi. said:
They both use different kernels....I think it'll get stuck at boot.
Sent from my LG-E970 using Tapatalk
Click to expand...
Click to collapse
what if I flash a new kernel ?
You can flash anything that uses [GEE] sources, so anything from international OR Sprint that says [GEE] will work as long as you flash a [GEEB] kernel afterward.
However, if it says [LS970] or [FL180], those roms wont work. Look for [GEE] and you'll be good.
OMGMatrix said:
You can flash anything that uses [GEE] sources, so anything from international OR Sprint that says [GEE] will work as long as you flash a [GEEB] kernel afterward.
However, if it says [LS970] or [FL180], those roms wont work. Look for [GEE] and you'll be good.
Click to expand...
Click to collapse
So if it's says Paranoid Android Mako it is safe to flash ?
OMGMatrix said:
You can flash anything that uses [GEE] sources, so anything from international OR Sprint that says [GEE] will work as long as you flash a [GEEB] kernel afterward.
However, if it says [LS970] or [FL180], those roms wont work. Look for [GEE] and you'll be good.
Click to expand...
Click to collapse
Old post but I'm poking around for a solution.
My E970 has been running Android 4.12 ROM eg8 beta 7-26 and associated kernel by MysteryEmotionz flawlessly for about a year. GPS locks quickly. I was able to install and configure Paulicat's LG Official Kitkat 4.4.2 http://forum.xda-developers.com/showthread.php?t=2771440 and it ran perfectly (no FC's) with one big but...
No GPS, which is a must have. GPS Toolbox never shows any satellites despite it showing satellites even when I am indoors and a few feet from a window on JB. I eventually tried numerous full wipes and flashes of the AT&T JB modem with both TWRP & CWM Touch, reinstalling stock AT&T 10j then wiping and reflashing the Korean KitKat ported from the [FL180]. I've tried both Paulicat's and the deodexed version by gourab4u with the same issue.
I've tried various build.prop edits and gps.conf changes. Is no one else experiencing this? Ideas?

Categories

Resources