• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Custom recovery on x!!!!!!!

hdokes said:
Where would one find this handy app? I searched on android market but did not find there. Can one provide a link?
Click to expand...

I put the link in the OP

bosox2k1 said:
How does one go about doing this? Mind explaining in idiot terminology?
Click to expand...

Install it
open it
press bootstrap recovery
done

Now if you want to make a backup press reboot recovery and then when you get there use the camera up+down buttons to scroll and the camera button to select and the power button to go back

If you ever get in trouble and your phone won't boot then do a battery pull and it will boot you into recovery
 
droider13 said:
I put the link in the OP



Install it
open it
press bootstrap recovery
done

Now if you want to make a backup press reboot recovery and then when you get there use the camera up+down buttons to scroll and the camera button to select and the power button to go back

If you ever get in trouble and your phone won't boot then do a battery pull and it will boot you into recovery
Click to expand...

So if i do the reboot recovery, is there certain options I should choose over others? Can I easily get back into normal phone mode by just turning it off and on again?

Also, the whole battery pull method--what if I take my battery out to do something to my sd card, if it boots into recovery mode, is it easy to rectify and just reboot into "normal mode".

Sorry for the, maybe pointless, questions, I just want to get some things clarified before I start doing this. First smartphone and never realized all this stuff was possible.
 
It says something about the logwrapper, logwrapper.bin and another file must be there or we are screwed.

What could I have done to remove those files? Is it safe to assume that they are still there and I did nothing to them---but then again, I really don't know. Basically, would I have to know exactly what I am doing to have somehow removed those files?

Really, thanks so much for the help to everyone.
 
Any brave REVOlution users can try the custom font :)

Obviously, it works. I was brave enough to try , heh.

revofont1.png
revofont2.png


Evolution_Font.zip

Put it on the root of your sdcard, select install .zip from sd card, choose the file, and go :)
 
In the words of "the King"..... Oh man.... I can not believe it! Somebody toss me some biscuits and gravy! ..... Backing up my x right now.... It's like a fix.... now I can hardly wait for 2.2!!!!
 
bosox2k1 said:
Now that this bootstrap has been released, isn't it safe to try? Or if that doesn't work then the SBF would work, right?
Click to expand...

Yeah, if it fails, then I'll have to SBF back to stock, root it, reinstall Clockwork, and I can nandroid back to my backup.

It's just a matter of making the updater-script and packing the .zip with the dev phone files.

Maybe I'll try it, but I've never used RSDLite before....
 
Pardon my ignorance but what does nandroid back to your backup mean?

I was under the impression that if bootstrap failed b/c the phone was trashed, you'd have to SBF it, re-root, download bootstrap again--then go back into recovery and then just hit restore since it was backed up to sd card (at least i thought). From reading your previous post--that seems like a no.
 
bosox2k1 said:
Pardon my ignorance but what does nandroid back to your backup mean?

I was under the impression that if bootstrap failed b/c the phone was trashed, you'd have to SBF it, re-root, download bootstrap again--then go back into recovery and then just hit restore since it was backed up to sd card (at least i thought). From reading your previous post--that seems like a no.
Click to expand...

It means exactly what you just posted.

Nandroid is the mechanism by which we make and restore our backups.
 
Fabolous said:
Yeah, if it fails, then I'll have to SBF back to stock, root it, reinstall Clockwork, and I can nandroid back to my backup.

It's just a matter of making the updater-script and packing the .zip with the dev phone files.

Maybe I'll try it, but I've never used RSDLite before....
Click to expand...

u never used RSDLite o_0
 
I just thought more about loading the dev phone /system files but it's not going to work.

It needs a Froyo kernel (doh!). Lol, can't believe I forgot about that.

Until a build of Froyo is modified to run on our 2.1 kernel, OR, we figure out how to flash the kernel, we'll have to wait.

Retrokid223 said:
u never used RSDLite o_0
Click to expand...

Yeah, I've never had my phone in a situation where I couldn't fix it with recovery (Droid 1), or unbootable (Droid 2)
 
First observations/feedback:

Performed a backup. Had the following errors:

1. E: Can't open /tmp/recovery.log
2. No /sdcard/android_secure found. Skipping backup of applications on external storage.
3. No sd-ext found. Skipping backup of sd-ext.
4. Backup complete
5. E: Can't open /tmp/recovery.log

Is there the potential of a secondary sd card besides the one contained within?
Should there be a recovery log in the tmp directory? The directory exists however there is nothing within.

Backed up images of the cache, data, and system seem to be intact.
 
hdokes said:
First observations/feedback:

Performed a backup. Had the following errors:

1. E: Can't open /tmp/recovery.log
2. No /sdcard/zandroid_secure found. Skipping backup of applications on external storage.
3. No sd-ext found. Skipping backup of sd-ext.
4. Backup complete
5. E: Can't open /tmp/recovery.log

Is there the potential of a secondary sd card besides the one contained within?
Should there be a recovery log in the tmp directory? The directory exists however there is nothing within.

Backed up images of the cache, data, and system seem to be intact.
Click to expand...
there are no errors. it is simply saying that you do not have apps2sd
 
Cool! I figured the big 'E' probably stood for .... oh ... I don't know... perhaps... 'Error'?

If I understand you correctly, as the 2.1 does not allow for apps to run from the sdcard.... there are none to be 'backed up'.... correct?
 
soooo, now that this is out, and X has been successfully rooted...

What does this mean for the OTA rollout of Froyo 2.2 in Sept by the big VZ?

Should I...

1) Wait for the Froyo rollout, and then root, & recover, and theme, and rom?

or

2) Root, Recover, Theme, ROM up....now?
a) And what does this mean if I do it now, and then the OTA rolls out? Do I accept the OTA, by unrooting, unrecovering, etc? Or just completely ignore the OTA?

Could use some valuable advice, thanks guys!

p.s. I WOULD be doing this on my Mac, using Terminal. (or whatever I need to do on the computer)
 
anaphora68 said:
I'll say this. I'm hoping, beyond hope, that Birdman and Rainabba can get over their differences with Koush and release the 2.2 ROM they've been working on.

Past that, I just ran a Nandroid backup...
Click to expand...
I wasn't aware of bad blood, whats the 411 on that
 
hdokes said:
Cool! I figured the big 'E' probably stood for .... oh ... I don't know... perhaps... 'Error'?

If I understand you correctly, as the 2.1 does not allow for apps to run from the sdcard.... there are none to be 'backed up'.... correct?
Click to expand...

yes and if we had custom roms and kernels too then we would have apps2sd without the need for 2.2
 
i wanna do all that crazy stuff like deoDEX, use app inventor, cook roms and stuff
i have no fear when it comes to technology
i also wanna be a cool Phone Guide and be all green
 
I know how everybody wants Froyo now, but what I think would be cool for me (until Froyo comes out), is just as close to a stock Android 2.1 ROM as possible. :P
 
You must log in or register to reply here.
Back
Top Bottom