Hello, all!
I ran through lots of threads, but I cannot find a remedy for my problematic rooting.
Firstly, maybe I have to warn you that I'm noob in rooting devices, I promise I'll catch up!
I very much would like to root my Dell Streak, I chose SuperOneClick 2.3.1 to do so.
I got SuperOneClick, turned my phone in USB debugging mode, allowed unknown apps, unmounted SD card.
Connected all cables...press Root and SuperOneClick gets non-responding after:
(see attached picture)
In this situation if I run adb devices I see mine listed.
Have you had similar situation? Have you got any ideas how to finish rooting my phone?
Ok. Forget SuperOneclick Go to this link and read, absorb, read again, read once or twice more then, absorb. Finally read over many more times and once you think you've taken it all in, read it again. Honestly. Rooting is great if you get it right but it's what nightmares are made off if you brick your phone.
http://forum.xda-developers.com/wiki/Dell_Streak_5/Flashing_Guide#Rooting_your_phone
Basically, you need to install Streakmod (a custom recovery) using "Fastboot". This will enable you to install "Superuser. zip". This will "Root" your phone. Best of luck.
You're nicer to him than I would have been. All I will add to what you said is that the search engine is his best friend and he might want to learn how to use it.
Yeah, but if the OP comes back with the same question i'll send em back to the same link. As you know, there is probably an answer to every "Android" related question within this forum. People just need to look. I'm just being nice cos back in February i was a noob asking the same question. What i quickly learned was, if you bother to look, you find and you learn loads of other valuable stuff along the way.
I had simialar issue and solved it
my dell streak was not able to fastboot dellstreakMOD because after reboot the system auto overwrite mod file. So I need Root first to trick/disable auto overwrite function.
Then I run into SupperOneClick 2.3.1 issue. I solved problem by using much older version supper One Click 1.55.
Good Luck!
One-click root solutions aren't recommended for the Streak because as you found out, they don't always work. However, the method on the wiki has a success rate of 100%. So what I don't understand is, why in the heck would anyone use a method that has a high rate of failure over a method that doesn't.
hey...s.o.c is no more recommended...
just flash the su.zip using streakmod and voila.. nothing else
Sent from my Dell Streak using xda premium
alpharetta said:
my dell streak was not able to fastboot dellstreakMOD because after reboot the system auto overwrite mod file. So I need Root first to trick/disable auto overwrite function.
Then I run into SupperOneClick 2.3.1 issue. I solved problem by using much older version supper One Click 1.55.
Good Luck!
Click to expand...
Click to collapse
The reason, why we are using the SupperOneClick is already mentioned: You are proposing us to do the fastboot method to get the custom recovery running. But to do so on the streak we first need to avoid the automatic restore of the stock-recovery tool. And to do so, we need a rooted device...
You see our point? It's like a cat biting in it's own tail, or a man sucking his own... You got me though?
It's not a proposal. If you bothered to look at the bottom of the flashing guide page on the wiki, you would have seen the following note:
Not recommended: Gingerbreak, SuperOneClick, Universal Androot, Z4Root
Click to expand...
Click to collapse
That note is on the flashing guide for a reason: these methods quite frequently do not work on the Streak. Besides, this really isn't as difficult as you're making it sound. The one thing that needs emphasis is that you'll install StreakMod Recovery twice. The first time is to root. The second time comes after using a file manager to delete install-recovery.sh, the file that causes the recovery to get overwritten.
If that series of steps in the flashing guide is too much for you to handle, I would not recommend rooting. The Streak is arguably the easiest device to root, requiring no special tools like goldcards to do the job. If you want a real challenge, try rooting an HTC Inspire. Without special tools an Inspire cannot be rooted.
Hi there quick question as I just got my hands on a Dell streak I see you post the guide for rooting and say its 100% safe is this 100% correct cause I don't fancy bricking it also will it work on build froyo 2.2.2?
By the way I'm not not a noob as I rooted my dhd the hard way round when it first came out the same way the inspire was rooted also built 2 custom roms and work on 3 others
Only asking cause the set up of the Dell is very different to an htc and a year on htcs are getting easier to root with a one click tool
And please don't say to read read and read again as that's what I will be doing anyway I ain't going to fly before I can walk lol
sent from my dhd
This rooting method works with any stock ROM. One-click methods fail for various reasons, and on a failure are likely to require the restore tool we have for the purpose, QDL Tool, in order to recover from the failed root.
With a Streak you need nothing more than some knowledge of how to use Fastboot to get the recovery on the Streak. This is more educational than using a one-click tool in my opinion. From there, the trick is immedately booting into the recovery after flashing it so you can flash superuser.zip. Once you've got superuser.zip on the device, you're rooted even if the recovery is overwritten. For best results however, you need to make sure to delete the file I mentioned in my prior post and install the recovery a second time. The one part that seems to trip most people up is flashing the recovery twice. They don't anticipate the recovery they just installed being removed when they try to get into it.
Now, is it 100% safe? Unless you do something you're not supposed to such as pulling the cable while in the middle of flashing a recovery or trying to erase the Streak using fastboot -w/fastboot -erase it's very safe. Safer in my opinion than the AAHK for the Inspire because with the AAHK you have numerous opportunities to brick the Inspire (S-OFF, Radio Install, Recovery Install) instead of just one (Recovery Install).
I don't have to tell you to read and read again. My sig takes care of that. But after 3,000+ posts I don't think you have to read my noob FAQ. Especially as you are not a noob.
Strephon Alkhalikoi said:
This rooting method works with any stock ROM. One-click methods fail for various reasons, and on a failure are likely to require the restore tool we have for the purpose, QDL Tool, in order to recover from the failed root.
With a Streak you need nothing more than some knowledge of how to use Fastboot to get the recovery on the Streak. This is more educational than using a one-click tool in my opinion. From there, the trick is immedately booting into the recovery after flashing it so you can flash superuser.zip. Once you've got superuser.zip on the device, you're rooted even if the recovery is overwritten. For best results however, you need to make sure to delete the file I mentioned in my prior post and install the recovery a second time. The one part that seems to trip most people up is flashing the recovery twice. They don't anticipate the recovery they just installed being removed when they try to get into it.
Now, is it 100% safe? Unless you do something you're not supposed to such as pulling the cable while in the middle of flashing a recovery or trying to erase the Streak using fastboot -w/fastboot -erase it's very safe. Safer in my opinion than the AAHK for the Inspire because with the AAHK you have numerous opportunities to brick the Inspire (S-OFF, Radio Install, Recovery Install) instead of just one (Recovery Install).
I don't have to tell you to read and read again. My sig takes care of that. But after 3,000+ posts I don't think you have to read my noob FAQ. Especially as you are not a noob.
Click to expand...
Click to collapse
Thank you very much for the info seems pretty much straight forward will crack on with it in a few days once I'm familiar with as much as I can need to learn the streak more before I start playing lol
As for the inspire its pretty much the same as a dhd and tbh flashing a radio is as simple as flashing a Rom from recovery I also tested flashing the radio from a different htc phone and regardless that it flashed but got stuck on splash screen I could still not brick the phone, now its really difficult to brick inspire or dhd, but it is known that eng s-off can cause issues on the inspire but not on the dhd
Just some info back for yourself mate as a thank you for yours also will hit the thanks button next time I'm pc
sent from my dhd
Thanks for the info. I rooted my roommate's Inspire using the AAHK on the day she got it. It ended up being a little more time consuming than using REVOlutionary to S-OFF my Aria the second time I rooted it*. I proceeded to put Android Revolution on the Inspire and she's a happy camper.
*The first time I rooted the Aria, which was the day I got it a year ago, I used UnrEVOked to root it. At the time there was no S-OFF possible.
Perspective for users of devices with locked bootloaders:
All dell devices are the equivilent of S-OFF/unprotected bootloader devices.
S-OFF, root, and custom are all seperate (but closely intertwined) concepts.
There are equivilents of superuser.zip for the nexus devices, as they ship either S-OFF or have
'fastboot oem lock/unlock' available to allow the user to S-ON or S-OFF at will.
Superuser.zip is equally valid on an already s-off'ed device that has a custom rec installed.
If your device can be officially S-OFFed and you install a custom recovery and use superuser.zip (or the device's equivilent form) you never have to touch a one click tool.
If your device is S-ON and there is no official way to S-OFF you must S-OFF it first, usually that requires making changes on it while it's on, which usually requires root. The only way to root a live device is though exploits in android, this is what one click tools do.
After having S-OFF'ed you can install a custom rec, and then it doesnt matter if you're rooted or not as you can install custom recs.
As long as you remain S-OFF'ed you never have to worry about rooting as custom recs/flashing zips completely bypasses android's security model.
This is the only reason that Android 3.0+ can be rooted, the ONLY ways to root 3.0+ is by rooting outside android. There are no known exploits in 3.0+ (and hence ICS devices are completely unrootable for the time being if S-ON) Every single 3.0+ device is rooted by either by superuser.zip or superboots (which are normal kernels that automatically install superuser.zip without needing a custom recovery)
The problem with superboots are that they are device AND rom specific, during the 2xx era for the s5 there were superboots available. But they had to be remade for every single version as flashing the wrong one will brick your device.
Most of the exploits used by one click tools are patched by 360, and I believe ALL exploits are patched in 4xx. Normally there are known vulnerabilities in 2.3.3, but Dell has added their own fixes to these seeing as it's one of the few devices running 2.3.3 that hasnt been updated to 2.3.4 or higher
Superuser.zip is version independant, and to a degree device independant. As long as it can mount your /system partition it can root it.
The S-ON/S-OFF terminiology is specific to HTC devices, but the concept is common to all android devices;
Dell = always S-OFF
HTC = dependant on device/carrier
Moto = mostly S-ON, some atrix's can be unlocked, xooms always unlocked
Samsung = usually S-OFF
'fastboot oem unlock' = sets S-OFF if allowed
'fastboot oem lock' = sets S-ON if allowed
Related
I tried to flash a custom rom on my eris last night with unsuccessful results.
To begin, my phone had the newest 2.1 OTA update on it and is running HBOOT 1.47. I downloaded and ran the 1-click universal root app. I noticed that a few new apps showed up (Latitute), but the Superuser app did not. I re-ran it several times but it still wouldn't show up.
Getting ahead of myself, I decided that I probably *DID* root the phone and I flashed Kaosfroyo V29 through the recovery menu. As I rebooted, the phone hung at the loading screen. I then tried to flash the Cyanogen mod with the same results.
After looking around, it appeared that the HBOOT 1.47 was exploitable with the 1.5 PB00IMG.zip update. I loaded it to my sd card and booted the phone in quickboot. It recognized the image but did not give me the option to update.
So now I am left with a phone that won't boot and without a backup (I know, I know).
What are my options? Is it still rootable from the recovery menu? Should I take it back to verizon and see if they can reflash/replace it (Doubtful as I probably voided the warranty).
wolfpack10 said:
I tried to flash a custom rom on my eris last night with unsuccessful results.
To begin, my phone had the newest 2.1 OTA update on it and is running HBOOT 1.47. I downloaded and ran the 1-click universal root app. I noticed that a few new apps showed up (Latitute), but the Superuser app did not. I re-ran it several times but it still wouldn't show up.
Getting ahead of myself, I decided that I probably *DID* root the phone and I flashed Kaosfroyo V29 through the recovery menu. As I rebooted, the phone hung at the loading screen. I then tried to flash the Cyanogen mod with the same results.
After looking around, it appeared that the HBOOT 1.47 was exploitable with the 1.5 PB00IMG.zip update. I loaded it to my sd card and booted the phone in quickboot. It recognized the image but did not give me the option to update.
So now I am left with a phone that won't boot and without a backup (I know, I know).
What are my options? Is it still rootable from the recovery menu? Should I take it back to verizon and see if they can reflash/replace it (Doubtful as I probably voided the warranty).
Click to expand...
Click to collapse
Try installing the engineering Bootloader. Instructions can be found in a sticky called Eris roll-up in the Eris developement section. Even if you can't flash a custom Rom after this you can still flash the official 2.1 ruu which will put your phone back to 100% stock and you can try again.
If your rooted and can still boot to fastboot your not bricked.
Sent from my Eris using XDA App
If the bootloader still appears (power phone on with vol-down+end), your phone is not bricked.
If the recovery boot still appears (power phone on with vol-up+end), your phone is not bricked.
If you don't have a SD card reader on your PC, you can transfer a different ROM to your SD card by booting to recovery and using the USB-MS toggle.
Smart money says that all you failed to do when you installed the ROM was perform a wipe before you flashed the ROM.
Prove this to yourself by installing a conservative ROM such as PlainJane, and when you get it running, for Dog's sake, make an effing Nand backup.
bftb0
I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Can I actually install alternative bootloaders on an unrooted phone?
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.
wolfpack10 said:
I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Can I actually install alternative bootloaders on an unrooted phone?
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.
Click to expand...
Click to collapse
Do you still have ra recovery? If so simply boot to recovery, wipe data and cache and reflash the rom.
All the 1 click root does is flash the custom recovery, so it did work.
Fyi
The Eris can now be rooted no matter what Bootloader version you have so doing the ruu will not prevent you from rooting. I myself was a leaker and had no problem rooting with the 1.49 s-on Bootloader.
As stated by btfb0, ALWAYS wipe data and cache before flashing a new Rom. ALWAYS do or have a nand backup ready just in case.
Sent from my Eris using XDA App
wolfpack10 said:
I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Click to expand...
Click to collapse
If you see the text "S-OFF" at the top of the screen, that is the bootloader, not the recovery boot. The one-click rooting method does not touch the bootloader, so, after successfully using "one-click", you will still have the same bootloader (initially).
wolfpack10 said:
Can I actually install alternative bootloaders on an unrooted phone?
Click to expand...
Click to collapse
You can install the Root PB00IMG.ZIP file onto a 1.46.xxxx or 1.47.xxxx bootloader phone - but you don't need to, because your phone already has a custom recovery installed on it (Amon_RA). As I mentioned previously, you get to that recovery facility by one of two ways:
1) Power phone off. Press and hold Vol-Up and then End/Power; continue to hold both keys down until you see the three skating droids appear (Don't release the keys until you see that screen). A menu system should appear 10 seconds after that happens. It will say "Amon_RA" on the bottom of the screen.
2) Make sure there are no files named PB00IMG.ZIP in the root folder of the SD card; either that or eject the SD card. Power the phone off. Press and hold Vol-Down and then End/Power; continue to hold both keys down until you see the three skating droids appear (Don't release the keys until you see that screen). A menu will appear immediately. One of the items will indicate that if you press "Vol-Up", you will boot into recovery. Press Vol-Up, and wait 10 seconds. You should be at the Amon_RA menu. (At this point, you can re-insert the SD card if you previously ejected it).
If you can't get either of these things to work, report back with exactly what you observe - saying "it didn't work" might be correct, but it isn't very informative.
wolfpack10 said:
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Click to expand...
Click to collapse
Not correct. Both the "one-click" and "Dummies" methods (see All Things Root forum over at AF) work for 1.47, 1.49.0000, and 1.49.2000 bootloaders.
wolfpack10 said:
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Click to expand...
Click to collapse
The PB00IMG.ZIP files are not compatible with the Amon_RA "update"-style installs; they are signed using an entirely different method. Not compatible. That's why it didn't work when you tried it (using Amon_RA). They are installed by starting up the bootloader with the PB00IMG.ZIP file in the root folder of the SD card. I am recommending that until you understand things a little better, you avoid this method - it only works with certain combinations of bootloaders and PB00IMG.ZIP file versions.
wolfpack10 said:
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.
Click to expand...
Click to collapse
It did work. You indicated in your first post that you used the Amon_RA recovery, which was installed by that method.
bftb0
Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.
wolfpack10 said:
Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.
Click to expand...
Click to collapse
Contacts should have been backed up through google. Although I have leaked and rooted some friends phone and their contacts never sync'd to their phones.
Sent from my Eris using XDA App
wolfpack10 said:
Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.
Click to expand...
Click to collapse
Glad you got it working.
If you were using Gmail instead of the HTC mail app for managing your contacts, all your contacts are still "in the cloud" (so long as you did not define them to be "phone only" when you added them).
If they were phone-only contacts, it would have been a simple matter to get your contacts back if you had made an initial Nandroid backup. I'm not saying that to add insult to injury, but rather (as you said) "Hopefully this thread will be helpful for other people in the future."
Backups are a really good thing.
BTW - You will find that Android Forums is a useful adjunct to this forum. The reason is that the ROM devs over here on XDA have their hands full trying to do both development work and interact with the users/testers reporting issues with their ROMs, so they don't spend much time in here (Q&A or General sub-forums). When they do announce a new hack, or patch, or rooting method, the descriptions are many times written tersely (for subject-matter experts, not newbs). There are a number of very helpful folks over on AF, and some good "sticky" posts that are quite a bit more detailed than what you will find here. I'm not ragging on XDA at all; just saying that by nature of the focus required for development work, the experts can't give much personal attention to individual users, even if they want to.
bftb0
I am been searching and searching for a tutorial to root my T-mobile UK hero.
Could someone help with find a straightforward guide as there seem to be soo many diffent methods which is just confusing me a bit.
about my device, Its currently running version 1.5
Rom 1.76.110.6
Also is there any easy/free way to unlock this device?
All help will be greatly appriciated.
I don't even know what a G2 is. but if it's basically a hero with a different case (the only reason I can imagine why it's lumped in with our heros), you should try my following instructions. The worst case is that it won't work in step one (the actual rooting process) in which case you'd have to get help from someone else.
Don's instructions for how to root your hero (yea, I'm Don, dkelley):
- download the one click root apk http://blog.23corner.com/tag/universalandroot/ from the official blog. (newbie points: copy it do your sd card if you didn't download it directly with your phone. checkmark "unknown sources" in settings->applications. install it using a file explorer that you can download from market for free such as "linda file manager".)
- run it, choose root for 1.5/1.6. takes half a minute. worked for me first time, but there isn't any obvious confirmation other than "done" message, so don't expect magical features popping up. It doesn't even install a superuser app or busybox... so you're still borked.... until the next step.
- download the free (old version, crappy features, but functional) superuser app from the market. install it (obviously). now you're just missing busybox. if you know how/want to bother putting it into your current rom, go for it. I didn't so I didn't.
- for sake of app backup, you can't run titanium without busybox (you already have root and superuser though, see post above if it matters that much). I downloaded the free applist tool from market to make a text file on sd card listing my installed apps. stock hero rom can't have too much installed anyway, won't take you THAT long to manually go through list and redownload/reinstall after flashing a new rom.
- install clockwork "rom manager". they say it's in market, I've never seen it. but an apk is floating around the net. it only needs root+SU which you have now. use it to download and flash a recovery rom of your choice. I use clockwork so it's an obvious choice here, but I think you can do amon-ra with this tool also, probably 1.6.x for those who don't care about dalvik wipes working properly.
- do a nandroid backup of your original rom NOW. could be really important... and this 1-click rooter can apparently UNRoot your rom too, so after a nandroid restore it might be the only way to get your phone back to stock. in my case I'm sol that way (hand-made goldcard rooting method, my phone's incapable of going stock ever again using my own skills...)
- newbie points: make sure you have a flashable signed gsm hero rom on your sd card somewhere. Reboot into recovery using "rom manager" or shutdown phone, then start it again but hold power AND home buttons without letting go until 8 to 12 seconds later you're booted into recovery. wipe everything (dalvik, cache, data, ext shouldn't matter yet from a stock rom...). "install zip file" or however they word the "flash rom" process in your recovery.
- reboot and enjoy.
I've got a t-mobile g2 and used the gold card method a while back, so can say that definitely works.
Thanks guys, I have decided to do the gold card and update it to a generic rom. Can i still get an unlock code to work? is there anyway on unlocking it?
I used a goldcard also on my phone months ago. a hero. pain in the butt to get done right... but works great.
this is why I recommended the above steps which are MUCH easier. I followed them (and organized those particular steps) and used them on my wife's hero a couple of days ago. It took me 15 minutes until I was running a new rooted rom on her phone perfectly with recovery installed, nandroid backup/restore, busybox, super user, the whole thing.
I know your phone isn't listed there - but again, downloading and running the apk won't do anything bad. it either works or doesn't, you'd know by now. it might not work but it's WAY faster and easier than a goldcard.
so imho it's worth a try for 30 seconds of your time.
if it says that it successfully roots your phone then just follow the rest of my instructions above to get everything setup how you'll need to.
goldcard works great though too - I just found it a very poorly documented experience. Hopefully it's clearer now.
when I goldcard rooted my phone I found several sets of instructions and they were all different - and not one of them worked on it's own, I had to combine bits and pieces. It was very scary LoL.
Good luck which ever route you take - hope you get a nice froyo rom running soon!
Hboot stuck
Hi I try to flash my G2 to generic RUU I did goldcard with success and I was doing upgrade trought RUU everything works great but then it says RADIO_V2 - FAIL PU.
Now when I try to turn on my G2 I get hboot screen and I can do anything
can somebody help me?
Thank You
dkelley said:
I used a goldcard also on my phone months ago. a hero. pain in the butt to get done right... but works great.
this is why I recommended the above steps which are MUCH easier. I followed them (and organized those particular steps) and used them on my wife's hero a couple of days ago. It took me 15 minutes until I was running a new rooted rom on her phone perfectly with recovery installed, nandroid backup/restore, busybox, super user, the whole thing.
I know your phone isn't listed there - but again, downloading and running the apk won't do anything bad. it either works or doesn't, you'd know by now. it might not work but it's WAY faster and easier than a goldcard.
so imho it's worth a try for 30 seconds of your time.
if it says that it successfully roots your phone then just follow the rest of my instructions above to get everything setup how you'll need to.
goldcard works great though too - I just found it a very poorly documented experience. Hopefully it's clearer now.
when I goldcard rooted my phone I found several sets of instructions and they were all different - and not one of them worked on it's own, I had to combine bits and pieces. It was very scary LoL.
Good luck which ever route you take - hope you get a nice froyo rom running soon!
Click to expand...
Click to collapse
The G2 is T-Mobile UK's version of the Hero, and as far as I know they have locked it down so tight that the only way of Rooting it regardless of what ROM it has(1.5, 1.5 update 1, 2.1 e.t.c), has always only been the goldcard method.
You have to use the goldcard method, I tried the other one when I was rooting my G2 and it didn't work.
I used this guide - BTDags guide, can't post a link though.
Google 'Complete Newbie Guide Hero' Its the first link.
I used the Goldcard to root my T-mob G2. I think I used this guide: Jesterz' guide It is a bit of a pain but you only have to do it once.
l0st.prophet said:
The G2 is T-Mobile UK's version of the Hero, and as far as I know they have locked it down so tight that the only way of Rooting it regardless of what ROM it has(1.5, 1.5 update 1, 2.1 e.t.c), has always only been the goldcard method.
Click to expand...
Click to collapse
thanks for the info! great to know. silly t-mobile.... like they have anything to gain from doing that....
Moved to Q&A as not development.
Guys and gals,
I just got a droid eris from a friend and want to root it and flash clockwork on it. I downloaded everything from unrevoked but when i try to install drivers for a windows computer it says that all drivers are up to date and it says htc bootloader. So i then run the package from unrevoked and nothing happens all it says on the screen is waiting for device. I have been all over you tube and forums can't find help to fix.
I am on 1.49 or something its also just stock 2.1. can anyone tell me what step I am doing wrong. please help.
DroidFamily said:
I just got a droid eris from a friend and want to root it and flash clockwork on it.
Click to expand...
Click to collapse
PROCEED DIRECTLY TO JAIL AND DO NOT PASS "GO".
Seriously, the combination of "newb" + "Clockwork" tends to be fatal to the Eris.
It is far more prudent for you to use the rooting methods described here in this forum - jcase's "Universal One Click .apk" comes to mind. Or, you can go over to AndroidForums and have a look at the Universal Root For Dummies. (The first rooting method that I mentioned is faster, but the second has an invaluable outline in the fourth post of that thread - with pictures - of how to use Amon_RA )
Only after you have completely mastered the use of the Amon_RA recovery should you consider using ROM Manager/Clockwork. (And you can use both, believe it or not).
Just yesterday someone hard-bricked their phone - possibly using the same recovery you are thinking of flashing.
If you insist on use Clockwork, for sure you ought to find out about what MD5 sums are, and how you can use apps such as scary alien's free market app "AFV" (Android File Verifier) to validate the signing of a ROM for which the developer has not provided a file size or MD5 signature.
bftb0
P.S. Neither of the two methods I mention above require a computer. That neatly solves your driver problem.
Much like the guy above, I'd avoid Clockwork and just go with something simple and almost guaranteed to work like the One-Click Root. With the Eris, Clockwork has a bad reputation. Some people buy into the taboo, some don't, but there's more evidence supporting bad things than good for it.
I'd avoid the possibility of turning your phone into a paperweight and steer clear of Clockwork.
bftb0 said:
It is far more prudent for you to use the rooting methods described here in this forum - jcase's "Universal One Click .apk" comes to mind. Or, you can go over to AndroidForums and have a look at the Universal Root For Dummies. (The first rooting method that I mentioned is faster, but the second has an invaluable outline in the fourth post of that thread - with pictures - of how to use Amon_RA )
Click to expand...
Click to collapse
Hindsight being 20/20 I would agree with the above post...
However I did use unrEVOked but was doing it thru linux so it was easier but did not like clockwork so I reflashed recovery with Amon_RA after I read up and realized how much better and easier it is.
This video I found will help if you still want to use the Unrevoked method
http://theunlockr.com/2010/09/22/how-to-root-the-htc-droid-eris-unrevoked-method/
Hope this helps you.
As a n00b - and I know this sounds like a commercial - really, the one click was the choice.
This is the thread that jcase started for that.
http://forum.xda-developers.com/showthread.php?t=742228
I am sure there is some really great reason to use a different method, but frankly, I just really needed to get on the newer roms. This was fast and easy. I didn't want to debug I just wanted it to work.
Just curious which rom are you going to be loading?
Hey all. I am actually from the Samsung Galaxy W community and since I'm gonna get the Atrix from my mom soon, I thought I should get a little heads up on how to root it and all. However, the guides here (no offense) freaked me out cuz they had lots of warnings and since the phone I use now is really simple to root (flash update.zip and you're rooted), I realised that rooting the Atrix isn't as easy as rooting the W. Thus I consulted my best friend, Google. He gave me this link: http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Is this the proper way to root? If so, then what do I do next? Because my motive for this phone is to install a custom recovery (ClockworkMod if possible) and (50% chance) stop it right there... I will really appreciate all the help I can get. Thank you, Atrix community.
---EDIT---
I got the method of installing the recovery. Now I just need you guys to verify if that is the proper way.
This looks like the well-known preinstall method. Yes, this is the most common (and IMO the most reliable) way to root the Atrix.
However, a common misconception when it comes to the Atrix is that you need root to get custom recovery. Those two probably couldn't be farther apart - one has nothing to do with the other. You not only don't need root to get custom recovery, it is in fact completely irrelevant because it operates on a much lower level. Instead, you need to unlock the bootloader (because fastboot is implemented in the bootloader, and because you need fastboot that isn't locked down), and then you simply flash your custom recovery via fastboot.
Now here's the problem. First, unlocking the bootloader is by far the most risky step of all. To do that you need to flash a piece of code (the unlocked bootloader, also known as pudding) in the most sensitive part of the phone. You screw this up and you got yourself a brick. Second, when you finally do unlock the bootloader, sometimes you'll be left in an unbootable state (the infamous Failed to boot XXX error). No worries, there's a fix for that too (it is called a softbrick btw). Point is, in that case you cannot just install the custom recovery and then "stop there", you'll need to install an OS too. If you prefer to stick to stock firmware, you should go with so-called fruitcakes, which is just stock firmware prepared to be flashed through custom recovery.
Nothing much to worry about though, everything is explained in detail here. You don't need to google or search in other places, everything you need is right here on XDA (in fact it is probably preferred that you stay within XDA instead of trying to follow random procedures from random places). I suggest you start with some basic noob stuff like this and this. (Some of the stuff in there is somewhat outdated, take any version info mentioned with a grain of salt.)
One big point. You will inevitably come across "SBFs" and advices to flash them. SBFs are inherently dangerous because they contain full complete systems (bootloader, radio, pds, and all the other very sensitive parts of the system), and they are flashed without any error checking, so it's very easy to brick (also known as hardbrick) your phone if you don't know exactly what you're doing. (That is also why all SBFs have been removed from XDA.) Unlocking the bootloader is the only time you should ever be dealing with a SBF, it should be avoided any other time if at all possible.
What I want to do is to get root and at the same time, get a custom recovery. Which means, I want to stick to stock ROM (again 50% chance of sticking to it). And that exactly what I meant by scary warnings... I have no idea what SBFs are (are they like .zip files that Galaxy W users use to flash files?). Anyway, the PUDDING thread was really, and I mean really, scary. Considering the fact that if I screw this phone, my mom will make me own the Galaxy W again...
Sent from my Samsung Galaxy W (GT-I8150) with CM9 RC 6
Yes, it can be scary, and for a reason. It is not for the faint hearted, although it goes without a hitch at least 95% of the time. The idea is that you get familiar with the process until the point where you feel comfortable with doing it.
SBFs are nothing like flashable ZIPs (well, except that both are used to flash stuff onto a device). Fruitcakes and custom ROMs come in flashable ZIPs. SBF stands for "single binary file" and is a proprietary Motorola file. It is created and signed by Motorola. Other than the pudding SBF which is the hacked unlocked bootloader, not much is known about them really, except that in some cases they can easily brick a device if misused.
There's another thing. If your atrix is too new, you might have a newer, non-unlockable bootloader. In that case all you can do is root the phone, no way to get custom recovery on it. Good news is, trying to unlock a non-unlockable BL won't do any harm, it just won't work.
If your goal is to have a custom recovery and root, I suggest you first deal with the recovery and then do the rooting. If you end up having to flash a fruitcake, by doing so you might get root anyway, depending on the fruitcake you choose (some are completely untouched, meaning no root, while some are completely stock but also rooted).
There is also an automated unlock method which you can try if you want. It should be slightly less scary to deal with. Personally, I dislike automated anything, I prefer to do the whole process myself (that way I also learn a bunch of stuff in the process), but to each their own.
ravilov said:
Yes, it can be scary, and for a reason. It is not for the faint hearted, although it goes without a hitch at least 95% of the time. The idea is that you get familiar with the process until the point where you feel comfortable with doing it.
SBFs are nothing like flashable ZIPs (well, except that both are used to flash stuff onto a device). Fruitcakes and custom ROMs come in flashable ZIPs. SBF stands for "single binary file" and is a proprietary Motorola file. It is created and signed by Motorola. Other than the pudding SBF which is the hacked unlocked bootloader, not much is known about them really, except that in some cases they can easily brick a device if misused.
There's another thing. If your atrix is too new, you might have a newer, non-unlockable bootloader. In that case all you can do is root the phone, no way to get custom recovery on it. Good news is, trying to unlock a non-unlockable BL won't do any harm, it just won't work.
If your goal is to have a custom recovery and root, I suggest you first deal with the recovery and then do the rooting. If you end up having to flash a fruitcake, by doing so you might get root anyway, depending on the fruitcake you choose (some are completely untouched, meaning no root, while some are completely stock but also rooted).
There is also an automated unlock method which you can try if you want. It should be slightly less scary to deal with. Personally, I dislike automated anything, I prefer to do the whole process myself (that way I also learn a bunch of stuff in the process), but to each their own.
Click to expand...
Click to collapse
So I was looking through the threads of the QnA section. And I came across this. Should I use the method mentioned in post #2 and #3? It looks pretty straightforward to me...
No, you cannot. The procedure you found assumes you have an unlocked bootloader.
I told you clearly what you need to do. Do not try to short-circuit the procedure. You need to go through ALL of those steps, there is no skipping ahead. It might seem scary, but either deal with it or give up on it. Do or do not, there is no try.
Oh, so is it like, you need to unlock bootlkader then root? If so, then I've finally got it!
Sent from my Samsung Galaxy W (GT-I8150) with CM9 RC 6
i rooted then was forced to unlock the boot loader when i screwed up my phone un-installing apps
used rescue root to one click root my atrix 4g (http://rescueroot.com/)
download clockwork mod recovery (http://www.clockworkmod.com/rommanager)
i installed clockwork mod recovery from fastboot (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus)
unlock the boot loader following this guide (http://forum.xda-developers.com/showthread.php?t=1302423)
as an added bonus here how to bypass that stupid motoblur crap (http://www.youtube.com/watch?v=wXDj-h1DEAM)... not nessicery for anything other then turning off the blur social media thing that comes installed with the phone
now i'm rooted, got the boot loader unlocked and running neutrino rom 2.91 GT+ for the last week, and so far i couldn't be happier
also it helped me to have a second computer, one to have all the how to running on and another to do all the work with
I have an at&t variant HTC m8, I recently stitched to cricket wireless. SIM swap went fine. I've been wanting to gain root to remove att bloatware. I'm on android version 5.0.2. My main issue is I've gotten nowhere unlocking boot loader using a pc. Tonight I resorted to using kingroot from Google play,which worked on third attempt. However supersu said it needs an update.
So basically I'm lost and trying to find away to gain root without a computer if possible.
I've never used kingroot. What happens if you try to update the root binary?
May be a bit irrelevant. I think you'll need to unlock the bootloader to do what you want (delete bloatware). I don't think kingroot alone will get it done. Reason being, you can't modify the system partition with root alone. You need kernel mod wp_mod, which is flashed with custom recovery TWRP. And you need an unlocked bootloader to flash custom recovery.
What issues did you have exactly when trying to unlock the bootloader?
I believe my main issue was that my pc is out of date running an unauthorized widows 7 lol. I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution. I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Lewis715 said:
I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution.
Click to expand...
Click to collapse
Not sure what "unable to obtain adb" means if you don't explain what happens exactly, where you are trying to get the files, etc. So all I can do is assume, and hope that I don't suggest you do things you already tried.
If you want an adb/fastboot installer, the following should work, and decently up to date: http://forum.xda-developers.com/showthread.php?t=2317790
Otherwise, there are other adb installers if you just type "easy adb" into the XDA search function.
No such thing as TWRP files that can help you unlock the bootloader. By definition, you can't install custom recovery until the bootloader is unlocked, and TWRP is a custom recovery. So nothing can be done with or by any TWRP files until you unlock the bootloader.
Lewis715 said:
I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Click to expand...
Click to collapse
Again, can't really help with what is "conflicted" unless you give some specific details.
Its understandable that a lot of the threads may be confusing, as the info is often outdated. This is getting to be an old device, and a lot of folks that wrote the various guides have moved on, and not updating the guides.
The following is a pretty good AT&T specific guide: http://forum.xda-developers.com/showthread.php?t=2799796
But as mentioned, some things are outdated:
1) The driver package is old. You can get updated drivers by downloading HTC Sync from the HTC website. After installing (which will also install HTC drivers) you can uninstall Sync, but keep the drivers; if you don't want Sync (but I haven't had any problems keeping it).
2) I believe the Dropbox link for adb installer is dead, but I already gave an alternative above.
3) The TWRP version is really old, don't use it! Get TWRP 3.0.2 from here: https://dl.twrp.me/m8/
The exception might be in the stock Android version on your phone is old, but if you tell me what it says for OS number on the bootloader screen, I can advise more specifically.
4) TWRP version is old, again, don't use it! v2.76 is the latest "stable" version, and you can get it here: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Everything else in the guide should still apply.
Vomer's guide is also a good one:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Again, the TWRP version is out of date (use the current one linked above).
You only need to do Sections 0 and 1, as the remainder of the guide (S-off, SuperCID) doesn't apply for what you are doing (unlock bootloader, custom recovery, and root).
Also, highly recommended to make a TWRP backup of the stock ROM, before you root.
After root, flash wp_mod with TWRP to enable system partition changes to stick (and deleting bloatware is a system change). What wp_mod depends on your Android version. But for Marshallow, the wp_mod can be found here (you just need the zip wp_mod, not the whole ROM): http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Lewis715 said:
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Click to expand...
Click to collapse
Of course, the vast majority of us don't have any real need to mess with the device. But we do, nonetheless!