Database Users

[Q] What recovery are you guys using?

They all seem broken so far. cwr has no working adb sideload, and twrp wont restore on 2.4x

trentreed said:
They all seem broken so far. cwr has no adb sideload, and twrp wont restore on 2.4x
Click to expand...
Click to collapse
If you are using the correct and most up to date version of CWM (6.0.2.3), then adb sideload is certainly present.

JaiaV said:
If you are using the correct and most up to date version of CWM (6.0.2.3), then adb sideload is certainly present.
Click to expand...
Click to collapse
Present yes, working no. If you run adb sideload then adb devices its mounting it as recovery.
Sent from my Nexus 7 using xda premium

Twrp was updated to fix the recovery issues

trentreed said:
Present yes, working no. If you run adb sideload then adb devices its mounting it as recovery.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If you are getting the 'Error: Closed' problem this is common and relatively simple to fix.
For example:
Code:
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXXXXXXXX recovery
C:\adb>adb sideload cm-10.1-20130228-NIGHTLY-mako.zip
error: closed
C:\adb>adb usb
restarting in USB mode
C:\adb>adb devices
List of devices attached
XXXXXXXXXXXXXXXXXX sideload
C:\adb>adb sideload cm-10.1-20130228-NIGHTLY-mako.zip
Sending: 'sideload' 4%

JaiaV said:
If you are getting the 'Error: Closed' problem this is common and relatively simple to fix.
For example:
Code:
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXXXXXXXX recovery
C:\adb>adb sideload cm-10.1-20130228-NIGHTLY-mako.zip
error: closed
C:\adb>adb usb
restarting in USB mode
C:\adb>adb devices
List of devices attached
XXXXXXXXXXXXXXXXXX sideload
C:\adb>adb sideload cm-10.1-20130228-NIGHTLY-mako.zip
Sending: 'sideload' 4%
Click to expand...
Click to collapse
Interesting, all I ever got to was adb side load then adb devices and it showed recovery. I stopped right there I'll have to give that a shot. Wish he would just fix it
Sent from my Nexus 7 using xda premium

ceejay83 said:
Twrp was updated to fix the recovery issues
Click to expand...
Click to collapse
2.4.3.0 and 2.4.2.1 both would not restore for me
Sent from my Nexus 7 using xda premium

TWRP is where its at. Restore works fine for me.

zephiK said:
TWRP is where its at. Restore works fine for me.
Click to expand...
Click to collapse
What version are you on?
Sent from my Nexus 7 using xda premium

I would recommend against using TWRP, I was for a while and after numerous updates I felt I was running alpha/beta software with all the bug fixing releases and subsequent bugs caused by those fixes. Use CWM, it's safer. I'm happy to run unstable software on my device anywhere but the main three: bootloader/radio/recovery.
Don't believe me about the instablilty, just read the last few pages of the TWRP thread.

negroplasty said:
I would recommend against using TWRP, I was for a while and after numerous updates I felt I was running alpha/beta software with all the bug fixing releases and subsequent bugs caused by those fixes. Use CWM, it's safer. I'm happy to run unstable software on my device anywhere but the main three: bootloader/radio/recovery.
Don't believe me about the instablilty, just read the last few pages of the TWRP thread.
Click to expand...
Click to collapse
I'm with you, thanks for the input

Been using twrp for a while without any issues.

Much prefer TWRP myself. I've had no issues although I don't use it daily or anything.
Sent from my Nexus 4 using Tapatalk 2

Tips and Tricks [Google Pixel] (sailfish)

New device new rules/tricks
The main purpose for this thread is to post info that doesn't real justify it's own thread.
Most of what is posted is what interests me, usually in no particular order.
If you think something is missing, please share (include links or as much info you can)
General Info
Index
Have a question? Please consider asking in the
Help Thread
How to Check if you have a Verizon or Google Model from CID info
Custom Recovery info
FAQs
USB Drivers
Using ADB and Fastboot commands
Unlocking the Bootloader
Rooting
WiFi Tether
Installing new security update with fastboot.exe for a bootloader-unlocked Pixel
[GUIDE] Restore to stock after soft BRICKED Written for XL version, but a good reference
Set/Change Active System Partition with Fastboot Command in Bootloader Mode
[Re]Activate Google Voice on Pixel
46 Google Pixel XL & Google Pixel Tips and Tricks (www.droidviews.com)
https://www.androidpit.com/google-pixel-tips-and-tricks

USB Drivers for using ADB/Fastboot commands
If using Mac or Linux drivers should not be an issue.
If using Windows 10 correct drivers should already be installed but you likely will need to select them in Device manager
If drivers are correct the Pixel should be listed in Device Manager as
Android Phone
adb composite interface
An easy way to install correct drivers on a Windows PC is using
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05
Official Google Drivers

Unlocking the Bootloader - 06 Nov 2016
If it's a pure Google device just run
Code:
fastboot oem unlock
If you bought the Pixel from Verizon, Best Buy.... dePixel8 method will be required to unlock the bootloader
Note: Verizon, Build Version NDE63X, Nov 2016 can be unlocked,Builds after that cannot.
Using dePixel8
Be sure Drivers are correct
Change screen timeout to 30 mins in settings/display options
Enable Developer Options
In Settings/About Phone >Tap build version until it says "you are developer"
go back to main Settings screen
Open Developer Options
Enable ADB Debugging (in Developer Options)
Be sure ADB and Fastboot commands are working
Download dePixel8
Run in Command prompt
Code:
adb push dePixel8 /data/local/tmp
Code:
adb shell chmod 755 /data/local/tmp/dePixel8
then
Code:
adb shell /data/local/tmp/dePixel8
when you see
Code:
[+] getting there, about 20 more seconds please
open the Chrome app on the phone
then you should see
Code:
[+] done
[+] rebooting your device to bootloader mode
[+] run "fastboot oem unlock" to unlock your bootloader
[+] P.S. Pixel is made by HTC, and dePixel8 was made by beaups
[+] cheers jcase - copyright Streamlined Mobile Solutions, LLC
Discussion Thread: BL unlock for Verizon Pixel just released by murryrulz
Do not relock the bootloader
[PSA] Read before relocking your bootloader by jcase

Rooting
Requires Unlocked Bootloader
[ROOT] SuperSU by Chainfire

Hotspot/WiFi Tether
Hotspot should work out of the box for most data plans except Unlimited Data plans
Verizon Unlimited Data Plans
Rooted method
Make sure your bootloader is unlocked and you are rooted.
Instal a Root File Manager (Root Browser / ES File Explorer)
enable root access in File Manager (it's off by default in some)
browse to /System > Long press build.prop > Open in Text Editor
Scroll all the way to the bottom. Type in "
Code:
net.tethering.noprovisioning=true
.. Then save and exit. Reboot the phone and you're good to go.
Discussion Thread: Pixel Hotspot by polo2883
[Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks. by Fenny
http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
Non Root method
Verizon native tether subscription bypass A Pixel XL thread
Sprint WiFi Tethering Thread
[ROOT/Guide] Native Hotspot Working by stuntnmore A Pixel XL thread

Setting up and Using ADB/Fastboot (Android Debugging Bridge)
For Mac or Linux: see Can ADB/Fastboot be used on Linux and Mac?
Setting up ADB/Fastboot (Windows)
[Index] Setting up and Using ADB/Fastboot
Using ADB/Fastboot
adb commands are used in normal boot/OS or in Recovery
fastboot commands are used in fastboot/bootloader mode
Set/Change Active System Partition with Fastboot Command in Bootloader Mode
Code:
Fastboot set_active _a
Code:
Fastboot set_active _b

Installing new security update with fastboot for a bootloader-unlocked Pixel.
Note: This is a work in progress, but it should be correct.
Even if it works for the Nov update, it may need to be written for future updates
Problem:
If you have modified the stock firmware (hosts file, root, kernel, etc.), the OTA update likely will fail
Solution:
This does not factory reset, user apps and data are not removed.
This will remove your custom kernel/root/hosts/recovery...
Install Verify Drivers
see post #2
Setup ADB.exe see
[Index] Setting up and Using ADB/Fastboot
[INFO] How I restored to stock after soft bricking, then flashed new kernel & rooted by CZ Eddie
Download the system image for Sailfish (Pixel) from google
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
Unzip the file
Unzip xxxxxxnde63v.zip from inside the new directory/folder
Copy files to same folder as adb.exe files (unnecessary if adb is setup as global)
Open open Command Prompt (with same directory path as firmware files)
Reboot into bootloader
Code:
adb reboot bootloader
or
Power off, Hold volume down button, power on
check your boot slot (_a or _b) and following line may need to be adjusted?
Code:
system_b system_other.img
Execute fastboot commands
Code:
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
Custom Kernel, Root, and other mods will need to be reflashed
Credit
[GUIDE] Update with fastboot by @firewave

Custom Recovery
Twrp links
TWRP RC1 for Pixel Devices
https://plus.google.com/+DeesTroy

Thanks a lot for this thread. Very helpful for updating my pixel. Have linked it a few times to help out. This thread should be stickied.

GeekMcLeod said:
Thanks a lot for this thread. Very helpful for updating my pixel. Have linked it a few times to help out. This thread should be stickied.
Click to expand...
Click to collapse
Thanks, hope it helps.
It is linked in the index

sd_shadow said:
check your boot slot (_a or _b) and following line may need to be adjusted?
Code:
system_b system_other.img
Click to expand...
Click to collapse
To be clear, you want the one used to match the one you're currently set to right? (My bootloader specifies boot slot a.)

sturmeh said:
To be clear, you want the one used to match the one you're currently set to right? (My bootloader specifies boot slot a.)
Click to expand...
Click to collapse
I did it the other way. System other seemed like it shouldnt be your boot slot. I updated it already and it's working so I think I got it right.

GeekMcLeod said:
I did it the other way. System other seemed like it shouldnt be your boot slot. I updated it already and it's working so I think I got it right.
Click to expand...
Click to collapse
so boot slot was a in bootloader?
you use b command?
is it now b in bootloader?
Sent from my XT1254 using XDA Labs

the Pixel has 2 system slots/partitions,
in theory you could have 2 different roms to choose from, that maybe an option in a future version of twrp
Sent from my XT1254 using XDA Labs

sd_shadow said:
so boot slot was a in bootloader?
you use b command?
is it now b in bootloader?
Sent from my XT1254 using XDA Labs
Click to expand...
Click to collapse
No, my bootloader still says my bootslot is a.

GeekMcLeod said:
No, my bootloader still says my bootslot is a.
Click to expand...
Click to collapse
thanks, sounds good
Sent from my XT1254 using XDA Labs

new
[Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks. by Fenny
http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
Sent from my sailfish using XDA Labs

I just tried reverting to stock and my phone is stuck in a bootloop and then eventually gets stuck on dead android with No command text. I followed all directions to the dot and I'm on boot slot b. Any ideas?
---------- Post added at 11:04 AM ---------- Previous post was at 10:43 AM ----------
Ok so I followed GeekMcLeod's advice about flashing system-other to the opposite partition. Since I was on boot_b I change the line in the OP to flash system_a and now my phone is booting. @sd_shadow I'm not sure if this is the case for everyone.

Just a short story about my experience so far with the Pixel.
When i first got my device it wanted to update. I let it update (OTA) and rebooted. Once that was done, I unlocked the bootloader, booted TWRP flashed it, rebooted TWRP and then flashed root. All was awesome, I went to reboot and noticed that TWRP shows which boot slot you're in (I was in B). I rebooted anyway and everything works as expected.
I was curious, so I booted back into TWRP, went to reboot and changed the boot slot to A, got an error but checked it again and it shows I was in fact in boot slot A. So i rebooted... it booted into non rooted, pre update android... so it looks to me that this seamless update system applies the update the opposite partition that your in. So if you're in A and take an OTA it applies it to B and then reboots into B (updated) and the opposite will happen if you take the OTA while in B. All apps and data you've collected is shared with either system partition.
So, in theory we could take the OTA as long as we flash the recovery and (possibly) boot images before downloading and applying it. We would only have to flash TWRP and root again.
And I agree, it looks like we should be able to dual boot two different ROMS, maybe even kernels without too much messing around.
I'm sure this is not new news but I just wanted to share and maybe someone will correct me or learn from it.

thanks for the replies, good stuff
Sent from my sailfish using XDA Labs

Root / Rom for Samsung Galaxy J3 Tellus SM-J320W8

Having trouble finding anything for this specific model, thank you for helping!

i would love even just an older firmware file :S

magik20 said:
Having trouble finding anything for this specific model, thank you for helping!
Click to expand...
Click to collapse
You can probably root but there are no custom recoveries or ROMs for this device yet. There won't be any until a developer with the knowledge actually gets one of these devices and that probably won't happen because the REAL developers own and build for the more popular and high end devices.
You'll probably get custom recovery and ROMs quicker if you learn to build them or port them for yourself. Sad, but true.
bilalwiggles said:
i would love even just an older firmware file :S
Click to expand...
Click to collapse
Sent from my SCH-I535 using Tapatalk

Is there a root of there is plz put a link I having trouble finding a root

Please root or twrp
Sent from my SM-J320W8 using XDA Labs

Vee89 said:
Please root or twrp
Click to expand...
Click to collapse
Does this device have a locked bootloader?

Not shure
Sent from my SM-J320W8 using XDA Labs

Vee89 said:
Not shure
Sent from my SM-J320W8 using XDA Labs
Click to expand...
Click to collapse
Then do a search for:
"How to check bootloader status on android"
This will give you different methods to check.
Learn to search instead of being lazy waiting for someone to do the thinking and the work for you. If you want to do this then get off your but and get busy finding answers.
You are the one that wants to do this to your device, not us, if it's what you really want then you'll do whatever it takes, if you don't then it means you didn't really want it in the first place.
You'll get TWRP faster if you learn to port or build your own, many new members that can't find anything for their device end up building their own TWRP, it's not that complicated.
Sent from my SM-S903VL using Tapatalk

Its locked
Sent from my SM-J320W8 using XDA Labs

Vee89 said:
Its locked
Sent from my SM-J320W8 using XDA Labs
Click to expand...
Click to collapse
Then you can't use TWRP unless you get it unlocked.
Before you ask how to do that, search first for yourself how to unlock bootloader on your model number.
If it can't be unlocked then you are out of luck with using custom ROMs, there are a lot of devices that can't be unlocked or use custom ROMs. In the future, research your devices before you buy them, that way you know whether it has custom support before you buy it. Then you won't be stuck with a device that has nothing available.
Sent from my SM-S903VL using Tapatalk

Vee89 said:
Its locked
Click to expand...
Click to collapse
Do you have the stock boot image from the stock firmware?

No
Sent from my SM-J320W8 using XDA Labs

Phone rooted check here :
BR,
[email protected]

ashyx said:
Do you have the stock boot image from the stock firmware?
Click to expand...
Click to collapse
How could I get the stock image? I really would like to root my device but it seems this model is a lost cause in most cases, I softbricked my device once by using a different models IMG to root mine, but i fixed it.

DemandingZ said:
How could I get the stock image? I really would like to root my device but it seems this model is a lost cause in most cases, I softbricked my device once by using a different models IMG to root mine, but i fixed it.
Click to expand...
Click to collapse
Did you try the video posted above?
Sent from my SM-S903VL using Tapatalk
---------- Post added at 09:42 PM ---------- Previous post was at 09:22 PM ----------
[email protected] said:
Phone rooted check here :
BR,
[email protected]
Click to expand...
Click to collapse
The done supports devices,with unlocked bootloader, if this device has an unlocked bootloader then custom recovery would be the best way to root and it wouldn't cost anything or require using any potentially questionable hardware or software. That's just my opinion though.
Sent from my SM-S903VL using Tapatalk

DemandingZ said:
How could I get the stock image? I really would like to root my device but it seems this model is a lost cause in most cases, I softbricked my device once by using a different models IMG to root mine, but i fixed it.
Click to expand...
Click to collapse
I'm still waiting for a response on this
https://forum.xda-developers.com/showpost.php?p=72585838&postcount=145
It seems not all J320w8 models are equal.

I really need the boot twrp for sm-j320w8 its network is unlocked i flashed it bricked it 3 times n now its killing me that i cant please send a link n i will send 25cash paypal thank you [email protected]

magik20 said:
Having trouble finding anything for this specific model, thank you for helping!
Click to expand...
Click to collapse
I think it's possible to do it via open shell adb in cmd.exe using the specific commands .. unlock the bootloader is done with fastboot in cmd under windows or in a linux terminal.
.
ADB: (android debug bridge)
adb devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
adb reboot - restart your phone normally
adb reboot recovery - restart your phone in recovery mode
adb reboot bootloader - restart your phone in bootloader mode (fastboot)
adb shell - allows to explore the phone, knowing that Android is based on linux you need to know the linux commands
adb remount - remount the system partition of the phone, you can then read and write
adb push xxx yyy - copy the xxx file from the computer to the yyy file / folder on the phone (root rights required)
adb pull xxx yyy - copy the phone's xxx file to the yyy file / folder on the computer (root rights required)
fastboot:
fastboot devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
fastboot reboot - restarts your phone normally
fastboot oem unlock - unlocks the bootloader
fastboot erase xxx - erases the xxx partition (userdata, cache, etc ...)
fastboot flash xxx yyy - flash the xxx partition with the yyy image

DroidShell said:
I think it's possible to do it via open shell adb in cmd.exe using the specific commands .. unlock the bootloader is done with fastboot in cmd under windows or in a linux terminal.
.
ADB: (android debug bridge)
adb devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
adb reboot - restart your phone normally
adb reboot recovery - restart your phone in recovery mode
adb reboot bootloader - restart your phone in bootloader mode (fastboot)
adb shell - allows to explore the phone, knowing that Android is based on linux you need to know the linux commands
adb remount - remount the system partition of the phone, you can then read and write
adb push xxx yyy - copy the xxx file from the computer to the yyy file / folder on the phone (root rights required)
adb pull xxx yyy - copy the phone's xxx file to the yyy file / folder on the computer (root rights required)
fastboot:
fastboot devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
fastboot reboot - restarts your phone normally
fastboot oem unlock - unlocks the bootloader
fastboot erase xxx - erases the xxx partition (userdata, cache, etc ...)
fastboot flash xxx yyy - flash the xxx partition with the yyy image
Click to expand...
Click to collapse
Irrelevant copy and paste info for Samsung devices.

[guide] how to root T-Mobile version V530

Credit goes to @Vincent_vann for offering original and patched boot image
Prerequisite:
You should have ADB installed
LG unified driver 4.2.0 or later installed
USB cable and battery should be at least 60%
Bootloader unlocked
Code:
fastboot oem unlock
Data should be backed up
USB debug should be enabled and your host computer is allowed
Patched boot image downloaded https://mega.nz/#F!zLIkzbwY!-sPXZvcv30t6oxyuOqdFfg
Steps
1. Plug your tablet to your host computer.
2. Open your command prompt and locate your ADB folder and enter the following
Code:
adb devices
You should see your device
3. Go to bootloader
Code:
adb reboot bootloader
If you have not unlocked bootloader, do it now
Warning: your data on the tablet will be wiped!!!
Code:
fastboot oem unlock
4. Flash your boot image. Locate the folder where the patched_boot.img is
Code:
fastboot flash boot
make sure you have pressed a space. Drag and drop the patched boot into the command prompt and press Enter. It should say OK
5. Restart
Code:
fastboot reboot
6. Make initial setup, enable developer option again and USB debug, and enable unknown source in Security Settings
7. Download and install Magisk Manager, and upgrade when necessary.
8. Your tablet is rooted.

How much can we expect to speed this tablet up with just root?

@mingkee, thanks for the tutorial. Finally got around to doing it. All good.
For Magisk, do we use it as a basic root or can modules be used. Haven't done anything on it yet (powered off and charging).
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3

marcdw said:
@mingkee, thanks for the tutorial. Finally got around to doing it. All good.
For Magisk, do we use it as a basic root or can modules be used. Haven't done anything on it yet (powered off and charging).
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
Click to expand...
Click to collapse
I have not added other module.
I root this table so I can install CF.Lumen to fix that muddy tint.

Ahh thanks for this!! I haven't had root in any device for awhile. hoping for twrp soon. Let me know if I can assist in any way!

These instructions are not fully understandable please advise after step 4. Flash your boot image. Locate the folder where the patched_boot.img is
Code: fastboot flash boot this is very very vague please give more information on how this is setup some people have ADB and ANDROID installers installed. You need to fix the steps please.
Ice

ice5192 said:
These instructions are not fully understandable please advise after step 4. Flash your boot image. Locate the folder where the patched_boot.img is
Code: fastboot flash boot this is very very vague please give more information on how this is setup some people have ADB and ANDROID installers installed. You need to fix the steps please.
Ice
Click to expand...
Click to collapse
Yeah, that does sound kind of odd.
What it means is type in (no quotes) "fastboot flash boot " ( note the space after) and then you are to drag the patched_boot.img file into the cmd window to complete the line.
Not necessary if the file is in the same directory as fastboot. So full line is
"fastboot flash boot patched_boot.img"
I too had to reread that line of instruction a couple of times.
LG G3 D851, CyanogenMod CM12.1 ROM, Fechda R7 Kernel, MultiROM, Tapatalk 4.9.5

Is anyone using TWRP? What version?

I've tried it and not getting anywhere.
adb devices - shows the tablet
fastboot devices - shows nothing connected
fastboot oem unlock - <shows waiting on any devices>
anyone else run into this?

beymapwrd said:
I've tried it and not getting anywhere.
adb devices - shows the tablet
fastboot devices - shows nothing connected
fastboot oem unlock - <shows waiting on any devices>
anyone else run into this?
Click to expand...
Click to collapse
Did you install the LG driver's? Happened to me because I forget to install the LG unified drivers. Link in OP
Sent from my [device_name] using XDA-Developers Legacy app

Some one created Twrp for our tablets, but I can't figure out why when I try to reboot into it , it goes to the fastboot screen...anybody??

Drivers installed, had to run first:
adb kill-server
adb start-server
then the rest of the commands..

coolchris305 said:
Some one created Twrp for our tablets, but I can't figure out why when I try to reboot into it , it goes to the fastboot screen...anybody??
Click to expand...
Click to collapse
where did you get the twrp from i cant find it anywhere i see other models but not lg v530

itzmehotsauce said:
where did you get the twrp from i cant find it anywhere i see other models but not lg v530
Click to expand...
Click to collapse
Download twrp builder...but even then i still can't boot into it...

coolchris305 said:
Download twrp builder...but even then i still can't boot into it...
Click to expand...
Click to collapse
well i got it rooted withthe method from this thread but when i go into rootchecker it says its not rooted im guessing its because i dont have su installed but i cant install the su without twrp if im not mistaken so im a bit confused its been a while since i rooted anything

itzmehotsauce said:
well i got it rooted withthe method from this thread but when i go into rootchecker it says its not rooted im guessing its because i dont have su installed but i cant install the su without twrp if im not mistaken so im a bit confused its been a while since i rooted anything
Click to expand...
Click to collapse
Yeah. Rootchecker confirms I have root on mines

I've run into the same issue. The image seemed to have been flashed, but whenever I try to boot into recovery it just goes to fastboot (bootloader).

Canadian Variant
Anyone know if there's any general rule to modifying stuff to work with other models? Other than build.prop edits to v533 instead of v530 I'm at a loss, and I'm guessing the boot image is specific to T-Mobile variants..
There's gotta be a way to work off this framework, but again I've got no idea, and it may be way beyond my skill level

So I've had this tablet since March but really haven't used it much. My question is once I root it using your written guide do you recommend a app to use for getting Free Hotspot Tether on it? I am a 11 year tenure TMO Customer & have a legacy grandfathered rate/data plan.
Even tho my data plan says I have unlimited hotspot tether it is blocked by TMO. I have reached out to T-Mobile on Twitter & even the executive resolutions team of the president office but they just said that at one point it was allowed but that TMO took it away for whatever reason.
So rather than fighting tthem further or getting the FCC or FTC involved for false advertising I figured I'll just use an app once rooted to bypass root. Just wondering if anyone knows what is the best app to use to achieve this once rooted. Thank you very much & have a wonderful day!! ?
All the best,
Ron.
---------- Post added at 04:13 PM ---------- Previous post was at 04:09 PM ----------
mingkee said:
Credit goes to @Vincent_vann for offering original and patched boot image
Prerequisite:
You should have ADB installed
LG unified driver 4.2.0 or later installed
USB cable and battery should be at least 60%
Bootloader unlocked
Code:
fastboot oem unlock
Data should be backed up
USB debug should be enabled and your host computer is allowed
Patched boot image downloaded https://mega.nz/#F!zLIkzbwY!-sPXZvcv30t6oxyuOqdFfg
Steps
1. Plug your tablet to your host computer.
2. Open your command prompt and locate your ADB folder and enter the following
Code:
adb devices
You should see your device
3. Go to bootloader
Code:
adb reboot bootloader
If you have not unlocked bootloader, do it now
Warning: your data on the tablet will be wiped!!!
Code:
fastboot oem unlock
4. Flash your boot image. Locate the folder where the patched_boot.img is
Code:
fastboot flash boot
make sure you have pressed a space. Drag and drop the patched boot into the command prompt and press Enter. It should say OK
5. Restart
Code:
fastboot reboot
6. Make initial setup, enable developer option again and USB debug, and enable unknown source in Security Settings
7. Download and install Magisk Manager, and upgrade when necessary.
8. Your tablet is rooted.
Click to expand...
Click to collapse
Hello would you happen to know of a app to use with this to get Free Hotspot Tether for TMO once I Root it. Hotspot is currently blocked on my legacy grandfathered data plan even tho my plan shows I have unlimited hotspot tether.
So rather than fighting T-mobile regarding this I figure I'll just root & use an app to get my free hotspot tether back. Thank you very much & have a wonderful day!! ?

@QkTreasures, I use WiFi Tether Router. Had it a few years. It works for the most part. Sometimes I can go hours tethering without using my hotspot data but there's been a time or two where it didn't hide the tethering.
LG G3 D851, PAC-MAN LP ROM, MultiROM, XDA Legacy

Lg v20 h91820h t-mobile bootloader cannot be unlocked - android 8 oreo

UPDATE:
I successfully unlocked the bootloader, flashed twrp, rooted, updated kernel and roms, tweaking gpu cpu for performance in pubg etc, greenify, flashify, power nap everything.
xposed framework take you in bootloop for this device.
now i am on kernel mk2000, superv20 rom, h91810u, 7 nougat.
if in future anyone feels any problem i am always here.
remember: linus is your friend for this device, and windows 10 suck.
and
sudo $(which fastboot) did miracles for me....
old post:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.

X_BlackBurn_X said:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.
Click to expand...
Click to collapse
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk

Thanks for thanks for replying on a short notice I have seen this post there is no reason to follow any of the post because the very first stage is to unlock the bootloader but as I cannot unlock the bootloader there is no point in following any of the posts my problem is what ever way I follow I am unable to to unlock the bootloader in fact what I can see is whenever I try to type in command ADB devices IC e my phone but when I type fastboot devices nothing happens it's like my phone is not in the fastboot that is why why I cannot unlock the bootloader I have tried every possible step mentioned on the internet and on various forums I also go through some videos on YouTube those guys follow the same steps and unlock their bootloader but my device cannot unlock for some reason so if you lovely people can help me out and figure out what exactly I am doing wrong as I have followed every step of unlocking the bootloader I've installed all the drivers I have updated all the drivers I have done exactly e all three steps which has been asked but still no luck thank you

clsA said:
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards

X_BlackBurn_X said:
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards
Click to expand...
Click to collapse
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.

C D said:
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.
Click to expand...
Click to collapse
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.

X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
...
(bootloader) ----------------------------------
(bootloader) Device-ID
(bootloader) F3D7DE171C893D55082EAE38270125EF
(bootloader) DA7CB3E78B1DB5709A2CA8********
(bootloader) ----------------------------------
OKAY [ 0.060s]
finished. total time: 0.060s
D:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.008s
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot getvar unlocked
unlocked: no
finished. total time: 0.003s
Click to expand...
Click to collapse

X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
As clsA said, flashing firmware does not require an unlocked bootloader.
Look at parts 1 and 2 of the other step by step guide here:
https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258

clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.

X_BlackBurn_X said:
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.
Click to expand...
Click to collapse
No problem the link @C D posted above seems to have all the working links for you

clsA said:
No problem the link @C D posted above seems to have all the working links for you
Click to expand...
Click to collapse
well we have a new problem now.
lgup error 0x2bc invalid command response code = 0x80000202 at 4 percent while flashing.
did i just brick my phone now ? as it says dont unplug until you are done and we have been getting same error again and again.
used the provided kdz file flashing as an upgrade.

ok so the new problem is... may be i was trying to flash h91810p naugaut on to a oreo h91820h
and if i am not wrong at this stage i messed up pretty bad my phone is stuck in donwload mode wont boot up and i need to flash back 20h again to get out of this mess. can anyone hlp me ....
i just wanna know h91810p downgrading from 91820h is possible or not ? cause one is naugaut and one is oreo.

UPDATE:
i was flashing wrong h91810p thats why it was showing error. on another website i got the file compatible to my phone t mobile version and flash was successful.
now i am on h91810p software version andriod 7.
problem UPDATE:
i still cant unlock bootloader. same problem as before downgrading from h91820h.
adb devices shows device.
adb reboot bootloader
fastboot devices gives no result.
phone cannot enter in fastboot mode. the problem still remains the same even after changing the software.
kindly help guys

clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.

NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.

X_BlackBurn_X said:
NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.
Click to expand...
Click to collapse
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.

C D said:
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.
Click to expand...
Click to collapse
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards

X_BlackBurn_X said:
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards
Click to expand...
Click to collapse
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk

clsA said:
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
thanks again for the showing me the right direction. i was talking about unlocking the bootloader in step 1.
i will go through your links and try to study this.
just one more question.
does this method unlocks the bootloader ?
if yes please reply yes i will be thankful to you.
i will follow this step now.
regards

X_BlackBurn_X said:
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.
Click to expand...
Click to collapse
Why does adb show your device as a 997 which is the Sprint variant
Sent from my LG-H910 using XDA Labs