Related
I apologize in advance if this question has already been asked but I was just wondering if it were possible to completely wipe the gs4 to stock like it come straight from Samsung and load your own kernels and roms. Or even load a dev edition or Google play edition load out so that the phone could be customizable. I mean isn't that all vzw does anyway is take the Samsung and Google packages add there own twist and apps to it and lock it down.? Sorry if this seems like a waist of time but it's just a question I keep asking myself but don't have the know how to test it for myself. Any input or further ideas would be appreciated.
cnall09 said:
I apologize in advance if this question has already been asked but I was just wondering if it were possible to completely wipe the gs4 to stock like it come straight from Samsung and load your own kernels and roms. Or even load a dev edition or Google play edition load out so that the phone could be customizable. I mean isn't that all vzw does anyway is take the Samsung and Google packages add there own twist and apps to it and lock it down.? Sorry if this seems like a waist of time but it's just a question I keep asking myself but don't have the know how to test it for myself. Any input or further ideas would be appreciated.
Click to expand...
Click to collapse
Here.. http://forum.xda-developers.com/showthread.php?t=2606501
Take some time and read through what's on that thread.
To answer your question though, unless your S4 is an MDK build or a Developer Edition you aren't going to be able to have a true custom recovery that allows for AOSP ROMs or custom kernels.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Here.. http://forum.xda-developers.com/showthread.php?t=2606501
Take some time and read through what's on that thread.
To answer your question though, unless your S4 is an MDK build or a Developer Edition you aren't going to be able to have a true custom recovery that allows for AOSP ROMs or custom kernels.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
cnall09 said:
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
Click to expand...
Click to collapse
Ohh OK gotcha! Hey to me that sounds like a great plan lol just I'm in way over my head when it comes to fully understanding what's needed to make something like that really happen.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Ohh OK gotcha! Hey to me that sounds like a great plan lol just I'm in way over my head when it comes to fully understanding what's needed to make something like that really happen.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
You and me both buddy. But hopefully someone with the know how will see this and give it a try. Who knows it could be the answer we have all been waiting for.
cnall09 said:
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
Click to expand...
Click to collapse
You can't just revert to the original Google-supplied Android files as that operating system shell doesn't have drivers for the specific hardware devices in your phone - it has to be modified to add drivers for the screen, radio, cameras, touchpad, and so forth. That's files provided in the Kernel, so in the end you're asking to revert to an earlier kernel.
You can't install a Google Edition ROM image without customizing it for the specific phone, which is what some people have done. That is, to take the stock ROM and replace bits with those from the GE phone to try to get closer to the original; however, you can't go very far with this without having to change the kernel to make it compatible with GE, so you're stuck.
It's not a horrible situation as we can still use Safestrap to boot a custom ROM as long as it's compatible with the touchwiz kernel. If we could replace that kernel, we'd be able to run a lot more ROMs, but since the locked bootloader will reject a non-Samsung kernel, we're stuck.
k1mu said:
You can't just revert to the original Google-supplied Android files as that operating sysm shell doesn't have drivers for the specific hardware devices in your phone - it has to be modified to add drivers for the screen, radio, cameras, touchpad, and so forth. That's files provided in the Kernel, so in the end you're asking to revert to an earlier kernel.
You can't install a Google Edition ROM image without customizing it for the specific phone, which is what some people have done. That is, to take the stock ROM and replace bits with those from the GE phone to try to get closer to the original; however, you can't go very far with this without having to change the kernel to make it compatible with GE, so you're stuck.
It's not a horrible situation as we can still use Safestrap to boot a custom ROM as long as it's compatible with the touchwiz kernel. If we could replace that kernel, we'd be able to run a lot more ROMs, but since the locked bootloader will reject a non-Samsung kernel, we're stuck.
Click to expand...
Click to collapse
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
Short answer - no, you can't do that...it doesn't work that way. Depending on the bootloader your phone came with you cannot downgrade. You can try erasing everything and starting over but that's one thing you cannot change.....your stuck.
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
Feel free to do what you want...but you may end up with a $600 door stop. ..
Sent from my SCH-I545 using XDA Premium 4 mobile app
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
You can totally do this, you can replace the kernel and everything. The phone won't boot, and you'd have a hard brick though. The problem isn't replacing the kernel, the problem is getting the phone to boot after doing so. Download mode operates through aboot, aboot has protections and conditions set that regulate what kernel and recovery partitions you can boot. If these are replaced with a "non-allowed" version the phone simply won't boot, in other words it would be hard-bricked at this point.
Sent from my SCH-I545 using XDA Premium 4 mobile app
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
"Shipping the phone down to nothing but download mode" - yes, you can wipe the internal ROM and strip it down to download mode.
Then you have a brick which runs just the downloader. OK, it's not quite dead, because you can flash stuff. But what can you flash?
OK, so you want to "install new kernels drivers and software". That's not always possible. You flash kernels and and software using the bootloader, but the bootloader won't allow you to flash a kernel that's not pre-approved by Samsung. If you're rooted, the rest of the phone storage can be overwritten with whatever custom software you want, but there's a hitch. You can install whatever software you want EXCEPT for the kernel. (If not rooted, you can't even do that without a custom recovery, which the bootloader won't allow.)
The software that you flash depends on the kernel to drive the hardware, so you can't flash base software that requires services that the stock kernel doesn't provide. This is why only certain ROMs are available for Safestrap - you can't flash CyanogenMod on a Safestrapped i545 because CM isn't compatible with the Touchwiz kernel. It's theoretically possible to modify CM to make it work with a TW kernel, but nobody has done that (unsurprising, as it would be a lot of work that would have to be repeated each CM release.)
The bootloader chain is the way Samsung enforces the restrictions on what you can and can't do with your phone. With a locked bootloader (like ours), you're very limited. Until the bootloader protections are breached, what you propose can't be done.
decaturbob said:
Feel free to do what you want...but you may end up with a $600 door stop. ..
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well thank you so much for your permission to do what I want I was so afraid you wouldn't approve. and I have geek squad protection with unlimited replacements and no deductable so it doesn't hurt my feelings in the least bit if things don't go as planned. I know i ain't as seasoned as some of yall on here but thats how things get done by asking questions and trial/error.
k1mu said:
"Shipping the phone down to nothing but download mode" - yes, you can wipe the internal ROM and strip it down to download mode.
Then you have a brick which runs just the downloader. OK, it's not quite dead, because you can flash stuff. But what can you flash?
OK, so you want to "install new kernels drivers and software". That's not always possible. You flash kernels and and software using the bootloader, but the bootloader won't allow you to flash a kernel that's not pre-approved by Samsung. If you're rooted, the rest of the phone storage can be overwritten with whatever custom software you want, but there's a hitch. You can install whatever software you want EXCEPT for the kernel. (If not rooted, you can't even do that without a custom recovery, which the bootloader won't allow.)
The software that you flash depends on the kernel to drive the hardware, so you can't flash base software that requires services that the stock kernel doesn't provide. This is why only certain ROMs are available for Safestrap - you can't flash CyanogenMod on a Safestrapped i545 because CM isn't compatible with the Touchwiz kernel. It's theoretically possible to modify CM to make it work with a TW kernel, but nobody has done that (unsurprising, as it would be a lot of work that would have to be repeated each CM release.)
The bootloader chain is the way Samsung enforces the restrictions on what you can and can't do with your phone. With a locked bootloader (like ours), you're very limited. Until the bootloader protections are breached, what you propose can't be done.
Click to expand...
Click to collapse
yes sir i did mean stripped down. sorry for the typo. and ok im not talking about stripping it down just to boot a custom rom or kernel. i want authentic samsung/google software and kernels. so the samsung wouldn't even accept its on software. I apologize for seeming argumentative thats not my intent at all. im just trying to get a good idea and handle on how some of this works. i appreciate your input and help on this matter and your patience.
cnall09 said:
yes sir i did mean stripped down. sorry for the typo. and ok im not talking about stripping it down just to boot a custom rom or kernel. i want authentic samsung/google software and kernels. so the samsung wouldn't even accept its on software. I apologize for seeming argumentative thats not my intent at all. im just trying to get a good idea and handle on how some of this works. i appreciate your input and help on this matter and your patience.
Click to expand...
Click to collapse
Yeah it's a good idea for someone like yourself who seems fairly new to this stuff, because what you're proposing is kind of what were trying to do to unlock the boot loader. The problem basically is that the very base software contains checks to make sure you're using Samsung approved software.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
joshm.1219 said:
Yeah it's a good idea for someone like yourself who seems fairly new to this stuff, because what you're proposing is kind of what were trying to do to unlock the boot loader. The problem basically is that the very base software contains checks to make sure you're using Samsung approved software.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i know how to permanently unlock it without bricking it. Hit it with a hammer smoke a whole lot n watch in amazement as the bootloader flies out of this phone, able to be replaced of course. Just kidding dont do that, although ive been tempted
cnall09 said:
well thank you so much for your permission to do what I want I was so afraid you wouldn't approve. and I have geek squad protection with unlimited replacements and no deductable so it doesn't hurt my feelings in the least bit if things don't go as planned. I know i ain't as seasoned as some of yall on here but thats how things get done by asking questions and trial/error.
Click to expand...
Click to collapse
reading helps too my friend....also I wouldn't jump to the conclusion that geek squad warranty coverage applies to the the misuse or negligent use of a product....you best read the fine print again.
any way good luck
I am trying to relock bootloader in attempt to get Android Pay working. Does anybody know how to do that? I have tried the fastboot oem lock without success. Also have reinstalled stock ROM mutliple times without success either.
Try downgrading the firmware first, then upgrade again using the official process posted on ASUS. This should work with any Lollipop firmware you have installed. By doing that this may downgrade the bootloader, and by updating it to 5.0 again that should re-lock the bootloader.
Even this might be the case, I think even after you do this it could be a waste, because the padfone s firmware doesnt even support taptopay. The only way android pay might work is by having padfone x firmware run. (even that might not work because its old).
I want this to work too, but I think (in my opinion) we should wait a little bit more to see if android AOSP could support that feature or if some person finds away to make it work by going past that safteynet api.
It is also not too long that a representative of google commented on this issue as well, hinting that they acknowledged the problem with this process.
I might as well wait, and plus not even all the stores in my area support this type of payment.
Justatechie said:
Try downgrading the firmware first, then upgrade again using the official process posted on ASUS. This should work with any Lollipop firmware you have installed. By doing that this may downgrade the bootloader, and by updating it to 5.0 again that should re-lock the bootloader.
Even this might be the case, I think even after you do this it could be a waste, because the padfone s firmware doesnt even support taptopay. The only way android pay might work is by having padfone x firmware run. (even that might not work because its old).
I want this to work too, but I think (in my opinion) we should wait a little bit more to see if android AOSP could support that feature or if some person finds away to make it work by going past that safteynet api.
It is also not too long that a representative of google commented on this issue as well, hinting that they acknowledged the problem with this process.
I might as well wait, and plus not even all the stores in my area support this type of payment.
Click to expand...
Click to collapse
Yeah, I reverted back to the X firmware to see if I could get it to work. It got to the option to add a card and just after agreeing to the bank terms, it gave me the error about android not being able to verify if device/software is compatible. I have disabled root and tried using root cloak.
After some reading I found that people were able to get it to work with relocking bootloader. Others said that future patches may fix the issue considering google wallet had the same issues when first released.
daggorlad said:
Yeah, I reverted back to the X firmware to see if I could get it to work. It got to the option to add a card and just after agreeing to the bank terms, it gave me the error about android not being able to verify if device/software is compatible. I have disabled root and tried using root cloak.
After some reading I found that people were able to get it to work with relocking bootloader. Others said that future patches may fix the issue considering google wallet had the same issues when first released.
Click to expand...
Click to collapse
Yes, Im hoping for AOSP support as its one step closer to putting on cyanogenmod, since it stems from that. Then it wouldn't be long for a compromise. Might as well wait.
I have internetted to the best of my ability and tried many, many different things, but I cannot get my Note 2 to root. Odin keeps failing on NAND or on restore.img or any other step. I have tried every usb port and every cable in my house. I tried this once before (maybe a year or two ago) and managed to get a verizon "unauthroized software" message. From this, I was able to get it back to stock, and I have left it alone since.
Now this is no longer my main phone, and I WILL root it, but I need some help.
It is deactivated (my service phone is now an old Fascinate).
It is SCH-I605, on 4.4.2, baseband is I605VRUFND7, kernel is 3.0.31, build is KOT49H.I605VRUFND7.
The phone is in developer mode, USB debugging is enabled, verify apps is disabled, and I don't have an option to "unlock OEM". I (currently) have Odin 3.10 and 3.12 on my desktop. I've got a thing called "CF-Auto-Root-t0ltevzw-t0ltevzw-schi605" which I believe it some kind of "patch" for the kernel that will grant root access.
I can boot the phone to recovery/download mode. I can start Odin, I can connect the phone, I can see it in Odin (usually on COM5). In NONE of the versions of Odin I have seen, do I ever see this "PDA" button, but I do have a AP button. Depending on the version of Odin, usually AP is the only button that is enabled. One of the tutorials talks about PDA button but the screenshot shows the AP button, so I have been trying this exclusively.
I can click start, and things will work pretty good for a little while, but then I will get some error. Usually it is on recovery.img, sometimes it is on NAND rewrite (I think ... I can't get back there). Always just "FAIL!". I cannot find a log to tell me why, and the message is completely useless. Sometimes it will just hang on SetupConnection, and once it hung on recovery.img for over 10 minutes.
The last time I did this (and recovered) I was on Win 7, now I'm on Win 10.
Can somebody please offer some advice? I can provide screenshots, chat on Skype, whatever is needed. Thanks!!
Emery
I also want to mention that I tried ghetto root but I am getting errors in it as well. The main error is that there is an unexpected newline (but I do not know which file), and then I am told that root fails, and Super SU does not appear on the phone.
i used Saferoot and it seems to work each time...
Forum
http://forum.xda-developers.com/showthread.php?t=2565758
SafeRoot Link:
http://forum.xda-developers.com/attachment.php?attachmentid=2760984&d=1400951117
Jaws4God said:
i used Saferoot and it seems to work each time...
Forum
http://forum.xda-developers.com/showthread.php?t=2565758
SafeRoot Link:
http://forum.xda-developers.com/attachment.php?attachmentid=2760984&d=1400951117
Click to expand...
Click to collapse
Thanks! I will try it right now!
Ok. So saferoot failed with "Your kernel is patched! This device is not supported."
I think it also said something about a locked bootloader, so I went looking for more information and found
http://forum.xda-developers.com/showthread.php?t=2118348
I tried "no you verizon" version first, which said that it failed (I took a copy of the log).
Then I tried the earlier "Back Atcha Verizon", and now I am back to "system software not authorized by verizon ..... blah blah go to the nearest verizon store for help".
Lol, now I have to remember how to undo this ... I think I had to restore the stock image with Odin or something.
In any case, what the heck is possibly going on? How is this the most locked-down phone on the planet? This is incredible and ridiculous and I don't even know!
emeryalan said:
Ok. So saferoot failed with "Your kernel is patched! This device is not supported."
I think it also said something about a locked bootloader, so I went looking for more information and found
http://forum.xda-developers.com/showthread.php?t=2118348
I tried "no you verizon" version first, which said that it failed (I took a copy of the log).
Then I tried the earlier "Back Atcha Verizon", and now I am back to "system software not authorized by verizon ..... blah blah go to the nearest verizon store for help".
Lol, now I have to remember how to undo this ... I think I had to restore the stock image with Odin or something.
In any case, what the heck is possibly going on? How is this the most locked-down phone on the planet? This is incredible and ridiculous and I don't even know!
Click to expand...
Click to collapse
weird.. yeah i used saferoot on my device a few times and haven't had an issue.. it shouldn't matter if your bootloader is locked.. that would only keep you from flashing a customer recovery...
I know mine is running 4.1.2 (MC3) so I should be able to unlock my bootloader but can't got get CASUAL to work... just fails at different points or loops trying to install CAD or something... so not sure what i need to do.
I did try to use Flashify to put a custom recovery on.. i got the "system software not authorized... " blah blah.. knew I did have to use ODIN to restore the factory firmware.. but it wasn't reading my phone.. finally after switching USB ports, it worked and I was able to put it back to stock and get it to boot and root again..
so if anyone has any ideas on how to get CASUAL to work, please let me know.
Galaxy Note 2 lessons from Verizon
There is still no root or bootloader unlock for Verizon Galaxy Note2 (Model SCH-I605). Ours quit working, by shutting down/locking up often. From what I've found out, this behavior is caused by Verizon's own software, not the hardware, forcing us to get a new phone. I STRONGLY recommend anyone on Verizon to drop the service immediately, before this becomes the standard. What we will see is, having to purchase a new phone product every two years, requiring us to turn in the old phone, then being sold a repackaged refurbished model at new phone prices.
Verizon is pushing the boundaries, and they are preventing a piece of equipment that you own from functioning in order to force you to buy another of their products. If allowed, this business model WILL spread to all their competitors. It will stunt the growth of future technologies since innovation will not be the motivation to buy a new product, the only motivation being the continual failure of a sabatoged product.
So again, please drop Verizon if you have them, and if you don't have them don't get them.
update.. i was able to get CASUAL to work.. had to download another program to reset the CAD Driver.. then it worked like a charm.. so have an unlocked bootloader and rooted. Right now i'm trying out Alliance ROM..
emeryalan said:
Ok. So saferoot failed with "Your kernel is patched! This device is not supported."
Click to expand...
Click to collapse
yep, i got this error too after I had tried Alliance 4.4 ROM... so I guess that saferoot only works for 4.3 and older..
LordBaronMarshall said:
There is still no root or bootloader unlock for Verizon Galaxy Note2 (Model SCH-I605). Ours quit working, by shutting down/locking up often. From what I've found out, this behavior is caused by Verizon's own software, not the hardware, forcing us to get a new phone. I STRONGLY recommend anyone on Verizon to drop the service immediately, before this becomes the standard. What we will see is, having to purchase a new phone product every two years, requiring us to turn in the old phone, then being sold a repackaged refurbished model at new phone prices.
Verizon is pushing the boundaries, and they are preventing a piece of equipment that you own from functioning in order to force you to buy another of their products. If allowed, this business model WILL spread to all their competitors. It will stunt the growth of future technologies since innovation will not be the motivation to buy a new product, the only motivation being the continual failure of a sabatoged product.
So again, please drop Verizon if you have them, and if you don't have them don't get them.
Click to expand...
Click to collapse
Even though my device is bootloader unlocked for testing CM releases I always go back to stock ND7 for stability minus bootloader then Ghettoroot and it's been working solid for years. And, unlimited data for $60 is hard to beat. Absolutely nothing wrong with the phone and software and not yet with the service as long as I can avoid the $20 unlimited data increase when contract expires in 2017.
mi7chy said:
I always go back to stock ND7 for stability minus bootloader then Ghettoroot and it's been working solid for years. .
Click to expand...
Click to collapse
what version is ND7 ? thank you.
Jaws4God said:
what version is ND7 ? thank you.
Click to expand...
Click to collapse
ND7 is Kit Kat 4.4.2.
mi7chy said:
ND7 is Kit Kat 4.4.2.
Click to expand...
Click to collapse
oh got ya. i haven't read much about that version.. wonder if it has possibility of unlocked bootloader or root.
Jaws4God said:
oh got ya. i haven't read much about that version.. wonder if it has possibility of unlocked bootloader or root.
Click to expand...
Click to collapse
It's the last official release. If you're already bootloader unlocked you can use Mobile Odin Pro to flash it minus the bootloader then use Ghettoroot. Only thing is Mobile Odin Pro only works with Lollipop such as CM12.1 or older. So, if you try CM13 and decide to go back to stock ND7 you have to first flash CM12.1 then use Mobile Odin Pro to flash stock ND7.
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
mi7chy said:
It's the last official release. If you're already bootloader unlocked you can use Mobile Odin Pro to flash it minus the bootloader then use Ghettoroot. Only thing is Mobile Odin Pro only works with Lollipop such as CM12.1 or older. So, if you try CM13 and decide to go back to stock ND7 you have to first flash CM12.1 then use Mobile Odin Pro to flash stock ND7.
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
Click to expand...
Click to collapse
oh interesting.. so right now i'm on a ND7 port.. should I bother flashing the ND7 without bootloader or is not really needed?
Thanks!
Question for those of you with experience on the V10. I just upgraded to the V20 (love it btw). My V10 is probably the first phone I never rooted, or loaded a ROM on. I've had many devices with custom roms in the past, however they were always carried branded (not unlocked) phones. Here is my question:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Thanks in advance..
X
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
xarius76 said:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Click to expand...
Click to collapse
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
beavis5706 said:
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
Click to expand...
Click to collapse
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
emdroidle said:
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
Click to expand...
Click to collapse
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
X
xarius76 said:
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
Click to expand...
Click to collapse
This is a substantial annoyance to many people, though there are some hopes of working around this...
xarius76 said:
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
Click to expand...
Click to collapse
I won't swear to it, but I was under the impression the updates come from LG, at which point it should still nominally update if brought to the EU. Failing that, LG Bridge should be able to get updates.
xarius76 said:
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
Click to expand...
Click to collapse
Remember, this is risky though hopeful.
Hello, forgive me for asking what are probably considered noob questions, but I've been reading quite a few threads and getting lost in the acronyms (not to mention the users that don't agree with one another).
I've got an S9+ with G965USQS3ARG8 with Verizon bloat. I'm trying to bring it over to Project Fi. Inserting my active sim from my Nexus 6 seems to work OK. I have a persistent message about it not being a Verizon sim though, and would also like to get rid of the Verizon bloatware to clean this thing up a bit. Can I flash a U1 firmware on here and call it a day? If so, can I use heimdall? I'm running Linux Mint, just updated to Java 11, and heimdall is correctly detecting my device. I don't have Windows, and it seems Odin is kind of the default around here, but it's not my best option.
Do I need to unlock my phone in any fashion first? I have adb, if necessary. I have G965U1UEU3ARJ2 downloaded already, I just don't want to brick this thing and am not sure if I should proceed. I'm used to using TWRP to flash Moto phones, this is a different ballgame. Also, am I likely to run into bootloader incompatibility issues? What do I watch out for?
Thanks!
Not to worry! I was in the exact same boat as you, was expecting to receive a G965U1 but got a Verizon G965U. I posted in this thread and a very helpful member here walked me through it: https://forum.xda-developers.com/galaxy-s9-plus/how-to/g965u-g965u1-firmware-links-t3763487/page144. My post started on page 144 and pretty much takes up the rest of the thread. The 5th number from the end is the bootloader version, and I was advised to pick a U1 firmware with the same bootloader version, so it looks like you want to pick something with a 3, as you have. The only other thing is I was advised to pick an XAA firmware, which I guess means completely carrier free, but I'm not sure how important it is, or if you can even find one with bootloader 3.
Anyway, it should all be spelled out in that link, as I was in your exact position and it didn't take me long to get converted to essentially a factory unlocked device. Only thing I'm not sure about is Heimdall, because here I had to use a patched version of Odin that would allow the flashing of a different models firmware.... If Heimdall will allow that then I guess it would work but I'm not sure, haven't used it in years and back when I did use it, Samsung firmware was just one file, was not broken up into parts like it is now. Anyway, good luck, you can do this.
YrrchSebor said:
Not to worry! I was in the exact same boat as you, was expecting to receive a G965U1 but got a Verizon G965U. I posted in this thread and a very helpful member here walked me through it: https://forum.xda-developers.com/galaxy-s9-plus/how-to/g965u-g965u1-firmware-links-t3763487/page144. My post started on page 144 and pretty much takes up the rest of the thread. The 5th number from the end is the bootloader version, and I was advised to pick a U1 firmware with the same bootloader version, so it looks like you want to pick something with a 3, as you have. The only other thing is I was advised to pick an XAA firmware, which I guess means completely carrier free, but I'm not sure how important it is, or if you can even find one with bootloader 3.
Anyway, it should all be spelled out in that link, as I was in your exact position and it didn't take me long to get converted to essentially a factory unlocked device. Only thing I'm not sure about is Heimdall, because here I had to use a patched version of Odin that would allow the flashing of a different models firmware.... If Heimdall will allow that then I guess it would work but I'm not sure, haven't used it in years and back when I did use it, Samsung firmware was just one file, was not broken up into parts like it is now. Anyway, good luck, you can do this.
Click to expand...
Click to collapse
Thank you very, very much, YrrchSebor! This was a very thoughtful and helpful reply. Your thread was a gold mine--it was nice to read about a problem that was actually applicable to my situation.
I can't remember if my copy of 3ARJ2 is XAA or not, so I'm grabbing a new copy of 3ARJ6 XAA from Updato. Hopefully Heimdall will work without protest, but if not, I guess I'll have to create a virtual machine with the patched Odin.
Well I tried to use Jodin3 with Heimdall to no avail. Now I'm installing VirtualBox and jumping through all the necessary hoops. Oh well, I'll get there eventually.
pvfjr said:
Well I tried to use Jodin3 with Heimdall to no avail. Now I'm installing VirtualBox and jumping through all the necessary hoops. Oh well, I'll get there eventually.
Click to expand...
Click to collapse
Keep us posted! I know with a virtualbox the trick is having the device recognized, once you get that you should be good I would hope.
YrrchSebor said:
Keep us posted! I know with a virtualbox the trick is having the device recognized, once you get that you should be good I would hope.
Click to expand...
Click to collapse
After messing with VB for a while, it dawned on me I still had a dual boot laptop on hand with a sad and degraded old Win7 install. I was able to make it work. The flash was a success! No more obnoxious notifications about sim cards. I do get odd strings of characters after texts though. May be a topic for another thread.