Related
This post is now deprecated there are new ways of rooting more easily here is the link to one of those
http://forum.xda-developers.com/showthread.php?t=1392310
just kept for reference
link no longer works as it is a very old boot img, if you wanna go this way use latest superboot
Rooting your Galaxy Nexus
Download this file contains necessary files and also lastest samsung drivers in case you dont have them, probably you need android sdk drivers for fastboot
Download
credit to @peteralfonso for the insecure boot.img which allows this to remount system and this way install su binary and Superuser.apk
This are the instructions for Galaxy Nexus
they require basic knowledge of fastboot adb and using command prompt/terminal
works same way on linux and windows
Be sure to have fastboot and adb ready and working
extract somewhere and you will get 4 files su, Superuser.apk , boot.img and drivers
turn off the phone
Boot into bootloader mode (Vol UP+ Vol Down + Power) then execute this command, be sure to have fastboot and boot.img on same folder or be ready to type a long path pointing to your boot.img
REMINDER: by doing fastboot oem unlock you will completely wipe your device so be sure to backup anything important
execute this command
Code:
fastboot oem unlock
fastboot boot boot.img
edit: thanks chirality forgot the oem unlock
the device will reboot and start in unsafe mode where you can enable adb as root usually on production devices this is not posible
Be sure to enable adb debugging on menu
back to command prompt
Code:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
and you are done and youve got your Galaxy Nexus rooted
This process does not involve flashing another boot.img, it just boots once with it and after that returns to original boot.img
As usual
YOU ARE PERFORMING THIS AT YOUR OWN RISK! I AM NOT RESPOSIBLE FOR ANY BRICKS OR PROBLEMS!
Which wont happen we are just pushing 2 files to our phone
edit2: sorry for the bad paths of adb was too late and didnt notice my error
Don't you have to do "fastboot oem unlock" first before being able to boot off the insecure image? I thought they fixed that with the Nexus S already.
Thanks for the post - apparently people are having problems with the Superboot method, so I'll give this a go when mine arrives today.
I guess this comes with all the usual "at your own risk" and "will void your warranty" warnings?
(sorry if that's a stupid question - this is my first Nexus, so I'm not sure where I stand on rooting, unlocking bootloaders, and the warranty etc.)
Great - worked without issue for me and I can now use the Entree VPN client for connecting into work. (the HD screen is great for remote desktop work)
Minor typo in the permissions lines though - should read:
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
Thanks very much,
Chris.
Thanks for this davioxx for putting together the guide, chriscole for the fixes and @peteralfonso for the insecure boot.img.
I'm now succesfully rooted.
It seems Root Explorer needs an update for the GN though. Only opens in the bottom left corner of the screen for me, and is comprised of static.
Sorry for the newbee question, been quite a while since rooting my nexus one...
Do i need to enable adb debugging on phone menu before executing the fastboot oem unlock code and then enable it again after it reboots and starts in safe mode?
w00t!
Thank you
You may want to change the path names on the chmod part, I blindly followed the instructions and the files were in diffrent places from where I pushed them to
But thanks \o/
I haz root!
Tnx, easy like all nexus devices, now need some you tube for that!
Sent Via My HTC Desire HD
looks pretty simple ... hopefully it will be the same process for us in the States
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
majikdragoon said:
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
Click to expand...
Click to collapse
Are you doing it via adb or fastboot?
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
majikdragoon said:
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
Click to expand...
Click to collapse
Hi probably you dont have the bootloader driver installed, that has to be done manually at least for my win 64 machine, check this thread about that
Set Up ADB, fastboot and drivers Nexus S it is practically the same for your Galaxy Nexus
Oh ok! I'll look at that now. Thanks fellas
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
there isnt a custom recovery yet and stock recovery needs signed recoveries
actually not hard you take 3 mins in all process
Babydoll25 said:
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
Click to expand...
Click to collapse
Babydoll25 said:
Unless there isn't a custom recovery available yet...
Click to expand...
Click to collapse
Ding ding ding.
Also some people don't want to flash a custom recovery anyway.
Sent from my Nexus S using XDA App
Drivers
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
coleburns said:
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
Click to expand...
Click to collapse
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
el3ctrik said:
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thanks for that, managed to get it working with pdanet.
however when i try to run the adb commands, i get the adbt cannot run as root in production builds
how did you get rooted?
thanks
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
originally,we used a zip file flashable in recovery. i have found it to work on gsm devices with 1.44 hboot and CW recovery. it did not work with twrp. if the following is too scary,feel free to test the zip files. that thread,info,and downloads can be found here. since not all recoverys are working,these values can be changed with simple adb commands.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser. use the keep bootloader locked directions)
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for giving me the echo comand,so yall didnt need to dump,edit with a hex editor,and copy back
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-kdj67f for fearlessly testing and putting up some screenshots in post 5. thanks!
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
*i have tested this on my gsm htc one. if someone wants to test on vzw,ill add you to the credits
mine!
So, this will work with hboot 1.54? And are you sure the memory blocks are correct for Verizon? I will test...
I'm s-off, stock Rom, cwm recovery and rooted.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
kdj67f said:
So, this will work with hboot 1.54? And are you sure the memory blocks are correct for Verizon? I will test...
I'm s-off, stock Rom, cwm recovery and rooted.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
99% sure we can certainly dump p3 and have a look-see first,if you'd like. We woukd need a dump from someone whose unlocked or relocked
Sent from my HTC One using Tapatalk 2
99% is good enough for me haha! Phone just hut 50% charged, give me a minute. Will post back with pictures.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 08:56 PM ---------- Previous post was at 08:41 PM ----------
Confirmed, code working. Flags set/reset. Phone even reboots and works will upload pics/screenshots.
Thanks!
Starting out unlocked:
Locking:
Locked:
Unlocking:
Re-unlocked:
Very good work!
Awesome! Thanks for confirming
Sent from my HTC One using Tapatalk 2
That was super easy... great write up! This will save so much time getting an unlocktoken and running through HTCdev. Many thanks!
scotty1223 said:
99% sure we can certainly dump p3 and have a look-see first,if you'd like. We woukd need a dump from someone whose unlocked or relocked
Click to expand...
Click to collapse
Verizon HTC One here, S-Off with SuperSU but otherwise stock, locked bootloader, hboot 1.54. I just did
Code:
dd if=/dev/block/mmcblk0p3 of=orig bs=1 seek=33796 count=4
and looked at the resulting dump and it has "PGFS" not nulls at that offset. I'm wondering if we should write "PGFS" back on Verizon/hboot 1.54 and not nulls?
bjorheden said:
Verizon HTC One here, S-Off with SuperSU but otherwise stock, locked bootloader, hboot 1.54. I just did
Code:
dd if=/dev/block/mmcblk0p3 of=orig bs=1 seek=33796 count=4
and looked at the resulting dump and it has "PGFS" not nulls at that offset. I'm wondering if we should write "PGFS" back on Verizon/hboot 1.54 and not nulls?
Click to expand...
Click to collapse
sounds like youre looking at offsets 00 01 02 03. every device ive looked at so far has the PGFS at that location. i havent looked ata vzw p3,but t mobile follows that. youll find the HTCU,HTCL,or nulls at 8404 8505 8406 8407.
im not sure your command is showing you the correct location. id dump and look at the whole thing.
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3
Hey Scotty,
I can't thank you enough for this info. I really didn't want to unlock via htcdev and it's been getting tiring making zips for everything I want to flash. This solved my problem and is reversible without record. You are the man and thanks for putting in the time.
isdnmatt said:
Hey Scotty,
I can't thank you enough for this info. I really didn't want to unlock via htcdev and it's been getting tiring making zips for everything I want to flash. This solved my problem and is reversible without record. You are the man and thanks for putting in the time.
Click to expand...
Click to collapse
glad to help
Can someone explain the benefits to me of being able to change between locked/unlocked? If not.... That's cool.
Sent from my HTC6500LVW using Tapatalk now Free
BaBnkr said:
Can someone explain the benefits to me of being able to change between locked/unlocked? If not.... That's cool.
Sent from my HTC6500LVW using Tapatalk now Free
Click to expand...
Click to collapse
For this thread and most people's needs, unlocking this way after s-off saves time. Re-locking just proved it was reversible in case someone did want to be locked again. Another way to get back to stock for warranty purposes, etc...
Most importantly, to prove it can be done!
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Fantastic, can this work for HTC One S too?
maybe needs finding correct blocks?
what it is unclear to me is that:
your method to unlock bootloader needs S-OFF, but S-OFF needs Unlocked bootloader and SuperCID, so maybe for HTC One S it's different
thanks for clarification
icest0rm said:
Fantastic, can this work for HTC One S too?
maybe needs finding correct blocks?
what it is unclear to me is that:
your method to unlock bootloader needs S-OFF, but S-OFF needs Unlocked bootloader and SuperCID, so maybe for HTC One S it's different
thanks for clarification
Click to expand...
Click to collapse
blocks are the same for one s.
method does indeed need s off. most common way to achieve s off for devices on the unlock program is via intial unlock thru htcdev to install root and recovery. at this point the commands are useful to get back to locked,and if one needs unlock after being locked for some reason. vzw is a bit different in that they cannot use htcdev,so a hack is needed to temproot,then s off. this does give them the luxury of being able to unlock without htcdev alltogether.
its also possible to s off via a java card,or be lucky enuff to find a user trial device that came that way. in this situation htcdev can be left out of the picture entirely.
hope that clarifes it
scotty1223 said:
blocks are the same for one s.
Click to expand...
Click to collapse
ok!
scotty1223 said:
method does indeed need s off. most common way to achieve s off for devices on the unlock program is via intial unlock thru htcdev to install root and recovery. at this point the commands are useful to get back to locked,and if one needs unlock after being locked for some reason.
Click to expand...
Click to collapse
ok...clear
scotty1223 said:
vzw is a bit different in that they cannot use htcdev,so a hack is needed to temproot,then s off. this does give them the luxury of being able to unlock without htcdev alltogether.
Click to expand...
Click to collapse
ehm...sorry...what is vzw?
its also possible to s off via a java card,or be lucky enuff to find a user trial device that came that way. in this situation htcdev can be left out of the picture entirely.
hope that clarifes it
Click to expand...
Click to collapse
thanks :good:
vzw=Verizon wireless
Sent from my HTC One VX using Tapatalk
scotty1223 said:
vzw=Verizon wireless
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
ah ok...
but since they need a temproot to get unlock without htcdev, wouldn't this be possible for all htc one (s)?
why is it limited to vzw?
icest0rm said:
ah ok...
but since they need a temproot to get unlock without htcdev, wouldn't this be possible for all htc one (s)?
why is it limited to vzw?
Click to expand...
Click to collapse
technically,yes. you could use a temp root and make a tool for any other carriers device so you would not have to unlock.
however, temp root exploits are typically patched quickly. htcdev is a reliable means of root to make other tools/exploits work. its much,much easier to simply unlock and install root and recovery than to keep looking for softwate temp root exploits.
with verizon you have no choice,since they do not allow official unlock.
Hello, can you please tell me why do i get this error ?
Hi i need to find a kernal with usb debugging and adb setting in developer settings automatically ticked because my phone screen is completely broken and im using a program that requires the two settings to be on. Please help if you can thank you!
I don't think a kernel can enable those, only the user can.. You can probably flash a ROM that has them enabled or a script
Sent from my SGH-M919 using Tapatalk
serio22 said:
I don't think a kernel can enable those, only the user can.. You can probably flash a ROM that has them enabled or a script
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I also broke my screen and was looking for this exact thing. It's Android Control and I need adb enabled. I tried various ways I found while searching to try to enable adb through TWRP and an adb shell on my PC, but it wouldn't work ( kept getting a "~ # ?[6n" prompt and "not found" when entering "su" ).
Then I found this kernel kitchen. In that thread the dev says you can make the ramdisk insecure and make adb mode persistent. Anybody able to help me out?
brokenchains said:
I also broke my screen and was looking for this exact thing. It's Android Control and I need adb enabled. I tried various ways I found while searching to try to enable adb through TWRP and an adb shell on my PC, but it wouldn't work ( kept getting a "~ # ?[6n" prompt and "not found" when entering "su" ).
Then I found this kernel kitchen. In that thread the dev says you can make the ramdisk insecure and make adb mode persistent. Anybody able to help me out?
Click to expand...
Click to collapse
What version? Mdl mk2 or nb4? Probably already insecure boot.img unless you're running stock tho
Debugging in dev options would be a different story tho. I might be able to figure out how to enable it thru command line tho
And now that I think about it, I don't even know what would work since you're dual booting.
ShinySide said:
What version? Mdl mk2 or nb4? Probably already insecure boot.img unless you're running stock tho
Debugging in dev options would be a different story tho. I might be able to figure out how to enable it thru command line tho
And now that I think about it, I don't even know what would work since you're dual booting.
Click to expand...
Click to collapse
I figured out how to get adb shell working, but I had to switch TWRP out for CWM non-touch. That let me use adb correctly through recovery and I found a way to enable adb in the ROM that way by pulling settings.db and editing the "adb_enabled" setting there. Now I'm just caught because I can't see the screen to authorize my PC to use adb... I tried to manually put the adb key from my PC's file into the adb_keys file on the phone but that didn't work and I'm pretty sure I did it right. That process is described here for anyone curious.
Well.. I tried different ways of rooting it and now I'm stuck.
when I run adb shell getprop I see that ro.debuggable is 0
This means I can't get access to my phone on fastboot mode in the bootloader.
So no root method works for me. I'm trying to find more information on this but all topics on XDA don't mention how to change this option to 1.
So, how can I make my device visible on the bootloader in order to root it and install TWRP?
edit: sorry, I could swear I was in the Q&A section
renatojf said:
Well.. I tried different ways of rooting it and now I'm stuck.
when I run adb shell getprop I see that ro.debuggable is 0
This means I can't get access to my phone on fastboot mode in the bootloader.
So no root method works for me. I'm trying to find more information on this but all topics on XDA don't mention how to change this option to 1.
So, how can I make my device visible on the bootloader in order to root it and install TWRP?
edit: sorry, I could swear I was in the Q&A section
Click to expand...
Click to collapse
You can enable USB debugging in developer options (click the build number 7 times if it doesn't show up in settings).
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
.