Related
Hello,
My G1 stopped receiving usb notifications. each time i connect it to a computer,the battery charges but i get no notifications about the usb.which means, i cannot mount it to a computer.
I run Cyanogen mod 5.0.7 test2, but i dont think its related since its started a couple of days after i installed the new rom.
i also tried it on different computers/usb cables, seems like its device related.
Anyone has any idea?
TIA,
Roy
use fix permissions option in recovery
it works for me
or
simply restart your phone while connected to the pc
It is device related, if you have a recovery that supports usb mounting from it, I suggest go there and mount your phone if you need to get something onto your device asap. If you have time, a full wipe fixed the problem for me.
Just tried the fix_permissions with no success.
the weird thing is that even in recovery mode, when i enable usb mass storage i still dont get anything!!
i'm trying to avoid a full wipe ,and starting to feel like it's a rom issue, anyone thinks the same?
Same Problem
I too have the same issue. Incase you have any solution let us know. I did some search in google but could not find any thing.
Nandroid, wipe, reflash, and retry. Retry with a different ROM and a fresh wipe maybe. You always need to wipe and reflash when you run into errors like this. Like it or not.
However, if that doesn't work, try a few different USB cords. Maybe something happened to yours, or the one you're using doesn't support a G1. Some companies rig theirs to work with just their product.
Edit: Just noticed you tried different cables and computers... How many different cables? Have you just tried your original one and then another one? Or about 3 - 5 maybe? These are quite common cables, and anyone you know should have at least one or two.
this happened to me a few times after i flashed cyans 5.07 test2 rom and all i did was restart and the notification came back. hope that helps.
Happens to me too with T1-T3. I can just reboot with the cable installed and it will mount once the phone is up.
pkrattu said:
this happened to me a few times after i flashed cyans 5.07 test2 rom and all i did was restart and the notification came back. hope that helps.
Click to expand...
Click to collapse
Same thing. This actually happened to me today and a restart brought it back.
I have the same issue
and everyday I have to reboot the phone while connected to the usb cord
to have the phone recognized.
alternative: try using dual mount sd widget out on the market. It lets you mount your SD card and still use the apps on the phone.
Is there a way to flash one of the Cynaogen or other mods without installing the android SDK? I am not extremely technically inclined when it comes to this stuff and I am not sure I understand how to do it.
Any help would be greatly appreciated.
Thanks
yes, most people install cyanogen rom on their phone without even touching a computer
So informative ...really
Well I attempted the SDK install and when I run ADB I dont get a list of devices. When I plug in the phone windows automatically installs drivers.
So I downloaded USBDeview uninstalled and plugged the phone back in, same drivers installed.
So where to from here?
Ok so followed all the instructions on Cyanogens page and ADB will not see my device, when I go to Start > Devices the Nexus One shows up and says Driver not installed.
I downloaded the drivers from the SDK and no luck, I added the path to environamental variables, tried again, no luck
Tried to force the driver install and manually install through windows and states the driver I am trying to install doesnt contain info about my device. Check to make sure its an x64 driver.
Running windows 7 ultimate. any ideas what could fix this?
Ok so added and renamed the proper files to recovery.img and added cynaogens mod and renamed to update.zip
Rebooted phone
Recovery Mode
Wiped
Install from SDcard update.zip
Installation failed
Where am I going wrong?
Download ROM Manager from the market and you can do it from there. I think you need the pay version too do nightlies, but the stable CM releases are available in the free version.
Sent from my Nexus One using XDA App
1) Can I assume you are rooted?
2) Can I assume you downloaded the adb drivers from Google?
If so I don't know how to help you without telling you to download clockwork mod sorry.
This is what I did.
Downloaded and installed 1 click root from here http://forum.xda-developers.com/showthread.php?t=747598
Downloaded Cyanogen Rom and gapps from here http://forum.xda-developers.com/showthread.php?t=722798 and saved them to my SD card.
Downloaded Rom Manger from the Market.
Ran 1 click root
Ran Rom manager, installed the clockwork recovery from rom manager.
selected install zip from sd, found zip of cyanogen and selected it.
Pressed perform back and perform wipe then press OK.
Rom Manager did its magic and installed cyanogen for me.
The phone rebooted, I opened up rom manger again and pressed install from sd card again
Found and clicked on gapps zip file. This time I didn't perform a backup or wipe(not sure if I was supposed to or not), Hit ok, then ok to reboot.
Rom Manager worked its magic again and voila I had/have Cyanongen rom with my Google apps.
I did this all last night and from memory, but I'm fairly sure those are steps I took. However if it breaks your phone its your own fault
jcohenlv said:
Ok so added and renamed the proper files to recovery.img and added cynaogens mod and renamed to update.zip
Rebooted phone
Recovery Mode
Wiped
Install from SDcard update.zip
Installation failed
Where am I going wrong?
Click to expand...
Click to collapse
Ur phone is not rooted. Period
jcohenlv said:
So informative ...really
Well I attempted the SDK install and when I run ADB I dont get a list of devices. When I plug in the phone windows automatically installs drivers.
So I downloaded USBDeview uninstalled and plugged the phone back in, same drivers installed.
So where to from here?
Click to expand...
Click to collapse
It will pop up and says that it cant find the driver for ur phone. Go on and manually apply the driver urself then u are set.
Not sure if this will help, but check USB debugging and the one below it in phone settings/applications/development.
Ken
Phone is rooted, used 1 click root.
When I try and manually install the driver Win7 tells me the drivers I try and load do not contain information about my hardware.
Ill try Average Canadians method and see how it goes.
Thanks
Ok so I attempted this as mentioned,
Now my phone is stuck at a looping "Cynaogen Mod" screen after doing the backup from Rom Manager.
Steps Taken to This Point:
D/L One Click Root - Unrooted Phone
Ran One Click Root Again - Rooted Phone
Downloaded Clockwork Rom Manager
Set Permissions For Super User
Downloaded Cyanogen 6 RC3 + GApps
Ran backup - phone rebooted
Phone rebooted and ran a bunch of stuff got to Cyanogen (mod) loading screen (looks like a boot animation) and this is where its stuck looping.
Any Ideas?
The animation is an android on a skateboard with a blue arrow circling it and has what I will call "lightning" circling around the outside. The lightning gets about 3/4 of the way around the circle then the screen goes black and starts over.... just wanted to give a bit more information.
Any help would be appreciated
Thanks
OK booted into recovery, got a green screen instead of the typical blue which I am assuming is a good sign
Ran "install from sd card"
Navigated for a few minutes till i found the Cyanogen zip file (update-cm-6.0.0-N1-RC3-signed.zip)
Installed
Phone rebooted
Got to Cyanogen Mod loading screen phone rebooted again and its stuck in the loop again......
Any ideas?
Ok attempted to flash back to stock FroYo 2.2 and getting:
asster failed: file_getprop("/system/build.prop. "ro.build.fingerprint") == google/passion/passion/mahimahi:2.1-update1/ERE27/24187:user/release-keys" ||
file_getprop("/system/build.prop. "ro.build.fingerprint") == google/passion/passion/mahimahi:2.2-update1/FRF50/38042:user/release-keys" || file
E:error in sdcard/update.zip
(Status 7)
Installation aborted.
I am assuming I am getting this cause the update is for FR50 and not FR91?
Ok so another update
Attempted to flash 2.1.1_Downgrade and still getting same error as above just with a different file name version.
At this point I will just wait for one of you to get back to me hopefully
Ok so .. trial and error is a great way to learn
If I would have opened my eyes the first time I would have seen the "nandroid" option and just restored my backup
So after a minor freak out, and a cigarette I have regained my composure and I am in the process of a restore. Lets see what happens
Ok so phone is back to where it was when I did the backup.....
Going to attempt this again and try it with what I think was the missed step THE WIPE!
Uh oh..... got the blue screen instead of the green screen before phone wiped .... hmm guessing that when i did the restore it re-flashed the original recovery mode. So looks like I am starting over with a fresh phone ....lol
(hope this commentary isnt too annoying, but they way I see it is one day it may help another noob like myself do this on his phone )
WOOT WOOT!
So there it is! CM 6 RC3
I want to thank everyone who offered advice in this thread and to that crazy Canadian who offered a great option to get this done!
I'm stuck at the grey N screen and I can't get out. I just got my NC today, updated to 1.0.1, used the latest Autonooter, followed the instructions to a T, everything worked great.
I left the SD Card in (didn't know you were supposed to take it out and reformat it, none of the instructions were specific about that). I was playing with the unit, everything was working great and decided to reboot it because I saw there was a custom animation and I wanted to see it (didn't remember seeing it the first time around). Now the thing won't reboot. It just gets stuck at the grey N screen. I've tried the power + home method and done the factory resets 3 times but when it resets it still hangs on the N-screen and won't boot.
I'm at a loss here. Some one please help.
jbright44 said:
I'm stuck at the grey N screen and I can't get out. I just got my NC today, updated to 1.0.1, used the latest Autonooter, followed the instructions to a T, everything worked great.
I left the SD Card in (didn't know you were supposed to take it out and reformat it, none of the instructions were specific about that). I was playing with the unit, everything was working great and decided to reboot it because I saw there was a custom animation and I wanted to see it (didn't remember seeing it the first time around). Now the thing won't reboot. It just gets stuck at the grey N screen. I've tried the power + home method and done the factory resets 3 times but when it resets it still hangs on the N-screen and won't boot.
I'm at a loss here. Some one please help.
Click to expand...
Click to collapse
Did you try taking the SD out and then booting? It'll keep trying to boot from it as long as nooter is on there.
wvcachi said:
Did you try taking the SD out and then booting? It'll keep trying to boot from it as long as nooter is on there.
Click to expand...
Click to collapse
Yes I did. It's doing all of this with the SD card out.
jbright44 said:
Yes I did. It's doing all of this with the SD card out.
Click to expand...
Click to collapse
I'd say interrupt the boot 8x (powering down will do) to initiate system restore, then re-root.
wvcachi said:
I'd say interrupt the boot 8x (powering down will do) to initiate system restore, then re-root.
Click to expand...
Click to collapse
Edit. That fixed it. Thanks. Man do I feel stupid. I thought the 8x reset and the 3 button method were the same. Apparently not. I'll try this again a little smarter hopefully this time.
Thank you for this thread. I thought I just bricked my 2 hour old nook. I stupidly restarted it after root with the nooter card still plugged in. Then I couldn't figure out why it was taking so long for the screen to turn on, so I kept pressing the button and then holding it. Then I realized the card was still in. Took the card out and tried to boot it, but it hung at the 'n' screen. The 8 interrupted boot method saved me from my stupidity though. Thanks.
Same here - left the card in...
8x reset and then a home and power reset cleared me up. Then update back to 1.1 and autonooter 3 again.
Loving it ever since.
hey
im having the same problem i did the factory reset to and nothing
wats the 3 count and wat else can i do
So what to do when factory restores and stock installs fail?!
OK... reviving this thread since it's my exact problem but I've been unable to find resolution. I've been searching everywhere for what to do next but nothing seems to be working.
I'm helping my buddy get his nook working. He said he was updating to 1.4 and when he rebooted it, it froze on the n screen. He plugged it back into his Win 7 machine to try the update again and it wouldn't mount as a USB device.
After a bunch of reading and fiddling, he built an SD card with ClockworkMod and installed in on an SD card. Or so he thought... he hadn't made it bootable. Over the phone, I walked him through restoring the image to his card and then it booted.
CWM comes back with a pile of errors. Specifically,
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When trying to format /data and /system, we also get errors.
We've downloaded various factory restore zips and tried installing them but they install (successfully according to CWM) and we reboot only to get stuck at the dreaded n screen again. We've done the 8 boot interrupt restore and get and error to call support (nobody answers this week) and done the regular power/+/n restore and it completes but leaves us again on the n screen.
Can anyone tell me the significance of these errors in CWM? It's the only thing different from all the tutorials and video walkthroughs we've followed and although we've seen these errors in other posts, there's never been a good explanation of them and how to resolve them if necessary.
Also, what is the latest version of CWM for the Nook Color and where do I find it? Is there an official site for CWM? Seems like people are just linking to older versions and sources all over the place with no common "go to the CWM site and get latest build of CWM." The latest I've found is 3.2.0.1 in a post back in August 2011.
Thanks in advance! Hoping this gets us over this hump and helps anyone else in the in the same situation.
moose
Solved it...
I've managed to solve the problem I outlined above. I'm not at home right now, so I'll post the specifics once I can get back and post the links and images I used to get this working.
Note that I had no concern for the data/books/apps that were on the device originally. I just wanted it working again with stock 1.4.1.
Basically, I noticed that after restoring to 1.1, the initial screen said "welcome to the future of reading" and then when I updated to 1.2, it said "read forever" so I knew the updates were at least doing something. I now needed to get rid of the errors in CWM 3.2.0.1 so started looking for something to blow away corrupt (?) partitions.
I found a post that had two zip files and it said they repartitioned the nook entirely. I hoped they would blow away my corrupted partitions by rewriting the partition table. I ran one, and it forced me to reboot. Then I ran the second and rebooted. It loaded up, got to the n screen and paused just long enough for me to lose some hope and then flipped over to the nook color boot animation. Yah! Progress!
Tried to register the device using my own bn.com account but wasn't successful. Turns out that you need to either use the original registered account on bn.com or unregistered the nook from his account, but since the error shared the same wording as previous failed factory restores (but this time in the nook registration interface), I assumed it was something locally. I came across a post in the searching that mentioned the need to unregister the nook from the original account to register it on another.
While trying to figure out what to do, I found a 1.4.1 signed stock image that also reconfigured the restore on the device and worked through CWM "install zip from SD" rather than using bn.com update zip via usb (i was still having trouble accessing the nook via usb at this point).
I downloaded the stock cwm 1.4.1 zip and installed it through cwm 3.2.0.1. It booted and then I saw the intro video on the nook registration page had a different woman. I got my buddy to send me the email and password he registered the nook with and the registration process was successful. I now have a working stock 1.4.1 nook color to return to my buddy.
I'll post the actual links to the posts/images that I used once I get home.
Hope this helps others!
I'm also getting the E: Can't mount / errors.
Will try this when I get home.
Also i'm just realizing now that i am using an older CWR v3.0.0.5, so that might be my issue also.
links
Mooseroo Could you please post links used to fix this issue
Try using this version of CWR. Just remember you can always choose a recovery image smaller than or the same as your SD card but not larger.
http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/
this is not working. same issue with nook 1.4.1 and CM7...hangs at "N" or goes black with CM7
Have you check the MD5 of all your files to make sure you have good downloads? It is frequently a skipped step but one of the easiest and first things you need to check.
Mooseroo - where are you?
mooseroo said:
I've managed to solve the problem I outlined above. I'm not at home right now, so I'll post the specifics once I can get back and post the links and images I used to get this working.
Note that I had no concern for the data/books/apps that were on the device originally. I just wanted it working again with stock 1.4.1.
Basically, I noticed that after restoring to 1.1, the initial screen said "welcome to the future of reading" and then when I updated to 1.2, it said "read forever" so I knew the updates were at least doing something. I now needed to get rid of the errors in CWM 3.2.0.1 so started looking for something to blow away corrupt (?) partitions.
I found a post that had two zip files and it said they repartitioned the nook entirely. I hoped they would blow away my corrupted partitions by rewriting the partition table. I ran one, and it forced me to reboot. Then I ran the second and rebooted. It loaded up, got to the n screen and paused just long enough for me to lose some hope and then flipped over to the nook color boot animation. Yah! Progress!
Tried to register the device using my own bn.com account but wasn't successful. Turns out that you need to either use the original registered account on bn.com or unregistered the nook from his account, but since the error shared the same wording as previous failed factory restores (but this time in the nook registration interface), I assumed it was something locally. I came across a post in the searching that mentioned the need to unregister the nook from the original account to register it on another.
While trying to figure out what to do, I found a 1.4.1 signed stock image that also reconfigured the restore on the device and worked through CWM "install zip from SD" rather than using bn.com update zip via usb (i was still having trouble accessing the nook via usb at this point).
I downloaded the stock cwm 1.4.1 zip and installed it through cwm 3.2.0.1. It booted and then I saw the intro video on the nook registration page had a different woman. I got my buddy to send me the email and password he registered the nook with and the registration process was successful. I now have a working stock 1.4.1 nook color to return to my buddy.
I'll post the actual links to the posts/images that I used once I get home.
Hope this helps others!
Click to expand...
Click to collapse
Just found this thread and I have the same issue - can you post the links you reference? Please?
tmccully said:
Just found this thread and I have the same issue - can you post the links you reference? Please?
Click to expand...
Click to collapse
I think he's talking about my files in this post.
Hiya!
Been on the forums for years modding my Nexus One and would like to thank everyone for their humongous contribution! 3 years of constant upgrading and improving of what turned out to be the best phone ever!
Now, I've come to an end where my self-confidence took over caution and preparation and i think i've made a boo-boo.
Long story short, i have a unlocked Nexus One that has been running a CM10 ROM with Blackrose for a good 6 months. Most of the functions were working fine, except for a few glitches, but last night i decided to go back to the roots, and install a stock Gingerbread ROM. I found a unrooted GB ROM, and went straight on to renaming it to PASSIMG, throwing it on card and rebooting. Now that's where the funny things started:
First, all goes well, click Volume Up, get it started, and than a screen with all OKs except for [7] BOOTLOADER - Fail-PU and a message saying 'Only Blackrose can be flashed'
Next, I get 7 OKs, except for BOOTLOADER, and the following: Partition update fail! Update fail! Do you want to reboot? Y/N
Figuring i forgot to uninstall Blackrose and need to do so, i let it restart, it comes up with a clean un-rooted GB ROM, and here's where my troubles start.
1. USB Connection: Plug it in, laptop doesn't recognize it at all. Classifies it as 'Unknown Device' and that's it. Tried fresh drivers, Universal Naked Drivers, SDK drivers, ASUS tablet drivers, nothing. Tried 3 cables, the HTC one, a Blackberry one and a Samsung one. Nothing. Uninstalled all USB hubs/devices, restarted the laptop multiple times. Debugging ON/OFF, no difference. I'm at a loss here, no clue what else to try!
2. Fine, i thought, let's flash a rooted rom! PASSIMG on the card, phone finds it, gets to the line 'Parsing... Passimg.zip' and goes back to the neutral screen. Tried it multiple times, different ROMs, nothing.
3. At this point, figured maybe an earlier ROM will cause an OTA update and fix things up. FROYO PASSIMG on the card, flashed 'succesfully', just like in #1, reboot to clean un-rooted FROYO. Checked USB connection, same again. OTA Update - constantly failed.
Been reading through Wikis and Q&A's here all day today, everything seems to be so easy to fix as long as you get a live ADB connection, and i know i could fix it, but i just can't get the laptop to recognize the bloody phone! Do not have access to another computer just now, so can't check whether it's just my Vaio.
So now, the questions:
1. Any other ideas on the USB issue? The phone does not display the usual 'choose your option/mass storage...' when connected, and nowhere in the menu is there an option for that.
2. When booting into recovery, i get the green droid with the white triangle and the !, and then get into the 3e recovery that has an 'update.zip' option. can i install a custom recovery without the phone being rooted? just of the sdcard? is there an update.zip that can re-stock my HBOOT?
any other ideas will be greatly appreciated, as of right now i am stuck with a FROYO handset that is perfectly capable of running JB, and it's really frustrating!
thanks in advance for all your help, cheers!
Ok so long story short: I installed Cyanogenmod onto my HTC One using their installer, used it for a month or so and decided to flash it back to stock, but not before flashing a Google Play Edition rom (Android Revolution's). The rom got me stuck in a bootloop which i've read should be pretty easy to get out of, however my computer won't recognize my phone. I've also done something while trying to clear caches and what not that says the phone isn't rooted. I've tried to re-root it but since i can't drop the file into my sd file (can't see my phone on my computer) i can't do that either. Whenever i do try to reboot out of bootloader i get stuck at the HTC loading screen. I can get the red FASTBOOT USB and my comp dings when i plug in, but i can't see my phone. I've tried re-downloading drivers. Device manager sees my phone, but i can't access my sd card. I also can't get abd push to work either.
I'm pretty damn new to all this...probably started playing around prematurely. I've read quite a few tutorials so i'm not completely dense as to how all this works, but pretty close to it. If i could just get my computer to see my device, get the root and a new rom file on my sd, i'm pretty sure i could figure the rest out. Also, my apologies if this has been answered before; I did some digging an didn't see anything that helped my issue. Any help would be appreciated.
Also...i should probably mention that i was playing around with the format /system etc commands in CMW recovery...and it's likely i may have rebooted at some point afterwards....so i'm pretty sure that is what is causing the HTC screen issue, but I still feel my main issue here is the inability to get any zip files or anything for that matter onto my sd.
Once again...any help here would be greatly appreciated. Thanks