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
Related
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.
EDIT: Wish I could delete this. Just found a post about how to fix this...but it involves opening the phone and messing with the hardware. Wish someone could walk me through it :s
So, I hope I didn't, but here is the scenario:
Wanted to install Lollipop ROM from KitKat...tried, failed, found out I needed to have a downgraded radio. Okay...use LG Flash Tool to give myself another try. Load up Jellybean...couldn't figure out how to flash custom recovery in Jellybean as all tutorials are outdated or just didn't work when I tried them, so I thought the best way to do it was to get the Kitkat OTA from Verizon and let it install, then flash a custom recovery (since I figured out how to do that with Kitkat...Autorec), then flash the old radio then the Lollipop ROM and voilà. However, when waiting for the download for Verizon OTA, I tried again to install a custom recovery, and when tried to load it, I just got a black screen. So I just decided to go back into the Android OS and install the OTA once it finished downloading...
The OTA finished downloading and I clicked install, my phone then rebooted...and stupid me didn't even realise what I have just done. The OTA tried going to recovery mode to install...but there's nothing there. Now I am stuck at a black screen that is trying to start recovery mode and when trying to reboot and get into download mode, it won't let me and just goes to the broken recovery mode.
So...can't really think of any other options for me. What can I do? When I plug it into my computer, it connects my phone as like 20 different drive letters that all say they need to be formatted.
So my question is...what can I do?
Hey all. Appreciate any help, because Im out of ideas here. A friend brought me his Vzw G2 yesterday morning, which he had bricked trying to install cm12 (He's had it rooted and unlocked since he got it), and he apparently tried to install a cm12- compatible twrp, and thats when he got a secure boot error. I fixed it just by using the lg flashing tool and a tot and restoring it to stock, but when I tried to flash it, I ran into the issue of twrp wouldn't flash anything, some drinks were had, and out of drunken stupidity last night we tried to dd a new copy of twrp, from twrp's shell onto it, which sent it back into a brick. Now, its worse, download mode cant even be accessed. I've been at this all day trying to fix it. Trying to go to recovery takes it to fastboot, but, it goes blank after about 10 seconds, and then no fastboot connection can actually be made to the device so I cant use fastboot. I'm on linux, so it does show all of the devices partitions under /dev, so I tried another post's idea of manually dding the entire bootstack onto the device, partition by partition, but that didnt seem to change anything. It's on the 39a lollipop update. Any one have any other suggestions?
Any luck?
No, sadly still nothing. I've tried re-dding a few times, but I cant think/read anything else to try.
Hi there,
I got a bricked G5S+, which I reported in another thread already.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
That happened after I rebootet the cellphone for a longer time.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me and now cannot access android anymore to do so.
Anyway I thought: fine: I will just flash the stock OS again taking care of the software defect.
After having had some issues I flashed Sanders (SANDERS_NPS26.116-26_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) following that thread here:
https://animetrick.com/flash-stock-rom-moto-g5s-plus-locked-bootloader-2018/
It is quite similar as this thread, which deals with installing a stock OS to a bootloader-locked phone:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
The thing is I followed all steps but still get the same error:
A lying down android with a red questionmark and saying 'no command'.
Does anyone have an idea what else to try?
I am not aversed to install a custom Rom, such as the official RR v6.0.0, but I have no idea how to do so with a currently bricked phone.
Maybe you guys have a solution for me to unbrick and finally use my phone again.
Thanks a lot!
Regards from Germany
Matt
Hey bro Im not sure if you still need help but, if so can you try to boot into a recovery?
Hi Carlos,
yes I still need help.
I can boot into recovery. And fastboot runs and detects the phone, too.
Any idea what I can do?
Go ahead and download twrp from the Roms sections and also begin the process to unlock the boot loader, we can see if it still can be done without having enabled the setting in the developer sections, and if so we can either then flash the recovery and a custom rom or install stock again.
Sent from my iDevice running Smoothshake v11.3.1
I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
There is no need anymore to install a custom rom (at least not currently )
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!
I have fallen into same issue, i cannot install any custom rom or recovery to it but i can access fastboot & one recovery that has update via adb sideload / sd card but nothing works, shows failed line 2 error / install aborted .
the device just showing oem locked in fastboot & rom install or recovery install fails & says cause too many links
the phone starts & stucks after the motorola logo
anybody with any idea?