Related
i have the international i9500 and i wanted to flash stock firmware to remove the bloatware and i tried to flash the stock rom with the adonis.pit and i checked re-partition .
when the flash was finished the bloatware wasn't removed and the boot anmation didn't revert back to the samsung animation and the phone also remembered my wi-fi password considering the fact i re partiotioned and wiped data.
how can i flash a stock rom without the bloatware (i'm from israel)
on sammobile there was the following options:
israel (cellcom)
israel (orange)
and israel (ILO) which is the stock one without the bloatware and when i flashed it the bloatware wasn't removed
Flash a stock firmware without PIT and without repartition.
Then use TrulyClean script to remove all the bloatware.
ignaciojn said:
Flash a stock firmware without PIT and without repartition.
Then use TrulyClean script to remove all the bloatware.
Click to expand...
Click to collapse
i flashed again without pit and without pepartition but the boot animation is still the carrier boot animation and not the samsung one as it should be.
will the trulyclean script restore the regular samsung boot animation?
oh and even after i reflashed without the pit and without the repartition it still remembered my wi-fi pass?! how do you explain that?
let me explain with a more basic explanation:
i bought the phone and the current rom was the cellcom branded rom (one of our carriers)
so i jumped to samfirmware and downloaded the israel/ILO which is an unbranded one
and flashed it the way you said (w/o pit and w/o re-partition) but the bloatware was still installed even after i did a factory wipe.
HOW COULD IT BEEE????
LSGio said:
i flashed again without pit and without pepartition but the boot animation is still the carrier boot animation and not the samsung one as it should be.
will the trulyclean script restore the regular samsung boot animation?
oh and even after i reflashed without the pit and without the repartition it still remembered my wi-fi pass?! how do you explain that?
let me explain with a more basic explanation:
i bought the phone and the current rom was the cellcom branded rom (one of our carriers)
so i jumped to samfirmware and downloaded the israel/ILO which is an unbranded one
and flashed it the way you said (w/o pit and w/o re-partition) but the bloatware was still installed even after i did a factory wipe.
HOW COULD IT BEEE????
Click to expand...
Click to collapse
NVM problem Solved
you should also tell the solution, and mark the thread as solved. this way, other users can solve the problem without opening a new thread
okty2k said:
you should also tell the solution, and mark the thread as solved. this way, other users can solve the problem without opening a new thread
Click to expand...
Click to collapse
Ok so there was an error in sammobile servers and the ILO firmware and the cellcom one are the same so that's why i had all the cellcom bloatware
and can you please tell me how to mark the thread as solved?
Hi,
I bought an S4 which was previously rooted. Last owner unrooted it and used triangle away to make sure all was as stock looking as possible.
Last week I did a factory reset on the phone as I was having issues with it. After the reset it shows all the stock apps and standard Rogers bloatware. BUT it now has a couple of Bell Bloatware apps as well!!!
I need to send the phone in for repair as I am getting "intermittent SIM card not detected, phone is restarting error". Should I be worried that Samsung will detect that the phone was at one time rooted?
What should I do?
Thanks
rezadue said:
Hi,
I bought an S4 which was previously rooted. Last owner unrooted it and used triangle away to make sure all was as stock looking as possible.
Last week I did a factory reset on the phone as I was having issues with it. After the reset it shows all the stock apps and standard Rogers bloatware. BUT it now has a couple of Bell Bloatware apps as well!!!
I need to send the phone in for repair as I am getting "intermittent SIM card not detected, phone is restarting error". Should I be worried that Samsung will detect that the phone was at one time rooted?
What should I do?
Thanks
Click to expand...
Click to collapse
When the last owner unrooted the phone, they likely used one of the odin files from here which are all Bell based for I337M (Canadian S4). There is a thread in here where this happened to another user and they returned the phone to stock Rogers instead of Bell, you will need to search for that thread. The bigger concern is Knox is probably tripped on the phone, when it boots up there will be some tiny text it the top left corner, yellow and red I believe, there is a thread about that here too.... If Knox is tripped (pretty sure it is) then all you can do is try to get it repaired by Samsung, I wouold be interested to find out if they do it or not.....
Thanks for the reply.
I shut the phone down and then turned it back on, paying close attention to evenrything. There is no small text in any corner. What is odd id that the phone goes through its boot sequence, gets to the lockscreen, and then goes through the boot sequence again a second time.
And for clarification, I have all the Rogers bloat, but I have three Bell bloat apps too!
I will do a search again to see if I can find the threads you have mentioned.
Gage_Hero said:
When the last owner unrooted the phone, they likely used one of the odin files from here which are all Bell based for I337M (Canadian S4). There is a thread in here where this happened to another user and they returned the phone to stock Rogers instead of Bell, you will need to search for that thread. The bigger concern is Knox is probably tripped on the phone, when it boots up there will be some tiny text it the top left corner, yellow and red I believe, there is a thread about that here too.... If Knox is tripped (pretty sure it is) then all you can do is try to get it repaired by Samsung, I wouold be interested to find out if they do it or not.....
Click to expand...
Click to collapse
rezadue said:
Thanks for the reply.
I shut the phone down and then turned it back on, paying close attention to evenrything. There is no small text in any corner. What is odd id that the phone goes through its boot sequence, gets to the lockscreen, and then goes through the boot sequence again a second time.
And for clarification, I have all the Rogers bloat, but I have three Bell bloat apps too!
I will do a search again to see if I can find the threads you have mentioned.
Click to expand...
Click to collapse
You have to go into download mode to see the text.
Sent from Black<3's I337 running Foxhound ROM
Put the phone in download mode and no small text.
Now that the phone is not rooted, can I put it in download mode, attach it to a PC and flash a stock Rogers 4.3 ROM via ODIN? Do I need root for this?
rezadue said:
Oh, and one other question. Now that the phone is not rooted, can I put it in recovery mode, attach it to a PC and flash a stock Rogers 4.3 ROM via ODIN? Do I need root for this?
Click to expand...
Click to collapse
Not to ODIN it no. Root not required.
Found the other thread, you have spoken of. It seems like that guy got bloatware from Bell INSTEAD of Rogers. I have blaotware from Rogers(ok
) AND Bell(Not ok).
http://forum.xda-developers.com/showthread.php?t=2422497
Almost same issue here on my N900W8. My phone is working fine and rooted, except I got the Rogers AND Bell apps too before rooting and flashing CWM (only way I knew of at the time to force boot following seandroid enforcing error). I data wiped, downloaded and flashed the labeled "Rogers" stock ROM from SamMobile, and first time I ever saw bloatware from two carriers on any phone.
I disabled the Bell apps thinking that was all, but instead of 4G, I get H+. LTE connects fine outdoors, but H+ seems slightly slower than the 4G I'm used to. Which makes me wonder if LTE speeds are impacted too, hope not. Anyway, it's a bother because I am rarely in an LTE zone.
Tomorrow, I will try unrooting with SuperSU (is this even important if I'm wiping & flashing?), data wiping with CWM, re-flashing same file from SamMobile and not flashing anything more, and trying emergency recovery with Kies. Anyone know if this will work or change anything in the end? Or is Kies 3 also affected by the Knox counter? CSC (OYA) is the same as the non-rooted up-to-date S4 in the house.
Thanks
OP, have you tried using someone else's SIM card? Just a thought.
I successfully rooted my Samsung Galaxy A8(Indian variant A800F). While experimenting withe the DPI values by ROM Manager's build.prop editor I made the mistake of changing it to 160. So all the UI elements were gone(Icons, Notification Bar, etc).
Then I had the bright Idea of resetting the phone which somehow did not revert to the original DPI settings. This in turn disabled USB Debugging and now I'm unable to use ADB. Moreover the FRP Lock is turned on too so I guess Download Mode won't work either.
The only thing I can do right now is taking screen shots and turning the phone off(Shutdown Dialogue Box is visible too). I did not take a backup at the time nor did I flash any recovery.
Hope I made my issue clear.
Now what options do I have left?
Can re-flashing the firmware do the trick?
Would the Samsung service centre guys re-flash the firmware even after the KNOX getting tripped off. Or I'll have to do that myself?
Any sort of help is highly appreciated. Thanks!
Yes you should be able to flash stock firmware again but no guarantee it'll work. All you need to do is get the original firmware from sammobile and Odin, downloaded both, extract all the Odin files to your PC, also extract the md5.tar file from the firmware zip, boot to download and connect, if it connects then that's a start, once connected click "ap" box and choose the firmware you just downloaded, wait a couple of mins for Odin to check the md5 is correct then hit start.
Sent from my SM-A500FU using XDA-Developers mobile app
Great. Will try that and post the results.
Just wanted to ask if this manual procedure may somehow make my situation even worse. Or is it completely safe to flash?
Really don't want to get into a deeper mess.
And thanks for the quick response
sanu23kumar said:
Great. Will try that and post the results.
Just wanted to ask if this manual procedure may somehow make my situation even worse. Or is it completely safe to flash?
Really don't want to get into a deeper mess.
And thanks for the quick response
Click to expand...
Click to collapse
Completely safe, that's the beauty of ODIN.
sanu23kumar said:
I successfully rooted my Samsung Galaxy A8(Indian variant A800F). While experimenting withe the DPI values by ROM Manager's build.prop editor I made the mistake of changing it to 160. So all the UI elements were gone(Icons, Notification Bar, etc).
Then I had the bright Idea of resetting the phone which somehow did not revert to the original DPI settings. This in turn disabled USB Debugging and now I'm unable to use ADB. Moreover the FRP Lock is turned on too so I guess Download Mode won't work either.
The only thing I can do right now is taking screen shots and turning the phone off(Shutdown Dialogue Box is visible too). I did not take a backup at the time nor did I flash any recovery.
Hope I made my issue clear.
Now what options do I have left?
Can re-flashing the firmware do the trick?
Would the Samsung service centre guys re-flash the firmware even after the KNOX getting tripped off. Or I'll have to do that myself?
Any sort of help is highly appreciated. Thanks!
Click to expand...
Click to collapse
you can flash it with service firmware (that means the firmware that one have all the file separately,pda csc cp bl pit) from,joomla or any other forum. it will reset the phone to its factory state.in ksa knox counter tripping not void the warranty.you can take the phone to any customer care without any problem.
How did you rooted it?
sanu23kumar said:
I successfully rooted my Samsung Galaxy A8(Indian variant A800F). While experimenting withe the DPI values by ROM Manager's build.prop editor I made the mistake of changing it to 160. So all the UI elements were gone(Icons, Notification Bar, etc).
Then I had the bright Idea of resetting the phone which somehow did not revert to the original DPI settings. This in turn disabled USB Debugging and now I'm unable to use ADB. Moreover the FRP Lock is turned on too so I guess Download Mode won't work either.
The only thing I can do right now is taking screen shots and turning the phone off(Shutdown Dialogue Box is visible too). I did not take a backup at the time nor did I flash any recovery.
Hope I made my issue clear.
Now what options do I have left?
Can re-flashing the firmware do the trick?
Would the Samsung service centre guys re-flash the firmware even after the KNOX getting tripped off. Or I'll have to do that myself?
Any sort of help is highly appreciated. Thanks!
Click to expand...
Click to collapse
How did you rooted it?
I used Smart Switch to unbrick after a having a FRP lock bootloop
Hi guys!
So I have a S7E 935F unlocked.
I tried to root the device and did everything as written and shown in every tutorial but it failed to do so.
After flashing recovery TWRP and trying to flash SuperSU the device just got into a boot loop.
I was reading around and understood that this is a problem due to encryption of the FS.
So I downloaded my firmware from sammobile and flashed my device again, everything got back to normal.
Well, almost normal. The rom I have has the same build number, version, kernel, everything is the same as the original one only that I have things in the settings menu I never has, like I have "apps" twice, one for apps permissions etc and one for apps manager, I also have "T roaming" no idea what it is, never had it, I have "service provider KT twophone".
Also the settings app crash a lot, browser gets stuck a lot, can't change system language to English (app crash).
At the home screen I Samsung Pay which I never had and I have some sort of a news app integrated on my home screen and it's marked with two stripes.
I verified this is a global rom for my country, not by any mobile company as before, I really don't have a clue what to do.
Can someone please advise?
T roaming and KT twophone service are both from korean carriers, maybe you have a wrong CSC installed or your /efs/imei/mps_code.dat is messed up.
Try to download and install the latest firmware of your region using Samfirm and if it still doesn't solve the problem, open up /efs/imei/mps_code.dat and see if matches your region name.
OK so I D/L the firmware again and same thing...
I checked /efs folder and its empty, maybe the content is hidden? Anyways my device has its IMEI and I can use it to make calls... thoughts?
roeio82 said:
OK so I D/L the firmware again and same thing...
I checked /efs folder and its empty, maybe the content is hidden? Anyways my device has its IMEI and I can use it to make calls... thoughts?
Click to expand...
Click to collapse
You need smart switch on your pc, enter your imei number in smart switch and it will download correct firmware according to your imei, then flash it. Good Luck
Sent from my SM-G935F using Tapatalk
Hi the same thing happend to me in settings but did downloading the firmware via smart switch change the settings and if so how do you do this
Tommmy5555 said:
Hi the same thing happend to me in settings but did downloading the firmware via smart switch change the settings and if so how do you do this
Click to expand...
Click to collapse
Hello, this smart switch method is obsolete. Use odin to re-flash your stock rom in case of any issues. Be sure to use correct and matching binary firmware.
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.