Discussion in 'Android Devices' started by GrdLock, Mar 17, 2010.
It shouldn't scroll anything when you run the chmod command.
What does it say?
You forgot the "shell" part.
adb shell chmod 755 /system/bin/flash_image
guess we won't be seeing that new rom today
and apply hand to head... just saw your update
got it now. I was copying and pasting from the first post.. was it not there? or i wonder how it disappeared...
grdlock, you (and company) are awesome...
correct me if I'm wrong, but unless we run the recovery img correctly, the eris_0_2 rom won't do anything, right?
Right, you have to follow the steps in order to flash the new eris_0_2 rom.
Done. Thank you, sir.
4. Go to Wipe, and do a wipe of data/factory reset, as well as dalvik-cache wipe.
Will this delete all my apps, contacts, and pretty much everything not on the sd card?
Edit: Nevermind everything was answered in IRC.
Anyway, YES I have USB Debugging on. I'm still not sure why it says unable to connect to device.
This is just making me happy. Hah!
New problem: when I want to do step 3 in the recovery image installation, I am having problems in getting error saying:
can't stat "recovery.img" does not exist.
I have unzipped Recovery.zip into the \tools\ twice now and it still does not recognize that the file is there...But when I run the command prompt to open just that file (without the adb command) it recognizes that the file is there, but windows cannot open it.
Confused. Any explanations would be very helpfull. And if this is timed I'm not liking the fact that I'm on a clock to get the new rom installed when I can't get past step 2.
it is case sensitive... try a cap R
Same thing here. recovery.img no such file or directory. BTW it is a lower case "r" in the file name.
Got it to work. Good thing my computer smarts (hah) goes back to DOS daze. Even though I have my tools folder "pathed" I had to change directories within the command prompt into the tools directory then use the push commands ... worked like a charm.
"8. Right-click My Computer > Properties, and go to Device Manager. You should see a device with a yellow exclamation next to it, this is your phone (if you don't see it you probably forgot to enable USB debugging mode)"
Debugging is on, but still no yellow exclamation next to an icon.
Should I just right click the "My HTC" in "Android USB Devices"?
That's what I did and it worked just fine. Might have something to do with if/how you installedyou phone onto it computer previously.
Re-Sign in @ Google "feature" still there after power cycle for eris_0_2 ROM
Hmmm, seems to be intermittent.
I'm really baffled that I don't have to *228
What is *228?
Plus, Cell Standby issue there, too. Airplane Mode fixes, though.
I followed the instructions to the letter but just cant get it to see the device. a video tutorial would help out, ALOT.
There is a new ROM to flash, 0.3 instead of 0.2.
TheFuzz has hosted it on his site. Follow all directions above, and INSTEAD OF the eris_0_2.zip link, use this
He also hosts a tutorial one page back, parallel with this one. It's an excellent bookmark.
Eris Root Roms
This is made with OTA updates disabled, Amazon.com uninstalled, and a few apparent bug fixes. It seems stable, my Facebook contacts synced, Google login bug existed still (for me), and everything so far (including WiFi) seems to work.
Edit: Oh, and WiFi being fixed (dhcp, rather) is part of this.
pk, do you have to redo the recovery and flash_image file also if you have done the 0_2 ROM already?
nope, just put the zip on your sd card, boot into recovery mode, do the wipe data/dalvik cache and flash the new zip
Does this fix the XP ADB issue that I had in the 0_2 rom where it wouldn't install the drivers?