Can someone explain why typing st.op into Messenging and Andchat locks up the phone? Both times it was on a line by its self, so idk if that's a requirement. I don't want to test while writing a thread though.
Sent from my T-Mobile G2 using XDA App
Doesn't lock mine up...
Sent from my T-Mobile G2 using XDA App
I just tried it and I didn't freeze.
It looks like typing stop anywhere hard locks up the phone. Even to the point of system sound effects and ui animations stopping half way. I'm not making this up lol.
Sent from my T-Mobile G2 using XDA App
It's almost acting like the old G1 with its root terminal capturing all keystrokes thing. Clearly this is different, but, ...
Sent from my T-Mobile G2 using XDA App
Ok I've had this same thing happen to me it sounds like a door hinge or something? I can't remember if it happened while typing stop (didn't happen now lol) but i have had this happen to me about 4-5 times
adrake400 said:
Ok I've had this same thing happen to me it sounds like a door hinge or something? I can't remember if it happened while typing stop (didn't happen now lol) but i have had this happen to me about 4-5 times
Click to expand...
Click to collapse
door hinge? Nothing is moving though.
Sent from my T-Mobile G2 using XDA App
The internal "stop" command unloads the java and GUI components and will leave you screen frozen if typed in a terminal with root access.
Very amusing, if that's what happens.
"start" would theoretically restart the GUI.
stop + enter in messaging app kills my phone too....wow thats not a great "feature".
just closed the keyboard and the phone rebooted (i typed start but it didnt do anything)
and i just did it again and it did the same thing
it only seems to do this with the physical keyboard tho it didnt do anything when using the HTC_IME
jmiller0526 said:
stop + enter in messaging app kills my phone too....wow thats not a great "feature".
just closed the keyboard and the phone rebooted (i typed start but it didnt do anything)
and i just did it again and it did the same thing
it only seems to do this with the physical keyboard tho it didnt do anything when using the HTC_IME
Click to expand...
Click to collapse
Yep, I used the physical keyboard and had the HTC IME enabled, it didn't work but I switched over to the default android keyboard and typed stop into the messaging app and it froze. Hahaha Great find!
Maybe we can use this as a exploit?
How? How is [a different implementation of?] this bug still here after 2 years?
Hah it worked for me too
Sent from my T-Mobile G2 using XDA App
Code:
I/ServiceManager( 1355): service 'isms' died
I/ServiceManager( 1355): service 'simphonebook' died
I/ServiceManager( 1355): service 'iphonesubinfo' died
I/ServiceManager( 1355): service 'phone' died
E/installd( 1363): eof
E/installd( 1363): failed to read size
I/installd( 1363): closing connection
I/ServiceManager( 1355): service 'wifi' died
I/ServiceManager( 1355): service 'connectivity' died
I/ServiceManager( 1355): service 'throttle' died
I/ServiceManager( 1355): service 'accessibility' died
I/ServiceManager( 1355): service 'mount' died
I/ServiceManager( 1355): service 'notification' died
I/ServiceManager( 1355): service 'devicestoragemonitor' died
I/ServiceManager( 1355): service 'location' died
I/ServiceManager( 1355): service 'search' died
I/ServiceManager( 1355): service 'dropbox' died
I/ServiceManager( 1355): service 'SurfaceFlinger' died
I/ServiceManager( 1355): service 'usagestats' died
I/ServiceManager( 1355): service 'telephony.registry' died
I/ServiceManager( 1355): service 'batteryinfo' died
I/ServiceManager( 1355): service 'entropy' died
I/ServiceManager( 1355): service 'power' died
I/ServiceManager( 1355): service 'backup' died
I/ServiceManager( 1355): service 'activity' died
I/ServiceManager( 1355): service 'meminfo' died
I/ServiceManager( 1355): service 'cpuinfo' died
I/ServiceManager( 1355): service 'permission' died
I/ServiceManager( 1355): service 'content' died
I/ServiceManager( 1355): service 'package' died
I/ServiceManager( 1355): service 'uimode' died
I/ServiceManager( 1355): service 'alarm' died
I/ServiceManager( 1355): service 'sensor' died
I/ServiceManager( 1355): service 'battery' died
I/ServiceManager( 1355): service 'hardware' died
I/ServiceManager( 1355): service 'vibrator' died
I/ServiceManager( 1355): service 'wallpaper' died
I/ServiceManager( 1355): service 'htc_checkin' died
I/ServiceManager( 1355): service 'bluetooth_a2dp' died
I/ServiceManager( 1355): service 'device_policy' died
I/ServiceManager( 1355): service 'window' died
I/ServiceManager( 1355): service 'bluetooth' died
I/ServiceManager( 1355): service 'audio' died
I/ServiceManager( 1355): service 'account' died
I/ServiceManager( 1355): service 'appwidget' died
I/ServiceManager( 1355): service 'statusbar' died
I/ServiceManager( 1355): service 'clipboard' died
I/ServiceManager( 1355): service 'diskstats' died
I/ServiceManager( 1355): service 'network_management' died
I/ServiceManager( 1355): service 'netstat' died
I/ServiceManager( 1355): service 'input_method' died
D/AK8975 ( 1365): Compass CLOSE
That's a logcat of what happens when you type stop in messaging.
also works for me when i type 'stop' and hit enter. have to turn off the swype keyboard first as well.
ctrl + alt + delete do the same.
I have a completely crazy thought. So pls don't flame/ lynch
What if the phone is already rooted? Someone in the thread said that once ur rooted, going into the terminal as su and typing stop kills all the internal processess and freezes the phone
Has anyoen tried to load a custom rom onto the g2? Not the desire z rom, not some t-mo one. A custom one...
I mean we have all been tunnel visioned on assuming that all the subsidized phones come unrooted but what if the nand lockdown requires the phone to be rooted at all times??
Maybe a fresh/ crazy out of the box approach can help...
Sent from my T-Mobile G2 using XDA App
adp21 said:
I have a completely crazy thought. So pls don't flame/ lynch
What if the phone is already rooted? Someone in the thread said that once ur rooted, going into the terminal as su and typing stop kills all the internal processess and freezes the phone
Has anyoen tried to load a custom rom onto the g2? Not the desire z rom, not some t-mo one. A custom one...
I mean we have all been tunnel visioned on assuming that all the subsidized phones come unrooted but what if the nand lockdown requires the phone to be rooted at all times??
Maybe a fresh/ crazy out of the box approach can help...
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Good theory, but unfortunately it doesn't really help us get custom ROMs at all.
We already have root. Getting root isn't a problem (see: VISIONary). The problem, afaik, is that nobody has found a way to get past the NAND lock, which prevents flashing anything without a heavily-encrypted key to sign the ROM with.
Wow, it's for real. And it's not just in messaging. I just confirmed that it works from the home screen(so search automatically opens up) AND from the market. It looks like it's from anywhere. Type "stop" and press enter, and phone freezes. Phone stays frozen until you pull battery OR until you type "start" and press enter(wait 2 seconds and phone reboots). This is crazy, man. Some way this can be used? Maybe we should try some other useful linux commands??
EDIT: Okay, well not from anywhere per se, but anywhere where keyboard input is being accepted. If this stops everything EXCEPT the kernel, is there a way this can be used to assist with perm root? Forgive me if I'm talking out my ass.
DOUBLE EDIT: Just so you guys know, I haven't modified the phone in any way, either. Completely stock.
no freeze here.
rhcp0112345 said:
no freeze here.
Click to expand...
Click to collapse
Did you press enter after you typed "stop"? Did you type anything else before "stop?" Did you use the hardware keyboard?
Related
My Xperia X10I has developed a hardware fault i belive , it started to rarely ,but suddenly shut down and reeboot and about 6-7 weeks or so and now it accours very often. When it reeboots it sometimes starts on a reboot loop sort of that can last for 30min and i have to take out the battery and turn it on again myself to have it reboot problerly , someties nothing helps . It seems that the shut downs accour when i f.ex browse the web or play a game that uses much of the devices cpu and ram . The issue has not been solved by the 2.1 update or beeing serviced at sony ericsson . the service log stated that they had just reset the phone and re-installed 2.1 and tested it ok.
has anyone had similar problems? this issue is frustrating
I too had the exact same problem with my X10. I took it to the SE service center, they told me it was the faulty motherboard that is causing the problem.
They replaced the motherboard and now my X10 is all working well.
I am sure its the hardware fault, take it again to the service center for repair.
Thank you very much i will tell the people at the service centre to put it under more load when they test it this time
So here's the story, bought my Galaxy 10.1 7 days ago, It was working perfectly, I turned it off, and plugged for a nice charge... a couple of hours later..
I tried to turn it on.. and nothing..
So far I have tried:
Holding the power button for several minutes with the tab plugged did not woked.
Holding the power button for several minutes with the tab un-plugged did not woked.
Holded PWR+Volume Down
I connected the tab to my pc and the USB detects that there's something there but nothing else..
is there anyway to use adb or fastboot to kick the thing out?
Please help
Sorry if double posted but I'm going nuts with this problem
Pwr button alone for 15 sec kicked my tab over every time I've locked it, and I'm screwin with pershoots kernel and overclock
lbrenes said:
So here's the story, bought my Galaxy 10.1 7 days ago, It was working perfectly, I turned it off, and plugged for a nice charge... a couple of hours later..
I tried to turn it on.. and nothing..
So far I have tried:
Holding the power button for several minutes with the tab plugged did not woked.
Holding the power button for several minutes with the tab un-plugged did not woked.
Holded PWR+Volume Down
I connected the tab to my pc and the USB detects that there's something there but nothing else..
is there anyway to use adb or fastboot to kick the thing out?
Please help
Sorry if double posted but I'm going nuts with this problem
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA Premium App
Have same problem, exactly as yours dont know what to do. Should send it to support but i live abroad so im fuc...
condorazul said:
Have same problem, exactly as yours dont know what to do. Should send it to support but i live abroad so im fuc...
Click to expand...
Click to collapse
I have exactly the same problem I live in Costa Rica and now I need to send it to USA, and it is going to be very expensive...
Mine is not coming up with any button combination at all...
can't you simply let it deplete his charge using headphones or so?
dcc22 said:
can't you simply let it deplete his charge using headphones or so?
Click to expand...
Click to collapse
Don't know what do you mean by this... the tablet is not even turning on... how am I going to discharge it?
I Will try to reflash it if finally dont manage to send it to USA. I've been reading some post and the drivers it need are available to download, but the firmware has not been released yet, none the less I will charge all the tab to my home insurance cos it seems to be an electric failure.
If someone gets the solution please help us
condorazul said:
I Will try to reflash it if finally dont manage to send it to USA. I've been reading some post and the drivers it need are available to download, but the firmware has not been released yet, none the less I will charge all the tab to my home insurance cos it seems to be an electric failure.
If someone gets the solution please help us
Click to expand...
Click to collapse
Can you share those posts? how can it be flashed in this state?
I've read some Post about passing the information through cmd in windows but I would have to read it again, think it was in nvidia developers or something similar, I guess that if the Pc recognizes the apx something can be done but I'm not an expert and this is my first and Perhaps last android tablet. I'll take a look and told you if I find something
I have the same problem. Bought the tab on Friday in the US and then returned home to the UK. It died last night - 2 days later.
Samsung technical support said it would need to be returned to a service centre. UK service centers can't deal with it as the tab isn't out here yet.
I have called Samsung US this evening and spoke to a very helpful guy who said I can send it back to the us to be fixed under warranty, but will have to pay to ship it there and for them to ship it back to me.
Unfortunately samsung's systems can't cope with my uk address so I will have to speak to the warranty company company direct - who are closed today as it's 4th July.
As a final point - I also spoke to best buy - to see if I could return it to them. As I bought it in store, I have to return it to store. Bunch of ............
Sent from my GT-I9000 using XDA App
tmbk said:
I have the same problem. Bought the tab on Friday in the US and then returned home to the UK. It died last night - 2 days later.
Samsung technical support said it would need to be returned to a service centre. UK service centers can't deal with it as the tab isn't out here yet.
I have called Samsung US this evening and spoke to a very helpful guy who said I can send it back to the us to be fixed under warranty, but will have to pay to ship it there and for them to ship it back to me.
Unfortunately samsung's systems can't cope with my uk address so I will have to speak to the warranty company company direct - who are closed today as it's 4th July.
As a final point - I also spoke to best buy - to see if I could return it to them. As I bought it in store, I have to return it to store. Bunch of ............
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yeap same here, I will be sending mine on wednesday if I cannot find a resolution on my own, I spoke to best buy as well and we have 14 days to get an exchange for a new one..
Just one question to all is anybody using the Invisi shield on your tab?
Here us the place where I read it it's inthat forum
http://forum.xda-developers.com/showthread.php?t=1130574
Think they are speaking about our problem
So if you send it to best buy they change it, but my problem is that my fifteen day will expire on the deliver, tomorrow I will try the solution posted before and see if it works, nothing to loose
condorazul said:
So if you send it to best buy they change it, but my problem is that my fifteen day will expire on the deliver, tomorrow I will try the solution posted before and see if it works, nothing to loose
Click to expand...
Click to collapse
Official policy is that if it was bought in store it has to be returned to store you got it from. The lady on customer services said some managers will accept returns by post but at their discretion. I got one that chose not to!
Sent from my GT-I9000 using XDA App
power button for about 10 seconds reboots for me (stock everything)
joebob1 said:
power button for about 10 seconds reboots for me (stock everything)
Click to expand...
Click to collapse
Lucky you... I was able to access my tab with nvflash and I think the problem is that my bootloader is broken
C:\nvflash>nvflash --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c704641bff4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
So if someone knows how to fix that It might bring the tab back up
same problem in mine lets wait for some illuminate to fix it
lbrenes said:
Lucky you... I was able to access my tab with nvflash and I think the problem is that my bootloader is broken
C:\nvflash>nvflash --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c704641bff4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
So if someone knows how to fix that It might bring the tab back up
Click to expand...
Click to collapse
can you get into odin or no?
I have also been able to access via nvflash. Tried Odin 1.3, 1.7 and 1.8 (might have been 1.83) and none detect it.
Sent from my GT-I9000 using XDA App
ericc191 said:
can you get into odin or no?
Click to expand...
Click to collapse
In this state it is impossible to get in to DOWNLOAD mode,and for what I have read the Tab is only flashable with a special service cable so I guess unless we get a very skilled Dev to find a workaround our only option is to return them
Hi I rooted my DZ about a week ago and installed CyanogenMod 7.0.3. It has worked perfect and I've been very pleased with it.
Last night I set the alarmclock for the morning, set the phone to charge and went to bed.
I then woke up 3 hrs late and discovered that my phone was turned off ?! I can't turn it on and nothing happens when I set it to charge.
My hopes are that its just the battery that's collapsed but what do you guys say ?
hoping the best for you but here's what happened to me:
Out of the blue my Desire Z stopped working: one moment everything is fine and then all of a sudden when i tried to turn the screen on nothing happened. well i didn't expect anything worse than having to take out the battery and reboot, but when i did just that only the home, menu, back and search button went on but not the screen...end of the story, i had to send it to the customer service wait for about 3 weeks (customer service in germany is rather poor because it is outsourced to another company) and get a mainboard replacement.
Maybe in your case it's just a dead battery, take it to the next electronics store and have them check if another battery fixes your problem...Good Luck!
Silly question but you have done a battery pull?
s0undless said:
hoping the best for you but here's what happened to me:
Out of the blue my Desire Z stopped working: one moment everything is fine and then all of a sudden when i tried to turn the screen on nothing happened. well i didn't expect anything worse than having to take out the battery and reboot, but when i did just that only the home, menu, back and search button went on but not the screen...end of the story, i had to send it to the customer service wait for about 3 weeks (customer service in germany is rather poor because it is outsourced to another company) and get a mainboard replacement.
Maybe in your case it's just a dead battery, take it to the next electronics store and have them check if another battery fixes your problem...Good Luck!
Click to expand...
Click to collapse
I'll go to my nearest 3 store next week to see if a battery swap will do it. I'm just afraid that it's the whole rooting thing that has caused it and that the warranty wont cover it :/
bombadier said:
Silly question but you have done a battery pull?
Click to expand...
Click to collapse
Yeah, several times
Been 3 weeks didnt get a call for the service center all they say the part is nt avaible. But 2day I try to check the workorder number online an it say YOUR UNIT IS UNDER REPAIR. does this mean the got the part an are currently repairng? N how long do they take after get the part to return the fone?:crying:
Be patient
Is it important how did i send this?
I did not learn my lesson! It took ZTE more than 30 days to repair my first Axon 7 (hard bricked, would not power up). Instead of giving up, I bought a second one only to find out that the Camera and Flashlight App (not the camera flashlight) does not work (error message "can't connect to camera, etc...."). I contacted ZTE customer service and after resetting phone to factory, deleting data/cache, etc. did not work, agent created an RMA, I shipped the phone to ZTE on 8/21, they received it on 8/24. Whenever I try to check the status of the repair online, I receive "invalid log in, contact administrator". I reported it, still not resolved.
I contacted customer service on Friday the 8/25 to make sure they received the phone, they confirmed receipt. I contacted them again on Thursday the 8/31 to check status, I was told that phone is in "Assess" stage and it will ship in 3.5 days. I contacted them again 2 days ago, 9/4 to see if it has shipped, the agent responded that the info given to me before was NOT correct, the phone is only in "Received" status and has not even been assessed! So to be blunt, the agents I communicated with before were making things up, basically lying! She promised to follow up and escalate the issue to find out why the delay. She also promised that some one will contact me by phone or email within the next 2 to 3 days. The moral of the story, don't believe everything that customer service agents tell you! In the past, their excuse was "no parts, no replacement phones", I wonder what their excuse is this time.
TheBoozer said:
I did not learn my lesson! It took ZTE more than 30 days to repair my first Axon 7 (hard bricked, would not power up). Instead of giving up, I bought a second one only to find out that the Camera and Flashlight App (not the camera flashlight) does not work (error message "can't connect to camera, etc...."). I contacted ZTE customer service and after resetting phone to factory, deleting data/cache, etc. did not work, agent created an RMA, I shipped the phone to ZTE on 8/21, they received it on 8/24. Whenever I try to check the status of the repair online, I receive "invalid log in, contact administrator". I reported it, still not resolved.
I contacted customer service on Friday the 8/25 to make sure they received the phone, they confirmed receipt. I contacted them again on Thursday the 8/31 to check status, I was told that phone is in "Assess" stage and it will ship in 3.5 days. I contacted them again 2 days ago, 9/4 to see if it has shipped, the agent responded that the info given to me before was NOT correct, the phone is only in "Received" status and has not even been assessed! So to be blunt, the agents I communicated with before were making things up, basically lying! She promised to follow up and escalate the issue to find out why the delay. She also promised that some one will contact me by phone or email within the next 2 to 3 days. The moral of the story, don't believe everything that customer service agents tell you! In the past, their excuse was "no parts, no replacement phones", I wonder what their excuse is this time.
Click to expand...
Click to collapse
This is the usual rant. Pretty much customer support office out there is actual crap. They said OnePlus's was hideous, I had lots of trouble with Google's Motorola, heard some stuff about Samsung too...
I don't have customer support here, (bought it in Thailand, live in Argentina ) but I'm grateful that I didn't have any hardware trouble. I DFU-bricked it but managed to get it back to life via disassembly and all.
Hope for the best... But we all know how bad customer support is. There are a bunch of threads that say basically the same.
Sorry to hear you got screwed. Maybe I've been lucky, but ZTE Axon customer service has been good. I've RMA'd 2 phones for the camera OIS problem and both time have been efficient. I did the advanced exchange on both and they went okay. The second phone they advance exchanged it without putting any hold on my card.
pt
Yes I had no issues with them either. Hell both of the times I called them the operator seemed to actually be located in the USA
I am still waiting for the promised email/phone call. If I don't get anything by the end of the day, I will contact them again. I am happy that someone had a good experience with them, as for me, this is my second nightmare!