Related
Hey guys, I have been using smart phones for a while and usually get around great without rooting. I had the HTC Dream back in the day and couldnt use it without rooting, lol. I am upgrading from the G1 which has met the end of the road for me. What are the benefits of rooting? With the Vibrant which I will finally have on Tuesday, is it necessary? And if it is HIGHLY recommended, how do I go about rooting it?
i would say root it cause its really easy takes not even 5 minutes seriously lol but i would also root it cause there is lots of bloatware on this thing so many apps that arent needed
I am not generally a rooter but this one seemed so easy (and it is) that I did it.
I didn't root the phone to dig into the files, I did it just so I could install stuff that I couldn't otherwise install. It bugged me to see a cool app and then read "YOU MUST HAVE ROOT ACCESS". That's not a problem anymore.
You certainly don't lose anything by rooting so I would say go for it.
Any other disadvantages/advantages
really there are no disadvantages accept maybe warranty but i think theres a way to unroot so no probs but once everything starts picking up there will be way more advantages than disadvantages
Besides the fact of removing awful apps (Bloatware), you can use your phone to tether. Also you can use an app called SetCPU to overclock your processor to actaully use your 1GHZ processor which speeds your phone up, along with a ton of other root apps. Youll be able to flash custom ROMS, flash themes, etc. Not sure if there is a volume hack for the vibrant yet, but that has been a reason for past rooted phones as well.
I highly recommend it...
AdFree Android removes nearly all ads from websites and apps
reasons to root
1. Use apps that require root access (such as Titanium Backup and Drocap2)
2. Remove preloaded bloatware (who needs TeleNav when Google Maps Navigation is totally free?)
3. Full access to filesystem (useful for developers and general tinkerers)
reasons not to root
1. Always involves some risk (however small) of irreversibly damaging your device
2. Could void warranty or official support
3. Makes it easier for you to accidentally mess up your system.
I only rooted my mytouch and g1 phones so i can get apps2sd, wi-tethering, and overclockcpu.
however, since the upcoming froyo update will allow most of that, i chose not to root for the time being. the phone is very fast and stable for my current needs and has an ample amount of internal memory. the only other reason to root for me would be to flash roms/themes because of my dislike for Samsung's TouchWiz.
it depends on what you ultimately want to get out of your phone.
ryan562 said:
I only rooted my mytouch and g1 phones so i can get apps2sd, wi-tethering, and overclockcpu.
however, since the upcoming froyo update will allow most of that, i chose not to root for the time being. the phone is very fast and stable for my current needs and has an ample amount of internal memory. the only other reason to root for me would be to flash roms/themes because of my dislike for Samsung's TouchWiz.
it depends on what you ultimately want to get out of your phone.
Click to expand...
Click to collapse
Same for me i had the g1 loved to root however i switched to unlocked iphone and now im back with the vibrant , the vibrant does everything i want now and the ease of the rooting might have me root if froyo is delayed by Tmobile or something.
Understood, also from reading I dont think there is a way to unroot the phone at all is it? And another ? since you all are being so helpful, is there already an app to at least see what speed your processor is running at. i know that task managers arent really needed, but some of them showed ur cpu speed as well as the load on it. is that something that anyone had an interest in and found. thanks for all of you all's help
Hmm, still debating on rooting. Waiting for my Froyo update. Plus I want to port my Harley-Davidson theme I made for my G1 to Vibrant. Hopefully they don't use those CRAMS files on Vibrant, cause that is when I had to stop themeing my G1. CRAMS was too difficult to mess with. Is the signing file method gonna be the same as G1, or is there a different testsign file? Plus I hope to see my stock file, plus a thinned down, less bloatware file, and themeing templates. So many factors to consider.
I say ROOT! I've never rooted a phone till this one. I just couldn't stand all the bloatware that was in this phone. They just had to be removed. Now all I'm waiting for are some sick ass ROMs I've seen done for other devices to hit this one. I'm sure I'll need help doing so, but this community has been fantastic when help is needed.
Plus side for me is that I also have a 3 week old New still in the box Nexus One as a backup phone in case I screw this one up.
I rooted mine because people kept saying you could tether, but none of the tethering apps actually WORK. They install fine, and Wireless-Tethering says it's working, but the access point never shows up. And Wired-Tethering says the kernel isn't compatible.
So I'd like to hear from any rooted users who actually got them working AND successfully tethered a laptop with it.
talltexan said:
Same for me i had the g1 loved to root however i switched to unlocked iphone and now im back with the vibrant , the vibrant does everything i want now and the ease of the rooting might have me root if froyo is delayed by Tmobile or something.
Click to expand...
Click to collapse
if there's any delay on the froyo update, i'd blame it on samsung
I was hoping not to have to root the phone so soon - especially until I could reset it back and a recover like Amon's is available, but after a glorious couple of days of honeymoon, the lags are just killing the experience for me. And I don't think I have a choice now, but to root. I'll try a general reset and see if it works. I have another Vibrant that seems to be only slightly laggy. But I have to return that one and keep the problematic one :-(
Even moving icons on the desktop now takes almost 2 second. Linpack still clocks at 8.5. No problem at all playing a video - just OS operations. The camera froze for 5 minutes and I finally had to just restart the phone. Restarting the phone is not painful on this device though. Very fast.
At this time so early in Vibrant development.. it honestly doesn't really make much of a difference if you root early or root later. Just enjoy the phone for what it is as of right now until the modding community becomes settled in. Just be aware if there are any incoming OTAs if you are unrooted to make sure that the OTA didn't do anything that would change the rooting process.
- Recovery (ability to flash custom ROMs) is in the making
- Custom ROM developers -- in the makes soon
So here's the question. Should I go ahead and invest on a Vibrant (but work for it will begin when I get the Slide done) cont... about 7 hours ago via HTC Peep
If I keep getting the donations I am now, I can get the laptop along with the Vibrant, just considering the Vibrant first ...cont about 7 hours ago via HTC Peep -WesGarner
Click to expand...
Click to collapse
I would personally go ahead and root it to unlock some essential applications and it takes <1 minute to do and its pretty simple. But there isn't any rush to root it now or later.. not at least CyanogenMod6 (Android 2.2) gets released for this beastly phone to have JIT.
nm found it
N8QDogg said:
Understood, also from reading I dont think there is a way to unroot the phone at all is it? And another ? since you all are being so helpful, is there already an app to at least see what speed your processor is running at. i know that task managers arent really needed, but some of them showed ur cpu speed as well as the load on it. is that something that anyone had an interest in and found. thanks for all of you all's help
Click to expand...
Click to collapse
With the root method given so far, I think the only thing you have to do to unroot it is to remove Superuser Permissions. That's the only thing that the root procedure added to the phone.
I'm rooting my phone when I get it, just because to me (at least) it is a part of the true android experience. I'm just geek enough to like to play with my equipment! Hurry up T-Mobile!!!
I know this topic must have been beaten to a bloody death, but as a former G1/Cyanogenmod user, I'm starting to debate whether or not I should root my G2. My G1 always gave me problems when I was running Cyanogenmod. This is likely due to the now low-end specs of the device, but I have grown wary of custom roms, regardless. I can't help but worry that my device may become unstable or slow like my G1, and that I might have difficulty restoring to factory state if I need to take advantage of my warranty.
One of the primary reasons I wanted a rooted device was to be able to effectively tether. Now that my G2 has this built in, there's one less point for rooting. I don't much ever plan of going out of the country, so I have no need for a SuperCID. I don't yet see any cool toys for G2 root users, like a USB host-enabled driver. Also, my main reason for rooting my G1, apps on the SD card, is now built-in, no partitioning required.
This isn't to say that I don't appreciate all the hard work that's gone in to making this option available. I just don't know how it can apply to me.
So tell me, why do you root, what do you geek out with using root, and what do you most often use your root for?
The simple answer is don't root then. I have rooted and flashed the hell out of every android device I've ever owned, until this one, and to be honest I wouldn't mind having just having root on this, which has now gone since the latest ota, but other than that, I have no intention of flashing anything on it as it seems to be just fine for my use. The root access I want for apps like shoot me and clock sync that I use regularly now. It would be nice to have a phone and just use it, rather than spending all my time setting it back up after each new Rom I've tried on a weekly basis. So, unless you need to, don't.
So cool posts here. I have to agree. I used to geek and tweak and check out ROMs on my TP2, too. I always ended up stock WM6.1(!) because that worked best. Now coming to Android and the DZ I am just shocked how badly this RULEZ. I don't feel like tweaking anything. I wouldn't fear losing warranty, I just don't wanna root yet. Well, I miss my front cam and the qwerty keys could be bigger )
Sent from my HTC Desire Z using XDA App
root/S-OFF is useful for me right now so that I can do a nandroid backup of my phone from time to time (via Recovery Manager/Clockwork). I am very happy with my stock ROM (HTC 1.34), which is a big change from my previous WinMo Touch Pro 2, where the stock ROM sucked big time.
If you don't feel like you need root, then don't do it, simple as that !
Still havent rooted and I seem to be happy with the stock rom of the Desire Z. Still waiting it out but I do miss some of the other apps that require rooting.
I eventually will root my device and get over the fear of bricking my unit. Are there any official updates happening?
Sent from my GT-P1000 using XDA App
kuplet said:
I eventually will root my device and get over the fear of bricking my unit. Are there any official updates happening?
Click to expand...
Click to collapse
There is a 1.72 OTA update for the Desire Z which is being pushed out. I don't know exactly where you are in the world, but this has certainly been rolled out in Europe. However, be careful, because right now rooting that updated ROM is not possible, and unless you have full radio S-OFF via gfree beforehand, you can't downgrade either once you put it on.
The "RELEASE" versions of Cyanogen have been stable as hell. Running CM 6.1.1 now. So if that's the reason why you're not doing it, take my anecdote for what it's worth.
If you don't want to root or use any of the custom ROMs then don't do it. It's your decision, not ours.
One of my biggest reasons for rooting is SetCPU. Right now, I can get my phone to last about a day and a half with minimal to moderate use. Days of heavy use it'll last at least 12hrs.
I also like having access to the system files in case I feel like messing with them.
Besides, rooting doesn't mean you have to flash a custom ROM. You can have a rooted phone with a stock ROM.
In my recent mental debate over the EVO 4G LTE vs. the Nexus, I've pondered the differences between stock ICS (pure/vanilla/etc) and the ICS we will see on the One series by HTC, including our very own EVO sequel. From the few screenshots I've seen of the One X, it does not remotely resemble the ICS I've learned to know and love with the work our devs our doing to bring the latest and greatest to the OG. Examples include the lockscreen (the Sense ring appears to still be the default one - is there an option to go straight ICS for the lockscreen?), the dock (I'm sure I can switch the launcher to fix this issue...), the notifications pulldown (I've actually not seen the Sense one yet, but I've heard various things indicating it is different from the one I'm no accustomed to), etc. Heck, even the color of the battery meter is green instead of blue!
Does anyone know or at least have an idea if we can change some of those things without rooting our devices? Having a brand new device, I don't plan on needing to root (or at least install custom ROMs, that is) for a while. But I am already missing the slick new interface Google has provided. While many claim that Sense 4.0 is going for the minimalistic approach to the latest iteration of their infamous skin, why do I feel like they have completely altered a widely praised operating system that has barely rolled out? I'm a little saddened when I see the video of the EVO 4G LTE and feel like the look of everything is dated.
But then I look at the hardware, think about the devs who'll inevitably move to this phone, and that excites me about the possibilities. I guess I'm more curious than disappointed, but I was wondering others' feelings on this topic.
Long answer short, you'll get aosp, miui and sense on the HTC which is nice if you get bored and want something different.
Sent from my PC36100 using XDA
alaman68 said:
Long answer short, you'll get aosp, miui and sense on the HTC which is nice if you get bored and want something different.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Can you make your short answer slightly longer? Haha how would I get AOSP and MIUI on the EVO LTE? You mean one devs get to work on it? Or stock?
Sent from my PC36100 using XDA
PsiPhiDan said:
Can you make your short answer slightly longer? Haha how would I get AOSP and MIUI on the EVO LTE? You mean one devs get to work on it? Or stock?
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Right. Not stock, would have to be rooted. My bad. The devs will be all over that phone anyway so it will be a blast
Sent from my PC36100 using XDA
It's a *good* thing the phone comes with Sense, its one more option you have, and Sense does add some useful features. Custom rom's will offer all kinds of options including optimized and bloatware free versions of Sense.
alaman68 said:
Right. Not stock, would have to be rooted. My bad. The devs will be all over that phone anyway so it will be a blast
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Completely agree. I'm kind of thinking of galaxy nexus, cuz I'm not fond of sense. But, I'm sure in no time we'll be able to rip sense OFF that SOB and put AOKP or some other variant of vanilla ICS.
Then, if you wanna run sense for a few days, that option will still be there. It's win-win.
Sent from my PC36100 using xda premium
If I'm running Sense 4.0, do you think I'll still be able to get the Quad ICS unlock screen, or something like that? I LOVE that lockscreen - way better than the silly ring that Sense creates. I don't understand why they didn't change that from 3.0 and 3.5 to something fresh. Oh, I would assume I have the "unlock with face" option too on this phone? It's been so long since I ran Sense, I forgot if these things are changeable or not!
My only concern with the custom ROMs is whether things will run okay, like camera and such. Also, if you are running AOSP, you'll miss out on the supposedly amazing camera suite that Sense 4.0 provides, right?
Tough choice!!!
Sense 4.0 + ICS ALL DAY!
Sent from my PC36100 using XDA
I went to tmobile today and toyed with the one s. I will say it isn't the ICS we know from the current development but it is beautiful and sleek. The soft keys are a bit cumbersome but I could get used to it. I am in no way drawn away from the evo lte and am more than anxious to own that device!
Sent from my PC36100 using xda premium
imheroldman said:
I went to tmobile today and toyed with the one s. I will say it isn't the ICS we know from the current development but it is beautiful and sleek. The soft keys are a bit cumbersome but I could get used to it. I am in no way drawn away from the evo lte and am more than anxious to own that device!
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
That's awesome, especially considering the One S is inferior to our EVO we're getting...
Sent from my PC36100 using XDA
Well I will answer my own question at this moment, because I stopped into a T-Mobile and played with the One-S for about 10 minutes. It appears that ICS as we know it is VERY coated by Sense, but not necessarily in a bad way. It is still beautiful, just very different. I noticed that there were no quick settings in the notifications menu, which is one thing I was very curious about. But overall, really nice and REALLY amazing! Considering that is the crappy version of our EVOs, I cannot wait for this thing. The One-S screen was awesome, and I know it can't touch the screen (both size and resolution-wise) of our new toy coming out. But the UI was terrifically smooth, the feel was nice (physically), and Sense was overall not intrusive. It was just omnipresent. I'm not disappointed at all - and I know the devs will give us amazing options in terms of removing Sense, or tweaking Sense to give us cool features like quick settings and slide to change brightness.
I can't wait until the One-X is out so that I can play with that one, since it will give a much more accurate portrayal of our experience we can expect. May 18th can't get here soon enough!
I'm posting this everywhere . Its a post by toastcfh over in the oneX forums about how much HTC locked the phone down. Among many things, it is impossible to mount SD from recovery due to their locking, even with custom recovery and HTC dev unlock. If toast says it, it is so, I mean, the guy is an Android/Linux GENIUS. he's the one that had the Evo root method instructions posted before launch day.
Quote.....
no, USB mount does not work in recovery. It appears to be locked out in recovery mode. the workarounds to get it working are one of two things.
(1) fastboot boot awesomeRecovery.img (this works because fastboot then boots recovery on the boot/temporary partition. So the you're not actually in recovery mode
(2) Offmode (this works because again you're again not technically in recovery mode. It uses the recovery ramdisk, kernel, and binaries but its still not technically recovery.
On that note I've seen suggestions that it's possibly a recovery issue with cwm and twrp. Unfortunately it doesn't appear to be the case. If it were then in CWM u wouldn't have usb when u fastboot boot the recovery or in offmode (fair assumption since both these options use the same kernel, ramdisk and binaries as recovery?). Can it be fix? Not that i know of. It looks to me like a total radio or bootloader lockout from using USB in recovery. Which means on a radio or bootloader level USB is disabled in recovery mode.
On that note I think we should raise the point to HTC that this locking down of the device does not suite our needs.Key points of fail would be as follows.
(1) Can NOT flash the boot partition from recovery. I've personally contacted HTC on this numerous times and they seem to just not care. Responding with "It's a security issue" and so forth. I would love to know how this is a security issue of any sort. Every other Android device has this ability except HTC devices since they started the HTC unlock ordeal. It's utter fail IMHO and HTC should listen to our needs .
(2) Can NOT flash recovery or boot partitions from system. This issue is NOT a deal breaker and isn't so bad when it comes down to the nitty gritty. But since the issue above exists, flashing with applications like htc dumlock and such were our only options. These work around apps cant be used to flash now because of the lockpout from system and it wouldn't be such an issue if HTC didnt lock us out in recovery from flashing boot.
(3) Can NOT flash P*IMG.zips in hboot/bootloader anymore. For the unlocked device running a custom firmware this is a must. Specially when radio updates and such are needed from the OEM. We seen a big use of this on the Sensation when HTC updated the device from Gingerbread to Ice Cream Sandwich. The update required new hboots, radios, and partitioning to actually use. So in that instead of having to flash a RUU Which didn't exist the only choice was to flash a custom P*IMG.zip that included all the radios and images need to run the builds. At this point we can't update those image/partitions without flashing an RUU. This makes no since and doesn't seem to do anything but make things more difficult on the unlocker to customize and modify their device.
(4) If all the conditions above HAVE to exist. Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
(5) WHAT WAS THE POINT OF HTC UNLOCK? I was to reach out and except us as a community. It was to keep us from having to exploit their firmware and look for holes to gain control of a device we rightfully own. WHAT DID HTC UNLOCK DO? It unlocked the devices at first and with each new revision of the unlock it gets more locked down and harder for us to use it as intended. WHAT DOES THAT LEAD TO? It leads to us hoping someone will take the time out of their life and exploit HTC's firmware so we can have access and control of our devices. I mean, it's bad when u have people poking a device with a paperclip to get a device unlocked to avoid a official unlock.
Bottom line; I'm personally fed up with HTC's unlock. It's absolute crap! It does not serve the purpose it was intended and only makes things harder then they were before. As a devoted HTC customer it has me questioning if my next device will be an HTC. With all the other options that would allow me to spend less time trying to gain proper access to my device and more time actually having fun with it, why choose HTC? Everyone else is shying away for these same issues. Everyone with an HTC unlocked device waits for someone to exploit HTC's firmware and give them a proper unlock. Why not just choose a device without the locked down/unlock instead? IDK but HTC needs to step up and listen to us. Every HTC forum with an HTC Unlock is screaming for these issues to be fixed.
My call to HTC is to fix these issue and/or give us proper documentation on flashing firmware to our devices via custom recoveries. The boot flashing lockout is dumb, pointless, and in NO WAY a security threat AT ALL and is nothing more then a CRAP RESPONSE to something that they sould be working to correct, instead of ignoring. In the end its hurting HTC's relations with developers and is ultimately doing the opposite of what it's original intent.
HTC, PLEASE READ AND LISTEN!!!11ONEone
To everyone else, SPREAD THE WORD!!!ONEone
End quote.........
There has to be a way to petition HTC. Reading this is making me lean galaxy Nexus, ...and I F$%kin HATE Samsung.
Edit: this post is from the One X forum TWRP topic.
Sent from my PC36100 using xda premium
No way I'm buying a Samsung phone.
I'll trust that someone will figure out how to get around the issue at some point. I love how the phone is stock anyway.
Sent from my PC36100 using XDA
PsiPhiDan said:
In my recent mental debate over the EVO 4G LTE vs. the Nexus, I've pondered the differences between stock ICS (pure/vanilla/etc) and the ICS we will see on the One series by HTC, including our very own EVO sequel. From the few screenshots I've seen of the One X, it does not remotely resemble the ICS I've learned to know and love with the work our devs our doing to bring the latest and greatest to the OG. Examples include the lockscreen (the Sense ring appears to still be the default one - is there an option to go straight ICS for the lockscreen?), the dock (I'm sure I can switch the launcher to fix this issue...), the notifications pulldown (I've actually not seen the Sense one yet, but I've heard various things indicating it is different from the one I'm no accustomed to), etc. Heck, even the color of the battery meter is green instead of blue!
Does anyone know or at least have an idea if we can change some of those things without rooting our devices? Having a brand new device, I don't plan on needing to root (or at least install custom ROMs, that is) for a while. But I am already missing the slick new interface Google has provided. While many claim that Sense 4.0 is going for the minimalistic approach to the latest iteration of their infamous skin, why do I feel like they have completely altered a widely praised operating system that has barely rolled out? I'm a little saddened when I see the video of the EVO 4G LTE and feel like the look of everything is dated.
But then I look at the hardware, think about the devs who'll inevitably move to this phone, and that excites me about the possibilities. I guess I'm more curious than disappointed, but I was wondering others' feelings on this topic.
Click to expand...
Click to collapse
There IS PLENTY of apps on the play store that offer home screen and lock screen customization, such as launcherpro, milocker, gosms, as far as changing the status bar and battery bar i'm not so sure, i haven't been on a phone with s-on in a while and can't tell you what rootless tweaks would work
Hi everyone,
Recently, a friend gave me my first Droid phone. It is a Droid2 A955 which had 2.3.20, and a cracked digitizer. My intentions were to get this device functional and rooted before replacing the digitizer. Well, like a tard, I let the device update to 2.3.4, and like an even bigger tard, I attempted to load the 2.3.3 SBF without doing my research first. Oops. Wait, scratch that. Big oops.
Now I am sure all of you know what the end result of that was, and you don't have to rub my head in the sand over it because I've been doing that for about a day now myself!!!
Either way, I have found someone who is willing to sell me their "went to collections" Droid2, with accessories, extra battery, and whatnot for around $50.. Their Droid2 already has Gingerbread 2.3.3 on it. I got him to give me the MEID, and I changed the MEID through VZW site on my "spare phone", and had him *22899 to OTA. All was successful, so it is free and clear for me to immediately activate and start using.
Here is what I need to know before I go messing with this phone, because I definitely can't afford to FF the bits on this phone up, especially when I'm having to pay for it, if you know what I mean!
1. From research, Droid 2 Gingerbread 2.3.3 can be rooted. How complex of a task is it? In fact, exactly what does "root" allow one to do? About the only real goal I have is to sparingly tether my laptop via wifi without having to sacrifice my soul to Verizon each month.
2. I understand that this phone will "nag" you to 2.3.4 and will automagically do the update if you don't stop it in 30 seconds, very much like my Droid2 did. What can I do to permanently disable the 2.3.4 update check once I have this functioning 2.3.3?
3. There is supposedly an "X" button that you push with the power button to enter RECOVERY MODE... Just what, exactly, is the "X" key?
I don't want another repeat of the D2.3.7 MEM_BLANK screen.
Actually, playing around, I was able to take the D2.3.7 down to D2.3.5, but unfortunately it still refused to take the stock Froyo flash or the 2.3.3. Is there earlier "bootloaders" SBF's out there that can be loaded into the Droid that *maybe* will allow us to unbrick them? When the memory is blank (according to MEM_BLANK), what is preventing the phone from committing the flash?? Mine stops at 99% and cries about something dealing with "BP". As if the bootloader is refusing to commit the flash to ROM after being uploaded into the phone's RAM.
Either way the Bootloader Screen displays Battery Low, so I'm spent trying to revive this device until I get the other one from my friend tomorrow.
I don't understand what is part of this Bootloader that is preventing us from fixing this. Better yet, I can't understand how Motorola would do such a shameful act of sabotage against their customers. I've been a hardcore Motorola fan since the StarTac/TimePort days, and Motorola has always been my #1 phone of choice. Not just because of its stability and reliability, but how easy they are to "monster flash" back to factory when things go crazy. Maybe I should just stick with my Razr MAXX and be a happy little boy.
I have noticed the 2.3.4 Gingerbread has been leaked for the Droid2 Global. It is not compatible with the regular Droid 2, unfortunately, and I hope that enough people are interested in restoring these bricks that some solution is released to bring them back to life.
I am reading that people are taking "backup repair" ROM's and storing them to the MicroSD card, and successfully wiping .621 from the device and reverting to a previous version. What is the odds of getting a "backup rom" from a 2.3.3 Gingerbread, or whatever device, and using that backup to unbrick the bricked pones because of .621? I don't know, because my experience with the Droid involved about 3 hours before I was at the Bootloader error screen. LMAO!
I am just trying to throw some ideas out there, because, the last time I flashed firmware on a phone, it was the Motorola V710, E815, RAZR, RAZR MAXX, v325(i), and a slew of LG's. The last "Smartphone" I flashed was the XV6700 (that WM5 phone was hilarious with the Apache WM6.0 code on it). So, as you can tell, I'm a little behind on the times, but I'm not too far behind you guys.
I thought about calling and complaining that this update "screwed my phone up" but I am also concerned if I have to return the core of this phone, and they see how bad the digitizer is in, I'm going to get a heaping bill. Either way it worked fine with the cracked digitizer, it was ultimately their software that crashed the device. Guess I could order and replace the digitizer and get them to replace it, but I'm not 100% positive they would still replace the device since it's technically not "under warranty." May be one of those "I'm out of contract you make this right or US Cellular is opening us with open arms"....
PS-- I used to be a VZW Customer Support/Service Techican. Back in my day we could get whatever firmware we needed through NetAce from "InfoCenter", not just for Moto phones, but LG and all the other devices as well. On some "returns" we had no choice but to do a factory "Monster Flash" in order to rid of the previous customer's data and bring the phone back to virgin status. I don't know how things are inside the Tech's office these days, though. Maybe I should call my Service Techs who still have jobs and see what they can do (I prefer not to get them involved because I don't want them risking their job).
I've also replaced many of the digitizers in these Droid 2's for my friends. They're a pain in the @$$, but retail on these puppies aren't exactly cheap, either.
Any advice you guys can give me would be greatly appreciated. Also, please be honest with me. Don't sugarcoat ****. If you guys don't think this phone is going to work right under "root" conditions with 2.3.3, or the phone simply isn't worth $50, please let me know!
Thank all of you!
Droid Root 2.3.3
Thanks for your help guys.
I have the Droid, same Bootloader 2.3.7 as my bricked one, but it is at Gingerbread 2.3.3.
I was able to get "MotorolaOneClick" to load Superuser to the device.
Now there are two things I need to accomplish
1. Unlock tethering
2. Disable device from taking 2.3.4 OTA
I think if I can get these two things taken care of, I'm golden.
You can find everything you need to do both if you search the site. Shouldn't be a problem.
Reading
I am pretty sure I have taken care of preventing update to 2.3.4.
But I am still having trouble getting tethering to properly work.
Downloaded the Wifi Tether.
Still get paywall screen.
Close Wifi Tether.
Get paywall screen through the phone!!!
Have to reboot.
Also out of curiosity, does the speaker (not speakerphone) sound like you need a hearing aid??? The speaker in this Droid 2 is absolutely horrendous, sounds like I'm trying to listen to an XV6700.
Soft Speaker!
OK, I think the speaker is ok in this phone, but I am determined this mesh screen covering it is completely clogged. Time to get a fresh box cutter (closest thing I have to an xacto knife at the moment) and carefully cut this thing out. I don't have a T3 at the moment, and quite frankly, I don't want to tear 5 or 6 layers apart to tear this clogged screen out!! Either way, if things go sinister, I still have the busted up Droid 2 to take the speaker out of (Or the entire ribbon from what my research reveals).
I can tell you this much. I wish I had the previous owners set of ears. I bet he could hear a pin drop a mile away if he was able to hear the sound out of this thing. Then again, I am used to volume levels from REAL Motorola phones, I was swapping between the v325i and Razr MAXX previous to this Droid 2, and was truly expecting the same sound quality with this phone.
Done
So I finally got tethering enabled without having to sell my soul to Verizon. There really wasn't a clear-cut way of doing it. But here is what it took.
1. Install Droid 2 Recovery Bootstrap v1.0.0.3.apk
2. Place TBH_D2_Tether_Patch_1.0.zip in root of SD Card.
3. Run the Recovery Bootstrap, then reboot (through the Recovery Boot program).
4. Install the ZIP from SD Card.
a. It makes 4 NV changes.
5. Reboot and exit from the Recovery Bootstrap.
Now I can tether through the built-in 3G Hotspot app, and the "Wifi Tether" app I downloaded also works and doesn't send the cellphone to the paywall.
PS---How do you guys communicate through these forums??? Just trying to get the captcha right takes like 45 minutes.
Hi, all!
I bought the Blade X Max from Cricket, as it's got 32GB internal storage, a bigger screen, and seems a very hip machine.
Since Cricket seems to have instructed the various vendors, LG, Alcatel, and now ZTE to not only just make it difficult to root, but near-impossible, at least for someone without extensive knowledge as an Android dev, it's an annoyance...
There are legit, non-bootleg apps for which I spent good money (Titanium, Apps2SD Pro, FlashFire and others), which require root... Unlocking codes tend to be expensive, and the sites that offer them seem more spam-generators than anything else, and the Dr.Fone Root tool doesn't seem to even know the device exists, and, it's as yet not on their supported list, that I can see.
The device was released a month ago, so I'm not expecting immediate miracles, but wondering if anyone else owns the device, and if anyone with the dev chops would be interested in exploring the possibility.
Thanks for reading, and have a great day!
I own the ZTE Blade X Max as well, I havent tried root or anything else yet, I was a little surprised though when searching through XDA and this thread was all I found in relation to the ZTE Blade X Max.
XperianceIT said:
I own the ZTE Blade X Max as well, I havent tried root or anything else yet, I was a little surprised though when searching through XDA and this thread was all I found in relation to the ZTE Blade X Max.
Click to expand...
Click to collapse
Well, since the device has only been around a few months, it's understandable that not a lot of the devs have access to one, but, yeah... All over the web, it's referred to as a carrier-branded phone, and people seem to not want to fiddle with it...
I don't need a custom ROM, but there are legit apps that I bought from the Play Store, and they require root...
I blame Cricket for being paranoid that someone would dare to customize her/his phone and tweak it... Times past, Cricket made it difficult to root a phone, but the LG G-Stylo was pretty much unrootable... I have a few paperweights of that model in my storage... The Idol 3 was able to be rooted, the 6055U Idol 4, not so much... and now this one... It seems that Cricket is trying to have the various manufacturers leave some things out of their flavors of Android, so that even someone who reasonably is willing to take the risk is sh!t out of luck... <sigh>
Yeah Cricket has been making it real hard to root any of their phones. I also have the Stylo 2, and they had lg remove the entire bootloader and stock recovery, how the hell that was possible is beyond me. Get used to this trend in Android, it's not just Cricket, allot of flagships are doing what they can to get rid of the ability to root, cause if we root we have control not them, and the manufacturers are making way to much in terms of ad revenue to allow us to have total control. My Blade X Max will sometimes randomly download apps and games without my permission, that's how they ( manufacturers ) make the money they do, we are basically walking billboards for them. So unless enough people get together and complain about the blatent abuse of the GPL Linux has laid out, it will never change, open source my ass, try getting the real source code for this phone, won't happen. I downloaded the source for the max x 2 and dug into the files, wasn't even the full code, and had junk files from dead devices. The Android world is not what it's supposed to be, get used to it.
zMILWAUKEE said:
Yeah Cricket has been making it real hard to root any of their phones. I also have the Stylo 2, and they had lg remove the entire bootloader and stock recovery, how the hell that was possible is beyond me. Get used to this trend in Android, it's not just Cricket, allot of flagships are doing what they can to get rid of the ability to root, cause if we root we have control not them, and the manufacturers are making way to much in terms of ad revenue to allow us to have total control. My Blade X Max will sometimes randomly download apps and games without my permission, that's how they ( manufacturers ) make the money they do, we are basically walking billboards for them. So unless enough people get together and complain about the blatent abuse of the GPL Linux has laid out, it will never change, open source my ass, try getting the real source code for this phone, won't happen. I downloaded the source for the max x 2 and dug into the files, wasn't even the full code, and had junk files from dead devices. The Android world is not what it's supposed to be, get used to it.
Click to expand...
Click to collapse
Indeed...
Next time around, going to buy a pre-unlocked device (hell, even our local Walmart Super-aircraft hangar sells 'em), and just have the device ported over... if the vendor (Cricket, Metro, whomever) won't do it, they don't need my business... I'm a write-off from years back with Verizon, and, although my credit rating is much better these days, I worked for a Sprint call-center, and they sucketh verily and forsooth, and I don't know much about AT&T proper, or many other vendors...
But there are some vendors that are generally pretty hip, if a bit expensive, and I'm looking into seeing if, even if this is a vendor-branded device, there's a way, or just a straight-up trade for a device I can work with... Cricket's Android Nougat flavor is buggy as hell, and this is just kinda silly.
<sigh>
What the hell...
"Oh, Brave new world that hath such people in it.."
Wow are you serious? No root method? I'm going to have to sell this phone? WTF I just liked it.
Sent from my Z983 using Tapatalk
justlovejoy said:
Wow are you serious? No root method? I'm going to have to sell this phone? WTF I just liked it.
Sent from my Z983 using Tapatalk
Click to expand...
Click to collapse
Well, apparently the bootloader's crippled, as Cricket seems to have insisted things be removed from ZTE's source code...
But, I'm wondering (though I might just be talking out my butt), if the code module could be extracted from ZMax Pro, as that's apparently its non-Cricket branded twin...
My coding chops are limited to old XBASE and a bit of Delphi/FPC, so I'm not the guy to do it, but am I in the ballpark with my idea?
Never really messed with the bootloader. I've always been developing from code tho. Haven't tinkled too much in about a year but need a laptop power cord before I can try anything. Bootloader isn't always a root blocker. It's more of a custom rom blocker if memory hasn't been affected by times changing
Sent from my Z983 using Tapatalk
justlovejoy said:
Never really messed with the bootloader. I've always been developing from code tho. Haven't tinkled too much in about a year but need a laptop power cord before I can try anything. Bootloader isn't always a root blocker. It's more of a custom rom blocker if memory hasn't been affected by times changing
Sent from my Z983 using Tapatalk
Click to expand...
Click to collapse
Well, again, my chops are decades old, and tend to involve xBASE and Delphi coding, and I know very little about C/C++ and Java, and plead ignorance of what Cricket has insisted on having crippled in the source, and I lean on the expertise of devs here and elsewhere for that reason...
Just that it's one helluva device, or would be if it could be at least rooted.... I just don't know how... :laugh:
pauljulian said:
Well, again, my chops are decades old, and tend to involve xBASE and Delphi coding, and I know very little about C/C++ and Java, and plead ignorance of what Cricket has insisted on having crippled in the source, and I lean on the expertise of devs here and elsewhere for that reason...
Just that it's one helluva device, or would be if it could be at least rooted.... I just don't know how... [emoji23]
Click to expand...
Click to collapse
Facts!
That's what the kids say today, lol. It's a beauty. Had to get mine swapped out for another due to the fingerprint reader and camera being intermittent between reboots. Not much I can say wrong about this device. Waiting on the key to the mailbox for my laptop charger still. Can't promise anything yet but I'm hopeful that our resources will get us started, even if it's just a long list of what doesn't work. Lmfao
Sent from my Z983 using Tapatalk
Is there anything we can do to this phone? Any thing
Sent from my Z983 using XDA-Developers Legacy app
Yes I have z982 and would like a forums section
Bootloader and recovery
zMILWAUKEE said:
Yeah Cricket has been making it real hard to root any of their phones. I also have the Stylo 2, and they had lg remove the entire bootloader and stock recovery, how the hell that was possible is beyond me. Get used to this trend in Android, it's not just Cricket, allot of flagships are doing what they can to get rid of the ability to root, cause if we root we have control not them, and the manufacturers are making way to much in terms of ad revenue to allow us to have total control. My Blade X Max will sometimes randomly download apps and games without my permission, that's how they ( manufacturers ) make the money they do, we are basically walking billboards for them. So unless enough people get together and complain about the blatent abuse of the GPL Linux has laid out, it will never change, open source my ass, try getting the real source code for this phone, won't happen. I downloaded the source for the max x 2 and dug into the files, wasn't even the full code, and had junk files from dead devices. The Android world is not what it's supposed to be, get used to it.
Click to expand...
Click to collapse
First off they can't remove the bootloader as android WON'T boot without it, and recovery is needed for factory resets. Cricket has never been helpful about supporting their phones, but of you do a search you can find out how to get into the recovery. (And it's the ZTE Blade ZMax, not X Max, X Max is just crickets version of the Blade ZMax)
To get into recovery you can go to this link for instructions
http://www.hardreset.info/devices/zte/zte-blade-x-max-z983/recovery-mode/
revjamescarver said:
First off they can't remove the bootloader as android WON'T boot without it, and recovery is needed for factory resets. Cricket has never been helpful about supporting their phones, but of you do a search you can find out how to get into the recovery. (And it's the ZTE Blade ZMax, not X Max, X Max is just crickets version of the Blade ZMax)
To get into recovery you can go to this link for instructions
http://www.hardreset.info/devices/zte/zte-blade-x-max-z983/recovery-mode/
Click to expand...
Click to collapse
Have always been able to get into the stock recovery, and the download mode... those are not the issues, friend....
Whatever Cricket specified be done to their stock ROM by ZTE, we're blocked from doing those things that would enable us to actually use legit apps that we paid real money for.
I don't care about any sort of custom ROM, as these days, I really don't have the time to **** with it... But I've been an Android user for years... I've no problem rooting a device, given a workable method, and at least nutshell instructions, and doing a few things, as a user... As long as there is a way to get back to Square 1, should I screw up, I'm not afraid to explore, and, again, I believe in supporting good developers... If an app does what I want it to, I buy it, as long as it doesn't break the bank... in that case, I uninstall and find something better or cheaper...
But Cricket, in their either paranoia, or control freak attitude has been progressively making their devices less and less possible to do what we bought them for, unless we happen to be Cricket employees, sworn to secrecy regarding those codes beneath and behind the *# ones that really don't do much, at least not the ones we need to use, such as the menu option for "unlock" which doesn't without other input...
pauljulian said:
Have always been able to get into the stock recovery, and the download mode... those are not the issues, friend....
Whatever Cricket specified be done to their stock ROM by ZTE, we're blocked from doing those things that would enable us to actually use legit apps that we paid real money for.
I don't care about any sort of custom ROM, as these days, I really don't have the time to **** with it... But I've been an Android user for years... I've no problem rooting a device, given a workable method, and at least nutshell instructions, and doing a few things, as a user... As long as there is a way to get back to Square 1, should I screw up, I'm not afraid to explore, and, again, I believe in supporting good developers... If an app does what I want it to, I buy it, as long as it doesn't break the bank... in that case, I uninstall and find something better or cheaper...
But Cricket, in their either paranoia, or control freak attitude has been progressively making their devices less and less possible to do what we bought them for, unless we happen to be Cricket employees, sworn to secrecy regarding those codes beneath and behind the *# ones that really don't do much, at least not the ones we need to use, such as the menu option for "unlock" which doesn't without other input...
Click to expand...
Click to collapse
... and just to say that I know that "unlock" and "root" are two different things... was just an example.
pauljulian said:
Have always been able to get into the stock recovery, and the download mode... those are not the issues, friend....
Whatever Cricket specified be done to their stock ROM by ZTE, we're blocked from doing those things that would enable us to actually use legit apps that we paid real money for.
I don't care about any sort of custom ROM, as these days, I really don't have the time to **** with it... But I've been an Android user for years... I've no problem rooting a device, given a workable method, and at least nutshell instructions, and doing a few things, as a user... As long as there is a way to get back to Square 1, should I screw up, I'm not afraid to explore, and, again, I believe in supporting good developers... If an app does what I want it to, I buy it, as long as it doesn't break the bank... in that case, I uninstall and find something better or cheaper...
But Cricket, in their either paranoia, or control freak attitude has been progressively making their devices less and less possible to do what we bought them for, unless we happen to be Cricket employees, sworn to secrecy regarding those codes beneath and behind the *# ones that really don't do much without other input...
Click to expand...
Click to collapse
I'm not sure how you would root that particular phone, but I'm sure there is a way, or will be once the phone is out there longer, being without root access is a pain in the a**
revjamescarver said:
I'm not sure how you would root that particular phone, but I'm sure there is a way, or will be once the phone is out there longer, being without root access is a pain in the a**
Click to expand...
Click to collapse
When I originally started the thread, yep... I know the thing's not been out long... like since May (and I know crap all about the "Z" model used by other vendors... Obviously there's a drastic difference in the firmware, though...)...
Given time, I'm certain someone will work it out... There's a gentleman on another thread that seems to be working on it, and I'm going under the thing of "no news is good news" :laugh:
I've no doubt there's a way... I did a short stint at a call-center for Sprint, and there are always ways... It's a matter of having the right set of input codes, to get to the means to do the real deal...
I really dig the phone, although Cricket's flavor of Nougat isn't the most stable in the world... but, with the legal and legit apps I bought and continue to support, that's less of an issue.
It's frustrating when a company knows what a pain in the ass it is without allowing the user to administer it as really needs be... and they still refuse to permit it... I get that turning it into a paperweight can get tedious, but, given the means to get it back to factory standard in a reasonably simple way without sending it in, or buying another is just what I would see as normal... It's my own fault if I haven't backed up my data, but, if I somehow hose the firmware, just give me a means to get back to the start... It worked with their edition of the the Alcatel Idol 3... the Idol 4 (6055U)... I just gave the hell up.
pauljulian said:
When I originally started the thread, yep... I know the thing's not been out long... like since May (and I know crap all about the "Z" model used by other vendors... Obviously there's a drastic difference in the firmware, though...)...
Given time, I'm certain someone will work it out... There's a gentleman on another thread that seems to be working on it, and I'm going under the thing of "no news is good news" :laugh:
I've no doubt there's a way... I did a short stint at a call-center for Sprint, and there are always ways... It's a matter of having the right set of input codes, to get to the means to do the real deal...
I really dig the phone, although Cricket's flavor of Nougat isn't the most stable in the world... but, with the legal and legit apps I bought and continue to support, that's less of an issue.
It's frustrating when a company knows what a pain in the ass it is without allowing the user to administer it as really needs be... and they still refuse to permit it... I get that turning it into a paperweight can get tedious, but, given the means to get it back to factory standard in a reasonably simple way without sending it in, or buying another is just what I would see as normal... It's my own fault if I haven't backed up my data, but, if I somehow hose the firmware, just give me a means to get back to the start... It worked with their edition of the the Alcatel Idol 3... the Idol 4 (6055U)... I just gave the hell up.
Click to expand...
Click to collapse
I don't mean to freak out anyone that "Holy Cr*p! Someone's doing something"
.... But I'm just wondering if anyone's doing something.... ?
It's not going to happen my best advice to you is get another phone. I have the z982 the z981,982,983 all of them are unrootable ZTE had a bad hack a few years back that almost shut them down root was giving full access to those phones through apps. I hate this phone and can't wait to get a new one. Never again will I buy ZTE
adambomb_13 said:
It's not going to happen my best advice to you is get another phone. I have the z982 the z981,982,983 all of them are unrootable ZTE had a bad hack a few years back that almost shut them down root was giving full access to those phones through apps. I hate this phone and can't wait to get a new one. Never again will I buy ZTE
Click to expand...
Click to collapse
Well, for damned sure I'm sick of Cricket's control freak practice...
But it seems there are too many vendors that undercut legitimate developers whose products require root access...
I don't really need a custom ROM, but I bought Apps2SD Pro, Titanium and some others because I found them to be well-written, well-designed, and they did what I needed them for... But, since I can't root this otherwise pretty cool device, I've basically wasted my $$... I'll get another device at some time, preferably from a vendor that is less paranoid about users actually using their devices to their potential, but for right now?
This is one of the most stupid situations I've found myself... A device that is capable of being a laptop replacement, but the vendor only insists on our using them as they dictate...
So, is disgust an applicable word?
... mind you, not at those among us who were suckered into buying a hip but crippled device.
(although I've the idea that those who actually work for Cricket but are sworn to secrecy by potential lawsuits and loss of employment actually have an idea as to whatever *# commands actually go deep enough to do what's needed)
But I have no issues with those such as I that found a really hip little machine, yet have found ourselves locked away from its potential...
My issues are with the control-freak assholes that set the policies for the companies we pay entirely too much to remain in necessary communication.