Related
Hiya! First of all, the symptoms:
-I've never been able to access the phone through adb outside of recovery.
-Things that should be found in /sbin/sh are not there.
That's about it. But it makes me reboot into recovery every time I need to screw with something in adb (which I don't think is supposed to happen), and it stops me from being able to boot from zImages, and from enabling compcache, and a bunch of other things that I'm sure that I haven't noticed yet...
Attached is a screenshot. First bit, I was trying to flash an experimental zImage, and the second, I was trying to enable compcache on CM6-Snap-v4!, to no avail.
Any help would be greatly appreciated! I kind of anticipate having to reroot, but I'd rather not . If that's the case, though, I'd be interesting in knowing what exactly nandroid backs up, so that I don't wind up going back to un-full-root in an attempt to keep my configuration.
http://dl.dropbox.com/u/560483/screweduproot.png
Bump, if it please you.
You need to be in recovery mode to use fastboot commands, well at least I always do.
I cannot get into /sbin/sh/ whether in recovery mode or not.
Also, the command is use is 'flash_image'
Ah, I suppose that that makes me feel better--and aye, I'm not quite up to speed on the various available commands available to me. A flashable zip of the zImage I wanted to flash went up, so I suppose that I'll just keep that knowledge stored away for the future. Thanks for the help!
(And one last thing: Should I be able to access the phone via adb while it's booted into android? I feel that I should...)
mrkmrk said:
Ah, I suppose that that makes me feel better--and aye, I'm not quite up to speed on the various available commands available to me. A flashable zip of the zImage I wanted to flash went up, so I suppose that I'll just keep that knowledge stored away for the future. Thanks for the help!
(And one last thing: Should I be able to access the phone via adb while it's booted into android? I feel that I should...)
Click to expand...
Click to collapse
I usually run my adb stuff while in recovery mode. I could be wrong, but it makes more sense to work on the engine when it is not running if you know what I mean.
Instead of adb remount, try this:
adb shell
# mount /dev/block/mtdblock4 /system
YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
*Also note that not all sections will apply to you. I have tried to seperate different senerios using * at each one. Also more then one section here may be needed by you.
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, s-on, and post OTA, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Thank you, really, for taking the time to write this guide. I shared that dreadful feeling of a brick a little while ago, but made it out alive. I know this will help a lot of people.
I'm not bricked, semi bricked or none of that. Rootrd and running BB 0.3
This is the best guide to everything you would need. Too bad you can't post this at the beginning of every thread or some kind of link on every page. This would answer a lot of question if some people would look hard enough. I'm not some smart phone guy by no means. I just read a lot before I ask. In my further reading I can direct people.with further problems here.
Thanks for all your work and giving me another fun hobby
Peace
Sent from my T-Mobile G2 using XDA App
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Good point . Not sure on that one
Sent from my T-Mobile G2 using XDA App
renn9420 said:
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
if you look where im saying /mmcblk0p21 we are replacing RECOVERY with CWM. i do that because i just dont like the idea of trying to replace hboot from a looping system. worst case something goes wrong, you still have hboot and you can try again. screw up hboot, game over! then once android is back up and running we worry about hboot on mmcblk0p18.
you should not state that steps can be changed if people are brave, someone is going to sip parts and cry that their hboot is boned and now they have a BRICK, this is the best post i have seen in the G2 section thus far and i have been through almost every thread(with any kind of importance) in the dev section and 90% of them in general and Q&A. thank you for this post and let's hope people READ at least 5 times before even starting on this.
Gotcha
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Amazing guide, thanks a lot.
fastludeh22 said:
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
Click to expand...
Click to collapse
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
reycat said:
Amazing guide, thanks a lot.
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
Click to expand...
Click to collapse
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
{golf clap} on the post.
you sir, have incredible patience... and it's truly appreciated.
fastludeh22 said:
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
Click to expand...
Click to collapse
Mmm... It seems all of it is quite a bit over my head.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
Click to expand...
Click to collapse
Don't ask me how I did it, but I actually downloaded a web page instead of the actual hboot file I should have used . I did it from the phone and didn't notice. Since I was supposed to rename it to make the typing easier, I didn't notice it was the wrong file.
Anyway, right now the phone is a complete brick. It doesn't respond to any button presses, the LED doesn't do anything when you plug in the charger... A complete brick.
Device offline?
fastludeh22 said:
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Click to expand...
Click to collapse
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
-FuRBz- said:
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
Click to expand...
Click to collapse
Download and instal PDANet, that gave me the drivers i needed for adb, now if only i could figure out how to get my device to register online through the ADB command interface.....
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
marley097 said:
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
Click to expand...
Click to collapse
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
-FuRBz- said:
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
Click to expand...
Click to collapse
Glad you got it! After drivers installed, did you fix it per a section of the op?
it all happened because i had tried flashing cm 6.1- it got stuck on the splash screen but i had done a recovery prior to trying to flash... once i got the drivers installed i was able to get in to adb and do a reboot-bootloader and was able to get into the recovery file
fastludeh22 said:
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
Click to expand...
Click to collapse
Lame....so how often do they release official pic10img's....? are we talkin a month....or a year?
FOR VERIZON Xoom's ONLY!!! NOT WiFi!!!!
This is copied from Koush's website and I made some changes to help those getting stuck because the OP makes assumptions that will get you caught up if you're not careful or used to ADB.
"Here are the instructions to root your device (this assumes you have adb and fastboot installed on your computer):
# Download the xoomroot.zip.
# Unzip the package.
# Put your junk in the box.
adb reboot bootloader (skip the next 3 steps if you have already unlocked via fastboot)
fastboot oem unlock
# wait for reboot
adb reboot bootloader
fastboot flash boot rootboot.img
fastboot reboot
# wait for reboot
adb remount
adb push su /system/bin/
adb shell
ln –s /system/bin/su /system/xbin/su
chmod 4755 /system/bin/su
#exit adb shell by typing 'exit'
adb push Superuser.apk /system/app/
Yep, that should do it."
This helped me because I kept getting stupid errors that I knew better and then realized that I needed to be IN adb shell get the last couple step working. Also MAKE SURE YOU HAVE FASTBOOT IN YOUR TOOLS FOLDER!!!!!
if you are still lost after this, here is an even more detailed version posted here: http://forum.xda-developers.com/showthread.php?t=981578
What is fastboot and how about some links to the needed software like ADB, Motorola drivers and whatever else would be needed. Otherwise thanks!
Put your junk in the box???
You call this a well written tutorial for noobs? This is awful
griffindodd said:
You call this a well written tutorial for noobs? This is awful
Click to expand...
Click to collapse
Can't this be scripted or at least a batch file for Noobies?
http://forum.androidcentral.com/motorola-xoom/63162-guide-rooting-moto-xoom-2-24-2011-a.html cheers.
I would have to agree there is room for improvement here
For all those posting saying this is kinda hard to read for noobs, I apologise the OP did miss step 3.... it should read...
#unzip the package
#put your junk in the box
(and then) #make her open the box
I hope this clears up any confusion on how to root.
Sent from my SCH-I500 using XDA App
Sorry
But all I did was copy this from the original posting and clarified the ares that messed me up. The files are easily found my using Google to search for them.
Here's another guide. May be easier for some people.
http://forum.xda-developers.com/showthread.php?t=981578
EDIT: Nvm, just saw that you posted this same link in the OP.
The other thread posted is easier to follow as this is a copy/paste from Koush's website. The other one has cliff notes
Droid-Xer said:
The other thread posted is easier to follow as this is a copy/paste from Koush's website. The other one has cliff notes
Click to expand...
Click to collapse
Thanks, but that was the first thing I said.
JaxDomino said:
Thanks, but that was the first thing I said.
Click to expand...
Click to collapse
You left out one important piece of information from the other post.
js042507 said:
***Xoom Rooting Guide for N00bs***
**Also, this Tutorial is for the 3G version ONLY. The Wifi model is different and uses an incompatible boot.img. Once again, ONLY FOR 3G MODEL**
Click to expand...
Click to collapse
Someone going by your post and not checking the other (especially a noob) would not know this and may try this method on the wifi version.
Through that post though I found a link posted by the OP of that thread for the wifi root.
http://forum.xda-developers.com/showthread.php?t=1010568
You might want to add that to the first post.
SPIDERTECH said:
You left out one important piece of information from the other post.
Someone going by your post and not checking the other (especially a noob) would not know this and may try this method on the wifi version.
Through that post though I found a link posted by the OP of that thread for the wifi root.
http://forum.xda-developers.com/showthread.php?t=1010568
You might want to add that to the first post.
Click to expand...
Click to collapse
The OP has been updated.
This guide is very concise and succinct (except for the junk in the box bit) but would be more appropriate for someone with experience with Android, just not with the Xoom.
It really isn't for Noobs. It doesn't define terms you are using like adb and fastboot, it doesn't include links to the needed files, it doesn't tell the user what they should be seeing each step of the way, it doesn't advise them on what could go wrong and what to do if it does.
I totally agree there is a need for a new guide for Noobs about rooting, and your heart is in the right place...but this is not that guide.
If you guys need to download the files for this you can get them in the Root Files pack on my thread : http://forum.xda-developers.com/showthread.php?t=1083739
Not trying to take people off this thread but the files are updated for 3.1 so it might help some
Okay so I'm having problems trying to get my Kindle Fire fixed. I first need the drivers installed properly. I've installed them a million times from the install_drivers.bat in one of the KFU's I just don't remember which one. I've uninstalled everything and I'm starting fresh as I thought this would be easy and it's turning into a very large headache. Step by step would be beneficial as I'm very clueless. I've tried http://forum.xda-developers.com/showthread.php?t=2166668 but that doesn't give much help just tells me what to and not how to do it. I know exactly what I need and to do and I've googled for days and still can't find nothing. I have tried plugging my Kindle in with both a USB and factory cable and everytime I look in device manager it says unknown device (code 43). So let's start from here and hopefully I can resolve this headache! I also (if this will help) have tried opening up the command prompt from the KFU tools and typed in fastboot -i 0x1949 oem idme bootmode 4000 and all it said was waiting for device and I tried this with the USB NOT the factory cable. I figured I just have to get my computer to configure it. I am pretty noobish when it comes to the Kindle, so any help would greatly be appreciated!
buckeyestilidie said:
Okay so I'm having problems trying to get my Kindle Fire fixed. I first need the drivers installed properly. I've installed them a million times from the install_drivers.bat in one of the KFU's I just don't remember which one. I've uninstalled everything and I'm starting fresh as I thought this would be easy and it's turning into a very large headache. Step by step would be beneficial as I'm very clueless. I've tried http://forum.xda-developers.com/showthread.php?t=2166668 but that doesn't give much help just tells me what to and not how to do it. I know exactly what I need and to do and I've googled for days and still can't find nothing. I have tried plugging my Kindle in with both a USB and factory cable and everytime I look in device manager it says unknown device (code 43). So let's start from here and hopefully I can resolve this headache!
Click to expand...
Click to collapse
Your aversion to use the information available to you is a little disappointing.
Ignoring the fact that you have another thread where this problem is already being discussed, the "Kindle Fire for Beginners" guide, linked to in the FAQ thread that you mentioned, has information on how to properly install your device drivers. The FAQ thread also points to another resource that can help you figure out your device driver problem. If that isn't enough, there is information on where to go when you have exhausted all of your options and still cannot get your drivers working. You ask for a step-by-step guide...well...there they are. Somebody has already gone through all the trouble of doing that for you ahead of time.
Writing a step-by-step guide (again) to tell you how get your drivers working properly, takes a little more effort than just saying..."Do this, do that, then do this, blah blah blah. There is no "one, two" fix to get your device working again. You actually need to educate yourself a little to understand what's going on. It'd be one thing if you had at least some experience, and you tried to resolve the problem yourself and failed, then asked for help. But you're starting from nothing, with nothing. Asking for a step-by-step tutorial from someone at this point is like asking someone to teach you how to read when you don't even know your alphabet yet....that person would have to FIRST go through the trouble of teaching you the alphabet, and THEN teach you how to read.
If you used the information available to you, and you had a specific question about something that wasn't necessarily covered in that information, or if there was something in that information that you didn't understand, I'm sure you would find that there are lots of people around here that are willing to help you figure it out. Otherwise (and I'm speaking from experience), it is very unlikely that you would find anyone of appropriate knowledge to even put forth the effort.
That being said...
...as many people around here can attest, I am always willing to help those in need (even you), assuming those in need (you), are at least willing to meet me halfway first....but I'm not going to hold anyone's hand, and I doubt anyone else will either.
soupmagnet said:
Your aversion to use the information available to you is a little disappointing.
Ignoring the fact that you have another thread where this problem is already being discussed, the "Kindle Fire for Beginners" guide, linked to in the FAQ thread that you mentioned, has information on how to properly install your device drivers. The FAQ thread also points to another resource that can help you figure out your device driver problem. If that isn't enough, there is information on where to go when you have exhausted all of your options and still cannot get your drivers working. You ask for a step-by-step guide...well...there they are. Somebody has already gone through all the trouble of doing that for you ahead of time.
Writing a step-by-step guide (again) to tell you how get your drivers working properly, takes a little more effort than just saying..."Do this, do that, then do this, blah blah blah. There is no "one, two" fix to get your device working again. You actually need to educate yourself a little to understand what's going on. It'd be one thing if you had at least some experience, and you tried to resolve the problem yourself and failed, then asked for help. But you're starting from nothing, with nothing. Asking for a step-by-step tutorial from someone at this point is like asking someone to teach you how to read when you don't even know your alphabet yet....that person would have to FIRST go through the trouble of teaching you the alphabet, and THEN teach you how to read.
If you used the information available to you, and you had a specific question about something that wasn't necessarily covered in that information, or if there was something in that information that you didn't understand, I'm sure you would find that there are lots of people around here that are willing to help you figure it out. Otherwise (and I'm speaking from experience), it is very unlikely that you would find anyone of appropriate knowledge to even put forth the effort.
That being said...
...as many people around here can attest, I am always willing to help those in need (even you), assuming those in need (you), are at least willing to meet me halfway first....but I'm not going to hold anyone's hand, and I doubt anyone else will either.
Click to expand...
Click to collapse
You're acting like I haven't tried everything. Obviously if I'm asking for help I have tried everything and studied into it and failed. You can check out Droidrzr.com, I am very knowledgeable and insightful over there. I'm not just coming over here demanding answers, I've tried everything except the liveusb as my labtop doesn't support it. I am patient but I just want help as obviously I'm not doing something right. I have no problem to supply answers to any questions as I need to fix my dads kindle quick. So please I want to start fresh and figure out what it is I'm doing wrong.
buckeyestilidie said:
You're acting like I haven't tried everything. Obviously if I'm asking for help I have tried everything and studied into it and failed. You can check out Droidrzr.com, I am very knowledgeable and insightful over there. I'm not just coming over here demanding answers, I've tried everything except the liveusb as my labtop doesn't support it. I am patient but I just want help as obviously I'm not doing something right. I have no problem to supply answers to any questions as I need to fix my dads kindle quick. So please I want to start fresh and figure out what it is I'm doing wrong.
Click to expand...
Click to collapse
Believe me, I am sympathetic to your situation, but without any specific insight as to what's happening on your end, other than the fact that you can't get it to work, I have no choice but to assume you haven't done the necessary groundwork to educate yourself in what you need to resolve your problem.
Did you read the Kindle Fire for Beginners guide? Did you understand all of it? If not, what didn't you understand? Have you checked the hardware ID of your device in the device manager and made sure it is in your 'android_winusb.inf'? What have you tried? What haven't you tried? The same goes for any other guide, tutorial or tool that you have been directed to.
No one can see anything you're doing or not doing, so without the appropriate amount of information to give us a clue to the specifics to your situation (other than drivers aren't working), you're just wasting your time. Are we literally supposed to assume you've actually tried "10 million different ways" to get your drivers working? Or do you think it would be more beneficial for everyone to know exactly what you have tried so an appropriate solution can be suggested? You haven't even told anyone what operating system you're using.
Put yourself on the other side for a moment, and imagine someone came to the Driodrzr.com forums...and despite a wealth of information available to them, the only information you can glean from their situation after six different responses across two different threads, is that they have tried "10 million different ways" to get their drivers working, yet they are still unsuccessful. Would you automatically assume they read and understood all of the information available to them and actually put that information to use...all while paying close attention to detail and following all instructions to a 'T'? Call me skeptical...but I think you wouldn't.
[Edit:] In case you're wondering, this is a more appropriate way to present your problem...
http://forum.xda-developers.com/showpost.php?p=40447680&postcount=149
...it isn't perfect, but it at least paints a good picture for anyone who reads it to get a decent idea of what's going on.
soupmagnet said:
Believe me, I am sympathetic to your situation, but without any specific insight as to what's happening on your end, other than the fact that you can't get it to work, I have no choice but to assume you haven't done the necessary groundwork to educate yourself in what you need to resolve your problem.
Did you read the Kindle Fire for Beginners guide? Did you understand all of it? If not, what didn't you understand? Have you checked the hardware ID of your device in the device manager and made sure it is in your 'android_winusb.inf'? What have you tried? What haven't you tried? The same goes for any other guide, tutorial or tool that you have been directed to.
No one can see anything you're doing or not doing, so without the appropriate amount of information to give us a clue to the specifics to your situation (other than drivers aren't working), you're just wasting your time. Are we literally supposed to assume you've actually tried "10 million different ways" to get your drivers working? Or do you think it would be more beneficial for everyone to know exactly what you have tried so an appropriate solution can be suggested? You haven't even told anyone what operating system you're using.
Put yourself on the other side for a moment, and imagine someone came to the Driodrzr.com forums...and despite a wealth of information available to them, the only information you can glean from their situation after six different responses across two different threads, is that they have tried "10 million different ways" to get their drivers working, yet they are still unsuccessful. Would you automatically assume they read and understood all of the information available to them and actually put that information to use...all while paying close attention to detail and following all instructions to a 'T'? Call me skeptical...but I think you wouldn't.
[Edit:] In case you're wondering, this is a more appropriate way to present your problem...
http://forum.xda-developers.com/showpost.php?p=40447680&postcount=149
...it isn't perfect, but it at least paints a good picture for anyone who reads it to get a decent idea of what's going on.
Click to expand...
Click to collapse
Trust me I understand, I think I'm just frustrated from not being able to figure this out and yet it sounds so simple. I am running windows and I can't check my hardware ID's because every time I go into device manager it says unknown (for the Kindle device). I'm gonna try on another computer but if you can tell me why it says unknown and how to solve it I believe I'd be good from there.
There could be a number of reasons why your device manager shows "unknown device". Your bootloader could be malfunctioning or you could just have the wrong information listed in your 'android_winusb.inf' file. It would be helpful to know what hardware IDs are listed in it.
It would also be helpful to know if there is any change in how your device shows up in the device manager when the factory cable is plugged in. On that note, where did you get your factory cable? Did you purchase it from Skorpn, or did you make it yourself? What happens to your device when you plug it in with the factory cable? We've already established that it sits at the Kindle Fire logo, but which one? Does it stay at one brightness, or does it go dim after a few seconds?
And I can tell you are running Windows by the fact that you have a device manager, but what version is it? What prevents you from being able to boot from a liveUSB on your computer? (BTW, this is required if your booloader is malfunctioning)
The more information like this that you can provide, the better chance you will have at getting your problem fixed. Paint a picture. Imagine you're explaining to a blind person next to you what's going on on your end.
soupmagnet said:
There could be a number of reasons why your device manager shows "unknown device". Your bootloader could be malfunctioning or you could just have the wrong information listed in your 'android_winusb.inf' file. It would be helpful to know what hardware IDs are listed in it.
It would also be helpful to know if there is any change in how your device shows up in the device manager when the factory cable is plugged in. On that note, where did you get your factory cable? Did you purchase it from Skorpn, or did you make it yourself? What happens to your device when you plug it in with the factory cable? We've already established that it sits at the Kindle Fire logo, but which one? Does it stay at one brightness, or does it go dim after a few seconds?
And I can tell you are running Windows by the fact that you have a device manager, but what version is it? What prevents you from being able to boot from a liveUSB on your computer? (BTW, this is required if your booloader is malfunctioning)
The more information like this that you can provide, the better chance you will have at getting your problem fixed. Paint a picture. Imagine you're explaining to a blind person next to you what's going on on your end.
Click to expand...
Click to collapse
Okay so I went onto another computer and it shows Andriod phone then the ADB interface. I immediately became exuberated with joy! Now do I do fastboot? Can I use KFU to just hit the option to put TWRP on? I don't wanna mess nothing up as this is all the computers in my house lol. If I do fastboot how do I open up the commands for it? I know I must shift and right click on something I just can't remember what. Thanks for the patience with one man who's finally got something to look forward to when it comes to his Kindle! I also just used a simple USB cord not the factory cable.
buckeyestilidie said:
Okay so I went onto another computer and it shows Andriod phone then the ADB interface. I immediately became exuberated with joy! Now do I do fastboot? Can I use KFU to just hit the option to put TWRP on? I don't wanna mess nothing up as this is all the computers in my house lol. If I do fastboot how do I open up the commands for it? I know I must shift and right click on something I just can't remember what. Thanks for the patience with one man who's finally got something to look forward to when it comes to his Kindle! I also just used a simple USB cord not the factory cable.
Click to expand...
Click to collapse
Plug your factory cable in to make sure the device is actually in fastboot. Does KFU detect your device while in fastboot?
soupmagnet said:
Plug your factory cable in to make sure the device is actually in fastboot. Does KFU detect your device while in fastboot?
Click to expand...
Click to collapse
I used a USB and it said offline in the KFU but it went to the menu to where I could hit options. I never tried the factory cable but I will when I get home. Also since I'm close to fixing this do you have an idea of what is the most stable ROM to put on this? I'm doing it for my dad so he's not into speed or processing anything. Just looking for a stable ROM that has good battery life.
soupmagnet said:
Plug your factory cable in to make sure the device is actually in fastboot. Does KFU detect your device while in fastboot?
Click to expand...
Click to collapse
The FAQ just says I change the bootmode. I know I must shift right click on something to send those commands but I just can't remember what, do you know what I shift right click to send those commands to fix this Kindle? Also can I just send TWRP to the Kindle through those same commands? Also I read the FB guide and the codes USB\VID_1949&PID_0006&REV_0100
USB\VID_1949&PID_0006
popped up in the hardware ID's so I know it's in FB. I just need to know where I shift right click to enter these codes: fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
buckeyestilidie said:
The FAQ just says I change the bootmode. I know I must shift right click on something to send those commands but I just can't remember what, do you know what I shift right click to send those commands to fix this Kindle? Also can I just send TWRP to the Kindle through those same commands? Also I read the FB guide and the codes USB\VID_1949&PID_0006&REV_0100
USB\VID_1949&PID_0006
popped up in the hardware ID's so I know it's in FB. I just need to know where I shift right click to enter these codes: fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
If KFU can detect your device in fastboot , you can use it to install custom recovery, FFF, and/or change the bootmode respectively. It uses fastboot commands to do this when your device is in fastboot mode. When your device is booted normally or in recovery, it uses ADB commands instead.
But...
...if you were to enter the commands manually, the fastboot.exe(adb.exe) must be in the same directory from which you are entering the commands. You can either change to that directory using the 'cd' command at your command prompt, or you can open a new prompt in that directory by pressing shift + right-clicking on that directory, then selecting "Open command window here". Some versions of Windows don't support opening a command prompt in this fashion, BTW.
As for your question of what ROM is the most stable, it would be safe to say that all JB/CM10 based ROMs are quite stable, but CM10. If you want a ROM that has good battery life, you might want to go with a GB/CM7 based ROM, but they're not as nice to look at and kind of awkward to navigate....simple things like changing the volume can be a chore.
soupmagnet said:
If KFU can detect your device in fastboot , you can use it to install custom recovery, FFF, and/or change the bootmode respectively. It uses fastboot commands to do this when your device is in fastboot mode. When your device is booted normally or in recovery, it uses ADB commands instead.
But...
...if you were to enter the commands manually, the fastboot.exe(adb.exe) must be in the same directory from which you are entering the commands. You can either change to that directory using the 'cd' command at your command prompt, or you can open a new prompt in that directory by pressing shift + right-clicking on that directory, then selecting "Open command window here". Some versions of Windows don't support opening a command prompt in this fashion, BTW.
As for your question of what ROM is the most stable, it would be safe to say that all JB/CM10 based ROMs are quite stable, but CM10. If you want a ROM that has good battery life, you might want to go with a GB/CM7 based ROM, but they're not as nice to look at and kind of awkward to navigate....simple things like changing the volume can be a chore.
Click to expand...
Click to collapse
My other computer I'm using doesn't support this :/ what can I do to get the KFU to recognize this? Also how do I change the bootmode?
buckeyestilidie said:
My other computer I'm using doesn't support this :/ what can I do to get the KFU to recognize this? Also how do I change the bootmode?
Click to expand...
Click to collapse
If KFU doesn't recognize your device, it's unlikely that fastboot will work anyway. You can confirm this by entering the following in the command prompt...
Code:
fastboot -i 0x1949 getvar product
...if it returns "kindle", you are good to install custom recovery, then change the bootmode.
Commands for installing custom recovery and changing bootmodes can both can be found in the "Kindle Fire for Beginners" guide.
If the previous command doesn't return a result, you need to fix your drivers.
soupmagnet said:
If KFU doesn't recognize your device, it's unlikely that fastboot will work anyway. You can confirm this by entering the following in the command prompt...
Code:
fastboot -i 0x1949 getvar product
...if it returns "kindle", you are good to install custom recovery, then change the bootmode.
Commands for installing custom recovery and changing bootmodes can both can be found in the "Kindle Fire for Beginners" guide.
If the previous command doesn't return a result, you need to fix your drivers.
Click to expand...
Click to collapse
I entered in a command prompt and It says 'fastboot' is not recognized as an internal or external command, operable program or batch file. I take it this means my freaking drivers aren't working :/ so since the kindle registers as Android ADB Interface what do I need to fix? I thought this was what I was aiming for?
buckeyestilidie said:
It says 'fastboot' is not recognized as an internal or external command, operable program or batch file. I take it this means my freaking drivers aren't working :/ so since the kindle registers as Android ADB Interface what do I need to fix? I thought this was what I was aiming for?
Click to expand...
Click to collapse
NO. You have to change directories ('cd') with your command prompt to the directory containing fasboot.exe. I just told you that two posts ago.
soupmagnet said:
NO. You have to change directories ('cd') with your command prompt to the directory containing fasboot.exe. I just told you that two posts ago.
Click to expand...
Click to collapse
Then I can run the kfu?
soupmagnet said:
NO. You have to change directories ('cd') with your command prompt to the directory containing fasboot.exe. I just told you that two posts ago.
Click to expand...
Click to collapse
My computer won't allow me to open a command prompt from the FB.exe though
buckeyestilidie said:
My computer won't allow me to open a command prompt from the FB.exe though
Click to expand...
Click to collapse
THIS RIGHT HERE is why I am so adamant that you read the information available to you and pay attention to what's being said.
The 'cd' command stands for "change directory". You use it to change the current directory of the command prompt (default is your User directory) to another directory. The correct usage of that command is...
Code:
cd
If you don't know the path of the directory you want to change to, right click on it and select "Properties".
If you still can't figure it out, type 'cd' (without quotes), enter a SPACE, then drag that folder into your command window. The rest should be self explanatory.
[Edit:] CASE IN POINT...Quoted directly from the Kindle Fire for Beginners thread
kinfauns said:
OK, so what are these commands?
To get started, click on the Start Menu to begin. Then, depending on the version of Windows, either use "Run…" or "Search" and type "cmd" to open up a command line window that will look a lot like...
{
"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"
}
The last line in this example is called a prompt and it's followed by a blinking cursor.
The prompt tells you where you are in the directory structure. When the "cmd" program first starts up, that location is your Windows user's home directory by default. In the above example, my username is "kinfauns" and my home directory by the same name is in the "Users" directory located on the "C:" drive. The "C:\Users\kinfauns" part of the prompt is the directory path and it uniquely describes the location of the home directory owned by the "kinfauns" user.
The blinking cursor indicates the program's readiness to accept a new command. Each time you execute a command, a new prompt/cursor will appear at the bottom, telling you that it's ready for you to type another.
Now type "dir" (without the quotes) and press Enter, and you'll see the names of all the folders in your home directory. The "dir" command just prints out a content listing of the directory indicated by the prompt. If you open up your home folder in Windows Explorer and look inside, you'll see everything in that folder shown in the list you got from the "dir" command. The "dir" command implicitly operated on the current directory shown in the prompt, but you can also provide an explicit argument to tell it what directory to list. For example, "dir C:\Users" lists all the users directories. Providing an argument after the command name will be important for the next command...
The "cd" command is used to change the current working directory. We need to get to the KFU directory, so we can use "C:\kfu" as an argument to the "cd" command. Type "cd C:\kfu" and press Enter to change to that directory. No output was provided, but the new prompt has a different directory path to confirm the "cd" command has executed successfully. You can try "dir" here to list the contents of the "C:\kfu" directory, but it's not necessary to first list it if you know what's in there already. In this case, we'll "cd" into the "C:\kfu\tools" directory, but you won't have to provide the full path. Since "C:\kfu" is already the current working directory, "cd tools" is equivalent to the "cd C:\kfu\tools" command. The one other key component to navigating the directory structure is the ".." directory. The ".." directory refers to the parent of the current directory, so "cd .." will take you back up to "C:\kfu" and another "cd .." will take you up to the "C:\" directory.
Now you'll be able to navigate through the directories and you should have a fair idea about how to construct a directory path (this will come in handy later). The fastboot and adb executables are in the "C:\kfu\tools" directory, so you'll have to get there using what you learned to be able to use them in the next section. There are just a few more tips that might come in handy...
Shift-right-click on/within a folder and select "Open command window here" to open a command line window with that directory path as the current working directory.
File/folder names or directory paths containing spaces must be enclosed in double quotes.
Drag and drop a file or folder from the Windows Explorer windows into the Command Prompt window. The complete, absolute path of the object will be pasted into the Command Prompt window automatically.
Utilize the "Tab" key to complete a file/folder name without typing it in its entirety (e.g. Try typing "cd C:\kfu\to" and then hit the "Tab" key).
For more information on Windows cmd commands, bleepingcomputer.com has a nice introductory tutorial and ss64.com has a full reference page of commands.
Click to expand...
Click to collapse
I seriously hope you'll learn from this and actually pay attention next time you read something.
soupmagnet said:
THIS RIGHT HERE is why I am so adamant that you read the information available to you and pay attention to what's being said.
The 'cd' command stands for "change directory". You use it to change the current directory of the command prompt (default is your User directory) to another directory. The correct usage of that command is...
Code:
cd
If you don't know the path of the directory you want to change to, right click on it and select "Properties".
If you still can't figure it out, type 'cd' (without quotes), enter a SPACE, then drag that folder into your command window. The rest should be self explanatory.
[Edit:] CASE IN POINT...Quoted directly from the Kindle Fire for Beginners thread
[/LIST][/B]
I seriously hope you'll learn from this and actually pay attention next time you read something.
Click to expand...
Click to collapse
I changed the directory to the tools subfolder in the KFU folder. I tried typing the commands I told you 2 or 3 posts ago. It gave me 3 dots and I waited 10 minutes and nothing. Now what am I doing wrong?
buckeyestilidie said:
I changed the directory to the tools subfolder in the KFU folder. I tried typing the commands I told you 2 or 3 posts ago. It gave me 3 dots and I waited 10 minutes and nothing. Now what am I doing wrong?
Click to expand...
Click to collapse
Nothing. That's normal when changing bootmodes in fastboot. Rebooting will boot your device into that particular bootmode.
But simply changing the bootmode to normal (4000) isn't going to fix your device unless there wasn't anything wrong with it in the first place. You'll likely need to access recovery to fix the original problem.
soupmagnet said:
Q16: What does it mean when my device is stuck at the Kindle Fire logo?It depends on which Kindle Fire logo you're talking about. If you're talking about the Kindle Fire logo that stays brightly lit without any change in brightness, it means the device is in fastboot mode. Just change the bootmode to normal or recovery and reboot. If the Kindle Fire logo you're talking about flashes and goes dim after being brightly lit for a few seconds, then your device is trying to boot normally to a malfunctioning operating system, likely caused by not wiping the data partition (factory reset) before flashing a ROM. If that's the case, you will likely need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall a ROM properly.
Click to expand...
Click to collapse
so my wife dorpped her s3 and broke the screen, the phone is rooted and i have adb debugging turned on i can use adb to pull/puch etc. but i dont know how, could some on tell me what adb commands i need to issue to the device to pull her internal sd data to my computer and push it back to her new s3, i also need to know how to wipe her phone with adb and reset to stock so i cna return it to the insurancce company, if anyone could tell me how to basically pull everything from her phone, internal sd data, and her text messages i know to pull the texts and view them i will need to use sqlite 3 to view the .db of her text messages but i cant figure out the commands to do so and i cant figure out how to format the commands so that it will pull the info to my desktop for viewing through sqlite 3 on the computer, also if i need to install sqlite 3 on the device with adb i need to know the commands for that as well, all help is welcomed, i have to get this thing back to stock in the next week or so, you are even more than welcome to call me an idot noob because i really am, i am very technically inclined and can follow complex instructions provided they are complete, please help ! lastly is there an adb command that would transfer what should be displayed on the screen if it worked within a emulator window if so please include that information as well.
This has been solved thanks to the info that was given, i was able to wrap my head around the entireity of adb, and my actual problem was not formatting of commands, my wife had a lock screen so i had to get that unlocked before adb would allow pulls if you need to do this with you phone i have posted a tutorial in the android general development and hacking [developers only] forums
MotoDefier said:
so my wife dorpped her s3 and broke the screen, the phone is rooted and i have adb debugging turned on i can use adb to pull/puch etc. but i dont know how, could some on tell me what adb commands i need to issue to the device to pull her internal sd data to my computer and push it back to her new s3, i also need to know how to wipe her phone with adb and reset to stock so i cna return it to the insurancce company, if anyone could tell me how to basically pull everything from her phone, internal sd data, and her text messages i know to pull the texts and view them i will need to use sqlite 3 to view the .db of her text messages but i cant figure out the commands to do so and i cant figure out how to format the commands so that it will pull the info to my desktop for viewing through sqlite 3 on the computer, also if i need to install sqlite 3 on the device with adb i need to know the commands for that as well, all help is welcomed, i have to get this thing back to stock in the next week or so, you are even more than welcome to call me an idot noob because i really am, i am very technically inclined and can follow complex instructions provided they are complete, please help ! lastly is there an adb command that would transfer what should be displayed on the screen if it worked within a emulator window if so please include that information as well.
Click to expand...
Click to collapse
I'm not going to call you an idiot noob. It seems to me that you know a little more than you express. A few Google searches could answer all of your questions. You are asking for someone to write you a novel, it's not going to happen.
Aerowinder said:
I'm not going to call you an idiot noob. It seems to me that you know a little more than you express. A few Google searches could answer all of your questions. You are asking for someone to write you a novel, it's not going to happen.
Click to expand...
Click to collapse
google has actually been un helpful in this dilema, however I think the explaination of adb commands on the sdk's page looks like it has enough information for me to write, my own novel (lol) so I will start there tonight, and hope that I understand the procedures described as well as I think I do, thanks for the reply anyway
Now that I have a little more information I guess what I really was trying to ask is for someone to give me a little better understanding of how issuing commands work I know how to issue ADB commands for instance with ADB HELP OR HELP ALL the command looks like this in the example. Adb pull [<local>] [<remote>] i dont understand what information adb is looking for where it says local and remote, is adb looking for me to type the [<local>] [<remote>] exactly this way or is it leading me to give a path for local and a path for remote, if so how do i go about figuring out said paths?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Local would be path on pc, remote would be path on phone.
sorry, for asking probably dumb questions
Aerowinder said:
Local would be path on pc, remote would be path on phone.
Click to expand...
Click to collapse
I know that it sounds stupid that i know how to open adb, i know how to issue commands (mostly) and i know that you said you think i know more than i am taking credit for, but heres the thing i do know ALOT about computers and can do almost anything with them however Command line utilities is not my strong suit, so local is the path on the pc remote is the path on the phone i am assuming that this would be the proper way to pull the sd data
adb pull -shared [< / sd>] [< C:\user agentlogon\Desktop>] if i wanted to store the file on my desktop would that be correct or am i just completly command line retarted? , i know that this isnt the real path but if it were is this correct formatting for the command line?
Like this: adb pull -shared "/sd" "C:\user agentlogon\Desktop"
Adb kill-server
Adb start-server
Adb pull <file> <Local>
Sent from my LT26i using xda app-developers app
Aerowinder said:
Like this: adb pull -shared "/sd" "C:\user agentlogon\Desktop"
Click to expand...
Click to collapse
Ok, so sorry, at this point i feel like a total idiot and im sure if your not right there with me your getting close, but i think this last question will help me understand command line utils better in the future, so when you see [<>] am i correct that the utility is showing me its okay to perform said command on [ ] directories <> files ? Also i am a very literal learner so do i use the quotes on the command or are you just quoting me?
[<>] = variable. Replace the entire sequence. So, [<local>] = "C:\directory\file.ext" This is not standardized across commandline apps. The [<>] is only meant to show the user that they need to replace this with his/her own value.
In commandline utilities, spaces separate commands, this is why you need quotations around directories that have spaces. If you don't, the C:\... directory will be interpreted as two seperate commands, resulting in a syntax error. I always use quotations around directories out of habit. / is often used as a switch. To be safe, always quote directories. This is standardized across all commandline apps.
TrinityHaxxor said:
Adb kill-server
Adb start-server
Adb pull <file> <Local>
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
Yeah i got the kill start sever on lock, and i am wanting to pull thecentire contents of the sd, not a single file, but thanks for your input it is all welcomed!
Aerowinder said:
[<>] = variable. Replace the entire sequence. So, [<local>] = "C:\directory\file.ext" hhis is not standardized across commandline apps. The [<>] is only meant to show the user that they need to replace this with his/her own val
In commandline utilities, spaces separate commands, this is why you need quotations around directories that have spaces. If you don't, the C:\... directory will be interpreted as two seperate commands, resulting in a syntax error. I always use quotations around directories out of habit. / is often used as a switch. To be safe, always quote directories. This is standardized across all commandline apps.
Click to expand...
Click to collapse
now i have a new problem it is saying /sd does not exist do you possibly have a screenshot of the path for the sd in a file manger you could post for me if not i will try to look at it with my wifes new phone and hope that the stock file system is the same as the modded system she has on the broken phone. also if this doesnt work how would i just do a full wipe of the phone so it looks like i just wiped it for privacy.
Try:
/storage/sdcard
/storage/sdcard0
/mnt/sdcard
/mnt/sdcard0
One of those should work.
Aerowinder said:
Try:
/storage/sdcard
/storage/sdcard0
/mnt/sdcard
/mnt/sdcard0
One of those should work.
Click to expand...
Click to collapse
IIts not giving me any errors, but its not giving me the files either, i tried to adb root to see if that would change and it says adbd cannot run as root in production builds, i tried to adb remount it says opperation not permitted, i tried adb shell then su and adb freezes and wont let me exit shell, it either freezes or just echo's what i type, so if i type exit it returns exit showing the word exit twice but leaves me no choice other than to close cmd and re open and restart adb, not sure what im doing wrong, the device show with adb devices in adb and shell but then says device not found when i try to su in shell lol, fml!