Related
I did not see any thread for this so opening a new one so its easy to find.
I rooted my phone using gingerbreak and like a wiseazz, loaded a custom recovery image of "recovery-RA-GNM-thunderg-1.2". Although the costom recovery loaded fine, I am stuck with a phone which has only blue and green colors. I loaded one of the custom 2.3 ROMs by Andy and it loaded fine, but still the graphic display is all messed up, only green an blue and some other tinges. When I look at the About phone I see that it says the model number as LG P500 , although mine is LG P506. Any help people??
My wife will kill me. Its her phone!!
why would you flash a P500 ROM to a P506 ? did you make a backup ?
I made a backup of the ROM, but I did not backup the recovery.img.
Can I try NAND restore of the old ROM. I have my doubts if that would work, because as soon as I put the custom recovery in it. It started getting messy colors. But I will try. If any one else has any pointers please let me know.
Also, I ready in one of these posts that Thrive and Phoenix are just variants of Optimus One, architecturally same. Bad decision
Ok. An update. I did a Nandroid backup and I have the ROM which came with the phone. It sucks. But I guess I will have to wait till one of the brainys in here come up with a good "Custom Recovery" and "Custom ROM" for LG Thrive.
I have a LG Optimus T and the LG p500 roms work fine with no problems. I would of expected the same for the att version. I guess you have to wait for one that supports it.
Sent from my LG-P500 using XDA App
More bad news. I thought if I can mix and match boot.img of LG506 with the system.img of P500, I can get away by loading the Custom ROM.
Bad Bad Bad decision. Right now, its in a bricked stage. Basically stuck in something called..fastBoot udc_start()...
Its not getting to recovery mode whatever I do. I wanted to get to recovery so I can restore NAND backup. I can even get to adb so I can start in recovery....
Somebody help please
Can anyone help me. I tried all possible routes to unbrick my phone. It keeps getting wosre and worse. Right now its stuck in "Emergency Mode". I have the NAND backup file with system.img and boot.img, but cant do anything with it since no ADP or customer recovery. I tried to do a KDZ update, but I think i need the v11e_00.kdz file for P506. Can anyone give me some pointers to recver my phone.
I have a thrive as well and I get the weird blue green screen using the unofficial cm7 rom from the optimus dev section. Luckily I back up the phone with rom manager first so now im back to where I started.
edit: Well after your post I decided to try it again... mistake. Now im stuck at the cm7 logo and im not really sure how to fix it...
edit 2: cant load recovery either... ****
I have tried out the custom roms and i get the strange color problem too. It's strange how the cell phone board is P500 but the model is P506. The phone must be different somehow hardware wise. Hmm....
Ok. An update.
I bricked my phone trying to experiment. I sent it out to LG repair and they put in the stock ROM and sent back. I will not be continuing my experiments again
Can any big hearted rooters help the LG thrive owners please..
Do experiments but cautiously
Sent from my LG-P500 using XDA Premium App
I have a similar problem with my phone now. I flashed rom and now my phone gets stuck on boot screen. I can get to recovery. But my backups not there for sum reason.
Edit: I found what was supposed to be tha stock rom for my phone but didnt work. Gets stuck after lg screen goes away. It will go to recovery. Does anyone have a copy of a nand
Backup for a P506 thrive?
I've managed to get myself in the same situation would you happen to recall the LG number you called or have a lead on who I can contact at LG. I will continue to search also. Thanks in advance.
Ok wow. You need to go to WWW.androidcentral.com once there go to the Phoenix/ thrive thread. We have a custom kernel made by joban to run the p500 roms without the color issue. Also have how to threads for rooting, CWM, and flashing.
Running oxygen v1.1 w/ joban kernel,cwm on my LG Phoenix. And its awesome. Fast, great battery
Don't forget to hit the thanks button!
Sorry that it took me forever to get back to this, but just one question. Are the kernels for the Phoenix and Thrive exactly the same?
No issues that i can recall being specific to the kernel.
Question: I have rooted the phone and installed ROM Manager. Set up Rom Manager as Optimus One. Here is the issue: I am able to reboot normally and keep root. But when I select to reboot into recovery from ROM Manager, the phone does a default setup and I'm back to factory default. When I try to get into recovery by using the PWR+Home+Vol up (and vol down at times), I get into fastboot with "udc_start()". Which I'm guessing is normal. What am I missing to get into recovery?
Thanks.
Assuming you have a thrive. You may want to check this out.
http://forums.androidcentral.com/t-lg-phoenix-thrive/138186-how-clock-workrecovery-mod-cwm-6.html
There appears to be a hickup with thrive and CWM.
lg thrive p506 EMERGENCY MODE!
my lg thrive come on and immediately goes into emergency mode. i have been searching for about two weeks for anything that will help me in xda forums, and youtube and phandroid. i cant find anything that conclusively brings the phone out of emergency mode. can anyone direct me to a program or forum that might be of assistance?
need more info. are you on stock unrooted, just rooted, or rooted with custom recovery and rom?
what were you doing when this happened?
^^^^need to know^^^^^^^^^
try this and let me know what you get. hold at same time Home+vol down+power.
hi guys im new to the samsung modding, but have been messing with modding since the G1. I have spent hours reading threads and nothing seems to work. I have rooted and installed rom manager. i heard it has issues. im trying to install a rom but i get signature verification failed error in the black and blue screen android recovery 3e. any help is greatly appreciated and im sick of going around in circles.
glow1284 said:
hi guys im new to the samsung modding, but have been messing with modding since the G1. I have spent hours reading threads and nothing seems to work. I have rooted and installed rom manager. i heard it has issues. im trying to install a rom but i get signature verification failed error in the black and blue screen android recovery 3e. any help is greatly appreciated and im sick of going around in circles.
Click to expand...
Click to collapse
First delete everything to do with rom manager, second download krylon360 clockworkmod final, third push the recovery to system/bin do not delete original recovery just over write it, and finally put update.zip on the root of sd card. Them power off phone hold volume up and down press power when in recovery select reinstall packages and clockworkmod will load up.
EDIT: rom manager has issues with galaxy s 4g.
Sent from my SGH-T959V using XDA Premium App
thanks i figured it out. i was using linda file manager. i then used another one in the market thats under root explorer. i got it to overwrite correctly. thanks alot! its now orange and currently backing up my system.
when you get a chance, flash the bali 3+ kernels too. will make handling cwm easier because it keeps your mounts and you no longer need the update.zip
I did search, but in all honesty Im not really sure what Im looking for. Yesterday I rooted with the Ace Hack. Then today I was looking through Rom Manager, and I downloaded cyanogenmod, and when it finished it wanted to load it, so I let it. Ive done two backups prior to this. Now when I turn it on the white HTC screen comes up, then it goes to the cyanogenmod 7 screen, skateboarding android with a ring around him and a loading arrow. And thats all it does, over and over. Is there a way to boot to the backups? A certain button combonation I should be using? Specific terms I should search for? Please, at least, point me in the right direction.
slipmagt said:
I did search, but in all honesty Im not really sure what Im looking for. Yesterday I rooted with the Ace Hack. Then today I was looking through Rom Manager, and I downloaded cyanogenmod, and when it finished it wanted to load it, so I let it. Ive done two backups prior to this. Now when I turn it on the white HTC screen comes up, then it goes to the cyanogenmod 7 screen, skateboarding android with a ring around him and a loading arrow. And thats all it does, over and over. Is there a way to boot to the backups? A certain button combonation I should be using? Specific terms I should search for? Please, at least, point me in the right direction.
Click to expand...
Click to collapse
You'll need to do a complete wipe to install CM over an existing sense build. Sense stores the dalvik on the data partition and CM7 stores it on the cache partition. If you don't do a full wipe, then the dalvik never gets set up properly.
You should still be able to get into cwm recovery via hboot. Make sure phone is off (pull battery if necessary). Hold VOL-DOWN button while pressing power for about a second. You should end up in the HBOOT screen. Select recovery and press power. Hopefully CWM recovery will boot up and you can just do a "Wipe data/Factory Reset" and be good.
I had just found out how to boot to recovery seconds before I checked the thread again. Instead I went to backup and recover, and restored from a backup, and it didnt work. So I am trying what you suggested, I really appreciate you giving me all the steps required.
I may have told it to not delete the dalvik when it wanted to start up cyanogenmod.
So what is the best way to download roms and switch between them?
slipmagt said:
So what is the best way to download roms and switch between them?
Click to expand...
Click to collapse
1 suggestion...ditch rom manager. I've had issues before where it messed up my downloads. Not everyone has this issue I will say, but I would try not using it. All the devs update their threads here on xda with the latest versions in their threads. Download them from the site, boot into recovery,back up your current rom, and flash away!
I got your 10 char right here
cwhitney24 said:
1 suggestion...ditch rom manager. I've had issues before where it messed up my downloads. Not everyone has this issue I will say, but I would try not using it. All the devs update their threads here on xda with the latest versions in their threads. Download them from the site, boot into recovery,back up your current rom, and flash away!
I got your 10 char right here
Click to expand...
Click to collapse
Agreed. I've never used RomManager with the Inspire, but I had nothing but problems with it on my Aria.
It gone. How do you switch between roms then?
slipmagt said:
It gone. How do you switch between roms then?
Click to expand...
Click to collapse
Like I said above...use the threads to find the roms. Download them and flash them in recovery. ALWAYS create a back up so you can flash back to your back ups if you want. All that can be done in recovery.
If you do not know how to do this then my thoughts on why rom manager exists are true. Search the threads and learn how to do all the fun stuff without rom manager and without needing someone to hold your hand. (Wasn't being mean just a figure of speech)
I got your 10 char right here
Hello, I have a Motorola Defy which i have rooted and installed clockworkmod on it. I tried to install Cyanogen mod 7.1 from the website. The phone got to the boot screen where it continued to cycle through it thing and nothing more. I restarted the phone and now it gets stuck at the first screen where its says "google". I tried to enter recovery again (power + volume down) and clockworkmod is completely gone. I want to go back to the stock OS so it atleast works again. Ive tried using the update.zip option in the stock recovery mode but I keep getting an error "failed to verify whole-file signature" when using a signed copy of cyanogen mod. I also tried putting my backup in a zip with the same error. Ive even tried formatting my sd card. What do i do?
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a different way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Marvelicious75 said:
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a dirrerent way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Click to expand...
Click to collapse
I cant use the program as my phone doesnt get detected when connected to my pc.
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Marvelicious75 said:
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Click to expand...
Click to collapse
I fixed it, there were a different set of buttons to hold to get into boot loader. The default recovery was not over written as i thought (happened to all my other phones). Thank you very much for you help. It has been very much appreciated.
Glad to hear it.
So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?
Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium
Any ideas?
Sent from my LG-LS970 using xda premium
Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.
No one can help?
Sent from my LG-LS970 using xda premium
Well that sucks...
Sent from my LG-LS970 using xda premium
Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.
I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.