Develop Bugs

[Q] Hard Bricking

What are the odds of hard-bricking the Nexus 7 while rooting and istalling a custom kernel? And if it bricks, is there a way to fix it?
I ask this because I want to root it, but I'm really worried.
Also, how can you fix a soft brick?

I think you should really care of these questions if you somehow corrupt both bootloader and recovery. I don't really know, but bootloader isn't a thing that is modified during rooting or changing kernel. Just carefully read the thread about rooting programs, follow the instructions and everything should be ok. The most potentially harmful thing that can be done is corrupting the recovery. It can be solved if you have a computer with adb and drivers installed. Just a sшmple command and recovery is reflashed. Unlocking the bootloader is a kind of thing that doesn't really change anything so you couldn't boot or something. It just clears the storage and changes something deep inside. Flashing ROMS/Kernels is a kind of coping files and if something goes wrong you can always reflash it from recovery or with adb or some app from the rooting kit. And also you can always flash everything stock. Just read and think of what you're doing. Good luck.

Can you help me, when I type fastboot oem unlock in the command prompt, it says <waiting for device>. Any idea?

LittleConfucy said:
Can you help me, when I type fastboot oem unlock in the command prompt, it says <waiting for device>. Any idea?
Click to expand...
Click to collapse
You probably have not configured devide ids for adb.
But probably the use of "sudo" should solve your problem.

rtfpessoa said:
You probably have not configured devide ids for adb.
But probably the use of "sudo" should solve your problem.
Click to expand...
Click to collapse
So, what do I have to do?! Sorry, I'm a complete noob xD

LittleConfucy said:
So, what do I have to do?! Sorry, I'm a complete noob xD
Click to expand...
Click to collapse
Just run:
sudo fastboot oem unlock

rtfpessoa said:
Just run:
sudo fastboot oem unlock
Click to expand...
Click to collapse
It doesn't recognize sudo as a command

LittleConfucy said:
It doesn't recognize sudo as a command
Click to expand...
Click to collapse
Are you on windows?
If yes, are you on bootloader mode?
If not:
1-Power off
2-Power On + Vol. Down
Then you execute "fastboot oem unlock"
If it doesn't work try to use any of the auto tools that you can find all over XDA forums

LittleConfucy, as you haven't told us what OS you're using, I'll assume it's Windows 7 or 8, doesn't really matter. Go here, download, install, launch, press the big button on top named "Full Driver Installation" and read what it tells you to do. It's written clear enough to understand. Just will give you some tips.
1. To install adb drivers, you should enable camera mode. It can be done in Settings->Storage. Just click on 3 dots and go to the USB connection settings. Select the option with PTP in its name and uncheck MTP if checked. After that your device should be recognized properly.
2. This App had a bug some time ago. It downloaded drivers and couldn't find them later. The workaround is to copy c:\Program Files (x86)\WugFresh Development\data\drivers\universal_drivers\UniversalAdbDriverSetup7.msi and rename the copy to UniversalAdbDriverSetup6.msi. It'll help.

Do you have any idea where can I see the drivers that were installed on the computer?

Slavon-93 said:
LittleConfucy, as you haven't told us what OS you're using, I'll assume it's Windows 7 or 8, doesn't really matter. Go here, download, install, launch, press the big button on top named "Full Driver Installation" and read what it tells you to do. It's written clear enough to understand. Just will give you some tips.
1. To install adb drivers, you should enable camera mode. It can be done in Settings->Storage. Just click on 3 dots and go to the USB connection settings. Select the option with PTP in its name and uncheck MTP if checked. After that your device should be recognized properly.
2. This App had a bug some time ago. It downloaded drivers and couldn't find them later. The workaround is to copy c:\Program Files (x86)\WugFresh Development\data\drivers\universal_drivers\UniversalAdbDriverSetup7.msi and rename the copy to UniversalAdbDriverSetup6.msi. It'll help.
Click to expand...
Click to collapse
So I have to copy the file, paste it in the same directory, without deleting the previous file, and change its name?

Need help...
After I rooted, I opened BusyBox and it said:
"There was a problem opening a shell with root acces. This is either being caused by superuser/supersu or by a device that is inproperly rooted."
I downloaded root checker, and it says that it's not proprly rooted

[Q] Soft bricked htc one m8 no OS

Looked all day for a similar situation and all the ones i found didnt help so this is my last resort.So today i decided to root my phone. I had great succsess and was eager to flash a new rom. My recovery is TWRP. I downloaded Android revolution hd to my external sd. I went into recovery mode swiped my rom, tried to flash Android revolution, the file was there but the image wasnt. Now i have no rom on my phone and cant figure out how to flash one using adb on terminal. The commands ive tried arent working and i get different results from others in similar situations. In fastboot it says 'fastboot usb' so i know its connected and the cables fine. Im definitely a noob at tech hence the reason i managed to make a stupid mistake like this but i could really use the help. Im a US Marine and need my phone by tomorrow. Sorry if this thread is in the wrong spot im new to forums. Thanks a lot guys.

What do you mean by "the file was there but the image wasnt" ?
Is it the zip file is on your external sd but can't see it in TWRP recovery ?
Make sure that you select Micro SDcard on storage option.
When you have an external sd, you don't really need those ADB commands ... just take it out and connect to a PC then put in a ROM.zip on your external sd

ckpv5 said:
What do you mean by "the file was there but the image wasnt" ?
Is it the zip file is on your external sd but can't see it in TWRP recovery ?
Make sure that you select Micro SDcard on storage option.
When you have an external sd, you don't really need those ADB commands ... just take it out and connect to a PC then put in a ROM.zip on your external sd
Click to expand...
Click to collapse
yes it was on my external but the image wasnt. But now i think my sd is broken theres a crack in it, and my computer doesnt pick it up anymore. convenient i know. Before i could see the whole file but the img. was missing. now none of its there. I can get a new sd and put a rom on like you said but i wouldnt be able to do that right now and was wondering if there was another way?

zacks94 said:
.... i wouldnt be able to do that right now and was wondering if there was another way?
Click to expand...
Click to collapse
Push the ROM.zip to internal sdcard
How-to :
Put a ROM.zip in your adb/fastboot folder
Put your device in TWRP recovery mode
Then adb push it to internal sdcard
command : adb push ROM.zip /data/media/0/
Once complete, select install - make sure the Storage selected is Internal Storage - you should see the ROM.zip

i will try this and get back to you. I appreciate the help.

zacks94 said:
yes it was on my external but the image wasnt. But now i think my sd is broken theres a crack in it, and my computer doesnt pick it up anymore. convenient i know. Before i could see the whole file but the img. was missing. now none of its there. I can get a new sd and put a rom on like you said but i wouldnt be able to do that right now and was wondering if there was another way?
Click to expand...
Click to collapse
If it's not picking up your phone in adb try redownloading the drivers, this website worked for me (http://www.andromods.com/download-files/get-htc-one-m8-usb-drivers-newest-all-models.html). Then try to adb push a stock rom to your device and redownload it in your recovery.

this is what i got and have gotten multiple times with different zips.

zacks94 said:
this is what i got and have gotten multiple times with different zips.
Click to expand...
Click to collapse
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/

1163
ckpv5 said:
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/
Click to expand...
Click to collapse
This is what i got while trying to push. Am i supposed to be on adb sideload, or bootloader? Sorry im dumb

ckpv5 said:
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/
Click to expand...
Click to collapse
woops. Ths...

zacks94 said:
This is what i got while trying to push. Am i supposed to be on adb sideload, or bootloader? Sorry im dumb
Click to expand...
Click to collapse
No need to select adb sideload or whatever ... just enter recovery, check mount - data is ticked then do what I mentioned before.
{
"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"
}

zacks94 said:
woops. Ths...
Click to expand...
Click to collapse
I don't know much about Mac, usually the different in command is only put the ./ infront of adb or fastboot
do you get your serial no and the word recovery when you run
./adb devices (put your device in recovery)
this is mine
View attachment 2913050
I tried to adb push HTC_One_(M8)_-_MaximusHD_7.0.0.zip /data/media/0/
(because I don't have the same ROM.zip as yours)
View attachment 2913055
And it is a successful effort

ckpv5 said:
No need to select adb sideload or whatever ... just enter recovery, check mount - data is ticked then do what I mentioned before.
View attachment 2913038
Click to expand...
Click to collapse
holy crap it worked. Thanks a lot.I really appreciate it.

zacks94 said:
holy crap it worked. Thanks a lot.I really appreciate it.
Click to expand...
Click to collapse
No problem ... glad that I could help

NO os. stuck in htc logo with CWM but device not recognized adb
ckpv5 said:
No problem ... glad that I could help
Click to expand...
Click to collapse
on mac. when i go to terminal and type fastboot devices it keeps coming with the message. "-bash: fastboot: command not found" i can boot into bootloader and into CWM but thats all. I have no OS. i have a few roms stored but when i flashed them it just stays stuck in the htc logo.
on my pc, i go to cmd and i downloaded android sdk. I placed a rom into platform-tools folder and when i do "adb sideload <filename>" it comes up with error: device not found.
I dont know what else to do. any help would be very appreciated regards
Raul

rauliroo said:
on mac. when i go to terminal and type fastboot devices it keeps coming with the message. "-bash: fastboot: command not found" i can boot into bootloader and into CWM but thats all. I have no OS. i have a few roms stored but when i flashed them it just stays stuck in the htc logo.
on my pc, i go to cmd and i downloaded android sdk. I placed a rom into platform-tools folder and when i do "adb sideload <filename>" it comes up with error: device not found.
I dont know what else to do. any help would be very appreciated regards
Raul
Click to expand...
Click to collapse
Your command is wrong.
On Mac .. you type
./fastboot devices
there is extra character needed ---> ./
when do adb command, it is ./adb
Note : I'm not familiar with CWM ... only TWRP ... all those I wrote here are based on TWRP recovery but should be the same

ckpv5 said:
Your command is wrong.
On Mac .. you type
./fastboot devices
there is extra character needed ---> ./
when do adb command, it is ./adb
Note : I'm not familiar with CWM ... only TWRP ... all those I wrote here are based on TWRP recovery but should be the same
Click to expand...
Click to collapse
It didn't work. I genuinely don't know whats missing. if device its not recognized. could be a driver issue on mac??
have a look at the screenshots
many thanks
Raul

Yep .. driver looks ok but you don't have fastboot & adb files ?
See this to get them : .http://forum.xda-developers.com/showthread.php?t=2390995
You mentioned you downloaded sdk, you need to run the command from platform-tools folder.
Check the screenshot how the directory looks : http://forum.xda-developers.com/showpost.php?p=55062969&postcount=10
You should have something like Rauls-MacBook-Air: platform-tools~Raul$ ./fastboot devices
BTW this is M8 forum ... why don't you post your problem in M7 forum ?
Maybe there are more people who familiar with Mac ... I never use one, I know only some basic.

Bootloader

I have read, I have searched thread after thread. I have the Google Pixel XL on Verizon. I have followed the directions to the letter for unlocking bootloader using dePixel. The issue I have is with the Developer Options. I am unable to enable the OEM Unlocking because it is grayed out. I have reset the device like 10 times. I have automatic updates disable in developer options. I need to be point in the right direction or have someone that can relate, to chime in. I am not looking for root....I just want the bootloader unlocked
{
"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"
}

That button will always be greyed out on the VZW firmware. After you unlocked do you see a warning message on boot? How do you know you are not, in fact, unlocked?

You don't mess with that button. Just follow the directions for dePixel8
Sent from my Pixel XL using Tapatalk

DualSportDad said:
You don't mess with that button. Just follow the directions for dePixel8
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I followed to the letter and I get nothing

Mike02z said:
That button will always be greyed out on the VZW firmware. After you unlocked do you see a warning message on boot? How do you know you are not, in fact, unlocked?
Click to expand...
Click to collapse
well for starters after I entered the cmd lines.....device never rebooted into fastboot for me to run the unlock cmd line

Ok first before we can help you, can you post the screen of the cmd window or copy paste the results of it?

mikeutsey said:
well for starters after I entered the cmd lines.....device never rebooted into fastboot for me to run the unlock cmd line
Click to expand...
Click to collapse
Set the phone from charging to file transfer. After hitting enter for the last command line op pen the chrome browser app. I don't know why but that's what worked for me.
Sent from my Pixel XL using Tapatalk

Why not just flash the Google factory image once you run the depixel8 program?
Edit: Looks like you missed a step somewhere. Make sure your device is connected to your computer via adb. I would run the 15 second adb install (Google it) than put the depixel8 file in your tools folder. Open tool folder shift and right click to to open cmd promt. Type adb devices and see if it's connected. Also be sure to turn on USB debugging in dev options.

jaxenroth said:
Why not just flash the Google factory image once you run the depixel8 program?
Edit: Looks like you missed a step somewhere. Make sure your device is connected to your computer via adb. I would run the 15 second adb install (Google it) than put the depixel8 file in your tools folder. Open tool folder shift and right click to to open cmd promt. Type adb devices and see if it's connected. Also be sure to turn on USB debugging in dev options.
Click to expand...
Click to collapse
The dePixel8 Program has yet to work for me. Still have not successfully unlocked bootloader

Marghost said:
Ok first before we can help you, can you post the screen of the cmd window or copy paste the results of it?
Click to expand...
Click to collapse

On the pic you posted i see that you need to put a Space between 755 and /...
Can you post the full log If this is not working!

Was able to get it to reboot with cmd line but still not working. Thanks for all of your help with this
Marghost said:
On the pic you posted i see that you need to put a Space between 755 and /...
Can you post the full log If this is not working!
Click to expand...
Click to collapse

OK I see try close your phone and boot to the bootloader screen with power and vol down pressed at boot. After run the command
fastboot oem unlock
And tell me what you see!

That did it.....thanks guys....never would have even considered physically turning off device and and manually fastboot :highfive:
Marghost said:
On the pic you posted i see that you need to put a Space between 755 and /...
Can you post the full log If this is not working!
Click to expand...
Click to collapse

Np bro glad I helped. If you want give me some thumbs up hehe
Great day
Sent from my Pixel XL using XDA Labs

Is ADB working for you? I'm not sure where your are in the process, so forgive me if you've done these steps:
- enable debugging in developer options (must first tap on build number 10x or whatever
- if you do adb devices from command prompt, do you get the device id? You need to allow the computer to talk to the phone (security authorization on the phone the first time you attempt adb), as well as have drivers properly installed on computer
- assuming adb is writing properly, people seem to have best success with depixel8 if they set screen timeout to 5 min or longer, and after starting depixel8 commands on the computer, is screen blanks out, truth screen back on and try and run an app ...
Hope this helps

error:Cannot load Unlock_code.bin NO solutions????

This is bothering me alot, bought an HTC10 thats with o2 and i cant get the final step to work.
I have received the email twice in as a many attempts,used Chrome and IE to download the unlock code. I placed the unlock code in the same folder as fastboot adb and the other adb
all drivers were installed,including the Android studio one thats 1.6gb along htcsync. When i type in adb devices my device sn comes up
Not sure what to make of this, i looked over the web their issues were that they either had a typo or missplaced the code ,is there really no solution for me?

I only saw this once before when I accidentally renamed the unlock file unlock_code.bin.bin. can we see the properties of the unlock_code.bin? Also I couldn't see from the picture if you had run the command prompt as admin?

Cat_On_Droid said:
This is bothering me alot, bought an HTC10 thats with o2 and i cant get the final step to work.
I have received the email twice in as a many attempts,used Chrome and IE to download the unlock code. I placed the unlock code in the same folder as fastboot adb and the other adb
all drivers were installed,including the Android studio one thats 1.6gb along htcsync. When i type in adb devices my device sn comes up
Not sure what to make of this, i looked over the web their issues were that they either had a typo or missplaced the code ,is there really no solution for me?
Click to expand...
Click to collapse
Why don't u uninstall HTC sync and try again.

In folder options for Windows turn on the option to see all file extensions and make sure its labeled "Unlock_code.bin". Also just Shift+Right Click in that folder so you have a Command Prompt that's already loaded in there so all you have to do is type the fastboot commands and not the entire directory. (makes life a little easier)

Tachi91 said:
In folder options for Windows turn on the option to see all file extensions and make sure its labeled "Unlock_code.bin". Also just Shift+Right Click in that folder so you have a Command Prompt that's already loaded in there so all you have to do is type the fastboot commands and not the entire directory. (makes life a little easier)
Click to expand...
Click to collapse
it is a bin file, the pic provided just cuts before it says its a bin file. �ts labaled exactly as in attachment
i updated to latest OTA , enabled USB debugging and still same problem :crying::crying::crying::crying:
attached the Unlock_code for refference

Try just dragging the .bin file onto the command window and then pressing "Enter." This gets rid of any possible path or name issues.

rwallhtc said:
I only saw this once before when I accidentally renamed the unlock file unlock_code.bin.bin. can we see the properties of the unlock_code.bin? Also I couldn't see from the picture if you had run the command prompt as admin?
Click to expand...
Click to collapse
Solved !
You need to run cmd as admin, simple as that haha
Question , OTA updates with unlocked bootloader+root will work or no?

Cat_On_Droid said:
Solved !
You need to run cmd as admin, simple as that haha
Question , OTA updates with unlocked bootloader+root will work or no?
Click to expand...
Click to collapse
Look into Magisk.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

soft root

Dear friends,
I would like root my g4. Marshmallow android 6 like I made with android 5.0, that in a soft root way. Is it possible?
Thanks a lot.
Kf
P.s I attached on this post the software configuration of my lg. Help me please!!!

I don't know if it is possible like in lollipop, but there is something called Magisk which is systemless root.

kenfalco_14 said:
Dear friends,
I would like root my g4. Marshmallow android 6 like I made with android 5.0, that in a soft root way. Is it possible?
Thanks a lot.
Kf
P.s I attached on this post the software configuration of my lg. Help me please!!!
Click to expand...
Click to collapse
kouzelnik3 said:
I don't know if it is possible like in lollipop, but there is something called Magisk which is systemless root.
Click to expand...
Click to collapse
Is your device unlocked?
No Root for MM for locked devices.
.
Sent from my LG-H815 using XDA Labs

How can i see if it is locked?

kenfalco_14 said:
How can i see if it is locked?
Click to expand...
Click to collapse
If you do not know it then it is likely that your device is not unlocked
You can reboot into fastboot by the command
adb reboot bootloader
and then you could execute
fastboot getvar unlock
And just before you ask not every model can be unlocked that being said only the h815 international and the h811 can be unlocked officially
Sent from my LG-H815 using XDA Labs

steadfasterX said:
If you do not know it then it is likely that your device is not unlocked
You can reboot into fastboot by the command
adb reboot bootloader
and then you could execute
fastboot getvar unlock
And just before you ask not every model can be unlocked that being said only the h815 international and the h811 can be unlocked officially
Click to expand...
Click to collapse
Do I need unlock the bootloader from lg site?

kenfalco_14 said:
Do I need unlock the bootloader from lg site?
Click to expand...
Click to collapse
Yes
Sent from my LG-H815 using XDA Labs

I tried to obtain the hardware id by adt, but I could'nt do the pc does'nt see the device. It is strange because it can see the sd cards like g4 attached device. I activated the debugging usb mode on the developer menu but I did'nt obtain the rsa device id so I think that phone can't work in usb debugging mode.
It is very stupid situation... :crying:

First, you need to check "Enable OEM unlock" in the developer menu. Then, you need to reboot into download mode from which you can get the fastboot command and then it should show you your device ID.
Here you are the tutorial which I used and it worked for me: https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003

I can't reboot in dowload mode. I push pwr+ vol - and nothing. I connected phone to my notebook and when I launch the adb command it tells me error "null" device. It is stranfe because I can see sd cards like g4...

kouzelnik3 said:
First, you need to check "Enable OEM unlock" in the developer menu. Then, you need to reboot into download mode from which you can get the fastboot command and then it should show you your device ID.
Here you are the tutorial which I used and it worked for me: https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Click to expand...
Click to collapse
kenfalco_14 said:
I can't reboot in dowload mode. I push pwr+ vol - and nothing. I connected phone to my notebook and when I launch the adb command it tells me error "null" device. It is stranfe because I can see sd cards like g4...
Click to expand...
Click to collapse
I'm sorry but he meant the fastboot mode and not the download mode! Just follow the link provided it contains a step-by-step guide for you!
.
Sent from my LG-H815 using XDA Labs

I changed pc, finally obtained the rsa key from usb debugging, after make adb reboot bootloader and see this. Then make fastboot oem device - id and nothing,. System is waiting for device...forever. Sorry for pic.

kenfalco_14 said:
I changed pc, finally obtained the rsa key from usb debugging, after make adb reboot bootloader and see this. Then make fastboot oem device - id and nothing,. System is waiting for device...forever. Sorry for pic.
Click to expand...
Click to collapse
This is the correct mode but please show a screenshot of your terminal output and the command you have typed on your PC!
I assume that it is Windows what you are using so you may consider to try FWUL instead it has all drivers included and you have everything required already installed and you can run it without touching your main operating system..
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
This is the correct mode but please show a screenshot of your terminal output and the command you have typed on your PC!
I assume that it is Windows what you are using so you may consider to try FWUL instead it has all drivers included and you have everything required already installed and you can run it without touching your main operating system..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I put last lg driver vwersion., i use win7 sp 1. Pc recognize cell without problem, I have rsa debugging key, that inn other pc no had. May be that because this phone is a refurbished one? I don't know other causes.
Ciao

kenfalco_14 said:
I put last lg driver vwersion., i use win7 sp 1. Pc recognize cell without problem, I have rsa debugging key, that inn other pc no had. May be that because this phone is a refurbished one? I don't know other causes.
Ciao
Click to expand...
Click to collapse
it sounds like a driver issue.. check ur device manager if u see unknown devices.
.... or FWUL ? http://tinyurl.com/adbiso
.

steadfasterX said:
it sounds like a driver issue.. check ur device manager if u see unknown devices.
.... or FWUL ? http://tinyurl.com/adbiso
.
Click to expand...
Click to collapse
No issues in the device manager. I have a dual boot with winzoz and ubuntu. Coul I implement this tool on linux? I tried it with Virtual box but I don't know how use, archlinux is for me too advanced ...

steadfasterX said:
it sounds like a driver issue.. check ur device manager if u see unknown devices.
.... or FWUL ? http://tinyurl.com/adbiso
.
Click to expand...
Click to collapse
No issues in the device manager. I have a dual boot with winzoz and ubuntu. Could I implement this tool on linux? I tried it with Virtual box but I don't know how use it, archlinux is for me too advanced ...

kenfalco_14 said:
No issues in the device manager. I have a dual boot with winzoz and ubuntu. Could I implement this tool on linux? I tried it with Virtual box but I don't know how use it, archlinux is for me too advanced ...
Click to expand...
Click to collapse
just use ubuntu and there do
Code:
sudo fastboot devices
if that suceeds
Code:
sudo fastboot oem device-id
.

Fasboot command not found. Do I need download some tool from ubuntu dc? I think yes..

kenfalco_14 said:
Fasboot command not found. Do I need download some tool from ubuntu dc? I think yes..
Click to expand...
Click to collapse
depends on your ubuntu version. newer ones should work like this;
Code:
sudo apt update
sudo apt install android-tools-adb android-tools-fastboot
(https://www.linuxbabe.com/ubuntu/how-to-install-adb-fastboot-ubuntu-16-04-16-10-14-04)
otherwise: https://duckduckgo.com/?q=adb+fastboot+ubuntu&atb=v56-2__&ia=web
.