I picked up a VS985, but it has some odd stuff going on. It came rooted and is running 12B, but I figured I would factory reset it just to be sure.
However, factory reset doesn't work. The lights slowly flicker, but it never actually resets. Download mode doesn't work at all.
What's going on? How can I get this up and running? I've rooted the VS985 before, but I wasn't prepared for this.
Sounds like you might have either a bad device, or else the cable isn't working well if you can't get download mode to work at all. Do you have the original cables and have you installed the latest G3 drivers from LG?
Not sure that it'd be cables at all - the Factory Reset just doesn't fire (I get alternating red and blue colors out of the LED that don't seem to end). This is some kind of problem that pre-exists cable issues.
How would I go about restoring Download Mode without a recovery module to flash with?
Having problems with ADB commands as well... nothing seems to be readable, despite having SuperSU up and running. Hoo boy. I'd tried using the shell to load the laf.img on, but when it isn't readable... Damn.
Kept slamming it with options, ultimately imageprepGUI managed to get TWRP onto it, flash 10B, load in bootstacks, debloats, G4 weather... I'm in the clear. How annoying.
Related
So here's the story. I'm kind of terrified right now that my phone might be a goner. So, I was wanting to apply the new update to my galaxy but everytime I tried it would say "error" and wouldn't work. So I removed my root via superSU hoping that might help, with no success. So the nice people on this forum were directing me to flash a stock rom through odin to my phone. I kept trying and trying and my phone would never get recognized by odin so nothing would happen. I tried everything that I could read online to fix it and it never did. So I just decided that I would boot to recovery and do a clean wipe of my phone after I back it up. well the backup didn't work, so I just took my SD card out since it had most of the stuff I wanted to keep. I tried the clean wipe and it was done really quickly. I started up the phone and after I selected my language it said the setup wizard was stopped. Since then, I can't get the phone to boot correctly. It gets past the verizon splash screen(after a way longer wait than normal) and says "com.samsung.(something) has stopped working" and then just reboots itself. It'l almost stuck in this endless cycle. Can anyone help me out? If not, just give me the bad news straight up, do I need to trash this phone? Did I successfully kill it on accident?
GAMECOCK1801 said:
So here's the story. I'm kind of terrified right now that my phone might be a goner. So, I was wanting to apply the new update to my galaxy but everytime I tried it would say "error" and wouldn't work. So I removed my root via superSU hoping that might help, with no success. So the nice people on this forum were directing me to flash a stock rom through odin to my phone. I kept trying and trying and my phone would never get recognized by odin so nothing would happen. I tried everything that I could read online to fix it and it never did. So I just decided that I would boot to recovery and do a clean wipe of my phone after I back it up. well the backup didn't work, so I just took my SD card out since it had most of the stuff I wanted to keep. I tried the clean wipe and it was done really quickly. I started up the phone and after I selected my language it said the setup wizard was stopped. Since then, I can't get the phone to boot correctly. It gets past the verizon splash screen(after a way longer wait than normal) and says "com.samsung.(something) has stopped working" and then just reboots itself. It'l almost stuck in this endless cycle. Can anyone help me out? If not, just give me the bad news straight up, do I need to trash this phone? Did I successfully kill it on accident?
Click to expand...
Click to collapse
Restoring this is going to be fairly easy once you get ODIN working.
First, make sure that Kies isn't running. Kies and ODIN will conflict with each other.
Normally issues with ODIN are fixed by ensuring that the cable is good, trying different USB ports, uninstalling and reinstalling the drivers.
If nothing works and you can't get ODIN to work, you might be able to use the Verizon Recovery Assistant or Kies to restore your phone to factory.
k1mu said:
Restoring this is going to be fairly easy once you get ODIN working.
First, make sure that Kies isn't running. Kies and ODIN will conflict with each other.
Normally issues with ODIN are fixed by ensuring that the cable is good, trying different USB ports, uninstalling and reinstalling the drivers.
If nothing works and you can't get ODIN to work, you might be able to use the Verizon Recovery Assistant or Kies to restore your phone to factory.
Click to expand...
Click to collapse
I'm going to try it on another computer. Hopefully it'll work!
k1mu said:
Restoring this is going to be fairly easy once you get ODIN working.
First, make sure that Kies isn't running. Kies and ODIN will conflict with each other.
Normally issues with ODIN are fixed by ensuring that the cable is good, trying different USB ports, uninstalling and reinstalling the drivers.
If nothing works and you can't get ODIN to work, you might be able to use the Verizon Recovery Assistant or Kies to restore your phone to factory.
Click to expand...
Click to collapse
This seems to have worked! Thank you so much for your suggestion, you really made my whole week now. I seriously appreciate it!
Alright. I need some advice one last time, I swear... after this I'm not going to try to do anything.
Phone worked quite well for 2 days. I was enjoying this rom quite a bit. I decided to change the DPI down to 560. I saw that some others in this thread had done so quite easily... so I used this app to change it. Made the change to 560, granted supersu permission and rebooted. Only problem is that... the phone has yet to turn back on. At the moment the only thing I can get it to do is give me a screen that shows a large white empty battery with a cable leading up to it and a hazard exclamation mark in the bottom right when I am trying to put it in download mode. I have tried on multiple computers to restore back to stock following these directions. The best that happens is my computer recognizes an unrecognized device. No luck.
I would love to change the buildprop back or anything, but not even adb recognizes the device.
Otherwise, nothing. I can't get into recovery. I can't get the phone to start at all. All black screen. I can't get any reaction out of it. Any advice would be helpful, I'm on hour two of this. I realize that this is most likely not a problem with the rom, but wanted to see if anyone else had an issue and has advice/let anyone else who's thinking of changing the DPI and shared my troubles reconsider.
Thanks again!
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
1619415 said:
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
Click to expand...
Click to collapse
Thanks for the reply!
That emblem only shows up when the battery is removed and I'm trying to put the phone in download mode. So it makes sense. Any other ideas? The battery that I'm using is about 80% full. I still can't find a way to recovery mode.
What other information can I provide to help you out?
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
1619415 said:
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
Click to expand...
Click to collapse
No screen. For anything (other than described).
This is exactly what I was afraid of, but my phone has always been odd. This dead battery screen has always shown up in download mode... even when my phone worked, I've never had the firmware update screen. Which has always been weird to me.
However, the only time my phone shows anything is with the dead battery screen. During such it will show up as an unrecognized device when attached to a computer, again... it's always done this. I was just curious if there was something else or a suggestion that someone more experienced then myself might have.
No that I read it, it sounds like there maybe a very slim chance of getting your device to work. If you mange to get some drivers for the unreconized device driver you maybe able to send adb and fastboot commands. I found this one tool (will limk below) that is call cydia impactor I found in one of rootjunky's toolkit files. I used this one function that was able to make drivers for my sony smartwatch 3 and phone. I will link for the direct download make sure to extract the zip. Inside of the zip you will find another zip called "Impactor_0.9.14.zip" make sure to extract it to it's own folder. If you want you can delete the first folder juat save the impactor folder. Then run the program called "Impactor" can connect your phone to the computer and click on the tab called "USB" then click the button called "Driver Scan". Follow any on screen instructions. It should now generate a driver for your phone if all went well and it will be reconized. Then you should be able to run adb reboot recovery or fastboot reboot-bootloader. The fact that your computer is even seeing the phone tells me that it has so hope of being fixed because your computer see's it. Your device might be in a bootloop of some sort. You may just have no os installed and it may have just glitched.
Download: http://rootjunkysdl.com/getdownload.php?file=Tegra Note 7/ADB root.zip (will immeditly download it)
Worst case scenario, you may try this, or at least read it for general info. I don't think you'll have to go this far though
http://forum.xda-developers.com/showthread.php?t=2582142
[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2
i changed my dpi once and it bootlooped on me. i was lucky enough to get into recovery and then i restored the data partition from an older nandroid.
i agree with 16. it does sound like the drivers may not be loaded up properly if your computer recognizes a device. have you tried the official lg drivers?
What system are you guys running?
Well, I've found out that for whatever reason... on my phone I have to take out the battery for a period of ~5-10 mins on any change DPI, system rom update, anything. Otherwise, my phone will not turn on. So if someone else find this, give it a try.
Alright, so I did a bit of a stupid thing and I acknowledge it. Anyway, here's my steps for what I did:
1). KingRooted the phone, SuperSUme'd to remove KingRoot's stuff
2). Flashed a deodexed ROM through FlashFire for OF1 using a how to list to upgrade and keep root(This is where I think I went wrong, I should have stuck with OC1 to begin with but I was curious ), the flash was successful
3). Because one of my apps(Greenify) requires the Xposed framework for many of the useful settings, I tried flashing a version of the framework designed for non-MDK bootloaders(Arter97's unofficial TouchWiz) through FlashFire, since it seems to be the only way to flash custom stuff on 5.0+ stuff at the moment
4). After this(Just like when I tried Arter's framework with regular OC1), my phone's Google apps started their mass crashing and force closing, which I tried to combat with factory resets but no dice
Unlike before, however, something along the line in my steps disabled the ability to go to stock recovery mode(I think it was KingRoot itself but it might have been the deodexed ROM) and after a bit I couldn't factory reset. Before, I was able to simply Odin flash the stock OC1 ROM. Now, however, Odin won't work either to restore the firmware. I always get the "fail" messages(This I'm not sure why, though it happens with both OC1 and OF1 ROMs so I don't think it's a matter of downgrading). This leaves me with very few options to recover from, especially because I've even tried Verizon's repair program(Stops at 83% and disconnects) and Kies' emergency recovery(Phone isn't recognized and upon manual recovery the result is the same).
The biggest thing that grinds my gears is that my phone isn't even bricked...technically. It started, it went to the Setup Wizard, but then the Setup Wizard crashed once the Gmail portion of the setup was supposed to start in an infinite loop....a "setup loop" rather than a boot loop. I have been working for hours to try and find a solution but so far nothing is working. My phone only starts to the "Software update failed, please use the Verizon Repair etc." message now but no program can recognize it.
Is this a form of hard-bricking? Just not having any method of recovery work even if it turns on? I will admit I'm not the most advanced user but I've been flashing ROMs and custom stuff(Using guides and the like, I'm not fluent enough to go freestyle) for years through a couple of different phones so I'm not a completely new user either. This is the most FUBAR'd I've gotten a phone so far though and I honestly can't afford a new one...that's why I'm going through all the paces I possibly can. Is there any possible way to salvage this? I've been wanting to go to the LG G3 anyway(Despite the G4 being out, the G3's cheaper and still miles better than any Samsung phone, my old one got stolen) but right now it's just not possible. Any suggestions?
Edit: After switching USB ports(Mine are notoriously bad for connections being gained and lost, my memory is bad but I can't see why I didn't think this was the issue), the Verizon repair method has made the phone able to start up. Everything seems to be in order now, more or less. I will say the custom Samsung screen(The unlocked one) came up which makes me think I still have the deodexed ROM installed. If so, then cool beans.
So I was having so many issues with my rooted phone crashing on jasmineRom 7.0 I thought maybe an OTA update had made it through and started downloading. No matter what I was doing the screen would turn blue and then restart. Sometimes it would crash blue again during reboot, and sometimes it would crash and then show the green demigod crash screen. So I researched flashing the .tot files to go back to stock. KDZ I didn't care for because it still showed the phone as modified software, and I wanted full stock so I could use the extended warranty with Verizon if need be. I eventually got the .tot method to work and everything was hunky dory, and showing stock. I upgraded all the way to marshmallow and decided I love every bit of it, but I couldn't figure out how to get my contacts and stuff off titanium backup without root. So I figured, "well roots not the problem if an OTA tried to download it just means I missed a setting or something". So I rooted again. No issues, I reinstalled JasmineRom 9.1 this time. Eventually it started crashing again, although this time I followed absolutely every guide I could find on disabling OTA. So I thought, "Great it's Jasmine" and I really wanted Marshmallow anyway so I followed xdabbeb's guide for getting the 35b bootstack on my phone, worked great no issues, and then I installed xdabbeb's firmware, combined with Edor's debloating zips. Everything was working great! I had no issues, I backed up just my apps, and some data, and reinstalled others and everything was great and working fine, and the phone was still official, no OTA's getting through. That was almost a full week ago. Yesterday I woke up and the phone wouldn't turn on. I took the battery out and put it back in and the phone came on, but then crashed with the blue screen again. So I thought great I guess I'll put it back to stock and use the warranty. By this time though I was having trouble getting it to load past the LG screen. I finally got it into TWRP and was able to wipe everything (except SD card) and then I stuck it in download mode and went to install the .tot files. Weeeeelllll, long story short, it crashed during download mode install with the LG Flash Tool. So now the phone gets stuck in download mode everytime I pull the battery and power it on. And crashes again every time I go to install anything. KDZ doesn't work, the flash tool says it can't communicate with the phone, because it crashes. And LG Flash Tool for the .tot files seems to crash everything it loads the modem, or consistently crashes on LAF:bin_user_mode. So I have no idea. At the moment it just looks like my phone is all funky defective, and Verizon may take it back and give me a new one so I'm going to try that. HOWEVER! If anyone has any ideas on what the issue is or what else can be done, I still want to hear it. Feel free to post
Also I've tried updated drivers for the computer, I've tried rolling back drivers, I've tried different KDZ files, I've tried the LGUP8974.dll fix where you flash that in flash tools and then flash the vs985 dll, which is what I had to do to get it back to stock the first time. I've tried everything I could find online except anything to do with fast boot and shorting the pins. Which I haven't tried because I can still access download mode it just seems to be stuck in download mode. Those methods from what I understand are for hard bricking, and for people who's phones don't turn on at all. Although if Verizon won't help I may try one of the laf recovery methods.
Thanks!
I was having problems with the phone, ended up doing a full wipe, and from there decided I'd upgrade to the latest Jasmine ROM. I did the upgrade, but as a result, WiFi and Bluetooth were broken. Tried a number of solutions and none worked. Eventually tried a couple different ROMs, same problem. That said, I WAS up and running. I even flashed 35B bootloader again and tried with the ROMs. Still no luck. This was last night.
Flash forward to today, I'm trying again to flash Jasmine, and in the middle of the flashing process, screen turns off and I get the blue/green strobe light effect like when you power up normally. Oh ****. Leave phone for 45 minutes and realize it's in a loop. Responds to nothing, pull the battery, know I'm ****ed at this point.
Now, I can't get the screen to come on. Can't get into recovery or anything. Holding down the power with any combo of volume and other keys does nothing 90% of the time. About 10% of the time, I can get the phone to vibrate, then start the blue/green strobe, but nothing happens even after half an hour. I've recently discovered that if I plug into USB, I get a slow, slow flashing red light. As in the light is fully lit for three or four seconds, slowly fades out for a second or two, then slowly fades back. It doesn't appear to be communicating with the computer through USB, just drawing power.
Any suggestions? I'm 99% I'm screwed, so I'm willing to give anything a go.
The reason it happened is if you already had the 35B Bootstack (not bootloader - that's only part of the Bootstack and the 35B Bootstack actually uses the 12B Bootloader) before flashing JasmineROM v9 and you didn't flash any Bootstack after flashing the ROM (either 24B or 35B), then JasmineROM's limited selection of 24B partitions overwrote only select 35B partitions, leaving a catastrophic mix of critical 35B/24B partitions.
If you remove the battery, then put it back in and go through the motions of putting it in Download mode, even though you can't see the screen you can verify it's in Download mode by looking in Windows' Device Manager in the Port section listed as "LGE...".
If so, flash the 10B TOT and you'll be good to go, start fresh, and get in the habit of always flashing an appropriate Bootstack after either flashing a ROM or restoring a TWRP Backup.
@nyr2k2 any updates on this, did you get it fixed?
i have not yet had the opportunity to try, but between what you wrote and a pretty detailed explanation provided by @cory733 via PM, i feel pretty confident i would be able to. i ended up just going ahead and getting an s7 edge, and i haven't had the time to work on this. i do intend to give it a go and bring this thing back from the dead...it was/is a solid phone.
thx for the help.