Related
I was trying to root my Eris and i went to the 1 click eris root thread, downloaded it, followed all the directions, now when i hold vol up and power it boots to the recovery thing. From here im supposed to scroll down to flash zip from sd. I cant. Ive tried the track ball, the volume keys, everything. All it will let me do is press the trackball to select "reset device" or whatever the first option is. Any help? Like is there any way to flash that zip without using that recovery thing? Sorry if this is some simple noob mistake. just got my eris last week.
Anybody? Is there a different bootloader/recovery program i could load onto my phone to flash the "rootme.zip"?
EDIT: i think my trackball might just be broken or something, is there somethin i could edit to make it where the vol keys move the selector up and down instead of the track ball? i can still press the trackball, just cant scroll with it.
Sounds like a broken trackball to me. Mine broke a month after I first got my Eris, it would only scroll left. The phone was under warranty so I got it exchanged no problem. My younger brother had the same problem except his trackball would not scroll down.
The trackball on the Eris seems to be really sensitive and any pivoting force placed on the usb cable when it's plugged in seems to be the culprit. Just swap out your phone for a new one at a Verizon store and you'll be good to go.
Read the 2nd post in this thread:
http://forum.xda-developers.com/showthread.php?t=804946
and follow the links there.
This is a method for technically sophisticated users; if you are intimidated by it, then DON'T USE IT.
(The author of that method - me - will not offer spoon-feeding services.)
There is a chance that ROM Manager/Clockwork recovery will work without a trackball, but I don't use that, and in any event you need to be rooted to install that, so there is a chicken-and-egg problem in proposing it as a work-around.
bftb0
If your trackball is rooted please do not go further in the process... simply run the RUU and go back to 1.5 or 2.1 and return your phone for a new one/ Incredible.
Hungry Man said:
If your trackball is rooted please do not go further in the process... simply run the RUU and go back to 1.5 or 2.1 and return your phone for a new one/ Incredible.
Click to expand...
Click to collapse
I was going to offer the OP the same advice, except for one thing: he didn't mention whether or not the trackball problem is also present with the stock O/S booted.
In addition to lots of reports from folks that clearly have broken/bad trackballs, there have also been multiple reports from people that experience scrolling problems with the trackball only when Amon_RA is booted - those folks are sort of SOL when it comes to a return, as they can't demonstrate the problem occurs with factory software.
But, yeah - if it is broken in both Amon_RA and the stock O/S, the OP should try and get a replacement phone. (Ugh! From the looks of recent reports, the OP might just end up with a "refurb" that also has a broken trackball)
bftb0
No way i can return it. im not the original owner, i bought it off of a friend for $20 lol, he thought it was broken but it just needed a new battery. the trackball scrolls left and right just not up or down, and it does this whether im in Amon_RA or not. its just the track ball is broken. I consider myself pretty "tech sophisticated" so ill try bftb0's first word of advice and see if that will work. Thanks for the help guys. if it doesnt work i guess im just SOL on getting my Eris rooted. Oh well, im due an upgrade and will probably get the droid 2 anyway but i was hoping to get the eris going.
EDIT: LOL go figure my luck here...my USB port is also gimped, like as in doesnt work at all, i charge my batteries on battery cradles that plug in the wall, and the method of flashing a zip without using the trackball requires you to connect your phone to your computer with usb cable, so im SOL. Thanks for trying guys, any other help (doubtful there is any) would be much appreciated.
So i opened up the app drawer in landscape and had an idea. is there anyway someone could mod the 1 click root thing so that the recovery operates in landscape? because since my trackball scrolls left and right i could then scroll "down" to the flash from sd card option, if it was in landscape.
use clockwork mod. be warned tho people have reported that using that their phone has bricked. but i didnt have problems with it when i was waiting on my referb with a working trackball. Call verizon and tell them your trackball is screwed up scrolling or not scrolling whatever its doing.
Does anyone have a link I can use go back to stock. I need a new phone what Tom do I flash
Sent from my Eris using XDA App
tperson1 said:
Does anyone have a link I can use go back to stock. I need a new phone what Tom do I flash
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=792026
It IS Lupus said:
use clockwork mod. be warned tho people have reported that using that their phone has bricked. but i didnt have problems with it when i was waiting on my referb with a working trackball. Call verizon and tell them your trackball is screwed up scrolling or not scrolling whatever its doing.
Click to expand...
Click to collapse
How do i install clockwork on an eris? ive looked around but everythings for the facsinate or aria or EVO
i had similar issues with my trackball not responding in recovery earlier this week
did some searching and found that i had to connect the usb cable and try some gentle wiggling - the usb port is so close to the trackball that it sometimes affects how the ball's movement is read
doesnt need to be plugged into PC, just the part that connects to the phone
i wanted to update Kaosfroyo to v38 and i had no control when navigating recovery screen or it would scroll to the bottom of the list without me touching anything
after doing some investigation i booted into recovery with the usb connected and held the plug where it connects to phone and tried holding the cord at different angles until it responded as i needed it to and presto! now running KF38 with no trackball issues
XDA has had all of the answers to my Eris problems so far, just have to do some digging
so I made an ultra bone head move. I orginally bricked my phone to hte point it said AST_STAT in red text I think learned of the vol up and down tick to put iit into download mode. I was able to flash and had a working device again although be it 2.1.
I should of really stopped at this point, I figured man that was easy I'll get the latest firmware and get back up to 2.2 well it bricked again I have the computer, phone and the ! I figured okay no problem its not as bad as last time right?
WRONG none of the button combos work and I bought a jig from mobiletechvideos.com and that just displays the same thing as above I can't get into download mode to save my life on my phone.
I've got a new one coming from T-Mobile as a swap but seriously the $450 axe they have hanging over my head doesn't feel so good I know there was a similar thread but it never went anywhere there was no resolution and I'm hoping one of you fine posters will have a trick to help me out of this jam.
I've tried every button combo nothing seems to do it I just couldn't leave well enough alone lesson learned but I'm hoping there is still a way out.
Thanks everyone!
...What did you try flashing that first time?
It wasn't per chance something that contained bootloader like one of the new Gingerbread ROMS was it? A few of them still have bootloader flashes which can brick you.
It would be helpful if you listed what you tried flashing and the steps you took.
When I brick like that, that's the only screen I get. If Odin sees your phone, you can flash it. The !--pc screen doesn't matter.
Sent from my GT-I9000 using XDA Premium App
Orginally flashed it with T959UVJFD.tar and 512.PIT using ODIN3 1.0 ODIN does see my phone I'll keep giving it a shot it kept freezing at Cache.rpf but persistence might pay off.
Thanks for the quick replies!
You should try using Odin 1.7. I found it works best.
Soo who wants the first handy J in the corner? J/K you guys are ****ing amazing you will be dumbfounded none the less.
So here is my situation.
MY Rig:
Dell XPS 420
Win 7
Wife's PC
Custom built Win 7 with ABIT Mobo
I D/L ODIN 7 it fails again at Cache.rfs so I pull the plug just like the first time around I turn it on and notice it isn't turning on quickly anymore so I use hte JIG BOOM DOWNLOAD MODE!!
My XPS will not flash my phone to save my life so once again I flashed on hers using ODIN 1.0 and same FW as mentioned above it failed on cache.rfs and I pulled the plug and put it in download mode again using two button (vol + -, USB + Battery) and it flashes it fine.
Seriously I'm in debt and I so want to move to CM 7 as my buddy runs it on his t-mobile 4G (the very first 4g phone can't remember name) but I think I'm just going to hold my horses on doing anything for awhile
I honestly think the XPS 420 chipset might not be good for flashing android phones I never ever could get it to go I even tried in a virtual environment running XP and same exact thing occurred every time.
sorry to repeat myself but thank you, thank you, thank you, thank you!
Okay, so I'm coming to Android from my Palm Pre via old skool WinMo, so I'm used to using the good will and work of others to make me look awsome smart in front of my friends, I mean, flashing ROMs and patches.
Anyway, I went and tried Joker's ICS 0.2 beta on my Photon, and while good, there were some things that I needed to use daily that just wasn't working well enough, so time to reflash to stock. Too bad I messed up the instructions and ended up removing CWM and locking the bootloader before getting the ROM loaded... yeah yeah. I still don't' know how I managed that one.
Long story short, I bricked it. Pressing Vol Down + Power would cause a BSOD while UP + PWR would only give me Fastboot, which would not allow me to load the factory ROM from inside RSD.
None of the other info I found matched what I ended up doing, so I'll share and maybe someone can shed some light or who knows, maybe it'll be helpful.
First, I did UP+PWR to get Fastboot and plugged in the USB cable. After that I started up RSD. While leaving RSD open, goto your command line and get to your fastboot directory.
Type:
moto-fastboot restart (or just "fastboot restart" if that's what your version calls for)
once it restarts, the phone will reassociate with RSD and automatically go into RSD mode where you can reflash the Moto Stock sbf.
The reason I had to do this was that I could not get the phone to load in any other mode besides fastboot and RSD was not having any of that.
Was there a better way of doing this?
Not to sound like I skadouche, but if you were able to boot into fastboot or any other of the boot methods, then it wasn't bricked. Bricked means that it might aswell be a "brick" because you wouldn't be able to do anything else at all with it. Fastboot is what I normally do when I fk stuff up as most of us do. Thanks though.
MoPhoACTV Initiative
Nah, I won't label you douche, because, well, yeah... I suppose it wasn't quite bricked, but as you couldn't get into any sort of recovery mode or RSD mode, it was quite difficult to get it to where I could flash it.
Multiple google and forum searches didn't turn up anything quite like what I was experiencing. Safer to put up one extra post on something I hadn't seen before and look like a tool than to say nothing and let someone else suffer if they happen to do stupid S*&t to their phone like I did
you dont know what the feeling of bricking is until youve sat at the bootloader screen for 20+ mins hoping it will finally pull up the rsd mode options
that engineering build scared the **** out of me XD
shabbypenguin said:
you dont know what the feeling of bricking is until youve sat at the bootloader screen for 20+ mins hoping it will finally pull up the rsd mode options
that engineering build scared the **** out of me XD
Click to expand...
Click to collapse
Somehow, I find it hard to imagine someone with your skill would have too much trouble with anything on these phones...LOL
Worry of "bricking" my phone was what kept me from flashing my phones as long as it did...
Luckily, there are a lot of great things out there from the gang over there at ACS (Thanks shabbypenguin and QBKing77) that make this 1000X easier for those of us lacking your skills
shabbypenguin said:
you dont know what the feeling of bricking is until youve sat at the bootloader screen for 20+ mins hoping it will finally pull up the rsd mode options
that engineering build scared the **** out of me XD
Click to expand...
Click to collapse
Anything that could scare you is worthy of a big budget horror flick.
"I Know What Phone You Flashed Last Summer" coming this June.
All I have in the way of true horror is HTC Apache unlocking. That is all. Oh yeah, and patching that damn thing so it changed Daylight Savings Time correctly.
So here's my story, I am not entirely new to rooting as I have successfully rooted my Motorola Droid, My Droid X2, My Acer Iconia a500 (twice), My aunts Lg something, and my mothers Kindle Fire.
So a few days ago my Droid X2 started acting up, and would go hours on end sometimes without working.
I was very happy to find out that Verizon would replace it with no hassle as it was less than a year old. I got the replacement yesterday and it's working great... that is until I found out it came stock with 2.3.5 right out of the box.
Now I have always trusted XDA forums and have used them for a long time (although I finally just registered today to ask this)
The only root method I can find is to downgrade to 2.3.4 and then root, then install voodoo root protector, then upgrade.
Now I saw a few things about possibilities of bricking your phone when trying to read those tutorials (I have never had to downgrade before) and I was a bit concerned.
I was mainly wondering, I don't care about loosing data on the phone. I have a backup sd card I can use if I need to format that, and like I said, the phone is new and actually doesnt have a single app I have installed on it yet.
Is there any easy way to go back down to 2.3.4 for my situation? I just got the free phone and don't want to brick it a day later you know?
From what I gather, you can SBF back down to 2.3.4 with no problem. There may be a certain way you have to do it though. I have never been on stock 2.3.5 so I cant tell you from experience. But Everyone says it's possible.
That's my question in a nutshell
Yeah, I read a tutorial about how to do it using RSDlite, which I downloaded to my comp.
Now what I'm cautious about is white file to use. One of the tutorials had one, now while I know a tiny bit about rooting I know NOTHING about flashing it back, I wasn't sure if there was a way that this could screw up my phone, as it seems everything tested is with a phone that had already been rooted, or if there is anything phone specific in that file, or even if it actually is an OTA original (I'd rather not mess around with anything customized right now)
Whatever is the easiest method for getting be back down, I know how to take it from there as I've done it before.
Thanks for the response though!
Excolo said:
Yeah, I read a tutorial about how to do it using RSDlite, which I downloaded to my comp.
Now what I'm cautious about is white file to use. One of the tutorials had one, now while I know a tiny bit about rooting I know NOTHING about flashing it back, I wasn't sure if there was a way that this could screw up my phone, as it seems everything tested is with a phone that had already been rooted, or if there is anything phone specific in that file, or even if it actually is an OTA original (I'd rather not mess around with anything customized right now)
Whatever is the easiest method for getting be back down, I know how to take it from there as I've done it before.
Thanks for the response though!
Click to expand...
Click to collapse
So you have never used an SBF file? If you would have used it on your broken Droid X2 when it wasnt acting right, it might have fixed your phone. An SBF file simply wipes everything of your phone (excluding your SD card) and flashes brand new software on it. The SBF files are provided by Motorola so its not like you are using something made by a dev and can break your phone easily. You should be able to use RSD lite to flash the 2.3.4 SBF file and you should be fine. But then again, I have never SBF'd from 2.3.5 to 2.3.4 personally so I would feel bad saying go ahead with no worries and something bad happen. So wait for someone else to respond first.
Thanks!
Thanks for that info!
Also, I doubt that would have fixed my old phone, it seems pretty much like a hardware issue. The screen will display static for hours on end (think like an old tv if you didnt have cable plugged in) I think it's a loose connection somewhere or something. I didn't bother to really troubleshoot it myself though because I was like "lets see if Verizon will give me a new one" and they did, and because they didnt have any "replacements" i got a brand new one, with a brand new battery, so I wasn't going to argue the fact
Anyway, if the file is from Motorola where can I get it? I saw on a verizon forum that they were not allowed to post it there (or is it "from motorola" in the sense it was leaked?)
Thanks for all your help so far, you've been great!
Excolo said:
Thanks for that info!
Also, I doubt that would have fixed my old phone, it seems pretty much like a hardware issue. The screen will display static for hours on end (think like an old tv if you didnt have cable plugged in) I think it's a loose connection somewhere or something. I didn't bother to really troubleshoot it myself though because I was like "lets see if Verizon will give me a new one" and they did, and because they didnt have any "replacements" i got a brand new one, with a brand new battery, so I wasn't going to argue the fact
Anyway, if the file is from Motorola where can I get it? I saw on a verizon forum that they were not allowed to post it there (or is it "from motorola" in the sense it was leaked?)
Thanks for all your help so far, you've been great!
Click to expand...
Click to collapse
Yeah, it does sounds like it was a hardware problem. Actually, I never thought about if motorola had a list of sbf files somewhere or if they were just leaked or what. I always downloaded them from threads like these. I just know they are made by motorola. You got me curious now. hmmm...
Duh
forget about my question as to where to get them, just saw the sticky at the front of this forum.
Although, it would be interesting to know if they were officially given out by motorola or leaked
Excolo said:
forget about my question as to where to get them, just saw the sticky at the front of this forum.
Although, it would be interesting to know if they were officially given out by motorola or leaked
Click to expand...
Click to collapse
What's An SBF File?
• SBF Is A File Leaked By Motorola That Is The System Image Flashed By RSDLite.
Taken from the Motorola Droid X2 FAQ page here
Excolo said:
So here's my story, I am not entirely new to rooting as I have successfully rooted my Motorola Droid, My Droid X2, My Acer Iconia a500 (twice), My aunts Lg something, and my mothers Kindle Fire.
So a few days ago my Droid X2 started acting up, and would go hours on end sometimes without working.
I was very happy to find out that Verizon would replace it with no hassle as it was less than a year old. I got the replacement yesterday and it's working great... that is until I found out it came stock with 2.3.5 right out of the box.
Now I have always trusted XDA forums and have used them for a long time (although I finally just registered today to ask this)
The only root method I can find is to downgrade to 2.3.4 and then root, then install voodoo root protector, then upgrade.
Now I saw a few things about possibilities of bricking your phone when trying to read those tutorials (I have never had to downgrade before) and I was a bit concerned.
I was mainly wondering, I don't care about loosing data on the phone. I have a backup sd card I can use if I need to format that, and like I said, the phone is new and actually doesnt have a single app I have installed on it yet.
Is there any easy way to go back down to 2.3.4 for my situation? I just got the free phone and don't want to brick it a day later you know?
Click to expand...
Click to collapse
bro, you wont have any problems downgrading/sbfing back to 2.3.4, i did it without any problems
i used sbf_flash through linux though idk about RSDLite
So after my battery ran out today I realized that Clockworkmod does not allow charging while the phone is off... This left me in a tricky situation where I could not charge my phone at all. I had seen others mention using another battery but I did not have one on hand. Here's how I replaced Clockworkmod with Amon-Ra to fix it (this also works for all recovery images that I know):
REQUIREMENTS:
-Computer with ADB
-Rezound with Clockworkmod or other faulty recovery
-Amon-Ra's recovery image (attached)
1) Unplug USB and remove battery
2) Put battery in
3) Plug USB into computer (with ADB installed)
4) Enter "adb devices" until you see your Rezound show up as recovery. During this time, the orange LED may either blink shortly first or be solid for a few seconds and then turn off. Once it turns off, it should be accessible over ADB.
5) Grab your amonra recovery img and use adb to copy to phone.
Example: adb push amon-ra-3.15.img /tmp/amon-ra-3.15.img
6) Flash the image to recovery.
Example: adb shell flash_image recovery /tmp/amon-ra-3.15.img
7) Reboot your phone (adb reboot) and repeat steps 1-3 (but this time using wall outlet)
8) Sit back and let Amon-Ra save your Rezound. Once your orange LED has been solid for over a minute, you should be good
Nice guide
Koush really needs to fix that problem or discontinue it for our phone
Sent from my Galaxy Nexus using Tapatalk 2
superchilpil said:
Nice guide
Koush really needs to fix that problem or discontinue it for our phone
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It is discontinued. I don't even really know where to get it anymore lol.
Granted, I don't use CWM, but nice job.
con247 said:
It is discontinued. I don't even really know where to get it anymore lol.
Click to expand...
Click to collapse
Rom manager. Also he offers touch for pay (which is what I mistakenly purchased thinking it could mount the internal sd. Either way though I agree, it is not safe for the average root user even to have a recovery that doesn't allow charging even through a wall outlet. It should only list Amon-Ra's under alternate recovery.
Chyrux said:
Granted, I don't use CWM, but nice job.
Click to expand...
Click to collapse
Thanks, I know the average user is using Amon-Ra or TWRP but figured I'd put this here so we have a clear guide for getting out of this situation where some users may end up returning their phone to HTC (possibly getting charged after the fact)
con247 said:
It is discontinued. I don't even really know where to get it anymore lol.
Click to expand...
Click to collapse
Its odd, those same people who can't search to find out how to fix the problem, can find CWM
Sent from my Galaxy Nexus using Tapatalk 2
I'm fairly new to the Rezound. Came from the Nexus side because I wanted a more multimedia-friendly device (better external speaker/camera/same res). I bought mine pre-rooted and flashed to Clean, which was pretty nice - until I ran into this issue. I bought another battery from Verizon and hooked the other one up to an external charger. I figure it won't hurt to have two batteries anyway.
I know a ton of people have bad things to say about CWM but is this really the only issue? It flashes just fine, right? I ran a nandroid on what I have now and tried to install the latest leak, but I got a ton of reboots. Eventually reverted back to Clean. Either way, thanks for the writeup. Would have saved me a ton of stress over the weekend, hahaha.
Nice work djh816. this was the thing i have always feared lol. matter of fact, this is a HUGE weight lifted out of my mind. Thanks so much for this. keep up the good work
nice guide but i dont think anyone uses cwm anymore. still, thanks
I do. Haven't had issues. I just, if you can believe it, charge my battery before I do anything.
Sent from my ADR6425LVW using Tapatalk 2
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
RED ZMAN said:
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
The OP of this thread are the instructions... Just do Steps 2-6.
Edit: or use hasoon2000's first AIO toolkit, which has AmonRa as a flash option (also another lingering source of CWM):
http://forum.xda-developers.com/showthread.php?p=22696442
RED ZMAN said:
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Haha I was fine as well with Clockworkmod Touch and had no clue it even had that problem until my battery finally drained all the way. Then I was SOL. But yea as he said, following those instructions simply replaces the recovery image. All your data will still be in tact (aside from your clockworkmod backups if you have them but Amon-Ra can read those too I think)
Yeah, I figured those instructions would work. You should advertise this as a how to swap between them also. There are others using CWM, and just not talking about it.
Thanks.
Sent from my ADR6425LVW using Tapatalk 2
I have an easier solution, while phone has been dead for 5-10 minutes, hold power button and as soon as screen flashes plug in the device. Works every time. I also have 3 batteries, 1 original, 2nd from my replacement from warranty, 3rd is extended. I don't ever even change batteries though.
Funny that people are still having/talking about this issue.
I remember when the issue first popped up on the Rezound and people were clueless. All kinds of theories as to the cause and solution.
I knew of the cause from a few phones back... CWM has a history of issues with charging while powered off. I learned of it from an initial release of CWM for a different phone would that when trying to charge with it powered off, would turn on the screen.
Easiest way is to run the command
adb reboot download
boom phone restarts...
I have had this modded version of CWM touch by someone else (I will let him say who he is just in case he does not want to take credit).
It is a modded version of CWM 5.8.1.4-Touch that solves the charging when off problem.
I can not support it but can assure you it works since I have been using it since the beginning of April. I do switch between this and AmonRa for testing my ROM but all my backups are with this.
Still need to copy the .hidenandroidprogress file from internal to external clockworkmod folder to solve the freeze problem when backing up or restoring.
Just install it just like any other recovery.
NOTE: If anyone want to take this and start another thread with it that is fine by me. I just don't have time which is why I never posted it before.
I ended up doing it through fastboot, as I'm a bit more familiar with that, but thanks for the notes and link. I'm now on Amon Ra.
Anything I need to know as a CWM user since, oh, the G1?
And do I need to worry about moving that file so backups work, like you did in CWM?
Thanks again.
Thanks man, this this is totally pimp, sent you a donation - get yourself some good beer!