Database Users

[Q] Buggy Display On Some Roms

Hello All,
I have been experiencing a very odd bug with a friend's gt540. The first occurred when I flashed the fastboot 2.1 rom. After flashing the rom it would boot and the screen would be all messed up. It's hard to explain, but basically there are static lines all over the screen with things misaligned and constant crazy flickering. You can still make your way through the menus though ever so slightly by pressing on the screen where the buttons are meant to be. Anyways, I freaked out but flashed a 2.2.2 aosp rom through fastboot and the issue went away and I naturally thought nothing of it.
More recently I decided to flash recovery through fastboot in order to flash newer roms and make nandroid backups, but after flashing swiftdroid and recovery, I found that the problem had returned. Not only is the screen all effed up on regular boot, but it is also messed up in recovery. It is by far the most bizarre things I've ever seen.
Swift droid, and oxygen, and pretty much all other gingerbread roms have given me this bug. I've flashed pretty much all of them through the buggy recovery. The only one's I've come across that have the screen working properly are Gingerbread Optimum 6.0 and his Froyo Optimum rom also.
My question is what the hell is going on? lol
At first I thought it was hardware, but if it was hardware why would some roms be fine and not others. Is there something that oxygen and swift have in common that might be the root of the problem? Has anyone experienced this on their phones before?
Maybe it's the kernel that certain roms are using?
I apologize for such a long question
Thanks a bunch for any help!

kweng_ca said:
Hello All,
I have been experiencing a very odd bug with a friend's gt540. The first occurred when I flashed the fastboot 2.1 rom. After flashing the rom it would boot and the screen would be all messed up. It's hard to explain, but basically there are static lines all over the screen with things misaligned and constant crazy flickering. You can still make your way through the menus though ever so slightly by pressing on the screen where the buttons are meant to be. Anyways, I freaked out but flashed a 2.2.2 aosp rom through fastboot and the issue went away and I naturally thought nothing of it.
More recently I decided to flash recovery through fastboot in order to flash newer roms and make nandroid backups, but after flashing swiftdroid and recovery, I found that the problem had returned. Not only is the screen all effed up on regular boot, but it is also messed up in recovery. It is by far the most bizarre things I've ever seen.
Swift droid, and oxygen, and pretty much all other gingerbread roms have given me this bug. I've flashed pretty much all of them through the buggy recovery. The only one's I've come across that have the screen working properly are Gingerbread Optimum 6.0 and his Froyo Optimum rom also.
My question is what the hell is going on? lol
At first I thought it was hardware, but if it was hardware why would some roms be fine and not others. Is there something that oxygen and swift have in common that might be the root of the problem? Has anyone experienced this on their phones before?
Maybe it's the kernel that certain roms are using?
I apologize for such a long question
Thanks a bunch for any help!
Click to expand...
Click to collapse
You can maybe download another fastboot ROM and try. It could've been corrupted. Can you please provide an image?

Rooted moto defy

Wifes defy is on stock froyo that I rooted with one click a few monthes ago. Has a custom recovery installed. Few questions.
1. If I try to boot into recovery, with volume down and power, it goes to stock recovery. I can boot into custom from the app. 2. I want to flash a basic gb rom on it, but afraid of problems since I can't boot into custom recovery to restore if needed. 3. How can I get past the stock recovery. My G2 is so much easier and I tired of searching with no conclusive answers.
Thanks
Sent from my Mikes HTC G2 with Google using xda premium

Ok did some more searching and tried to install the 2ndinit recovery thing and now the phone is stuck at black screen with white M.
HELP

I'm assuming power on with volume down doesn't do anything?
Turn off the Defy, remove the battery from the back. Then, if you volume up and power, can you get the Bootloader?
If you get that far then goto
http://forum.xda-developers.com/showthread.php?t=966537
and follow the "how to flash SBF-file" should get you on the right track. You can use the wiki and forums to find the right SBF, depending on if you want stock or custom ROM.

[Q] sgh i337m can't install any custom rom

Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.

wondakson said:
Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.
Click to expand...
Click to collapse
I too have been plagued by this same issue,
but only on a blue moon so to speak, I kept rebooting
and eventually my phone booted through that silly splash screen!

wondakson said:
Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.
Click to expand...
Click to collapse
First off I am hoping you are flashing from recovery and not trying something through goo manager. Second, it sounds as though you are skipping the wiping step before installing a new rom, you absolutly have to wipe cache/dalvik/ and factory reset all before flashing any rom.... also I wipe the system too to make it a clean install, make sure you put the rom of choice on the external sd and make sure you have a nanroid backup with your installed recovery twrp or cwm.....
PS lokidokie and saftey starp only apply to US versions (I337) not the Canadian I337M use only the roms build of this model.... I haven't had very good luck with cm based roms in the past so I tend not to flash those... I flashed one rom and the phone got super hot ... not sure what the issue was ... nand back to stock starter over with a differnet rom

Adizzzle said:
I too have been plagued by this same issue,
but only on a blue moon so to speak, I kept rebooting
and eventually my phone booted through that silly splash screen!
Click to expand...
Click to collapse
How long did you wait at the splash screen before booting again and again? After a new installation does the phone take extra time at the splash screen or is it at a different screen?

wondakson said:
How long did you wait at the splash screen before booting again and again? After a new installation does the phone take extra time at the splash screen or is it at a different screen?
Click to expand...
Click to collapse
Please... you need to provide some more info for people to help you..... rom you tried to install and the steps.. not tryin to be mean just hard to help without details....

Ahh I know the problem if your flashing all of them from the att section. It could be that all of those roms you tried have loki built into the kernel and is stopping you from booting. Are u choosing ones that say they are specifically for the Canadian model or the ones for att?

I would also suggest booting once first before flashing gapps. I am using this Carbon rom http://forum.xda-developers.com/showthread.php?t=2568699 and it's universal, for US or CA models. I highly recommend it.

[Q] Stuck on LG logo

I recently purchased a lg g2, the korean variant f320s, it was running kitkat with a lot of bloatware on top. I successfully rooted the phone and after that i found a cwm recovery installer for this version of the phone and i hooked up the phone and ran the installer on my pc, it finished installing and the phone rebooted into the custom recovery which was in chinese i went into a menu option and then pressed the back button on the screen and the phone instantly rebooted and got stuck at lg boot logo. Is there anyway to fix this? i have tried wiping cache, dalvik and factory reset from the recovery that i can access(chinese or something) but to no avail. I can access the download mode but my pc does'nt recognize the phone and this step is crucial for i guess installing the stock rom through lg flash tools. The phone however is recognized when im in recovery and i plug it in but it only shows as a drive that is faded out and entering it shows nothing. please help me i just got it two days ago

Have you tried to use adb to sideload a rom?

playerone_ said:
Have you tried to use adb to sideload a rom?
Click to expand...
Click to collapse
i'm sorry im a complete noob in this regard could you explain a bit on how to go about doing that? i am downloading the stock kitkat rom for the model its in kdz format

.
I flashed cloudy flex rom on it through external sd in recovery and now when i boot it up it stays on lg logo for a while then screen goes black and botts up again directly into CWM recovery, please help someone...

Same problem
sheroy1995 said:
I recently purchased a lg g2, the korean variant f320s, it was running kitkat with a lot of bloatware on top. I successfully rooted the phone and after that i found a cwm recovery installer for this version of the phone and i hooked up the phone and ran the installer on my pc, it finished installing and the phone rebooted into the custom recovery which was in chinese i went into a menu option and then pressed the back button on the screen and the phone instantly rebooted and got stuck at lg boot logo. Is there anyway to fix this? i have tried wiping cache, dalvik and factory reset from the recovery that i can access(chinese or something) but to no avail. I can access the download mode but my pc does'nt recognize the phone and this step is crucial for i guess installing the stock rom through lg flash tools. The phone however is recognized when im in recovery and i plug it in but it only shows as a drive that is faded out and entering it shows nothing. please help me i just got it two days ago
Click to expand...
Click to collapse
EXACT same problem as you... Every detail is exactly the same.
I am trying to find a solution. Any luck?

.
naleyb01 said:
EXACT same problem as you... Every detail is exactly the same.
I am trying to find a solution. Any luck?
Click to expand...
Click to collapse
Yeah you just need to flash a different rom through the sd card i tried cloudy rom but it didnt work then a i tried Lamhoang rom and it did the trick im on jellybean now though and i'll try flashing something else in a month or so

ALL FIXED
You are a legend!! Device back up and running.
Okay so I installed that same rom you did but the home/back/menu buttons weren't working so not wanting to muck around, I did some quick searching (which I should have done before >.<) and worked out how to get the Cloudy roms working on a korean device.
You need "Philz cloudy f320 recovery", the kitkat baseband and the rom. LINK
1 - Install the new recovery from zip and then boot back into recovery after this. You will now be greeted with philz recovery which is awesome.
2 - From here, proceed to install the rom as noted on the rom page.
This process worked for me for the Cloudy G3 V1.3 rom.
Thanks a lot for your help!! happy to return the favour! But i am hoping the above info already does that. :victory:

naleyb01 said:
You are a legend!! Device back up and running.
Okay so I installed that same rom you did but the home/back/menu buttons weren't working so not wanting to muck around, I did some quick searching (which I should have done before >.<) and worked out how to get the Cloudy roms working on a korean device.
You need "Philz cloudy f320 recovery",
1 - Install the new recovery from zip and then boot back into recovery after this. You will now be greeted with philz recovery which is awesome.
2 - From here, proceed to install the rom as noted on the rom page.
This process worked for me for the Cloudy G3 V1.3 rom.
Thanks a lot for your help!! happy to return the favour! But i am hoping the above info already does that. :victory:
Click to expand...
Click to collapse
Good to know you got it working again i still cant figure out why this problem occurred in the first place why did the phone brick from the recovery when the recovery was working fiblne after? Also i can just get the new recovery over the one already on the phone without removing the previous one right? Thanks for the info im gonna try out the cloudy roms soon

I have no idea.. something to do with that chinese recovery I am guessing.. There are still a few issues I am going to address but for now my phone is 95% working.
The only issue is that if I try go into download mode, it still doesn't go to the second screen (All i get is the small blue dots). Bit of a pain because that's something nice to fall back on if you ever need to.
I'll search around and try and figure these out in the next week or two, but I am happy with what I have for the moment.
Yep, you literally install the new recovery over your current one and then you can restart phone back into your rom and then reboot back into recovery using an app or the button method.

naleyb01 said:
I have no idea.. something to do with that chinese recovery I am guessing.. There are still a few issues I am going to address but for now my phone is 95% working.
The only issue is that if I try go into download mode, it still doesn't go to the second screen (All i get is the small blue dots). Bit of a pain because that's something nice to fall back on if you ever need to.
I'll search around and try and figure these out in the next week or two, but I am happy with what I have for the moment.
Yep, you literally install the new recovery over your current one and then you can restart phone back into your rom and then reboot back into recovery using an app or the button method.
Click to expand...
Click to collapse
Yeah i have the same issue with the download mode as well and the phone cant seem to sync properly with the lg mobile support tool either.Do let me know if you figure something out

My D850 will only run stock roms

Hey everybody,
I'm somewhat of a newb. I did successfully root and flash Paranoid Android on my old Galaxy S2 Skyrocket, but the LG G3 is giving me fits. I did have trouble rooting it, but finally found a method that worked. I've tried flashing CM, PA, RR, and more. All of them bootloop. I flash stock Lollipop and it boots right up. Did I miss something? Is there an easy answer? Do I unroot, go full stock, then try again? Thanks for any advice/suggestions!

First, you are in the wrong section. Should ask in the Q&A section.
Can you give more details? Did you downloaded the right rom? Do you say it bootloops but it just a long boot?

Sorry about that, but thanks for replying. I'm sure I have the right roms as I've tried several. I think I would have gotten at least one right. By bootloop, I mean the LG logo comes up, screen goes black, LG logo, black screen, LG logo, etc etc. I'm able to boot to recovery, and clear data, cache, dalvik, and/or factory reset, but that doesn't fix anything. At this point, I'm trying to unroot and flash back to original stock kitkat.