Hello!. I'm trying to buy an LG G2 from someone but the problem is it's not booting. His explanation is a bit ambiguous. He says he was trying to make an update, whether OTA or trying to flash some custom ROM, he didn't say, and while doing so "the wifi disconnected and everything had been wiped." When he powers the phone on, it goes through the LG logo into CWM Advanced Menu. (see attach)
I asked him if he can get to recovery or download mode and he replied that he couldn't check because he's not at home.
I've used CWM and TWRP in the past, trying to flash different types of ROMs on different devices, but I've never accessed CWM Advanced Menu, nor do I know why it's booting into it.
What i need to know is: Can I fix this? Has anyone experienced this or had to deal with it in some way? Should i buy it?
Thank you!
From the image looks like your in recovery, and using clockworkmod 6.0.4.4 in the advance menu, try selecting the go back at the bottom and see if you get to the main menu. From there you can see if there is a backup and restore. Just a thought, i use twrp so not that versed with cwm.
Yea, the thing is, i cant access the phone myself, and when i asked if he can "go back" he said that he can't. That's the screen the phone boot into, and you cant go back from there.
monodsp said:
Yea, the thing is, i cant access the phone myself, and when i asked if he can "go back" he said that he can't. That's the screen the phone boot into, and you cant go back from there.
Click to expand...
Click to collapse
You can use the return to stock kdz method. Id paste the link but with the xda app not sure how
Related
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
What version of CWM did you flash?
Pm me and we will use a chat service (aim, yahoo messenger) and I will walk u through it.
My suggestion of what I would do is this. Find a windows computer somehow. Go to the development section and look for the sticky about rooting the ns4g. Look for the link to flash the d720 back to stock. Download all those files to a flash drive. Take the drive to the windows computer and set things up then flash the phone back to out of the box stock.
Then you can go back to the Mac and do the root and 3024 cwm recovery and rename the sh file that puts stock recovery back in at boot time. After all this you can do what you want but I would suggest staying with the stock experience. This might be extreme to fix this but in my opinion, I wouldn't waste time trying to fix it, especially since you are new to this. It's like computers, yeah you could try to fix it but you could be opening a can of worms. It might take less wasted time putting it back to complete stock instead of f-ing around trying to figure out what happened and how to fix it. You could take hours trying to fix an install of windows that keeps falling on it's face, or you could format and install windows fresh and new in maybe thirty minutes. Which is easier?
CM7 will not work at the moment because it still uses 2.3.3, go find instructions for a 2.3.4 Nandroid. if you want though,i heard that supeaosp works on a ns4g.
Sent from my Nexus S using XDA App
westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
Dude, you can't flash regular Nexus S ROMs on the Nexus S 4G.
Reflash the latest clockwork recovery.
Use fastboot flash recovery recovery.img
then...
Go to recovery, mount the USB storage, and put this zip on the usb storage:ROM
Go to recovery and flash that zip
here's the recovery that works. cwm and stock. How many times is this going to happen with new people and this phone in this forum section before a new subsection is made? We are going to be putting out a lot of these unnecessary fires with people making first time mistakes until something is done so as to not confuse them. Some don't realize that there are different versions of the same phone that aren't necessarily compatible with each other.
The way things are set up now, it isn't making this problem go away. I think that a different method should be tried if the current one isn't working too well. I'm flogging a dead horse now......
I'm looking to root my new NS4G as well -- and do it right the first time. On a Mac as well.
If the similarly-suited OP had issues I'm a bit more skeptical about my effort.
A separate forum might be necessary so people with the D720 hardware don't have near-brick experiences.
Sent from my PC36100 using XDA Premium App
soooo....did the op ever get it running again? i wonder if anyone ever took up on his paypal offer
HALP!
My phone just went black, and when i turned it back on after taking battery in and out, xRecovery is gone, and I now have clockworkmod for X10 Mini for some reason! ... i have X8.
I can't reboot through CWM, it says that "ERROR: Current recovery seems bad!"
Also I'm guessing xR-files are different from CWM's, so the backup I had using xR probably won't work. What do? I don't wanna brick this.
Prior to this error i just installed a few apps. A few that I can think of are; Dropbox, Clockr (clock widget) and Screenshot. Last one needed SU-admissions, it may be that.
Please help.
Cheers
EDIT: Solved - it turned out FroyoBread has a dual recovery-situation; XREC and CWM
But keep on feeding me info!
To further assist you please answer this questions.
Is your bootloader unlocked?
What is your current ROM?
Possible solutions;
If you can still enter a recovery flash a working rom and after that restore your backup.
If thats not work you will have to flash thru various recovery tool SE provides.
Solved!
I took a chance on rebooting, and was able to enter xRecovery and reboot from there.
Next question - where did clockworkmod come from?
Please advice...
Mika Dee said:
To further assist you please answer this questions.
Is your bootloader unlocked?
What is your current ROM?
Possible solutions;
If you can still enter a recovery flash a working rom and after that restore your backup.
If thats not work you will have to flash thru various recovery tool SE provides.
Click to expand...
Click to collapse
I've never done anything with bootloader, other than a program to load various loaders, i don't know what it is.
My current ROM is FroyoBread by Doixhan.
As you can see in my second post, I WAS able to load xRecovery and reboot from there. Now I would very much like to know why a program i've never installed suddenly makes scary moves on my phone=P
Thanks for your reply!
The answer is that you are using a dual recovery ROM
If you tap screen while booting it will enter CWM if you press back button it will enter Xrec.
Mostly ROM made for stock uses dual recovery, again.
Tap Screen = CWM
Back Button = XREC
PS:
Modifying your phone takes courage. If your afraid to brick it then read carefully and follow before you try. It takes courage to achieve something.
Mika Dee said:
The answer is that you are using a dual recovery ROM
If you tap screen while booting it will enter CWM if you press back button it will enter Xrec.
Mostly ROM made for stock uses dual recovery, again.
Tap Screen = CWM
Back Button = XREC
Click to expand...
Click to collapse
So you're saying my custom ROM has two recovery-programs with two different entry-modes?
It's strange that I never read anything about CWM when I installed either XREC or FroyoBread.
Anyways, thanks for the answer, dude. This really got me scared for a second=P
Based on your statement yes you have dual recovery. Give it a try to see. Dont worry it wont brick your device when you enter a recovery. Just dont do anything just restart it after you test it,
Mika Dee said:
Based on your statement yes you have dual recovery. Give it a try to see. Dont worry it wont brick your device when you enter a recovery. Just dont do anything just restart it after you test it,
Click to expand...
Click to collapse
I know NOW it won't brick my phone - but you know, I couldn't find anything about online, and I never installed that program (which said I couldn't boot because of invalid restore-files) - so you see WHY I was all revved up=P
I've owned a smartphone (this x8) for two months now, but I feel I got a nice knowledgebase of how all this stuff works - but I don't like sudden unexpected things like this. If I was scared of rooting and custom roms, I wouldn't have done ANY of this.
But thanks anyways, I love XDA
Hello ladies and gents,
So I'm a total noob and I think I bricked my phone.
I got root by using the motochopper tool
then I went for custom recovery, but I think I flashed the verizon version instead of the ATT version (I was trying to install the Google Wallet fix with a custom rom)
Rebooted the phone, I get an unlock symbol and samsung custom
I can boot into recovery mode and I still have root access / command line.
The phone either boots to black screen with a oscillating blue light or if I go into the other mode it says 'downloading'
Anything I can do to get my phone back working? Did I totally brick it?
Yes, if you see anything on the screen, that would be a soft brick, you are getting the unauthorized screen, then you need another kernel for sure, lets start there...
You really should either put your device in your information screen or tell us what type of device you have, that is very important.
I can not tell you what kernel, not knowing what device has the problem.
I see you mentioned att, is it US or Canadian version?
These are a must when you are seeking help.
I have the AT&T US Version of the S4, 1337
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
TheAxman said:
Yes, if you see anything on the screen, that would be a soft brick, you are getting the unauthorized screen, then you need another kernel for sure, lets start there...
You really should either put your device in your information screen or tell us what type of device you have, that is very important.
I can not tell you what kernel, not knowing what device has the problem.
I see you mentioned att, is it US or Canadian version?
These are a must when you are seeking help.
Click to expand...
Click to collapse
Do you have any type backup? Have you tried, power off phone. hold down power button and volume up at same time, when it vibrates, let go of the power button, it should go into recovery, and lets try restoring your backup.
Your problem is you have the wrong kernel loading, flash a ATT kernel once in the recovery, it will boot.
willenglishiv said:
I have the AT&T US Version of the S4, 1337
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
Click to expand...
Click to collapse
Just ODIN flash the stock firmware for ATT I337 and re-root? That's what I would try.
blyndfyre said:
Just ODIN flash the stock firmware for ATT I337 and re-root? That's what I would try.
Click to expand...
Click to collapse
Actually Ax has the best solution if he can get to recovery... your way will work but by far to many steps for something that simple...
just saying!!
sloanster said:
Actually Ax has the best solution if he can get to recovery... your way will work but by far to many steps for something that simple...
just saying!!
Click to expand...
Click to collapse
I agree Ax's solution is simpler, but OP said that he cannot boot to recovery.
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
Click to expand...
Click to collapse
blyndfyre said:
I agree Ax's solution is simpler, but OP said that he cannot boot to recovery.
Click to expand...
Click to collapse
But he can adb so he can push the kernel onto his phone and flash in recovery
Edit: my bad, he did say he can't boot into recovery. Odin is his best bet.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
he hasn't answered the get into recovery yet, nor has he said he has a backup. I was trying a simple solution. Then we can move on to the odin back.
TheAxman said:
he hasn't answered the get into recovery yet, nor has he said he has a backup. I was trying a simple solution. Then we can move on to the odin back.
Click to expand...
Click to collapse
Hope it gets it worked out!!!
The main thing is he's got options...:angel:
Hey guys. Here's the deal: I screwed up my BELL LG G2 and the only thing I could get it to take was a TMobile .TOT file. So I did that and it "works" now. Thing is, I get no bell internet now because well... It's messed up. The phone thinks it's a D801 but it's actually a D803. So anyway, I want to get Bell stock back. I downloaded the stock bell kdz so that's not a problem. I have that latest (like last month I believe) KDZ flash tool from LG called "LG Flash Tool 2014". Here's where things get messy...
Step by step:
1) I open the file "LGFlashTool2014.exe" and it opens fine.
2) For "type" I select "3GQCT" (I don't even know what this means to be honest), for "PhoneMode" I select "Emergency" (tried DIAG too and it makes no difference) and for KDZ I select the D803 Bell LG G2 KDZ file I have. I leave version blank as it fills itself in.
3) I select either "Normal Flash" or the other one that wipes everything (neither work....)
4) It then brings up it's second screen and I select "Start" at the bottom.
5) It brings up the third screen asking about language and I either leave it or choose "other country". Both of these options (in the top drop down menu) give me no options for actual languages in the bottom drop down menu. The bottom drop down is just blank. Anyway, so I then select "start" again.
6) The LG Update Tool pops up and does the following:
It verify's my phone's connection, says "extracting software" then "S/W Upgrade is in progress" then it suddenly stops and says "Upgrade stopped due to error." Followed by instructions to disconnect the phone, remove the battery, reconnect the phone, and turn it back on (it's a bloody LG G2 so I can't take out the battery...)
What do I do here guys? I'm seriously confused. Oh, and yeah I've tried uninstalling and re-installing... My phone is in download mode. USB Debugging is on. What the hell else can I do?
I have this same error.
I have s80210a-EUR-xx and Rayblobe ROM (since late last year) , android 4.2.2
I get stuck to that exactly same point "Upgrade stopped due to error."
Trying to get kitkat with this thread: http://forum.xda-developers.com/showthread.php?t=2705259
edit: finally all the searches got me somewhere. so, tomorrow i'm going to try this:
http://forum.xda-developers.com/sho...ght=upgrade+stopped+due+to+error#post49513049
terhiha said:
I have this same error.
I have s80210a-EUR-xx and Rayblobe ROM (since late last year) , android 4.2.2
I get stuck to that exactly same point "Upgrade stopped due to error."
Trying to get kitkat with this thread: http://forum.xda-developers.com/showthread.php?t=2705259
edit: finally all the searches got me somewhere. so, tomorrow i'm going to try this:
http://forum.xda-developers.com/sho...ght=upgrade+stopped+due+to+error#post49513049
Click to expand...
Click to collapse
Firstly, thanks for taking the time to reply to me. I reallly appreciate it (nobody here seems to give a flying.... Well, you know). What exactly is that post you linked saying? Not sure I understand what he means.
BUMP!
Can you boot into recovery?? Try getting that ROM in zip mode and flash it through recovery. It should work.
Sent from my LG-E610 using XDA Free mobile app
I'm trying to first flash stock ROM and then go back with the original plan.
Also, I did find "stock kitkat ROM" .zip. But I don't know if you can post links to other places than xda?
I've made my nandroid backup already, so first i'm going to test that kitkat rom. because, if it works, it's much easier
Shao Merng said:
Can you boot into recovery?? Try getting that ROM in zip mode and flash it through recovery. It should work.
Sent from my LG-E610 using XDA Free mobile app
Click to expand...
Click to collapse
If you mean to get bell stock rom and flash it, I tried. It bricked my phone and I had to do the TMobile .TOT. Now that I have TMobile, I have no recovery and I have no idea what recovery to put on the phone (CWM or TWRP? Bell or TMobile?)... God this is such a pain in the butt... If I ever get the G3 I wont be rooting it...
Alright so I rooted the TMobile rom on my LG G2 (again, it makes no sense because I have a Bell phone). I then installed "Flashify" which can be found in the app store. I found the TWRP recovery img for D801 TMobile LG G2 (you can find it by searching on google) and then I booted up adb (you need to install adb if you don't have it). I put the bellstock.zip (I renamed the file) into the folder for adb and opened adb. I then typed "adb sideload bellstock.zip" (you need adb sideload to be running from recovery on your phone first. In TWRP Recovery -> Advanced -> Adb Sideload). Adb started to very slowly sideload the .zip and I was excited that it was working. Well, it got to 100% and said "Success! Enjoy!" and I was so happy. I hit the reboot button and...
LG Symbol just stays on my screen and the phone never finishes booting. It's not a bootloop though, just the LG logo on my screen with a pulsing blue/green notification light. How do I get past the LG Logo?
Thanks guys...
Just tried sideloading a different version of the Bell Stock rom... It failed. Maybe I should have cleared cache or something first? Anybody?
Try to push roms to your phone instead of sideloading since sideloading is more risky. If youhave a custom removery then did you tryed to format system first? And then installing the rom? You dont need to wipe data if same android version if you still have data on it else also wipe data factory reset and also dont forget to flash the right modem for your stock kitkat/jellybean.
wulsic said:
Try to push roms to your phone instead of sideloading since sideloading is more risky. If youhave a custom removery then did you tryed to format system first? And then installing the rom? You dont need to wipe data if same android version if you still have data on it else also wipe data factory reset and also dont forget to flash the right modem for your stock kitkat/jellybean.
Click to expand...
Click to collapse
When I try to push adb just re-pastes the whole menu into the cmd window and does nothing. I could only get sideload to "work". And yeah, I have the radio for Bell, I just haven't flashed it yet because I want get rom working first. Also I did wipe everything before installing the rom.
Hello my fellow XDA Members. I am stuck in a tight spot and after reading and re-reading some things the situation doesn't look very promising. I hope this is the moment that Karma shows up and I can get some help on this. Here it goes.
Specs - LG G2 D801 Variant > TWRP V2.8.3.1 > NO OS Currently
I was running Cloudy G3 Rom smoothly and got bored and decided to flash that new rom that is a 5.0 Rom all variants. Did the usual back ups and flashed it. Something happened when I flashed the rom. It went through the Aroma installer and then said "successful" but stuck in a bootloop. I tried it again and nothing happened. Then I tried to wipe everything again and started getting an E: Cannot mount (data or system I forget which as that error went away after I completely formatted data, wiped everything and reflashed Cloudy Stock. )
> Cloudy stock bootlooped and nothing is happening in TWRP. I Am using the USB OTG method of getting files on the phone and getting it charged but anytime I try to do anything (flash a rom, an older version of TWRP) it just immediately restarts TWRP and thats that. I have No OS at all.
> I tried to use one of the methods to get into download mode and flash a stock KDZ but the phone acts like it is going into DL mode (shows the little blue transition screen) but never gets into the ACTUAL download mode where the PC or flash tool can recognize it.
So in a nutshell > No OS > I can get into TWRP but it does nothing > No Download Mode > Don't want a new phone > Don't want to take it apart and try to short circuit anything if possible. LOL.
I am totally stuck here. I am done alot of work and even helped friends and family out with their devices over the years. I am just not sure if I need to consider it a done deal and get a new phone or maybe one of you guys know of something easy and obvious (please let it be the latter) I am missing. Thanks for any help you can offer. I Will be standing by.
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
wisefreakz said:
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
Click to expand...
Click to collapse
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
jcnbama said:
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
Click to expand...
Click to collapse
@jcnbama
Have you tried this or this?
euphoria360 said:
@jcnbama
Have you tried this or this?
Click to expand...
Click to collapse
The first one I can not do as I do not have any knowledge at all of Ubuntu, Linux, or any of that. It would take forever to get a working knowledge of that software in order to get things going again. I would probably just have to either take it to a cellphone repair shop or get another phone before I could do the first link.
I have not tried the second one but it is a viable option. I was looking at it online and trying to talk myself down from having to do that. I would reallllllllly rather not have to take my phone apart if I can keep from so that's kind of what this post is all about. Just trying to see if anyone knows of ANYTHING else before I go taking apart my phone.
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
euphoria360 said:
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
Click to expand...
Click to collapse
TWRP boots and I can go into wipe, advanced wipe, and format data and it says it's successful. I can use file manager and move items back and forth from USB OTG. If I try to flash anything it just reboots TWRP immediately so I can't install any .zip files at all.
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
euphoria360 said:
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
Click to expand...
Click to collapse
First of all calling people lazy is not nice. I'm not lazy I am trying to play it safe. I wouldn't want to brick it to the point to where I don't even have recovery and it can not even be charged any longer. I have Ubuntu on my desktop upstairs. I have used it a little. It's not that I am completely ignorant to Ubuntu I am just a total novice. Also the issue described in that post doesn't exactly match my situation. I am not in a black screen. It's more like a bootloop that I can not get out of because TWRP is not doing what it needs to do and I can not flash TWRP a ROM or get into DL mode at all. Also that post says,
"VERY IMPORTANT!!!!!!! You must use the img files that correspond to the ROM you have installed before getting the problem to avoid breaking your phone."
I don't have a rom on my phone soooo...
You didn't answer my question well. If on TWRP you can finish installing rom without any error, and you keep coming to twrp after restarts, that's another situation. Try this:
http://forum.xda-developers.com/showthread.php?t=2451696
But if you cant even finish install in twrp (twrp gives you errors or just restarts before giving you "successful", either you have problem in rom you try to flash or you need to build everything up from start.
That lazy thing was for encouraging you to do it.
And you cant brick your device. There is always a way on G2.
For img files: find them from last stock rom that was working on your phone.
Deleted