Greetings all, I have come to ask for advice on how to debrick my lg v60 version V600TM20n. First, how I ended up in this situation.
To begin, I followed this guide to unlock bootloader and root my phone then I followed this guide in an attempt to install a custom rom however, i did not get too far.
I tried to remove vbmeta verity as per the requirements of the form and in doing so input this line into my bootloader fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img with the file provided by this form I think this is where the issue I have is comming from but moving on.
I then attempted to download lineage os following the guide but it did not work and I was fed up by this point to I began the process of reverting everything I did. I downloaded SuperSu to deroot my device. After derooting my device I went to the bootloader and typed in fastboot oem lock, locking my device and dooming me.
In my attempts to escape from the hell I am currently in I downloaded LGUP v1.16.03 and v1.14 (I tried them both deleting the previous one before installing the new one) yet each time I was stuck with the this error code Error Code = 0x2000, Invalid command response when the progress bar reach 9%.
The dll i used is version 0.0.3.23 and the one provided by LGUP v.1.16.03, and the firmware I attempted to download was V600TM20n_02_TMO_US_OP_0111.kdz on LGUP it says V600TM20n oh and also I did try UPPERCUT, no resuts
Currently on my phone's download mode screen at the bottom in red it says Modified / E / L / RO / id : 3(NA2_US) I have also tried LGUP Cmd but same results
I have tried LG bridge but it says connecting and then no device found :/
I wish i could say i tried lg flash tool but i have no idea on how to use it
Possibly another big mistake (idk what im doin) I used the QFIL and restore the abl_a and abl_b to their original versions after locking the bootloader.
Please tell me if there is anything else I can do or if I now own a $300 brick. If I do have a $300 brick is there any value I can get from it to fund my walmart flip phone that I will have to buy?
unregisteredhypercam said:
Greetings all, I have come to ask for advice on how to debrick my lg v60 version V600TM20n. First, how I ended up in this situation.
To begin, I followed this guide to unlock bootloader and root my phone then I followed this guide in an attempt to install a custom rom however, i did not get too far.
I tried to remove vbmeta verity as per the requirements of the form and in doing so input this line into my bootloader fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img with the file provided by this form I think this is where the issue I have is comming from but moving on.
I then attempted to download lineage os following the guide but it did not work and I was fed up by this point to I began the process of reverting everything I did. I downloaded SuperSu to deroot my device. After derooting my device I went to the bootloader and typed in fastboot oem lock, locking my device and dooming me.
In my attempts to escape from the hell I am currently in I downloaded LGUP v1.16.03 and v1.14 (I tried them both deleting the previous one before installing the new one) yet each time I was stuck with the this error code Error Code = 0x2000, Invalid command response when the progress bar reach 9%.
The dll i used is version 0.0.3.23 and the one provided by LGUP v.1.16.03, and the firmware I attempted to download was V600TM20n_02_TMO_US_OP_0111.kdz on LGUP it says V600TM20n oh and also I did try UPPERCUT, no resuts
Currently on my phone's download mode screen at the bottom in red it says Modified / E / L / RO / id : 3(NA2_US) I have also tried LGUP Cmd but same results
I have tried LG bridge but it says connecting and then no device found :/
I wish i could say i tried lg flash tool but i have no idea on how to use it
Possibly another big mistake (idk what im doin) I used the QFIL and restore the abl_a and abl_b to their original versions after locking the bootloader.
Please tell me if there is anything else I can do or if I now own a $300 brick. If I do have a $300 brick is there any value I can get from it to fund my walmart flip phone that I will have to buy?
Click to expand...
Click to collapse
Here,try this copy.Make sure you delete all previous versions of LGUP.
Related
I was recently given an LG Optimus L9 P769BK and decided to try and unlock the bootloader and root it. Most of the guides (such as: http://forum.xda-developers.com/showthread.php?t=2584997) suggest flashing to V10G_00 first before flashing to the EU V20B_00. I was able to flash to V10G (from V20H that was already on the phone using "LG Flash Tool 2014") but now, no matter what tool I use, I am unable to get ANY ROM to flash to the phone.
Methods/Tools used and the results:
1)http://forum.xda-developers.com/showthread.php?t=2085344
1a)Result: The software that is launched in Step 10 crashes before doing any updating
2)http://forum.xda-developers.com/optimus-l9/general/p765-unbrick-using-lg-flash-tool-2014-t2950433
2a) Using CDMA + Diag or Emergency: Goes to 10% of SW Update then fails with an error saying to remove the battery and try again. Doing this does not resolve the problem
2b) Using 3GQCT + Diag or Emergency: Can not connect to phone. Reseating the connection and power cycling the phone does not resolve this.
3) http://forum.xda-developers.com/showthread.php?t=2748384
3a)Using the LGP769_20121004_LGFLASHv1350.dll and a bin from V20B_00 it freezes around 570 seconds with a write error. The phone no longer boots outside of SW Update Mode.
The phone will now only boot into SW Update mode.
System:
OS: Windows 8.1 64bit
Drivers: LGUnitedMobileDriver_S52MAN314AP22_ML_WHQL_Ver_3.14.1
Any thoughts on what to do next?
UPDATE: The LG Flash Tool mentioned in 3) no longer sees the phone. After following the steps mentioned in the guide again
UPDATE2: Reinstalled the drivers. Method 1) still crashes, 2) same results, 3) still not "seeing" the phone when connected.
UPDATE3: (using Win 7 machine). Method 2) gives an odd "Can not connect to server error" when tried. Method 3) gives a write error on "Failed to Write OMAP" (ill get the exact line in a minute)
UPDATE4: Ignoring the error (aka NOT clicking the box) from Method 2) allowed the phone to flash with no problem
Only the very first v10a had an unlockable bootloader. And the first couple of v20ies or all of them. I unlocked and rooted with v20c, later versions could have locked Bls.
My phone actually has an encrypted bootloader so no ROM will work
I have no soldering skills so I ordered a 910k cable and will do the unlock with it.
Dear Esteemed XDA members,
I have spent literally days of testing and researching to try and unbrick my phone. Friends and family have seen my obsession with trying to fix this, some even offering to buy me a new phone!!!! But this ain't about money - this is about having control of my damn device!!! I'm usually pretty good with trying to solve this kind of stuff, but this time I'm truly stumped (and desperate, and obsessed!). I have come to the conclusion that it's directly related to ARM Trusted Firmware. Here are the details of my "journey" to date... please read it, and if you know how to fix it, please share!!! then I can get my life back!!!! Before I go any further, I am certain that my problem was initially triggered by doing an official update on a rooted phone. So to avoid experiencing the same problem I'm about to describe, it's best to unroot and relock your device before loading new official firmware.
I have a Huawei Honor 4x (Che2-UL00, with Kirin 620 chipset) with an unlocked bootloader. Recently, I tried to manually upgrade from Kitkat (emui3.0) to Lollipop (emui3.1), using the official update.app from huawei's website (image was good - I checked the hash). To load the update.app, I used the official huawei recovery. The progress bar went to roughly 90% and then hung. Upon restarting my phone, it went into rescue mode with the following error: Func NO : 15 (bl31 image) Error NO : 1 (security verify failed).
Interestingly, I looked closely at the fastboot.img files for kitkat Vs lollipop (I got the image files by using HuaweiUpdateExtractor). I noticed that only the lollipop fastboot image contains this error message text. Also, bl31 is related to ARM trusted firmware, for more info search for BL31 (Secure Monitor) on google, or see bl31_main.c in the Trusted Firmware source code. So it seems that the lollipop image is using the full ARM trusted firmware, an extra layer of security which is preventing the (unlocked) bootloader from allowing me to load into recovery. I think this is the core problem, and I think there is a way to solve it but I just don't have a deep enough understanding to get there. Below I'll explain each step I went though and provide some additional diagnostic info:
1. First step was to access recovery mode (Vol UP + power). This failed and resulted in same bl31 error message.
2. Second step was to try and update again using the three-button force update (Vol Up + Vol Down + Power). It vibrates once after a few seconds, and freezes with the logo screen with the red light flashing. As an experiment, I tried this without the SDCARD and noticed it vibrated almost instantly, which suggests that it does try to load something from the SDCARD when inserted. I didn't get any further in this mode.
3. Final step I tried was to load into fastboot (Vol Down + Power). This worked and I got into a special "Rescue&Fastboot" mode. First thing I tried was to manually downgrade to kitkat by flashing the kitkat images using the fastboot flash command. The images boot.img, system.img, recovery.img flashed successfully. cust.img simply failed. I desperately wanted to flash the kitkat fastboot.img which doesn't contain the trusted firmware bl31 image stuff, but fastboot replied: FAILED (remote: Command not allowed). In fact, many of the fastboot commands fail with this same error message, even though there is the "PHONE unlocked" writing in red on my phone screen. With the limited command set available (even fastboot oem device-info is not allowed!), here is the diagnostic info I was able to get:
a) fastboot oem check-rootinfo
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1452356543
I think this change from RISK to SAFE is the core of my problem. the change_time is from several days ago when I attempted to update. I think it reflects the trusted firmware state (I'm guessing here, as I can't find documentation for these commands).
b) fastboot oem backdoor info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
I think that FB LockState: LOCKED means that fastboot is locked (guessing again, can't find documentation!), which explains why many of the commands fail.
c) fastboot oem check-image
(bootloader) secure image verify successfully
I think this checks the recovery image, because when I flash a different recovery, this signature check fails
d) fastboot getvar rescue_phoneinfo
rescue_phoneinfo: Che2-UL00 V100R001CHNC00B365
This appears to be the ROM version at the time of purchase.
e) fastboot oem get-build-number
(bootloader): Che2-UL00 V100R001CHNC00B384
This actually corresponds to the build number of kitkat I was using just before the failed upgrade to lollipop.
f) fastboot oem relock mycode
FAILED (remote: root type not allowed).
I tried this just to see if it wold relock. I'm not sure what the error means, but I do not that this command failed with signature verify fail if i change the recovery image.
Here are the questions I want to ask:
1. Can I force the device to flash a new image? I can't get into recovery or have full access to fastboot commands due to the trusted firmware stuff. And as I mentioned earlier the three button trick fails with a freeze at the logo screen. It appears that I need to do this using a means other than fastboot. The only interface I have is Android Sooner ADB Interface. adb devices renders nothing. Only fastboot finds a device.
2. Can I somehow make the "security verify check" pass so that I don't get that bl31 error? I'm not sure exactly which images this bl31 thing is trying to verify! Perhaps some combination of images from the new lollipop stuff I tried to flash and the kitkat build I had running previously?
3. Can somehow disable all this Trusted Firmware stuff??
4. Any other suggestions???
This is driving me to the brink on insanity!!! Gotta figure it out!! Thanks for reading and trying to help!
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
prezident36 said:
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
Click to expand...
Click to collapse
I still find it hard to believe this problem absolutely cannot be solved. However, I took it to a Huawei service center and they weren't able to unbrick it either. They had to replace the mainboard, which seems like a complete waste. Cost around $50, so not the end of the world but still annoying.
Anyway, screw this whole "trusted firmware" rubbish. I'm the owner of the device, yet I'm not "trusted".
hello, i have exactly the same problem!
---------- Post added at 10:58 PM ---------- Previous post was at 10:41 PM ----------
Where do i get the replacement mainboard from?
Me too, upgrading kitkat to lollipop. Now facing that rescue error.
My Honor 4X is unlock bootloader and root before upgrading lollipop,
Hi all,
I've spent a rather frustrating week or so in the throes of searching Google and XDA to figure out how to get my brand new RS988 upgraded to the 21c software version on Nougat. Here's what I've done so far:
-Check for OTA updates using the OS. No dice...it went from 11a to 11c and will not find any further updates.
-Use LG Bridge to try to update the software. No dice. The software tries to get the current OS version and then says "cannot find operating system version" and won't contact home base to get the new files.
-Reboot into boot loader to install TWRP. No dice...the phone will not reboot into the boot loader for some reason. I've tried using both the ADB method of "adb reboot bootloader" and "adb reboot-bootloader", but both just have it reboot into the full OS. I've also tried powering on the phone while holding the volume down button, to no avail.
-All root and TWRP methods, and even getting the official bootloader unlock require booting into the boot loader
The one thing I *have* been able to get to work was re-flashing a KDZ of the RS98811c software from autoprime's linked repository.
As best as I can tell, I am stuck. Without being able to install TWRP via the boot loader I don't know how to update the software. Please help me figure this out!
Edit: additional device info added
Android version: 6.0.1, 2016-07-01 security patch
Baseband version: MPSS.TH.2.0.c1.4-00010-M8996FAAAANAZM-1.43591.5
Kernel: 3.18.20
Build: MMB29M
Configuration: F15.LGE.RS988.0
Software version: RS98811c
Security software: MDF v2.0 Release 1
Thanks!
Use lg up
It's possible that you have the RS988.BPT version (Brightpoint), which only got updated to 11h, I believe. I sent in a RS988.USA version, and they swapped for a new BPT motherboard. I've since sent it back yet again to get that resolved.
It appears to be a Tracfone Wireless version, according to the box, at least. It was supposed to be new, not refurb, so fingers crossed that's all good as well. Even if it was the Brightpoint version, wouldn't that have been fixed when I flashed the USA stock ROM?
I also don't see how to use LG UP to reboot into boot loader mode. It only shows me the phone, with nothing clickable, and a selection of 4 processes: refurbish, upgrade, phonesetting, and FOTA upgrade. Not wanting to mess up my phone, I am trying to be cautious about just trying either of the latter two options. Especially without a file there. Thoughts?
You did unlock the bootloader am I correct?
Matthew_Jay said:
You did unlock the bootloader am I correct?
Click to expand...
Click to collapse
Nope. I can't get into the bootloader (unless I've totally missed a method to do that). Even the instructions on LG's website pre-suppose that you can enter the bootloader. Step 9 on their bootloader unlock instructions say:
9. Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window.
Click to expand...
Click to collapse
Unfortunately, issuing that command simply reboots the phone without a bootloader in sight. Any commands issued by fastboot after the "adb reboot bootloader" command just sit there saying "waiting for device". I think if I could get this far, the excellent instructions elsewhere on these forums would have me sorted the rest of the way, since then I could use TWRP to flash a more recent OS version. Thus far, it's only LG UP which works, which also requires a .KDZ file, but I can't find one for any version > 11c.
One further edit - I re-read autoprime's instructions and was at least able to get the phone to boot into recovery mode. (I can't tell whether the grey or white highlight is the "active" selection, so I haven't tried selecting one since I'd rather not wipe my device unnecessarily.) But in that mode it won't connect to my Win10 machine for adb or fastboot to do anything. Still can't get it into fastboot mode using "adb reboot bootloader". What am I missing? Feel free to be super-basic, since it's probably something of that sort.
AdamDG said:
One further edit - I re-read autoprime's instructions and was at least able to get the phone to boot into recovery mode. (I can't tell whether the grey or white highlight is the "active" selection, so I haven't tried selecting one since I'd rather not wipe my device unnecessarily.) But in that mode it won't connect to my Win10 machine for adb or fastboot to do anything. Still can't get it into fastboot mode using "adb reboot bootloader". What am I missing? Feel free to be super-basic, since it's probably something of that sort.
Click to expand...
Click to collapse
Simple answer is "You can't". I am in the same boat, stuck on 11c with no OTAs in sight. The ability to boot into the bootloader wasn't added until a later version (11h, I think?) So until/unless LG releases a KDZ of one of the later versions, you (and I) are out of luck.
Further futile time spent with LG revealed one more issue: the phone apparently was originally for Tracfone. (Never mind that I bought something specified as RS988.AUSATN and not as RS988.ATFNTN.) LG claims they have no say in the operating system or updates (even before they determined it was Tracfone) and now Tracfone says LG is solely responsible for the OS.
What is going on with these jokers?
AdamDG said:
Further futile time spent with LG revealed one more issue: the phone apparently was originally for Tracfone. (Never mind that I bought something specified as RS988.AUSATN and not as RS988.ATFNTN.) LG claims they have no say in the operating system or updates (even before they determined it was Tracfone) and now Tracfone says LG is solely responsible for the OS.
What is going on with these jokers?
Click to expand...
Click to collapse
Hey AdamDG, were you able to solve your issue? I am stuck with the same situation and asinine LG folks won't help me out because Total Wireless/Tracfone are supposed to take care of the matter. But the latter are not responsible for software updates because they are MVNOs and don't (need to) care.
Truly jokers, but more importantly, taking customers for a s(laughter) ride!
hi friends,
i bought a blackview bv6000s.
It came with android 7.0 nougat.
I wanted to downgrade to 6.0 Marshmallow..
I know that the same gsm was sold with this OS ( marshmallow ) for a while.
So i ran my SP Flash Tool and flashed an official rom found on the blackview website.
I took BV6000s_Blackview_20170930(for MT6737T).
I flashed everything ( even the preloader => it worked last time i did it ).
But when i switched on my phone after having reconnected the battery,
the screen didn't display anything except a black luminous light.
I think i have bricked my phone using an official ROM.
How is it possible?
Thank's a lot for your explainations.
gunsailor said:
hi friends,
i bought a blackview bv6000s.
It came with android 7.0 nougat.
I wanted to downgrade to 6.0 Marshmallow..
I know that the same gsm was sold with this OS ( marshmallow ) for a while.
So i ran my SP Flash Tool and flashed an official rom found on the blackview website.
I took BV6000s_Blackview_20170930(for MT6737T).
I flashed everything ( even the preloader => it worked last time i did it ).
But when i switched on my phone after having reconnected the battery,
the screen didn't display anything except a black luminous light.
I think i have bricked my phone using an official ROM.
How is it possible?
Thank's a lot for your explainations.
Click to expand...
Click to collapse
It's ARB --Anti Rollback. Several OEMs use this. Sometimes there are ways around it, sometimes not.
I don't know about this brand specifically, but Motorola prevents you from downgrading firmware unless your bootloader is already unlocked AND you leave gpt.bin off when flashing the earlier firmware. You will brick your phone if you try to install ANY earlier Motorola firmware without those conditions.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
It's ARB --Anti Rollback. Several OEMs use this. Sometimes there are ways around it, sometimes not.
Click to expand...
Click to collapse
it's not due to ARB. i've followed these instructions with the same type of phone:
How to find current rollback index
_ Reboot to fastboot mode
_ Enter the following command: fastboot getvar anti
_ If the output is blank, then anti-rollback has not yet been enabled. If you get a number in the output, then that’s your current rollback index.
and my terminal retuned:
PHP:
$ adb devices
List of devices attached
WKMJKVWG8POB6DKF device
$ adb reboot bootloader
$ fastboot getvar anti
anti:
finished. total time: 0.003s
so there is no rollback index.
ChazzMatt said:
I don't know about this brand specifically, but Motorola prevents you from downgrading firmware unless your bootloader is already unlocked AND you leave gpt.bin off when flashing the earlier firmware. You will brick your phone if you try to install ANY earlier Motorola firmware without those conditions.
Click to expand...
Click to collapse
i tried to upgrade also and it is the same. i don't know about gpt.bin ( it's not referenced by my scatter file - MTK ) but i've entered the "developer mode" and switched on "unlock oem".
your type of smartphone is not the same as mine.
thank's for your answer anyway.
Why the downgrade Nougat is so much better that marshmallow & Oreo?
gunsailor said:
it's not due to ARB. i've followed these instructions with the same type of phone:
How to find current rollback index
_ Reboot to fastboot mode
_ Enter the following command: fastboot getvar anti
_ If the output is blank, then anti-rollback has not yet been enabled. If you get a number in the output, then that’s your current rollback index.
and my terminal retuned:
PHP:
$ adb devicesList of devices attachedWKMJKVWG8POB6DKFdevice$ adb reboot bootloader$ fastboot getvar antianti: finished. total time: 0.003s
so there is no rollback index.
i tried to upgrade also and it is the same. i don't know about gpt.bin ( it's not referenced by my scatter file - MTK ) but i've entered the "developer mode" and switched on "unlock oem".
your type of smartphone is not the same as mine.
thank's for your answer anyway.
Click to expand...
Click to collapse
No, I have Motorola and LG. But you were asking how it could have happened and I was saying many OEMs put measures into place to prevent downgrading to earlier firmware.
Sent via open market LG US998 V30/V30+
hiitsrudd said:
Why the downgrade Nougat is so much better that marshmallow & Oreo?
Click to expand...
Click to collapse
hi hiitsrudd,
Marshmallow is less consumer than nougat ( watt ) because it has a simpler interface.
that's why i want to downgrade.
ChazzMatt said:
No, I have Motorola and LG. But you were asking how it could have happened and I was saying many OEMs put measures into place to prevent downgrading to earlier firmware.
Click to expand...
Click to collapse
thank's again ChazzMatt, but i can confirm via fastboot that my phone has not been bricked by ARB because there is no rollback index.
it was anyway a probable cause of my problem.
but if i can't neither upgrade from an official rom, i face a problem totally different.
i'll go to the blackview website too, then i'll go back to tell you how to fix this issue.
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11. Many guides online seem to gloss over needing the bootloader unlocked before root. TMALSS; I'm not sure if the non-international version can be bootloader unlocked and/or if I can root without needing this. Long version of what I've tried is below:
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Thus to unlock the bootloader, I am following a guide from TWRPupdate:
It says to perform 'adb reboot bootloader' and then 'fastboot oem device-id':
Code:
C:\adb-platform-tools>fastboot device-id
fastboot: usage: unknown command device-id
My phone only reboots into normal mode whenever running reboot bootloader command within ADB.
I can run fastboot commands when I run 'adb reboot fastmode' but I don't believe this is true fastmode. As I have tried everything mentioned here, such as cables or different computers. Essentially most fastboot commands I've tried do not work except for showing my device as listed / connected.
I have also tried the drivers from LG / Google / ADB separately. And on 2 computers.
Is it possible that I don't have rescue mode or a bootloader still? As I get a black screen when entering recovery mode (but my computer recognizes A device), but adb nor fastboot does. I used to see the recovery screen logo, but I stopped seeing this screen either after updating to Android V11 or reading/backing-up the partitions in QFIL.
In last resort, I have tried rooting via patching the boot image using Magisk v23. I downloaded the firmware for my carrier, converted the KDZ to DZ via Python, and extracted the boot.img_117638 file. Given the file is 0 bytes with nothing in text edit, I still converted it to an img file. But in the kdztools android app, when I select this image file and run, I get:
Code:
!Invalid input file
!Installation failed
I'm guessing the boot.img file should have some data in it. But I'm not sure this method would even work due to the fastboot issues, especially with 'download to device' errors.
-------
I'm just at a standstill on what to even try next. I don't see many people having this much trouble unlocking/rooting their v60. Did the OTA Android v.11 break the root-ability?!
PS: Debugging and OEM unlock are both set in developer options. I can also list drivers used if need.
Thanks for the help in advance!
While digging I also found a post by alexenferman whom managed to use QFIL to root many older ZTE smartphones. They state it may but likely won't work on newer flagship phones. It's a great tutorial I'll have to try soon, but is there a reason it likely won't work here?
kyij said:
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11.
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
NGOwner said:
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
Click to expand...
Click to collapse
Haha, I remember reading that and still continued
I am on Verizon myself using this TM model. I know the phone was unlocked to the point where I could use it with Verizon. I even got 5g using my old 4g sim card.
Anyhow.. I have tried using that command already, and get the same 'command not supported issue'.
Code:
C:\adb-platform-tools>fastboot devices
LMV600TMc40cxxxx fastboot
C:\adb-platform-tools>fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Again have tried different computers and cables as I've read fastboot can be pretty picky too.
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
NGOwner said:
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
Click to expand...
Click to collapse
Yes I do, I have turned it off and back on as well.
Well then at this point, I'm tapped out. Smarter folks than me will need to step in and take up the mantle.
[NG]Owner
I ended up posting a form to reddit where about 10 people insisted I did something wrong, and with little surprise -- I did.
I did not flash the engineering bootloader after saving a copy.
Makes a lot more sense since it seemed like a lot of steps to backup without actually doing anything
Thanks NG for the help too!
are you success to unlock bootloader yet. if no i will show you
adb reboot fastboot> select reboot bootloader on your phone> fastboot oem unlock