I have LG v30 and i can't unlock bootloader, because windows refuses installing drivers so when i type "fastboot flash unlock unlock.bin" i just frozes and i can reboot the phone to normal state. Can somebody help or had simular problem? I live in Europe in Poland, and i have unlock.bin file
HubertoX said:
I have LG v30 and i can't unlock bootloader, because windows refuses installing drivers so when i type "fastboot flash unlock unlock.bin" i just frozes and i can reboot the phone to normal state. Can somebody help or had simular problem? I live in Europe in Poland, and i have unlock.bin file
Click to expand...
Click to collapse
There's a DOZEN trouble shooting tips list in the WTF Instructions. On that page, scroll down to Section 7.
Tell us which ones you have done? I know you haven't done all of them. When you read them you will understand how I know.
ChazzMatt said:
There's a DOZEN trouble shooting tips list in the WTF Instructions. On that page, scroll down to Section 7.
Tell us which ones you have done? I know you haven't done all of them. When you read them you will understand how I know.
Click to expand...
Click to collapse
THIS DOESN'T WORK so what I'm doing wrong? My phone is "unplugded" in windows and sending unlock is doing nothing idk where is my ADB folder
HubertoX said:
THIS DOESN'T WORK so what I'm doing wrong? My phone is "unplugded" in windows and sending unlock is doing nothing idk where is my ADB folder
Click to expand...
Click to collapse
One of the tips is to install another version of ADB.
One of the tips is to try another USB cable.
One of the tips is to try another USB port..
One of the tips is to try another computer.
That last one seems to work for most people as a last resort.
Since you won't read them in the Instructions, here are all the tips:
7: TROUBLE SHOOTING
MOST people have no problems. If you do, look through this list.
1) You can't flash the new-unlock.bin code.
Look at your current "About Phone". You want to confirm you're on Oreo with pre-July 2018 security patch firmware.
For any North American variant you Frankensteined, make sure you are on US998 Oreo pre-July 2018 firmware.
2) If you can't flash the new_unlock.bin code or you can't flash TWRP.
* Look in your ADB folder on your PC and confirm all known Windows file extensions enabled.
* Confirm all Windows hidden files and folders are visible.
If that doesn't help, try this:
3) Confirm USB debugging is on in Developer Options, and your PC has authorization for your phone.
4) Install another version of ADB. Install as close to the root of your hard drive as possible. X:\ADB where X is your hard drive.
5) Re-install LG mobile drivers.
6) Try another USB cable.
7) Installing this Windows driver found attached to this post. (Thanks @gazzacbr and @FZZF.)
8) Install Google USB driver. (Thanks @s0lidsneak.)
9) Try another USB port on your computer.
10) Reboot the computer.
11) Try another computer. (THIS seems to always solve the problem. Kudos if you find an an old Win7 PC.)
12) Master Reset (full reset of phone using hardware buttons). Phone will be reset anyway after bootloader unlock. Doing it prior may fix something preventing the command from working.
Nope this doesn't work
HubertoX said:
Nope this doesn't work
Click to expand...
Click to collapse
You are not doing it right. You aren't even following the troubleshooting tips.
I know you haven't tried other computers.
You said you don't even know where your ADB folder is?
So you aren't doing it right. It DOES work, but your have to follow instructions.
What variant do you have, what firmware are you even on?
ChazzMatt said:
You are not doing it right. You aren't even following the troubleshooting tips.
I know you haven't tried other computers.
Click to expand...
Click to collapse
My other pc is laptop with windows 10 that have more problems than my normal pc and i don't have any cables other than stock one
Ok now I can't install TWRP, bootloader unlocked
HubertoX said:
Ok now I can't install TWRP, bootloader unlocked
Click to expand...
Click to collapse
OK, you finally finished Section 5, unlocking bootloader. See, it does work.
Now you're on Section 6, installing TWRP and rooting. Make sure you're reading it on a web browser, not something like XDA app. The app truncates entire paragraphs of explanation.
Read the section thoroughly, follow the directions, read the troubleshooting tips again. Everyone else can do it, so there is something you are missing or doing differently than you should. Or something you're not doing, that you should.
What kind of error message are you getting?
ChazzMatt said:
OK, you finally finished Section 5, unlocking bootloader. See, it does work.
Now you're on Section 6, installing TWRP and rooting. Make sure you're reading it on a web browser, not something like XDA app. The app truncates entire paragraphs of explanation.
Read the section thoroughly, follow the directions, read the troubleshooting tips again. Everyone else can do it, so there is something you are missing or doing differently than you should. Or something you're not doing, that you should.
What kind of error message are you getting?
Click to expand...
Click to collapse
I have this thing:
C:\Users\hchrz\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
target didn't report max-download-size
sending 'recovery' (29808 KB)...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\Users\hchrz\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
target didn't report max-download-size
sending 'recovery' (29808 KB)...
Second time it's doing nothing, i lefted phone pluged to the pc for 5min and nothing. I have only unlocked bootloader
Now my phone is dead, some kind of bootloop and I can't go to fastboot
HubertoX said:
Now my phone is dead, some kind of bootloop and I can't go to fastboot
Click to expand...
Click to collapse
Try Master Reset (which is different from Factory Reset).
---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------
HubertoX said:
I have this thing:
C:\Users\hchrz\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
target didn't report max-download-size
sending 'recovery' (29808 KB)...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\Users\hchrz\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
target didn't report max-download-size
sending 'recovery' (29808 KB)...
Second time it's doing nothing, i lefted phone pluged to the pc for 5min and nothing. I have only unlocked bootloader
Click to expand...
Click to collapse
The max download size error is USB cable/USB port/ADB not communicating well.
Someone with a VERY similar screen name to yours had the exact same issue when trying to unlock bootloader.
Hughbert3200 said:
Hello I know this post is really old but i was trying to complete this today because i just got my old v30 out of storage. It started off as a h931 carrier locked from atnt. Tried rooting it downgrading google plus to do some spoofing on pokemon go. Well that didnt go to well since the phone has a locked bootloader and wont allow majisk.
So i saw this and said "Finally someone came out with something for an LG phone". Well anyways, I followed the post all the way down to looking at your screenshots to try and get the exact version (10d to 20a). And still my fastboot commands are locked. It gets stuck right after the i attempt to flash the new_unlock.bin, just says "Target didn't report max-download-size. Sending 'unlock' (1kb)......." I see tons of other people posting how they got theirs to work. But mine won't for some reason. Yes I am on US98820a and its not bootlooping at all, just no fastboot commands.
Thank you for your time and I love how at least someone gave LG some attention. Even if it was with a Huawei unlock code :laugh:
Click to expand...
Click to collapse
Well, you can also get the same error when trying to install TWRP. It's the SAME communication, where you are trying to install flash something via fastboot flash commands.
Something about your cable/port/ADB installation is not agreeing with your phone. Or missing drivers. You got the bootloader unlocked, now you just need to get TWRP installed -- then you will never need ADB/fastboot again.
This guy had problems with flashing TWRP:
https://forum.xda-developers.com/showpost.php?p=78331633&postcount=2391
Shonlinus said:
Excellent bro! But I want to know whether my firmware (us99820a) is early enough for This trick?
---------- Post added at 02:22 AM ---------- Previous post was at 02:04 AM ----------
1----D:\Downloads\platform-tools\platform-tools>fastboot flash recovery TWRP-3.2.1-joan-v0.1.img
target reported max download size of 536870912 bytes
sending 'recovery' (29808 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.016s
2----D:\Downloads\platform-tools\platform-tools>fastboot flash unlock unlock.bin
target didn't report max-download-size
sending 'unlock' (1 KB)...
3----FAILED (status read failed (Too many links))
finished. total time: 36.499s
I'm trying to unlock my US998 but ERRO info (see 2----),then I reboot and try to flash twrp and it seems that it can recognize my device,however it fails every time I try to flash unlock.bin ,and stuck in 'sending 'unlock' (1 KB)...' then if I unplug the phone ERRO info(3----) shows up ,someone plz give me some advice
Click to expand...
Click to collapse
Shonlinus said:
yeah! success after I change another cable!
now I am in twrp
Click to expand...
Click to collapse
He changed cables and it worked.
Sorry my phone can't go into fastboot mode and restart to facotry
HubertoX said:
Sorry my phone can't go into fastboot mode and restart to facotry
Click to expand...
Click to collapse
You don't need fastboot mode for Master Reset.
Most V30 don't even have fastboot capability.
ChazzMatt said:
You don't need fastboot mode for Master Reset.
Most V30 don't even have fastboot capability.
Click to expand...
Click to collapse
Dude I can't install TWRP but I'm in FASTBOOT
HubertoX said:
Dude I can't install TWRP but I'm in FASTBOOT
Click to expand...
Click to collapse
You said you couldn't get into fastboot mode...
HubertoX said:
Sorry my phone can't go into fastboot mode and restart to facotry
Click to expand...
Click to collapse
I'm confused where you're at.
But you either need another cable, another ADB version or another USB port.
This guy, today, used an older ADB:
Tinkerer_ said:
"adb" command returns "Android Debug Bridge version 1.0.32", "Revision eac51f2bb6a8-android".
The Android SDK Tools entry in WinXP "Add or Remove Programs" is 1.16 (Google). Not sure that matters.
Might be a good idea to test it with Windows later than XP before recommending it. (I have not.)
...
Click to expand...
Click to collapse
ChazzMatt said:
You said you couldn't get into fastboot mode...
Click to expand...
Click to collapse
I just dropped battery to 0% and I opened LGUP and i just did FIRMAWARE UDPATE from US to EU
HubertoX said:
I just dropped battery to 0% and I opened LGUP and i just did FIRMAWARE UDPATE from US to EU
Click to expand...
Click to collapse
EU isn't compatible with US variants. Why did you do that?
What variant did you start with?
Are you reading ANY of the Instructions in WTF and Frankenstein?
Sent via open market LG US998 V30/V30+
I tried EU and phone works, US not but so yeah, I'm doing Factory data reset
HubertoX said:
I tried EU and phone works, US not but so yeah
Click to expand...
Click to collapse
What variant did you start with? What was the phone when you bought it?
H930, H931, LS998, US998?
Related
Hi
deleted the following apps as it was nagging while restarting the phone.
SprintZone_SZ_2.5.15.apk
Sprint_InstallerNC_2.1.0.apk
SprintMobileWallet_1.5.apk
vtt-sprint_T.5.1.0.74.apk
I have a backup of these apps
now when I start the phone, it continuously shows "Contacting Network" then fails
then after a while it shows "Hands Free Activation"
Your activation could not be completed. Please try again later.
if I press "OK" it shows
Sorry!
The application SprintOmaDm (process com.motorola.android.sprintomadm) has stopped unexpectadly. Please try again
ROM details
45.4.13.MB855.Sprint.US
Androd 2.3.5
Baseban Ver N_01_29.10R
Kernel 2.6.32.29
Build No: 4.5.1A-1_SUN-254_13
the phone is rooted
please help
Did you try restoring the apps you deleted to see if that fixed it?
Sent from my MB855 using xda app-developers app
Shad0wguy said:
Did you try restoring the apps you deleted to see if that fixed it?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
can't access the home screen. it is constantly trying to connect to the network and will not go further.
it restarts the network search after it fails. loop.
problem got worse.
tried fastboot recovery and flashed cg59.smg boot
now the phone shows "Failed to boot 2
Starting RSD mode
please help
From where did you take that cg?
Cg59 is not recovery. How did you got such idea?
peetr_ said:
From where did you take that cg?
Cg59 is not recovery. How did you got such idea?
Click to expand...
Click to collapse
followed this thread.
http://forum.xda-developers.com/showthread.php?t=1573727
You probably mean this...
scottgl9 said:
Confirmed! I got rid of the aweful 2.3.5 electrify bootloader. Just did this:
[email protected]:~/Desktop/SMG_BP011UP$ fastboot flash boot CG59_0x00000130.smg
sending 'boot' (3294 KB)...
OKAY [ 0.206s]
writing 'boot'...
OKAY [ 0.734s]
finished. total time: 0.940s
Click to expand...
Click to collapse
That was last post from scottgl9...
And there is written fastboot flash boot, not recovery. And noone knows, where did he take that.
You need to take and try 2.3.5 recovery dump.
peetr_ said:
You probably mean this...
That was last post from scottgl9...
And there is written fastboot flash boot, not recovery. And noone knows, where did he take that.
You need to take and try 2.3.5 recovery dump.
Click to expand...
Click to collapse
looks like I may have to wait a long time if I am lucky! otherwise parts for sale! new phone just two weeks old from ebay India about $500 wasted.
You need to read all over here, download the dump and try flashing things with fastboot (in your case, just recovery), if you find a solution, you will help others too.
peetr_ said:
You need to read all over here, download the dump and try flashing things with fastboot (in your case, just recovery), if you find a solution, you will help others too.
Click to expand...
Click to collapse
thanks peetr
I am prepared to try any options available. but the thing is I have only two weeks familiarity with Android and this is my first Android phone.
hope I can get some help with flash mem dump using RSD
found a solution
its here
http://forum.xda-developers.com/showthread.php?t=1785561
portman said:
can't access the home screen. it is constantly trying to connect to the network and will not go further.
it restarts the network search after it fails. loop.
problem got worse.
tried fastboot recovery and flashed cg59.smg boot
now the phone shows "Failed to boot 2
Starting RSD mode
please help
Click to expand...
Click to collapse
i got past this error, you need to get a few files for the photon, one is an sbf (511 mb), another is the stock rom 2.3.5 which you will install through bootstrap, and third when you finally boot into the rom itself, another sbf through rsd and you're good to go. check the "revive the photon from grave" thread, it is all there
say thanks, it helps motivate :angel:
I take no responsibility for any damages incurred to your phone
Please use this script only when necessary
Here is a little script I put together to fastboot L9s with ability to flash/restore ics xloader and uboot (p760, p765, p768, p769) jb (p760)
*I've only tested it on Win 7, but it should work on Vista , not sure about XP and 8
Very useful post about installing the drivers
*Some phones may need a different timing, 4 seconds won't work, worth to try between 0 to 4s and see what works best
Original thread about fastboot
http://forum.xda-developers.com/showthread.php?t=2119090
It's based on wpark - [DEV][Bootloader] u-boot / omap4boot for P920/P720/P940 and its variant
update: file updated, mylk Thanks for catching the mistake!
update2: added p769 20f
Thanks, I'll try this out once I'm home, maybe my phone will finally let me fastboot. Whenever I've tried before, it just normally reboots, doesn't switch to fastboot mode.
Sent from my LG-P768
i think there is some errot in your start.bat .
IF /I '%INPUT%'=='6' GOTO Selection5 ( i think it should be Selection6 , right ? )
and here is my p1.bin an p2.bin . mine is P765 JB (HongKong V20D) . hope you can put this into your file . and may help others .
View attachment 1986726
Tried the method in the link in the 1st post, didn't work. Tried this, still nothing. I get the same "unexpected 2ndstage response" error.
is there somebody who has tried fastboot ?
how is the screen like of the phone ?
is it just a black screen ?
and why the cmd just go to the folder of "yours" then i cant find anything in this folder .
sorry for my nood question ......
cris7i said:
Tried the method in the link in the 1st post, didn't work. Tried this, still nothing. I get the same "unexpected 2ndstage response" error.
Click to expand...
Click to collapse
Both work the same under the hood. Perhaps you've wrong drivers if you get same error msg.
mylk said:
is there somebody who has tried fastboot ?
how is the screen like of the phone ?
is it just a black screen ?
and why the cmd just go to the folder of "yours" then i cant find anything in this folder .
sorry for my nood question ......
Click to expand...
Click to collapse
#1 is just a general fastboot, you can put whatever (boot.img, recovery.img, etc) you want to flash via fastboot in "yours" folder - type: fastboot devices and you'll see if your phone is recognized
and the rest is mainly for recovery, ics xloaders and uboots work nicely with offline flashing method also several people mistakenly soft bricked their phones with omap4boot by flashing prada files which can't happen with this tool
For me general fastboot works on ArchLinux. But I only put recovery with it...
Rixx666 said:
For me general fastboot works on ArchLinux. But I only put recovery with it...
Click to expand...
Click to collapse
of course if you have functional rom and unlocked bootloader you don't need it
Hi there, its been a while since I tried fastboot again, but I have good news. Fastboot worked on my P768 using this method, I selected option 1. Then I was able to send recovery to my phone and then root the phone using a flashable SuperSU zip! 'adb reboot recovery' takes me straight into CWM!
I have some questions though.
Is fastboot permanently on the phone like it is on the P760 now? or do I have to use this program each time to send fastboot commands?
Does this mean that I could potentially flash a custom rom to my phone now? I know all the custom roms out there are not for the P768, so I will get camera problems. But is this the missing piece of the puzzle for custom rom development/testing?
Thank you lelus for this great tool!
donk165 said:
Hi there, its been a while since I tried fastboot again, but I have good news. Fastboot worked on my P768 using this method, I selected option 1. Then I was able to send recovery to my phone and then root the phone using a flashable SuperSU zip! 'adb reboot recovery' takes me straight into CWM!
I have some questions though.
Is fastboot permanently on the phone like it is on the P760 now? or do I have to use this program each time to send fastboot commands?
Click to expand...
Click to collapse
Fastboot is definitely there but something doesn't get passed along during adb reboot bootloader or oem-unlock and phone just reboots instead of booting to fastboot.
Does this mean that I could potentially flash a custom rom to my phone now? I know all the custom roms out there are not for the P768, so I will get camera problems. But is this the missing piece of the puzzle for custom rom development/testing?
Click to expand...
Click to collapse
I'm pretty sure* you can use Android Kitchen to replace these files in latest Cyanogenmod zip with ones from p768 jb and have camera working.
*i might be wrong
Lelus said:
Fastboot is definitely there but something doesn't get passed along during adb reboot bootloader or oem-unlock and phone just reboots instead of booting to fastboot.
I'm pretty sure* you can use Android Kitchen to replace these files in latest Cyanogenmod zip with ones from p768 jb and have camera working.
*i might be wrong
Click to expand...
Click to collapse
great, keep it up @donk165
Thanks. When I find the time. I'm going to make a guide for unlocking the boot loader, pushing CWM with fastboot and rooting.
I'm not confident in building CM, but I did see another user who was willing to try but was stuck with a locked boot loader. Hopefully together we can get the ball rolling for P768 development.
Sent from my LG-P768 using xda app-developers app
donk165 said:
Thanks. When I find the time. I'm going to make a guide for unlocking the boot loader, pushing CWM with fastboot and rooting.
I'm not confident in building CWM, but I did see another user who was willing to try but was stuck with a locked boot loader. Hopefully together we can get the ball rolling for P768 development.
Sent from my LG-P768 using xda app-developers app
Click to expand...
Click to collapse
i think we need help from devs to port camera from official p760 cm to p768 maybe @markolino631 can do it for us, seen we had unlocked bootloader and able to push cwm using fastboot.
I got a P769 from a friend and it is total dead,black screen, no SW update or hard reset key combinations works, only can fastboot and shows a mirrored LG logo , on top right it says V0.5, but unable to flash x-loader, u-boot or recovery, always show the error "remote partition does not exists", i tried to erase the partitions with fastboot but still the error is same. does somebody experienced the same? they call this phone un-brickable
AttiqAamir said:
I got a P769 from a friend and it is total dead,black screen, no SW update or hard reset key combinations works, only can fastboot and shows a mirrored LG logo , on top right it says V0.5, but unable to flash x-loader, u-boot or recovery, always show the error "remote partition does not exists", i tried to erase the partitions with fastboot but still the error is same. does somebody experienced the same? they call this phone un-brickable
Click to expand...
Click to collapse
My guess is corrupted nand or partition table.
What did your friend do to the phone?
Well I don't know, he just sent me that it is not booting. Is there any tool / way to initialize the nand?
AttiqAamir said:
Well I don't know, he just sent me that it is not booting. Is there any tool / way to initialize the nand?
Click to expand...
Click to collapse
Not that I know of
Hey I know this has been a long time to reply but since nothing is working try this command in fastboot
fastboot oem format
I found this information here
http://www.omappedia.com/wiki/Android_Fastboot
The website has a lot of information
Sent from my LG-P769 using xda app-developers app
kuma82 said:
Hey I know this has been a long time to reply but since nothing is working try this command in fastboot
fastboot oem format
I found this information here
http://www.omappedia.com/wiki/Android_Fastboot
The website has a lot of information
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Just heads up, the fastboot files are from lg prada p940 which has somewhat different partition setup but it's definitely worth trying as a last resort if nothing else works.
Thank you for your help, i tried as you advised but it failed it replied as
FAILED (remote failure)
finished. total time: 0.001s
So, the other night my Rezound slipped off a shelf and into the toilet. I pulled it out immediately, popped open the case and used a blow dryer on it, then stuck it in a bag of rice. The next day I stuck the battery in and it seemed to be working alright. Then I went to respond to a snapchat and found that the camera was not working. I thought maybe a simple restart might help, but the phone never restarted. I stuck it back in the bag of rice, thinking maybe their was still some moisture that could be pulled out. Today, after roughly 48 hours in the rice, I put the battery in, and it goes into the bootloop.
I pulled the SIM, tried going into recovery, factory reset, wipe cache, etc. Everything I can find on any forum does not work. I found a couple different PH89IMG.zip files, but after the bootloader analyzes them, it says that it can't do anything because they're older versions that what is on the device, which is "4.05.605.14 710RD" according to my wife's phone. I also downloaded the RUU, but the device has to be powered on for that to work, and it won't go past the white screen with green htc logo.
I would really love to resolve this without doing a factory reset, because there are a few things saved on the device itself that I can't really replace. Does anybody have any ideas for anything else I could try? Including maybe having the PH89IMG.zip file for the stock version of Android...
Is there a way that I could extract the PH89IMG.zip file from my wife's rezound, or utilize her phone in any way to repair my own?
ggoodman1022 said:
Is there a way that I could extract the PH89IMG.zip file from my wife's rezound, or utilize her phone in any way to repair my own?
Click to expand...
Click to collapse
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
mjones73 said:
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
Click to expand...
Click to collapse
Thanks. I'll give that a shot. It was working the next day, but then stopped after a restart. And it was only in the water for maybe 2 seconds, max. My wife's phone fell in a pool before, and got pulled out about a minute later, then worked after about 48 hours in rice.
mjones73 said:
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
Click to expand...
Click to collapse
So editing the version listed in the .txt file made it so it didn't hang up on loading the file, but then it just refreshed the main bootloader screen. When I select fastboot, or go to restart the phone, it's still hung up in the bootloop :crying:
I'm not up for an upgrade until November 1, so I've been using my OG Incredible...
ggoodman1022 said:
So editing the version listed in the .txt file made it so it didn't hang up on loading the file, but then it just refreshed the main bootloader screen. When I select fastboot, or go to restart the phone, it's still hung up in the bootloop :crying:
I'm not up for an upgrade until November 1, so I've been using my OG Incredible...
Click to expand...
Click to collapse
Can you get to recovery? I see you have no recovery. You can try to fastboot a recovery.img, I am sorry but sounds like you screwed up your system, you will be lucky if it accepts a recovery. I deal with lots of broken phones in the business I am in and sorry to say once they are water damaged they 90 percent of the time they end up useless. If you need help with fastboot I will help.
jhr5474 said:
Can you get to recovery? I see you have no recovery. You can try to fastboot a recovery.img, I am sorry but sounds like you screwed up your system, you will be lucky if it accepts a recovery. I deal with lots of broken phones in the business I am in and sorry to say once they are water damaged they 90 percent of the time they end up useless. If you need help with fastboot I will help.
Click to expand...
Click to collapse
How does one go about trying to "fastboot a recovery.img?" I'm very limited in my knowledge on these things...
ggoodman1022 said:
How does one go about trying to "fastboot a recovery.img?" I'm very limited in my knowledge on these things...
Click to expand...
Click to collapse
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
kcipopnevets said:
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
Click to expand...
Click to collapse
I'll give this a shot next time I have access to a windows machine... Some time in the next few days or so
ggoodman1022 said:
I'll give this a shot next time I have access to a windows machine... Some time in the next few days or so
Click to expand...
Click to collapse
This can be done on a Mac or Linux box as well, ADB is available for both, just substitute the appropriate filenames or commands for each OS.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
This can be done on a Mac or Linux box as well, ADB is available for both, just substitute the appropriate filenames or commands for each OS.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Sweet!! I'll look into it after I finish my homework
kcipopnevets said:
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
Click to expand...
Click to collapse
So I finally got around to doing this, after buying a replacement phone off a guy on Craigslist, but I would still like to try and get this phone back up and running... I downloaded all the files and installed adb, etc. When I try to run the command, "fastboot flash recovery TWRP_2.6.3.0_Vigor_PH98IMG.zip" I get the following in the terminal:
sending 'recovery' (6323 KB)...
OKAY [ 1.464s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.780s
Any other ideas??
ggoodman1022 said:
So I finally got around to doing this, after buying a replacement phone off a guy on Craigslist, but I would still like to try and get this phone back up and running... I downloaded all the files and installed adb, etc. When I try to run the command, "fastboot flash recovery TWRP_2.6.3.0_Vigor_PH98IMG.zip" I get the following in the terminal:
sending 'recovery' (6323 KB)...
OKAY [ 1.464s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.780s
Any other ideas??
Click to expand...
Click to collapse
You don't flash the zip, extract the file and flash the recovery.img file.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
You don't flash the zip, extract the file and flash the recovery.img file.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
got it. thanks! it said the recovery was successful, but it still gets stuck in the bootloop :crying:
It may be time to admit what I feared from the moment it hit the water...
ggoodman1022 said:
got it. thanks! it said the recovery was successful, but it still gets stuck in the bootloop :crying:
It may be time to admit what I feared from the moment it hit the water...
Click to expand...
Click to collapse
Wipe, flash a ROM, and manually flash boot image... Other than that, could be toast.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
Wipe, flash a ROM, and manually flash boot image... Other than that, could be toast.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Can it be a stock ROM, or would it have to be something like CyanogenMod?
ggoodman1022 said:
Can it be a stock ROM, or would it have to be something like CyanogenMod?
Click to expand...
Click to collapse
I think its irrelevant at this point... Personally, I would use EclipticRez v9 or Tachyon as they are both rock solid ROMs. EclipticRez includes an Aroma installer script, so it might be a little easier (select S-ON and Lunar kernel).
Sent from my Nexus 4 using Tapatalk
acejavelin said:
I think its irrelevant at this point... Personally, I would use EclipticRez v9 or Tachyon as they are both rock solid ROMs. EclipticRez includes an Aroma installer script, so it might be a little easier (select S-ON and Lunar kernel).
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I actually found this thread earlier - http://forum.xda-developers.com/showthread.php?t=2632629 and followed the instructions, it was giving me some trouble around step 10 and kept going back into the bootloop. Then I tried it for probably the 5th time and it finally worked!! So the phone is back to full function now. I've been out of the house for a few hours, but it worked before your last reply literally right before I walked out the door.
Thank you SOOOO SOOOO SOOOOO much for the advice both on this thread and on that one I mentioned above (since it was also your instructions there)
ggoodman1022 said:
I actually found this thread earlier - http://forum.xda-developers.com/showthread.php?t=2632629 and followed the instructions, it was giving me some trouble around step 10 and kept going back into the bootloop. Then I tried it for probably the 5th time and it finally worked!! So the phone is back to full function now. I've been out of the house for a few hours, but it worked before your last reply literally right before I walked out the door.
Thank you SOOOO SOOOO SOOOOO much for the advice both on this thread and on that one I mentioned above (since it was also your instructions there)
Click to expand...
Click to collapse
No prob... glad you got it working. Water damage is weird, hopefully it sticks!
acejavelin said:
No prob... glad you got it working. Water damage is weird, hopefully it sticks!
Click to expand...
Click to collapse
The [semi] good news is that I found one on Craigslist (same phone because I really like it) for just $60 a couple days after I got fed up with using the OG Incredible. And the guy had 2 extra batteries, a case, and ghost armor on the screen as well. So now I have the original Rezound and the spare.
Hi there guys,
I'm new to the forum so apologies if this has been posted in the wrong place.
So I was directed to this forum to attempt to solve a different problem but in my hast, I have caused an even bigger problem!
So initially I was having problems with the new Android Wear update with regards to rooting, so I wanted to find a way to roll the software back or restore the device to stock.
I came across this post http://forum.xda-developers.com/g-watch/development/tool-lg-g-watch-return-to-stock-t3158349 and attempt to do as advised, but half way through the process, the program froze. I then tried to reset the watch from the button at the back, but the watch is now stuck on the fastboot menu. I used ADB to see if I could still connect to the device but no devices can be found.
I have checked the device manager and can see the device as "Android Bootloader Interface" but can't seem to get it past the fastboot menu.
Any help would be much appreciated.
Thanks in advance.
just do it again, as long you can get fastboot, you are safe.
Jaocagomez said:
just do it again, as long you can get fastboot, you are safe.
Click to expand...
Click to collapse
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Montezz1 said:
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Click to expand...
Click to collapse
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Xmaster24 said:
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Click to expand...
Click to collapse
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Montezz1 said:
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Click to expand...
Click to collapse
Check the bootloader lock status and report back
Xmaster24 said:
Check the bootloader lock status and report back
Click to expand...
Click to collapse
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Montezz1 said:
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Click to expand...
Click to collapse
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Xmaster24 said:
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Click to expand...
Click to collapse
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Montezz1 said:
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Click to expand...
Click to collapse
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Xmaster24 said:
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Click to expand...
Click to collapse
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Montezz1 said:
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Click to expand...
Click to collapse
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Xmaster24 said:
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Click to expand...
Click to collapse
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Montezz1 said:
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Click to expand...
Click to collapse
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Xmaster24 said:
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Click to expand...
Click to collapse
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Montezz1 said:
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Click to expand...
Click to collapse
This device I just want to know if you ever actually successfully flashed anything to this device
Xmaster24 said:
This device I just want to know if you ever actually successfully flashed anything to this device
Click to expand...
Click to collapse
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Montezz1 said:
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Click to expand...
Click to collapse
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Montezz1 said:
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Click to expand...
Click to collapse
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Xmaster24 said:
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Click to expand...
Click to collapse
I do not believe it...
After all of this, it was the drivers...
I don't get it though!! I tried to reinstall them before and nothing changed!
It's only when I completely deleted them and reinstalled that it worked.
Honestly dude, thank you so much for your help and patience. My watch is now working and paired with my phone.
I'm waiting for it to sync but hopefully I will be able to run ADB and all will be well again
Thanks you so much again.
Hello there, I have a rooted LG V30 that I got about a few months ago.
Earlier today I went to open Magisk Manager for the first time since I rooted and it told me I needed to update Magisk Manager.
So I did.
When it relaunched itself, it crashed and continued to crash.
Now I can no longer open the Magisk Manger.
Not only can I not open the Magisk Manager, but it would seem I'm unable to give any apps root privileges as of now.
I've tried reinstalling twrp using ADB but I can't seem to get it to work. It keeps freezing on me during the 3rd recovery question or fastboot can't find my device.
If anyone can tell me what has happened that would be nice.
If you need logs, please let me know how to get them and I will update the post with them.
~ Thanks, bditt.
Use magisk uninstalled to uninstall and reinstall. That probably will work.
zrzhu said:
Use magisk uninstalled to uninstall and reinstall. That probably will work.
Click to expand...
Click to collapse
Hi there, I know this is silly, but would you mind explaining how to use the magisk unistall file?
I get it as a zip and can't seem to run it like an APK.
From what I understand, I need to use TWRP to run it.
Sadly, I can't seem to boot up into TWRP.
bditt said:
Hi there, I know this is silly, but would you mind explaining how to use the magisk unistall file?
I get it as a zip and can't seem to run it like an APK.
From what I understand, I need to use TWRP to run it.
Sadly, I can't seem to boot up into TWRP.
Click to expand...
Click to collapse
Yes, you flash it in TWRP.
Boot to TWRP the way you do in WTF instructions, with fastboot flash commands.
ChazzMatt said:
Yes, you flash it in TWRP.
Boot to TWRP the way you do in WTF instructions, with fastboot flash commands.
Click to expand...
Click to collapse
When I try, I get to the asking for a reset questions, and I press yes, but on the third yes screen, it freezes.
Then it just reboots normally.
bditt said:
When I try, I get to the asking for a reset questions, and I press yes, but on the third yes screen, it freezes.
Then it just reboots normally.
Click to expand...
Click to collapse
Actually read my reply?
Nothing in my post has anything to do with what you just posted. I said to use fastboot flash commands, just like in WTF INSTRUCTIONS.
I hate people who don't bother to read.
I will never ever suggest hardware button dance. Nowhere in WTF INSTRUCTIONS do I say to use hardware button dance. The exact opposite.
So read my answer again and do that.
____
If you've managed to wipe out TWRP using YOUR method, then you need to follow WTF Section 6 to re-install it.
Still, in either instance you'll be using fastboot flash commands to boot TWRP.
ChazzMatt said:
Actually read my reply?
Nothing in my post has anything to do with what you just posted. I said to use fastboot flash commands, just like in WTF INSTRUCTIONS.
I hate people who don't bother to read.
I will never[)b] ever suggest hardware button dance. Nowhere in WTF INSTRUCTIONS do I say to use hardware button dance. The exact opposite.
So read my answer again and do that.
____
If you've managed to wipe out TWRP using YOUR method, then you need to follow WTF Section 6 to re-install it.
Still, in either instance you'll be using fastboot flash commands to boot TWRP.
Click to expand...
Click to collapse
Okay, when trying to flash TWRP I get an error:
"sending 'recovery' (22588 KB)...
FAILED (remote: Requested download size is more than max allowed)"
When I tried to boot into twrp I get an error:
"downloading 'boot.img'...
FAILED (command write failed (Too many links))"
Any clues?
I redownloaded the files and still the same errors.
bditt said:
Okay, when trying to flash TWRP I get an error:
"sending 'recovery' (22588 KB)...
FAILED (remote: Requested download size is more than max allowed)"
When I tried to boot into twrp I get an error:
"downloading 'boot.img'...
FAILED (command write failed (Too many links))"
Any clues?
I redownloaded the files and still the same errors.
Click to expand...
Click to collapse
See the WTF Section 7 Troubleshooting Tips. I know you've already unlocked your bootloader, but they also address ADB/fastboot flash command issues which you are having. The "too many links" problem is definitely ADB not communicating with your device.
You need to reinstall Google/Windows/LG mobile drivers, try different ADB installation, different USB cable, different port, different computer.
See Section 7 of WTF for more advice.
ChazzMatt said:
See the WTF Section 7 Troubleshooting Tips. I know you've already unlocked your bootloader, but they also address ADB/fastboot flash command issues which you are having. The "too many links" problem is definitely ADB not communicating with your device.
You need to reinstall Google/Windows/LG mobile drivers, try different ADB installation, different USB cable, different port, different computer.
See Section 7 of WTF for more advice.
Click to expand...
Click to collapse
After reading the thread, I tried 3 different cables, all the different ports on my PC, 2 different computers, all the ADBs linked in your thread, updated my drivers on both PCs, and I get this error each time now when running .\fastboot.exe flash recovery .\TWRP.img :
Sending 'recovery' (30324 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
bditt said:
After reading the thread, I tried 3 different cables, all the different ports on my PC, 2 different computers, all the ADBs linked in your thread, updated my drivers on both PCs, and I get this error each time now when running .\fastboot.exe flash recovery .\TWRP.img :
Sending 'recovery' (30324 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
Please type the exact fastboot command you are entering into the box?
I hope it's not what you have typed above...
See screenshot of what it should be.
ChazzMatt said:
Please type the exact fastboot command you are entering into the box?
I hope it's not what you have typed above...
See screenshot of what it should be.
Click to expand...
Click to collapse
Hi, sorry, was away from my computer for a little bit.
This is what I am doing.
bditt said:
Hi, sorry, was away from my computer for a little bit.
This is what I am doing.
Click to expand...
Click to collapse
You're not using some sort of virtual Windows environment, are you?
If not, then try different ports, different cables, different ADB installations, different computer.
Also try lower case f on fastboot. Who knows, it might make a difference.
V30 has a difficult relationship with ADB. If you scroll up, one guy had to try three different USB cables.
Good news is once bootloader unlocked and TWRP installed, you won't need fastboot again.
ChazzMatt said:
You're not using some sort of virtual Windows environment, are you?
If not, then try different ports, different cables, different ADB installations, different computer.
Also try lower case f on fastboot. Who knows, it might make a difference.
V30 has a difficult relationship with ADB. If you scroll up, one guy had to try three different USB cables.
Good news is once bootloader unlocked and TWRP installed, you won't need fastboot again.
Click to expand...
Click to collapse
Okay, no, not on a VM or anything.
Using 4 different cables, all the ADB installations linked, different ports, and different computers. Still no luck. Not looking good for me right now. ;(
bditt said:
Okay, no, not on a VM or anything.
Using 4 different cables, all the ADB installations linked, different ports, and different computers. Still no luck. Not looking good for me right now. ;(
Click to expand...
Click to collapse
Don't remember if we covered this...
What happens when you use the commands: fastboot boot TWRP.img ?
That should boot TWRP temporarily on your phone from your PC.
Then in "temporary" TWRP, you choose to boot to recovery in the Boot section of TWRP (this would only work if you still have TWRP installed) OR you can try to do some actions. Perhaps even run the uninstaller for Magisk and re-install Magisk?
_________
Next topic...
Which TWRP are you trying to reinstall? Stable 3.2.3.7 from the WTF thread? or another? Sometimes people get hold of some other older TWRP. Just want to make sure you aren't using anything older than stable 3.2 3.7.
Similarly there is a TWRP beta out right now. I don't normally recommend betas, but you could try to install it, just to see
https://www.androidfilehost.com/?fid=4349826312261670996
ChazzMatt said:
Don't remember if we covered this...
What happens when you use the commands: fastboot boot TWRP.img ?
That should boot TWRP temporarily on your phone from your PC.
Then in "temporary" TWRP, you choose to boot to recovery in the Boot section of TWRP (this would only work if you still have TWRP installed) OR you can try to do some actions. Perhaps even run the uninstaller for Magisk and re-install Magisk?
_________
Next topic...
Which TWRP are you trying to reinstall? Stable 3.2.3.7 from the WTF thread? or another? Sometimes people get hold of some other older TWRP. Just want to make sure you aren't using anything older than stable 3.2 3.7.
Similarly there is a TWRP beta out right now. I don't normally recommend betas, but you could try to install it, just to see
https://www.androidfilehost.com/?fid=4349826312261670996
Click to expand...
Click to collapse
After trying 5 different computers, 6 cables, a bunch of different ADB's, and so many other things, I was able to get this to work.
Thanks for so much info and help.
Really appreciate it.
To be a little more specific on what happened:
After a bunch of tries on many different computers. I went on my mothers laptop.
Which is on Windows 10 version 1903.
I went and installed all the drivers on the laptop.
Tried a while.
Gave up for the day.
Got on today and kept trying.
First try and I was able to get it working.
Uninstalled and reinstalled magisk and everything.
Root works fine now.
Once again, thanks so much for the help.
I think the laptop restart is what actually fixed it. I realized I forgot to restart the laptop after installing the drivers while I was laying down for sleep last night.
bditt said:
After trying 5 different computers, 6 cables, a bunch of different ADB's, and so many other things, I was able to get this to work.
Thanks for so much info and help.
Really appreciate it.
Click to expand...
Click to collapse
Glad you got it working.
Different computer usually fixes it, just took you SEVERAL different computers!