Related
Firstly, I'd like to say hello as I just recently purchased my E4GT and moved over from a HeroC. So far the community has seemed pretty warm and helpful so I'll just go ahead and get down to it: I've searched. I've Googled. I've even Youtubed but nothing seems to have an answer to my problem.
I'm running Ubuntu 11.10, up to date, with Heimdall 1.3.1 installed. My problem is that even though the device is detected in download mode, when I run
Code:
heimdall flash --kernel zImage
I keep coming up with this error
Code:
Initialising connection...
Detecting device...
libusb couldn't open USB device /dev/bus/usb/001/016: Permission denied.
libusb requires write access to USB device nodes.
ERROR: Failed to access device. libusb error: -3
Now I will admit that while I have read and reread the wiki looking for my mistake, I am fresh to the E4GT and Samsung altogether, so if this is some simpleton error I would not be entirely surprised. I'm at my wits end as I have the drivers, verified so with an ADB reboot command, so I'm not sure what my issue is. Any and all advice/help/guidance will be hugely appreciated.
Very simple fix. Follow the steps you would follow to get adb running.
---------- Post added at 08:36 AM ---------- Previous post was at 08:33 AM ----------
Here http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
CBowley said:
Very simple fix. Follow the steps you would follow to get adb running.
---------- Post added at 08:36 AM ---------- Previous post was at 08:33 AM ----------
Here http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
Click to expand...
Click to collapse
Thanks for the info, unfortunately adb is already detecting my device. Ran through the setup anyways and still the same error. I'm wondering what's causing libusb to not rw at this point.
EDIT: Gonna reboot, then give it a shot with sudo added to the flash command. May or may not work, but I'm willing to try anything before I give up and hunt down a friend with a windows machine.
EDIT2: That's exactly what it needed! Now I'm officially rooted
Sent from my SPH-D710 using XDA
Will there be any way to solve the exactly same issue but running on Windows? Btw, I am running Windows 10.
Similar problem
malatewodn said:
Will there be any way to solve the exactly same issue but running on Windows? Btw, I am running Windows 10.
Click to expand...
Click to collapse
Same problem with my tablet, trying to install TWRP
Hi. I've installed Android SDK and the API for the device (Android 4.2.2, samsung SMT110 for me, API 17). After, Heimdall was running without any problem.
My system is windows 10
Sorry guys, I've been reading all night trying to figure this out, and now my brain's all twisted, and I feel like I'm missing something obvious...
Is there a super-quick way to boot the Fire into fastboot mode once you already have FFF, TWRP, and a rooted rom installed??
The threads I've been reading all night seem to be geared to someone who doesn't have all that installed yet.
Can it be done with terminal emulator on the fire?
I had assumed it could be accessed from TWRP, but no dice. Would a quickboot app from the market get me there, like on almost every device I've used before?
Because of driver issues (that I still haven't solved) the only way I've done it before is when I installed FFF, and TWRP by shorting the board and using Ubuntu from a USB stick. (I'm wanting to switch from just having an ICS Rom to dual-booting, and I have everything ready, but I just am getting confused over how to simply get onto fastboot to accomplish this.
Thanks to anyone in advance that might help...
An easy way would be to use kfu and select boot mode 4000. Or u can just use the fast boot command
Sent from my Amazon Kindle Fire using xda app-developers app
powerpoint45 said:
An easy way would be to use kfu and select boot mode 4000. Or u can just use the fast boot command
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I need windows to recognize it that way though. That's the whole problem... I've NEVER gotten windows to pick it up but one time... Weeks ago.. Then it was softbricked.. Tried everything and finally had to use the shorting trick with the Ubuntu stick.
No, this post is about me asking if there's some other way once I've installed FFF, TWRP, and am rooted. (Like terminal emulator or something like a rooted app from the Play Store.)
Sent from my SPH-D710 using xda premium
Apparently, I can solve all my headaches by just using a factory cable?
Okay...Here's my problem there:
I've probably got 12-15 Android tablets around the house, and at least 6 phones: The number of USB cables for these devices I've collected is just silly, what with extra chargers and whatnot...
I'm sure one of them is a factory cable from when I opened my Fires.
Could anyone please, upload a picture of THEIR factory cable so I can figure out which one is which? I promise to shut up about fastboot for a while if anyone could do me that solid.
Sent from my Galaxy Nexus using Tapatalk 2
If you bought a skorpn it should have a scorpion logo on it
---------- Post added at 12:21 AM ---------- Previous post was at 12:16 AM ----------
Easiest way to get into fastboot shift+right click on the tools folder in kfu select open command window here power off your kindle leave it unplugged type fastboot -i 0x1949 getvar product (hit enter) it will say waiting for device plug your kindle in it will power on in fastboot mode it should return product : kindle
---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------
When you want to go back to normal type fastboot -i 0x1949 oem idme bootmode 4000 (hit enter) then type fastboot -i 0x1949 reboot (hit enter) it will then boot normal
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
No pun intended but with all the hassle and questions dualboot sounds like a poor choice but hey your kindle
Thepooch said:
If you bought a skorpn it should have a scorpion logo on it
---------- Post added at 12:21 AM ---------- Previous post was at 12:16 AM ----------
Easiest way to get into fastboot shift+right click on the tools folder in kfu select open command window here power off your kindle leave it unplugged type fastboot -i 0x1949 getvar product plug your kindle in it will power on in fastboot mode it should return product : kindle
Click to expand...
Click to collapse
No, brother: I'm just talking about the regular stock cable that came in the Amazon box: I have no idea which ones out of the jillion cords I have's the right one.
I'll try your recommendation above...just a minute, I'm booted into Ubuntu right now.
Sent from my Galaxy Nexus using Tapatalk 2
Most micro usb to standard work fine I use the one for my droidx all the time
---------- Post added at 12:44 AM ---------- Previous post was at 12:37 AM ----------
Also if your using linux you will need to have fastboot setup on it if you ran andadb script add sudo to the lead of all your commands
Thepooch said:
Most micro usb to standard work fine I use the one for my droidx all the time
Click to expand...
Click to collapse
Well, I've got a ton of cords. If any work, then what's all the talk about using factory cables for, or the jigs that replicate the connection that people sell?
Btw, I just tried the command from above in Ubuntu: no luck (the command went thru in kfu, but said "waiting for device"). Trying windows next, but I've got a feeling that won't work, as my drivers have never gotten to work right.
Sent from my SPH-D710 using xda premium
Yeah, Windows didn't care one bit when I plugged it in and turned it on. Booted straight into ICS, and still says waiting for device in the terminal.
See, I've been doing this stuff for hours... I know how to try this:
I just wanted to know if, with FFF and TWRP, and the ability to run Su in terminal emulator, if there might be an easier way.
Sent from my SPH-D710 using xda premium
Edit: Solved, thanks to Thepooch, who spent a lot of time on Teamviewer setting up a toolkit on a linux USB. No more headaches.
Hello, I have recently downloaded fbmode, and after following the steps prior to execuion, the execution fails, only giving me the error: couldn't write bp1, panic! After 4 hours of trying other software and searching for a solution, I made this post. I am using sustem v6.3.3, which is, from what I have read, 2nd generation. Any help would be much appreciated. I am also on a Arch Linux Box right now. Thanks.
-Hydrochloricacid
see my [2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only
---------- Post added at 05:23 PM ---------- Previous post was at 05:21 PM ----------
short answer is you need a Fastboot/Factory cable to start the process.
MikiBest said:
Mobile shell doesn't support the seconds hand for analog clocks. They sell the Spb Time to enhance the clock features.
Click to expand...
Click to collapse
Had the same issue. I was pushing fbmode to /data/local/fbmode from a different thread and getting that error 'couldn't write bp1'.
Changed to push to /data/local/tmp and all worked without factory cable.
Sent from my LG-P930 using Tapatalk 2
More clarification please...
nightlimits said:
Had the same issue. I was pushing fbmode to /data/local/fbmode from a different thread and getting that error 'couldn't write bp1'.
Changed to push to /data/local/tmp and all worked without factory cable.
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
Can you clarify what you did... I'm having the same problem.
Did you change, "adb push fbmode /data/local/fbmode" to "adb push fbmode /data/local/tmp" or did you change something else?
(sorry I'm a bit of a beginner and do not have a factory Kindle cable)
ajax_borges said:
Can you clarify what you did... I'm having the same problem.
Did you change, "adb push fbmode /data/local/fbmode" to "adb push fbmode /data/local/tmp" or did you change something else?
(sorry I'm a bit of a beginner and do not have a factory Kindle cable)
Click to expand...
Click to collapse
[6.3.3] Flashing FFF and TWRP without Fastboot Cable
sd_shadow said:
[6.3.3] Flashing FFF and TWRP without Fastboot Cable
Click to expand...
Click to collapse
You can also use an Android phone cable
Oh C'mon, is it even worth it?
I must apologize for my rant in advance, and is not directed at this group, but the task at hand: IMO all this is absolute Bull$h1t. I simply wanted to root my old Kindle (I've done this several times before without incident), and I go around and around downloading 5 gig SDK software, additional rooting programs, drivers, then being told I need a legacy this, and ADB that, and yet another different driver here, and so forth and so on, and then "oh no it dont work with windows 8.1" so I start this nonsense over on my XP box, and then 4 more hours later I read maybe its cause its the wrong cable, or whatever the "fix" is this hour!!!
Well. I did it my way.
Maphoo said:
I must apologize for my rant in advance, and is not directed at this group, but the task at hand: IMO all this is absolute Bull$h1t. I simply wanted to root my old Kindle (I've done this several times before without incident), and I go around and around downloading 5 gig SDK software, additional rooting programs, drivers, then being told I need a legacy this, and ADB that, and yet another different driver here, and so forth and so on, and then "oh no it dont work with windows 8.1" so I start this nonsense over on my XP box, and then 4 more hours later I read maybe its cause its the wrong cable, or whatever the "fix" is this hour!!!
Well. I did it my way.
Click to expand...
Click to collapse
[How To][Root] Kindle Fire 1 update 6.3.4 [2014]
Sent from my XT907 using Tapatalk
I don't know if this is what EVERYONE is seeing with this problem, but in MY case, the problem was that various scripts were attempting to run fbmode as non-root user.
The most simplistic way of dealing with this is to start an adb shell, su to root, then execute /data/local/tmp/fbmode:
c:\ adb shell
$ su
# /data/local/tmp/fbmode
# exit
$ exit
c:\ adb reboot
The kindle should then reboot in fastboot mode.
---------- Post added at 09:45 PM ---------- Previous post was at 09:27 PM ----------
pestaub said:
I don't know if this is what EVERYONE is seeing with this problem, but in MY case, the problem was that various scripts were attempting to run fbmode as non-root user.
The most simplistic way of dealing with this is to start an adb shell, su to root, then execute /data/local/tmp/fbmode:
c:\ adb shell
$ su
# /data/local/tmp/fbmode
# exit
$ exit
c:\ adb reboot
The kindle should then reboot in fastboot mode.
Click to expand...
Click to collapse
After thinking about this some more, I'm guessing that the 'run as root' solution is not the root (no pun intended) cause of the problem. I don't know where/what 'bp1' is, but I'd be willing to bet that some of the other messing around that I've done has caused it to become unwriteable. Wish I knew what that was.
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