Related
Hi All
I was wondering whether someone could tell me whether this is likely to work before I spend hours trying...
My situation is that the echo / muffled voice issue is a CONSTANT issue for me - I bought on a contract rather than through Google, so would have to return to Huawei directly for "repair" - which I've already done once and pretty sure they just sent the phone back to me. Besides, I don't have a spare phone and setting up the phone again every time is a pain, especially as I use it for work and need to involve our IT to register and install [email protected]
It's this latter point which prevents me from rooting - the software audits and reports on rooting - so it'd get blocked and I'd get a slap on the wrist. Using RootCloak or similar is also not an option I'm willing to go down (my company deals in security things so this wouldn't go down well at all!).
So what I'm aiming to do is:
Modify build.prop to turn the noise cancelling mic off
Without wiping my device and having to install all my apps again
Without rooting
I've come across this: How to edit build.prop without root and I'm interested in whether the approach without root would work?
In short, it would involve booting into a custom recovery (TWRP?) temporarily through fastboot (without unlocking the bootloader as that wipes all my data), and then modifying the file via adb.
So - does anyone know whether this is a feasible option on the 6P?
Thanks!
What you may be able to do is unlock the bootloader. Once unlocked you can flash twrp recovery on the device (however do not root it when it asks if you want to). Then from there you should be able to pull and push a modified build.prop. However you will have to wipe your device in order to make it happen. That is the only way I could think of since the bootloader has to be unlocked in order to edit files on the nexus.
This won't work, even using adb to modify system files requires root.
Long story short: you can't do it. I'm pretty sure even using adb to modify system files requires root.
Grr - So I'm either stuck with a phone that I can use for emails / calendar for work, but doesn't work as a phone - or I have to root to make it work as a phone, but not use it for work
I'm not sure I have the energy or desire to keep sending this back for repair, only for them to not fix anything - it seems that some units just work, others don't.
OP, were you ever able to resolve this issue?
I have the same problem, got a replacement from Huawei for the bootlooping issue (same IMEI as before) and have the horrible microphone issue and don't want to root it.
I want to try the build.Prop quora.com thing as well but that is the only reference I have seen that claims to allow modification without root.
So, I'm having a particularly strange issue here. I recently got this Sprint Note 4 and activated it. However, there appears to be a missing option under settings. Tethering and Hotspot is straight up gone. To clarify, I have pictures attached showing the item listing, and one without it.
Clarifications of troubleshooting I've tried so far:
I have attempted a factory reset of the device
I have attempted to do a reset with ##72786#
I have tried updating Profile, PRL,
I am using a DeOdexed PH4 6.0.1 ROM. I have tried reflashing per instruction (triple wiping Cache, Dalvik, Internal, System, etc)
I have tried flashing a STOCK OTA PH4 ROM to see if it would show up there. It does not.
I called Sprint technical support to reprovision my phone. They pushed out a a reprovisioning that I accepted. No change.
At one point, Wanam/Xposed was attempted to be installed. I checked for system/csc/features.xml. It was not there
http://forum.xda-developers.com/note-4-sprint/development/rom-stock-ph4-bloated-deodexed-t3473610/ is the custom ROM i'm using. However, it doesn't seem like a ROM specific issue.
If I use Activity Launcher or itools, i can access the actual wifi hotspot MENU (the toggle off and on, LAN settings, etc). I can enable it and the system will broadcast the SSID. However, if I try connecting to it, no devices are able to successfully connect.
here is the Activity Launcher referenced, for other readers:
http://forum.xda-developers.com/showpost.php?p=66713935&postcount=7
but anyways, regarding devices not being able to connect, sometimes the data connectivity (through hotspot only, not for the entire phone) will go dead if you don't start using it immediately after first unlocking and activating tether.
in my experiences, if you keep data alive by immediately connecting a device after your first time turning tether on (after unlock) by downloading a large file or somewhat frequently reloading web pages (on the connected device!) -- anything that will keep data sending and receiving -- it will stick, and the data service to connected device issues will stop.
it's not foolproof, it's not a silver bullet, but this is the method to the madness I have learned and worked for me many times when changing roms and even getting new phones.
it's been a couple months since I had to fiddle with it last, so I can't remember if it was necessary to re-unlock after a failed attempt at keeping data alive. you might only have to toggle data off then back on for another attempt.
when I had the problem of connected devices losing internet access, it would only happen after having worked for a few seconds to a few minutes. it'd work then abruptly stop, and this is my "fix"
My issue seems more in line with the devuces failing to validate to begin with. Not losing connection.
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
beezar said:
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
Click to expand...
Click to collapse
The very very very first time, I OTA'd to PH4. The next two tries were wiping completely and using the PH4 tar file. So both methods have been attempted.
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Sterist said:
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Click to expand...
Click to collapse
I thought you meant loss of internet connection in the sense of anti-tether provisioning from Sprint. My phone's LTE never goes down (and I am able to still browse the internet from the mobile device while tethering).
The connected devices never successfully "connect". They aren't listed as connected devices under the mobile hotspot. My other Android phone (without mobile data) is forever connecting. My macbook claims it has an assigned IP but is "unable to access the internet". So I'm not sure what the hell is going on with that.
At this point, I have restored my Note 3 as my active device until I get this resolved. I'm willing to re-write everything down to the barest metal I can.
Somebody in another topic mentioned something about PIT. I don't know anything about that sort of thing. My knowledge extends about as far as installing recovery and flashing ROMs.
I'm confident I could follow procedure, but could use a guiding hand on where to go from here.
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Sterist said:
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Click to expand...
Click to collapse
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Gamemaster1379 said:
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Click to expand...
Click to collapse
Just a thought and question: when you Odin stock tar to recover from this condition, are you using the rooted extended power menu to boot to download mode? Or, do you prevent the auto reboot of stock tar flash with Odin options?
A noted developer, @idone from Galaxy Tool app, once shared with me that rooted shortcut or preventing auto reboot can prevent the normal flash of Odin booting to recovery momentarily to set csc options. csc options flashed may not restore on any boots if you skip that initial auto boot.
The suggested method is to power down and pull battery for 30 seconds our more before reinserting battery and manually booting to downloaded mode. And do not uncheck auto reboot or pull battery but use Odin defaults and let phone auto boot. Doing this allows the phone to boot into recovery to do its thing briefly before booting system. I usually just let it perform the setup wizard and didn't activation just in case.
I rarely do the the data profile update or PRL because if letting the phone setup this way and phone prompts to reboot later, I believe this all done. But since this may allow ItsOn to bootstrap initialize, after flashing TWRP and backing up, I wipe internal memory and factory reset before flashing a custom ROM. Data format is optional; I don't always do that.
But if you do all that and don't see hotspot in Settings of stock, that's a problem. Maybe from dead stock, try KIES or Smart Switch to restore latest stock and check again?
Sent from my SM-N920P using Tapatalk
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 everyone.
I just recently got a used S5e, mostly for the Dex capability. I am a consultant, so sometimes I'm in a location where I need a desktop, but don't always have room for my 15" laptop. I haven't had a Samsung device in years... preferring brands with easy root and a nearly limited skinning (currently, OnePlus devices... basically).
I had kind of resigned myself to not having root on this device, since it is a Samsung, so I was surprised when I came on here to see if anyone else was having the update problem, I found root threads. Currently, my device looks like it's on the May 2019 update (One UI 1.1, Android 9, Build PPR1.180610.011.T720XXU1ASED).
Still trying to resist rooting the device, especially since I saw the no-root debloat thread. But I would like to know how to get this stupid thing updated. From what I've read, it has to do with an XML file containing a Samsung URL that returns a 404 when queried manually. The software updater doesn't reflect that, though... and just says you're up-to-date.
So if I can root this and flash a debloated ROM, that would serve a few purposes. Otherwise, if there's a way to force an OTA (or find it and download it to the SD card), that would be fine, too.
Any advice.
Flapjack said:
Hi everyone.
I just recently got a used S5e, mostly for the Dex capability. I am a consultant, so sometimes I'm in a location where I need a desktop, but don't always have room for my 15" laptop. I haven't had a Samsung device in years... preferring brands with easy root and a nearly limited skinning (currently, OnePlus devices... basically).
I had kind of resigned myself to not having root on this device, since it is a Samsung, so I was surprised when I came on here to see if anyone else was having the update problem, I found root threads. Currently, my device looks like it's on the May 2019 update (One UI 1.1, Android 9, Build PPR1.180610.011.T720XXU1ASED).
Still trying to resist rooting the device, especially since I saw the no-root debloat thread. But I would like to know how to get this stupid thing updated. From what I've read, it has to do with an XML file containing a Samsung URL that returns a 404 when queried manually. The software updater doesn't reflect that, though... and just says you're up-to-date.
So if I can root this and flash a debloated ROM, that would serve a few purposes. Otherwise, if there's a way to force an OTA (or find it and download it to the SD card), that would be fine, too.
Any advice.
Click to expand...
Click to collapse
If I'm understanding you right, you just want an OTA update applied? If that's the case, Frija is what you want to get the latest firmware for your device, and Odin will be your flasher. For stock rom flashes you don't even need an unlocked bootloader, much less root!
There are a ton of guides for Odin available, but still, if you have any questions please post!
Thanks for the reply!
I've used Odin quite a bit in the past, but I do know different situations need different files, so I'll probably do a quick refresher.
As for root, it definitely is a nice-to-have, mostly to remove bloatware, but if the debloat thread here works pretty good (and someone has info on just how much I can remove and keep Dex functionality), I would love to know that as well.
So, I am having a new problem. Using Frija, I downloaded the latest update. However, no matter what I do, I can't get a PC to recognize the tablet in download mode. It just says something about Windows not being able to recognize the device. In Device Manager, it says: "Device descriptor request failed". I've tried with and without the Samsung drivers, with three different USB cables, on two different PCs.
I'm worried that something is physically wrong with the USB port. That doesn't really make sense, though... as it charges fine, and shows up in Windows correctly once it's fully booted to Android.
**EDIT**
False alarm. I needed to press "up" again after getting into download mode and connecting the PC. So odd. It's updating now!
Hello, I am trying to unbrand my LTE Tab A from Sprint SM-T517P by flashing another CSC, or flashing another PIT on a patched version of ODIN with no success.
Can anyone tell me how to do it properly? I have read about Chimera, and Samkey, but they are too expensive, and I worry about bricking my LTE tablet (do not want to root, and there is no root anyway).
Any help?
I made little progress. I think I got the latest correct firmware for it downloaded, but it didn't want to flash with a patched Odin, but it did flash successfully with a non patched version of Odin.
After that, I tried flashing a CSC from another firmware of an LTE that is unbranded (SM-T515), but I always get a SECURE CHECK FAIL PIT error.
Does that mean I need to unlock the bootloader? Is that even possible? I wonder how Chimera, or Samkey is able to change CSC thru just software, but they are too expensive for me
Any help?
I soft bricked the tablet by flashing the AP, CP, and CSC of the latest firmware of International unlocked model SM-T515... I was able to recover by flashing its latest firmware for SM-T517P.
I worry about hard bricking it, but after so many tries with different things, I feel so close
Flashing only the CSC of any other firmware hasn't worked so far, and flashing anything other than Android 10 Q doesn't work either, even after unlocking bootloader.
I have NOT flashed bootloader of another firmware yet, super worried I may hard brick it if I flash another BL even after unlocking its bootloader.
hmmm i dont think there are many modifying the sm-t517p. i also own one of those on t mobile . i wanted to add twrp and root ....i cant seem to find any version made for it...so onto the magisk played with thatfor a couple days and locked it up a few times ...i think for now ill be okay with no modding ..idk why im compelled to screw p a perfectly fine working tab-phone. i did however just see that kali linux can be run on it without messing the os up..maybe ill ry that next... why did you want to modify yours? so you could switch carriers im guessing? luckily for me t-mobile took over sprint........just curious
bootloader unlock...
Unlocking BootloaderUnlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Crystaltransistor said:
hmmm i dont think there are many modifying the sm-t517p. i also own one of those on t mobile . i wanted to add twrp and root ....i cant seem to find any version made for it...so onto the magisk played with thatfor a couple days and locked it up a few times ...i think for now ill be okay with no modding ..idk why im compelled to screw p a perfectly fine working tab-phone. i did however just see that kali linux can be run on it without messing the os up..maybe ill ry that next... why did you want to modify yours? so you could switch carriers im guessing? luckily for me t-mobile took over sprint........just curious
Click to expand...
Click to collapse
Hi, I also have a sm-t517p and have searching to find twrp and root. So you had no luck at all? No root even with magisk?