I tried rooting my S2 but something obviously went wrong. When i was finished rooting and tried rebooting it, it was just stuck on the bootscreen with the yellow triangle. I went to sleep and the next day it was still like that, so I went on the internet to find some help. I found the stock rom and kernel and tried booting that. Now what happens is that the boot screen comes and after 10 seconds the phone just turns off. When i tried unrooting it, i couldnt because Odin wont recognice my phone. I have also tried using Heimdall, but that wont find my phone either.
I have the international version, think it's called something like I900 etc.
I tried asking on Reddit and when they couldnt help me, they sent me here. I also discovered that i forgot to put the phone in debugging mode.
I can still acces the download and recovery mode, and yesterday i ordered a USB jig, that will be coming in the mail soon.
What should i do?
It seems you flash a wrong kernel/Image. Try to get a Orginal Kernel and a Orginal Rom.
Together with the correct PIT File.
Be sure to check if you have a 9100 or a 9100G .. this is different processor.
If you get into the Download Mode... all can be fixed.
If you get an Screen with 3 Symbols (Phone, Triangle, PC)
You are in the First Stage Bootloader, and must repartition Flash.
Odin should always detect your Phone.
Please search for Recovery Flash, or unbrick in some Android-Forums...
I don't want to link because there were many good sites.
Hope this helps.
PS: Flashing isn't automatically Illegal.
I'm Software-Developer and need sometimes to root Smart-phones, with custom kernels for different Projects.
For rooting There are 2 apps which will help you to have superuser permission on your device-one is superuser and the other one is
I recommend supersu over superuser.
Supersu also has an option to install via clockworkmod recovery(can be installed via rom manager) So it becomes an system app.
Related
i installed bluestacks on my windows 10 laptop (HP elitebook ) , it worked well the first time , i installed whatsapp on it ,it worked properly for few minitues messages started flowing but i couldnt get the chance to read them because my laptop frozes for seconds so i restarded it, the next time i started bluestacks after opening the laptop i found that it went back to initializing phase, i'm forever stuck there.
i'm not sure if it needs a good internet to initialize
for the second time?
if not , why it stucks in initializing , i tried multiple suggestions i found on internet (like compatibility solution) but didnt work out.
if there is nothing to do, how can i extract whatsapp database so i can read my chats on another device.
if i installed whatsapp on another device, i won't get the messages i recieved once on bluestack again,right?
please help me whatsapp chats are so important to me.
you can't able to restore those chats again
if you are using windows 10 directly download whats app to your lap directly from store or go to link https://www.whatsapp.com/download/
Earlier this year I moved to El Capitan on my MacBook Pro. Ever since I've been finding the h2 console very very slow. Here are timings taken today, no other apps running:
2 min 5 sec: Launch the console and wait for it to finish loading. Uses a shell script which does the following:
cd "/Applications/h2 1.3.167/bin"
java -cp h2-1.3.167.jar org.h2.tools.Server
2 min 48 sec: Click on the console's Connect button in my browser and wait for the database to be opened and the console to be ready to work
2 min 20 sec: Run a very simple query which the DB engine takes 18ms to process
21 sec: Click on the console's disconnect button and wait to be back at the "front page" for the console
This is on 1.3.167; I tried 1.3.176 earlier today, and it's just as slow, but it gives an error about my database contents once it's finally been opened, so I'll have to look into that sometime.
Has anyone else come across this extreme slowness? What can I do to solve it?
For those who may come along after me, here is the resolution (for my configuration).
It turned out the problem was that my machine name (in Sharing preferences) consisted of my first name and then an apostrophe and then "MacBook Pro". (for example, Santa's MacBook Pro) Except, the apostrophe wasn't: it was a smart quote.
No, I didn't put it there! I didn't even know until now that it was possible to do that. The Mac did it all on its own.
And, of course, the machine name was copied through to HostName. The smart quote was in there, too. Which was causing Java's StringCoding.encode() to have problems encoding the host name string in UTF-8. Which was causing DNS resolution to take 5s instead of 80ms. Which was making the h2 Console work glacially slowly...
Here are the two threads which helped me solve the problem:
h2 google groups
another thread here
Good luck! I hope your resolution is as simple as mine turned out to be!
I had the same problem, but it was actually
sudo scutil --set HostName asdf
That fixed it for me.
In my case, running macOS Mojave, I solved the slowness simply by using localhost in URL instead of my local IP which seems to be the H2 default.
I have installed Domino Designer in a Windows VM on VirtualBox on OS X.
When I start entering code in the JavaScript editor, Domino starts to work for every letter I type. The hourglass icon appears and the network symbol on the status bar flashes. This operation takes up to several seconds for every letter I type.
If I try to type anything before the hourglass disappears, the keyboard may hang up and the result is a long list of the same letters that I have to delete again (causing the hourglass to appear for each letter I delete again).
I have tried to disable functionality like "Content Assist", "Quick Diff" and other helpful stuff without luck.
I would really appreciate hints or tips to make this nightmare vanish...
I've not used domino designer, but first thought would be that your VM isn't handling the processing required by the designer.
What are the specs on you windows VM? Did you allocate enough RAM, for example? Make sure they match the requirements to run the designer:
http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1351628933716&osPlatform=Windows
Thanks to Joel for leading me into the right path.
I did several things, and together it now seems that I have a much better environment. I still see the hour glass from time to time, but it does not mess up my code anymore, and most of the time it does not bother me.
What I did was the following:
Changed the memory settings for Domino in this file:
[notes dir]\framework\rcp\deploy\jvm.properties
New values:
vmarg.Xmx=-Xmx1024m
vmarg.Xms=-Xms512m
vmarg.Xmca=-Xmca512k
Then I changed the virtual memory of my guest Windows install to a fixed swap file of 4096 MB.
At least I connected my Mac to a faster network using Thunderbolt to Ethernet cable adapter. I don't think the last thing did any difference, but at least I now have a faster and more reliable network connection.
I have a usb driver with multiple IOKitPersonalities each with a IOMediaIcon entry. all works fine if the usb devices are plugged in after the kext has been loaded (kext loads fine, is signed, etc.). but after reboot of the computer, only ONE of the usb devices shows the standard orange default usb image. if I unplug/reload kext/replug the usb device in, the image gets corrected.
Any thoughts?
(Details:
running Mac OS X 10.10.1 (I don't think I saw this problem before Yosemite, definitely not a problem on 10.6.8), all the Personalities are the same (except for the IDs (which are correct I think since the usb device loads correctly if I plug in after the kext is loaded) so it isn't mistake with the personality...)
I don't know how to fix your specific problem, but I can give you some pointers which may or may not be helpful (sorry, a bit too big for a comment, but not a proper answer):
The icon stuff is handled in user space, the only thing that the kernel should have to do in theory is set the IOMediaIcon before registering the service. Setting it in the personality should be fine.
In user space, Disk Arbitration takes over. You can download (most of?) the source code for it from Apple's Open Source Site.
A quick search reveals that the diskarbitrationd source code does indeed reference the IOMediaIcon, in DADisk.c
I don't know how well it works to recompile diskarbitrationd and substitute Apple's binary with your own, but if that works, maybe you can modify it to log output from the icon code, and get closer to your answer that way?
The other source of error I can possibly think of is that although the system gets the correct icon information, it can't actually find the icon file? I've heard about various bugs related to bundles and resources in the context of /System/Library/Extensions vs /Library/Extensions since they added the latter. If your icons are in your kext bundle, and you've switched to /Library/Extensions, try switching back to SLE.
I hope that helps your debugging efforts!
I would like to change the output mode of an Intel GMA450 based graphics chip to "cloned" mode.
Since the environment is a Windows Embedded Standard and only one of the connected monitors might be visible for the enduser, I would like to either permanently set the output mode to cloned or reset it continuously to cloned mode in case the actual mode differs (e.g. after a reboot, disconect/reconect of the second monitor or by other means).
Is there a way (Registrykey, API for the Intel driver, Win-Api) to change the display mode to cloned / dual output programatically?
Update:
I found the SDK for the IEDG driver it seems that I might be able to programatically set the resolution, clone mode etc.
However, I can't find the SDK or any information for the driver I am currently using: Intel® Graphics Media Accelerator Driver for Windows* XP, version 14.32.4.4926.
This isn't a good answer, but it might get you headed in a direction to figure it out.
My last laptop had an external monitor connected, and the Intel drivers would often be confused about the orientation of the secondary after a reconnect or a reboot. I got tired of dealing with that and tried to fix it programatically because the clicks were too many in the GUI. Select this monitor, select rotation, select other monitor, select rotation, apply, arrange, apply, wait...
I spent about a day on it (ahh, the days of being an employee vs. self-employed!) and the solution I found was to use a program to compare the registry (regshot perhaps?) to discover what keys were involved in the correction (what they were before versus what they were after) and then there was an intel-provided exe that forced the driver to reset based on the registry-- the exe was essentially like pressing the "apply" button in the gui. I was running XP and if I recall, the gui management was for configuration of the Intel Graphics Media Accelerator Driver for Windows XP as well. So the final solution became a cmd file on my desktop that would apply a REG without confirmation and then run an exe with some parameters.
Now, I don't have that laptop (they didn't let me walk out the door with it when I quit!) and I do not remember the specifics on the exe that was required to do the reset. Just changing registry keys didn't spontaneously cause it to take effect-- there was an api call involved, which I just handled with their exe. I know that isn't a lot to go on, but something tells me the file was in the driver package, or somewhere on the drive already, and I just found it. Running it at the command line gave options. Like /reset.
I hope that helps you a little. Be sure to post back if you figure it out.
Also post back if I'm completely mistaken and it didn't happen like this at all. But that's the way I remember it. :)