[Q] Atrix Battery Died during OTA update, won't boot...HELP?!? - Atrix 4G Q&A, Help & Troubleshooting

Hello everyone. I have a problem with my Motorola Atrix and I am hoping someone might be able to help me.
I got it as a late Christmas present so its still practically new. I tried doing an OTA update from 2.2 to 2.3 and the battery died whilst the update was taking place. I replaced that battery with my spare battery which was fully charged, but now it won't load. When trying to load on startup, it gets stuck at the dual core logo and gives an error message if I press the volume button. The message says something like "Starting RSD protocol support". I am gutted...
I have been searching feverishly through the forums for some help, and I have come across some information with regards to the types of bricks, ie hard/soft, but I am not sure which it is in my case. There is alot of information available, but I can't find any with my problem. I am not opposed to trying to fix the problem myself as I have some experience in messing around with software, though that was back in the days of p2k-tools some 10 years back, but I would appreciate a nudge in the right direction and some advice maybe since I am almost clueless about Android software. Any help would be greatly appreciated.
Additional info:
The phone is completely factory default software wise, so is not rooted or running any form of custom firmware. UK carrier - Tmobile.

I think you have two options. If it's still under a warranty, take it back to the store and ask them to repair it. Or if you don't care about a warranty, you can follow this post http://forum.xda-developers.com/showthread.php?t=1136261 to unlock your phone and install a custom ROM. But if you decide to unlock you phone, before trying anything, read the post completely. I'm saying again, read the post completely before doing anything.
I myself unlock the Atrix and using a custom ROM and I have a pretty good battery life compared with a stock ROM.

Thank you for your response. I will look into the warranty idea and see how that goes. I hope there is not a long wait period which is my biggest reservation about this option since I need my phone.
In so far as installing the custom ROM and unlocking it, is there maybe another way that would allow me to continue to use stock firmware and OTA updates? I have been reading through some threads where they say once there is a custom firmware, running an OTA update could brick the phone. I also really just prefer to keep the phone original. If this can't be done, then I will have to give the warranty thing a serious go before I consider the alternative.

shottah said:
Thank you for your response. I will look into the warranty idea and see how that goes. I hope there is not a long wait period which is my biggest reservation about this option since I need my phone.
In so far as installing the custom ROM and unlocking it, is there maybe another way that would allow me to continue to use stock firmware and OTA updates? I have been reading through some threads where they say once there is a custom firmware, running an OTA update could brick the phone. I also really just prefer to keep the phone original. If this can't be done, then I will have to give the warranty thing a serious go before I consider the alternative.
Click to expand...
Click to collapse
Go here > http://www.motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page. Another alternative is to flash 2.3.4 stock via RSDLite, but if the update went through on your phone you could brick. Hopefully one of these will work for you! Other option is to unlock the bootloader.

If you have a full battery why not download the T-Mobile software and write it back to the phone via rsd.
Sent from my MB860 using Tapatalk

CaelanT said:
Another alternative is to flash 2.3.4 stock via RSDLite, but if the update went through on your phone you could brick. Hopefully one of these will work for you! Other option is to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the suggestion. How can I tell if the update went through? Can I access this information in the phone's current state?
lonegunman said:
If you have a full battery why not download the T-Mobile software and write it back to the phone via rsd.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
By now the battery is just short of full, but it should be enough to get through the flash. Where would I get the T-mobile software? I have checked their site and the latest android update they have is 2.1 on the site. I have also looked at the Motorola website, but their means of update is via an update program called Motorola Software Update.
Sorry if I appear a bit dense, its just from what I'm seeing is that I may only have one chance to do this and get it right, else its bye bye Atrix. I am still waiting on a response from Motorola with regards to my query about the warranty. If I can get it sorted myself, I will definitely prefer that as opposed to having to wait on them to diagnose etc.

Have a look for the ATRIX super firmware thread on here and see if the T-Mobile software is in it, it may be the old software but it's worth a try as you can send the phone in to be fixed or just take it to a T-Mobile store and let them deal with it for you.
Sent from my MZ604 using xda premium

CaelanT said:
Another alternative is to flash 2.3.4 stock via RSDLite, but if the update went through on your phone you could brick. Hopefully one of these will work for you! Other option is to unlock the bootloader.
Click to expand...
Click to collapse
If I implemented the automated update via the link you provided, could that circumvent the potential bricking you described, provided the program can access the phone? By the way, the link you gave was software for an AT&T mobile, while mine is T-Mobile UK. Will this make a difference?

shottah said:
If I implemented the automated update via the link you provided, could that circumvent the potential bricking you described, provided the program can access the phone? By the way, the link you gave was software for an AT&T mobile, while mine is T-Mobile UK. Will this make a difference?
Click to expand...
Click to collapse
Ah, you're on an international Atrix? AT&T update won't work for you then.
Sorry, I missed that at bottom of the OP.

If you get stuck and are in london pm me and I will see if I can help.
Sent from my MB860 using xda premium

CaelanT said:
Ah, you're on an international Atrix? AT&T update won't work for you then.
Sorry, I missed that at bottom of the OP.
Click to expand...
Click to collapse
No problem, I appreciate whatever help I can get.
lonegunman said:
If you get stuck and are in london pm me and I will see if I can help.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Thanks for the offer pal. Wish I was in the London area to get the help but, I'm in Stoke.

Ok, i have no idea if this will work but hay the phone is knacked so why not give it a go, it's under warranty so you can send it back if it don't work go http://forum.xda-developers.com/showthread.php?t=1125944 find the orange full and t-mobile service files, download them and write them to your phone via rsd, it's kinda hard to say what one first, its a shame that the t-mobile one is not a full one as that would be perfect, the battery should still charge so leave it on over night, also if can try and make a motorola service cable, that will put power to your so no need to worry about a battery, have a look on here as to how to make it.........ok forget all that if you check out post 276 on the link above it has download for the GB rom t-mobile uk which is what you need to wirte via rsd.

Even if you don't pay you're carrier for warranty Motorola gives you a year warranty on the phone and that's the sane with almost all carriers I sent my unlocked atrix in for screen issues and they still fixed it and same with my hd2 and ipod touch

Any update on this?
Sent from my MB860 using Tapatalk

lonegunman said:
Any update on this?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Sorry pal, been busy with classes so no time to update the thread. Basically, I tried to update via Motorola software, but it seems it cant access the phone to begin the update process. I tried to do download the OEM ROM of 2.3.4 from the ATRIX superthread, as this seems the safest option to me, bit it seems its on a host that no longer allows downloads. I tried to request a mirror, but I don't seem to have the authority to post in that thread. If you or anyone can make the request for it to be reuploaded to another mirror, I would be most great full.
Post 276 of Atrix Formwares Superthread
ROM:
Original Gingerbread SBF for ATRIX MB860 T-Mobile UK
Android 2.3.4 ---- Blur_Version.45.31.2.MB860.T-Mobile.en.GB
filename:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.2-release-keys-signed-T-Mobile-GB.sbf.gz

Did you try this?
http://forum.xda-developers.com/showpost.php?p=19908591&postcount=276

shottah said:
Sorry pal, been busy with classes so no time to update the thread. Basically, I tried to update via Motorola software, but it seems it cant access the phone to begin the update process. I tried to do download the OEM ROM of 2.3.4 from the ATRIX superthread, as this seems the safest option to me, bit it seems its on a host that no longer allows downloads. I tried to request a mirror, but I don't seem to have the authority to post in that thread. If you or anyone can make the request for it to be reuploaded to another mirror, I would be most great full.
Post 276 of Atrix Formwares Superthread
ROM:
Original Gingerbread SBF for ATRIX MB860 T-Mobile UK
Android 2.3.4 ---- Blur_Version.45.31.2.MB860.T-Mobile.en.GB
filename:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.2-release-keys-signed-T-Mobile-GB.sbf.gz
Click to expand...
Click to collapse
When you say that the updated doesn't start because the Motorola software can't access the phone, is your phone recognized when you plug it into your computer?

dratsablive said:
When you say that the updated doesn't start because the Motorola software can't access the phone, is your phone recognized when you plug it into your computer?
Click to expand...
Click to collapse
The laptop recognizes the phone since I can hear USB noises when plugged and unplugged. When I try to run the software, it tries to connect and then I get the message:
"Motorola Software Update is unable to identify your device at this time. Please try again."
zigbee_chitti said:
Did you try this?
Click to expand...
Click to collapse
Yes I did try the link, but sharing is disabled on that host so I cant download it. That is exactly what I need from what I understand, but I don't have enough access to request a mirror, even though I have more than 10 posts for some reason.

Ok, well it seem over the whole megaupload thing any of the file sharing sites are playing it safe, you need to find someone who has the t-mobile file already and can send it to you, i have the orange one but not sure if it will brick your phone or not.

lonegunman said:
Ok, well it seem over the whole megaupload thing any of the file sharing sites are playing it safe, you need to find someone who has the t-mobile file already and can send it to you, i have the orange one but not sure if it will brick your phone or not.
Click to expand...
Click to collapse
The OP of that file would have access to his files on the host, its only 3rd parties who can't download his files from uploaded to his account. If he/some one else who has it can upload it to another site, it would be fine. He should still have access to his files on his account with the host though, so if anyone is feeling kind to make the request on my behalf, I would appreciate it very much since I am being prevented from posting in that section myself. Thnaks.

Related

Help Can't Update OTA Gingerbread 2.3.4 Not Rooted Droid X2

Help Can't Update OTA Gingerbread 2.3.4 Not Rooted Droid X2
I have been trying for a month no luck
no help from Moto or Verizon.
I'd like to get this update
See attachment this is what I get
when I try 2 Pull
Thank You
You could always try to SBF and see if that helps. Applying a SBF is fairly simple, check out some of the guides on the forum.
+1 to sbf comment
U could even just sbf straight to 2.3.4
Did u ever root before at all?(this phone that is)
ashclepdia said:
+1 to sbf comment
U could even just sbf straight to 2.3.4
Did u ever root before at all?(this phone that is)
Click to expand...
Click to collapse
I 'd like to fix this problem of no OTA updated
No (No)
This is my first smartphone.
Got it mid-July
Thank You
ImgBurn said:
Help Can't Update OTA Gingerbread 2.3.4 Not Rooted Droid X2
I have been trying for a month no luck
no help from Moto or Verizon.
I'd like to get this update
See attachment this is what I get
when I try 2 Pull
Thank You
Click to expand...
Click to collapse
SBF is always an option, if you're comfortable doing it. It's nothing really.
So you jumped through vzw support hoops and they just leave you hanging?! I'd tell them you want it replaced w/ another for which the replacement will likely come w/ 2.3.4 installed. Have you tried taking it to a corporate store and ask if they can manually push it to your phone?
Sent from my DROID X2 using xda premium
Have you attempted to update while connected.to wifi?
I've always updated over wifi...
Have you done anything to this phone? Where did you get the phone? I only ask because if the phone came from someone else, perhaps something was done to it.
Many times people rename some of their files or uninstall some of the files, like fota and updater and it will fail to update. Aside from that, SBF is probably the most effecient way to fix the issue.
reaktorblue said:
Have you done anything to this phone? Where did you get the phone? I only ask because if the phone came from someone else, perhaps something was done to it.
Many times people rename some of their files or uninstall some of the files, like fota and updater and it will fail to update. Aside from that, SBF is probably the most effecient way to fix the issue.
Click to expand...
Click to collapse
Hi
I've done very little to phone purchased
from Verizon in mid July. Froyo 2.2.2 was
installed. Sometime in August updated OTA
to GingerBread 2.3.3 no problem.
Fastfoward to present I've tried for last
month no push and when I try to pull
always get same result see attached.
I just don't get it...
Try checking this setting. You will want to make sure it's enabled and that you can make and receive phone calls.
Battery & Data Manager -> Data Delivery -> Background Data -> Enabled
If that does not work for you, you can also try to reset to factory defaults. This may fix the issue but you'll lose all your personal settings.
Undoubtedly, unless there is a hardware problem with your phone, which is possible but not probable, SBFing directly to 2.3.4 WILL fix the issue. Again, you'll lose your settings and such but you'll have a fresh phone and you can move on to greener pastures instead of worrying about what is wrong with the phone.
You can find a very well written guide that will walk you through the process below.
http://forum.xda-developers.com/showthread.php?t=1317707
This is what I would recommend as you could spend hours, days, even months trying to fix your phone and still not find out what app or quirky issue the phone is having. Applying an SBF update sounds complicated but in reality, its as simple as installing a driver for a printer.
Simply plug in the device, run an application, point it do the SBF file, and leave it alone until it finishes. The guide goes into detail, including the resources you'll need, such as the SBF file, the Motorola Drivers, RSD Lite, and what to expect.
Even if you choose to continue troubleshooting, I would recommend reading the guide anyway just to familiarize yourself with how your phone works. In the future it'll make troubleshooting your phone a bit easier.
Hope that helps!
reaktorblue
This looked like the solution crosses fingers
(Battery & Data Manager -> Data Delivery -> Background Data -> Enabled)
I was hoping as I had turned off my Phone to charge it. I though o yea
this is the problem. No such luck it was enabled. I'd like to try the
SBFing directly to 2.3.4 but don't you have to be rooted. I didn't really want
to root at this point with this issue of no OTA.
Setting to factory defaults looks like what I'll try but losing all my settings
ah. Is there any way to back up phone so not to lose all my settings
with out rooting.
Thank You
Thank everyone for all the suggestions
P.S. I was on the phone with VZ yesterday for 2.5 Hours
The Tech ended up telling me there was no update .
Last Update was 2.3.3 in August.
WoW Whats Up With That??
ImgBurn said:
reaktorblue
This looked like the solution crosses fingers
(Battery & Data Manager -> Data Delivery -> Background Data -> Enabled)
I was hoping as I had turned off my Phone to charge it. I though o yea
this is the problem. No such luck it was enabled. I'd like to try the
SBFing directly to 2.3.4 but don't you have to be rooted. I didn't really want
to root at this point with this issue of no OTA.
Setting to factory defaults looks like what I'll try but losing all my settings
ah. Is there any way to back up phone so not to lose all my settings
with out rooting.
Thank You
Thank everyone for all the suggestions
P.S. I was on the phone with VZ yesterday for 2.5 Hours
The Tech ended up telling me there was no update .
Last Update was 2.3.3 in August.
WoW Whats Up With That??
Click to expand...
Click to collapse
AH yes...the trusty vzw level one tech
U better believe there is a 2.3.4 lol. I was in the soak test for it and the Motorola forum manager Matt announced it being released lol
Oh yeah. MAYBE u will have some.luck over there if u wanna try Motorola support forums before sbf route. Droidx2 forum manager Matt MAY(can't say he has ALWAYS been helpful) help ya out.
Aldo vzwsupport on twitter I find better than phoning them. Motorola also has tech support on twitter.
But u DO NOT have to be rooted in order to sbf.
not even a little bit lol.
if u WERE rooted sbf would make u lose that root.
Sbf rewrites your system partition and flashes the necessary files and "stuff"(lol) so that your phone is "factory out of box" condition. Root is totally NOT NEEDED to do an SBF.
U hook up to your computer.
Put ur.phone into RSD protocol mode and.use the rsdlite program u can download to ur computer(w/ necessary drivers) and flash the sbf file to ur phone.
pretty simple thing.to do.
Longest part really is downloading the necessary drivers and programs and files.
Go here to read a great easy to follow tutorial on how to sbf.
http://forum.xda-developers.com/showthread.php?t=1317707
It has ALL the necessary links to downloads for sbf files, drivers, rsdlite program, etc
Everything u could need is I'm that thread
don't be.intimidated by the lengthy tutorial. It is easier than u think.
PLUS if u have any questions or.need clarification u can post in that thread and someone knowledgeable will help you out.
or u can get on the #dx2 channel at webchat.freenode.net for "real time" help. Its an IRC(chatroom) for us X2 users. Usually someone is there who can help ya out
ALSO please keep us updated on ur situation. If u find a solution PLEASE POST IT HERE...so that way others who run into this problem can.find the solution they need
Good luck brotha!
WTF
Hy guys,
Thanks for all your help & suggestions ashclepdia, reaktorblue
& X0dus. You won't, I can't believe this is what was stopping me
from getting update. I saw it before but reading it's description
I didn't think it would be a problem and I'd save battery
power. I had this setting checked (as you see in attached)
the second I unchecked it and returned to home screen update
was available.
WoW I spent hours no days with moto & vz level 2 tech's and
not 1 every went over my setting's. The level of incompetence
& misinformation from these 2 company's well they should hang there
heads in shame. Don't get me started I could write a book about
all the nonsense these 2 have put me through sense buying
this phone from vz in July 2011. Sorry For the rant.
Anyway I sincerely want to thank all you guys for your help
& suggestions. There's more talent in this post then vz & moto
L2 techs put together . This forum ROCKS!!!!!!!!!!!!!!!!
P.S. So I guess if you don't want an update check this box .
Also New Rules corporate store only have salesman got
this from L2 tech & calling local store. Guess we know
there priorities.
Hahaha....I guess our android system is considered a "social application " in itself lol...
Good to see ya got the fix...and glad it ended up not being something serious.
Could u also add the word "SOLVED" to the beginning of thread title for others who experience this problem.
And yeah...I have been told by many people that I should try to get a job as a phone tech support since im always helping my friends/coworker fix phone problems Hahaha...and I still consider myself to be a "noob "to Lol

updating unlocked atrix from 2.3.4 to 2.3.6

i want to update my unlocked atrix to 2.3.6 but i see that people say that it's gonna brick my phone so there is no way to update it?
my atrix is on stock 2.3.4
unlocked
rooted i guess
career unlocked by unlock code
plz someone help me :S
If you use a fruitcake, you'll be fine. If you wipe all data/system/etc and use the sbf, you will also be fine. The worst I've heard of is a soft brick that takes a hell of a lot of time and effort to fix. So, I'd go with fruitcake if I were you. I did it yesterday, and it worked like a charm.
http://forum.xda-developers.com/showthread.php?p=22552497#post22552497
Fun498 said:
If you use a fruitcake, you'll be fine. If you wipe all data/system/etc and use the sbf, you will also be fine. The worst I've heard of is a soft brick that takes a hell of a lot of time and effort to fix. So, I'd go with fruitcake if I were you. I did it yesterday, and it worked like a charm.
http://forum.xda-developers.com/showthread.php?p=22552497#post22552497
Click to expand...
Click to collapse
what about OTA ? will it hard brick my phone?
soudy1994 said:
what about OTA ? will it hard brick my phone?
Click to expand...
Click to collapse
There is risk that it can
Sent from my MB860 using Tapatalk
Fun498 said:
If you use a fruitcake, you'll be fine. If you wipe all data/system/etc and use the sbf, you will also be fine. The worst I've heard of is a soft brick that takes a hell of a lot of time and effort to fix. So, I'd go with fruitcake if I were you. I did it yesterday, and it worked like a charm.
http://forum.xda-developers.com/showthread.php?p=22552497#post22552497
Click to expand...
Click to collapse
Do you still have that file and can you post it some where?
The file you linked to is not valid anymore and I'm in desperate need to get it.
Thanks for any help
there is no other way? cuz i never used adb before and i'm afraid i will do something wrong
c'mon guys i need help
A few pages later on the new link is posted. I forget exactly where. It's a mediafire link if I remember correctly. And I wouldn't risk a hard brick if I were you. I flashed a SBF to return my broken phone back to Motorola and attempt warranty, but the phone was useless either way. It worked, but I had to wipe nearly every partition. Please don't risk. Fruitcake is proven
this thread isn't TOO dead
I thought there was a way to officially update the atrix to 2.3.6 since that is the official version O/S it supports?
Just picked one up yesterday and it has 2.3.4
redking117 said:
this thread isn't TOO dead
I thought there was a way to officially update the atrix to 2.3.6 since that is the official version O/S it supports?
Just picked one up yesterday and it has 2.3.4
Click to expand...
Click to collapse
Yeah I just went into "about phone" and hit update... what's wrong with that?
Can't you still root 2.3.6?
If your phone is working fine now do yourself a favor and leave it alone. OTA update has caused many problems like killing wifi and many people have had problems playing with roms and you can't go back. This is good advice.
Sent from my MB860 using XDA
I was subscribed to this and just want to add my data point:
on unlocked (bootloader) phone ("Unlocked" printed on boot screen), upgraded to 2.3.6 over the air. This caused Unlocked to disappear from boot screen but I believe I was still technically unlocked. I went through the unlock process again just to be safe. which put "unlocked" back on boot screen, then unrooted by normal flash recovery method, and running fine an dandy all along
I did have a problem with a bad sim card previously, which made it seem like 2.3.6 was a problem, but it is not, for me at least.

[Q] Software update Photon 4G

After searching for an answer here, I noticed Sprint is saying that the 2.3.5 update is available. I know there was some issues with it "leaking" out after the soak test but has anyone acquired the file to manually update their photon? Ive not seen an sbf or even an update.zip, and both Sprint and Motorola say the update should be available for all. I've gone back to completely stock, and still no update. Sprint of course says its there, but neither anyone on the phone or at the stores can help me get it. I am comfortable enough doing it myself if I had the requisite files, but I don/t Is there anyone out there in photon land who might have the file I am searching for? Its PHOTON 4G_MR5 (4.5.1A-1_SUN-254_12.Sprint.en.US) (45.4.12.MB855.Sprint.en.US). If anyone has it or if this has been answered I apologize, but I have searched without success, and as usual both the carrier and manufacturer are useless.... I know what the update brings and no I don't care about the boot loader. I just want the update and the 1080p recording!!
Thank you!
If you have the file, please PM me, and let me know. Otherwise, I will check back and hopefully someone will have an answer for me. I am not going to post my email or anything, so please PM me about it!
If you go and upgrade to 2.3.5 you wont be able to unlock the bootloader anymore
Thanks but
Modo-mopho said:
If you go and upgrade to 2.3.5 you wont be able to unlock the bootloader anymore
Click to expand...
Click to collapse
IF you re-read my original question, I am NOT concerned with that, I simply want the file. Anyone else?
If the software update menu doesn't work for you, look into this. I haven't used this file, I don't know for sure but others have stated that they think that's the official one.
It would be a mistake on all counts.. Don't people realize that you can get 'everything' that the 2.3.5 update entails including 1080p without crippling your poor phone? Its like buying a Ferrari so you can drive 35mph around town..
And there's no need to go all CAPS LOCK on him, he was just trying to be informative.
[email protected] said:
IF you re-read my original question, I am NOT concerned with that, I simply want the file. Anyone else?
Click to expand...
Click to collapse
Check the Imperium Website downloads section. You need to be on 198_6 prior to flashing.
Things to keep in mind before you flash it:
Every single fix or improvement has already been done by the devs here without the drawbacks
The devs here have already improved upon this release so custom ROM's are faster and offer more features
If you don't like=You have to buy a new phone
If it breaks something=You have to buy a new phone
If you change your mind=You have to buy a new phone
If you want GSM support in the US=You have to buy a new phone
YOU CANNOT DOWNGRADE, UNLOCK OR REVERT THE CHANGES MADE BY THIS UPDATE
the source code was just added earlier today to sourceforge.net check it out it might help...
http :// sourceforge. net/projects/photon4g.motorola/files/
Thank you all, I think lokifish made up my mind for me. And I do apologize about the caps, it was just a very unhelpful post. Not their fault I realize, but just wasnt helping my situation. I will look into the custom roms a little further I think.
Sent from my MB855 using XDA
Well I just got a Warranty replacement from my local Sprint store and my Photon states system version 45.3.6.MB855.Sprint.en.US and Android version 2.3.4. I don't have any system updates and I tried flashing the sbf to unlock the bootloader and it fails. I do believe the version I have won't allow me to unlock but if the Android version is suppose to be 2.3.5 on this system version I wonder how the hell I have 2.3.4. Anyone with an idea???
jmsdahutt said:
Well I just got a Warranty replacement from my local Sprint store and my Photon states system version 45.3.6.MB855.Sprint.en.US and Android version 2.3.4. I don't have any system updates and I tried flashing the sbf to unlock the bootloader and it fails. I do believe the version I have won't allow me to unlock but if the Android version is suppose to be 2.3.5 on this system version I wonder how the hell I have 2.3.4. Anyone with an idea???
Click to expand...
Click to collapse
To unlock you want 2.3.4. What guide did you follow to attempt unlock?
I myself got a replacement photon less than a month ago and was able to succesfully unlock my bootloader. However I did struggle a bit. I will look for all the files I used and see if I can send you on the right path.
Lokifish Marz said:
To unlock you want 2.3.4. What guide did you follow to attempt unlock?
Click to expand...
Click to collapse
I used the pudding guide with bootloader unlock method.
http://forum.xda-developers.com/showthread.php?t=1216143
mquezada21 said:
I myself got a replacement photon less than a month ago and was able to succesfully unlock my bootloader. However I did struggle a bit. I will look for all the files I used and see if I can send you on the right path.
Click to expand...
Click to collapse
Thanks, but not necessary as I'm the root-unlock-relock guy that hosts all the files and maintains the Photon Compendium.
jmsdahutt said:
I used the pudding guide with bootloader unlock method.
http://forum.xda-developers.com/showthread.php?t=1216143
Click to expand...
Click to collapse
I hope you didn't flash the 2.3.5 pudding. That thread is out of date and not maintained. For all the files and guide, why not use the updated and maintained Photon Compendium?
mquezada21 said:
I myself got a replacement photon less than a month ago and was able to succesfully unlock my bootloader. However I did struggle a bit. I will look for all the files I used and see if I can send you on the right path.
Click to expand...
Click to collapse
Cool! I would appreciate that! I'm fairly good at figuring things out but I'm still new to the photon stuff. I left mine stock after I got it then my girlfriend broke her phone so I didnt have it for a while. LOL! I finally have it back now. Now I like to learn more about development on different devices to contribute more to the community. Just taking it step by step now LOL!
---------- Post added at 02:44 PM ---------- Previous post was at 02:39 PM ----------
Lokifish Marz said:
Thanks, but not necessary as I'm the root-unlock-relock guy that hosts all the files and maintains the Photon Compendium.
I hope you didn't flash the 2.3.5 pudding. That thread is out of date and not maintained. For all the files and guide, why not use the updated and maintained Photon Compendium?
Click to expand...
Click to collapse
For some reason the derpunlock.sbf file when I flash fails. I've tried redownloading the file and tried again with the same results. My phone is in usb debub mode charge only and all needed drivers installed. Is that normal????
jmsdahutt said:
Cool! I would appreciate that! I'm fairly good at figuring things out but I'm still new to the photon stuff. I left mine stock after I got it then my girlfriend broke her phone so I didnt have it for a while. LOL! I finally have it back now. Now I like to learn more about development on different devices to contribute more to the community. Just taking it step by step now LOL!
---------- Post added at 02:44 PM ---------- Previous post was at 02:39 PM ----------
For some reason the derpunlock.sbf file when I flash fails. I've tried redownloading the file and tried again with the same results. My phone is in usb debub mode charge only and all needed drivers installed. Is that normal????
Click to expand...
Click to collapse
DO NOT DOWNLOAD FROM THE PUDDING THREAD!!! PEOPLE HAVE PERMANENTLY LOCKED THEIR PHONE BY FLASHING THE WRONG FILE!!!
DOWNLOAD THE ROOT-UNLOCK-RELOCK PACK!!!
You have to follow the steps!!! If you are in USB debug then your are not in RSD mode which means you can't flash ANY SBF. Straight from the Compendium;
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash derpunlock.sbf.
Close RSD Lite and disconnect phone.
Reboot phone into fastboot mode (same process as getting to RSD mode) and connect phone to computer
Double click "Command Prompt" shortcut in the "Unlock" folder.
In the Command Prompt window type moto-fastboot oem unlock
Look for the UNIQUE ID number and copy it.
Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED (fastboot should reply <bootloader> Device is now unlocked )
Lokifish Marz said:
Thanks, but not necessary as I'm the root-unlock-relock guy that hosts all the files and maintains the Photon Compendium.
Click to expand...
Click to collapse
There is no need to be like that, thats pretty mest up I'm just trying to help the guy.... -__-'
Lokifish Marz said:
Thanks, but not necessary as I'm the root-unlock-relock guy that hosts all the files and maintains the Photon Compendium.
I hope you didn't flash the 2.3.5 pudding. That thread is out of date and not maintained. For all the files and guide, why not use the updated and maintained Photon Compendium?
Click to expand...
Click to collapse
I flashed from photon compendium
---------- Post added at 03:02 PM ---------- Previous post was at 02:49 PM ----------
Lokifish Marz said:
DO NOT DOWNLOAD FROM THE PUDDING THREAD!!! PEOPLE HAVE PERMANENTLY LOCKED THEIR PHONE BY FLASHING THE WRONG FILE!!!
DOWNLOAD THE ROOT-UNLOCK-RELOCK PACK!!!
You have to follow the steps!!! If you are in USB debug then your are not in RSD mode which means you can't flash ANY SBF. Straight from the Compendium;
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash derpunlock.sbf.
Close RSD Lite and disconnect phone.
Reboot phone into fastboot mode (same process as getting to RSD mode) and connect phone to computer
Double click "Command Prompt" shortcut in the "Unlock" folder.
In the Command Prompt window type moto-fastboot oem unlock
Look for the UNIQUE ID number and copy it.
Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED (fastboot should reply <bootloader> Device is now unlocked )
Click to expand...
Click to collapse
I'll try again and return with the results! I appreciate the help!
[email protected] said:
After searching for an answer here, I noticed Sprint is saying that the 2.3.5 update is available. I know there was some issues with it "leaking" out after the soak test but has anyone acquired the file to manually update their photon? Ive not seen an sbf or even an update.zip, and both Sprint and Motorola say the update should be available for all. I've gone back to completely stock, and still no update. Sprint of course says its there, but neither anyone on the phone or at the stores can help me get it. I am comfortable enough doing it myself if I had the requisite files, but I don/t Is there anyone out there in photon land who might have the file I am searching for? Its PHOTON 4G_MR5 (4.5.1A-1_SUN-254_12.Sprint.en.US) (45.4.12.MB855.Sprint.en.US).
Click to expand...
Click to collapse
IMHO this update is totally not worth it. I (admittedly) totally screwed up and took this update. My phone is rooted but on stock. I hadn't had any other problems with other updates but I guess I was just playing with fire before and got lucky then. Well, 12 hours and a lot of yelling later, I have my phone back. I won't accept the update, not worth the headache again.
In all of my research to fix the phone, I found this YouTube video... (my new membership won't let me post links,). Anyway, search on YouTube for "How to unroot / unbrick the Motorola Photon 4G to stock Android" by QBKing77. The video should come right up. LOTS OF HELP! I'm a visual learner and like to see others run through the process first before I try so I know what to expect. Just make sure you have the latest files before you begin the whole process.
Lots of luck!
Agree that this update is not worth it in terms of functionality. I'm honestly not sure why Moto is bothering with it, but it speaks well of their commitment to support.
But, since (after endless ROM cooking & flashing in the the WinMo days), I've decided to stay stock Android, I did this during the soak test so that perhaps I can get a peak at stock ICS a bit early in the ICS soak.
BUT - anyone who likes custom ROMs needs to totally ignore 2.3.5 and its locked bootloader.
Wow.....
I have know a lot more
:good::good::good:

Install ICS from another region.

I bought a Razr Maxx from Amazon, it came from Hong Kong with AsiaRetail ROM, it works fine with except the encoding of music tags. I want to switch to the same Motorola's Android version but from another region (For example: US). I was reading a few procedures, but all they explains migratations from GB to ICS and I am already on ICS (673.94.328.XT910.AsiaRetail.en.03). Does anybody knows any procedure to download and install Motorola's Android stock ROM?
Thanks in advance.
You can use RSDLite to install any european ICS version. I did it in mine too, from an Asian ROM to Retail.eu (Rtail British)
http://forum.xda-developers.com/showthread.php?t=1850683
http://sbf.droid-developers.org/umts_spyder/list.php
EDIT: also this one I posted a while ago: http://forum.xda-developers.com/showthread.php?p=31477142#post31477142
davizera said:
You can use RSDLite to install any european ICS version. I did it in mine too, from an Asian ROM to Retail.eu (Rtail British)
http://forum.xda-developers.com/showthread.php?t=1850683
http://sbf.droid-developers.org/umts_spyder/list.php
EDIT: also this one I posted a while ago: http://forum.xda-developers.com/showthread.php?p=31477142#post31477142
Click to expand...
Click to collapse
Thank you so much. It worked just fine, I had issues on the first boot but I applied a factory reset and it solved.
I have 2 questions:
- Is it totally secure the sbf files from droid-developers? (I had never hear it before)
- I can't share my data conection, i don't have Internet on my computer through the phone
rcdeoliveira said:
Thank you so much. It worked just fine, I had issues on the first boot but I applied a factory reset and it solved.
I have 2 questions:
- Is it totally secure the sbf files from droid-developers? (I had never hear it before)
- I can't share my data conection, i don't have Internet on my computer through the phone
Click to expand...
Click to collapse
I really think that the sbf files are safe, there's no reason to think differently. It's not like they would put a worm on it, but I think they are pretty safe, coming from a leak.
About the data connection, did you try changing from open to WEP to WPA and so on?
davizera said:
I really think that the sbf files are safe, there's no reason to think differently. It's not like they would put a worm on it, but I think they are pretty safe, coming from a leak.
About the data connection, did you try changing from open to WEP to WPA and so on?
Click to expand...
Click to collapse
Ummmm, i didn't try that, but i have connection to the gateway IP (ping), but i can't go beyond it.
I have another issue, encryption for applications and disk doesn't work, I always get a black screen and never finish the process.
davizera said:
I really think that the sbf files are safe, there's no reason to think differently. It's not like they would put a worm on it, but I think they are pretty safe, coming from a leak.
Click to expand...
Click to collapse
Various components of the firmware need to be signed by Motorola in order to be flashable via fastboot. That's one of few pros of a locked bootloader.
rcdeoliveira said:
Ummmm, i didn't try that, but i have connection to the gateway IP (ping), but i can't go beyond it.
I have another issue, encryption for applications and disk doesn't work, I always get a black screen and never finish the process.
Click to expand...
Click to collapse
Try a different set if sbf files. You may have gotten a corrupt down load. Or possibly a modded set.
Sent from my DROID RAZR using xda app-developers app
sttierney said:
Try a different set if sbf files. You may have gotten a corrupt down load. Or possibly a modded set.
Click to expand...
Click to collapse
Mate, you clearly don't know what are you talking about - please stop giving wrong advice. There are checksums and digital signatures in place, which are verified by RSD Lite and phone prior to flashing, thus modified/damaged file won't be accepted by the device. Only genuine files, which were signed by Motorola, can be flashed to the phone in the fastboot mode.
@rcdeoliveira: With regard to your network issue, please debug your upstream connection - e.g. TTL. This feature definitely works for me. Regarding the whole device encryption, initial run may take up a lot of time, so be sure to leave the device at the "black screen" overnight attached to a charger.
I need help. I just bought used droid razr maxx. Then When I got home, i realize it cant be rooted,something bout the su binary cant be pushed?Then I did some research,and I realize,since my razr maxx is from china,it somehow is different? Anybody know how to change this? For god sake,I cant even install some simple apps such ass foursquare?? Can I just place Any region update files in the MicroSD n update?My firmware is GAS_ASIA_SPYDERICS_P008 n System version 67.213.906.XT910.ChinaRetail.en.CN . I read about flashing using fastboot but my pc cant detect my fone when in flashboot,why is that? All the drivers are already installed. Now I cant root or use custom ROM. T_T

Bricked by OTA Update! [Not rooted]

Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app

Categories

Resources