Hi.
I rooted my LG Optimus 2X with Super on click root. It worked great after right after. I uinstalled CarHome and F-Secure, and after that my phone restared.
Now, It would not start. I only boot until the LG logo, and after that it reboot. So it go on and on and on. I can get the phone into ADB, and I'm a newbie on android, so I got no clue what to do. I aslo tried to use the recover program by LG, but I get a message that tells me that my phone does not support the update.
Is there anything that can sovle my problem or do I need to take it to the place I bought my phone?
I had the exact same problem (a hole thread in here). Your phone is bricked (as of now there's no solution as far as I know). When you rooted your phone you lost the warranty, so if unlucky you cannot return it without having to pay to get it fixed... If lucky the might just switch the phone with a new one...
I've sent mine back to the seller and hopefully I'll get a new one...
This thread could be useful for you:
http://android.modaco.com/content/lg-optimus-2x-2x-modaco-com/334664/bricked-lg-optimus-2x/
There's actually new development in the right direction. Paul from modaco (2x.modaco.com) are preparing af NVflash of the 2x, which will completely reflash the memory with the standard rom from stock meaning we should be able to fix the easily...
Should be ready on wednesday...
I've been looking into these two treads, but could not found anything that my fix the problem.
Well, I've got to go to my the seller and hopefully they will fix it fast.
Try to remove the SD card and then try to switch on once more...
I've been trying with and without SD card , Sim card, Battery many times. So I thats not the problem I think
thats why you should freeze apps instead of uninstalling them.
Did you try to hard reset the phone?
If you got an adb connection and root, try to obtain the apk's (search the forum) and push them to system/apps.
Thats all I can think of for now. I'm no expert on this
Did you make a system backup using Clockwork Recovery before you rooted? If so, boot back into recovery and restore the backup. I bricked my phone the first time I installed a different ROM but luckily I had a backup that I was able to restore and try again.
Sent from my HTC Incredible using Tapatalk
xphire said:
Did you make a system backup using Clockwork Recovery before you rooted? If so, boot back into recovery and restore the backup. I bricked my phone the first time I installed a different ROM but luckily I had a backup that I was able to restore and try again.
Sent from my HTC Incredible using Tapatalk
Click to expand...
Click to collapse
The Optimus 2X does not (yet) have Clockworkmod Recovery working. At least not in a way available to the public (MoDaCo's Paul said he would release some stuff next week)
I can't get it to hard reset. When I boot up the phone I hold in the power button and the - volum butten. Then I come to a screen with the droid, I press the home button and I get Android recovery system (3e), but I'm unable to choose anything. I only can switch between the 4 chooses, by pressing +/- volum button.
Nope, can't get it to connect to adb. Tried, but I couldn't manage it.
Well then maybe someone here can point you to actually selecting something from that list. I mean, it has to be possible to "choose" one of the 4 options but I've never owned an android until (hopefully) in 3 weeks so I can't tell you how it works exactly.
Edit: Just checked the manual again, did you make sure you pressed home and vol- for 10 seconds ?
Well, yes. I pressed home and - volum until I got a recover mode or something.
But as I know theres know way to fix this problem atm. I'll have to send it back to my reseller or wait for Paul to release the fix.
Related
Hi guys,
UK G1 (Dream) phone recently updated to the 1.6 build, all working fine.
Yesterday I tried installing the free app Shop Savvy. the phone resetted itself after install and sat on the G1 boot screen permanently.
Now phone will pass this boot screen (Tmobile G1)
Tried:
Recovery mode - will not work at all
Quick boot - brings up the multicolour screen but does nothing after.
**PHONE IS NOT ROOTED**
looks like I have had the phone JUST over a year, not looking good...
Any ideas?
You can boot in to the SPL/bootloader so thankfully you haven't bricked
If you're on a contract with tmo you could take it back to the store and they should give you a replacement, but where's the fun in that?
If you want to fix the problem yourself, all you need to do is downgrade to firmware 1.1, then accept the OTA update to 1.6.
Here's the procedure:
1)Put the phones SD card in to a card reader and format as fat32
2) Extract this file and copy it to your SD card as 'DREAIMG.nbh'
3) Put the card back in the phone and hold down power and camera to boot in to the bootloader.
4) Flash it. (Action button is the trackball).
It's a good idea to leave the charger plugged in and have a decent amount of charge in the battery (eg 40%+).
Afterwards the phone will restart and you will need to re-enter your google account info. All your apps and data will be gone, but there's not much we can do about. You can set things up and install apps while you wait for the prompt to update.
Thanks alot AdrianK,
Really appreciate the steps and info, nice one
I have done some flashing on other phones etc so I have no problem with this. However, I am wondering how a normal app such as Shop Savvy could corrupt my ROM and am wondering if it might not be better to get a new phone as this one could have hardware fault?
What do you think?
Silver.
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
SilverfoxUK said:
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
Click to expand...
Click to collapse
I think you can take the battery out restart the phone
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Once you get to RC7 use these to build back upto 1.6
http://code.google.com/p/official-android-firmware/downloads/list
SilverfoxUK said:
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Click to expand...
Click to collapse
Yeah that's the RC7 ROM, the UK ROM for 1.1. RC29 is 1.1 for US phones.
This is all very odd, especially that it was an app that caused it, or as you suggested possible hardward failure. Oh well, I guess all you can do now is take it back to tmo.
The story so far...
Bought a new Optimus Black and gave it to my girlfriend for her birthday a couple of days ago. After playing with it for about an hour she put it down, I picked it up and decided to have a tinker. I installed Cyanogen mod 3.5.1 after rooting it with Gingerbreak. So far so good but I didn't really like the look of the ROM and the absence of a Market seemed like hassle so I used ClockworkMod to restore the backed up stock ROM.
It's still working fine but now I see there is an official update from inside the phone. I presume it's the upgrade to Android 2.3 so run it and reboot the phone. That's when it all goes wrong. I'm now stuck in the CWM recovery screen. I try all the options, following any online guides I can find that were supposed to have worked for people. I try restoring the backup, restoring cyanogen, clearing the cache, dalvik, everything but nothing happens and I keep booting back into the CWM recovery screen.
Next day I try the LGUnitedMobileDriver and the phone recovery option but despite trying several times I can get no further. A friend tried to use Odin to restore it but got no success. Finally, we tried restoring with a KDZ file with
KDZ_FW_UPD_EN, Windows Enabler and LG B2CTool and now the phone got stuck in yet another loop - a black screen with 'updating firmware'. The LEDs flash for a minute and it reboots and does the same again.
What's more, the phone will now no longer charge or turn on without being connected to the mains.
What are my options here?
Follow the tutorial given below.
http://forum.xda-developers.com/showthread.php?t=1275315
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
pickarooney said:
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
Click to expand...
Click to collapse
have you tried the CS_EMERGENCY option in R&D TOOLS? Wait I'll find the link..
Here >>> http://forum.xda-developers.com/showpost.php?p=18841596&postcount=8
http://forum.xda-developers.com/showpost.php?p=18740082&postcount=45
The CS_EMERGENCY is the only thing worked, he used a german V10A ROM. If you managed to unbrick it, you can flash it again with your desired KDZ, or use CS_EMERGENCY and flash directly your desired KDZ. TRIAL AND ERROR.
Emergency c-section... nope, I will try that now!
Said that it will get stuck at 4% but it is still flashing. Just wait for the phone to reboot by itself.
It just crashes with a fatal error as soon as it gets to the second tab (downloading) on both PCs I tried it on. I tried several KDZ files with the same result.
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
pickarooney said:
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
Click to expand...
Click to collapse
Does it have warranty? Why not RMA it, I think it has a hardware problem now since you mentioned it doesn't charge anymore. Also, have you tried a different USB cable?
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
pickarooney said:
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
Click to expand...
Click to collapse
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
gabwerkz said:
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
Click to expand...
Click to collapse
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
darkzorn said:
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
Click to expand...
Click to collapse
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
Fingers crossed for you !!!
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
IT will mostly work..Good luck though and please do reply here and let us know if it worked..
I'm a complete noob in dire need of help. I wanted to root my phone, and read the 3 procedures mentioned in the sticky thread. The 2nd one (nvflash) seemed very well explained and was sure to work with 2.3.4 so I decided to use that. As I was in my friend's house I used his pc and installed the drivers while my phone was connected in apx mode. Then I double clicked the "install internal xp" batch file which resulted in a black window with some texts, but seeing this my friend freaked out and closed the window before the process was finished. I told him he shouldn't have done that. I then disconnected the phone and switched it on. It seemed to switch on properly. So I then switched it off again and pressed and held the power and vol down switches to see if I got cwm. This showed LG screen for a few seconds and then the screen went off.
Now whatever I try to do I can only see the LG screen for a few seconds and then the screens goes off. No power on, no recovery, no nothing. And I can only attempt to even power on once, after the screen goes off I must remove the battery before the power button does anything again.
I tried to freshly nvflashing the recovery many times, but it made no difference. Does this mean my phone is bricked? Please tell me how I can solve this as I'm really worried.
NVFlashing the recovery again *should* have worked. So we first need to make sure you're trying to start CWM the correct way.
1) Unplug phone
2) Remove battery for 10 seconds.
3) Insert battery
4) Hold volume-down, do not let go, keep pressing it.
5) Press power button, keep it pressed.
If/when you get the second LG-logo, bluish halo, you can release both buttons, not before.
Nope, that was exactly what I was doing to access the recovery. I tried it again just now and it didn't work.
It just displayed the regular LG logo and then the screen went off. I'm not sure the phone completely shuts down 'cause if I keep it like that it gets quite hot and I can't use the power button again to try to power up. Only removing and re-inserting the battery gives me another attempt.
Is there any chance this is a hardware issue?
Hardly any chance this is hardware related if it was working before the first NVFlash.
Good, next step will be to NVFlash a complete stock ROM. You will unfortunately lose any data you might have on it, but that's the price to pay.
Go here, follow the instructions precisely, skip installation of apx-driver. Report back.
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
sean8000 said:
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
Click to expand...
Click to collapse
It works, yes, but is the original Froyo. This is just a way to get the phone up and running again.
Later you have a few choices. Either install CWM, then install you ROM of choice, or upgrade it to the latest for your region by using the LG Update tool.
EDIT. Oh, and btw, it is better to open a command-window and type the flash.bat command. If there are any errors you will still have them on-screen.
Thank you for all the help and support. I didn't get a chance to flash the rom till now (being on a vacation without a smartphone sucks). But I'll try it asap and report back.
So, how did it go?
TrymHansen said:
So, how did it go?
Click to expand...
Click to collapse
I haven't flashed it yet. I've decided to do it after I return home. I'm at my friend's house for 2 more days.
Ok, bad news. I flashed the stock rom you linked. The process went pretty smoothly. After the window got closed and the lg logo on the phone was visible 2 times, I unplugged it and installed the battery. But switching it on wasn't fruitful. It just displayed the LG logo for a couple of seconds and then the screen went off (just like before, only faster). I tried repeating the whole process, even tried to nvflash cwm once again, but nothing happened.
So is it a hardware issue? My phone is no longer in warranty period, so a hardware problem would be really bad...
So is it a hardware issue?
Click to expand...
Click to collapse
I don't know.
What would be helpful is to get a copy of the output you get when you NVFlash, it's simply the only way to verify that the flash process went ok. If you have an aborted flash it of course won't work, and may display the behaviour you describe.
EDIT: Btw, early on there were some ROMs which refused to boot properly unless the baseband was of an early variety as well.
If you feel confident the NVFlash has been successfull, smartflash an old baseband as well, see if it boots then.
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
gabriel2anjos said:
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
Click to expand...
Click to collapse
Now what's this "Jtag service"? (edit- I googled it and it seems to be a method of un-bricking stuff with specialized hardware or something, but I'm not sure I can have that done where I live)
Is there any way to fix the bootloader by myself?
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
sean8000 said:
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
Click to expand...
Click to collapse
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
TrymHansen said:
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
Click to expand...
Click to collapse
Ok, I'll try that when I have the time.
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
sean8000 said:
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
Click to expand...
Click to collapse
If it is you're only the second person in this forum to ever brick his phone. Anything's possible I guess. Some flash cells may have been damaged the first time the power was yanked. But then we should presumably get some verification errors during flashing.
Anyway, I'm at my wits end, and I really do hope you get it up and running, but I don't have anything more to contribute. Good luck.
Corrupted bootloader means that your cellphone simply don't know what to do when you hit the power button, due to the damage. As the cell phone can't turn, the pc can't recognize it. If your cell phone were a samsung, you could try to use a jig to have acesso to the download mode. But I don't know if it would work for a LG. You could try anyway.
And if you live at big city, usually it's common to have some jtag services.
Please, dont be afraid of hitting thanks
Please, dont be afraid of hitting thanks
Ok, so I took the phone to the service center today. The guys there said its battery terminals are messed up. They said replacement terminals are not easily available, but they'll try to find some. And of course I'll have to pay for it. I guess it's still better than using the phone as a paperweight.
What do you guys think?
Good luck I managed to mess up my phone like you too. I'm from India. But the difference was that I was covered by warranty. I managed to get a bunch of hardware replaced and was up and running again.
A friend of mine tried to root his white tmobile g1 and im not sure what he did to it. heres what im working with.
press power button goes to g1 screen and then to the factory android recovery (e2)
can wipe, factory reset and can select install update.zip
the phone wont take any update i throw at it and ive tried like 7-8 i have found here on xda. I have no idea what phone was on previously.
I CANNOT access the bootloader no matter what i do. i even went as far as to dissasemble the phone and replace the buttons (thought home might be sticking), anyone have any ideas on how i can possibly ressurect this?
without bootloader access i cant flash to downgrade. Im at a loss here and really hate getting outsmarted by a phone. I dont think its a brick... yet being i can hit stock recovery and that blue led test works.
If bootloader is truly gone, not just hidden from you, the phone can not boot. I know of no flash able update.zip for a bootloader in the stock recovery which unfortunately means this is a brick. The blue light mode is only helpful for JTAG, sorry
Sent from my Nexus 7 using xda premium
I finally managed to get the phone to boot by swapping the cables out of another phone. Weird issue but nice having a half dozen phones laying around for parts
Sent from my HTC One XL
I apologize in advance if this has been discussed in the past, but my searching here hasn't helped so I gotta ask for help.
Having a problem with me wife's HTC Vivid. It's bone stock. Nothing has been messed with other than whatever updates may have been installed automatically over the air. She wouldn't let me touch it to root it, mod it, nothing.....
Anyway. Problem happened Saturday night. Phone shut down due to dead battery. Put it on charger overnight. Tried to boot it up Sunday morning and it stops at the white HTC screen. Period. Just sits there. Forever.
I did some reading, learned how to hold power and vol down buttons to get to HBOOT. Tried navigating to recovery. It goes to white HTC screen, then to a black screen with a green circle arrow icon, then to a red triangle with an exclamation point.
I downloaded drivers and the HTC RUU and was going to try fastboot usb, but when it said all data will be lost I stopped.
My wife has tons of pics and stuff on her phone (that she has failed to back up ) and really doesn't want to loose them.
Before I wipe the phone and try to reinstall the stock rom do any of you have any suggestions on a way to get it back up and running and recover her pics and stuff?
Or are we screwed? :crying:
Ginther said:
I apologize in advance if this has been discussed in the past, but my searching here hasn't helped so I gotta ask for help.
Having a problem with me wife's HTC Vivid. It's bone stock. Nothing has been messed with other than whatever updates may have been installed automatically over the air. She wouldn't let me touch it to root it, mod it, nothing.....
Anyway. Problem happened Saturday night. Phone shut down due to dead battery. Put it on charger overnight. Tried to boot it up Sunday morning and it stops at the white HTC screen. Period. Just sits there. Forever.
I did some reading, learned how to hold power and vol down buttons to get to HBOOT. Tried navigating to recovery. It goes to white HTC screen, then to a black screen with a green circle arrow icon, then to a red triangle with an exclamation point.
I downloaded drivers and the HTC RUU and was going to try fastboot usb, but when it said all data will be lost I stopped.
My wife has tons of pics and stuff on her phone (that she has failed to back up ) and really doesn't want to loose them.
Before I wipe the phone and try to reinstall the stock rom do any of you have any suggestions on a way to get it back up and running and recover her pics and stuff?
Or are we screwed? :crying:
Click to expand...
Click to collapse
You get the red triangle/exclamation point because you dont have a custom recovery installed if Im correct. Using the all in one here is the most user friendly way of installing -
http://forum.xda-developers.com/showthread.php?t=1498003
Install twrp and you should be able to recover your pics/vids by selecting "mount/mount sdcard" in the twrp ui with your phone plugged in to your pc. Then opening the storage located under computer. Navigating to the appropriate folder & cut/pastting to a folder on your pc.
I dont know how technology savvy you are but it sounds like flashing the stock kernel will repair your phone hanging on the htc logo. This is the stock ICS kernel - http://d-h.st/rHX
You can flash it through the all in one. Or follow up here -
http://forum.xda-developers.com/showthread.php?t=1416836
Hope this helps. Good luck!
Sent from my HTC Raider X710e using xda premium
yosoywilson78 said:
You get the red triangle/exclamation point because you dont have a custom recovery installed if Im correct. Using the all in one here is the most user friendly way of installing -
http://forum.xda-developers.com/showthread.php?t=1498003
Install twrp and you should be able to recover your pics/vids by selecting "mount/mount sdcard" in the twrp ui with your phone plugged in to your pc. Then opening the storage located under computer. Navigating to the appropriate folder & cut/pastting to a folder on your pc.
I dont know how technology savvy you are but it sounds like flashing the stock kernel will repair your phone hanging on the htc logo. This is the stock ICS kernel - http://d-h.st/rHX
You can flash it through the all in one. Or follow up here -
http://forum.xda-developers.com/showthread.php?t=1416836
Hope this helps. Good luck!
Sent from my HTC Raider X710e using xda premium
Click to expand...
Click to collapse
Thanks for the help. I was able to get the bootloder unlocked with the all-in-one but when I tried to install the kernel it kept failing. I tried several different things over and over again but no luck.
I finally got frustrated and tried the HTC RUU from their website to see what would happen. I had to relock the bootloader before it would work though. It finally ran successfully and the phone is back up and running now.
Only bad news is that I wasn't able to recover any of her files.
Now she understands the importance of backing up files and getting stuff OFF the phone to another form of long term storage. :good:
Thanks again for the help.
Ginther said:
Thanks for the help. I was able to get the bootloder unlocked with the all-in-one but when I tried to install the kernel it kept failing. I tried several different things over and over again but no luck.
I finally got frustrated and tried the HTC RUU from their website to see what would happen. I had to relock the bootloader before it would work though. It finally ran successfully and the phone is back up and running now.
Only bad news is that I wasn't able to recover any of her files.
Now she understands the importance of backing up files and getting stuff OFF the phone to another form of long term storage. :good:
Thanks again for the help.
Click to expand...
Click to collapse
You probably could have recovered your media. Just by mounting the internal memory like I said in my original post. You really should invest in an SD card that way no matter what happens your stuff is accessible. You can use up to 32GB. People also say 64GB SDXC cards work too. But glad its up and running again.
HTC VIVID ICS 4.0.4 SENSE 4.1
yosoywilson78 said:
You probably could have recovered your media. Just by mounting the internal memory like I said in my original post. You really should invest in an SD card that way no matter what happens your stuff is accessible. You can use up to 32GB. People also say 64GB SDXC cards work too. But glad its up and running again.
HTC VIVID ICS 4.0.4 SENSE 4.1
Click to expand...
Click to collapse
I got into CWM recovery and tried mounting the sdcard but kept getting "error mounting sdcard"
No mater what I did I could not get it to mount and become visible on my pc. I could see the disk drive(s) for the phone, but they were shaded and when I'd try to access them it would say insert disk into drive. When using the all-in-one it would try to push the kernel to the phone, but it got errors too. I tried putting the kernel on a micro sdcard and installing it from cwm with no luck. Couldn't get that to show/mount/work either.
I've done modding to my Samsung phones and build my own pc's so I'm not too technologically challenged.... but, Something was just wrong with this phone and it didn't want to cooperate.
And/or I didn't have the time and patience to keep jacking with it.
Switch to twrp
Sent from my Vivid 4G using Tapatalk 2