I really need some help please! I think I may have done something very bad. I have a tmobile mytouch 3g. I was trying to update from cyanogenmod 4.2.1.9. I was using a darkstar theme from ringer nation.
Here’s where I think i screwed myself. I am fairly new to all this stuff so I was trying to find a guide on how to update the mod and instead of doing it properly by adding the files to the sd card, doing a wipe, and then installing everything. I instead messed up and did an install of sapping.nbh and basically followed all the directions to originally root the phone. Including formatting the sd card and everything. When I realized that i was doing this all wrong I was still able to load my os and everything seemed ok. I was getting a sd card error that said that the card was blank or had an unsupported file system, but I was able to mount it so, I erased everything off the card and then put the cyanogen update and the drc83_base file and attempted to load into recovery and do the update.
I loaded into and did a wipe. I attempted to follow the instructions on upgrading from the cyogen page. (God I wish I had found that page first) But after I did the wipe and I attempt to Apply any from SD I get “error: sd card is not mounted”
When I attempt to reboot the phone it goes to the tmobile mytouch logo, THEN it goes to my them logo from Ringer Nation, then it just goes to a black screen I let it sit there for like 5 minutes to see what would happen, but nothing. So I took out the battery and sim. I can get into recovery though so I hope that someone can help me figure out where to go from there.I thought that since I had done a wipe that the theme would have been deleted as well? This is weird.
I did do a nandroid backup before. Hopefully that will prove to be helpful. Sorry for the long post, but I wanted to dump as much useful information about this problem so that hopefully someone will be able to help! BTW I'm using a mac with the latest snow leopard software.
As I am desperate for help, please reach out to me via aim – icolinirie or via email
Thank you in advance for everything. This is a great community, and all of Cyanogen’s work is greatly appreciated!!
EDIT: I really need some help! Here's some more information. I have a Magic 32B. Its running Cyanogenmod v1.4 + JF Recovery.
From what I have gathered I need to adp into my phone in order to get it to mount. Anyone know how to do this on a mac. I am trying, but I don't fully understand. I have created the .bash_profile from terminal and typed the following "export PATH=${PATH}:/Users/itunes/Documents/android-sdk-mac_86/tools" which is the path to the tools file in the sdk. I am just stuck at this point. I don't know what to do from here.
Hi I quote.
Install SDK utilities you need to connect your PC to your phone
You can download the full SDK from the Android Developer website for your platform
http://developer.android.com/sdk/index.html
You'll need to download the SDK appropriate for your platform and extract it into a directory somewhere. I'm going to assume you're using Windows here and suggest you extract it into a folder called
C:\AndroidSDK\
on your hard disk. You can put it anywhere you like really, but if you do you'll need to substitute it for the folder above.
Add the tools directory to your system path for easy access
In Windows it's easy to add the Android SDK Tools directory to your system path. Doing this lets you use the Android SDK tools anywhere and makes it easier for you.
On Windows XP: Go to Control Panel->System, Choose the 'Advanced' tab and then click 'Environment Variables' To do this on Vista/Windows7: Simply go to Control Panel->System and choose 'Advanced System Settings' and then 'Environment Variables'
Now that you've got here locate Path under System Variables and click Edit, then add the following to the end of the string displayed:
;C:\AndroidSDK\tools\
Then click OK until you get out of the menus.
Now that you've done this you should be able to bring up a command shell and type 'adb' and it should run straight away without needing to change path.
Please note that you can skip this step completely if you find it too complicated - however you will need to CD to the ?AndroidSDK\tools every time you open up a command prompt so it's worthwhile doing. I'm going to assume you have made the change above in all further examples as it gets too complicated really. If you're not confident in a DOS shell, I'd suggest you do a little bit of reading up on basic navigation in DOS first.
Enable Debugging mode on the phone before connecting to PC and installing the ADB driver
Menu > Settings > Applications > Developement > USB Debugging
Install the USB drivers correctly - check using "adb devices".
If you have already connected your phone to your computer before then the USB drivers are probably already loaded. If you're lucky then typing 'adb devices' in a command prompt will produce something like:
C:\AndroidSDK>adb devices
List of devices attached
XXXXXXXXXXXX device
Where XXXXXXXXXXXX is the serial number of your phone. If it doesn't produce that line, then you need to check Device Manager and ensure the device drivers for your phone were installed correctly.
If you are having issues installing the ADB driver, you need to connect your phone then go into Device Manager and check the ADB device properties. Check the following property and it'll look something like:
Device Instance Id: USB\VID_0BB4&PID_0C02&MI_01\7&293A7D0D&0&0001
To fix the driver installation problem, you need to edit the driver's .ini file and change all the references of 0C03 to 0C02, or 0C02 to 0C03 if your device property states your Device Id is 0C03.
Note: After flashing a new ROM, your Device Id may change again to either 0C03 or remain as 0C02. So you need to update the .ini file again as above to refelect the change and re-install the driver. Another known way to fix the above issue is to download and install HTC Sync - this seems to install the correct drivers.
How to use ADB
ADB stands for Android Debugging Bridge - it's a useful way of talking to your handset while it's running. ADB provides commands for copying files to and from your phone, installing packages and debugging your Android applications.
Useful commands include:
adb devices - lists which devices are currently attached to your computer
adb install <packagename.apk> - lets you install an Android application on your phone
adb remount - Remounts your system in write mode - this lets you alter system files on your phone using ADB
adb push <localfile> <location on your phone> - lets you upload files to your phones filesystem
adb pull <location on your phone> <localfile> - lets you download files off your phones filesystem
adb logcat - starts dumping debugging information from your handset to the console - useful for debugging your apps
adb shell <command> - drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
How to use Fastboot
Fastboot is another boot method and is used to drop the phone into a safe mode to load/flash alternate roms. You need USB debugging turned on before you can use Fastboot mode - so I'd recommend you do this first (under Settings->Applications->Development->USB Debugging). You will also need to power off your phone first (hold down Power and select Power Off) and then hold down the Back+Power Buttons to start the phone in Fastboot mode. You will need your USB cable connected to be able to issue any commands and assuming your drivers are correct you should be able to issue:
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
Other commands in this mode include - we'll cover these below in subsequent sections.
fastboot boot <filename> - boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> - flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
fastboot binaries for mac and linux can be found here.
3. Learn how to use fastboot and boot a recovery rom
Download a recovery rom for your device
There are several different recovery roms available for the HTC Magic devices.
Amon_RA has created several nice recovery roms available from http://forum.xda-developers.com/showthread.php?t=530492 and get the Recovery Rom appropriate for your device - these recovery roms have Nandroid Backup and Nandroid Restore and are perfect for the average user.
You can also use Cyanogen's 1.3.1 Recovery ROM available for: PVT32A devices and PVT32B devices - this rom has some additional options for partitioning your SD card for ?Apps2SD/Swapper/etc.
Fastboot the recovery rom
Fastbooting a rom doesn't write anything to your device - it just loads it directly from your PC - so it's a completely safe way of fixing/recovering/backing up your existing rom. To fastboot a rom you need to first drop your phone into Fastboot mode and check that it's working. Now drop into a command shell and make sure the recovery image you're wanting to load is in the same directory that you're running this in. If it's called something other than recovery-rom.img then substitute that instead.
C:\AndroidSDK> fastboot boot recovery-rom.img
If you are having problems changing the directory in the command prompt, just make a copy of the command prompt .exe itself, and place it in the folder that contains the recovery rom, then run the above command.
And once again, if you have a perfected SPL which does not allow remote fastboot, you will have to fix it first.
Use the Recovery Rom to Backup your current ROM with Nandroid
Once you've booted to a recovery rom - you can use the Nandroid Backup option. If you get a 'cannot mount /dev/mkblkxxx error' when you do this then check your microSD card is inserted correctly and if so, wait a few seconds for it to register to the recovery rom correctly. If at first you don't succeed, try, try again (sdcard can take a few seconds to mount!)
You do not need to be a rocket scientist to do this.
you can use the ADB to put in recovery again by fast boot
http://forum.xda-developers.com/showthread.php?t=530492
Hey! First off Thanks for the reply! I really appreciate someone chiming in to throw some advice my way! But while reading your thread you described the instructions for windows. In this case I have a macbook pro running snow leopard.
I did download the android sdk to my documents folder and I understand that I need to execute some scripts from the terminal on my mac to get things running. But I really dont know what those scripts are or what exactly to do.
I can get into the recovery mode on the MyTouch by holding power and home when powering on. So do I open the console from the recovery screen on the mytouch and then run the scripts on the terminal from my macbook? And which scripts should I run to get the sd card mounted onto my desktop (that is what I'm trying to do). Im not too sure what to do from there either. I want to get the phone back to stock android 1.5 os so that I can root again. My sd card has to be corrupted because it keeps giving me an error saying that it wont mount when I try to do a fix file systems or try anything from that menu. What to do??
What!
can you get in the recovery?
Yeah I can get into cyanogen v1.4 recovery. I'm just stuck from there.
Ok ok If I understand this correctly then you are not briced. you do not have any imag on your phone.
if you do not have anything nadroid recovery on sdcard you must enter a new ROM on the sdcard and flash it
remember full wipe.!
Yes this is what I believe I must do. But I need to either find a way to mount my SD card from the phone while it is in recovery mode (cyanogen v1.4). That's my problem.. I wish there was an easier way to get it mounted onto my mac from the recovery screen. I think I'm just going to go to best buy tomorrow and get a micro sd card reader and maybe another sd card just in case.
Once I have done that though. What files should I put onto the sd card in order to flash it back to original factory android 1.5.
What do you think?
Good idea
I have never used cyanogen v1.4 recovery
I use the recovery-RA-sapphire-v1.5.2H.img and ther you can use USB togle in recovery mode, You must go to the store to buy the adapter that fits on your Mac, I have two adapters for your Mac, you can borrow
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
icolinirie said:
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
Click to expand...
Click to collapse
Bergen . norway.
http://maps.google.no/maps?f=s&utm_...o-google-gm&utm_medium=ha&utm_term=google map
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
icolinirie said:
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
Click to expand...
Click to collapse
it is sick cold. I'll take one picture out the window
How to unbrick soft bricked Atrix, I installed http://www.youtube.com/watch?v=wQvrEH74dgI and when I installed Gapps, it didn't started and when I tryed system restore it did so but when it started it got stucked at "M" screen and nothing else is happning.
knotabs loca
manyelski said:
How to unbrick soft bricked Atrix, I installed http://www.youtube.com/watch?v=wQvrEH74dgI and when I installed Gapps, it didn't started and when I tryed system restore it did so but when it started it got stucked at "M" screen and nothing else is happning.
Click to expand...
Click to collapse
I'm in a similar situation. I was asked to use latest CWM. I happened to use Tenfar's CWM that came with the boot loader unlock.
I haven't tried it yet. Will give a shot this weekend
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Intelensprotient said:
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Click to expand...
Click to collapse
I can't turn on my phone, or DO ANYTHING with it, the only thing is that I get "M" screnn taht's all, if i want to turn it down I hae to do a battery poll.
Excactly, that's what Early Enumeration is for Usually, USB is loaded when the OS is up, I suppose - at least you can't normally connect with ADB during boot. However, with Early Enumeration set, you can connect while the phone is still booting and access every capability ADB or the shell is able to provide. (Granted, uninstalling the .apk in question with adb uninstall did not work for me, that's why I posted the manual approach, but that may have been an error on my side.)
I wonder if my issue is the same. Mine is stuck in a 'dual core' reboot over and over.. I can't get into recovery mode or anything. Sometimes I hate phones.
JeRrYFaR said:
I wonder if my issue is the same. Mine is stuck in a 'dual core' reboot over and over.. I can't get into recovery mode or anything. Sometimes I hate phones.
Click to expand...
Click to collapse
Mine is tha same
Stuck in mortorola unlocked boot screen
Intelensprotient said:
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Click to expand...
Click to collapse
How do you find the device's IP address?
So I have a bit of an issue. Somehow last night, after trying to help my parents with our home theater system, with the device laying on a soft surface, the LCD (not the glass) somehow broke. I am really not sure how this happened, the phone itself didn't fall, it was laying on a bed the entire time. When I went to grab the phone and turn it on, I was pretty surprised. You can see what I mean in the attached file.
Now the problem with this is, while I would normally just walk into the Sprint Store, complain and get a new phone. I am not in the US for another 5 months. In the mean time of trying to figure out what to do, I would like to at the very least, grab any files off my phone, or back up my phones' file structure.
I am able to do a minimal amount of tapping on the phone, only on the upper half of the screen, but I can't see anything, nor does the device respond with any touch data from the bottom half.
I obviously can't access the files if the device is locked, which means I have to bypass the lock screen. I found this guide, but unfrotunately, Method 1 didn't work, and I can't get adb to recognize my phone for Method 2.
I also have tried using CWM (the non-touch version) to backup my data, but I let it sit there for 45 minutes and I couldn't tell if it was finished or not. It didn't appear to actually be doing anything.
Could someone help me navigate around this or provide some assistance in allowing me to just get the files off the phone while I search for a new one?
With that being said, does anyone have some recommendations? I was thinking of getting a Motorola X or Nexus 5.
EDIT: Update:
I have access to terminal via Cerberus shell. I was able to use Method 2 to disable the lock screen (or in this case set it to Swipe). It is still pretty difficult to use the phone but I can at least backup whatever data I still do have on the phone to my laptop.
Would anyone be able to give me some advice as to uninstall applications or XDA xposed modules via shell? Or perform a backup or enable ADB debugging?
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Darnell0216 said:
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Click to expand...
Click to collapse
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
slixzen said:
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
Click to expand...
Click to collapse
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Darnell0216 said:
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Click to expand...
Click to collapse
I have a sony xperia P that I am using right now until the replacement phone I got arrives. Any idea how I could use that? I have had minimal success with the phone so far in trying to get that phone to flash custom recoveries, to root the device (not sure why, but my laptop just doesn't want to seem to do it, even using automated tools).
Is it better to just wait for the replacement phone to arrive and grab what I need from that and push it? Could you link me to any guide or steps that you used with yours?
Thanks for such quick responses by the way!
EDIT:
Flashing TWRP and booting into recovery with command prompt open and running adb devices / fastboot devices does not show any devices available.
Is there a specific menu setting or other option I need to use to be able to run adb?
When you use TWRP, the phone will be recognized by the PC but the driver doesn't install correctly off the bat. Go to Device Manager and look for your phone. You may need to click the View -> Show Hidden Devices option. Update the driver manually by selecting the one provided by your manufacturer. Some have a dedicated ADB driver for specific functions (bootloader, etc).
The adb key is stored in data/misc/adb/adb.keys -You can pull this file from any other android connected to that PC (or just copy it if you have a root explorer) and push it to the broken one if necessary. This will bypass any ADB authorization issues while the phone is fully booted and let you see the screen.
➜ No big ol’ SDK ➜ Latest Google drivers ➜ No messing with inf files ➜ ADB from any location ➜ Drag and drop files
Figured XDA needed a couple more ADB driver guides, so I'm bringing these down from Google drive where they've been getting a lot of use--with no complaints so far. :fingers-crossed:
Follow the steps below to install the Google ADB driver for "normal" (OS) mode.
Follow post #2 to install the driver for sideload mode. You must do this to sideload OS .bin files via stock recovery.
See post #3 for basic info/tips for using the command window and entering adb commands.
[EDIT September 21, 2015] If you're running Windows 10, read this:
At step 3 you install 15 Second ADB Installer. Some Win 10 users are reporting a problem. Please do this to help track it down:
- Be sure to run as Administrator.
- If you get an error, post the exact error and when it happens. Do not rerun Installer until someone replies to post.
- If you do not get an error, please post and say so and tell what type of Win 10 you have (home, pro, enterprise, etc.)
Thanks!
Install ADB Driver for "Normal" (OS) Mode
This uses @Snoop05's 15-Seconds ADB Installer. It provides the driver and software you need and puts the path to adb.exe into your PATH variable so you can run ADB commands from any folder.
Before you begin:
(1) Turn off anti-virus software
(2) Disconnect other physical devices that use adb and shut down any virtual ones. This can go very smoothly if you're not running anything that uses adb, including emulators, some photo-sync software, Gatesjr debloater, etc.
1. Make sure adb debugging is enabled on the the device. (Settings->My Device->Developer Options: Debugging)
To open Developer Options: In Settings -> My Device, tap on the serial number until Developer Options appears at bottom of screen.
2. If you've never connected Fire HD to computer, connect now and read this:
a. You may see a USB debugging message on tablet, tap "Always" and "Allow."
Even if you don't see message, Windows should try to install generic MTP drivers (not ADB!). Wait until you see success or failed message.
b. Unplug/replug and wait for Windows Explorer OR for message that prompts what to do when device is connected and choose Open window to Display Files, check Always do this and then OK.
c. Disconnect..
3. If you KNOW there’s no adb driver installed for the device, go to next step.
. . . If driver might already be installed, do hidden steps.
Connect to computer, open Device Manager (instructions below) and see if a driver is listed under Android Device.
- If a driver is NOT listed, go to next step.
- If a driver IS listed, open CMD window in folder containing adb.exe and run adb devices command (step 12).
* If adb devices DOES return an ID, this driver is working and you don’t need to install a different one.
* If adb devices does NOT return an ID:
a. In Device Manager, right-click the driver and choose Uninstall.
b. Unplug the device and restart Windows.
4. Download the latest version, currently v. 1.4.3, of 15 seconds ADB Installer and run it as Administrator.
If you are not Administrator, right-click the file and choose “Run as Administrator“
Read all about 15-seconds Installer at the link.
Press Y to install ADB and Fastboot
Press Y to install ADB system-wide or N for current user onlyYou should see:
Installing ADB and Fastboot . . .
4 files(s) copied
If you see 0 files copied, post the error with your Windows version and the drive it's installed on.
Press Y to install drivers
View attachment 3455788
5. An Install Wizard will run. Look for it and install device software!
6. Connect the Fire to the computer and wait until you see it in Windows Explorer.
7. 6/3/2016 Update for Win 10: Your drivers might already be installed. Check for Allow USB Debugging on tablet. Go to step 12 and run the adb devices command.
. . . If it shows serial number and unauthorized, you need to enable USB debugging and run command again. It should then show serial number and "device." You're done!
. . .If it doesn't show serial number, continue the steps.
Win 7 and 8.1: Open Device Manager:
Win10: ? Win8: Right-click Start Button and choose Device Manager. Win7: Click Start button and type Device Man [enter]
8. Find Fire under Other Devices, right-click it, and choose Update Driver Software.
If you don't see Fire under Other Devices, disconnect/reconnect or try a different USB port, or try toggling Enable ADB in Developer Options. If nothing works, disconnect and reboot both Fire and computer and try again.
{
"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"
}
9. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
10. Find Android Device, click it and press Next.
. . . If Android Device is not listed, look here.
If you DID NOT run 15 Seconds ADB Installer, STOP, disconnect from PC and run it now.
If you DID run 15 Seconds ADB Installer:
a. Double-click Show All Devices.
b. Under Manufacturer, scroll to Google, Inc, click it and continue.
↠ If Google, Inc is not listed, the ADB drivers are not installed, they installed incorrectly or were corrupted. STOP now and follow all the steps again.
11. Select Google, Inc in left pane and then Android Composite ADB interface in right, and press Next.
If the screen you see only has the Model pane (on the right above), scroll down to Android Composite ADB.
↠ If the driver is not listed, drivers have not been installed, they installed incorrectly or were corrupted. STOP now and follow all the steps again. 12. At the warning screen, press Yes.
Driver is updated!
13. Run the adb devices command and confirm it returns a device id:
a. Open CMD window: Hold down the Shift key, right-click the desktop (or an empty space in a folder) and choose Open command window here.
b. Type: adb devices [enter]
View attachment 3467199
If you see an ID followed by “device,” the driver is installed correctly. DONE!
If you see an ID followed by “unauthorized,” look at the tablet for “Allow USB Debugging?” message and tap OK.
If debugging message disappears before you say “OK,” unplug/replug tablet to see it again.
Repeat the adb devices command and confirm it now looks like above. DONE!
If you do not see an ID, the driver may not be correctly installed or USB debugging might still be disabled on your tablet. Verify all connections and reboot tablet and PC and repeat this step. If adb devices still doesn’t return an ID, follow this guide from the beginning again.
Install ADB Driver for Sideload Mode
Windows can’t recognize the Fire in sideload mode until you install the driver for it.
Note: These steps are pretty much identical to Post #1. Refer there for illustrations.
1. Connect the tablet to the computer and put it into sideload mode, like this: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
To reboot to recovery:
- From CMD window, run: adb reboot recovery
or
- Manual: (a) Power off the Fire. (b) Hold the power and volume-up buttons until Amazon logo appears, then let go.
2. Open Device Manager, find KFARWI under Other Devices, right-click it and select Update Driver Software.
If you don't see KFARWI under "Other Devices," see hidden text.
When KFARWI isn't under Other Devices, first be sure you "clicked" Apply Update from ADB on tablet to get into sideload mode.
If you did, see if "Android Device" is listed at top of Device Manager with a driver under it.
If Android Device is not listed, unplug/replug the tablet and see if KFARWI shows up under Other Devices. If it does, go to step 3. If it doesn't, post the problem.
If Android Device is listed, open CMD window in folder containing adb.exe and run adb devices command
- If adb devices returns an ID, this driver is working and you don’t need to install a different one.
- If adb devices does not return an ID, in Device Manager, right-click the driver, select Update Driver Software and go to Step 4.
3. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
[See “Select your device’s type”]
4. Click Android Device.
[See "Select the device driver you want . . .”]
5. Select the same driver you use for “normal” OS mode (post #1, step 10) and press Next.
6. Click Yes at warning screen.
Driver is updated!
7. In CMD window, run adb devices command and confirm you see your device ID and "sideload," like this:
8. DONE! Issue the sideload command or reboot to exit sideload mode.
Note (shouldn't happen, but . . . ) If you don't get a device ID and you had a driver installed at step 2 and updated it, you'll have to uninstall the driver.
In Device Manager, right-click and uninstall the driver under Android Device.
Restart computer and reboot tablet (to get out of sideload).
Go into sideload mode, right-click KFARWI under Other Devices and see if it has Update Software option.
- If YES, update the driver.
- If NO, reboot once more and go into sideload and you'll have Update option. Update the driver.
Info and Tips for Using the Command (CMD) Window - for "Newbies"
Here's some basic info for using the CMD window and entering commands found in the guides.
Open CMD window
Hold down the shift key, right-click an empty space in an open folder (including desktop), and choose "open command window here"
Give commands on-the-fly
If you used 15-Second Installer (post #1) you can open the CMD window from any convenient location, so you can easily give adb commands "on the fly."
Example: Open CMD from desktop and run adb devices to confirm adb recognizes your Fire.
Install an app (or sideload a bin file)
Open CMD window in the folder containing the file and enter the command: adb install filename.apk
If you open CMD from a different folder, include the full path: adb install "full_path_to\filename.apk"
Format: If there are spaces in the path or filename, put quote marks ( " ) around "full_path_to\filename.apk"
Drag & drop files and copy/paste commands
To enter a long or complicated command or file name into the CMD window, use drag & drop or copy/paste.
Drag and Drop
Type: adb install <--type a space after "install"
. . . then drag and drop your file into the window. The "full_path_to\filename.apk” will be inserted at cursor.
Copy and Paste
Select the command or long file name and use CTRL-C to copy it. In CMD window, type adb install(space) as above, right-click the top bar of the window and choose Edit then Paste.
Installing drivers for sideload
Is there a discussion or a fix for installing the ADB drivers for sideload using windows 10? I'm not sure if Windows 10 is the issue, but instead of getting KFARWI in device manager, I get MT65xx android device. I've followed the instructions after step 9 several times with no luck. I've tried updated the drivers with the ones mentioned in step 3 but ADB device doesn't list a device. Any suggestions?
rking38 said:
Is there a discussion or a fix for installing the ADB drivers for sideload using windows 10? I'm not sure if Windows 10 is the issue, but instead of getting KFARWI in device manager, I get MT65xx android device. I've followed the instructions after step 9 several times with no luck. I've tried updated the drivers with the ones mentioned in step 3 but ADB device doesn't list a device. Any suggestions?
Click to expand...
Click to collapse
Sounds like you're opening Device Manager while in recovery, not sideload mode. Look at step 1 again: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
Once in sideload mode, you should see KFARWI.
(I edited OP to make step for getting into sideload more obvious)
DoLooper said:
Sounds like you're opening Device Manager while in recovery, not sideload mode. Look at step 1 again: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
Once in sideload mode, you should see KFARWI.
(I edited OP to make step for getting into sideload more obvious)
Click to expand...
Click to collapse
Wow...follow the instructions from step one! thanks for your patience
15 Second ADB problem
DoLooper said:
Installing Google ADB drivers for your Fire HD:
Click to expand...
Click to collapse
MRDirtyPixels said:
I followed a guide to install Lolipop on my device, I managed to get the 15 Second ADB Installer but could only get the 1.3 version to work.
When I try to do it now it states on the device that I need 1.3.2 or higher. The 1.4 download gives me an Access Denied message and installed 0 drivers.
Click to expand...
Click to collapse
Someone else encountered this with 15 Second installer. Are you running Win10? What flavor (pro, home, etc)? At what point exactly is "Access Denied" displayed with version 1.4.2?
Also, do you have folder, C:\adb or C:\users\username\adb? If yes, what files are in it?
Please let me know these things so I can try to find a fix. EDIT: @MRDirtyPixels I'll post how to update the driver when you reply. Thanks!
Fire HD 6 on 4.5.3
Win7 Ultimate x64
I'm having an issue at "Apply update from ADB". I do not have this option in recovery - only "Reboot your Fire", and "Reset to Factory Defaults".
I've had ADB drivers installed from past projects. Tried it, got this issue. Went back and installed the ADB drivers from the 15 second installer to see if that helped, still have this issue.
Also, at no point is my Fire listed under "Other Devices" - I don't even have that listed as a category. The Fire is always listed under "Android Device" > "Android Composite ADB Interface", so I figured my drivers were all set.
Any ideas would be greatly appreciated.
**EDIT: Should I somehow remove/uninstall all ADB related drivers and software and try again?
You use sideload mode to downgrade to 4.5.3 from OS 5. (It's only an OS 5 recovery option.) Since you're on 4.5.3, presumably with OTA blocked, you don't need sideload. Sounds like your drivers set up right for OS mode. Go root!
EDIT: @jiznon Be sure OTA is blocked. Else you'll OTA update as soon as you turn on wifi to root!
DoLooper said:
You use sideload mode to downgrade to 4.5.3 from OS 5. (It's only an OS 5 recovery option.) Since you're on 4.5.3, presumably with OTA blocked, you don't need sideload. Sounds like your drivers set up right for OS mode. Go root!
EDIT: @jiznon Be sure OTA is blocked. Else you'll OTA update as soon as you turn on wifi to root!
Click to expand...
Click to collapse
Oh, great! I may have overlapped a guide or two. Thanks so much!
I managed to turn airplane mode earlier as the OTA began to download. Should be good, ya?
jiznon said:
I managed to turn airplane mode earlier as the OTA began to download. Should be good, ya?
Click to expand...
Click to collapse
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
DoLooper said:
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Click to expand...
Click to collapse
I see. That step isn't for sometime in the guide I'm following (it also states to install sideload drivers). Maybe it should be edited.
http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
jiznon said:
I see. That step isn't for sometime in the guide I'm following (it also states to install sideload drivers). Maybe it should be edited.
http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
Click to expand...
Click to collapse
Well, it's the step you do before turning on wifi to root. Notice that first step says that if you're on 4.5.3, get kingroot and go to step 6. So you're right there, at step 6.
jiznon said:
. . . (it also states to install sideload drivers). Maybe it should be edited. http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
Click to expand...
Click to collapse
Yes, I see I introduced some confusing info about drivers/versions in last update. I'll fix. thanks.
DoLooper said:
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Click to expand...
Click to collapse
DoLooper said:
Well, it's the step you do before turning on wifi to root. Notice that first step says that if you're on 4.5.3, get kingroot and go to step 6. So you're right there, at step 6.
Click to expand...
Click to collapse
Right. I'm still at "Before You Begin:
Install adb device drivers if you don't have them.
Here's an illustrated guide for Windows drivers. Install driver for both OS mode and sideload mode."
Wanted to make sure I don't miss anything. Looks like I'm on the right track. Thanks!
**EDIT: Everything went smooth. Thanks everyone!
Hi DoLooper, I'm currently following your [Root] OS 4, 5.0.n and Install Lollipop & Gapps ("Newbie Friendly") guide to root and update a Fire HD 7 and that's how I got here. I have successfully completed this guide, but only after I solved a problem that I ran into along the way. I solved it myself, so I want to share how I did it.
I had a Samsung phone before, had Samsung Kies (bringing along drivers) and "Minimal ADB and Fastboot" installed. I had removed all of these and all traces of them I could find. But when I got to step 4 of your first post in this guide, it always asked whether I wanted to install a driver with the name "Google, Inc. SAMSUNG Android Phone". I was worried the driver might be set wrongly in some way and I would brick my Fire tablet during the rooting process because of that (possible?). I continued anyway and after the driver installation finished, it didn't refer to the Fire as a Samsung device in the device manager anymore and the other steps in this guide were successful as well. So I guess I'm safe now.
However, I do have to add that when the Samsung drivers from Kies were still installed (I forgot about them at first), the device manager did refer to the Fire as a Samsung even after step 4. So I guess the moral is that you have to clean your system of other Android drivers/software thoroughly and restart first - and only then begin the procedure described in this guide.
Last but not least, thank you very much for spelling everything out step by step, it all seems like a doable task now.
podikan said:
. . .
I had a Samsung phone before, had Samsung Kies (bringing along drivers) and "Minimal ADB and Fastboot" installed. I had removed all of these and all traces of them I could find. But when I got to step 4 of your first post in this guide, it always asked whether I wanted to install a driver with the name "Google, Inc. SAMSUNG Android Phone". I was worried the driver might be set wrongly in some way and I would brick my Fire tablet during the rooting process because of that (possible?). I continued anyway and after the driver installation finished, it didn't refer to the Fire as a Samsung device in the device manager anymore and the other steps in this guide were successful as well. So I guess I'm safe now.
However, I do have to add that when the Samsung drivers from Kies were still installed (I forgot about them at first), the device manager did refer to the Fire as a Samsung even after step 4. So I guess the moral is that you have to clean your system of other Android drivers/software thoroughly and restart first - and only then begin the procedure described in this guide.
Click to expand...
Click to collapse
This is helpful and I'd like to add it, but I'm a little confused. Step 4 is just installing the 15-second Installer software. I don't think it asks anything. Could you please clarify the step where you got that prompt? Also, when it was listed under Samsung, you were able to right-clicking and choose Update and install the google drivers, right? Thanks.
Well, at the end of step 3 the program 15 Second ADB asks "Do you want to install device drivers?" and then a windows prompt appears. This is when I got the following prompt on top of that (only have it in German, sry): imageshack.com/a/img911/8983/bBg2q0.jpg I assume it's some kind of driver, as 15 Second ADB calls it. Is it really specific to a device?
As for your second question, if I remember correctly I was able to do that (I had to dig for it like you explain in step 9 after ". . . If Android Device is not listed, look here."). But afterwards it was still displayed as a (fully installed) Samsung portable device in my device manager. No chance I would go ahead and root from there. That's when I found and removed the Samsung drivers which came with Kies, rebooted, and started the procedure from the beginning.
ADB not cooperating
Ok. I am on a Fire HD 7 Gen 4 at OS 5.1.1, and attempting to downgrade to 4.5.3 for rooting purposes. (My eventual goal is to get CyanogenMod or another 'pure android' ROM on it, if you can help with that, great) When in sideload mode, Windows doesn't detect my device at all (no KFARWI or any other 6-letter combo) but ADB can detect it in both sideload and OS mode. My problem is this: Whenever I attempt to flash a .bin stock recovery, adb stalls for about a second, while on my Fire I only see:
Now send the package you want to apply to the device with "adb sideload <filename>"
Finding update package...
Opening update package...
Verifying update package...
before the device reboots. On adb I then see: "failed to read command: connection reset by peer" Any subsequent attempts without a manual reboot into sideload mode just instantly time out. I have a feeling this has something to do with the weird reboot, but how do I prevent it?
DoLooper said:
Install ADB Driver for Sideload Mode
Windows can’t recognize the Fire in sideload mode until you install the driver for it.
Note: These steps are pretty much identical to Post #1. Refer there for illustrations.
1. Connect the tablet to the computer and put it into sideload mode, like this: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
To reboot to recovery:
- From CMD window, run: adb reboot recovery
or
- Manual: (a) Power off the Fire. (b) Hold the power and volume-up buttons until Amazon logo appears, then let go.
2. Open Device Manager, find KFARWI under Other Devices, right-click it and select Update Driver Software.
If you don't see KFARWI under "Other Devices," see hidden text.
When KFARWI isn't under Other Devices, first be sure you "clicked" Apply Update from ADB on tablet to get into sideload mode.
If you did, see if "Android Device" is listed at top of Device Manager with a driver under it.
If Android Device is not listed, unplug/replug the tablet and see if KFARWI shows up under Other Devices. If it does, go to step 3. If it doesn't, post the problem.
If Android Device is listed, open CMD window in folder containing adb.exe and run adb devices command
- If adb devices returns an ID, this driver is working and you don’t need to install a different one.
- If adb devices does not return an ID, in Device Manager, right-click the driver, select Update Driver Software and go to Step 4.
3. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
[See “Select your device’s type”]
4. Click Android Device.
[See "Select the device driver you want . . .”]
5. Select the same driver you use for “normal” OS mode (post #1, step 10) and press Next.
6. Click Yes at warning screen.
Driver is updated!
7. In CMD window, run adb devices command and confirm you see your device ID and "sideload," like this:
8. DONE! Issue the sideload command or reboot to exit sideload mode.
Note (shouldn't happen, but . . . ) If you don't get a device ID and you had a driver installed at step 2 and updated it, you'll have to uninstall the driver.
In Device Manager, right-click and uninstall the driver under Android Device.
Restart computer and reboot tablet (to get out of sideload).
Go into sideload mode, right-click KFARWI under Other Devices and see if it has Update Software option.
- If YES, update the driver.
- If NO, reboot once more and go into sideload and you'll have Update option. Update the driver.
Click to expand...
Click to collapse
thank you
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.