First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.
Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk
Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on
No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
fastbook oem unlock
install Amon RA recovery
flash new rom.
Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.
From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.
OK I purchased a used G flex that was stuck in a constant boot loop. I've followed every guide all over this forum for restoring this phone or even the G2 threads as well. My phone is the ATT D950 version. The phone thinks it's a D959 when trying to flash with the LG Flashtool 1.8.1. I've tried the custom DLL DGUP_8974 with the ATT LGD950AT-01-V20b-310-410-MAR-22-2014+0.tot and the JAN-25-2014+0.tot file too. Neither have worked at all. I fail at the same spot. The one constant thing that I've noticed is. The flash tool doesn't see the phones IMEI#. So I'm thinking it's completely F'ed right now. I use to be able to boot into CWM 6.0.4.8. But now it doesn't boot into anything but download mode. I've tried all of the different methods I could find and I'm at my ends with the phone. If no one has any other idea's to try. I'll just sell it as parts on feebay.
The only other screen I can see is a white screen with what looks to be 3 choices in Korean I believe. I don't know what any of it is so I'm assuming that won't help me either.
For any inquiring minds. I've googled, youtubed, XDA'd, and possibly checked any site that had a reference to fixing this issue. Every guide is fairly similar but an old or newer LG flash tool. I've used the original ATT DLL with the same results. All of the other post I've see are people succeeding pass my point of failure so I think the phone truly is done. And lastly I've tried multiple computers and cables.
Nobody has any idea's on what I could do next?
You could try the trouble kdz to get it booting, download one of the att flash able zips, then use freedom flex to get a recovery and flash the zip you downloaded. Not sure if that'll work, but seems like it should
kintwofan said:
You could try the trouble kdz to get it booting, download one of the att flash able zips, then use freedom flex to get a recovery and flash the zip you downloaded. Not sure if that'll work, but seems like it should
Click to expand...
Click to collapse
Thanks that's one thing I haven't tried and will when I get off work tonight.
By the way forgot my standard disclaimer....so I'm not responsible if this blows your phone up for good, losses the imei (which could possibly be gone already), etc. It's generally not a good idea to flash another versions kdz l, but don't think there's another option with you not having recovery, adb and the build.prop being wrong.
No problem man. I'm not a rookie to the flash game and I do understand the disclaimer lol. The dude I got this phone from who had flashed what looked to be a T-mobile rom and most likely caused this issue. I got it cheap so if it's screwed I'll just sell if on Feebay.
Please close up. I was able to get out my bootloop after discovering my phone still had CWM recovery working. I was able to restore my phone back to an older 4.2.2 rom that I had. If you're stuck and booting into a custom recovery I'd follow one of the recovery boot loop fixes. The one I use I flashed a zipped command that wiped a corrupt partition since I could get into ADB mode to push the files. If you have TWRP, it has an ADB mode that will allow those commands to work. But CWM people will need to sideload the files that will auto push the files needed to correct the corrupt partitions. As always folks, please back up before you flash anything. That's what saved my phone in the end outside of the partition clearing files sideloaded in CWM.
Prompt [q] HELP! Stuck for almost 24 hours........
Alright guys, here goes nothing. I have a LG-D415.(On TMo service). I have been on the Fastboot screen since I rebooted this morning (into recovery, was the command issued. When I couldn't find Recovery Mode, which I'm about ready to assume there isn't one, I am lost as to where to go from here. I cant do anything from fastboot, no access to ADB, I do have Stock Lollipop .IMG files, custom recoveries, as well as my STOCK ROM which is D41520b_00.kdz, which I know all files are current and complete. I have used them all within the last two weeks. This is my first time booting into fastboot. I cant boot into recovery, bootloader, or OS. I dont know what to do. I have only been at this for about a month, and in the first week, I D/L'ed Xposed before he had the Lollipop patch.......aaannnddd, Bootloop! I spent 4 days finding the correct method to fix it. It seems like TMo screws the pooch when it comes to the versatility of their devices....ANY AND ALL HELP IS AND WILL BE GREATLY APPRECIATED. I HOPE SOMEONE HAS A MAGICAL ANSWER BECAUSE I'VE BEEN LOOKING FOR ABOUT 18 HRS NOW WITH NO LUCK. THANKS AGAIN IN ADVANCE...
I have had this problem before. How I fixed it was taking out the battery, waiting for 30 sec (this is important), and then going into factory reset mode which should take you into recovery. If you are having the same problem I did, anything you do in fastboot gives you an error right?
If that doesn't work I had the same issue but I was on a KitKat ROM which fastboot wouldn't take any commands, I used a batch file script that pushed commands and corrected the problem for me, it contains laf.img and cwm.img
https://mega.nz/#F!U1hzhKKK!mqh1qN2c0IrNyWbHCojgyw
Sent from my LG-D415 using XDA Free mobile app
Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Are you able to pull logcat?
Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"
dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.
i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.
You can try by helping me to look for a circuit PDF from the board or trying it yourself.
I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately
Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.
I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate
we can connect through hangouts / etc.
look up for my user at gmail
Hey all i apologize in advance im really new to all this stuff. I have a d950 it was rooted (cwm kept saying root was lost) and im using the stock ROM. The other day i got an update notification on my phone i kept ignoring it for a few days and one day i turn my phone over and its in CWM. I tried to use the restores that i had created with no luck and somehow ended up erasing my phone as in all the restores and anything else is gone. I have been lurking here for about a week trying different things the phone wont boot to any mode except CWM. First the drivers would not work with the phone ended up having to modify the google usb drivers since the lg ones would not work. I was then able to push stock firmware that i found into the phone but when i try to install it says installation aborted after about a second. I have read that its more then likely because it isnt compatible with my phone but it said it was for the d950. I then tried to enter fastboot with no luck just still cycling between the LG logo or CWM. At this point any help would be appreciated before i give up and have to get another phone.
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html