Bricked-Kernel v1.4r1 killed my screen - HTC Sensation
Hi Guys not trying to scare anyone couldnt post in developers section, so brought it out here.
Was running RevolutionHD 4.1.5 and wanted to use the 2-way phone recorder.
so installed Bricked-Kernel v1.4r1 installed the radio and cleared dalvik cache and installed system tuner pro so I could underclock 50%.
I noticed it was getting very hot right bottom side under sd microSD card and the screw at right bottom was 70c plus. So I am leaning towards graphics chip being over clocked to far and damaging the connector.
The screen faded to black so i turned it off pulled battery let it cool down and tried a reboot.
System boots and buttons are responsive, no screen , backlights are there.
heat build up is quick and really hot.
Also just connecting the battery, it lights up and starts generating heat.
but still can be booted.
I did under clock and set to boot but did not try to undervolt and set to boot.
Not angry or blaming anyone --->> show-p1984
just putting it out there as a report kinda thing.
DuratecPaul said:
Hi Guys not trying to scare anyone couldnt post in developers section, so brought it out here.
Was running RevolutionHD 4.1.5 and wanted to use the 2-way phone recorder.
so installed Bricked-Kernel v1.4r1 installed the radio and cleared dalvik cache and installed system tuner pro so I could underclock 50%.
I noticed it was getting very hot right bottom side under sd microSD card and the screw at right bottom was 70c plus. So I am leaning towards graphics chip being over clocked to far and damaging the connector.
The screen faded to black so i turned it off pulled battery let it cool down and tried a reboot.
System boots and buttons are responsive, no screen , backlights are there.
heat build up is quick and really hot.
Also just connecting the battery, it lights up and starts generating heat.
but still can be booted.
I did under clock and set to boot but did not try to undervolt and set to boot.
Not angry or blaming anyone --->> show-p1984
just putting it out there as a report kinda thing.
Click to expand...
Click to collapse
Sorry, I doubt it's the kernel. Sometimes things go wrong when installing software. Something went wrong.
Less likely, but still possible, hardware issue. Things do break sometimes.
Can you boot to recovery or bootloader? Does screen work in recovery? Do you know/use ADB? What happens when you're connected via ADB?
Hope you can sort this out.
P.
Try to enter bootloader. From there You will see if your phone is really damaged. You can also flash stock firmware from there, even blind. It will not be hard. I don't think that kernel is Your LCD killer, so try flashing stock and send it to warranty repair.
Sent from my HTC Sensation Z710e using Tapatalk
DuratecPaul said:
Hi Guys not trying to scare anyone couldnt post in developers section, so brought it out here.
Was running RevolutionHD 4.1.5 and wanted to use the 2-way phone recorder.
so installed Bricked-Kernel v1.4r1 installed the radio and cleared dalvik cache and installed system tuner pro so I could underclock 50%.
I noticed it was getting very hot right bottom side under sd microSD card and the screw at right bottom was 70c plus. So I am leaning towards graphics chip being over clocked to far and damaging the connector.
The screen faded to black so i turned it off pulled battery let it cool down and tried a reboot.
System boots and buttons are responsive, no screen , backlights are there.
heat build up is quick and really hot.
Also just connecting the battery, it lights up and starts generating heat.
but still can be booted.
I did under clock and set to boot but did not try to undervolt and set to boot.
Not angry or blaming anyone --->> show-p1984
just putting it out there as a report kinda thing.
Click to expand...
Click to collapse
1st Question: Why would you want to underclock by 50% !?!?
2nd Question: What clock speed did you set it at?
3rd Question: Was the Kernel running fine at the default clock speed?
I haven't used system tuner myself - but if i'm not mistaken you can also set the cpu voltages? Did you change anything there OR maybe you had to change the voltage and didn't?
It could also simply be a hardware failure waiting to happen. I had the same problem with my first sensation. After I moved from ARHD 3.5.2 to 3.6.0 my phone died when I was playing a game. This was due to a slightly faulty graphics chip. I use to have random restarts when I was on stock ROM but never thought about why it happened until my phone died.
My phone has been fixed by HTC and is all good now
Yeah I Have tried to boot to recovery, But its like hitting baseballs blindfolded.
as for ADB Ive got it and used it be4, but havent tried this option yet, Nor do I know all the commands I need to use... good thing search is here 8)
1st Question: Why would you want to underclock by 50% !?!?
2x 780000 is plenty fast enough helps with the battery and theres not many programs I use that needs more than that speed atm
2nd Question: What clock speed did you set it at?
I had it set to low 34.6mhz and to a high of 96mhz ondemand gov.
3rd Question: Was the Kernel running fine at the default clock speed?
yes but was warm ...nothing abnormal tho
I haven't used system tuner myself
I did the cpu clock, tested for half a day.
then set it to boot. was fine.
I set the voltages lower ran them for other half of day, but never set them to boot.
It could also simply be a hardware failure waiting to happen. I had the same problem with my first sensation. After I moved from ARHD 3.5.2 to 3.6.0 my phone died when I was playing a game. This was due to a slightly faulty graphics chip. I use to have random restarts when I was on stock ROM but never thought about why it happened until my phone died.
Yes Ive had the gaming/App crashes on stock kernal too
My phone has been fixed by HTC and is all good now
Yeah Im considering doing a DIY screen replacement, but Im thinking this wont cure it.
And then you get to sort out that nasty lag with the digitiser after doing it
DuratecPaul said:
2nd Question: What clock speed did you set it at?
I had it set to low 34.6mhz and to a high of 96mhz ondemand gov.
Click to expand...
Click to collapse
what kind of clocks are these, are you serious?
RussianBear said:
what kind of clocks are these, are you serious?
Click to expand...
Click to collapse
+1
either its a typo or
surprised the phone even worked at these clocks.
just to be clear. if you boot into recovery (with fully powered off, holding vol- and power button) nothing appears on screen ?
RussianBear said:
what kind of clocks are these, are you serious?
Click to expand...
Click to collapse
Um, minimum clock on most kernels is 192MHz or thereabouts.
If you were really clocked as low as claimed (though I don't see how), I see why phone would blow up.
P.
Sent from my Sensation using Tapatalk
PaulGiz said:
Um, minimum clock on most kernels is 192MHz or thereabouts.
If you were really clocked as low as claimed (though I don't see how), I see why phone would blow up.
P.
Sent from my Sensation using Tapatalk
Click to expand...
Click to collapse
He said his max was 96mhz....you do realise no android phone can run at that max speed? esp a Sense 3 based Sensation. You need at least 400mhz peak freq to be able to use the phone without lag.
but yes that wont cause the screen it go off so not the problem.
PaulGiz said:
Um, minimum clock on most kernels is 192MHz or thereabouts.
If you were really clocked as low as claimed (though I don't see how), I see why phone would blow up.
P.
Sent from my Sensation using Tapatalk
Click to expand...
Click to collapse
Nah, his phone just hasn't finished booting up yet. It takes a few hours at that speed.
aww dang ... yeah was a typo
was 360 and 920mhz.
but still is fried unfortunately and generating heat....
hmm gonna have to use my gal s2 till this gets fixed
I had something similar with bricked kernel. Installed the one before his latest, phone booted ok but got really hot very quickly, it smelt like a burnt out scalextric car . Quickly pulled the battery and restored my backup. Luckily mine still works fine.
Sent from my HTC Sensation Z710e using XDA App
good luck bro
---------- Post added at 12:17 AM ---------- Previous post was at 12:16 AM ----------
good luck bro..don mess it up
I wouldn't be so quick to deny this as the kernel's fault. I mean, the odds are low, but it is possible. Plus, there is a reason kernel devs, ROM devs, and mod devs always write up a disclaimer, sometimes humorously, stating that it's not their fault if anything happens to the phone. Kernels are direct interaction with the hardware, I've sent bad code to microprocessors before only to have them literally crack open with that nasty, burning component smell.
Some examples that took about 3 minutes to find.
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
Click to expand...
Click to collapse
Disclaimer:
You are flashing this at a risk. I am not responsible for any bricked devices! Thanks!
Click to expand...
Click to collapse
DuratecPaul said:
installed the radio and cleared dalvik cache and installed system tuner pro
.
Click to expand...
Click to collapse
Ever check the md5 & sha1?? If you installed a corrupt zip, then bummer, you f'd your phone.
Try pushing a ruu from adb.
Sent from my Bricked Energy Sensation.
yes checksum's were checked shar's were shar'ed.
cache's cleared and superwiped
I still maintain bricked kernel was the culprit, but I am not blaming but myself.
Just an update to this, the problem still exists but I can plug my hdmi dongle in and see and use the OS (guess that proves I didn't uc/undervolt too much), altho I cant use it to get to recovery.
Im a nub when it comes to ADB, but can use most commands now 8).
its definately graphics chip burn. that 1 corner gets to 80c + within 5mins. which leaves me with no time to flash.
Ive pulled it apart and going to replace the bottom board from here www.parts4repair.com
other than that I picked up a evo3d gsm for cheap and am now playing with that.
There is an easy way to keep it cool. Take cover off, plug in usb, put the phone in the condom. Immerse in water with ice, but make sure condom "neck" is above water. Flash. Boast to people about water cooled sensation. If flashing different Rom/kernel works-profit
Sent from my HTC Sensation Z710e using XDA App
Oh, BTW, you don't need 5 mins to flash kernel.
Sent from my HTC Sensation Z710e using XDA App
Related
[Q] Shut down problem -> Doubt about returning to HTC
Hello, Recently I've had many problems with the Sensation. It shuts down randomly. I searched in many forums, wiped all, changed rooms, tryed new kernels, radios, and nothing worked. If I look a log of the battery, you can see peaks of 0mA. I just bought a new battery (Anker), hoping that it's the battery, but some issues (it shuts down more often if I have some apks like Gmail (official) installed) make me think it's not a battery problem. So (if the new battery does not work), I want to send it to HTC, but first I will need to do S-ON, with it's a little dangerous. My questions are: -Anything I can have forgotten about the shut downs? -They can fins my phone have been rooted? (I will not do a S-On if they can find I rooted my phone) Thank you
Going back to S-ON is not dangerous at all, and if you're sending it back to HTC they'll know if it is S-OFF Once you're back to 100% stock there's no way they'll be able to see if it's rooted as they won't even think to look
For me it worked to format my sd card. I had also random shut downs when i used it and when it was a sleep. might not be the solution for as you wiped everthing, but might help someone else
Make sure the cpu isnt going to low (194mhz) set minumum to 384mhz
bonesy said: Make sure the cpu isnt going to low (194mhz) set minumum to 384mhz Click to expand... Click to collapse Interesting. Are you sure ? I'll give it a try, maybe it will work
Yea mine does the same, Also using Fauxcock and having different screen off profiles seems to set the cpu speed to screen off profile on wake
[Q] Screen Corruption
Hi. Today, when I unlocked the screen, I got something like this (see attachements). Is this a software problem or is it the gpu failing? I didn't even touch the transormer, it was on my desk all night, and in the morning when I wanted to use it.. you can see what happened. It looks like it was displaying only 256 colors. Should I send it back to asus or is it fixable? help
Juist flash another rom and see what happens.
If it was overclocked that may have done it and if it was recently droped or bumped it could be the digitizer cable is out of place
mrevankyle said: If it was overclocked that may have done it and if it was recently droped or bumped it could be the digitizer cable is out of place Click to expand... Click to collapse I don't remember bumping it or shaking it like crazy, but this thing happens even in recovery mode and during reboot, so it's gotta be hardware. Now I remember having similiar problem years ago, with an old CRT monitor and faulty VGA cable, so maybe the cable is really out of place. It's crazy how sensitive this hardware is. edit: it was overclocked to 1.3 ghz, but not when when the screen was locked. And I remember clearly it was ok when I was locking it. Can this still be a reason?
I saw this once or twice a long time ago when using kernels which overclocked the GPU and RAM...
a.mcdear said: I saw this once or twice a long time ago when using kernels which overclocked the GPU and RAM... Click to expand... Click to collapse will getting back to stock kernel/rom fix this issue? or is the damage permanent?
Looks similar to the pics of the cable being loose problem. The thread is probably buried...try finding it and I bet that the pics you find are similar to yours.
yes it was the cable problem. I hit the back of the tablet a few times and the screen went back to normal. Wondering how long it will last before it happens again.
[Q] Phone reboots when hot (not bootloop)
Hi, My Sensation (the 1.2ghz model, stock battery) has started rebooting after heavy use. I'm not sure if the phone did this when it was completely stock as I didn't use it very much before flashing. I flashed to stock ICS first. After playing Temple Run for a solid 2-3 hours the phone gets very hot, then it randomly reboots. (and my damn stats were gone). I let the phone cool and played more yesterday, again after 2-3 hours it rebooted again.. I wondered if it was the ROM so I super wiped and installed Android HD Revolution 6.5 - exactly the same problem. I tried plugging my phone in to my PC and looking at the logcat but it wasn't rebooting when I did get it in. It was setting CPU time or something fairly frequently - is this normal? Has anyone else had this issue? My PC used to do this all the time when it was overheating so I think the same problem is occurring here. Is it my phone? I bought the phone from a friend and it would be a pain in the ass to get it sent off on his insurance (especially with this problem, they might turn it on, find no issue and fire it back) EDIT: Just to confirm - it's not only when Temple Run is on. After it rebooted the first time, I scrolled through the apps whilst it was still fairly hot and it rebooted again so its not specifically Temple Run which is making it reboot.
You can try flash sebastiankernel and see if there are any overclock, underclock, overvolt or undervolt problems. But most likely you have a defect model, send it back and describe to problem to them so they will know how to fix it.
if cellphone temp goes over 50 it automatically turn off , there is no defect in ur phone but this happens get cpu master add powr eidget on screen n keep a look out n u b fine hit thnx if i helped Sent from my HTC Sensation Z710e using xda premium
Thanks for the replies. I've actually been using a temperature widget. The hottest I've seen it record is 43c. Also, after it turned off it was this temp aswell so I don't think its quite getting to 50c. So no one else has this problem after heavily playing 3D games? (or at all?) Is there anything else I can try to fix this?
[Q] can overclocking burn Nexus S beyond repair?
Hi guys, Sorry to bring you my phone troubles but It seems I have smoked my phone and you are the best source of knowledge I know of. I have had a nexus s (gsm) [i9020a] model for a year and recently rooted it. Then I installed system tuner and overclocked it. It was fine until I got an OTA update (to 4.1.2 ) two days ago. I should have known not to accept the update after a root but I did. Since then I keep getting freeze phone into the X graphics you usually get when you boot up. So today I further juiced it up using System |Tuner, uping values I had no ideas about Soon there after I got another crash, and lock and this time when i pulled the battery and replaced it, nothing comes up. Dark! . No power or any sign of activity with or without charger. Have I totally ruined the phone? Anything I can do? Thanks for your help .
You can if you use too high oc with high voltage, for a longer period, like in months. I wouldnt say that caused your phone to die but it could be your phone couldnt take the oc at all. Sent from SpeedMachine i9023
Overclocking will rarely break any hardware. Increasing the voltage though is playing with fire. Nevertheless, I believe what killed your Nexus S is the famous battery pull. You wouldn't be the only person that has killed their phone doing this, you can look around the forums...
[Q] Tablet shutdown just after boot.
Hello, I've registered especially for that problem, so what happens is after I get the cool NVIDIA bootscreen, I instantly come up with a message saying "Turn off" or some kind of shutdown message. Before you ask, yes, my bootloader is unlocked, and it was rooted until I do a factory reset, since it was doing this auto shutdown, I also currently have CWM Recovery, which is quite a nice recovery ! Here's a list of things I tried and that didn't do anything: Try to cancel the shutdown somehow Booting the tablet multiple times Factory Reset Also, I can't seem to use it with my computer since, well, that damn shutdown on startup. So what can I do ? I still have access to the recovery. Could it work to give it some ADB in the tablet's face ? I really need this beautiful piece of hardware to play vidyagames. And also, the battery is full, and working properly (I can kind of see the battery on top, it's probably at 80% or something.) I'd also like to point out that it suddenly started doing that. And there's also a SD card in it. And also, when I access the fastboot, well, I can hear it on my computer, guess it's a good sign ! And yes, it's the one with Wi-Fi, so if I have to use a ROM, I don't think I would have much choice. Also Android version is Lollipop. EDIT: Nevermind for the ADB, it requires my tablet to be on, at least I can still use CWM Recovery and fastboot ! yay EDIT 2: The message is: Power Off Shutting Down...
WavingStory said: Hello, I've registered especially for that problem, so what happens is after I get the cool NVIDIA bootscreen, I instantly come up with a message saying "Turn off" or some kind of shutdown message. Before you ask, yes, my bootloader is unlocked, and it was rooted until I do a factory reset, since it was doing this auto shutdown, I also currently have CWM Recovery, which is quite a nice recovery ! Here's a list of things I tried and that didn't do anything: Try to cancel the shutdown somehow Booting the tablet multiple times Factory Reset Also, I can't seem to use it with my computer since, well, that damn shutdown on startup. So what can I do ? I still have access to the recovery. Could it work to give it some ADB in the tablet's face ? I really need this beautiful piece of hardware to play vidyagames. And also, the battery is full, and working properly (I can kind of see the battery on top, it's probably at 80% or something.) I'd also like to point out that it suddenly started doing that. And there's also a SD card in it. And also, when I access the fastboot, well, I can hear it on my computer, guess it's a good sign ! And yes, it's the one with Wi-Fi, so if I have to use a ROM, I don't think I would have much choice. Also Android version is Lollipop. EDIT: Nevermind for the ADB, it requires my tablet to be on, at least I can still use CWM Recovery and fastboot ! yay EDIT 2: The message is: Power Off Shutting Down... Click to expand... Click to collapse Since you have access to CWM, I'd recommend you do what I recommended another user http://forum.xda-developers.com/showpost.php?p=58946728&postcount=2
NaminatoR1254jaime.sier said: Since you have access to CWM, I'd recommend you do what I recommended another user http://forum.xda-developers.com/showpost.php?p=58946728&postcount=2 Click to expand... Click to collapse So... do I have to reflash a new recovery image and put a new OTA ? Or just a new OTA ? EDIT: Of course not.. I got it, I have to flash a new OTA with CWM right ? So.. it means that my current OTA is corrupted or something. Nice... but how do I flash it ? EDIT 2: Ok found how, I sideloaded the OTA, which is quite a new thinig to me.. I never ever did modifications to my tablet without a tutorial, it was upgrading... so I guess that's good... And it didn't do jack s***. It stills power off... weird.
WavingStory said: So... do I have to reflash a new recovery image and put a new OTA ? Or just a new OTA ? EDIT: Of course not.. I got it, I have to flash a new OTA with CWM right ? So.. it means that my current OTA is corrupted or something. Nice... but how do I flash it ? EDIT 2: Ok found how, I sideloaded the OTA, which is quite a new thinig to me.. I never ever did modifications to my tablet without a tutorial, it was upgrading... so I guess that's good... And it didn't do jack s***. It stills power off... weird. Click to expand... Click to collapse Very weird. Must be defective. Did you try reflashing stock images via fastboot? (I've never done it, fyi)
NaminatoR1254jaime.sier said: Since you have access to CWM, I'd recommend you do what I recommended another user http://forum.xda-developers.com/showpost.php?p=58946728&postcount=2 Click to expand... Click to collapse Well, I don't think it works by fastboot, I don't even think the tablet is bricked, could it be on the hardware level ?
WavingStory said: Well, I don't think it works by fastboot, I don't even think the tablet is bricked, could it be on the hardware level ? Click to expand... Click to collapse I have the same problem. I've tried flashing the recovery 2.1 files, sideloaded the 2.2 ota, etc. The last thing i'm going to try is wiping the system with trwp then installing the 2.1 recovery again. -that did not work. I have initiated the RMA process.
Anyone has some instruction how to safely open a NVIDIA Shield Tablet ? I woud love to check if some hardware went off so I can rebuild it. EDIT: Wait, it can't be hardware... It just can't ! Why ? Well... simply because right now i'm in TWRP recovery, everything is working exept... oh wait... CPU temperature is going crazy. 429491929 C... yep... I don't think that's right.
Ok, sorry for the double post, I know it's really bad... BUT I THINK I KNOW WHY ! Bad thing, it's the CPU thermometer, it has gone crazy. So, I installed you know, that TWRP recovery, and I checked the CPU temperature. Wanna know what it is ? It's hotter than plasma, or lava, or anything. Heck even the big bang. CPU: 429491899 C. That's right, that much, so... any idea how to fix the CPU Thermometer ? I knew it was something with the hardware. My theory is that it is not connect properly to the CPU. Since everything on TWRP is working... TOO FAST COOL! like all the apps I had on that tablet. So here, problem half-solved. The tablet shuts down because of the CPU temperature, to prevent it from overheat ! EDIT: Finally fixed it ! ;v; Like I said, it was the CPU Temperature, since it kinda fell off my bed now that I remember, what is the CPU thermometer ? Well, it's a small bar near your stylus slot. Inside the thing, also, when you insert you stylus you insert it directly into the hardware part, next to that CPU Temperature thing, maybe that caused it, but well, basically, I opened my tablet with a cool little trick, basically, I took the back of my stylus and I forced softly on the tablet in the stylus slot. And what happened ? It opened a little ! So, what I did is slowy remove the plastic around to to not cause any crack of damage and it worked perfectly ! I saw that little CPU thermometer going off and what I did is basically push it back into where it was ! Also, the wi fi antenna is next to the camera, it's pretty small for your information ! But yeah, I putted back the plastic case after that and booted my tablet... and IT WORKED!!! It booted perfectly ! So: It was not the ROM or the OTA, it was the auto shutdown to prevent overheat. Also, it seems like recovery mode and fastboot don't care about temperature... so they won't be shutting down ! I'd like to thank the creators of that TWRP Recovery, it's the thing that helped me find out that it was the CPU Temperature ! It's also the first time of my life I touched to some hardware. And i'm really proud of myself even for such a small thing ! Hope it helps someone in the futur ! Thanks for trying to help me !
WavingStory said: Ok, sorry for the double post, I know it's really bad... BUT I THINK I KNOW WHY ! Bad thing, it's the CPU thermometer, it has gone crazy. So, I installed you know, that TWRP recovery, and I checked the CPU temperature. Wanna know what it is ? It's hotter than plasma, or lava, or anything. Heck even the big bang. CPU: 429491899 C. That's right, that much, so... any idea how to fix the CPU Thermometer ? I knew it was something with the hardware. My theory is that it is not connect properly to the CPU. Since everything on TWRP is working... TOO FAST COOL! like all the apps I had on that tablet. So here, problem half-solved. The tablet shuts down because of the CPU temperature, to prevent it from overheat ! EDIT: Finally fixed it ! ;v; Like I said, it was the CPU Temperature, since it kinda fell off my bed now that I remember, what is the CPU thermometer ? Well, it's a small bar near your stylus slot. Inside the thing, also, when you insert you stylus you insert it directly into the hardware part, next to that CPU Temperature thing, maybe that caused it, but well, basically, I opened my tablet with a cool little trick, basically, I took the back of my stylus and I forced softly on the tablet in the stylus slot. And what happened ? It opened a little ! So, what I did is slowy remove the plastic around to to not cause any crack of damage and it worked perfectly ! I saw that little CPU thermometer going off and what I did is basically push it back into where it was ! Also, the wi fi antenna is next to the camera, it's pretty small for your information ! But yeah, I putted back the plastic case after that and booted my tablet... and IT WORKED!!! It booted perfectly ! So: It was not the ROM or the OTA, it was the auto shutdown to prevent overheat. Also, it seems like recovery mode and fastboot don't care about temperature... so they won't be shutting down ! I'd like to thank the creators of that TWRP Recovery, it's the thing that helped me find out that it was the CPU Temperature ! It's also the first time of my life I touched to some hardware. And i'm really proud of myself even for such a small thing ! Hope it helps someone in the futur ! Thanks for trying to help me ! Click to expand... Click to collapse Glad you fixed it!!! So thats the little thing bar right to the stylus... You didn't take any photos of it at all right? I remember seeing on YT a video of someone opening their tablet
NaminatoR1254jaime.sier said: Glad you fixed it!!! So thats the little thing bar right to the stylus... You didn't take any photos of it at all right? I remember seeing on YT a video of someone opening their tablet Click to expand... Click to collapse Well, I would have taken a picture, but I have nothing to capture pictures with... so.. yeah. Else I would have taken photos, it's pretty safe to open it by the way.
If the "bar" you're referring to is the one just off center on the right side, then that's where a Sim card is installed on the LTE model... Sent from my SHIELD Tablet using XDA Free mobile app
NaminatoR1254jaime.sier said: Glad you fixed it!!! So thats the little thing bar right to the stylus... You didn't take any photos of it at all right? I remember seeing on YT a video of someone opening their tablet Click to expand... Click to collapse An Droid said: If the "bar" you're referring to is the one just off center on the right side, then that's where a Sim card is installed on the LTE model... Sent from my SHIELD Tablet using XDA Free mobile app Click to expand... Click to collapse Nope, it's a sort of small bar near the camera, just on the top of it, it's made of some steel I think !
2 questions I'm having the same problem. I already have opened the cover based on how you described it. 1. I can't find the thermometer and what kind of fix should I do with it? 2. How did you install TWRP when the device couldn't even boot properly. Thanks ---------- Post added at 06:39 PM ---------- Previous post was at 06:01 PM ---------- I blindedly pushed some components back (dangerous) and decided to put back the cover. I rebooted and yeah, it booted properly! However,after a few minutes it auto shut down again. So I guess the theory that it's about the CPu thermometer might be true. The question is, where is it really located and what should be it's position? Thanks.
Finally Fixed! After several sessions of tinkering the unknown components of the hardware, I finally decided to take it to the next level. So I carefully removed the electrical tape covering the perimeter of the battery. Lo and behold - there's a white wire that is loose and I've determined its correct connection through its length. Since I didnt have a soldering iron and I'm too afraid to use it should I have one, I used brute force connection via electric tape. I peeled more skin to secure conductivity. Apparently, it's the connection to the CPu thermometer. When it is unlinked, it should register as weirdly high value, triggering hard reset. During the boot up and initialization, the firmware takes note of the value. After studying the behaviour of the problem, apparently the firmware in the chip also occasionally checks the temperature esp when an app is launched. This explained why I couldn't boot at the beginning or if ever boot was successful, antutu causes shut down. So as a solution, I made sure the contact between that freaking white wire and the solder placement on the board MUST be secure. I'm using my fixed shield tablet to post here Btw. Apparently it has become faster. Antutu is 55,000. But charging the battery seems slow. I must have accidentally messed up something with the battery. Boy I love my Shield tablet!
Thanks many many times!! It fall down of the carpet and later that evening I noticed that it s off. thanks the happenstance that TWRP shows the CPU Temperature it was fast located. so I was able to search for.. and finally xda did it again.. Thanks all of you
Same problem Well, my tablet got the same problem Here some pictures, can you tell me where is the temeprature sensor?
Faced the same problem and I fixed it as suggested by soldiering the white wire behind the tape. Look at the picture to know where it is located. First attachment with the tape on. Second image with the tape off and after soldiering the white wire to the board. I hope that helps.
SalehCoder said: Faced the same problem and I fixed it as suggested by soldiering the white wire behind the tape. Look at the picture to know where it is located. First attachment with the tape on. Second image with the tape off and after soldiering the white wire to the board. I hope that helps. Click to expand... Click to collapse wow ... excellent post. this also solved my restart problem. thank you very much. interesting side-fact: this only affected stock images. all alternative roms (bliss, etc. ...) started fine ...
I've got this exact problem as well but even after soldering this white wire, it keeps shutting down.. Edit: after some more attempts, I got a new temp: 92c. But I still got shut downs.. So I managed to switch it back to that weird 42516516161 etc temperature and now it wont turn off with the Custom Rom Bliss Pop.
I had the same issue. The device started to shut down by itself, sometimes right after boot. Luckily I stumbled to this thread while googling for the issue. Then I verified the problem by installing cpu-z and watching the temperature while waiting for the device to power off. Indeed, just before powering off the sensor jumped to -46 C. So with your help I found the culprit and soldered it back. No shutdowns ever since!