Database Develop

SD Card Unmounting-CM-4.1.11.1 :)

I installed Win 7 Ultimate version on my system, these past couple of days.
I am having an issues mounting my G1.
It mounts for like 15 seconds and unmounts itself.
I have the 1.6 drivers, installed.
ADB works fine.
Is there a special trick to getting this mounted with Win7.
I didn't have issues with XP.
Thanks for an help

Mikey1022 said:
I installed Win 7 Ultimate version on my system, these past couple of days.
I am having an issues mounting my G1.
It mounts for like 15 seconds and unmounts itself.
I have the 1.6 drivers, installed.
ADB works fine.
Is there a special trick to getting this mounted with Win7.
I didn't have issues with XP.
Thanks for an help
Click to expand...
Click to collapse
im using Win 7 Prof and I keep getting an message that tells me that I could have errors so to scan it but I just choose to continue without scanning and it mounts alright, so no special trick here sorry

I have the same problem on windows 7.
when it does it leave the phone plugged in.
safely remove hardware from within windows.
unplug the phone
plug it back in
wait 20 secs
mount

I get that error message as well.
Edit: Off-Topic.......
What's with win7 wanting to back up everytime i plug in my phone???
Anyone getting that as well?

For the error make sure the partition table of the card is "msdos"
You can check by going to recovery console and typing the following
Code:
parted /dev/block/mmcblk0 print
No idea about win7 wanting to backup

Fingerlickin said:
For the error make sure the partition table of the card is "msdos"
You can check by going to recovery console and typing the following
Code:
parted /dev/block/mmcblk0 print
No idea about win7 wanting to backup
Click to expand...
Click to collapse
yea my partition table is msdos ... dont know why i get that error :\

I just got word from a fellow XDA member:
yea google probably wont make win 7 drivers until win 7 is officially released
Click to expand...
Click to collapse

Yea. No official windows 7 drivers so you should expect problems

alritewhadeva said:
Yea. No official windows 7 drivers so you should expect problems
Click to expand...
Click to collapse
Deja Vue

Well you can backup everything and repartition the card.
Post 3 HERE has a script that will help. Follow instructions in the post and do options 9, 1, backup to pc, 11, 10 in that order. You won't loose your apps but you will loose your dalvik-cache so the first boot will take up to 15 mins. If you don't already have your card partitioned then you can just do 1, backup to pc, 11.

I guess i'll be using aFile more often till they push the drivers out.

Windows 7 Refuses To Recognize My G1 When In Recovery :(

OK so I felt like resetting my phone and reflashing CM 4.2.15.1 so I wiped my phone completely and reformatted my SD card. When I booted into Cyan's Recovery my phone wasn't recognized. So I was like no big deal let me just go into device manager and install everything related to my G1 and reconnect my device. Did that and still nothing. I tried booting into fastboot and it recognized it so I thought maybe if I flashed Amon-RA's recovery it might fix it. After that I tried going back to recovery and still nothing. Luckily I had a microSD adapter to put the ROM on my SD and so I flashed it and booted up my phone. All the drivers including adb installed fine but once I tried going to recovery to reformat my SD(I forgot to add ext partitions the first time around ) but once I got to recovery Windows told me I had an unknown device plugged in. I tried plugging it into all my other ports but no change. Can anyone help me out?

Sure, your problem is:
Windows
Click to expand...
Click to collapse
Eliminate that and you'll be good to go.

lbcoder said:
Sure, your problem is:
Eliminate that and you'll be good to go.
Click to expand...
Click to collapse
.....................................................................
HAHAHHAHAHAHAHHAHEHHEHEHEHEHEHHAHAHAHAHAHAHAHAHHAHAHAHHA

lbcoder said:
Sure, your problem is:
Eliminate that and you'll be good to go.
Click to expand...
Click to collapse
Lol. Very true.
Anyways, while in Recovery can you open up Command Prompt and run adb shell? or any kind of adb command? (Don't think cyanogen's recovery has adb access, but I could be wrong.) Windows 7 always told me my phone was an unrecognized device, but it still let me use adb and mount it to transfer files.
Oh, did you delete the drivers under device manager? If you delete all the ones (Might be just one. I think it is. ) your phone uses, Windows will automatically reinstall it as a USB Mass Storage.

How to FORCE stop phone from showing up as USB drives in Recovery, still no root :(

Okay I don't know if this will help anyone, but I figured out how to stop Windows from detecting the phone as two USB drives when the phone goes into Recovery mode, and to make it show up as Android Composite ADB device.
I do NOT have HTC installed, rather, I'm using the USB 3 drivers that come down through the SDK, so I'm not sure how to do this if you are using the HTC Sync drivers intead.
At any rate, start with the phone off and disconnected. Open the Device Manager. Boot with your prefered method into Recovery mode, then connect the phone. It should detect as USB Mass Storage Device under Universal Serial Bus Controllers. Right click on USB Mass Storage Device and click Uninstall and then OK. Once this is done, disconnect the phone (you can leave it running in Recovery).
Open My Computer and navigate to C:\Windows\inf. Copy the files usbstor.inf and usbstor.pnf to your desktop or wherever, it doesn't matter, just make sure you put them somewhere you can get them later. Then delete them from the C:\Windows\inf folder. These are the drivers that Windows automatically uses for USB storage devices.
Ok, now bring Device Manager back to the foreground and plug the phone back in in Recovery. It should show up as Android Phone with an exclamation mark. If Device Wizard pops up cancel out of it. Now right click on the Android Phone and click update driver. Click Browse my computer for driver software. Click Let me pick from a list... Click Android Phone and Next. Click Have Disk. Browse to your SDK folder into the USB Drivers folder and you should see android_winusb.inf, select that then click OK. You should now have a list of three items to select, this part I am not sure if there is a 'right' or a 'wrong' but I go with Android Composite ADB Interface.
Select that or whichever one you think and this is what it will install as. Bingo, now whenever you connect the phone into Recovery or boot into Recovery with it already connect it correctly detects as the Composite ADB Interface or whichever you selected, but does NOT show up as any USB drives.
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
At any rate, to get everything back to normal as far as your computer being able to use USB storage devices just copy those two files back to the inf folder before you connect them and you should be fine.

bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
.
Click to expand...
Click to collapse
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.

Or you could try what I've done 7 times and achieved ADB Shell 7 times...
1. Turn the phone off.
2. Start running Loop.bat
3. Unplug USB cable.
4. Turn device on in Fastboot by holding in the optical joystick and power.
5. Plug USB in.
6. Hit power button once to get to HBOOT.
7. Wait two seconds for it to do it's thing.
8. Pull off the back of the phone.
9. Hit Vol - to Recovery then hit power.
10. Immediately after doing this continuously push the sd card in and out (about every .5 - .75 seconds)
11. ?????
12. Profit

@DigitalDementia--
How is what you said relevant in this thread?

bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
Click to expand...
Click to collapse
drtrmiller said:
@DigitalDementia--
How is what you said relevant in this thread?
Click to expand...
Click to collapse
Pretty positive it had everything to do with that section of the first post, he said he still couldn't achieve root I attempted to help him. Why don't you explain to me exactly what it doesn't have to do with this thread?

rynosaur said:
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Click to expand...
Click to collapse
The real bummer here - and I should have known better, really - is that this wipes your phone.
I suppose it should be obvious, but take it from someone who's pretty new to Android phones and just wiped their entire phone after following your steps: Please add a warning to your original post.
It's late, I'm tired and irritated, but I'm sort of bummed to know I went from hero to zero in trying to enter shell (again) during recovery all in an effort to get proper perm. root. Sort of ****ty to know that I just lost everything.

still no root
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App

USB drives are ok in recovery
When I am in recovery with adb and working correctly it still shows the 2 USB drives so this is normal and ok, what you have done is fool yourself into thinking that your phone is in correct mode but it really is not, this is why it still does not work, sorry.

rynosaur said:
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Now that I've scorched the earth, I'm hitting this thing hard with every trick I can think of to get the shell in recovery again.
Thankfully, I at least have my app list on appbrain.

After researching around the different forums, I think this maybe my issue. I will have to make this attempt when I get home.
This is what I posted on a different forum. I am not sure if this is a similar experience you were having:
So, for a little a bit I was having issues with finding and modding the usb.inf file. I got that finally resolved... Now as I go to one of the first parts of the procedure, executing the adb shell command. Well at first it said the 2 lines, about the daemon and whatever the second line was. Anyways, the third line did not say "no device found" it went straight to a shell prompt "$" . The instructions made a point in the instructions for it to say " no device found" .
I went ahead with the rest of the instructions. No Luck. And I did both methods. A co-worker of mine told to run adb devices to see if my phone is recognized. I will also make that attempt tonight.
I wanted to know if any of you had some insight. I made sure I was in the right directory.
I will make another attempt on a different machine tonight.
Thanks. Oh yeah, I do have some UNIX experience if that makes a difference.

I had the same problem, used this method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!

kentoe said:
I had the same problem, used this method here
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
Click to expand...
Click to collapse
I rooted in Windows, rather than linux, simply because I like the look of MejDam's procedure better than the linux script posted here on XDA--and his windows procedure is accompanied by his YouTube video
Long story short: I had ADB Composite Device AND the two storage volumes mounted together, as I got shell, and did the other steps in recovery. NB: they were mounted as Generic Storage Volumes, not writeable partitions. The stock recovery on DI does not allow host to mount either partions, although I'd like to see if
Code:
mount /dev/block/mmcblk0p1
worked for the SDcard on the sdcard, cuz then it would be a cinch to mount sdcard/emnc partition into host OS--windows, linux, Atari 2600, etc Worth a try.
Anyhow, my conclusion: a bad driver setup could be a barrier to catching adb shell, but it is certain not the prevailing problem for most, IMHO.

Was wondering if bast525(the creator of the thread) was ever able to adb shell while in recovery, and if so what did you do thanks.

Heh, I wish.... I've tried just about every method posted on these forums, and five different SD cards from Sandisk, PNY, and Kingston. The only thing I haven't tried is rolling back to the pre OTA update, because I don't want to wipe the phone at this point.

Finally flashed android after running on sd for over a year, a few issues

Like I said, I finally decided to take the plunge after running it exclusively on my sd for over a year, and now usb connectivity isn't working. Before all I had to do was install sd split widget, hit it and wait for aboug,t 20 minutes the first time, then each one after that was only about 1 minute.
Anyway, I flashed to scooter's cyanogen, but I was having issues with the lcd density(I use 320x480 for swype, and he didn't include roguetools, and I have no data and I couldn't connect to my computer to transfer it over, so I could not use it), so I flashed to super froyo rls16. I had been using it on SD so I was familiar with it. I installed it fine, used Titanium to restore all my apps and stuff, but when I went to hook it up to my computer to transfer some apps, I couldn't get it to connect. I have left it in split activated mode for 2+ hours and still nothing.
Some things to note
In both scooter's and superfroyo, I get a message from windows saying if you use a 2.0 usb port then it can perform faster.
I have tried the built in share files functionality in superfroyo and it just sits there for as long as I let it
I've tried different USB ports
I've tried uninstalling windows drives and reinstalling
I'm using windows 7 x64
Like I said, while running on SD, I had no issues with this stuff at all.
Its not urgent, thanks to titanium, I got all my apps and data back the way they were, but since I have no data and MMS doesn't work for verizon/android/vogue, now I have no way of transferring files or pictures on this phone.
Thanks for reading this all and a special thanks to all the devs who got me to this point.

http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel-release.git;a=tree
Download the latest 2.6.25 kernel from there - 10/31/10
Works fine on USB 2.0 mode for my Touch

Same thing happened to me. My theory is that Windows looked for a driver and it installed one that won't let you use your phone as a mass storage device. Try using a different computer and see if it has the same affect.
And the 2.6.25 kernel is not compatible with Scooters Cyanogen Mod.

mikurej95 said:
Same thing happened to me. My theory is that Windows looked for a driver and it installed one that won't let you use your phone as a mass storage device. Try using a different computer and see if it has the same affect.
And the 2.6.25 kernel is not compatible with Scooters Cyanogen Mod.
Click to expand...
Click to collapse
I had the same problems with both kernels (.25 or .32).
I use the Dual Mount SD widget.
Did you install the ADB drivers?

waterpolo said:
I had the same problems with both kernels (.25 or .32).
I use the Dual Mount SD widget.
Did you install the ADB drivers?
Click to expand...
Click to collapse
Yea I installed the ADB Drivers. Thing is Ubuntu and Mac OS X detect it fine with no problems and instantly at that. Silly Windows trying to find drivers.
But it also didn't work on my brothers netbook with XP and it didn't have the ADB drivers

I'm using the latest .32 kernal.
And I'm using ADB drivers with the dual mount widget.

[Q] Is there a way of installing a ROM to SD without the need to use the EMMC

Hey all,
I managed to brick my Nook HD+ a few month ago (see previous threads). The EMMC partitions are broken and I cant access them.
So, I noticed a few ROMS that work of a SD Card. The only problem is, the installation seems to need to store the ROM on the internal EMMC in order to install it.
Is there a way round this?
Cheers

There is an emmc-less Rom you can find the link from the following thread.
http://forum.xda-developers.com/showthread.php?t=2544606
Direct link
http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67

Thanks for the reply.
I'm struggling with the adb push part and adb just wont work, ive tried
http://forum.xda-developers.com/showthread.php?t=2336088
http://rhuno.com/flashblog/2013/03/17/getting-the-nook-hd-recognized-by-adb/
the driver installs successfully and i still cant see my nook via adb. Is there anything i could be missing.

smurfster said:
Thanks for the reply.
I'm struggling with the adb push part and adb just wont work, ive tried
http://forum.xda-developers.com/showthread.php?t=2336088
http://rhuno.com/flashblog/2013/03/17/getting-the-nook-hd-recognized-by-adb/
the driver installs successfully and i still cant see my nook via adb. Is there anything i could be missing.
Click to expand...
Click to collapse
What OS are you running? I had no issues once I did step 7 myself on Windows. On Linux it really depends on the distro and I don't use a Mac so not sure.

smurfster said:
Thanks for the reply.
Click to expand...
Click to collapse
You should really hit the Thanks Button for him instead of just saying thanks

jpisini said:
What OS are you running? I had no issues once I did step 7 myself on Windows. On Linux it really depends on the distro and I don't use a Mac so not sure.
Click to expand...
Click to collapse
tried a different computer and still no luck. I use windows 7 pro
someone mentioned I need the google usb driver. But how do I install it? it wont install via the right click > install option

Maybe try https://nookdeveloper.zendesk.com/entries/21943338-nook-developer-start-up-guide#top

Well I'm stuck nothing seems to work

Just a quick note.
Be sure to use v1.0.31 of adb or greater, or it will not see your device.
Also, in my bootimg_tools_ovation are the files necessary to get adb working in linux.
(the "hidden" .android folder gets copied to home, and the rules file to /etc/udev).
Someone really should make a live linux usb/flash image with working adb for the nook. (Just boot from usb key and have working adb)
Wouldn't be that difficult.