Hi all, I would like to say hello to begin with. I don't remember if I've posted here before or not. I have a question regarding my smartphone insurance if any of you would know anything about it. See, I rooted my phone long ago. I flashed and restored nandroid backups as I worked my way through my path of enlightenment (so to speak) in custom ROMs. Anywho, I am a proud owner of a Motorola Droid X (1st gen), and I recently flashed the Revnumbers unofficial CM7 build on my phone. Everything was great until my com.android.phone process force closed on me every time I tried to place a phone call and also force closed on me upon a fresh boot. I came to find out upon further research that it was due to a problem with the power control widget when switching from 2G/3G, and that running some SQLite commands in a terminal emulator would fix the problem by switching the preferred network value in a database file. I don't know what I did, but I made a nandroid backup after the problem occured, and the force close went away after I restored it. Now it's back, and I'm at my wit's end with this damn thing and I have decided I'm gonna pay the deductible on my insurance and get me a new X. I was wondering if the root status on my phone (as well as the com.android.phone FC) would eliminate my chances of getting a new phone. I know I could just run it over with my car, but I just can't bring myself to do that. Any help would be greatly appreciated.
P.S. I found out that other X users were having the same problem, not just with CM7, but with all 2nd int ROMs.
I really don't mean to post this in the wrong section if I did. I have had enough of this pos DX and I'm definitely thinking about buying my friend's very lightly used Bionic for $120.
Not sure what the insurance policy is like that you have, but if you've done anything at all (custom ROM, custom Kernel, rooting etc.) then that normally means you're not covered. You'd need to go back to 100% stock to be on the safe side, which would probably also fix your problem.
If you've got the option of a Bionic for $120 then that's a tempting offer. I'm certainly no Motorola fan and would advise other, better phones, but $120 is a good price for that, assuming it's in good condition.
Archer said:
Not sure what the insurance policy is like that you have, but if you've done anything at all (custom ROM, custom Kernel, rooting etc.) then that normally means you're not covered. You'd need to go back to 100% stock to be on the safe side, which would probably also fix your problem.
If you've got the option of a Bionic for $120 then that's a tempting offer. I'm certainly no Motorola fan and would advise other, better phones, but $120 is a good price for that, assuming it's in good condition.
Click to expand...
Click to collapse
Well, I researched my problem when it occured, and a lot of threads on various forums such as Rootzwiki, and a device-specific forum were present with people having the exact same problem. They said it occured on all 2nd-int ROMs, and they took measures such as reflashing, wiping the data and factory resetting, even SBFing back to stock, still to no avail. It seems that once the preferred network mode value is altered, it stays that way regardless of reflashing or SBFing back to stock. I think I know what the actual problem is, but I don't know how to edit the database files myself. One of the threads on Rootzwiki said that the db file under something like android.providers.settings has a db value that is named as "preferred_network_mode" iirc, and that changing the value with an app called sqlite would fix it. I did not find such an app, and with the SQLeditor I tried out, I could not find the preferred_network_mode even searching that exact phrase, character for character. If I can fix this DX, I would love to continue on with it, but if it's too much trouble, I may just bite the bullet and pay the deductible to get a new phone. My mom thinks I shouldn't root or flash because it voids the warranty, but I didn't think that the insurance providers cared about software. I guess I'll just have to run it over with my car or something if I can't fix the problem. It's so bad that I can't even place or receive calls. That's the one thing for which I absolutely need to use my phone.
Related
i was sitting here on XDA and i saw that a user here had his phone stolen from him, and people posted several solutions like GPSTracker and latitude but the user did not have either installed. would anyone be interested in a remote brick? basically it would be like SMS commander, but you send a text that holds a password and the correct brick phrase and the phone will brick. the best(and worst) way i can see to do this would be to have an old radio on the sdcard and have the haykuro SPL on there as well. then when the phone receives the text it flashes the old radio and then the haykuro SPL which we all know would brick the phone. i am still working on possible implementation or another way of doing this(maybe run "wipe all" in terminal), but i was just wondering if anyone would be interested before i really try it out.
maybe in future if app works well our ROM devs could include in their build and then it couldn't be removed(easily). the main reason i would want something like this is so if my phone was stolen i could make it useless to the idiot that stole it.
few minor details that would need to be worked out:
won't work if SIM is changed as number would be different
if i use the terminal command "wipe all" then theif would only need to have a new ROM to install and it would be all better
on the of chance you get the phone back you would want to be able to easily fix the phone
let me know what you think, keep in mind this is a very early stage idea and i haven't put more than 20 minutes thought into it
cant lie the idea is brilliant but execution would be the make or break point, and i have a feelin this will take alot of test g1's to get working lol...and multiple devs as a team to get up off the ground. But im all for it, i have had bad luck in the past especially with sidekicks and etc and this would be a perfect idea to have.
Great idea but don't forget when restoring it (if you manage to retrieve your phone), it should only 'unlock' to a certain pass phrase pre-set by the user. If not anyone could just run the 'unlock' command to start using it again.
On the whole, a great idea.
However, I think flashing an incompatible theme with your current build would be sufficient, seeing as 99% of the people who go around stealing phones would have no idea how to fix a G1 stuck on the T-Mo/Not-Flashing-Android Screen.
Although the Old Radio+New SPL combo ensures that there will be minimal data retrieval, it also seems like overkill for the majority of circumstances, seeing as your phone would become a paperweight.
The terminal command "wipe all" will wipe the data and system partitions and crash the phone, when the person who stole it tries to reboot it it won't boot
Even if you wipe (or remove the SD card) most builds would still boot regardless. A remote kill switch has been around on many platforms for some time, hell even Microsoft have been threatening to use it on Vista for pirated builds but it has never happened.
In this case, perhaps the app would need root access, so it could remotely reboot the G1 and run a script to force a boot loop, if you wanted to go as far as rendering the mobile temp unusable.
However the G1 as it is has plenty of security flaws... I mean many of us managed to get root without issue and I'm sure any google searches will point them to this forum. There is no security for fastboot, nor accessing the recovery image so people can pretty much do as they please - If they know how.
Yeah, I don't know about bricking the phone because it would suck if eventually you did get it back. Then you're stuck with a brick phone maybe theres away around it though which could work not sure how you'd implement this though. I mean the idea is there just going to be abit hard to execute because the problem is with all these theft problems, if they have the phone off when the sms is sent then it doesn't work.
I wouldn't mind having this. If someone snatched my G1 out of my hands and got away, I would just use my friend's cell 1 minute later to make my phone a paper weight, then have peace of mind. lol
Dladu said:
Yeah, I don't know about bricking the phone because it would suck if eventually you did get it back. Then you're stuck with a brick phone maybe theres away around it though which could work not sure how you'd implement this though. I mean the idea is there just going to be abit hard to execute because the problem is with all these theft problems, if they have the phone off when the sms is sent then it doesn't work.
Click to expand...
Click to collapse
i am noting the issues, what i am planning is something similar to SMS commander, when the phone gets a text that says a certain thing it does something. if the phone is off then the text will still arrive when the phone is powered on, hell i could probably even remove the recovery screen and then the person would need to fastboot the phone.
sms commander just "listens" for the text of an incoming message and if it matches a certain phrase it runs a command. obviously i would need root, but at this point if you haven't rooted your phone this(if it works) woulud do it.
with that said, i am researching the APIs to see what would need to be done, i used to have something like this on my old 8525 and i never had to use it, but i'm paranoid about stuff like this
i love this idea, there was this time when i had sold my touch pro on craigslist but the buyer had ripped me off! so that just pissed me off!
(good name ideas)
Cold-Droid
Lock Me
Ban-Droid
Dream Lock
Use me...Not!
Where's My owner
or just a plain app called
"Brick"
This app would be cool if it detected the owners sim card so if it were ever replaced it would say wrong sim card enter passkey (which they will not know)
and if they were to ever put the sim card back in then still it will tell you(sim card has been removed please eneter passkey)
or something like that! just an idea!
kind of like sim lock but instead of sim being locked, the device will be locked!
Why you would want to destroy a phone?
Just remote wipe your data, thats enough. Write that as an app!
Not bricking!
Have you guys used/considered Mobile Defense?
So here is my idea for this application.
Instead of completely bricking the phone, make it so that if the SIM card is removed, or the secret SMS message is sent that it does a complete phone lock and displays a message on-screen stating "This phone is suspected to have been lost/stolen. Please call XXX number to return the property.". All the while sending precise GPS locations updated every x minutes to a preset Email address and/or send a SMS to a preset phone number. This way the real owner may be able to easily recover the phone and none of the information is exposed. The only way to unlock it is to put in a code to unlock it. After x amount of days without being recovered, the program will issue a recoverable brick all the while showing the same message. After x more days after the soft brick, the phone will format all ROM and be unrecoverable. By that time, the real owner would have already gotten his/her replacement G1 if they had insurance, and the thief will have a fancy paperweight.
Great idea
Is this going to get anywhere?
that'd be funny if you could lock the phone at a screen that has a customized text.
Like F**K YOU B*TICH
or maybe
If Found Contact -
ETC. and it just stays at that screen. wonder if thats possible
edit- i shoulda read page 2 haha. same idea as Setnev lol.
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts
So, I have successfully bricked my phone (not by choice). I am a long time WinMo user and I have never even come close to bricking a phone. Today was exactly one week from when I bought my first android phone and I bricked it.(not blaming android, I love android)
I have tried EVERYTHING, to no avail.
My phone is on the phone++!++computer screen.
So, first thing tomorrow morning, I am headed to the AT&T store for replacement (I will act dumb and get the phone).
My questions are -
1.Will my information (contacts,emails,etc.) on the phone be checked or in any way violated?
2.If they do find out that I had rooted the phone, after I have already walked out of the store, can they do anything about it?
1: Yes, the contacts and all other data on the phone itself is still there, and will all still be there when Samsung / AT&T *un-bricks* the phone.
2: They "could", but I am not knowledgable enough to know if they "will".
Or, save yourself the hassle, and the negative moral karma, and read here:
forum.xda-developers.com/showthread.php?t=731989
I've intentionally (with much failure), tried to "break" the phone so that I'd know how to fix it.
The above linked post will not only recover you from your "phone++!++computer" issue, but actually works so far as the dreaded "orange hex dump".
TehDave said:
1: Yes, the contacts and all other data on the phone itself is still there, and will all still be there when Samsung / AT&T *un-bricks* the phone.
2: They "could", but I am not knowledgable enough to know if they "will".
Or, save yourself the hassle, and the negative moral karma, and read here:
forum.xda-developers.com/showthread.php?t=731989
I've intentionally (with much failure), tried to "break" the phone so that I'd know how to fix it.
The above linked post will not only recover you from your "phone++!++computer" issue, but actually works so far as the dreaded "orange hex dump".
Click to expand...
Click to collapse
I have tried everything. I don't want to return this phone, but there is no option left.
None of the methods work and I am pretty experienced in this stuff. So, its not that I am messing up on the methods, its just that there was a batch of phones that had the key combos disabled.
Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.
ukulele_ninja said:
Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.
Click to expand...
Click to collapse
I can tell you that by flashing ONLY the pit file in odin another user and myself were able to succesfully make the phone unresponsive to all buttons, all methods and all pulls of the battery. it literally turned into a brick...then again i would call this an illegitimate method after realized how simple it is now. as long as i can get power to the phone thou i have to agree ive been able to save it every time now
ukulele_ninja said:
Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.
Click to expand...
Click to collapse
Seriously?
I was up for six hours last night trying to fix the damn thing. I don't want to replace the phone just because I want to beat the system. I have never ran into problems when I am modding. I always figure it out, but when the phone is absolutely unresponsive to all keys, what am I going to do?
Anyways, this thread can be closed now.
That same screen (http://img228.imageshack.us/img228/8420/hum1e0.jpg) happened to me yesterday. I thought I had tried all of the key combos but I missed one.
Try the following: (I know you said you tried all of the methods, but I thought it was worth mentioning just in case)
http://forum.xda-developers.com/showthread.php?t=731989 (Method 3)
I hope if you have not tried that yet, that it will work for you and save you the hassle of going to ATT.
Alec5216
seems pretty complicated to flash this phone. My last one-Nokia N900- is very easy to work with. It never get bricked.
alec5216 said:
That same screen (http://img228.imageshack.us/img228/8420/hum1e0.jpg) happened to me yesterday. I thought I had tried all of the key combos but I missed one.
Try the following: (I know you said you tried all of the methods, but I thought it was worth mentioning just in case)
http://forum.xda-developers.com/showthread.php?t=731989 (Method 3)
I hope if you have not tried that yet, that it will work for you and save you the hassle of going to ATT.
Alec5216
Click to expand...
Click to collapse
I tried that too, nothing. I got it exchanged. No hassle.
AT&T store rep just said the phone will be factory reset and there is nothing to it.
Anyway thanks for the help folks, really appreciate it.
Lets hope, I don't bust this one because the phone I just got is also impervious to key combos. I tried getting into recovery (just for the heck of it), it didnt work with the keys, had to do it with "adb reboot recovery".
First of all running stock Droid 3 Rooted Flashed to cricket
with all the fixin's, Bootstrap, CMW, ... etc....
:edit ... Now with safestrap.
_________________________________________
I noticed after taking my phone out of my pocket while trying to turn it on from normal off screen while on that it wouldn't show up the light still indicated it was working I can even turn off the phone.
Taking the battery out and back in semi fixed this but only to the extent where when the phone is turned on the moto logo doesn't appear but the droid eye does.
whence at the booted screen if I were to let it go black it has a chance to not stay on unless I RIGHT after it boots unlock it and keep it lit,
(but)
the main problem I noticed was it really only did this after lets say I was typing or doing anything with the qwerty board open and perhaps I let the screen turn off after a minute,
when I try to wake it up it stays black. EVERY TIME like most of the time,
it has to do with the keyboard being open when the screen goes to sleep.
WHAT IS WRONG *pulls hair out*
_________________________________
I can't say when but I've looked everywhere
tried uninstalling every app but the essentials,
then restoring to my first restore which was after my first initial root.
Tried factory reset,
Tried flashing back to stock,
yeah I think this counts for as much as I've gone insane looking for an answer for.
I have been told this sounded like a software issue so all I'd need to do is re install like I did when flashing back to stock THIS MORNING.
____________________________________________________
I need help to identify somehow if this IS or IS NOT a software/hardware problem.
and an answer to help me fix this would be nice as well thank you.
I know I am supposed to be brief but putting in all that into google and into every forum I have delved just isn't going to put it the way it needs to be said.
______________________________________________________
______________________________________________________
Edit:
Ok so far since no one has said anything I have also reinstalled my old newest state, still giving me crap.
Then just did the newest update 5.7 blah and still it's happening.
I hypothesize it might be the flex ribbon cable maybe (but it really might not) I read from another phone it might be a capacitor but it might not.
Whatever is wrong the phone still is able to at times now 40/60% of the time work properly and wake normal but then again not.
__________________________________________
Right as of now I have put isc to see if this helps .......... .... to be continued or helped.
I'm back, well ics installed fine after the second time made it boot loop over and over.
-----------------------------------------------------------------------
I can receive calls now
but
no sms, mms, or internet.
(even though the network status settings are blank it's weird I can still receive calls, and send calls.)
since you can't restore the apn's with 3rd party I now have this NEW issue.
the phone goes unresponsive within cdma workshop and ##Program does not work.
I'd like some help in finding out now how to if it is possible yet to properly flash to cricket and or just change my apns and get into cdma as well as QPST.
__________________________________________
PLEASE I NEED HELP thank you
-3nJo1
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Thanks
necromanteion said:
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Click to expand...
Click to collapse
Thanks for your input.
(verizon wouldn't replace it since I baught it from someone else (legit) and I don't have verizon.
UNLESS you think if I had the previous owner take it into the store could they replace it? what steps would they take to see if it was rooted?
_______________________
I never unrooted it when I did allll of this
Do you think rerooting is soumething that I should have done before doing this?
Or most likely is this a flex ribbon cable thing ....
I just tried the diagnostic (leave keyboard open then turn the screen off and on thing)
it came on at least 3 times normal then it didn't either right after the 3rd try or upon closing the qwerty board ...
also do you have an answer at all for the ics portion of my problem?
THANK YOU
___________________________________________________________
EDIT!!!!!!!! Actually realized I did reroot after the sbf ota flash .....
so all things aside yehs I also did that any other solutions inquiries ...
ANYONE ELSE PLEASE HELP!
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
stud beefpile said:
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
Click to expand...
Click to collapse
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
I bought my d3 off craigslist and the power button and n key weren't always working. I took it in to Verizon and had a new one in the mail 3 days later!
Sent from my XT862 using XDA App
Sorry didn't read the part about you being on cricket. Maybe you could make friends with someone that has d3 on verizon have them activate it and take it in for you.
3nJo1 said:
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
Click to expand...
Click to collapse
I believe there is another apn type tool that the Cricket Android tools are using for their specific settings. You may have to search XDA a bit to see if anything shows up for othere phones on Cricket.
Sent from my DROID3 using XDA App
I am wondering how stop an update on a Droid Bionic?
I understand you need to "move the update from /cache to your SD card" once downloaded.
However, I do not know where "/cache" is located, how it is accessed, or how the moving process is done.
I connected my phone to a PC via USB and could not find "/cache" stored on the phone. The only thing close was a cache folder within "com.google.android.apps.maps", which doesn't seem like what I'm supposed to be looking for. I've also tried looking in Menu>Settings>Storage but do not see any 'cache' info.
I've been searching the forums but have had no luck; plenty of references to a 'cache' from
people who clearly know what they are talking about, but I can not find any explanations or instructions.
Any help is appreciated. This is my first Android device btw! (though I've been reading this forum for a week or two now)
Wow, you're wanting to stop .905 while most people are chomping at the bit to get 6.7.xxx. You can't do it with your PC, you will need to do it from your phone with a file manager app.
I think you need to be rooted to see the cache'. you will also need a root file manager like "root explorer" to move the update to your SD Card.
ICS is much much better than the GB OS. I would reconsider the update, better things are coming around the corner.
If you choose to stay at .902, I would suggest doing some reading about the rooting process. Bad things can happen if you haven't done some research.
There are many here that will be glad to help you, but you will need to be a little knowledgeable to "help them, help you"
root .902
http://www.droidforums.net/forum/droid-bionic-hacks/198045-902-root-method.html
advanced root and play with leaks and return (well written, read 1st post several times,) also has links to current drivers
SamuriHL spends his life supporting that thread and spends too much time helping others
http://www.droidforums.net/forum/droid-bionic-hacks/214902-downgrade-902-no-app-data-loss.html
I'm not sure if I helped or confused, mainly just want you to be aware
greeneink said:
Wow, you're wanting to stop .905 while most people are chomping at the bit to get 6.7.xxx. You can't do it with your PC, you will need to do it from your phone with a file manager app.
I think you need to be rooted to see the cache'. you will also need a root file manager like "root explorer" to move the update to your SD Card.
ICS is much much better than the GB OS. I would reconsider the update, better things are coming around the corner.
If you choose to stay at .902, I would suggest doing some reading about the rooting process. Bad things can happen if you haven't done some research.
There are many here that will be glad to help you, but you will need to be a little knowledgeable to "help them, help you"
Click to expand...
Click to collapse
thanks; that's really what I needed, a point in the right direction. I confess it's a bit new to me. I just got this phone, programmed it using steps found here (great forum!), and activated it on pageplus, but this was the first time I just got 'stuck' on something.
I read that 3G worked much better with 902 than with 905. this is why I was thinking of sticking with 902, at least until a legit/finalized version of ICS gets released (which allegedly, is very soon...maybe). Since I don't know much about the OS yet I figured I could survive the wait without 'knowing what I'm missing' so to speak.
whoa, just googled and saw that a new leak is out. I picked an odd time to be a newb working on a Bionic.
Thanks again!
If you do take the plunge into a leak, you should probably stick to one where FXZ to 902 isn't blocked so you can return to stock if needed. Everything 235 and after is poison, so to speak, and you won't be able to go back, which (thanks Moto) makes it really difficult to go forward (thanks Moto). I'm on 232 and I'm happy as a clam. It's stable and doesn't have many issues. Now when the official update comes out, they should release an FXZ and we'll be safe again and can all take the dive into ICS.
so, I realized you could postpone the update by just not accepting it when the prompt comes up.
so, I use my Bionic for a while and am quite happy. Then today, I noticed I no longer had 3G service. I tried restarting it, removing the battery,
toggling some of the data changes, no luck. I figured since ICS is (allegedly) right around the corner, there was really no reason not to go ahead and update.
I ran the update. I now have no phone service, no texting, and no 3G/1x.
My question is: how far in the process do I need to go back to get things running again? Right now what I have is a blinking white triangle in the notifications bar. My phone is stock in every way.
Edit: in "about phone/status" I have no phone number (it's blank). no MIN, no network. My PRL version is 'unknown'. so, basically I think I need to just start over, using the info I used successfully before (adam3rd is my hero), beginning with flashing a pageplus PRL. but I shouldn't need to reactivate it on pageplus, or need a new sim card, right? I feel like whatever happened wouldn't have effected my status with PP or the sim card, but I can't find a clear answer....any help appreciated
The white triangle is your phone searching for a signal to activate itself. Take your sim card out and re-insert it. you may need to wipe the dirt off the gold metallic area
greeneink said:
The white triangle is your phone searching for a signal to activate itself. Take your sim card out and re-insert it. you may need to wipe the dirt off the gold metallic area
Click to expand...
Click to collapse
thanks for the response. I actually had 4 bars of signal strength along with the white triangle. I'd assumed this meant I could 'detect' the verizon/PP network but wouldn't be able to get out of 'roaming' status until it was activated for the network.
I actually contacted PP via chat to reactivate it. they did it, but the problem wasn't resolved so I tried a factory reset. boom, activation screen came up! now I have fone and text again.
my real problem now is getting data to work consistently. gonna wait until the legit ICS comes out before tackling that one again.
You're going to love .246
no signal drops, fast reaction on apps. it's truly a who;e new phone experience
greeneink said:
You're going to love .246
no signal drops, fast reaction on apps. it's truly a who;e new phone experience
Click to expand...
Click to collapse
yes, I'm very excited. a little paranoid about updating since I'm on PagePlus and haven't seen anyone use Pageplus and .246 yet. but I may just try using the info on howardforums; I know it 'should' work, but that's just not the same as confirmation.
on a side note; I believe I may have discovered what my data problem was; I think I'd just disabled the 'connect with data over mobile network' option and forgotten I'd done so a month later. pretty funny. but it's been a good learning experience, heh