Anybody out there know how to fix this?
All I have is a black screen giving a USB version. Won't connect to or be recognized by ActiveSync.
it's still ok given that the usb is shown. just cradle back the unit and restart the upgrade. don't expect activesync to "recognize" your device. just hit the upgrade exe file and it should proceed. this happened to me once when i upgraded to 2005.
THANKS VERY MUCH, I'm going to try that, I'll report back my success (hope)
You Are Fantastik, Thanks! Thanks! and Thanks!
Now let me ask you, this happen to you when you were updating to Windows Mobile 5? If so I too am looking to upgrade to WM5 just thought I should get O2's final update before doing WM5. Seen WM5 (for Xda IIs)for sale on ebay for about $16 to download, with all instructions.
Do you have any suggestions or advice, I'm feeling pretty brave now.
THANKS
yes this happened to me when i decided to upgrade to wm2005. what happened was the instructions said that i should first do a reset before proceeding with the upgrade (not sure if it was a soft or hard reset). anyway, i forgot to do this and went straight away to the upgrade. after a couple of minutes the upgrade screen (on my laptop) said something like "device error"...of which the screen on my xda said "usb version-something"...with a dark background (i think this is the one you experienced). anyway, i did a couple of resets (even a hard reset) and my screen was stuck with the same info. i believe this is called bootloader mode. i remember reading the instructions that if this happened i simply cradle back the unit and hit the upgrade command on my pc. it worked!
for you, i'm not as familiar with upgrading an xda2s. but in my opinion, as long as you can get your unit to bootloader mode you are still fine. in fact i do remember reading a couple of posts that some chaps had a completely blank screen. they said that they kept on doing hard resets until the unit went back to bootloader. true enough, a buddy of mine upgraded to 2005 and his screen went blank. he did something like 10 or so hard resets and he was able to get it to bootloader mode. from there he proceeded with the upgrade and he succeeded.
hope that helps and good luck
Oh, I should have said, your suggestion worked. I put it back in the cradle and restarted the ROM upgrade and it worked perfectly. I just thought that since ActiveSync was not recognizing it, it was Broke.
Thanks, now weather to temp faith again and try to upgrade from 2003 se to WM5. Did you find WM5 to be a big improvement over 2003se?
nice to know it worked. wm2005 is fantastic in all aspects. the only con i found was that one of my apps was not working due to not being compatible. i use animated today (animation of my baby girl rocking back and forth on her rocker), when i upgraded i couldn't get it to work anymore. however; i wrote to the app developer and he said they're working on an upgrade to make it compatible with 2005. so it's not really a con...more of just waiting until the release is out for the upgraded software. so in your case, there might be some apps which may not work properly (or not work at all) due to it being incompatible. there's a thread somewhere in this forum listing the proven apps that work well with wm2005.
a LOT of people complained about the memory issue when they upgraded to 2005...myself included. however the fixes came out (ramdisc, doc tools, etc) and from there everything worked out fine. for you, when you do upgrade to wm2005 just make sure you follow every bit of tip and instructions so as to make the transition and experience worth it. i read a lot from the forum (as well as buzz's website); a lot of chaps didn't do this and they ended up downgrading to 2003se.
other than that, a lot of my favorite apps work well with wm2005. i still have this app i used 2 years ago (today plug-in) and it works with 2005.
cheers
Sounds pretty cool, watching your daughter rocking when ever you want. What is buzz's website?
buzz was the one who enabled wm2005 to be ported to the xda2. the website is:
http://buzzdev.net/
TONS of info and resources in there.
cheers
Thanks for all your help, I'll check out buzz's website.
Related
Hi there, I've recently bought an XDA / Wallaby originally locked to O2 and thanks to your software on the site I've now got it running on my Orange payg with full web access in under 2 hours of ownership - Wonderful! Big improvement over my Psion Revo .
Since getting this, my wife's now decided she loves the xda also so I'm looking for a second one for her.
My question is this; I've now found one listed on ebay quite local to me (so I can see it's as described before paying) but it has the following apparent problem, quoted verbatim:-
'I recently tried to upgrade the OS on it which resulted in me deleting the ROM Image so the OS/Rom needs to be re-installed. I would take the time to do this myself but do not have the time, and I have just got myself a P900 so am looking to use that. The software can be easily re-installed and is freely available. I have moved to the P900 purely for its bluetooth and camera functions and no other reason, i was totally happy with the XDA, it just needs a good home with someone that will take the time to load the software back onto it.'
Can I obtain any software to rectify this or am I biting off too great a problem?
As the item closes tonight (thursday) I'd appreciate any comments asap.
Thanks all, Charles
If Boootloader is working, reflashing the device should be no problem. You just require a SD-Card >= 64 MB and a (external) Card Writer.
How to do thi is described here http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
You can ask him, if he can try enter Bootloader by pressing Power button and doing a soft reset. It will be interesting, what there is displayed....
Stefan
thanks for that. Just read the link article. So I need to factor in the cost of a SD read/writer as I haven't got one. On that basis I think it could work out cheaper to just buy another O2 locked wallaby xda and unlock it for Orange.
But I'll watch to see what the item closes at.
BTW, do you have any idea of the price of the sd read/writer? I'll check with ebay myself as well.
Rgds
Charles
Should be not much. About 5 Euro, max 10 Euro + shipping.....
Stefan
While walking a colleague thru his first WM6 upgrade last night, I happened to notice that my IPL had somewhere reverted to 1.00 Well, I just couldn't have that, and set out to re-up it to 1.04
Reflashed it to Vodafone OEM ROM, which for some reason also requires flashing any Radio Rom to get it past the Windows splash screen. Still showed IPL 1.00
Flashed it with the SIM-CIM unlock files, got the IPL up to 1.01
Next, still really wanting to get back to 1.04, and not being happy with a device that was running any and all ROMs I was throwing at it, I tried MTTY and tried to force 1.04nb on it, it wouldn't take it, but it didn't quit.
Then, about 4 am, I got really clever, took the 1.04.nb file, ran it thru nbhtool and made a .nbh file.
Put that on the SD card as HERMIMG.img, and fired up the bootloader.
The file flashed quickly, and gave me the Whoopie, it Worked message.
So, I removed the card, and did a soft reset. And that was the last thing the little guy ever did, reset to dead.
Good thing is our company has these things laying about like some companies have ball point pens, so getting replacement took just minutes.
Now I stick strictly to the guides, improvisation is best left for other folks.
This has been another in the continuing series "Noobs and our toys, how we break em".
... and you admit to the whole world that you are a total idiot?
... I'm convinced
You got balls kid, I'll give you that....
More Like This in the Wiki
Thanks for the excellent HOWTO
I'll try your procedure in a couple of months time when it's time to buy something more exciting (Toshiba Portégé G900, i-mate Ultimate 7150 or Nokia E90 -- which one shall it be?).
Actually you should have thanked him for the HowNOTTo!!
Not if you're looking for a good reason to buy another phone
simple said:
Actually you should have thanked him for the HowNOTTo!!
Click to expand...
Click to collapse
That's kinda what I was going for... don't get too cocky too soon, and learn from my dorkup. And no, I don't mind admitting I bricked one, I know that many of the senior guys must have too at some point, there are those that have, and those that will.
One thing though, in the 4 or 5 months I've had a Hermes, it has been amazing to see the evolution in tools and utilities that have evolved. Now I just have to keep straight in my noob brain which tools are cross compatible.
This is exactly what happened to my hermes... I sent it to be repaired 2 months ago.. and it is still being repaired I don't know how on earth this can take so much time. They've been saying they are waiting for some "parts" for 5 weeks now :>
Isn't it a bit strange?
Okay today I intentionally bricked my phone. Not once, not twice, but 6 times with three bad ROM's (long boring day) and pulled the USB during the flashing at around 20%-95% as well as other no,no's
The experiment. To see how fast, and what I would use to unbrick it. Now being stuck in an all white screen or bootloader might bring fear or tears to some, but what I discovered is probably the best and easiest way to get your phone back to life in a relatively short amount of time.
If this has been covered before or mentioned elsewhere I didn't see it so I apologize if thats the case.
After I bricked each time I simply hooked up the usb cable to my pc. As you know when you are bricked or stuck in a loader Active Sync does not launch. What I found was that if you use a factory WM6 AT&T ROM it will still connect via usb and will flash said ROM 100% of the time restoring you're phone to a working state.
Now I did this 6 times today and it worked every time. I mean I really f'd with this second phone unplugging, Task Manager'd out during a flash, hard reset during a flash, etc. Every time it worked.
Hope this helps.
Well, you have been only lucky for 1 reason:
You always 'bricked' your device when it was in the middle of flashing the OS! This does not really matter as long as BOOTLOADER and CID are intact!
Do the same experiment but this time pull the plug at 15% and you will most likely fail to recover from that! At around 15% is the moment where the CID block gets written to the phones ROM.
Be very carefully that you do not 'brick' your device earlier because of in the state before 15% IPL and SPL are getting flashed! If you destroy the bootloader you can't do anything anymore!
If you are going to try that out please flash your phone first with the nbh from the CINGULAR WM5 (it is in the wiki) by using CustomRUU! CINGULAR WM5 has KITL enabled and you will be able to 'unbrick' your device by using the GUIDE in the WIKI.
I WILL NOT BE RESPONSIBLE IF YOU BREAK YOUR DEVICE TO A POINT OF NO RECOVERY POSSIBLE!
CID block is never written to the phone, it's just an area of storage inside the GSM chip.
however, if incomplete code is flashed to the GSM chip, the radio AT interface cant' boot... and then there's no way of talking to it, hence making it now dead.
On a different note, if the Radio Bootloader is in the middle of flashing (although I believe 0108 is persistent) and the connection is broken, you're now royally ****ed.
So, the GSM chip is not in the phone then?
<just kidding!>
However,
pulling the plug around 15% will most likely end in a brick! That was where I had my pc crash - thankfully KITL was enabled!
Tried again
Okay I did this at 12% and then at 16% (could not time it right for 15%) and I was able to recover. If I am just one lucky bastard, and this is highly against the odds, I would say don't do this on purpose like me.
My only point of the experiment was to see if I was to ever brick, at least I knew of one possibility that would recover it. And when looking at it like that it was a success.
Now that all is back to normal, I have HARD SPL.7 and have no issues.
ihavetinyballs said:
Okay I did this at 12% and then at 16% (could not time it right for 15%) and I was able to recover. If I am just one lucky bastard, and this is highly against the odds, I would say don't do this on purpose like me.
My only point of the experiment was to see if I was to ever brick, at least I knew of one possibility that would recover it. And when looking at it like that it was a success.
Now that all is back to normal, I have HARD SPL.7 and have no issues.
Click to expand...
Click to collapse
HARD SPL? try a different SPL and then try it again...
Oh yeah... Try to kill your bootloader too... And if it's like one of my devices
(HTC Charmer with a black screen... Only the power led lights up for half a second when I press the power button)
then try to flash your "holy" rom
eh, i don't understand why people call it bricking if only the OS needs a reflash
I wasn't clear. The phone was never hard SPL'd till after the experiment when I decided to lock the ***** up to keep it safe from doing more stupid stuff. The os flash wasn't all I crashed out on. I did this with this on purpose with the radio versions as well.
ihavetinyballs said:
I wasn't clear. The phone was never hard SPL'd till after the experiment when I decided to lock the ***** up to keep it safe from doing more stupid stuff. The os flash wasn't all I crashed out on. I did this with this on purpose with the radio versions as well.
Click to expand...
Click to collapse
then you are crazy
There are 2 possible explanations for your "luck":
Either the ROM you're flashing contains nothing but the OS and maybe the EXTENDED ROM in which case it does not really matter if you pull the plug because of your BOOTLOADER and GSM will remain intact or your FLASHING UTILITY 'ignors' the BOOTLOADER / GSM flash and writes only the OS and EXTENDED (which would have the same effect as case 1 when pulling the plug!).
However,
flashing an entire ROM takes a while, especially between 12% and 30% if you flash IPL / SPL / SPLASH / GSM / OS / EXTENDED - there is enough time to pull the plug at 15% because of it takes almost a minute until it jumps to 16% ...
I don't want to animate you to try that out because of sooner or later you will brick the device for sure!
Can you host the ROM file + flashing utility you used for your experiments, so, that we can download it and take a closer look?
ihavetinyballs said:
I wasn't clear. The phone was never hard SPL'd till after the experiment when I decided to lock the ***** up to keep it safe from doing more stupid stuff. The os flash wasn't all I crashed out on. I did this with this on purpose with the radio versions as well.
Click to expand...
Click to collapse
The world belongs to renegades and mavericks...
I did it with TNT's latest as well as VP3G 3.62
OK I'll bite where is WM6 AT&T ROM?
I have a bircked phone tytn (tried to unsucessfully unbrick around 50 times), not sure why or where it bricked.
Can reload but sticks at screen alignemnt EVERY TIME.
Was given as a challenge (failed so far).
If I could find this and it worked I be happy chappy long time.
If it works of mine it will work on anyone's.
Give it up dudes (or duedess if there is one out there).
Here is the secret. Use the bundled WM5 Cingular ROM from HTCs download site.
ihavetinyballs said:
Here is the secret. Use the bundled WM5 Cingular ROM from HTCs download site.
Click to expand...
Click to collapse
Do you have a link, filename or even better can post on Rapidshare?
Edit: btw, the moniker is hilarious!
rob8 said:
Do you have a link, filename or even better can post on Rapidshare?
Edit: btw, the moniker is hilarious!
Click to expand...
Click to collapse
He gave you the info you need. Go to HTC's site. Or use google.
K since i took the time to post this I might as well link it.
Go to the bottom of this page.
It is about time to give out a WARNING !!!
People, do not try to brick your device and trust in that you can recover from that by using the ROM from the HTC's website! This is not a magic tool and it won't bring your Hermes back to life if your device is really screwed up! There is nothing in the Cingular ROM what 'magically' does the trick! IHAVETINYBALLS was either just lucky or he isn't really bricking his device (consciously or unconsciously).
If you do not believe me ask other senior members with lots of experiences, such as OliP ...
However, I know there is no way of stopping fools to do foolish things, so, go ahead, destroy your expensive toy! You can always find a new one on eBay ... !
For all the retards who don't get it. (meaning the point)
To the dip**** retards who don't get the point. Like I said, I am probably just lucky. And like I said again, DO NOT try this unless your phone is stuck and ****ed, it was just an experiment. I have two 8525's one I bought as a refurb from AT&T for $99 and another one that was from an angry owner who threw it away at the AT&T store (as it was bricked and now "useless") and I pulled it from the garbage bin. Recovered it (just did a hard reset and put in a new battery and factory ROM and did a few experiments.
It didn't cost me anything and I did put a warning out there. The point of it all was that if you give up on bringing it back to life, maybe just maybe you should try this out.
Obviously if your phone is working just fine, don't do this or your a ****ing retard. Its meant for bricked or stuck phones as a possible recovery as it worked on said phone numerous times in various states of bad flashing and various types of ROMs.
This phone is now running vp3G 3.62 and now has HARD SPL.7, and Radio 1.54.07 and is running flawlessly.
So one mans brick/stuck frustration is making for an excellent spare / backup for me.
trying now
ok - have hybrid brick (no KITL, screwed CID and radio)
if everyone crosses their fingers at the same time maybe it will help???
will post back results!
Bugger
thanks for giving me hope! but alas...no good
hopefully someone else can figure out how to get back from a hybrid brick of no KITL and SPL 1.09
I don’t know if it’s an age thing, as in phone years = two years being geriatric or what but it’s been doing some weird stuff.
Periodically, it’ll crash. The screen will totally freeze with it either on the home screen or a black screen as though it’s switched off. Ho hum, yet another battery pull to rectify it.
It doesn’t like too many text messages so I have to regularly do a bit of housekeeping there. Related to that, typing is starting to irritate me on there. The predictive seems to have a mind of its own and, well, it just winds me up so I end up making calls instead of texting.
Some of my text messages have vanished without me deleting them! I’ve noticed texts can be located in the SIM contact and the phone contact yet strangely my SIM tells me it has no texts. Nevertheless, when I’ve decided to embarked on a housekeeping mission, I learn that messages I intended on keeping have gone before I’ve even started deleting anything!
For a while, the phone also didn’t seem to know where I was. I was and still am in the UK and a few times, it put me in Balkan. That’s great. I’m all for a free holiday but it could have warned me so I could have packed properly!
It likes to use data even when I’m not even touching the phone! Whenever I pick up the phone, I always check next to my network that there is no counter. However, often when I pick it up I can see an hour or two has passed on a counter meaning its gobbling data. What’s spooky about this is that I’m meticulous about switching stuff off that uses data and it still turns itself on! This was the whole reason I didn’t take this phone on holiday last year; I reverted to my LG Renoir because it was safer!
The last thing it’s done, just a few minutes ago is re-start itself! I wasn’t even using it; it was just sat on the table next to me minding its own business and decided to re-start. Why?
After the Balkan incident happened a few times, my Mum said my phone was crazy. I agree with her.
Has anyone else had weird stuff happen on their phones?
If you have not tried it yet I would do a hard reset. Power your HD2 on while holding down both the volume up and down buttons and follow the on screen instructions when the come up.
Also make sure to back all of your personal data up from the HD2 first as this will wipe it clean.
For a while, the phone also didn’t seem to know where I was. I was and still am in the UK and a few times, it put me in Balkan. That’s great. I’m all for a free holiday but it could have warned me so I could have packed properly!
Click to expand...
Click to collapse
This made me laugh hilariously too by the way.
The earlier roms often exhibited some, all or less of these behaviors. If you are still on a 1.4 rom version, get it updated.
T-Macgnolia said:
If you have not tried it yet I would do a hard reset. Power your HD2 on while holding down both the volume up and down buttons and follow the on screen instructions when the come up.
Also make sure to back all of your personal data up from the HD2 first as this will wipe it clean.
This made me laugh hilariously too by the way.
Click to expand...
Click to collapse
This is something I could try. I’ll get doing a bit of housekeeping first though. Thanks
samsamuel said:
The earlier roms often exhibited some, all or less of these behaviors. If you are still on a 1.4 rom version, get it updated.
Click to expand...
Click to collapse
I’m on the original version that came with the phone. I think that might be 1.43.
When you mentioned a ROM update, I thought
I’m so overwhelmed with the information on this forum. There are so many ROMS it’s hard to know what to pick and I’m seeing far too many posts where people have tried to update and something’s gone wrong.
I just don’t have the level of understanding about phone software to carry this out successfully.
If it were as easy as it is to update my iPod via iTunes, then I’d do it but all this looks way too scary
if you want to keep a stock rom, an update is very easy. and a lot of bugs in the first releases have been fixed.
just go to the website of your carrier and download the rom in the support section. if your phone isn't branded you can download the newest version on the htc website.
if you upgrade your rom you also have to backup all your data, cause it will get lost during the update process.
you can use pim backup for contacts and messages, or just use microsoft myphone.
yea mine was mental on teh original 1.43 too, lots of accidental calls,
to get the update start with htc.com, most of the uk carriers dont bother hosting the updates, htc.com - top right, pick country, then support - select phone - downloads and change teh small dropdown from all to rom upgrade, look for your carrier, , if a rom doesnt accept your serial when you click to download it, it isnt right for your phone, and you maybe have an unbranded, meaning it would take the regular WWE (world wide english) update, in which case try the one that doesnt have a carrier name attached.
once downloaded, read THIS which is linked to from THIS, which is a list of very usefull guides and related posts.
Thank you for all your excellent replies!
I got the latest T-Mobile ROM 3.14.110.1 from HTC website and completed the update following the HSPL installation.
Those links were absolutely wonderful! Thank you so much! I also found it useful watching the Youtube videos that were linked in one of the threads.
I’m currently personalising my phone and I’ve forgotten how to add Bluetooth as a QuickLink. I know it can be done as I saw the solution on here when I first got the phone and did it then so I’m having a look around see if I can find it again.
Oh and what a pleasant surprise being able to watch Youtube on my phone at last! Nice one!
Thank you all ever so much
besca147 said:
I’ve forgotten how to add Bluetooth as a QuickLink. I know it can be done
Click to expand...
Click to collapse
id recommend you dive straight in and install cookies home tab(CHT) mod and CHT editor. (Link is in the CHT mod thread).
Not only do they make sense wonderfull, but it has built in quicklink assignable toggles for BT, wifi and such.
samsamuel said:
id recommend you dive straight in and install cookies home tab(CHT) mod and CHT editor. (Link is in the CHT mod thread).
Not only do they make sense wonderfull, but it has built in quicklink assignable toggles for BT, wifi and such.
Click to expand...
Click to collapse
This is seriously wonderful! Thanks for the sharing this info and the link.
I've put the stuff on this evening and the add ons to get me the bluetooth toggle.
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