In any type of troubleshooting, there are diagnostic and non-diagnostic options.
The diagnostic approach is to identify the original source of the problem. By doing so, you can not only attempt to fix the issue, but decrease the likelihood of future recurrence.
The non-diagnostic approach is to blindly attempt a fix that works for most common problems. If that does not work, the next common fix will be tried, and so-on.
Each approach has its merits. Non-diagnostic fixes tend to be much faster and simpler, but they don't necessarily prevent future problems. Additionally, since they are a one-size-fits-all solution, they generally carry some side-effects.
What do I mean?
Go into the CM7 Nightlies thread and describe a problem that you are experiencing. Within a few minutes, multiple people will tell you to wipe cache/dalvik. If that doesn't work, a handful more will tell you to do a complete wipe.
Those are non-diagnostic fixes: they will solve most of the cases most of the time, but they give no insight as to why there was an issue in the first place. Was something flashed improperly? Did some data become corrupted? Did the user mess with the wrong system files? Were too many apps installed? All of these potential causes would be "fixed" by a full wipe, but all have drastically different implications for future behavior. A full wipe may get a user's phone up and running again, but gives him no clue as to what went wrong. He has failed to learn how to avoid the problem going forward.
Please don't get me wrong: I'm not saying that non-diagnostic fixes don't have a legitimate place in our toolbox, but if you are someone who uses them a lot, you should really consider a more thorough investigation the next time you have an issue.
Consider a vehicle that is having engine problems. If you could afford it, the fastest solution would be to just get a new car (essentially the equivalent of wiping your phone and starting fresh, right?). But what if car #2 starts having problems? What about #3? How many are you going to buy before you stop and say, "Hm, why can't I keep a car running for more than a few months?"
Of course, wiping a phone is free, so no one sees repeated wipes as anything more than an inconvenience. Hell, some of you have said that you like to regularly wipe your phone: that it is part of a routine for you (I've seen some of you say that you do it once a week).
And I can't blame forum members for offering non-diagnostic fixes to people asking for help: it only makes sense. It is my amateur observation that the majority of users seeking help are horrible at articulating the problem. They'll say generic things like, "My phone isn't working. It's acting really screwy. That fix didn't work. It won't let me do anything." With a complete lack of real detail, a non-diagnostic fix is really the only solution that can be offered.
There is absolutely nothing wrong with asking the forum for help: that's how most of us learned in the first place. But take a moment to consider the responses you are getting. Are they generic answers like, "do a full wipe"? If so, why? Did you not include enough detail for a more specific solution? Did you include plenty of detail and that is perhaps the only solution the person helping you knows?
And to those of us who are trying to help people, we should also be considering the advice we hand out. No, most of us do not have the time to hand-hold a stranger and walk them through a detailed investigation that can diagnose an underlying issue. Still, are you telling the same guy for the 5th time to wipe his phone? Rather than do that, encourage him to figure out the actual problem; otherwise the cycle will just continue.
Our love for quick-fixes (both giving and receiving) makes non-diagnostic tools very appealing, but if they are the only thing we use, we prevent ourselves from actually learning more about how these systems work. A guy who buys a new car every time he has a problem will never learn how to maintain a car. He'll never learn how to check fluid levels. He'll never have to find out that he's been chewing up the transmission with his driving style. Our phones are the same way. If "wipe it" is your go-to fix, what have you actually learned about maintaining your phone?
Amen, brother Byron!
Sent from my ADR6300 using XDA Premium App
Awesome. Thanks byrong.
I could have sworn I read this before bit somewhere else. Nah, no way. Not possible!
Sent from my CM7 HTC INCREDIBLE using Tapatalk
Related
So the Evo is the first android phone I've owned and coming from an old HTC Touch I have to say Im loving this phone. I've been thinking about flashing some custom ROMs so I have been learning how android works and refreshing myself on Linux but so far I havent really seen much about what people are doing to make sure their phones are secure. I know in certain circles most people wont try to pull anything cause they know they will get caught, but with all the people using Android who just seem to dive in has anyone ever checked to make sure no one was pissing in the punch? eg. backdoors, etc.
My phone is still stock atm but it drives me nuts when I can literally count the frames while scrolling. HTC promised me 2.2 will fix this but there is still something about not being allowed root that irks me.
I also wanted to say thank you to all the developers who are working on ways to fix HTC's f-ups. By you all showing HTC up and making them look bad you are forcing them to improve their software.
Not that I'm worried about other lesser known (to me) developers, but I usually stick to the big guys (Fresh, Damage for my EVO so far) anyway. I have absolutely no worries about malicious security leaks from their ROMs.
But like I said, I wouldn't personally be too worried about using someone else's ROM either. I might think twice about a 1 post member, but I wouldn't worry about it too much if I were you.
Who knows, maybe I'm naive.
I do not want to upset anybody, just trying to get some understanding of the entire upgrade to a new OS version.
I'm a programmer myself, but on Windows platform and mostly do middle tier business server side apps. Do not know a thing about Linux and android. But had some java experience in the past.
I wonder why we cannot get Froyo so long? Ain't the sources open? Even if we do not have some drivers, these parts cannot change dramatically from version to version. Published API must be stable...
Is this about Dalvik JVM? But, I guess this must be in released ROMs for other phones in the line.
What's the deal? Will appreciate some explanation here.
Android is open source, but that is only the operating system and the kernel, but the drivers and RIL that make the device actually functional are the issue as far as I'm aware. From what I've read here and in IRC, Samsung gave us a hack-job RIL, which is causing many of the issues with getting an AOSP ROM fully compiled and working. I think there may be some driver issues as well to be worked out yet, but I feel those are less important than getting things like phone/data/messaging working. I'm guessing there are more technical reasons why they can't just get 2.1 or 2.2 built from source, but those are probably the big issues.
Honestly, it boils down to Samsung.
Put simply, they're crappy coders (as HTC once was many moons ago), or they're just hella lazy (I strongly believe its the former, given RFS and this RIL mess). Most companies are pretty crappy coders, but most of the time, it doesn't interfere with major things, like OS upgrades.
That, plus the lack of effort or support on Samsung's part, has me never wanting to buy another Samsung phone again, or ever recommending an Android phone from Samsung....
I'm gonna do my best to find in my next phone another quick processor with a nice super AMOLED screen and be done with Samsung, I've had enough, and I'm a very patient person....
What is RIL? Is this Radio Interface Library?
Is it linked into kernel or other module? Not extractable at all?
As I imagine it to myself, if it is some sort of dll or package, it shouldn't matter if we do not have source, because it's interface have to be already strictly defined. It doesn't matter if it is buggy. It should work with any android version.
Please correct me if I'm wrong.
P.S. I have Dell Axim v50x and people already created ROM from scratch! However it doesn't have RIL. ;-)
CNemo7539 said:
What is RIL? Is this Radio Interface Library?
Is it linked into kernel or other module? Not extractable at all?
As I imagine it to myself, if it is some sort of dll or package, it shouldn't matter if we do not have source, because it's interface have to be already strictly defined. It doesn't matter if it is buggy. It should work with any android version.
Please correct me if I'm wrong.
P.S. I have Dell Axim v50x and people already created ROM from scratch! However it doesn't have RIL. ;-)
Click to expand...
Click to collapse
if it could have been done, birdman would have done it already
Well I think it's a valid question. Some might think it tedious or obnoxious, but absolutely valid. This is a development forum after all. The reason we don't have 2.2 isn't a hardware limitation, so it must be a practical one -- or yes it would be here.
But I'll just speak from speculation in the hopes that someone will correct me. For god sakes this is a development forum! We've got releases, we have fixes, we have patches, we have complaints, we have gossip. I'd love to see all the _development_ discussion I can get.
From a wider puzzle-piece perspective, I would like to know what is missing. We have working drivers. We have working hardware. We have full source from Google for the operating system. There are several other android phones on Verizon, a few even have Froyo. Sprint currently offers a CDMA Galaxy S phone (Epic) with android 2.2, and that phone possibly shares some hardware (though the WIMAX radio is totally irrelevant to us).
I'm not up to speed on exactly what the RIL is, or how it gets plugged into the android kernel. The RIL (Radio Interface Layer) is a software layer between android itself and the drivers controlling the phone hardware. Google provides some samples for a carrier to create one to govern communication on their network. I'd expect one issue of randomly hacking something like this, is if you are taking over your radio hardware's communications, then you have the capability of putting unwanted data on the network, which might even be criminal. Am I being extreme? So, perhaps we can't touch the RIL and need to wait for it to be spoonfed to us by those that bought the radio band from the FCC. Perhaps this code is inexorably married to particular hardware, unavailable for reading, or even encrypted. Maybe the primary limitation is the royal pain in the apricots that it is to inspect, decompile, and reverse engineer binary code.
But what if we could do something?
My understanding is the RIL is only a carrier-specific interface to the underlying hardware. Shouldn't it be similar between phones, even with wildly different hardware? Shouldn't its interface also be similar between close versions of android? The Droid 2 is a verizon phone with a RIL that does indeed work with Froyo. What I'd like to know is A) can another phone's RIL be extracted within the same carrier, and B) Being the abstract entity that it is, what prevents it from being married to the Fascinate's hardware base?
To be honest, I ardently believe a frank discussion (sans opinions, complains, problems, just productive discussion w/ a smattering of facts) BELONGS in the Development forum.
I'll stop here, in case this thread dies, as so many of mine do.
Jt1134, adrynalyne, and fallingup(angel12) are all very capable as well. This is solely the fault of none other Samsung.
Edit: to answer your question, i think that.the answer about RIL is no, although i dont have a good qualified answer about why the RIL from D2 cant be ported im sure that if it could have, it would have. Sorry thats not a better answer.
Sent from my ADR6300 using XDA App
I don't know anything about how the RIL works, but I would assume that it could only be easily ported from one device to another if they were using the same chipset in the underlying hardware for the phone. I doubt you'd be able to take the Droid 2/X RIL, and take it to the Droid 2 Global or Droid Pro. Given that, I'm guessing that you can't really take a RIL from one phone and put it on another without extensive work, since most OEMs tend to use different hardware in their devices. From what I've heard, there is a semi-working AOSP build floating around, so the devs are trying, but Samsung's crappy source to work from is not making things easy for them.
There are actually some semi-working builds of aosp floating arpunfld but the last time I checked one out it was missing one thing that I consider to be kind of a biggie. It couldn't quite make calls. I'm sure they have it to make calls now but there is a reason its not out to the forums yet. I agree withstand nuts up there. Thanks you Samsung.
Sent from my ADR6300 using XDA App
ksizzle9 said:
There are actually some semi-working builds of aosp floating arpunfld but the last time I checked one out it was missing one thing that I consider to be kind of a biggie. It couldn't quite make calls. I'm sure they have it to make calls now but there is a reason its not out to the forums yet. I agree withstand nuts up there. Thanks you Samsung.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i believe there was still no radio at all in aosp, and the hope is that 2.2 can fill in the gaps
Wow, wow, wow!
Why do we need another phone RIL? Current one from SF at hand should do perfectly. Did Google changed something in android API related to a RIL? I don't know for sure, but never heard or read anything making me think they did it. Android should call RIL and that is set in stone. ALL calls signatures must to be known. Something new may be added, but it is not show stopper.
So, I still do not understand - is it not extractable or what?
Even if not and it is somewhere in protected memory, encoded or whatever, Froyo slapped on top must work, IMHO. And sources available. So, why we stuck waiting for Samsung?
I know, one may say - do it yourself if you are so smart... Once again, I just want to understand root of the problem. I probably can do something, because I have degree and experience. But, it will take me forever. From what I've tried and seen learning curve is very steep.
On the other hand, skilled developer might simply need fresh look at the problem... May be guys just hitting wrong wall?
CNemo7539 said:
Wow, wow, wow!
Why do we need another phone RIL? Current one from SF at hand should do perfectly. Did Google changed something in android API related to a RIL? I don't know for sure, but never heard or read anything making me think they did it. Android should call RIL and that is set in stone. ALL calls signatures must to be known. Something new may be added, but it is not show stopper.
So, I still do not understand - is it not extractable or what?
Even if not and it is somewhere in protected memory, encoded or whatever, Froyo slapped on top must work, IMHO. And sources available. So, why we stuck waiting for Samsung?
I know, one may say - do it yourself if you are so smart... Once again, I just want to understand root of the problem. I probably can do something, because I have degree and experience. But, it will take me forever. From what I've tried and seen learning curve is very steep.
On the other hand, skilled developer might simply need fresh look at the problem... May be guys just hitting wrong wall?
Click to expand...
Click to collapse
is it possible? perhaps...but the 5 or so guys who really develop for this phone havent been able to get it to work....nor is aosp working 100% on any galaxy s phone
Response from developers?
Anyone?
Yes, you know so much, we are waiting for you to fix it.
Hurry the hell up.
adrynalyne said:
Yes, you know so much, we are waiting for you to fix it.
Hurry the hell up.
Click to expand...
Click to collapse
Agree get your ass moving so we can have teh honeycombzzzz. Quit being such a lazy stingy jerk and get us our AOSP!
ksizzle9 said:
Jt1134, adrynalyne, and fallingup(angel12) are all very capable as well. This is solely the fault of none other Samsung.
Edit: to answer your question, i think that.the answer about RIL is no, although i dont have a good qualified answer about why the RIL from D2 cant be ported im sure that if it could have, it would have. Sorry thats not a better answer.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
yes i was just pulling one dev name out for the heck of it
but i subscribe to the "if it could have been done, it would have been done"
adrynalyne said:
Yes, you know so much, we are waiting for you to fix it.
Hurry the hell up.
Click to expand...
Click to collapse
I don't care what you did for community! But you behave like f****g jerk.
No real explanation for the rest of us? Stay on irc, we will survive without your comments here.
CNemo7539 said:
I don't care what you did for community! But you behave like f****g jerk.
No real explanation for the rest of us? Stay on irc, we will survive without your comments here.
Click to expand...
Click to collapse
that may be a problem for those who just stay here as virtually everything is irc only these days...or the majority of it anyway
CNemo7539 said:
I don't care what you did for community! But you behave like f****g jerk.
No real explanation for the rest of us? Stay on irc, we will survive without your comments here.
Click to expand...
Click to collapse
How many different ways do people need to say that "it's being worked on"? The devs are doing a lot of work on our device, but also working with other stuff, all in their free time. Follow the stuff they do on Twitter and github, or join in on IRC.
Attitudes such as your's are precisely why the devs have stopped posting stuff here. You act as though it's a simple process to do things, when it isn't, especially when Samsung gives you a crappy base to start from. The devs have to first get Samsung's source fixed and cleaned up, then start on whatever it is they want to work on, all while finding more bugs and issues that need fixed, primarily all stemming from the crappy source. If you want to be angry at someone, make it Samsung, not the few devs that are working on our device.
Sent from my StupidFast Voodoo Fascinate
As I said - I will survive. I'm OK even with not rooted stock.
Was it so difficult to answer what the real problem is? I don't know what is the problem with this generation? Do I need to be on FB, irc or whatever to get the answer? Why do not answer in place? Ain't it this forum purpose?
No, seems like I need to kiss somebody ass to get meaningful response these days... That way he can maintain his "super god" status.
I do believe I've been pretty polite stating my question, even though English is not my native language. What generated so much sarcasm?
I'm having 0 issues with my DVP. BUT what I am haing issues is finding usable apps, not on the marketplace.
Every time I think i fine something useful like say a file explorer i find this noted on the page.
"Update: TouchXperience does not seem to work on non-HTC devices,"
I'm not a big user of Apps but certain things should be usable no matter who makes your phone, I mean it's still windows.
You are either the only NOT having problems with the 16GB Dell Venue Pro, or you have an 8GB Dell Venue Pro.
May 4th Venue Pro just died last night. Won't boot past the Dell Screen. These phones are complete POS. I am starting to lose my mind with these things. PLEASE.... if you don't own one, go with an HD7 if your are with T-Mobile. I don't care how much brighter the Venue Pro screen is, it is not worth the headaches of the 15-20 crashes a day. Or as I just stated -- the phone completely dying.
have you solved your problem?
Nope... they say they will send another, but I have to wait for them to manufacture it and ground ship it; hence - in about 3 weeks. Another monthly payment with no phone. I have really given up. These things were never built correctly and never will be. If you would like to see where I am at mentally:
http://en.community.dell.com/support-forums/mobile-devices/f/3824/t/19376375.aspx
I have to figure out a way to get an HD7 cheap I guess. I am not dumping another $400 on a phone. I wish someone from Microsoft would read this and see that I love my Zune, love my Zune software, and Love the Windows Phone 7 OS. But all this is being completely ruined for me by the Dell Venue Pro.
If someone from Microsoft is reading this... HOOK ME UP....get me an HD7 at cost! I need another Windows Phone but as I stated, I am not dumping another large pile of money into an almost identical product (minus the crashing and now permanent lock-ups) less than a year after I already forked money out.
MICROSOFT --- PLEASE HELP US. At least pull the Windows Phone license from Dell. They are taking your great operating system and dragging it through the mud. Everyone I know is incorrectly associating these Dell Venue Pro fiasco's with Windows Phone 7.
I havent had any issues with the phone. If you have having a problem with the apps installing, just wipe the phone and reinstall the update. If you still have problems just have Dell send you a new phone, you may have got a bad one. That happens sometimes with every type of phone. Personally, I think that these people complaining that the phone is a "POS", is more user error than anything else. And for them Im going to recommend a non-smart phone, and the idea that a developing website may not be the place for them if they cant even figure out how to work the phone. If you need help wiping the phone back to stock and then updating from there let me know. I can post the steps for you.
theusername said:
I havent had any issues with the phone. If you have having a problem with the apps installing, just wipe the phone and reinstall the update. If you still have problems just have Dell send you a new phone, you may have got a bad one. That happens sometimes with every type of phone. Personally, I think that these people complaining that the phone is a "POS", is more user error than anything else. And for them Im going to recommend a non-smart phone, and the idea that a developing website may not be the place for them if they cant even figure out how to work the phone. If you need help wiping the phone back to stock and then updating from there let me know. I can post the steps for you.
Click to expand...
Click to collapse
That is close to the most insulting thing I have ever read. I smart phone isn't for me. I may not be able to code apps and develope a website, but this isn't rocket science. I have gone through 4. There is no "user error". The phone's have just crashed under normal operation -- app loading or not app loading. There are so many complaints all over the web by tech savy people (go look at the guy over at zdnet) with the exact same problem.
Since you are chalking this up to "user error" , enlighten me as to what you think has been done? As far as a wiping the phone back to stock, it is stock on the Dell screen. I can force a hard reset with the down volume, camera, and power button, but it fails everytime.
As I stated, before you chalk this up as "user error", go do some research on the web. The failure rate of the 16Gb units is astounding. There is not a whole lot of things you can do to these phones to brick them, unless you start tampering with the SD card, jailbreaking or hombrewing the OS, or both. Other than that it is pretty much idiot proof.
Thanks for trying to downplay the situation, but I am sure most people on here are not buying your excuse.
I have two 16GB Venue Pro's, one I use for personal use and one for development. I received my first DVP about 2 months ago, and have had no issues with it. I ordered my second one, and have it for about two weeks with no issues. So between development and personal use I have seen no major issues with these phones. The only problem I have seen here, is your many threads and complaints through out this section. Frankly if you have had 4 phones and they all seem to have problems, the only common denominator there is you sir. XDA is for development and help, not just to flame phones and complain.
The largest thread on Dell Mobility....
http://en.community.dell.com/support-forums/mobile-devices/f/3824/t/19358469.aspx
apparently I am the common factor there too? Zero flaming here. As you see in the above thread, everything I state is WIDESPREAD, DOCUMENTED, and FACT. Nice try though, sir.
theusername said:
I have two 16GB Venue Pro's, one I use for personal use and one for development. I received my first DVP about 2 months ago, and have had no issues with it. I ordered my second one, and have it for about two weeks with no issues. So between development and personal use I have seen no major issues with these phones. The only problem I have seen here, is your many threads and complaints through out this section. Frankly if you have had 4 phones and they all seem to have problems, the only common denominator there is you sir. XDA is for development and help, not just to flame phones and complain.
Click to expand...
Click to collapse
Check out the poll at:
http://forum.xda-developers.com/showthread.php?t=891295
Not all 16GB have problem, but a fairly high percentage do.
missionsparta said:
The largest thread on Dell Mobility....
http://en.community.dell.com/support-forums/mobile-devices/f/3824/t/19358469.aspx
apparently I am the common factor there too? Zero flaming here. As you see in the above thread, everything I state is WIDESPREAD, DOCUMENTED, and FACT. Nice try though, sir.
Click to expand...
Click to collapse
I would ignore him, there are obviously good working units but the issues are real, documented and acknowledged and anyone who would dismiss that fact just because he has had a good experience is not worth arguing with. Been through 4 myself so I guess I just dont know how to use the highly advanced features of the Dell
efjay said:
I would ignore him, there are obviously good working units but the issues are real, documented and acknowledged and anyone who would dismiss that fact just because he has had a good experience is not worth arguing with. Been through 4 myself so I guess I just dont know how to use the highly advanced features of the Dell
Click to expand...
Click to collapse
I've had 3 2 have been good. So I know there are issues. The one I am using right now is really good. But I only add the really part when I swapped sd cards. So that is indeed an issue. I assure you I have neither user issues nor flame anyone. Missions statements are true. Your points about complaining and flaming are right on though. At some point threats and complaints fo become overwhelming.
I'm not trying to upset you buddy, I'm just saying if you hate the phone return it. You don't need to keep posting everywhere here about how much you hate this phone.
Sent from my Venue Pro using XDA Windows Phone 7 App
I'm having 0 problems with the phone itself, and the apps from the marketplace are fine.
My issue is comeing from the actual usable homebrew apps. The ones we actually could use for something like adding ringers and files.
And I do have the 8 gig model with NoDo and am looking into a 32gig class 10 microsd card but it cost me almost 600 for the phone. (UPS charged me 80 bucks for crossing the border)
so for me it's quickly becoming a usability issue, not a phone issue. THe phone works as planned.
Hello HD2 forum
I am planning on purchasing a HD2 second hand, to ultimately dual boot windows phone 7 and ICS.
I am buying it from a local trade in store for good prices and warranty, ideally i would like to power it on in store before the purchase to check its clean and ready for me to follow the tutorials available.
Other than identifying that the phone is still running windows mobile, is there any other way for me to check that the phone has not previously been messed with? Something in the settings? Maybe i should check for a secondary mode with certain key combination on boot?
Thanks a lot!
You kinda need to define what you mean by "clean"...I assume you mean stock (and never been modded, but these are 2 different things totally unrelated to each other, more to that in a minute).
IMO the best thing you could do would be to read up on the flashing process. This will tell you what to look for, if you're looking for a stock never-been-modded phone.
But back to your question...the first major sign I'd look for would be HSPL. I'm not going to go into detail about how to find out if it's installed. You'll have to do your own homework. Read every 'how to' and 'newb' (or noob) guide on xda. XDA is an awesome site and the dev's here write awesome documentation. Do them the favor of reading it. I mean, I don't know what you're an expert on but it might get on your nerves if I ask you simple questions about that topic cause I'm too lazy to do the research myself. The research is easy, the reference material is all contained here in various forums, depending on what you want to do. I show my appreciation for that by taking advantage of it, and don't forget to thank the dev's if something is especially helpful...they like that.
As far as checking to ensure that it's still running WinMo...that's gonna be about as effective and informative (about the phone being virgin-stock) as whether or not it's raining that day or not. What's that got to do with anything? Exactly. Nothing. My HD2 is running (at the moment) a WinMo 6.5 build. But it's been flashed more than a hundred times. My daily software is an SD Android build. Before I flashed my HD2 for the first time, I probably spent about 30 hours just reading about the process and trying to understand the process of what I was going to be doing (while reading, I usually had video tutorials playing on my 2nd monitor...I'd give up the reading when it got interesting). So that's it, really...read read read. It's not fail safe. I can't tell you how many times I waited on pins and needles to find out if I had ****-canned my new €400 phone. If you have a heart condition, you just shouldn't ride this ride. ;-)
I just got a SGS2, cause I prefer Android to WinMo. WinMo's a full time job, as is flashing. Something was always not performing the way I wanted it to (efficiency or performance etc), which was why I started flashing, but it gets to be like a drug. Nothing's ever good enough, cause you wind up wanting the best. I'd flash a ROM and install all my **** (manually, one cad file at a time) and then flash a different one and have to reinstall everything again. It was even worse if I had set up my homescreens, and folders the way I wanted them...to that end, I'd highly recommend that you also research mass-installer programs. I can't think of the name of it right now, but you pack all of your cad's in one folder and this program installs all of them (which means like 65% typically, cause invariably about 1/3 will fail for one reason or another).
Even still, looking for HSPL (which is required to flash anything on the HD2) is not very indicative as to whether or not it's been previously modded. When I got my phone it was virgin/stock, of that I'm sure. I bought it from a person, and the person was not capable of performing such tasks (he wasn't so technically inclined). But in your case, you're going to have no idea. It is not only possible but also very easy to return the phone to stock by removing HSPL leaving virtually no trace of it having ever been modded (I say virtually, cause I don't THINK that it can be traced when HSPL has been removed, but I'm not a dev and not a guru). So even the absence of HSPL doesn't even really tell you that it's never been modded, it only says that if it was- then the modder was smart enough to cover his tracks.
Basically, I don't think there's an answer to your question. There are clues that say YES THIS PHONE HAS BEEN MODDED. But there's no definitive sign to look for that say THIS PHONE HAS NEVER BEEN MODDED, and you dunno if someone's gonna lie to you. But I am inviting you to prove me wrong, read the documentation and get back to me.
Good luck flashing, don't **** it up though. You'll be pissed if you brick your ****, which is easy to do. Hell, it's probably a thousand times safer to buy a phone with HSPL installed, then you can flash all you want with no risk. The main risk, is ****ing something up in the HSPL installation process, but there are ways to minimize the risk...which all amount to: read, read, read.
And if you decide you'd be interested in previously modded HD2 (with HSPL already installed), let me know, make me an offer. Mine's just a wifi media device at the moment and I'll probably be marketing it in the near future regardless. It currently has HSPL, and I haven't decided to remove it before sale or not. I saw one on Amazon last week that was at a premium price, cause the seller had Android running on it. It's a great phone if you like WinMo, but I find Android to be much less 'high maintenance' and I used to be a huge WinMo fan (I'm a 10 year WinMo user, if you can believe that!).
Regardless, this is getting long. Those are my 2pence. Be easy.
[EDIT] Hell, if you were closer I'd let you borrow mine for a few weeks to see if you like the phone. I'm a nice guy like that.
There is no way of knowning to be honest, unless you go into bootloader and you see the firmare on it has been tinkered, ( i.e. Hspl, radio, rom ) and depending if it is a eu or tmous version. good luck tho!
l
I cannot tell you anything specifically to your phone but I can tell you some things in general.
Some people will probably tell you that it's not worth to root your phone in 2021 but I wouldn't agree. I rooted my first phone in 2013 and I've changed tons of phones from that time never being able to go more than seven days without root. It's a kind of addiction so you will get used to feeling that phone is totally yours due to the fact you can do whatever you want with it.
It doesn't mean that it's totally safe and people who don't know what they are doing can **** the things up. It's not because of the root but it's because of the people. Some people just play with the things they shouldn't play with.
Everything considering your phone and its futures depends on the custom ROM.
You may get a totally different custom ROM which doesn't have to do anything with your current phone or you can make it literally the same one which will be rooted.
"OS" is "ROM".
Everything depends on what you can find. I don't know about every phone on this world so browse the forum and you will see.
I haven't used my phone for anything else other than entertainment so I can't really tell you anything about your work but considering that you work, depending on where you work, it may be a little bit unsafe.
dedq said:
I cannot tell you anything specifically to your phone but I can tell you some things in general.
Some people will probably tell you that it's not worth to root your phone in 2021 but I wouldn't agree. I rooted my first phone in 2013 and I've changed tons of phones from that time never being able to go more than seven days without root. It's a kind of addiction so you will get used to feeling that phone is totally yours due to the fact you can do whatever you want with it.
It doesn't mean that it's totally safe and people who don't know what they are doing can **** the things up. It's not because of the root but it's because of the people. Some people just play with the things they shouldn't play with.
Everything considering your phone and its futures depends on the custom ROM.
You may get a totally different custom ROM which doesn't have to do anything with your current phone or you can make it literally the same one which will be rooted.
"OS" is "ROM".
Everything depends on what you can find. I don't know about every phone on this world so browse the forum and you will see.
I haven't used my phone for anything else other than entertainment so I can't really tell you anything about your work but considering that you work, depending on where you work, it may be a little bit unsafe.
Click to expand...
Click to collapse
thank you very much for your detailed answer @dedq
so a ROM can be replaced after rooting with something else rather than default "Android" right?
i'm a really cautious person so i wouldn't play with some setting until i know what i'm doing with it first
another thing please, do you mean by unsafe that the ROM could have vulnerability for attackers to acces my phone?
or things may get lost?
Jonsnoww said:
thank you very much for your detailed answer @dedq
so a ROM can be replaced after rooting with something else rather than default "Android" right?
i'm a really cautious person so i wouldn't play with some setting until i know what i'm doing with it first
another thing please, do you mean by unsafe that the ROM could have vulnerability for attackers to acces my phone?
or things may get lost?
Click to expand...
Click to collapse
"Default Android" is your current ROM. You have ROM now as well. We have all been very cautious in the beginning with these kinds of things like flashing U systems and those kinds of things but the thing is chances are high that you will **** something up. Everyone did that and you can count on yourself probably going to third-party technician at least two or three times. We have never made those mistakes on purpose but it's very slippery to play with these kinds of things. I suggest you don't change anything if you really need your phone on daily basis because you may lose it for a couple of days. I'm talking from my experience but I hope you won't have negative experiences if you want to try rooting and doing something more.
It is always assumed that your phone is the safest when it's default. That means no root and no flashing anything. Rooting your phone is basically opening it to tons of vulnerabilities.
Don't play with those kinds of things if you work some kind of job where your phone is under constant surveillance.
Jonsnoww said:
Hello,
so i have a Redmi note 7 - Global Version (Lavender) phone, and i have so many questions that concerns me about..
first of all i don't like how things getting very slow with my MIUI and the android 10
i thought of rooting the phone but I'm not sure if it's worth it.. there's so many confusing things on the web and tutorials to choose from.
i don't like how companies collect data and peek on my privacy silently in the background that's why i would like to root if it's going to solve this problem. I'm afraid that i won't be able to find the features i have now if i rooted my phone and installed a new ROM for example, will my phone work properly with all of the existing features in it? what's the downside to voting or choosing a wrong ROM?
and if finally found the best ROM for me, am i obligated to do updates to it manually every time a security patch comes on for example?
i mean the work is not over by just successfully installing a new ROM and rooting?
second what is the best ROM out there? IS OS same as ROM? or the ROM is just representing the UI "for example MIUI" ? or is it replacing " Android"?
any privacy concerns? or attacks? i'll be using my phone for work and very important stuff.. that i can't lose..
please someone enlighten me
and i'm so sorry for very basic questions but i got lost in so much reading articles
thanks in advance
Click to expand...
Click to collapse
I’m also of the opinion that rooting is worth the eventual hassle. Except that it’s not that big a hassle on this phone if you use Orangefox and the build in root solution. If you choose not to root but care about privacy take a look at Netguard (Github version).