Related
I have a Lg G3 F460k10i and the sim tool kit (stk) is not visible in the apps drawer although its visible in the settings>apps>activities.Have tried installing it from the system files, but I aint successful. How can I get it to work since I highly depend on it for the network operations in my region?
theolin82 said:
I have a Lg G3 F460k10i and the sim tool kit (stk) is not visible in the apps drawer although its visible in the settings>apps>activities.Have tried installing it from the system files, but I aint successful. How can I get it to work since I highly depend on it for the network operations in my region?
Click to expand...
Click to collapse
did you find out of this?
im googling like h*** now, apparently i need this to get a service from my bank up and running.
Edit:
just ordered a new simcard as is saw that this helped some users.
will report back to u.
After flashing TWRP and Venom3.0 I started testing the various ROMs. Of course I was on a very small 8GB Micro after my SanDisk 64GB went corrupt (3years and a few washing machine and drier cycles) and made a newb move. Didn't think to save a backup pre/post unlock to the internal and just copy it onto my PC.
It wasn't until the next day that I realized I wasn't receiving calls. The phone would ring on the callers end but my phone would stay unaffected unless a vm was sent. I searched in the m9 and then overall xda for a solution to no avail. Once I used Gsearch with more vague terms I was only able to find one thread from a few years back when voice over LTE must have been kinda new.
Someone had the exact same problem, described my situation exactly and the fix proposed worked for the guy.
It was to modify the default.XML in system/customize/ACC
I switched all the "voLTExxx" values to "true" as they were all "false" and now callers are directed straight to vm. Im still completely unaffected in my phone abilities so I know I was close. All this is after I switched the the ATT dev edition ROM found here on XDA in one of the M9 stickeys.
Im thinking maybe someone with the same setup could upload their XML file that is working so I can check if it was that? Maybe that won't work but you know what will? Thanks guys.
Im seeing someone else posted just a few minutes ago and turning off LTE works. That is not a solution in my opinion and was the failsafe on the original post I read.
SeanMurphy said:
After flashing TWRP and Venom3.0 I started testing the various ROMs. Of course I was on a very small 8GB Micro after my SanDisk 64GB went corrupt (3years and a few washing machine and drier cycles) and made a newb move. Didn't think to save a backup pre/post unlock to the internal and just copy it onto my PC.
It wasn't until the next day that I realized I wasn't receiving calls. The phone would ring on the callers end but my phone would stay unaffected unless a vm was sent. I searched in the m9 and then overall xda for a solution to no avail. Once I used Gsearch with more vague terms I was only able to find one thread from a few years back when voice over LTE must have been kinda new.
Someone had the exact same problem, described my situation exactly and the fix proposed worked for the guy.
It was to modify the default.XML in system/customize/ACC
I switched all the "voLTExxx" values to "true" as they were all "false" and now callers are directed straight to vm. Im still completely unaffected in my phone abilities so I know I was close. All this is after I switched the the ATT dev edition ROM found here on XDA in one of the M9 stickeys.
Im thinking maybe someone with the same setup could upload their XML file that is working so I can check if it was that? Maybe that won't work but you know what will? Thanks guys.
Click to expand...
Click to collapse
The dev edition (617) ruu won't fix the issue. As far as voLte is concerned, it's basically the same as running a custom rom in that you can still be affected by the issue and you can't disable Ehanced (or HD) Voice in the rom (this is tied to your sim and not the rom, I think).
Currently, this is the best solution, I think...flash an att RUU (502 - either 1.32 or 2.6, it doesn't really matter) . Then go into Mobile network settings, and disable Enhanced Voice. Once this is disabled in stock ATT rom, you can flash a custom rom and that setting should stick.
Alternatively, you might try getting on with ATT support to see if they can disable that setting on their end.
Okay. Maybe post this to the thread from 8hrs ago because some of them are having the same issue. Ill get back when I try that, I am on 1.32 currently.
Quick questions before I proceed.
jollywhitefoot said:
The dev edition (617) ruu won't fix the issue. As far as voLte is concerned, it's basically the same as running a custom rom in that you can still be affected by the issue and you can't disable Ehanced (or HD) Voice in the rom (this is tied to your sim and not the rom, I think).
Click to expand...
Click to collapse
1.Why do you think it this doesn't work after I unlocked? What I mean is, with that value set to true, and everything works fine; what is in the flash that doesn't allow HD Voice?
jollywhitefoot said:
Currently, this is the best solution, I think...flash an att RUU (502 - either 1.32 or 2.6, it doesn't really matter) . Then go into Mobile network settings, and disable Enhanced Voice. Once this is disabled in stock ATT rom, you can flash a custom rom and that setting should stick.
Click to expand...
Click to collapse
2. I'm currently on 1.32 and I don't see that option anywhere despite being on this ROM. Which is now clear that it isn't the same thing as this RUU? I'm downloading the 2.6 RUU from HTC's website and will flash it as per their instructions (Thanks for the link by the way:highfive
3.Should I re-edit my XML file before the flash or is this RUU going to take care of that?
Also, I had to idea the info about your post wasn't copied in the text when I reposted this to that other thread. I'll delete if you prefer.
SeanMurphy said:
1.Why do you think it this doesn't work after I unlocked? What I mean is, with that value set to true, and everything works fine; what is in the flash that doesn't allow HD Voice?
2. I'm currently on 1.32 and I don't see that option anywhere despite being on this ROM. Which is now clear that it isn't the same thing as this RUU? I'm downloading the 2.6 RUU from HTC's website and will flash it as per their instructions (Thanks for the link by the way:highfive
3.Should I re-edit my XML file before the flash or is this RUU going to take care of that?
Also, I had to idea the info about your post wasn't copied in the text when I reposted this to that other thread. I'll delete if you prefer.
Click to expand...
Click to collapse
it didn't have anything to do with unlocking. You have voLte enabled for your att account and you're in an area that supports voLte, but you're running a rom that doesn't.
This is just my current theory. We'll see if it works for you.
I don't know what it will take for a custom rom to support voLte.
I didn't include a link because I thought it would be easy enough to find, but I guess most people here complain if they're not spoon fed.
Um...credit the source of the info or just link to my post. Don't just copy and paste as your own.
Anyway...carry on and please report back if it works for you.
Edit: oh, and forget the default.xml file. It's probably fine as is. I assume you got that from my post from a couple of months ago. I don't think that was the problem.
jollywhitefoot said:
it didn't have anything to do with unlocking. You have voLte enabled for your att account and you're in an area that supports voLte, but you're running a rom that doesn't.
This is just my current theory. We'll see if it works for you.
I don't know what it will take for a custom rom to support voLte.
Click to expand...
Click to collapse
Got it, is voLte an ATT exclusive feature in the U.S.?
jollywhitefoot said:
I didn't include a link because I thought it would be easy enough to find, but I guess most people here complain if they're not spoon fed.
Click to expand...
Click to collapse
You posted the link on the M9 resource thread where I was able to find it on my own, it was a genuine high five, and yes, I thanked that bit as well.
jollywhitefoot said:
Um...credit the source of the info or just link to my post. Don't just copy and paste as your own.
Click to expand...
Click to collapse
This is what I was attempting to explain; I'm not use to the XDA app UI and I didn't know it didn't include the info about the OP when I pasted in the text. Sorry for the confusion Jolly, I must've come off like the biggest assclown to ask for your time in a while. Your help IS appreciated and I have thanked some of your posts so far.
jollywhitefoot said:
Anyway...carry on and please report back if it works for you.
Click to expand...
Click to collapse
I'm stuck at the RUU actually, I have AV off and the install shield wizard loads up, flashed a few windows then shuts down. Sync is still installed, I've restarted my PC, ran as admin.
Do you know if HTC released that as a flashable .zip? I hate doing anything to my phone through my PC because it creates another variable to go wrong.
jollywhitefoot said:
Edit: oh, and forget the default.xml file. It's probably fine as is. I assume you got that from my post from a couple of months ago. I don't think that was the problem.
Click to expand...
Click to collapse
It was you
SeanMurphy said:
Got it, is voLte an ATT exclusive feature in the U.S.?
Click to expand...
Click to collapse
Yes, but only in some areas. Mostly larger cities right now
SeanMurphy said:
You posted the link on the M9 resource thread where I was able to find it on my own, it was a genuine high five, and yes, I thanked that bit as well.
Click to expand...
Click to collapse
Gotcha. I was like...what link?
SeanMurphy said:
This is what I was attempting to explain; I'm not use to the XDA app UI and I didn't know it didn't include the info about the OP when I pasted in the text. Sorry for the confusion Jolly, I must've come off like the biggest assclown to ask for your time in a while. Your help IS appreciated and I have thanked some of your posts so far.
Click to expand...
Click to collapse
No problem....just funny
SeanMurphy said:
I'm stuck at the RUU actually, I have AV off and the install shield wizard loads up, flashed a few windows then shuts down. Sync is still installed, I've restarted my PC, ran as admin.
Do you know if HTC released that as a flashable .zip? I hate doing anything to my phone through my PC because it creates another variable to go wrong.
Click to expand...
Click to collapse
It was you [/QUOTE]
I don't think there's a zip yet. I've had that happen a few times with ruu. Once it was antivirus. Another time or two it was a bad download.
jollywhitefoot said:
I don't think there's a zip yet. I've had that happen a few times with ruu. Once it was antivirus. Another time or two it was a bad download.
Click to expand...
Click to collapse
Wowwwwww was that an adventure.
Re-downloaded the ATT RUU and updating (bad download first time)
Disabled "HD Voice" under the mobile settings (easiest part of the whole show)
re-flashed TWRP (Ran into a million windows problems, had to perform clean windows install)
Flashed the same custom ROM I had before
Calls came through, everything working great.
Thanks again Jolly!!!!! I would be stuck with twitter eating 11% of my battery usage despite me not having a twitter account
:good::highfive::good::highfive::good::highfive:
This phone was given to me with marshmellow and im having the issue of not being able to update google play service among other things. the other issues im having might be the effect of the google play service. i just wanted to know if its worth attempting the downgrade on lollipop
shatheone said:
This phone was given to me with marshmellow and im having the issue of not being able to update google play service among other things. the other issues im having might be the effect of the google play service. i just wanted to know if its worth attempting the downgrade on lollipop
Click to expand...
Click to collapse
Depending on the underlying issue, you may still encounter the Play Services issue on Lollipop as you have on Marshmallow.
First, see if you can work the issue out on your current system.
- Delete cache and Data on Play Services.
- reset app preferences and reset default apps in the menu in the Apps folder in Settings.
- delete your Google account and re-install it.
- use LGUP-NEW to reinstall your Marshmallow rom (H81220). Check out this site for some H812 stock roms:
https://lg-firmwares.com/lg-h812-firmwares/
scroll down to the firmwares list and install the correct stock kdz - carrier and version
You can downgrade to Lollipop (H81210) using LGUP-NEW - frankly I haven't noticed a lot of difference between them but does have the current advantage of being rootable. Some members report better battery life but you will lose some security updates.
sdembiske said:
Depending on the underlying issue, you may still encounter the Play Services issue on Lollipop as you have on Marshmallow.
First, see if you can work the issue out on your current system.
- Delete cache and Data on Play Services.
- reset app preferences and reset default apps in the menu in the Apps folder in Settings.
- delete your Google account and re-install it.
- use LGUP-NEW to reinstall your Marshmallow rom (H81220). Check out this site for some H812 stock roms:
https://lg-firmwares.com/lg-h812-firmwares/
scroll down to the firmwares list and install the correct stock kdz - carrier and version
You can downgrade to Lollipop (H81210) using LGUP-NEW - frankly I haven't noticed a lot of difference between them but does have the current advantage of being rootable. Some members report better battery life but you will lose some security updates.
Click to expand...
Click to collapse
thanks for the reply, i actually did all of those things, including a factory reset. i will try to reinstall using lg up, maybe something in the stock image got corrupted? i learned that even if my phone boot loops, it wont be repaired as the serial number is out of range. so i might hold on to it until theres a good custom available
shatheone said:
thanks for the reply, i actually did all of those things, including a factory reset. i will try to reinstall using lg up, maybe something in the stock image got corrupted? i learned that even if my phone boot loops, it wont be repaired as the serial number is out of range. so i might hold on to it until theres a good custom available
Click to expand...
Click to collapse
Yes, very possible that something got corrupted. Definitely try a re-install of your stock kdz with LGUP-NEW.
If you haven't checked out steadfasterX's bootloader unlock thread, you will have to in order to install any custom rom with some assurance of success:
https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288
You might as well get started now as it won't be long before he publishes. You will have to install his SALT program and create a backup before proceeding to unlock your bootloader preparatory to installing any custom rom:
https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864
sdembiske said:
Yes, very possible that something got corrupted. Definitely try a re-install of your stock kdz with LGUP-NEW.
If you haven't checked out steadfasterX's bootloader unlock thread, you will have to in order to install any custom rom with some assurance of success:
https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288
You might as well get started now as it won't be long before he publishes. You will have to install his SALT program and create a backup before proceeding to unlock your bootloader preparatory to installing any custom rom:
https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864
Click to expand...
Click to collapse
i couldnt get LG up to recognize my phone even after taking out the battery, so ill have to find another usb cable and try that. i see two different kdzs for my software version so ill have to research the correct one. and im not planning one unlocking the bootloader until theres a better way. id sell it before risking a brick
shatheone said:
i couldnt get LG up to recognize my phone even after taking out the battery, so ill have to find another usb cable and try that. i see two different kdzs for my software version so ill have to research the correct one. and im not planning one unlocking the bootloader until theres a better way. id sell it before risking a brick
Click to expand...
Click to collapse
IF, you'd actually read steadfasterX's thread and in particular his latest update (last page on the thread, currently) ... you would realize there had already been a proof of a successful unlock of an H812. I suspect your phone has been screwed up by somebody who didn't know what they were doing in the first place. No one has done more work in this area and had more successes than steadfasterX - good luck for waiting for a better way or getting much trying to sell it - check ebay and see the prices - LOL.
sdembiske said:
IF, you'd actually read steadfasterX's thread and in particular his latest update (last page on the thread, currently) ... you would realize there had already been a proof of a successful unlock of an H812. I suspect your phone has been screwed up by somebody who didn't know what they were doing in the first place. No one has done more work in this area and had more successes than steadfasterX - good luck for waiting for a better way or getting much trying to sell it - check ebay and see the prices - LOL.
Click to expand...
Click to collapse
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
shatheone said:
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
Click to expand...
Click to collapse
The risk of bricking your phone has been minimized with steadfasterX's process - he has had a couple of successful unlocks of an H812 now and when he publishes it for the public, the risk will be minimized as much as it can be in any unlock case.
With respect to your phone not being recognized by LGUP-NEW. Make sure you have installed the LGMobileDriver_WHQL_Ver_4.2.0 available for download from the US LG site - the Windows driver will give you problems.
sdembiske said:
The risk of bricking your phone has been minimized with steadfasterX's process - he has had a couple of successful unlocks of an H812 now and when he publishes it for the public, the risk will be minimized as much as it can be in any unlock case.
With respect to your phone not being recognized by LGUP-NEW. Make sure you have installed the LGMobileDriver_WHQL_Ver_4.2.0 available for download from the US LG site - the Windows driver will give you problems.
Click to expand...
Click to collapse
well i wouldnt care doing it if there was more rom support, i dont see a point in unlocking at this point. if im missing a benefit of unlocking right now, enlighten me. and thats the driver i already have installed
shatheone said:
well i wouldnt care doing it if there was more rom support, i dont see a point in unlocking at this point. if im missing a benefit of unlocking right now, enlighten me. and thats the driver i already have installed
Click to expand...
Click to collapse
One benefit might be fixing your screwed up phone. Still didn't read the OP I guess as you were advised to in steadfasterX's bootloader unlock thread. Here's an idea ... before making summary judgements with little or no knowledge, perhaps you should check with the member that is sited in the "proof" for the H812 and post your questions there for the Roms he has tried. My understanding was that he was on Lineage for Nougat - the most popular downloaded custom rom for .... are you ready ... the H815/H811 - here's an idea ... why don't you check out ALL the roms that are for the H815/H811 in the Android Development section ... hmm ... really?
sdembiske said:
One benefit might be fixing your screwed up phone. Still didn't read the OP I guess as you were advised to in steadfasterX's bootloader unlock thread. Here's an idea ... before making summary judgements with little or no knowledge, perhaps you should check with the member that is sited in the "proof" for the H812 and post your questions there for the Roms he has tried. My understanding was that he was on Lineage for Nougat - the most popular downloaded custom rom for .... are you ready ... the H815/H811 - here's an idea ... why don't you check out ALL the roms that are for the H815/H811 in the Android Development section ... hmm ... really?
Click to expand...
Click to collapse
if you took 10 seconds, you would see i actually posed in that thread. and all they did was direct me to the OP which says nothing about lineageos working for h812, or that the h815/ or h811 roms work for this variant. all it says is that i can flash nougat based roms. so the thread isnt too helpful, im not sure why you think it is.
shatheone said:
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
Click to expand...
Click to collapse
Hey man, i'm agreeing with you for most of this...
I'm also not going to risk anything until 10 H812 users have successfully unlocked bootloader and flashed a custom rom (one thats intended for h815 or h811) with steadfasterx's method. Maybe you can flash H815 custom roms once the bootloader is unlocked... but just to be safe, let's flash other stock carrier firmwares in the meantime...... in the end no matter what anyone says, its your phone at risk...
Member TheLatios381 and I were asking same question here:https://forum.xda-developers.com/g4...10-q2-2017-t3567402/post75742903#post75742903 because no answer to our question on steadfasterx's thread...
Has anyone tried unlocking a T-Mobile g7 bootloader from the developer options? I've turned on developer options and OEM unlock option is in there but I haven't connected it to pc to check with ADB.
only the EU bootloader has been unlocked, something to do with TMO releasing some keys or something for the secuity, I believe. I know on HTCs I used to have TMO had certain encryption on wifi calling and a few signatures that were broken by touching the security partition needed to gain root and install custom OSs. Once LG updates their bootloader unlock page to include TMO version G7 (I have one, too) then we'll see a KDZ thread and then root
cohan1219 said:
Has anyone tried unlocking a T-Mobile g7 bootloader from the developer options? I've turned on developer options and OEM unlock option is in there but I haven't connected it to pc to check with ADB.
Click to expand...
Click to collapse
Root is unlikely on the T-Mobile variant due to T-Mobile using different RSA Encryption keys compared to every other carrier, also the development for this phone is basically one guy. I hope I'm wrong about it being unlikely but from what I've been reading and what I've been told it's a slim chance it's going to happen
Joe199799 said:
Root is unlikely on the T-Mobile variant due to T-Mobile using different RSA Encryption keys compared to every other carrier, also the development for this phone is basically one guy. I hope I'm wrong about it being unlikely but from what I've been reading and what I've been told it's a slim chance it's going to happen
Click to expand...
Click to collapse
Thanks for the update, I guess if there's not root by November its time to switch to the OnePlus 6T.
sharpknight said:
Thanks for the update, I guess if there's not root by November its time to switch to the OnePlus 6T.
Click to expand...
Click to collapse
I think the 6T is going to be on TMobile if that's the case I shall be doing the same, I do love this phone don't get me wrong but I've always wanted a one plus device and having root again would be great as well
that one guy is checking the bootloader again and trying to help us ive been taking to him hope he's right about them locking it the same way give it a little time he thought bootloader was unlocked he doesn't have the device there's others we can't give up man adb root is possible prob hacking laf maybe possible and there's a way someone will get it anyone trying to I'll also help to
Joe199799 said:
I think the 6T is going to be on TMobile if that's the case I shall be doing the same, I do love this phone don't get me wrong but I've always wanted a one plus device and having root again would be great as well
Click to expand...
Click to collapse
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.
20degrees said:
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.
Click to expand...
Click to collapse
Honestly I just want it for viper4android literally that's it and maybe greenify and adaway other than that I'm good.
Honestly I probably won't switch over I'll just deal with it
20degrees said:
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.
Click to expand...
Click to collapse
Greenify was the biggie to me particularly with the Xposed module. Titanium Backup. Disabling system apps that the UI wouldn't let me disable. (Maybe that can be done via adb w/o root. I should try.) BootManager. MinMinGuard. Worthwhile system-wide font replacement w/o bloat. (No apps, no junk, no "apps that don't support <thing> or <favorite font>", just replacing files in /system/fonts.)
Lots of other little things that -- added together -- made my phone just that much nicer to me.
I'm really happy with my G7 all around (except for the WiFi stability, that still sucks). I just wish I had all those little tweaks back.
I made a post about a week ago but never got any replies. Has anyone else ran the "fastboot flash unlock_critical" command? My phone restarts and shows the erasing screen but no actual bootloader unlock.
Any updates?
I'll try out when I make it back home sorry was flooded here we either need to mod kernel or laf aand github has a repo on some I'm checking on I'll be able to check more sorry and package disable pro will freeze apps or use autoprimes way on rooted you can use twrp file manager to delete system apps on moto z2 oem can't be touched but there's ways
the aristo 2 has different commands has anyone tried that way and we still need a twrp to flash their is thread about making one we can get somewhere this would be a great phone with root without it sucks
ecompton59 said:
the aristo 2 has different commands has anyone tried that way and we still need a twrp to flash their is thread about making one we can get somewhere this would be a great phone with root without it sucks
Click to expand...
Click to collapse
What are the different commands?
Okay I've tried the fastboot critical command same went to erase screen with the circle but fastboot flashing get_unlock_ability comes back 1 I've extracted kdz to dz still playing around trying
sign the petition to LG
https://www.change.org/p/lg-electro...ion&utm_term=b1c99c243f314531935fa8ffc92c4c4f
There is an option for the T-Mobile version. Can someone actually try continuing with the progress?
I can't since I don't have the T-Mobile version.
LGM710TM is LG G7 from Italian provider TIM.
It has nothing to do with T-Mobile.
awww
umminkug said:
https://www.change.org/p/lg-electro...ion&utm_term=b1c99c243f314531935fa8ffc92c4c4f
Click to expand...
Click to collapse
There's been petitions for like every locked-down LG device since the beginning of time. Never has it been effective, never will it be. LG doesn't reverse its bootloader locking policy.
Hi all,
Just want to make sure I am doing this correctly and ask a few questions on the way. I have ordered an unlocked Note 10+ direct from Samsung because I really wanted Aura Blue (plus totally bonkers pre-BF discounts). My understanding is that, as I use T-Mobile, the radios are not going to be optimized for T-Mobile's network, leading to crappier call quality, and some features will not work.
1. Is this correct?
If so, my understanding is that I can use Odin to flash the T-Mobile firmware without rooting or unlocking the bootloader, and this will allow the phone to work as though I purchased it from T-Mobile. Assuming that I have this right so far, I need to download and install Odin, download the most recent T-Mobile firmware from here: https://www.sammobile.com/samsung/galaxy-note-10-plus/firmware/SM-N975U/TMB/
and install according to the instructions on the page for "5 Files" (https://www.sammobile.com/samsung/g...e/SM-N975U/TMB/download/N975USQS2ASJ8/299552/).
2. So far so good? Do I have this right so far?
3. Sometimes my wifi gets wonky and file downloads get corrupted. Is there a way to ensure the integrity of the file before I install it onto my phone?
4. I understand that there will be a lot of Samsung and T-Mobile Bloatware. To remove this, I just follow these instructions via ADB, is that right?
https://forum.xda-developers.com/ga...msung-galaxy-note-10-note-10-debloat-t3964027
or these: https://android.gadgethacks.com/how-to/disable-bloatware-for-free-your-galaxy-note-10-10-0207598/
5. Anything I'm missing?
Thanks in advance for the help. I haven't used these programs since my Galaxy S3 so I'm quite rusty.
The directions look pretty accurate, but there's a few other things you will need to do.
Don't use the home_csc when flashing the Tmobile firmware to the device. Also you will want to place the userdata file into the correct spot on the odin flashing tool. The userdata contains all the carrier specific stuff.
Do a factory data reset before you flash the Tmobile firmware (to remove the FRP lock). After flashing the Tmobile firmware be sure to do another factory data reset to ensure things (OTA, etc) work properly.
As for the download you could try using samfirm and having it check the CRC32. Checking the CRC will double check the file integrity. I don't have samfirm anymore on my PC because I upgraded to the Note 10+, but someone else may have a link to a download (or you can google search it to locate it.. Which is what I did to obtain the app before).
As for the bloat I just uninstalled what apps I could that I didn't need, and for the others I used an app from Google Play Store to disable them. I do suggest that you try disabling apps first and not trying to remove them. If you remove the wrong app you will undoubtedly encounter issues/problems.
scottusa2008 said:
Don't use the home_csc when flashing the Tmobile firmware to the device. Also you will want to place the userdata file into the correct spot on the odin flashing tool. The userdata contains all the carrier specific stuff.
Click to expand...
Click to collapse
Okay, so use CSC_*** rather than HOME_CSC? Will Odin tell me about how to place the userdata into the correct spot?
scottusa2008 said:
Do a factory data reset before you flash the Tmobile firmware (to remove the FRP lock). After flashing the Tmobile firmware be sure to do another factory data reset to ensure things (OTA, etc) work properly.
Click to expand...
Click to collapse
Will I still need to do the factory data reset if I basically take it out of the box, make sure it works, and then flash it? Can't hurt, I guess, I just want to be clear about my timeframe on installation.
scottusa2008 said:
As for the download you could try using samfirm and having it check the CRC32. Checking the CRC will double check the file integrity. I don't have samfirm anymore on my PC because I upgraded to the Note 10+, but someone else may have a link to a download (or you can google search it to locate it.. Which is what I did to obtain the app before).
Click to expand...
Click to collapse
That's what it was! Checking the CRC32 hash. I remember now.
scottusa2008 said:
As for the bloat I just uninstalled what apps I could that I didn't need, and for the others I used an app from Google Play Store to disable them. I do suggest that you try disabling apps first and not trying to remove them. If you remove the wrong app you will undoubtedly encounter issues/problems.
Click to expand...
Click to collapse
Gotcha. Do you recall which app you used? I guess I could just hide them in a launcher app, too, but I am particularly miffed about the fact that Facebook apparently comes pre-installed and can't be uninstalled on the unlocked N10+ (though I do not have one in my hands and obviously can't confirm myself as a result).
Thanks!
XanRules said:
Okay, so use CSC_*** rather than HOME_CSC? Will Odin tell me about how to place the userdata into the correct spot?
Click to expand...
Click to collapse
Yes use the CSC_*** and not the HOME_CSC when flashing.
For the userdata you should see it when you look at the Odin interface. Essentially as you place the 5 individual parts into each appropriate spot in Odin, you should see the 6th spot labled userdata.
XanRules said:
Will I still need to do the factory data reset if I basically take it out of the box, make sure it works, and then flash it? Can't hurt, I guess, I just want to be clear about my timeframe on installation.
Click to expand...
Click to collapse
If you just take it out of the box, turn it on and do not add a Google Account to it then you can just skip the factory data reset.
If you just take it out of the box, turn it on and add a google account to it then you will want to factory data reset it before flashing it with the carrier firmware.
XanRules said:
Gotcha. Do you recall which app you used? I guess I could just hide them in a launcher app, too, but I am particularly miffed about the fact that Facebook apparently comes pre-installed and can't be uninstalled on the unlocked N10+ (though I do not have one in my hands and obviously can't confirm myself as a result).
Click to expand...
Click to collapse
I use CCSWE App Manager for disabling apps I don't want to use. It's a paid app, but it doesn't cost that much if I recall correctly (think a few bucks... It's been a while since I bought it).
scottusa2008 said:
Yes use the CSC_*** and not the HOME_CSC when flashing.
For the userdata you should see it when you look at the Odin interface. Essentially as you place the 5 individual parts into each appropriate spot in Odin, you should see the 6th spot labled userdata.
Click to expand...
Click to collapse
Cool. And what I do with that field will be self explanatory?
scottusa2008 said:
I use CCSWE App Manager for disabling apps I don't want to use. It's a paid app, but it doesn't cost that much if I recall correctly (think a few bucks... It's been a while since I bought it).
Click to expand...
Click to collapse
Great, I see it. Thanks!
XanRules said:
Cool. And what I do with that field will be self explanatory?
Click to expand...
Click to collapse
If by "self explanatory" you mean the firmware file with the word USERDATA as part of it's name goes into the the spot on odin labled "USERDATA"... Then yes
XanRules said:
Great, I see it. Thanks!
Click to expand...
Click to collapse
No problem
@scottusa2008 Can you clarify this for me? In SM-N975U1 and SM-975U both have T mobile(TMB).
1. Can you explain why are we flash use file from U version instead of U1?
2. Do I download the latest version of the file?
3. If I want to flash back to original for return or warranty which file do I need?
I need to confirm these information so I purchase the phone tommorow
OxyEthane said:
Can you clarify this for me? In SM-N975U1 and SM-975U both have T mobile(TMB).
Click to expand...
Click to collapse
My responses in this thread pertained to the OP asking about flashing U firmware onto his/her U1 model phone. Even if "both" have it (and I used both) I only got the full functionality available from the carrier when I flashed the carrier firmware.
Otherwise I got generic one size fits all functionality with the U1 firmware... Which was fairly decent, but the U firmware was a better performer for Tmobile IMHO.
But flash what you want and see what changes. If you did research onto the subject then you should be aware of the bootloader version (explained further below).
OxyEthane said:
1. Can you explain why are we flash use file from U version instead of U1?
Click to expand...
Click to collapse
Not sure why this is still a problem to understand? It's been answered before and even on different threads/forums if you search for knowledge. Or go ahead and try it to find out... Either way here's how I understand it (and from past experience).
Unless things have drastically changed (which I have not heard have or seen) firmware for the U1 model is unbranded firmware. It's has a carrier bloat free experience, configured to obtain updates through samsung with a generic one size fits all carrier compatibility pending on what sim card is installed. Once installed the phone configures itself based on what sim card settings are present and (from poking around on my last rooted phone and from what I can remember) some configuration scripts on the phone (enabling/disabling bands and etc). This is why some features won't work and some will, but again it depends on the carrier and what the carrier requires.
Unlike the U1 firmware the U firmware is carrier specific and contains customizations/tweaks for said carrier by that carrier. The firmware also will contain changes made by the carrier and any carrier specific apps.
OxyEthane said:
2. Do I download the latest version of the file?
Click to expand...
Click to collapse
If your going to flash firmware then you flash either the U1 firmware or the U firmware. You shouldn't mix and match firmware parts.. Just pay attention to the bootloader version of the firmware. You can only flash firmware that has a bootloader version equal too or greater then that of what is currently on the phone.
OxyEthane said:
3. If I want to flash back to original for return or warranty which file do I need?
Click to expand...
Click to collapse
Only if the bootloader is equal to or greater then what is currently on the phone then yes.
OxyEthane said:
I need to confirm these information so I purchase the phone tommorow
Click to expand...
Click to collapse
Sorry I could not get back sooner but had to work to pay the bills. As a side note you can find all of your answers on the internet. None of this is special access private information, it's been covered quite extensively.