Related
The 4.0.4 OTA update was waiting for me when I woke up this morning. I started the install but when it went to reboot it hung up with a picture of the Android man on his back with a red error/warning triangle.
I haven't done anything with it, hoping someone might be able to help me out.
The phone is rooted but running 4.0.2 stock rom. the battery was a little low when i started the install, but i plugged it in before starting.
Thanks in advance for help,
jvoosh
the reason is that your phone is rooted ,so ... if you want OTA ,you had better unroot you rom or ruu
so can I hard reset the phone (pull the battery) without screwing anything up and then figure out how to unroot the phone?
thanks for your help,
j
Ditto
I'm in exactly the same boat, and hope someone answers this before I try a battery pull.
EDIT: I read around and found some people describing our situation, and mentioning that they did battery pulls to no avail. So I did, and nothing broke. However, the update didn't go through, and now I'm trying to figure out why this happened.
Same issue
I'm having the same issue. Phone got the IMM76k update, and after downloaded, was prompted to restart and install. So i did, gets through part of the install, and then goes to the android man on his back with a red exclamation mark. Have tried multiple times, all to no avail. Now, when I click check for update, it says system up to date, but still on 4.0.2.
Non-rooted, bootloader unlocked...anyone have any luck fixing this?
After downloading update, get Android man on back with red exclamation point
I'm having some difficulty getting the update to install, along the lines of some of the comments posted before mine:
I was able to force download the OTA update (IMM76K) according to the instructions on this original post. (It took a few tries, but eventually worked.)
I select the "Restart & Install" option (which is the only option available to me), and it restarts.
I get the relatively familiar Android man with his blue-green glowing polyhedron wireframe guts spinning, and a progress bar beneath him. After getting through what looks like about 20%, it slows down significantly, and I get the Android man on his back with a red exclamation point above him where the polyhedron used to be. I don't recall seeing any specific error message any of the three times that I tried this. (The first time, I did a battery pull; the second and third times, I just waited, and it eventually restarted on its own.) Needless to say, I'm still on 4.0.2.
I'm afraid I'm not very familiar with different version names and so forth (e.g,. I don't know what yakju is), but this was a phone that Verizon sent me in December 2011 here in the US.
Here's the information from my "About phone" page:
Model number: Galaxy Nexus
Android version: 4.0.2
Baseband version: I515.09 V.EK05 / I515.EK02
Kernel version: 3.0.8-gaaa2611 [email protected] #1
Build number: ICL53F
When I first got the phone, I immediately unlocked the bootloader and rooted it. I did NOT install a custom recovery, nor did I install any custom ROM.
It sounds like there might be some kind of validation error, but I do not recall doing anything that would make my OS non-stock, except perhaps side-loading Google Wallet, but since that doesn't even require root, I can't imagine that it would have any effect. My Superuser app shows only the following apps to have ever used root permissions: BusyBox Free, Secure Settings, Superuser, Terminal Emulator, and Titanium Backup. I've only used BusyBox and Secure Settings with Tasker to automate certain tasks, but nothing crazy! Mostly, I just need root for Titanium Backup. (I cannot recall exactly what I restored from my stock Gingerbread Droid X, but I was very careful to only restore apps and their corresponding app data--and I avoided restoring any Google-provided apps.) Even my tethering is done through an app not requiring root (SVTP).
Any advice (not requiring that I do a factory reset or flash a custom recovery or ROM) would be greatly appreciated! I'd also like to hear about people who have similar circumstances, but didn't have problems updating (so that I can rule out various factors).
Thank you in advance!
same exact issue here.
A "solution", albeit less than ideal
The OTA update eventually came to my phone naturally, and it still didn't work. (No surprise there.)
I called up Verizon tech support, and they had me do the Google Services Framework workaround to try to force the update again. Of course, it didn't work.
They said "We're going to need you to reset your device." (i.e., to factory default).
I told them that was wholly unacceptable, since I want to make sure that all my settings are preserved. (I'm kind of obsessive compulsive about things being set the way I like them, and Titanium Backup, as great a program as it is, has sometimes caused some trouble for me when restoring system settings, and especially since I'd be doing a restore after upgrading the OS, I was nervous about that option.)
Verizon got Samsung on the phone. They had no advice except "We're going to need you to reset your device." Both the Verizon rep and I told him that wasn't acceptable.
So Verizon's "solution" was to send me a new device, allow me five days to get everything transferred over, and then have me return the old device.
Up side: In case there was something wrong with my hardware or something else got messed up, I get a new device that I can get set up with the exact same settings as the old one.
Down side: The "new device" is refurbished, so there could potentially be some kind of baggage.
The "new device" came with 4.0.2. I booted it up without the SIM card, skipped all the logging in to Google, and immediately started going through the steps to unlock the bootloader and root the device. (I used the Galaxy Nexus Root Toolkit, which worked like a charm on a 64-bit Windows 7 machine I had lying around.) After unlocking and rooting, I logged into the device with my Google credentials and let it restore my settings and apps that I had downloaded from Google Play.
Then, it notified me that the 4.0.4 (IMM76K) update was available, so I installed that, and it worked without a problem.
Then, I installed the SIM card and got the new device activated through Verizon's website for activation.
Then, with both devices side by side, I went through every phone setting and made sure it's what I wanted, I made sure every app was installed (and if it was a non-Google Play app, I restored it through Titanium Backup), and I restored data for apps that don't store their data in the cloud (e.g., various games) through Titanium Backup. (I made a backup of my old device with Titanium Backup and transferred it over to the new device after getting the new one up and running.)
Everything seems to be working just fine, and the "new device" runs a bit faster and smoother than the old device, and that's with both devices rebooting and then going through the exact same "click paths", side by side.
So it's a bit of a hassle, but everyone who has a Galaxy Nexus should still be under warranty, so if you're polite with your Verizon tech support representative, they may be willing to help you out.
Verizon can sometimes be infuriating with their update release schedule and keeping their customers informed, but they sure do a good job accommodating their customers in other ways.
I realize this isn't really a "solution" to the Android man on his back problem, but this seemed to be the path of least resistance for me, and I'm pretty happy with the outcome so far. (It's been less than 24 hours since I got the "new device" set up!)
Other things I realized I should have tried (and still may, before I wipe my phone and send it back):
- uninstalling BusyBox (through the app itself, since it makes modifications to the system) and Secure Settings
- unrooting
Good luck!
My friend who has a nexus has his bootloader unlocked and CWM on it. He got the OTA today on his way into work and like you guys, he has a broken android when he boots up. We can get into CMW but we are unable to mount his internal SD storage onto our computer and he has no ROM zips on his phone. Any advice as to how to get his phone up and running?
Will wiping the system/data fix it? Is there a way to get a ROM like AOKP onto the device outside of CWM?
Edit: After several reboots it decided to just boot into the stock ROM. Really strange. Anyhow, flashed AOKP and all is well now.
HI guys, I'm hoping you can help me with a problem that's led me to start threatening my galaxy ace (S5830i) with a hammer.
Actually it's not the phone's fault it's purely my own stupidity, but none-the-less I'm here for help because I've spent all day and night trawling the net, trying to figure out how to proceed to resolve my issue on my own but I simply cannot make sense of the conflicting information I'm finding.
I promise you thing thing if nothing else, I have tried my very best to read around a hundred other forums, pages, and how 'to's but I'm finding that I have no resolution that I can work with because either:
- The tutorials turned out to be for the S5830 - not the i model - when I got to the forum
- The youtube videos all seem to be spoken in accents I cannot understand or not explained clearly, or are too technical
- Links I go to to get apk files etc are broken, wrong or leading me up another path I cannot follow
- Software does NOT look on my screen as it does on tutorials or websites (SDK for example)
- The people explaining the resolution type with such poor English I cannot understand what they're actually saying
- The solutions that work for others are too technical or advanced for me to understand and I'm finding it difficult to learn as I go (apart frm the root instructions which I found quite easy)
Anyway, I'll start at the beginning:
I have a samsung galaxy ace (S5830i) running:
- Gingerbread 2.3.6
- Baseband version S5830iXXLK1
- Kernel version 2.6.35.7
- Build number GINGERBREAD.XXLK3
I've already rooted it so I have superuser access, and I managed that perfectly well on my own
I installed titanium backup and somehow I managed to uninstall the stock email that comes with the phone. I think this is my problem because I now cannot download anything from google play, nor can I add a new gmail account to do so, so I'm stuck in no mans land not able to use googleplay (because my gmail account is now missing from my phone) nor can I seem to figure out how to get th apk file directly into the phone so that I can start fresh.
I'm also absolutely stuck on how to flash the phone and start again because nothing I seem to read is explaining it in simple clear terms that a layman can understand. When I do find a simple explanation, I find it's only for the non 'i' version of the phone, or if I find a simple instruction it's zip files for the rom do not contain all the files I need to use with odin v1.5
Also, there are conflicting explanations on flashing the rom on different forums/sites so I dare not use one over the other because another one contradicts it. I do not want to ruin my phone as right now it still basically works for now as a phone.
In my phone menu, the gmail icon is still there, just not the icon/app that said "email". The icon is now missing from my menus and with it there is now no way to use the play services without a gmail account on the phone.
When I click the gmail icon, it stats to open and then just shuts off quickly, not opening gmail, so I'm pretty sure all this is due to me deleting the email app using titanium backup.
Make sense?
What I'd really be grateful for is if on of you guys could help me out and explain in very simple terms what I need to do to either install the apk directly (preferred) so that I can add a gmail account to the phone and get access to google play again, or failing that a simple how to flash the rom with stock gingerbread, together with links to software that's known to be bonafide.
I am literally being driven mad going around in circles on forums and sites to keep going back to square one.
Any help will be very gratefully received. Or I'm afraid this may mean I'm going to smash my new phone int a wall and never use a smartphone again, because obviously I'm too stupid to play around with them on my own.
I really appreciate your help if someone would be able to invest a little time here.
Thanks very much for your time, guys
Jobeeey
additional info
Right, these are the instructions I found on this forum, but I'm unclear if I'm approaching this right..
Flashing s5830i with Odin v1.85
1.Turn off the phone and put it in Download mode by pressing Power+Volume Up+volume down.
2.Open Odin v1.85.Run as Administrator!.
3.Put the files in Odin and don't touch the settings
4.If it's a one-file firmware put it in PDA section.
If it's multiple put the files in the correct section.
5.Click start and don't touch the phone!Don't turn off computer and don't unplug the phone!It will reboot automatically and the first boot will take some time,so don't panic!
Click to expand...
Click to collapse
I've found a rom (which is a single file) and if I'm reading this right I place that in the PDA section of Odin after installing the usb drivers onto my pc (done that and windows recognizes my phone in the sense that it isn't now hassling me for drivers every two seconds).
Ok.. so I seem to have got the correct rom for my specific ace model.. and the instructions seem to be that I now:
1) Connect usb cable
2) Boot my phone into download mode (I can do that I think).. but at what point do I press vol down to download a new os.. before or after pressing start in Odin?
3) Open Odin and add file as in my attached screenshot (I can do that)
4) Click 'start' in Odin
5) Wait for my phone to reboot
And that should be job done, the phone should be flashed with the stock rom again and that should get me back on track, right? Or am I about to screw up my phone and ruin it even further?
Thanks for reading. I hope someone can advise if I'm doing this right as I've seen other forums say that I should tick the 'Re-partition' box, and other that say I shouldn't, and this one says nothing about it at all.
This is one of the tings that's confusing me, and once I'm now flashing a phone for the first time it's flippin scary to do it on my lonesome!
This is what I mean..
I've just tested going into download mode with odin ready, and the phone gets there (vol up+down + power on).. but each time it gets into download mode it seems to disconnect from odin and no com port is open. I get the windows device disconnected/connected beeping and the connection seems to sever.
What the Fffff...
This is exactly what I'm talking about.. nothing seems to be working like it's meant to be and I'm getting nowhere with any instructions I can find after god knows how many hours researching this.
:crying:
update (lol)
Mornin all,
So, just in case anyone finds this useful..
The flashing problem is kind of irrelevant now because:
A) Odin (tried several versions) simply will not stay connected to my phone when it boots into download mode, and having checked many tutorials for this it sees that this is a problem some of us cannot get past.
Anyway, one of the methods to resolve this was to wipe the cache and clear all data etc, which I did, and now my phone is stuck on the "pres the android" screen, and my phone will no longer get past that. Tried pressing clockwise in all four corners but still nothing.
No probs.. so we move on to a new step of trying to split the roms via cygwin, but guess what? Every single time I try to download the cygwin files, that freezes at about 98% and will not download, no matter which mirror I select.
So, this is what I call a curse that isn't going to be lifted by me no matter hat. It's not not meant to be.
Therefore, what I'm going to do is take it to a local shop that unlocks mobiles and give it to them to flash back to stock rom for me.
If that doesn't work, do you know what I'm gonna do?
Nothing. Because there's nothing you can do when the processes do not follow the same progress as they do in the tutorials.
I hope other novice S5830i users save themselves all his time and trouble and don't bother following the same process and become locked out of their phone at the touch android screen.
Update
Yipee,
Right, I stumbled across a solution that worked for me.
What I did was get my 2gb msd card that came with the phone and slapped MindCR v1.0.12 on the card and whacked that in my phone (this bypassed not being able to get a new rom on the sd card as it wasn't unmounted before the crash, so my pc wouldn't recognise the date to put it on via the pc).
Then I updated the rom from that 2gb card (vol up + menu + power to get into recovery mode) and it took it a few minutes to update the firmware and give me back the full use of my phone, and with a shiny new os on it. Whoop!
I didn't bother with CWM as I'd forgotten to add it before flashing, but it worked none-the-less and I'm now back in business (wiped it manually).
As it turned out this version of MindCR works really well so far as I can tell. I realise there are updated roms now but I've come to the conclusion after the scare I had that if you're not entirely sure what you're doing, it's best to leave it alone if it ain't broke.
SO.. now I have a phone with what seems to be a better os than the stock and less bloatware on it, no phone problems I can see after thorough testing... and from what I can tell it turned out to be better than it was before the disaster.
And I learned a bit in the process. Like for example, don't feck around removing apps from smartphones with titanium unless you've backed them up and you're prepared to stress out for over 20hrs wondering what to do about it.
And, also, don't expect much help from a forum because you may not always get it. << That' not a dig at xda by the way. It's just a BIG forum so your threads may not be seen by the right person before they get buried in past pages.
Hope my little journey helps another unsuspecting S5830i user who comes across the thread.
Basically I bought Samsung Galaxy A5 2017, which was branded. Whilst I was using it the phone had all the operators’ apps and themes which I didn’t want. Also the whole phone was even crashing sometimes and was slow. I found a YouTube video showing how to de-brand my phone, and I’ve managed to de-brand it following some steps, after I have successfully de-branded my phone it automatically installed 7.0 Nougat and it got rid of all the crap inside, and then the phone was faster and smoother. Keep in mind I only de-brand it I did NOT root my phone, I also checked whether it is rooted or not from the root checker.
However as I was playing around with it and I found that I can’t access two apps ‘S Health’ and ‘Secure Folder’, for both of these there is some error message coming up, it says this:
S Health: Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices (0x100030522830)
Secure Folder: Secure Folder cannot be set up because unauthorised software was installed on the device.
I know this is the result of my phone being de-branded and maybe the current software is not compatible, I don’t really know, I have check all around the internet to find if someone has this problem and a lot of people have this issue but the way how to fix it is not clear, I couldn’t find a video which would explain clearly how to fix it and there isn’t much on forums either.
Please if anyone could help me solve this problem, my phone is new and I haven’t got much stuff there so if this problem would be fixed by erasing data like a factory reset then I don’t’ have problem with it, I also don’t mind rooting my phone, but I would prefer to have it unroot at least for now but if there is no other way then I’m fine to root it, it’s just that I need to know how to root it and I have to be sure it’s going to work, because I’ve seen that there are several roots and ways you can do it. Therefore I need to know which one is the most appropriate for this matter. And can I go back to the unroot state after I've rooted my phone?
And also can someone tell me. What if I wait for software update for example new Nougat 7.2 maybe it will fix this problem, or is it better just to fix it now whether or not it has to be rooted and don’t bother waiting. If the new software update can get it fixed and it’s guaranteed that it will. I can wait a bit, it’s not a big deal, but I would like to really use those two apps really soon.
If you have any questions or something wasn’t mentioned please ask.
Thank you for your time
Hello,
I wasn't 100% sure if this was the correct thread or if I should have posted under the ROM section for this phone. We own a start-up company, and have signed some contracts with some larger companies. In one particular contract, we need to take certain security precautions.
My wife has purchased me a Samsung Galaxy S7 SM-G930W8 (the Canadian model). I live in the USA. It's unlocked and multi-csc (whatever that means). The product code is XAC (I believe that means unlocked). We contacted Samsung to verify that a USA sim card would work in the phone, which it does, and that it wouldn't lock the phone to that sim card, which it doesn't. So we're good there.
We explained the issue about the software. The phone comes with some software pre-installed that we cannot have on the phone if we're going to be using it as a company phone, which we would like to do. Samsung said we could disable most of the apps, which we were aware of, however, the contracts specifically states certain types of programs cannot be installed on our company devices.
I asked them if I where to gain root access and remove those programs, would it void the warranty. They said no. The only way we would void the warranty is if we dropped the phone and damaged it, or got it wet.
What would be the best way to go about removing these programs and trying to get a more cleaner version of Android? I understand that a ROM would have to be specific to this phone, because of the various hardware in the phone. But we are not looking for any "extra" programs that tend to come with ROMs to attempt and make them better. I noticed some ROMs for this phone include a custom installer, where we can pick and choose what we wanted installed. But they also come with customized kernels with various security features disabled (such as a fake version of KNOX).
Could someone recommend the best route to go here? Stability is extremely important, however, so is security. We cannot have unapproved third party apps / mods on the phone, but we have some leigh way there. For example, I could probably get around installing a custom recovery partition because the code on that custom recovery partition is not running while we're accessing company resources. If we have to go the route of using a custom ROM, we'd prefer one that supports over the air updates, but does not force them.
Any ideas?
Thank you and sorry for such a novice question. I had done a good bit of research into this and thought I found the perfect one, just to discover that it appears to no longer be supported and the thread on XDA has been deleted.
**EDIT: I should add that my wife upgraded it to Android 7, but I was afraid that would limit our options, so I downloaded the stock XAC ROM for this phone and used Odin to flash it back on, so it's currently running 6.0.1. I'm not sure if that makes a difference or not.
Thanks!
Am I reading correctly that you must completely remove the apps from the phone, not just disable them? The thread below describes how to disable system apps without rooting or otherwise modifying your phone's firmware.
https://forum.xda-developers.com/galaxy-s7/how-to/root-required-oreo-disable-apps-t3814249
Flashing modified firmware will disable Knox, which is something you might not want to do in your case. Also, if you're contractually bound as far as security precautions go, you're probably going to want to update to the latest Oreo firmware and keep it up to date with any security updates as they are issued by Samsung.
Hai Karate said:
Am I reading correctly that you must completely remove the apps from the phone, not just disable them? The thread below describes how to disable system apps without rooting or otherwise modifying your phone's firmware.
Click to expand...
Click to collapse
I apologize in advance if I get your gender incorrect, a quick google search shows your name is unisex. I am going to assume you are a male, until otherwise told so. Yes sir, you are reading correctly that I must completely remove the apps from my company devices, including this phone. I appreciate that my wife bought it for me, but she doesn't fully understand the business like I do and I don't think she really thought it through. I imagine it costed a good bit of money, so I'd hate to have her send it back because I cannot remove the apps.
I appreciate the links to the threads, however, I already know how to disable the apps, but that is not enough. They physically cannot be installed based on what they're capable of doing (ie, a potential for viewing documents / schematics / pcb layouts labeled as confidential or highly confidential, or even worse, being poorly written in such a way where the program is exploitable and someone gains unauthorized access to our network, the certificates we have installed on the phone, etc.)
Hai Karate said:
Flashing modified firmware will disable Knox, which is something you might not want to do in your case. Also, if you're contractually bound as far as security precautions go, you're probably going to want to update to the latest Oreo firmware and keep it up to date with any security updates as they are issued by Samsung.
Click to expand...
Click to collapse
[/QUOTE]
Updating to Oreo is something that we will be wanting to do, but something I have been holding off on, in case I have to flash a modified firmware, or ROM as it's sometimes referred to. As for Knox being disabled, I actually believe that is something we are going to need to happen, have it disabled. We use special software that provides similar functionality that Knox provides, but is a lot more advanced. We actually use a few products for that.
I do have to admit that my knowledge regarding cell phone firmwares is a bit limited, although I do write firmware for other custom created devices. My worries with custom firmware are:
1) Certain security features (excluding Knox) might be disabled or removed (ie, the ability to encrypt the internal flash, encrypt the MicroSD card, having SELinux turned off, having secure boot disabled)
2) The firmware containing programs that most people would find useful but stuff I cannot have. If I have the ability to uninstall it, that's okay, I can do that. But if it's stuck, like it is now, where I can only disable it, that is not okay.
3) Something being installed without my knowledge.
Our security setup checks company phones to see if they're rooted, and if they are, it marks the device as non-compliant. I can have a device as non-compliant for a few hours....but if it's marked as non-compliant for a few days, one of the larger companies we're dealing with call to ask why, and then we have to do a secure session, where they login to one of our devices, but cannot physically click anything, just look, and have us go into various software to see why it's non-compliant, and, well, it's not fun.
We had it happen once because my wife accidentally sent an email from a personal device to a in-house email address, which never got encrypted, and it triggered a security audit, which was not fun at all and I'd rather not go through that again.
Are there no bloat-ware free signed official images or is there no way for a developer to import a signing key into the device to keep secureboot enabled? Also, out of curiosity, why would running a custom firmware disable Knox? In our case, that's something we need, however, I was just curious. And if we go the route of custom firmware, is there a way to show that it's gone, or will all the custom firmware's install a fake version of Knox?
Thank you for taking the time to answer my questions. I really do appreciate it. I know how precious time can be, how busy a person can get, and I realize I have a lot of questions here, but I really need to make sure we're secure.
One of the programs we'll have on there is something called Symantec Endpoint Mobile. I am not sure if you have heard of it or not, but that provides virus protection, etc.
So CSC contains the regulatory information for my country and the providers....my phone is a Canadian phone. I thought Canada did not have Straight talk, yet, my wife's straight talk sim worked. I noticed in the recovery menu, it shows multi-csc. Does that mean my phone has the country specific stuff for more than one country? I'm wondering if I should try changing it to a US phone.
AP contains the kernel, the recovery partition, the system partition, and the bloatware, right?
BL is simply the bootloader.
If I could gain root on this phone without flashing a custom ROM or maybe somehow by just flashing something like TWRP without voiding the warranty, I could just modify the meta-data for the apps that I need to uninstall to allow them to be uninstallable, correct?
Since I went from a partial install of 7 back down to 6.0.1, my camera does not work. I'm wondering if it's because the ROM I used wasn't the correct ROM. It was the G930W8VLU2API1 ROM, minus the CSC, which was G930W8OYA2API1.
I've tried a factory reset, I've reflashed the ROM, using the non-HOME CSC, I've wiped the cache partition....still no camera. It simply says Warning Camera failed. I tried a few of the tricks I've read about on the net to fix it, but so far, no luck. Cleared the data and cache for just about every program, including the camera. I believe the problem might be because I have internet turned off right now, no sim card in, and even though I have automatic updates turned off, the phone still started to download an update.
Did Android 6.0.1 show Secure Boot status in Download mode? My wife, with the same phone, but the American AT&T unlocked carrier version (we paid full price), her's has a Secure Boot: Enabled. She's also running 8.0.0. With my 6.0.1, all there is is a Secure Download, which she also has, but no Secure Boot listed at all.
If secure boot is disabled, I should be able to flash any custom BL without tripping Knox, even if it's not signed.....right? I know with my datacenter, the bootloader changes even a bit, the servers and workstations are not booting, unless I sign the bootloader with my MAK.
**EDIT: Also, what exactly are these z3x things I see on the gsmhosting site? It's hard understanding exactly what they do based off their description because I don't think the developers native language is the same as mine. I go to z3x-team.com, and it almost looks like the device can do almost anything with the Samsung....upgrades, downgrades, unlock codes (wtf?), etc. Is it just a scam or are they worth the investment?
**EDIT2: I made a mistake. I guess there's some special Samsung Knox policy that gets applied to Samsung only devices, that configures it in some sort of way to make it compliant, so Knox has to stay.....
Background: my wife arrived home yesterday with a Samsung Galaxy Tab A 10.1 2016 model (SM-P585) that had been written off by her company due to lockscreen protection being enabled and no one knowing who the last person was that it was issued to.
I kid you not.
Anyhow, one quick Odin flash later and it's booting up happily. However, FRP was enabled and now requires sign-in from the last person to have signed in on it, which is unknown. So I find myself one last step away from an awesome - and surprisingly well looked after - tablet but with no idea of what to do about FRP.
I've done a fair amount of reading and, outside of all those sites that seem to be run by the same Asian gent who is adamant I can only do it with his absolutely-not-suspicious-at-all application, understand that I can either flash 1) a combination file or 2) an old firmware in which the old workarounds are still effective, both of which will allow me to bypass it, but neither of which will work without USB debugging enabled and that can only be done via the developer options. And obviously I can't get to that.
If anyone has any advice on how I can make this work in my favour without having to get rid of it, I would sincerely appreciate it.
Alternatively, if this is the wrong place to post this question, a quick point and a kick in the ass in the right direction.
[Quick edit] I have no issues with rooting if that's what's required. Again, requires developer tools so...
Hint: Add " SM-P585 " to front of this thread's titel thus mainly people who owns such device get addressed, too.
I thought of that, but I don't believe this is an issue limited to my specific device model. I think it could apply to most, if not all, Android devices at some point.