I have a customer that has an Asus Vivo with Windows 8 RT, and somehow he has lost/forgotten his password. I am new to the Windows RT environment, thus I can see why people dislike it. I was wondering if there is anyway to mount the Tablet to a PC to back it up; a way to possibly reset the password with out resetting the whole device to factory defaults; for I am lost and have searched the web for ways to do so, but no one seems to have an answer. Any help or suggestions would be very much appreciated.
Thank You
Jamie
If it was set up using a Windows Live account (or "Microsoft account" as they're now called), just use the standard paswword reset function on the website.
If it was using a local account (possible but not a great idea on RT) then the best bet is Safe Mode (Shift+F8 during bootup; might be possible with a Touch or Type cover but probably easier via USB) and log in as Admin, then force a password reset of the account. Possibly useful info: http://www.howtogeek.com/107511/how-to-boot-into-safe-mode-on-windows-8-the-easy-way/
As a side note, resetting the whole device, if it was using a Microsoft account, is relatively painless; your apps will need to be re-installed but you won't be charged again, your email and such will need to re-download but should already be configured, all in all it's fairly straightforward. Now, if there's documents on the tablet that for whatever reason aren't anywhere else... that's a problem if you reset it. No way to pull the storage and mount it in another PC, either.
What's your beef with RT from what you've seen of it so far (which it sounds like probably consists of nothing but the boot screen and the login screen)? It's only meaningful distinction from full Win8 is the need for ARM-compiled apps and the restriction of third-party code, but the first is a fact of life for any ARM-powered tablet (damn near all of them until quite recently; still most of them) and the second is easy to bypass. From an administrative position (i.e. trying to reset a password) it's identical to Win7.
I appreciate the quick response. Unfortunately this is tablet was not setup with a Microsoft Account, but was setup with a Local User account.
The only way it seems you can get into the options for boot with this tablet is holding the shift key and restarting it while you are at the login screen. I have tried to hold shift and tap f8 at a fresh start-up and the tablet continues to boot to the login screen.
Now when I hold Shift and restart the tablet, it goes right to Choose an Option, then I click Troubleshoot > Advanced Options > and there all I have is Automatic Repair, Command Prompt (Which you can't use without logging in to the local user account), and Startup Settings.. Under Startup Settings the only options it has is: Enable low-resolutions video mode, Enable boot logging, Dissable Automatic Restart on system failure, and Disable early-launch anti-malware protection.. It seems to me that this Asus Tablet with Windows RT does not have safe mode..
Thank You,
Jamie
Windows RT doesn't support safemode. It's possible to get at with some BCD tweaks, but it's not very straightforward.
Actually, pretty easy to get to it just using msconfig (assuming you can boot into Windows first). The downside: no touchscreen drivers, no Touch Cover drivers, no support for many of the peripherals. You'll need a USB keyboard, and probably a USB hub and USB mouse as well. A less "minimal" configuration might work better.
If you think there's a reasonable chance you'll need Safe Mode in the future, I recommend adding a second boot option to the main boot list (just clone the default one) and configuring it for Safe Mode. That's probably the easiest way... but it has to be done proactively.
GoodDayToDie,
Where you say "Actually, pretty easy to get to it just using msconfig (assuming you can boot into Windows first)," what do you mean by "(assuming you can boot into Windows first)?" I can boot into windows, but I cannot login because my customer has forgot his password.
This is a reason why I have an issue with Windows 8 RT, for there is no Safe Mode by default.. Micorshaft seems to be like Apple, thus locking the OS down to where you do not have full capabilities to fix an issue with there OS. It is too bad that you cannot run typical diagnostic tools off of a disc, because of the Hardware that they chose for the tablets... Only if they would keep a traditional chipset for both Linux (android) and Microsoft (Windows 8 RT), you could do all that you could with x86 and 64bit architecture. They need to keep things simple and compatible, instead of using prioritized junk.
Sincerely,
Jamie
I mean "boot into an interactive Windows session". If you can't get past the login screen, *you* aren't really into Windows (the machine might be running it, when I said "you" I meant you, personally). That's as true for RT as for any other OS.
Out of curiosity, what would you do if the client came to you with a BitLocked laptop and said they forgot the password for that? Well, obviously you'd tell them to use the recovery key. But it turns out they ignored the advice of the BitLocker installer and never saved the recovery key anywhere. Not good, right? OK, now what if it was a smartphone, and they forgot the PIN? There's a policy in place from their employer that ten failed PIN attempts in a row will will wipe the device. Now what?
They're screwed. Just like your client is here.
Look, the default configuration of Safe Mode on x86 versions of Windows is a security liability. It's a trivilally exploitable direct-to-admin elevation of privileges... assuming you have physical access to the device. On desktops, and to a lesser extent on laptops, that's not really a concern; the assumption is that if the attacker has physical access, it's already game over. On tablets, that's much less true. Tablets are sealed devices; there's no easy way to get the hard drive (or rather, the flash memory chip) out of one. They're designed to be highly mobile, and to a certain extent are designed to be shared - certainly many of them are used at kiosks and the like. They're also both easy and attractive targets for theft. The threat model is very different.
On x86 versions of Windows, if you're concerned about a local-access attacker, you use BitLocker and you set a strong password on it. You also change the admin password, so even if somebody gets through BitLocker (or they got to your machine while it's running already), they can't trivially gain full control over it. That's because protecting against local attackers is not the expected level of protection needed, so it's not the default configuration.
On tablets, if you're *not* concerned about a local attacker, you might do things like enable Safe Mode (which, from a security perspective, is actually Unsafe Mode), or disable BitLocker key protectors (possible even if an Exchange policy forces you to turn BL on). Similarly, if you weren't worried about forgetting your password, you might use a local account and not bother to create a password reset disk (yeah, that's still possible. Nobody ever does it, but it's possible). That's because the most likely attack, by far, will be somebody who has stolen the whole device and therefore the default configuration is to provide whatever security which can be offered in the face of such a situation.
Apparently, if you are worried about local attackers but *aren't* worried about losing your password, and then you lose your password anyhow, the thing you do is go complain to an IT shop. The IT guy then comes and asks an online forum how to do his job. The forum gives him the help they can. The IT guy then rants about Microsoft when the help offered is "insufficient".
Here, pop quiz for you: Which of the following people is it the fault of that the customer can't access their account?
1) Microsoft, who provide at least five different ways to reset the password (online account, password reset disk, enabling the Admin account for normal login, creating a second Admin account, or enabling a Safe Mode boot option) plus allow you to have the tablet remember the password for you (auto-login) or use no password at all.
2) Myself and the other members of this forum, who are offering what help we can, unpaid, of our own free will, because we care enough about this OS that we'll help people adapt to it and hope for nothing more than a "thanks"?
3) You and any co-workers you might have, who despite doing this for a living, are unfamiliar with the security model of a new OS... but are willing to pile abuse on that OS and its developers when they close a security hole that you expected to find open?
4) Your customer, who ignored Microsoft's advice about using an online account (justifiable, but a nonetheless questionable decision given the intended use of RT) and also ignored or avoided good password management techniques (like using a hard-to-remember password without creating a way to change or reset it, and without writing it down anywhere)?
I'll give you a hint: it's not 1 or 2.
Oh, and you can totally run diagnostic tools. Hell, the tablet comes with a bunch of them built in, but you can also boot off USB. Yeah, they need to be compiled for ARM, but - as I just pointed out - Microsoft ships a suite of them with the tablet. They even include a tool that can solve an unrecoverably lost password: wipe the system and start again. On previous Windows versions, you'd probably to do a full re-install at that point! Think of the time saved. However, "login as admin without any password" (what the default configuration of Safe Mode allows) is *not* a diagnostic tool. It's a gaping security hole.
Also, Safe Mode is totally still available. However, much like logging in *all the time* using the built-in Administrator account (possible by default on XP and before, disabled by default on Vista and later), allowing anybody who wanted to to boot into a full-permission no-password (by default) account was deemed too dangerous on RT. I was suprised when I discovered Safe Mode missing from the RT boot menu as well... for about 5 minutes. Then the obvious reason for it clicked. I went and enabled Safe Mode on my tablet anyhow, because it *is* a potentially useful diagnostic tool... (although, since neither theTouch Cover nor touchscreen work in Safe Mode, it's actually really hard to use) but I also changed the Admin password, so for your use case it wouldn't do any good anyhow. That's OK; I have the ability to reset my own password if needed. Admittedly, MS could have taken care of this themselves by removing the ability to log into disabled accounts when using Safe Mode, instead of disablign the mode by default... but that wouldn't have done you any good either.
I think the tl;dr version of what GoodDayToDie said is as follows:
The fact that you can't get into this tablet isn't microsofts fault at all, its the customers fault for being a complete and utter moron who can't remember a password and completely ignored the fact that the windows 8/RT setup process really wants you to make an online account rather than a local one which if he had done wouldn't have left us in this position.
Safe mode is a total security liability. That's why in my school they have disabled safe mode and also password protected the bios which is setup so you can only boot from the hard disk. There is then a sensor on the case which triggers when the side panel is removed which then causes the bios to prompt for password just after the POST check on next boot. Stupidly they have soldered the screws down on some machines, hilarious watching them trying to get the machines open again, they sit there with dremels trying to cut new slots for another screw driver why they don't just remove the solder with the hot air guns and soldering irons in the workshops is beyond me.
You might be able to edit the bcd to enable safe mode, but I suspect that the tpm will fail checks and refuse to give the bitlocker key if you do that. I know it'll cause integrity checks to fail on x86/x64. If you have the bitlocker key then you can mount it in recovery and back up all the files, but you'll only have that if it's a registered ms account, or the owner went way out of his/her way to get it beforehand.
As ar as MS goes, this isn't their fault. This is your customer's fault and nobody elses. Getting rude and arguing won't solve anything. There is no real need for safe mode on RT, except for security exploits such as what you want.
I did put Safe Mode on my machine... it actually doesn't appear t upset BitLocke to do it, so long as I suspend BitLocker once, reboot, and re-enable it. The check for "has my boot process been messed with?" happens right before where you would get the boot screen. Booting an alternate option from the Windows bootloader doesn't appear to bother it at all.
GoodDayToDie said:
I did put Safe Mode on my machine... it actually doesn't appear t upset BitLocke to do it, so long as I suspend BitLocker once, reboot, and re-enable it. The check for "has my boot process been messed with?" happens right before where you would get the boot screen. Booting an alternate option from the Windows bootloader doesn't appear to bother it at all.
Click to expand...
Click to collapse
Bitlocker checks the state of the BCD before it releases the key. By suspending and restoring it you're saying that the new state is what it should be at. If you didn't suspend it and edited the BCD it should refuse to boot.
I have determined that I at least will need to unlock my bootloader which I am already loathing since that means everything on my phone will get reset. We also don't even have signed firmware for this device. I don't care about root, but I also don't use any of this pay nonsense. I do play a certain game that will moan about my phone being modified though. I was already looking at the nougat thread regarding root and passing everything but I'm not interested in magisk and the headache that comes with having to deal with safetynet updates.
Far as I understand:
1. Get TWRP, can I get away with just booting it and not actually flashing?
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
2. I guess tomparr's zimage kernel zip found here: https://www.androidfilehost.com/?fid=457095661767134479 is required since the system is going to be changed for what I want to do
3. Steps somewhere a long the lines of this http://www.theandroidsoul.com/enable-tethering-nougat-alongside-android-pay/
a. Add the net.tethering.noprovisioning=true line
b. Open Terminal emulator on your device and issue the following commands one-by-one:su
settings put global tether_dun_required 0
exit
If I am understanding anything wrong or anyone wants to point me at anything else to read that would be great.
[rant] What an annoying experience this has been, before a few hours ago I praised motorola(lenovo) for what an amazing phone this was, that is until I got that ridiculous update pushed to my phone. Yes, it is definitely snappier and more responsive, but I'm not giving up functionality because the developer of the dammed OS caved into pressure from carriers. I bought an unlocked phone an no carrier has any right to restrict any of my phones features just because they think they can. I work in an office where login into the wif is a thing and I will have multiple devices with me sometimes, so I used to just bluetooth tether the other devices from my main phone and not have to deal with mutliple logins, there are also times when out and about where my gf's signal isn't great and she will use my data to be able to keep using her phone. DAMMIT THIS IS FRUSTRATING.... [/rant]
After purchasing several Optus X Smart 4G smartphones outright that are currently being sold in Australian stores I felt the need to make others aware.
Despite being branded as an Optus mobile phone it is actually an Alcatel mobile phone that comes shipped with some nasty packages, one being "Files" that after several days of enjoying your new purchase is upgraded to "File Manager" an application which now runs a boost application (Hawk Super Cleaner/ antivirus).
This boost application runs 24/7 and nags the user to click an icon then displays advertising. When you remove this application it defaults back to the factory installed version that does not contain "File Manager" stuffed with the boost aplication.
Being installed as an Android System App "File Manager" stuffed with Hawk Super Cleaner/ antivirus is granted with higher Android Operating System App permissions than the end user has limited controll over which brings privacy and security concerns to the device IMHO.
To stop automatic updates that will reinstall the boost aplication a user needs to log onto the Google Playstore and go into settings, then check do not automatically update applications to stop ALL playstore automatic app upgrades. Doing this in the phones bundled "Updates" aplication has no affect in stopping the automatic reinstall. Caveat being that Playstore app upgrades now ALL need manually input from the user who needs to remain mindfully to not update "File Manager".
The other option is to run "File Manager", go into settings and turn off the on screen alerts, this will allow "File Manager" stuffed with Hawk Super Cleaner/ antivirus to run 24/7 on the device and be granted with the many permissions you (like myself) may not want to (and never did) accept upon uograde / install,. However, the on screen displays will be gone from the phone.
Don't bother trying to stop it on the Android operating system level via options like disable app, do not allow peeking and rely on uninstall to the factory shipped version of the app as Android and Included bloatware settings do not act as expected and it will automatically install itself again, also displaying on screen despite the end users wishes and Android settings being checked.
Never being advertised that the phone would have on screen advertising to the end user or forced third party apps as part of the Android operating system I have made a complaint to Optus, the communications ombudsman, the "File Manager" developer, Playstore, Play Protect, XDA forum and anywhere else that I felt relevant.
My unconfirmed fear is that this device may allow the manufacturer to controll bloatware updates in the future via a command and control server rather than exclusively at the Playstore, hopefully this is an unjustified fear and one day the Playstore can clamp down on this type of unwanted and non authorised Android System App behaviour and put security fears to rest.
Currently awaiting an outcome
UPDATE: The Telecommunications Industry Ombudsman has forwarded my complaint to Optus for a resolve.
My argument was that Optus sold a product and forcefully allowed a third party aplication (Hawk Super Cleaner/ antivirus) to be side loaded and included as an Android system App, which in my opinion is outside the scope of Optus being simply a supply conduit to internet services as Optus now dictates what third party app the customer of this product must use 24/7 and without a reasonable opt out.
I have also suggested that Play Protect offer the end user the option to force a single Android System App from updating and add a detection flag for Android System Apps that stuff a third party aplication and byspass the new app install agreement methods used by the Playstore, AI is needed to detect mass user bases being unfairly exploited for the means of profit at the flick of a switch.
Hopefully the 4 devices purchased are given an easy Android System App uninstall option for bloatware that advetises on this phone by default, or get side loaded onto the phone without end user authorisation and after the purchase of the product has been made.
Otherwise replacement phones of similar specs that have Android as expected and advertised on the product box, and without forced Android System App advertising will be preferred for complaint resolution.
Now awaiting complaint communications from Optus.
Hi have you tried 'rooting' the phone to control the system better and remove that type of application? I have heard it may be the only way to stop such apps when standard obvious methods fail. (You will have to Google that as I know nothing more than what I have read). I would be pleased to know how you go with that as I have thought about doing it with my own phone but I haven't had as much of a problem as you are experiencing. ([email protected])
Put a custom recovery on it if there isnt one available im more than happy to build one for it if you would like and then flash magisk root
Install es file explorer, grant system root permissions and remove the file manager completely by deleting it then replace with another stock one in which you know has nothing being forced on you,
I was in the same boat have the optus x spirit next up from smart and the amount of 3rd party applications is to be quite honest shocking in my opinion i developed a TWRP for the X spirit and did exactly what i mentioned above no problems now
Rom for 5056i
Hello just wondering if possible to build a twrp or some rom to root this mobile of mine. Thanking you chaschas
Just a quick question to anyone how maybe be running Android 13 and also using Samsung gear/wear app.
Does the app actually work with devices connected? As in are you able to access features?
I have it installed and devices connected (Galaxy buds Live, Galaxy Buds Pro, Galaxy Watch 4) however in the app they appear to not be connected, and tapping connect does nothing. They do work (mostly). I am sure the app just needs updated for 13, but curious if anyone possibly upgraded from 12/12L and it actually works. I had a brain fart and ended up having to wipe device, so i just installed 13, but if anyone upgraded and it works, I will re-install 12 and upgrade through the normal path.
Make sure the Wearables app has all the many permissions it needs enabled or it will puke on you.
I just went through this with it. It seems Samsung changed and increased the number of needed permissions. Google play Services must be enabled at least initially for Wearables to detect the bt devices. If all of these conditions are not met it will behave erratically when detecting devices or completely fail to connect.
Also try a network reset.
Even on Samsung phones this app is a nosey Parker problem child
It gave me a run for my money...
blackhawk said:
Make sure the Wearables app has all the many permissions it needs enabled or it will puke on you.
I just went through this with it. It seems Samsung changed and increased the number of needed permissions. Google play Services must be enabled at least initially for Wearables to detect the bt devices. If all of these conditions are not met it will behave erratically when detecting devices or completely fail to connect.
Also try a network reset.
Even on Samsung phones this app is a nosey Parker problem child
It gave me a run for my money...
Click to expand...
Click to collapse
Thanks, ya I did all that. That also lead me to believe it has more to do with it needing updated for 13 as all the devices are allowed notification access, but wear asks to allow access. says it cant show notifications on the watch, even though all the permissions and notification access are allowed.
I'm looking for some help in finding a workaround for the pixels (6 pro, 7) dropping 5g nr connection due to lack of ims registration on Android 13.
My device is running build: tp1a.221105.002
Pixel 7 was a friends device running the latest.
Pixel 6 is working fine on Android 11. (I wish I could just roll back like we could in the old days...)
Test setup:
Ubuntu 22.04 desktop
Open5gs core
SRSRan_Project running on a b210, transmitting inside a faraday cage
USB C connect to phone through Faraday Cage USB port
Running scrcpy to monitor phone visually in parallel with "logcat -b radio"
So far I've tried using the *#*#0702#*#* ims menu. I futzt around with a menu called, "Edit Ignored CarrierConfig Filter".
Tried a few registrations with a handful or ims registration related toggles.
The most promising was: ims.ims_registration_required
But it didn't fix the issue. Still getting PDU sessions and just losing connection after a few minutes.
For more details check the attached logs, but in human speech; The device registers just fine according to the amf. The UE is even assigned a PDU session and I can access the internet to watch YT or ping around the network. But after 1~5 minutes (always random) the UE will use drop connect. The amf logs don't show an reregistration or UE-idle messages either.
For comparison sake I used a gold standard pixel 5 and pixel 6 running Android 12 and they work fine. Additionally, I found an S22 to try running Android 13 and that phone stays connected for hours when testing.
Before I set out to build the ims server using Kamailio, I wanted to make sure the phone didn't require it. When I move to 5g handovers I'd like to isolate the test using the RSRP to trigger by itself and not have to get lost in the ims networking handover also.
Thanks in advance for all the help!
P.S. I wrote this in a bit of a hurry. I'll make some edits around lunch.
Edit: Mixed up my android versions. Corrected.
stans_hands said:
Pixel 6 is working fine on Android 11
Click to expand...
Click to collapse
Didn't the 6 series launch with 12? Maybe I'm delirious but I'm pretty sure that's the case.
Also the 12 bootloader has been compromised. Is there a reason you avoid 13 (and coming later this year 14).
Good Call, Thanks for pointing that out. I mixed up the android versions. Correct now.
These phones are only for test networks I run as a hobby. I'm not hurting to use them so upgrading isn't a priority. For me learning is the goal, how the phones work and some of the more niche options hidden from regular users.
I'm hoping to make Android development my passion.
Update:
Rerooted the Pixel 6 with tq2a.230505.002
Problem persists.
Borrowed a friends Pixel 7 running android 14 and the problem still exists on even the newest Android.
Samsung and Sony might be the only good test phones at this point.