Hello everyone,
I am very happy that I finally found this awesome forum, now I will able to learn more about my phone and android in general and help others just like I used to do before with my previous iPhone (OS). I used to jailbreak easily and enjoy all the features that I could find for the iphone. However, before 6 months I decided to switch to Android and got Samsung Galaxy Note 3 from Sprint, updated to 4.4.4. I absolutely love the device and never think to return to iPhone until I learned that rooting the Samsung will void the warranty that make me to reconsider another android phone other than Samsung. However, this isn't my concern right now, I have questions any help, even a small one would count to give me ideas and solutions.
I am new to rooting my phone (Never done it yet), but I am certain that I would want to do it because I want to change my device ID. I have noticed some apps from Play Store, will ask to pull my unique device ID and based on that they can store my information on their server no matter what I do, they will recognize my phone via device ID. I have tried these methods and they both failed.
*I tried to completely clean my phone from any data or history related to that app, I even change my account ID (email).
*I tried to use VPN from 5 different countries.
My phone was easily recognized by those app and they even retrieve my data that is save on their server. Note: most apps will pretend that after you uninstall and install that it doesn't recognize you as old user, but it does (Tested). I really have concern and I consider this to be a challenge.
I want to know:
1- Am I able to root my phone on version 4.4.4 and if so will it void the warranty from just trying to use the device ID feature?
2- If I do root the phone, just by rooting does that mean I am blocked by Samsung from getting any new updates and other apps updates?
3- For device ID, if I change my device ID for good and keep changing, will that affect me negatively anyhow, I mean samsung will notice and cut updates?
4- If I am prevented from having these updates. Can I download them manually and install them using my laptop.
I am sorry for my English and for being new to Android world. I would appreciate any kind of information that could help me. either by replaying or providing links.
Thanks
Edwardo
Edwardosd said:
Hello everyone,
1- Am I able to root my phone on version 4.4.4 and if so will it void the warranty from just trying to use the device ID feature?
2- If I do root the phone, just by rooting does that mean I am blocked by Samsung from getting any new updates and other apps updates?
3- For device ID, if I change my device ID for good and keep changing, will that affect me negatively anyhow, I mean samsung will notice and cut updates?
4- If I am prevented from having these updates. Can I download them manually and install them using my laptop.
Thanks
Edwardo
Click to expand...
Click to collapse
Edwardo,
Welcome to XDA! We're a friendly bunch here. I wanted to start off by saying that I appreciate how much information you gave in your first post. It is very nice to have enough information to truly help you. Now, onto your questions:
Rooting on 4.4.4
Unfortunately, there is currently no way to root the 4.4.4 version of the phone without tripping KNOX. KNOX is just the "switch" that says whether or not your phone software has ben tampered with. Technically, your warranty is void once you tip KNOX. In practice, though, Samsung doesn't really care if your KNOX is tripped. If you need to claim your warranty (i.e. broken screen, stuck button, etc), you can do so with a tripped KNOX and they won't even blink an eye.
In terms of "how to root," this thread has a very good method for gaining root access.
Future Updates from Samsung
Gaining root access should not affect future updates from Samsung or Sprint. If you end up going the "Custom ROM" route, you would have to restore back to the "stock" ROM before updating, but that is relatively easy.
Device ID changing
Unless I'm mistaken, there are two primary ways that apps identify you: Device ID and a proprietary (facebook, google, etc) login. It'd be obvious if the app is asking for a login, so the Device ID (UID) will be the one that you're wanting to change.
I've only used Titanium Backup to change my UID (you'll need to buy the "pro" version to unlock that capability), so I'm not sure of other methods, but I know that TiBu works.
The main updates (i.e. 4.4.2 to 4.4.4) to the phone will not be affected by changing your device ID. The only thing that could really be affected by it would be your Samsung Account. This is what updates your Samsung Apps. Most of these updates will be security-related (in my past experience). I doubt that the ever-changing Device ID would negatively affect it, but it's a possibility.
Manual Updating vs. OTA Updates
One great thing about XDA is that we have tons of resources to help others with their phones. If you do ever have issues with your phone, you can always restore a fully-stock ROM. Once you get used to flashing ROMS to your device, updating becomes trivial.
Here is one example of a "full restore" that will bring your phone to a completely stock state (even if you were on an older version). This thread has another one.
Hopefully this adequately answers your questions.
-Topher
topherk said:
Edwardo,
Hopefully this adequately answers your questions.
-Topher
Click to expand...
Click to collapse
Big thanks for the warm welcome and answering my questions. You have highlighted some points, I did not think about, if I change my device ID, I might not let Samsung recognize my device and get some updates, as you said it is possible, but I am very certain I will have to do it. I never use apps that force to access (Facebook, google, etc) I immediately delete them. So yes, those apps store my data based on the unique device ID.
I am going to read the links you provided and slowly I will root my device and download the app you have recommended.
Again thanks!
Related
Hiya
I have an Alcatel Onetouch Pop C1 4015D (and for the record, I'm never buying this brand or similar junk again). I just got it un-bricked after a few months thanks to the online USB firmware updater. It's currently in pretty much its factory-default state again, preinstalled crapware and all.
What I'd like to do is install a custom ROM on it, to have a clean system I can actually enjoy owning, e.g. AOSP (if that is what I think it is: the basic, clean Android system). The problem is that I'm getting a little overwhelmed with information, tutorials linking to more tutorials, tutorials linking to downloads for which I have to "complete a survey" and such (abort abort abort), 2 different tutorials for the same thing stating different ADB commands, a few outright scams, etc etc etc. There's tons of information out there, but 90% of it seems wrong, irrelevant, device-specific or otherwise unusable. I've already spent hours on this and still haven't gotten anywhere.
I'd be very grateful if someone actually reliable could walk me through the entire, correct process, please. :fingers-crossed:
I'm just going to write down the bits and pieces of info I already have:
I've already rooted it with Framaroot; no problems there, superuser works.
I've found this site that lists several ROMs, presumably specifically for the C1, including the standard ROM and a cleaned version: tinyurl dot com/o24wqoe. The AOSP one strikes my fancy and is on my SD card already.
The same site says I can just put the provided ROMs on my SD and install them as updates via stock recovery, but I highly doubt that because I read everywhere you specifically can't do that. Sounds like fake advice to me.
I'm told I'd need to unlock my bootloader, but once in fastboot/bootloader mode none of the offered fastboot unlock commands really do anything. The "..." appears in my console and then nothing.
I've tried installing TWRP and CWM recoveries, but you know, "your device is not supported". There's this video of a C1 with a custom recovery (watch?v=_TGgXIp3fWM) and the comments claim it's CTRecovery, but I can't even find anything about that. I already submitted requests for a fix for my device to twrp and cwm half a year ago before I bricked this thing, and one person promised he was gonna make a build for me, but nothing came from any of that.
I think that's just about all the useful things I can extract from this whole mess of information I have...
Please help me make sense of this overload of info and device-specific shenanigans, and walk me through what seems to be such a simple process for everyone with a mainstream device?
For the record, I'm back down to barely being up-to-date on what is what anymore. I'm more than familiar enough with the theoretical side (bootloaders, partitions, bios, etc) because of my heavy computer usage (professional programmer), but once I get into Android I'm just lost. All that fancy terminology nobody seems to bother to explain, things that are taken for granted but aren't really obvious (like a guy demonstrating the installation of a custom ROM, and only mentioning 10 minutes into the excessively long video that you need to install a custom this and custom that first), so many alternative methods for the same thing that have different dependencies (unlocking bootloader vs custom recovery), etc... I don't know anymore what's device-specific and what isn't, who is telling the truth, what a given tutorial is actually making me achieve in the end, etc. TL;DR I'm lost, I'm not stupid but I'm not gonna pretend to know anything about Android's subsystems anymore at this point.
wow u wrote a full post and u speaked for me as have the same problem
Custom recover
i have made a recovery for the 4015x
and got one of the roms to work
(and a fixed stock recovery)
there are 6 versions of this phone and at least two different partition tables that ive seen
but getting it back from softbrick id use the "mobile upgrade s 4.1.1" from the alcatel site
alcatel,mobiles,all mobiles, pop c1, support and on the right hand side down load the program and follow
this forces a stock rom back on the phone (no root and all data wiped)
im waighting on the mods to let me post links so i can host the roms and recoverys
but if you want to mess with the roms your self you can edit the partition tables and get the roms to install.
id use the app "diskinfo" to check what partitions your system and data etc etc are useing and chainge this in the roms.
hope this helped
p.s. if not i could poss look at editing the aosp rom for you and host if for a bit
just waighting on beeing able to post links :s
Alcatel onetouch c1 pop
MY PHONES flash light or led light comes on but it wont come on at all jus remains black wont start ....i tried restoring rom but ,it was useless ,well i used the upgrade tool and there wasnt the right models for my phone what should i do now .oh and also my phone has no stock rom from nowhere on google im so in need of getting back my phone .how can i fix a bricked or whatever phone its a alcatel one touch pop c1 4015a
What is the online USB firmware updater? Mine is also bricked
Please, I hope somebody doesn't start berating me for not reading XDA posts about my Verizon Galaxy Note II more thoroughly. I have read many over recent years and been saved by quite a few during the hacking of my SCH-I605. Furthermore, I've been working in software development and network administration for decades now, so please don't somebody suggest I not mess with rooting my phone, custom recoveries, et cetera. I am here asking questions to make sure I don't hard brick my phone. Not asking resulted, about two months ago, in almost succeeding at Kobol's very interesting "short the tiny resistor" mode of getting out of a boot loop. I have a fully functioning phone now running rooted Kitkat and it's a sturdy platform, runs really great after I melted most of the bloatware and froze the rest (in case I ever need it), but I'd still like to move on to Lollipop and there is only one means for doing so which I know of (CyanogenMod), which I think may be problematic unless I am able to reflash an earlier ROM with unlocked bootloader.
The basic question I need verified is multi-part but basically boils down to this:
1. Is it or is it not true that if one is at baseband version I605VRUFND7, the bootloader is locked and one cannot install a custom recovery? (I think I read that in a few places anyhow.)
2. Is it or is it not possible to flash back to I605VRALJB from rooted I605VRUFND7?
3. Is flashing back to I605VRALJB, then installing TRWP or CWM, then using custom recovery to flash the latest CM12.x the best and only way to get from rooted Kitkat to rooted Lollipop?
4. I know there are some functional improvements in Lollipop but are they really that significant? I like the whole "material" thing which comes with Lollipop, but not at the price of loss of functionality.
Anyhow, here's my little sob story, which has a happy ending -- perhaps some of these details will elucidate my situation and lead to better answers:
I got tired of waiting around for Lollipop and had been unrooted by Kitkat for almost a year when I rooted again back in July 2015. I had wanted to go with the latest CyanogenMod Lollipop version, but ran into problems first using Heimdall (which refused to properly connect and write) and then trying Odin (against best advice post-root) to install a custom recovery (preferred TWRP but would go with CWM). Always led to that "unauthorized software" boot screen, which then necessitated reinstalling stock Kitkat and rerooting (I found the Ghettoroot .BAT file worked okay.) All was well, I was too busy to think about Lollipop but I woke up one morning about a month after I rooted Kitkat to find my Note II was stuck on red Verizon book splash-screen. Found a great article and YouTube showing all the keypress sequences which might exit a Note II from been stuck in boot -- but unfortunately not until after my further finagling just left me with a dead no-display-at-all device. I undertook Kobol's method, which requires partially reassembling the Note II's electronics outside its case and attempt to reboot with a very tiny screwdriver shorting a minute resistor on the motherboard right adjacent to the CPU -- I did in fact see the screen flash on briefly -- but I held my little screwdriver down too hard, accidentally gouged out the tiny resistor, and ended up buying a refurbished motherboard which very likely may have been scavenged from a stolen phone before going on sale on eBay. New motherboard worked great, I erased the original owner's info and data and proceeded to reinstall and root Kitkat. (Motherboard was already at I605VRUFND7) when I received it.
Anyhow, I also tried to install a custom recovery after I had new motherboard and rooted Kitkat. Using the TWRP Manager app put me back on the "unauthorized software" boot failure screen from Verizon, but I was able to Odin back Kitkat easily enough without losing my apps and configuration data. I believe I tried to use ROM Manager and Flashify as well -- but didn't find those apps very cooperative (though I didn't bother to upgrade to "pro" level on any of these in cast that matters). Unless I am mistaken, all these apps just place a zipped update file in the root of my internal SD card and then just hand it over to the Note II's stock recovery. I figured I just needed to stop and regroup later. That was a few weeks now.
Honestly, after the ordeal of having to replace a broken motherboard, and also -- after having looked at Verizon, Sprint and AT&T and the new Galaxy devices with no removable back and cracking the phone open necessary to replace the battery or upgrade the hidden microSD card and not liking that one would have to pay $600 over two years for a smartphone even further crippled at the cell carriers' requests -- it's even more important to me to be careful not to damage my Note II. (In fact, my Note II had turned out to be irreparable, I might even have even bought a refurbished unlocked Note 2 or 3 or 4 -- Samsung has made a real error on their latest generation of phones with their sealed backs and no user-accessible microSD reader.)
Yet, perhaps naively, I really do want to move on to Lollipop and even Marshmallow when CyanogenMod makes that available. So I really would appreciate it if you guys can verify whether what I intend to do (downgrading to pre-Kitkat in order to install custom recovery and then CM12.x) is workable? Or if there's a better solution? Or if I should just be content to have Kitkat rooted with all the fat cut off?
Many thanks. Hope my digression was not too long. Please don't anybody yell at me. XDA Developer's web forum is so full of very useful write-ups but unfortunately also some incorrect information and a lot of just plain useless posts -- it's really difficult sometimes to tell posts by guys who are actually experts from post by well-meaning folks with a lot of ideas but not so much expertise specific to SCH-I605 and VRUFND7. And I really need to get this right. (Granted that nobody on the forum can be held culpable should on mess up my phone based on their advice.)
Thanks once again!
Sorry for a very strange problem.... My wife still uses her old S III (I9300), although it is so outdated and partly broken. Some time ago we flashed CM 12, so that some apps who need a more up-to-date android can be used. But the phone is too slow, there is a crack in the display and sometimes it starts to reboot without any reason. There is not enough memory to install additional apps and without LTE it is no fun.
=> I want to buy a new smartphone for her, but she doesn't want to. She wants to save money and use it, until it is not usable any more.
Of course I could give it a good strike with a hammer or give it a treatment in the microwave oven, but I would prefer only a temporary lack of functions, so that perhaps later I can use it as backup phone for the kids. Therefore I am looking for some trick, app or system setting to SIMULATE, that the phone is broken. When she is happy with her new phone, I intend to "repair" it "by chance"....
Any ideas? How can I simulate, that the phone is broken? Thanks!
You need to hardbrick it.I dont know how to but you can Google it.
ArdaCsknn said:
You need to hardbrick it.I dont know how to but you can Google it.
Click to expand...
Click to collapse
Thanks for the reply! I googled, but i think i want to SOFTbrick it, not to hardbrick it. As I wrote above, I want to "revive" it after some time....
I think the simplest way may be to take the phone, create a backup of all data, put the phone into download mode, start flashing a stock ROM, remove the USB cable when it starts to flash the final file, and reboot the phone. Hopefully, the phone will display the "firmware upgrade encountered an error" message which can be resolved by re-flashing the stock ROM with Odin.
Based on my experience with flashing a stock ROM over a stock ROM, this procedure always leaves the data and apps intact.
cm_new said:
Thanks for the reply! I googled, but i think i want to SOFTbrick it, not to hardbrick it. As I wrote above, I want to "revive" it after some time....
Click to expand...
Click to collapse
Ah,sorry I read it but while replying I forgot somehow.Yeah, then you need to soft brick it .It can be achieved by deleting some system files.So phone can got into bootloop.If your wife doesnt now how to get in to recovery then you should be ok.
Stock rooted phone needed for this, activate factory app. It will give a black window with device information over everything onscreen. Disable factory app to remove it later on.
By flashing the stock firmware in an attempt to make it all better gives the perfect opportunity to pretend the process buggered it.
Put some clear tape on the battery contacts ?
Is there a current, standalone method for bypassing google account protection or factory reset protection on the Samsung Galaxy A02 USA Variant?
Recently purchased from a buy sell trade group claiming fully unlocked and factory reset, ready to go. Absolutely FRP locked.
As irritating as this is, I currently do not have access to a PC and am hoping to utilize a method on the device alone to bypass.
Update, I have tried using a PC along with multiple "premium unlock options" as well as ADB and FastBoot commands. Nothing seems to work with this device. I've put it into fastboot mode successfully, but none of the normal fastboot commands work to remove frp. This is why you don't buy used phones online.
DrRoxxo said:
Update, I have tried using a PC along with multiple "premium unlock options" as well as ADB and FastBoot commands. Nothing seems to work with this device. I've put it into fastboot mode successfully, but none of the normal fastboot commands work to remove frp. This is why you don't buy used phones online.
Click to expand...
Click to collapse
You can find remote FRP unlocking solutions on Ebay (runs about 20 bucks). Basically you hook up the phone to your pc and run a USB redirector software, then a tech on the other hand uses the official Samsung server to calculate the FRP key for any Samsung model and firmware version. It worked for me a number of times.
Pm me and ill send you the firmware I used
i sure could that firm ware tried everything to bypass frp can you help im using odin firm ware is A025USQS1BVA3
Use android 10 build date 20210626133126 samfw use patched odin
Tyrone M said:
i sure could that firm ware tried everything to bypass frp can you help im using odin firm ware is A025USQS1BVA3
Click to expand...
Click to collapse
Use android 10 build date 20210626133126 samfw use patched odin 3.14.1
I am exhausted but I believe it was this one. https://samfw.com/firmware/SM-A025U/TMK/A025USQS1AUE3
jayvee1 said:
Use android 10 build date 20210626133126 samfw use patched odin
Use android 10 build date 20210626133126 samfw use patched odin 3.14.1
Click to expand...
Click to collapse
TKXS
My pleasure, I hoped it helped. Let us know your progress
At the end of my wits, i am reaching out to the great minds for aid with frp removal.
i have a samsung a02s sm-124d. At this point i have tried dozens of methods with and without pc, tool, and more. This phone does not do alliance knox, not the emergency call, and i cant really find anything that doesnt lump it over to 124dl, which it is not and im afraid would brick it.
Only thing i havent tried is with another samsung but that isnt an option atm. i have os launcher 14 on it, access to most apps and galaxy store. major settings are still locked. Any idea what would be best route?
Thanks for taking time to hear me out.
Harm
HarmoneY said:
At the end of my wits, i am reaching out to the great minds for aid with frp removal.
i have a samsung a02s sm-124d. At this point i have tried dozens of methods with and without pc, tool, and more. This phone does not do alliance knox, not the emergency call, and i cant really find anything that doesnt lump it over to 124dl, which it is not and im afraid would brick it.
Only thing i havent tried is with another samsung but that isnt an option atm. i have os launcher 14 on it, access to most apps and galaxy store. major settings are still locked. Any idea what would be best route?
Thanks for taking time to hear me out.
Harm
Click to expand...
Click to collapse
What version of android are you on? I got to settings from add to home screen on one phone and from google news feed on another.
jayvee1 said:
What version of android are you on? I got to settings from add to home screen on one phone and from google news feed on another.
Click to expand...
Click to collapse
its android 11. i can get into settings with os14 and have hidden settings installed, but it wont let me into apps, change my lock screen, and anything google checks and wants me to put in pass or previous account. i was able to indirectly sign into chrome through google, but it doesn't go into the phone.
thought maybe if i was signed in to chrome and tried to link samsung account with it; but it still wants me to sign into google.
HarmoneY said:
its android 11. i can get into settings with os14 and have hidden settings installed, but it wont let me into apps, change my lock screen, and anything google checks and wants me to put in pass or previous account. i was able to indirectly sign into chrome through google, but it doesn't go into the phone.
thought maybe if i was signed in to chrome and tried to link samsung account with it; but it still wants me to sign into google.
Click to expand...
Click to collapse
Try "add to home screen" from chrome. Don't worry about bricking the phone. It's really hard to permanently break a phone. Almost always you can hook a samsung up to odin and start over. The only phones I haven't been able to fix without a new motherboard is a motorola and an Apple.
jayvee1 said:
Try "add to home screen" from chrome. Don't worry about bricking the phone. It's really hard to permanently break a phone. Almost always you can hook a samsung up to odin and start over. The only phones I haven't been able to fix without a new motherboard is a motorola and an Apple.
Click to expand...
Click to collapse
ill give it a try. *edit* looked everywhere. can ya fill me in on that?
currently it will quite often bring up my os right after it showing the welcome screen. There are references to 124d at a few sites, including samfw, but nothing more. The detailed model info i got off of the imei is correct, but since some programs say 124dl, i figure that would be my next move.
I am planning to brainstorm/plot out a methodology on the darn thing. i figure it might be worth the headache warning for anyone else lol!
Also, my kiddo handed off a samsung to me, and two days later so does my uncle, nice older models with display issues. so i may even figure that out and try some two phone action.
Apologies for the long ramble, And thanks, jayvee1, everyone, y'all have been awesome.
HarmoneY
If you still have this issue dm me, I had it and I was able to get rid of it.. p.s. it will cost you...
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy.
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
stop_making_things_worse said:
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy.
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
Click to expand...
Click to collapse
Give me some time working on it , u have spent so much time on this , can u spend little more . I may help u so let me do some research and come to u
DIVASM said:
Give me some time working on it , u have spent so much time on this , can u spend little more . I may help u so let me do some research and come to u
Click to expand...
Click to collapse
stop_making_things_worse said:
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy
Click to expand...
Click to collapse
stop_making_things_worse said:
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
Click to expand...
Click to collapse
can u try this
, if it is not wokring tell me
That is one of many videos and posts I have already seen and followed. The fundamental issue is not being able to unlock the bootloader in developer options. No amount of dancing gets "OEM Unlock" to display for me. Other threads indicate the 227U specifically does not have a way to unlock the bootloader, while 225/227 do.
I have the SM-T227U from Rogers and I have the OEM Unlocking option by default. I am on TP1A.220624.014.T227UVLS5DWC5 build number.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make Self Root And Try
I have same frustration nothing is getting the oem to show up. I have some know how's with rooting ect my other tablet is my Frankenstein lol but unfortunately it's not one of these tabs. Any word on a fix ?
wesmat95 said:
I have the SM-T227U from Rogers and I have the OEM Unlocking option by default. I am on TP1A.220624.014.T227UVLS5DWC5 build number.
View attachment 5936903
Click to expand...
Click to collapse
Hm interesting, if you boot to download mode, are you able to unlock the bootloader there?
wesmat95 said:
I have the SM-T227U from Rogers and I have the OEM Unlocking option by default. I am on TP1A.220624.014.T227UVLS5DWC5 build number.
Click to expand...
Click to collapse
This is a very interesting piece of information. I believe we can flash official firmware from samfw without worry, so I will try this route, however this specific build isn't available that I can see (it's old, they only have newest I guess?). I'll try the version they have and cross my fingers that it works and my SIM still works.
You did not have to do any steps, correct? OEM Unlock option showed without having to do the whole date/time dance?
stop_making_things_worse said:
This is a very interesting piece of information. I believe we can flash official firmware from samfw without worry, so I will try this route, however this specific build isn't available that I can see (it's old, they only have newest I guess?). I'll try the version they have and cross my fingers that it works and my SIM still works.
You did not have to do any steps, correct? OEM Unlock option showed without having to do the whole date/time dance?
Click to expand...
Click to collapse
No I did not. It just appeared in developer options. I just got this tablet about 7 months ago. Just got it out to do some development on it. I do have to mention that it is on the latest One UI update that appeared on my device a couple days ago. I did however notice that there are newer updates on SAMFW for it not available on my device. Maybe Rogers blocking update? Don't know. Found it wierd.
Wish39 said:
Hm interesting, if you boot to download mode, are you able to unlock the bootloader there?
Click to expand...
Click to collapse
Technically I should be able to. Haven't done it yet though.
Having the same problem. Everything I've tried so far can't even get to the OEM unlock to appear in debug. Pretty much hobbles doing anything. Is the freebie SM-T227U with android 13. Box has date of 05/09/23 so really new. Hardware revision 1.0 and SW is T227USQU4CWC2. Maybe a way to force flash older firmware and make OEM unlock work?
stop_making_things_worse said:
Other threads indicate the 227U specifically does not have a way to unlock the bootloader, while 225/227 do.
Click to expand...
Click to collapse
Really going to piss me off if true.
popeye2014 said:
Having the same problem. Everything I've tried so far can't even get to the OEM unlock to appear in debug. Pretty much hobbles doing anything. Is the freebie SM-T227U with android 13. Box has date of 05/09/23 so really new. Hardware revision 1.0 and SW is T227USQU4CWC2. Maybe a way to force flash older firmware and make OEM unlock work?
Click to expand...
Click to collapse
You could try flashing the Canadian T227U firmware using patched Odin, as it apparently can be bootloader unlocked.
We have AT&T and Verizon to thank for making Samsung permalock the devices they sell in the US.
Wish39 said:
You could try flashing the Canadian T227U firmware using patched Odin, as it apparently can be bootloader unlocked.
We have AT&T and Verizon to thank for making Samsung permalock the devices they sell in the US.
Click to expand...
Click to collapse
Thanks probably will try something like that. At this point might as well try even if end up bricking it. Really want it unlocked and the ability to use other carriers. Last thing I need is another tablet with just wifi. which is what it pretty much is being locked.
wesmat95 said:
Technically I should be able to. Haven't done it yet though.
Click to expand...
Click to collapse
I can't even get to bootloader. When it inters fastboot it just says interning fast boot and never actually does. I have no idea why
bencinilife said:
I can't even get to bootloader. When it inters fastboot it just says interning fast boot and never actually does. I have no idea why
Click to expand...
Click to collapse
Fastboot doesn't exist on Samsungs. They replace it with Download mode
stop_making_things_worse said:
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy.
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
Click to expand...
Click to collapse
I am literally going threw the same thing! i see everyone with different variants of the a7 lite doing this all day. I've tried everything to get the OEM Unlock option to pop up and literally nothing! Never ever thought it would just not be possible out the gate. Ive got the T227USQS5CWD1
Hardxcore_Cary said:
Never ever thought it would just not be possible out the gate.
Click to expand...
Click to collapse
Then you must not have purchased or used any North American Samsung devices in the past 5+ years.
Another user with a Canadian model reported having OEM Unlock (although I don't believe they've clarified whether they could actually do the BL unlock via Download mode).
So you could try flashing Canadian firmware
Update trying to flash Canadian FW to US (TMOBILE) tab:
Pulled both major versions up on samfw and tried differnet things. As a preface to outlining the issues I am facing, I have to state two things: 1) I have no idea what these files actually are. but 2) If I flash BL+AP+CP+CSC files that are for my carrier, it works fine (I've had to unbrick this by doing this several times). So, I can and have successfully flashed what is basically already the official FW for my device (SM-T227U_TMB_T227USQS5CWD1_fac <---this succeeds in ODIN).
I have now tried SM-T227U_RWC_T227UVLS5DWC5 and SM-T227U_RWC_T227UVLU4DWC2. I get different errors based on how I go about it, but errors nonetheless.
If I just blanket try BL+AP+CP+CSC I get
Code:
Non-KNL image not allowed: pit
If I use the BL+CP+CSC from my carrier and only the AP from RWC (I assume this is rogers), I get
Code:
Non-KNL Image not allowed: boot
For T227U_RWC_T227UVLU4DWC2 there's an additional error message of
Code:
Fused 5 > Binary 4.
RP Check Error: boot
Non-KNL Image not allowed: boot
I assume this is because the fw version doesn't match the "fused" version or something? I dunno.
Just reporting my findings.
EDIT: Upon further inspection of all the FW offerings, it appears only T227UVLS5DWC5 (Canada), T227USQS5CWD1 (US), and T227USQU5CWD2 (US) are even remotely viable due to device requiring U>=5 (sw/ver, bin value, whatever you want to call it). Unless there's a way around this?
I have validated that I can flash BOTH US F/Ws successfully, even though one is for a different carrier in the US. But the canadian version is a no-go due to the pit/boot errors noted above.