I believe that you are going to have to wait on Netflix for that, for an official app. I believe that they are working on one.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Universal 1 Click Eris App Apk - No PCs, No Scripts Needed, EASY
- Thread starter jcase
- Start date
-
- Tags
- htc droid eris
I believe that you are going to have to wait on Netflix for that, for an official app. I believe that they are working on one.
Yeah, eu1 figured-out (http://androidforums.com/eris-all-things-root/205697-notes-recovery-booting-1-5-vs-2-1-otas.html) that HBOOT 1.47.0000 phones seem to act a little differently than others...
Cheers!
zachslusser
Lurker
so I used this method to root my eris and now the phone is getting so many error messages. I cant even send or receive texts and earlier I couldn't make calls what should i do ?
Zach,
Sorry for the slight delay... I got a "database error" here on AF a little while ago when trying to reply to you.
Can you give us a little more detail? Like did you install a custom ROM and if so, which one?
Also, did you do the wipes (Wipe Data/Factory Reset) before flashing the custom ROM (assuming you did flash a custom ROM)? [I suspect this might be your culprit].
Hopefully, you took a Nandroid backup first-thing after rooting...
Let us know.
Cheers!
zachslusser
Lurker
well i tried the xtrsense custom rom as well as the vanilla 2.0 by the same person and one other, and they were all garbage. i did the wipe data but maybe i didnt do it when i first rooted it like the first time but i know i did a few times when i switched to the other ones. I actually just put flashback21 something or other on it to try and reset the root and it worked
maybe rooting isnt for me i dunno
maybe rooting isnt for me i dunno
zachslusser
Lurker
i really would like to be able to put apps on the sd card as well has have the ability to have voice to text and live wallpapers but i dont know what i should do.
Well, Zach's xtrROM and xtrSense ROMs were very highly regarded around here and over at XDA. That being said, selecting a custom ROM that's right for you and fits you is a highly subjective and personal matter and there are a lot of different ROMs to choose from.
I'm not really a heavy ROM flasher (that's really an understatement, actually), so I'm not the best person to give personal advice on the merits of different ROMs, other than repeating what I've heard from other people that I respect regarding their experiences. There are many threads out there where people have compared and contrasted various ROMs, so you should peruse through the threads, both here and over at XDA to get a better feel for what is out there that might fit you best and/or work best for you.
Cheers!
zachslusser
Lurker
So does that then mean that I obviously did something wrong when I rooted? Are the errors and nt being able to use certain features a normal thing ?
Not sure (you didn't say exactly what the errors were
)...I'm guessing that perhaps you didn't wipe before flashing the custom ROM at first and this led to some wonkyness. Your best bet would be to view the threads about xtrROM and/or xtrSense here in AF or over at XDA to see what others have experienced w/installation issues and such.Cheers!
I can't seem to flash any roms. I tried kaosfroyo, nonsensikal, xtrSense, xtrRom. All of them seem to be rebooting in an infinitely loop. Some roms, I see a custom load screens, some roms I don't. I waited for half an hour on some of them.
I used this 1 universal click to root in this thread. Then made my nanodroid backup, luckily I can recover it. I then wipe data and wipe Dalvik-cache. Still none of these roms work.
Am I missing 1 step?
I used this 1 universal click to root in this thread. Then made my nanodroid backup, luckily I can recover it. I then wipe data and wipe Dalvik-cache. Still none of these roms work.
Am I missing 1 step?
yoyohere2,
Well, you are the second boot-looper of the day (sorry, no prizes
). There's another member that been posting in this thread: http://androidforums.com/eris-all-things-root/221926-question-help-flashing-roms.html
about boot-loops with their phone too. Current theory is that the default overclocking of the ROM (higher than the stock 528Mhz) might be to blame. Anyway, check out the thread and maybe try flashing something like PlainJaneT2_v2 which we have established is NOT overclock at boot-up higher than stock. If so, perhaps this will explain and confirm what is happening with not only your phone, but the other poster's too.
Please let us know (feel free to hop into the other thread). Cheers!
Houstatlanavegas
Well-Known Member
dumb question but how do i get a custom rom??? new to rooting happy i did it i think havent seen the advantages anyone wanna help ya boi?!?!? please
Hey, welcome back, by the way!
Take a stroll over to Droid Eris Android Development - xda-developers and look for the threads prefixed with "[ROM]"...there's tons of them over there...
Also, for recommendations over here at AF, look for the "Which ROM" or "Best ROM" threads (there's way more than there should be, if you know what I mean
).Cheers!
Houstatlanavegas
Well-Known Member
ok ok but for instance i downloaded the white widow on my sd and now i dont know how to flash it so i can use it thats all i need help with really, and thanks good to b back i missed yall *tear* lolHey, welcome back, by the way!
Take a stroll over to Droid Eris Android Development - xda-developers and look for the threads prefixed with "[ROM]"...there's tons of them over there...
Also, for recommendations over here at AF, look for the "Which ROM" or "Best ROM" threads (there's way more than there should be, if you know what I mean
Cheers!
So, have you done the 1-click root yet?
You might want to read-through erisuser1's thread http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html since it'll teach you a lot about what is going on.
That image is the splash screen of the stock recovery boot.
Seeing it suggests that you are not completing the installation process, which requires that you reboot normally at least once (after installing and running the one-click app) before you try booting into recovery.
The original instructions were a little vague on that point, but it is discussed several times elsewhere in this thread.
Good luck!
eu1
I do not seem to be able to root my Eris at all. I tried one click root and universal root. Both appear to run OK, I cannot get to the recovery screen using up vol and pwr. When I use dn vol / pwr I can choose recover, but the phone seems to hang on the white screen with the skateboarding droids.
When I go through Gscripts, it says I have root, but when I use a terminal and SU, I get permission denied.
Any ideas?
I picked the phone up used yesterday.
Thanks.
When I go through Gscripts, it says I have root, but when I use a terminal and SU, I get permission denied.
Any ideas?
I picked the phone up used yesterday.
Thanks.
Neither the "One Click" nor the "Dummies" method install "su" directly - they only install the custom recovery. So, using "su" in a terminal emulator would not be a proper test of success anyway. (I'm not sure what you meant by "go through Gscripts").
One thing that has been overlooked by several people is that in both the "One Click app" method and the "Dummies" method, you need to reboot the phone in the middle of the instructions.
Also, note that the three skating droids will appear on your phone for about 9-14 seconds before the custom recovery menu appears. (I am assuming that you waited longer than that, and the phone gets "stuck" there, but thought I would mention it just in case).
The fact that you can not use Vol-Up+End to power up directly into the recovery simply means that you have the 1.47.0000 S-ON bootloader on your phone; but Vol-down+End (into HBOOT mode) followed by Vol-Up should launch the custom recovery.
If you still had a stock recovery still on your phone, you would see an image that is a droid plus a exclamation point inside a triangle; since you are seeing the three skating droids, and then a hang, I will assume that *something* happened which corrupted your recovery partition.
The way that the rooting technique works, there is a small risk that the very beginning of the recovery partition will get overwritten by 16 bytes of data - which contains the android boot signature and some critical load addresses.
If that's what happened, then the best way to avoid that problem is to immediately shut down the phone at the conclusion of the rooting process (whether the 2nd phase of "One Click", or "part_2" of Dummies), and then attempt to launch the recovery (Vol-Down+End to HBOOT, followed by Vol-Up)
Good Luck
eu1
Thanks EU1, appreciate your willingness to help out.
In one click I reboot the phone, then when it is on, I shut off and hold dn vol/pwr, select recovery with the up volume, then pwer. This is where it will hang (for at least 3-5 minutes before I pull the batt).
Is that the correct sequence?
I did root a moto devour, but it was much more involved, using the computer to log onto the phone, move and change files. I thought I came across something similar on this site. Would that method overcome my not being able to get the recovery to load, or should I continue to run one click and hope it takes eventually?
Thanks.
Tony
Something looks unusual in the very last part of your description -
When you have started the phone up into HBOOT mode (after the first run of One Click) using Vol-down+End, you only press Vol-Up to start the recovery boot - no use of the Power (End) button at that point. (Unless what you meant by "then pwer" is you getting frustrated and yanking the battery)
It sounds like you have the 1.47.0000 bootloader (from your description); in that case, the correct sequence for either the One Click (or the Dummies) method is:
- Install and run One Click app (Dummies: run part_1 script)
- Power phone off normally
- Power on (boot) phone normally
- One Click method, do nothing - the 2nd phase runs automatically at boot (Dummies: run part_2 script)
- Power phone off normally.
- Power phone on with Vol-down+End (to launch HBOOT mode)
- Press Vol-Up key to boot recovery.
- Install custom ROM using Amon_RA custom recovery (optionally make a nandroid backup first)
I would encourage you to give the Dummies method a try if you can't get One Click to stick - and then compare the screen you observe after running the part_2 script - do you notice ANY differences?
The exploit which is being run is extremely straightforward and deterministic - it should "take" the first time it is executed.
In the spirit of due diligence, I suppose we should also check the initial state of the phone, too:
- Was there any evidence that the phone was previously rooted?
- What is the existing software version on the phone? (Settings -> About phone)
- Did you confirm the bootloader version # (that I presumed)? It is on the screen when the phone enters HBOOT mode.
The only other thing that I can think of is that I am not sure of how One Click detects that it's own phase 1 operation has been completed. If you are going to run it again, you might try uninstalling & re-installing it before you run it again.
eu1
eu1,
I think the 1-click app simply knows that the phase 1 is complete by virtue of the reboot having taken place (it listens for a boot completion broadcast action) and then writes the custom recovery.
So, I think that's why jcase instructed the user to de-install the app after getting rooted so that the app does not continue re-installing the custom recovery after each reboot.
Cheers!
"uninstall & uninstall" - LOL, damn phone's auto-correct.
I've got to get out of bed and post using a real computer.
lol...I've fixed your quote in my reply
...(I owe you at least that much ).I actually read and replied very quickly before running off to a quick meeting--I didn't even catch that...
.