Hello there,
Is there anyone who can help me getting back to KitKat 4.4?
I have bought a Note Pro and the previous owner cleaned it and updated it to Lollipop.
The troubles I experience are:
flickering screen,
unwanted reboots and
the message: cpu overheated.
[solved this a bit by limiting background services and it is al lot less but I do not like it].
So I would like to go back to KitKat as I understood on this forum this OS is rockstable.
I flashed original firmware P900XXUANK2 [PHN version] with Odin to my Pro, well it starts up but freezes with
"Samsung" in the screen, and that is it. [Did this several times]
When I flash it back to Lollipop it works, but still having prementioned problems.
Is there anyone who would like to help me, I am a newby and searched on XDA but am stuck.
Would appreciate any help.
Greetings
Aedriaen
The Netherlands
I have a note pro p905
I flashed between lollipop and KitKat and never had similar problem
maybe it is your bootloader that is locked to lollipop and it prevents you from flashing KitKat
maybe you need to flash the KitKat factory firmware which is 4 files with pit file
if someone can confirm this I will put the link to a factory firmware
This sounds like the battery connector issue to me, it may not be software.
http://forum.xda-developers.com/showthread.php?t=2835337
Sent from my SM-P900 using Tapatalk
Aedriaen said:
Hello there,
I have bought a Note Pro and the previous owner cleaned it and updated it to Lollipop.
The troubles I experience are:
flickering screen,
unwanted reboots and
the message: cpu overheated.
[solved this a bit by limiting background services and it is al lot less but I do not like it].
So I would like to go back to KitKat as I understood on this forum this OS is rockstable.
I flashed original firmware P900XXUANK2 [PHN version] with Odin to my Pro, well it starts up but freezes with
"Samsung" in the screen, and that is it. [Did this several times]
Click to expand...
Click to collapse
You should read the threat " Flickering Screen "
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Lollipop or Kitkat, either cannot solve hardware problem: cracked battery connector. This connector should be re soldered, software cannot fix it.
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
Again, either system can not fix this problem of cracked battery connector.
muzzy996 said:
This sounds like the battery connector issue to me, it may not be software.
http://forum.xda-developers.com/showthread.php?t=2835337
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Hello Muzzy996,
thanks for the reply, battery connector seems to be OK since I am able to transfer data between de pro and my pc.
Also Odin gives me a green light when I connect the pro to the pc. Loading the battery is not a problem either. So it seems to me the connector don't seems to be the problem.
Anyway, thanks for your help.
Appreciate it!
Beut said:
You should read the threat " Flickering Screen "
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Lollipop or Kitkat, either cannot solve hardware problem: cracked battery connector. This connector should be re soldered, software cannot fix it.
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
Again, either system can not fix this problem of cracked battery connector.
Click to expand...
Click to collapse
Hello Beut, thanks for the reply.
Connectors seems to be ok, loading the battery works fine, transfering data to my pc and vice versa works fine.
Odin gives a "green" light when flashing so I don't think this is the problem.
Tried it again with the latest Odin and flashing works fine, but the problem remains.
Flickering occurs only when the connector is not conneted to the device.
Appreciate your help.
Teflanzy said:
I have a note pro p905
I flashed between lollipop and KitKat and never had similar problem
maybe it is your bootloader that is locked to lollipop and it prevents you from flashing KitKat
maybe you need to flash the KitKat factory firmware which is 4 files with pit file
if someone can confirm this I will put the link to a factory firmware
Click to expand...
Click to collapse
Hello Teflanzy,
Thanks for the reply. I searched the internet for hours but am only able to find 1 file containing the Samsung
Galaxy Pro 12.2 Kitkat 4.4 firmware.
If someone has another or a site where to fetch it, I would appreciate it.
Appreciate your help.
Aedriaen said:
Hello Beut, thanks for the reply.
Connectors seems to be ok, loading the battery works fine, transfering data to my pc and vice versa works fine.
Odin gives a "green" light when flashing so I don't think this is the problem.
Tried it again with the latest Odin and flashing works fine, but the problem remains.
Flickering occurs only when the connector is not conneted to the device.
Appreciate your help.
Click to expand...
Click to collapse
I think you confuse between battery connector and USB connector. When using Odin, you are only working with USB connector.
Flickering when not connected to a charger, the problem is from your cracked battery connector which can only see under microscope.
Trust me, the only fix is resoldering your battery connector. Kitkat or Lollipop has nothing to do with flickering screen.
Beut said:
You should read the threat " Flickering Screen "
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Lollipop or Kitkat, either cannot solve hardware problem: cracked battery connector. This connector should be re soldered, software cannot fix it.
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
Again, either system can not fix this problem of cracked battery connector.
Click to expand...
Click to collapse
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
I think this is the problem, any idea where I can get the Kitkat bootloader for the Pro. Searched but didnot find it.
When I have this file [excuse me for being a newby] can I flash this with Odin using the BT option?
Greetings
Aedriaen
Aedriaen said:
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
I think this is the problem, any idea where I can get the Kitkat bootloader for the Pro. Searched but didnot find it.
When I have this file [excuse me for being a newby] can I flash this with Odin using the BT option?
Greetings
Aedriaen
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/
I don't know which model you have SM-P900 or SM-P905/907. Search for firmware from that site, Cellular South is for US region.
Depending which one you want, Kitkat and Lollipop have different bootloader.
what is your model ? What firmware are you going to flash ?
This is Bootloader for Kitkat Note Pro
http://www.mediafire.com/download/6862sfh6d8bjas7/BL_Kitkat_Note_Pro.rar
In Odin, you should load BL ( bootloader ) and AP ( rom file ), after it's done, you should boot normally to the start screen.
Beut said:
I think you confuse between battery connector and USB connector. When using Odin, you are only working with USB connector.
Flickering when not connected to a charger, the problem is from your cracked battery connector which can only see under microscope.
Trust me, the only fix is resoldering your battery connector. Kitkat or Lollipop has nothing to do with flickering screen.
Click to expand...
Click to collapse
Hello Beut,
I found out that when the battery is above 40% the problem does not occur. Only beneath 40% the flickering
starts???
Greetz
Aedriaen
Aedriaen said:
Hello Beut,
I found out that when the battery is above 40% the problem does not occur. Only beneath 40% the flickering
starts???
Greetz
Aedriaen
Click to expand...
Click to collapse
Must either be the internal battery connection or the battery itself. Again going to point you back to the flickering thread, specifically post 131 in it. Look at the photos in that post.
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Sent from my SM-P900 using Tapatalk
Related
Hi, hope someone can help me.
I have a Samsung Galaxy S4 (GT-I9500), it was on Android 4.3 and I upgraded to Andorid 4.4.2 via Kies.
This was a legitimate provider update.
Immediately on the first boot the Samsung Logo was blocky and pixelated, so was the Samsung animation.
This blocky-ness persists on the desktop and any app I open.
UNTIL I lock the screen and unlock it. Then everything becomes clear again.
I since then I installed a new 4.4.2 ROM via Odin, but no luck.
I have ClockWorkMod installed too. The strange thing is that when I boot into recovery mode (into ClockMod) the resolution is fine.
Any ideas?
Help would be greatly appreciated.
Thorfell said:
Hi, hope someone can help me.
I have a Samsung Galaxy S4 (GT-I9500), it was on Android 4.3 and I upgraded to Andorid 4.4.2 via Kies.
This was a legitimate provider update.
Immediately on the first boot the Samsung Logo was blocky and pixelated, so was the Samsung animation.
This blocky-ness persists on the desktop and any app I open.
UNTIL I lock the screen and unlock it. Then everything becomes clear again.
I since then I installed a new 4.4.2 ROM via Odin, but no luck.
I have ClockWorkMod installed too. The strange thing is that when I boot into recovery mode (into ClockMod) the resolution is fine.
Any ideas?
Help would be greatly appreciated.
Click to expand...
Click to collapse
can you give us a pic?
Trozzul said:
can you give us a pic?
Click to expand...
Click to collapse
Here you go.
I find out something else.
If I enable the lock screen pattern the the display stays blocky.
Thorfell said:
Here you go.
I find out something else.
If I enable the lock screen pattern the the display stays blocky.
Click to expand...
Click to collapse
I think it's got to be config or software related beacause if I turn the lock screen back to swipe, restart and then lock it's fine again.
I just took a look at the screenshots I attached.
They look fine!
that's very odd. What would cause the screen to display the images badly but save the screenshots as normal?
Thorfell said:
I just took a look at the screenshots I attached.
They look fine!
that's very odd. What would cause the screen to display the images badly but save the screenshots as normal?
Click to expand...
Click to collapse
well if CWM looks fine, try flashing twrp and see if twrp is pixely, if not get back to stock 4.2.2 or 4.3 and see whats up. maybe you had a bad install on 4.4?
Trozzul said:
well if CWM looks fine, try flashing twrp and see if twrp is pixely, if not get back to stock 4.2.2 or 4.3 and see whats up. maybe you had a bad install on 4.4?
Click to expand...
Click to collapse
I tried flashing back to 4.3, but Odin Failed.
I am trying to get a different 4.4.2 ROM now.
Once I download the new ROM (my bandwidth is terrible), do you think it's worthwhile to re-partition in Odin as well to fix the blocky issue?
Do you think it could be boot loader related?
Thorfell said:
I tried flashing back to 4.3, but Odin Failed.
I am trying to get a different 4.4.2 ROM now.
Once I download the new ROM (my bandwidth is terrible), do you think it's worthwhile to re-partition in Odin as well to fix the blocky issue?
Do you think it could be boot loader related?
Click to expand...
Click to collapse
thats up to you for the re partitioning, you know what it does right? as for Odin, did you get your firmware from here Sammobile.com? is download mode the same way as well?
Trozzul said:
thats up to you for the re partitioning, you know what it does right? as for Odin, did you get your firmware from here Sammobile.com? is download mode the same way as well?
Click to expand...
Click to collapse
I fugure if the pixelation is config related or a corruption then a repartition would fix it.
I will put a 4.3 XFA rom from sammobile and see if the problem goes away. It will have to be on after the easter weekend though
Thorfell said:
I fugure if the pixelation is config related or a corruption then a repartition would fix it.
I will put a 4.3 XFA rom from sammobile and see if the problem goes away. It will have to be on after the easter weekend though
Click to expand...
Click to collapse
No matter what I do, I can't get a 4.3 ROM on my galaxy.
I have flashed back to an official Samsung 4.4.2 for my region but the blocky-ness is still there.
I'm going to take the device to a Samsung store and see what they say.
Thanks for the advice.
Thorfell said:
No matter what I do, I can't get a 4.3 ROM on my galaxy.
I have flashed back to an official Samsung 4.4.2 for my region but the blocky-ness is still there.
I'm going to take the device to a Samsung store and see what they say.
Thanks for the advice.
Click to expand...
Click to collapse
Latest update: The Samsung Service centre is not particularly helpful.
I left my phone there yesterday and explained the problem.
Got the phone back and all they had done was wipe the data and reinstall Android. It has not fixed the pixelated problem.
I explained the problem again in excruciating detail and have left the phone with them once again.
let's see what happens.
Can anyone tell me what actually kicks off the graphics processing as soon as the phone boots?
As in when the very first image is displayed on boot (the Samsung logo with device model number).
Is it the bootloader? If so any ideas on what I can do to reinstall the standard samsung one?
Problem solved.
So after all of that Samsung replaced my screen and it sorted the problem out!
Still, it's very odd that it failed immediately after the 4.4.2 update.
Two days ago my Galaxy Note 10.1 gt-n8010 got stuck at the initial screen (Samsung Galaxy Note 10.1)
It was working normally, and it was last successfully upgraded to a custom rom and CWM 6.0.3.6 a month ago.
The custom rom was (to my best knowledge Android Revolution HD 11.2 - 4.1.2)
Booting into recovery and download modes works.
CWM recovery works partially. Erasing Cache en resetting to factory works, and sometimes results in getting to the second splash screen of the boot process where it again gets stuck (Samsung animation keeps glowing), but more it keeps getting stuck at he first boot screen.
Erasing Dalvic cache leads to immediate reboot.
CWM log files cant be opened / external sd card can't be reached/mounted.
So CWM is only working for a small part.
I've attached images of the CWM screens including a log-screen that shows that files and folders cannot be found.
Using ODIN, to flash a new CWM or custom/original ROM result in a FAIL message.
Tried different ODIN version, two original Samsung data cables and two computers. Alle the same result. FAIL.
I'm hesitant to continue now without some help. I might do more harm and destroy all chances there are to recover this tablet.
I've flashed all my phones and tablets before. I'm not an expert, but never had a mishap, because I triple read the instructions. The situation that arises now is not a result of a failed upgrade/flash, but suddenly appeared one morning.
On the last days i thought i had also broken my tablet and i had more or less the same problem. If i were you i would directly download an official 4.4.2 and flash it via odin. Then if you everything works i would try whatever you want to flash
Try changing recovery. Give TWRP a try. Had it happen with a phone and switching recoveries solved it.
Sent from my SM-N900T using XDA Free mobile app
Well I had the same problem due to toooo many consecutive reboots
I was on gnabo then wid twrp
then I reflashed 4.4.2 update via odin and everything was a breeze after that
and one more thing
be sure to change the recovery cause the same one might not work again
well at least it didn't do worth me
I use philz now
Can't flash anything
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Deadbeef said:
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Click to expand...
Click to collapse
are you sure you do not have a bad cable
I've used two different original Samsung cables. Same result.
Brick?
Change a Odin version like odin 3.07 http://forum.xda-developers.com/showthread.php?t=1837605?
your odin shows your device is Samsung I9505 Galaxy S4
Where does Odin show the device is a i9505? It's a n8010.
reCAPTCHA
I am having similar issues (Galaxy Note 10.1 N8010 Gnabo ROM) - stuck on the samsung logo (never managed to get past it though) boots into recovery but can't mount sd card OR internal storage. Can't flash anything using Odin, always gets a Complete(Write) operation failed. Any suggestions ?
Looks like we're both in the same sinking boat.
Sorry for late reply
Deadbeef said:
Where does Odin show the device is a i9505? It's a n8010.
Click to expand...
Click to collapse
Sorry for late reply
Your Odin Screen Shot Say i9505 as your device
Deadbeef said:
Looks like we're both in the same sinking boat.
Click to expand...
Click to collapse
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
georgesmh said:
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
Click to expand...
Click to collapse
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Agyar said:
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Click to expand...
Click to collapse
guys did any of you solve the problem??
georgesmh said:
guys did any of you solve the problem??
Click to expand...
Click to collapse
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Agyar said:
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Click to expand...
Click to collapse
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
georgesmh said:
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
Click to expand...
Click to collapse
I've seen few other occurrences of this on different roms on various forums, so probably not Gnabo issue. also, nobody nowhere had a fix for it
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
dmarchant said:
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
Click to expand...
Click to collapse
I don't think it was flash failure, at least not in my case, since device worked without any issue for quite a while after last flashing... what was different now is that my battery was drained out for the first time i quite a while...
Hello all. I am from the UK and recently purchased a sprint model phone. I wanted to remove handsfree activation. In order to do that i need a root. I rooted 5.1.1 with kernel SpaceX-Kernel-v0.1_N920P(official).tar and all seemed ok. Then i noticed that you could root marshmallow. I followed a tutorial on youtube and flashed two files through twrp no-verify-opt-encrypt.zip and SuperSU zip. I rebooted the phone and now i have a persistent problem. After around 15-30 seconds my phone shuts off and reboots itself. I have tried reflashing stock roms and the problem still persists. I have no idea if i have broken the phone as its usable until it shuts off . I went into the about phone section and it tells me the baseband and software versions are unknown aswell. Is there anyway to recover this?
Known issue. Drain battery until it is dead and charge again.
tdunham said:
Known issue. Drain battery until it is dead and charge again.
Click to expand...
Click to collapse
Thank you very much for responding. That has solved the issue completely! Using MOAR rom on 6.0.1 with no issues. Thanks once again!
suddenly i bought this phone second hand. then when I tested Turning on my bluetooth it won't turn on.
Is there anyone experiencing the same problem?
I already did troubleshoot and performed this steps:
1. Wipe cache of Bluetooth Applications on System apps in settings
2. Force stop Bluetooth Applications on System apps in settings
3. Restart my phone
4. Wipe Cache on stock Recovery & restart my phone
5. Restore Factory Settings on Recovery
but suddenly bluetooth still won't open when touching it on notification panel nothing happens even directly on the settings toggling the bluetooth won't work. :crying:
my phone is untouch on rooting world.
So my questions is;
1. Will rooting and flashing rom can solve my bluetooth problem?
2. Is this a hardware problem?
3. Is there a separate chip or module for bluetooth on the motherboard of S7 edge?
to all XDA members I'm asking if you have an idea on this matter please feel free to reply to this post.
thanks you so much!
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Beanvee7 said:
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Click to expand...
Click to collapse
if it is a hardware problem? is there a separate module or chip on the s7 edge motherboard? or it is integrated on the processor ?
I don't know the answer to that
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
dhawal4u said:
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
Click to expand...
Click to collapse
what custom rom have you tested?
i already tried Batman-Rom
lervzz said:
what custom rom have you tested?
i already tried Batman-Rom
Click to expand...
Click to collapse
batman / superman / tgp and many others
none working
dhawal4u said:
batman / superman / tgp and many others
none working
Click to expand...
Click to collapse
I tried flashing newest stock nougat firnware XTC csc.
Tried it using ODIN
But still bluetooth won't turn on.
Can you say that our problem is hardware failure? But I think if it's a hardware issue then wifi should not work too. Because wifi and bluetooth is on the same chip module. ???
Update: I've talk to numerous technician and they think its not a hardware issue since my wifi is working. They said that wifi and bluetooth is on the same micro chip module. So if it is hardware issue on the bluetooth wifi should not work too. ???????? @dhawal4u
Same Problem here. Since 2 months after trying Badman Rom my Bluetooth doenst work. Now I load Stock Rom, Bootloader, Modem but no solve for the Problem
Hello people of XDA Forum,
Since a couple of years I own a Xiaomi Redmi 8A, which I ordered brand new on AliExpress.
After a couple of failed attempts to install a Custom Rom on the device, I still have an unlocked bootloader
and a "offical" stock firmware on the smartphone installed. Sadly now occurs an other problem,
frequently the screen "freezes" when I want to use the touchscreen. Sometimes when I put the power-button
and pressing it another time the screen responsed to it. But not always, it's getting very frustating when
for example I play "Call of Duty Mobile". My question is that I want to know of the problem is software-
or hardware based? Hopefully you can help me out, thnx
Have you modified anything in your device recently? No? Then it's probably hardware issue.
Do you have any damage to your phone? Then it's even more likely to be hardware issue.
XDHx86 said:
Have you modified anything in your device recently? No? Then it's probably hardware issue.
Do you have any damage to your phone? Then it's even more likely to be hardware issue.
Click to expand...
Click to collapse
Thanks for the reply. Now I have this problem for a couple of weeks sadly... There is no visible damage on the
device, but I have dropped the smartphone a couple of times out my hand... So I have this problem and I thought
that a firmware upgrade might help me out, but the problem still remains.
TrippyBlade said:
Thanks for the reply. Now I have this problem for a couple of weeks sadly... There is no visible damage on the
device, but I have dropped the smartphone a couple of times out my hand... So I have this problem and I thought
that a firmware upgrade might help me out, but the problem still remains.
Click to expand...
Click to collapse
If you think the damage to your phone is significant enough for it to affect your screen then maybe you should send it for a checkup.
Although you can try using different ROM to test if it works since it's probably much cheaper to do so than fixing the screen.
But don't flash an OTA update, flash latest stock ROM manually or flash a custom ROM. That way the settings are reset, you can backup your data with TWRP.
XDHx86 said:
If you think the damage to your phone is significant enough for it to affect your screen then maybe you should send it for a checkup.
Although you can try using different ROM to test if it works since it's probably much cheaper to do so than fixing the screen.
But don't flash an OTA update, flash latest stock ROM manually or flash a custom ROM. That way the settings are reset, you can backup your data with TWRP.
Click to expand...
Click to collapse
Allright, thank you very much for the suggestion. Finally I managed to flash an older Fastboot ROM through
the "MI Flash Tool", which solved my touchscreen problems.