Database Info

Transfer ANY data from old phone to new

I realize there are a few other threads about this, but I scanned them and I didn't see anything laid out all in a row. I'm short on time, I'm selling this phone tomorrow. In a nutshell:
*I have an HTC Arrive (original) and a Samsung Focus (new)
*I can dev unlock since I paid the $99
*I know how to flash ROMs on Android and even hack a bit from the old WM6.5 days.
*I'm decently resourceful
At this point are there any ways to transfer texts from old to new? If it's a bit involved that's okay as long as it's concise and I can follow it. Game data would also be nice but no biggie. I've seen terms like "interop unlock" but don't know what that is, etc. Various threads have various "this only works if" and "no longer works" so basically I'm looking for a latest steps version.

Did you read either the "interop unlock" thread (the explins exactly what it is) or the "unlocks that are available by phone model" thread (that just started yesterday and is very clear)?
Short version though: you can't currently backup SMS on the Arrive, unless you revert to NoDo (before the interop-lock). It sucks, but MS has been quite unhelpful in terms of backup solutions, and the inability of the Arrive to use Connection Setup has crippled some of our efforts on the phone.
You could flash a custom ROM, but that would wipe all your data so it's not a very useful option.

GoodDayToDie said:
Did you read either the "interop unlock" thread (the explins exactly what it is) or the "unlocks that are available by phone model" thread (that just started yesterday and is very clear)?
Short version though: you can't currently backup SMS on the Arrive, unless you revert to NoDo (before the interop-lock). It sucks, but MS has been quite unhelpful in terms of backup solutions, and the inability of the Arrive to use Connection Setup has crippled some of our efforts on the phone.
You could flash a custom ROM, but that would wipe all your data so it's not a very useful option.
Click to expand...
Click to collapse
Yeah I'm really sorry to have shot from the hip when I posted, but I had done some research a few weeks ago and hadn't planned on selling my Arrive so quick. Your post was exactly what I was looking for, nothing has changed since I read that previously. The new thread I'll check out though, thanks.

The Market Incompatibility Final Solution

The short version:
Let's get Google to change the market incompatibility from "You can't have this," to "Are you sure...?" Because quite honestly why waste precious minutes downloading an APK from some unknown source that for all you know could be tempered with and wind up ****ing up your device.
The teal deer version:
There are now numerous threads regarding this issue and I think it's time we had one that was the central place for us to discuss this issue as it's too scattered about and so far all attempts at remedying the issue have been either in vain or temporary. We shouldn't have to suffer so much over something so unnecessary.
The idea is sound, sure, but its ways of going about doing so are very wrong. In the event that an app doesn't work as expected, or at least in suspicion of such, it need only be noted as a warning to the user. So instead of seeing that black bar stating that we can't have app X and have the install button disabled, we should see that same black bar but with a warning and the install button enabled irregardless.
If big brother is worried that because the app is known to have issues on our devices then they need only to disable the ability to rate the app for that specific user. But that's about it, as it's fairer to both parties involved. We shouldn't have to go through the hassle of having to have to keep looking for ways around something that only goes to further slow down progress, or downloading and installing APK files every time there's an update to our apps (some of which were paid for)!
We need to attack the disease at its source rather than treat the symptoms.
What the issue is basically is that "power" users prefer to use tweaked settings that the market doesn't like despite the fact that those same apps Google deems incompatible, when installed as APKs, actually work flawlessly.
I figured we should have this thread focus on the following issues:
---------------------------------------
1. Have something of a Database (or at least a simple list for now) of all the apps that El Goog doesn't want us to install. Just to emphasize the issue as there are quite a bit of apps that work flawlessly and appear in the market, while others aren't (in some cases without the developer's own wishes or knowledge for that matter). And we then label them as working 100% perfectly well or buggy under conditions Y and Z.
We make the list of all apps that are known to be incompatible and actually are! So far I've not encountered a single one. And I've been using my freak device with its freaky settings for a year+ now.
2. This is something I'm still thinking about and am not 100% sure if should be done. Start a petition on Change.org and bring this to big brother's attention as he tends to ignore the little guy. In numbers there's strength.
3. Get a list of app developers who are aware of the issue and support our cause. The reason for three is because I've been in contact with one app developer who was turned down by big brother after pursuing help with this issue because they "don't provide support for custom roms." And it's OK that they don't, as it's reasonable enough. But give us the option of opting out if you think it's wise to, and opt in even if it might cause issue. We're adults for god's sake.
4. Make a list of currently available solutions to fix the so-called 'feature' while we're waiting for an actual fix.
I'll keep this post as updated as I can with the latest known and consistently updated fixes for this 'bug'. Yeah, I said it.
---------------------------------------
So far every single app I used worked flawlessly on my I9100 running CM10 with DorimanX custom kernel. I've set the DPI to 160 and I can't imagine myself going back to anything above that. And to emphasize, I've had these setting (or at least the DPI and CM) for so long now (about a year) that I forget sometimes that I'm using something that isn't exactly 'standard', per se.
I mean, if you can live with the default dpi then that's cool, good for you. But I've had a taste of the forbidden fruit, and now I can't go back. . . .
I'm not going to start crusading just yet. First I'd like your, the community of XDA, input on this issue before we do anything. If you have any suggestions or criticism you'd like to share with us, I'd like to hear it, personally. For I may be wrong about the whole thing. Call it, lacking in confidence.
Thank you.

Reserved, just in case.

Also reserved, just in case.

Well this is fantastic. Congrats on the nerve for writing this freakishly long post. That's what I was thinking since the moment I encountered "I'm sorry, but we think this won't work as planned on your device and we deem you stupid enough to make wrong choices, so we'll just put this install button on this shelf right here, where you can't reach it" error.
However, I just said screw it, there's tons of sites where I can just download what I want without anyone questioning my motives and whether it will work or not. Never thought of it as a big deal, just as a tougher way of doing stuff, but not much I can do about it.
To get to the point, I support this cause, will sign whatever I need to sign, but am to lazy to start it myself Just wanted to give you some support. If you're willing to put some more time into this, maybe this is the beggining of a revolution! Revolution of geeks with custom DPIs! But it's still something damn it!
Cheers mate!
Sent from my Desire HD using xda app-developers app

Thank you, Uros. I was happy to read your reply.
It seems that there is no interest in this, however. Very unfortunate, but I suppose if this is what the people want. . . . It was worth a try.

Thanks for your effort.

I am rather curious to know if this is because people were going "tl;dr" or they're genuinely not interested in having this issue fixed. I just need to know so that I could make the proper adjustments.
Granted, it would take a bit longer, but as Goethe said, "I apologize in advance, had I had more time, this letter would be shorter."
Or is it that most people believe that the odds of getting Google to listen to us are too small?

There's a reason why Google won't give us the option to install anyway, just as there's a reason as to why this probably hasn't been noticed by as many people as preferred.
It all comes down to noobs.
Regarding this thread, the noobs are probably coming across this thread and click because they're interested by the title. They see all the text and think "F&#k that!". Unfortunately, that is generally the noob mentality.
Maybe colouring some of the text and spacing it out a little bit more could help the cause, but only time would tell.
Now onto the matter at hand.
I personally don't think Google will allow us to install apps anyway (even though I think they should) because noobs are super dangerous to themselves. In general, noobs won't read which then means that if they go to install an app which isn't compatible and install it anyway, they won't read that it could potentially harm their device.
The other type of user to make a mistake when it comes to installing such apps, would be the general android population. After all, us here on XDA are but a small proportion of Android users globally. Just because we have knowledge about what should and shouldn't be on our devices and how to make things work which shouldn't, the average Android user isn't the same.
They'd probably see the message and simply think "It says it could harm my phone but it's a great phone so nothing will go wrong". That is where problems can then occur.
The noobs and the average android owner would then have mucked up their device in one way or another and would be blaming and complaining to Google (as if it was Google's mistake). That makes it cause more harm than good, hence why I don't think it will happen.
Just my 2 cents, of course
''Silence is golden, but duct tape is silver''

Rooted G2x won't get past LG logo on reboot.

Before anyone chews me out for thinking I haven't researched this here, believe me I've already spent hours over the last couple days researching XDA and tried all kinds of things and I'm just at a loss for knowing what else I can do from what's available (some download links don't work etc.), and from what I remember from way back when I first rooted the phone. I take care of my developmentally disabled sister and don't have a lot of spare time to devote to researching this. No time and always stressed from my caregiver responsibilities. Not asking for sympathy, just understanding that I can't devote a lot of research time for this. I learned how to root the phone from XDA without bothering anyone, but this just has me stumped. Tried NVflash (this will flash the images to the phone, but still can't get past LG logo), LG updater / alternate updater tool (neither will see the phone),
I'm willing to pay for either an absolute certain fix with clear instructions and download links for any software needed that work, or possibly sending the phone to someone that can get the thing working again for a reasonable price. Keep in mind I can wait for a cheap broken phone on Ebay to replace the motherboard. I also luckily had another G2x that had Froyo and not rooted, but I decided to update it to GB even though the camera sucks. I uploaded two Youtube vids to show what's happening with it. I can't post links yet, but this is the extension for part 1 at Youtube: /watch?v=ulZzWFgNosY and part 2 :/watch?v=YVV9Vzbz0dg. Just ad these to the youttube url after the .com

Nutinbutdabluz said:
Before anyone chews me out for thinking I haven't researched this here, believe me I've already spent hours over the last couple days researching XDA and tried all kinds of things and I'm just at a loss for knowing what else I can do from what's available (some download links don't work etc.), and from what I remember from way back when I first rooted the phone. I take care of my developmentally disabled sister and don't have a lot of spare time to devote to researching this. No time and always stressed from my caregiver responsibilities. Not asking for sympathy, just understanding that I can't devote a lot of research time for this. I learned how to root the phone from XDA without bothering anyone, but this just has me stumped. Tried NVflash (this will flash the images to the phone, but still can't get past LG logo), LG updater / alternate updater tool (neither will see the phone),
I'm willing to pay for either an absolute certain fix with clear instructions and download links for any software needed that work, or possibly sending the phone to someone that can get the thing working again for a reasonable price. Keep in mind I can wait for a cheap broken phone on Ebay to replace the motherboard. I also luckily had another G2x that had Froyo and not rooted, but I decided to update it to GB even though the camera sucks. I uploaded two Youtube vids to show what's happening with it. I can't post links yet, but this is the extension for part 1 at Youtube: /watch?v=ulZzWFgNosY and part 2 :/watch?v=YVV9Vzbz0dg. Just ad these to the youttube url after the .com
Click to expand...
Click to collapse
After going to the store to get soup and remedies for my sister (just came down with a cold... sigh), I sat down at my computer and was disappointed that I didn't even get a response let alone an offer to help -NOT EVEN FOR PAY! So I went over what I'd done the last two days and figured it out. Phone works now, but the problem was the person's instructions were terrible. So no credit and no money. Sorry, I had to work too hard to work out what was not clearly instructed. There's a lot of that here I find. The person knows what they're talking about in their mind, but they sometimes fail to convey it clearly in written form and give instructions that are not easy to follow. Anyway, a general thanks is in order for XDA. :good:

Good to hear that your phone is working C:

Nutinbutdabluz said:
After going to the store to get soup and remedies for my sister (just came down with a cold... sigh), I sat down at my computer and was disappointed that I didn't even get a response let alone an offer to help -NOT EVEN FOR PAY! So I went over what I'd done the last two days and figured it out. Phone works now, but the problem was the person's instructions were terrible. So no credit and no money. Sorry, I had to work too hard to work out what was not clearly instructed. There's a lot of that here I find. The person knows what they're talking about in their mind, but they sometimes fail to convey it clearly in written form and give instructions that are not easy to follow. Anyway, a general thanks is in order for XDA. :good:
Click to expand...
Click to collapse
Pretty sure a high majority of people that write the guides are in high school, so there's that.
Sent from my Nexus 7 using Tapatalk HD

Hi;
Read your post; and am in the same situation. Could you PLEASE tell the rest of us "G2Xers" HOW you managed to get out of that Boot-Loop????? Quite sure your solution would be most appreciated by the rest of us!!!!!! Leave me an answer also, and thanks loads!!!

[Q] Unlocking Spring Galaxy S5 for new carrier in USA.

I am attempting to unlock my secondhand purchased Sprint Galaxy S5 to be use on T-mobile's GSM. I was under the impression the phone was already unlocked, and have tried contacting the seller but to no avail, they simply will not take my calls.
I realize this has probably been asked 1,000 times before, and may very well be within the wrong forum; for that I apologize in advance. I've been unable to go through Sprint, as they insist on giving me nothing but a hard time because I am not the original owner of the device. It is not blacklisted (I have checked this on several websites, on top of having dealt with Sprint's CSR's-- I feel they of all people would have let me know if this were the case)
I have tried forum searching and have found quite a few threads that make mention of it but have not sifted through every last result as most are simply people arguing over whether the hardware makes such a transition possible or not. After about 4 hours of reading, I've come away with the knowledge that... It may or may not be possible to accomplish it is what I'm after.
One thing that is certain, none of the short-and-sweet methods I've foudn ont he internet (open dial pad enter *#xxxxxxxxx# then tap few a through simple menus.. They seemd too good to be true, and so it turned out to be), furthermore upon entering a domestic SIM from another carrier I do NOT ge tprompted to enter the sim unlock code.. It just boots to the main screen and says "Invalid Sim"
So far the most promising seems to be using a private service for $15-30 to unlock my phone-- But even then I think I will have trouble. Alternatively, I am hoping to learn something about the custom rom's I keep reading about. The only problem is that I am not quite versed in these matters. I read the instructions and I truthfully cannot make heads or tales of it.
So being that this is probably a frequent question, I'm not necessarily looking for someone to sit down and explain it like I'm five-- as great as that would be, I just don't anticipate it happening. However, if someone could point me to some information in plain English that I may use to learn a thing or two (please, not even intermediate guides-- While I understand Desktop computers inside and out, for some reason, as stated previously, I cannot make heads or tales of any of the threads regarding custom mod's and flashing that I've read thus far,) and I've only experience in rooting a single phone, it was a much more basic, very old smart phone and I used a Clockwork Mod to do so. That being the case, I didn't really have to do anything aside from load a CWM file onto an SD card and enter debug mode or whatever it is called

Rooting Samsung Galaxy Note 5 / Sprint Nougat SM-N920P - INFO OVERLOAD

Gents/Ladies,
This is my first ever post here. I have however been active on tons of message boards and I realize right away I've probably broken 19 of your "Never Do This In First Post" laws that are a sticky somewhere I didn't see. Move my post, forgive my sins and let's get on with the suffering.
I am a web/desktop/automation software engineer of 20+ years and I thought (WRONGLY!) that rooting my Galaxy Note 5 that turned into a sloth after Sprints Nougat update would be a cinch. Well, I've googled 3 different tutorials, watched 2 full Youtube tutorials and the only thing I can say for sure is that the people who made them have SEVERE ADHD (if you really have ADHD as I do, mine is severe, pardon my humor) and must be on crack and speed and meth and helium with a wedgie to trump all wedgie's because not one of them typed or spoke in complete sentences or finished a thought. I felt like I was back in the military where everyone assumes you know all the jargon, acronyms, and social flatulence necessary to succeed and if you don't ... well that's not their problem is it?
So to my actual question. I attempted to use Odin 3 and the TWRP in a couple of different tutorials to ROOT my phone and each time things moved right long until I got to the "Blocked" message when it attempted to write the new ROM to the phone (or I think that's what happened).
My situation may be overly complex as I don't own a PC, write all my software in Parallel's VM's and attempted to use a Win 10 VM to root from.
So first, is there a way to root my phone (Samsung Galaxy Note 5, SM-N920P, Nougat, Sprint) from my mac only and if not does anyone know if trying to do it through a VM is just a NO-GO? Secondly, if there's not goo answers to my first question. Can someone drop me a link to a VERBOSE TUTORIAL WRITTEN FOR FIRST TIME ROOTERS that is specific to my phone and carrier?
Lastly, thank you so much to all of you who work your butt's off in your spare time helping people like me and people smarter and nicer than me succeed in BRUTE FORCE TAKING CONTROL of our phone's that our carriers should have given us from the TOP (time of purchase) with a stern warning that if we do something stupid it's on our heads.
Hopefully someone takes mercy on my evil soul and introduces me into this dark world of incomplete sentences and unfinished thoughts.