Stuck on Chrome Os verification is turned off - chromebook

I have an outdated Samsung Chromebook Alex 5 running ChromeOS 58.
However, I am trying to enter developer mode so that I can have Linux on the machine and enjoy my other world, but then, that seems not possible as I cannot get past this Chrome OS verification is turned off screen after a reboot
I have tried Ctrl + D key combinations but can't get past these screen.
But I see that I can type some thing but can't do anything with what I type.

Related

VS2019 Xamarin Forms Remote IOS simulator Black screen - How to fix?

Xamarin Forms Project
Microsoft Visual Studio 2019 Version 16.9
Xcode on Mac version 12.4
Using IPad Pro 11 inch running 14.4 as the simulated device and IOS version.
( I tried other simulators )
If I build and run Simulation on the Mac, it works. So i believe it is a remote simulation issue.
If you set IOS simulator to remote it starts and appears to run the simulation
in the simulator but it just shows a black screen.
Ive updated everything I can think of. Mac OS, XCODE on latest available.
Visual Studio, W10, all latest available and everything restarted...
Still it doesnt work. You do see brief at time of deployment dots spinner that reminds of the spinner when shutting down.
How do I fix the back screen simulation. ?
EDIT: With Latest Updates, it works again.
After upgrading to VS2022, upgrading Xcode on the mac.
Even the simulators are now ios15.x
Somewhere is all those updates the problem is gone.
You could have a try with Forget the Device first:
Next step, better need to reboot Mac .
Last, Pair to Mac again with Add Mac manually:
If it also can not work, maybe need to check the quality of network whether is well.

Xcode 6.1 and iOS Simulator 8.1 very slow to run

I'm using Xcode 6.1 and iOS Simulator 8.1. It takes a long time to run the simple apps that I've written using the iOS Simulator. Build process was ok but then the iOS Simulator will show the black blank launch screen then the app screen for like 5 minutes before the app launch. Many times it shows error "Lost connection to iPhone 6(/5/4s)". Tried to re-start Xcode and iOS Simulator, and MacBook Pro multiple times already. Tried to reset "Content and Settings" in the iOS Stimulator, but doesn't help.
What could be the possible causes? Any advice/solution? Thank you.
I suggest that you boot up the device that you want to use prior to the Build&Run in Xcode. If you hit Build&Run in Xcode while the device is not booted, you will need to wait for the device to boot. This can take a long time depending on your I/O load (eg: if Spotlight is indexing at the same time you are trying to boot, or if your home directory is on a slow volume like a network mount).
Just open up iOS Simulator.app ahead of time and select the device you want to test on from the Hardware->Devices menu. Then it will be ready when you need it.
Make sure 'slow animations' is not selected under the Debug tab in the iOS Simulator. That fixed the issue for me.
Googled on this issue and some said it's a Xcode bug with the 6.1 beta, but I had the 6.1 release version installed alreadt. I even try the 6.2 beta, hoping Apple has a fix for this, but no luck, still the same.
So desperate that I decided to upgrade my 3 years old MacBook Pro RAM and harddisk to SSD. Problem solved with the upgrade! The iOS Simulator runs normally now.

My iPhone no longer shows up in organizer

I deleted the provisioning profile to fix this to no avail.
I connect and everything.
Itunes can detect my phone. I can't do the same. I wonder why.
This happens since I installed XCode 5 beta. I CAN access my iPhone from that Xcode 5 Beta.
Now I have uninstalled Xcode 5 Beta, upgrade my original Xcode to 5 and I still cannot see my iPhone.
My iPhone should show up in organizer when I plug it in right?
As Vision says
Use a legit Apple cable!
If you have installed iOS7 a lot of fake cables doesn't work anymore.

Running iPhone 5 Simulator on Snow Leopard

I am running the iOS6 SDK on my mac running Xcode 4.2 on Snow Leopard using steps from this Stack Overflow post.
I'm now trying to get the iPhone 4" screen to work. I have been able to get iOS 6 to show up in the iOS simulator under the Hardware > Version menu. When I try to load an iOS 6 device, I get the error: "The simulated application quit" - "Click Relaunch to try again". It then gives me an option to switch to a different SDK. If I choose iOS6, it again crashes. If I choose iOS 5, it loads correctly.
I also don't have an iPhone 4" screen option under the Hardware > Device menu.
I have copied the iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator6.0.sdk folder from the Xcode Disk Image to my computer.
I'm not able to upgrade my computer past Snow Leopard.
So I need to be able to:
load iOS 6 in the iOS Simulator
load an iPhone 4" in the simulator
Problem is Xcode 4.5 on your mac.
The original post says how to run ios 5.1sdk on "Xcode 4.2 on Snow leopard".
Xcode 4.5 is not available on snowleopard.
Install Xcode 4.2 and follow the steps again.
Another idea is to use Virtual Box and run XCode in it. Of course, running OS X on virtual box is quite difficult and not entirely legal (although you do have a Mac, so it can be justified). You can follow this link if interested.
http://www.sysprobs.com/guide-mac-os-x-10-7-lion-on-virtualbox-with-windows-7-and-intel-pc
It's for windows 7, but you should be able to get it to work on OS X as well.
I VMware Fusion 5 (and maybe 4 also, I don't remember) allows Mac OS X Lion and Mountain Lion to run in a VM. So you could install VMware Fusion, and use it to run a virtualized instance of Mountain Lion. Since the hardware is virtualized, it shouldn't matter that your Mac doesn't support anything newer than Snow Leopard.
Performance will likely be poor, though - my experience is that you need at least 4 gigs of RAM for VMware Fusion to run smoothly. If your Mac is too old for Lion and Moutain Lion, it'll probably won't have that amount of RAM installed.
It's said that Xcode 4.2 is the last supported version on Snow Leopard. So no it won't work and you'll have to get Lion.
I found the answer on another StackOverflow post
You would have to be under Lion in this case with both Xcode 4.2 and
4.5 installed. There should be no problem with this.
Don't forget...
As stated in a Stack Overflow post
"I installed Xcode 4.2 on a Snow Leopard and when iOS SDK was published I imported the iOS 5.1 SDK" Look at another Stack Overflow post
Use the 2nd post link. It works perfectly, just copy "6.0" instead of "5.1".
Don't forget that you could just use an external iOS device that can run iOS6
You could always ask for support from developer.apple technical support
Delete your simulator and re-download

Xcode 4.2: Error 0xC002 when trying to use a jailbroken iPhone 3G for development

I have this jailbroken iPhone 3G with iOS version 4.2.1 (the latest supported version). When I connect it to Xcode 4.2, Xcode starts copying the debug symbols. It stops copying towards the end of the process, and shows the following error:
Xcode has encountered an unexpected error (0xC002)
No such file or directory, at ‘/SourceCache/DTDeviceKit/DTDeviceKit-867/DTDeviceKit/DTDeviceKit_Utilities.m:864’
Anybody experiencing anything similar?
I know I should try and restore the phone, but I'm asking just in case anybody can come up with a solution that doesn't involve restoring it.
In this post on mactechnews.de, one guy reports the same problem -- with no solution, so far.
Alright, after a lot of testing and digging up the filesystem... I solved it.
It turns out that there are just a few files that are not downloaded from the device (for reasons still unknown). They are related to the dyld cache (don't really know what this is and what it's for). Here are the steps to make your 4.2.1 device debuggable in XCode 4.2 and 4.3.x:
Close Xcode
Go to: ~/Library/Developer/Xcode/iOS DeviceSupport/4.2.1 (8C148)/Symbols/System/Library/Caches/com.apple.dyld/ Note: if you don't have this folder, run Xcode, connect your device, and wait until the error 0xC002 appears in Organizer - the folder should be created by that time.
Create 3 empty files there called:
.copied_dyld_shared_cache_armv6
.processed_dyld_shared_cache_armv6
dyld_shared_cache_armv6
Run Xcode and enjoy the light next to your device eventually go green:)
Or, for the terminal lovers:
cd ~/Library/Developer/Xcode/iOS\ DeviceSupport/4.2.1\ \(8C148\)/Symbols/System/Library/Caches/com.apple.dyld/
touch .copied_dyld_shared_cache_armv6
touch .processed_dyld_shared_cache_armv6
touch dyld_shared_cache_armv6
This is obviously a hack but it works perfectly for debugging and I haven't noticed any side-effects so far.
Enjoy!
Small update:
I tested it on my snow leopard hackintosh, with the Xcode 4.2 (most recent to date) and although the device is active in the organizer and it is possible to run the app on the device, i get black screen on launch. It gets installed but apparently debugger cannot get attached. I had the same problem with 4.0.2, when the 0xC002 problem didn't yet occur so I think it's unrelated and might even not happen to others. Nevertheless, 0xC002 is still solved.
On my main development machine with Lion and Xcode 4.3.2, device is perfectly debuggable.
The answer above (https://stackoverflow.com/a/9944892/1390251) works, basically,
but for newer versions of Xcode you probably need to rename the files as follows,
having them end with '7' instead of '6':
touch .copied_dyld_shared_cache_armv7
touch .processed_dyld_shared_cache_armv7
touch dyld_shared_cache_armv7
If not sure, you can keep both sets of files (...6 and ...7)
in the relevant folder (can also be 5.1.1 for that matter)
and it should work.
(have tested it on iPhone 4 with iOS v5.1.1 genuine)
It seems that you cannot debug apps on iOS 4.2.1. I tried several restores to iOS 4.2.1 with same effect. Downgrading to iOS 4.0 was the only thing that worked.
The reason for whole problem is that iOS 4.2.1 is not supported in XCode, according to this website.
Error in Xcode getting debugging info from 5.0.1 iphone
solved, see the link to archive with iOS5.0.1 debug info
download & unpack to "~/Library/Developer/xCode/iOS DeviceSupport/" & be happy =)
I fixed this bug in![enter image description here][1] this way:
I duplicate the 5.1.1(9B206), rename it to 5.1.1(9A405)[my ios device is this version], then the error is gone.

Resources