Related
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
MGArcher007 said:
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
Click to expand...
Click to collapse
Have you resolved this issue, if so, would you mind sharing how you did it. I've been combing the net for a few days trying to discover what is going on and your issue appears to be exactly what I am experiencing. I've read about flashing back to my stock firmware using Odin but I cannot get into download mode, when I try and get there, the phone only says "recovery reboot" in blue small font on the top of the screen and reboots.
Thanks
Ladies and gents, I apologize for abandoning this thread. I forgot exactly how I got to get the phone to update, but if I recall correctly, it had to do with me putting the phone in download mode, downloading the original firmware and using ODIN to flash it. Afterward, the "unlocked" padlock symbol disappeared and the phone was able to get the OTA update from AT&T.
I have since moved from an LG G4 to a V20 and that is what I am currently playing with. I also have a Samsung Galaxy S6 Edge (which T-Mobile replaced my G4 with when the touch screen stopped responding). I was quite stoked to find out that there is a way to root it and (seemingly) unlock the bootloader, so I'll be toying with that this weekend to see what I can do. I'd love nothing more than to just wipe that Samsung-ified Android and install a vanilla Android or CM.
Good luck to anyone who is still trying to fix this issue. Again, my apologies. I'll dig through my archives and see if I can piece together what I did to get it going again. I still have the S5 Active. Best phone by far. It's a great backup phone for when the new stuff goes kaput.
I'd attempted (and succeeded) in rooting the s7 Edge without much of a problem, it seemed to be working fine. I was considering flashing a custom ROM as well, but before I could get to that point the phone started behaving oddly. It would refuse to boot, freezing at the AT&T logo screen and vibrating in a 1-3 pattern (1 vibration, then pause, then 3, etc., ad nauseum). I realised I still had ADB access at that point in boot (somehow, I have no idea) and used it to reboot to bootloader and see what I could do with Odin.
ALL VERSIONS of Odin I have tried (3.12, 3.12.3, PrinceComsy variants of both) have failed to restore the stock image and unroot the device. I have attempted to use multiple different stock images I've found around these forums and elsewhere, and all attempts have resulted in either the phone throwing an error about the Odin version I'm using, or Odin itself telling me that the flash failed and the phone indicating some strange message about the boot or the firmware being 'fused' or something. Exact error is SW REV CHECK FAIL : [system]Fused 3 > Binary 1
All I appear to have accomplished is preventing the device from ever booting properly -- it refuses to boot normally, and by default enters Recovery mode (the stock recovery, which is essentially useless and won't do anything at all). I would very much appreciate some help getting this device off the ground again; I'm sure we can figure something out together! As I type this, I am attempting yet another version of the stock firmware I've dug up, so... fingers crossed that gets some better results. If not... please help. Currently trying the APK1 version of the stock firmware.
Cheers,
vexx32
vexx32 said:
I'd attempted (and succeeded) in rooting the s7 Edge without much of a problem, it seemed to be working fine. I was considering flashing a custom ROM as well, but before I could get to that point the phone started behaving oddly. It would refuse to boot, freezing at the AT&T logo screen and vibrating in a 1-3 pattern (1 vibration, then pause, then 3, etc., ad nauseum). I realised I still had ADB access at that point in boot (somehow, I have no idea) and used it to reboot to bootloader and see what I could do with Odin.
ALL VERSIONS of Odin I have tried (3.12, 3.12.3, PrinceComsy variants of both) have failed to restore the stock image and unroot the device. I have attempted to use multiple different stock images I've found around these forums and elsewhere, and all attempts have resulted in either the phone throwing an error about the Odin version I'm using, or Odin itself telling me that the flash failed and the phone indicating some strange message about the boot or the firmware being 'fused' or something. Exact error is SW REV CHECK FAIL : [system]Fused 3 > Binary 1
All I appear to have accomplished is preventing the device from ever booting properly -- it refuses to boot normally, and by default enters Recovery mode (the stock recovery, which is essentially useless and won't do anything at all). I would very much appreciate some help getting this device off the ground again; I'm sure we can figure something out together! As I type this, I am attempting yet another version of the stock firmware I've dug up, so... fingers crossed that gets some better results. If not... please help. Currently trying the APK1 version of the stock firmware.
Cheers,
vexx32
Click to expand...
Click to collapse
You have to use either the stock version of the firmware that your phone was on or newer. You can't use any older versions. APK1 is the latest version i believe. Use the official Odin. The .12 version and you should be good.
dirtydodge said:
You have to use either the stock version of the firmware that your phone was on or newer. You can't use any older versions. APK1 is the latest version i believe. Use the official Odin. The .12 version and you should be good.
Click to expand...
Click to collapse
Thankyou. It took me longer than it really should to figure out which firmware version to load. Downloading that now... fingers crossed, heh.
Do you think it's worth attempting to re-root and install a modified ROM on it for the performance tweaks that I've seen cropping up here and there? Or should I just count it lucky it's still mostly salvageable?
vexx32 said:
Thankyou. It took me longer than it really should to figure out which firmware version to load. Downloading that now... fingers crossed, heh.
Do you think it's worth attempting to re-root and install a modified ROM on it for the performance tweaks that I've seen cropping up here and there? Or should I just count it lucky it's still mostly salvageable?
Click to expand...
Click to collapse
Depends on what you want. Personally i would root it and go to the Verizon forum and download Stang5.0litre rom. That's an awesome rom. I'd stay away from echoe rom, seems like the devs are hit or miss on support. The dev for the stang rom is awesome and very active. I ran both of then and prefer stange.
dirtydodge said:
Depends on what you want. Personally i would root it and go to the Verizon forum and download Stang5.0litre rom. That's an awesome rom. I'd stay away from echoe rom, seems like the devs are hit or miss on support. The dev for the stang rom is awesome and very active. I ran both of then and prefer stange.
Click to expand...
Click to collapse
Woah, woah, what? You can flash a rom based on another carrier? Will it still work? O.O
vexx32 said:
Woah, woah, what? You can flash a rom based on another carrier? Will it still work? O.O
Click to expand...
Click to collapse
Yea it works. I know that one does. You'll get a message that says "unauthorized SIM card: or something like that. Just ignore it and use WiFi to setup the phone. Once you have it setup use package disabler or titanium to freeze "setup wizard" and that'll get rid of that notification. You'll have to manually setup your AT&T APN. After that your golden.
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
bkenobi69 said:
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Try to dial *#0808# in the stock phone application.
You should see a menu with several options.
Select "MTP+ADB" under USB settings and press "OK".
Then you'll be able to connect your phone via MTP or ADB to your PC.
If there's no menu, then (assuming you're rooted) open a good file browser (ES, Root Explorer or something) and open the file /efs/carrier/HiddenMenu (it's a simple text file) and replace OFF with ON there.
Save the changes and reboot the phone.
Now the menu should be operational.
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
bkenobi69 said:
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
Click to expand...
Click to collapse
Currently root is impossible for MM on G900V CID11.
Impossible means you cannot gain it now, most likely it's forever.
There's no internet site which can help.
You must choose: root on LP or unrooted MM.
You must decide if you want a stock ROM or something (TW-based) else too.
It's a good idea to flash and use a stock firmware for the time while you're thinking.
Interesting... I guess I must have been reading things wrong because I thought I could go to MM with root. I'll try going to Lollipop then but first I'm going to just flash back to JB 4.4.4.
I downloaded 4.4.4 from Samsung and was going to write it with Odin, but it says FAIL when I try to flash. I suspect I just tripped Knox...
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I'll look around to find a guide, but if you have a suggestion, I'd certainly listen!
bkenobi69 said:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means that you've upgraded your phone's firmware while experimenting.
Now you cannot directly flash 4.4.4 with Odin, you're limited to 5.0 (BOK3) and above.
Ok. I'll read the guides on the head of this list and see if I can find the right information.
FWIW, I was following the same how-to that most of the stickies point to and say is safe. I wonder how I got to a position that I'm in now when I did the same as recommended. Painiac's thread points to the same thing I did:
https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
I think I may have tried to flash a MM stock rom though when it got into a boot loop. I suspect that would be the issue.
Bootloop is not a problem in this case.
Just reboot to the recovery and perform a factory reset from there.
The phone will boot but the first boot will take 10-15 min.
bkenobi69 said:
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Marshmallow can not be rooted on CID 11 devices. The Samsung drivers are found here: https://www.samsung.com/us/support/owners/product/galaxy-s5-verizon You can follow the 5.0 root guide here: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529 to downgrade to 5.0. If you want to downgrade past that to a version lower than 5.0, you will still have to follow that guide then follow the instructions here (I recommend you to follow the root guide for 5.0 above then skip steps 1 and 2 on this page): https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858 . You can find stock firmwares here: https://forum.xda-developers.com/showthread.php?t=2784880 (stock firmware, kernel, and modem files) and if you get bootlooped or bricked, just reflash the combination file from the root guide. If you want to root 4.4.4, follow the downgrade method using all of the NK2 files but the flash the NGC kernel, run through the setup, then use towelroot and flash the NK2 kernel after that. If you ever get stuck on the red Verizon screen, just pop the battery out and reboot.
That's about all anyone can do and a run down of everything.
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
bkenobi69 said:
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
Click to expand...
Click to collapse
Understandable, I can't believe it is 2018 and we still haven't invented a way to compress 1.7GB into 1.7MB archives to make life easy on low connections. How is battery life on 4.4.4 and which update of 4.4.4 are you on? I've been having an issue with my phone dropping a percent every 2 minutes on 5.0/6.0. It would be nice find a version to root along with excellent battery life.
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Ok, I tethered to my wife's phone and am burning her data (shhhh, don't tell her).
I grabbed all of the OC4 files, the PB1 rom, and lolliroot. I think I have everything I need so long as OC4 is a good place to end up.
bkenobi69 said:
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Click to expand...
Click to collapse
Here are some files (that I been hunting for about an hour for). Just gonna reference this for future use and anyone who comes across this thread. http://rootjunkysdl.com/files/?dir=Galaxy S5
Nice find!
I have the phone up and running on stock PB1 currently. I'm going to let it sit to see what the battery is like prior to rooting. While I haven't gotten it hooked back up to my account yet nor do I have it rooted, I feel pretty confident now that I'm on the right track. Thanks!
Just to finish out this topic, I have not successfully completed attaining root on 5.0. I flashed PB1 to the phone and then followed this guide for installing KingRoot:
https://androidforums.com/threads/root-question.1120150/
I got the lolliroot files from here:
https://www.androidfilehost.com/?fid=312968873555011514
Thanks to all who offered help!
Qyuck question... I've got my phone working well bow, but there's one issue with apps I'm not sure how to address. I want to use Verizon Visual Voicemail but I can't find it on the Play store. I disabled updates so I wouldn't get the marshmallow update and break root. but, with updates turned off, VVM won't get pushed. Any suggestions?
1. Thanks to @FP_XDA and GSMZambia for the great directions found here
2. The other stuff and ideas:
The above method does put the U firmware on your phone. I had trouble getting it to connect to the network. I did try different combinations of files in the AP tar; CP; and CSC, but it would either not connect after a factory data reset or loop with the message about my SIM has changed, please restart.
I tried just flashing the following combinations through flashfire, but maybe this is a Sprint SIM issue and it works on other SIM cards; however, I have Sprint.
The U firmware seemed to work fine on the software. Including boot.img in flashfire would take away the eng_boot and root. I just had trouble connecting to the Sprint network.
Do you need to use the v5 combo file and flash a certain CP/CSC before going through the rooting steps? The U firmware CSC file is different in size, so is it a partition (PIT) issue since that will write the cache.img.ext4 file and those vary in size from stock to the U? Is there a certain order to flash in flashfire to get it to work properly?
Anyway, I downloaded several U CSC firmwares (XAA, XAS, SPR (last two are sprint)), but ran into some network issue every time. The operating system seemed stable, but the lack of connection and some random entries under settings make it so close, but yet so far.
I don't mind the Sprint firmware, but can you unlock additional LTE bands if you use the stock sprint firmware on another carrier?
Thanks for any help!
Here is more info about the Settings submenu options:
Here is some more detailed info:
The submenus under settings give me options like K twophoneservice; T roaming; Giga LTE. I think it is CSC related as those carriers are Korean based. I think this may be my issue along with a few others I've seen on reddit. Just wondering why it says that though. I used the G930U version, so not sure why this would appear.
Any help or suggestions?
Thanks
Bootloop
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Aggiedude said:
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Click to expand...
Click to collapse
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
lvpre said:
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
Click to expand...
Click to collapse
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
XMayhem2099 said:
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
Click to expand...
Click to collapse
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
elesbb said:
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
Click to expand...
Click to collapse
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
lvpre said:
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
Click to expand...
Click to collapse
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed?
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
elesbb said:
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD.
Click to expand...
Click to collapse
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
Click to expand...
Click to collapse
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed? .
Click to expand...
Click to collapse
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
Click to expand...
Click to collapse
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
lvpre said:
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
Click to expand...
Click to collapse
Yeah I am currently rooted with the U firmware BL4. I want to upgrade to Oreo, hoping for performance improvements, better battery, etc. But I guess since the Oreo U firmware is still BL4, I can just downgrade if I can't get root back.
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
Click to expand...
Click to collapse
I never mentioned a bootloop? Is this about something else? The point I am trying to address is the loss of Sprint connectivity after flashing eng boot. This is because of the packages that need to be disabled.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
Click to expand...
Click to collapse
So you flash everything, eng boot, and are currently rooted. You then flash the provided file via flash fire, factory reset, and now you no longer are able to connect to Sprint network? When you say "can't connect to Sprint network", are you referring to data or to Sprint network entirely? If you go under your "about phone" section, what does your IMEI and phone number display? Don't actually type it here, but it should be something comprehensible. It shouldn't say "unknown" or a bunch of zeros, etc. [/quote]
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
Click to expand...
Click to collapse
True..
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
Click to expand...
Click to collapse
I do. A lot of people want to be back to BL4. There is NO difference in the newer bootloaders EXCEPT a special "key" type of thing that prevents downgrading. That is the only thing different. This is why the U firmware is still on BL4 despite having an Oreo update. Sprint changes the BL version just so people like us have extra hurdles to overcome when we want something different. Its very stupid tbh.
But, I would like to help you guys out, however, I AM NOT upgrading to the BL5/6. Noway nohow.
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
lvpre said:
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
Click to expand...
Click to collapse
Hmm. That's weird. What does your about phone section say for IMEI and phone number? Everything good? I wonder if something is affecting the PRL. Try updating that via settings menu before you flash the firmware and factory reset. The CSC shouldn't really affect that part. I have changed mine multiple times to just eff around and see what/if anything changed. Its more for the phone to know what menu options are available and such. For instance, call recording shows up when its not a US branded carrier.
Sadly I will never flash the newer BL. But I will definitely keep trying via the thread and if you would like to discord or something similar I would be down. School starts in about 2 weeks so I'm basically free till then
sim boot loop
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Aggiedude said:
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Click to expand...
Click to collapse
Thanks for posting this!!! I'm glad that I wasn't the only having this issue. I tried it again using a different method and still got the SIM boot loop. This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Anyway, hopefully, someone else will be able to figure this out.
Hi, I get a notification to update magisk. then I update it and use the recommended action to update it. After that it asks me to reboot the device. After rebooting the device it goes to fastboot only. And I see the device now changes to US996 while what I have is H990DS.
Can someone explain to me what's wrong and how to fix it without losing all my data?
thanks...
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
aliks00 said:
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
Click to expand...
Click to collapse
It's common knowledge that if you root your phone you never apply an OTA
Sent from my LG-H910 using XDA Labs
cnjax said:
It's common knowledge that if you root your phone you never apply an OTA
Click to expand...
Click to collapse
Thanks, but who said I ever applied an OTA? It was magisk that wanted to update itself, I've been performing magisk updates regularly for quite some time and never had a problem, in fact I can't even perform an OTA phone update as I have AT&T variant but with a different sim...
Other times, when updating magisk, I lost root but never lost the ability to boot...
I was running alpha-omega oreo with mk2000 kernel and updating rom, kernel and magisk regularly through TWRP (or direct install in case of magisk though magisk app) and never had this problem before... at least I can manage to boot from recovery/TWRP so hopefully I will soon manage to get things working again... that is, if I can copy some images to my SD card that windows insists that is corrupted but that's another story...
I ended up flashing whole rom again and everything is back to normal