Hello All,
Well, today I finally managed to unbrick mt KFHD after about a month or so of using it as a paperweight...Over the course of the last month I made four attempts at making the factory cable myself. Having absolutely zero prior experience and armed with the cheapest piece of crap soldering iron money can buy, my first 3 attempts ended in useless melted messes. Luckily this morning I decided to make one last attempt and I was finally able to pull it off.
Anyways, once I was finally able to get into fastboot mode, I went ahead and just flashed the stock rom and was thrilled to watch my kindle successfully boot up for the first time in over a month. Having finally managed to unbrick my device, I proceeded to do my victory dance around the house. Unfortunately as soon as I sat back down I realized that I had celebrated a little bit too soon. No matter what I tried, I could not get the wifi to turn on. There wasn't even a MAC address listed.
After much searching and many attempts to fix the problem, I cam accross a forum post from someone saying that they had the same issue, and they were only able to fix it after flashing a custom rom...something to do with the mmc0 block or something I dont quite remember. Since without wifi the KFHD is pretty much useless, I figured I had might as well give it a shot. It was a bit of a process, but I was able to flash TWRP and CM11, and now my wifi and basically everything else is working again.
My apologies for the somewhat long back story, but I didn't want to leave out potentially relevant information. The issue I am facing now is this: when logcat is open, anytime I touch the screen I am getting about 40 instances of this error --
06-01 22:40:25.830 E/TI OMAP PowerHAL(535): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
This happens regardless of whether or not I actually have the governor set to interactive. I've done quite a bit of searching to no avail...
Here is some of my system information:
Kernel: 3.0.72+ [email protected] #1
CM Version: 11-20140601-NIGHTLY-tate
Android: 4.2.2
I used No-Frills CPU App to see if changing the governor had any effect, and this information came from the About CPU function of that app..
- file: /sys/devices/system/cpu/cpufreq/interactive/boost:
0
- file: /sys/devices/system/cpu/cpufreq/interactive/boostpulse:
sh: <stdin>[1]: cat: /sys/devices/system/cpu/cpufreq/interactive/boostpulse: Permission denied
- file: /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration:
80000
Once again, sorry for the long post..anyone who has taken the time to read it, I thank you very much. If anyone has any ideas/suggestions, or even if you could just help me by telling me a little more about what the problem is, it would be very very much appreciated. I haven't had much luck searching :/
I wouldn't worry about it, I see this on Maromi's kernel when I mess with the frequency, I think it is a kernel device that doesn't show up, the file that calls for that sys path probably just needs taking out of the kernel.
Sent from my LG-P769 using Tapatalk
Related
This turns out to be a crash bug in Android see last post
While i was researching ways to maximize the battery life on my captivate I came across a setting in the tasker wiki that would help me log the life of my battery.
I had already set up juice defender and other ways to let tasker turn on and off battery draining settings like GPS and WIFI and thought that this would be a good way to track on a day to day basis how much life i was getting out of each battery.
Here is what i found. The day after i set up the tasker profile i began watching results. Around 11 am the next day my phone began to loop in reboot. it just went right to my bootanimation and then home screen, boot animation, home screen....
I thought nothing of this as i flash roms often and was beta testing some stuff at the time. I proceeded to flash stock ---> flash custom rom. what i i had to repeat this process a few times because it continued to reboot. After a few flashes i became stable. the following day at around 11 am my phone began to boot loop again. this time i flashed stock and left it there only to begin looping again. i turned the phone off for a while and then flashed stock--> custom rom. It looped again.
this time i brought the phone to a device support center and had it replaced.
with the new phone i use no settings or backups from TiBu except for a few apps like handcent, takser, angry birds and a couple other games. at this point i thought that my old phone was just worn out from the many flashes. Two days after getting the new phone and installing all apps (except the few apps like tasker) my phone began to boot loop at 11AM. this time i flashed to stock and it began to boot loop again. I repartition and flashed again and it became stable. Until the next day at 11am when it began to boot loop again.
i returned to the device support center with a stock phone in boot loop.
this time I have not used a setting from tibu backup but have returned all aps to almost the same as before (the best i can by memory)
day one i Ran stockfor a day.
day two i ran the same custom rom/kernel combo.
day 3 i ran everything with the apps set up and used the same battery that was in from the last time it looped.
The only Thing that was the same from both phone that looped what isn't in my newest phone is that tasker setting.
I am almost 99% sure that this setting did something to the file system at low levels which is unrepairable by flashing.
Is this a bug? i do not know, I reproduced it twice but do not think that a device support center will replace a third device for me.
If anyone is/has ran this profile with no problems than I can let this go as unsolvable.
If anyone is willing to test this setting and can reproduce the bug then i think we will have something to take to Samsung regarding a system bug that is unrepairable at user level.
here is the link for the profile
i followed this setup exactly as stated except here Write File: File "Batterlog.txt" i used "BattLog.txt" im not sure if it makes a difference but if you are going to set this up please try it using BattLog.txt
here are the steps
Code:
1. Make up a new profile, context: Power: Battery changed, priority normal -> done.
3. Add task Alert: Flash: Text "%BATT % %MEMF", If checked "%BATT !~ %BATTPREV" -> done
4. Add task File: Write File: File "BattLog.txt", Text "%DATE %TIME %BATT", Append checked, If checked "%BATT !~ %BATTPREV" -> done
5. Add task Variable: Variable Set: Name "%BATTPREV", To: "%BATT"
I guess everyone must think that i indeed did find a bug in the filesystem because not one person has come forward to try this out. If I am wrong at least you have yourself a very nice way to track you battery usage.
I read over your task and don't think I missed anything unusual (ie. weird infinite loop condition that would make it constantly write to the file).
I'm not about to try it, of course, given what you have experienced. You might try the limit repeats or cooldown period settings for the profile in case that really is the issue.
I can tell you I've been using the file writing actions for a clipboard history task I wrote and have not had your issue, even when I screwed up a condition and it was infinitely writing my clipboard contents to a file for a couple of minutes straight.
I'm running an i896 captivate with a js3 rom fwiw. Hope you get it figured out.
Sent from my SAMSUNG-SGH-I897 using XDA App
tiuk said:
I read over your task and don't think I missed anything unusual (ie. weird infinite loop condition that would make it constantly write to the file).
I'm not about to try it, of course, given what you have experienced. You might try the limit repeats or cooldown period settings for the profile in case that really is the issue.
I can tell you I've been using the file writing actions for a clipboard history task I wrote and have not had your issue, even when I screwed up a condition and it was infinitely writing my clipboard contents to a file for a couple of minutes straight.
I'm running an i896 captivate with a js3 rom fwiw. Hope you get it figured out.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I am not attempting to recreate at this time. I will be when I have a replacement phone. If this is indeed a fs bug i can imagine anyone who does not want their phone aymore could use this setting and go into infinite loop and get a replacement. The does not require root and can be used on any firmware. Samsung would have to react.
so after running the new phone for a week i got the boot loops again today at 11:08am
i am trying to see if it is battery related as I DID NOT have the tasker setting in place.
here is the log if anyone wants to try and help solve this. i have other batteries i will be trying this week. (everyday until i fix it) the problem is though that if the filesystem is damaged than testing on this phone is useless.
http://dl.dropbox.com/u/17699865/android_report1298308267139.zip
I solved the bug bug cant fix it.
follow the link to my report.
anyone able to reproduce?
i have been able to send the message to myself but it always arrives in 2 part.
goo.gl/wCrlp
Hi!
I got my kindle fire hd today (german edition) and tried to root my device. So i watched the guide on *** and read several articles and forum threads to be prepared rooting the kindle fire. Ok first of all: i might have damaged the screen, although i have no clue how this happened. One of the corner led doesn't work properly anymore. The effect is like heavy clouding on led tvs.
I followed exactly the tutorial on ****. After the first step, the processor starts to heat up and the tablet slows a bit down. After the second reboot the tablet gets really hot and significantly slows down. The screen starts to flicker and the tablet needs about 10 seconds to execute a command. After a reset to factory defaults everything works like charm except the clouding. I changed the usb port, reinstalled the android sdk and even used qemuroot. Nothing works. I am going to send my kindle back and buy another one, but i wont try to root it without solving this problem. Does anyone have an idea??
/edit as a new member i can't post any urls. The first *** is reverendkyle.c*m and the second is an article on redmondpie
Sounds like you received a defective device. Send it back.
Maybe the "German Edition" versions were those that didn't make the first round of quality control checks.
soupmagnet said:
Sounds like you received a defective device. Send it back.
Maybe the "German Edition" versions were those that didn't make the first round of quality control checks.
Click to expand...
Click to collapse
I only mentioned it because my firmware version isn't 7.21 (sorry my fault) but 7.20. Never heard of it, maybe the eu version somehow differs from the us version.
noskill123 said:
I only mentioned it because my firmware version isn't 7.21 (sorry my fault) but 7.20. Never heard of it, maybe the eu version somehow differs from the us version.
Click to expand...
Click to collapse
7.20 is on the 32GB that I just received today.
soupmagnet said:
Sounds like you received a defective device. Send it back..
Click to expand...
Click to collapse
yup, it's the right advice. don't try to force any root, send the device back instead and have a new try with the next one.
The root will work for both 7.2.0 and 7.2.1, barring any anomalies with your specific device. I would use the automated root found on this forum when you try rooting next time, since it'll eliminate any possible mistakes (not saying you made any). Either way, everyone else is definitely right in saying you got a defective device. Luckily, Amazon's pretty good about replacements when you're under warranty. My own device's CPU was running so hot, it smelled like things were melting. Got it replaced with no fuss, and no extra charges.
noskill123 said:
Hi!
I got my kindle fire hd today (german edition) and tried to root my device. So i watched the guide on *** and read several articles and forum threads to be prepared rooting the kindle fire. Ok first of all: i might have damaged the screen, although i have no clue how this happened. One of the corner led doesn't work properly anymore. The effect is like heavy clouding on led tvs.
I followed exactly the tutorial on ****. After the first step, the processor starts to heat up and the tablet slows a bit down. After the second reboot the tablet gets really hot and significantly slows down. The screen starts to flicker and the tablet needs about 10 seconds to execute a command. After a reset to factory defaults everything works like charm except the clouding. I changed the usb port, reinstalled the android sdk and even used qemuroot. Nothing works. I am going to send my kindle back and buy another one, but i wont try to root it without solving this problem. Does anyone have an idea??
/edit as a new member i can't post any urls. The first *** is reverendkyle.c*m and the second is an article on redmondpie
Click to expand...
Click to collapse
That’s exactly what happen to me about 10 days ago my KFHD
Get hot and speed is unbelievable slow down but I do manage to reset to factory setting
http://forum.xda-developers.com/showthread.php?p=32866304#post32866304
But finally I manage to root my KFHD and switch off upgrade option because I don’t want
The same problem occurs to me again.
My mistake at the first time is I mix up the method using manually method by reverendkjr
And on half way using script giving by sparkym3, so on the second attempt I only use
manually method by reverendkjr doing exactly what he is done and I get my KFHD rooted
I hope this will help you
NB
Even I uncheck automatic update they still updated my KFHD now I am with 7.21
and became unroot yes will start allover again.:fingers-crossed:
I had whatever, that updated to 7.3 as soon as I turned it on. Rooted fine with KF First Aide. Installed ES File Explorer, Google Play, etc. All was well. Then I read a post here how hard it was to copy/paste with ES File Explorer. I was joking about it with my husband and showing him how easy it was and copied random file... literally just randomly long pressed a file to show him the options, picked copy, and then went to another directory and *meant* to point to but touched paste instead... it was one of the Google Play files.
Kindle fire hd 7" immediately started freaking out. A mac address type error flashing so quick I couldn't do anything else. It was the same low letters and numbers you'd get with a mac address but said error and just an OK button which did nothing when you manage to tap in while flashing. Restarted, thinking if I was lucky Google Play just would't work... got the red triangle and neither option helped. So I ordered one of SkOrPn's cables which works flawlessly and boots right into fastboot. Yay for SkOrPn! Not so ya for me... (not their fault!).
It shows up as "Tate-PVT-08". I've tried every variation of driver I can find. Uninstalling all old things I can find, complete with the command line command to show ghost hubs/devices and what not and removing them and shut down/start up fresh too... no joy. Also removing and restarting between each driver try... neither of the Amazon drivers work for fastboot for me. I've tried so many things at this point my brain is fried.
So I'm hoping someone can help direct me how to fix this. . I won it in an online giveaway, so I'm not out anything, but it'd sure be nice to use it! As messed up as the Kindle crap is I'd be pissed if I bought it... but I'm majorly spoiled on Sony (Ericsson) and their "ya, play with it, screw it up, we don't care, here's how to fix it online just plug it in"... even before they had the online thing they'd let you send it back (and paid shipping both ways for it!) would reflash firmware and send it back with paper ticket that said "No problems found" lol... even on a device you actually bricked (wouldn't turn on... not the cute "brick"="I screwed it up but it's fixable" that people use now).
Any help or advice would be greatly appreciated. Especially if you could steer me to drivers that work for 2nd generation HD 7 inch in fastboot on Windows 8. Thanks for reading if nothing else!
Try The SoupKit found here.
This is a Kinology HD using XDA Premium
Swap cables. Boot with the factory cable then switch to a normal one.
Thanks for the reply, but I've been doing that. Great advice for anyone who doesn't know though!
You couldn't have damaged anything by just copying a file unless either:
You cut the file
OR
You overwrote a system file
OR
You filled up your system partition.
If you still need help, I might be able to do some researching.
Sent From my Kindle Fire HD running CM10.1
I'd say your fast boot driver didn't install right mine showed up like that and I had to keep playing with drivers to get it to work
Sent from my Amazon Kindle Fire HD running CM 10.1
Same Problem
I'm having the same problem! If you fixed it please let me know!
FIXED!!
It's fixed! You have to use KindleFireAide. Just follow all of the directions and it's perfect.:laugh::laugh::laugh::good::good::good:
Shawnsch said:
I'd say your fast boot driver didn't install right mine showed up like that and I had to keep playing with drivers to get it to work
Sent from my Amazon Kindle Fire HD running CM 10.1
Click to expand...
Click to collapse
Thanks, I was hoping there was a better answer than just keep uninstalling/reinstalling various drivers in various ways til it works lol.
I've got a pc I haven't plugged it in to I'll try this weekend, if that doesn't work I'll do the Linux Soup Kit.
Deviantelf said:
Thanks, I was hoping there was a better answer than just keep uninstalling/reinstalling various drivers in various ways til it works lol.
I've got a pc I haven't plugged it in to I'll try this weekend, if that doesn't work I'll do the Linux Soup Kit.
Click to expand...
Click to collapse
Use Kindle Fire Aide. It comes with all of the drivers.
Geckodudes said:
Use Kindle Fire Aide. It comes with all of the drivers.
Click to expand...
Click to collapse
That was my first thing to try. Unfortunately one of them says stopped by user (preferred one) and the alternate won't install, gets to the end of installing and says didn't install, do manually... which has the same results. I'm getting the same results on another pc. Fun times lol.
Edit... I give up, it's Linux time. Will report back later.
My husband did the Soup kit (correct version, followed directions, etc.) with it for me while I was at work today on an pc he put Linux on (so nothing phone/tablet/adb/driver has ever touched it for anything). He's more savvy with Linux, I haven't used it much since the 90s while he regularly has it as a dual boot on his main pc. He used Ubuntu, followed the Soupkit directions and still no Linux love either.
I'm pretty much down to just sending it back, worst case they send it back and tell me I'm screwed. Both of us are so spoiled on Sony (me) and Google/Nexus (him)... that this some things only works sometimes and just keep bashing your head into the wall and something you already tried three times will work thing is out of our frame of reference (which is what it took to get it rooted lol). I've already spent more time trying to fix the stupid thing for something that shouldn't have even caused an issue than I've spent on both my Sonys combined... even though I've borked both more than once... crazy.
My only advice ... buy a real tablet lol. Luckily I won this so I'm not out anything if Amazon won't swap it... but I really like the 7" size for book reading.
I'll fix it for you...
Deviantelf said:
My husband did the Soup kit (correct version, followed directions, etc.) with it for me while I was at work today on an pc he put Linux on (so nothing phone/tablet/adb/driver has ever touched it for anything). He's more savvy with Linux, I haven't used it much since the 90s while he regularly has it as a dual boot on his main pc. He used Ubuntu, followed the Soupkit directions and still no Linux love either.
I'm pretty much down to just sending it back, worst case they send it back and tell me I'm screwed. Both of us are so spoiled on Sony (me) and Google/Nexus (him)... that this some things only works sometimes and just keep bashing your head into the wall and something you already tried three times will work thing is out of our frame of reference (which is what it took to get it rooted lol). I've already spent more time trying to fix the stupid thing for something that shouldn't have even caused an issue than I've spent on both my Sonys combined... even though I've borked both more than once... crazy.
My only advice ... buy a real tablet lol. Luckily I won this so I'm not out anything if Amazon won't swap it... but I really like the 7" size for book reading.
Click to expand...
Click to collapse
If you're gonna send it anywhere, if you pay for shipping I could try to fix it. No guarantees, of course.
If you are on Windows 8 to install kfhd drivers you must advanced boot with unsigned drivers install mode active
Sent from my KFTT using xda premium
KindleFireGuy said:
If you are on Windows 8 to install kfhd drivers you must advanced boot with unsigned drivers install mode active
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
Ya did all that fun stuff, repeatedly with various drivers with all the 20 steps in between to remove others, lol.
Husband spent quite some time with Linux and SoupKit to no avail also. He could get his phone to work (making sure he had all the rules and steps correct), but it never would do anything with the tablet.
I gave up and called Amazon late Monday. They had me turn it on and verify the red triangle screen then sent me a new one that arrived today. Take the new one out of the box and put the old one in they said. They paid shipping both ways. If they complain I'll tell them send me the old and I'll send the new one back lol (at my expense). If they want to make the thing such a mess to deal with what do they expect? They know there's a whole group of people that won't live with the crappy launcher mess they have .
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
The same problem, HELP US
Elgari said:
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
Click to expand...
Click to collapse
I HAVE THE SAME PROBLEM, I DON´T KNOW WHAT´S HAPPEN. Can you fix it?
i have heard occasionally around on the forums of peoples power buttons and such doing this after a while, if that is the case you might be able to test for it but its kinda complicated. Is it sleeping or shutting off? If it's shutting off it would be interesting to see why but you'd have to have either a logcat running on the pc the entire time, a cat of the kmsg, or something of that nature running and turn off while its doing that, then you can find the root of the problem. If it won't do it while plugged in, cm has a way to wirelessly do adb commands. I think hashcode said in his sources theres a test binary for the buttons to see if they are doing anything, but i'd have to figure out how to cross compile it by itself if thats the case, unless its precompiled.
Yes, cassualy I fix it last week. I open the Kindle, looking the wires and conectors and close again. And voila . . . fixed!
Enviado desde mi Amazon Kindle Fire HD mediante Tapatalk
tldr; the thing with the oven appears to have worked, although you'd have to be stupid, desperate, or both to try it.
Much loved Galaxy Note 4 SM-N910F started to fail with freezes, reboots and so on. Looks like a phone dying of eMMC failure, according to the bulk of articles on the specific symptoms.
Happily, I'd replaced it (with a Note 10 - lovely phone, but not as revolutionary-lovely as the Note 4 was when it was new), and had had six years of happy use out of the thing. I could bin it with my head held high.
Might have a go at recovering it, though.
Attempts to factory reset failed, resulting in boot to download mode "Firmware Update Encountered An Issue" scary screen... I see. This could be a fun challenge before I bin it then!
Odin flash of Stock ROM fell over repeatedly with various fails - often with 'mmc read' and 'could not do normal boot' scary screens
Various versions and vintages of Odin all produced similar results
Un-brick seemed to work, in as much as I could then flash TWRP (https://forum.xda-developers.com/note-4/help/samsung-galaxy-note4-sm-n910f-unbrick-t3552826)
TWRP flashing of any rom seemed to fail and fall over - generally 5-10% (guess) into the process.
Now getting bolder, tried re-partitioning, various PIT files, NAND erase, and all the forbidden things. The errors kept coming, and my 'unbrick' microSD was earning its keep.
The thing is, I really liked this phone - and I wanted it to try newer ROMs on and so forth, so I resisted the urge to chuck it in the bin. That, and finding things like using TWRP terminal mode to re-format /system and /data in different partition types, and then back to ext4, seemed to improve matters - if only temporarily - all suggested that there might be life in the old girl yet.
A couple of my searches came across articles like this and this, that suggested that the issue might have to do with failing solder joints rather than the eMMC itself and ... well then they talked about putting your phone in the oven, and I dismissed them as madness.
I mean, if putting your phone in the oven would 'reflow' dodgy solder, it would re-flow ALL the solder in the phone, right? Makes no sense. Bloody stupid.
Not going to fall for some obvious troll hoax.
So I put my phone in a 100 deg C oven for 5 mins. Took it out, and let it cool to room temperature slowly over a couple of hours.
Now
Odin can flash a whole stock ROM with success
TWRP can flash a whole non-stock ROM with success
Odin can re-flash a whole stoc... oh. Failed at around 80%. Poo.
TWRP managed a reflash, though!
Odin managed a whole stock reflash, again!
Setting up the flashed phone, though, results in freezes and boot loops. Damnit.
Another day of frustrated mucking about, hovering the thing over the bin.
OK, one more go. This time 120 deg C for 6 minutes.
This time
First and every subsequent re-flash, in Odin and TWRP, works fine.
Odin'd it back to stock, then wipe and factory reset. All fine.
Reconfig process passes without incident.
Google Play updating itself and ALL THE APPS works fine.
Setting up accounts, streaming Youtube for hours, playing games... all fine. Much more stable than it'd been in a while.
It's been a week, now, without incident.
So I thought I'd mention it.
But I still think you'd need to be an idiot to bake your phone in the hope that it'd do *anything* other than make things much worse, right?
charleshking said:
But I still think you'd need to be an idiot to bake your phone in the hope that it'd do *anything* other than make things much worse, right?
Click to expand...
Click to collapse
Maybe.
There's an app called Wake Lock - PowerManager - I've installed on my son's 910F since a month or so and the phone still works.
It'll slightly take it's toll on battery, but hey you save some $ for the next phone.
@charleshking: Reflowing def does work, I know a guy that had to do it 3 times within 6 months to fix his gaming laptop. But it's only meant to be a temp fix, sooner or later the oven thing won't work (failed on him after the 4th try).
The Wake Lock manager app just holds open a wake lock so the phone never enters deep sleep/doze mode, which in the case of an EMMC failing phone can cause it to not wake up.
Last year I had a Note 4 T-Mobile N910T which had a failing EMMC, it had most of the issues you mentioned. But eventually it died, it caught on fire while I was charging it. I now have an N910T which is working with no issues, bought new on eBay almost a year ago.