I unlocked/rooted/installed the stock Android ROM via the All-in-one tool yesterday. Everything went well, except I was getting some errors in Android with the stock ROM, specifically with the phone and media applications. They were both crashing. I read in the ROM thread that you have to flash the radio to get rid of the phone error. Well, I didn't read that before I loaded everything so that .zip wasn't on the phone itself.
Now the phone doesn't show up in Windows, or if it does, it shows up as a CD-ROM drive that I cannot access. I tried flashing it with ADB, but I'm having issues with that as well. When I plug in the phone, I can do "adb devices", and it shows up fine. Reboot into the bootloader/fastboot, everything is fine. Then as soon as I try to do anything, flash the radio, push the .zip to the phone, I get "error: device not found", and I can no longer run any commands on the phone until I reboot the phone and end adb.exe via task manager. Then the cycle continues.
I'm normally pretty good with these things, but I'm stumped here. I've used Android devices in the past, but was an iPhone user for a long time and now I'm coming back and it looks like a lot of this stuff has changed.
Any help is appreciated, at this point my phone is pretty much useless
Thanks!
EDIT: I should also note that I can sometimes get the radio flash to go through, but then I get a "FAILED (remote: signature verify fail).
smaug8821 said:
I unlocked/rooted/installed the stock Android ROM via the All-in-one tool yesterday. Everything went well, except I was getting some errors in Android with the stock ROM, specifically with the phone and media applications. They were both crashing. I read in the ROM thread that you have to flash the radio to get rid of the phone error. Well, I didn't read that before I loaded everything so that .zip wasn't on the phone itself.
Now the phone doesn't show up in Windows, or if it does, it shows up as a CD-ROM drive that I cannot access. I tried flashing it with ADB, but I'm having issues with that as well. When I plug in the phone, I can do "adb devices", and it shows up fine. Reboot into the bootloader/fastboot, everything is fine. Then as soon as I try to do anything, flash the radio, push the .zip to the phone, I get "error: device not found", and I can no longer run any commands on the phone until I reboot the phone and end adb.exe via task manager. Then the cycle continues.
I'm normally pretty good with these things, but I'm stumped here. I've used Android devices in the past, but was an iPhone user for a long time and now I'm coming back and it looks like a lot of this stuff has changed.
Any help is appreciated, at this point my phone is pretty much useless
Thanks!
EDIT: I should also note that I can sometimes get the radio flash to go through, but then I get a "FAILED (remote: signature verify fail).
Click to expand...
Click to collapse
Hey, want me to take a look on TeamViewer?
Matt said:
Hey, want me to take a look on TeamViewer?
Click to expand...
Click to collapse
Sure, let me set it up on that machine. I have it on a computer at work right now.
You use any IM programs? I basically use them all.
smaug8821 said:
Sure, let me set it up on that machine. I have it on a computer at work right now.
You use any IM programs? I basically use them all.
Click to expand...
Click to collapse
Hangouts really
Related
sorry if this clutters up the forum for a bit, i promise to delete it when it dies.
i've recently started using adb when i flashed over to 5.0.2h. i followed the instructions in the tutorial and was able to use adb. 2 nights ago, i began doing more complicated commands (for me) and tried to push a .apk into /system/app.
i wasn't immediately successful but i eventually got it in there and decided to reboot my phone. after this reboot, however, i lost the use of adb. i tried upgrading to the usb drivers haykuro posted, uninstalling them and re-trying the old one, rebooting the computer, rebooting my phone and none of it works. i've since wiped my phone and flashed it with the latest h build from haykuro (thanks haykuro!) but that didn't work either. now i'm trying to see if the 1.5 sdk will work.
i was wondering if anyone would have an idea about what i should do next. should i reinstall adb? try it on another computer? another cable? it's not the worst loss in the world, my phone is fine and my usb cable still works in the conventional way. i even checked to see if i somehow lost root and i was able to get su on the terminal emulator. but i still want the use of adb for nandroid, if nothing else.
thanks in advance!
I had the same problem after flashing to the G rom. I couldn't get ADB to work but fastboot recognized my phone and I was able to flash back to my backup. First time I did a complete wipe before flashing, second time, no wipe, made no difference in either case for me
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
I just had the same problem, I had to update the driver and it is working fine now.
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
zer0day said:
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
Click to expand...
Click to collapse
Give me a few minutes I will find you a link for it.
jordanjf86 said:
Give me a few minutes I will find you a link for it.
Click to expand...
Click to collapse
Here it is. http://dl.google.com/android/android_usb_windows.zip after downloading this when you go to update your driver in device manager make sure to use this. Hopefully this will help it worked for me.
jashsu said:
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
Click to expand...
Click to collapse
yes, that's what it comes up as. and i've tried the usb drivers from haykuro's page and they didn't work before and after rebooting my computer.
i'm on vista and it wont accept the updated drivers. it downloads the standard removable memory drivers and wont let me update to anything else. anybody have any ideas
just installed the 1.5 apk and adb and it works again. for people running haykuro builds, i would suggest trying this if you have adb problems. just intall the 1.5 sdk as normal, copy adb.exe and AdbWinApi.dll into \system32 and you should be good.
unless requested i will delete this thread in two days. thanks everyone!
Hmm... i tried that and its still not working ):
Ive tried like 10 different USB drivers from various sites including this one, downloaded the 1.5 SDK and installed it, wen through several reboots and it always says either that the driver is for the wrong platform, the most up to date one is ALREADY installed (HTC Bootloader), or that Windows couldn't find any drivers.
Under ADB Interface in device manager is "%USB\VID_0BB4&PID0FFF.DeviceDescRelease%"
did you try and update the driver through the device manager? i've heard that it's the only way to update it for some people.
I had already Posted & Solved This Issue here : http://forum.xda-developers.com/showthread.php?t=493703
Go Check It, It ll work for sure....
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:
Hi
I actually replying about the bible quote you have mentioned? you into theology?
I'm using Rogers HTC dream and i'm planning to get the cyannogen mod going.
well changing the spl is not a problem and my phone is running spl1.33.2005.
When i try to use to fastboot method from cyannogen's wiki
i can't get the usb drive works, it keeps saying that :"windows cannot install drivers". At first time i thought it is win7 64bit system's problem. Then i try to do it on a winxp machine, it didn't work either!
Thanks
Try this:
http://wiki.cyanogenmod.com/index.php/Install_the_Latest_Android_sdk#Windows
beav_35 said:
Try this:
finally got the usb works, no question marks etc. Now is the damn fastboot mode doesn't work now......I know I'm so close to the finishing line
Click to expand...
Click to collapse
What's wrong? Describe what is happening and I will try to help you get it working.
lol thanks man. after few hours searching on the internet, i found out that many people have the same problem as i do.
when type in "fastboot devices", there is no "serial number" coming out, if you try "fastboot reboot", the cmd will stay on "waiting for devices".
This can be solved by downloading the android SDK package. Put the system.img and radio.img into it. try "fastboot" again.
For me it works, as soon as seeing the serial number on the cmd, i'm so happy^^.
well, the phone is faster in responding, but the available is reduced
In the stock rom I usually seeing 40MB available, but right now I only have 32MB?
That is to be expected because the rom installs some apps that you probably didn't have before. If you setup apps2sd it will move all your apps over to the sd card and free up lots of space. I have 77mb available space.
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.
Hello all,
I am very new to the community of rooting and am completely lost. A friend of mine gave me this dell streak 7 because someone gave it to him and he was never able to get it to work. I am stuck at "Starting Fastboot USB download protocol" If someone would possibly explain how I might go about fixing this and using it with it's maximum potential I would appreciate it very much. Now although I am very tech savvy I don't have the slightest clue about rooting or loading custom roms so I will have to be talked to like a child until I get comfortable. As of now I have connected the streak to my computer but have yet to have it recognized. That's pretty much as far as I have gotten. I do have a 32gb SD card as well if it needs to be used in the process somehow.
Thanks for all everyone's time and help
Incase the thumbnail does't work here is a link for dropbox
dropbox.com/s/yqc8s4ndybqrwnr/2013-02-25%2009.08.52.jpg
Your not stuck, it's just waiting for you to use the Fastboot command from your PC. Open the little side door, insert a small paperclip into the small hole to reboot normally if it will.
Read this also: http://forum.xda-developers.com/showthread.php?t=1395964
YAY !
wptski said:
Your not stuck, it's just waiting for you to use the Fastboot command from your PC. Open the little side door, insert a small paperclip into the small hole to reboot normally if it will.
Read this also: http://forum.xda-developers.com/showthread.php?t=1395964
Click to expand...
Click to collapse
ok so, while waiting for a response from someone on here I was playing around with it and realized that the first step i was missing was getting the computer to recognize the tablet. I never had the correct drivers installed and I was having a hard time getting windows to recognize the drivers.
Anyway I am finally able to get the drivers into windows and now I am able to control the device from the command prompt on the computer.
What is my next step? how do i load the rom into the device ? and which one is the best to use for this one ?
I'm thinking the last person who had this device messed it up very badly and now all it wants to do is go into fasboot mode nothing else, i thought I had installed the (Clockwork mod recovery.img) S7-6.0.1.2.img into the recovery using this guide http://forum.xda-developers.com/showthread.php?t=1334487,
After i do that I says done. but nothing happens on the device after is says "Flashing StorMgr partition recovery"
sending 'recovery' (4742 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.010s]
finished. total time: 0.543s
ddg5060 said:
ok so, while waiting for a response from someone on here I was playing around with it and realized that the first step i was missing was getting the computer to recognize the tablet. I never had the correct drivers installed and I was having a hard time getting windows to recognize the drivers.
Anyway I am finally able to get the drivers into windows and now I am able to control the device from the command prompt on the computer.
What is my next step? how do i load the rom into the device ? and which one is the best to use for this one ?
Click to expand...
Click to collapse
You have your choice. You can use HoneyStreak ROM's by DJ_Steve, which are completed (Honeycomb Android 3.2)
You can run my CM10.1 (Android 4.2.1)
Where to now ?
giveen said:
You have your choice. You can use HoneyStreak ROM's by DJ_Steve, which are completed (Honeycomb Android 3.2)
You can run my CM10.1 (Android 4.2.1)
Click to expand...
Click to collapse
Yes but exactly how do I do that? I can't seem to figure out where to start the flashing process. All I am able to do with my device is get into fasboot mode, where do I go from there ? I want to use CM10.1
I tried holding vol (+) and power - nothing
I tried holding vol (-) and power - nothing
Thanks again for all your help
Search is your greatest ally. This has been answered a good 50-100 times.
Yes i know
giveen said:
Search is your greatest ally. This has been answered a good 50-100 times.
Click to expand...
Click to collapse
Yes I realize this but as I am extremely new to the scene and there is sooooo much info, it's hard to know where to begin. I don't even know what to look for really because I don't know what tools do what. It's like having all the pieces to the puzzle but unable to put them in the correct order.
ddg5060 said:
Yes I realize this but as I am extremely new to the scene and there is sooooo much info, it's hard to know where to begin. I don't even know what to look for really because I don't know what tools do what. It's like having all the pieces to the puzzle but unable to put them in the correct order.
Click to expand...
Click to collapse
Basics of flashing: http://www.youtube.com/playlist?list=PLB99FAE280F618B12
Please help?!?!
wptski said:
Basics of flashing:
Thank you. I will look at these and hopefully it will clear some things up. The problem is that my situation is unique I think. I don't know if maybe i have a broken button or the person who gave it to me really messed it up but all it does is boot into fastboot automatically, although I can get it into NVFLASH mode i don't know what these modes do. Are they both able to flash the system so I can use the device? If so do some files work in one that don't work in the other?
I tried putting the device in NVFlash mode caus I want to put the CM10.1 FW on it, am I headed in the right direction ? The only things that I can launch are "Install JB_Alpha_E.bat" and "NVFLASH.exe" running the Install_JB one opens the command prompt and it looks like it is doing something which is how it looks in the video but then suddenly after it processes some files the command prompt window just closes, am I doing something wrong ?
Click to expand...
Click to collapse
You are doing it wrong. Go read my first post in that thread very very very very very very very carefullly.
http://forum.xda-developers.com/showthread.php?t=2130081
I'll give you a hint, the line you want to pay attention to is stated right above the download links.
Failed executing command 12 NvError 0x12002
So because the cmd prompt closes so fast I cannot see the error, so I took a video and paused i played it until it froze right where the message came up.
Here is what it says if failes right after creating partitions blah blah blah
Failed executing command 12 NvError 0x12002
command failure: create failed (Bad data)
bootloader status: fatal failure to read / write to mass storage (code:9) message: nverror:0x8 (0x19000008) flags: 0
What does that even mean ? is the device broken somehow ?
Sorry
giveen said:
You are doing it wrong. Go read my first post in that thread very very very very very very very carefullly.
http://forum.xda-developers.com/showthread.php?t=2130081
I'll give you a hint, the line you want to pay attention to is stated right above the download links.
Click to expand...
Click to collapse
Sorry I seem so dense when it comes to this stuff, I really don't know android stuff that well.
I looked back and maybe I'm missing what you are saying but I already have the device in NV mode and have the drivers installed if that is what you were talking about.
Now it's just the crashing problem that i'm having. Any ideas? or am I still doing it wrong?
ddg5060 said:
Sorry I seem so dense when it comes to this stuff, I really don't know android stuff that well.
I looked back and maybe I'm missing what you are saying but I already have the device in NV mode and have the drivers installed if that is what you were talking about.
Now it's just the crashing problem that i'm having. Any ideas? or am I still doing it wrong?
Click to expand...
Click to collapse
Sorry, at the time I had posted that you were still working with fastboot.
Do you have the drivers installed and in device manager it states that it sees "nvidia recovery" ?
Hard reset with a push pin, go back into NVFLASH mode again, and run the batch file again. If it fails, you hvae to do this step every time.
giveen said:
Sorry, at the time I had posted that you were still working with fastboot.
Do you have the drivers installed and in device manager it states that it sees "nvidia recovery" ?
Hard reset with a push pin, go back into NVFLASH mode again, and run the batch file again. If it fails, you hvae to do this step every time.
Click to expand...
Click to collapse
Yes I am in NVflash mode, I have done the pin press and retried several times each time it the cmd closes and i assume it is getting that error.
i can post a picture of the freeze frame that i was able to pause it on if that helps.
ddg5060 said:
Yes I am in NVflash mode, I have done the pin press and retried several times each time it the cmd closes and i assume it is getting that error.
i can post a picture of the freeze frame that i was able to pause it on if that helps.
Click to expand...
Click to collapse
I forgot to mention that I did also install the drivers using the nvidia package like the tutorials stated. That all went fine.
Ps. Ignore the play button the the picture, it's just a screen cap of my phone paused on the frame.
ddg5060 said:
I forgot to mention that I did also install the drivers using the nvidia package like the tutorials stated. That all went fine.
Ps. Ignore the play button the the picture, it's just a screen cap of my phone paused on the frame.
Click to expand...
Click to collapse
Your SOL.
Notice it says FAIL TO READ/WRITE
You are in read-only mode.
giveen said:
Your SOL.
Notice it says FAIL TO READ/WRITE
You are in read-only mode.
Click to expand...
Click to collapse
Ok, i did notice that, other than the obvious what does that mean, is it possible to get it out of read only mode?
ddg5060 said:
Ok, i did notice that, other than the obvious what does that mean, is it possible to get it out of read only mode?
Click to expand...
Click to collapse
Only one user has claimed to have gotten out it without returning it to Dell.
wptski said:
Only one user has claimed to have gotten out it without returning it to Dell.
Click to expand...
Click to collapse
Damn, let me guess, he won't tell anyone how to do it either or show pictures of claimed revived device.
As far as dell goes, is it something that they will fix or do they consider the warranty void because of whatever was done to it to make it like that?
So sad and here I thought I was actually progressing in fixing it. Question though, how does something like that happen? Did the person flash it wrong? Or interrupt it while writing some critical process?
Actually he did tell us how to do it, it was just 1 in a million chance it works.
Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
AlkaliV2 said:
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
Click to expand...
Click to collapse
So, I've been on stock until I switched over to CM12. I do have a twrp backup but apparently only did that after I moved to CM12. I have only the most basic (read basically nonexistent) understanding of ADB, and can follow directions I find online but no real knowledge as to how anything works. I also did not use wugfresh, but unlocked via ADB and rooted via chainfire. Honestly, I followed most of the direction I found on youtube via a creator called wwjoshdo (I'd link but I'm not allowed).
Otherwise that feels like the info. I didn't fiddle with my nexus until I started have battery issues and then decided to unlock/root/flash, and that was about 6 weeks ago. I'm also running what standard apps for a rooted device on CM12, flashify, cyandelta, setcpu, and, Titanium Backup. Help?
llawhsoj said:
Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
Click to expand...
Click to collapse
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
RMarkwald said:
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
Click to expand...
Click to collapse
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
llawhsoj said:
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
Click to expand...
Click to collapse
So this link will get you up and running with ADB (if it isn't already working): http://forums.team-nocturnal.com/index.php?/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10-updated-9-11-2015/
These are the most common commands that are used with ADB once you get it installed. Also, an excellent way to pull a log from the command prompt: http://developer.android.com/tools/help/shell.html
Assuming you can see the device once you pass the command, "adb devices" it means you are connected but the MTP driver hasn't been loaded properly. I had to fix this by cycling Android debugging and ADB notification in developer's option until Windows was like, "Hey! There it is!" Also, MTP works properly for me when booted into TWRP so if you desperately need to transfer a file you can do it from the TWRP recovery menu.
Noob Tip/Reminder: Make sure that when you plug it in the first time you change it from 'Charge Only' to MTP and if things still seem quirky reboot Windows. It's all just a game of getting it recognized at this point.