Database Develop

[Q] My HTC One International is not showing any CID

Question 1: Is this normal, if yes, then how can i find my CID?
{
"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"
}
Question 2: S-OFF or HTCDev unlock?
Question 3: If S-OFF, which method is easier/better revolutionary or moonshine?

Asad_612 said:
Question 1: Is this normal, if yes, then how can i find my CID?
View attachment 2091535
Question 2: S-OFF or HTCDev unlock?
Question 3: If S-OFF, which method is easier/better revolutionary or moonshine?
Click to expand...
Click to collapse
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal preference. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.

bobsie41 said:
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal preference. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.
Click to expand...
Click to collapse
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app

randykzc said:
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
That is only if you do it with the instructions on HTCDEV. With S-OFf you can relock and it will show LOCKED.

fastboot oem readcid

randykzc said:
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
There is an ADB command to change it to 'locked' instead of 'relocked'. It's mentioned in revone's thread:
http://forum.xda-developers.com/showthread.php?t=2314582
I used revone to S-OFF and it was quite easy.
Code:
./revone -l

bobsie41 said:
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal prefierence. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.
Click to expand...
Click to collapse
1. I saw other devices pictures which showed CID in bootloader mode, and also my previous HTC OneX had such information available.
2. I'be read somewhere users having issues with S-Off with HTC one. Previously I had Inc S and I S-Off it using revolutionary.
Thanks.

Asad_612 said:
1. I saw other devices pictures which showed CID in bootloader mode, and also my previous HTC OneX had such information available.
2. I'be read somewhere users having issues with S-Off with HTC one. Previously I had Inc S and I S-Off it using revolutionary.
3. Can you provide me the link of renove S-Off?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2314582

TarekElsakka said:
There is an ADB command to change it to 'locked' instead of 'relocked'. It's mentioned in revone's thread:
http://forum.xda-developers.com/showthread.php?t=2314582
I used revone to S-OFF and it was quite easy.
Code:
./revone -l
Click to expand...
Click to collapse
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.

Asad_612 said:
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.
Click to expand...
Click to collapse
Uncheck in settings/energy/fastboot and close (at the bottom). That may help.

gee2012 said:
Uncheck in settings/energy/fastboot and close (at the bottom). That may help.
Click to expand...
Click to collapse
unchecked, but still the same error :/

Asad_612 said:
unchecked, but still the same error :/
Click to expand...
Click to collapse
Is usb debugging enabled and is HTC Sync manager not running?

gee2012 said:
Is usb debugging enabled and is HTC Sync manager not running?
Click to expand...
Click to collapse
usb debuggin enabled and sync manager updated and running as well...still device not connected error

Asad_612 said:
usb debuggin enabled and sync manager updated and running as well...still device not connected error
Click to expand...
Click to collapse
You have to close sync manager (best is to uninstall except the drivers).

gee2012 said:
You have to close sync manager (best is to uninstall except the drivers).
Click to expand...
Click to collapse
Tried that too, still nothing ... is there any shortcup sort of adb files?
I dont know if there is an issue with my adb files or something else...cause i can start adb shell, but im having problem with it detecting my device...

Asad_612 said:
Tried that too, still nothing ... is there any shortcup sort of adb files?
I dont know if there is an issue with my adb files or something else...cause i can start adb shell, but im having problem with it detecting my device...
Click to expand...
Click to collapse
There is a problem with your drivers somehow, go to device manager in windows and delete the phone from the list. Reboot the pc and try again.

Asad_612 said:
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.
Click to expand...
Click to collapse
"adb push" command is not shell command!
you need type: adb push revone /data/local/tmp/ before you entered into shell by "adb shell".
1) adb push revone /data/local/tmp/
2) adb shell
3) and so on..

tash2013 said:
"adb push" command is not shell command!
you need type: adb push revone /data/local/tmp/ before you entered into shell by "adb shell".
1) adb push revone /data/local/tmp/
2) adb shell
3) and so on..
Click to expand...
Click to collapse
yea i figured that, but still got error, see this:
Code:
C:\fastboot>adb push revone /data/local/tmp/
2048 KB/s (648208 bytes in 0.309s)
C:\fastboot>cd /data/local/tmp
The system cannot find the path specified.
C:\fastboot>adb shell chmod 755 /data/local/tmp/revone
C:\fastboot>adb shell
[email protected]:/ $ busybox df -h
busybox df -h
/system/bin/sh: busybox: not found
127|[email protected]:/ $

Asad_612 said:
yea i figured that, but still got error, see this:
Code:
C:\fastboot>adb push revone /data/local/tmp/
2048 KB/s (648208 bytes in 0.309s)
C:\fastboot>cd /data/local/tmp
The system cannot find the path specified.
C:\fastboot>adb shell chmod 755 /data/local/tmp/revone
C:\fastboot>adb shell
[email protected]:/ $ busybox df -h
busybox df -h
/system/bin/sh: busybox: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
"C:\fastboot>cd /data/local/tmp" What is it??? You need here to specify a way to yours adb.exe file.
if youer adb.exe in c:\fastboot folder you need
1) c:\fastboot> adb shell
2) [email protected]:/ $ cd /data/local/tmp
3) [email protected]:/ $ chmod 755 revone
4) and so on ..regarding s-off thread

tash2013 said:
"C:\fastboot>cd /data/local/tmp" What is it??? You need here to specify a way to yours adb.exe file.
if youer adb.exe in c:\fastboot folder you need
1) c:\fastboot> adb shell
2) [email protected]:/ $ cd /data/local/tmp
3) [email protected]:/ $ chmod 755 revone
4) and so on ..regarding s-off thread
Click to expand...
Click to collapse
My adb files are in c:\fastboot folder, i followed the process and this is the result, its still not detecting the device:
Code:
C:\fastboot>
C:\fastboot>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 /data/local/tmp/revone
chmod 755 /data/local/tmp/revone
[email protected]:/data/local/tmp $ adb devices
adb devices
List of devices attached
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
251|[email protected]:/data/local/tmp $

HELP Needed Urgent!!

i got my htc one to s-off so that i could come flash RUU to come back to stock. But now i want to get my phone back to s-on. Have any idea how to do so??

susmit95 said:
i got my htc one to s-off so that i could come flash RUU to come back to stock. But now i want to get my phone back to s-on. Have any idea how to do so??
Click to expand...
Click to collapse
You might want to put a description of what you need into your thread titles, as people are much more likely to help you.

Back to S.ON - e.g. sent your device to HTC for service:
*Android SDK, ADB and Fastboot installed
*Stock unmodified hboot!!
*Download: revone
Enable USB-Debugging and boot your device into Android and connect it to your PC, then go on...
Boot your device into Android, enable USB-Debugging and connect it to your PC, then go on...
1. Put revone file in your fastboot/adb folder.
2. Open CMD and navigate to your fastboot/adb folder.
3. Insert following commands in CMD (step by step):
adb push revone /data/local/tmp/
adb shell
cd /data/local/tmp
su
./revone -l
4. Reboot your device to Bootloader
5. Insert following commands in CMD (step by step):
fastboot oem writesecureflag 3

cherrytontonne said:
Back to S.ON - e.g. sent your device to HTC for service:
*Android SDK, ADB and Fastboot installed
*Stock unmodified hboot!!
*Download: revone
Enable USB-Debugging and boot your device into Android and connect it to your PC, then go on...
Boot your device into Android, enable USB-Debugging and connect it to your PC, then go on...
1. Put revone file in your fastboot/adb folder.
2. Open CMD and navigate to your fastboot/adb folder.
3. Insert following commands in CMD (step by step):
adb push revone /data/local/tmp/
adb shell
cd /data/local/tmp
su
./revone -l
4. Reboot your device to Bootloader
5. Insert following commands in CMD (step by step):
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
its compulsory to get my phone rooted??

its compulsory to get my phone rooted??
Click to expand...
Click to collapse
You don't need a root to use "./revone -l " and "fastboot oem writesecureflag 3" commands.

[Q] change "relocked" to "locked" when putting phone back to stock?

[Q] change "relocked" to "locked" when putting phone back to stock?
I followed this thread but mine says "relocked" and it still says S-OFF. is it possible to get it to say "locked" without going through the whole process of unlocking, rooting, and using revone again?
I'm sending my phone back to get the screen replaced which isn't under warranty, so does it even matter that it says "relocked?"

mcarswell said:
I followed this thread but mine says "relocked" and it still says S-OFF. is it possible to get it to say "locked" without going through the whole process of unlocking, rooting, and using revone again?
I'm sending my phone back to get the screen replaced which isn't under warranty, so does it even matter that it says "relocked?"
Click to expand...
Click to collapse
Use revone -l to change back to "locked"

There is not a way without rerooting for Tue device to day say locked and not relocked BUT you can easily get rid of S-Off. It doesn't take long either...
1.) Reroot.
2.) Download revone to computer.
3.) Navigate Using Command Prompt to where revone file is located on computer and move the Downloaded file to /data/local/tmp using the command "adb push revone /data/local/tmp" without quotations while phone is booted into OS and connected to computer.
3.) Use Command Prompt with phone connected to computer to run these commands or you can use Terminal Emulator app without a computer but will need a computer later on to run RUU again...
3A.) adb shell
3B.) su(SU Will Now Request SU Access For ADB Shell, Grant It)
3C.) cd /data/local/tmp
3D.) chmod 755 revone
4.) Reboot device
5.) Once device is fully booted back up run these commands again while connected to computer
5A.) adb shell
5B.) su(Will Not Need To Request Access Again)
5C.) cd /data/local/tmp
5D.) ./revone -P(If It Tells You "No Need To Reboot" Then Move On To Step 7 And If It Tells You To "Reboot To Continue" Move On To Step 6).
6.) Reboot
7.) Once fully booted back into OS open another command prompt and run these commands with Command Prompt while connected to computer.
7A.) adb shell
7B.) su
7C.) cd /data/local/tmp
7D.) ./revone -s 0 -u(To Be Safe).
7E.) Reboot
8.) Once again open another command prompt window and run these commands
8A.) adb shell
8B.) su
8C.) cd /data/local/tmp
8D.) ./revone -t -l
9.) Reboot
10.) Run RUU And Allow It To Successfully Complete.
11.) Once booted back into OS open command prompt and type in the final two commands
11A.) adb reboot bootloader
12.) Once it boots into bootloader and recognizes device type in this command
12A.) fastboot oem writesecureflag e
Sent from my HTCONE using Tapatalk 4

[GUIDE] Obtaining S-OFF on Sprint HTC One HBOOT 1.57

I had some trouble getting S-OFF using HBOOT 1.57, and I finally got it. Here is what I did in hopes someone may find it useful:
Before you Begin:
If you get stuck at the white HTC Logo when booting or you get "Process com.htc.dialer isn't responding" at any point in this guide, or even before it, you are likely missing your Radio. (I don't know exactly how this happens, but it apparently does sometimes.) I had this problem once, and flashing the latest radio from here in recovery fixed it.
Steps:
Flash this ROM. (Other ROMs may work, but this one gave me no trouble at all)
Flash this Kernel. <-- Important! Firewater will fail if you don't do this!
Follow the Firewater Instructions to obtain S-OFF. It should work the very first time. (Use the "normal, rooted device method" set of instructions.)
You should now be S-OFF! After this, you can proceed to flash your favorite ROMs Kernels, and HBOOTs. If you would like to downgrade to HBOOT 1.44 (I did), you can find the files here.
Please post if this works for you or if you need help. Thanks to all the developers who made this possible!

Thank you very so much
thank you very much you helped me save my htc was like brick but since I got resurrect from your guide

Branchys said:
thank you very much you helped me save my htc was like brick but since I got resurrect from your guide
Click to expand...
Click to collapse
Awesome! Glad I could help.

Question
Pew446 said:
I had some trouble getting S-OFF using HBOOT 1.57, and I finally got it. Here is what I did in hopes someone may find it useful:
Before you Begin:
If you get stuck at the white HTC Logo when booting or you get "Process com.htc.dialer isn't responding" at any point in this guide, or even before it, you are likely missing your Radio. (I don't know exactly how this happens, but it apparently does sometimes.) I had this problem once, and flashing the latest radio from here in recovery fixed it.
Steps:
Flash this ROM. (Other ROMs may work, but this one gave me no trouble at all)
Flash this Kernel. <-- Important! Firewater will fail if you don't do this!
Follow the Firewater Instructions to obtain S-OFF. It should work the very first time. (Use the "normal, rooted device method" set of instructions.)
You should now be S-OFF! After this, you can proceed to flash your favorite ROMs Kernels, and HBOOTs. If you would like to downgrade to HBOOT 1.44 (I did), you can find the files here.
Please post if this works for you or if you need help. Thanks to all the developers who made this possible!
Click to expand...
Click to collapse
Hi, what specific ROM and Kernel version did you use to get Firewater to work? I have flashed rom Bad_Boyz_Sprint_ONE_Sense_6_v1.0 and Kernel ElementalX-sprint-m7-13.1 but USB debugging is not working and Firewater is not working properly, I am guessing its a kernel issue. I leave everything on default while installing Kernel thru TWRP. Can you confirm? I appreciate the help

DanielGalan said:
Hi, what specific ROM and Kernel version did you use to get Firewater to work? I have flashed rom Bad_Boyz_Sprint_ONE_Sense_6_v1.0 and Kernel ElementalX-sprint-m7-13.1 but USB debugging is not working and Firewater is not working properly, I am guessing its a kernel issue. I leave everything on default while installing Kernel thru TWRP. Can you confirm? I appreciate the help
Click to expand...
Click to collapse
Did you check if your fastboot drivers are working?

StormyNight said:
Did you check if your fastboot drivers are working?
Click to expand...
Click to collapse
Yes, I did fastboot devices and I got the device listed there. Although I could see that in the phone it does not appear the 4 bars of USB debugging. I had it checked in the Dev Options. When I do the same with the stock 4.4.2 I do get those 4 bars and the indication that the USB debugging is active.

DanielGalan said:
Yes, I did fastboot devices and I got the device listed there. Although I could see that in the phone it does not appear the 4 bars of USB debugging. I had it checked in the Dev Options. When I do the same with the stock 4.4.2 I do get those 4 bars and the indication that the USB debugging is active.
Click to expand...
Click to collapse
Does fastboot devices work in the bootloader?

StormyNight said:
Does fastboot devices work in the bootloader?
Click to expand...
Click to collapse
Yes it gets recognized. But when I turn on the phone and try to run the firewater commands it does nothing. No error nor the prompt of the disclaimer. I thought I better asked you and see if you have any idea of what could be wrong.

DanielGalan said:
Yes it gets recognized. But when I turn on the phone and try to run the firewater commands it does nothing. No error nor the prompt of the disclaimer. I thought I better asked you and see if you have any idea of what could be wrong.
Click to expand...
Click to collapse
firewater, I believe runs with the phone booted into android, not fastboot.

Aldo101t said:
firewater, I believe runs with the phone booted into android, not fastboot.
Click to expand...
Click to collapse
Yeah. I just booted to fastboot to check the drivers. When I push the firewater file I get success. Its just the last command that does no action.

DanielGalan said:
Yeah. I just booted to fastboot to check the drivers. When I push the firewater file I get success. Its just the last command that does no action.
Click to expand...
Click to collapse
Verify if the file access permissions changed.. it might be that chmod isn't working.

StormyNight said:
Verify if the file access permissions changed.. it might be that chmod isn't working.
Click to expand...
Click to collapse
Hi. I meant adb devices. And I was wondering how do I check the file permissions. Can I try to copy firewater with a root file manager ? Thank you
This is what I get in adb
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
5927 KB/s (4522136 bytes in 0.745s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
After this, there is no action from firewater. I should get a warning prompt, but I don't.

DanielGalan said:
Hi. I meant adb devices. And I was wondering how do I check the file permissions. Can I try to copy firewater with a root file manager ? Thank you
This is what I get in adb
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
5927 KB/s (4522136 bytes in 0.745s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
After this, there is no action from firewater. I should get a warning prompt, but I don't.
Click to expand...
Click to collapse
Are you doing adb reboot before doing adb wait-for-device? Also make sure that your device has no lock mechanism enabled (pattern lock etc).

StormyNight said:
Are you doing adb reboot before doing adb wait-for-device? Also make sure that your device has no lock mechanism enabled (pattern lock etc).
Click to expand...
Click to collapse
I do, this is what I found weird. Screenshot 1 is stock rom 4.4.2 and it says USB debugging enabled. Screenshot 2&3 is Bad_Boyz_Sprint_ONE_Sense_6_v1.0 ROM with its default kernel, it shows no USB debugging enabled even when its selected

DanielGalan said:
I do, this is what I found weird. Screenshot 1 is stock rom 4.4.2 and it says USB debugging enabled. Screenshot 2&3 is Bad_Boyz_Sprint_ONE_Sense_6_v1.0 ROM with its default kernel, it shows no USB debugging enabled even when its selected
Click to expand...
Click to collapse
No idea :S You might want to uncheck Verify apps over USB in Screenshot 3 btw.

StormyNight said:
No idea :S You might want to uncheck Verify apps over USB in Screenshot 3 btw.
Click to expand...
Click to collapse
I tried but no luck. Is there any other ROM I could try firewater with? I was thinking maybe the Venom.

DanielGalan said:
I tried but no luck. Is there any other ROM I could try firewater with? I was thinking maybe the Venom.
Click to expand...
Click to collapse
Try following the instructions on this post.

StormyNight said:
Try following the instructions on this post.
Click to expand...
Click to collapse
Thank you for bearing with me.
I did as indicated on that post, but still having issues with firewater. This is what I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA34MS906354 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
4533 KB/s (4522136 bytes in 0.974s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
←7←[r←[999;999H←[[email protected]:/ $ su
su
←7←[r←[999;999H←[[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
There is no action after this

DanielGalan said:
Thank you for bearing with me.
I did as indicated on that post, but still having issues with firewater. This is what I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA34MS906354 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
4533 KB/s (4522136 bytes in 0.974s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
←7←[r←[999;999H←[[email protected]:/ $ su
su
←7←[r←[999;999H←[[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
There is no action after this
Click to expand...
Click to collapse
Try flashing an older release of CyanogenMod - I'd try Snapshot M8.

StormyNight said:
Try flashing an older release of CyanogenMod - I'd try Snapshot M8.
Click to expand...
Click to collapse
Hi, I tried but I had the same results, the commands are accepted but there is no action after the last one . I'm gonna do a last attempt on my other computer and see if it works.

Tell me what this fastboot command would do

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