[FIX GUIDE] For Flickering / jumping screen after unlocking the screen - Galaxy Tab 10.1 General

Hello , like many of you , i got the flickering screen / jumping screen after unlocking my screen. Rebooting works but as soon as i close the screen or it shuts itself, unlocking it will cause it to flicker / jump like if the resolution was bad or something.
Installing ANY rom from the developpers did not work. From jellybean to revolution , to any popular modified rom.
My tablet is the galaxy 10.1 P7510 , here's what i did.
Updated clockworkmod from 4.0.04 to 5.5.0.4
Restore tablet to the day 1 when you unrooted it (instructions clearly told you to make backup, remember?)
Install Kies official by samsung
Update your tablet , you will now gain the newest version , official by samsung
Your tablet will now be rooted by samsung though , few components of the CWM remains.
Download clockwork mod 5.5.0.4 recovery file , flash it through Odin3 through PDA section
You will now gain back Clockworkmod but yout CWM will flicker / jump like crazy
Make your way through wipe
You may now try to install any modified ROMs, me i installed Revolution 1.0
Make your way through installing the ROM , i put it in ALARM folder because its the easiest to reach , choose your ROM , then press down 6 times to be able to press on YES to installt he rom
RESULT : CWM flickers / jumps but my modified ROM FINALLY does not jump / flicker after unlocking the screen
Good luck everyone!!!!!!!!!!!!

Hello,
this doesent work for me.
My tab cant be updatet with Kies. ist only 3.1.
When i flash the 4.0.4 open Austria with odin i will have the flickering screen.

Related

Device soft brick after flashing rom

Hello all hope you will be able to help me.
Device : Nexus S I 9020
So basicly iam kinda new to whole this world of "android" former Iphone user.
last mounth i got my nexus S wich is my first android phone.
As soon as i got it i started to read guids and etc.
Root the device and ofc the nexy step was trying Rom`s.
but then a problem , every time i try to flash a rom i get status 7 error.
tryed every possible combination of restore / wipe etc...
nothing helped , so i came back to the stock one (backup i made before i started)
after a while i discovered the app Rom mananger , wich install rom update recovery etc...
so i updated my recovery and installed CM7 using it.
used it for a while and went back to the stock.
after cople of days tryed to install MIUI using rom manger every thing went clear and after the intall device reboot it self and then stuck on the Google logo with the lock in the botom of the screen.
and nothing helped since then restore , factory reset/restore / wipe`s etc.
as last resort i tryed Odin and it worked like a charm got my device back and runing.
today i tryed to install a new rom AOASP(i think , or some thing like that) in the first time from the recovery (several times) with every possible wipe.
all the time status 7 error , then went to rom mananger and again same thing.
stuck on the google logo.
now iam gonna use Odin again hope it will work this time too.
Any idea how to resolve it , or why this is happen ?
and how can i resolve the status 7 error and what does it mean ?
Thank you all.
(sorry for this been so long , wanted to give as much details as possible)
Contact this guy. Looks like the same problem. If you can't get it going, I can also fix it so just PM me...
http://forum.xda-developers.com/showthread.php?t=1091789
doesnt seem to be the same problem like i had.
Any way at this point i was able to restore my phone using Odin , and then restore it into my stock backup (including all my data and etc...)
but the problem remain the same.
cant install any rom (status 7 error).
and when i try to install any rom using Rom mananger iam stuck on the google logo after the reboot.
so what can i do ?
Problem solved by using Odin ro restore it and after that flash Nanbackup and finally updating the CWM recovery.
If any one get the problem try this
Btw SuperAOSP is GREAT !!!!
gl all.

[Q] Help. Stuck on the title screen after I removed SG4 battery during boot.

Hi everyone,
I'm a noob here but I read the guidelines
You're the only who can save me tonight (it's 3 a.m. here and sry for my bad english).
I rooted my Galaxy S4 (international version - Snap 600 - i9505) and I flashed the latest nightly of cyanogenmod. I started my device and, after 4-5 minutes, the rom started. I felt immediately disappointed, it's a pre-alfa version and I installed it just to try it.
So, I decided to install the Pure Google Rom with Android 4.3 (http://forum.xda-developers.com/showthread.php?t=2341026).
I rebooted my device, but for some reasons (I got a small crash, because I failed, removing my battery during the boot animation), my phone is now stucked at the title screen.
I can see just "Samsung Galaxy S4 - GT_i9505" on an infinite black screen. I'm so sad, I wish to solve this problem...
P.S. I tried to reboot in recovery mode: almost the 70% of the times I tried, it failed entering recovery mode. The only time it entered recovery, I wiped everything, but nothing seems to change.
Please help :\
demLong said:
Hi everyone,
I'm a noob here but I read the guidelines
You're the only who can save me tonight (it's 3 a.m. here and sry for my bad english).
I rooted my Galaxy S4 (international version - Snap 600 - i9505) and I flashed the latest nightly of cyanogenmod. I started my device and, after 4-5 minutes, the rom started. I felt immediately disappointed, it's a pre-alfa version and I installed it just to try it.
So, I decided to install the Pure Google Rom with Android 4.3 (http://forum.xda-developers.com/showthread.php?t=2341026).
I rebooted my device, but for some reasons (I got a small crash, because I failed, removing my battery during the boot animation), my phone is now stucked at the title screen.
I can see just "Samsung Galaxy S4 - GT_i9505" on an infinite black screen. I'm so sad, I wish to solve this problem...
P.S. I tried to reboot in recovery mode: almost the 70% of the times I tried, it failed entering recovery mode. The only time it entered recovery, I wiped everything, but nothing seems to change.
Please help :\
Click to expand...
Click to collapse
Usually the international version is i9500 running on Exynos Octa core. Are you sure you loaded the right firmware?
If you have flashed the custom recovery (CWM, Philz, TWRP), you can try to load different firmware (copy to SD card first). Worst case, you can use Odin to flash. Unless it is hardware problem, it is not easy to brick the phone.
Thx
tingtan said:
Usually the international version is i9500 running on Exynos Octa core. Are you sure you loaded the right firmware?
If you have flashed the custom recovery (CWM, Philz, TWRP), you can try to load different firmware (copy to SD card first). Worst case, you can use Odin to flash. Unless it is hardware problem, it is not easy to brick the phone.
Click to expand...
Click to collapse
Thank you, I flashed the philz touch version for i9505 and it works flawlessly. I installed the Google Stock Rom and it's working. I'll update tomorrow if I got crashes or black screens.
Thank you so much tingtan

[Q] After rooting, flashing recovery and echorom v2 screen works all wrong!

Hi guys, I rooted my new note 4 n910f (snapdragon version) via odin and also installed clockwork mod 915f by accident, then used the clockworkmod recovery to flash echo rom and once I booted up I realised my whole screen works all wrong, I'll have to press a whole inch higher than a button is on the screen for it to work. Its as if my whole screen is extremely un calibrated now. When I was running pure out of the box stock it was fine so it can't be a hardware issue if it was working a hour ago just fine.
How do I fix this issue and what can I do?
I have to press on a completely different part of the screen than whats being shown to interact with the system...
restore nandroid or flash official stock rom, then do it again with all that made for 910f ?

Help urgently !

today I tried to install CyanogenMod 12.1 on my Samsung note 3 SM-N900 (4.4.2) from this project
http://forum.xda-developers.com/gala...od-12-t2999486
and it mentioned in 1 of the comments that i have to get lollipop bootloader so i could flash the CM Mod ... so i flashed the bootloader and i tried to boot my device . It kept viewing many errors of many apps that stopped working and behind it is a black screen ... i tried resetting the mobile to its factory setting ( first time flashing ROMS so i was a bit afraid ) and it works totally fine . even when i restart the device but when i enter the recovery menu and click reboot from there the whole bunch of errors comes back .. so my question is what did i do ? what exactly is a boot loader ? could i continue on with my device like this without getting near the recovery menu ? or will it lead to an error in the near future ?
yoyo3999 said:
today I tried to install CyanogenMod 12.1 on my Samsung note 3 SM-N900 (4.4.2) from this project
http://forum.xda-developers.com/gala...od-12-t2999486
and it mentioned in 1 of the comments that i have to get lollipop bootloader so i could flash the CM Mod ... so i flashed the bootloader and i tried to boot my device . It kept viewing many errors of many apps that stopped working and behind it is a black screen ... i tried resetting the mobile to its factory setting ( first time flashing ROMS so i was a bit afraid ) and it works totally fine . even when i restart the device but when i enter the recovery menu and click reboot from there the whole bunch of errors comes back .. so my question is what did i do ? what exactly is a boot loader ? could i continue on with my device like this without getting near the recovery menu ? or will it lead to an error in the near future ?
Click to expand...
Click to collapse
You should have read before doing this.
It means flash the lollipop version first or update to lollipop if available.
Your url doesn't work for me.
Then flash twrp. In twrp flash cm12.1 and a recommended gapps.
You need to get logcat and post it to that thread so the developer can helo you. But first you need to do your part and at least get through the flashing process.
I wouldn't ignore any system errors.

G900F - Can't use the screen after installing a custom rom.

Hey guys,
the phone:
Samsung Galaxy S5 SM-G900F
Last official firmware:
G900FXXU1POJ2 (VD2) 5.0 Germany
I flashed TWRP via Odin
Then SuperSU via ODIN
Then installed a custom recovery.
After full install and reboot it hangs on the first screen and I cannot touch it. It won't do anything. Reboots, deleting cache won't help.
Do you know what I did wrong or why I can't use my phone anymore?
mrclaver said:
Hey guys,
the phone:
Samsung Galaxy S5 SM-G900F
Last official firmware:
G900FXXU1POJ2 (VD2) 5.0 Germany
I flashed TWRP via Odin
Then SuperSU via ODIN
Then installed a custom recovery.
After full install and reboot it hangs on the first screen and I cannot touch it. It won't do anything. Reboots, deleting cache won't help.
Do you know what I did wrong or why I can't use my phone anymore?
Click to expand...
Click to collapse
I installed a freshly new official stock rom, it'll boot but won't go any further and bootloops.
Then I tried a CM - ROM and it's the same with another rom. The touchscreen doesn't work. But the touch works on TWRP. That's really weird.
It freezes, the LED is always on and the softbuttons too.
ask you if you have this problem before root
lol twrp is costume recovery and just flash twrp and applied the supersu.zip and its done phone rooted
but if you have problem after touch think
1- you don't flash the true cm ( klte is for 900F )
2- your touch panel is damaged
3- for your original stock rom ( lag ) ty to wipe data and cache ( attention you will lose your data with )
popmpopm said:
ask you if you have this problem before root
lol twrp is costume recovery and just flash twrp and applied the supersu.zip and its done phone rooted
but if you have problem after touch think
1- you don't flash the true cm ( klte is for 900F )
2- your touch panel is damaged
3- for your original stock rom ( lag ) ty to wipe data and cache ( attention you will lose your data with )
Click to expand...
Click to collapse
- I was on official vodafone germany firmware.
- Phone told me to get the last update
- Phone installed last update
- After installation phone was bootloopin
- I did hard reset
- Phone booted up until it said, that it is installing a few applications (you know what I mean)
- While installing progress of that it restarted and installed and restarted and so on..
So I decided to get a custom rom.
- I flashed TWRP for KFTL (I have SM-G900F) via ODIN.
- Everything works fine.
- I flashed Chainfires SuperSU via ODIN.
- Everything works fine.
- I installed a custom ROM (eg: The Galaxy Project)
- It booted and then freezes.
So after that I was afraid and flashed a stock rom via Odin but it was the same with the official OTA-update from Samsung. Reboots while installing first apps.
Then I tried with CM but it freezes too. I am sure it has nothing to do with the screen.
On official (stock) ROMs it reboots while installing first apps.
On custom ROMs it freezes. It won't go any further. It must be something else. Any ideas?
BTW: I have another SM-G900F and it works flawlessly. I know that I am doing.
what y mean freeze the phone or just touch ( but bottom work like vol )
if only touch think is damaged
popmpopm said:
what y mean freeze the phone or just touch ( but bottom work like vol )
if only touch think is damaged
Click to expand...
Click to collapse
Hm. If you boot up your phone for the first time or after hard reset or after an update it boots up and then there comes the very first message that android is preparing the apps for the first start, right? On official firmware it bootloops when that message comes.
On CyanogenMod it boots until this Screen:
And then it freezes.
I can't believe that it has to be the touch panel, because everything works fine in TWRP. The phone won't let me go any further than the first Screen. And the touch can't be damaged. Before I did the official Samsung update everything works fine.
mrclaver said:
Hm. If you boot up your phone for the first time or after hard reset or after an update it boots up and then there comes the very first message that android is preparing the apps for the first start, right? On official firmware it bootloops when that message comes.
On CyanogenMod it boots until this Screen:
And then it freezes.
I can't believe that it has to be the touch panel, because everything works fine in TWRP. The phone won't let me go any further than the first Screen. And the touch can't be damaged. Before I did the official Samsung update everything works fine.
Click to expand...
Click to collapse
y don't understand me the bottom work or not when phone is on freeze moment if yes think is not touch is all phone ( cpu ram some thing hardware )

Categories

Resources