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
Can somebody tell me what happened to my motorola atrix?It just suddenly turned white screen...i only got it for at least 2 weeks...it's like the lcd has been damaged but i haven't dropped it not even once...
have u rebooted it?
Can you post a pic of what it looks like?
I already have rebooted it...I did the restore factory setting and even did the hard reset..nothing works...
That looks software based since it seems to follow whatever is on the screen, rather than physical damage which would stay in one place. Have you considered flashing the phone back to stock?
http://forum.xda-developers.com/showthread.php?t=991072&highlight=sbf+flash
which one do i download?the 1.2.6 or 1.5.2? or is it both?
By the way my phone was pre-rooted when i bought it..may i ask how would i know what drivers should i use?32bit or 64 bit?thanks
Use 32 bit if you have a 32 bit computer, or 64 for 64. And flash 1.2.6 with rsd life, ota to 1.5.7, then ota to 1.8.3
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
Im sorry but im new to this...what is ota?what do you mean ota to 1.5.7 to ota 1.8.3
zmokez008 said:
Im sorry but im new to this...what is ota?what do you mean ota to 1.5.7 to ota 1.8.3
Click to expand...
Click to collapse
OTA is over-the-air (no computer required). What I suggest is a fresh data factory wipe along with flashing of 1.8.3 SBF (or if you want 1.5.7 to OTA). Whatever suits your fancy.
zmokez008 said:
Im sorry but im new to this...what is ota?what do you mean ota to 1.5.7 to ota 1.8.3
Click to expand...
Click to collapse
Follow the directions in my previous post to flash your phone back to completely stock software. Once that is done, go to Settings -> About Phone (bottom of the list) -> System Updates. You must be on wifi to download the updates. First, it will download an update to 1.57 (I don't think it goes straight to 1.83). Download and install that update following the prompts. Once that is done, do it again to get the 1.83 update. Now you have a fully up-to-date, and hopefully functioning screen, Motorola Atrix.
Since you are flashing back to stock, I recommend using gladroot to obtain root on the phone. This will avoid the formatting of your internal and external storage that gingerbreak rooting method would require. Gladroot files and instructions here: http://forum.xda-developers.com/showthread.php?t=1016060
Basically these are your steps:
Flash 1.26 SBF
Run gladroot.bat
OTA update to 1.57
run afterupdate.bat
OTA update to 1.83
run afterupdate.bat again
The batch files I referenced are in the gladroot download.
jimbush3 said:
That looks software based since it seems to follow whatever is on the screen, rather than physical damage which would stay in one place.
Click to expand...
Click to collapse
Physical damage would not necessarily appear in the same place all the time. It looks to me like the problem appears when a sufficient number of pixels in one column/row are white, and the white is then streaking into other pixels that shouldn't be white. Could indicate a problem with the display circuitry properly handling the voltages. I'd be surprised if this is not a hardware problem. I guess we'll find out after the OP reflashes the ROM.
GoodFoot said:
Physical damage would not necessarily appear in the same place all the time. It looks to me like the problem appears when a sufficient number of pixels in one column/row are white, and the white is then streaking into other pixels that shouldn't be white. Could indicate a problem with the display circuitry properly handling the voltages. I'd be surprised if this is not a hardware problem. I guess we'll find out after the OP reflashes the ROM.
Click to expand...
Click to collapse
Quite true. I was thinking of an impacted screen and not so much of design/production issues. I'm curious to see the outcome now too.
It didn't work...is there any other way?by the way my phone became unrooted after the process
by the way not all of it is white...during the opening of the phone where the logo of motorola comes up the line is colored purple and the icon of contacts when somebody is calling the line is also purple..
It sounds defective. Did you say you bought it rooted? Somebody might have dumped off a bum phone on you.
Sent from my MB860 using XDA App
I dont think there's something wrong when i bought it...It's still fine for 2 weeks..is there any other way?can overcharging did it?there's time that i charge it overnight..
Two things:
I have replaced 4 screens on my girlfriend's Motorola a1200 and 3 years later is still working. Screens go bad AND the internal cable can loosen over time and cause your problem. eBay usually has new screens for under $20.00 and you can Google for instructions on how to do it. It's actually fairly simple and you probably just need to re-seat your current screen cable. I seriously doubt it's anything other than a loose cable or worn out screen.
Sent from my SAMSUNG-SGH-I897 using XDA App
Can't be worn out screen...i just got it for at least 2 weeks..by the way whenever i browse my phone not all have this white screen like when i access the messaging page
I guess i'll just have to stick with it for a while...btw i found a useful apps that help me on my phone..it's called screen filter..while its activated the white screen can't be seen that clear and i read that it help conserve battery so it's like hitting 2 birds with one stone..anyway thanks for the help guys.
All, I've gone through many of the forums here and all I am now is confused. Issue: Had CWM and NVFLASH on and Honeycomb on gtab. Some issues, wanted to go back to stock. Followed instructions; however, now it's in a loop. I cannot get to it via PC. Holding power and volume key, see the 3 birds and "recovery key detected, goes to gtablet screen, goes to screen with a box (arrow in it pointing down) and status bar across bottom, goes to w/tap n tap screen, goes to screen with tnt; then reboots through the process again and again. I've spent the past two weeks going through the internet and reading the various methods to unbrick, none work; because I can't get to the internal SD card.
Is there a way to fix this? Is there a way to use the external micro-SD card? Or do I just need to throw this thing away? Any assistance would be appreciated. Oh, I've tried the Code Red and every other unbricking method I came across.
Thank you in advance, Michael
[email protected]
Since you are only experiencing a cycled boot loop then you are not bricked. There is still hope.
What NVflash file did you use to get back to stock?
Which bootloader do you want to run?
http://viewsonic-gtablet-for-dummie...268582d53a1&fw_sig_social=1&fb_sig_network=fw
This website helped me out allot when I was in a jam.
nobe1976 said:
Since you are only experiencing a cycled boot loop then you are not bricked. There is still hope.
What NVflash file did you use to get back to stock?
Which bootloader do you want to run?
http://viewsonic-gtablet-for-dummie...268582d53a1&fw_sig_social=1&fb_sig_network=fw
This website helped me out allot when I was in a jam.
Click to expand...
Click to collapse
I grabbed the latest one. Basically, I'm almost at the "throw it in the trash" stage. If there is a way to boot from the external SD card to load the stock 1.1 version; that's what I would like to do and give this to my niece. Thank you for replying.
Michael
There is a way to "install clockwork from external SD" - search that phrase and you should find it.
BTW- If you plan on trashing it, I'll pay for shipping to my house. I'll 'throw it away' for you
new_to-droid said:
I grabbed the latest one. Basically, I'm almost at the "throw it in the trash" stage. If there is a way to boot from the external SD card to load the stock 1.1 version; that's what I would like to do and give this to my niece. Thank you for replying.
Michael
Click to expand...
Click to collapse
Well all and all I know your fustration. The first link I beleive you are using is the Stock 1.1 from the 3588 branch. That one I used before and had nothing but issues. The best one to use is from the 4349 branch perfered with CWM pre-installed. After flashing that file shut the Tablet off during boot up. Then boot into recovery mode by holding down the volume + while pressing the power button. Do a Wipe Data Factory reset, Clear Cache, and then under advance Wipe Dalvic Cache then go back to main menu of CWM and reboot device. Make sure you don't select reboot recovery since that will not let you boot into anything but CWM. TNT TabUI will then boot up and you chould be good to go.
Thanks...but
Thanks to everyone. I still can't get this darn thing to connect to the PC or CWM to run. I would love to be able to just put it back to stock and be done with it. The more I work with Android devices, the more I'm convinced that I will stick with Windows or Apple. Android is great, but until there is a one size fits all solution; the tweaking and manipulation one has to do just to increase the functionality is what will be Android's downfall. Nothing is "simple" with Android and unless you're a programmer; there isn't much one can do with it. Partially it is the manufacturer's fault (i.e. Viewsonic) for putting out crap that doesn't even work; part of it is Google for not requiring standards for Android (yeah, no standards are great because one can explore/tweak/etc); and it is my fault (for this instance) for thinking that I could tweak and enhance my system. So, I'll put this thing up on Craigslist and see if I can make some change with it and get a newer device or just stick with a laptop and be done with it. Thanks again everyone for all your help.
$$Price?
Sent from my Droid using XDA
new_to-droid said:
Thanks to everyone. I still can't get this darn thing to connect to the PC or CWM to run. I would love to be able to just put it back to stock and be done with it. The more I work with Android devices, the more I'm convinced that I will stick with Windows or Apple. Android is great, but until there is a one size fits all solution; the tweaking and manipulation one has to do just to increase the functionality is what will be Android's downfall. Nothing is "simple" with Android and unless you're a programmer; there isn't much one can do with it. Partially it is the manufacturer's fault (i.e. Viewsonic) for putting out crap that doesn't even work; part of it is Google for not requiring standards for Android (yeah, no standards are great because one can explore/tweak/etc); and it is my fault (for this instance) for thinking that I could tweak and enhance my system. So, I'll put this thing up on Craigslist and see if I can make some change with it and get a newer device or just stick with a laptop and be done with it. Thanks again everyone for all your help.
Click to expand...
Click to collapse
Sorry to see that your experience with your newly found failure did not come with a price of knowledge. Truth be sayed I am no programmer, geek or knowledge of script writing either, but what I can pass along to all new-to-android persons is that your best path is to read and follow instructions to the T or you will end up with a expensive paper wait. The web link I posted above is pretty self explained and I give that man credit because I was a newbie too once. Then somewhere in these forums I found that website and was able to recover from just about anything that happened to my poor Gtab. Hell, I even had to drill a hole in the back of the case just because I wanted more and there was ICS from Team DRH. But truth be said that web link is your path and only path to going back to the stock UI and recovery.
Price
50 plus shipping to us only
new_to-droid said:
50 plus shipping to us only
Click to expand...
Click to collapse
I'll buy it. DIBS EVERYONE!
PM me with your info and I'll have the money sent right away.
Even if I couldn't get it to work, I could use it for parts for my current g-tab.
EDIT: Don't mind my post count. I'm very active on SD, just not here.
Just wanted to mention that I have not been PM'd or replied to. Hope this guy got his tab to work.
Hi everyone,
First time poster here, but don't worry I haven't bricked my phone while trying to flash it
Unfortunately, I have a XT910 with a damaged display, I was wondering if anyone has had any ideas that I could implement. My first thought was to try and bypass the need for the screen on the phone via the HDMI out, but it seems you need to select the option for output via HDMI on the phone itself.
-Everything seems to work except for the display
-Device connects to computer and is able to transfer files (suppose I could try and put it into recovery, but I'd be doing it blind)
Thought at the moment is to try and load a rom which would force the use of HDMI out when detected or try and mod it myself (I'm not sure if its possible)
If I dont get any useful help within the next week, first dibs gets free* parts
But most apps are based on touch. How are you going to navigate or are you just trying to get files off of it? You could also get a replacement screen.
I'm in the same situation. Touch works still very well but be aware of smithereens...
Edit: Sorry, wrong thread. I need to go to bed!
iBolski said:
But most apps are based on touch. How are you going to navigate or are you just trying to get files off of it? You could also get a replacement screen.
Click to expand...
Click to collapse
Im not looking to use it in a regular phone way, was trying to find if there was a possible way to set it up with more computer-like functionality. Because it still works i should be able to download apps onto it using play.google.com and do it via my computer(for superuser, busybox and terminal)
Because the screen is actually glued to the LCD/digitizer it needs to be replaced as a unit. With is mucho expensive ($220ish) i.e not worth my while. I have other phones that I can use, I was just looking for a new project
HybridOfTheTwo said:
Im not looking to use it in a regular phone way, was trying to find if there was a possible way to set it up with more computer-like functionality. Because it still works i should be able to download apps onto it using play.google.com and do it via my computer(for superuser, busybox and terminal)
Because the screen is actually glued to the LCD/digitizer it needs to be replaced as a unit. With is mucho expensive ($220ish) i.e not worth my while. I have other phones that I can use, I was just looking for a new project
Click to expand...
Click to collapse
without being able to use the screen, I think it's going to useless. You have to touch the screen in order to launch and interact with apps since they are all written with a touch screen in mind.
Sent from my Eclipsed 1.3 Droid RAZR via Tapatalk.
Before I explain my problem, let me first say that I am a novice when it comes to modifying phones. Shortly after buying my Razr, I knew that I wanted to root my phone, but I didn't know how. I found a program (that I can't recall now) rooted it, and had no problems. My problem came when I wanted to accept the OTA upgrade. I tried using Voodoo to keep my root while I accepted the OTA update, but that's where things when wrong. I don't know everything that went wrong because it seemed like nothing that I was doing was having any effect. It was having an effect, but not the effect that I wanted. After some uneducated decisions on my part, I found my Razr stuck in a bootloop. After trying to "fix" things, I gave up on it, but I decided to hold onto the phone. I replaced it with an HTC Rezound and moved on. I chose the Rezound only because it wouldn't take long to get it and it was affordable.
Last week, I decided that using the Rezound (it's definitely not all bad) has made me want to revive the Razr. I ordered BlackHat's adapter and used MattLGroff's utility (http://forum.xda-developers.com/showthread.php?t=2192467) to wipe my phone and flash JB.
This worked, with two exceptions. First, the phone still wouldn't charge. I came across a forum post that talked about successfully charging a phone in the car when it wouldn't charge inside with a computer or wall outlet. I was skeptical, but it worked. After charging the phone in the car, I can now charge it inside with a computer or wall outlet.
The second problem remains, and I am wondering if something that I did to soft-brick the phone caused a hardware problem. That seems unlikely, but I am new to this, so anything's possible as far as I'm concerned. In the attached picture, you can see that the bottom third of the screen shows up almost like static on a TV, but it's broken down into a grid. Also, the right half of the screen shifts up almost the height of the screen. Both of these problems come and go, but the "static" at the bottom of the screen comes much more often. I have to navigate through folders and menus before the shifting problem happens. Regardless, if I am at the home screen, for example, and I shift right or left (or navigate anywhere for that matter), the screen will be clean with no errors for a moment. After a second or so, the glitches usually show up.
I almost forgot about the last issue. When I wake the screen, it's quick and responsive; however, when I turn off the screen (by tapping on the power button), there is a lot of lag in the animation. Normally it would be a quick and smooth transition to the thin, horizontal line, and then it would quickly disappear. Now I can watch as it slowly blurs and stretches. It works, but it lags. This happens every time I turn off the screen.
Does anyone know what could cause this? Am I beyond repair? After typing this out, I doubt that it's a hardware problem, mainly because the static and shifting are not constant. But again, I'm totally new to this.
If anyone has any suggestions that involve utilities, then it would be ideal if I can use Linux. I have access to a Windows computer, but not at home.
Thanks in advance to anyone who can offer some insight.
Does anyone have any insight into this? Two months later and I'm still stumped. It doesn't matter how I use MattLGroff's utility...the same issues are still present. Could I maybe use a utility that will revert me to an older system? That way, I might be able to receive an OTA upgrade to JB.
I'm grateful for ANY input...
Thanks!
Just try to update through rsdlite, search for fastboot files here in development or google it and find the right one for your region.
Sent from my XT910 using xda premium
AztekSoul said:
Just try to update through rsdlite, search for fastboot files here in development or google it and find the right one for your region.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Thanks for the response, AztekSoul. I would have responded sooner, but I've been pretty busy.
I run into some trouble when I try your suggestion. I've downloaded RSDLite, and I run it through Wine. I am able to load the XML file that comes with build 6.7.2-180_DHD-16_M4-31/Blur_Version.6.16.211.XT912.Verizon.en.US (found here: http sbf DOT droid-developers DOG org/cdma_spyder/list DOT php).
My problem is that RSDLite won't show my device. I've tried clicking "Show Device" when booted into AP Fastboot and when booted regularly. I've tried plugging in the phone with Team Black Hat's factory adaptor (found here: http shop DOT teamblackhat DOT info/Factory-Adapters-motadapt DOT htm) and plugged in with just the USB cable that came with the phone.
It seems like nothing I do will get me any further. I also tried to enter Recovery mode, but I get the lying down android and the red triangle with the exclamation mark.
If you have any further ideas, I'd be grateful to see them. Thanks!
BTW, sorry about the URLs. I can't post links because I haven't submitted at least 10 posts to the forum.
neffje said:
Thanks for the response, AztekSoul. I would have responded sooner, but I've been pretty busy.
I run into some trouble when I try your suggestion. I've downloaded RSDLite, and I run it through Wine. I am able to load the XML file that comes with build 6.7.2-180_DHD-16_M4-31/Blur_Version.6.16.211.XT912.Verizon.en.US (found here: http sbf DOT droid-developers DOG org/cdma_spyder/list DOT php).
My problem is that RSDLite won't show my device. I've tried clicking "Show Device" when booted into AP Fastboot and when booted regularly. I've tried plugging in the phone with Team Black Hat's factory adaptor (found here: http shop DOT teamblackhat DOT info/Factory-Adapters-motadapt DOT htm) and plugged in with just the USB cable that came with the phone.
It seems like nothing I do will get me any further. I also tried to enter Recovery mode, but I get the lying down android and the red triangle with the exclamation mark.
If you have any further ideas, I'd be grateful to see them. Thanks!
BTW, sorry about the URLs. I can't post links because I haven't submitted at least 10 posts to the forum.
Click to expand...
Click to collapse
hi,i had the same bug with rds lite didn't show me the spec of the phone,but only --------.
try anyway and remember to have the motorola driver in the pc (i don't know if works with wine,i had try only i my other windows pc)