While looking at other forums, I was seeing that a lot of people have problems with the message "system software not authorized by Verizon..." and people seem to have somehow accidentally got around that message. I have seen that message plenty of times on my phone and am pretty sick of it. Since the g900v has a locked bootloader with the 11' Toshiba chip, roms can't be custom, they have to be stock based but if you can somehow get around that message, could that mean you could flash custom (not touchwiz) roms without worrying about Verizon or a locked bootloader. If anyone has a way around it or knows an idea of how to get around it, it would help a lot to me and many other galaxy s5 users
Related
I've been checking for updates on my GT-I9505 and so far I've gotten that everything is up to date already and now all of a sudden I got the following message: Your device has been modified. Software updates are not available.
The most weird and infuriating is that I have purposely kept my S4 completely stock, no root, no nothing. All I've done is that I've installed a few alternative launchers.
As far as I've understood - I can use triangleaway to get back to official (I'm on baseband I9505XXUDMH6). But seriously, what's the point of that status anyway, if I don't root or flash and it still gets effed up???
Anyone seen or heard of something like this before??
What should I do, any suggestions?
At the moment I'm planning to go to the local (tech) store, where I bought this in August (or maybe end of July) and going to have a little chat, if they tell me, that it's my fault and that I must have done something, then Samsung Estonia, here I come....and if things go really south then I'm going to the Consumer Protection Agency (hope it has an understandable meaning....don't know the international equivalent), so far in Estonia they've managed to do something if things are really wrong and hurt the consumer.
I also realize that I'm furious at the moment, but I'm also really serious....worked my butt off to buy this phone and shown great restraint not to flash or root and something like this happens....
Let this be (warning sounds too harsh) note to all not rooted and trying to keep their warranty and if anyone can share some insight, suggestions, sympathy or whatever - thank you!
It's been over two weeks now.
I've been in contact with my retailer, they only recommended a factory reset and the clerk admitted that he's not too familiar with the subject.
Samsung Estonia takes a bit too long with each of their replies (as they're probably too busy with marketing all the time), but they have more helpful replies than the retailer - told me to go to a service center in Tallinn. They were able to be more helpful with other issues that I had raised.
I also read from their site, that the 4.3 update is live in Estonia since October 31st, so I wanted to try if Kies would update my device although the device status isn't official - it only showed that my device is up to date. I was just bored and decided to try OTA as well - surprisingly it didn't say that it wasn't able to update, because the device isn't official, but it said that my device is already up to date.
I rushed through the settings to check it out and now, totally out of the blue, my device is once again official.
Whoever might wonder upon this story in the future with a similar problem, I'm sorry that I couldn't help you and can only wish you patience, good luck and hope that things will turn out better in the end as they did for me (for the moment at least)
A new development:
After the device status turned official again, I found out that the 4.3 update should be live in the Baltic region since October 31. But my phone still didn't find it. Samsung Estonia finally said that it's probably the fault of a wrong region setting, but it has to be checked and can be changed for a fee, as warranty doesn't cover it. I've been checking for an update for the past couple of days and this morning the device status had changed to custom once again. Wrote to Samsung Estonia, that I'm fine with waiting for the update or paying for the region change, but a device status switching back and forth between official and custom is Samsung's fault and it should be dealt with by them.
Hopefully they'll get the message and will clear this mess with their own resources.
Hey there.
I had a similar 'issue' not long ago. I randomly browsed through the settings and the 'about' section to find that the device status was unofficial. I haven't rooted or flashed anything at all, however it didn't really create a problem. I then restarted my phone, then it said 'official' again only to change back to 'unofficial' again in about 10 minutes.
If i restarted and tried to update quick enough it would work, if the phone ran for a while I got the same message as you 'your device has been modified' or something.
I got the 4.3 update and the problem has since disappeared...
I started a thread too out of curiosity but no one seemed to know the answer. It might just be a little software bug
Hi guys,
I joined today finally after years of searching the forums for help. I finally came across an issue that I cant figure out myself and I now turn to your bright minds.
I have a Droid Razr M XT907 rooted, but with a locked boot loader thanks to Motorollya. This proprietary Android version they have on here blows. Its one thing after another. First I was having issues with the auto back up constantly running even though I never signed up for it. Even now, as it sits in quarantine it can still start up which makes me nervous. I would love me some of the new CyanogenMod, and was VERY excited about putting it on my Razr M until I found out I have that awesome firmware update that destroyed the boot loader unlock exploit. (Speaking on this, If anyone has any information on how to still unlock my boot loader by perhaps flashing an older version of the firmware if that is even possible, I would love you deeply) Anyways on to my current issues.
I have a massive number of "APPS" running in the background snagging my data and I dont understand what they are.
Everyone of them are labeled as numbers and taking various amounts of background data from my pool. And a couple others that are Verizon and Motorola based apps. What are these? What are they doing? How do I control this situation. Below is the LIST and how much background data they use
13697=3.74MB
com.verizon.permissions=3.62MB
16953=218KB
16384=516B
11287=516B
19328=516B
17452=516B
13668=516B
12112=516B
13966=516B
18144=516B
14146=516B
This is one month of used background data, and the apps im concerned about.
Ok, so typically my Google-fu is on point but I'm at a loss for finding relevant posts for my particular issue.
The issue is getting cellular data to work on the Galaxy S5 (Sprint edition), whilst using the Straight Talk carrier, while also on CM13 (snapshot). The phone was originally on Sprint, my wife just got the new Note 7 (lol - at time of the post is the day after the major announcement they'd be recalling all Note 7's), it was paid in full and as far as I can tell it is unlocked. I promptly put a new recovery on it and finished it off with CM.
I'm gonna take a moment to say something irrelevant. Oh. My. God. has rooting/custom ROM/bootloading improved over the years. Maybe it's the fact I finally have a device that was popular enough to have a real big community that worked on it, or what, but everything went SO much smoother than any experiences I've had putting custom roms on devices (then again, the fact that my other devices were always Verizon phones or Chinese tablets probably has something to do with it too). The only hiccup was recompiling an updated executable through a *nix shell. Anyways, back to the point.
I have LTE data working on stock ROM (backed it up before flashing to CM). When I switch to CM, I get working voice/text, but without all the data stuffs. What I suspect the issue may be is that the CM release that works with my phone (k1tespr) is trying to find the Sprint data network and use it. Everything works the way it should on Stock, and I've reinstalled CM multiple times now after verifying that LTE/Voice/Text works on stock, but still running into this wall when I go to use CM.
Hopefully because of the popularity of this device, and the popularity of Straight Talk BYOP's, someone figured this out!
Side Note: In the CM Cell data settings, when I go to "Select Carrier" at the bottom, it errors out, briefly rebooting the cell data settings. The error is "com.android.phone has stopped working". Looks/feels like a CM bug.
Hello folks, new to the forum here. My wife and I both recently got Galaxy S7s from Sams, and our carrier is AT&T. For whatever reason, the push updates never happen on my phone, so I am still in 6.0.1, but my wife's has gotten 7.0 pushed to hers. Problem is that after a while (perhaps a couple of days), her phone starts to develop a persistent lag, where she can't really do anything at all, like typing or changing apps, so severe is the lag. The phone was basically useless at that point, so she would have to restart the phone to restore its normal function. But the lag would always return, and she would need restart multiple times per day.
Talking to Samsung and AT&T proved fruitless at getting any troubleshooting done other than factory resetting the phone. That of course fixed the problem, but as soon as the 7.0 push update happened, the lag came back. We eventually got AT&T to send us a new phone on warranty. But just recently her phone got 7.0 pushed and sure enough the lag is back. Clearly the problem is software related, as my phone is still 6.0.1 and runs perfectly.
I am pretty uninitiated in the Android world, and so I was hoping you folks might be able to help us restore her phone, as I am certain we will get no useful help through the "official" channels. We aren't looking to root or anything, but if there is troubleshooting or a guide we could walk through, we would sure appreciate the help.
Thanks!
I had the same problem when my S7 did the update from 6.0.1 to Android 7. I asked AT&T to change the phone and they did. When the new phone did the update the lag problems started again. I downgrade to stock 6.0.1 and disable the update service with Package Disabler. Now I keep on android 6.0.1 (which I like more than the Nougat) and I do not have lag problems.
You could try to flash the Nougat update manually. It's not exactly simple, but a fair amount of reading up on it should prepare you. Obviously you'll lose all personal data, and there's even a chance it might still be laggy for you. There is a guide on how to do this on droidviews.com that helped me tremendously. Make sure that if you try this, you plug in the phone only after it is in download mode and only after Odin is open. Plus you'll need the drivers and to make sure the phone is in USB Debugging mode via developer options, as well as turn on OEM unlock before you try this. Good luck!
Hello Everyone,
Right, I'm just going to give a quick intro to the situation TLDR below.
So I've been on android for a long time, ever since I got rid of my Nokia brick but my girlfriend has been apple since her first phone, so of course, I've been singing androids praises to her about the battery life, rooting and other such android brilliance, then a few months back she said fine but she had a few features she wanted mainly a big screen, removable battery, fingerprint scanner, and a good camera so after looking at loads of phones we settled on the lgv20, and then my headaches with the phone started.
TLDRGot my girlfriend who has been on apple her whole life onto android, didn't work out so great and now I'm looking for some help.
So the current state of the phone is
it's a H910 that was updated to oreo with a H920 kdx then dirtysanterd, then flashed with a rootable oreo rom and rooted with magisk manager, forgive me if I missed anything I did all this a while ago so it's not fresh in my mind and I'm pretty tired right now so il probable edit this later.
But the issues are weird and unlike anything, I have dealt with before so call on the knowledge of any LG v20 gurus for help, the first problem was present out of the box but did seem to get worse after all the flashing and rooting ect, the phone will turn off seemingly at random and won't turn back on until plugged in, and it will also do this if you try to take a photo with flash but not if you use the flash as a torch.
Now the second issue is due to being in the UK and the LG v20 being a US phone and was the reason I started messing with ROMs and rooting, the signal is terrible, I did check to see if this would be an issue before getting the phone and it seemed to be fine for others, but after having this issue and looking a bit deeper I have seen some people having the same issue with signal and having success flashing a modified modem, but I'm worried that it might not work and may make the signal worse, but if anyone has had success getting signal in the UK please let me know how.
Finally, there are just a few annoying things like some pretty heavy slowdown at times and some general glitchiness with apps freezing and crashing, so if there are any good ways to make the phone a bit more optimized and stable while keeping root that would be nice.
Thanks to anyone who reads this, and thank you to anyone who takes the time to share any knowledge and ideas
A lot of stuff there.
Flash issue sounds like a hardware problem but it could be software gone wrong.
Same for signal problem.
I would flash back stock Nougat *US996 KDZ (usa version) to see if the problems go away. Do not root and trial it for a few days.
This will also change the modem which might help signal issue. There is guide to cross flashing variants on this forum and youtube. Search *LGUP patched V20*.
So try this first is my advise.
*is best clean stock rom without network restrictions or bloat