Related
Today I got my Kaiser back from repairs. I got my mainboard replaced because of connection issues. It came back with it's original 'software'.
After installing Hard-Spl (white screen edit) I successfully flashed "Dutty's Official WM6.1 5.2.19209 Release" to my Kaiser.
I wanted to Hard Reset my device using the soft-buttons and soft-reset method, but it seems to be broken (?). I managed it in the past (before flashing and repairs) but for some reason it doesn't work anymore. Soft-resets and Bootloader mode still work.
Anyone got an idea?
Thanks in advance
P.S.: In the meantime I hard-resetted my device by going to Settings => System => Clear Storage
Dr. Strangelove said:
Today I got my Kaiser back from repairs. I got my mainboard replaced because of connection issues. It came back with it's original 'software'.
After installing Hard-Spl (white screen edit) I successfully flashed "Dutty's Official WM6.1 5.2.19209 Release" to my Kaiser.
I wanted to Hard Reset my device using the soft-buttons and soft-reset method, but it seems to be broken (?). I managed it in the past (before flashing and repairs) but for some reason it doesn't work anymore. Soft-resets and Bootloader mode still work.
Anyone got an idea?
Thanks in advance
P.S.: In the meantime I hard-resetted my device by going to Settings => System => Clear Storage
Click to expand...
Click to collapse
Few Tricks, Make sure you are not plugged in USB. Make sure you are not "fat fingering it." Some people use chopsticks to be sure. And Hold it for long after the Screen goes Black.
Believe me, I've already tried the things you said.
Although I successfully mananged in the past to hard reset my phone, I checked the threads and the following vid:
How To Hard Reset Kaiser:
http://www.youtube.com/watch?v=fZPzT_L2FZQ
Usually I am the problem, but this time I can't figure out what I'm doing wrong.
Just wondering:
Which part of the Phone (ROM) is in control of the Hard Reset part? (e.g.: Bootloader, Radio Rom, Regular Rom,...)
Use "Clear Storage". It does the same thing.
Also, JM is most likely correct. It is most likely an issue of how you are pushing the buttons. Make sure you hold only ythe soft keys first, using your fingernails, then push the reset tab on the bottom & hold it. Don't just push the reset & release, but keep it held down.
Based on your previous message about your phone being haunted - mine is too btw, I think it's because the soft buttons aren't being acknowledged by the OS - which implies some REAL big problems.
I took mine back to the T-Mobile store today where I got told that it needs to be sent back to their workshops to fix it... and then got told that "mostly they just send out a new phone".
My phone is exhibiting the following symptoms.
1) Green and Red phone buttons do not work.
2) Soft buttons do not work.
3) D-Pad and wheel work intermittently.
4) (and most strange) the back-space key on the slide out keyboard does nothing, and on the virtual keyboard it flashes (to suggest that the key is being pressed) but still does nothing.
I've tried to access the bootloader, and perform a hard reset. I'm now looking for the original T-Mobile ROM to install (which was why I went into the shop), as the issue around the backspace key implies to me that the issue is in the OS not in the hardware.
Jon
Thanks already for all the input.
I've been trying all weekend in every different possible way to perform a hard reset. Fat fingering is really no possibility anymore. I've used every possible tool I had (needle-nose pliers, chopsticks, pens,...) to eliminate fat fingering.
But nothing helped. Jon (a nice guy) might have given a possibly correct diagnosis for my problem. But it wouldn't explain why I still can get into the bootloader.
Problems since receiving my phone from repairs:
Backlight changed out of itself => performed Hard Reset
Phone pad pops up and seems to start dialing => flashed new ROM
Wakes up constantly after a few seconds from standby => performed Hard Throw against the wall
As you can see, my latest problem is that the phone automatically wakes up from standby after a few seconds. The weird thing: it only does this when I put it in standby, but it doesn't wake up if it enters standby by itself.
=> NOTE: This may support the 'fat finger'-theory: the Kaiser gets some sort of keyboard input due to faulty hardware. Therefore I cannot Hard Reset my device, because of the additional faulty input.
I've used the "Clear Storage" method to perform one of my hard resets, but this has to be solved. I will be sending the phone back for yet another repair.
Thanks again for your input everyone.
Problem found?
I think I found the problem:
I just noticed that the camera button is already pushed in halfway (like when you focus the camera before you take a picture). If I push the button gently, it immediately takes a picture without focussing (it does automatically focus before taking the shot, but not on my command).
Also, when I enter the camera app, it sometimes instantly focuses. Other times I cannot focus at all.
Hard reset is still no go.
Yet another thanks for your useful help.
Maybe found the solution?
Hi Guys...
I found that by tapping the base of the phone, it "unlocks" itself, thereby making it work. It's become *S*L*O*W* as hell, and I'm really tempted to ask them to take a look at it, but right now I need all the functions, so I'm holding off.
But, give that a try and see what happens!
Jon
Thanks for still answering my question. Go community!
Dr. Strangelove said:
...
I will be sending the phone back for yet another repair.
...
Click to expand...
Click to collapse
Last week I finally received a fully functional and working Kaiser (have been waiting for that since december...). I couldn't accept a disfunctional Kaiser coming back from repairs.
The problem did indeed seem to be the camare button that was stuck. I tried really hard to get it to unblock, but I didn't work. I must say, I didn't try your method (didn't think of it).
Still thanks a lot.
I am experiencing exact same issues on my Kaiser (Tilt), it randomly starts to type stuff in the phone application on its own and I can't do anything to stop it, I have replaced ROMs, SPLs, Radios, now using a shipped rom with shipped radio but still that problem comes up after a few days of usage and doesn't go away until I hard reset, anyone knows what I can do to fix it? it's probably out of warranty. I checked the camera button and it seems fine.
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Do a hard reset / wipe. That's my suggestion.
Try booting into recovery (Home Button, Vol Up + Power), and resetting your cache and wiping it. Then try logging in with your Google account. If all else fails, try changing your Google password on the PC then logging in on the phone. And then if it still fails, looks like you need to flash the phone again. Next time, don't enter the thing wrong! Stop rushing haha .
I wasn't rushing, I was playing with the lock. It takes about 30 times before it's permanently requiring the username/password. But really...you can't blame me for not expecting this. :/
I'm currently trying to flash a new ROM but I've run into another problem - I can't get it to boot into downloader/recovery. It's not the lack of the 3 button combo - I've managed to reach Recovery and Downloader ONCE each in the past, but never again since.
And now with all my efforts to boot into recovery/downloader, it now cannot boot into normal usability mode (or in my case, locked mode). Instead, the Galaxy S logo loops endlessly.
Sigh.
Have you read the thread for the fix for Galaxy S variants that are lacking the 3 Button Combos? It's in Android Development. Maybe try that? Or, can you still connect the phone and connect with Kies?
I can't turn on the phone anymore, meaning no changing to USB debugging etc. And I'm having problem accessing recovery/download, even though I definitely HAVE done each of them once before and therefore do not have the 3 button problem.
Without turning on my phone, Kies can't detect it
So what happens when you power on?
Now, it shows the first Galaxy S splash screen, then shows the boot logo, then nothing. The boot logo continues to glow endlessly.
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
okpc said:
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yeah it's continuously shining. Haven't left it for up to five minutes though... And even then it probably won't help since I'm still locked out of the phone, and unable to access download/recovery mode to reflash it.
After waiting for a long time, the logo disappears, screen goes black. Menu and back buttons light up. Nothing else.
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
PaulForde said:
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
Click to expand...
Click to collapse
Good advice considering he said his 3 button combo stopped working =))
All I did when I got that black screen was adb reboot recovery and wiped and phone bootedup fine. But only if you have debuging enable and and sumsung drivers. Hopes this help.
Sent from my SGH-T959 using XDA App
Can't enable USB debugging when phone can't be turned on at all.
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
danamoult said:
Can't enable USB debugging when phone can't be turned on at all.
Click to expand...
Click to collapse
you need to be able to enter recovery mode for you to solve this problem
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
dear friend dont worry or panic... i'll tell you a trick , go to the samsung customer care and tell them that your phone gets heated up very often and today it just refuses to boot up normally...
since your device cannot get into recovery mode or download mode the company will never know that you had played with the system files in the device or not... (rooted )..
since the samsung people will also try to get your device in recovery mode.. but when it will not go to the recovery mode you will get a mother board replacement under warranty.....
this heating up of the device is a common problem in the galaxy here in india.. so use this excuse and i know it works 100% ... (just dont tell them that you had rooted and lagfixed your device )
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
OzzYGuY said:
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
Click to expand...
Click to collapse
distortedloop said:
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
Click to expand...
Click to collapse
chill my dear friend.... it cant be true.... its just his 1st post.. and samsung cannot be so dumb to leave a password protected keypad that can be cracked so easily.. even i tried the back key on a call with a password lock.. i cannot get passed the lock screen....
This is my second SGS with this problem and I am trying to determine if it is common or if I am just monumentally unlucky.
During normal use the bottom soft keys (menu and back) will become non-functional. One will stay lit and one will go out, but both will cease to work. Everything else on the phone is still responsive, sometimes the keys 'revive' themselves after a short period of time, other times I need to lock the phone to get them back.
I got this phone (a replacement) on the 6th, and this started on the 12th and has been happening more and more often ever since. Has anyone else seen this or have an idea what it may be? Or is this phone is destined to be my 2nd DOA in a month?
Here is a video showing the problem: '
you tube.com/watch?v=1s-wqWsHaIs
That is definitely not normal behaviour.
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
hol17 said:
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
Click to expand...
Click to collapse
FYI: Samsung support told me to return my phone.
It is almost like one of the soft keys gets stuck 'down', because it is the same behavior if you just hold down one of the keys. Mine seems to happen more when bluetooth is on and it comes and goes in spurts; good for an hour, bad for an hour, etc.
ETA: I am sure now that the soft keys are getting 'stuck down'. I have seen it 3 times now where I would press the left soft key and the light on the key will remain out, then after a second or so the quick search screen comes up and the left soft key light is still out.
any solution to this problem? i seem to have a slightly different issue
this just happened to me recently everything was working fine until this morning when i tried to press the menu and back buttons it wouldnt work, although the buttons light up and is registering my actions when i press them the light turns off and let go is lit up again.
could this be a software issue or something conflicting with my lednotification mod?
please reply ^_^
I've got the exact same issue with my soft keys getting stuck too. Just started a couple days ago, phone's less than a month old. I was also told to take my phone in for repairs.
Oh one tech support guy told me that Froyo might fix it... I'm kinda hoping for that, seeing as how this issue isn't exactly 100% reproducible for the warranty service department
I have the same problem its almost like the soft key is being held down, anyone find a fix for this?
Add me to the list
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
robcarey said:
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
Click to expand...
Click to collapse
Lock it back and go again.
I know this post it's a bit old, but i was harvesting the web looking for an answer to my problem that seems to be the same posted here.
I have a i9000T with eclair 2.1 and soft keys get stuck now and then. I couldn't find a way to reproduce this behaviour.
Recently (yesterday) i flashed a new 2.3.3 firmware hoping this curse to end. The problem seems to persist, but in some situations that i asume for a bad flashing (i didn't repartition neither wipe the phone before flash).
Anyway, can anybody tellme if this is a software or hardware issue? I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
cknu said:
I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
Click to expand...
Click to collapse
Only one way to find out mate.
You need to flash a 2.1 rom that consists of 3 files. 512 pit and re-partition.
Should get you back on track again.
I did flash it again with the 2.3.3 JVH, a few moments ago. Also did a repartition and wipe data and cache. It seems nice, but in a few minutes the same happend. Now, when i press the menu button it takes a nice screenshot of the phone. xD
I need to flash to a 2.1 version? Why is this? I thought flashing with any rom will work.
Thanks.
Solution to this problem!
Hey all - I found a solution to this problem - I can confirm this has fixed the problem on TWO phones for me - read the whole thread as this fix doesn't like custom firmwares, but works fine with all the regular FWs I've downloaded.
Works perfect - and simple fix!
http://forum.xda-developers.com/showthread.php?t=869492
^^^
Do not do this unless you have a i9000m. You will break your buttons.
electrotune1200 said:
^^^
Do not do this unless you have a i9000m. You will break your buttons.
Click to expand...
Click to collapse
Too bad i didn't see this before
I have I9000T used this 2663 method and now my soft buttons doesn't work anymore...
Didn't find a clear solution in the forums so i want to ask, like i said my phone is a I9000T with official 2.2.1 (UBPJA) rooted using SuperOneClick and unlocked editing the nv_data.bin file.
I was thinking on doing a hard reset to get back to the factory defaults but i see many ways of doing it that it gets confusing... i see peolple doing it through the privacy menu but i think that only erase data and doesn't restore anything OS wise, also see other people doing it using volume + home + power and selecting later clear storage, i think this is the same that the option in the privacy menu, and finally i see some people typing this code *2767*3855# what is the proper way to get back to the original OS in my case?
Thanks in advance...
Yes you read it right I want to know how I can brick my phone or make it stop working completely. Now let me explain the reason why. I had installed an app called "Launcher Pro". Later I uninstalled it and that is when all hell broke lose. Basically when ever I would swipe my screen to unlock the phone, I would get constant error messages that would reappear the moment I would close them, and to make matters worse it would lock out the rest of the screen so I can not click any thing else (just like in windows vista and windows 7 when a UAC message pops up). This is further complicated by the fact that I have a Bell Canada Samsung Galaxy Phone, which does not have the 3 button recovery ability but that is not the end of my problems. I got this phone at a store called Best Buy and got their warranty. Now one of the things that voids the warranty is unlocking the phone, guess what?? My phone is unlocked. So since my phone is not dead, it boots up, the lock screen loads up, the top bar shows u the battery life and the fact it is getting service and can receive calls (but which I can not answer since when it comes to that screen, the screen freezes up with the error messages). So if I take the phone to Best Buy, they are going to pop in a different sim other then bell and when they see that it works, will hand me back my phone and void my warranty. So I need to have the phone in such a condition that they can not check that and yes there can be no physical or water damage either. How do I accomplish this?
Is it rooted ? Did u happen to enable usb debugging ?
If so a mere "adb reboot recovery" followed by a wipe data would solve ur issues
Ya it is rooted, but usb debugging is not activated and I can not activate it the normal way through the settings screen, if you would know a way to do it some other way, that would be great. Just to let every one reading this know, I do not want to change my phone if I can help it, if there is a way for me to fix this with out bricking the phone and getting a new one, I will be more then happy to keep my current phone. Thanks
Zink6 said:
Ya it is rooted, but usb debugging is not activated and I can not activate it the normal way through the settings screen, if you would know a way to do it some other way, that would be great. Just to let every one reading this know, I do not want to change my phone if I can help it, if there is a way for me to fix this with out bricking the phone and getting a new one, I will be more then happy to keep my current phone. Thanks
Click to expand...
Click to collapse
Have you tried booting into safe mode. Usually booting into safe mode will disable any 3rd party apps from loading. This might give you the chance to uninstall LauncherPro or even enable USB debugging. The method to get into safe mode for the Bell Vibrant seems tricky though:
Menu + Home + Power On right when you see the Samsung logo (specifically: http://forum.xda-developers.com/showpost.php?p=8583886&postcount=17) probably hold the keys. I know in the other Android phones (HTC Ion) you have to hold Menu from beginning til it boots.
http://forum.xda-developers.com/showthread.php?t=758678
Seems to work sometimes...
Why dont you just re-lock your phone?
Sent from my GT-I9000M using XDA App
Why unlocking it with code would void the warranty? if you flash, yes, maybe. but you enter the unlock code... isn't the official way? Don't bother how i got the code, I bought it, it's mine, i can unlock it. period. i dont understand how they would consider to void the warranty because you unlock with code. btw, Bell does give unlock code for 75$. so, my phone is not eligible for warranty?
MadWhips said:
Why dont you just re-lock your phone?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Guys c'mon.. At least read his post. He can't gain access to the phone at all right now. How do you expect him to relock?
Honestly with no adb you can't do much if u dont have 3button working
Try all those 3button tricks posted for those who can't get to recovery/download mode.
One if i recall is :
Turn off phone
Press n hold Home + Vol Down (or Vol up, up 2 u) + power
Keep holding, your phone will restart once, then twice, then let go off power button.
Its worth a shot
I work at best buy. They will not stick another sim card into the phone. Is it within the 30 day return policy? If its within 30 days go return it and show them the phone dont work and they will exchange it for you.. If its not within the 30 days they will most likely have to send the phone out to Samsung.
What i would do :
1. Take the phone back to the store.
2. Tell them the thing dont work...they wont know if its unlocked or rooted.
3. Ask them to exchange it under the manufactures warranty (if its not within the 30 days) and hopefully they will exchange it and not have to send it out to samsung.
WIN.
PM me if anything.
Asked the rep at best buy (by the way this is best buy Canada), and he said warranty is void if unlocked.
like eduard said, just take it do them. don't even ask or mention unlocking coz that will make them think that you have unlocked it.
take it there, say it doesn't work. done. don't ask, don't tell.
lol thats why you dont tell him you unlocked it! wow man.
its not about you telling them that u unlocked it, their procedure is to insert a different sim into the phone before sending it out for repair and/or exchange. And that is when I will be caught. So aside from giving best buy the phone, does any one else have any other ideas?
Did you try this?
http://forum.xda-developers.com/showthread.php?t=813580
I also have a Bell SGS. I got it from Wireless Wave and fortunately I have 3b recovery. You've tried both (up+home+power) as well as (down+home+power) right? You let go as soon as you see the boot screen that says i9000.
Drop it in the water?
zorxd said:
Drop it in the water?
Click to expand...
Click to collapse
Water damage is not covered by warranty.
From what i read, i can't imagine this is a hardware problem (though i could be wrong), so probably the worst that can be is that your phone needs a reflash. How much would that cost in CA if you can't talk it into a warrantee case?
Ya its not a hardware issue, its a software one. Let me give u more information. The phone boots and goes to the lock screen. Shows the correct time and date and shows on the top that it was connected to my phone service but the moment I swipe the screen to unlock, I get repeating messages, one of them reads "The process android.process.acore has stopped unexpectedly. please try again." and the other reads "The application TwLauncher (process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again". Both messages have a "force close" button on the bottom that takes the message away just for it to reappear a second later.
Also from what I have been reading in the forums, if I can only get my phone into usb debugging mode in any other way then the typical MENU > Settings > Applications > Development > USB debugging, it would solve all my problems. If any one knows how to do that, please share your knowledge.
There is a post on here for making a USB dongle that powers the phone straight into download mode.
You need a USB plug and a resistor.
You can then re flash.
Sent from my GT-I9000 using Tapatalk
Here's what you can do:
When you've started the phone (and the error messages come up) you connect your device to your PC with the USB cable.
At that point you'll see a new menu on the background (behind the error messages) for the selection of your connection (Samsung Kies, Mass Storage, etc...)
Click away the error messages very quickly and press the button Samsung Kies (you may have to try several times before you can do this but it's possible)
Then you open Samsung Kies and you use the procedure that is mentioned in the post below to reflash your device with a test firmware:
http://forum.xda-developers.com/showthread.php?t=766589
Make sure to read through that tread to know what codes you have to use in the registry. You should be able to flash your device in Kies with a (test/official) firmware this way.
In the end you my not even have to return it at all...
I would like to write simple security app for my phone, that wouldn't allow manipulating with mobile after it is ordered to enter disabled mode. I thought about it, and there are 2 things needed to be done. First I'll have to disable screen - not a hard task, but secondly, I need to ensure anyone won't be able to hard reset phone until mobile have disabled state. Normal reset won't be a problem, I plan to start that security app right after the phone powers up and load windows.
If the phone won't respond to commands and to perform hard reset(which would allow bypassing app by wiping it), phone is useless to anybody.
So if I want that to work, I need to disable hard-reset option by any means, but not disable whole phone.It got to be able to power up so app can again run and undo all changes. Is there any way to do that and don't break anything?
I've seen similiar app to what I want build, but it disabled phone totaly, so even after recovering it, it was unusable. That is where I want to improve, so I'd be glad if someone could help me.
i know nothing about mobile programing, but got some though regard what you want to achieve, you may need a customized password protected bootloader.
Dark_Raven said:
I would like to write simple security app for my phone, that wouldn't allow manipulating with mobile after it is ordered to enter disabled mode. I thought about it, and there are 2 things needed to be done. First I'll have to disable screen - not a hard task, but secondly, I need to ensure anyone won't be able to hard reset phone until mobile have disabled state. Normal reset won't be a problem, I plan to start that security app right after the phone powers up and load windows.
If the phone won't respond to commands and to perform hard reset(which would allow bypassing app by wiping it), phone is useless to anybody.
So if I want that to work, I need to disable hard-reset option by any means, but not disable whole phone.It got to be able to power up so app can again run and undo all changes. Is there any way to do that and don't break anything?
I've seen similiar app to what I want build, but it disabled phone totaly, so even after recovering it, it was unusable. That is where I want to improve, so I'd be glad if someone could help me.
Click to expand...
Click to collapse
hey, this sounds like a cool task. I can help with the SPL modification.
you would also want to protect it from reflashing with another ROM.
cmonex said:
hey, this sounds like a cool task. I can help with the SPL modification.
I think it might be just enough for now If we could password protect our systems from being wiped/flashed, but as I read, this wasn't possible. I'm not sure if times changed, but with android and win7 becoming popular, I doubt that anyone will take an effort and I don't know enough to make it by myself...
Click to expand...
Click to collapse
Dark_Raven said:
cmonex said:
hey, this sounds like a cool task. I can help with the SPL modification.
I think it might be just enough for now If we could password protect our systems from being wiped/flashed, but as I read, this wasn't possible. I'm not sure if times changed, but with android and win7 becoming popular, I doubt that anyone will take an effort and I don't know enough to make it by myself...
Click to expand...
Click to collapse
this can be done in several different ways by changing SPL...if you're interested PM me and I can sort something for you.
Click to expand...
Click to collapse
This will be cool app .
I think what cmonex said may help by securing SPL itself, to start with.
Thanks.
Disable Hard Reset?
I think someone has already done that - and sent it to me in a virus in an MMS. My phone keeps wanting to "Power Off". If I respond "Yes", it immediately restarts. If I respond "No", it wants to "Power Off" again after a couple of minutes. The phone doesn't respond to the power button. I can't perform a hard reset.
I've been trying to find a copy of the shipped ROM to try reflashing it, but none of the links to the Australian Telstra ROM (2.31.841.6) seem to work. Can't seem to find one ANYWHERE?
This is driving me CRAZY.
Is there any OTHER way of doing a hard reset (eg while connected to PC?)
PS Oddly enough, it seems that while the phone is connected to the usb port of the PC, it DOESN'T try to power off! - Whoops, cancel that... "Power Off" dialog just came up!