Just finished the 3.1 update. Here's a few notes.
Update appears to freeze at some points but finishes eventually. don't worry
update does not remove root! yay!
resizing widgets is cool
still no quick controls in browser =[
samsung camera app is updated slightly. seems the same but a couple of the icons a little bit different
seems more responsive overall
scrollable list of recent app is awesome
installed apps now have a "open" icon in the market instead of just saying "free"
wifi icon is a bit different in the system bar
added ability to set different image for lock screen
there's a new usb debugging image. it's an android bee. pretty cool
the samsung app store("Samsung Apps") and music hub are gone.
is it just me or is the browser much better now?
"talkback" keyboard now available
home key now takes you to the most recently used home screen rather than the middle one
did I miss anything else?
Can you still boot into fastboot?
smaskell said:
Just finished the 3.1 update. Here's a few notes.
Update appears to freeze at some points but finishes eventually. don't worry
update does not remove root! yay!
resizing widgets is cool
still no quick controls in browser =[
samsung camera app is updated slightly. seems the same but a couple of the icons a little bit different
seems more responsive overall
scrollable list of recent app is awesome
installed apps now have a "open" icon in the market instead of just saying "free"
wifi icon is a bit different in the system bar
did I miss anything else?
Click to expand...
Click to collapse
my lockscreen now has a different image. it used to just show my wallpaper. is anyone else experiencing this or did mine just get screwed up?
never mind this. this is on purpose. updating original post.
Did the update add google books? It is still listed as incompatible with my device (IO GT 10.1) on the market.android.com website.
camblue said:
Can you still boot into fastboot?
Click to expand...
Click to collapse
I've never tried to reboot into fastboot. why would I need to? the bootloader comes unlocked...
just tried it now and it did not work.
@tau_
I can't comment on this. Google books is not available in Canada anyway so I can't say whether the update made any difference. I just installed it myself with adb.
in case you didn't see the update to my original post, "adb reboot recovery" no longer works. I am highly unimpressed
edit: "adb reboot recovery" doesn't work but "reboot recovery" while in adb shell still works. thank god..
tau_ said:
Did the update add google books? It is still listed as incompatible with my device (IO GT 10.1) on the market.android.com website.
Click to expand...
Click to collapse
I now have Google Books 3.0.1-117394 on the system.
How is the quality of the images in the gallery. 3.0 did a poor job of displaying the initial image. And would improve drastically when you zoomed in a little. has this been fixed?
And setting wallpapers any better then 3.0? Images were cropped terribly with 3.0 when set as wallpaper.
All The I/o wallpapers are gone
"reboot fastboot" doesn't do anything. did it before?
"reboot bootloader" works but I was not able to do anything from there. neither adb nor fastboot recognized the device.
I never really noticed any problems with image quality before so I don't know what to say about that.
the wallpapers are the same. this is not a bug. they did it on purpose. it does that so that the moving up effect looks cool when you open the app drawer.
and falconeight is right. i/o wallpapers gone =[. they should be in the system image I posted somewhere, right?
falconeight said:
All The I/o wallpapers are gone
Click to expand...
Click to collapse
I had one and lost it. That is a shame.
Well considering that fastboot was the only way to load cw recovery it is pretty important. Odin is a pin in the butt to flash in.
smaskell said:
I've never tried to reboot into fastboot. why would I need to? the bootloader comes unlocked...
just tried it now and it did not work.
@tau_
I can't comment on this. Google books is not available in Canada anyway so I can't say whether the update made any difference. I just installed it myself with adb.
Click to expand...
Click to collapse
Can one of you guys pull the 3.1 update and post it? It may be usable for us to root the retail versions.
camblue said:
Well considering that fastboot was the only way to load cw recovery it is pretty important. Odin is a pin in the butt to flash in.
Click to expand...
Click to collapse
good point. I wasn't thinking about that. I never bothered to install clockwork before so I never had to use fastboot(on the galaxy tab. obviously, I have on all my other devices). Anyway, couldn't someone make a clockwork image that we could flash via recovery? or could we not use rom manager to flash the recovery?
cosimoss said:
I had one and lost it. That is a shame.
Click to expand...
Click to collapse
let me know what folder they are in and i'll pull them and post them
thepro8 said:
let me know what folder they are in and i'll pull them and post them
Click to expand...
Click to collapse
already done.
http://forum.xda-developers.com/showthread.php?p=14580792#post14580792
they're not in a folder though. they're part of the launcher apk
Google books is there
falconeight said:
All The I/o wallpapers are gone
Click to expand...
Click to collapse
I found someone else uploaded them here:
http://forum.xda-developers.com/showthread.php?t=987277
thepro8 said:
let me know what folder they are in and i'll pull them and post them
Click to expand...
Click to collapse
Cheers already got them from this thread.
Thats the only thing holding me up,,,well other than it not updating due to i think root, busybox, and cw mod installation, it keeps failing, might be a good thing though since i am sure someone will do a workable zip to install this update
smaskell said:
good point. I wasn't thinking about that. I never bothered to install clockwork before so I never had to use fastboot(on the galaxy tab. obviously, I have on all my other devices). Anyway, couldn't someone make a clockwork image that we could flash via recovery? or could we not use rom manager to flash the recovery?
Click to expand...
Click to collapse
Related
There is a thread with this info in it, but it is buried deep in over a hundred pages and I thought the warning for HelixLauncher bared having a new post.
Here is the link to download the update.
http://android.clients.google.com/packages/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
Looks like that link is dead... here is a mirror
http://dl.dropbox.com/u/113487/signed-passion-FRF50-from-ERE27.1e519a24.zip
And one more just in case the others go down.
http://www.filefactory.com/file/b1chb29/n/update-nexusone-FRF50-signed.zip
Warning!! If you use Helixlauncher, uninstall or remove its defaults. It will go into a Force Close loop, making the phone unusable without booting into recovery again and performing a factory wipe/reset.
How to flash the update, I used these steps and it worked fine, but remember, there is always the possibility to brick the phone.
1. Download file from link up there.
2. Rename the file to update.zip.
3. Note that if you're using Windows and don't have "show file extentsions" turned on in the file explorer you won't see a .zip. Just rename it to "update" (no quotes, of course) because it's already a zipped file.
4. Copy the update.zip file onto your microSD card.
5. With your Nexus One off, hold down the trackball and press the power button.
6. You'll be booted into a white screen with three Android robots on skateboards. Select "Bootloader."
7. On the next screen, select "Recovery."
8. Your phone will reboot, giving you a picture of the Android robot and an exclamation point inside a triangle.
9. Now press the power button and volume up button at the same time. It could take a couple of tries.
10. Now (using the trackball this time) choose "Apply sdcard:update.zip" and let things run their course.
Taken from the update-1 instructions on:
http://www.androidcentral.com/how-ma...your-nexus-one
Also, I don't think my phone rebooted own its own after the update. After a minute or two, I tried hitting power and power+vol up to get the menu and reset manually. During that time it reset and booted up fine. So I say give it a few minutes before trying to reboot after the update finishes.
Edit: a ton of threads have popped into existence about froyo, but I didn't see any with early warnings about Helixlauncher.... ah well, maybe this post can be helpful for someone out there.
Edit 2: From what I am seeing, AT&T phones are on a different build of Android than the T-mobile N1. Seems like if you have an AT&T version you are out of luck for right now. This update was meant for the demo devices given to the Press outlets around launch, before the AT&T phone existed.
thanks for this, just a quick question.
Is this ok to use on a nexus one in england? it's not usa only or something is it?
thanks
Can it be flashed over Cyanogen? I read somewhere that it couldn't...
shrub said:
thanks for this, just a quick question.
Is this ok to use on a nexus one in england? it's not usa only or something is it?
thanks
Click to expand...
Click to collapse
If it is a US update then using it on a nexus one in England might not be a good idea, but I doubt it would hurt the phone, but some things might not work right.
St.Jimmy! said:
Can it be flashed over Cyanogen? I read somewhere that it couldn't...
Click to expand...
Click to collapse
You have to be back to stock recovery, so best to follow the directions in this thread. -> http://forum.xda-developers.com/showthread.php?t=686593
you made my day, man. Downloading...
Marine6680 said:
If it is a US update then using it on a nexus one in England might not be a good idea, but I doubt it would hurt the phone, but some things might not work right.
You have to be back to stock recovery, so best to follow the directions in this thread. ->
I flashed it over cyanogen 5.0.7 Test2 and it worked without any problem. Just helixlauncher is going nuts
Click to expand...
Click to collapse
Yeah I had to do a wipe when Helixlauncher went nuts on me, but Android restored all my apps for me lol.
Re: Official Froyo 2.2 update download, instructions, and HelixLauncher user Warnings
So...can we reinstall helixlauncher safely after updating? Just want to make sure
naynada said:
So...can we reinstall helixlauncher safely after updating? Just want to make sure
Click to expand...
Click to collapse
Not sure if Helixlauncher will already work with Froyo
i keep gettin installation aborted
Ritmjunk said:
Marine6680 said:
If it is a US update then using it on a nexus one in England might not be a good idea, but I doubt it would hurt the phone, but some things might not work right.
You have to be back to stock recovery, so best to follow the directions in this thread. ->
I flashed it over cyanogen 5.0.7 Test2 and it worked without any problem. Just helixlauncher is going nuts
Click to expand...
Click to collapse
Wait what?!?! Your saying it works just flashing over CM? Iv read all day that you have to go back to stock.. Have you tried/know if it works over 5.0.6?
Click to expand...
Click to collapse
Crime843 said:
i keep gettin installation aborted
Click to expand...
Click to collapse
I cant find it in the market anymore .....
johanove said:
Ritmjunk said:
Wait what?!?! Your saying it works just flashing over CM? Iv read all day that you have to go back to stock.. Have you tried/know if it works over 5.0.6?
Click to expand...
Click to collapse
I'm not joking really. I flashed it over cyanogen 5.0.7 TEST 2 and my N1 is working fine. I'm from Belgium and bought the N1 in U.K.
Click to expand...
Click to collapse
Ritmjunk said:
johanove said:
I'm not joking really. I flashed it over cyanogen 5.0.7 TEST 2 and my N1 is working fine. I'm from Belgium and bought the N1 in U.K.
Click to expand...
Click to collapse
Ok I assume you used Paul's release then?
Click to expand...
Click to collapse
johanove said:
Ritmjunk said:
Ok I assume you used Paul's release then?
Click to expand...
Click to collapse
Jeeee yes, sorry .... I just saw the header and this topic is about the official release/download. Indeed I used Pauls release..... sorry my mistake.
Click to expand...
Click to collapse
naynada said:
So...can we reinstall helixlauncher safely after updating? Just want to make sure
Click to expand...
Click to collapse
Ritmjunk said:
Not sure if Helixlauncher will already work with Froyo
Click to expand...
Click to collapse
Yeah I'm thinking the new update broke it, helixlauncher is integrated much deeper into th OS than most apps, so it would be more vulnerable to even small changes
Crime843 said:
i keep gettin installation aborted
Click to expand...
Click to collapse
I read somewhere, that another person had the same issue. Are you using stock recovery? Also, are you on the latest 2.1 update 1? I'm not sure the issue really. Try a search of the other threads, see if there is a solution.
same here... tried it twice with installation aborted each time. Redownloaded the file... renamed and copied to the sd card again.... same results.
Ritmjunk said:
johanove said:
Jeeee yes, sorry .... I just saw the header and this topic is about the official release/download. Indeed I used Pauls release..... sorry my mistake.
Click to expand...
Click to collapse
Cool, ill give it a try then. Thanks for your quick response!
Click to expand...
Click to collapse
Can someone post a link to HelixLauncher? Can't find it in the Market.
Thanks!
about the HELIXLAUNCHER:
there is NO NEED FOR WIPING everything! i had the same problem after updating and these force kills were really anoying.
here's what you have to do
1. remove your sim card (necessary because other wise your phone will reboot in safe mode - don't ask me why, but it did)
2. get into safe mode: (menu button long press while the X flashes on the load, give it a few tries, it vibrate long if it works)
3. delete helix
4. reboot
5. pray and thank me ;-)
worked for me!
I know you guys hate when people jump the gun...but I'm honestly running out of ideas here. Earlier today I tried to use LCD Density changer on my Nexus S...whether this was stupid on my part, you all can decide later. As for now my nexus boots a black screen. I'm only posting here cuz maybe in finding a solution we can uncover a bit about how the nexus is set up, because it seems to refuse any changes made to the system through fastboot or adb push.
I have tried just about every option to restore the system to stock format, and need help getting my nexus back to booting condition. I've tried fastboot flashing the system.img and just get a "write failed" error. I've pushed the whole system dump to /system through adb and when i reboot it is still missing the files i just pushed. I've flashed different boot.img's in combination with the first two steps, and still my phone remains unbootable.
Any ideas what could be going wrong?
fykick said:
I know you guys hate when people jump the gun...but I'm honestly running out of ideas here. Earlier today I tried to use LCD Density changer on my Nexus S...whether this was stupid on my part, you all can decide later. As for now my nexus boots a black screen. I'm only posting here cuz maybe in finding a solution we can uncover a bit about how the nexus is set up, because it seems to refuse any changes made to the system through fastboot or adb push.
I have tried just about every option to restore the system to stock format, and need help getting my nexus back to booting condition. I've tried fastboot flashing the system.img and just get a "write failed" error. I've pushed the whole system dump to /system through adb and when i reboot it is still missing the files i just pushed. I've flashed different boot.img's in combination with the first two steps, and still my phone remains unbootable.
Any ideas what could be going wrong?
Click to expand...
Click to collapse
Is it safe to say you didnt do nandroid restore prior?
Yes, that is correct...didn't think it'd cause this much of a problem(stupid me). I asked earlier if maybe some could upload a nandroid restore for me so I could at least attempt that. But I got no response, so I'm still in the dark.
fykick said:
Yes, that is correct...didn't think it'd cause this much of a problem(stupid me). I asked earlier if maybe some could upload a nandroid restore for me so I could at least attempt that. But I got no response, so I'm still in the dark.
Click to expand...
Click to collapse
When I get home in an hour, I'll factory wipe and make a backup of the stock rom for you.
Any recommendations on where to upload?
I got you man im backing up right ow....going to wipe then backup again and ill upload it so give me a bit
maybe ill be really nice and include some custom transitions for you
Only been 1 day since it came out, since it boots to black, take it back to the store, act stupid, get another one. Solved.
nandroid
pm'ing you the link
let me know if it works
mount usb storage copy and paste the into clockworkmod/backups
unmount usb storage and restore....gave you all the goodies too
nxt said:
Only been 1 day since it came out, since it boots to black, take it back to the store, act stupid, get another one. Solved.
Click to expand...
Click to collapse
Hahahahaha best thing I've heard all day
Apparently the NS is super-brickable, according to JBQ (@jbqueru) on android-building:
-Even though Nexus S is designed to be suitable for AOSP work, there
are some caveats. I very strongly recommend against trying to use
Nexus S for anything related to AOSP at the moment. Trying to unlock
or use your Nexus S for AOSP work could easily turn it into a Nexus B
(where B means "brick"); I have two of those, they're not very useful.
I'll send some guidelines about what is currently possible once I've
finished pushing the source code.
Click to expand...
Click to collapse
Is there anyway I can get the link for that nandroid? I seem to have messed my system files up as well.
wdfowty said:
Hahahahaha best thing I've heard all day
Apparently the NS is super-brickable, according to JBQ (@jbqueru) on android-building:
Click to expand...
Click to collapse
Now that is a frightening prospect;( How can google make a dev phone thats super brickable... hmmm
JD
AndHel said:
Is there anyway I can get the link for that nandroid? I seem to have messed my system files up as well.
Click to expand...
Click to collapse
Can I get the link for the stock nandroid also? I need to use a secure boot image.
Okay, thank you very much for the Nandroid. It worked and I'm back up and running.
OKay
So i sent the backup to at least 3 people anyone care to let me know hows its going and whether or not they like the customizations
drexman8244 said:
So i sent the backup to at least 3 people anyone care to let me know hows its going and whether or not they like the customizations
Click to expand...
Click to collapse
maybe you can upload it to mediafire or somewhere else, and create a thread? it might help others out
ill take your advice on that Thanks
adb push may not have been working because your system wasn't mounted properly in Clockwork recovery. I had this issue when trying to root. In Recovery, go to Mounts & Storage and hit "Mount System" THEN adb push the system dump.
You probably didn't need to nandroid. Could have just used adb to reset the density line in your build.prop I assume?
fykick said:
Okay, thank you very much for the Nandroid. It worked and I'm back up and running.
Click to expand...
Click to collapse
Please mention it on the Thread Title PROBLEM SOLVED.
An nandroid backup can be found here http://forum.xda-developers.com/showthread.php?t=877601
Hi guys, i'm the developer of LCD Density Changer. Sorry about the problems it caused.
Is it true that the Nexus S, doesn't support a density change. That would be a real bummer! Not for the app, but in general. I just don't hope Google blocks a density change in their new Android versions.
A question: does the "preview/temporarily" density change works in the LCD Density Changer app. If so, there is still hope.
Meanwhile, based on these reports I will put up a note to warn Nexus S users.
Hello. Please help me. my phone can not use the rom manage. I have used one once, but can not be used again. when I turn on the program, still connected 3g/wifi but nothing more happened at all. I have copied the program into the correct directory. My phone rooted.This phenomenon occurs after I Flast 2.1
What doesnt work? Does it not install? Why are you copying the app at all? Why not install from Market?
I installed the application from Market but I can not use the rom manage.
I don't know!
duongthanhcong said:
I installed the application from Market but I can not use the rom manage.
I don't know!
Click to expand...
Click to collapse
Rom Manager*
You have to be rooted to use it.
You can't expect people to help you if you don't tell them the problem.
So its installed, did you flash the clockworkmod? Should be the top most option.
dcontrol said:
You can't expect people to help you if you don't tell them the problem.
So its installed, did you flash the clockworkmod? Should be the top most option.
Click to expand...
Click to collapse
Also, did you download it from the market, or did you steal the pro version from online? I am asking because you said "I copied it to the right directory"
Maybe I understand his/her problem. Rooted, installed RM but cannot install Clockwork?
Few options here, search for the standalone update.zip with Clockwork and do it that way OR wait a few hours and try again.
The 1st choice I had to do once because RM wasn't liking my phone and the 2nd choice sometimes the server is down.
First, my phone t959 rom UVJI6 normal. Then my rom to version 2.2 T959UVJFD. I do not feel satisfied so I returned to the Odin 2.1.
My phone has a normal root and fix lag.
but then, I could not manage to use the rom again.
Sorry for my english level is limited. I'm from Vietnam
blizzard1017 said:
Maybe I understand his/her problem. Rooted, installed RM but cannot install Clockwork?
.
Click to expand...
Click to collapse
Yes. this is my problem. How do I do now?
Thanks!
If youre trying to flash another rom you need to disable the lagfix first.
Sent from my SGH-T959 using XDA App
My assumption is you have OCLF, try removing it then giving it a go.
Google a clockwork update zip that is pushable with ODIN, I found one the other day. I MAY have it still but I am not sure and I honestly have no clue where I found it, wasn't xda I am about 90% sure. It is not really a solid fix but will get you to where you have CWM. Rom Manager will not recognize you have it installed but when you go to enter recovery mode it will enter into CWM.
Did you by chance also flash a custom kernal? When I tested out a few I noticed my phone did the same thing, my knowledge currently doesn't expand far enough to know if they can even be related though. I am still learning a lot myself.
blizzard1017 said:
My assumption is you have OCLF, try removing it then giving it a go.
Google a clockwork update zip that is pushable with ODIN, I found one the other day. I MAY have it still but I am not sure and I honestly have no clue where I found it, wasn't xda I am about 90% sure. It is not really a solid fix but will get you to where you have CWM. Rom Manager will not recognize you have it installed but when you go to enter recovery mode it will enter into CWM.
Did you by chance also flash a custom kernal? When I tested out a few I noticed my phone did the same thing, my knowledge currently doesn't expand far enough to know if they can even be related though. I am still learning a lot myself.
Click to expand...
Click to collapse
(See attachment)
Master™ said:
(See attachment)
Click to expand...
Click to collapse
Always living up to your name...
I had mine fixed up through some trial and error hopefully this gets the OP in the right direction.
I was wondering if there was a way to change the home button from holding the power button and selecting home to just tapping the power button and having that serve as the home button.
Furthermore, is there a way to changed launchers in CM7?
Lkr721993 said:
I was wondering if there was a way to change the home button from holding the power button and selecting home to just tapping the power button and having that serve as the home button.
Furthermore, is there a way to changed launchers in CM7?
Click to expand...
Click to collapse
Not sure but in Settings > CyanogenMod settings > Tablet tweaks > Choose soft-buttons, you can put the home button right on the screen.
Not sure if you knew that but if not, now you know.
Launchers: In the Market.
that's pretty handy, thanks for the tip. i'm going to enable that now.
do you know if there is a way to get flash support in CM7? i know that it is supported in the kindle OS
Lkr721993 said:
that's pretty handy, thanks for the tip. i'm going to enable that now.
do you know if there is a way to get flash support in CM7? i know that it is supported in the kindle OS
Click to expand...
Click to collapse
Download Flash Player from the Market.
devilot said:
Download Flash Player from the Market.
Click to expand...
Click to collapse
Lkr721993 said:
that's pretty handy, thanks for the tip. i'm going to enable that now.
do you know if there is a way to get flash support in CM7? i know that it is supported in the kindle OS
Click to expand...
Click to collapse
Yes, exactly what Devilot said. Adobe Flash from the Market should do the job.
Has anyone thought of taking the ICS virtual buttons and porting them into CM7?
in regards to installing flash from the market, it says 'incompatible with your device'. i'm having the same issue with Dolphin Browser HD at the moment
Lkr721993 said:
in regards to installing flash from the market, it says 'incompatible with your device'. i'm having the same issue with Dolphin Browser HD at the moment
Click to expand...
Click to collapse
That's strange. Maybe go into Recovery and clear cache and Dalvik-cache? You're using CM7, correct?
I'm using CM7 as well, and flash installed fine for me. Just make sure to do a Delvik/Cache wipe AFTER you install the ROM, and you *should* be fine.
As far as launchers go, definately check out GO Launcher EX v2.71. Its not available in the market yet, just off their website, but its made specifically for 7 and 10 inch tablets.
http://golauncher.goforandroid.com/
- dredd
aoaleman said:
That's strange. Maybe go into Recovery and clear cache and Dalvik-cache? You're using CM7, correct?
Click to expand...
Click to collapse
yes i am on CM7. clearing caches did nothing.
i just backed up my CM7 install, gonna try a reinstall and see if i can fix it
dredd0606 said:
I'm using CM7 as well, and flash installed fine for me. Just make sure to do a Delvik/Cache wipe AFTER you install the ROM, and you *should* be fine.
As far as launchers go, definately check out GO Launcher EX v2.71. Its not available in the market yet, just off their website, but its made specifically for 7 and 10 inch tablets.
http://golauncher.goforandroid.com/
- dredd
Click to expand...
Click to collapse
It is now available in the Market.
look for flash player 10.3 apk, i had the same problem and that worked for me you have to reboot the tablet after you install it for it to work
mono feo0 said:
look for flash player 10.3 apk, i had the same problem and that worked for me you have to reboot the tablet after you install it for it to work
Click to expand...
Click to collapse
Yeah like mono feo0 said, try Flash 10.3.186.7.
If not, also try 11.1.111.5.
reinstalling CM7 did the trick. unfortunately i have to reinstall everything now
Lkr721993 said:
reinstalling CM7 did the trick. unfortunately i have to reinstall everything now
Click to expand...
Click to collapse
I'm sorry to read that. But next time use Titanium Backup to backup your apps and data. Makes things so much easier. On a brighter note, I'm glad you got it working.
aoaleman said:
I'm sorry to read that. But next time use Titanium Backup to backup your apps and data. Makes things so much easier. On a brighter note, I'm glad you got it working.
Click to expand...
Click to collapse
to be honest, i have nothing to complain about, I only had CM7 running for a few hours, there isn't that much to put back on it. i will check out titanium backup though!
Lkr721993 said:
to be honest, i have nothing to complain about, I only had CM7 running for a few hours, there isn't that much to put back on it. i will check out titanium backup though!
Click to expand...
Click to collapse
Cool! Enjoy your CM7 powered Kindle Fire.
Wow, that is definitely odd. I have two KFs, both on CM7, and both installed Flash Player straight from the market without hesitation.
Glad you got it to work though!
Seems to be quite a few little quirks and bugs that happen to some and not others. I'm sure as the roms and devs get going the bugs will be fewer.
Does ADB not work when in recovery?
When my N7 is in recovery mode (CWM) my PC (Win7) doesn't see any attached USB devices and "adb shell" obviously tells me "no devices found".
My N7 is rooted, unlock bootloader, has CWM (non touch) installed and when in "regular", normal boot I can perfectly "shell in" via adb, just not in CWM recovery....
Does CWM not support that as of yet, or am I doing something wrong?
Not sure. Adb works fine for me in cwm
Sent from my Nexus 7
Why did you installed CWM into your tablet, instead of loading it ONLY when you need to? That is the proper approach.
bagofcrap24 said:
Not sure. Adb works fine for me in cwm
Click to expand...
Click to collapse
OK, so it might just be something I'm doing wrong.
TECK said:
Why did you installed CWM into your tablet, instead of loading it ONLY when you need to? That is the proper approach.
Click to expand...
Click to collapse
Counter question: Why not?
You don't have to decide what's the proper way to do things for me, I think I know what I'm doing - also I might need it (or at least it's supposed root adb shell access) everytime I go to recovery, so why keeping the need to have to "fastboot boot" it everytime instead of just booting into it?
Also - as said above - adb and fasboot both work fine, just not in CWM.
I might try another driver, maybe that'll help.
HellcatDroid said:
You don't have to decide what's the proper way to do things for me, I think I know what I'm doing.
Click to expand...
Click to collapse
The proper way is to tempload CWM, not install it. You want to be special and do it your way, feel free to... nobody is stopping you. Since you know what you are doing, then you should not have any issues.
HellcatDroid said:
I might try another driver, maybe that'll help.
Click to expand...
Click to collapse
What's wrong with using the default Google USB drivers? They work properly.
TECK said:
What's wrong with using the default Google USB drivers? They work properly.
Click to expand...
Click to collapse
See first post, not working in CWM for me right now.
Might not be the drivers, if you have any real help to give, feel free to share.
I would not use other drivers, except the Google USB ones provided on their developer site.
Based on my experience, you can have only headaches if you replace stock recovery with CWM. That's the main reason why I always temp load it, instead of physically install it. I know it is convenient to have it installed, but how often do we use it? Very rarely. The less I tweak on the phone, the safer it is. Are you running 6.0.1.0 on your tablet?
First, do you see the Android 1.0 driver marked as invalid in device manager?
If yes, then the fix is easy... Follow the procedure I posted in my signature to properly install the ADB drivers.
Do you have any "fancy" drivers installed, like Samsung, Unsigned from XDA, etc.? Get rid of all of them, if you do and make sure you ONLY deal with Google drivers.
If not, this is what I would do in this situation: I would install the Google factory image (straight from console, no crazy toolkits) and restore everything back to normal. Then, I would test the stock recovery and see if everything works as expected. After that, I would tempload CWM 6.0.1.0 and see if there are any issues. I know is a ****ty deal, especially if you have lots of customizations on your tablet. The goal is to see if you can run all proper commands while using the stock recovery. If you cannot, that's a different ball game.
It's been the drivers.
i installed the ones from the Android SDK and everything works now (had drivers d/l'ed from the Asus page so far).
TECK said:
Based on my experience, you can have only headaches if you replace stock recovery with CWM.
Click to expand...
Click to collapse
Based on my experience it doesn't really matter - unless you are going to use some special functionality CWM breaks (like the full device encryption on the S2 with GingerBread 2.3.x - and I got even that to work with an own build).
Bottom line: every one does things differently and something perfect for one might be suboptimal for the other.
TECK said:
That's the main reason why I always temp load it, instead of physically install it.
Click to expand...
Click to collapse
I love the option to be able to temp-boot a kernel, my Droids so far (Samsung Galaxy S2 and S3) didn't support that.
Tempbooting a kernel is perfect for testing a new build as you don't have to reflash a working one if the one you tried doesn't work
Though, it'd be just more work for me to tempload CWM everytime I need it, but as said, that's just me.
TECK said:
I know it is convenient to have it installed, but how often do we use it? Very rarely.
Click to expand...
Click to collapse
Negatory, I use it alot.
Mostly for the rooted adb shell access though, yet that's rather often - and also quite often away from my home computer with everything loaded and temploading without the kernel image.... hmm, not really
TECK said:
The less I tweak on the phone, the safer it is.
Click to expand...
Click to collapse
Safety is overrated (disclaimer: that's a joke )
For me it's more like "the more I mod the hell out of it, the more fun it is - and if everything breaks, I restore/reflash factory and start over".
CWM won't stay for too long anyways, eventually I'll smack my own kernel and own recovery-kernel onto it.
Time to check out those sources
TECK said:
Are you running 6.0.1.0 on your tablet?
Click to expand...
Click to collapse
Yeah.
TECK said:
Do you have any "fancy" drivers installed, like Samsung, Unsigned from XDA, etc.? Get rid of all of them, if you do and make sure you ONLY deal with Google drivers.
Click to expand...
Click to collapse
Nothing "fancy" but Samsung drivers, yes.
And getting rid of them is totally out of the question as my S2 and S3 won't work anymore, then.
But everything works now, got the Google SDK drivers for the N7 and the Sammy drivers for the rest and everything looks good
TECK said:
(straight from console, no crazy toolkits)
Click to expand...
Click to collapse
Yeah, that's exately how I do it, adb and fastboot all "by hand".
TECK said:
I know is a ****ty deal, especially if you have lots of customizations on your tablet.
Click to expand...
Click to collapse
All hail to the backups, just restore my data after the wipe :good:
Anyways, thanks for the help, after all it was that link to the tut that got me to install the Google SDK drivers