I read the wiki but it only tells you "Why you should" root your phone. Obviously Google removed root from the latest firmware for a reason. If its for security reasons, how can you be "safe" with a rooted phone? Can you still download paid apps from the App store with a rooted phone? How well does the Apps on the SD card work? The main reason I would want to root my phone is for the SD card app feature. The G1 space sucks ass and its constantly telling me I am low on space.
When you root your phone, it automatically installs an app called "SuperUser" (assuming you're using one of JesusFreke's builds). SuperUser allows you to control which applications have root privileges.
Also, Google probably removed root because of stuff like the fact that it enables you to copy protected apps and the like... and even if they didn't know at the time, they probably knew that it would happen
Superuser protects your phone by allowing programs you give permission to that use root. I can still see paid apps in the Market (I haven't bought any yet, but I will). I didn't move my apps onto my SD card because Paragon Partition Manager froze during the partitioning and I had to reinstall Vista .
The only con is that you have to wait for JF's updates
I believe I also read here that rooting your phone voids your warrenty, so if you have a problem with it make sure you switch back to the official firmware before sending it in
androidmonkey said:
I read the wiki but it only tells you "Why you should" root your phone. Obviously Google removed root from the latest firmware for a reason. If its for security reasons, how can you be "safe" with a rooted phone? Can you still download paid apps from the App store with a rooted phone? How well does the Apps on the SD card work? The main reason I would want to root my phone is for the SD card app feature. The G1 space sucks ass and its constantly telling me I am low on space.
Click to expand...
Click to collapse
I'll try to answer your questions the best I can:
-I don't work for Google so be advised this IS pure speculation on my part. With that said, I think they removed root access for the masses to avoid the possibility of folks having their Android handsets compromised by malicious apps.
Though, having root doesn't necessarily mean this WILL happen to you.
So long as you have common sense, and know better to install apps from questionable sources, you'll be fine. Additionally, the JesusFreke firmwares have a "SuperUser Whitelist" app that will ask for escalated privileges whenever a process requires root.
This is provided as another layer of security.
So to say it again, do not allow apps/processes to run unless you KNOW EXACTLY WHAT THEY DO. Follow that and you won't have any problems.
-Market apps can be installed and used without issue. I have dozens apps installed (and yes, a few paid apps as well) and have had ZERO issues with them. Matter of fact, if you look through the market, you'll see several cool apps that require root (Task Manager, WiFi Tether, etc).
-Far as installing and running apps from the sdcard, I'll defer to someone else because I haven't done it myself. I prefer to wait until an easier, or official method becomes available. Though, I have moved the various caches (Web, Maps, Market, etc) to the sdcard without issue.
That helps to conserve space with the internal memory.
Hopefully that helps you.
Thanks for all the replies. So is it safe to say that if I only install apps from the Android Market I should be safe? Can programs on the Android Market be malicious? Hopefully Google is monitoring the applications for malicious code.
So, what is the "best" guide to use for rooting a RC33 phone?
programs on the market could possibly be malicious, read reviews, i found a game that said it needed the internet, gps, and some other stuff in order to work, but yet the app never used any of those features in the actual gameplay, thus i removed it and reported it as malicious because i frankly don't feel that it should need access to things it isn't gonna use. a general rule is that if a single person said it was malicious then don't install it, and never be the first to install an app. let someone else break their phone first
The only con for rooting your phone is that people who don't know any better usually end up bricking it. "oooh root yay! i don't know what it duz bat it sounds cool! oh no! i brcked it halp plz"
And you can still unbrick your phone pretty easily.
IzzeLing said:
The only con for rooting your phone is that people who don't know any better usually end up bricking it. "oooh root yay! i don't know what it duz bat it sounds cool! oh no! i brcked it halp plz"
Click to expand...
Click to collapse
lol, your quote can be used on a LOL Cat.
i wouldnt say that waiting for the updates is technically waiting, when you have a rooted phone...
at least for me, i must have been on the bottom of t-mobile's randomized IMEI list when it came to updates.. I used to see people all around me have updates for weeks before me. Coincidentally i was the first to have mine... but the updates are released right from the google site, plus the wait time for JF and others to work their magic.
cant complain with a rooted phone, if anyone is skeptical about it... you CAN reverse the process
the.snks said:
-Far as installing and running apps from the sdcard, I'll defer to someone else because I haven't done it myself. I prefer to wait until an easier, or official method becomes available. Though, I have moved the various caches (Web, Maps, Market, etc) to the sdcard without issue.
Click to expand...
Click to collapse
I've moved my apps and caches to the sdcard and now I never have to worry about running low on space.
I followed one of the tutorials about moving the apps, but when paid apps came out, I had some problems. The solution was to move not only the "app" directory but also the "app-private" directory to the sdcard. Once I did that, everything was fine. I am able to install both free and paid apps with no problems. I'm very glad I did it -- no regrets.
I have an 8gb sdcard and I partitioned 1gb to apps and caches (ext2 format) and 7gb to data (fat32 format).
unknown.soul said:
Superuser protects your phone by allowing programs you give permission to that use root. I can still see paid apps in the Market (I haven't bought any yet, but I will). I didn't move my apps onto my SD card because Paragon Partition Manager froze during the partitioning and I had to reinstall Vista .
The only con is that you have to wait for JF's updates
Click to expand...
Click to collapse
Rooting may be safe to people like you all, but rooting is definitely the downside of android. Sd card blank and file recognition errors are the opposition to what android has made. I will not root my phone again because of the unexpected long term damage this has caused to my phone. I will tell my friends not to root their phone unless they want to turn their android to ruins. These kind of problems happen for absolutely no reason at all.
ri123 said:
Rooting may be safe to people like you all, but rooting is definitely the downside of android. Sd card blank and file recognition errors are the opposition to what android has made. I will not root my phone again because of the unexpected long term damage this has caused to my phone. I will tell my friends not to root their phone unless they want to turn their android to ruins. These kind of problems happen for absolutely no reason at all.
Click to expand...
Click to collapse
I disagree with the statement "downside". Android is about open source and customization. The downside to root is that you need to spend a bit of extra time playing with your phone when it doesn't end up going the way you planned or there are bugs in a new Rom. Other than the extra time on the phone, I have not run into a downside. I have not looked back since I rooted.
Sent from my Kang Banged Dinc2
ri123 said:
Rooting may be safe to people like you all, but rooting is definitely the downside of android. Sd card blank and file recognition errors are the opposition to what android has made. I will not root my phone again because of the unexpected long term damage this has caused to my phone. I will tell my friends not to root their phone unless they want to turn their android to ruins. These kind of problems happen for absolutely no reason at all.
Click to expand...
Click to collapse
I 100% disagree with this statment. having a rooted phone in itself will not cause any errors. even the process of rooting won't brick a phone or cause problems (so long as you understand what you are doing). although there is the way out in right field chance of something going even if everything is done right (very hard to brick a phone if you truley know what you are doing and are sober at the time)
android has always been and (hopefully) always will be open source. the android code it self in pure aosp is in fact rooted. it is the carriers and cell phone makers and such that lock the bootloader and deny privalage. as any linux user knows it is easily possible to damage you phone/pc/etc if you don't know what you are doing, but having root privalage in itself causes no harm - only to the novice.
this stament of unexpected long term damaged caused by root is false, it was caused by someone not knowing what they were doing and shouldn't have root privalages in the first place.
*excuse my spelling errors as rooting a phone doesn't improve my gramar/spelling*
Sent from my HTC Vision using xda premium
demkantor said:
I 100% disagree with this statment. having a rooted phone in itself will not cause any errors. even the process of rooting won't brick a phone or cause problems (so long as you understand what you are doing). although there is the way out in right field chance of something going even if everything is done right (very hard to brick a phone if you truley know what you are doing and are sober at the time)
android has always been and (hopefully) always will be open source. the android code it self in pure aosp is in fact rooted. it is the carriers and cell phone makers and such that lock the bootloader and deny privalage. as any linux user knows it is easily possible to damage you phone/pc/etc if you don't know what you are doing, but having root privalage in itself causes no harm - only to the novice.
this stament of unexpected long term damaged caused by root is false, it was caused by someone not knowing what they were doing and shouldn't have root privalages in the first place.
*excuse my spelling errors as rooting a phone doesn't improve my gramar/spelling*
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
To prevent factory reset bricking I had to move to a different Rom. I knew what I was doing. I returned to stock Rom and factory reset, and every zip I downloaded from my computer could not be recognised properly by my phone.
I know that android is based on pure root, but who should I blame if something goes wrong with my phone? Every rooted phone becomes faulty, why should I pay extra just because I can't download anymore roms?
Think about the random percentage of people that have had their phones bricked just because of rooting problems. I am one of them.
Your statement "only to the novice" is something I disagree with.
I remember when I read a thread about someone's Samsung Vibrant getting hard bricked all of a sudden! Or when I read a Sony Ericsson touchscreen refusing to work after light debugging. These people will most likely be paying for their android phones.
In a way, I do not completely disagree with you. In a way I believe that Android should start believing in its roots.
For the moment, I do not know who to blame for the mess my phone is in. I didn't do things wrong on purpose. So maybe it is better not to root. Maybe it is more advisable to complain to the creator of your phone if there is not "enough", or if there is too much bloatware. Maybe Android should be fixing my HTC! I need to stop all this unnecessary refusal from happening on my android. This is why I find the essence of rooting initially bad. When there is no limits, something can go wrong.
Please may I let you know that my touchscreen is mostly unresponsive. I will be surprised if I have got all of my spelling correct! If I still had the advantage of the warranty, I would be sending my phone straight to HTC to get repaired.
Sent from an unusually unresponsive touchscreen on my HTC Explorer A310e using xda app-developers app
ri123 said:
To prevent factory reset bricking I had to move to a different Rom. I knew what I was doing. I returned to stock Rom and factory reset, and every zip I downloaded from my computer could not be recognised properly by my phone.
I know that android is based on pure root, but who should I blame if something goes wrong with my phone? Every rooted phone becomes faulty, why should I pay extra just because I can't download anymore roms?
Think about the random percentage of people that have had their phones bricked just because of rooting problems. I am one of them.
I remember when I read a thread about someone's Samsung Vibrant getting hard bricked all of a sudden! Or when I read a Sony Ericsson touchscreen refusing to work after light debugging.
In a way, I do not completely disagree with you. In a way I believe that Android should start believing in its roots.
For the moment, I do not know who to blame for the mess my phone is in. I didn't do things wrong on purpose. So maybe it is better not to root. Maybe it is more advisable to complain to the creator of your phone if there is not "enough", or if there is too much bloatware. Maybe Android should be fixing my HTC! I need to stop all this unnecessary refusal from happening on my android. This is why I find the essence of rooting initially bad. When there is no limits, something can go wrong.
Sent from an unusually unresponsive touchscreen on my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
I'm not trying to sound rude here but the only blame is to ones self if YOU screw up your phone.
yes you can blame a phone company when the hardware fails from normal use, or your cell phone carrier for adding useless apps. or well blame android for creating an operating system that at its heart allows one to have full access to every part of it.
android doesn't write the radio, android doesn't write the bootloader, they are not firmware or hardware only os. they also are not responsible for a bad rom.
I will say again the act of rooting your phone in itself causes no damage, only when you do something wrong during this process is it possible to brick your phone, and as for the percentage of people who did brick there phone 99.99% of them messed up, that means their own fault.
.01% had a major power surge while phone was updating via fastboot and their computer only coppied a portion of the firmware to the phone and then the dog kicked over the phone knooking the battery out leaving no bootoader... or whatever, it is hard to do this wrong
and again having a rooted phone will intself not brake hardware, not damage firmware, will not cause a single issue
the missue of having root, or the improper method of obtaining root is the only problem, and people who don't know what they are doing (fully understand) well just shouldn't root, or should learn to except blame at the very least...
done with my ranting, good day...
Sent from my HTC Vision using xda premium
demkantor said:
I'm not trying to sound rude here but the only blame is to ones self if YOU screw up your phone.
yes you can blame a phone company when the hardware fails from normal use, or your cell phone carrier for adding useless apps. or well blame android for creating an operating system that at its heart allows one to have full access to every part of it.
android doesn't write the radio, android doesn't write the bootloader, they are not firmware or hardware only os. they also are not responsible for a bad rom.
I will say again the act of rooting your phone in itself causes no damage, only when you do something wrong during this process is it possible to brick your phone, and as for the percentage of people who did brick there phone 99.99% of them messed up, that means their own fault.
.01% had a major power surge while phone was updating via fastboot and their computer only coppied a portion of the firmware to the phone and then the dog kicked over the phone knooking the battery out leaving no bootoader... or whatever, it is hard to do this wrong
and again having a rooted phone will intself not brake hardware, not damage firmware, will not cause a single issue
the missue of having root, or the improper method of obtaining root is the only problem, and people who don't know what they are doing (fully understand) well just shouldn't root, or should learn to except blame at the very least...
done with my ranting, good day...
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
As I have said,one of the problems with rooting is that people have to move off their Rom in case of factory reset bricking.
0.1% have got the limited service error or the bad zip file error with their phone practically in a trap.
Much more than 0.1% have the sdcard blank error
I understand root enough to install roms and unroot my phone.
I did not do this on purpose, I just installed stock Rom and factory reset and my phone did not work as it intended to.
This is why I shall, in the future, ACCEPT things and rant about my rooting experience to those people who would unconsciously root. More ranting is needed.
Sent from my HTC Explorer A310e using xda app-developers app
ri123 said:
As I have said,one of the problems with rooting is that people have to move off their Rom in case of factory reset bricking.
0.1% have got the limited service error or the bad zip file error with their phone practically in a trap.
Much more than 0.1% have the sdcard blank error
I understand root enough to install roms and unroot my phone.
I did not do this on purpose, I just installed stock Rom and factory reset and my phone did not work as it intended to.
This is why I shall, in the future, ACCEPT things and rant about my rooting experience to those people who would unconsciously root. More ranting is needed.
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
whenever you flash something to your phone expecially firmware you should check the md5sum, its a given and those 0.1% would not have a brick due to a curropt download if they did this so again not the fault of root
having root access WILL NOT cause your sd card slot to quit working, this just has no merrit, having root has just doesn't break hardware in itself, it just doesn't
depending on the phone and how you rooted and if you have an unlocked boot loader and loads of other question need to be figured out before you flash a stock rom, especially from bootloader (if the rom is packaged with a radio, hboot, recovery etc)
once you have true soff you can flash almost anything, including things that shouldn't be flashed. have a security flag is good for this exact purpose, to keep people from flashing what they shouldn't - yes this is how most people brick their phone, they don't fully understand.
and I'm not saying you stupid by I do agree it doesn't take a genius to flash a rom, but knowing the steps that someone has written down is diffrent then undertanding why it works
listen I know you said more ranting is neccessary, but it isn't, the fact is you figured out how to have fun with your phone by following some steps you read in a forum somewhere or watched a youtube video, that's great fun, I know I love it to.
but you didn't bother to figure out why it works or what to do/not to do, because you didn't you made a mistake, it happens, no one thinks less of you.
now you should learn from your mistake and learn to accept blame for making this make, no one told you to do what you did, and you didn't take the time to find out the repercutions of what you were about to do before you damaged your phone.
again root privalages in itself CAN'T harm your phone it just enables you to make a mistake as you have lost some security against it, just as owning a gun won't make you shoot someone but gives you the ability to do so (exuse my analogy as I know it is not apples to apples)
**** happens, get on with your life, no need to rant, no one thinks less of you, learn from mistakes, accept blame when you should... and as always exuse my speeling/grammar errors as root in it self won't make me smarter either
good night
Sent from my HTC Vision using xda premium
demkantor said:
whenever you flash something to your phone expecially firmware you should check the md5sum, its a given and those 0.1% would not have a brick due to a curropt download if they did this so again not the fault of root
having root access WILL NOT cause your sd card slot to quit working, this just has no merrit, having root has just doesn't break hardware in itself, it just doesn't
depending on the phone and how you rooted and if you have an unlocked boot loader and loads of other question need to be figured out before you flash a stock rom, especially from bootloader (if the rom is packaged with a radio, hboot, recovery etc)
once you have true soff you can flash almost anything, including things that shouldn't be flashed. have a security flag is good for this exact purpose, to keep people from flashing what they shouldn't - yes this is how most people brick their phone, they don't fully understand.
and I'm not saying you stupid by I do agree it doesn't take a genius to flash a rom, but knowing the steps that someone has written down is diffrent then undertanding why it works
listen I know you said more ranting is neccessary, but it isn't, the fact is you figured out how to have fun with your phone by following some steps you read in a forum somewhere or watched a youtube video, that's great fun, I know I love it to.
but you didn't bother to figure out why it works or what to do/not to do, because you didn't you made a mistake, it happens, no one thinks less of you.
now you should learn from your mistake and learn to accept blame for making this make, no one told you to do what you did, and you didn't take the time to find out the repercutions of what you were about to do before you damaged your phone.
again root privalages in itself CAN'T harm your phone it just enables you to make a mistake as you have lost some security against it, just as owning a gun won't make you shoot someone but gives you the ability to do so (exuse my analogy as I know it is not apples to apples)
**** happens, get on with your life, no need to rant, no one thinks less of you, learn from mistakes, accept blame when you should... and as always exuse my speeling/grammar errors as root in it self won't make me smarter either
good night
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thanks for the reply.
I feel more people should know the repercussions and 'cons' of rooting so I thought of involving my situation as it could affect someone's choice of rooting.
What is a security flag? My phone is s on and yet it does not work.
Also, what is 'true soff'?
Sent from my HTC Explorer A310e using xda app-developers app
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.
Well, I ditched my iphone to try out the nexus one... I just got the phone today and I barely know how to use it stock (2.1). Phone is untouched, brand new from google...
I guess I would like to take advantage of the phones power and more importantly, try out version 2.2.... any advice where to begin, tutorials etc? thx in advance, I will go back to reading this site!
First, get to know your phone. Use it as long as you can before rooting, until you get used to it and EVERYTHING it does. When it starts to get boring, ROOT it! By that time you should know every secret the phone offers!
not a big fan of patience... I would like to learn to root it and play around... but nothing brick like...
2.2 would be nice and anything else people recommend, lol....
thx man, goodnight.
Mr.Kakarot said:
Well, I ditched my iphone to try out the nexus one... I just got the phone today and I barely know how to use it stock (2.1). Phone is untouched, brand new from google...
I guess I would like to take advantage of the phones power and more importantly, try out version 2.2.... any advice where to begin, tutorials etc? thx in advance, I will go back to reading this site!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=688000
Inside there's a link, follow the Pre-requisites on that link first... and setup ADB first.
ok so set up that ab thing first then follow the tutorials... also, should I have mentioned it is a *rogers 3g phone (att&t)
thx again and goodnight 4 real
If you barely know how to use it stock.... you should probably figure that out before you go around rooting it, flashing custom ROMs, and trying the latest BETA OS release. Once you've got the stock OS figured out and are getting bored with it, THEN root and move on.
Learn how the phone works. This is no iPhone and the settings with this phone are plentyfull. Have in mind that after you flash a Cyanogen ROM for instance, you will have 4 times more settings to play with, hence the advice to learn the basic functions on your N1. But anyways, you will come to a certain point where the GEEK in you wakes up and you wanting MORE..
DO also know that when you want to root your phone, you need to unlock you phone. Doing this will VOID YOUR WARRANTY. I will also advise you to use your phone for a period of time to see that there are no issues with hardware and build of the phone (buttons, dust under screen, trackball not working, not chargin, loose connectors etc etc..), just to be safe. Coz once you unlock it, there is NO going back to lock it again (at this point)
Setting up ADB and Recovery can be the most struggling with drivers and interface but once that is passed and you start using recovery on a daily or weekly basis, is all smooth ride from there. I guarantee you many hours customizing and experimenting with this phone than any other non-andoid phones you have had in the past.. is pretty much an addiction. i have rebooted this phone more the last 3 months than any other phones in my whole lifetime .
Rule of thumb is always have a recent Nandroid (backup done in recovery) before flashing. Flashing ROM's are usually safe as safe can be. Kernels are not risky to flash either, but remember that Kernels are the ones that controls voltages and speed of you Processor and other things, and flashing wrong Kernels can result in non functioning behavious in your OS and worst case, the processor overheating, so know what you are doing when flashing Kernels. At one point you will start trying out kernels because if you are on a hunt for more battery life, the ROM + Kernel combination are the main things that makes this happens.
Then , a last note: I addvise you to NOT update radios if you don't have any problems with the one you have. The Radio's are the one that controls your ability to call controls your phone's antenna and Wi-Fi. If you DO flash radios and happen to terminate the process, i guarantee you a bricked phone. So beware. If you upgrade to FROYO, one of the processes is flashing a new radio. So let things runs it course once in process.
Have fun trying to optimize your phone to last as long as it can on one battery charge...
If you like to begin in Android World you can start from the following blog
nextworldmobile.com. It has reviews of Android Applications that you must put on your mobile plus Flashing Tutorials etc.
Theunlockr.com is a great website for rooting and anything on the nexus. They also have videos
-------------------------------------
Sent from my Nexus One
pretty valid points from all of you, thanks very much.... I think I will give it a week or atleast the weekend... once I got in on luck.... maybe I will move on
I do buy and sell phones a lot... might be best to wait and see if there is a way to reverse the process and keep warranty intact first?
thx a bunch.
since the OTA Froyo should be coming in by maybe end of next week, i'd wait and just mess with 2.1 for now
jblazea50 said:
since the OTA Froyo should be coming in by maybe end of next week, i'd wait and just mess with 2.1 for now
Click to expand...
Click to collapse
It should definitely be soon, and will give you a chance to have new software and features without voiding your warranty. Win-win :-D
jblazea50 said:
since the OTA Froyo should be coming in by maybe end of next week, i'd wait and just mess with 2.1 for now
Click to expand...
Click to collapse
I really recommand to do that exact thing:
learn nandroid (backups )
then play with your 2.1
2.2 will be out before you could have learned everything you wanted from 2.1
thx again, I am pretty excited about 2.2... coming from a 3gs... I kind of thought I would not like my n1.. but I see no problems with 2.1.... I cannot imagine the performance increase it claims.... gonna be sweeeeet.
So, anything non warranty killing you guys recommend? apps/tweaks etc? thx
Mr.Kakarot said:
thx again, I am pretty excited about 2.2... coming from a 3gs... I kind of thought I would not like my n1.. but I see no problems with 2.1.... I cannot imagine the performance increase it claims.... gonna be sweeeeet.
So, anything non warranty killing you guys recommend? apps/tweaks etc? thx
Click to expand...
Click to collapse
You can download Launcher Pro from the Market to replace the current home Launcher. It will allow you to have up to 7 home screens and makes everything a whole lot smoother when you swipe between the screens.
sweeeeet tip bro, thx!
i believe that there exists a non-warranty-voiding method of updating to froyo. it's much faster than 2.1, and battery life is also improved.
for apps, there are threads about it but, some that are just pretty darn neat would include:
google skymap
barcode scanner
google goggles
some augmented reality apps would be:
layar
wikitude
for a better typing (rather swiping) experience, get swype. you should be able to find instructions on how to put it on around here, and there is a non-timed release in the apps/themes section
i use 'and explorer' as a file explorer
pandora is a must if you like internet media
google listen isn't bad (although i hear good things about other apps) for pulling down any podcasts you like
and, go give the navigation app a try. it's the bees knees. not only does it give turn by turn directions, but as long as you load the trip while in a 3g or wifi connection, it caches the whole thing, so you can drive through dead zones and won't lose the the path, as long as you have gps signal. plus, it switches to street view to show you the destination, when you get there
timothydonohue said:
i believe that there exists a non-warranty-voiding method of updating to froyo. it's much faster than 2.1, and battery life is also improved.
...
Click to expand...
Click to collapse
yeah, i updated mine via the non-warranty-voiding method, but since i like some of the apps that require root, i had it rooted
to update to frf50 (Froyo) without voiding warranty, you need to download the OTA file and rename to update.zip and place in the root of the SD card
1. power off phone
2. hold down volume down button and press power
3. scroll to recovery and hit power (should take you to screen with an exclamation mark or something similar
4. while holding down power button, press volume up
5. this should take you to stock recovery and you can now apply update.zip from sd card
those may be the correct steps, i don't think i'm missing anything; there's some guide located in the general forum
thx for the app suggestions, I will try them all
as for the above instructions... each site I try to grab 2.2 from.. says it no longer exists? thx
timothydonohue said:
i believe that there exists a non-warranty-voiding method of updating to froyo. it's much faster than 2.1, and battery life is also improved.
for apps, there are threads about it but, some that are just pretty darn neat would include:
google skymap
barcode scanner
google goggles
some augmented reality apps would be:
layar
wikitude
for a better typing (rather swiping) experience, get swype. you should be able to find instructions on how to put it on around here, and there is a non-timed release in the apps/themes section
i use 'and explorer' as a file explorer
pandora is a must if you like internet media
google listen isn't bad (although i hear good things about other apps) for pulling down any podcasts you like
and, go give the navigation app a try. it's the bees knees. not only does it give turn by turn directions, but as long as you load the trip while in a 3g or wifi connection, it caches the whole thing, so you can drive through dead zones and won't lose the the path, as long as you have gps signal. plus, it switches to street view to show you the destination, when you get there
Click to expand...
Click to collapse
ps: will pandora work in Canada? thx
Hi so I just heard that the D3 was rooted two days ago (been keeping up until a week ago). I'm not exactly a pro in this area or have ever rooted a device before but I have spent quite a few hours today reading up on the process and any info I could find.
Basically I just want to know if I should root my D3 or wait out another week or so? I heard that a SBF (?) hasn't been found yet so the stock rom can't be recovered and there is really no recovery net yet so should anything go wrong, there aren't a lot of options.
There is a one-click method to root but I'm going to try the original method using the adb shell (lol still researching what on earth to do with that still, just installed the android sdk :x). I'm not concerned about the process of rooting my droid, it's what comes after that makes me hesitant in doing so.
I read that there is a (seemingly simple) method to unroot the D3 by deleting the su file in some directory and rebooting (can't remember, it seemed legit however). Would "unrooting" have any consequences or would your device be back to the exact same state it was in right before you rooted? I'm not planning to drastically mess around with my D3 should I root it. Just want to take a few screenshots in an app to help out a dev, freeze any bloatware that won't cause problems, do a complete nand backup, and... thats about all that comes to mind right now.
I guess what I'm trying to ask is if rooting my D3 tonight would have any irreversible consequences and if there is any benefit in holding off the root?
Oh! Btw the OTA, I know that rooting won't affect ones ability to receive the update but that it will unroot your device and keep it that way. Would the rooting-discovery process have to start anew for people who update using the OTA (Thinking Verizon might patch the root-exploit) ? I know that updating via OTA isn't too bright anyway because devs just take the update and build on it before releasing it on their own custom ROMs and whatnot, but I feel official updates are somehow more stable (most likely flawed thinking, feel free to correct me on that lol).
Yes - SBF is an important component which would guarantee 100% pre-root configuration.
Removing the su binary and the superuser app would however put the phone back in factory state for this exploit. But anything you do while rooted inside /system is your responsibility to correct. Motorola patches usually verify only file existence/checksums and not creation/modification dates, so you should be fine with simple push of the removed (or renamed) stuff back. I remember I was able to update my D2G without unrooting in the past, but that's not necessarily granted for any other updates of that or any other Motorola phone. Ideally, you want phone in factory state to guarantee update will pass.
Another issue is nand backup you mentioned. Custom recovery isn't yet available for this phone. You can't do nand backups. So even this "safety net" isn't here. Installing custom recovery is a "100% secure way" to have OTA updates fail to apply since it messes up with phone's /system files. Un-doing CWM is a bit more complex than unrooting only and if not done carefully - a sure way for a soft brick. SBF is what we all want before start messing with anything, IMO.
So if an OTA updates fails for whatever reason, your phone will get soft bricked or?
I don't think ill be updating anway, but its good info to know for the future.
Sent from my DROID3 using Tapatalk
I would say root the device and don't worry about unrooting. If you have to return it to the store or something, unfreeze the apps and delete su. Once you mess with it though, it will be very difficult (impossible?) to ever make /system binary identical to the factory image without an sbf. That said, I doubt VZW takes the time to investigate this very closely.
But I don't see any other reason to ever unroot. When the OTA update comes down, just don't install it. In a few days after its first released, the community developers will tell you how to install it with root and not botch anything up.
Dmw017 said:
So if an OTA updates fails for whatever reason, your phone will get soft bricked or?
I don't think ill be updating anway, but its good info to know for the future.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
No - fortunately not. It will just say "Update failed" and phone will reboot back to normal.
Regarding updates - you may want to reconsider - updates usually fix bugs, bugs like the bluish camera or the wrong geotagging. Or stuff like phone shooting at max brightness after removal from HD dock.
But as the other poster mentioned - the community would do the hard work for you 'back-porting' the update to a rooted phone. Sure enough - we need custom recovery to be made before we can install any 'backported' updates or other customizations.
But all will come with time.
If you need to use an app that requires root (like openvpn or VPNC), or if you want to remove some of the unwanted apps Verizon stuck on the phone, you should root of course, but if you don't care about such stuff and want to be 'compliant' with stock software - stay as is, until at least SBF comes.
Yeah I rooted already but should an update come, I could always unroot my device. An update would be really welcome too. Yeah the bluish tint on the cam is bad but there are soft fixes for that. What I really really want out of the update is the huge improvement in battery life I've heard about. Im using the extended battery right now and straight up, it sucks. I've heard good things about the extended battery but mine lasts ... maybe 10 hours under light - medium usage, playing music for several hours and having the display on for about an hour. I expected a lot more. Numerous people have reported getting 24-48 hrs of life while others got 15 under normal/heavy use.
There have been a few reports of peope already receiving an OTA update (devs/testers most likely) but have said many pf the d3s current issues were fixed with it, primarily the blue tint on cam and the battery life.
Honestly, with root, I figured my battery would outlast a day like a champ, but there have been no/minimal improvements, even with every piece of bloat frozen. I even froze google Maps because it constantly showed up as using cpu (and therefore battery), have my radio set to cdma, and only have 1 gmail account syncing.
Sent from my DROID3 using Tapatalk
Recently my BFF thinks that her boyfriend is starting to lose feeling for her and start finding other girls. She wants to break up but her boyfriend won't let her go unless she provides evidence that he is losing feeling/cheating on her. She asked me to help but I'm at a loss except for one idea.
It was recently reported in the newspapers that you could bypass all security by freezing an android phone for an hour, then quickly removing the battery and putting it back on and turning it on while it was still below -10 degrees celcius. Is this really possible?
Secondly, his phone is a Galaxy Mini with whatever is the newest firmware (I'm a galaxy Mini II user so I'm not too sure), stock kernel, stock ROM, non-rooted but bootloader i think by default it's unlocked in SG. (mine came unlocked). It's been in use for quite some time only.
If the freezing is not possible, could we do it by any other method? note: before i can get pass the damn password i can't turn adb, unknown sources or debugging on.
Yeah that's all. Also, we can't wipe the /data since that's what we're gunning for. The method must be accomplish-able within 2 hours.
I might sound like I'm asking for a lot and might be unreasonable but please help.
Thanks in advance.
P.S. Please don't talk about the "just break up" or "politely ask him". If that had worked I wouldn't be asking here. He refuses to break up and he refuses to give his phone to me, even to "play". so called ethical hacking through the human link doesn't work anymore. We plan to take his phone for a while, bypass the pattern lock, then sieve through information.
blazerphoenix said:
Recently my BFF thinks that her boyfriend is starting to lose feeling for her and start finding other girls. She wants to break up but her boyfriend won't let her go unless she provides evidence that he is losing feeling/cheating on her. She asked me to help but I'm at a loss except for one idea.
It was recently reported in the newspapers that you could bypass all security by freezing an android phone for an hour, then quickly removing the battery and putting it back on and turning it on while it was still below -10 degrees celcius. Is this really possible?
Secondly, his phone is a Galaxy Mini with whatever is the newest firmware (I'm a galaxy Mini II user so I'm not too sure), stock kernel, stock ROM, non-rooted but bootloader i think by default it's unlocked in SG. (mine came unlocked). It's been in use for quite some time only.
If the freezing is not possible, could we do it by any other method? note: before i can get pass the damn password i can't turn adb, unknown sources or debugging on.
Yeah that's all. Also, we can't wipe the /data since that's what we're gunning for. The method must be accomplish-able within 2 hours.
I might sound like I'm asking for a lot and might be unreasonable but please help.
Thanks in advance.
P.S. Please don't talk about the "just break up" or "politely ask him". If that had worked I wouldn't be asking here. He refuses to break up and he refuses to give his phone to me, even to "play". so called ethical hacking through the human link doesn't work anymore. We plan to take his phone for a while, bypass the pattern lock, then sieve through information.
Click to expand...
Click to collapse
ADB isn't on, well i think somehow exploit might work. Search around XDA there are some tutorials here.
F4uzan said:
ADB isn't on, well i think somehow exploit might work. Search around XDA there are some tutorials here.
Click to expand...
Click to collapse
Erm sorry i'm not sure what do you mean by exploits. I'm sorry I'm kinda new to all these stuff.
How do u know that the phone is not "Debugging On"
Most android users are turning on that feature.
Well if the Debugging is ON ... I got the way to unlock the pattern within 1 minute.
Fastest way to bypass: Wipe data. If you can't, there are only harder ways.
Factory reset
You can always do a factory reset to remove the lock but it will wipe /data. You can still do that tho. It's explained here : http://www.hard-reset.com/samsung-gt-s5570-galaxy-mini-hard-reset.html . Also the fastboot mode works with adb swell as download mode.
Generalil said:
You can always do a factory reset to remove the lock but it will wipe /data. You can still do that tho. It's explained here : http://www.hard-reset.com/samsung-gt-s5570-galaxy-mini-hard-reset.html . Also the fastboot mode works with adb swell as download mode.
Click to expand...
Click to collapse
Mini doesn't have fastboot. It only have Recovery, and Download Mode (don't tell me about normal boot).
My mistake ;P A habit from LG-GT540
ಠ_ಠ
So I have some malware on my S21 ultra reinstalled the factory operating system and this thing whatever it is is still taking screenshots and just doing weird things. Like what is the next step here thanks in advance
MECHMILLER said:
So I have some malware on my S21 ultra reinstalled the factory operating system and this thing whatever it is is still taking screenshots and just doing weird things. Like what is the next step here thanks in advance
Click to expand...
Click to collapse
You need to give more details bud. We are not mediums here.
Which version of the phone do you have? Where did you buy it? Rooted, non-rooted? What weird things, other than taking screenshots? How exactly do you understand that it is taking screenshots, does it give you a notification or do they just appear in the gallery? How often does it happen, is it random or does it also happen when you do certain tasks?
If you need help with such a potentially complicated issue, you need to give as many details as possible so people can help you without guessing everything.
On Android 9 and above it's almost impossible to have an embedded rootkit that a factory reset won't kill. On 8 and below it is.
So it's something you installed (including updates), or that's living in your data or one of the factory installed apps. Fun times
MECHMILLER said:
So I have some malware on my S21 ultra reinstalled the factory operating system and this thing whatever it is is still taking screenshots and just doing weird things. Like what is the next step here thanks in advance
Click to expand...
Click to collapse
The best solution for this is to ODIN reset.
MECHMILLER said:
So I have some malware on my S21 ultra reinstalled the factory operating system and this thing whatever it is is still taking screenshots and just doing weird things. Like what is the next step here thanks in advance
Click to expand...
Click to collapse
That's not enough information to offer any intelligent solution. Please elaborate further. With every single, minute detail. We'd all be happy to help.
Download your factory ROM and flash the phone using Odin
Download Odin 3.13.1 - Samsung Odin download with ROM Flashing Tool
Odin download. Download Samsung odin 3.13.1, latest Samsung ROM Flashing Tool for android - Samsung odin download
odindownload.com
arf8 said:
Download your factory ROM and flash the phone using Odin
Download Odin 3.13.1 - Samsung Odin download with ROM Flashing Tool
Odin download. Download Samsung odin 3.13.1, latest Samsung ROM Flashing Tool for android - Samsung odin download
odindownload.com
Click to expand...
Click to collapse
That's complete overkill. More than likely a factory reset is all that's needed... and greater care when downloading.
Pre-Pie OS's are susceptible to rootkits that can breached protected partitions but not the more modern Android versions if I remember correctly.
This is an example of one that requires a reflash to totally wipe it from the phone:
Redirect Notice
I disagree, tot overkill at all if its a persistent malware. Plus if you want peace of mind it is about as simple of a process as loading the factory ROM. Why take a risk?
OP hasn't checked into this thread after the initial message. Maybe the issue has been solved.
I think we can stop trying to break our heads until he/she reappears and joins the conversation.
enigmaamit said:
OP hasn't checked into this thread after the initial message. Maybe the issue has been solved.
I think we can stop trying to break our heads until he/she reappears and joins the conversation.
Click to expand...
Click to collapse
Or the rootkit has infiltrated all the OP's devices and data drives
Be prepared and never sync all your backup copies at the same time, stagger the syncing to help avoid the possibility of all copies being compromised.
This unlikely but it's a wild, wild world.
blackhawk said:
That's complete overkill. More than likely a factory reset is all that's needed... and greater care when downloading.
Pre-Pie OS's are susceptible to rootkits that can breached protected partitions but not the more modern Android versions if I remember correctly.
This is an example of one that requires a reflash to totally wipe it from the phone:
Redirect Notice
Click to expand...
Click to collapse
When I typed that original post I was using the phone and the keyboard kept screwing up and I was exhausted. I have factory reset the phone. The strange things that were happening like when I'd hit my recent apps tab at the bottom, if open say Ebay app then Chrome. I'd hit the recent and it would show gallery and settings. Since the factory reset it has still been taking screenshots. I've only had this phone about 20 days and got it at bestbuy. It's over the 15 day period to just take it back but hadn't been incredibly long so I guess we will see what they say. I dont do alot of app downloading or visit a bunch of websites and so on so I have no clue how this happened. Here's the real kicker, this stuff is also happening on my wife's phone (a11) I am honestly thinking about throwing the a11 in the trash and trying to get this one replaced. It's so damn frustrating it's caused arguments because I'm the one who will spend time learning how to do stuff with this. Like how to use everything the phone is capable of and can look in the settings and see that the "tracking device" in the settings that can UNLOCK YOUR PHONE, ACCESS YOUR CONTACTS" is the find my phone app that you installed from Samsung. So of course I am a "hacker" and really know nothing about this crap. And she's the person who will download every survey and shopping app she can find. So this is where I am with it idk what else to do.
MECHMILLER said:
When I typed that original post I was using the phone and the keyboard kept screwing up and I was exhausted. I have factory reset the phone. The strange things that were happening like when I'd hit my recent apps tab at the bottom, if open say Ebay app then Chrome. I'd hit the recent and it would show gallery and settings. Since the factory reset it has still been taking screenshots. I've only had this phone about 20 days and got it at bestbuy. It's over the 15 day period to just take it back but hadn't been incredibly long so I guess we will see what they say. I dont do alot of app downloading or visit a bunch of websites and so on so I have no clue how this happened. Here's the real kicker, this stuff is also happening on my wife's phone (a11) I am honestly thinking about throwing the a11 in the trash and trying to get this one replaced. It's so damn frustrating it's caused arguments because I'm the one who will spend time learning how to do stuff with this. Like how to use everything the phone is capable of and can look in the settings and see that the "tracking device" in the settings that can UNLOCK YOUR PHONE, ACCESS YOUR CONTACTS" is the find my phone app that you installed from Samsung. So of course I am a "hacker" and really know nothing about this crap. And she's the person who will download every survey and shopping app she can find. So this is where I am with it idk what else to do.
Click to expand...
Click to collapse
Try something bud, in the settings there is the palm swipe capture option. When you find it try and disable it and see if the issue persists. If your phone has no virus, it might have some issue with the gestures or the screen and it might be getting mistaken that you are trying to make a screenshot.
And regarding your wife, you gotta sit her down, smash on the table with your hand so you can get her attention for a bit, and show her some videos about security and the risks involved with ignorant behaviors in the digital world.
Good luck.
babyboy3265 said:
Try something bud, in the settings there is the palm swipe capture option. When you find it try and disable it and see if the issue persists. If your phone has no virus, it might have some issue with the gestures or the screen and it might be getting mistaken that you are trying to make a screenshot.
And regarding your wife, you gotta sit her down, smash on the table with your hand so you can get her attention for a bit, and show her some videos about security and the risks involved with ignorant behaviors in the digital world.
Good luck.
Click to expand...
Click to collapse
I have the palm swipe off. She reset hers and says it's still doing "weird stuff" but this has been such an extreme issue with us that I can't and won't touch her phone. Because even with her sitting there watching me if I'm going through **** too fast for her to see exactly what's happening it's like I'm asked to slow down and I try to... Then she's will be like well what's this and start touching **** on the screen and u lost where I was in the first place because I then have to explain something that was just there.. Like if I'm in running processes and it's like WHATS THAT. And it will be a system operation that she read somewhere is "a concern for vulnerability" and doesn't understand that it doesn't mean that because that's there that it's a problem.. It's there normally and it is possible that's a way for security to be compromised.. Hopefully you can see the pattern I'm going in..... I am pretty good with this stuff for a power user. I know what oden is.. I know what a ROM is and stuff but I have never actually loaded my own ROM on a phone. And the fact that I sort of understand some of this is working to a huge disadvantage because it's like.. Well you know how to do this stuff so no wonder she's concerned.. When in fact I don't know how to do this stuff.. I made (foolishly) the comment when I was showing a process used by find my phone to her and my sister... The fact that I just showed you this process running that your asking me about you're just viewing it in a different place shows that if I wanted to track you I'd do it and you'd be too stupid to ever find out... And it was just frustration.. I meant Id just look at your Google history or something along that mannor.. Anyways I'm gonna be heading to bestbuy to see what they say.. As far as her phone is concerned I'd rather just spend the 200 bucks and throw it in the trash. I can't do that with the s21 so this is where I am with all this. I wad actually told by my family not to worry about it.. So what if someone steals your bank info it will be fraud and you won't be responsible for it anyway.. So just forget about it and use it....and here I am
This isn't rocket science... or a soap opera
Do a factory reset then change your Google account password.
Don't load anything until it's verified to be functioning ok*.
Then be careful what you load.
*If that fails reflash the firmware.
arf8 said:
I disagree, tot overkill at all if its a persistent malware. Plus if you want peace of mind it is about as simple of a process as loading the factory ROM. Why take a risk?
Click to expand...
Click to collapse
I am ready to do this if needed. I know this isn't a major thing to do but I've never actually done it and don't know where to get my factory ROM for this on my carrier and all of that good stuff. And do I need a computer to do this with oden or can that be done completely on the phone. I am not worried about anything on here I CA. Re-download apps and photos and stuff are backed up ill just start over
blackhawk said:
Or the rootkit has infiltrated all the OP's devices and data drives
Be prepared and never sync all your backup copies at the same time, stagger the syncing to help avoid the possibility of all copies being compromised.
This unlikely but it's a wild, wild world.
Click to expand...
Click to collapse
Plot twist: the malware actually created the OP
SomeXGhost said:
Plot twist: the malware actually created the OP
Click to expand...
Click to collapse
Yeah that's sounds about right... we're getting played.
SomeXGhost said:
Plot twist: the malware actually created the OP
Click to expand...
Click to collapse
I feel the same way.
blackhawk said:
Yeah that's sounds about right... we're getting played.
Click to expand...
Click to collapse
Yea I feel like I've been created by malware with all the problems this had actually caused me.
MECHMILLER said:
Here's the real kicker, this stuff is also happening on my wife's phone (a11) I am honestly thinking about throwing the a11 in the trash and trying to get this one replaced.
Click to expand...
Click to collapse
if this is for real I'd say your problems are far bigger than just yours and your wife's phones. I'd be looking at everything in your house, computers, routers, your amazon Alexa and every cloud drive you own.
3mel said:
if this is for real I'd say your problems are far bigger than just yours and your wife's phones. I'd be looking at everything in your house, computers, routers, your amazon Alexa and every cloud drive you own.
Click to expand...
Click to collapse
Don't forget the smart appliances.
My bets on the fridge... you know the cold, silent type.