Database Info

V10 h900 root

Does the V10 h900 have root capability for marshmallows?

I am also looking for root on marshmallows, any help will be greatly appreciated. thank you so much in advance

I can't remember. Can you unlock the bootloader on the H900? If so, you can root it -- even on Nougat.
-- Brian

In developer options, you can tick on OEM unlock, but I'm having a problem booting into the bootloader to finish the adb instructions to unlock the bootloader. Is there another way?

vulcanrvn said:
In developer options, you can tick on OEM unlock, but I'm having a problem booting into the bootloader to finish the adb instructions to unlock the bootloader. Is there another way?
Click to expand...
Click to collapse
It's not possible to unlock the bootloader on the H900 via the LG website anyway.
I cannot post url's here but if you go to androidsage and search for the LGV10 you should find some useful instructions on how to root the device without unlocking the bootloader first.

I cant find anything
IvorTollah said:
It's not possible to unlock the bootloader on the H900 via the LG website anyway.
I cannot post url's here but if you go to androidsage and search for the LGV10 you should find some useful instructions on how to root the device without unlocking the bootloader first.
Click to expand...
Click to collapse
Hey guys,
ive got to telll you its getting frustrating. There is no way to access the bootloader .. Ive searched for 2 Weeks now. I watched like 100 Videos and read 900 Websites. But everyone says : Now access bootloader , Now access recovery mode. But that doesnt work at all. I think both modes might have been removed from the phone. Because everytime I try to access the bootloader my phone just restarts. And everytime I access the recovery Mode it says: No command . And yes I tried the combinations and adb I tried everything but nothing worked. Please help me

OEM Unlocking issue [SOLVED]

I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.

Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170

depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.

Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?

depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"

geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?

rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.

geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?

rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.

rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.

geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.

geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/

geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net

Huawei p8 bootloader unlocked But oem greyed

Hi everyone.
So I am in a bit of a pickle. I unlocked bootloader and rooted phone few months ago. Phone started playing up. Did not have a backup, I know, stupid me... So had to do official install stock rom straight after booting phone. Another thing to point out, I have lost my unlock bootloader code and huawei have stopped giving them out. Now when I boot in fastboot it's noted as unlocked but the other one think protection something is locked. In developer options oem unlocking is greyed out. Every fastboot command comes back as failed. Tried reflashing twrp and its result is yet again failed. Twrp has gone after the new official rom update. Root has also gone. Any ideas would be really helpful. Tried dc unlocker but it's gone, lol. Thank you everyone.

Unlocking re-locked bootloader

Hello.
Background:
I have re-locked my bootloader in process of recovering my phone from bricked state(I have used service firmware to recover it). But now I can not unlock bootloader again since asus official unlock tool says that there is "unknown network error ... [104]". Asus offical support says that my phone is no more supported and so they are not going to help me.
Question:
Is there any unofficial methods to unlock bootloader? Is it possible to make official unlock app to work again without changing motherboard?
--
Thanks in advance.

p01ar said:
Hello.
Background:
I have re-locked my bootloader in process of recovering my phone from bricked state(I have used service firmware to recover it). But now I can not unlock bootloader again since asus official unlock tool says that there is "unknown network error ... [104]". Asus offical support says that my phone is no more supported and so they are not going to help me.
Question:
Is there any unofficial methods to unlock bootloader? Is it possible to make official unlock app to work again without changing motherboard?
--
Thanks in advance.
Click to expand...
Click to collapse
how did you do to block the bootloader?

hillan821 said:
how did you do to block the bootloader?
Click to expand...
Click to collapse
I have just executed
Bash:
fastboot oem asus-back
without understanding what it does

how to unlock a locked bootloader ! ( oem greyed out )

So i received a american pixel 4 xl with a locked bootloader. imei starting with 35
i was able to unlock the bootloader here is the steps i took, note im in Australia.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
the firmware on the device was american,
i flashed my countrys firmware (australian) optus/telstra/vodaphone etc
use adb side load *firmware.zip*
factory reset , booted device on with australian sim,
and boom oem was available ,
(last step is to adb reboot bootloader,
and ./fastboot flashing unlock and you will see a message on pixel.
intially with the Original firmware on the device it would not unlock.. i tried factory reset
/ fastboot flashing unlock etc and it would not work...
anyhoo i have not seen anything on here suggested flashing another firmware origin so i thought this might help those with locked at&t / verison carriers, intially it was GREYED OUT AND SAID contact carrier or connect to the internet.
Hope this helps someone ! as all the forums ive swiped thru have said this is not do-able, lol turns out it is.

xorrgnlusrx said:
So i received a american pixel 4 xl with a locked bootloader. imei starting with 35
i was able to unlock the bootloader here is the steps i took, note im in Australia.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
the firmware on the device was american,
i flashed my countrys firmware (australian) optus/telstra/vodaphone etc
use adb side load *firmware.zip*
factory reset , booted device on with australian sim,
and boom oem was available ,
(last step is to adb reboot bootloader,
and ./fastboot flashing unlock and you will see a message on pixel.
intially with the Original firmware on the device it would not unlock.. i tried factory reset
/ fastboot flashing unlock etc and it would not work...
anyhoo i have not seen anything on here suggested flashing another firmware origin so i thought this might help those with locked at&t / verison carriers, intially it was GREYED OUT AND SAID contact carrier or connect to the internet.
Hope this helps someone ! as all the forums ive swiped thru have said this is not do-able, lol turns out it is.
Click to expand...
Click to collapse
The firmware does not determine whether the bootloader is unlockable.
When the device connects to the Internet, it checks its IMEI against a whitelist on Google's servers. If it has been authorized for bootloader unlock, OEM Unlocking will become available.
If it doesn't, it's likely that you have a locked variant.

V0latyle said:
The firmware does not determine whether the bootloader is unlockable.
When the device connects to the Internet, it checks its IMEI against a whitelist on Google's servers. If it has been authorized for bootloader unlock, OEM Unlocking will become available.
If it doesn't, it's likely that you have a locked variant.
Click to expand...
Click to collapse
What if it is already unlocked and I want to relock it? I flashed stock firmware, the bootloader is still unlocked but now I can't lock it again because the option is greyed out.

emko7 said:
What if it is already unlocked and I want to relock it? I flashed stock firmware, the bootloader is still unlocked but now I can't lock it again because the option is greyed out.
Click to expand...
Click to collapse
The OEM Unlocking toggle does not lock or unlock the bootloader itself. It simply allows you to unlock the bootloader when enabled.
If you want to relock your bootloader, you do this via ADB while in bootloader mode: fastboot flashing lock

V0latyle said:
The OEM Unlocking toggle does not lock or unlock the bootloader itself. It simply allows you to unlock the bootloader when enabled.
If you want to relock your bootloader, you do this via ADB while in bootloader mode: fastboot flashing lock
Click to expand...
Click to collapse
For some reason I couldn't get into fastboot mode, "adb reboot bootloader" would just restart my device. If I booted into recovery, the "reboot into bootloader" option would just start up the phone. But I eventually found out I can lock the bootloader in download mode