I have Prestigio PAP 4500 with Clockwork mod recovery installed. I have installed custom 4.0.4 ROM on it and it worked well for about a year. Yesterday the device started to heat up in upper part(I think wireless module is stored there, as WiFi usage also heated that part). It also started to drain energy very fast - it already was 10% down few minutes after unplugging from overnight charging. I've though some process might be using 100% power so I tried rebooting. It got stuck in android loading screen for over an hour before I decided to remove battery.
I've tried to use clockwork menu to return to factory settings, wipe partitions. Didn't help. I've tried installing stock another rom(PAP 4500T DUO JB 4.2.2 by serg v4.1 Final port Lenovo, "сток"). It also got stuck in Android loading screen. After that I returned to stock rom and it is stuck on eReader Prestigio app ad, which Prestigio shows during loading.
When stuck on that screen upper part of the phone heats up a lot. The battery is not getting warm. I know that after changing rom it might take longer for device to boot, but I have waited for 1 hour or more each time. I've also tried booting without SD card and SIM card.
What else can I do to possibly make the device work? XDA Assist said it might be hardware issue, if so it would be nice if I could do something more to diagnose it.
Related
Hi guys,
so the main Problem is, my GT-I9100 does not Boot properly, or turns off pretty fast (it somehow does boot, but it turns off while booting).
I'll try to explain step by step what i did so far.
I had a Custom Cyanogenmod 9 Rom on my Phone and it worked for like half a year now (was too lazy to update).
And suddenly it wasn't able to boot anymore as described. I thought it was the Battery so i charged it for a few hours, but still couldn't boot.
After that i tried to start into CW Recovery, wiped Cache, Wiped Dalvik -> still same problem.
Then i just let the phone on on Recovery mode until the Battery was totally empty, recharged to 100% -> still same problem.
So i thought, the rom might got crushed howsoever -> installed Original Kernel with Odin BUT the problem still occured....
That's the point where i am right now.
The Phone starts, the "Samsung Galaxy S2 GT-I9100"-Logo shows, the Boot-Logo shows up (Cyanogenmod logo showd up as well as now the Samsung Logo). On CM the Phone turned off while booting, now it always gets through the Samsung boot Logo, it initialized some apps (cause off Factory Reset) like 9/46 Apps then shuts down, after turning it on again it starts returning to initializing the apps now and again after a few initialized apps like 10/37 it shuts down again.
I kept on turning it on until all apps were initialized and now it tries to instal the initialized apps but shuts down after a short time again. And it is not able to instal a app in that short time, so i wont make any progress anymore with turning it on over and over again...
Don't really know whats wrong, already unplugged SIM. I thought about it being a Hardware Problem... But maybe it's not and you might know some way to fix it
I'll get my HTC One soon, delivery started yesterday, so it's not that much of a problem, but it's a shame 'cause i wanted to give my S2 to my brother
Hi Guys,
i have a serious problem with my mediapad 7. I dont use it very often since i've bought me a nexus 5. So it lays some weeks with no usage on my desk. Yesterday i've tried to start it, but it shuts down after reboot, with a battery is empty message. So i have loaded the battery the last night (it should be 100%) but today it still shuts down after booting with the empty battery message. Also, if it is connected at the charger during the boot process.
So i have booted in recovery mode (TWRP) and have wiped the whole system, installed it new and booted it up. Still battery error. So i have deleted the batterystats.bin file in recovery, but the problem remains.
My RomVersion is Cyanogenmod 10.2.
So. Before I begin to disassemble the tablet and change the battery, I wanted to ask if anyone has a tip for me here.
Best regards,
Jacob
If you formatted the data partition it's bricked. Data should just be wiped, w/o the media folder.
W/o a working nandroid backup, i once had to reflash the stock recovery via usb, then flash a rom with the dload method(sd card), stock 4.03 or the rooted variants Comec v2.1(didnt work for me) and CleanICE. As in CleanIce the Network Location service was missing, it was only good for reflashing TWRP and now being able to install roms thru it.
I own a stock rom rooted note2 with Os 4.3 JB. Since few days battery is draining fastly, it is discharging when being charged but it doesn't discharge when the phone is switched off. Also, whenever I restart or power on android it starts with logo which says - " Android is upgrading.... Starting apps.... finishing boot...", this happens on every start up although android works after that but drains at very fast rate. This happened after flashing audio zip for increasing volume from this thread " http://forum.xda-developers.com/showthread.php?t=2799537 ".
Please help! ! it has imp. data, and I have to recharge it again and again, avg battery capacity of note2 stands for 8 hrs but it just drains out within 2 ~ 4hrs on light usage. I did wipe out dalvik cache because of problem with super user which is working well right now( this fix I found on XDA). I went to recovery mode to find problem for the same I.e Android upgrading, there on clicking both reboot and shutdown ( once at a time), error poped out saying- " root possibly lost. Fix? ... no... .no... fix root (/system/xbin) etc., then after applying fix, the device rebooted and showed android upgrading ... finishing boot... then I went to root checker it said rooted and all the other root functions are working, but now battery is draining,(discharging even while charging), after switching to recovery mode and again rebooting, same root fix error repeats itself and Android is upgrading ... finishing boot .. logo is displayed. Could you please suggest any other way so that instead of doing factory reset I can revert back these errors without unrooting or factory resetting as I myself had thought of doing the same but it is not possible, even reloading rom cannot happen since I didn't save latest rom which I was supposed to do after eradicating earlier problem but now this error has occurred.
Thanks in advance.
boot loop
Hello,
since yesterday my M4 E2303 is stuck in a boot loop. It just displays Sony xperia on a black screen and reboots. I did already a factory reset using the PC-Companion, but without any success. Has anybody an idea what other options do I have to trouble shoot? I've never used customized firmware.
sberk
try this...press volume up and volume down and power on/off same time, for 30 seconds
Thank you, I tried it. It vibrates but everything else stays the same.
This happened to me too. My phone booted after I connected it to my computer and then booted while keeping power+vol up. After a while it got past the Xperia logo
Thank you,
while I did not get the result I'm hoping for, at least I got some reaction. The LED turned blue and I found now a new fastboot device. Hopefully I can use the fastboot connection to get more information.
sberK82
Hello, stuck with same problem on my E2303, did you found out how to fix this problem?
miltostammy said:
try this...press volume up and volume down and power on/off same time, for 30 seconds
Click to expand...
Click to collapse
Thank you thank you thank you thank you thank you!!! I managed to shut it down and now I'm in the recovery. This is best than nothing. Thanks!!!
Not firmware fault
sberk82 said:
Hello,
since yesterday my M4 E2303 is stuck in a boot loop. It just displays Sony xperia on a black screen and reboots. I did already a factory reset using the PC-Companion, but without any success. Has anybody an idea what other options do I have to trouble shoot? I've never used customized firmware.
sberk
Click to expand...
Click to collapse
I fixed my sony m4 Aqua by simply putting it in the freezer, you should try it, it is the processor that is overheating I also tried firmware and everything else but the phone worked fine for about another day
Jeffrey69__4 said:
I fixed my Sony m4 Aqua by simply putting it in the freezer, you should try it, it is the processor that is overheating I also tried firmware and everything else but the phone worked fine for about another day
Click to expand...
Click to collapse
hello
I had same problem yesterday and today, for no reason heated a bit (maybe over 50 degrees ) and rebooted, but after some time didn't want to boot again, just waited to cool down and boot to success
my recommendation is that after booting Android install an CPU tuner (if you are rooted) and low max speed for big and little, it does not heat so much and performs quite well
my M4 heated over 70 Celsius degrees, quite uncomfortable to keep it in hand
helo
now my problems with overheating and reboots are even bigger, doesn't want to boot , reflashed with flashtool, without excluding and without wipe from recovery, and done a factory reset, problems not solved, no root for now, just custom recovery, disabled wi-fi and bluetooth, in location/scanning, and usage info, in about phone, still heats up and reboots , if I use the phone after 5 minutes reboots, cpu-z detects temps from 45 to 65 without running apps, battery is on 37 degrees, I have to cool it in cold water(hey its winter and -13 degrees outside) but still takes some time to reach under 30, in about 2 minutes reaches 27
tomorrow I will wipe everything from recovery and flash again with flashtool
but...
I dunno what to do if it doesn't work, I'm thinking to throw it to garbage, very disappointed by this phone
while I writhed above text, the phone was charging and rebooting and rebooting and rebooting .............
update
got mad and wiped everything, flashed Lollipop 26.1.A.3.111, didn't want to boot, flashed TWRP recovery, made factory reset from recovery, booted, still heats up from 56 to 62, and got 2 reboots
but... after some minutes after second reboot something happened, temp dropped under 50 degrees from 39 to 46, still warm but no reboots ( cross fingers to stay like that ) but Big cluster is staying to 960 MHz and doesn't want to drop lower only goes up from time to time, Little cluster works normal ( watching cpu-z for about half hour ) for now works, still a bit warm but not too hot
no root for now
on Marshmallow 26.3.A.1.33 temps jumped up and down too fast in one second from 55 to 59 and back to 58 and up to 61 and reboot without cpu or gpu usage , some times gone over 70, flashed an wiped and flashed Marshmallow and nothing
wiped and flashed Lollipop 26.1.A.3.111 and thought it will do same but it got back working "normal" I hope, dunno what to think
after Marshmallow update I rooted by flshing boot.img don't remember witch su version and by mistake I updated all apps in Playstore but managed to repair it by flashing another boot.img and doing an clean up from settings in su app, all apps managed to get right su rights, and a bunch of su checkers from Playstore detected that su is present in the right place sys bin xbin vendor bin etc but phone started to reboot and really heated up
hello......
my phone died............ so farewell Sony and M4Aqua, actually I don't know if it's Sony fault, Qualcom is to blame for crappy soc, it bootloops over and over again and heats up like hell
flashed all stock roms I found and nothing
I can't get into recovery
Bro, Flash stock rom with Flashtool, with selected "USER_DATA", and "APPS_LOG", and after flash wait 20-25 minutes to boot
Absolutely same thing with me. I flashed all stock roms that I found and still stuck in bootloop. The only one that boot normaly is CM13 but WiFi, bluetooth and camera not working at all.
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Have you performed a factory reset? (It will delete all your data and apps)
rp-x1 said:
Have you performed a factory reset? (It will delete all your data and apps)
Click to expand...
Click to collapse
Yes, when the phone was new and the restarts were annoying. It fixed it for 1 day. The next day it was restarting again.
This would point to an app you've installed causing the issue. Factory reset again and install each app one by one until the restarts happen to find out which.
SteveTM said:
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Click to expand...
Click to collapse
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
cmstew said:
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Click to expand...
Click to collapse
Will try it when I'll have time for it, thanks for the help!