I was looking at a toshiba chromebook 2 but was wondering if you can root a phone on it as i wanted to root my G4.
Sent from my LG-H811 using XDA Free mobile app
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
mrme73 said:
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
Click to expand...
Click to collapse
Is it an easy process? Ive been rooting since 2011 so i can't imagine rooting a chrome book would be too hard?
Sent from my LG-H811 using XDA Free mobile app
I don't think it's that hard but I've only tried it when testing it for a netbook. You will have to search that model as it varies. Usually called developer mode and dual booting with another Linux distribution.
Yes. You just need to enable developer mode, install Arch Linux, disable software verification settings, and obtain adb/fastboot via command prompt (although the versions may or may not be outdated).
kibmikey1 said:
Yes. You just need to enable developer mode, install Arch Linux, disable software verification settings, and obtain adb/fastboot via command prompt (although the versions may or may not be outdated).
Click to expand...
Click to collapse
Hi, I'm trying to flash Marshmallow on my Nexus 7 using my Dell Chromebook. I'm almost there but my N7 says I have to update my ADB to 1.0.32. Unfortunately Ubuntu hasn't updated their repositories so any idea how I can update ADB on my chromebook?
thanks
Sent from my D6503 using Tapatalk
mrme73 said:
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
Click to expand...
Click to collapse
if i do this will it "root" my phone so I can get apps that require root?
Also, I have a galaxy j3 eclipse, will this work on my phone
rickyiswhite said:
I was looking at a toshiba chromebook 2 but was wondering if you can root a phone on it as i wanted to root my G4.
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you can root a phone on a chromebook just put it in developer mode and use your crosh shell to run adb and fastboot.
There is a lack of information and a bit of misinformation here. You don't "root" your chromebook and you don't have to install Arch Linux. So here is the breakdown. If you want to root your phone you can do so by using ADB. To do this you have to do a few things:
1. Enable Developer mode on your chromebook (this requires a powerwash which will delete data and reset your chromebook)
2. Open Crosh by pressing Ctrl + Alt + T
3. Type "shell" and press enter.
4. Update ADB and move the binaries to their appropriate location by typing:
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
5. Make sure ADB is working by typing "adb --version" and pressing enter. This will tell you the version of ADB that is installed, which the current version is 1.0.40 Typing "adb --version" will also tell you where ADB has been installed to. This should say: /usr/local/bin
6. Enable Developer Mode on your phone and enable USB Debugging within the Developer settings.
7. Test that you can communicate with your phone by typing "adb devices" with your phone connected to your chromebook. If your device shows up make sure that you can send data to your phone by typing "adb reboot recovery". This should reboot your device into recovery.
8. If you were able to successfully reboot your phone into recovery using ADB then you have everything you need to root your phone using your chromebook. Just look up how to root your phone using ADB and you will be good to go. This is the method I used to unlock my Bootloader, install a Custom Recovery and the method I used to root my OnePlus 6T with Magisk.
phone not connecting
What do i do if phone does not connect?
how do i put the TWRP.img file into the same folder where the fastboot and adb files are? or how do i type the command to flash it to my oneplus 7 pro in my crosh shell window.
I am able to unlock my boot-loader via adb and and fastboot but cant find away to access the Chromebooks file system to flash twrp and and custom roms. help!!! Im attempting to convert the Moto G7 to a more secure linux rom.
lonnie89 said:
I am able to unlock my boot-loader via adb and and fastboot but cant find away to access the Chromebooks file system to flash twrp and and custom roms. help!!! Im attempting to convert the Moto G7 to a more secure linux rom.
Click to expand...
Click to collapse
On my pixelbook with the beta Linux installed copy the downloadet twrp.img file to the linux folder that's located in the files app. Should then show up in your home Linux directory.
How do I get access to that file system in croots and flash it to the phone.
How do I get access to the file and move to the phone in croots what are the commands. It's my my downloads folder.
garretts228 said:
There is a lack of information and a bit of misinformation here. You don't "root" your chromebook and you don't have to install Arch Linux. So here is the breakdown. If you want to root your phone you can do so by using ADB. To do this you have to do a few things:
1. Enable Developer mode on your chromebook (this requires a powerwash which will delete data and reset your chromebook)
2. Open Crosh by pressing Ctrl + Alt + T
3. Type "shell" and press enter.
4. Update ADB and move the binaries to their appropriate location by typing:
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
5. Make sure ADB is working by typing "adb --version" and pressing enter. This will tell you the version of ADB that is installed, which the current version is 1.0.40 Typing "adb --version" will also tell you where ADB has been installed to. This should say: /usr/local/bin
6. Enable Developer Mode on your phone and enable USB Debugging within the Developer settings.
7. Test that you can communicate with your phone by typing "adb devices" with your phone connected to your chromebook. If your device shows up make sure that you can send data to your phone by typing "adb reboot recovery". This should reboot your device into recovery.
8. If you were able to successfully reboot your phone into recovery using ADB then you have everything you need to root your phone using your chromebook. Just look up how to root your phone using ADB and you will be good to go. This is the method I used to unlock my Bootloader, install a Custom Recovery and the method I used to root my OnePlus 6T with Magisk.
Click to expand...
Click to collapse
Hi. Thanks for a working method. I have tried each step and Crosh gave me error:
bash: /usr/local/bin/adb: cannot execute binary file: Exec format error
One question - do i have to be on "developer channel" in Chromebook?
Coz then i will have to reinstall Chromebook.
Best Regards
Nick
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally yes - i need to be in Developer mode for ADB.
Full article is here - how to and what is what.
How to Use ADB and Fastboot on a Chromebook
For a long time, Chromebook users who also need access to the Android Debug Utility (ADB) and Fastboot for Android devices were left with one option: Crouton. Now, however, both ADB and Fastboot are included in Chrome OS. Here’s how to access them.
www.howtogeek.com
eurovive said:
Finally yes - i need to be in Developer mode for ADB.
Full article is here - how to and what is what.
How to Use ADB and Fastboot on a Chromebook
For a long time, Chromebook users who also need access to the Android Debug Utility (ADB) and Fastboot for Android devices were left with one option: Crouton. Now, however, both ADB and Fastboot are included in Chrome OS. Here’s how to access them.
www.howtogeek.com
Click to expand...
Click to collapse
Sorry I didn't leave that detail behind for you, but yes that method does indeed require dev mode. However there are other methods that don't require it now using Linux. I have not done them so I am only forwarding this information:
https://www.reddit.com/r/chromeos/comments/dtwfpm
Thats a nice suggestion too. As someone says Chromebook should be Intel-ready to run Android apps, thats why i was thinking whats wrong. I have Arm based Tegra K1 with saying some how limited support of updates, therefore having support for Crostini feature. Will try later.
Related
I rooted my AT&T HTC One and when i was going to flash a rom I accidentally wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now.
Please help please help!!!!!!
coachpete said:
i rooted my at&t htc one and when i was going to flash a rom i accidentally wiped the phone completely. I can go into twrp but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a usb otg cable but the phone didnt seem to recognize it. Please help. I've been stuck without a phone for about a week now.
Click to expand...
Click to collapse
can someone please help me!!!!!!
HTC One not recognized by Windows 7 or Windows 8
coachpete said:
I rooted my AT&T HTC One and when i was going to flash a rom I accidentally wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now.
Click to expand...
Click to collapse
I am baby stepping through the trouble shooting process to try to get an image over to the phone so I can reimage through TWRP v2.7.0.0 but neither my Windows 7 machine nor my Windows 8 machine are recognizing the HTC One as a media device. I have tried the updated drivers with no luck. PLEASE HELP!!
coachpete said:
I am baby stepping through the trouble shooting process to try to get an image over to the phone so I can reimage through TWRP v2.7.0.0 but neither my Windows 7 machine nor my Windows 8 machine are recognizing the HTC One as a media device. I have tried the updated drivers with no luck. PLEASE HELP!!
Click to expand...
Click to collapse
you can use ADB from twrp recovery to push a rom to your /sdcard
follow this guide step by step and quote me here if you have question.
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer, either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\android-sdk-windows\tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery (2.6.3.3 or higher) on your device.
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
Here is a list of the HTC M7 roms
Connect your phone to computer using usb cable
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes and there is no progress bar. When the command prompt give you back the hand and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Computer doesn't recognize my HTC ONE
alray said:
you can use ADB from twrp recovery to push a rom to your /sdcard
follow this guide step by step and quote me here if you have question.
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Click to expand...
Click to collapse
Thank you but my computer does not recognize my HTC one. I have tried installing the drivers from various sources but still no go! please help @alray
coachpete said:
Thank you but my computer does not recognize my HTC one. I have tried installing the drivers from various sources but still no go! please help @alray
Click to expand...
Click to collapse
check step 4 of the above prerequisites, click on ''show content'' then you'll find the instruction how to correctly install drivers.
Still no luck with the drivers
alray said:
check step 4 of the above prerequisites, click on ''show content'' then you'll find the instruction how to correctly install drivers.
Click to expand...
Click to collapse
Followed the detailed instructions for downloading and installing the correct drivers and my Windows 7 machine still does not recognize the HTC One correctly.
coachpete said:
Followed the detailed instructions for downloading and installing the correct drivers and my Windows 7 machine still does not recognize the HTC One correctly.
Click to expand...
Click to collapse
boot your phone in twrp, go in windows device manager and take a screenshot and post it here
when your phone is in twrp main menu, open a cmd prompt and do this command:
Code:
adb devices
what is the output?
FINALLY
alray said:
boot your phone in twrp, go in windows device manager and take a screenshot and post it here
when your phone is in twrp main menu, open a cmd prompt and do this command:
Code:
adb devices
what is the output?
Click to expand...
Click to collapse
Thanks for all your help I am now up and running!!!!!!
First and foremost I am not the developer of this App! I just discovered it and thought those of you missing Greenify might find this useful.
[What's Brevent]
There are a lot of apps which claim to prevent apps from running. However, most of them requires ROOT, or do a system modification via Xposed or patching or unlocked bootloader.
Brevent can app-standby or force-stop apps, prevent apps from running in long time. It doesn't require ROOT, nor modify system. Furthermore, it may doesn't work well on ROOT or modified system. There is an experimental feature to start Brevent Server without adb, please read guide - permissions.
Brevent supports Android 5.0 to Android O DP3, requires "USB debugging" in "developer options". I mainly used it on Google Pixel with Android 7.1.2.
[Simple Guide]
0. (Device) open Brevent, read "Guide"
1. (Device) open Brevent, navigate to "Developer Options", turn on "USB debugging"
2. (PC) Download ADB: https://developer.android.com/studio/releases/platform-tools.html
(If you live in China, you can download it here too: https://developer.android.google.cn/studio/releases/platform-tools.html)
3. (PC) Uncompress, navigate to "platform-tools" directory in Command Line, refer to "Guide - ADB"
4. (PC and Device) connect device and PC with usb cable, type "adb devices" in PC Command Line, and confirm the authorized dialog on Devices if needed
5. (PC) type "adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh" in PC Command Line
[FeedBack]
For any issues, please open an issue at github with logs: https://github.com/brevent/Brevent/issues
1. crash log (in PC's command line): adb -d logcat -d -b crash
2. brevent server log (in PC's command line): adb -d logcat -d -b main -s BreventServer BreventLoader
2.1. enable debug for Brevent Server, type in PC's command line: adb -d shell setprop log.tag.BreventServer DEBUG, then get brevent server log
2.2. disable debug for BreventServer, type in PC's command line: adb -d shell setprop log.tag.BreventServer "" (Note for the back slash)
https://play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Alternative To Greenify, Native Feature
ggrant3876 said:
First and foremost I am not the developer of this App! I just discovered it and thought those of you missing Greenify might find this useful.
[What's Brevent]
There are a lot of apps which claim to prevent apps from running. However, most of them requires ROOT, or do a system modification via Xposed or patching or unlocked bootloader.
Brevent can app-standby or force-stop apps, prevent apps from running in long time. It doesn't require ROOT, nor modify system. Furthermore, it may doesn't work well on ROOT or modified system. There is an experimental feature to start Brevent Server without adb, please read guide - permissions.
Brevent supports Android 5.0 to Android O DP3, requires "USB debugging" in "developer options". I mainly used it on Google Pixel with Android 7.1.2.
[Simple Guide]
0. (Device) open Brevent, read "Guide"
1. (Device) open Brevent, navigate to "Developer Options", turn on "USB debugging"
2. (PC) Download ADB: https://developer.android.com/studio/releases/platform-tools.html
(If you live in China, you can download it here too: https://developer.android.google.cn/studio/releases/platform-tools.html)
3. (PC) Uncompress, navigate to "platform-tools" directory in Command Line, refer to "Guide - ADB"
4. (PC and Device) connect device and PC with usb cable, type "adb devices" in PC Command Line, and confirm the authorized dialog on Devices if needed
5. (PC) type "adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh" in PC Command Line
[FeedBack]
For any issues, please open an issue at github with logs: https://github.com/brevent/Brevent/issues
1. crash log (in PC's command line): adb -d logcat -d -b crash
2. brevent server log (in PC's command line): adb -d logcat -d -b main -s BreventServer BreventLoader
2.1. enable debug for Brevent Server, type in PC's command line: adb -d shell setprop log.tag.BreventServer DEBUG, then get brevent server log
2.2. disable debug for BreventServer, type in PC's command line: adb -d shell setprop log.tag.BreventServer "" (Note for the back slash)
https://play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en
Click to expand...
Click to collapse
One of the reasons I rate this phone so highly is that there are plenty of 'native' features present that make rooting less necessary.
My phone is a UK Sky Mobile Exynos model, and under 'Maintenance', 'Battery' there is an option to put 'non running' apps to sleep, just like 'Greenify'. I don't know if this is true for other regions or carrier's. Maybe other people can check this to see if it's so for their region and carrier.
kxdaorbit said:
One of the reasons I rate this phone so highly is that there are plenty of 'native' features present that make rooting less necessary.
My phone is a UK Sky Mobile Exynos model, and under 'Maintenance', 'Battery' there is an option to put 'non running' apps to sleep, just like 'Greenify'. I don't know if this is true for other regions or carrier's. Maybe other people can check this to see if it's so for their region and carrier.
Click to expand...
Click to collapse
I agree with you on the phone but there are two features that I miss with root.
1. Titanium Backup - they ability to back up your apps and data. I know there is Samsung Cloud but I'm not a big fan of cloud based services.
2. TWRP - the ability to back up your whole phone and restore it if needed.
ggrant3876 said:
I agree with you on the phone but there are two features that I miss with root.
1. Titanium Backup - they ability to back up your apps and data. I know there is Samsung Cloud but I'm not a big fan of cloud based services.
2. TWRP - the ability to back up your whole phone and restore it if needed.
Click to expand...
Click to collapse
I get your apprehension about cloud based services, but this is 2017, you'll have to bite the bullet sooner rather than later.
Also don't forget, if you have really super sensitive or personal data that you can't trust to cloud based services, we have 'Smart Switch'. Enables you to make as close to a 'nandroid' backup as is possible, and to store it locally. You can then restore single elements or the whole phone. Thank you Samsung.
kxdaorbit said:
I get your apprehension about cloud based services, but this is 2017, you'll have to bite the bullet sooner rather than later.
Also don't forget, if you have really super sensitive or personal data that you can't trust to cloud based services, we have 'Smart Switch'. Enables you to make as close to a 'nandroid' backup as is possible, and to store it locally. You can then restore single elements or the whole phone. Thank you Samsung.
Click to expand...
Click to collapse
Yes I read a thread yesterday that said you can use Smart Switch and back it up to your sdcard. It's getting better, I started with the T-Mobile G-1 and the only way to root and even do screenshots was with adb. I learned adb and it has served me well on android, even on the S8+ to get rid of the battery icon I had to run a few commands to get SystenTuner UI to work.
Why don't you just use Samsung built in always sleeping option for apps? Works great
Compusmurf said:
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Click to expand...
Click to collapse
If you have rooted, it's not problem.
And if you don't have rooted, no other alternative third-party apps can app-standby other apps or force-stop apps quickly.
I am rooted, but the app doesnt seem to see that I am rooted.
MrPhilo said:
Why don't you just use Samsung built in always sleeping option for apps? Works great
Click to expand...
Click to collapse
I agree, s8 already have functions to put your apps to sleep immediately without waiting 3 days.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G955F using Tapatalk
BratPAQ said:
I agree, s8 already have functions to put your apps to sleep immediately without waiting 3 days.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
how do you get here ?
crayonyes said:
how do you get here ?
Click to expand...
Click to collapse
Settings - Device Maintenance - Battery
Then at the very bottom is "always sleeping apps"
Sent from my SM-G955F using Tapatalk
BratPAQ said:
Settings - Device Maintenance - Battery
Then at the very bottom is "always sleeping apps"
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
got it, Thanks
Where is the experimental feature to start server without adb?
mrQQ said:
Where is the experimental feature to start server without adb?
Click to expand...
Click to collapse
suku_patel_22 said:
I am rooted, but the app doesnt seem to see that I am rooted.
Click to expand...
Click to collapse
]
Compusmurf said:
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Click to expand...
Click to collapse
If you have Root
Just press "back" about 6 times
And then a new menu appears
There you press on "ROOT"....
Hi there,
I recently bought a LG K40s and wanted to unlock the bootloader in order to root this phone. But I could't find any instructions on how to do this nor a fastboot mode for that phone.
Does anyone know how I can get root access on this phone?
Thanks in advance,
Oebbler1
Fastboot: switch off the smartphone by holding the Power button for a couple of seconds. Then connect the Type C USB cable with your PC or laptop. Now push Volume Down and connect this cable with your device. When
hi. I try to root this device but when I use ADB this don´t go to bootloader, the device reboot in normal mode. I look TWRP web and this device isn´t in the list
Any method to root this device?
Regards
Help
we need to create a post to get help to root and install twrp on LG K40s
@jessepinheiro50
To root Android as 1st thing of all things these requirements must be achieved
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next step is to install the USB-driver matching your device
Then check you can access phone from PC via USB
Code:
adb devices
and that boot-loader can get unlocked
Code:
adb shell "getprop ro.oem_unlock_supported"
and if returned value=1 verify that you can deal with phone's boot-loader
Code:
adb reboot bootloader
fastboot devices
Next step is to boot into phone's boot-loader, and unlock it WHAT WILL ERASE ALL DATA ON YOUR PHONE
Code:
fastboot OEM unlock
fastboot reboot
At last step you flash the software that will add root to Android
Code:
adb devices
adb sideload <ROOTING-SOFTWARE-ZIP>
adb reboot
Any news?
Any news on how to root this device?
solve ?
renanflores85 said:
Any news on how to root this device?
Click to expand...
Click to collapse
there is an apk that search for what program can root the current android, and the only it show was stumproot, idk if is safe, i never saw it before, but searching for it, it show that is a root program for lg
jwoegerbauer said:
@jessepinheiro50
To root Android as 1st thing of all things these requirements must be achieved
Next step is to install the
Then check you can access phone from PC via USB
Code:
adb devices
and that boot-loader can get unlocked
Code:
adb shell "getprop ro.oem_unlock_supported"
and if returned value=1 verify that you can deal with phone's boot-loader
Code:
adb reboot bootloader
fastboot devices
Next step is to boot into phone's boot-loader, and unlock it WHAT WILL ERASE ALL DATA ON YOUR PHONE
Code:
fastboot OEM unlock
fastboot reboot
At last step you flash the software that will add root to Android
Code:
adb devices
adb sideload <ROOTING-SOFTWARE-ZIP>
adb reboot
Click to expand...
Click to collapse
this don't worked, it just reboot the phone, and it show 1 when it check if is possible to use boot-loader
letsbrick said:
this don't worked, it just reboot the phone, and it show 1 when it check if is possible to use boot-loader
Click to expand...
Click to collapse
Try
Code:
fastboot flashing unlock
instead of
Code:
fastboot OEM unlock
jwoegerbauer said:
Try
Code:
fastboot flashing unlock
instead of
Code:
fastboot OEM unlock
Click to expand...
Click to collapse
That's not work for me. adb don't identify the device and only wait.
wallrony said:
That's not work for me. adb don't identify the device and only wait.
Click to expand...
Click to collapse
yeah is waiting for any device
So... The problem is that "adb reboot bootloader" doesn't init smartphone in bootloader, but in normal boot process. it's feasible to think about how to "unlock" the "boot of bootloader", since LG may have blocked in this device.
we should create guides in XDA how to install drivers on PC
as this is common hardship for many.
most preferably some autoinstaller of all drivers, for all devices (taken from manufacturers)
indestructible master said:
we should create guides in XDA how to install drivers on PC
as this is common hardship for many.
most preferably some autoinstaller of all drivers, for all devices (taken from manufacturers)
Click to expand...
Click to collapse
No, that's not the problem. Fastboot commands run only when the device's in bootloader device.
So, i solved to persist and search many ways to see something. And that, i got in recovery menu (with Restart System, Wipe, Start ADB sideload - but without connection with PC, as a not connected device, the connection isn't stablished because adbd is a not found command from device shell, in the log returns that, and system wait more or less of 5 minutes to back to recovery menu). In that, i could see the recovery logs, and the last is the normal procedure of a factory reset, i think. In that i encountered some properties that are defined by default:
Code:
ro.boot.flash.locked=1
ro.treble.enabled=true
ro.bootloader=unknown
ro.product.name=mmh551m_f
And by peace of mind, i run
Code:
adb shell "getprop ro.bootloader"
on PC terminal with adb and that returns me the "unknown" that i see in the log. Running
Code:
adb shell "getprop"
returns all prop of the system, so that can be examined to make something. So... I tried to change property using setprop, like ro.boot.flash.locked to 0, or ro.bootloader to any value, but no success.
And to finalize, in contact with LG support whatsapp, the ChatBot returns me a message saying that the bootloader function isn't available by secure reasons.
I think that the value was simply hided from the original value to not access the bootloader, but it's in device ... But with no permission to change the value and not know what value set in the prop.
There are a guide to unlock the boot-loader, but not yet to root.
Root LG K41S + SafetynetAPI pass
Disclaimer These kind of modifications are not for the faint of heart!!! Flash/modify at your own risk!!! I will not be responsible for bricked phones, Dead batteries, world war 3, yada yada yada..... you Know the Rest. :sneaky: Introduction...
forum.xda-developers.com
I followed this process and it doesn't go past the [ fastboot OEM unlock ] step.
I just get < waiting for any device >
However, when I try to use Google Pay and other such apps, I am faced with a security issue.
The question is: Is the bootloader unlocked or not ?
If so, how to relock it ?
Have a device of this wich has a problem with the screen apparently, after changing the screen it wont boot, no battery animation when charger is connected, only a red light and a smooth periodical vibration. If i hold power on and any vol buttons it seems to try boot showing lg logo but fail quicly and keeps off.
Something happened when i repaired it was that side buttons flex got broken so had to order a new one, it passed a lot of time to receive it but i believe that day with broken flex when testing the new screen i think i've seen the battery animation... Im not sure.
But seem its a common issue in this model. So is there something i can do to fix the mainboard?
Since there is no proper information about unlocking the bootloader for the newer versions of Oneplus Nord 2, this is how I got it to unlock and actually work.
For my system it did reset the device, clearing all the files and factory restoring the device, just make sure to make a backup before you do anything.
Just like any other post, no warranties or anything, this is all at your own risk.
1: Make sure to enable OEM unlocking and ADB Debugging in the developer options
1.1: To have these options, first go to About phone > Version
1.2: Keep tapping the "Build number" to unlock the developer options
1.3: Navigate back to settings and open Additional Settings. There you will find the Developer Options.
2: Install: Platform tools: https://androidfilehost.com/?fid=17248734326145690420
3: Install: MediaTek Preloader USB VCOM drivers: https://drive.google.com/file/d/1TPbW-v9-yOrzH15OaHmsPQad420mULeF/view
4: CMD to the root of the platform tools and use the command "adb reboot bootloader"
5: While in the weird tiny screen, validate that your device is there by typing "fastboot devices"
6: If so, type fastboot flashing unlock
7: Profit.
Hope this helps any other people searching for a proper way to do this.
OMG I spent hours searching for a working fastboot driver. Unlocked successfully! I owe you a beer man drop me your paypal
meterpreter said:
OMG I spent hours searching for a working fastboot driver. Unlocked successfully! I owe you a beer man drop me your paypal
Click to expand...
Click to collapse
The cheers is already great, hope they release a working stock rom soon so we can finally have some custom roms going!
Eastw1ng said:
The cheers is already great, hope they release a working stock rom soon so we can finally have some custom roms going!
Click to expand...
Click to collapse
I hope so too. I would really like to put lineage on this thing, probably the only os that can make a usable device out of this actually very good phone
Unlocking the bootloader requires two settings to be made in Android's Developer Options:
ADB Debugging
Allow OEM Unlock
@Eastw1ng, as obvious as this may be once you remember, unlocking the bootloader is something most people don't do very often - it might make sense to include that in the OP
@NetSoerfer, you're not wrong, quickly added it to the start.
I have a issue, Fastboot cant't find mobiledevice in win10. Adb commands working great. Debugging and oem unlock options enabled.
Tried:
1. different usb ports, cables and PC
2. Oneplus, Google and Mediatek USB drivers. With ADB or Bootloader interface.
3. Reinstalling PC USB drivers.
Am i missing out something?
CapnRene said:
I have a issue, Fastboot cant't find mobiledevice in win10. Adb commands working great. Debugging and oem unlock options enabled.
Tried:
1. different usb ports, cables and PC
2. Oneplus, Google and Mediatek USB drivers. With ADB or Bootloader interface.
3. Reinstalling PC USB drivers.
Am i missing out something?
Click to expand...
Click to collapse
use latest platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
HofaTheRipper said:
use latest platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
Hmmm, it worked, I think last one was ver. 30. Last year I downloaded "15 second ADB". It seems it made a mess in my ADB directories. Had to delete few folders and path from win10 Environment Variables. Made new folder and added new path.
I think it is last time when I use some kind "ADB installer".
I wonder if Android Studios didn't come with it automatically? Because I reinstalled that and it didn't work?(it might be that 15 sec installer messed up paths)
CapnRene said:
Hmmm, it worked, I think last one was ver. 30. Last year I downloaded "15 second ADB". It seems it made a mess in my ADB directories. Had to delete few folders and path from win10 Environment Variables. Made new folder and added new path.
I think it is last time when I use some kind "ADB installer".
I wonder if Android Studios didn't come with it automatically? Because I reinstalled that and it didn't work?(it might be that 15 sec installer messed up paths)
Click to expand...
Click to collapse
Can you tell me how to install these drivers I tried but still not detecting
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
X:\Users\XXX>where adb
X:\platform-tools\adb.exe
And system variables
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CapnRene said:
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
C:\Users\Rene>where adb
C:\platform-tools\adb.exe
And system variables
View attachment 5420349
Click to expand...
Click to collapse
I have done all the things still it's not detecting but surprisingly it's detecting my old one plus 6 easily.
On another lappy where I . using zorin os ubuntu based os simple terminal commands installed android platform tool on Linux and I got easily detected Nord with same commands.
But anyway thanks
CapnRene said:
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
C:\Users\Rene>where adb
C:\platform-tools\adb.exe
And system variables
View attachment 5420349
Click to expand...
Click to collapse
Can you tell me twrp given in another thread is working on oos11.3 v10 ?
pankspoo said:
I have done all the things still it's not detecting but surprisingly it's detecting my old one plus 6 easily.
On another lappy where I . using zorin os ubuntu based os simple terminal commands installed android platform tool on Linux and I got easily detected Nord with same commands.
But anyway thanks
Click to expand...
Click to collapse
Have you tried installing these "MediaTek Preloader USB VCOM drivers"? Quite often it's a driver issue and you'll be able to see in the device manager if something's not properly loading the drivers.
pankspoo said:
Can you tell me twrp given in another thread is working on oos11.3 v10 ?
Click to expand...
Click to collapse
It is working for me on v10, just make sure to have the v10 bootloader on hand, it might require a reflash of that after the recovery patch
Eastw1ng said:
Have you tried installing these "MediaTek Preloader USB VCOM drivers"? Quite often it's a driver issue and you'll be able to see in the device manager if something's not properly loading the drivers.
Click to expand...
Click to collapse
Yes installed
Eastw1ng said:
It is working for me on v10, just make sure to have the v10 bootloader on hand, it might require a reflash of that after the recovery patch
Click to expand...
Click to collapse
V10 bootloader means boot.img? If you have that please send me
pankspoo said:
V10 bootloader means boot.img? If you have that please send me
Click to expand...
Click to collapse
You can find the images sakarya posted before: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
pankspoo said:
Yes installed
Click to expand...
Click to collapse
Alright, well just put it into fastboot mode and check your device manager, does it show any devices that are not properly installed? If so, try to resolve it from there
Eastw1ng said:
You can find the images sakarya posted before: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
Click to expand...
Click to collapse
Thanks
So I have a Infinix Note 12 pro 4g x676b. The manufacturer of this model has another model with the same name which is more popular. Now let me get to the point. I wanted to root this phone with magisk. its android 12. I tried a few tutorials for it but i realised i need twrp, but this phone model dosent have a twrp img. So i tried the method of fastboot and adb. i patched my boot.img using magisk and then try to patch it to my mobile using my pc. The adb device gets detected and i get it into fastboot. But in fastboot the device does not get recognized. I tried installing all the drivers but the manufacturer does not provide any. I got every unnofical driver installed but still it dosent detect. And also my phone does not get detected in device manager either in other devices or portable devices. What do i do now?
May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
xXx yYy said:
May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
Click to expand...
Click to collapse
that is not my question tho. My phone does not get recognised on my windows pc
potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is getting recognised as Unknown device?
A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Take note that a phone's Android is rooted if SU is present in Android's filesystem.
xXx yYy said:
A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
Click to expand...
Click to collapse
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread
potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is a driver related problem.
You may be able to get your work done using wireless adb, although flashing stuff wirelessly is very risky (if the connection breaks whilst the flashing is still going on).
mvikrant97 said:
It is getting recognised as Unknown device?
Click to expand...
Click to collapse
not even an unknown device just nothing is there
potatosil said:
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread
Click to expand...
Click to collapse
To root a phone's Android Fastboot isn't needed as you suppose : ADB is the correct tool.
Most people instead of adb.exe what comes with Android SDK use adbLink2 app what provides a link between your Android device and your computer.
adbLink2 features:
Install Programs without Android SDK
ADB/Fastboot enabled command-line
Busybox for root and non-root
Built-in WIFI/USB remote
Manage devices via USB or IP address
Root-aware File Manager for Android devices
Install/Uninstall Apps
Connect to devices ad hoc
Manage multiple devices from one PC
Edit XML and other files on your devices
Log file viewer for adbLink2
Hyperlinked HTML Help
adbLink2 is available for Windows, macOS and Linux/ChromeOS
BTW to clarify things, you obviously don't know of:
1.
Before I define root, it's important to understand why it exists and how it works. It's because Android uses permissions ( Linux-based permissions, to be exact ) in the file structure. Every file, every folder and every partition has a set of permissions. These permissions decide who can read a file ( look at or access the contents without changing them ), write to a file ( be able to change the contents of that file, or create a new file inside a folder or partition ) and execute a file ( run the file if it's a type that can run, like an app ). This is done based on users and permissions - certain users have access, while users who don't have the right permissions are blocked from having access.
When you first set up your phone and turn it on for the first time, you are assigned a user ID. If another user logs in via Google, they are assigned a different user ID. When an app is installed on your phone, it's also assigned a user ID of its own. The system itself is a user and other processes that need to run on your phone may have their own user ID. Everything that can do anything to any files on your Android is a user.
2.
To get elevated permissions ( root access ) you place the SU binary ( SubstituteUser ) in a spot that it can run when it's called to run - that's called a PATH - e.g /data/local/tmp. If any app is in user ID's PATH it will run without telling the system exactly where it is. You also need to make sure the SU binary is in a spot that your user ID has permission to execute ( run ) files. Any other app ( Google Play has plenty of apps that need root permissions ) will also need the same access. When you use a method to root your phone, all this is sorted out by the folks who built the root method.
3.
This is where root comes in. The SU binary uses flags when it's run to tell the system what user ID you want to switch to. For example, if I run the SU binary on my Google Pixel phone like this "su Jim -c 'mount - o rw,remount -t auto /system'" I will run the mount command as the user Jim ( after supplying Jim's password ). If I run the SU binary with no flags or arguments, it switches me to the root user. Normally you would need to supply a password, but since "root" is an unused user on Android it has no password. Running the command "su" will switch you to the user root, and assign you the user ID of 0, and put you in the root group. You are now the Super User.
4.
As the Super User you can do anything to any file, folder or partition on your Android. By anything, I mean literally anything. You can remove bloatware apps and you can also remove essential system files that break your phone. You can also do things to the hardware like change the CPU frequency and ruin your phone forever.