Another problem. After flashing to the latest ROM, I plugged the phone into the USB for the last of your scripts and noticed that the adb is now giving me a problem. So I went to My computer and devices and tried to update the driver as I did the first time and it says not found. Any ideas? Win 7 x64 NOTE: Tried rebooting both computer and phone and nothing. I will give it a shot on another computer when I get off work to see if I get the same problem.
Is this the next revision of the 0_3 ROM? I.e. "Minor modifications, added busybox, nano, su, spareparts.apk, superuser.apk, removed some bloat." still applies? Benefits to updated kernel? Other changes? I happy and ticked to see this... Love the ongoing development, but told myself today that I have my current rom (0_3) set up just the way I like it and I'm not going to mess with it anymore... yeah.. I didn't believe when I said it either..
I just rooted my phone a couple of hours ago and everything went well except for the install_extras.bat file. It said that the device was not found and I was unable to install the extras. So how would I load the ROM to get the live wallpapers like the Nexus 1 has. And also, is it true that the live wallpapers and Nexus launcher disables Sense UI?
Can you check if you can get adb on your phone. Like I have the yellow ! when listed in devices for adb and when I try to update the drivers, I cannot. So Im just wondering if you having same error as me. Thanks in advance.
I was able to get adb on my phone because before I rooted, I got the same yellow ! and then updated the driver like the guide said and now it just shows up in the device manager as a removable drive. I hope that's the answer you were looking for...
It answers the question. Just cant figure out why I cant get the yellow ! to go away as I followed the instructions to a t.
ok so i cannot enter the same commands from terminal emulator. any of you gurus know the correct commands? ive placed the extracted files from recovery.zip to the root of the sd card. is this even possible? im trying to push the files from the sd to the system of the phone right?
I know I've seen a "fix" for this somewhere, and I apologize but I cannot find it. I'm trying to restore my settings and apps with Titanium, but when I open Titanium for the first time since flashing I get a blank screen when I should be getting the super user permission request. Anybody know the fix? My searches give me nothing, granted I suck at searching. Can't find my ass sometimes in the dark. EDIT: Seriously. I feel like a twat. Debugging wasn't checked. Got it
I may have missed this, but can I delete the recovery img file too? I know I can delete the eris21official-root and PB00IMG.
hey so do I absolutely need the recovery img right now? can't I just update to the Rom like I did last time?
I think the recovery image on your sd is what allows you to enter recovery mode (booting with the up volume button pressed) and therefore update your rom. You could always replace it if you find the recovery mode not working... right?
The main benefit that we've noticed so far is that the google login bug is fixed with the new rom. I realize people hate completely reflashing their phones. Problem is, with a new official release from Verizon, it's difficult to make an upgrade package for a custom rom without knowing exactly what they changed. I did my best shot though to make an upgrade package. You can give this a shot if you like. Everyone who's tried it so far (including myself) it worked successfully. However, depending on your configuration and customizations, it IS possible to screw up, so be sure to run a Nand backup before running the upgrade just incase, then if it screws up you can just restore. Multiupload.com - upload your files to multiple file hosting sites! There's the file. Download, place on sdcard, reboot into recovery, wipe your dalvik cache only, then flash the upgrade. If you have installed the recovery partition successfully, you can remove the .img file from your sdcard, it's not needed. Yes, you NEED the recovery partition. It's the only way to install custom roms. The method you used to install the original rooted rom only worked because that rom was signed by HTC. We can't sign roms that will work in HBOOT, so our custom roms won't flash using HBOOT.
FYI - I tried the upgrade package above but flashed it from the Eris_0_2 rom and it failed to install correctly. I am downloading the OTA official rom now and will flash the upgrade package afterwards and report whether that works...
I was able to flash the eris21official-root but still am encountering an error with the upgrade package (ota-update)
If you flashed the eris21official-root image that's all you need. The ota-update is a very finiky upgrade package to upgrade from an older rom to the eris21official-root rom without wiping your whole phone.
sweet...thanks for the prompt reply! you've done a kick-ass job spearheading this whole process, btw. thanks to you and all the other devs for your hard work!!
I dont see #5 for Install wireless tethering when I run that .bat file. Am I missing something? #5 in that .bat file is to exit. EDIT: I just copied wireless_tether_2_0-pre8.apk file over from /files/ location to my SD card and installed it.
ok so i THINK my dad got me threw the command deal with the recovery...i THINK...how is the new rom? i know you were saying that you had everything the way u wanted it and werent going to flash anymore lol so did you decide to goahead with the new rom? if so hows it looking???
