s3 mini lafleur firmware..screen rotation not working..help me - Galaxy S III Mini Q&A, Help & Troubleshooting

Dear frndz..
i hve s3 mini lafleur..
screen rotation not working...
i did root n flash other cntry firmwares...but no way..
wot can i do?
now screen rotation working only through "Ultimate Rotation Control app"
is this any hardware pblm? or software?
help me frnds.....
am waiting ur quick response...:crying::crying::crying:

anyone can help me?

bijoyaya said:
anyone can help me?
Click to expand...
Click to collapse
dial *#7353# and make accelerometer sensor test. if it works = no hardware issue
try a full wipe or flash stock rom

i wiped n flash stock rom also...but no way...........type this code...i got one arow....
samersh72 said:
dial *#7353# and make accelerometer sensor test. if it works = no hardware issue
try a full wipe or flash stock rom
Click to expand...
Click to collapse

samersh72 said:
dial *#7353# and make accelerometer sensor test. if it works = no hardware issue
try a full wipe or flash stock rom
Click to expand...
Click to collapse
hi there, I have the same issue with auto-rotation, it does not work anymore (even if auto-rotate toggle is on).
I dialed your code, and as result, I have a black arrow pointing up, with written below 'Accelerometer Senor Test'.. how can I understand if it is actually working? Thanks for your time.
Update: here's how test works, http://dc442.4shared.com/doc/L_8P0YtP/preview.html
For me, the arrow does not move.. so, what should I do?

oldslowdiver said:
hi there, I have the same issue with auto-rotation, it does not work anymore (even if auto-rotate toggle is on).
I dialed your code, and as result, I have a black arrow pointing up, with written below 'Accelerometer Senor Test'.. how can I understand if it is actually working? Thanks for your time.
Update: here's how test works, http://dc442.4shared.com/doc/L_8P0YtP/preview.html
For me, the arrow does not move.. so, what should I do?
Click to expand...
Click to collapse
first try to reset the phone and test.
if not, flash stock firmware and test.
if it doesnt work, it means you have a hardware issue (sensor broken)

samersh72 said:
first try to reset the phone and test.
if not, flash stock firmware and test.
if it doesnt work, it means you have a hardware issue (sensor broken)
Click to expand...
Click to collapse
I see, but, do you know is there any other option than hard resetting? Elixir 2 (https://play.google.com/store/apps/details?id=com.bartat.android.elixir&hl=it) detects my accelerometer (by giving detailed informations), but it is like it is stucked / frozen.
I wonder if there is a way to 'un'freeze it.
TY

oldslowdiver said:
I see, but, do you know is there any other option than hard resetting? Elixir 2 (https://play.google.com/store/apps/details?id=com.bartat.android.elixir&hl=it) detects my accelerometer (by giving detailed informations), but it is like it is stucked / frozen.
I wonder if there is a way to 'un'freeze it.
TY
Click to expand...
Click to collapse
im pretty sure it is a hardware issue... no idea other then trying what i mentioned

samersh72 said:
im pretty sure it is a hardware issue... no idea other then trying what i mentioned
Click to expand...
Click to collapse
Okay, TY, I see if I can find alternatives, I'm going to update this thread soon.
EDIT: finally fixed.
Here's how (for my s3 mini 4.1.2, modded stock TouchWiz):
1) enter Recovery
2) wipe dalvik cache and cache
3) update kernel (in my case, with Virginity's one (http://forum.xda-developers.com/showthread.php?t=2550392): it is a modded version of AMJ3 kernel, for me, it works fine).
G-sensor aka Auto rotate aka Screen rotation now is back working fine.
Previously, I had already wiped cache and dalvik cache, so I can only guess that I needed a cleaner kernel.
PS. For future needs, if you have Fastboot on your device (s3 mini has not got), you can also check this out:
Here is a description of the exact process I used to adjust the sensor:
1. Power down phone.
2. Hold volume down button down while turning power on.
3. Wait for black screen with light blue text with yellow text as highlight with blue background.
4. Screen title: Factory Mode with selections, Full Test, Item Test, Test Report, Clear eMMC, Version and Reboot.
5. Select Item Test using the volume up and down button then push the Home button.
6. There is a very long list of items: selected the G-Sensor Calibration > home button.
7. There are four items: Clear Calibration, Do Calibration(20), Do Calibration(40), and Exit.
8. Select Clear Calibration > Home button.
9. Lay on flat surface and do not touch while calibrating.
10. Select Do Calibration(20) > Home button.
11. Select Exit > Home button
12. No selection on this screen used Back Button.
13. Select Reboot > Home button.
14. This reboots back into regular interface and complete.
Source:
http://bzjoe.blogspot.it/2013/02/calibrate-accelerometer-g-sensor-on.html

Related

CWM doesnt do anything, "back button disabled", help please.

i had a custom froyo 2.2 rom (cant remember the name) and decided today to install gingerbread 2.3.
i went for cyanogen rom, downloaded the most recent one and copied it to the SD card.
then i went to recovery mode (an old CWM version that was installed the time i installed froyo). wipe everything, install zip from SD card and everything went good.
2.3 is installed and working, but cyanogen doesnt include google apps so i had to download an extra .zip that includes google apps (market, maps, etc). so i rebooted into CWM (now a new version that was installed with the rom v4.0.0.5) but now it doesnt work!
any option i choose from the CWM menu just doesnt do anything and goes back to the menu. if i scrool down the last option (to return to the first option) he writes "back menu button disabled" and if i go again it writes "back menu button enabled" but still doesnt do anything.
i search the forum and the web and found nothing, please help me because im getting scared that the phone might be broken..
thanks in advance.
saproandroid said:
i had a custom froyo 2.2 rom (cant remember the name) and decided today to install gingerbread 2.3.
i went for cyanogen rom, downloaded the most recent one and copied it to the SD card.
then i went to recovery mode (an old CWM version that was installed the time i installed froyo). wipe everything, install zip from SD card and everything went good.
2.3 is installed and working, but cyanogen doesnt include google apps so i had to download an extra .zip that includes google apps (market, maps, etc). so i rebooted into CWM (now a new version that was installed with the rom v4.0.0.5) but now it doesnt work!
any option i choose from the CWM menu just doesnt do anything and goes back to the menu. if i scrool down the last option (to return to the first option) he writes "back menu button disabled" and if i go again it writes "back menu button enabled" but still doesnt do anything.
i search the forum and the web and found nothing, please help me because im getting scared that the phone might be broken..
thanks in advance.
Click to expand...
Click to collapse
Move the cursor past the top menu choice 3 times in either direction.
Sent from my abucus
wow it worked, thanks a lot man i was getting really scared
i know it was a newbie thing but oh well, i hope this thread helps someone in the future.
thanks once again.
saproandroid said:
wow it worked, thanks a lot man i was getting really scared
i know it was a newbie thing but oh well, i hope this thread helps someone in the future.
thanks once again.
Click to expand...
Click to collapse
That's not such a newbie thing. There is info about it but it's not the easiest to find. Also the solution is not at all obvious...
Sent from my abucus
this just saved my life...thanks for the solution!
Hi
I'm facing exactly the same issue and in full panic mode right now. Please help, I didn't comprehend what you guys meant by move the cursor past the top menu choice three times.Please!
rollno88 said:
Hi
I'm facing exactly the same issue and in full panic mode right now. Please help, I didn't comprehend what you guys meant by move the cursor past the top menu choice three times.Please!
Click to expand...
Click to collapse
Use the vol + and vol - buttons to move the menu selection cursor. You can cycle through the entire menu wrapping 3 times or you can move backwards from the top choice to the bottom choice then forwards to the top choice again, etc. the source code waits for this "wrapping" to occur 3 times before it enables the back option again.
Sent from my abucus
Chezbel said:
Use the vol + and vol - buttons to move the menu selection cursor. You can cycle through the entire menu wrapping 3 times or you can move backwards from the top choice to the bottom choice then forwards to the top choice again, etc. the source code waits for this "wrapping" to occur 3 times before it enables the back option again.
Sent from my abucus
Click to expand...
Click to collapse
Thanks a ton . The issue was solved by selecting with the power button for some reason. I'd been trying that earlier but pressing it alongwith the menu button so nothing had happened. Anyways, thanks again for your help and I hope this helps some future noob!
just saved my life thanks chezbel
why does it do that??
v3rsatile23 said:
why does it do that??
Click to expand...
Click to collapse
+1. What's the rationale for it?
I think it was originally to work around some broken hardware on an old phone. There may be comments in the source code, but i haven't looked in a long time.
EDIT: /bootable/recovery/recovery.c says
// Some users with dead enter keys need a way to turn on power to select.
// Jiggering across the wrapping menu is one "secret" way to enable it.
// We can't rely on /cache or /sdcard since they may not be available.
Click to expand...
Click to collapse
And you have to "wrap" 3 times to get the back button to be enabled/disabled.
Sent from my One XXX
Thanks Chezbel, you're my hero!
Saved me too, thanks!
i had this problem once, can't remember how i unlocked the back button but i think i pressed both volume buttons at the same time and it unlocked.
Chezbel said:
Move the cursor past the top menu choice 3 times in either direction.
Sent from my abucus
Click to expand...
Click to collapse
BRO..U SAVED MY LYF
THANKS
i got scared
again thanks a lot bro
i also had the same problem in my micromax p275 tab but no vol+ or vol- button how can i go through menu im using cwm recovery thanks guys and im using cwm recovery ok

Menu and Back buttons light up but will not respond

I have a i9000 16GB European version Galaxy S
The menu and back buttons stopped working after I flashed a custom rom. They light but they won't respond to touch at all. I have since went back to stock firmware but the issue persists. I have opened up the phone to see if any flex cables became lose, but the only flex cable there is for the home button (which is the only button that works btw). Can anybody help out? Thanks!
Try to:
1. Factory Reset;
2. Flash Stock ROM with re-partition.
spamtrash said:
Try to:
1. Factory Reset;
2. Flash Stock ROM with re-partition.
Click to expand...
Click to collapse
I already did that but it still doesnt work
Can be sensor hardware related problem then...

Unofficial CyanogenMod 10.1 - home doesn't work

Hi,
I downloaded a JB 4.2.2 CyanogenMod ROM from the original development's thread. I tried a couple of similar ROMs previously, but my home button doesn't work correctly on apparently any Ice Cream Sandwich + ROM. Essentially what happens is, when the screen is on, the home button is completely useless. Pressing it down, waiting for a few seconds - it just doesn't respond to any command. There are almost no options in the phone related to hardware buttons, and if I, for example, select an option to make holding down the hme button bring up the multitasking window, it still doesn't do anything. The only situation where I observed it doing anything is when the phone's screen is off - pressing the button instantly wakes the device up. I tried flashing the badass kernel, though it didn't really do much. Other hardware buttons seem to be working just fine. I had no such problem on CyanogenMod 7.2 and when I restore a backup with this system, it still works correctly. I don't have problems with getting into recovery either.
Another thing with this ROM is, the lockscreen doesn't appear, no matter if I set a security pattern, set it to slide or whatever else. Pressing the wake button or home button instantly wakes the device up.
I'm not sure whether it's a ROM-specific problem or what, but regardless, as a new user, this is the only forum I can post this problem to. If anyone knows a solution or if such a problem was solved previously, I'd be happy to learn the fix.
I bet you flashed gapps...
Sent from my GT-S5570 using xda premium
ast00 said:
I bet you flashed gapps...
Click to expand...
Click to collapse
Actually... yeah, I did. Is that a problem?
luke100ster said:
Actually... yeah, I did. Is that a problem?
Click to expand...
Click to collapse
Yes. Wipe data, reflash, wait until boot, then go to recovery and then flash gapps.
Sent from my GT-S5570 using xda premium
ast00 said:
Yes. Wipe data, reflash, wait until boot, then go to recovery and then flash gapps.
Click to expand...
Click to collapse
Huh, I would've never guessed this could be an issue, but I did as you said and... yeah, everything seems to be working perfectly fine. Thanks for the help, highly appreciated
ast00 said:
Yes. Wipe data, reflash, wait until boot, then go to recovery and then flash gapps.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
Perfect! Thank you very much. :good:
(it works after flashing gapps)
Edit: Home button does not wake up when it is in deep sleep. So, it is useless. I am sorry We need another fix.

[Recovery]【T210R & T210】 Unofficial CWM Adv. Edition PhilZ Touch

This is an old unofficial version. Please go to THIS thread for the updated, official version.
All information below this line pertains to the old, unofficial version. Use the link above to get the official version.
Updated (v2) Slow recovery bootup fixed.
This is an unofficial version of CWM Advanced/PhilZ Touch recovery. Main thread located HERE. Go to the main thread to learn about all the features.
It uses the zImage and ramdisk provided by @ketut.kumajaya with a few tweaks to get it working made by myself.
Please take a moment to say thanks and/or donate to @ketut.kumajaya for helping us out.
It takes a few seconds longer for CWM based recoveries to boot than the stock recovery, so be patient.
Credits go to:
@Phil3759 for the advanced features
@ketut.kumajaya for the working zImage
and of course Koush and the CyanogenMod team
Link to kernel source https://github.com/kumajaya/android_kernel_samsung_lt02
~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the on-screen menu doesn't show, hit one of the up/down buttons at the bottom to get it to appear. This is the same issue seen with CWM recovery and is caused by booting into recovery with the key combo. I highly recommend using the Quick Boot app or another software method of booting recovery.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Instructions:
1. Download ODIN on your computer.
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program. Un-check Auto Reboot. See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them).
7. Select "PDA" then choose the recovery file you want to flash.
8. Hit "START". Wait for Odin to finish (~10-15 seconds). The message area will display "RES OK" when finished.
9. Wait for device to restart. Skip this step if you unchecked auto reboot.
10. Restart directly to recovery mode before rebooting into OS.(Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen).
11. To get the Internal SDcard to be recognized properly, choose the Advanced option; then touch the "Storage set to" option. It should change from "/data/media/0" to "data/media/". Then reboot recovery using the "Power Options".
I also recommend adjusting the Menu Height to a smaller value using the PhilZ settings option.
Notes about ODIN
--Make sure that "Re-Partition" is NOT checked.
--Auto Reboot can be un-checked if the recovery doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 10).
Instructions for recovery flashable version:
Boot into your previously installed custom recovery.
Select the Install Zip option.
Find the recovery zip.
Flash.
Reboot recovery.
Enjoy your new recovery.
Main Menu
Downloaded and installed. What i found so far is that it reacts little slow and the time in the status bar is gone in lockscreen.... After unlocking clock comes back in status bar.
Cant change GUI height correctly, all the time i touch GUI it increases the value only...
batman08 said:
Downloaded and installed. What i found so far is that it reacts little slow and the time in the status bar is gone in lockscreen.... After unlocking clock comes back in status bar.
Click to expand...
Click to collapse
I'm not sure what you mean about the time. It is not supposed to be in the status bar on the lock screen, and that has nothing to do with this recovery.
Sent from my DROID RAZR MAXX HD
gr8nole said:
I'm not sure what you mean about the time. It is not supposed to be in the status bar on the lock screen, and that has nothing to do with this recovery.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
Ok, haven't paid much attention to that to be frank.
batman08 said:
Downloaded and installed. What i found so far is that it reacts little slow and the time in the status bar is gone in lockscreen.... After unlocking clock comes back in status bar.
Cant change GUI height correctly, all the time i touch GUI it increases the value only...
Click to expand...
Click to collapse
In regards to it reacting slowly, since you complained about that with TWRP also, I believe that is a problem with your tablet. I can't imagine it working any faster on mine. Every selection is immediate.
Keep increasing the gui height until it goes to a lower value (around 100 it switches).
Sent from my DROID RAZR MAXX HD
gr8nole said:
In regards to it reacting slowly, since you complained about that with TWRP also, I believe that if a problem with your tablet. I can't imagine it working any faster on mine. Every selection is immediate.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
Some other users also experienced slow reaction with latest TWRP. I used TWRP 2.5.0.0 and speed and reaction was ok, on 2.6.xx reaction is slow...
Awesome job. Like how this is all coming together slowly for this tablet...
gr8nole said:
This is an unofficial version of CWM Advanced/PhilZ Touch recovery. Main thread located HERE. Go to the main thread to learn about all the features.
Since your in the recovery mood you should check out shabbyPenguins recovery OUDHS I think
Click to expand...
Click to collapse
my phone is samsung GT-I8268 Marvell PXA988 kernel
please Compile CWM Recovery for I8268
 @ketut.kumajaya
Can we have cwm flashable zip please.
Regards.
Sent from my GT-N7100 using xda premium
nitol said:
Can we have cwm flashable zip please.
Regards.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Done. Flashable zip in OP.
After flashing one of the custom ROM's, I still get Android System recovery in Recovery mode. Tried 3 different ones, not working... Anyone? In Download mode it however says Custom...
/edit: turning off auto-reboot fixed it!
OP updated with v2. Slow recovery bootup fixed.
Ive tried this with auto reboot checked and unchecked.. and im still getting android recovery. I have Kies installed.. do i need to install drivers on my pc?? I waited several minutes but all i get is leave cs...
freak69ize said:
Ive tried this with auto reboot checked and unchecked.. and im still getting android recovery. I have Kies installed.. do i need to install drivers on my pc?? I waited several minutes but all i get is leave cs...
View attachment 2418355
Click to expand...
Click to collapse
Hit START
Ohhh.. DUHHH... hahaha i should have know that seeing thats how i rooted my S3. So i take it i have root also now right?? Or do i have to flash something else?
freak69ize said:
Ohhh.. DUHHH... hahaha i should have know that seeing thats how i rooted my S3. So i take it i have root also now right?? Or do i have to flash something else?
Click to expand...
Click to collapse
Flash the root.zip from the cwm or twrp thread.
Sent from my DROID RAZR MAXX HD
Hi, i have a t217A tab 3 7.0 and it has a msm8960 cpu not the msm8930 you mentioed earlier, which shows up under cpuz as a Krait 1.73 gighz
when i boot to recovery it says encrypted and the flash fails. im guessing i need a diffrent version. is there a current build for the touch screen recovery for this version already made and in place ? if so could someone link me ?
and i had a q , you mention that this should be flashed via already flashed recovery , is this mandatory or can i flash the touch version via odin straight away ? do i need to flash the regular non touch recovery then flash the touch or can i get away with directly flashing the touch recovery without first flashing the non touch?
I have rooted already , the method on this forum worked for the t217A
thanks
spydergt said:
Hi, i have a t217A tab 3 7.0 and it has a msm8960 cpu not the msm8930 you mentioed earlier, which shows up under cpuz as a Krait 1.73 gighz
when i boot to recovery it says encrypted and the flash fails. im guessing i need a diffrent version. is there a current build for the touch screen recovery for this version already made and in place ? if so could someone link me ?
and i had a q , you mention that this should be flashed via already flashed recovery , is this mandatory or can i flash the touch version via odin straight away ? do i need to flash the regular non touch recovery then flash the touch or can i get away with directly flashing the touch recovery without first flashing the non touch?
I have rooted already , the method on this forum worked for the t217A
thanks
Click to expand...
Click to collapse
No , it has msm8930 it will still show as 8960 it's a qcom thing. Also this isn't for your device.

[SOLVED] Wrong Recovery made touch screen off calibration

Hello everyone I tried looking up this problem and maybe I am not using the right words but I could not find a solution. I ended up installing the wrong TWRP recovery from the app to my Note 4 910T and now the touch screen is way off calibration. I ended up installing TWRP 2.0.3.0 Edge / Now that I was able to get the right one the screen still doesn't work right. I have to click almost middle of the screen to select bottom buttons. Any suggestions would help. Thanks
Tried re-flashing N910TUVS2EPK2 (Came with recovery) via ODIN and nothing. I also tried installing the recovery by itself via ODIN and nothing as well. I tried reflashing TWRP 2.0.3.0 and even tried CWM and nothing. I also tried installing these recoveries via ODIN, N910TUVU1ANK4, N910TUVU1ANIH. I tried the BL on its own "N910TUVS2EPK2" . No luck yet.
boot up system, use s pen to open dialer, dial *#2663# when the menu pops up hit the top white square that says tsp fw update. when its done you should be good to go.
moddernate said:
boot up system, use s pen to open dialer, dial *#2663# when the menu pops up hit the top white square that says tsp fw update. when its done you should be good to go.
Click to expand...
Click to collapse
Thank you for taking your time and answering. It worked!!!
Thanks
Thanks had same problem and this solved it.
moddernate said:
boot up system, use s pen to open dialer, dial *#2663# when the menu pops up hit the top white square that says tsp fw update. when its done you should be good to go.
Click to expand...
Click to collapse
So..I did that... and it just flashes something too fast to read, then says "mmi complete" and the problem continues..
....and now... i feel like an idiot.... I was not typing the * ... just #2663#.. it worked when I did it correctly.
I just thought I woudl point it out, in case someone else misses it, like I did .
ALSO.. you MUST have an active sim card in when you do it.

Categories

Resources