I don't know if I am missing anything, but I have rechecked each step five times. The phone is recognized a US998 on Oreo 20b. I installed all the drivers for fastboot(not an issue since it works on my pixel), and lg's device drivers. I have also enabled oem unlocking and usb debugging and changed the usb mode to photos. ADB works fine, but fastboot does not function at all. I have bootloader unlocked and rooted many devices, but I cannot understand why this is happening.
whowatchlist said:
I don't know if I am missing anything, but I have rechecked each step five times. The phone is recognized a US998 on Oreo 20b. I installed all the drivers for fastboot(not an issue since it works on my pixel), and lg's device drivers. I have also enabled oem unlocking and usb debugging and changed the usb mode to photos. ADB works fine, but fastboot does not function at all. I have bootloader unlocked and rooted many devices, but I cannot understand why this is happening.
Click to expand...
Click to collapse
fastboot only works while your phone is in bootloader (e.g. after adb reboot bootloader), it doesnt work while being booted into a system (or recovery), adb is there for that.
SGCMarkus said:
fastboot only works while your phone is in bootloader (e.g. after adb reboot bootloader), it doesnt work while being booted into a system (or recovery), adb is there for that.
Click to expand...
Click to collapse
I am in the bootloader when I type the commands, because I see instructions on how to unlock the bootloader on my phone. I also have options for power off and reboot.
so from usb debugging you did
adb reboot bootloader
then the phone reboots to fastboot and you typed to verify you were connected to fastboot
fastboot devices
I had to try a few different computers before i got it to work. Same exact adb software and unlock files. One one computer the fastboot was acting screwy and on the other it worked immediately.
Please share the exact commands you are typing and the output.
My computer shouldn't be the issue, since I tested fastboot commands with my pixel yesterday. After I issue any fastboot command (including fastboot devices) it says " <waiting for device> " . I've used fastboot on other devices many times, so I understand what I'm supposed to do.
whowatchlist said:
My computer shouldn't be the issue, since I tested fastboot commands with my pixel yesterday. After I issue any fastboot command (including fastboot devices) it says " <waiting for device> " . I've used fastboot on other devices many times, so I understand what I'm supposed to do.
Click to expand...
Click to collapse
So it shouldn't hurt to try another computer then.
LG drivers can be wonky.
If it works on another computer, then you can figure out WHY, instead of just complaining it should work on that one computer.
I've seen where changing cables made a difference, changing ports made a difference, changing ADB installations made a difference, and changing computers. Don't ask me why.
ChazzMatt said:
So it shouldn't hurt to try another computer then.
LG drivers can be wonky.
If it works on another computer, then you can figure out WHY, instead of just complaining it should work on that one computer.
I've seen where changing cables made a difference, changing ports made a difference, changing ADB installations made a difference, and changing computers. Don't ask me why.
Click to expand...
Click to collapse
So far I've tried 2 computers, FWUL, and 3 different adb installations, along with all available USB ports. I have exhausted my opinions.(I may have 1 more cable)
whowatchlist said:
So far I've tried 2 computers, FWUL, and 3 different adb installations, along with all available USB ports. I have exhausted my opinions.(I may have 1 more cable)
Click to expand...
Click to collapse
Try FRANKENSTEIN again, but this time DL PARTITION the Oreo KDZ?
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Try FRANKENSTEIN again, but this time DL PARTITION the Oreo KDZ?
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Unfortunately I have already tried that.
whowatchlist said:
Unfortunately I have already tried that.
Click to expand...
Click to collapse
What variant did you start with?
Sent via open market LG US998 V30/V30+
I started as a VS996, then I flashed us998 10d nougat with dl partition, next I reset and upgraded to us998 20b oreo, tried fastboot and failed, then flashed 20b with dl partition and tried again.
whowatchlist said:
I started as a VS996, then I flashed us998 10d nougat with dl partition, next I reset and upgraded to us998 20b oreo, tried fastboot and failed, then flashed 20b with dl partition and tried again.
Click to expand...
Click to collapse
That is very strange. May not make a difference, but maybe try US998 20A.
After bootloader unlock and TWRP, you can flash the 20D ROM, so it doesn't matter you're using "early" Oreo.
Thanks to everyone that helped me. I busted out my old dell laptop and used my pixel's cable to get the phone recognized. Then I went to device manager and updated the device driver to a android bootloader interface(of which I somehow had multiple???). Now fastboot works fine. Quite the interesting ordeal huh.
If anyone runs into a similar issue, you should look in device manager for the phone. If there is nothing, you have to try a new cable/usb port/computer. If the device is shown, update its driver to android bootloader interface. This may be a fringe case, but Microsoft is constantly breaking drivers with windows 10
whowatchlist said:
Thanks to everyone that helped me. I busted out my old dell laptop and used my pixel's cable to get the phone recognized. Then I went to device manager and updated the device driver to a android bootloader interface(of which I somehow had multiple???). Now fastboot works fine. Quite the interesting ordeal huh.
If anyone runs into a similar issue, you should look in device manager for the phone. If there is nothing, you have to try a new cable/usb port/computer. If the device is shown, update its driver to android bootloader interface. This may be a fringe case, but Microsoft is constantly breaking drivers with windows 10
Click to expand...
Click to collapse
Glad it worked out.
I don't think its a fringe case. I also had to use a different computer and on the other computer i did not install the lg drivers. Fastboot worked instantly.
Related
I tried rooting my LGP-769 (originally 20f) using a bin and KDZ for 20d. Halfway through, the software (on the PC) crashed, and now my phone is stuck at "S/W Upgrade" screen. It no longer appears in device manager, and the LG software used for flashing does not see it as connected, so I can't flash anything back that way. Things that I've tried:
Hard boot: no change, still stuck at S/W upgrade
Leave battery out for 15 min: no change
Can't flash because device no longer exists in Dev Manager
Do I have any options here? What went wrong?
Thanks in advance. I've only been a smartphone owner for a week and I'm worried that I've already ruined my device.
I can fastboot (just gets to mirrored LG logo), but this does not allow access to any software, nor does this change anything in device manager or the LG recovery tool.
http://forum.xda-developers.com/showthread.php?p=44756934
CM 10.1 P769
kuma82 said:
http://forum.xda-developers.com/showthread.php?p=44756934
CM 10.1 P769
Click to expand...
Click to collapse
Thanks for the tip! Unfortunately this did not work for me; I posted details of how it failed in that thread, but the short story is that LG's KDZ-uploading tool does not see the phone as connected, even though the OMAP fastboot device does appear in windows' device manager. Do you have any other thoughts on how this might be fixed?
Are you sure you flashed the ice cream x & u? Try doing in manually to make sure?
CM 10.1 P769
kuma82 said:
Are you sure you flashed the ice cream x & u? Try doing in manually to make sure?
CM 10.1 P769
Click to expand...
Click to collapse
I tried ICS and JB in the fastboot utility for all models on the file (p760, 768, 759 I think); none worked. Which is to say that the phone looked like it fastboot'd (according to display and dev manager), but the LG utilities (used for KDZ flashing) would always say the phone is disconnected.
What do you mean by doing it manually? I haven't seen an option like that before - interested.
When you fastboot and choose 769 ics x and you you should see it say its copying x and u. Doesn't sound like it went through proper. I have wiped completely the boot partition and flashing those 2 make it recognize the phone again.
Sent from my LG-P769 using xda app-developers app
quickfastgoninja said:
I tried ICS and JB in the fastboot utility for all models on the file (p760, 768, 759 I think); none worked. Which is to say that the phone looked like it fastboot'd (according to display and dev manager), but the LG utilities (used for KDZ flashing) would always say the phone is disconnected.
What do you mean by doing it manually? I haven't seen an option like that before - interested.
Click to expand...
Click to collapse
Instructions for doing it manually.
http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
Note: if you get type
fastboot devices and nothing comes up, you might not have installed the drivers twice. If you do see fastboot installed in two locations, let me know you might have another issue.
CM 10.1 P769
kuma82 said:
Instructions for doing it manually.
http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
Note: if you get type
fastboot devices and nothing comes up, you might not have installed the drivers twice. If you do see fastboot installed in two locations, let me know you might have another issue.
CM 10.1 P769
Click to expand...
Click to collapse
Thanks, I'll give that a shot tonight. What does the poster mean by "images" to move into the folder - KDZs?
quickfastgoninja said:
Thanks, I'll give that a shot tonight. What does the poster mean by "images" to move into the folder - KDZs?
Click to expand...
Click to collapse
Lol I am the poster, I extracted the images .img files. You have to download the files (.img s)and put them in the "yours" folder. Open the fastboot (lelus) folder and inside you will find another folder named yours.
CM 10.1 P769
kuma82 said:
Lol I am the poster, I extracted the images .img files. You have to download the files (.img s)and put them in the "yours" folder. Open the fastboot (lelus) folder and inside you will find another folder named yours.
CM 10.1 P769
Click to expand...
Click to collapse
Whoops! Sorry about that...
Ok, flashed following those procedures with those IMGs. Tried using LG Mobile Support Tool --> Upgrade Recovery, but that still hangs as usual. I'll try the Lelus method for flashing V20D kdz next. I'm guessing I should let it return to S/W Upgrade mode, and not try to keep it fastboot'd for this?
Thanks again.
More info on fastboot
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55
CM 10.1 P769
Ok, I tried both LG update tool's recovery as well as the offline flash method - each of these in both fastboot mode as well as S/W upgrade (after fastboot + reset) - no luck, unfortunately. Update tool hangs, and offline flash says cell phone is not connected.
I've never seen fastboot drivers in more than one location in dev manager though - never saw it listed under "TI boards"? I had thought that fastboot was successful because [fastboot devices] command lists the device as connected (following manual IMG flashing).
quickfastgoninja said:
Ok, I tried both LG update tool's recovery as well as the offline flash method - each of these in both fastboot mode as well as S/W upgrade (after fastboot + reset) - no luck, unfortunately. Update tool hangs, and offline flash says cell phone is not connected.
I've never seen fastboot drivers in more than one location in dev manager though - never saw it listed under "TI boards"? I had thought that fastboot was successful because [fastboot devices] command lists the device as connected (following manual IMG flashing).
Click to expand...
Click to collapse
I never used the lg recovery tool, but I heard it takes a couple of hours to download and run. Maybe you though it was hanging, but it wasn't.
CM 10.1 P769
seriously guys help....!!!
hey guys i wanted to unlock my bootloader
was following multiple guides as when i typed "adb reboot oem-unlock" it used to reboot phn normally
i used OMAPFlash_1229_2ndlastt and did something with "uboot" after that nothing is working
no s/w mode nothing... but my pc device manager detects it...
seriously guys help....!!!
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script to get into fastboot at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
So you solve it! :good:
:/
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
foreverman said:
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
Click to expand...
Click to collapse
Then try enter in lelus fastboot mode, ad then flash x-loader, uloader, boot.img and recovery.img from stock rom for your device type model. Then repeat steps 1 and 2
Where can I find the lelus script?
Sent from my Note II
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Then you need a Technician with a Octopus Box to repair your partition table...
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Can you boot into recovery? We now have a custom recovery for locked bootloaders (and CM roms). If you can get into recovery, I would try some adb commands to mount the partitions.
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
ciccillover said:
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
Click to expand...
Click to collapse
Your EMMC partition is wiped or fried... you really need a JTAG service or a Box like octopus because your L9 is Hard-bricked...
Thanks for your opinion. Yet, I still want to hear from others.
I'm running into more and more problems with the L9 as their me grows.
-Fastboot doesn't work under Windows 8.1 and 10, but under the now obsolete(for me) Windows 7, unlike my other devices, which are fine with Win 10.
-ADB seems to work, but requiring the device to be still able to boot.
-I always boot to recovery from within Android as long as the L9 ain't bricked. After a failed rom install, during which the sd card failed(could no longer write or be formatted afterwards, the last time stamps of files and folders were set during the failed install) I discovered a problem with TWRP(Artas182x's and Edwin's), which may have been present since a long time: Trying to invoke TWRP via keypress will brick the device!
So, if my P760 no longer boots, there's only download mode available, sort of the final line of defense.
-There's sort of a trick if even download mode fails: After a failed attempt unplug phone, force switch-off, if the phone is in brick state. Then switch on, force switch-off again, and only then attempt download mode again. And have patience while holding down the vol button, it might take up to 20 seconds for the phone to switch itself on into download mode. (A single forced powerdown will cause Fastboot NOT to work the next time)
But I'm absolutely clueless about the recovery issue, for now TWRP is semi-working, can only be accessed via Android, as long as the phone is fully working.
W/o Fastboot, I now have flashed stock rom several times and rooted it with Kingo rooter just to be able to run Flashify to install TWRP. If Flashify is the culprit for the TWRP issues, I could need a recommendation for a better working app.
ciccillover said:
Thanks for your opinion. Yet, I still want to hear from others.
Click to expand...
Click to collapse
Tried OMAP flasher ? It needs memory configuration file in order to work with our device
No, I didn't. I have sold the phone for spares.
Inviato dal mio LG-D855 utilizzando Tapatalk
I never needed the OMAP drivers and tools. As they are ancient, they will probably make even more problems with newer Windows versions.
I could by no means invoke Fastboot on this device with Windows 8.1 and 10, Seven worked. So you had to go for Download Mode instead to recover to stock rom, then root with the Kingo tool, then install TWRP via Rashr or Flashify, the most time consuming way to recover from the frequent bricks.
And the LG Flash Tool 2014 always needed several attempts to get the job done. The latest official recovery tool from LG works in D/L Mode, but will always download the rom image anew.
Can someone help me out with the commands that will wipe my g3 of everything through ADB. My screen is so damaged nothing responds by touch. Normally I wipe everything in recovery... But that's not possible with the screen so damaged
Not what you're asking for but it would be what I would do ...
I would put the phone in Download mode (you can verify it's in download mode by looking for the LG or LGE entry in Windows' Device Manager in the Modem section), then use LG Flash Tool to flash whichever stock KDZ you want (10B, 12B, 23C, 24B or 35B) in CSE mode. That'll wipe everything off your phone except your MicroSD card.
roirraW "edor" ehT said:
Not what you're asking for but it would be what I would do ...
I would put the phone in Download mode (you can verify it's in download mode by looking for the LG or LGE entry in Windows' Device Manager in the Modem section), then use LG Flash Tool to flash whichever stock KDZ you want (10B, 12B, 23C, 24B or 35B) in CSE mode. That'll wipe everything off your phone except your MicroSD card.
Click to expand...
Click to collapse
I use a mac. Phone is toast.... Sim card slot failed, then it dropped on my driveway. I got a N 6p so I really just want to erase it and recycle it.... But I don't have access to a Windows computer. It's mac only right now. Is it possible to kdz on a mac? Never done the tot or kdz route.... Never had to
318sugarhill said:
I use a mac. Phone is toast.... Sim card slot failed, then it dropped on my driveway. I got a N 6p so I really just want to erase it and recycle it.... But I don't have access to a Windows computer. It's mac only right now. Is it possible to kdz on a mac? Never done the tot or kdz route.... Never had to
Click to expand...
Click to collapse
Okay, I see. No, there's no way to flash a KDZ or TOT on a Mac.
Okay, another way possibly around this issue, but first some questions. You have the Mac driver installed from http://www.lg.com/us/support-mobile/lg-VS985-Metallic-Black?
If you go through the motions of putting the phone in Download mode, do you know where to look/how to verify that the Mac recognizes it? I don't, so I'm no help there.
Assuming that again, despite the screen being unreadable or blank, but if the Android OS does load on the phone, you won't be able to do adb / superuser commands because if this is the first time you'll have done this from this Mac installation to that particular Android ROM installation, you'll 1) have to already have had USB Debugging enabled on the phone and 2) the first time a prompt will pop up on the phone asking for confirmation to either once or permanently allow adb commands from that particular computer OS installation. I forget but maybe also the first time you do commands that would require SuperUser access, you might get a prompt on the phone for that.
So. Download mode or going through the necessary motions in recovery or custom recovery would be the only way.
Do you have stock or custom recovery? Either way if I gave you a screenshot of what you would see on each step you could hit the right things and then at least if you still have an Android OS that'll load, you might be able to verify via MTP that internal storage is wiped, and you could just leave it on faith that you also correctly wiped data and caches.
Is completely destroying the phone beyond all possible usefulness a possibility?
I have twrp installed. USB debugging is on. It was running skydragon ROM with Holyangels custom kernel. I can use android sdk with Mac terminal to flash any commands. I can get into the recovery and see the screen... But no touches register on the device. The screen is shattered and the digitizer is damaged.
318sugarhill said:
I have twrp installed. USB debugging is on. It was running skydragon ROM with Holyangels custom kernel. I can use android sdk with Mac terminal to flash any commands. I can get into the recovery and see the screen... But no touches register on the device. The screen is shattered and the digitizer is damaged.
Click to expand...
Click to collapse
I was thinking the volume and power keys can be used as an alternate to the touchscreen.
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
Unfortunately not in twrp.
I might be in luck but no clue how. So I plugged the phone into my computer and I had zero battery. It booted up and before I could even open the terminal, it said android is upgrading with the warning get not to pull the battery. Since there was zero power it shut down. I put It on the charger and upon rebooting it's at the setup screen. Very bizarre
I found the commands I was looking for (or at least going to try) but somehow with the setup wizard going USB debugging is now unchecked. A box comes up to allow it when running commands from terminal but with the screen so borked no chance to check that box. Gonna take a hammer to it now I guess to be sure it's damaged beyond repair
318sugarhill said:
I found the commands I was looking for (or at least going to try) but somehow with the setup wizard going USB debugging is now unchecked. A box comes up to allow it when running commands from terminal but with the screen so borked no chance to check that box. Gonna take a hammer to it now I guess to be sure it's damaged beyond repair
Click to expand...
Click to collapse
You can run adb commands while in twrp. You can also simulate touch events with adb.
Can I run ADB commands in twrp without USB debugging checked?
318sugarhill said:
Can I run ADB commands in twrp without USB debugging checked?
Click to expand...
Click to collapse
Im pretty sure you can. It would take two seconds to try and find out.
Sent from my LG-VS985 using Tapatalk
318sugarhill said:
Can I run ADB commands in twrp without USB debugging checked?
Click to expand...
Click to collapse
I don't think any settings in the running Android ROM affect custom recovery capabilities at all.
roirraW "edor" ehT said:
I don't think any settings in the running Android ROM affect custom recovery capabilities at all.
Click to expand...
Click to collapse
I'm able to run ADB commands through Recovery....except the commands I wanted.....Tried to sideload a rom so it would wipe...but to no avail....have to swipe the screen to confirm the sideload! Android file transfer came up and I was able to delete everything from the internal SD card from there. I'm assuming since I'm getting the setup screen the rom is a fresh install (still not sure how that happened) and I can just recycle the device now without beating it to shreds.
318sugarhill said:
I'm able to run ADB commands through Recovery....except the commands I wanted.....Tried to sideload a rom so it would wipe...but to no avail....have to swipe the screen to confirm the sideload! Android file transfer came up and I was able to delete everything from the internal SD card from there. I'm assuming since I'm getting the setup screen the rom is a fresh install (still not sure how that happened) and I can just recycle the device now without beating it to shreds.
Click to expand...
Click to collapse
Can you verify via MTP through the USB connection to your Mac that any of your files aren't on your internal storage?
@318sugarhill You could also try pulling something from you internal sd card to see if it is still there...
Code:
adb pull /sdcard/DCIM/
...for example. If you get pictures, you need to try something else.
You dont happen to have a usb otg cable do you? Lol. I just tried my wireless mouse with mine in twrp and ti worked.
PiousInquisitor said:
@318sugarhill You could also try pulling something from you internal sd card to see if it is still there...
Code:
adb pull /sdcard/DCIM/
...for example. If you get pictures, you need to try something else.
You dont happen to have a usb otg cable do you? Lol. I just tried my wireless mouse with mine in twrp and ti worked.
Click to expand...
Click to collapse
Awwww! ^^^ Awesome idea!
@318sugarhill
Make sure and have everything plugged in before you turn the phone on, and don't unplug the OTG cable or mouse/adapter before turning the phone back off. I've blown up two OTG cables before.
@318sugarhill , road warrior, I just had another thought. PhilZ Touch Recovery has a buttons only mode, I believe you could flash it like when you first installed twrp (dd commands) and then wipe or install a rom or whatever. I havent ever used PhilZ though. There might be an swipe involved to change to hardware key mode.
This should work. I actually just tried it. Buttons mode works without changing anything.
PiousInquisitor said:
@318sugarhill , road warrior, I just had another thought. PhilZ Touch Recovery has a buttons only mode, I believe you could flash it like when you first installed twrp (dd commands) and then wipe or install a rom or whatever. I havent ever used PhilZ though. There might be an swipe involved to change to hardware key mode.
This should work. I actually just tried it. Buttons mode works without changing anything.
Click to expand...
Click to collapse
I'll give this try a later tonight. I do not have an oTG cable. I appreciate all the help.
PiousInquisitor said:
@318sugarhill , road warrior, I just had another thought. PhilZ Touch Recovery has a buttons only mode, I believe you could flash it like when you first installed twrp (dd commands) and then wipe or install a rom or whatever. I havent ever used PhilZ though. There might be an swipe involved to change to hardware key mode.
This should work. I actually just tried it. Buttons mode works without changing anything.
Click to expand...
Click to collapse
I wondered about PhilZ too. It's been too long since I used it so I couldn't remember.
So,
Yesterday i was trying to root my S7 (SM-G930V). I was going through all the lists of things to do from a website on rooting with Magisk. Using ADB and Fastboot to get it working. I'm stuck at trying to install the boot.img onto my phone but when I'm doing anything with Fastboot it is not seeing my device. i been looking around the web for any answers and got nothing. With ADB I got as far as connecting my device and rebooting it into boot-loader and all i got to do from what the website says is to download the boot.img to it using fastboot. Then the problem comes in with Fastboot not noticing my device. i have it connect with USB and all drivers up to date. I'm i missing something impotent? I'm still kinda newbie at this.
did you try a diff cable?
hiitsrudd said:
did you try a diff cable?
Click to expand...
Click to collapse
Yup, It just doesn't read the devices for some reason when its in bootloader
During a flash, the connection to my V30 was interrupted for some reason, probably a worn out USB cable getting knocked into and shifting around in the USB C port. Ever since then, the phone refuses to get past the bootloader or recovery if I hold down the proper keys.
I have used a modded version of LGUP that I originally downloaded to help frankenstein this phone to refurbish, upgrade, even chip erase (this does get rid of the IMEI and other important numbers but since this phone is no longer my daily it's fine if it has no IMEI to me, I'll be honest I'm not sure if chip erase gets rid of any other stuff that should absolutely never be touched). The phone still boots straight to the bootloader. I have also tried flashing custom recoveries (such as TWRP, this has been successful) and installing .zip format roms to the device through the recovery (not successful, still boots straight to bootloader without fail).
So uh... did I manage to brick my V30? Or does it sound like there's at least a bit of hope? Any help would be greatly appreciated, I really wanted to use this thing as a sort of glorified iPod because of that magical dac.
Jeebüüs said:
During a flash, the connection to my V30 was interrupted for some reason, probably a worn out USB cable getting knocked into and shifting around in the USB C port. Ever since then, the phone refuses to get past the bootloader or recovery if I hold down the proper keys.
I have used a modded version of LGUP that I originally downloaded to help frankenstein this phone to refurbish, upgrade, even chip erase (this does get rid of the IMEI and other important numbers but since this phone is no longer my daily it's fine if it has no IMEI to me, I'll be honest I'm not sure if chip erase gets rid of any other stuff that should absolutely never be touched). The phone still boots straight to the bootloader. I have also tried flashing custom recoveries (such as TWRP, this has been successful) and installing .zip format roms to the device through the recovery (not successful, still boots straight to bootloader without fail).
So uh... did I manage to brick my V30? Or does it sound like there's at least a bit of hope? Any help would be greatly appreciated, I really wanted to use this thing as a sort of glorified iPod because of that magical dac.
Click to expand...
Click to collapse
You've tried going into download mode manually, use Dev Patched LGUP in Refurbish mode to reinstall US998 20h KDZ?
ChazzMatt said:
You've tried going into download mode manually, use Dev Patched LGUP in Refurbish mode to reinstall US998 20h KDZ?
Click to expand...
Click to collapse
I've entered DL mode manually and I'm using the dev patched version of LGUP. I haven't tried that particular KDZ though, I could give it a shot for the hell of it. Anyways thanks.
Also, would using Qualcomm download mode work? I'm fine with opening up the phone to trigger the contacts, I just don't know if I'll be able to do any good once in that mode.
ChazzMatt said:
You've tried going into download mode manually, use Dev Patched LGUP in Refurbish mode to reinstall US998 20h KDZ?
Click to expand...
Click to collapse
Just tried that KDZ, didn't help.
Jeebüüs said:
Just tried that KDZ, didn't help.
Click to expand...
Click to collapse
Sorry.
What happens when you use ADB/fastboot commands to get to bootloader? It never finishes booting?
Jeebüüs said:
Also, would using Qualcomm download mode work? I'm fine with opening up the phone to trigger the contacts, I just don't know if I'll be able to do any good once in that mode.
Click to expand...
Click to collapse
First, you don't need to open the phone to enter QDLoader / EDL / 9008 mode:
With the phone connected to a PC (you don't need any special software loaded, just the USB connection), and with the phone powered on and unlocked, hold vol +, vol -, and power to shutdown the phone. Keep holding them till you get a countdown on the screen. The second the countdown completes, and the screen shuts off, let go of power, keep holding vol -, and start tapping the crap out of vol +.
If you have problems getting into recovery using the key combo, this is at least 5x as hard to get it right. When you do, the screen will be blank and the phone will show up in your OS as 9008. Example in Linux:
Code:
Bus 001 Device 015: ID 05c6:[B]9008[/B] Qualcomm, Inc. Gobi Wireless Modem ([B]QDL mode[/B])
To exit 9008 if you decide not to flash anything, just press and hold vol - and power until the phone reboots.
Now, with that said, you still need the firehose. I haven't looked for it yet because I haven't needed it, but there is a V30 (all models except the H932) firehose out there somewhere. Also, of course, you need QFIL.
Now will this help -- as long as there isn't a hardware problem with your phone, you can do anything you want in QDL mode with the understanding that signatures are still checked, so you can only flash V30 (non-H932) firmware. If flashing a KDZ doesn't fix your problem, you must have a problem with a partition that doesn't get flashed from a KDZ. Unfortunately, if you don't know which one, it will be trial and error and you will need a complete dump of a V30 minus EFS.
-- Brian
ChazzMatt said:
Sorry.
What happens when you use ADB/fastboot commands to get to bootloader? It never finishes booting?
Click to expand...
Click to collapse
Pretty much. Fastboot behaves normally and it does reboot with the fastboot reboot command but it just ends up right back at the bootloader unless I use the key combos required to get into LGUP DL mode/recovery.
That's great info Brian. Always thought opening phone, disconnecting battery ribbon, and shorting test points are only way to force qdl 9008 mode. Thanks for this info :good: