Related
For those who prefer manually rooting their NST with the NookDevs method, here's a modified uRamdisk based on the 1.1 update:
WiFi version:
uRamdisk_1_1_rooted_wifi
USB version:
uRamdisk_1_1_rooted_usb
As always, take your time to do a proper backup first!
ros87 said:
For those who prefer manually rooting their NST with the NookDevs method, here's a modified uRamdisk based on the 1.1 update:
uRamdisk_1_1_rooted
As always, take your time to do a proper backup first!
Click to expand...
Click to collapse
This USB access or Wifi access? If it's USB access I can add it to TouchNooter instead of repacking my own version of uRamdisk
GabrialDestruir said:
This USB access or Wifi access? If it's USB access I can add it to TouchNooter instead of repacking my own version of uRamdisk
Click to expand...
Click to collapse
Added both wifi and usb-only version to OP.
If I use this method can I add nook color tools back to my touch?
ryanpl said:
If I use this method can I add nook color tools back to my touch?
Click to expand...
Click to collapse
root is root, you can adb install / push whatever you want
If you're unsure about doing things manually you should probably wait for GabrialDestruir to release a updated version of TouchNooter.
How is the adb over usb supposed to work? I replaced the uRamdisk with the one with usb for 1.1 after booting with noogie, but when i hook the nook up to my computer with usb and do "adb devices" i don't see anything.
check adb links from http://forum.xda-developers.com/showthread.php?t=1138564
In short: on linux dbus rules (tested, working). on windows you need drivers,
cceerrtt said:
check adb links from http://forum.xda-developers.com/showthread.php?t=1138564
In short: on linux dbus rules (tested, working). on windows you need drivers,
Click to expand...
Click to collapse
Ahha, thank you! Will try with the windows drivers.
nickveldrin said:
Ahha, thank you! Will try with the windows drivers.
Click to expand...
Click to collapse
The usb ramdisk works just fine.
Getting the drivers installed on windows can be a bit of a pain
Yeah, the xboxexpert drivers I installed for ADB over USB just mucked things up for me. Gonna stick to wifi for now, I suppose...
-e
P.S. Yay I can finally post here!
---------- Post added at 07:09 PM ---------- Previous post was at 06:36 PM ----------
A big thank you to ros for this. With the ADB over WiFi uRamdisk, WiFi works again! (As does adb, doy)
-e
hmm...
I have had some amount of success with this, but it doesn't seem to be complete. Followed instructions and copied uRamdisk wifi over, and can get adb to work over wireless, but for some reason superuser is borked. I don't think I actually have root, although when I login through adb shell, it displays the #. Gonna try to do it again.
LastSilmaril said:
Yeah, the xboxexpert drivers I installed for ADB over USB just mucked things up for me. Gonna stick to wifi for now, I suppose...
-e
P.S. Yay I can finally post here!
---------- Post added at 07:09 PM ---------- Previous post was at 06:36 PM ----------
A big thank you to ros for this. With the ADB over WiFi uRamdisk, WiFi works again! (As does adb, doy)
-e
Click to expand...
Click to collapse
vatoamigo said:
I have had some amount of success with this, but it doesn't seem to be complete. Followed instructions and copied uRamdisk wifi over, and can get adb to work over wireless, but for some reason superuser is borked. I don't think I actually have root, although when I login through adb shell, it displays the #. Gonna try to do it again.
Click to expand...
Click to collapse
Not entirely sure what your mean?
If you got adb access with root prompt (#), then the uRamdisk is doing exactly what it should
If you need su and Superuser, then you have to add them to your system manually, this is not related to the uRamdisk.
ah
Yeah, I suppose you're right, that's the problem. I guess I need to upload su and superuser manually. Do you have a link that shows me how to do that? I looked everywhere for a superuser.apk, but can't get market working.
Everywhere? I guess you should try google at the first place. It took me 10 second to find this link.
http://nookdevs.com/NookColor_Installing_su_and_the_Superuser_app
It is actually the same howto I used some time ago.
the secrets of google...
cceerrtt said:
Everywhere? I guess you should try google at the first place. It took me 10 second to find this link.
http://nookdevs.com/NookColor_Installing_su_and_the_Superuser_app
It is actually the same howto I used some time ago.
Click to expand...
Click to collapse
I appreciate the link. I actually did try google, but apparently wasn't successful. Thanks.
Hi, BIG thanks for the file, works like a charm.
Edit (don't want to add meaningless message to this tread)
Thanks for your kindness.
UomoNero said:
I have a strange problem with superuser, apparently installing su mess with my nook; my nook think that the battery is 0% but when i uninstall su and superuser package works fine.
I'm the only one with this problem? Is somehow related to 1.1 update?
Thanks for your kindness
Click to expand...
Click to collapse
That question is better asked in a new thread as it's not related to uRamdisk
fwiw, I pulled su from TouchNooter and Superuser.apk from my phone and it works without problems on 1.1.0.
In your case I'd try Settings->Device Info->Erase and Deregister Device
This will force cache and databases to be rebuilt which often solves strange problems like that.
Can't get this to work... I've installed a fresh 1.1.0 update, changed ramdisk to support adb through usb, changed both adb_usb and android_winusb. After installing drivers when i connect my nook it shows as "Android ADB interface", but adb devices shows nothing
EDIT: Solved! Had to modify android_winusb a little bit more...
ros87 said:
For those who prefer manually rooting their NST with the NookDevs method, here's a modified uRamdisk based on the 1.1 update:
WiFi version:
uRamdisk_1_1_rooted_wifi
USB version:
uRamdisk_1_1_rooted_usb
As always, take your time to do a proper backup first!
Click to expand...
Click to collapse
Multiupload is down...
Googie2149 said:
Multiupload is down...
Click to expand...
Click to collapse
And still is.
Sorry for the necromancy, but can somebody please re-upload those IMG files? thanks!
Ok, this isn't my first rodeo as I've owned many android devices including the old nexus 7. I'm trying to unlock and root this but I can't install the drivers. I tried the device manager method and when I search it can't find anything and I tried a website to manually do it by downloading a zip and choosing it to no avail. Any one have the link to the drivers as that website may not of been accurate or anyone have any other suggestions?
You need to unzip it first.
Username invalid said:
You need to unzip it first.
Click to expand...
Click to collapse
Yes I did that and it only had two folders that showed up while browsing in the update drivers part in device manager. One was AMD86 and the other was i3 something and neither of those matched the picture in the steps but I used the link given within the same tutorial.
http://developer.android.com/sdk/win-usb.html
Username invalid said:
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Ok I still cannot install the drivers. When I downloaded the file provided in that link, there are no driver options at all. There are only two folders in which I described in my previous post and neither have drivers in them. I'm no noob and have done this plenty of times, I even tried to adb reboot bootloader and it says device not found and yes USB debugging is on so I'm assuming I can't do anything until I some how install the drivers.
Which website guide are you looking at?
Username invalid said:
Which website guide are you looking at?
Click to expand...
Click to collapse
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
C-4Nati said:
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
Click to expand...
Click to collapse
If nothing else works, you might consider partitioning your hard drive and installing a secondary OS. Both Windows 8.1 and Ubuntu worked for me no problem.
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
cd Downloads
fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
adb push update-supersu-v1.51.zip /sdcard/Downloads
C-4Nati said:
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
Click to expand...
Click to collapse
Ok I installed the drivers correctly, I figured it out. Now when I try the adb commands it says device offline when it's clearly not lol...
I've got everything working now and unlocked and rooted. I appreciate all the help you have offered to me. I do not remember it being this difficult with the original Nexus 7 lol.
C-4Nati said:
Ok I installed the drivers correctly, I figured it out. Now when I try the adb commands it says device offline when it's clearly not lol...
Click to expand...
Click to collapse
Fastboot is all you need to root your device.
C-4Nati said:
I've got everything working now and unlocked and rooted. I appreciate all the help you have offered to me. I do not remember it being this difficult with the original Nexus 7 lol.
Click to expand...
Click to collapse
I'm having a similar problem with drivers, why don't you post how you solved it? I am trying on 2 different windows 7 machines. google drivers don't load, asus drivers don't load. Device manager just says "windows could not find driver software for your device."
---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------
I figured it out, have to turn MTP on, then install drivers - then you can turn MTP back off if you want.
How to ROOT your T-Mobile Galaxy S4 on a Mac / Linux PC using Heimdall
Before you do ANYTHING, start here:
Download and install Heimdall: http://www.glassechidna.com.au/products/heimdall/
And Install libusbx: http://libusbx.org/
What is Heimdall?
Heimdall is a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung Galaxy S devices.
What is libusbx?
libusbx is a library that provides generic access to USB devices. As a library, it is meant to be used by developers, to facilitate the production of applications that communicate with USB hardware.
Click to expand...
Click to collapse
Onto the magic..
1. Download CF-Root by Chainfire here: http://forum.xda-developers.com/showthread.php?t=2294005
2. Unzip the file: CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip
3. Unzip the file called "CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5" that is inside the original zip file.
4. You should end up with "recovery.img" and "cache.img.ext4" (Put them on your desktop or somewhere easy to navigate to!)
5. Put your phone into download mode. (Hold Volume down + Power + Home button)
6. Connect your phone to your computer.
6. Open your favorite Terminal program on your computer. (I use the stock Mac Terminal)
7. Run the following command:
sudo heimdall flash --RECOVERY *RECOVERY DIRECTORY* --CACHE *CACHE DIRECTORY*
NOTE: Replace *RECOVERY DIRECTORY* and *CACHE DIRECTORY* to the full path of where the file is on your computer!
NOTE: --RECOVERY and --CACHE are CASE SENSITIVE!
For example: heimdall flash --recovery C:\Users\user\Desktop\recovery.img --cache C:\Users\user\Desktop\cache.img.ext4
8. Your phone should reboot.
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
9. Done!
Note: This does not install a custom recovery, but you can download ROM Manager from the Play Store and install ClockworkMod Recovery using that. Alternatively, you can flash a recovery.img using the same way you flashed these two files. (heimdall flash --recovery *RECOVERY DIRECTORY*)
Click to expand...
Click to collapse
Getting an error?
If you receive this error message:
Initialising connection…
Detecting device…
Claiming interface…
ERROR: Claiming interface failed!
it’s because you have used the Samsung Kies software, which you should uninstall at once, but as it adds some kernel extensions, run this as well:
A. Launch Terminal
B. Get Root and run these:
sudo sh
kextunload -b com.devguru.driver.SamsungComposite
kextunload -b com.devguru.driver.SamsungACMData
kextunload -b com.devguru.driver.SamsungACMControl
C. Try again!
Click to expand...
Click to collapse
thanks, But a couple of qns.
1. USB debugging should be turned on or off?
2. when I put the device in download mode, it asks up to cancel and down continue in download mode. What to press?
If i put down, it says - downloading do not turn off. At this time, I've not run the heimdall command yet on terminal. (Ubuntu).
The error thats spit out is:
Initialising connection...
Detecting device...
libusbx: error [op_open] libusbx couldn't open USB device /dev/bus/usb/001/007: Permission denied.
libusbx: error [op_open] libusbx requires write access to USB device nodes.
ERROR: Failed to access device. libusb error: -3
didadi said:
thanks, But a couple of qns.
1. USB debugging should be turned on or off?
2. when I put the device in download mode, it asks up to cancel and down continue in download mode. What to press?
If i put down, it says - downloading do not turn off. At this time, I've not run the heimdall command yet on terminal. (Ubuntu).
The error thats spit out is:
Initialising connection...
Detecting device...
libusbx: error [op_open] libusbx couldn't open USB device /dev/bus/usb/001/007: Permission denied.
libusbx: error [op_open] libusbx requires write access to USB device nodes.
ERROR: Failed to access device. libusb error: -3
Click to expand...
Click to collapse
1. It does not matter.
2. Yes, you press volume down to continue.
As for that error, try installing this on your Linux setup: http://libusbx.org/
It should have been bundled with Heimdall for Linux but maybe it isn't.
theexel said:
1. It does not matter.
2. Yes, you press volume down to continue.
As for that error, try installing this on your Linux setup: http://libusbx.org/
It should have been bundled with Heimdall for Linux but maybe it isn't.
Click to expand...
Click to collapse
Hmm,still the same err,but I guess I was able to detect S4.
I did install libusbx from source, by
./configure && make && make install && sudo ldconfig - blah.
Then tried to use heimdall flash command/action.
Try using sudo before the heimdall command.
sudo heimdall flash ....
theexel said:
Try using sudo before the heimdall command.
sudo heimdall flash ....
Click to expand...
Click to collapse
hmm,sudo is able to write,but stil one error, "recovery" not found in specified PIT as below. One last step?
--------
Downloading device's PIT file...
PIT file download successful.
ERROR: Partition "recovery" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------
heimdall flash --RECOVERY ./clockworkmod_6.0.3.2_jfltespr.img --no-reboot - May be like this?
---------- Post added at 11:13 PM ---------- Previous post was at 11:07 PM ----------
Alright,thank you very much!. I am rooted. Exact command to run is:
sudo heimdall flash --RECOVERY /path_to_recovery/recovery.img --CACHE /path_to_cache/cache.img.ext4
Fantastic! thanks
Glad you got it sorted!
Sent from my SGH-M919 using Tapatalk 4
theexel said:
Glad you got it sorted!
Sent from my SGH-M919 using Tapatalk 4
Click to expand...
Click to collapse
Would this also work if say...I bricked my phone?
I run windows virtualized on OpenSUSE, but the USB drivers for windows won't work in a virtual environ. I can never be too sure if I can get my hands on a windows PC.
nyloxy said:
Would this also work if say...I bricked my phone?
I run windows virtualized on OpenSUSE, but the USB drivers for windows won't work in a virtual environ. I can never be too sure if I can get my hands on a windows PC.
Click to expand...
Click to collapse
You'd probably need to flash the whole Samsung Stock firmware not just the files I listed above, but yes, it should be possible, bud. :good:
If you want me to check it out for you and write a tutorial, I'll be more than happy to me.
theexel said:
You'd probably need to flash the whole Samsung Stock firmware not just the files I listed above, but yes, it should be possible, bud. :good:
If you want me to check it out for you and write a tutorial, I'll be more than happy to me.
Click to expand...
Click to collapse
Thanks for the info! Quick tutorial would be the bomb! I just got into rooting and flashing a few weeks ago and I never want to go back! :victory:
Started using the Infamous Alpha. Currently on 8.6, and it's rock solid. I just worry that there may be a time in the near future that I brick my S4 and I'm no longer a fan of windozzz!
Just 3 big steps.
1.Download and install Heimdall: http://www.glassechidna.com.au/products/heimdall/
2. Install libusbx. You need to download the sources and compile them. Usual ./configure, make , make install.
Use sudo su and then compile.
you may have to do , sudo apt-get install libudev-dev before compiling the libusbx libs.
3.Onto the magic..
..as said in post 1....
Make sure to use sudo for the heimdall flash ...Needless to say use the caps.!
Then install cwm from the Google Play and then you are Golden.
Thank you again to theexel for quick replies thru my earlier posts.:good:
Added a fix for a possible error:
If you receive this error message:
Initialising connection…
Detecting device…
Claiming interface…
ERROR: Claiming interface failed!
Can somebody make a video on how to do this?
This sounds confusing and I don't wanna brick my phone lol
I'm willing to donate to whoever does a video!
So will this wipe my phone?
[email protected] said:
So will this wipe my phone?
Click to expand...
Click to collapse
No. It will only root your phone.
flemingg said:
There is nothing can be done without the libraries files.
Click to expand...
Click to collapse
Library files?
Noob help with installing libusbx?
Hi Guys,
First off kudos and many thanks Exel for posting this. Also, sorry to bug you all with such a noob question but may I bother someone to post the exact commands/syntax for installing libusbx on/in mac os x 10.8.x? I've tried looking online and may not be using the right keywords to get the information I need.
Thanks loads for all the help you guys,
nv_gck
Re: Noob help with installing libusbx?
NV_GCK said:
Hi Guys,
First off kudos and many thanks Exel for posting this. Also, sorry to bug you all with such a noob question but may I bother someone to post the exact commands/syntax for installing libusbx on/in mac os x 10.8.x? I've tried looking online and may not be using the right keywords to get the information I need.
Thanks loads for all the help you guys,
nv_gck
Click to expand...
Click to collapse
Hi Guys,
Please ignore my last request. I figured it out from the INSTALL file in the libusbx source code. Also, I did it without installing the full Xcode IDE on my Mac, just the Xcode terminal tools. Have successfully rooted.
Thanks again Exel
NV_GCK said:
Hi Guys,
Please ignore my last request. I figured it out from the INSTALL file in the libusbx source code. Also, I did it without installing the full Xcode IDE on my Mac, just the Xcode terminal tools. Have successfully rooted.
Thanks again Exel
Click to expand...
Click to collapse
Glad you got it working!
It would really be worth it to mention that you actually have to compile libusbx from source. I spent a half hour Googling before coming to this realization.
Hey there fellas, spent the last couple hours trying to get this to work and keep getting hung up in terminal here,
Code:
Invalid argument: folder/recovery.img
Any help?
Hello, this is my first post on this forum, though I have lurked on XDA since as far back as my droid eris.
I have looked around the kindle fire forum for the answers I seek, but I have not seen a thread that helps. If I am asking a redundant question, please kindly show me the relevant thread(s) and I will read them.
I was at a small computer store my friend owns in our tiny little town (white hat computer solutions minersville, pa), when a mutual friend and former classmate of ours brought us a Kindle Fire D01400 with a cracked screen he bought off ebay. the previous owner claimed it worked despite the cracked screen, From a hardware standpoint that is quite correct, as you can see everything yet, and the touchscreen responds.
However, they neglected to mention they were selling one that already was modified, it is running TWRP 2.4.4.0 and has an improperly flashed ROM on it ( the stock keyboard crashes, home screen soft key does nothing, gmail works, but google play store does not). sideloading a keyboard app on fixed the keyboard, but the gapps with the exception of gmail don't function. I figured doing a wipe and flash of a new rom and gapps would be a good starting point to attempt to fix this problem.
However when I go into TWRP recovery and try to wipe the system, dalvik, or cache, the operation fails.
I have tried taking the TWRP manager app and sideloading it and using that to update to the latest TWRP. but the version number remains at 2.7.0.1
So my question is, with the above details kept in mind: How exactly do I go about fixing this tablet and making it a functional piece of android hardware for my friend/customer?
Try my flash able twrp.zips thread http://forum.xda-developers.com/showthread.php?t=2811253
Kindle Fire Flashable Recoveries TWRP/COTR/CWM[2014]
Sent from my XT862 using Tapatalk
sd_shadow said:
Try my flash able twrp.zips thread http://forum.xda-developers.com/showthread.php?t=2811253
Kindle Fire Flashable Recoveries TWRP/COTR/CWM[2014]
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Downloading and trying it now. Thanks, I usually do my best to find relevant threads before posting, I am not sure how I missed that one.
Will post back with results as soon as I am done
EDIT:
Flashed it to twrp 2.6.1.0 otter I still can't use the wipe option. tried factory reset figuring i could just push the rom and gapps down using adb again, but factory reset also failed. is there a permission I can reset using adb?
vstrenko said:
I am not sure how I missed that one.
Click to expand...
Click to collapse
It's not stickied and 'flashable recoveries' can be misleading, but that is what they are called by many.
---------- Post added at 02:59 PM ---------- Previous post was at 02:05 PM ----------
vstrenko said:
Downloading and trying it now. Thanks, I usually do my best to find relevant threads before posting, I am not sure how I missed that one.
Will post back with results as soon as I am done
EDIT:
Flashed it to twrp 2.6.1.0 otter I still can't use the wipe option. tried factory reset figuring i could just push the rom and gapps down using adb again, but factory reset also failed. is there a permission I can reset using adb?
Click to expand...
Click to collapse
If you edit your post i don't get notified.
sorry I didn't realize, I lurk more than I post
vstrenko said:
sorry I didn't realize, I lurk more than I post
Click to expand...
Click to collapse
what is the rom version currently installed
full name listed in setting>about device(maybe about phone or tablet)>system version
JellyBeer-v4.33-23072013-190721
vstrenko said:
JellyBeer-v4.33-23072013-190721
Click to expand...
Click to collapse
have you used adb.exe or fastboot.exe before?
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
windows 7 or 8?
I have used adb before with my acer iconia a500 and my droid3
windows 7 64bit is my OS
vstrenko said:
I have used adb before with my acer iconia a500 and my droid3
windows 7 64bit is my OS
Click to expand...
Click to collapse
use Install.Drivers.bat from Kindle Fire Utility if you have not yet.
reboot pc, check device manager with kindle connected to PC
should be listed as an Android Phone>adb interface
if OK then
boot Kindle to TWRP
in command prompt on PC
Code:
adb devices
should get something like
Code:
123456789 recovery
if you get waiting for device for more than a few secs or or some kind of bad command error post it.
---------- Post added at 04:15 PM ---------- Previous post was at 04:03 PM ----------
if response is good
Code:
adb shell "cat /proc/cmdline"
sd_shadow said:
use Install.Drivers.bat from Kindle Fire Utility if you have not yet.
reboot pc, check device manager with kindle connected to PC
should be listed as an Android Phone>adb interface
if OK then
boot Kindle to TWRP
in command prompt on PC
Code:
adb devices
should get something like
Code:
123456789 recovery
if you get waiting for device for more than a few secs or or some kind of bad command error post it.
---------- Post added at 04:15 PM ---------- Previous post was at 04:03 PM ----------
if response is good
Code:
adb shell "cat /proc/cmdline"
Click to expand...
Click to collapse
When it is booted into android, it shows in adb as
Code:
list of devices attached
0123456789ABCDEF device
When I boot into TWRP and execute adb devices i get
Code:
list of devices attached
with no further error messages
In TWRP on the second row at the top, along with the battery level (100%) and time 5:26pm, it says SIMULATING ACTIONS in all caps. is it supposed to say that or should it say something else
vstrenko said:
When it is booted into android, it shows in adb as
Code:
list of devices attached
0123456789ABCDEF device
When I boot into TWRP and execute adb devices i get
Code:
list of devices attached
with no further error messages
In TWRP on the second row at the top, along with the battery level (100%) and time 5:26pm, it says SIMULATING ACTIONS in all caps. is it supposed to say that or should it say something else
Click to expand...
Click to collapse
ok
try
with Kindle off, but connected to PC
Code:
fastboot devices
then boot Kindle
sd_shadow said:
ok
try
with Kindle off, but connected to PC
Code:
fastboot devices
then boot Kindle
Click to expand...
Click to collapse
fastboot reports nothing at all when i try that, when i type that in it pauses for a fraction of a second then i am left with a prompt on a new line to enter a command
Code:
C:\Windows\system32\> fastboot devices
C:\Windows\system32\>
vstrenko said:
fastboot reports nothing at all when i try that, when i type that in it pauses for a fraction of a second then i am left with a prompt on a new line to enter a command
Code:
C:\Windows\system32\> fastboot devices
C:\Windows\system32\>
Click to expand...
Click to collapse
download adb-fastboot.zip
Create a folder in C drive named adb (c:adb)
Unzip adb-fastboot.zip
Copy adb/fastboot files (AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe) to folder
Connect kindle to pc, power off kindle
Open Command Prompt
Enter Commands
Code:
cd\adb
Code:
fastboot devices
power on kindle
sd_shadow said:
download adb-fastboot.zip
Create a folder in C drive named adb (c:adb)
Unzip adb-fastboot.zip
Copy adb/fastboot files (AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe) to folder
Connect kindle to pc, power off kindle
Open Command Prompt
Enter Commands
Code:
cd\adb
Code:
fastboot devices
power on kindle
Click to expand...
Click to collapse
It is on when I use fastboot devices from a command prompt.
that is what I get as a result
vstrenko said:
It is on when I use fastboot devices from a command prompt.
that is what I get as a result
Click to expand...
Click to collapse
you may not have enough posts to link images, if that was your intent
try sending a pm or email
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Kindle should be off when entering fastboot commands, because kindle is in fastboot mode only a short time when powering on
sd_shadow said:
you may not have enough posts to link images, if that was your intent
try sending a pm or email
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Kindle should be off when entering fastboot commands, because kindle is in fastboot mode only a short time when powering on
Click to expand...
Click to collapse
Previous owner of the device had the TWRP recovery set to use simulation mode. I was unaware that was even an option since i was not familar with TWRP( my previous android flashing experiences used clockwork) after unchecking those boxes in the advanced settings, I was successfully able to flash a rom and gapps, and everything was perfect after that.
sorry for wasting so much time on this, I really missed something simple on this one.
vstrenko said:
Previous owner of the device had the TWRP recovery set to use simulation mode. I was unaware that was even an option since i was not familar with TWRP( my previous android flashing experiences used clockwork) after unchecking those boxes in the advanced settings, I was successfully able to flash a rom and gapps, and everything was perfect after that.
sorry for wasting so much time on this, I really missed something simple on this one.
Click to expand...
Click to collapse
no problem, I've never used the simulation options before...
I downloaded SDK and set it up, and now I'm using the CMD with the adb commands as far as I can. Now, the problem is the following. When I type "adb devices" I get a list of around 20 items, all stating offline. I tried the restarting the server (http://forum.xda-developers.com/goog...lator-t2804157) and for a brief moment, like 2-3 sec, there is only one device, but it says offline as well.. after that, the list keeps on filling until it reaches around 20 items again. Another thing I saw and tried is using "adb -d reboot bootloader" and it gives the same "error: more than one device", this time without emulator. Another thing I tried is booting into fastboot from the phone itself and following the htcdev method, but when I try to get the token it freezes on "waiting for device" and nothing happens. So basically, I can't unlock the bootloader because I can't even see my phone in the adb devices. I have had HTC Sync isntalled along with the HTC drivers it provides. Also the Windows drivers are installed as well. As I'm typing the thread, I saw that windows has some updates that it wants to install, and I'm letting them install right now.. eventhough I doubt that this is the problem. I'm starting to feel annoyed and I'm looking for help.. any ideas are welcome....
EDIT1: I just restarted my PC with all the updates it installed. I decided to also restart my phone and re-insert the battery just in case. As a side note, when I do adb devices when my phone is unplugged, the list stays empty. After I plug my phone the process goes like I described.. like 20 devices show up, all under the same ID/Name and all with the Offline status.
P.S. - I don't have Bluestacks. I have Sandboxie and Daemon Tools but I doubt they cause the problem as I have tried without them as well.
Ok....
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
Install min adb and fastboot... After that, boot your device into bootloader..open min adb by right clicking and chose open file location..inside folder right click and hold shift and chose open cmd here..in cmd window, type fastboot devices. Let's check and see if PC sees the phone
---------- Post added at 07:10 PM ---------- Previous post was at 07:09 PM ----------
And also... What ROM u on? Sometimes cm 11 and kk ROMs won't let PC see them. There's a diff process for that
Before I go to bed...
Alright, I need some quick help before I lay to sleep.. I somehow managed to unlock the BL and flash CWM but what I don't know how to do now is flash the SU. Should I:
A) Place the .zip version of SuperSU(http://forum.xda-developers.com/showthread.php?t=1538053) in my SDcard and flash it via CWM or..
B) Download something (which, though? hAlp) from here http://androidsu.com/superuser/ and flash it via CWM..
Which one will be the most beneficial and give the root?
P.S. - I will try to explain, as far as I can and remember, what I did to get my device recognised so that the people who read can get help..
Your ROM should have supersu already installed
---------- Post added at 01:31 AM ---------- Previous post was at 01:29 AM ----------
If u flashed cwm or twrp, the option to flash supersu should automatically appear. If not, yes..flash via recovery.
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
But you need to s off to gain root