Related
A friend of mine had her Eris metroflashed to MetroPCS. Calls and SMS work, but she wants me to provision the rest of it to work like i did with my own Eris on metro. I tried it to find out the Eris one click root app is not on the market anymore however i had the APK, erisone.apk. I loaded it to her SD card and downloaded Astro File Manager and attempted to install, which it proceeded to tell me it couldnt be installed on that phone. All i need is RA-Eris recovery as i will be loading a custom ROM. Is there an easy way to change the recovery on it so i can do this? I was thinking i just needed to update to 2.1 OTA (can someone provide the link? the old link from google doesnt work anymore) then the Erisone.apk will work (this apk loads custom recovery as well as a root very easily). I need to load a custom ROM before i can begin with the provisioning, what do you guys think i should do?
Does this work http://forum.xda-developers.com/showthread.php?t=742228?
Or see this list of options that scary alien provided http://forum.xda-developers.com/showthread.php?p=10013596#post10013596.
roirraW "edor" ehT said:
Does this work http://forum.xda-developers.com/showthread.php?t=742228?
Or see this list of options that scary alien provided http://forum.xda-developers.com/showthread.php?p=10013596#post10013596.
Click to expand...
Click to collapse
The top one is one i tried. The bottom link there mainly concerns rooting. Im trying to install a custom rom thats already rooted so i don't care much for rooting but i guess its necessary to install a new recovery image right? All i want to do is install ra-eris recovery so i can load a custom rom. The one click method you linked automatically installs a new recovery image and thats what im really after. I just don't think that one you linked is compatible with 1.5
Helgaiden said:
The top one is one i tried. The bottom link there mainly concerns rooting. Im trying to install a custom rom thats already rooted so i don't care much for rooting but i guess its necessary to install a new recovery image right? All i want to do is install ra-eris recovery so i can load a custom rom. The one click method you linked automatically installs a new recovery image and thats what im really after. I just don't think that one you linked is compatible with 1.5
Click to expand...
Click to collapse
You have to be rooted and have a custom recovery in order to install a custom ROM.
Editing...ignore what I had posted in this space before.
The second link (starts with "Failing that...") says it works with 1.5.
You have to be rooted to have a custom recovery. This i know...but can you have a custom recovery without being rooted? I dont care about getting this phone rooted, i just want a custom recovery on it.
Helgaiden said:
You have to be rooted to have a custom recovery. This i know...but can you have a custom recovery without being rooted? I dont care about getting this phone rooted, i just want a custom recovery on it.
Click to expand...
Click to collapse
You HAVE to be rooted to change: recovery, kernel, hboot, ROM, and radio. The only exceptions are official updates, whether they be OTA or running a RUU update from Windows with the phone connected.
Root access effectively means being able to change things you're not normally allowed to change.
If you want a custom recovery on your phone, you're going to have to root it. To be technically fully rooted, you would probably have to change your hboot (referred to as S=OFF), too, but it doesn't sound like you need that part. This may not be the answer that you want, but it is what it is.
roirraW "edor" ehT said:
You HAVE to be rooted to change: recovery, kernel, hboot, ROM, and radio. The only exceptions are official updates, whether they be OTA or running a RUU update from Windows with the phone connected.
Root access effectively means being able to change things you're not normally allowed to change.
If you want a custom recovery on your phone, you're going to have to root it. To be technically fully rooted, you would probably have to change your hboot (referred to as S=OFF), too, but it doesn't sound like you need that part. This may not be the answer that you want, but it is what it is.
Click to expand...
Click to collapse
Okay, i will try one of those other root methods then. Do any of them install a custom recovery as part of the process like the universal one click root does?
Helgaiden said:
Okay, i will try one of those other root methods then. Do any of them install a custom recovery as part of the process like the universal one click root does?
Click to expand...
Click to collapse
I'm sure they all probably do, but I'm sure they say definitively in their threads, too. Everyone who roots wants to install a custom recovery so that they can flash rooted ROMs. Most everyone, anyway. Only those who just want the stock ROM but rooted wouldn't care about the recovery, but those are a minority.
Alright cool. Im gonna do the last method from Scary Allen's post. Just a question though..
i hook up the phone to the PC then click install_root.bat. That should do what i want, however in what mode should the phone be in when i have it plugged in? Powered on like normal, in the stock hboot/recovery mode...??
Helgaiden said:
Alright cool. Im gonna do the last method from Scary Allen's post. Just a question though..
i hook up the phone to the PC then click install_root.bat. That should do what i want, however in what mode should the phone be in when i have it plugged in? Powered on like normal, in the stock hboot/recovery mode...??
Click to expand...
Click to collapse
You should keep questions about various methods of doing things in the original thread. If it doesn't say in the thread about what mode it should be in, then you'll have to ask GrdLock. If it doesn't specify then maybe it doesn't matter what mode it's in. The only thing it specifies is:
MAKE SURE YOUR SDCARD IS NOT MOUNTED TO YOUR COMPUTER OR THIS WON'T WORK!!!!
Click to expand...
Click to collapse
roirraW "edor" ehT said:
You should keep questions about various methods of doing things in the original thread. If it doesn't say in the thread about what mode it should be in, then you'll have to ask GrdLock. If it doesn't specify then maybe it doesn't matter what mode it's in. The only thing it specifies is:
Click to expand...
Click to collapse
yeah i got that much out of it. Okay, thanks for your help.
The jcase "One Click" .apk does not work on 1.5, as you discovered.
Note that the root exploit method that One Click employs does work on 1.5 - but unfortunately the One Click app itself only runs on 2.1.
The Universal Eris Root for Dummies! method will work on both 1.5 and 2.1; it uses the same (wag3slav3) rooting exploit, but does not require the 2.1 OS to be running in order to work correctly. All it does to your phone is to install the Amon_RA custom recovery - exactly what you are looking for.
This method is the same one referenced by scary alien in his post mentioned above - the second URL in his post.
I've said this before, but I'll say it again: when you say "rooted", it means different things to different people. The most general definition is that you have "installed something on your phone which gives you privileges to alter some or all of the phone software which the device manufacturer did not intend".
So - you can have an engineering bootloader on a phone, but a completely stock OS... and that would be a "rooted" phone. Same deal for a set of root tools installed in the OS, but a S-ON bootloader and a stock recovery partition. Or a stock bootloader, a stock OS, but a custom recovery - again, that is also a "rooted" phone. In all three cases, you now have the means to alter whatever you want on the phone. That's all that "rooted" really means; it doesn't necessarily mean that the OS has been kanged up.
bftb0
ahh confirmation it doesnt work on 1.5, nice haha. Well thanks. Ill look into the Dummies root method but right now im leaning toward's GRDLOCK's method. At least i know i have good valid options though, thanks!
I've poked around the forum looking for solutions but found no situation the same as mine. I'm beginning to prepare to flash a new ROM onto my Eris, so I was doing to do a nandroid backup. I have a rooted 2.1 (non-OTA, it was one of the update versions people posted online before 2.1 officially came out)
So I boot up holding down Power and Volume Down. So far, so good. I get to the screen that has some phone info and then HBOOT, <SEND> FastBoot Mode, <VOL UP> Recovery
I hit Volume up, and phone vibrates, goes to the Androids on skateboards, and then to a picture of the phone with a red triangle and exclamation point inside it. It just stays like that until I pull my battery. Then I can turn it back on to regular mode without any problems. However, I'm not sure what's going on.. and this would be a problem if I wanted to change ROMs.
Any help would be appreciated. Thanks
raconteur001 said:
I've poked around the forum looking for solutions but found no situation the same as mine. I'm beginning to prepare to flash a new ROM onto my Eris, so I was doing to do a nandroid backup. I have a rooted 2.1 (non-OTA, it was one of the update versions people posted online before 2.1 officially came out)
So I boot up holding down Power and Volume Down. So far, so good. I get to the screen that has some phone info and then HBOOT, <SEND> FastBoot Mode, <VOL UP> Recovery
I hit Volume up, and phone vibrates, goes to the Androids on skateboards, and then to a picture of the phone with a red triangle and exclamation point inside it. It just stays like that until I pull my battery. Then I can turn it back on to regular mode without any problems. However, I'm not sure what's going on.. and this would be a problem if I wanted to change ROMs.
Any help would be appreciated. Thanks
Click to expand...
Click to collapse
It sounds like you installed the leaked 2.1 root ROM (very early, buggy version of 2.1) and never installed a custom recovery (your information above indicates that you currently have a stock recovery).
You could verify that this is the case by checking your phone's information against this thread: http://androidforums.com/eris-all-things-root/87118-reference-what-htc-rom-do-i-have.html (it is a little crazy / scary that someone has used the 2.1 base root ROM all of this time given all of the bugs that it had ).
I *think* that you could use jcase's 1-click app (see http://forum.xda-developers.com/showthread.php?t=742228) to push Amon_RA's custom recovery onto your phone.
There's other methods too, but you might want to explore the simplest first.
Amon_RA's recovery works. thanks
scary alien said:
I *think* that you could use jcase's 1-click app (see http://forum.xda-developers.com/showthread.php?t=742228) to push Amon_RA's custom recovery onto your phone.
Click to expand...
Click to collapse
FWIW, that is correct. Even though the "Leak Root" HTC ROM is already rooted, it contains the same chmod 777 symlink business in its' boot scripts, so the jcase OneClick or the Dummies method can be used to install a custom recovery to the "Leak Root" HTC ROM. (Even though it is already a "rooted" ROM in a sense). The recovery could also just be flashed directly using fastboot, as the Leak Root ROM installs the 1.49.2000 S-OFF bootloader.
Sounds like the OP fixed his problem - somehow.
bftb0
bftb0 said:
FWIW, that is correct. Even though the "Leak Root" HTC ROM is already rooted, it contains the same chmod 777 symlink business in its' boot scripts, so the jcase OneClick or the Dummies method can be used to install a custom recovery to the "Leak Root" HTC ROM. (Even though it is already a "rooted" ROM in a sense). The recovery could also just be flashed directly using fastboot, as the Leak Root ROM installs the 1.49.2000 S-OFF bootloader.
Sounds like the OP fixed his problem - somehow.
bftb0
Click to expand...
Click to collapse
Thank you for the confirmation, bftb0 as always...
Yes, it would be nice for the OP to disclose the resolution information for the sake of helping others.
Cheers and Happy New Year's Eve Eve!
I'm not sure what information you're asking for but..
HBOOT-1.49.0000 (PB0010000)
not only did Amon RA recovery work, regular recovery works now as well (unless that's amon RA recovery also, but it looks different). Thanks for your help
in recovery it says
Build: RA-eris-v1.6.2
raconteur001 said:
I'm not sure what information you're asking for but..
HBOOT-1.49.0000 (PB0010000)
not only did Amon RA recovery work, regular recovery works now as well (unless that's amon RA recovery also, but it looks different). Thanks for your help
in recovery it says
Build: RA-eris-v1.6.2
Click to expand...
Click to collapse
I think we were looking for confirmation that you really did have the base leaked 2.1 root ROM--but it looks like, based on the HBOOT version (1.49.0000) that you actually had an un-rooted 2.1 leaked ROM.
Also, you must have run the 1-click app to gain Amon_RA's custom recovery, correct?
If you would have cross-checked the original ROM's Settings -> About Phone -> Software information's "Software version" and "Kernel version" against the information in http://androidforums.com/eris-all-things-root/87118-reference-what-htc-rom-do-i-have.html it would have made diagnosing what was going on a little easier.
Thanks for responding!
Ah. I used z4root some time ago. So i'm definitely rooted because Superuser and Wireless Tether are on my phone. I have the v2 leak: 2.26.605.4
raconteur001 said:
Ah. I used z4root some time ago. So i'm definitely rooted because Superuser and Wireless Tether are on my phone. I have the v2 leak: 2.26.605.4
Click to expand...
Click to collapse
Thanks, the v2 leak info does help .
I'm only familiar with Z4 root w/regard to how it rooted my Droid X...did it (Z4) install Amon_RA's custom recovery or did you get it by another means? (I ask this because your initial post indicated you had trouble booting into recovery and it appeared from what you described to be the stock recovery).
scary alien said:
Thanks, the v2 leak info does help .
I'm only familiar with Z4 root w/regard to how it rooted my Droid X...did it (Z4) install Amon_RA's custom recovery or did you get it by another means? (I ask this because your initial post indicated you had trouble booting into recovery and it appeared from what you described to be the stock recovery).
Click to expand...
Click to collapse
I had to flash RA recovery using the ROM Manager app
raconteur001 said:
I had to flash RA recovery using the ROM Manager app
Click to expand...
Click to collapse
Aha! Thank you very much! That's actually two very useful pieces of information (to me at least ):
1) Z4 can root an Eris without installing a custom recovery (this is the first confirmation I've heard of this)
2) ROM Manager is a good vehicle for flashing / installing a custom recovery (I don't have any direct experience with ROM Manager, so this is good to know).
Thank you again for sharing with all of us!
Cheers and have a safe and Happy New Year!
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?
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
Hi!
I've been using Androwook 2.0 for a while and love it. However, I'd like to try 2.1 and the BAKED ROMs. Based on feedback on the forum, I want to use the Team Win recovery (TWRP) as opposed to my currently installed Clockwork Recovery.
Problem is, I can't work out how to replace CWR with TWRP. I've downloaded GooManager and instructed it to install the TW recovery. It says it's done so but when I reboot to recovery it takes me back to CW.
So, question is: how can I replace Clockwork Recovery with TWRP on a TF201?
Many thanks in advance for your thoughts!
Regards,
mroshaw
mroshaw said:
Hi!
I've been using Androwook 2.0 for a while and love it. However, I'd like to try 2.1 and the BAKED ROMs. Based on feedback on the forum, I want to use the Team Win recovery (TWRP) as opposed to my currently installed Clockwork Recovery.
Problem is, I can't work out how to replace CWR with TWRP. I've downloaded GooManager and instructed it to install the TW recovery. It says it's done so but when I reboot to recovery it takes me back to CW.
So, question is: how can I replace Clockwork Recovery with TWRP on a TF201?
Many thanks in advance for your thoughts!
Regards,
mroshaw
Click to expand...
Click to collapse
you could use fastboot method: http://www.teamw.in/project/twrp2/93
also it is recommended to use AndroidRoot bootloader: http://forum.xda-developers.com/showthread.php?t=1774352
Thank you for the reply. I'm not that comfortable with that level of tweaking and I had really hoped that Goo Manager would sort me out. Is it a known issue that Goo Manager cannot install TWRP if another recovery is present?
If so, I'll give the fastboot method a go at the weekend.
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Danny80y said:
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Click to expand...
Click to collapse
I think most of us are unaware of exactly what is going on behind the scenes when you tell an app to update the recovery. The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid. I flashed twrp via the fastboot method. I did not use the AndroidRoot bootloader.
Danny80y said:
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Click to expand...
Click to collapse
Yeah, not a particularly helpful response to be honest. If you don't know the answer to the question, probably best not to post a reply.
emptyshell said:
The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid
Click to expand...
Click to collapse
Indeedy - thanks for that.
The Androwook flashing process felt really safe and gave a lot of less techy Prime users access to a ROM that transformed (excuse the pun) the TF201 into a usable device. I don't think a lack of a full understanding of the inner workings of the technology or process should stop people from using it or from asking questions. Otherwise, what's the point of the forum?
If anyone is able to answer the question as to why Goo Manager will not install TWRP on top of an existing CW recovery, I'd greatly appreciate it. :good:
emptyshell said:
I think most of us are unaware of exactly what is going on behind the scenes when you tell an app to update the recovery. The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid. I flashed twrp via the fastboot method. I did not use the AndroidRoot bootloader.
Click to expand...
Click to collapse
I had problem with GooManager too, so I flashed TWRP manually via fastboot.
Be aware her if you want to use twrp backup/restore you'll probably need modified bootloader as stated above. Twrp uses .img backup format, not blob, and modified bootloader can handle them correctly, which is not the case of original one.
You could have a non functional restore process for /boot. One solution could be to reflash the ROM after the restore in that case, so if you don't want to modify the bootloader always keep the zip of the ROM that you backup.
Thanks all.
I'll go the manual route then, I think. Be as well to go the whole hog and do the modified boot loader too, by the sounds of things.
Thank you for your useful responses and input - much appreciated.
Couple of things to be aware of, firstly, fastboot method for installing twrp not too hard, read the instructions a couple times before you proceed. If you do run into problems, go back to the forum and ask, don't try to "fix" it with a method that hasn't been proven. Secondly, when you install twrp, you can forget you cwm backups, they are now worthless. That being said, make a back up in twrp at your earliest convinence.
Third, read the instructions, most are pretty clear but if you don't understand something ask before you start you can save yourself a lot of trouble.