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.
Related
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!
Hello friends.
Need couple advices.
Just became an owner of this phone.
No ROMs available, nothing yet, phone is new, I understand.
But,
1) I can`t enter neither recovery nor fastboot ("no command" with fallen robot with red warning in stomach instead of recovery and some factory mode instead of fastboot).
2) Drivers.. what`s with them? Any advice? (adb at least, PC doesn`t see the phone, except file transfer)
3) twrp?) root?) xposed?))) (android 7.0)
Will be very grateful for any help
Great questions. I have also ordered the phone but have not yet received it.
Would you like to tell us a bit about the phone? Does it work well? Do the stereo speakers work or is one speaker just a fake?
-Tiz- said:
Great questions. I have also ordered the phone but have not yet received it.
Would you like to tell us a bit about the phone? Does it work well? Do the stereo speakers work or is one speaker just a fake?
Click to expand...
Click to collapse
Thanks)
Works fine, a bit heavier than i expected, but now i like it.
stereo is fake, as usual
Already managed to enter recovery, fastboot, to connect from pc in fastboot. But still fail with adb drivers.
Found scatter file, that should suit, and now going to try readback firmware from the phone.
Then want to experiment with different TWRPs, and so on
On 4pda, they tellin about androidpay problems
My cam is ok, but one`s guy from 4pda - just terrible, may be he need to factory reset.. we`ll see
that`s it for now
I have this on order from Amazon. I'm really hoping someone with the skills will be able to get TWRP and Lineage setup for the S60. I'm a noob at this, especially about MTK devices. How hard would it be to port over a build from an existing phone with the same general config (Helios P25, 6 + 64 GB)? I have concerns after reading about finding malware on the X5 Pro and I'd like to mitigate that.
Those of you that already have your S60's, are you aware of any pre-installed adware or other unwanted software? Seems to be a very common issue on Doogee handsets....
What is the real weight of the Doogee S60 handset please? Various spec sites and retailers have it listed from 173g to 337g! They can't all be right. Doogee don't list the weight on their website so I expect it to be bit heavy. I will be really grateful if someone who has one can put it on a scale and weigh it.
I've just received mine.
It's 289grams
The truth at last
fingery said:
I've just received mine.
It's 289grams
Click to expand...
Click to collapse
Thank you a lot.
At last some genuine information!
Doogee never answered my emails and don't list the weight in their specs. I did get a reply from one retailer who said it is 202g and they get their specs direct from Doogee so it must be correct. I was suspicious so thought I would ask here where there is no commercial pressure to deceive.
It is a bit hefty at 289g so will now look for another rugged phone - any recommendations?
Just received today.
297 gr as you can see in attached pic.
I am also interested on rooting, TWRP... and also very interested on Bluetooth+ plus ANT+ service. I don't know if this o is possible in this phone, but very interested to me for connect with heart rate monitor ANT+ (this works very well with my previous Nexus 5).
Any information will be appreciated!
Thanks.
Ruben
PD: Sorry, pic is on Google photos and I can't attach it or putting a link to it!
Curiousdrummer said:
Thank you a lot.
At last some genuine information!
Doogee never answered my emails and don't list the weight in their specs. I did get a reply from one retailer who said it is 202g and they get their specs direct from Doogee so it must be correct. I was suspicious so thought I would ask here where there is no commercial pressure to deceive.
It is a bit hefty at 289g so will now look for another rugged phone - any recommendations?
Click to expand...
Click to collapse
{
"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"
}
Having spent a few hours setting up my S60 yesterday i have a few issues. Can anyone clarify if this is just me or are we all seeing similar :
Fingerprint reader - easy to setup and seems to detect quickly however once configured it's very poor in use. More often than not the device fails to recognise my print and unlock.
NFC - Annoying notification "NFC service. Touch to view settings" cannot be hidden/removed.
NFC - Android pay not working. Error message saying device may be unlocked or rooted etc.
Build details etc shown on attachment.
I heard somewhere that S60 is prerooted, maybe thats issue with Android Pay?
Chamelleon said:
I heard somewhere that S60 is prerooted, maybe thats issue with Android Pay?
Click to expand...
Click to collapse
Shame they market it with NFC and using it to Tap and Pay but Android Pay isn't supported on it.
Any idea if there's any way around before i spend hours on it?
fingery said:
Shame they market it with NFC and using it to Tap and Pay but Android Pay isn't supported on it.
Any idea if there's any way around before i spend hours on it?
Click to expand...
Click to collapse
I have set upa third part application to pay, and it seems to work, but I haven't used yet. I also have read the warning with Android pay, but in spain there are other apps supported by banks. But yes, it is annoying the nfc notification always on task bar.
And my fingerprint sensor is working correctly.
Ruben
Enviado desde mi Nexus 7 mediante Tapatalk
I find it hard to believe they pre-root the phone from the factory although kudos if they did. For those of you with your phones already have you installed any anti-malware and what has been the result? I've been reading up on the issues the X5 Max Pro owners have been having and I'm hoping to avoid that s***storm if I can.
fingery said:
Shame they market it with NFC and using it to Tap and Pay but Android Pay isn't supported on it.
Any idea if there's any way around before i spend hours on it?
Click to expand...
Click to collapse
on many Chinese phones, Android Pay does not work because google servers do not certify!
their certification on a certain phone requires financial costs.
But Android Pay is easy to run having root rights
TWRP and ROOT access will be ready soon!
STOCK ROM + TWRP + ROOT + XPOSED (is said to be buggy)
First of all i should thank a lot and redirect all regards to this very man serg2327, because all that below is totally his merit
Firstly, speaking about drivers, I didn`t install any extra, just the ones the phone did automatically. You only need to connect ur phone to ur pc in different states (e.g. turned off, recovery, fastboot) and all will be installed by itself (except adb drivers)
STOCK ROM
Was made from full (64gb) memory dump.
I cant post links, i`m very sorry
U can google them at the theme of doogee s60 at 4pda.
Or, may be serg2327 will post them here
1. Unpack the firmware
2. In SP Flash Tool point to the scatter file containing in firmware
3. Flash any partition u want (I flashed all of them and everything was fine)
TWRP + ROOT *(+XPOSED)
twrp is ported from BV8000
there`s a touchscreen bug, but there`s also some temporal solution
supersu is also taken from BV8000
Recovery could also be flashed thru SP Flash Tool, u just need to tick it in download menu and put the right path, but in this case, due to a touchscreen bug u will need an otg cable and a mouse, otherwise u won`t be able to flash supersu and that will cause in loosing twrp after booting system.
That`s why we will flash recovery thru fastboot, because there during the first boot - touch is available, but only for the first time, afterwards it will also fail.
So,
1. Download and place recovery.img somewhere, copy the path. I place it just in C:\ for convenience.
2. Download and place supersu.zip into the /sdcard of your phone (do it while your phone is on, before proceeding further, because in twrp my pc couldn`t see the phone)
3. Turn off the device, then press and hold together "pwr" and "vol+" until the screen turns on, then u see a green robot with a red warning in the stomach, then press and hold "pwr" and then just slightly press "vol+" (don`t hold it, and press only after "pwr" is held), u`ll see the stock recovery menu, choose with "vol-" fastboot mode (or bootloader, don`t remember, it is second from upwards), press "pwr" to enter this mode, u should then see just a small FASBOOT written on a black screen.
4. Connect the phone to the pc, open cmd.exe as an Administrator, type:
fastboot devices
u should see ur phone by its serial (like adb devices)
if everything is ok, go next.
type in cmd:
cd C:\ (or other path where the recovery is lying)
fastboot flash recovery recovery.img
fastboot boot recovery.img
then u`ll get ur phone booting in twrp, and touch should work this time
5. Flash supersu from /sdacrd
*5.1. If u like, can also flash xposed (it is beta version, is said to be buggy) at this very moment, while u have ur touch available
6. Wipe dalvik cache and boot to system
*7. For using xposed u need an installer (ticking modules, etc)
8. Open supersu, it will ask for a binary update, press cancel and forget about it.
9. That`s it, u have twrp + root.:good:
p.s. The firmware is deodexed, that means we can freely clean chinese system trash.
And, one more great thanks and regards to serg2327 . It`s more of his knowledge than mine
link to firmware / backup: https://mega.nz/#!APhWya7B!nNrDImupeIaPyPAvIrFxGyyfoZEAIO-DEAy2XFtCDIM
link to TWRP: https://mega.nz/#!NHpBlY5C!RPVpVCUuTslLOrcf_bjL4pBYOGblcrRlN8CQ9I7cIbY
in the TWRP the sensor does not work, control via the otg cable through the optical mouse
after the TWRP firmware you need to boot into it and install the root, otherwise the android system will restore recovery
link to patch root: https://mega.nz/#!0HRHzbia!rX1iMekfYymzSzq0AtTT96-lELMziirBIAF3kpe_BCc
regret to tell, but firmware is odexed.. 80-90%, it accidentally happened that during brief look i saw couple apps from that 10-20% deodexed, the rest has .odex files
I'm expecting my phone today, so I'll post impressions over the weekend. Any news about about a Lineage port?
My s60 issues so far..
Hi, i have a s60 for about 2 weeks now and i can tell its not without issues:
1. Screen comes ON with no reason, as IF somebody tryes to unlock with finger print, it and says "too many attempts, try later" .It happends quite often and it goes every 30 seconds or so.. Then stops.. Half an hour latter starts again... Annoing..
2. Finger print unlocking-hit and miss... Sometimes it unlocks as soon as you touch it, sometimes doesn't work at all..
3. Loud speaker ,again, sometimes on full volume you get loud and crisp sound, even then one of them is fake, but next time, out of nowhere sound becomes so crappy , like from ripped speaker, doesn't take high piches at all, even IF you tune volume half way dawn.. like its broke sudennly.. latter OK again.. That affects sounds, like call or notifications- sometimes its loud and clear, sometimes you just miss them..
4. Calling 2 out of 10-12 calls, -you dont hear them, well you do, but so quite, that you just can't make up the words. And then it fixes itself..
5. Camera is inposibble to focus where you want. It hunts a lot.. In the menu settings for ISO and shutter speed set to auto and greyed, like its there, but you can't change it-gimmick??
Over all-battery life is great, screen is superb with very natural color reproduction, camera is very good then you get it in focus. Dynamic is clear and loud then it works.. Call quality is superb then it works. Never dropped WiFi conection, Bluetooth connects instantly and never had an issue, reception very good.
Hope all thouse problema are software related and can/will be fixed by update, becouse its a nice phone. Love the size of it.
Information available:
Boost site: https://www.boostmobile.com/phones/coolpad-legacy.html
Manufacturer details: https://coolpad.us/legacy-boost/
Youtube video I made: https://www.youtube.com/watch?v=wylMivqymUM
This phone was purchased from Walmart and obviously they are no help. Went to a Boost Mobile and a Verizon store and neither one could do anything either (BTW huge props to Verizon on their customer service). I need to know how to clear this phone of all prior information (which is seems that a factory reset from within the OS does not do) and also how to get into the bootloader. Normal physical button methods like power+volume down or up or all 3 just make it say "official" on the screen and then it boots anyway. How do I hack this thing? I've gotten into literally hundreds of Android phones that were bricked and this is the first time I have had this new problem and I don't know where the blame lies. Even if there is a halfway legit custom ROM I could put on the thing, I don't know, I've tried everything I can think of. Can anyone help?
Thank you in advance!
adrenatek said:
Information available:
Boost site: https://www.boostmobile.com/phones/coolpad-legacy.html
Manufacturer details: https://coolpad.us/legacy-boost/
Youtube video I made: https://www.youtube.com/watch?v=wylMivqymUM
This phone was purchased from Walmart and obviously they are no help. Went to a Boost Mobile and a Verizon store and neither one could do anything either (BTW huge props to Verizon on their customer service). I need to know how to clear this phone of all prior information (which is seems that a factory reset from within the OS does not do) and also how to get into the bootloader. Normal physical button methods like power+volume down or up or all 3 just make it say "official" on the screen and then it boots anyway. How do I hack this thing? I've gotten into literally hundreds of Android phones that were bricked and this is the first time I have had this new problem and I don't know where the blame lies. Even if there is a halfway legit custom ROM I could put on the thing, I don't know, I've tried everything I can think of. Can anyone help?
Thank you in advance!
Click to expand...
Click to collapse
You can get to fastboot via adb. I can't get the bootloader to unlock tho.
@adrenatek, I know this is a belated reply, but I just got one of these devices myself and wanted to chime in. Let me see if I understand correctly: are you stating that, after performing a factory data reset, your userdata remains intact on your device? Or, did you get it figured out by now? Also, as to fastboot mode, adb reboot bootloader will get you there, but this device is not supported for OEM unlocking.
can anyone tell me if i can unlock the BL of C3505L..
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."