LG G3 Bootloop - AT&T LG G3

Hi guys. I have an unlocked AT&T LG G3 D850 and I cannot for the life of me figure out why it's stuck in a bootloop. I've tried just about everything but nothing works. I'm able to access both recovery and download mode, but every time I exit it, I just get thrown into another bootloop. Strangely, I didn't do anything to the phone recently, and it was working absolutely fine minutes before I noticed the bootloop.
First thing I tried was wiping everything and reinstalling the ROM. I am rooted and was running a Marshmallow distro of Resurrection Remix, with TWRP 3.0 (I think) running my recovery. I booted into TWRP and cleared everything, reinstalling the ROM. Didn't work. Okay, so maybe the ROM is to blame. Tried some different versions, still nothing.
I then tried flashing stock firmware using download mode, and kept getting errors at the beginning of the LG flash tool utility. After switching USB ports, it started working. However, after about 30 minutes, it would fail, and I would get a message saying it couldn't communicate with the device. I tried this multiple times to no avail.
Eventually, I ended up running the program one last time and left it for a couple hours. When I got back to check it, I was super relieved because the phone had apparently successfully been flashed back to stock firmware. Keep in mind this process usually only takes 4-8 minutes, whereas my phone took hours to get it done.
Finally, I booted the device, full of hope. NOPE. Bootloop again. I tried resetting it using the volume down combo, but it stays in a bootloop every time.
I am running out of options and getting desperate, and I really don't wanna fork out the cash for another phone if I don't have to. Any help would be greatly appreciated. Thanks everyone!

acmilandroid said:
Hi guys. I have an unlocked AT&T LG G3 D850 and I cannot for the life of me figure out why it's stuck in a bootloop. I've tried just about everything but nothing works. I'm able to access both recovery and download mode, but every time I exit it, I just get thrown into another bootloop. Strangely, I didn't do anything to the phone recently, and it was working absolutely fine minutes before I noticed the bootloop.
First thing I tried was wiping everything and reinstalling the ROM. I am rooted and was running a Marshmallow distro of Resurrection Remix, with TWRP 3.0 (I think) running my recovery. I booted into TWRP and cleared everything, reinstalling the ROM. Didn't work. Okay, so maybe the ROM is to blame. Tried some different versions, still nothing.
I then tried flashing stock firmware using download mode, and kept getting errors at the beginning of the LG flash tool utility. After switching USB ports, it started working. However, after about 30 minutes, it would fail, and I would get a message saying it couldn't communicate with the device. I tried this multiple times to no avail.
Eventually, I ended up running the program one last time and left it for a couple hours. When I got back to check it, I was super relieved because the phone had apparently successfully been flashed back to stock firmware. Keep in mind this process usually only takes 4-8 minutes, whereas my phone took hours to get it done.
Finally, I booted the device, full of hope. NOPE. Bootloop again. I tried resetting it using the volume down combo, but it stays in a bootloop every time.
I am running out of options and getting desperate, and I really don't wanna fork out the cash for another phone if I don't have to. Any help would be greatly appreciated. Thanks everyone!
Click to expand...
Click to collapse
Did you try choose board_dl on flash tools?
Sent from my iPhone using Tapatalk

hyelton said:
Did you try choose board_dl on flash tools?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Not yet, but I definitely will. What difference does it make? Thanks for helping!

acmilandroid said:
Not yet, but I definitely will. What difference does it make? Thanks for helping!
Click to expand...
Click to collapse
When flashing an AT&T choosing that will make the phone boot into mini OS then you'll select reset/restart and it should boot unless there's an hardware issue
Sent from my iPhone using Tapatalk

hyelton said:
When flashing an AT&T choosing that will make the phone boot into mini OS then you'll select reset/restart and it should boot unless there's an hardware issue
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It says download failed at 517 seconds. "We can't communicate with phone." Meanwhile, the phone is back at 0%. Should I leave it for a couple hours like I did the one time it actually worked?

acmilandroid said:
It says download failed at 517 seconds. "We can't communicate with phone." Meanwhile, the phone is back at 0%. Should I leave it for a couple hours like I did the one time it actually worked?
Click to expand...
Click to collapse
Did you freshly put the phone into download mode? And using a usb 2.0 port right?
Sent from my LGLS675 using Tapatalk

hyelton said:
Did you freshly put the phone into download mode? And using a usb 2.0 port right?
Sent from my LGLS675 using Tapatalk
Click to expand...
Click to collapse
Yes. However, I'm not sure if I was able to manually boot into download mode or the phone automatically did it. I did pull the battery before connecting the phone, and I did hold volume up. I just don't know if I physically put it into download mode myself.

New issue. Got to about 89% when I get an "fboot fail" error message. My phone is bootlooping again.

acmilandroid said:
New issue. Got to about 89% when I get an "fboot fail" error message. My phone is bootlooping again.
Click to expand...
Click to collapse
Were you able to solve the issue and progress any further???

Related

[Q] G2x Update Prob (Possible Brick)

Hey ppl. I have a really BIG problem with my G2x and I was wondering if you could help me out. I ran the LG Mobile Support Tool to update my G2x to 2.3.3. After the process, my phone is stuck on "S/W Upgrade Please wait while upgrading..."
I tried using to LG Support Tool and it's saying that I'm running V21e
I can't boot into recovery. All I get is "S/W Upgrade Please wait while upgrading..."
Before doing this I had done a backup through the recovery. How do I get it to bootup?
Any advice and assistance would be greatly appreciated.
I have the same problem! Stuck on "S/W Upgrade Please wait while updating..."
So pulling the battery out, unplugging the USB and pressing vol-down + power doesn't boot to recovery? Did it freeze at 4% or get all the way through and now you're having this problem?
I'd suggest shutting the phone completely off and trying to root it again using NVFlash: http://forum.xda-developers.com/showthread.php?t=1054492&highlight=nvflash
I think that's the only real option if you can't get into recovery. I'm not guaranteeing it will work, but it's worth a shot.
If you can get it rooted again and get back to CWM, flash 2.3.3 using this: http://forum.xda-developers.com/showthread.php?t=1179748 instead of LG's awful garbage updater.
deanp0219 said:
So pulling the battery out, unplugging the USB and pressing vol-down + power doesn't boot to recovery? Did it freeze at 4% or get all the way through and now you're having this problem?
Click to expand...
Click to collapse
It went all the way through.
I did the battery pull and pressed Power + Vol-Down and it didn't boot into recovery.
Same issue.
I've been working on this since about 1:00 PST.
I've tried 32 bit laptop. 64 bit desktop.
When I had initially got it going after about an hour, it basically had gotten to the "download" tab and constantly got stuck a 4%.
I have never had root on the phone, no custom roms or anything. Just a $543 brick.
Called LG was told to "Pull the battery and put it back in". Seriously? You guys had me on hold for 5 minutes and wasted 15 minutes of my time to tell me that?
Then I was told by the same guy if that doesn't work there are no other current workarounds other than sending the phone back to them.
No thanks.
Then I was live chatting with an LG guy named Jorge at the same time. He told me we needed to hard reset. Told him can't do that because the "S/W Upgrading" screen will just flash back after a power plus volume up hold. He said he believes we're having issues because it is so new, they seemed to have been blind sided by this. He said that they think that everyone was trying to update at the same time, possibly suggesting server overload.
Anyway, I've tried multiple computers, multiple USB ports on each. Multiple USB cables, and I even tried using a KDZ file that apparently housed the entire update. But for the life of me, I have no clue how to flash a .kdz file.
Any suggestions are MORE than welcome!
Thanks guys, and good luck.
deanp0219 said:
I'd suggest shutting the phone completely off and trying to root it again using NVFlash: http://forum.xda-developers.com/showthread.php?t=1054492&highlight=nvflash
I think that's the only real option if you can't get into recovery. I'm not guaranteeing it will work, but it's worth a shot.
If you can get it rooted again and get back to CWM, flash 2.3.3 using this: http://forum.xda-developers.com/showthread.php?t=1179748 instead of LG's awful garbage updater.
Click to expand...
Click to collapse
Did you try any of this?
deanp0219 said:
Did you try any of this?
Click to expand...
Click to collapse
Yea. I tried it and still nothing.
I'm at the same place. I have CWM installed and can access it. I've flashed different ROMS and tried to restore my old one. It all works, I'm sure, but I can't get past that S/W Update screen to find out!
Sorry guys, wish I could help more but I'm stumped. I'm sure there are people on here smarter than I am who can figure this out. It seems to be a widespread problem so hopefully someone will figure out a fix. Damn LG s/w updater. This isn't the first time it's bricked phones.
http://www.google.com/search?source...gc.r_pw.&fp=79f73547dc11dcbf&biw=1366&bih=667
I currently have the same problem, don't think there is a fix.
1 click recovery
http://forum.xda-developers.com/showthread.php?t=1056847
follow these steps... must have windows xp to work
http://forum.xda-developers.com/showthread.php?t=1179750
Working Solution!
Spunix said:
follow these steps... must have windows xp to work
http://forum.xda-developers.com/showthread.php?t=1179750
Click to expand...
Click to collapse
YOU ARE A LIFESAVER! It worked!!!
It really works just on a Windows XP.
See the sticky at the top of Q&A. http://forum.xda-developers.com/showthread.php?t=1180331

unbricking help

alright so somehow in the process of flashing and going back to stock and what not I messed up my g2x and now I have no baseband or battery info and whatnot, you all know the story. Ive spent the last 5 days on the internet trying everything I could find to get it up and running again and I keep hitting a brick wall.. Yes ive searched and tried multiple things but the one thing that I cant get past is the kdz flashing, everytime, no matter what I do, it always gives me the phone not found error, the USB cable and port are fine and I have the drivers installed and everything. Ive tried on VM Xp mode and in Win 7 Ultimate and no luck. If someone can give me some help/support thatd be awesome.
http://forum.xda-developers.com/showthread.php?p=16362191
Sent from my LG-P999 using Tapatalk 2
okay, but ive done that, after i flash stock recovery it just boots up and its normal except still no baseband and ? battery. Then i try to kdz flash and it says phone not found.. cable and port are fine.
Gameler said:
okay, but ive done that, after i flash stock recovery it just boots up and its normal except still no baseband and ? battery. Then i try to kdz flash and it says phone not found.. cable and port are fine.
Click to expand...
Click to collapse
jrfaulkin said:
You can use XP mode to do this, and yes the USB driver will detach. Just re-attach it and the flasher will kick right back in where it left off. I had to do this just twice during the procedure. As long as you stay on top of it you will have no problem.
http://forum.xda-developers.com/showthread.php?t=1180743
Click to expand...
Click to collapse
From the same thread...read the thread...the answers/suggestions are there...
Sent from my LG-P999 using Tapatalk 2
yeah and everytime i hit start the program just freezes

[Q] Oneplus one bootloop

Hello. A few days ago my one arrived (with two hits in the frame). I used it without any problems until the battery was at 2%, then I put him in charge and when it came to 100% it started to reboot constantly. The few times it doesn't stop on the 1+ screem it works without recognizing the sim only for a maximum of 2 minutes (but usually a few seconds). Then it "restarts to restart". When I had the time to do that I noticed that in the settings the IMEI is unknown. Is this a problem that someone has already had? Is it fixable? I tried everything, all types of wipe and also to flash the stock from fastboot in two different versions but nothing. I unlock the bootloader and I install the CWM recovery to try installing the CM11 or ColorOS but there is no way to transfer them on the phone. Nothing also with twrp. I try adb sideload but it blocks at 17 %. When the pc recognizes the opo the copy of the rom stops in the middle. Adb push doesn't work. Can be an idea try to remove the battery? I don't want to do it if it is not necessary. I opened a request for a replacement but given the long development times I would like to solve by myself. Thank you for the attention and sorry for my bad english.
you can access your phone through adb yeah? have you checked logcat? at what point is it restarting?
eudemonics said:
you can access your phone through adb yeah? have you checked logcat? at what point is it restarting?
Click to expand...
Click to collapse
Yes I can access through adb. I can use the phone for 3 second such 2 minutes, so there is not a fixed point. It restarts when it wants. Five minutes ago I flashed cm11 through otg with cmw, but I didn't solve the problem. A moment ago I flashed coloros through otg but nothing. I completed the configuration, i did two swipes, than it restart the bootloop. I'm going crazy. Francly I don't know logcat
please someone help me
Have u tried to flash via fastboot the full image from cyanogen web site?
Hey bud, I'm having similar problems as you,no imei,reboots,bootlooping...all of it.
Sent from my ME302C using Tapatalk
bagadj said:
Have u tried to flash via fastboot the full image from cyanogen web site?
Click to expand...
Click to collapse
of course, I tried it with the 25r version of the cyanogenmod and also with the 22q many times
tdamocles said:
Hey bud, I'm having similar problems as you,no imei,reboots,bootlooping...all of it.
Sent from my ME302C using Tapatalk
Click to expand...
Click to collapse
It's incredible. I opened a RMA but I am still waiting for a response.
gallici96 said:
Yes I can access through adb. I can use the phone for 3 second such 2 minutes, so there is not a fixed point. It restarts when it wants. Five minutes ago I flashed cm11 through otg with cmw, but I didn't solve the problem. A moment ago I flashed coloros through otg but nothing. I completed the configuration, i did two swipes, than it restart the bootloop. I'm going crazy. Francly I don't know logcat
Click to expand...
Click to collapse
it's an ADB command used for debugging. you might be able to see just what's causing the phone to bootloop.
https://developer.android.com/tools/help/logcat.html

[Q] Verizon Samsung Galaxy SIII (SCH-1535) BOOT LOOPED, LOST RECOVERY AND OS!!

HELP!!!
About 1 month ago, my Galaxy S3 running 4.4.2 (Completely stock: no root, rom, or custom firmware), suddenly got into a boot loop about 3 weeks after receiving the 4.4.2 update. At first, it would boot up completely into the OS, then shut down before I even had time to enter PIN. Sometimes, after shutting down, it would restart by itself, but only on some occasions. I was able to enter and constantly use recovery and download mode with no shutdowns, so it wasn't a battery problem, instead a software/firmware one. I found that if the phone was plugged in while booting, I was able to use the phone with no problem, but it shut off as soon as the charger was removed. I then factory reset it, wiped the cache and such, but the problem still persisted. After about not touching it for a week, the phone wouldn't even make it past the first Samsung boot animation and jingle without turning off. However, the plugging in method would make it go further into the boot sequence, but it still wouldn't boot into the OS. After leaving it alone for one more week, I then LOST RECOVERY ACCESS! It would boot up to the android figure, but shut off immediately. I was able to access download mode, and therefore, tried to flash an earlier firmware with ODIN.
The phone was recognized by ODIN, but the flashing process failed. I first tried to root the stock ROM, but ODIN couldn't find the recovery. I then tried to downgrade my firmware to 4.1.2. I got a FAIL message on my PC and an error message on the phone (in ODIN mode) saying, " SW REV CHECK FAIL: FUSED 2 BINARY 0" Now every time I try to turn on the phone, it goes straight into ODIN mode, and it shows the message, : Firmware upgrade encountered an issue, Please use Software Repair Assistant & try again" with an image of a phone and PC linked together, but being interrupted by a yellow triangle with an exclamation mark in it.
HELP ME PLEASE. I LOVE THIS PHONE AND I STILL HAVE A WHILE UNTIL I CAN GET A NEW ONE!!!!
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
cindylike24 said:
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
Good point cindy if its an internal hardware issue verizon will replace it at no charge
From my Wicked S3 running MIUI
how is this even possible?
gorilla29 said:
HELP!!!
About 1 month ago, my Galaxy S3 running 4.4.2 (Completely stock: no root, rom, or custom firmware), suddenly got into a boot loop about 3 weeks after receiving the 4.4.2 update. At first, it would boot up completely into the OS, then shut down before I even had time to enter PIN. Sometimes, after shutting down, it would restart by itself, but only on some occasions. I was able to enter and constantly use recovery and download mode with no shutdowns, so it wasn't a battery problem, instead a software/firmware one. I found that if the phone was plugged in while booting, I was able to use the phone with no problem, but it shut off as soon as the charger was removed. I then factory reset it, wiped the cache and such, but the problem still persisted. After about not touching it for a week, the phone wouldn't even make it past the first Samsung boot animation and jingle without turning off. However, the plugging in method would make it go further into the boot sequence, but it still wouldn't boot into the OS. After leaving it alone for one more week, I then LOST RECOVERY ACCESS! It would boot up to the android figure, but shut off immediately. I was able to access download mode, and therefore, tried to flash an earlier firmware with ODIN.
The phone was recognized by ODIN, but the flashing process failed. I first tried to root the stock ROM, but ODIN couldn't find the recovery. I then tried to downgrade my firmware to 4.1.2. I got a FAIL message on my PC and an error message on the phone (in ODIN mode) saying, " SW REV CHECK FAIL: FUSED 2 BINARY 0" Now every time I try to turn on the phone, it goes straight into ODIN mode, and it shows the message, : Firmware upgrade encountered an issue, Please use Software Repair Assistant & try again" with an image of a phone and PC linked together, but being interrupted by a yellow triangle with an exclamation mark in it.
HELP ME PLEASE. I LOVE THIS PHONE AND I STILL HAVE A WHILE UNTIL I CAN GET A NEW ONE!!!!
Click to expand...
Click to collapse
I would love to help, but please help me first. how do you claim to have 4.4 kitkat when for the i535 there is confirmed to only be 4.3 for a stock OS? this will make a big difference in the outcome of who can help you. Google and android both confirm that 4.3 is the last update for this phone coming from verizon. How can you have 4.4 stock with touchwiz and everything? unless you have AOSP, which is another things entirely. this phone does poorly for 4.4 in AOSP because we don't have a proper kernel or baseband for it. it wasn't officially released.
anyway, that is my question to you.
cyberkeeper1 said:
I would love to help, but please help me first. how do you claim to have 4.4 kitkat when for the i535 there is confirmed to only be 4.3 for a stock OS? this will make a big difference in the outcome of who can help you. Google and android both confirm that 4.3 is the last update for this phone coming from verizon. How can you have 4.4 stock with touchwiz and everything? unless you have AOSP, which is another things entirely. this phone does poorly for 4.4 in AOSP because we don't have a proper kernel or baseband for it. it wasn't officially released.
anyway, that is my question to you.
Click to expand...
Click to collapse
4.4.2 is the latest and probably the last update for the i535. This should fix your problem OP. http://forum.xda-developers.com/showthread.php?t=2791801
I wish it was.
cindylike24 said:
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
No, Cindy, it isn't under warranty anymore. It has been more than one year. I wish it was though!
Thanks, but...
JudgeFutta said:
4.4.2 is the latest and probably the last update for the i535. This should fix your problem OP. http://forum.xda-developers.com/showthread.php?t=2791801
Click to expand...
Click to collapse
Thank you so much for your help. I flashed the file, and I got recovery back. However, the phone has just returned to the state that this problem begun with. It still goes further into the boot sequence (still won't start) when plugged in, but it will shut off before it finishes and as soon as it's unplugged. It won't even start the sequence without the charger.
Any other suggestions?
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate. On ODIN, make SURE you check the bootloader update option, F. Reset Time, and auto reboot. Otherwise, the bootloader will not allow you to boot.
Sent from my SCH-I535 using XDA Free mobile app
gorilla29 said:
Thank you so much for your help. I flashed the file, and I got recovery back. However, the phone has just returned to the state that this problem begun with. It still goes further into the boot sequence (still won't start) when plugged in, but it will shut off before it finishes and as soon as it's unplugged. It won't even start the sequence without the charger.
Any other suggestions?
Click to expand...
Click to collapse
Try flashing the .tar file from the second post. Also make sure you have odin setup correctly like cyberkeeper1 said.
cyberkeeper1 said:
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
VRUDNE1 4.4.2 has been available for roughly two months.
Verizon PDF (laziness, Verizon did not change the software name to VRUDNE1): http://www.verizonwireless.com/support/system_update/galaxys3.html
Samsung PDF (click first question under FAQ): http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
Quick online search: http://www.droid-life.com/2014/06/19/verizons-samsung-galaxy-s3-galaxy-s4-mini-kit-kat/
SlimSnoopOS said:
VRUDNE1 4.4.2 has been available for roughly two months.
Verizon PDF (laziness, Verizon did not change the software name to VRUDNE1): http://www.verizonwireless.com/support/system_update/galaxys3.html
Samsung PDF (click first question under FAQ): http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
Quick online search: http://www.droid-life.com/2014/06/19/verizons-samsung-galaxy-s3-galaxy-s4-mini-kit-kat/
Click to expand...
Click to collapse
Many thanks, Slim.
Should be made a sticky. This is important stuff for this phone.
Sent from my SCH-I535 using XDA Free mobile app
cyberkeeper1 said:
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate. On ODIN, make SURE you check the bootloader update option, F. Reset Time, and auto reboot. Otherwise, the bootloader will not allow you to boot.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Would the file go under PDA (AP) or BL?
gorilla29 said:
Would the file go under PDA (AP) or BL?
Click to expand...
Click to collapse
PDA (AP)
JudgeFutta said:
PDA (AP)
Click to expand...
Click to collapse
I tried everything you suggested. I am able to boot into the OS, but only while connected to power. Definitely helped, but didn't solve.
Any suggestions?
gorilla29 said:
I tried everything you suggested. I am able to boot into the OS, but only while connected to power. Definitely helped, but didn't solve.
Any suggestions?
Click to expand...
Click to collapse
However, the phone will still shut down once booted, despite it being connected to power.
gorilla29 said:
However, the phone will still shut down once booted, despite it being connected to power.
Click to expand...
Click to collapse
It may be the battery or the phone just went out.
JudgeFutta said:
It may be the battery or the phone just went out.
Click to expand...
Click to collapse
Maybe, but the phone never shuts off during recovery. I bet the phone is just done. Lol

[Q] DAMN IT! Deleted everything - NO OS Installed

So I was going to reinstall Cataclysm ROM because it has been giving me problems the last few days, mainly it's been dropping my WiFi signal forcing me to switch it on and off just to use my phone, like once every minute
So I downloaded the file to my device, and went to flash it, but I wiped the dalvik and cache, and I pressed data I'm pretty sure, 100% by accident cuz I was so mad at my WiFi signal constantly dropping
Anyways now my phone says "No OS Installed, are you sure you want to reboot?"
I just did a few hours worth of research and... nothing seems to work
I've tried a few ADB sideload guides but I can't seem to follow what they're saying since my screen shows something completely different than what theirs shows
I checked a couple forums too and no one else was experiencing what I am
So I've come to you guys to help D:
Basically I have TWRP installed, my computer doesn't recognize the device when I use the flashall.bat in Windows, so I tried a few different cables, same thing
Any other ideas?
I saw the USB OTG method works, should I just buy one of those and try it out?
It's just like an add on hard drive that I'll load the ROM onto right?
Do I have to flash the stock img or can I flash a new ROM, like Cataclysm again, or Carbon or something?
I'm going to go buy one of those USB OTG drives, a Kingston 32 or 64gb one from Canada Computers
#fingerscrossed it works guys!
If you have anything else for me to try let me know!
devchaube said:
Basically I have TWRP installed, my computer doesn't recognize the device when I use the flashall.bat in Windows, so I tried a few different cables, same thing
Click to expand...
Click to collapse
Flashall.bat, which uses the program fastboot, isnt meant to be used with a recovery (in this case, TWRP). It is to be used on the bootloader.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Flashall.bat, which uses the program fastboot, isnt meant to be used with a recovery (in this case, TWRP). It is to be used on the bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah the bootloader is the menu with the reccovery, restart BL, and start, and poweroff right
i tried it on that menu too, did not work
be back in an hour, gonna go get the usb otg, good sale right now, $15 for 32gb!
beekay201 said:
Flashall.bat, which uses the program fastboot, isnt meant to be used with a recovery (in this case, TWRP). It is to be used on the bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Back in business! Picked up a couple of USB 32GB OTGs for $15 each (WICKED)
Plugged them into my PC, transferred 3 ROMs over (Cataclysm, XtraSmooth, and Stock IMG)
Just tried Cataclysm now, and it's working, everything was successful, and no problems!
Damn I love USB OTG
devchaube said:
Yeah the bootloader is the menu with the reccovery, restart BL, and start, and poweroff right
i tried it on that menu too, did not work
be back in an hour, gonna go get the usb otg, good sale right now, $15 for 32gb!
Click to expand...
Click to collapse
If it did not work there, it must have been a missing driver issue. Or your fastboot setup.
Sent from my Nexus 5 using Tapatalk
Okay so I flashed Cataclysm ROM and XtraSmooth ROM but they both give me a black screen after the white "android" logo is done
I think its the black screen of death
Any ideas on how to get rid of it?
devchaube said:
Okay so I flashed Cataclysm ROM and XtraSmooth ROM but they both give me a black screen after the white "android" logo is done
I think its the black screen of death
Any ideas on how to get rid of it?
Click to expand...
Click to collapse
Wipe /data before you switch roms
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Wipe /data before you switch roms
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Got it working last night, since I couldn't do it using TWRP or CMD
I just used Wugs Toolkit, selected the bricked / bootloop option, and flashed stock + unrooted it
Loaded the newest imgs available, so I'm good for now
I'll wait a bit, see if the WiFi thing comes back on stock, if not then it was probably something to do with Cataclysm, I didn't even save any logs to hard to see what it was
Thanks for all your help though!
It didn't work because you didn't install the drivers for adb/fastboot properly. Anyhow nice to see your device is working again!

Categories

Resources