I have a G6 H872 from T-mobile, with an unlocked bootloader.
For some reason no commands other than unlocking the bootloader work, and I can't flash TWRP.
I get an error saying remote: unknown command. I've tried different usb ports, different cords and different computers, all return the same error.
Is there a fix for this?
Not yet, head on over to this post from the g6 t-mobile community https://forum.xda-developers.com/tmobile-g6/how-to/wip-tmous-lg-g6-twrp-root-mega-thread-t3584115
100% same issue with me :/ any luck with your device?
usmras said:
100% same issue with me :/ any luck with your device?
Click to expand...
Click to collapse
Anyone get this done?
Related
Hi,
So I recently got my hands on this new phone, and the blimming phone won't unlock. I'm using the XT1700!!! Not E3 Power!. It's on TESCO UK, and the System Version is "23.0.XT1700_S303_160829_UK". Yes, in developer options, OEM Unlocking is ticked! Tried two PCs, different drivers, different cables... idk.
I get the output on my phone to unlock with both "flashing unlock_critical" and "oem unlock"; both say "Unlock failed, returning to fastboot in 3s..."
This is the output in CMD:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 7.803s
Any suggestions? I'm really not sure.
jcolongo said:
Hi,
So I recently got my hands on this new phone, and the blimming phone won't unlock. I'm using the XT1700!!! Not E3 Power!. It's on TESCO UK, and the System Version is "23.0.XT1700_S303_160829_UK". Yes, in developer options, OEM Unlocking is ticked! Tried two PCs, different drivers, different cables... idk.
I get the output on my phone to unlock with both "flashing unlock_critical" and "oem unlock"; both say "Unlock failed, returning to fastboot in 3s..."
This is the output in CMD:
Any suggestions? I'm really not sure.
Click to expand...
Click to collapse
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure if you read elsewhere in the unlock bootloader thread, the S303 firmware DOES NOT allow the bootloader to be unlocked.
My E3 is S124 firmware, although I have been running Lineage OS 14.1 (android 7.1.2) on it for some time.
Sorry but there's no way you can unlock this model
bubba1601 said:
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure if you read elsewhere in the unlock bootloader thread, the S303 firmware DOES NOT allow the bootloader to be unlocked.
My E3 is S124 firmware, although I have been running Lineage OS 14.1 (android 7.1.2) on it for some time.
Sorry but there's no way you can unlock this model
Click to expand...
Click to collapse
Is there not anyway I can flash S124? Its MTK so I could surely use a flashtool?
bubba1601 said:
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure you need to unlock the bootloader to do that.
Its really not worth the hastle.
S124 isn't available anywhere to download unless you pay for it, but you got to unlock the bootloader before you can flash it, as its only available as a TWRP back up.
I lost my IMEI number doing that and had to flash an S131 E3 power firmware and reflash my IMEI which wasn't easy at all.
I've just checked and S303 and S512 are indeed bootloader locked.
Click to expand...
Click to collapse
bubba1601 said:
bubba1601 said:
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure you need to unlock the bootloader to do that.
Its really not worth the hastle.
S124 isn't available anywhere to download unless you pay for it, but you got to unlock the bootloader before you can flash it, as its only available as a TWRP back up.
I lost my IMEI number doing that and had to flash an S131 E3 power firmware and reflash my IMEI which wasn't easy at all.
I've just checked and S303 and S512 are indeed bootloader locked.
Click to expand...
Click to collapse
Damn man. Is there anyway I can root at least?
Click to expand...
Click to collapse
jcolongo said:
bubba1601 said:
Damn man. Is there anyway I can root at least?
Click to expand...
Click to collapse
Not unless you find one if these "one click root" apps via PC that supposedly magically root.
Its a shame these bootloaders cannot be advertised as not unlocking compatible, it would have saved you a lot of trouble.
Do try everything although to be fair, I've not seen anyone post about unlocking those two firmwares.
I'm only sorry I can't help more
Click to expand...
Click to collapse
bubba1601 said:
jcolongo said:
Not unless you find one if these "one click root" apps via PC that supposedly magically root.
Its a shame these bootloaders cannot be advertised as not unlocking compatible, it would have saved you a lot of trouble.
Do try everything although to be fair, I've not seen anyone post about unlocking those two firmwares.
I'm only sorry I can't help more
Click to expand...
Click to collapse
It's all good. I'm making progress however; managed to find a S124 SP flash firmware, but I'm scared to flash it, as I'll be out of a phone for 3 months which is a problem, as I need it for collage. I'll continue to look around.
Click to expand...
Click to collapse
Hi,
I have the OnePlus 5 8GB.
I unlocked my bootload, rooted my phone, all good.
But then I realized android pay is not working with rooted phones, so i wanted to undo it.
for some reason i ran this because i found it in a guide to lock the bootloader again (yes, it was was stupid):
./fastboot flashing lock
After that i got the message that my device is corrupt and cant boot. So i ran ./fastboot oem unlock and that message disappeard.
I tried booting, but nothing happend for 10 minutes, still boot animation. so i went into fastboot, flashed twrp and tried doing a factory reset, but whatever i do, I get tons of these error messages:
Updating partition details...
Error opening: '/data/misc/[...]
Error opening: '/data/user_de/0/[...['
(No such file or directory)
What can I do?
I can even ADB sideload because of those errors.
edit:
also it shows nothing for bootloader version or baseband version in the fastboot screen.
https://imgur.com/a/z2KN3
doesnt look good. cant copy anything to device or from device
Might have to RMA the phone. I'm not sure I've seen anyone unbrick a phone after locking the bootloader with a custom recovery still installed. I hope someone knows of a way. Good luck bro.
Also, of you get it working, use Magisk, it allows Android pay to work while rooted
Eric214 said:
Might have to RMA the phone. I'm not sure I've seen anyone unbrick a phone after locking the bootloader with a custom recovery still installed. I hope someone knows of a way. Good luck bro.
Also, of you get it working, use Magisk, it allows Android pay to work while rooted
Click to expand...
Click to collapse
Anything I should do to have them not reject the RMA?
thx for the Magisk advice, using it now.
Oh I think i got it.
flashed the OP5_recovery.img from their website via fastboot, android launched again!!!
TheCorax said:
Anything I should do to have them not reject the RMA?
Click to expand...
Click to collapse
Since it's obvious someone tampered with the software, they may reject it.
You don't lose warranty if you root, but they won't cover the cost if anything happens to it due to the user's intervention.
If you manage to get the stock ROM onto the phone, you may be able to flash it from TWRP.
TheCorax said:
Oh I think i got it.
flashed the OP5_recovery.img from their website via fastboot, android launched again!!!
Click to expand...
Click to collapse
So, did it work? Did it boot Android or just recovery? Please let us know so that anyone who comes up with this problem can solve it without suffering as much as you did.
Sent from my OnePlus 5 using XDA Labs
elbuenzurdo said:
So, did it work? Did it boot Android or just recovery? Please let us know so that anyone who comes up with this problem can solve it without suffering as much as you did.
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
Yes it works again. That what I meant by android is launching.
TheCorax said:
Yes it works again. That what I meant by android is launching.
Click to expand...
Click to collapse
How do you do to get your device recognized? I have a similar problem for that command. But muy device just turned off and doesnt do nothing, Im trying flash it but nothing atm.
I have a leeco le s3 x626
Can anyone point me to a guide to root the original, stock Marshmellow Android version of the G4 Plus? All I see are Nougat and Oreo guides
emkorial said:
Can anyone point me to a guide to root the original, stock Marshmellow Android version of the G4 Plus? All I see are Nougat and Oreo guides
Click to expand...
Click to collapse
Yeah, here you are: https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
Thanks. Any tips on how to get ADB to see the device? It refuses to, so I cant unlock the bootloader. I've tried 3 different USB drivers off motorolas sites and 4 different cables. It just doesnt work.
emkorial said:
Thanks. Any tips on how to get ADB to see the device? It refuses to, so I cant unlock the bootloader. I've tried 3 different USB drivers off motorolas sites and 4 different cables. It just doesnt work.
Click to expand...
Click to collapse
Fastboot devices command does not show your devices serial number?
What PC you have? Disable all firewalls and driver signature verification, also try other PC of possible or other USB ports.
Guess 4th time is a charm, it worked, all rooted now. Thanks for link!!
Hello all! First post here so if I out this in the wrong section, or do the pst wrong, then feel free to correct me.
I am trying to root my old phone, which is a Moto e4. I tried rooting with mutiple sources (Using a computer) but all of them failed. I concluded through google searches that one reason this may be happening is because the bootloader is still locked, so I started on that.
I got to the command promt, and can locate and identify the device, but when I run the command to unlock the bootloader and get the code for the motorola website, (fastboot oem unlock, and some variations of this command, all the same result.) When I do this, I get the results that I should get, but where the code should be, it says not found. I have my OEM unclokcing checked in Deve settings, and USB debugging is on as well. I am at school right now, so unfornatly I cannot give information on the model number, or anything like that, but I can respond to questions when I can. If I don't even need to unlock the bootloader on the moto e4 to root, then all the better, but I am fine with going through the trouble of unlokcing the bootloader!
Thanks,
Eriith
Eriith said:
Hello all! First post here so if I out this in the wrong section, or do the pst wrong, then feel free to correct me.
I am trying to root my old phone, which is a Moto e4. I tried rooting with mutiple sources (Using a computer) but all of them failed. I concluded through google searches that one reason this may be happening is because the bootloader is still locked, so I started on that.
I got to the command promt, and can locate and identify the device, but when I run the command to unlock the bootloader and get the code for the motorola website, (fastboot oem unlock, and some variations of this command, all the same result.) When I do this, I get the results that I should get, but where the code should be, it says not found. I have my OEM unclokcing checked in Deve settings, and USB debugging is on as well. I am at school right now, so unfornatly I cannot give information on the model number, or anything like that, but I can respond to questions when I can. If I don't even need to unlock the bootloader on the moto e4 to root, then all the better, but I am fine with going through the trouble of unlokcing the bootloader!
Thanks,
Eriith
Click to expand...
Click to collapse
yes bootloader needs to be unlocked.
It could be a usb driver issue
See moto driver link in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
sd_shadow said:
yes bootloader needs to be unlocked.
It could be a usb driver issue
See moto driver link in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
In between the time you responded and now, I have ublcoked the bootloader, and got TWRP to work, not I just need to install Magisk and start the root! Thank you for responding though.
So my beloved LS997's charging port has given up the good fight and no longer works, so I have been hamstringing it along charging batteries outside the phone using an external battery charger... And bought myself a "New Unlocked LS997" that came with Android 7.0 with the intention of rooting it and flashing LineageOS on it and being good to go.
Problem though, Dirty Santa doesn't seem to work beyond step one, and when I attempt to flash a different KDZ per other rooting methods I am getting a SPC code error preventing me from flashing said KDZ.
Anyone have any luck rooting these devices? Thanks in advance!
Americancosworth said:
So my beloved LS997's charging port has given up the good fight and no longer works, so I have been hamstringing it along charging batteries outside the phone using an external battery charger... And bought myself a "New Unlocked LS997" that came with Android 7.0 with the intention of rooting it and flashing LineageOS on it and being good to go.
Problem though, Dirty Santa doesn't seem to work beyond step one, and when I attempt to flash a different KDZ per other rooting methods I am getting a SPC code error preventing me from flashing said KDZ.
Anyone have any luck rooting these devices? Thanks in advance!
Click to expand...
Click to collapse
Use the How to root ZV7 guide by runningnaked. Also you need to flash the vs995 file with Uppercut or the modified Uppercut floating around somewhere. If you are past ZV7 you can't do anything for root. With Uppercut make sure your phone is all set for adb and properly connected. Then also try to open Uppercut as administrator. It will show dump system and other options at bottom if loaded correctly.
If us996...then try the official lg unlock bootloader method. What I described is for ls997.
Ls997 cross flashed to us996...idk. depends on what software version if that's that case.
As for adb...when connected to PC make sure to also have photo transfer selected instead of file tranfer.
If it's an LS997 that's been cross-flashed to US996 firmware, then it should be rootable because if it weren't , then you wouldn't even be able to cross-flash anything on it.
Americancosworth said:
Problem though, Dirty Santa doesn't seem to work beyond step one, and when I attempt to flash a different KDZ per other rooting methods I am getting a SPC code error preventing me from flashing said KDZ.
Anyone have any luck rooting these devices? Thanks in advance!
Click to expand...
Click to collapse
I used the modified LGUP found over here.
Make sure you put the phone in download mode (with the phone powered off, hold down volume-up, then connect the phone via USB to your computer) before running LGUP. The rooting guides don't mention this since they assume you know how to downgrade firmware before starting the main rooting procedure.
C D said:
If it's an LS997 that's been cross-flashed to US996 firmware, then it should be rootable because if it weren't , then you wouldn't even be able to cross-flash anything on it.
I used the modified LGUP found over here.
Make sure you put the phone in download mode (with the phone powered off, hold down volume-up, then connect the phone via USB to your computer) before running LGUP. The rooting guides don't mention this since they assume you know how to downgrade firmware before starting the main rooting procedure.
Click to expand...
Click to collapse
My mistake...yes download mode before lg up...not adb. True on the cross flashed and being rootable.