[Q] Mediapad 7 - Strange battery behavior (no real battery life question) - Huawei MediaPad, T-Mobile SpringBoard

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.

Related

[Q] Non-stop crashing and rebooting

Hello, guys. First of all, I'd like to apologize in advance for my bad english. If there is any part of the message that isn't very clear, please inform me so I can correct it.
Here's the deal: I've been using for some time the Jelly Bean Ressuction Remix Rom from Westcrip.
Since about a month and a half (since version 3.9, I believe), I've been getting some weird and random signal drops. Back then, I had to manually reboot my phone so the data connection would come back. At the time I thought it was because the rom was still a nightly build, not very stable, so I coped with it.
This problem has worsen considerably since one or two weeks ago: those "signal drops" have become more and more regular. And following the signal drop, the screen would flicker a little and then the phone would automatically turn off. When I turn the phone back on, the battery is almost depleted, even tho it was full right before the crash. Again I'd blame the RR from Westcrip (by the time I was using the version 3.1.0). When version 3.1.2 came out, I did a clean installation (wipe data/factory reset/format system partition/wipe cache and dalvik, etc), even changed the kernels (used both Dorimanx and Siyah), a lot of modems, and still got this same problem: signal drop (usually when the phone is under a relative amount of stress, like playing Angry Birds, browsing the web, and even while using whatsapp!!!) followed by the phone turning itself off.
I then thought: what the hell, the problem has to be with the rom, not my phone. Then, I tried installing different roms (Paranoid Android and Slim Bean), and still got the same results. If anything, the phone is rebooting even more often now than before. I can't use it for 15 straight minutes and I get that problem,
Since this has happened with all these different roms I dont believe its related specifically to any of those.
Another strange thing: this "signal drop" followed by the rebooting only happens when the phone is disconnected from any power source and being actively used by me. If I'm recharging it, for example, the phone wont reboot at all. Also, if it is over my desk but I'm not using it, the phone also wont reboot. However, if I take it out from the power source and starting using it, I'll get another reboot in about 5-10 minutes of use.
I searched the forum and didnt find anyone with a similar problem... have any of you guys seem this happen before? I'm beggining to think that my phone is gonna die on me anyday now.
Regards!!
Daimao1984 said:
Hello, guys. First of all, I'd like to apologize in advance for my bad english. If there is any part of the message that isn't very clear, please inform me so I can correct it.
Here's the deal: I've been using for some time the Jelly Bean Ressuction Remix Rom from Westcrip.
Since about a month and a half (since version 3.9, I believe), I've been getting some weird and random signal drops. Back then, I had to manually reboot my phone so the data connection would come back. At the time I thought it was because the rom was still a nightly build, not very stable, so I coped with it.
This problem has worsen considerably since one or two weeks ago: those "signal drops" have become more and more regular. And following the signal drop, the screen would flicker a little and then the phone would automatically turn off. When I turn the phone back on, the battery is almost depleted, even tho it was full right before the crash. Again I'd blame the RR from Westcrip (by the time I was using the version 3.1.0). When version 3.1.2 came out, I did a clean installation (wipe data/factory reset/format system partition/wipe cache and dalvik, etc), even changed the kernels (used both Dorimanx and Siyah), a lot of modems, and still got this same problem: signal drop (usually when the phone is under a relative amount of stress, like playing Angry Birds, browsing the web, and even while using whatsapp!!!) followed by the phone turning itself off.
I then thought: what the hell, the problem has to be with the rom, not my phone. Then, I tried installing different roms (Paranoid Android and Slim Bean), and still got the same results. If anything, the phone is rebooting even more often now than before. I can't use it for 15 straight minutes and I get that problem,
Since this has happened with all these different roms I dont believe its related specifically to any of those.
Another strange thing: this "signal drop" followed by the rebooting only happens when the phone is disconnected from any power source and being actively used by me. If I'm recharging it, for example, the phone wont reboot at all. Also, if it is over my desk but I'm not using it, the phone also wont reboot. However, if I take it out from the power source and starting using it, I'll get another reboot in about 5-10 minutes of use.
I searched the forum and didnt find anyone with a similar problem... have any of you guys seem this happen before? I'm beggining to think that my phone is gonna die on me anyday now.
Regards!!
Click to expand...
Click to collapse
Hey,
pls backup ur apps and then do this:
0) Do a nandroid Backup via recovery
-- backup and restore
-- backup to internal (or external) sd card
1) Download Rom
2) Put it on internal sd card
3) Go into recovery mode
4) DO A FULL WIPE!! (U won't loose ur backup on sd card [but u can copy it to PC, too, if u want])
-- wipe data/ factory reset
-- wipe cahe partition
-- advanced > wipe dalvik cache
-- mount and storage > format data/system/cache
5) Then flash Rom
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
6) Then flash Gapps
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
7) Recovery > wipe cache partition
8) Recovery > advanced > wipe dalvik cache
9) Then flash Dorimanx
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
6) Reboot and u r done!
Links:
ROM: U should have already the newest one, or at least u know, where u find it.
Dorimanx Kernel
Gapps
Much success,
CHEERS
Hi, thanks a lot fot the help.
I did all the steps above and I'm still getting the same results...
Another thing to notice is that yhe phone gets really hot for apparently no reason at all (like booting up, running aLogcat and other minor apps), and when that happens, I usually get a signal drop (if the phone is plugged in it wont reboot, if its not, it will reboot).
Is there anything else I can try?
Updating: I've been restoring my old nandroid backups for the whole day to see if the problem had anything to do with Jelly Bean. Well, I've gone back to the old ICS days and every version of it had the same random and constant rebooting. Even versions that didn't have any problem before.
I'm beggining to think I have a hardware failure of some sort. Do any of you guys know what could cause this kind of hardware failure? Since the phone has been getting hot for no apparent reason, it seems to me its a problem with the SGS2 cooler. Is that even possible?
OK so I have this problem but only when using my backup battery. (Not official). When It gets around 30% it begins to make my screen flicker and loose signal and just die.
So maybe you haven't got an original (official) battery in your s2?
Sent from my Galaxy SII
I dont think I have an unofficial battery. Its the same battery that came with the phone (bought from Amazon), and also, mine says Samsung on the back. Dunno if its enough to assume its official. Is there another way to check if my battery is official?
Daimao1984 said:
Hi, thanks a lot fot the help.
I did all the steps above and I'm still getting the same results...
Another thing to notice is that yhe phone gets really hot for apparently no reason at all (like booting up, running aLogcat and other minor apps), and when that happens, I usually get a signal drop (if the phone is plugged in it wont reboot, if its not, it will reboot).
Is there anything else I can try?
Click to expand...
Click to collapse
Do u check if u r using the correct Roms for u phone? (i9100, i9100p, i9100g,etc)
CHEERS
Send from my SGSII-i9100, running RootBox nightly with Dorimanx Kernel.
Hi I am also facing the same problem. Mobile is getting hot near the camera lens.

[Q] Random reboot then data wipe

Hi there,
So I was on Skype to my friend on my i9300, running stock 4.3, rooted, with yank555 kernel and with PhilZ 5 recovery. All these modifications were done about four weeks ago and the phone has served me perfectly well until today.
The flashing Samsung logo that comes up just before the phone boots appeared and the keys stayed lit, when nothing happened for a minute, I held the power button until it reset. Next, the phone took a good two or three minutes to boot and seemed to have forgotten all the information I inputted into it. I still had most of my apps but all the sign in information was gone and all the Google Apps had to reinstall themselves.
There seems to be no cause for the break down, and I don't have a recent backup as I haven't planned to flash anything until 4.4 is officially released. Does anybody know what could have caused this or if there is a way to recover my data?
Cheers.
Unplanned system shut down can partition corruption, reasons for it can be various -battery voltage suddenly dipped, kernel panic etc.
Data on your internal sd should still be there, as on the external sd. Anything else will be gone as it sounds like your data got wiped.

[Q] [Help Needed! !] Battery Drain and Logo On Boot Screen displays Android is upgra

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.

Encryption unsuccessful random! Need help. Galaxy S3 CM 12.1

Sup guys, so i just had a really strange problem that popped out randomly, i was watching a youtube video and i had to help a person quickly and when i came back just a minute later i saw my phone showing encryption unsuccessfull when i pressed the power button to turn my screen on. Well it said to factory reset my phone, i don't store any important data on my phone anyways so i just went for it, and it restarted went to my TWRP recovery and tried factory reseting it, to no success. It basically failed to access /data/ and other directories and i can't see any files in them through recovery. And so i can't even factory reset it, i can't install a ROM cause the partition is corrupt i assume. How can i "unbrick" this? I was running the good old Temaseks CM 12.1 ROM, has been working fine for a looong time. My PC recognizes the phone but i can't access any data, it just shows that it's connected, odin doesn't recognize it.
Can somebody help me please ? I use my phone alot and it's really important.

Phone Switching off and Restarting only after Wipe

Recently I've encountered a problem on my Redmi Note 3 Pro 3 gb ram 32 gb. I've been using custom ROMs and Kernels for a while. One day my phone switched off after getting warm. It switched on after some time. Then I tried Wiping Cache and Dalvik through TWRP and it didn't work as I had the same problem over again. Then I tried flashing another ROM through TWRP and I couldn't complete it as my phone restarted while I tried to flash a new ROM. Then I tried copying my files from phone to USB OTG and that too failed as phone continued to restart. The only option I had is using Fastboot. I downloaded the latest Global ROM MIUI 10 and flashed new ROM using MiFlash. Phone booted perfectly and after I synced my Mi account and Google account the phone switched off again and when I tried to restart it boots up till lockscreen and switches off Immediately.
Again I booted up Xiaomi Recovery as TWRP was now gone and Wiped the ROM and it booted up normally, after few tries I finally didn't sync Mi or Google account and Didn't install anything on phone as it might switch off again. I'm pretty sure it'll switch off again. Other than that I think the device is okay as I'm posting this thread from the same phone. It couldn't be a ROM issue as you can see I've tried different MIUI ROMs even the Custom MIUI ones. What could be the reason for this behavior? I hope someone could help me as it is my main device and this issue is driving me nuts.
Bibin Shree said:
Recently I've encountered a problem on my Redmi Note 3 Pro 3 gb ram 32 gb. I've been using custom ROMs and Kernels for a while. One day my phone switched off after getting warm. It switched on after some time. Then I tried Wiping Cache and Dalvik through TWRP and it didn't work as I had the same problem over again. Then I tried flashing another ROM through TWRP and I couldn't complete it as my phone restarted while I tried to flash a new ROM. Then I tried copying my files from phone to USB OTG and that too failed as phone continued to restart. The only option I had is using Fastboot. I downloaded the latest Global ROM MIUI 10 and flashed new ROM using MiFlash. Phone booted perfectly and after I synced my Mi account and Google account the phone switched off again and when I tried to restart it boots up till lockscreen and switches off Immediately.
Again I booted up Xiaomi Recovery as TWRP was now gone and Wiped the ROM and it booted up normally, after few tries I finally didn't sync Mi or Google account and Didn't install anything on phone as it might switch off again. I'm pretty sure it'll switch off again. Other than that I think the device is okay as I'm posting this thread from the same phone. It couldn't be a ROM issue as you can see I've tried different MIUI ROMs even the Custom MIUI ones. What could be the reason for this behavior? I hope someone could help me as it is my main device and this issue is driving me nuts.
Click to expand...
Click to collapse
Make sure u selected clean flash while flashing fastboot rom including cleaning user storage and internal sd.
Dont encrypt.
Are u rooting ? If rooting use magisk only.... not supersu.
Remove sd card, sim card . clean it. Put back.
If still cant solve....open back cover. Remove both battery connecter and connect again. Charging board flex connector on both end and connect again. Sometimes carbon can create problem.
naik2902 said:
Make sure u selected clean flash while flashing fastboot rom including cleaning user storage and internal sd.
Dont encrypt.
Are u rooting ? If rooting use magisk only.... not supersu.
Remove sd card, sim card . clean it. Put back.
If still cant solve....open back cover. Remove both battery connecter and connect again. Charging board flex connector on both end and connect again. Sometimes carbon can create problem.
Click to expand...
Click to collapse
I've Selected Flash all While Fastboot flashing....Yet I've
Same issue, Boots till lockscreen then screen goes black....Then when I use Mi Recovery to Wipe all it boots up and I can use the phone. But if I try to Open a few apps or try to Sync, phone switches off again. Any way I'll try the cable fix and report here.

Categories

Resources