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

Root Black Hat Question

Steven58

Steven58

Former Heavyweight Champion of Android Forums
Moderator
I saw a post saying you can deodex using Black hat. I d/l'd it for 1.99 and noticed that one can only d/l leaked roms. I didn't see how it deodexes for you. What am I doing wrong.

Ps; i did d/l r2d2 but that's all I did.

Steven
 
it has deodexed roms in it...so if you install one of those it would technically deodex your phone. But it doesn't have a deodex my phone button:D...
 
thanks bro. I d/l r2d2 so,

How do I install it?

and..

Is it possible to undo if I do install a custom rom?
 
go into rom manager, choose install rom from sdcard, find the r2d2.zip in the tbh folder, and choose backup before you install

Also make sure you repress bootstrap recovery in the droid x bootstrap app

and yeah you can undo it by restoring a backup
 
Steven you must have been a Guide for a different Droid before... with 10k+ posts and asking these questions I figured you are new to the X.
 
I know... for real.. my wife would kill me if I was on the computer / phone that much.. she hates my phone anyway, and she is the one that bought it for me for my b-day... haha, irony is a b.itch..
 
Hey, I remember Steven when he had less then a 1000 posts :) I was mostly lurking at that time :)We all had a good time waiting for incredible to be announced :)
 
jonathanmsims said:
I know... for real.. my wife would kill me if I was on the computer / phone that much.. she hates my phone anyway, and she is the one that bought it for me for my b-day... haha, irony is a b.itch..
Click to expand...

Our wives should get together, theyd have a lot in common. Between my phone and ps3...
 
used black hat to get the r2d2. tried it out. I liked it but it took too long to boot consistantly. Above that swype wouldn't work with it so I went back to stock 2.2 ota rooted....for now.

Interestingly enough, I got stuck in boot mode trying to install the rc file that supposedly takes blur out. So, I had to use sbf to get back in. It worked. I learned a lot. Now, I can make my way around. :)
 
Have they ever offered the OTA rooted deodexed? Not the leak, the actual ota with the new stronger radio.
 
Gareee said:
Have they ever offered the OTA rooted deodexed? Not the leak, the actual ota with the new stronger radio.
Click to expand...

That's what I am hoping for. I am running the 2.3.15 leak but am getting reboots (no big deal, only like 1x a day) when I unlock my phone.
 
SFWB said:
That's what I am hoping for. I am running the 2.3.15 leak but am getting reboots (no big deal, only like 1x a day) when I unlock my phone.
Click to expand...

You must come from a Blackberry and are used to the instabilities.

Man, 1x unplanned/unexpected reboot a day would drive me up a wall especially when I get it as I'm using the phone. I had my first and only random reboot from my DX several days ago, at night, when I wasn't even using the phone - I just saw it vibrate on the table when it booted up. That irked me.

It's a phone. IMO, a phone - as a tool I pick up and use daily - should be highly stable. I'd say it should be more stable than my computer - I don't mind deliberately rebooting it more frequently than my computer, but it'd better not crash.
 
binary visions said:
You must come from a Blackberry and are used to the instabilities.
Click to expand...

No, but I did have a WinMo phone for work that was the worst piece of technology I had the misfortune of using - ever.

Like I said, the reboots happen when the screen is locked and I go to unlock it. And it's only been once a day. If it happened in the middle of a call or something else, then I'd be losing my mind.

It hasn't caused a problem, yet...
 
The day my phone starts rebooting when I unlock it, even a couple times a week, is the day I SBF back to 2.1. Actually, the whole reason I didn't do the OTA upgrade to 2.2 (and went with the leak instead) was that my install of 2.1 was great - stable and fast. I like some of the features in 2.2 and am mostly happy with it but I'll be back on 2.1 in a heartbeat if it means no reboots.

I did a 2.1 -> 2.2 leak (2.3.9, I think?) -> 2.3.15 upgrade and about the only trouble I have is the battery manager occasionally force closing.

Anyway, glad you're happy, just thought I'd mention that there are lots of really stable phones out there and you shouldn't have to tolerate a daily reboot.
 
binary visions said:
You must come from a Blackberry and are used to the instabilities.

Man, 1x unplanned/unexpected reboot a day would drive me up a wall especially when I get it as I'm using the phone. I had my first and only random reboot from my DX several days ago, at night, when I wasn't even using the phone - I just saw it vibrate on the table when it booted up. That irked me.

It's a phone. IMO, a phone - as a tool I pick up and use daily - should be highly stable. I'd say it should be more stable than my computer - I don't mind deliberately rebooting it more frequently than my computer, but it'd better not crash.
Click to expand...

Then you may want to get just a phone and not a computer that can make phone calls. ;)

These are computers and you have the freedom to add and remove all sorts of things and probably have. So unless you are running strictly stock I don't think you have a right to complain its isn't stable because it rebooted once in the middle of the night. If its completely stock ...never mind ;-)
 
Having worked in IT for a long time now, I know that this is essentially a small computer. I am accordingly understanding of when and where it should be acceptable to become unstable.

To claim that the expectations should be set for instability is really selling the system short. There is no reason to have an expectation of instability. Yes, there is a lot you can do to decrease the stability of the system because the OS is fairly open and flexible, but there are changes that you can make where you should expect a decrease in stability (using SetCPU, modifying system files), and there are a lot of other changes (the vast majority) where the system should handle problems gracefully. Rebooting is not handling it gracefully. Force closes are graceful.

In the last, oh, maybe 5 years I can probably count on my fingers the number of times my home computer has crashed during use that required a reboot to become functional. Systems don't have to be unstable. I don't agree that having an open and flexible OS - and leveraging that fact - by necessity is going to cause crashes. A well designed OS will be robust enough to tolerate a certain amount of misbehavior from applications.
 
binary visions said:
Having worked in IT for a long time now, I know that this is essentially a small computer. I am accordingly understanding of when and where it should be acceptable to become unstable.

To claim that the expectations should be set for instability is really selling the system short. There is no reason to have an expectation of instability. Yes, there is a lot you can do to decrease the stability of the system because the OS is fairly open and flexible, but there are changes that you can make where you should expect a decrease in stability (using SetCPU, modifying system files), and there are a lot of other changes (the vast majority) where the system should handle problems gracefully. Rebooting is not handling it gracefully. Force closes are graceful.

In the last, oh, maybe 5 years I can probably count on my fingers the number of times my home computer has crashed during use that required a reboot to become functional. Systems don't have to be unstable. I don't agree that having an open and flexible OS - and leveraging that fact - by necessity is going to cause crashes. A well designed OS will be robust enough to tolerate a certain amount of misbehavior from applications.
Click to expand...

Well I to have worked in IT for a very long time and I agree with you. However the one big thing I see here is that it may be too open as any willy nilly can write and app. Is it the OS that caused the reboot or a poorly written app that didn't follow the rules? Hard to tell.

BTW my Dinc rebooted in stock form and I had a small problem with that (although a reboot once a week or so doesn't bother me) but once I started rooting loading ROMs and such I quite holding the manufacturer responsible for the reboots. And since I see you in this section I have to wonder if you are doing these things also and if its far to blame them.

BTW I've worked in TI long enough that I remember when things rebooted all the time. Maybe that's why I'm not to upset with a random reboot from time to time.
 
Piiman said:
Is it the OS that caused the reboot or a poorly written app that didn't follow the rules? Hard to tell.
Click to expand...

Of course. But if the OS is written well, it should resist rebooting when an app is misbehaving. You can't stop everything, but the vast majority of apps should be able to crash gracefully without taking out the entire phone.

And since I see you in this section I have to wonder if you are doing these things also and if its far to blame them.
Click to expand...

Certainly a fair question. I've got a good handle on what things will reasonably reduce reliability, and what things won't, so I wouldn't be objecting if I thought I was affecting system stability in some way.

In any event, I don't have any objection to the stability of my phone. I said the reboot irked me a bit, but I'm not calling Verizon about it or bagging on the phone because of it.

BTW I've worked in TI long enough that I remember when things rebooted all the time. Maybe that's why I'm not to upset with a random reboot from time to time.
Click to expand...

Sure. Things have come a long way, though. I don't see why currently-developed phones shouldn't be held up against the current state of computing. It's only 15ish years since Windows 3.11, but I'm not going to say, "well, it's better than things were."
 
You must log in or register to reply here.
Back
Top Bottom