Tell me what this fastboot command would do - X 2014 Q&A, Help & Troubleshooting

fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
It is referenced in the fire rooting guide, seems harmless?
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362/post64350457#post64350457
Quote:
Originally Posted by flyapart
Great! Noob question warning -- I can get the root prompt but can't seem to install SuperSU. Can you tell us what commands you used from the terminal to do this? Also which file you used to install it (apk vs zip) and where they need to be placed? Thanks!!!
I just opened the root.bat from the other method in the 5.0.1 page and pasted the cmds manually in a cmd prompt
seems to have worked as I can use a terminal emulator and enter 'su' and get Superuser prompt
I believe it is/was more or less this
You will need the root_fire.zip from the other thread, and then open a command window in the folder where you extract those files.
Quote:
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb remount
adb push files\libsupol.so /data/local/tmp/
adb push files\root_fire.sh /data/local/tmp/
adb push files\su /data/local/tmp/
adb push files\Superuser.apk /data/local/tmp/
adb push files\supolicy /data/local/tmp/
adb shell chmod 777 /data/local/tmp/root_fire.sh
adb shell /data/local/tmp/root_fire.sh
# This Part reopened fastboot and I just re-ran the cmds from the first post in this thread #
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
# after device reboots and you see it with 'adb devices' #
adb remount
adb shell /system/xbin/su --install
adb reboot
Click to expand...
Click to collapse

xt1096 root fail.
d33dvb said:
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
It is referenced in the fire rooting guide, seems harmless to try on xt1096?
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362/post64350457#post64350457
Click to expand...
Click to collapse
Answered my own question, posted result for reference
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
...
(bootloader) 'append-cmdline' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.016s

Related

[Q] Unlocked N1 - But Root Fail - ERROR- could not get pipe properties (MAC)

hi there,
been busy all evening on my Mac trying to unlock and root my nexus one retail. Got the phone unlocked after extensive reading on SDK and ADB Hoped that the positive flow would continue when switching over to the rooting process, but unfortunately I seem to get stuck and have failed
I downloaded the correct superboot version for my phone and placed it in my home folder (on same drive as where I successfully did the fastboot procedure for unlocking). And then I entered this in Terminal:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /superboot
suikerchiller-macbook-3:superboot suikerchiller$ chmod +x install-superboot-mac.sh
suikerchiller-macbook-3:superboot suikerchiller$ ./install-superboot-mac.sh
ERROR: could not get pipe properties
downloading 'boot.img'... OKAY
booting... OKAY
suikerchiller-macbook-3:superboot suikerchiller$
---
As a result my phone automatically reboots into basic settings. Does anybody know what I'm doing wrong??? I'm a total n00b but am really eager to learn In a bit of trouble now as well, because I don't know what to do anymore and dare to touch my fone either.
Any help would be great. Can't wait to finally be released from Vodafone's retail nexus one terror and want to challenge all those ignorant iphone studs out there and show how cool and superior my Nexus one actually is
P.S. I searched for quite some time on the forum and couldn't find a post/thread that was related to my problem. Please forgive me if this is some sort of double post.
If your phone is unlocked, don't bother with superboot, just flash a custom recovery and use it to install the su zip...
http://forum.xda-developers.com/showthread.php?t=682828
Place the recovery image in your sdk tools folder, place the su zip on your sd card, connect via fastboot and type:
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
Flash the su zip from recovery, and you're done!
many many thanks for the quick reply I placed the recovery image in my sdk tools folder.
However, still have a couple of questions:
I don't know what you exactly mean with a su zip??? Where can I get this file?
what do you mean with: "flash the su zip from recovery"?
I put a link in my original post. The eclair/froyo version works for gingerbread, also...
Once in recovery, you chose the flash zip from sd option, and then the chose zip from sd option, find and select the zip... It will be obvious when you do it...
sorry, it's still too much rocket science for me I guess
I uploaded the su zip file (did not unzip or rename file) to my sd card (activated usb storage and dropped the zip via Mac in the main folder of my phone).
what do you exactly mean with "connect with fastboot"? I shut down my fone first and pressed power button at same time with track ball. Then I did this:
---
suikerchiller-macbook-3:tools suikerchiller$ fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot: command not found
suikerchiller-macbook-3:~ suikerchiller$ fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$ cd ~
suikerchiller-macbook-3:~ suikerchiller$ cd /fastboot
suikerchiller-macbook-3:fastboot suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
As you can probably see it didn't really work haha what am I doing wrong? Sorry for my n00biness!
You said you have already unlocked your bootloader. In order to unlock the bootloader I you have to connect with fastboot...
How did you unlock the bootloader?
I unlocked it via the first 7 steps of this procedure (sorry have to copy paste a lot of text because im not allowed to post outside links on forum yet haha):
-----
Connect your Nexus One to your PC/Mac and turn it off.
Hold the trackball and hit the power button (while holding the trackball). You should see the following bootloader screen.
Now from the files you downloaded previously, you will see a folder called ‘fastboot‘ (if you extracted fastboot.zip that is!).
On a Windows machine – launch Command Prompt and CD to fastboot folder. (Type in ‘cd ‘ (without the quotes and drag and drop the fastboot folder to the command prompt). Type in ‘cd fastboot‘ again and now type the following command ‘fastboot-windows oem unlock‘ (without quotes) and hit enter.
On a Mac or Linux machine – launch the Terminal and CD to fastboot folder (type in ‘cd ‘ and drag and drop the folder. Now hit enter.). Now CD to the other fastboot folder and type the following (without quotes): ‘./fastboot-mac oem unlock‘ (for Mac) or ’./fastboot-linux oem unlock’ (for Linux) and hit enter. You will see the following. Ignore the error.
This is the screen that you will see now. Use the volume button (on the side) to select ‘Yes’. (Please read the full message displayed on the screen thoroughly). Now push the Power button to select this option (weird, I know. Trackball would have been a better choice to select!).
Great! You have successfully unlocked the bootloader! You will see the unlock image while your phone boots up.
----
I did this successfully and had the black screen and selected unlock phone. So when I press the power button & trackball at same time now I get a white screen now and it says in pink on top: ***Unlocked***
Ok substitute the term fastboot-mac instead of fastboot, into my previous instructions
damn, still doesn't seem to be working:
---
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:~ suikerchiller$ cd /fastboot
suikerchiller-macbook-3:fastboot suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
----
it's really weird, it looks like my fastboot is not responding anymore... Any idea what's going wrong here???
thanks so much for taking time and helping with figuring this one out!!!
Just tested something. When my phone is switched on normally and connected via USB, Terminal recognizes it as an adb device. However, when I switch into fastboot, Terminal doesn't recognize it:
---
suikerchiller-macbook-3:tools suikerchiller$ adb devices
List of devices attached
HT07YP804207 device
suikerchiller-macbook-3:tools suikerchiller$ adb devices
List of devices attached
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
Is this where the problem resides?? Anyone know how I can fix this???
adb will only work when it can see the adbd on your phone, so the phone had to be booted to either recovery or fully bolted.
fastboot will only connect when your phone is booted in fastboot. If its not connecting, reboot your phone and mac and try again...
suikerchiller said:
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
Is this where the problem resides?? Anyone know how I can fix this???
Click to expand...
Click to collapse
Sorry, just re-read this...
Command not found, NOT device not found.
You should be typing fastboot-mac, not fastboot...
Do you have a file called fastboot-mac in the same folder as your adb and recovery img?
rebooted my mac and phone... Still no difference, this is my latest command:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac devices
-bash: fastboot-mac: command not found
---
can this be the reason: my fastboot folder is in a different (other) folder than my 'android sdk' folder... should i drag and drop fastboot into the tools folder of sdk???
YES!
Put the fastboot-mac file in the same folder as the other stuff!! xD
haha ok, so I copied my fastboot-mac file (original file from fastboot folder) into AndroidSDK/tools folder. It's in the same folder now where the .img file is in as well.
But it still doesnt seem to be working. These are the commands that I have been using:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac boot recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac devices
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$
---
What's going wrong??? I'm going slightly mental now. Also running out of beer at same time. Not a good combination
can you list the contents of that folder, and tell me what result you get?
this is the list of files in my AndroidSDK/tools folder:
--
suikerchiller-macbook-3:tools suikerchiller$ ls
Jet hierarchyviewer
NOTICE.txt hprof-conv
adb-mac layoutopt
adb_has_moved.txt lib
android mksdcard
ant monkeyrunner
apkbuilder proguard
ddms recovery-RA-passion-v2.2.1-CM.img
dmtracedump source.properties
draw9patch sqlite3
emulator traceview
etc1tool zipalign
fastboot-mac
---
and here are the commands for fastboot, in case they can be of any usage
suikerchiller-macbook-3:tools suikerchiller$ ./fastboot-mac
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
Hmmmmm, well the file is there, so that's really weird because you mac is definately saying that it's the command it can't find...
I'm not much of a mac guy, but I do know that your mac is the one having the problem...
Try:
./fastboot-mac flash recovery name-of-recovery.img
suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ ./fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
sending 'recovery' (3380 KB)... OKAY
writing 'recovery'... OKAY

[Q] [Help needed] Fastboot doesn't provide token ID to unlock the bootloader

Guys, I have a problem with my HTC One M7. I am trying to unlock the bootloader using the HTCDev guide (available at htcdev site).
But suddenly I am not able to complete Step 8 (running command "fastboot oem get_identifier_token").
Command "fastboot devices" shows my phone in a fastboot mode:
\> fastboot devices
mt6589_phone_720pv2 fastboot
But none of fastboot oem commands executes successfully (including "get_identifier_token").
Instead I get only three dots ("...") and nothing changes after that:
\> fastboot oem get_identifier_token
...
Other commands (like fastboot reboot) function, but not "fastboot oem get_identifier_token". I can't unlock my bootloader, could you please help!
andrey o said:
Guys, I have a problem with my HTC One M7. I am trying to unlock the bootloader using the HTCDev guide (available at htcdev site).
But suddenly I am not able to complete Step 8 (running command "fastboot oem get_identifier_token").
Command "fastboot devices" shows my phone in a fastboot mode:
\> fastboot devices
mt6589_phone_720pv2 fastboot
But none of fastboot oem commands executes successfully (including "get_identifier_token").
Instead I get only three dots ("...") and nothing changes after that:
\> fastboot oem get_identifier_token
...
Other commands (like fastboot reboot) function, but not "fastboot oem get_identifier_token". I can't unlock my bootloader, could you please help!
Click to expand...
Click to collapse
Never seen that before but since we have S-off now you can unlock the bootloader without HTCDev
check out the revone thread in the Original Development section.
If you're using Windows 8, I would use the following link that I've seen floating around here"
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
I had issues getting the token for mine until I used that guide to convert my Microsoft USB 3.0 drivers into Intel drivers.
gunnyman said:
Never seen that before but since we have S-off now you can unlock the bootloader without HTCDev
check out the revone thread in the Original Development section.
Click to expand...
Click to collapse
Thanks for this advice, I am now trying to do it with revone.
I have successfully pushed the file to the phone, but when executing adb shell commands I get a error:
"- exec '/system/bin/sh' failed: No such file or directory"
How to fix it?
andrey o said:
Thanks for this advice, I am now trying to do it with revone.
I have successfully pushed the file to the phone, but when executing adb shell commands I get a error:
"- exec '/system/bin/sh' failed: No such file or directory"
How to fix it?
Click to expand...
Click to collapse
Not sure, but the folks in that thread are super helpful
you're in an ADB shell when you execute the command?
gunnyman said:
Not sure, but the folks in that thread are super helpful
you're in an ADB shell when you execute the command?
Click to expand...
Click to collapse
Yes, I am now reading that thread to find the answer.
Here's what i do and what I get:
> adb devices
List of devices attached
0123456789ABCDEF recovery
> adb push revone /data/local/tmp/
4584 KB/s (648208 bytes in 0.138s)
>adb shell cd /data/local/tmp
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
Start the shell. Then do the cd command separately
gunnyman said:
Start the shell. Then do the cd command separately
Click to expand...
Click to collapse
same result
> adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
Is the phone in recovery or booted up? Needs to be booted
gunnyman said:
Is the phone in recovery or booted up? Needs to be booted
Click to expand...
Click to collapse
It was in recovery mode - my mistake, thank you for pointing.
I have booted it and executed the needed commands, but still another mistake:
>sudo adb shell
[email protected]:/ # cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
[email protected]:/data/local/tmp # ./revone -P
revone v0.2.1
revone failed (error code = 1)
1|[email protected]:/data/local/tmp #
Step by step I am coming closer to the result, thanks so much for your help

[Q] KFHD 7 Gen3 11.3.2.1 root

Hello,
I've tried to root my KFHD Gen 3 SW 11.3.2.1.
I've installed ADB interface and windows recognizes the KFHD as "Android Composite ADB Interface" in the hardware- manager.
First attemp to root: "Restore_by_Bin4ry_v31" an original "stock" cable. Batchfile runs, device is making backup, restarts 2 time - no root access
Second attemp: Selfmade fastboot cable. KFHD boots in fastboot mode und I've tried "11.3.2.1_root_script.zip" from xda forum - no root access.
Step- by step:
- connect with factory cable
- start runme.bat:
sending 'boot' (5846 KB)... OKAY [ 0.691s]
writing 'boot'... OKAY [ 0.437s]
finished. total time: 1.129s
...
Device detected: KFSOWI (JDQ39)
Attempt acdb exploit...
KFSOWI (JDQ39) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
ioctl: Bad address
Attempt fb_mem exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt perf_swevent exploit...
Root complete. Rebooting to fastboot...
Upgrade complete. Deactivating updates...
resuming boot... OKAY [ 0.001s]
finished. total time: 0.001s
[email protected]:/ $
KFHD reboots. Nothing happens. In the runme.bat are a lot more commands, but the command window isn't executing anything? Is the In the runme.bat are the next commands:
adb wait-for-device
echo Device connected. Pushing files...
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
echo Changing permissions...
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
echo Executing Exploit (could take some time, be patient!)
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
echo.
echo.
adb reboot
echo Root complete. Rebooting to fastboot...
fastboot -i 0x1949 wait-for-device
fastboot -i 0x1949 flash boot new-boot-prod.img
echo.
echo.
echo Upgrade complete. Deactivating updates...
fastboot -i 0x1949 continue
adb wait-for-device
adb shell
when i enter the commands by myself, it is not working. "Device not found"?
When i open another cmd window and enter the commands, it tells me, after executing
"adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"":
Error No such file or directory
Failed to obtain root privilege.
....
What can I do?

[Tool] Flashe 1.2

Welcome to Flashe!:victory:
Flashe is basically an all-in-one installer which only requires a few clicks and you are root,unlocked(bootloader), and you can choose a recovery to install in the process. This is much easier than using ADB commands or fastboot.:good:
The program does included a feature that allows you to use a custom boot image and get rid of the "unlocked bootloader" screen.
WARNING: USE AT YOUR OWN RISK
Requirements:
-Atrix HD,Razr HD,Razr MAXX
- .bin logo file(rename to logo when put in flashe folder)
- .iso for your recovery(CWM,TWRP, or Philz)
Future Update:
-Downloads the required files from a server
-Menu(choose to install other things
-GUI, instead of text there is a actual button interface.
Errors:
You MUST allow the program to boot you into recovery otherwise the custom recovery is lost due to the android os overwriting it. If you have any other errors pm
me!
This uses djrbliss's exploit,special thanks to him for his exploit, but the rest is all coded in by me.
Enjoy!
Alienware258 said:
This uses djrbliss's exploit,special thanks to him for his exploit, but the rest is all coded in by me.
Click to expand...
Click to collapse
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
quasihellfish said:
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
Click to expand...
Click to collapse
I totally agree
quasihellfish said:
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
Click to expand...
Click to collapse
I looked at the threat, and it calls it a threat because it is a rooting tool.
Also,When I first started rooting I did not get how to use it at all(Mythtools).Instead I used programs on my android.So I made this to help new users coming to the atrix community once I finished learning ADB commands and some fastboot commands.
Here is the source:
Code:
adb kill-server
adb wait-for-device
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb install Superuser.apk
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
adb shell rm /data/local/tmp/su
adb shell rm /data/local/tmp/busybox
adb reboot
adb wait-for-device
adb push unlock /data/local/tmp
adb shell chmod 755 /data/local/tmp/unlock
adb shell su -c /data/local/tmp/unlock
adb shell rm /data/local/tmp/unlock
adb reboot bootloader
fastboot getvar all
fastboot continue
adb wait-for-device
adb reboot bootloader
echo [-] To continue you will need a boot file which will
echo [-] replace the "Unlocked Bootloader" image. Name it:
echo [-] logo.bin
echo [-] Continue when you are in the bootloader and have the file.
pause
fastboot flash logo logo.bin
fastboot continue
echo [-] Processe complete!
echo [-] -Root installed
echo [-] -Bootloader unlocked
echo [-] ---------------------
echo [-] This next step will install a recovery.
echo [-] Recovery will allow you to install your own roms,etc(depending on the selected recovery)
echo [-] Rename your recovery image "rec" so it should be 'rec.img' then continue.
pause
adb reboot bootloader
echo [-] Continue once in bootloader
pause
fastboot devices
fastboot flash recovery rec.img
echo [-] Once finished flashing continue...
pause
adb reboot recovery
echo [-] Complete! You now should have recovery installed. Enjoy!
pause

Unable to use ADB Push on 3t

I'm unable to use the adb push command on my rooted OnePlus 3t running OOS 4.0.2. My device shows up after typing adb shell and im also able to execute 'su' command but after that if i try adb push <source> <destination> it returns the following
OnePlus3T:/ $ su
OnePlus3T:/ # adb push 1Carbon /sdcard/
sush: adb: not found
127|OnePlus3T:/ #
I've already downloaded the latest platform-tools and drivers.
is there any solution for this? Thanks in advance!
UTK18 said:
I'm unable to use the adb push command on my rooted OnePlus 3t running OOS 4.0.2. My device shows up after typing adb shell and im also able to execute 'su' command but after that if i try adb push <source> <destination> it returns the following
OnePlus3T:/ $ su
OnePlus3T:/ # adb push 1Carbon /sdcard/
sush: adb: not found
127|OnePlus3T:/ #
I've already downloaded the latest platform-tools and drivers.
is there any solution for this? Thanks in advance!
Click to expand...
Click to collapse
You don't do adb shell,that means your running this command from your phone's terminal which isn't what your trying to do.sp instead of adb shell just do the ADB push command
HeXDeMoN said:
You don't do adb shell,that means your running this command from your phone's terminal which isn't what your trying to do.sp instead of adb shell just do the ADB push command
Click to expand...
Click to collapse
Ohh such a beginners mistake there xD Also, im trying to push some pics via adb so that their timestamp is preserved and it requires me to run adb as root. i now tried adb root and then the push command which worked but timestamps were still altered. what am i doing wrong now?
Anyone?
Bump.

Categories

Resources