Device owner already set before purchasing? - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting

I did a factory reset and wiped the cache, several times in a row last night, because I got sick of a few things and wanted to run a test.
I wanted to install IceBox Apps Freezer. You don't need root, so long as you set it to be 'Device Owner' using ADB shell:
Code:
adb shell dpm set-device-owner com.catchingnow.icebox/.receiver.DPMReceiver
The app says to remove all accounts associated with the device in order for that to work. On our tablets (all models) this isn't possible. So I had to find out a way that would clear all 'device owners.' Google itself is very specific about how this is to be done: Factory reset.
Caution: If provisioning has already started, affected devices must be factory reset first.
Click to expand...
Click to collapse
Since I did that, and didn't register the tablet with Amazon, Managed Provisioning shouldn't apply. However, I followed all the steps, made sure WiFi was and still is off and went into ADB and this is what I got in return:
{
"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"
}
Trying to set device owner but device is already provisioned
Click to expand...
Click to collapse
Um what? Is that even legal?

have you seen anyone having success with Amazon devices?
it's possible they didn't include this feature

yossijoe said:
have you seen anyone having success with Amazon devices?
it's possible they didn't include this feature
Click to expand...
Click to collapse
As far as I can tell, through all possible methods to gain Device Owner, Amazon has provisioned the devices, en mass, before they are even purchased. Likely done with NFC which is included on the Fires, but is another piece of software Amazon blocks us from accessing and or using. Even a factory reset and attempt to add device owner on language selection screen failed.
IMHO this really should be illegal. What the hell did we actually buy then if we don't own these?

Related

Need help about this weird issue

hi everyone,
I have this issue: zygote is asking for root permission under S7 Edge 6.0.1 superSU Pro 2.79-SR3 and I want to get rid of it, keeps popping every 30 to 40 min. Any help would be great
{
"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"
}
That is weird. Zygote is an Android daemon that is used to launch apps. It shouldn't be requesting su permissions from the user. Do you give it permission or do you deny? Are you on a custom ROM?
Bigbabyjesus said:
That is weird. Zygote is an Android daemon that is used to launch apps. It shouldn't be requesting su permissions from the user. Do you give it permission or do you deny? Are you on a custom ROM?
Click to expand...
Click to collapse
thanks for responding, I'm on stock Rom and I allways deny permission without any issue in launching apps, everything is smooth without errors. I did some researches on that case, and I've found that it was impossible for Zygot to ask for root permission, so I guess it's just a malware, but it's not detected with Avast Pro, I'm really confused
Do you install apps from anywhere other than the playstore? Maybe you need to wipe and reinstall stock through TWRP. It can be hard to find malware by hand.
Bigbabyjesus said:
Do you install apps from anywhere other than the playstore? Maybe you need to wipe and reinstall stock through TWRP. It can be hard to find malware by hand.
Click to expand...
Click to collapse
Yep I Have some alternative shops, I suspected that they were the gate from wich the malware came from so I deleted all of them except Aptoid, but the Evil is already inside now. BTW a wipe is not even to considered since I don't have time to reinstall and reconfigure more than 30 handy tool apps (drive droid, Exposed and its modules, lucky patcher and many more .....). thanks for caring, anyway I'll try to uninstall suspected apps and see.
Good luck.

A way to unlock hardbricked Meizu Pro 5 ?

Hi,
I've hard bricked my Pro 5. No recovery access, no boot to rom, locked bootloader. After many search i see this : https://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678, but this is bull-****.
I test many manipulations to get something on my phone other than "Bootloader, Locked".
So i dicovered this : Press and holp Vol + and Vol - and press one time power button. We get this :
{
"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"
}
After research about this, we get this :
http://forum.gsmhosting.com/vbb/f777/galexy-s6-exynos-7420-dead-1975230/#post12369382
And this :
http://www.mediafire.com/file/9qmezaezy1fyzrr/Galaxy_S6_Boot_recovery.pptx
Possible way to unlock hardbricked Pro 5 ?
Same way exist for Qualcomm Processor : http://www.androidbrick.com/unbrick...-have-the-right-kind-of-rom-qhsusb_dload_edl/
Subscribed, i do also have a spare "bricked" device
same problem here bro.tried everything..only mode available is fastboot and locked bootloader.in pc device manager i get unknown android 1.going to investigate the problem futher more.pls keep us in touch.tnx
barbonee said:
same problem here bro.tried everything..only mode available is fastboot and locked bootloader.in pc device manager i get unknown android 1.going to investigate the problem futher more.pls keep us in touch.tnx
Click to expand...
Click to collapse
Hey there. Got the same problem. Tried everything. Nothing happens. Have you got your problem solved yet?
The same problem
Sent from my PRO 5 using Tapatalk
Only way to solve this is taking the phone to technical service. Done it myself. Be careful tought, they will try to make you change the entire mother board (280€), but if you insist they will "find a way" to install the correct software in your phone and leave it as if it was new
it is possible to recovery via dongle ... but sn and imei can be lost
Try this thread.
https://forum.xda-developers.com/me...hard-bricked-lost-t3838461/page2#post79752427
Try this thread; it worked perfectly for me.

Axon 7 Nougat Root

Hello guys.
What is the status about the root / bootloader unlock for Axon 7 running nougat?
these are the specs of my phone right now, and to be honest, after many years of being an iPhone owner I feel kinda lost regarding the root techniques.
{
"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"
}
WizeMan said:
Hello guys.
What is the status about the root / bootloader unlock for Axon 7 running nougat?
these are the specs of my phone right now, and to be honest, after many years of being an iPhone owner I feel kinda lost regarding the root techniques.
Click to expand...
Click to collapse
NP just read Controllerboy's guide if you have an A2017G.
But before that, be warned about 2 things:
Your data will be wiped after you unlock the bootloader, and if you unlock it you'll probably be wiping and trying ZIPs every once in a while, so get used to backing up stuff and using Google for contacts etc.
That guide was for Marshmallow I think. You can download version B10 or B11 from ZTE's website, then unpack it until you get an update.zip (it should come as a zip with a bunch of numbers, and inside it there's a zip matrioska'd inside). Put it on the root of your internal storage (root means outside of any folder) and go to Settings the Updates. It should find the zip and install it. After that go to Developer options (to enable it go to About phone and tap Build number a buncha times, then it should appear above About phone) and enable Enable OEM Unlock. Now you have Marshmallow and can use the guide.
Another way is doing all the procedure up there but using axon7toolkit instead of that guide. Never used it for this procedure but it should work just fine and do the same. You can get more experience from using the guide though, and that experience may come in handy if you ever tinker too much

Stock S8 (UK, Three) - CTS profile fail

I purchased a refurbished S8 (SM-G950F) from Argos eBay a few months ago. Phone seemed in perfect cosmetic condition, but the software side of it has started to annoy me.
I couldn't get banking apps to work correctly, then found out that when running Safety Net I get "CTS profile match - Fail". I've done nothing to it (root, ROMS etc), so can only assume it's something to do with the bootloader in the refurb process?
Also, weirdly, in "About Phone", the "My Phone Number" is totally different to mine.
Phone is currently on Nougat. Would it have had Oreo installed OTA if it was passing Safety Net?
What options do I have with regards to making it pass CTS profile match? Would flashing a new stock ROM be a waste of time if the bootloader has been modified?
Thanks in advance.
Sounds like the bootloader has been unlocked, try using magisk and magiskhide to hide root from your banking apps. Works for me on the Halifax banking app
Trying to install TWRP via Odin (to then get me to installing Magisk) but I'm going round in circles.
Everything I read online says you don't need a PIT file in Odin, but this is what mine is showing (JOdin3 on Mac OS, FYI)
Downloaded TWRP file and added to PDA section
{
"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"
}
Click Start, and get this popup
If I select a PIT it tells me I have I to re-boot phone, but when I re-boot into Download mode, it won't connect in Odin!
So it took me a bunch of attempts and a few times where I thought I'd soft-bricked it, but managed to install Magisk (and updated to Oreo in the process)
Ended up borrowing a legit Samsung cable, and doing it all on a Windows machine.
Also now have Google Pay working and fingerprint login on my banking app

SM-A510F : Forgotten lock pattern

Hey guys,
I'm posting here as a last resort before a factory reset.
By the way, let me first say that I'm sorry to post this here, as I know it's SO stupid, what's happening.
I had the same lock pattern for 2 years now, never had a problem.
Last week, it just fell out my mind completely. I've been trying for 4 days straight to remember it.
It's quite a complicated one, with the pattern tracing deactivated so I can't remember the shape and my thumb tried with its motor memory but to no avail :x
The thing is, I extensively use the notepad stock app (Samsung Notes ? Android Notes ?) and I have a **** TON of info I REALLY don't want to lose. And it's not on the SD card, ofc.
I don't care much about the rest, to be honest.
Fun fact, I only synced contacts via the android sync function.
So how can I either remove the lock pattern or access my phone files with an explorer on my computer (I guess I can find a memory file for the notepad somewhere), knowing that :
- Not rooted
- USB debugging not activated
- Not registered with Samsung account
- Android version is the latest available in France for an SM-A510F as I do all updates
I can provide as much as I can to prove my ownership of the phone if needed.
Thank you for reading and maybe for helping.
You have absolutely every right to laugh to my (dumb) face.
EDIT :
Just tried something else. Booted in recovery to try an ADB command.
Since Windows didn't recognize the phone in recovery mode, I selected the option "Load package with ADB" or something like that.
Now the phone was listed in devices on ADB and I tried this : adb shell rm /data/system/gesture.key
Result : error.
Great.
So since the phone was unresponsive to any button, I waited and there was a timeout on the package load.
BUT NOW...
I have a blue screen that says "Error!" and it's completely unresponsive.
GREAT.
I'm off to work, read you soon.
XOXO
{
"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"
}
<Mod Edit>
Thread closed by OP request.

Categories

Resources