Just posted the official D800 nightlies!!!
http://get.cm/?device=d800
I posted the push to git earlier, which signified this =).
530 please have mods delete ur dev thread in the Dev section, and let official CM members/maintainers create one.
Tried this a little while ago, afterwhich all I booted to was the LG logo. LED changing colors. no more. Couldn't get back into twrp either. Ended up booting to the factory erase mode and got everything back.
You have had success installing this? I have the LG G2 (D800) 32 GB Black (which, if you ask me, the back looks like dark blue, not black like in pictures. an att thing? .
Anyway, thanks for any info.
Related
Hi, I have an AT&T LG Phoenix I bought straight up without plan. Long story short I have flashed a gingerbread rom onto it, and now I get a greenish, and once the phone goes to sleep (black screen) I wake it up and stays black, although I know its working because the volume keys work. I can't seem to get hold of a stock rom from LG site. Any suggestions would be great. Thanks
LG-P505
Dimitri
Sent from my AT&T 4G ATRIX.
Did you flash a ROM that was made for the Phoenix or one for the p500? Cause that will give you problems if you flashed the p500 one.
For KDZ you can try this:
http://forum.xda-developers.com/showthread.php?t=865479
no kdz available for phoenix. you gotta find someone's backup files. someone posted before. you gotta restore with those files.
@rty1138, I found the source files for the rom but nothing else. So I went ahead and tried to setup a build environment for it, but Ubuntu doesn't play nice with Java 5 so kinda got stuck there. Help a buddy out!
I know about this link... http://forum.xda-developers.com/showthread.php?p=15986005
Edit: Nevermind. Fixed it!
After a convoluted process and many mishaps on my part (I bricked it) my phone has a working, rooted and stripped down version of 2.3.6 on it. Which works as intended except the screen is now grainy and the colors are over-saturated. (side note: unfortunately I did not do a backup of the stock firmware-stupid I know)
I'm guessing this is a driver issue with the firmware or gpu because the pictures I took before I tried getting cyanogen on my phone now look very pixelated; almost like one of those cheesy after effects. I tried updating the firmware and it said I was current. Is there a way to update drivers? Do I have to find the original firmware for my phone (I looked on here the forum with the huge list of branded and unbranded and was at a loss)?
Also in my endeavor to attain the cm7 I tried rom manager which never worked even after getting the pre-rooted firmware. It will let me download the new clockwork but it does not appear to flash it and any attempt to install or reboot to clockwork doesn't do anything (gives prompts, I say yes, nothing happens). As a result of following the cyanogen wiki twice it says I have two custom firmwares and I cannot get into clockwork at all. I could the first time through before I bricked it but now I can't. Is there a way to remove the extra kernel?
The only reason I have a working phone is because of Odin. Is there a way to use Odin to install cm7 and would that fix the display issues or am I better off finding the stock firmware and hoping the display will default back to working?
Thank you in advance,
noob
http://forum.xda-developers.com/showthread.php?t=1313659
Branded? Unbranded?
There is only one variant of the I777 - AT&T Branded. Anything in the Development forum for the I777 will work on an I777.
It's not like the I9100 with a bunch of minor subvariants.
drmorbo said:
After a convoluted process and many mishaps on my part (I bricked it) my phone has a working, rooted and stripped down version of 2.3.6 on it. Which works as intended except the screen is now grainy and the colors are over-saturated. (side note: unfortunately I did not do a backup of the stock firmware-stupid I know)
I'm guessing this is a driver issue with the firmware or gpu because the pictures I took before I tried getting cyanogen on my phone now look very pixelated; almost like one of those cheesy after effects. I tried updating the firmware and it said I was current. Is there a way to update drivers? Do I have to find the original firmware for my phone (I looked on here the forum with the huge list of branded and unbranded and was at a loss)?
Also in my endeavor to attain the cm7 I tried rom manager which never worked even after getting the pre-rooted firmware. It will let me download the new clockwork but it does not appear to flash it and any attempt to install or reboot to clockwork doesn't do anything (gives prompts, I say yes, nothing happens). As a result of following the cyanogen wiki twice it says I have two custom firmwares and I cannot get into clockwork at all. I could the first time through before I bricked it but now I can't. Is there a way to remove the extra kernel?
The only reason I have a working phone is because of Odin. Is there a way to use Odin to install cm7 and would that fix the display issues or am I better off finding the stock firmware and hoping the display will default back to working?
Thank you in advance,
noob
Click to expand...
Click to collapse
Are you able to reboot the phone in recovery using ADB?
Its gotten to the point where nothing I try works. I managed to get cm7 installed and it got stuck in a boot loop. Flashed back to the stripped down version again. Everything that could go wrong has. For now I just want to go back to whatever firmware came with my phone out of the box. The startup logo was at&t so I guess I'll go for the branded version (which I can't find on here--its almost 3 am I apologize for my idiocy) and hope the screen issue is resolved.
Thanks again
defeated
drmorbo said:
For now I just want to go back to whatever firmware came with my phone out of the box. The startup logo was at&t so I guess I'll go for the branded version (which I can't find on here--its almost 3 am I apologize for my idiocy) and hope the screen issue is resolved.
Click to expand...
Click to collapse
Which you can't find? Someone posted the link to my return to stock guide in post #2 of this thread.
If you return to complete stock using Entropy512's Return/Unbrick to stock package, you will regain the AT&T boot logo instead of any custom boot logo. The phone will be just like it was when you first took it out of the box.
If you want the stock ROM plus root, Entropy has a package for that also. Just flash one of his packages with Odin, or use the One-Click downloaders for his package that are linked in my guides.
Update: You can also download all of these from my Download Repository.
Okay so I did the return to stock without root one click and that went fine. However the display is still not working properly. Solid colors are fine and I even went into the debug screen and tested all the colors. They were brilliant but any dimming or shading of two colors just looks wrong. The only thing that I can think of is the bootloader is wrong. It says my phone is a I9100 which it isn't. However I'm not sure why a bootloader would affect the display. Does the I777 have a different initialization process for the gpu? Or is the issue somewhere else?
drmorbo said:
Okay so I did the return to stock without root one click and that went fine. However the display is still not working properly. Solid colors are fine and I even went into the debug screen and tested all the colors. They were brilliant but any dimming or shading of two colors just looks wrong. The only thing that I can think of is the bootloader is wrong. It says my phone is a I9100 which it isn't. However I'm not sure why a bootloader would affect the display. Does the I777 have a different initialization process for the gpu? Or is the issue somewhere else?
Click to expand...
Click to collapse
That might affect it but I highly doubt it.
So do you have any idea what could have caused it? I tried searching the forums but I couldn't find somebody with a similar problem.
Where exactly does it say your phone is I9100?
It shows "Samsung galaxy s II I9100" before the at&t load screen.
drmorbo said:
It shows "Samsung galaxy s II I9100" before the at&t load screen.
Click to expand...
Click to collapse
The return to stock did not complete correctly. This screen appears after flashing a non-stock kernel with Odin/Heimdall.
Entropy512 said:
The return to stock did not complete correctly. This screen appears after flashing a non-stock kernel with Odin/Heimdall.
Click to expand...
Click to collapse
Yes. The very first method I tried was the heimdall from the cyanogen wiki. I've used various methods without success. However the last effort was to restore the phone and I used the one click stock without root. Was it supposed to restore the bootloader? Also I updated ota and the display works much better. The remaining discoloration/pixelation could have been there all along as I didn't wait long to put cyanogen on it (1 day) and I have nothing to compare it to.
drmorbo said:
Yes. The very first method I tried was the heimdall from the cyanogen wiki. I've used various methods without success. However the last effort was to restore the phone and I used the one click stock without root. Was it supposed to restore the bootloader? Also I updated ota and the display works much better. The remaining discoloration/pixelation could have been there all along as I didn't wait long to put cyanogen on it (1 day) and I have nothing to compare it to.
Click to expand...
Click to collapse
The return-to-stock-with-root shouldn't touch bootloaders - but it should have restored a stock kernel. IF you're getting the "yellow triangle" I9100 boot screen, the last thing flashed with Odin/Heimdall was NOT a stock kernel.
There is no yellow triangle. I used the exe from the link in the first response in this forum. In any case I'll throw a picture of the phone while turned off but charging tonight. The display issues aren't grave but they are noticeable and annoying. Do you know of an app that allows you adjust graphical/display settings? Maybe it would suffice.
I found information concerning my display issues. Apparently it's an issue with the phone. Its called black crush. My phone has this and oversaturated red. So shading details are pixelated and reddish.
http://forum.xda-developers.com/showthread.php?t=1124669
Also I noticed people repeatedly mentioning screen modes under setting>displays however my phone does not have this option. Also all of the mentions have been under the forum for the regular version of the phone not the AT&T variant. Is the AT&T version missing this option or am I blind?
drmorbo said:
I found information concerning my display issues. Apparently it's an issue with the phone. Its called black crush. My phone has this and oversaturated red. So shading details are pixelated and reddish.
http://forum.xda-developers.com/showthread.php?t=1124669
Also I noticed people repeatedly mentioning screen modes under setting>displays however my phone does not have this option. Also all of the mentions have been under the forum for the regular version of the phone not the AT&T variant. Is the AT&T version missing this option or am I blind?
Click to expand...
Click to collapse
AT&T version is missing screen tuning unless you run a custom ROM that readds it like Serendipity VIII or Unnamed.
Okay cool. So I used the one click with root and the wifi is broken and it won't let me do an OTA. however I had previously used the one click without root and I was able to OTA and that solved the broken wifi. What would be the easiest way to fix the wifi?
Flash cwm>factory restore/wipe (I don't have cwm and I remember the cyanogen wiki way to get cwm messed up my soft buttons--two didn't work anymore)
Or
Flash the 12/21 dd kernel (I did originally try this route. However Odin didn't recognize the kernel. I even repackaged I with just zImage. Still nothing.)
Thank You again Entropy
DrMorbo
Sounds like there is something broken about the oneclick... Try flashing the return-to-stock package with Heimdall. Heimdall also lets you flash kernel zImages without packaging into a tar.
However Heimdall needs its own driver mojo on Windows - I can't really help you with this, I've flashed a device from Windows only once, and that was the Tab 10.1 because Heimdall won't talk to it.
Nevermind. I tried the update a third time. It decided to work (48 hours later). Everything works. Wifi works. The screen is better (I used voodoo screen tuning to greatly diminish the black crush and red saturation. I can finally customize my phone now. Any nifty apps you know of Entropy? (Regular or root needed)
Thank you again Entropy,
DrMorbo
Hello,
I have had my T-mobile LG P509 Optimus T for about a year now and I have had it rooted just as long. My husband plugged it into his PS3 the other day and it went to the fastboot mode started screen, thanks to the wonderful posts on here I was able to fix it. Then the following day it got left outside all day long, battery was drained and the phone was off. I charged the phone and when I turned it back on it would not go past the Android Logo screen. Again thanks to all the wonderful posts on here I was able to get it back up and running. The problem I am having now is that every time the phone gets turned off, it gets stuck on the android logo screen again and I have to re install the ROM. the recovery is not helping. It is quite tedious to have to constantly re install everything from Google Play just to get my phone to work. Is there anyone out there that can give me a permanent fix or give me a ROM that is specific for the LG P509 instead of the one I am using currently that is for the LG P500 Optimus One.
Android Version 2.2.2
Kernel Version 2.6.32.9
Build Number NuDroid T1D-S
Software Version LG-P509 V10s
Recovery Rom is Original_Recovery_ThunderG.zip
ROM is FRG83.zip
p509
the roms are the same
my phone is a p509 but im running every rom on this forum fine and everything goes well except some cases of data because tmobile uses a "funny sim"
P509
I figured they were. I am just trying to find out why every time my turns off and I turn it back on I get stuck on the Android screen and it goes no where, Doing the recovery of my back up from the recovery menu (volup+home+power) does nothing I mean I actually have to re install the ROM. Is there anyway for me to find out what is wrong. What ROMS are you running if you do not mind me asking. Also is there an actual list anywhere of the Factory System Apps that I can freeze with my Titanium Backup. I have the Pro version. PLEASE HELP. I have had this rooted for over a year with no problems and now it just wants to act all crazy.
P509
hrpalmer611 said:
I figured they were. I am just trying to find out why every time my turns off and I turn it back on I get stuck on the Android screen and it goes no where, Doing the recovery of my back up from the recovery menu (volup+home+power) does nothing I mean I actually have to re install the ROM. Is there anyway for me to find out what is wrong. What ROMS are you running if you do not mind me asking. Also is there an actual list anywhere of the Factory System Apps that I can freeze with my Titanium Backup. I have the Pro version. PLEASE HELP. I have had this rooted for over a year with no problems and now it just wants to act all crazy.
Click to expand...
Click to collapse
It sounds like the rom is corrupted. I believe from your description it fails to load properly on reboot. there are a lot of options available for you. Most of the roms are for new baseband. Unfortunately you will have to experiment. Read the posts carefully, start here first http://forum.xda-developers.com/showthread.php?t=1152306. Next I would read this http://forum.xda-developers.com/showthread.php?t=901247 this will tell you almost everything you want to know. I would upgrade to the new baseband v20g http://forum.xda-developers.com/showthread.php?t=1149530 . Then I would upgrade the rom there are many good roms available. I wish you luck when I first stated flashing roms there were three days of hell before I started to get amazing results. I have a P509 on t-mobil network, and currently running cyanogem mod rom 7.2.0 RC1 it is gingerbread 2.3.7 New basband with lots of script tweaks. the performance is very good. good luck I will check back to see if I can help.
P509
Thank you,
I will give those a look and see what happens. I will let you know.
same
i have same problem i have p509 and my phone fell during kdz and i think it partly works but no rom can load up :O
P509
I have done many different options. The one that I found to be the easiest is to take your micro sd card and put it in the adapter into your PC. Then in the ROMs section of this forum find a ROM that suits you. or you can use the Rom I listed in my initial post being the FRG83.zip download it to your PC then copy it to your SD card. Put your SD card back into your phone. Then go to the recovery menu. Volup+home+power hold until the recovery menu pops up. then wipe the data, then install zip from sd card choose the file that you just downloaded and let it do its thing. It has worked for me numerous times. All else fails follow the guide that is posted above very good info to have.
After rooting my phone for the first time about a month ago, I though to myself "This is awesome!". After thinking that, I dug deeper and deeper into the Android Universe and found custom ROMs. The first one I flashed was just a standard 4.0.3 ROM that worked fine. The second one I flashed was a CM10 JB ROM (for my device), and this also worked. But yesterday, (22nd August) I realised that flash player wouldn't work, even though I had the .apk installed on my phone. I found out what dual-booting was when I flashed the CM10 ROM but I didn't need to do it at that time. I downloaded the latest Siyah kernel, flashed it, turned on my phone and it worked fine (CM10) and then I realised I had to go back into recovery mode to change my primary and secondary ROM. I did this, and then next time I tried to turn it on, it just stays on the boot logo. (Siyah logo when I had the SIyah kernel on there and the default SGS2 boot logo with the yellow triangle when I changed back to a plain, old, boring, nothing special kernel). I am currently downloading an OSP file to see if that will help.
That is pretty much all the info I can supply with my knowledge of Android devices but I can try and give some more if needed.
Also, do you think if I took my phone back to **** Sith (Australian retailer where I bought it from) and played dumb (eg. I went to turn it on and the screen just stayed like this, I even left it like that over night and nothing happened) they would give me a new one? I know it voids warranty when you root but maybe if I get someone who doesn't know much about these phones I could get lucky.
Please give me as much help as you can. I haven't told my parents yet because I'm not prepared to face their wrath yet. God knows what they'll do to me!
So your hoping theres someone like you on the other side of the counter when you take the phone back?
Can you get into recovery/download mode lol
Maustin96 said:
After rooting my phone for the first time about a month ago, I though to myself "This is awesome!". After thinking that, I dug deeper and deeper into the Android Universe and found custom ROMs. The first one I flashed was just a standard 4.0.3 ROM that worked fine. The second one I flashed was a CM10 JB ROM (for my device), and this also worked. But yesterday, (22nd August) I realised that flash player wouldn't work, even though I had the .apk installed on my phone. I found out what dual-booting was when I flashed the CM10 ROM but I didn't need to do it at that time. I downloaded the latest Siyah kernel, flashed it, turned on my phone and it worked fine (CM10) and then I realised I had to go back into recovery mode to change my primary and secondary ROM. I did this, and then next time I tried to turn it on, it just stays on the boot logo. (Siyah logo when I had the SIyah kernel on there and the default SGS2 boot logo with the yellow triangle when I changed back to a plain, old, boring, nothing special kernel). I am currently downloading an OSP file to see if that will help.
That is pretty much all the info I can supply with my knowledge of Android devices but I can try and give some more if needed.
Also, do you think if I took my phone back to **** Sith (Australian retailer where I bought it from) and played dumb (eg. I went to turn it on and the screen just stayed like this, I even left it like that over night and nothing happened) they would give me a new one? I know it voids warranty when you root but maybe if I get someone who doesn't know much about these phones I could get lucky.
Please give me as much help as you can. I haven't told my parents yet because I'm not prepared to face their wrath yet. God knows what they'll do to me!
Click to expand...
Click to collapse
Can you still boot to your second Rom ie CM10?
Can you still get to CWM recovery?
If your answer are yes.
-boot to CWM recovery
-flash your Samsung custom ROM again
-wipe dalvik cache
-wipe permissions
-flash Siyah kernel
-reboot phone
Swyped from my Samsung Galaxy SII
Dude, take a chill pill. This is XDA, there are a lot of awesome people here who might know a solution to your problem
Luckily, you are not the only person alive to screw up their flash player while they were on cm.
If you can go to download mode, you can start all over again from scratch by flashing a stock firmware.. and from there, let your custom stuffs begin!cheers
Sent from my brain using telekinesis
Thanks for all the responses guys!
I have managed to fix through scouring every corner of the internet. It probably took a lot longer than it should have since it i sme, oh well! I'm just so thankful everything is working again.
I think I'll stay away from dual booting!
How do I close this thread?
Send a PM to prbassplayer. He's the moderator.
Sent from my Galaxy S2 GT i9100
Thread closed
Per request.
(I had included all links to the zips and files I used but XDA wouldn't let me include those due to this being my first post.)
I need help. I messed up pretty bad. I have a Galaxy S3 T999N on Metro Pcs. A buddy got me into root about a year ago. It's been slow for me, because I'm scared of bricking my device. (I've read many guides, forum posts and watched many videos but I've never had the courage to flash a custom ROM, even though it looks really fun.)
SPECS
Galaxy S3 T999N 4.2.1 on Metro Pcs
The phone was rooted with Odin 3.07.
Later I used Odin 3.09 to flash custom recovery for TWRP. (Zip: openrecovery-twrp-2.3.1.1-d2mtr)
A couple days ago, I finally got enough courage to flash a custom rom. I Used titanium to back up all my apps, then used twrp to make a restore.
I used TWRP on the nightly I found (cm-11-20140217-NIGHTLY-d2mtr.zip). It failed. I apologize for not doing a log dump... I can't remember exactly what the log said. Something like (ERROR 7 or STATUS 7)
I wiped the cache and dalvik cache and used the recovery I made before the attempt at cyanogen, then I wiped the cache and dalvik cache again. TWRP said it was a successful recovery. When I went to reboot into the stock OS... It just hangs at the "Metro PCS Wireless for all" intro screen.
I started to do research on that symptom. found all kinds of threads on boot loops.
I tried leaving the battery out for 30 seconds, then booting into twrp to wipe the cache several times.
Then I tried the same steps with the dalvik included.
Then I repeated that same process with a factory reset. (several times.) Always the same result.
I even tried that entire process with wiping the entire phone, DATA, cache, dalvik, system, then doing recovery again. Doesn't work.
My recovery isn't working. I don't know what to do. (ALSO, INTERESTING SYMPTOM: I've noticed after doing the recovery, during the boot, the part when the black with white font Galaxy splash screen plays, the sound that it makes when the blue galaxy animation forms... it sounds like that sound starts late and gets cut off, then it sticks at the "Metro PCS Wireless for all" intro screen. It only does this after a factory reset, it doesn't make any sound at all otherwise because I think my phone's sound was turned off when I made the restore.)
I had a tech buddy try to find my stock rom, he wasn't sure which one to use. (confusion between Metro pcs and T-mobile S3s discussed below.) He told me to try another custom rom. If I could get one to work, that means the phone is still good and the custom rom would give me time to possibly find the stock rom for my model. (I just paid my bill, I'm wasting service right now.)
First I tried to find a stock rom for my phone. If I used "metro pcs" as a part of the google search, it came back with mostly results pertaining to Samsung Galaxy S III SCH-R530M (I've owned the SCH-R530M... it was white and the first model variant that Metro PCS had. I think it was only 4G not 4GLTE) All I could find for the T999N is a T-Mobile stock 4.1 but my device is 4.2. and on metro PCS. I was told that when the device updated to 4.2, partitioning and other things changed on the device specific to a 4.2 setup. So if I tried to use a 4.1 stock rom I could brick my device. (In the reading I've done, I've never came across anything that said that on the internet.)
So I moved on and started looking for another custom rom. I had seen a lot of videos on pacman. Looks awesome. After doing some reading, I found pacman on the android forums. (pac_d2mtr-20130510-v22.1.1)
IT WORKED! I was super excited. I got this X-mas-ish feeling in my stomach, like I just opened an awesome gift.
The Wifi Worked, but the camera, DATA and calls did not work. I was still super excited! First I explored Pacman, and ended up in the about phone section. (Model number was SCH-R530M! This probably isn't going to function the way I'd like, I thought to my self.)
The more I played with pac's interface, the more it kept freezing. Had to do a bunch of battery pulls.
On the same thread mentioned above, There was some talk about MMS problems, someone suggested flashing this for 4g and MMS fixes. (AOKP TO METRO FIX.zip) using TWRP, It flashed successfully but didn't fix my calls or DATA.
BY THIS TIME, IT WAS LATE, HAD BEEN READING FOR HOURS AND I WAS FEELING TIRED AND REALLY BUMMED.)
Then I tried to look for my models modem files to flash. (I'll be honest, I'm new to this, I had no idea where to look.) eventually I found a modem repostiory on a thread(Can't find the site in my history, but I found the link) I found this: USC_T999N_GalaxyS3_UVBNC1_Modem. I flashed that, it didn't work either.
At that point, I think I flashed AOKP TO METRO FIX.zip and USC_T999N_GalaxyS3_UVBNC1_Modem.zip out of panic and frustration of not having a phone. Could I have messed up my radios? is it possible that even if I ever get back into my stock, could the radios be messed up now cause I flashed AOKP TO METRO FIX.zip and USC_T999N_GalaxyS3_UVBNC1_Modem.zip?
I'm scared... and burned out. I really need a phone and don't have money for an insurance deductible or a new phone. (I know... what a stupid noob, right?)
I hate my current job and have been on the hunt for about three months, which paid off with a couple interviews. I'm waiting for 2nd interviews to be scheduled. How will they or anyone else interested in
hiring me, reach me?
A lot of the threads I've read, people report that their device can't boot into recovery or boot into download mode. MINE CAN STILL DO BOTH.
I'm not sure what to do. I appreciate anyone who took the time to read all of this.
TO SUM IT ALL UP, I WAS WONDERING:
1. Is there another method how to fix the boot loop problem?
2. I also heard that T-Mobile and Metro PCS merged, which is why I have a T-Mobile model. Would it matter if I used the T Mobile Stock (or custom rom.) When technically I'm on Metro PCS?
2a. Would that effect my ability to make calls?
3. Also, is it true that using a 4.1 stock rom after having taking the 4.2 update, will that brick my Phone?
3a. Is there a place that offers 4.2 stock roms? I could only find 4.1 (not sure where to look.)
3b. My wife has the exact same phone, same model, rooted, only hers is 4.1 and mine is 4.2 - Could there be a method or some useful way to use the firmware from the wife's phone?
4. Is it possible that if I ever get back into my stock, could the radios be
messed up now cause I flashed AOKP TO METRO FIX.zip and USC_T999N_GalaxyS3_UVBNC1_Modem.zip while messing with pacman?
5. My phone can still go into download mode and it still boots into recovery. Is there any hope that I can save this? What else do I need to consider? Is all my network settings stuck on the recovery?
THANK YOU FOR YOUR TIME.