Related
Hi All,
I have a Huawei Enjoy 7 - Model SLA-LA00 (running Nougat 7.0, EMUI 5.1, Boot is unlocked).
I'd like to root it, but I've tried Kingoroot, King Root, iRoot etc and it repeatedly fails. On checking it seems that my device isn't compatible with those apps. I would like to use the ADB method, but there's no custom recovery image for the SLA-LA00, I've also checked and it seems, there isn't but please correct me if I'm wrong.
Is there a custom recovery available for my model?? Also, I've tried looking but, is there an International firmware for this model??
Any assistance would be appreciated, thanks.
Regards,
marquez010
Hello, was going to create a new thread, but think yours fits what I need to ask aswell.
Same phone here, bought it in Shanghai and now in Brasil, was trying just to make it google able. Salesman at the official Huawei store tricked me to think it would just need access to a open network for it to work. Silly me.
Well, as you, unlocked it with ADB and with no answers from nobody, tried to flash it with a random TWRP. Obviously didn't work. Now the phone wont boot into system, but i still can manage to put it in fastboot mode and it still replies to ADB.
Question is if someone that knows better than me can tell me what to do to at least get back where I was, before I finish killing this damm stupid phone, wich also doesn't seem such bad idea.
lucasresende said:
Hello, was going to create a new thread, but think yours fits what I need to ask aswell.
Same phone here, bought it in Shanghai and now in Brasil, was trying just to make it google able. Salesman at the official Huawei store tricked me to think it would just need access to a open network for it to work. Silly me.
Well, as you, unlocked it with ADB and with no answers from nobody, tried to flash it with a random TWRP. Obviously didn't work. Now the phone wont boot into system, but i still can manage to put it in fastboot mode and it still replies to ADB.
Question is if someone that knows better than me can tell me what to do to at least get back where I was, before I finish killing this damm stupid phone, wich also doesn't seem such bad idea.
Click to expand...
Click to collapse
Hi , all you have here :
https://www.getdroidtips.com/huawei-enjoy-7-b161-nougat/
Hey, thanks a bunch. Found that post before, but it looks like its for an older version of this phone. Mine was running b190 nougat. Don't know if should try to flash this one, but if no other ideas, will try it.
Well, was able to boot it again. Flashed it with yet another twrp that i found for a similar (or so i think) huawei and even tough it didn't work, when I connected the phone to the charger and it responded the power up volume combination and allowed me to reboot normaly.
Guess I'm back to where I started. Think now is better to wait, maybe there wiil be a moe suitable release of a gms core package that it requires for google play to work (have it, but installation fails on rebbot) or twrp updates with a version that works for me and then I can try to install gapps thru it.
Back to my old crappy lg now.
Good morning, everyone,
I appeal to your knowledge because I don't know what to do anymore. I have an Honor 7 that I gave to my son. It was unlocked and custom firmware installed.
He had another phone and so put the honor7 aside. Lately I've been trying to take it back. I made a complete rest.
Until then, everything is fine. The phone starts. I am coming to the configuration page. I enter the IDs of my account (on which the phone is registered) and the... ren to do google tells me that this is not the owner account.
We tried with all the accounts and emails we could have but nothing to do.
I find myself with a phone that is unusable and blocked by google. Knowing that the reset has locked the bootloader and that I can no longer install custom firmware.
Have you ever had this case?
Thank you for your help.
Translated with www.DeepL.com/Translator
HI....
not sure, if that helps you:
https://productforums.google.com/forum/#!msg/gmail/KK_5Va2eBbs/216OubBtAgAJ
https://www.androidpolice.com/2015/...ne-you-might-trip-a-72-hour-security-lockout/
https://www.techoxygen.com/bypass-google-account-unlock-frp-huawei-p9-lite-nexus-6p/
Be careful.... i just found it on google and did not test anything
Thank you. I'll look into it.
Dattel01 said:
HI....
not sure, if that helps you:
https://productforums.google.com/forum/#!msg/gmail/KK_5Va2eBbs/216OubBtAgAJ
https://www.androidpolice.com/2015/...ne-you-might-trip-a-72-hour-security-lockout/
https://www.techoxygen.com/bypass-google-account-unlock-frp-huawei-p9-lite-nexus-6p/
Be careful.... i just found it on google and did not test anything
Click to expand...
Click to collapse
Don't work
That's called factory reset protection or "Google lock".
You said you have installed custom rom? According to this https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/ you should be able to remove the lock by reflashing your rom (or just gapps if those were not included in that rom).
Hope this helps
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...
SO, haha been about a week now trying to figure out how to revive my n200 without sending it in to OP..
I successfully converted it to oem, but that wasnt enough for me so i flashed the CherishOS GSI and tried a few other treble projects..
Wanted to go back to oem but in the process of doing so from a GSI , i lost some partitions so i figured to just use the msm tool knowing it was the tmo variant version, since i converted it to OEM it wouldnt work , CORRECT??? Because when it went to boot up after the tool finished it froze on the tmobile boot screen and started a bootloop.
I somehow got it into EDL mode because it didnt recognize the original button combinations to get into edl mode and with the bootloader now re-locked i cant do a damn thing. Used the msm tool again and weirdly when it went to boot up after completion it didnt boot up the tmobile boot screen, it was the oneplus boot screen which had me happy bcuz i wont have to convert it again but at the sametime annoyed because IT WAS STILL IN BOOTLOOP.
BUT WAIT THERES MORE>>>
I finally get it to get passed the boot logo, onto the set up when you first buy the phone, i agree to the terms, it reads my sim and that checks out but when it goes to turn on the wifi to continue set up, it freezes and guess what BOOTLOOP. Have tried a bunch of things even somehow got into settings from emergency call but cant access developer options to be able to unlock bootloader.....
SOSOSOSOSOSOSOSOSOSOSOSOSOSOSOSOS PLEASE HELP?!
Thanks.
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
oCAPTCHA said:
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
Click to expand...
Click to collapse
OnePlus will not do anything due to the warranty being void...
DM me. I can work this out with you. I ran into a similar problem.
oCAPTCHA said:
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
Click to expand...
Click to collapse
Tried sending it for repair but had the op guy look up my imei and ITS A DAMN DEMO PHONE I GUESS!? Cant return it, bought off amazon refurbrished and due to my anger problems i shattered the screen but other than that i shouldnt of been sold a damn demo phone from the start.
T3CHN0T33N said:
OnePlus will not do anything due to the warranty being void...
Click to expand...
Click to collapse
they would repair it, they even repair tmobiles version and metro and all but it really ticked me that amazon refurbrished sold me a demo phone or the phone is now thinking its a demo phone somehow..
Springles2 said:
DM me. I can work this out with you. I ran into a similar problem.
Click to expand...
Click to collapse
Never discuss in DMs! This person has illegitimate intentions.
T3CHN0T33N said:
Never discuss in DMs! This person has illegitimate intentions.
Click to expand...
Click to collapse
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Springles2 said:
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Click to expand...
Click to collapse
it's not against the rules it's just not a good idea to do
T3CHN0T33N said:
it's not against the rules it's just not a good idea to do
Click to expand...
Click to collapse
Thank you for the advice! Just wanted to see if I could legitimately help!
T3CHN0T33N said:
Never discuss in DMs! This person has illegitimate intentions.
Click to expand...
Click to collapse
illegitimate intentions, lol what are you trying to say? didnt know my intentions had any type of rules to be followed.
if oneplus sends people on the daily unlock codes in order to unlock their bootloaders on their phones, shouldnt people be able to explore some other OS's and things of that sort? My intentions were to TEST out GSI's that developers worked hard on to work with certain devices and provide some feedback and hopefully come along one that i can use on the device as a daily.
This is Forums, know your place. I think we are all a lil illegitimately intentional at times dont ya think?
no offense.
Springles2 said:
Thank you for the advice! Just wanted to see if I could legitimately help!
Click to expand...
Click to collapse
Thanks for your gratitude.
Hello everyone,
It is OK to ask others to send DM for communication if both parties agree.
But, as a general reminder (across the internet), please be caution when you exchange DMs. Make sure you do not post any personal information or financial information to others. Be safe and be alert.
jerryhou85 said:
Hello everyone,
It is OK to ask others to send DM for communication if both parties agree.
But, as a general reminder (across the internet), please be caution when you exchange DMs. Make sure you do not post any personal information or financial information to others. Be safe and be alert.
Click to expand...
Click to collapse
Thank you for explaining it to others who might need it
Also, will never ask for anyone’s personal info or financial info or anything to do with their identity. That is their information and have no interest in knowing more than their username on here
Maatt_OG said:
SO, haha been about a week now trying to figure out how to revive my n200 without sending it in to OP..
I successfully converted it to oem, but that wasnt enough for me so i flashed the CherishOS GSI and tried a few other treble projects..
Wanted to go back to oem but in the process of doing so from a GSI , i lost some partitions so i figured to just use the msm tool knowing it was the tmo variant version, since i converted it to OEM it wouldnt work , CORRECT??? Because when it went to boot up after the tool finished it froze on the tmobile boot screen and started a bootloop.
I somehow got it into EDL mode because it didnt recognize the original button combinations to get into edl mode and with the bootloader now re-locked i cant do a damn thing. Used the msm tool again and weirdly when it went to boot up after completion it didnt boot up the tmobile boot screen, it was the oneplus boot screen which had me happy bcuz i wont have to convert it again but at the sametime annoyed because IT WAS STILL IN BOOTLOOP.
BUT WAIT THERES MORE>>>
I finally get it to get passed the boot logo, onto the set up when you first buy the phone, i agree to the terms, it reads my sim and that checks out but when it goes to turn on the wifi to continue set up, it freezes and guess what BOOTLOOP. Have tried a bunch of things even somehow got into settings from emergency call but cant access developer options to be able to unlock bootloader.....
SOSOSOSOSOSOSOSOSOSOSOSOSOSOSOSOS PLEASE HELP?!
Thanks.
Click to expand...
Click to collapse
So i actually got the phone going FINALLY, had to wait for the android 12 update and found a couple tricks to get the phone to turn on without it freezing and going into bootloop. I know for a fact that some of the files for the wifi hardware and network were corrupt or deleted along with some partitions so thats why the msm tool didnt work, Converting to oem from tmobile variant also threw a red flag for the msm tool because it is now identified as a oem variant and the tool was only for tmobile.. Just happy to have this phone back, aint the best but after the andoid 12 update, its pretty damn good to me honestly. After this experience i have learned alot about coding, developing, and just more knowledge about how operating systems work along with other components and so on. thanks for trying to help everyone.
Maatt_OG said:
So i actually got the phone going FINALLY, had to wait for the android 12 update and found a couple tricks to get the phone to turn on without it freezing and going into bootloop. I know for a fact that some of the files for the wifi hardware and network were corrupt or deleted along with some partitions so thats why the msm tool didnt work, Converting to oem from tmobile variant also threw a red flag for the msm tool because it is now identified as a oem variant and the tool was only for tmobile.. Just happy to have this phone back, aint the best but after the andoid 12 update, its pretty damn good to me honestly. After this experience i have learned alot about coding, developing, and just more knowledge about how operating systems work along with other components and so on. thanks for trying to help everyone.
Click to expand...
Click to collapse
Please write something up on how you did it! It could save someone!
Springles2 said:
Please write something up on how you did it! It could save someone!
Click to expand...
Click to collapse
Well at times it would just bootloop nonstop after using the msmtool, but then tried entering safe mode and that was a success but remembered each time it went to turn on the wifi to set up the phone it would freeze and bootloop no matter what,
So from emergency call find your way into permission manager , from there you can open settings app, disable location and anything that would trigger wifi to turn on , airplane mode is on remember this, you need to turn it off withput having the wifi kick on. Disabling some modem/network apps or that has anything to do with wifi, location, carrier, modem that you can disable, do it. Once you're able to turn airplane mode off successfully you can get passed the wifi part of the phone setup and use your mobile data instead, or what I did is use gnirehtet , you can find it on GitHub. Install on PC, make sure you enable USB debugging and have the default USB config set to USB tether, not hotspot .extract zip to platform tools, Move the apk file from gnirehtet zip to your phone, run the provided command from the zip and you'll get a request to allow debugging on your phone from PC, once you do that. You'll finally be able to update your n200 T-Mobile phone to Android 12 which is the only way I found to do this. Make sure you update to Android 12 and not another android 11 before turning wifi on or anything else or you will have to start ALL OVER. Done it twice it's a pain in the arse
Springles2 said:
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Click to expand...
Click to collapse
I was going to say keep discussion in the open in case any future people come across the same issue. If there's one thing I hate is coming across the same issue as my issue on stack overflow or elsewhere and OP from 7 years ago saying, "Never mind, I figured it out."
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.