Database Users

[Q] Tablet has four icons on bootloader screen? Help

This tablet was bought from a online warehouse as a returned item. Just for kicks I powered up using the power and - volume. There is Four icons "RCK, Android, USB, and Wipe Data. I have up graded to the JB OTA and I know it had been reset before I got it. Now if I am right has someone tried to root this tablet? I base that on the RCK icon which when selected just shows the android on his face with a red exclamation.
There is no text showing that the boot loader has been unlocked. So where do I go from here to unlock and root ?

That's the normal ASUS JB bootloader, if there isn't any text when turning the tablet on saying: "Device unlocked" it isn't. So if you want to unlock download the unlocking tool apk from ASUS website, install and run on your tablet. After unlocking just check the development section of the forums and get informed on how to install recovery (CWM or TWRP), root and custom ROMs.

Thanks
jgaf said:
That's the normal ASUS JB bootloader, if there isn't any text when turning the tablet on saying: "Device unlocked" it isn't. So if you want to unlock download the unlocking tool apk from ASUS website, install and run on your tablet. After unlocking just check the development section of the forums and get informed on how to install recovery (CWM or TWRP), root and custom ROMs.
Click to expand...
Click to collapse
Thanks for the quick reply. I would of been surprised if it had of been rooted and Amazon.com's techs hadn't of caught it when it was returned.
Going to hold off rooting it until the warrantee is gone. Still having nightmares about my Viewsonic gTablet turning into a cyborg tablet thingy and attacking me. All because I just had to try every ROM I could cram down it.

Although unlikely, it could still be rooted if it was done prior to the jb update, and it could still be locked even if rooted. Download root checker from the market and you can safely test this.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

[Q] Quick question about unlocking bootloader

I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.

dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.

dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
I'm no expert at all but I ran motoapocolyps and if didn't do anything. It will either fail and your phone will be fine or, depending on what update you last took, unlock it. My phone is past due for unlocking the bootloader unless there is a way to downgrade it.

Hi
aviwdoowks said:
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.
Click to expand...
Click to collapse
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!

dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted

dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.

aviwdoowks said:
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted
Click to expand...
Click to collapse
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!

RikRong said:
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.
Click to expand...
Click to collapse
"You can't cover up a BL unlock." <- THANK YOU! That is what I was trying to confirm....
I was thinking that since you can do this to cover up the unlocked bl warning: http://forum.xda-developers.com/showthread.php?t=1901444
that you can also do something to cover up the AP screen as well.
Since I'm rooted, and this phone is supposed to get 4.4, I'm not too upset that I can't unlock (Though with 4.4 I'll probably lose root ).. The stock rom is pretty nice on these, and root gives me pretty much anything I want for customization.
Thanks!

dreamersipaq said:
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!
Click to expand...
Click to collapse
I am the one confused! I need to learn my codes.

/!\ WARNING /!\ Do NOT relock your bootloader around the time of updating to 5.1!

Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootloader is not a good idea
Please also see the below link provided by @efrant
https://support.google.com/nexus/answer/6172890?hl=en
This goes into more detail about how google have enhanced device security with 5.1 and some other pitfalls that you may wish to avoid. This is pretty salient information, so do give it a read.

Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER. ???
Sent from my Nexus 9 using XDA Free mobile app

ChristianJay said:
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.

So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device protection a locked bootloader would serve a purpose. Preventing someone from just flashing a custom rom and keeping your device.

:thumbup:

I thought I really #$# up
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...

xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..

rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
Click to expand...
Click to collapse
Hi root,
I saw that thread yesterday ...
I thought this was already covered when the N6 came out, to get the bootloader unlocked you had to do a 1st boot of the device and ENABLE OEM Unlock, then you were good to go to get into fastboot and unlock.
The reason was google put the option there for 5.0, vice all our previous versions which had no toggle for it.
I think it was people jumping the gun and not doing that first boot, but immediately jumping into fastboot and flashing, and that caused it, yes? Because the BL wasn't unlocked, they couldn't flash the OTA and boot img ...

daijizai said:
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
Click to expand...
Click to collapse
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.

xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
kng60ft said:
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
Click to expand...
Click to collapse
There is no need to lock the device to take an OTA. You can keep it unlocked and do an ota

doitright said:
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
Click to expand...
Click to collapse
Not nonsense. Yes you need physical access to carry out the attack, but with a locked bootloader and the new precautions against unlocking and fastboot it makes locked bootloaders fairly bulletproof.
I cannot recommend unlocked bootloaders to anyone that works SCIF'd and leaves their phone in a shared box during the day, anyone that crosses international borders, or anyone whose phone might contain IP or trade secrets and could be a target of theft.
This is as much about trusting the phone afterwards as it is about protecting your data on the phone - even when encrypted.

y2whisper said:
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device detection a locked bootloader would serve a purpose.
Click to expand...
Click to collapse
Just keep it unlocked

rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootlaoder is not a good idea
Click to expand...
Click to collapse
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.

nyteryder79 said:
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
Click to expand...
Click to collapse
Thats good.

http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
This may help if you got stuck in a bootloop.

is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?

darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.

Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58201783&postcount=106
should help

darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
Factory reset?
Not really the thread to ask this though.

rootSU said:
Factory reset?
Not really the thread to ask this though.
Click to expand...
Click to collapse
Thanks, and sorry

Please help want to unlock bootloader

Guys please help I can't unlock the boot loader(ze550kl) for the following model I wanted to install cm. Thank you
ASUSSKU WW
BOARD msm8916
BOOTLOADER unknown
BRAND asus
CHARACTERISTICS phone
COUNTRYCODE WW
CPU_ABI arm64-v8a
DEVICE ASUS_Z00L_63
DISPLAY LRX22G.WW_user_1.17.40.1234_20160304
FINGERPRINT asus/WW_Z00L/ASUS_Z00L_63:5.0.2/LRX22G/WW_user_1.17.40.1234_20160304:user/release-keys
HARDWARE qcom
HOST builder5-pc
ID LRX22G
MANUFACTURER asus
MODEL ASUS_Z00LD
PRODUCT WW_Z00L
TAGS release-keys
TYPE user
USER builder5
CODENAME REL
INCREMENTAL WW_Z00L-WW_user_1.17.40.1234_20160304-user-20160304
RELEASE 5.0.2
SDK_INT 21
RADIO 202c10_11.1.0_160304
Root Access:no access
SU:not found
How to unlock bootloader?

Use the boot loader unlock app found in the General subforum.

HampTheToker said:
Use the boot loader unlock app found in the General subforum.
Click to expand...
Click to collapse
I tried it just restarts and there is no white logo screen

The white logo screen is only for the ZenFone 2 base models. For ZenFone 2 Laser variants, the logo screen will and should remain black. To verify whether your device hadha been truly unlocked, head over to fastboot mode on your device, and type the command: "fastboot oem device-info" (without the quotes) into the command prompt/terminal.
If it says device unlocked: true, that means your device had been successfully unlocked.
Another method is to try flashing TWRP onto your device, then attempting to boot into recovery. If it boot successfully, your device had been unlocked. If the ASUS logo just flashes and goes instantly, and then rebooting back to the system, it is still locked.

Rizzed said:
The white logo screen is only for the ZenFone 2 base models. For ZenFone 2 Laser variants, the logo screen will and should remain black. To verify whether your device hadha been truly unlocked, head over to fastboot mode on your device, and type the command: "fastboot oem device-info" (without the quotes) into the command prompt/terminal.
If it says device unlocked: true, that means your device had been successfully unlocked.
Another method is to try flashing TWRP onto your device, then attempting to boot into recovery. If it boot successfully, your device had been unlocked. If the ASUS logo just flashes and goes instantly, and then rebooting back to the system, it is still locked.
Click to expand...
Click to collapse
Thanks Rizzed I'll check via fastboot

Any results?

Same device and same problem
I have tried with a few "different" unlock apps and still get the following result after running
Code:
fastboot oem device-info
HTML:
...
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.004s]
finished. total time: 0.004s
Also I noticed that Asus' support page from the country where the device was bought does not have "utilities" section where the unlock apk would be located. (can't post a direct link since I'm new here, so here's part of the link: asus.com/br/Phone/ZenFone-2-Laser-ZE550KL/HelpDesk_Download/)

for this version of firmware(WW_user_1.17.40.1234_20160304) it does not work.. I have tried many times ... I am downgrading to 1.16.... will check.. For 1.16, bootloader unlock works with the unlocker app for ze600kl

hemantjangid39 said:
for this version of firmware(WW_user_1.17.40.1234_20160304) it does not work.. I have tried many times ... I am downgrading to 1.16.... will check.. For 1.16, bootloader unlock works with the unlocker app for ze600kl
Click to expand...
Click to collapse
Does it really work after downgrading? I'm currently sitting right here pulling my hair out over this. Would be great if it really works.

Did you manage to downgrade?
I tried downgrading but failed with fota_return_code 409 ("can't install this package [date] over newer build [date]").

igorrafael said:
Did you manage to downgrade?
I tried downgrading but failed with fota_return_code 409 ("can't install this package [date] over newer build [date]").
Click to expand...
Click to collapse
Before attempting to downgrade, go to FASTBOOT mode, and type this commands (in order),
fastboot erase system
fastboot oem reboot-recovery
It should be able to flash successfully now.

Rizzed said:
Before attempting to downgrade, go to FASTBOOT mode, and type this commands (in order),
fastboot erase system
fastboot oem reboot-recovery
It should be able to flash successfully now.
Click to expand...
Click to collapse
Thanks for the tip. Erasing system didn't work but your gave me the idea of changing the recovery partition. I managed to flash the stock version from this post. Only after the second line of the recovery screen showed "1.16" I managed to flash the file UL-Z00L-WW-1.16.40.763-user.zip
Unfortunately still didn't manage to unlock after a factory reset with the new firmware. Using unlock apk from this post:

igorrafael said:
Thanks for the tip. Erasing system didn't work but your gave me the idea of changing the recovery partition. I managed to flash the stock version from this post. Only after the second line of the recovery screen showed "1.16" I managed to flash the file UL-Z00L-WW-1.16.40.763-user.zip
Unfortunately still didn't manage to unlock after a factory reset with the new firmware. Using unlock apk from this post:
Click to expand...
Click to collapse
Really sorry about that..
I'm currently trying out all the other previous software, starting from the latest to the oldest. I will inform you immediately if it works out.

nrv.patel said:
I tried it just restarts and there is no white logo screen
Click to expand...
Click to collapse
I have been trying to unlock using the official unlock app since seven days. @Rajko said the app works sometimes. Also I have noticed that devices that were updated to 1.17 build are facing the same problem. Others who unlocked their device before the update were able to unlock BL. I even tried downgrading to 1.15 and 1.16 but no success till now. Maybe Asus has patched the bootloader with the 1.17 update and as you know bootloaders cannot be downgraded normally and can be fatal for any device. We may be able to unlock when Asus releases unlock app for Z00L.

sziraqui said:
I have been trying to unlock using the official unlock app since seven days. @Rajko said the app works sometimes. Also I have noticed that devices that were updated to 1.17 build are facing the same problem. Others who unlocked their device before the update were able to unlock BL. I even tried downgrading to 1.15 and 1.16 but no success till now. Maybe Asus has patched the bootloader with the 1.17 update and as you know bootloaders cannot be downgraded normally and can be fatal for any device. We may be able to unlock when Asus releases unlock app for Z00L.
Click to expand...
Click to collapse
Can confirm this. I downgraded to the oldest but to no avail.
Is there any way to downgrade the bootloader though? I really am thinking of selling this device for those high-end phones (Samsung S7/HTC 10) if there really is no solution.
Sent from my ASUS_Z00LD using XDA-Developers mobile app

Rizzed said:
Can confirm this. I downgraded to the oldest but to no avail.
Is there any way to downgrade the bootloader though? I really am thinking of selling this device for those high-end phones (Samsung S7/HTC 10) if there really is no solution.
Sent from my ASUS_Z00LD using XDA-Developers mobile app
Click to expand...
Click to collapse
if we don't figure it out within a month I'll also look into a replacement. For now I'll try to live with the stock rom...
btw, any reason you'd go for Samsung/HTC instead of Motorola/OnePlus?

igorrafael said:
if we don't figure it out within a month I'll also look into a replacement. For now I'll try to live with the stock rom...
btw, any reason you'd go for Samsung/HTC instead of Motorola/OnePlus?
Click to expand...
Click to collapse
The HTC looks to be an excellent choice. Their last few devices weren't up to par, and it's cost them dearly. They've stepped their game up with the 10, and I think it'll be the device to put them back in the game.
The Galaxy S7 family speaks for itself.
As for Motorola, I'd avoid them like the plague. They're horrible with updates and are getting sued right now for failing to properly honor their customers warranty claims.
Oneplus is a toss up, IMO. The Oneplus 3 could be a hit or a miss. I'm not sure when it's supposed to drop, but I'd keep my eye on it.

HampTheToker said:
The HTC looks to be an excellent choice. Their last few devices weren't up to par, and it's cost them dearly. They've stepped their game up with the 10, and I think it'll be the device to put them back in the game.
The Galaxy S7 family speaks for itself.
As for Motorola, I'd avoid them like the plague. They're horrible with updates and are getting sued right now for failing to properly honor their customers warranty claims.
Oneplus is a toss up, IMO. The Oneplus 3 could be a hit or a miss. I'm not sure when it's supposed to drop, but I'd keep my eye on it.
Click to expand...
Click to collapse
Interesting, I personally had very good experience with Motorola and have seen a lot of people having trouble with samsung phones.
My view on Samsung is biased though, as I barely consider them android phones. Prejudice aside , I see them as designed for people who want the status of iPhones but want something "like an android".
I hope the OnePlus 3 turns out to be good

igorrafael said:
Interesting, I personally had very good experience with Motorola and have seen a lot of people having trouble with samsung phones.
My view on Samsung is biased though, as I barely consider them android phones. Prejudice aside , I see them as designed for people who want the status of iPhones but want something "like an android".
I hope the OnePlus 3 turns out to be good
Click to expand...
Click to collapse
Well, sorry for saying this, but I personally do not trust any companies from (you know which country). Their phones may pack in very high specifications at very low and attractive prices, but really, there must be a catch, right? (personal opinion)
I live in Singapore and unfortunately, I don't see any Motorola smartphones being sold at any of our major electronics store or even online.
Sent from my ASUS_Z00LD using XDA-Developers mobile app

igorrafael said:
Interesting, I personally had very good experience with Motorola and have seen a lot of people having trouble with samsung phones.
My view on Samsung is biased though, as I barely consider them android phones. Prejudice aside , I see them as designed for people who want the status of iPhones but want something "like an android".
I hope the OnePlus 3 turns out to be good
Click to expand...
Click to collapse
I didn't say Moto makes a bad phone. On the contrary, their phones are usually pretty solid. It's their business practices and weak update support that turns me off, but they undeniably make good phones. Just don't expect to run the latest and greatest Android has to offer a year after release.
My opinion of Samsung is biased as well. My previous device was a Galaxy S4, and I LOVED it. It was a damn good phone that could take whatever I threw at it. And, the dev support...that phone had every ROM and mod you could ever want. The only reasons I didn't stick with Sammy were the price, and I the fact that my Samsung experience had gotten a little stale after three years with a Galaxy S4. Plus, these Zenfone variants dropped when I was ready to upgrade, and they were pretty attractive. I don't regret it for a second. Like I said previously, if Asus would drop ZenUI, I'm certain that the root community would want what they have to offer.
Oneplus is due to release a good device. I have a good feeling that they'll drop that crappy invite system this time around. If they do that and give us another flagship killer, the Oneplus 3 would be more than likely sell like hotcakes.

Does unlocked BL automatically mean root is possible.

I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?

Bubba Fett said:
I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?
Click to expand...
Click to collapse
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.

lightninbug said:
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.
Click to expand...
Click to collapse
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.

Bubba Fett said:
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.
Click to expand...
Click to collapse
No.. thought I was getting it today via UPS... Guess I was tracking the wrong package lmao (stoner moment)... The G pad X came today instead... Lammmmme!!!

LG blocked fastboot commands since MM so the standard would usually be Unlock BL, flash recovery then flash SU.
But its not the case anymore.
Now its Unlock BL wait till an official.tot or .kdz to be released or leaked from LG, then repack it with root or a recovery and flash via LGUP or LG Tool.

just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.

Z51 said:
just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.
Click to expand...
Click to collapse
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.

lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.

douger1957 said:
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.
Click to expand...
Click to collapse
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!

Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
Amen to that lol! Do you know how long does it take to restore every single app when you dont have titanium backup installed and your device rooted? (i have 113 user apps in my lg g3), you can easily take up to 2 hours installing and setting up. while when you have titanium, you can sit there and drink up your coconut juice while it does everything on its own and everything already set up, and it is pretty quick too. Also, i hate ads. unless the benefit me (that's how i found out about the LG V20 lol) Not to mention that many of the ads out there are either scam or viruses . Also, rooting is the way to really owning your device. a device is not yours until whatever thing you want to do can actually be achieved because you (the owner) wanted to and not because the company wanted to. :good:

I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.

Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
Lol you might as well return it now then. Beucase i doubt it will be done that quick. I mean, i bought this phone because of its great features. And even though i like to root, flash, and all that, well, i have set up my mind in a balanced mode and said "well, chances to get root are 50%, sure i like to root my phone but probably it wont be possible ". To be honest i usually wait about 3 month before buying a new released smartphone because by around that time, they usually have root and have gotten bugs already fixed. But i couldnt resist the offers on this one LOL. so, if it doesnt get root, i will stuck with it for a while anyway.

Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
I'm in the exact same boat as you. My V20 is sitting all pretty on my desk. T-14 days before I return it if no root. Been rocking the OnePlus 3 with an awesome ROM since the first Note 7 recall. Absolutely loving it. Got the V20 only because of the screen, camera, and supposedly better sound--all of which are probably marginal upgrades compared to OP3 especially considering it's well over twice the price.

V521 didn't have root until update was released. I grabbed and uploaded the ROM, and soon rooted .dz was there.

Confirmed: Similar to T-Mobile LG G5 there are not flash commands in fastboot to write a new recovery. Will need someone to create a TOT file to get us TWRP and root I think.

confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT=&quot]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
c:\adb>fastboot boot v20.img
downloading 'boot.img'...
OKAY [ 0.700s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.721s
Click to expand...
Click to collapse

lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Don't get your panties in a bunch. It was a simple question. I come on here to make money. I fix phones for a living and I come here to fix what people attempting to root broke and brought to me to fix. If you don't want to root, you don't have to. If you do, then by all means root your phone. No need to be a **** about it.
Sent from my SM-G928V using Tapatalk

Amd4life said:
confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT=&quot]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
Click to expand...
Click to collapse
Apparently LG disables boot/flash. I'm going to try to get a tmobile TOT file tomorrow. I'm working on updating a TOT extractor tool right now to work it.

Can someone run this:
Code:
fastboot getvar all

Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
I will most likely root my phone when the time comes. I am not against rooting at all... I rooted all of my phones except the Note 7. What I'm saying is that root isn't for everyone, not everyone should root their phone even if they think it's the thing to do and that I think there's a place at XDA for people who don't want to learn ADB commands.