Hey all, I'm new here and to Android phones in general.
I just picked up a Photon, not the Q, from a friend who had flashed it to Cricket. I'm looking to put it back to Sprint and replace the Duramax I have, but I'm not smart enough in phone tech to do it. I read somewhere that Motorola made it almost impossible to change PRLs and all that, and everytime I do the ##PRL# deal the screen shuts down for a split second and then pops back up the dialer screen, that happens with a few different ##codes. I've found a few different posts about how to do it, though pretty much all of them are for EVOs, but nothing in it seems to work for me, plus they assume one has the general know how already to do it. I'm a pretty quick learner and don't mind spending time getting to know different systems, so I was wondering if anyone could give me any extra info or links that could set me in the right direction. I appreciate your patience in this, I just want a better phone...
I'm looking through everything about flashing and I'm losing heart pretty quick. I was in the marines for four years and I though they had a lot of acronyms, holy crap... I'm about to call it quits and toss the phone unless there really is an easier-to-understand way of doing it. I don't care about rooting it or anything, I just want a smartphone that works with Sprint...
mrtoby86 said:
Hey all, I'm new here and to Android phones in general.
I just picked up a Photon, not the Q, from a friend who had flashed it to Cricket. I'm looking to put it back to Sprint and replace the Duramax I have, but I'm not smart enough in phone tech to do it. I read somewhere that Motorola made it almost impossible to change PRLs and all that, and everytime I do the ##PRL# deal the screen shuts down for a split second and then pops back up the dialer screen, that happens with a few different ##codes. I've found a few different posts about how to do it, though pretty much all of them are for EVOs, but nothing in it seems to work for me, plus they assume one has the general know how already to do it. I'm a pretty quick learner and don't mind spending time getting to know different systems, so I was wondering if anyone could give me any extra info or links that could set me in the right direction. I appreciate your patience in this, I just want a better phone...
Click to expand...
Click to collapse
I would say don't give up. I think it's quite simple.
Go here and read the last item in the post: http://forum.xda-developers.com/showpost.php?p=20331623&postcount=6
The pack below made by loki should have everything you need to flash an sbf file in rsdlite. I have never gone back to stock, but I did this process when I unlocked and rooted.
http://billionuploads.com/users/LokifishMarz/31/SBF's & Root-Unlock
You may want to confirm some of this with someone more experienced, but usually if you break something, it can be fixed.
I really really appreciate your response and suggestions knG333.
I tried what was posted, flashing the "1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US.sbf" file through RSD Lite a couple of times, but each time it would tell me there was an error flashing it. Do you know if, besides RSD mode, the phone has to have any other settings on it? Like, does debugging have to be on or anything?
Please forgive my ignorance in this, we all started from somewhere, right?
mrtoby86 said:
I really really appreciate your response and suggestions knG333.
I tried what was posted, flashing the "1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US.sbf" file through RSD Lite a couple of times, but each time it would tell me there was an error flashing it. Do you know if, besides RSD mode, the phone has to have any other settings on it? Like, does debugging have to be on or anything?
Please forgive my ignorance in this, we all started from somewhere, right?
Click to expand...
Click to collapse
There is one error message that is normal. Have you tried booting the phone up after flashing in rsd despite the error? "*RSD lite has a known bug where it will give a "failed" error during the final "rebooting phone" phase. IGNORE THIS ERROR AND MANUALLY REBOOT PHONE "
knG333 said:
There is one error message that is normal. Have you tried booting the phone up after flashing in rsd despite the error? "*RSD lite has a known bug where it will give a "failed" error during the final "rebooting phone" phase. IGNORE THIS ERROR AND MANUALLY REBOOT PHONE "
Click to expand...
Click to collapse
Yeah, I rebooted it manually and nothing seemed to have changed. Plus it said it failed during the flashing stage, not during the final rebooting stage, it didn't even get to the rebooting stage.
When the phone shows up in RSD Lite, is the program supposed to show all the details of the phone like IMEI and such? The phone is being recognized by the program, but only the model number is coming up, all other fields for the phone are saying N/A. Am I supposed to put the phone in any specific mode before hooking it up to RSD Lite besides RSD mode from the boot screen?
My previous distress has turned into stubborn perseverence, I'm going to get this thing fixed
Related
Got my gTab yesterday. [VERY EXCITED!]
Plugged in wall outlet, waited 4 hours to charge.
Connected to WiFi.
Updated TapnTap, as instructed.
My Vist Ultimate computer didn't see the gTab when I plugged it in, at least not so I could get to the root directory.
So I went to an old XP and tried that. It worked.
Wanted to Root it, so I installed (sorry if that's not the correct word) ClockworkMod v08.
So far so good.
Then rooted TnT Lite v 4.2
Still good.
Then rooted TnT Lite suppl 4.25
STILL okay.
Then went to gMail. Added my gMail account. (An account I use for business.) It took a LONG time to do whatever it was doing. So I went to do something else, thinking it would continue doing it's thing in the background. I was wrong. It messed up, and I kept getting error messages.
Next thing I know, I'm somehow in that infinite boot loop.
It was about 2 am, and I was tired, and... panicked!
Next thing you know I'm freaking out and went hog-wild (while following directions to the letter), to get my brand new toy to work.
I did nvflash windows, still infinite boot loop. I tried putting the vanilla recovery 3588 on there. Still infinite boot loop.
Kept at things, trying everything I read, and STILL... infinite boot loop.
Then I figured it was time to try to get my Vista computer working so I wouldn't have to keep transferring stuff from the Vista to the XP to the miscroSD card to the gTab, and followed directions about APX mode.
I was delirious, exhausted and scared, and kind of went postal (in a frenzied OCD sort-of way), trying everything and anything to get rid of the infinite boot loop.
Now it won't even power up. (AT ALL!) I think I gave it a heart attack, or possibly a stroke. And that's with not even owning it for 24 hours!
I've tried the long 45 second power hold, then the short one. [Did that about 37 times.] I've tried power and Vol+. Nope. Then did a few power and Vol-, just to really freak the poor sick, dead thing out. [Like kicking the proverbial dead horse, I guess. Trying to see if there was any life left in it.] I even read to turn off the lights to see if there was a faint glow. But nope. No glow.
I will now follow the directions from another post, and will let it just sit for 24 hours (if I can survive the wait) to let the battery discharge and then see if it will boot. [After this nightmare, there is no WAY I will take off the back and hit the reset button--thereby definitely voiding my warranty.] But I hope I'm not like the woman from the forum thread: http://forum.xda-developers.com/showthread.php?t=968177
If I am, and can't get this thing to power up, do you think WOOT will let me return it???? I'm so upset that I broke my new toy so quickly. If anyone has any suggestions about getting this thing to boot up, I'd appreciate it. [at this point, I'd be happy to have it boot up in the infinite boot loop!]
Oh, and one last question, how does having it turned off (because I can't turn it on) and sitting there drain the battery to the point that it needs to start fresh after a mere 24 hours with no activity? Is that typical for tablets?
THANK YOU to anyone who can offer advice on what to try next or how to remedy this problem. Please keep in mind that I am good with PCs and laptops/netbooks, but am VERY new to this whole android and tablet things, so if you send instructions, please give implicit directions (as though you are instructing a 3-year-old), without feeling as if you are insulting me. [Please believe it's what I need, and will appreciate. As will the other wooters who just turned their gTabs into brinks] And know that you will be helping Roebeet by answering my questions, because the poor guy must be exhausted from all of us lay-peoples' foibles and mess-ups. [The man seems to be a God at this site!]
Did you do what is mentioned right after step 10 in this thread?
http://forum.xda-developers.com/showthread.php?t=865245
"If your tablet bootloops…Also may be required to get market running correctly on some ROMs...
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. Then, redo steps 7-10. This erases all data on your tablet, including backups."
But first... switch to decaf and get some rest... ;-)
Panic doesn't help.
It might actually be powering up but staying in APX mode. I've seen one do that. If that's the case you can still nvflash it back to normal. Let it charge for 15-20 minutes and leave it on the charger. Try to start it up and see if your pc can see it.
You maybe got the bootloop because your tab had sleep death while syncing. Was the error you got by chance something like process.acore? If so that is a classic error that happens after syncing contacts, sometimes there are empty contacts with no data that make the tab go nuts. Simply deleting the bad contacts solves the problem.
A simple wipe data/cash/davlic would have been the first place to start. Breathing helps when stuff goes wonky.
If you can get it to recovery a repartition is totally necessary. Deffinetly... and maybe some whiskey ....
Good luck.
good luck with woot return, dont even think they do it.
I wouldn't worry about the warranty. You already voided it when you rooted the device.
I'm so sorry, guys, I didn't check off the subscribe notification, so I didn't know that anyone had written.
cdavisccs28, I didn't do that while the tablet was boot looping, but somehow it went from bootlooping to complete death.
K J Rad, it wasn't charging, and wouldn't boot. [And you can probably guess, I tried numerous times.]
Mantara, the death in the middle of syncing certainly didn't help it, and, as you suggested, might have been the last nail in the coffin. The whiskey suggestion was funny! Actually I, personally don't drink, but as you might have deduced, I'm a carrier. [AKA: I've been told that I drive people to drink.]
spike378 & filterking: Yup, I think you are both correct. How I managed to spike from "excited as a schoolgirl" to "completely tanking" in less than 24 hours amazes even ME! [And I know me, and am used to me! I think that was a personal record!] [If I don't laugh about it, I'll cry!]
THANK YOU ALL for replying! Your time and concern meant a lot to me, but I think this baby is totally bricked! Elvis has DEFINITELY left the building! If I do get another one (I'll have to start saving again), I might be too afraid to play with it. I really am good with PCs and notebooks, so I might just keep staying with what I know. YOU GUYS ROCK, for trying to help me, and I really appreciate it!
Same problem. I booted the device up, and connected it to WiFi. Then it gave a popup where it asked to update to the newest version. I said okay, and let it do its thing. Then it restarted into a bootloop. So, I turned the device off, and tried to turn it back on, except -- nothing. With the USB plugged in, it's not recognized by the computer at any time after I press the power button. I've been trying to get it to boot for an hour now and it's still just sitting there with a black screen. Not even a backlight is showing. Anyone know of any solution? Or is it time to ask for an RMA from Woot!?
h.nocturna, WOW, you didn't even get to the part where you started doing everything and anything (in a frenzy) to get it to work properly! That might be a good thing, h.nocturna, because you haven't voided your warranty! You might need to send it to Viewsonic to be fixed (since it messed up while you were doing their update), but at least you can do THAT! I mailed my brand new brick to my son up in college and gave him this site, and told him to have a blast, and do whatever he wanted with it. [He's known me his whole life, and said even HE "can't fathom my destroying something so completely in less than 10 hours."] I wish you luck!
Oh, one more question that will help the masses, I'm sure. So how do you get your computer to recognize the device as a hard drive, when it is plugged in to a Windows PC (without voiding the warrenty, of course)? [Vista Ultimate does not recognize it, and neither did Windows 7.] Please give step-by-step instructions for the lay-person. [By answering this question, at least we will solve THAT problem for folks!]
badtypist,
I wrote you a fix last night and when I went to save it the Forums had been shut down and do it didn't save to post --
and I had been on the road and was exhausted and just couldn't stay up long enough to redo it if and when they came back up. Sorry.
You simply needed to find one solution and then let us get down the procedure to follow to fix it.
Several people in the past have gotten to the point where you were. I read two fixes.
One was some people were able to get the tab to start again by playing with the
power switch -- hold it for long, long times and then press a short startup, etc. Somehow they got that to reset and start.
Somewhere else in the forums -- and I have never done this with either of my tablets --
there are a few threads where someone in this kind of situation opened up
the tablet card and simply unplugged the battery for 10- or more seconds. There also
is a reset button inside the case as shown in an old thread where someone opened a
G-Tab up and took pictures.
If any of those three choices get to where you can either use power / volume - to get
into NVFlash more ---- or to where we can load CWM -- then you are in fair shape.
LOTS AND LOTS OF BOOT LOOPS ARE ASSOCIATED WITH PARTITIONING. Simply
getting into CWM and re-partitioning to 2048 and 0 and then using CWM to "Fix
Permissions" will get it working. CWM also will let you wipe the cache and wipe the
factory data, which sometimes will allow and NVFlash to come on up and work right.
You see, we were not dead by any stretch.
You might pass this on to the recipient of the tablet.
Also, so many people are trying to do so much that is over their heads -- and so many
people are borking their tablets -- that this site and the folks that can help -- just can't communicate. Sad day.
I wish you luck. Hope this helps.
Rev
EDIT: Well, I guess we missed the boat completely. Evidently she mailed of the G-Tab and checked
out for good!!!
Hi Rev! Sorry I didn't get back to you sooner. I TRIED to get back to you sooner, but I think this site was down, because it kept timing out and wouldn't let me get to the site OR the conversation thread! I tried a few times, then tried later, and now just tried again!
I think you guys are getting BLASTED with desperate lay-people from the over 10,000 tablets sold on Woot who have "borked" their tablets. (That's a funny word, Rev! I hope I'm using it properly! And please note, although the WORD is funny, the actual situation is NOT funny!)
Yes, I mailed the offending frustration-linked object to my son, and can't "take it back," but perhaps I will beg for and borrow enough money to try again, sometime soon! If I do, I will come back here again sine I feel I have bonded with the wonderful, sharing folks on this site. (I'm a she, by the way, not a "he.") I admire (okay, worship) the folks who help us lay-people out so we don't sit alone crying and trying to power/Vol+ in solitude!
I've read your other posts previously, Rev, and you are so wonderful to help us n00bs! So please remember "badtypist" (hopefully with good thoughts) and when you hear my name again, let's hope it's to say... THIS TIME I ROOTED IT CORRECTLY!!!!
Thanks again, for your time, Rev AND the rest of you, which wasn't wasted, because I sent my son this link and he will (in his spare time) read through it to fix HIS new tablet. [I think he kind of liked that his mom messed up! He got a VERY expensive new toy, if he can fix it.]
Perhaps I'll talk with you soon...
badtypist (and bad ROOTER. Or is it ROOTERIST? Or maybe ROOTIST? Whatever the proper term, I think we can all agree that I AM bad at it!)
Gtab Update Problems
So, I would agree with some of the posts above. I would also point out that you have two options (or some combination of the two):
1. Try to return the tablet, or put in a warranty claim (the warranty specifically does not cover modification\rooting)
2. Try to fix it yourself
I tend to choose #2 f I think the chances are better than 50/50 in my favor. Also, if the hardware is okay, you can have it fixed in 20 minutes.
The experience that the OP went through is EXACTLY why I discourage newer g-tablet owners from rushing in and flashing alternate firmware to their tablet. I am often chided for this recommendation, but I believe that it is unwise to modify a brand new tablet.
If you still want to mod it, you should have a backup plan. I save my update file to an external USB drive. You should then be able to re-install the stock update by placing it on a microSD card. You need to rename it to update.zip, and add a file that tells it to look at the microSD card for an update. I am a but fuzzy on the specifics, but that file is named "command", and I found it somewhere here in the forums.
As I plan on modding my newer woot tablet (or maybe my older Sears one). I will first set this up, and will work out the details.
Hi buzzzard, thanks for the great info! VERY helpful. I did see that video while researching the gTab, but didn't bookmark it, so I appreciate your adding it here! My son will see all your posts and will use all of your suggestions to try to raise my brand new gTab from the dead! [It wasn't even in zombie mode when I shipped it to my son, so we'll see what happens! I'll keep ya'll informed.]
wasserkapf, you are probably right about not jumping in with both feet for us n00bs. And I most certainly don't mean to be disrespectful in ANY way, but I have a (serious) question... if I'd kept the tap-n-tap and played with it for a while, how would that have changed things for me if I eventually decided to root it to a faster, better OS? [I'm not meaning this sarcastically, I really want to know what I'd have to learn in order to change the results I had, in case I ever do this whole process again, or in case others out there are (hopefully) learning by my mistakes.] What would you suggest lay-people should be learning about the gTab BEFORE attempting to root it? [The answer to this question wil help a LOT of folks!]
buzzzard,
I have always understood -- and I don't want to know bad enough to spend the time
researching it -- that the warranty is void when you load non-standard software.
And even if it were not, I have real questions about messing up a computer and then
taking it back to the seller as if it were faulty. Seems to me there is a dishonesty
component in that equation.
I think modders SHOULD accept the risk that they can trash their tablets -- and that
if they do then the loss is theirs.
Rev
P. S. -- I've tried to say this much without starting a flame war -- if you do I won't
answer you and will ask the moderator to close and hide the thread.
badtypist said:
wasserkapf, you are probably right about not jumping in with both feet for us n00bs. And I most certainly don't mean to be disrespectful in ANY way, but I have a (serious) question... if I'd kept the tap-n-tap and played with it for a while, how would that have changed things for me if I eventually decided to root it to a faster, better OS?
Click to expand...
Click to collapse
For one, this will give you time to read up and learn more. I can tell that you are confused by all of this. You don't "root it to a faster OS". Rooting is a method to gain root privileges on the tablet. To you windows users, root is the equivalent of Administrator. There also is only one OS available for this tablet, and that is Android. Some have made modified/customized versions of Android, but it is still Android.
[I'm not meaning this sarcastically, I really want to know what I'd have to learn in order to change the results I had, in case I ever do this whole process again, or in case others out there are (hopefully) learning by my mistakes.] What would you suggest lay-people should be learning about the gTab BEFORE attempting to root it? [The answer to this question wil help a LOT of folks!]
Click to expand...
Click to collapse
There seems to be the misperception that you have to install a custom firmware to get root privileges or Android Market access. This can be done on the stock firmware, and then makes the tablet much more useful.
butchconner, I know you weren't talking to me, but I am taking full responsibility, and am hoping my son can resurrect my gTab, and I DO hope there will be no flaming, as well. ["There's no need for flaming. It's unsportsmanlike, kind-of rude and unproductive," said the mom to all reading this thread. So please don't flame so this won't get deleted for other poor people who "bork" their gTabs.]
badtypist,
wasserkapf was around when I got my first G-Tablet -- when we were all getting started last November.
You have no idea how bad the software was back then and the things we had to do to make things work.
It wasn't a question of 10 different ROMS and whether it was fast or not -- it was a question of making it work.
But I agree with wasserkapf (and I don't mean this comment particularly at you ) that
people are trying to do too much to fast. In addition to being a minister, I also was
an exec in the IT field for 30 years. I learned to read the docs, to move slow, to make sure each step was
successfully completed before moving on, to test things that
I'm not sure of -- and a whole host of other things that IT people use to operate their
company's systems without crashing it and losing data.
I helped a guy along the way who said he was inexperienced and that his tablet was in
the same kind of situation yours ways. He had gotten his G-Tab, charged it up, and had loaded EVERYTHING he could find on it.
Three or four different ROMS including an
experimental ROM he had been warned was risky. Yet he was having to ask what
recovery was and where to look for files and other basic questions.
I think everybody should get their tablet, upgrade to the latest version of stock, install z4root and
Titanium Backup and learn to use them, then install the latest version of Angry Birds and whatever useful software they need -- and then enjoy
that for a while while they learn the ins and outs of modding.
I help people because of the kind of person I am and because I am retired and have
some time to devote. But I also will be honest and tell you this -- I don't suffer
obnoxious, foolish people well -- and there are folks I just don't help because someone gave them good advice
and they didn't listen........I help folks who need and deserve to be helped.
The alternate ROMs are nice. And it's neat to add market and other useful stuff to
your tablet. But none of those kinds of things are so important that they are worth
what some folks do.
Nuff said. I don't respond to flames. And when you have been helping people as long
as I have, then you can have your opinion.
Peace,
Rev
Update Failure from 45.2.7 to 45.3.6 SOLVED!!!!
LOTS of people who purchased NEW Photons in the past few weeks have phones that shipped with a faulty image from the factory. These phones shipped with Software Version 45.2.7, but are ABSOLUTELY UNABLE to upgrade to 45.3.6. Anytime you try to update, the installation stops at 30% and quits. The common error message has something to to with the AccountAndSyncSettings.apk file.
I've figured out a FIX to the update failure. It may seem like it's a bit risky, but if you're on the last day of the 14 after initial purchase when you can swap out the phone no questions asked, it's worth a try. Actually, it's pretty simple without a lot of heavy lifing. Keep in mind, the phone this worked on had very few apps installed and was NOT rooted. I work in the IT field, but have NEVER done any modding - and I found it quite easy to do.
Some Background: My phone was purchased NEW direct from Sprint on 10/08/2011. It came with software version 45.2.7. When attempting to upgrade to 45.3.6, I received the now infamous error that has something to do with the AccountAndSyncSettings.apk file. Tried EVERYTHING the first few days with the phone - no upgrade success (about 15 factory resets). Made multiple posts on this board and read all of the responses for days. NO UPDATES from Sprint or Motorola. So, I took the phone back to a Sprint store for a 'no questions asked within 14-days exchange'. Never activated email, didn't even sync my contacts. Just went straight to the update. The new phone was also a 45.2.7 Software Version phone, and as you can probably guess, Update Failed on the 2nd phone as well. Went to THREE Washington, DC area Sprint authorized repair facilities to see if they can 'manually' update the phone, or even re-image the phone. Sprint was USELESS!!! Not only did the 'technicians' (and I use that word VERY loosely) not know anything about our problem, they had NO means to manually apply an update or write a new base SBF (system boot file) to the phones. Finally, after sitting in traffic coming home from work today, I had reached my breaking point.
The Fix: After days of scouring websites and phone calls to Motorola and Sprint (those were nothing more than a waste of cell minutes), I figured maybe I could mess with it myself. I had been hesitant because I was afraid of 'bricking' the Photon and then I'd have nothing more than a $200 paperweight. Then it hit me. What if it was already 'bricked'? Somebody has had to have done it to their Photon already. If they had, they must have looked for a solution. If there was a 'recovery solution' for a bricked Photon, maybe that fix may solve the problems we are all having with our BRAND NEW Photons.
Searching last night, I found a link from a few months ago. As a new member, I'm not allowed to post the link. But if Google these exact words, the VERY FIRST return is a page from the AddictiveTips website.
Came home from work, poured myself a cocktail and I went to work. First I downloaded the SBF. Now this takes the phone back to the version PRIOR to 45.2.7 (sorry, forgot to write that down when taking my notes). When you follow the link to download the SBF, there are a bunch of link options. Some have been taken down, others are still working. The file you want to download is 471MB and has this filename:
1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US
Then I downloaded the RSDLite software and drivers. I used a 32-bit Windows 7 laptop and installation went without a hitch. There are 64-bit drivers, but I'm not sure how they work. I did read where 'some' people had problems with the 64-bit varieties, so that's why I made a point of doing it on a 32-bit PC. From there, the instructions on the above listed link worked PERFECTLY.
There are a few things to keep in mind. BE PATIENT. This does take a while, and there were a few times that I wondered if something went wrong. It may hang at some stages for a few minutes, be patient.
Once I flashed the phone with the SBF and it was done installing and rebooting, (much to my amazement) all of my apps and customizations were in tact. I pulled my SD card to be safe, but I suspect it wouldn't have messed up my SD card. I would pull it prior to flashing just to be safe. If you want to take one extra step just to ensure success, you could do a factory Reset PRIOR to doing the flashing. I didn't have to, but it probably wouldn't hurt.
Literally seconds after it booted into the OS for the first time post SBF flashing, I was alerted to a software update: Update 45.2.7 (6.5MB). Downloaded rather quick and promted me to install now or later. I pressed install and away it went. Once again, be patient. It takes a few minutes. The progress bar moves rather steadily until it reaches 75%. Then it appears to stall/hang there for a few minutes. Then, the install progress bar vanishes and the OS boots up. A few seconds later, I got the message "Software update was successful. Your phone has been upgraded to 45.2.7". I went to SETTINGS, ABOUT PHONE, SYSTEM UPDATES and queried for additional updates. Sure enough, 45.3.6 was available. Forgot to document the file size. Downloaded and clicked INSTALL. Much like the previous update, progress moved steady till about 75%. Then progress bar and Android character vanished and the phone booted into the OS. About a minute later, the words I have been looking for for over a week:
"Software update was successful. Your phone has been upgraded to 45.3.6"
Queried software update again, and it said your phone was UP TO DATE. Yipee!!!!
I was getting NO SOUND. I think it was beause I inserted the SD card while the phone was still powered on. So, I rebooted the phone and EVERYTHING works perfectly.
If you want to wait for Mark (forum manager) to come up with a fix, I understand. In fact, it's probably the right thing to do. But if you're beyond frustrated (like I was) in the lack of information and lack of solutions from Sprint or Motorola; and want to take matters into your own hands; this worked for me.
do u happen to have a link for the 64 bit drivers ?
I'm unable to locate one.
Thanks for your help.
daddymikey1975 said:
do u happen to have a link for the 64 bit drivers ?
I'm unable to locate one.
Thanks for your help.
Click to expand...
Click to collapse
See here.
http://forum.xda-developers.com/showthread.php?p=18642169
This method has been on XDA for some time. The sbf of 198_6 was even posted way before Motorola started to push it out. Just takes a peek into the dev section.
Glad you got it working.
Thanks!
This has worked for me.
I just followed the instructions.
@OP - Thank you so much! I had a slow, laggy Photon with the "Sleep of Death", and needed to get it to update so that I wouldn't experience that issue anymore.
I followed your instructions, and got the phone working again. At one point, I wanted to throw the phone at a wall.
Now, I love my MoPho.
Thanks for making me fall in love with my phone all over again!
By the way, you are a Junior Member, this is your first post, and I gave you your first thanks. You are very intelligent, I must say! I am very proud of you. Your first post, and you did something this amazing! I must say, you are a genius! You will make a great Senior Member, it takes time to become a Senior Member, and you will make a great one! Very proud of you. Thanks a lot! I really appreciate it !!!
Motorola has re-issued the 198_6 build to address this problem. Also, 198_7 is available in the MoPho dev subforum
tbhausen said:
Motorola has re-issued the 198_6 build to address this problem. Also, 198_7 is available in the MoPho dev subforum
Click to expand...
Click to collapse
Well for me it does not fix....still the same old fail at about 30% install
Sent from my MB855 using XDA App
After failing 4 dozen times, I can happily report that the update FINALLY works!
HAPPY HAPPY JOY JOY!!
Riggy
I'm glad that it works. I used the same method, had a few issues but eventually got it to work.
Fyi...the NEW ota still did not work for me....spoke to sprint who spoke to moto tech support....moto wanted me to send them the phone (and be without a phone for week while they played around...sad moto..very sad)
Sprint is replacing my phone for free..good on Sprint
As for moto..this will be my LAST! moto phone..their service on this whole issue has been bad...and the joke of a support forum and "Mark" motos party line [email protected]%$!!!!...kiss my
... bye
Sent from my MB855 using XDA App
I'm hoping someone can help me, and I may need led thru steps.
I came from an x2, which I had managed to root, install recovery, and flashed and changed several ROMs, all successfully.
On my rezound however, I'm kinda stuck. I unlocked it, using the htc instructions and links, and rooted using zerg. I apparently don't have, and never have had recovery. Originally I just couldn't go any farther as far as gaining recovery or flashing roms, would get an error message and it would go to reboot. I don't know what I did 2 nights ago, but how whatever I do from the boot screen, I get an immediate haptic response, and it goes right to the white htc screen, where it is locked until I pull the battery. I've even tried to do factory resets, and it asks the prompt questions, but eventually it just reboots to the locked htc screen, until I pull the battery. Then it will reboot normally, but nothing was wiped.
I'm not totally inept, on the phone or the computer, but I'm definitely still a noob, but I really want to learn this stuff, the customization possibilities are the main reason I got the rezound.
I would appreciate some patient assistance from some of you knowledgeable folks!
Thanks in advance! Scott
Try using scott's cleanflash tool. It will flash recovery for you. It will also flash the boot.img (kernel) when you flash a custom ROM.
Sounds like you have fastboot checked in the settings.
If you really want to learn more about flashing, do yourself a huge favor and read up on ADB and fastboot. There's a few really good guides on them you can find by searching the forums, and knowing the basic commands will save you quite a bit of hassle vs. constantly doing battery pulls.
update..getting worse
thanks to the 3 of u who tried to help so far, i have tried some of your advice, but now my phone is basically non-functional, with constant reboots. it wont even allow me to do a hard reset. i tried it thru settings, when i could access them, and thru the "battery pull and buttons method". it confirms the reset, and goes thru the motions, but when i reboot it...everything is the same...including my problem. i need a functioning phone, does anyone know how i can go about putting my x2 back into service?
i know a lot of people on here probably figure i'm getting what i deserve, but if it comes down to it i will run over it with my car and get an insurance replacement. i really want to learn how to do this stuff, but without the background or any help, maybe i AM too "stoopid" Thanks Scott
Are you able to connect to your pc with it so you can use adb or RUU?
Not that I'm going to be the one with the answer to your problems, but maybe you can post exactly what you did that got you messed up in the first place because your post is a little confusing and it would help people who really know this stuff figure out what happened and how to fix it. Looks like you rooted and then did you ever flash a recovery?
ifyou would like hell free to shoot me your gtalk if you have one and I'll gladly help you out, got no plans tonight so I can help at whatever point you see this that also goes for anybody else having issues!
Sent from my sexy otterboxed ADR6425LVW using Tapatalk
i appreciate it!
pwnwolf117 said:
ifyou would like hell free to shoot me your gtalk if you have one and I'll gladly help you out, got no plans tonight so I can help at whatever point you see this that also goes for anybody else having issues!
Sent from my sexy otterboxed ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Ty wolf...and I very likely will take you up on your kind offer very soon! I was away all afternoon and evening today.
I did get out of the bootlooping mess I had earlier, I found a related post on droid forums, posted by malkavian under the title "continuous rebooting". The fix involved removing the sim card and typing in a code, and it fixed my most pressing problem.
I still have big problems though, I can't do anything from the boot/recovery screen, it goes right to the white htc screen and locks until I pull the battery. Also, I have tried several times to do hard resets, and those don't work either. I hope to talk to you soon...and thanks in advance! Scott
Alright So I bought this Atrix for 50 bucks. Guy was having problems and coulnt figure it out. Its rooted and unlocked. When I plug the charger into it (the stock wall charger. not to the computer) it goes to the M boot screen. I can't get to any other screen to come up. When I hold the volume buttons down, I get "Cant start RSD Battery too low to flash". also, When I plug it in, The green LED lights up for a second then turns off as it goes to the Motorola screen. I can't turn it on either with just the battery. any Ideas?
crazydavy said:
Alright So I bought this Atrix for 50 bucks. Guy was having problems and coulnt figure it out. Its rooted and unlocked. When I plug the charger into it (the stock wall charger. not to the computer) it goes to the M boot screen. I can't get to any other screen to come up. When I hold the volume buttons down, I get "Cant start RSD Battery too low to flash". also, When I plug it in, The green LED lights up for a second then turns off as it goes to the Motorola screen. I can't turn it on either with just the battery. any Ideas?
Click to expand...
Click to collapse
I had this problem just last night. I searched around xda and the internet, and came upon this: http://www.atrixforums.com/forum/mo...e-rsd-lite-flash-sbf-file-motorola-atrix.html
Give it a shot. If it doesn't turn on now, what's the worse that'll happen by trying this?
Just charge the battery and flash a SBF with RSDLite.
Make sure that you don't downgrade the ROM. Read sticky for more info about hardbricking risks.
Wrong section.
Sent from my MB860 using Tapatalk 2
What SBF file do I need? Im not sure what is on the phone and I dont wanna Brick it if I can avoid it.
Go the latest SBF(the latest being 2.3.6/4.5.141 if you have an ATT atrix. Otherwise a full list of SBF files are here http://www.filefactory.com/f/89f588286a560e39/ ). Bricking occured when downgrading, so long as you upgrade or stay the same you should be fine.
rkkaranrk said:
Wrong section.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, admin?
I bit the bullet and did it. All was going good till my cat jumped on my computer desk and then failed saying something about switching to BP or something along those lines. Now I cant get the phone is RSD again
Was your battery charged enough? Sometimes if your battery is low it won't complete the flash.
What directory is your sbf file located at? Sometimes it won't work unless you put it directly in the C:\ drive.
Have you got the latest RSDlite?
What SBF did you flash?
Did you use the usb ports at the back of the pc?
If you can't get it in RSD again then I suggest giving it a charge for an hour or so and trying again later. Also check the md5 of the sbf file to check that the file is correct. Sometimes the 'Switch phone to BP Pass through mode' can be fixed just from trying a different usb port or computer.
crazydavy said:
I bit the bullet and did it. All was going good till my cat jumped on my computer desk and then failed saying something about switching to BP or something along those lines. Now I cant get the phone is RSD again
Click to expand...
Click to collapse
congratulations your mobile device is sucessfully bricked.
mine did[(do)will] the same, you have to take it to the assistance, i know what must be done, the assistance guys told me, but it can only be done by them.
so, you better hope you dont have the same problem as mine. [but if you got the error talking about didnt booting radio////failed to switch to BP(or some s**t like that) you probably have it, and only motorola can fix it.]
Edit: we know is the wrong section but only modetators can complain/report/warn. if we are not, lets just help the poor dude while the problem is unsolved.
guidoido004 said:
congratulations your mobile device is sucessfully bricked.
mine did[(do)will] the same, you have to take it to the assistance, i know what must be done, the assistance guys told me, but it can only be done by them.
so, you better hope you dont have the same problem as mine. [but if you got the error talking about didnt booting radio////failed to switch to BP(or some s**t like that) you probably have it, and only motorola can fix it.]
Edit: we know is the wrong section but only modetators can complain/report/warn. if we are not, lets just help the poor dude while the problem is unsolved.
Click to expand...
Click to collapse
Have you googled the error? If you have, you'd find that it is a common error and I haven't seen any cases where they didn't eventually get fixed. OP just needs to get back in to RSD and have another go. The guys from 'assistance' don't know what they're doing, they'll take any reason to say that 'only motorola can fix it' because they don't know any better.
devize said:
Have you googled the error? If you have, you'd find that it is a common error and I haven't seen any cases where they didn't eventually get fixed. OP just needs to get back in to RSD and have another go. The guys from 'assistance' don't know what they're doing, they'll take any reason to say that 'only motorola can fix it' because they don't know any better.
Click to expand...
Click to collapse
I wold haVE GOOGLED IT BUT RSD lite closed on me. I would get back into RSD but I can't get the phone back into it. I power on and hold the volume buttons and it doesnt do anything.
And also now while its stuck on the Motorola boot screen, Unlocked is missing from the corner like it use to be there.
Well after just fidiling around with it, it just started working. After about 45 minutes of just sitting there on the motorola screen, it booted up. Now its time to set it up all the way and put CM7 on it im guess.
I wasn't talking to you about googling the error, I was talking to the guy who had said that your phone was bricked when clearly it wasn't. The error would have been a fail at 'Switching Device to BP Pass Through' stage which does not mean you're device is bricked.
Anyway, good to see you fixed it. And the unlocked text goes away when you flash an SBF, that's normal. Get cm10 on it
I went back through and kind of got that after the fact haha. Im glad I got it fixed also too. Not I can get rid of the dreaded Iphone 4 :\ and be back where I belong. Is there a stable CM10 for it? I havent gotten to look around much yet since I was fixing the main problem.
It really doesn't work the way everyone says it should. I was trying to unlock the bootloader on my phone, and I made sure to download firmware for the phone that matched the model number. It was a Lumia 920 model RM-820 from AT&T, and the firmware I used was supposedly designed for that phone. The filename of the firmware I found was RM820_3051.50009.1425.2001_RETAIL_nam_usa_100_01_443332_prd_signed.ffu
Ever since I flashed it, it's been bringing up a frowning face and rebooting itself. I've been told to use the WDRT tool, but it won't recognize the phone no matter what I do. It keeps searching for the device and never finding it, no matter how many times I reset the phone or whether I pull up the screen with the gear and the lightning bolt by using volume up. When I use the screen with a gear and lightning bolt, the software tries to detect something, but it never gets any further than the "please wait" screen. Anything other than that mode completely fails to detect anything.
It's very difficult to find information on this problem, because a lot of the FAQs and guides are really old and full of dead links. I don't have any kind of real background in this, and I struggled to make sense of anything I was reading about this. I'm really kind of a moron when it comes to phones, and I was a little overconfident because I know what I'm doing with PCs. I really hate how phones obfuscate all the details, won't tell you what's going on, turn your device into a brick if you make one mistake, and make it so hard to do anything with a device other than what the manufacturer intended.
In all honesty, it's very likely that if I don't get this thing fixed, I'll probably end up putting my SIM card into a TracPhone or similar device for a couple months until I can afford a new phone. Could someone help out a total moron? Please?
EDIT: Well, you can actually go ahead and close this thread... I don't know what happened, but apparently my Mom was able to fix it. The procedure failed on my desktop PC, my Surface Book, and my old laptop... but my Mom tried to use her laptop, and somehow it worked. I wasn't even watching her, so I have no idea how, though. And she doesn't know anything about computers, but she somehow did in 10 minutes what I couldn't do in 2 days.
athenian200 said:
It really doesn't work the way everyone says it should. I was trying to unlock the bootloader on my phone, and I made sure to download firmware for the phone that matched the model number. It was a Lumia 920 model RM-820 from AT&T, and the firmware I used was supposedly designed for that phone. The filename of the firmware I found was RM820_3051.50009.1425.2001_RETAIL_nam_usa_100_01_443332_prd_signed.ffu
Ever since I flashed it, it's been bringing up a frowning face and rebooting itself. I've been told to use the WDRT tool, but it won't recognize the phone no matter what I do. It keeps searching for the device and never finding it, no matter how many times I reset the phone or whether I pull up the screen with the gear and the lightning bolt by using volume up. When I use the screen with a gear and lightning bolt, the software tries to detect something, but it never gets any further than the "please wait" screen. Anything other than that mode completely fails to detect anything.
It's very difficult to find information on this problem, because a lot of the FAQs and guides are really old and full of dead links. I don't have any kind of real background in this, and I struggled to make sense of anything I was reading about this. I'm really kind of a moron when it comes to phones, and I was a little overconfident because I know what I'm doing with PCs. I really hate how phones obfuscate all the details, won't tell you what's going on, turn your device into a brick if you make one mistake, and make it so hard to do anything with a device other than what the manufacturer intended.
In all honesty, it's very likely that if I don't get this thing fixed, I'll probably end up putting my SIM card into a TracPhone or similar device for a couple months until I can afford a new phone. Could someone help out a total moron? Please?
EDIT: Well, you can actually go ahead and close this thread... I don't know what happened, but apparently my Mom was able to fix it. The procedure failed on my desktop PC, my Surface Book, and my old laptop... but my Mom tried to use her laptop, and somehow it worked. I wasn't even watching her, so I have no idea how, though. And she doesn't know anything about computers, but she somehow did in 10 minutes what I couldn't do in 2 days.
Click to expand...
Click to collapse
I've had a similar problem with mine, bootloader unlock process didnt finish correctly and my Lumia 920 won't switch on, respond to Soft/Hard resets or respond to connections to the computer. WDRT and WPInternals no longer detect the device at all.
I hope someone knows how to sort this out