Related
Hello Everyone,
I had this random reboot problem and posted it in various forums on the web but had not found the root cause of the problem.
But now I seemed to have completely solved it. Here is how for those experiencing similar issues.
1. If you are having it from just few days, then it is surely got to do with the phone trying to fetch data when the signal strength is very low. I found out that -113dbm is the least signal possible and the phone displays a '+' mark in the signal status notification bar. Hence when the signal goes to somewhere near -112dbm and -102dbm the phone goes into a reboot.
So if this is your problem, then you need to download "Shutupbatterymanager" from the market and set the phone to turn off data connections when the signal is below a certain threshold. It is also attached in this post below. For example you can slide the signal bar in the app and set it to -102dbm cutoff after which it will disable the data connections. This is one way of solving the issue if you have had reboot problems occur very recently.
2. The best way to solve this issue is to compromise on your 'downgradability'. For me the above option did not work well after a few test runs and then I accidentally found out that flashing this file (thanks to Higgsy for making this) is the best way. Maybe motorola found out the issue after numerous posts in their support forum and has solved it with a change in the kernel. So just download the file and flash the froyo 2.2 GB UK sbf file with your RSDlite.
It would be helpful if someone can post their kernel version. The flashed one after using this file that seems to solve the problem is [email protected] #1
Hope it solves all your reboot issues. Google you can please index this for some much needed help for desperate Defy owners.
Thanks to: Higgsy and Sorensiim
PS: Important point i forgot to mention is that the change in the kernel is reflected when you get into recovery by holding Vol down + power button. Here if you are on newer and changed version, touching the corner of screen does not work. Instead pressing the volume rocker simultaneously up+down will enter recovery functions.
Substantially is the UK 3.4.2-117 sbf that have you flashed?
alezzandro said:
Substantially is the UK 3.4.2-117 sbf that have you flashed?
Click to expand...
Click to collapse
Yes, but it is not the complete sbf. Some segments have been knocked off and it has been repacked by Higgsy so that there is no locked bootloader and downgradability problem.
Which means the complete SBF already has this fix built-in?
Yes it should.
Sent from my MB525 using XDA App
okidoki - thanks good to know
I would verify the change by going into stock recovery.
Sent from my MB525 using XDA App
How about if I do still have the problem with Pay'S Rom (3.0/3.1) that is based on: 3.4.2_145-003 Motorola SBF.
I cant flash the sbf file that you named because its older I think. Right?
Is there a chance of getting a cleaned and fixed version of the 3.4.2_145-003 Motorola SBF?
OK before I get confused with the build numbers do this. Power off phone and boot with power button and volume down. Once recovery appears tell me if you are able to enter recovery using the corner of the screen or is it through pressing the volume rocker up and down simultaneously.
It works by pressing the volume rocker up and down simultaneously and NOT by a tab in a corner.
mrt3k said:
It works by pressing the volume rocker up and down simultaneously and NOT by a tab in a corner.
Click to expand...
Click to collapse
OK then you are already on the newest froyo kernels and not on the eclair ones which had the problem.
Now tell me, is your rebooting problem still there?. When do you face it? What is your observation?.
i think if you are using pays rom, then you must've flashed the whole sbf already. you don't need to flash this partial old sbf, since the new sbf should include the old fix (of course some assumption here, hehe) you probably can't downgrade using official sbf either...
mrt3k said:
How about if I do still have the problem with Pay'S Rom (3.0/3.1) that is based on: 3.4.2_145-003 Motorola SBF.
I cant flash the sbf file that you named because its older I think. Right?
Is there a chance of getting a cleaned and fixed version of the 3.4.2_145-003 Motorola SBF?
Click to expand...
Click to collapse
Yes I flashed the most recent kernel, as I mentioned before.
Well, the reboot happens just spontaneously some times a day and also often when a calls or an SMS comes in. But not always, usually only when the phone has not just been rebooted but is still switched on for some time.
But for now: I changed the sim card (from T-Mobile Germany to Base/Eplus/Germany - jus for testing) and afterwards there was no reboot for 12 hours. So maybe the reason is the sim-card, thats my idea at least. But with the Sim-card I want to use on a regular bases, the T-Mobile one, I did have the reboot problem even with the newest kernel.
mrt3k said:
Yes I flashed the most recent kernel, as I mentioned before.
Well, the reboot happens just spontaneously some times a day and also often when a calls or an SMS comes in. But not always, usually only when the phone has not just been rebooted but is still switched on for some time.
But for now: I changed the sim card (from T-Mobile Germany to Base/Eplus/Germany - jus for testing) and afterwards there was no reboot for 12 hours. So maybe the reason is the sim-card, thats my idea at least. But with the Sim-card I want to use on a regular bases, the T-Mobile one, I did have the reboot problem even with the newest kernel.
Click to expand...
Click to collapse
OK then. Continue your observation on the sim card and come back again to report if this occurs again. All the best.
Ok I will do so. Thanks for your help!
But apart from the hint on the sim-card (which is not yet proven) - Any idea? Do we know that the brand new kernel does not have the error anymore? Or could it still be part of the release if Moto did not realize and fix it?
So, do you see any other thing that could cause all the reboots?
Every rom out there has ways by which you can still maintain downgradability. I did the same. I loaded chinese sbf and then tried various roms by restoring it by nandroid backups. Also people like jboogie and higgsy give boot only and safe sbfs which can be tried. For me flashing the above attached sbf from higgsy and restoring the rom posted by Iaoa PL deblur solved the problem totally.
Sent from my MB525 using XDA App
Strange thing, without any further changed to the system, no update or so..... suddenly there are no reboots anymore. The problem seems to have been solved - at least no reboot for nearly a day so far.
What i just did: Removed the SIM, put another in, later changed again. Also: Put out SD-card, formated it again (standard sector size - was 32byte before) and put all files back on the card and inserted it again.
I also uninstalled JuiceDefender.
Well, either its total random or one f the above mentiond changes whatsoever solves the problem. I hope it'll stay like this now - I'm happy than!
mrt3k said:
Strange thing, without any further changed to the system, no update or so..... suddenly there are no reboots anymore. The problem seems to have been solved - at least no reboot for nearly a day so far.
What i just did: Removed the SIM, put another in, later changed again. Also: Put out SD-card, formated it again (standard sector size - was 32byte before) and put all files back on the card and inserted it again.
I also uninstalled JuiceDefender.
Well, either its total random or one f the above mentiond changes whatsoever solves the problem. I hope it'll stay like this now - I'm happy than!
Click to expand...
Click to collapse
Yeaaah, thats some good news. Enjoy your Defy
After 100h of perfect work of my DEFY, I rebooted it - and what happened? After this, the reboot problem! Same thing than before!
Spontanious reboot and reboots when a call comes in!
What I also observed: after some reboots, the Defy does not find any services, "only emergency calls possible". Could that be a hint?
mrt3k said:
After 100h of perfect work of my DEFY, I rebooted it - and what happened? After this, the reboot problem! Same thing than before!
Spontanious reboot and reboots when a call comes in!
What I also observed: after some reboots, the Defy does not find any services, "only emergency calls possible". Could that be a hint?
Click to expand...
Click to collapse
This is exactly the same problem I had. Why dont you do this. Flash the new poland leaked sbf and then restore nandroid backup from Iaoa. He has a rom for the same poland version.
This solved my problem. Hope it works for you too.
And please remember that you can get back to 2.51 roms and nothing below that if you flash this sbf.
I just tried to flash the Telstra (Australia) SBF. No info comes up in file properties and it gives an instant 'failed flash' message.
I am a bit stuck- i can only flash the China Froyo and the GB Froyo, the only 'Fixed' SBF I can ever flash is the 2.2GB_NoCG_31_39.sbf -(Higgsy fix). The China rom is the first and only Froyo rom I flashed with the above fix.
1a. :I want to know why I cannot flash 'fixed SBF's' that come with JBoogie, ADXLmod, barebones etc roms.
1b :Why do I still have to use the 'Higgsy fix' 2.2GB_NoCG_31_39.sbf? It appears that I am somehow locked to it.
1c :Is it because of the Telstra rom I am on- with all rom flashing instructions, it is mentioned eg 'if you are on 2,21 or 2.34 fw etc- no reference is ever made to the 2.26 fw.
2: I want to know how flashing a rom without the corresponding SBF actually affects the operating of the rom- eg: I get random reboots, black screens, freezups=- is this likely an issue with the rom or because I cannot flash the fixed SBF.
3. Will restoring a Telstra nanodroid on top of the China Froyo SBF that I am running, then applying the fixed Telstra SBF that racca graciously provided make my Defy exactly like stock- or will there still be remnants of the China Froyo etc rattling around under the hood and potentially affecting stability and continuing to affect my ability to flash fixed SBF's as per Q 1 & 2.
4. Does anyone have a FullTelstra SBF that works unlike the one already posted on XDA.
I have tried renamimg and moving sbf to root folder as per a suggestion for 64 bit windows, though i am only on 32bit, it didn't work for me- 'start' is still greyed out in RSDLite..
I have also tried different rsdlite versions.
I welcome any other suggestions or questions.. At least I would like to know what is going on and how it affects my phone as I have spent hours and hours searching these and other forums and am none the wiser..
Cheers
Gavin
Accidental 2nd post-ignore.
what exactly are you trying to do?
i can't make much out of your long and pointless statements.
be specific about what you need, then maybe we can help.
all i can understand is that you might want the fixed sbf, so here it is.
http://mir.cr/6MJBVDCN
Thanks for that, pointless is a bit harsh though, long maybe- i was trying to give some background to prevent 'have you tried that, just do this- when it is clearly not applicable to my situation.
I will try to put it in point form.
I hope that is a bit clearer, but it is a complicated situation- there are alot of threads dancing around similar themes, but I cannot find specific answers to these questions- i can't see how I could provide less information without having 5 pages of people directing me to posts that I have already looked at but aren't applicable, so yes it is a bit long, but by doing this much misdirected effort is saved by myself and those helping.
Thanks again
Looking at my original post again, it was hard to see what I was asking, thanks racca.
I just restored the Telstra factory reset nanodroid- the start button was greyed out with the Telstra SBF , so i can't use it. Had to use the 'Higgsy fix' to get it to boot. Weird, i just don't understand it.
To be honest, with all the eventual issues with any rom i use, i would prefer to go back to stock (i will have to put up with the grey status bar, short battery life and no flash). I am tired of getting crashes at the most inopportune times.
Can't wait until the bootloader is fully cracked- I have put Gingervillain (CM7 base) on her Desire, which is much more stable than any rom when i was using it.
Update- it just won't boot now, have to reflash the China Froyo SBF, looks like I am stuck with daily @ 3x daily reboots, bluetooth that works 60% of the time, dropped calls etc....
Change SBF file name
Hey there,
I kinda have the same issues as you do, I think...
The RDS lite gave me an instant ROM-flash error when trying various SBF's. I simply renamed the file name to an SBF file name that was working, yes it got a little confusing... first I renamed the original working SBF to *.old.
Suddenly the flash process was working, I've renamed SBF-files on 4 different occasions in order to get it to work.
I'm not quite sure whether you have this issue or you have something different going on, but feel free to try it.
//Dave
Sounds like a plan, I will give it a go. Thanks.
Thanks Dave69 and Racca, i just renamed the TElstra fixed sbf to the higgsy fix; restored the stock nanodroid and flashed it and it worked. It at least gives me the confidence to flash others now, but will sit on this for a bit- don't have time for more tinkering this weekend.
Titanium wouldn't work with the Telstra rom- said it had restored apps, but wouldn't restore evn one.
Thankfully I got Barebones running, SBF and all. Looks great. Thanks guys.
I would still like to know what's going on though, I haven't tried the TElstra full SBF with the rename yet- it had a different issue than others- just failed. May try again later.
Sounds like you have the same problem as me, was on the telstra on. Not being careful enough I flashed a non downgradable 3.4.2_155-002 sbf. So now I can't downgrade back to the stock Telstra one. I have tried both nandroid backups and flashing the stock telstra sbf and neither work. so am stuck on this rom running JBoogie GingerBlur
Not compaining, for a blur rom it is quite fast, only thing is I can't downgrade back to telstra if the phone needs to be returned for anything.
Hope this helps.
Cheers.
Try following the renaming method-though i had titanium issues, it os enough to get me through a warranty claim- i did it before with the same nanodroid backup from xda. Btw, i just flashed the 3.42 out of frustration and it let me go back with the renamed fixed sbf.
I am very impressed with barebones, even the xda app is quicker...
superfastmonkey said:
Try following the renaming method-though i had titanium issues, it os enough to get me through a warranty claim- i did it before with the same nanodroid backup from xda. Btw, i just flashed the 3.42 out of frustration and it let me go back with the renamed fixed sbf.
I am very impressed with barebones, even the xda app is quicker...
Click to expand...
Click to collapse
ok, now where do i begin. i'll just say what i can think of instead of answering every single question.
sbf's contains various code groups as you may noticed while flashing it slipts into smaller pieces.
out of those, cg31&39 are non-downgradable and the pair of them must match. all other partitions on the phone are either not flashed by the sbf (e.g. bootloader/mbmloader, pds), useless (cdrom) or downgradable (kernel, recovery, lbl, devtree).
there are no hardware incompatibilities except the chinese ones, but if you don't update cg31(cdt) to match your /system(cg39) you might have some minor issues (i singles these out because they are not downgradable, of course you'll have issues if you don't match all other things).
you might have a chance fooling tel$tra by flashing the sbf i provided (stock 2.26.0) and restore the nandroid. it should be almost identical except you'll get busted when they try to do flash their service sbf.
the bottom line is,
1. if you flashed any sbf larger than 50MB it must have cg39 in it, and you can't downgrade.
2. you must use matching kernel/devtree with the system: the chinese ones will not be compatible with any other roms, you can't mix match froyo with eclair.
Thanks racca, it makes things a bit clearer. I didn't think I had flashed the GB rom, but I must have-it was 3 or 4 mths ago- it explains why I used the Higgsy fix...i think the China one came out very shortly after..
I should probably try flashing a 2.1 rom b4 restoring the telstra nano if I want stock-( with Telstra, we will have to wait until 3 mths + after the rest of the world gets Froyo for them to fill it to the brim with bloat ware..)..
It looks like the Higgsy fix didn't work for our devices anyway-i suspect my phone believes it is a 3.42 fw now.
In any case, I am relieved to have a way to flash the fixed sbf's now.. Barebones is very impressive, no hint of an issue, but need to run it for a week to really see.
Thanks.
I have a Telstra phone too and after a week of owning it back in January, I had already installed a 2.2 De-blurred ROM. I did have radio issues at first and also remember a non-stop reboot issue. I think it was the USB debugging somehow but I could be wrong.
Now I install new ROMs with ease when the need strikes me.
Are you able to flash the fixed sbfs for roms you install?
I've just put the CM7 rom on mine, best rom I've used. Also flashed a fixed rom with it.
Next thing i tried was restoring a nandroid backup of the default telstra rom, then flashed a fixed stock telstra sbf, this worked and was able to at least make the phone look like it was stock. Whether or not that would be enough if i had to send the phone in for repairs. Can only try if it needs to go in.
CM7 is by far the fastest rom I've tried. Only used for a day so far and no problems yet. Highly recommend this one.
Cheers
Sent from my MB525 using XDA App
I flashed the fixed sbf by renaming after restoring the telstra nano and it worked, but didn't run properly, I did it a couple of months ago with just the nano after having jboogies blurless ginger and it passed for warranty. Haven't tried renaming the full telstra sbf yet. I might over the long weekend.
Sent from my MB525 using XDA Premium App
That's what I was hoping, but for now I'm staying with cm7.
Will go back to the telstra one only if it needs warranty work.
Sent from my MB525 using XDA App
samorgs said:
That's what I was hoping, but for now I'm staying with cm7.
Will go back to the telstra one only if it needs warranty work.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
You'll be fine.
On a side note, it's ridiculous that Optus have official froyo already, Telstra due in July.
Sent from my MB525 using XDA Premium App
If you were impatient and flashed a leaked SBF like and still wants to get the official update, here is a shord guide for you. I examined the 6.36.0 sbf and the code groups for CG31 and CG39 are the same as the leaked froyos so i flashed it on my phone running CM7 and it booted After it i downloaded the OTA let it install and now i am on the official 2.2. I can change it with the CM7 anytime i want and if i have to take the phone to the service restore it to stock 2.2 So step by step
1. If you are on any leaked froyo download the latest us eclair sbf(JORDN_U3_6.36.0) from http://www.and-developers.com/sbf:defy
2. Boot into the stock recovery and wipe
3. Boot into the bootloader and install the SBF from point 1
4. Let the phone reboot then go throught the motorola blur registration then setup a wifi connection.
5. Download the OTA (settings->about) and if the download finished let it reboot and install the update.
6. Enjoy stock untouched 2.2 T mobile froyo
hi is this only for US people or will it work in UK as well?
It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App
Does it supports 720p video recording!!
vick33 said:
It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
What is the version number after the update?
Anyone can upload nandroid and sbf ?
It came out as OTA so no sbf available. Every version is the same as it was with the test update... it is android 2.2.1 34.4.9 they did not changed anything from the test update so i am not satisfied at all...
Sent from my MB525 using XDA App
Can i send in my defy for service with this rom?
Edit: I guess this rom is official. Read this thread. http://forum.xda-developers.com/showthread.php?t=1044980 .Cool stuff. Thanks for the heads up!
I tried flashing this and now my phone wont turn on i needed this so i can return it to T-Mobile with a stock ROM, but now my phone won't even turn on. Tried removing battery and putting back in, no matter how long i press the power button, it wont even turn on. help plz
On which rom were you before? Did you wiped before flashing the sbf? I have done it myself many times.
i was on CM7 and i wiped and flashed like u said. it might be my phone.
EDIT:
well nevermind, looks like the screen is fried. it seems to have flashed but the screen wont display anything cause when i plug it in to the computer, i hear the little beep and the LED notification appears, but no display.
you cant burn the screen like that. If it beeps then you are ok. You should try flashing the nordic sbf for example, fom it i have gone fortth and back to the us froyo the way i described.
so what should you do:
1remove your battery and while putting it back hold volume up.
2 start RSD lite and connact your phone
3 if it is connected flash the sbf.
If the PC does not sees the defy then your battery is flat. Charge it with an external or try mcgyver, you cant brick defy with flashing.
Will this work if you flashed the 2.2 OTA then used a custom froyo ROM. I basically want to take this phone back to stock.
I thought we couldn't downgrade.
Sent from my MB525 using Tapatalk
i was on nordic when i did the things i written. Got back the official now i have done it from other custom roms like CM7, but wipe in the stock recovery before trying it. I dont have any problem but seems like someone had so be careful.
I'll give it a shot because my nandroid restore is buggy.
Will post results.
Sent from my MB525 using Tapatalk
It would be interesting if it wont work for you. Cg-s for the us eclair are same as for the froyos
Sent from my MB525 using XDA App
Finally a way for US users to return to FULL STOCK regardless of firmware
It worked!!!
I was on barbones 1.5.1 then went to a backup nandroid version of my original stock rooted. Was kind of buggy so I decided to try this
1. Wiped everything using the stock recovery
2. Bootloader and flashed nordic 2.2.2 and "skipped" the automated setup until the phone desktop appeared then waited until RSD said the phone "passed".
3.Wiped everything using the stock recovery again
4. Bootloader and flashed 2.1 JORDN_U3_6.36.0 then pressed "start" at the motoblur screen and waited until RSD said the phone "passed".
5. I then entered my motoblur info and "skipped" everything until I was at the android desktop. After syncing was finished (waited about 5 min) I proceeded to "Download the OTA (settings->about->system updates) and after the download finishes let it reboot to install the update"
Thanks "vick33" nice find!
Note:
I could not update the kindle app without it giving me unsigned package errors. My solution was to root and uninstall the oem kindle app.
Then unroot and perform a factory reset. The oem kindle app did not restore and I was able to install the latest kindle without errors.
No other issues have been found.
*** CONFIRMERD TO WORK ***Another solution maybe to update the kindle app prior to updating the phone to 2.2 via OTA. Possible the better way to go considering it does not require rooting or removal of a system installed bloatware.
i mean the screen doesnt show anything. screen is black, idk whats wrong with it. im not saying the sbf had anything to do with it, just saying the screen went out. i just turned it in anyways, so ill be getting a new one soon.
Background. Was using 2.2 for the longest time, loved Firefly. Went ahead and bit the bullet and decided to go to 2.3 and use Gingerbread. Solid week of great success. However I started notcing my antenna saying no signal. Several Reboots and still nothing worked. Decided I would One-Click Back to 2.1 and start fresh. Well I never had issues with Odin 1 Click before, but now I get in a boot loop (ATT SPlash Screen) I have noticed when its unloading the package after , the last thing i see is CSC and that it boots into the loop. Would love to get my phone back to stock so i can see if its a hardware or software issue with my antenna. I have looked at this link, http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 but was afraid I possibly might still have GB bootloaders on my phone. I would think not if Odin finished, but I just want to double check with the community so I dont brick.
Thanks guys.
Can you get into DL mode? IF so, i would try and Odin again. ALthough I looked at the link in your OP, unless your heart is set on 2.1JH7, i would use the Odin3 one click downloader. That will restore your phone to 2.1JF6 as well as flash the correct bootloaders. I have gone back and forth from continuum to cm7 a few times now using that method.
Thanks for the quick reply. however this is the 3rd time trying Odin-1 Click tonight and I still end up in a boot loop. I have redownloaded the file just to make sure I didnt have a corrupt one. I just want a stock system and see if the constant antenna issues continue. (Trust me Ive tried different modems and all those possibilities.) Is it safe with that link? I noticed when i do Odin they flash a sbin and bootloader. I am assuming that puts it back on 2.1
which Odin are you using? Are you using the one click program that gives you stock firmware... JF6 firmware?
It is here:
http://www.megaupload.com/?d=SBSMALFJ
Yup thats what I have. It looks like it doesn't load the android system. Soon as it says installing Multi-CSC its done and rebooting. It would seem like its not unpacking the files. I have no status bar at the bottom. I have no idea why its doing this. Here is the crazy part. If i go back to the ginberbread stock, its not a problem to get to boot.
while I'm no expert.. seems like a bootloader thing. Try downloading it again from the link i put up and see if it was maybe a corrupted download.
The bootloaders are the first thing flashed in odin. It stopped after that then you have stock bootloaders. Also if all you see is the white AT&T screen and then it reboots, that indicates stock bootloaders as well. The gb bootloaders have a black galaxy s I9000 screen as the param.lfs image.
I would bet money you have stock bootloaders, use that link you posted that work be perfect. If you go back to gingerbread and want to return to stock bootloaders you'll have to use one click again even though you got a problem from it this time, if you get the same problem you know this worked to fix it.
And lastly usually problems with cell signal are modem related ... Which one were you using, did you even try another one? That would've been my first move instead of going all the way back to stock.
Hey studacris,
I have been using Mosaic (Love the work you guys do over there). I did try and use the other method to get back to Stock Last night and it did the same thing. Just a bootloop. If its plugged into the USB cable it goes directly to the Battery Symbol, if its not the Att 3G bars loop. I can flash to Gingerbread stock and then apply Other Roms. I tried GR-2 and Mosaic again, but still nothing with the signals. I just dont like the fact I cant get back to Stock with those 2 different methods. What I think is odd is when I load Gingerbread, it seems like items are being unpacked and loaded. When i try to go to Stock, everything happens super quick, making me believe nothing ever gets installed on the Internal Card during the unpacking sequence. I am no pro, but thats just something i noticed. Here was my original post on the Mosaic board. http://forum.xda-developers.com/showthread.php?p=14043766&highlight=Rizz67#post14043766
So I posted about 2 months ago with no reply hopefully I get a response this time. When I originally posted I was having trouble sbfing my D2G. I have the correct sbf file for it. I was on ICS sbfing the GB firmware back so I could install CM7. But after I finished flashing I still had the ics boot anim. And I was stuck in boot loop. I've tried using all different versions of RSD lite aswell. So today I had a R2D2 that I was doing the same thing on. This time when I sbfed the boot anim. was changeing based on the different sbf files I used (r2d2 and d2). (Yes I'm aware the d2g and d2 have different files.) I've tried them all though from froyo to GB and the A9557 R2D2 sbf. They all put me in boot loop and now both of my d2's are bricked. RSD Gets done and wants me to manually power up the phone while its looping. I boot back to boot loader and it gives me a pass. Even though it loops. I've also tried it on XP and win. 7. How in the world can I get my phones back to working order. Help help help
Sent from my NookColor using xda app-developers app
Did you try google? You tube? Moto forum? ACS ?
Pp.
Sent from my ginger infused Mayan calculator.