id like to further my phone knowledge and learn how to use ADB. planning to read up on it,watch some videos,and then run the flashback zip to put my phone back to stock. then id like to reroot it the "old skool" way
just wondering if anyone has any links they liked or found particularly helpful before i start clicking the search button. either on ADB in general,or procedure,files,etc. for using it to root the eris.
thanks for any info
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers.
follow me on twitter @scotty1223
Device(s): ReZound, Dinc (ret), Nexus one, Eris (ret), Gtab
Thanks: 534
Thanked 1,123 Times in 687 Posts
Quote:
Originally Posted by scotty85
id like to further my phone knowledge and learn how to use ADB. planning to read up on it,watch some videos,and then run the flashback zip to put my phone back to stock. then id like to reroot it the "old skool" way
just wondering if anyone has any links they liked or found particularly helpful before i start clicking the search button. either on ADB in general,or procedure,files,etc. for using it to root the eris.
thanks for any info
You have to download sdk. Have u done that yet? There's a bunch of stuff.
__________________ THE PLUMBER
HTC Rezound - Scott's Developer Edition 1.2 S-OFF, HTC Incredible - ICS Aokp build 26
HTC Eris - Condemned CM7 V 23 R.I.P., HTC Eris - GSB v4.4-full_ODEXED_CM7.2.0, ViewSonic Gtablet - TnT
Do you have questions about the forum? Click here: http://androidforums.com/faqs/.
There's stuff in here where eu1 (of course ) posted steps for doing a Nandroid backup, doing your wipes, flashing your new ROM, all via adb and the custom recovery.
This was the method of last resort for those whose trackball's had totally gone south on them and before the trackball-optional recovery (and part of my impetus for creating said recovery ).
You have to download sdk. Have u done that yet? There's a bunch of stuff.
not yet,BC. i watched the video on the TB root forum,and im about to start checking out the links provided by doogald and scary. usually the GF is out of the house in the evenings,but shes changing jobs and been here the last couple nights pestering me(did i say that out loud?) so hopefully not much on the agenda tonite and i can start getting it figured out. getting excited to be doin somethin new with my lil eris
Device(s): ReZound, Dinc (ret), Nexus one, Eris (ret), Gtab
Thanks: 534
Thanked 1,123 Times in 687 Posts
Quote:
Originally Posted by scotty85
not yet,BC. i watched the video on the TB root forum,and im about to start checking out the links provided by doogald and scary. usually the GF is out of the house in the evenings,but shes changing jobs and been here the last couple nights pestering me(did i say that out loud?) so hopefully not much on the agenda tonite and i can start getting it figured out. getting excited to be doin somethin new with my lil eris
I have all the required stuff but haven't tried my hand at it yet and probably won't have the time to do it. I'm getting started on take offs to quote a contract to plumb 633 new houses.
I have all the required stuff but haven't tried my hand at it yet and probably won't have the time to do it. I'm getting started on take offs to quote a contract to plumb 633 new houses.
holy crap,BC! thats a bunch of plumbing!
ive downloaded andinstalled sdk and got adb working.
i used the adb shell to do a system dump to screen(not sure what that is but it seemed like a harmless command ) and rebooted,and rebooted to fastboot and to recovery. apparently i have no fastboot drivers as adb doesnt see the phone in that mode.
lol...no problem, we just crossed posts a few minutes apart... It took me a sec to find the files on my laptop (I'm moving stuff from my desktop to here and I couldn't remember where I put the files , but its all good now ).
By the way, I think I left off the part of the command where you have to specify the Nandroid backup to be restored.
Amon_RA's recovery.c appends the name of the selected Nandroid backup path to the end of the command I posted above. I'll edit it in a sec to reflect this.
Thanks! (and I hope I caught you in time)
edit: clearly, you already figured-it out ^^^
Last edited by scary alien; March 23rd, 2011 at 08:35 PM.
The Following User Says Thank You to scary alien For This Useful Post:
lol,i figured there was a way i had to specify what one,but i wasnt sure how to do it... i went ahead and pasted the command and it defaulted to the most recent. wich was coincidentally the one i wanted
if id wanted to pick a different one... would i leave off the "--defaultinput -s <nandroid-backup-directory>" and replace it with "/sdcard/nandroid/xxx/yyy" ? or would i just tack that on the end of your entire command? (xxx=phone id,and yyy=backup name)
oops,just saw your comment that youll edit. ill refresh and check now
edit: got it! thanks again,mister scary!
Last edited by scotty85; March 23rd, 2011 at 08:43 PM.
lol,i figured there was a way i had to specify what one,but i wasnt sure how to do it... i went ahead and pasted the command and it defaulted to the most recent. wich was coincidentally the one i wanted
if id wanted to pick a different one... would i leave off the "--defaultinput -s <nandroid-backup-directory>" and replace it with "/sdcard/nandroid/xxx/yyy" ? or would i just tack that on the end of your entire command? (xxx=phone id,and yyy=backup name)
oops,just saw your comment that youll edit. ill refresh and check now
edit: got it! thanks again,mister scary!
Well, the "--defaultinput" parameter says this in the nandroid-mobile.sh source:
Code:
--defaultinput Makes nandroid-mobile non-interactive, assumes default inputs from the user.
So, that's probably why it figured-out to restore your latest (or alphabetically last?) backup.
The "-s " is used to specify the subdirectory (i.e., Nandroid backup directory in this context) to be restored.
Here's a .zip containing both the recovery.c and the nandroid-mobile.sh script that it references:
so i now have a rooted thunderbolt while i dint go the completely "old school" route with it,the knowledge i gained from this helped me even with the easy root. im not done playing with the eris and adb yet,but wanted to say thanks again for the info everyone provided
Does the Thunderbolt need to be rooted? I know that I resisted rooting the Eris until it was clear that 2.1 had issues that weren't going away by staying stock.
Or is rooting just like Mt. Everest - it's there, so you do it?
so i now have a rooted thunderbolt while i dint go the completely "old school" route with it,the knowledge i gained from this helped me even with the easy root. im not done playing with the eris and adb yet,but wanted to say thanks again for the info everyone provided
FWIW, the method I used to figure out what command-line the recovery system was using was simply to have an adb shell running, and then, after manually starting the backup/restore operation, run a "ps" command to get the PID of the script process, and then
cat /proc/<PID>/cmdline
(with "<PID>" replaced by the actual numeric value, of course)
This is relatively easy to do because the backup/restore operations take a long time to complete, so there is plenty of time to capture the info.
For shorter-lived jobs, you could get the same info by using "strace" to attach to the running /sbin/recovery program, and looking for exec() or execve() calls in the output of strace.
Just mentioning this because different recoveries use different versions of nandroid-mobile.sh, and also pass it different command-line arguments.
eu1
__________________
Please don't send me PMs - post your questions so others may benefit from any answers given.
Does the Thunderbolt need to be rooted? I know that I resisted rooting the Eris until it was clear that 2.1 had issues that weren't going away by staying stock.
no,id be a liar if i tried to say it "needed" to be rooted. it does have its share of bloatware,but if you dont mind it being there,it doesnt seem to hurt it... its incredibly smooth,fast,and capable.
Quote:
Originally Posted by doogald
Or is rooting just like Mt. Everest - it's there, so you do it?
well,i do really enjoy rooting and romming,and modifying my phones(hello! my name is scott and im a flashoholic ),but i did have a couple of somewhat practical reasons:
-the ability to make nandroid backups
-the ability to backup apps and their data with titanium
-the ability to use other root apps like drocap and setcpu.
also cyanogenmod will be supporting it. i love cm7,im not fond of sense at all,so i will be able to set my phone up how imost enjoy using it the most by rooting it.
so i played around with this some more. went back to 1.5 firmware and 1.47.0000 bootloader by flashing the MR2 PB00IMG. i then rooted with adb and the v4 hack,and used jcases How To Install Engineering bootloader FOR LEAK ROOTERS - xda-developers to install the root rom(tho i dont think i really needed to do that,since i dint install one of the leak roms) and get my S-OFF bootloader back.
at this point, i could not install the recovery in fastboot as described by jcase because for some reason adb quit seeing my phone i finally gave up and just installed it thru hboot with scary's and my lil experiment ( making an hboot flashable recovery )
i then tried to install the "newer" 1.7.1 track ball optional recovery(thanks scary ) via adb and kept getting a "failed to copy 'recovery-RA-eris-v1.6.2-trackball-optional.img' to '/sdcard': Is a directory
any ideas what im doing wrong? not that it matters much, ive got the older tracball not required,but im trying to become more adb proficient.
Last edited by scotty85; March 29th, 2011 at 12:36 AM.
at this point, i could not install the recovery in fastboot as described by jcase because for some reason adb quit seeing my phone i finally gave up and just installed it thru hboot with scary's and my lil experiment ( making an hboot flashable recovery )
I've had the PC become "confused" about the USB state after many (otherwise normal) reboot cycles where I had just left the USB cable plugged in. Usually I would just unplug & re-plug the cable, and if that didn't work I would move to a different USB port. If that didn't work, I would reboot the PC (or VM). I don't remember ever getting into a state where an inability to communicate via adb to Amon_RA was anything other than transitory.
Quote:
Originally Posted by scotty85
i then tried to install the "newer" 1.7.1 track ball optional recovery(thanks scary ) via adb and kept getting a "failed to copy 'recovery-RA-eris-v1.6.2-trackball-optional.img' to '/sdcard': Is a directory
any ideas what im doing wrong? not that it matters much, ive got the older tracball not required,but im trying to become more adb proficient.
Not completely sure what you are saying here; my answer presumes you are trying to do an "adb push" with Amon_RA (or other) recovery booted:
- Make sure to do an "adb shell mount /sdcard" first - the recovery does not mount the SD card by default when it first boots. (But it will leave it mounted after some of the menu operations - you can check to see what is mounted with no arguments given to the mount command - "adb shell mount" ).
I will occasionally take a lazy approach to copying files, where I will just use a trailing slash, as in:
Code:
adb push foo.fil /sdcard/
instead of
Code:
adb push foo.fil /sdcard/foo.fil
Whether or not it accepts the former might depend on the version of adb in use, though.
HTH
eu1
PS I don't know how scary is having you install it, but once it is pushed to the phone someplace (doesn't even need to be the SDcard, BTW, because the recovery image is fairly small) the "flash_image" program built in to Amon_RA will work just fine:
I've had the PC become "confused" about the USB state after many (otherwise normal) reboot cycles where I had just left the USB cable plugged in. Usually I would just unplug & re-plug the cable, and if that didn't work I would move to a different USB port. If that didn't work, I would reboot the PC (or VM). I don't remember ever getting into a state where an inability to communicate via adb to Amon_RA was anything other than transitory.
i have experienced this and have applied the same fixes. yesterday i dint try the reboot,as it was getting late and i dint feel like waiting on it
it appears that i just needed a different driver for 2.1 eclair to work. in 1.5,i downloaded the htc sync drivers and had to put the phone into sync in order for adb to see it. seemed to work ok that way,tho i know you usually want the phone to be in charge only while in adb.
after running the root rom PB00IMG,nothing i did let the phone be seen. once i restored my 2.4 backup, adb was back to seeing it.
Quote:
Originally Posted by erisuser1
Not completely sure what you are saying here; my answer presumes you are trying to do an "adb push" with Amon_RA (or other) recovery booted:
you are correct. i was simply trying to push the newer tracball optional recovery with adb,just for the experience of doing it. i dint have the phone in recovery,so if that was needed,thats prolly why it dint work
Quote:
Originally Posted by erisuser1
- Make sure to do an "adb shell mount /sdcard" first - the recovery does not mount the SD card by default when it first boots. (But it will leave it mounted after some of the menu operations - you can check to see what is mounted with no arguments given to the mount command - "adb shell mount" ).
I will occasionally take a lazy approach to copying files, where I will just use a trailing slash, as in:
Code:
adb push foo.fil /sdcard/
instead of
Code:
adb push foo.fil /sdcard/foo.fil
Whether or not it accepts the former might depend on the version of adb in use, though.
HTH
eu1
PS I don't know how scary is having you install it,
i was just using the commands listed in the first post of his htread. in his defense it does say that he purposely ommitted steps that those proficient in adb should know. i figured i was missing something. if he doesnt post up here i will ask in his thread,after reading through it again to see if its allready been discussed.
Quote:
Originally Posted by erisuser1
but once it is pushed to the phone someplace (doesn't even need to be the SDcard, BTW, because the recovery image is fairly small) the "flash_image" program built in to Amon_RA will work just fine:
I think some of the details I omitted were really just the adb connectivity issues one might have. I just didn't want to turn that thread into an even longer adb tutorial, lol.
The scenario 4 section in the other thread does show how to push the trackball-optional file over (4B) and to use the flash_image command (4D) just like eu1 showed. There's also the fastboot flash method listed (which you already tried but ran into connectivity issues).
You're already there, mate!
Cheers!
The Following User Says Thank You to scary alien For This Useful Post:
thanx scary! i booted into recovery and ran the commands and it worked like a charm *smacks forhead* since i allready had "trackball optional" i used the commands to push the "tracball not required" version and voila! that is now what i have.
im off to work,but ill use the commands again to push the "tracball optional" version back
The HTC Droid Eris launched for Verizon Wireless on November 6th in part as the carrier's first Android Phone. However it was overshadowed by the other member of the inaugural Verizon Droid duo - the Motorola Droid. The Droid Eris might look fa... Read More