[Q] White Screen - General Questions and Answers

Hello I'm having some serious trouble with my android device. Whenever I turn it on it will just show a white screen. I can put the phone to sleep and when I press the power button again, the screen is still white. I can hear my text ringtone etc but the phone is useless with the white screen. Factory reset won't help either.
Any ideas?

what lead to the white screen?
external reason - water, dropping, general impact... ect?
i don't think it would be software since you did a factory wipe and since all the other software bits seem to be working.
i would suspect that the flex cable sending data to your lcd has come loose. either from the board or the lcd. hopefully its on the board side. thats easier to fix.. depending on how comfortable you are taking something apart.

I rooted my phone and was trying to make it run faster by deleting files using Titanium Backup. I deleted some essential Google file so now i cant access the market. I don't think this is the cause of the white screen though. Every now and then the phone will boot up correctly without the white screen so i don't think its a software issue.
How would I re-attach the flex cable?

You could still try to reflash via Odin.

Ok thanks I'll look into that. Any other ideas?

flash it
Boot into recovery, usually a power button volume button combo but varies depending on device. Then wipe/reflash Rom.

Should I use RSD?
I have a motorola spice

And how do I reflash rom?

alsterr said:
And how do I reflash rom?
Click to expand...
Click to collapse
Via Odin, I am pretty sure, that there is some tutorial around here.

I found odin tutorials but none of them have a Motorola phone. They only used Samsung phones. Would it work on a Motorola phone?

Ok I think I found a way but I need the sbf file for the Canadian Motorola Spice. I have a friend with the stock rom. anyone know how to extract it?

via Adb
---------- Post added at 04:05 PM ---------- Previous post was at 04:04 PM ----------
Sadly, I dont remember the commands.

OK so I'm going to take it apart tomorrow to see if it is a hardware issue.
What's the deal with flashing a custom rom? What limitations are there on the rom I can use?

I figured out I need to install the application G apps to access the market again. how would i do that?

alsterr said:
I figured out I need to install the application G apps to access the market again. how would i do that?
Click to expand...
Click to collapse
Download the gapps package for android 2.1. it should be a .zip. Then go into CWM and flash

sorry for the really late reply.. for some reason i only just now got notified...
rsd lite is what i used to flash my electrify. which is a Motorola. i would assume it would be the same program from you as well.
as to reattaching a cable or reseating a cable its all a matter of how comfortable you are with taking things apart. if your really nervous about it.. i wouldn't suggest doing it at all. you are going to be dealing with a lot of very small bits... well maybe not so many but there will be a few.
the tools you will need are jewelers screwdrivers and maybe some small torque bits.

wolficus said:
sorry for the really late reply.. for some reason i only just now got notified...
rsd lite is what i used to flash my electrify. which is a Motorola. i would assume it would be the same program from you as well.
as to reattaching a cable or reseating a cable its all a matter of how comfortable you are with taking things apart. if your really nervous about it.. i wouldn't suggest doing it at all. you are going to be dealing with a lot of very small bits... well maybe not so many but there will be a few.
the tools you will need are jewelers screwdrivers and maybe some small torque bits.
Click to expand...
Click to collapse
Hey guys. Sorry I didn't check back in. I took my phone apart and saw that half the flex cable was ripped. My phone is a slider and the edge of the keyboard would cut a little bit of the cable each time. I replaced the cable and Motorola took care of giving me the stock rom. Guess I got lucky.
Thanks to all you guys for your help

Related

[Q] Lg Vortex problem help please?

I bought a lg vortex and it worked great i rooted it with z4root no problems at all
that was intill i did a flashclockrecovery and it turned off and now is stuck at lg boot logo!
i have no clue how to fix it i called lg they said to send it in so the can reflash the rom software to the phone and i was thinking i could do that my self any one know how to do this?
any advise would be great!
How can you get it to recovery mode? so there for i can install the software with the lg updater tool to the phone.?
(if these makes a diffrence it the same exact button layout of optimus "t" an "s"
buttons just look diffrent !)
I also performed the same steps, and am now stuck at boot screen. The hard and soft reset methods do not work. Phone does not connect to pc, I have even tried an LG flashing application...but still could not detect the phone via usb. Any advice?
I have found one solution and fixed my phone which btw was the only solution to this mess :/
Little Help
I am having the EXACT same issues that you described. Could you please tell me how you got it fixed. I've tried everything I can think of.
Here is the thing, the LG Vortex has no support for hacking right now. You can only root the device.....no overclocking, roms ect. as of yet. So before I sadly explain how I fixed the issue....do not make the same mistake twice. Z4 root does work, both perm root and temp root. Anything beyond that, sorry. I bricked my phone just like you. Sadly you are screwed buddy. I came up with the bright idea of totally frying my phone so that Verizon does not know the root process had taken place (void warranty). I cut a dc adapter up stuck both ends on battery terminals for phone....after battery was out and flipped the powerstrip on and bam...fried phone. The low voltage like that is safe so dont worry. I would advise using a powerstrip instead of physically plugging the ac adapter in. Take phone back and say it suddenly stopped charging. SAY NOTHING ELSE, NO APPS FROM MARKET, NO PC HOOKUP OR ANY DATA PLACED ON PHONE. If you do by chance get shocked from doing this.....stop your crying its 12volts.
by the way, dont leave any root programs on your sd card...as verizon will want all the original items back for a phone exchange. Also ya know make sure you did indeed fry it.....I double checked and first time it didnt do it. If you put batt in and phone does not come on at all....then it worked. Just make sure those wires are not touching eachother so much as seperate connecters where the battery touches ya know. If you just touch wires together, powerstrip will pop/lil sparks on wires or you may pop a breaker. But them little dc adapters I do not think can pop a breaker. Just get an electricity flow through the phone and it will fry.
Doodie
I really appreciate you taking the time to give me a heads up on that stuff. I've been afraid that it was bricked. Just to clarify, what do you mean by dc adapter? I've been having nightmares of verizon finding out that i tried to root it from seeing something on that internal memory, so I'm really glad you went into that. So, I know how to remove everything from my sd card and/or reformat it if need be, but i'm confused about exactly how to use the "dc adapter" to baby buzz this thing into amnesia.
Thanks alot for the help,
T
I placed the wires from the DC adapter on the the little terminals where the battery touches. I wouldnt recommend doing this beyond the 30 day warranty period fyi.

Nexus 5 Screen will not light up

Hey guys I've had my N5 for almost a year now but it seems to have gone kaput on me recently...
On Monday I was on a skype call, (just audio) when my phone suddenly restarted, I didn't pay much mind to it as that happened before and it would usually just cut back on, but this time, it restarted, and restarted and just didn't stop. That lead me to think its the power button being stuck so i checked it out and made sure its not being depressed and well yeah it wasn't. And soon after that the phones screen was sometimes on during the reboots and sometimes off. I knew it was rebooting because the N5 vibrates a bit when Google pops up on the loading screen in a certain way, but yeah now the screen doesn't light up at all, there's still vibrations and sounds like when I call or when I say Okay Google a few times, the LED will even light up during a call. I know the phone is "on and working" in the background but the screen doesn't light up and as such I can't touch it, any ideas and or advice friends?
bump de bump?
Possibly your backlight burnt out? Water damage?
if you are running cyanogenmod, you could be experiencing sod "sleep of death". thats when you know the phone is on and working, but the screen doesnt turn on. ive been reading lots of complaints about cm and the sod.
TheROMGuy said:
Possibly your backlight burnt out? Water damage?
Click to expand...
Click to collapse
As the phone kept rebooting it went from seeing everything, to seeing nothing but the back light to dark, so maybe? It was just by me on my desk too so I was doubtful about the water damage but I put it in the sealed rice bag for about 24 hours just in case but still no luck.
I actually am running cyanogenmod and whenever I do have a problem I always feel that its related to CM as the phone doesn't have any physical damage...maybe I should look into that, any other ideas friends?
P.S I am using the ElementalX Kernel and UNFORTUNATELY I turned on the FAST CHARGE USB option and that makes the phone play funny with the computer, if you guys have any advice as to how I could turn off that option please do let me know
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
I used this tool to try and remove anything that could be bothering my phone, software wise, and I'm not sure if it wiped away Kernels and Roms but thought you guys should know, my computer now recognizes the phone and I can see folders and such, which are now empty.
dynamo147 said:
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
I used this tool to try and remove anything that could be bothering my phone, software wise, and I'm not sure if it wiped away Kernels and Roms but thought you guys should know, my computer now recognizes the phone and I can see folders and such, which are now empty.
Click to expand...
Click to collapse
all it does is completely wipe your phone and install an older android version. flashing the factory img will do the same, except youll get the newest android version. don't use these tools, doing things the right way will be more beneficial to you. anyways, since cm is having issues, try a different rom, or just go stock.
simms22 said:
all it does is completely wipe your phone and install an older android version. flashing the factory img will do the same, except youll get the newest android version. don't use these tools, doing things the right way will be more beneficial to you. anyways, since cm is having issues, try a different rom, or just go stock.
Click to expand...
Click to collapse
Thats my problem though my screen is still untouchable or see able and it makes it hard to flash stuff since I can't properly use TWRP, and having the fast charge hack on my computer doesnt really sense im in USB Debug but I guesssss its off now though, but still no screen loving
dynamo147 said:
Thats my problem though my screen is still untouchable or see able and it makes it hard to flash stuff since I can't properly use TWRP, and having the fast charge hack on my computer doesnt really sense im in USB Debug but I guesssss its off now though, but still no screen loving
Click to expand...
Click to collapse
if still no screen, its probably physically damaged(hit or factory damage). is an exchange possible?
simms22 said:
if still no screen, its probably physically damaged(hit or factory damage). is an exchange possible?
Click to expand...
Click to collapse
Well i got mine through the Play Store and I did think about an RMA, I know there was that free screen replacement thing going on but the customer rep sounded like he had no idea what I was talking about. and I'm thinking its a flex cable issue as my phone hasn't incurred any damage from drops or bumps or anything since i make it a point to be stationary while using phone, but....where the sim card tray is, that "bridge" or thin piece on the bottom side toward the phone has split as a result of my bad sim card ejecting, but that was when i first obtained the phone, also there is another split, inside the phone there is a canopy above the charging port that is split but i still know that occurred long before this, and its not even an electrical piece along with the sim card bridge thing.
BUTTT yeah im afraid if I RMA they will use that as an excuse to charge me $400, even though I know it's not playing any sort of factor in my screen acting up....Is there a policy on that?
dynamo147 said:
Well i got mine through the Play Store and I did think about an RMA, I know there was that free screen replacement thing going on but the customer rep sounded like he had no idea what I was talking about. and I'm thinking its a flex cable issue as my phone hasn't incurred any damage from drops or bumps or anything since i make it a point to be stationary while using phone, but....where the sim card tray is, that "bridge" or thin piece on the bottom side toward the phone has split as a result of my bad sim card ejecting, but that was when i first obtained the phone, also there is another split, inside the phone there is a canopy above the charging port that is split but i still know that occurred long before this, and its not even an electrical piece along with the sim card bridge thing.
BUTTT yeah im afraid if I RMA they will use that as an excuse to charge me $400, even though I know it's not playing any sort of factor in my screen acting up....Is there a policy on that?
Click to expand...
Click to collapse
ive rma'ed before, google is really good about it. i sent my nexus 7 back with a custom recovery, rom, kernel.. and the thing going on with google and exchanging the n5 once without question, isnt about the screen, its for anything.
simms22 said:
ive rma'ed before, google is really good about it. i sent my nexus 7 back with a custom recovery, rom, kernel.. and the thing going on with google and exchanging the n5 once without question, isnt about the screen, its for anything.
Click to expand...
Click to collapse
I suppose I might as well shoot for it? Is there a way to decline paying for the device if they decide that I should pay?
dynamo147 said:
I suppose I might as well shoot for it? Is there a way to decline paying for the device if they decide that I should pay?
Click to expand...
Click to collapse
send back the rma? honestly, i dont know. i dont know anyone thats ever had to pay. unless its obvious that you did something, youll be fine.
So when you hold down the power button and the vol - for about 15 seconds the bootloader screen doesn't show up? If so, yeah try to RMA.
I will chat it up with one of the customer service peeps and see what they think then, and maybe even hopefully one will know about the replace anything deal
anactoraaron said:
So when you hold down the power button and the vol - for about 15 seconds the bootloader screen doesn't show up? If so, yeah try to RMA.
Click to expand...
Click to collapse
and yup Ik its in bootloader mode though because the computer beeps and tries installing drivers and what not and also because it does that single vibrate, but yeah the screen is still dark so I can't see my selections, I believe I can still actually make a selection though, just unable to see them
dynamo147 said:
and yup Ik its in bootloader mode though because the computer beeps and tries installing drivers and what not and also because it does that single vibrate, but yeah the screen is still dark so I can't see my selections, I believe I can still actually make a selection though, just unable to see them
Click to expand...
Click to collapse
Check to make sure you have the newest drivers (there's a sticky in the general section with all the useful info). If you bought it from the play store see if you can get an RMA - Google seems to have a good rep with this. It wouldn't hurt to flash a factory image to erase everything either before sending it off (privacy and whatnot). If you have the newest TWRP (2.8.0.1) if you boot into recovery and you should be able to access the internal storage without having to select anything (in case there's anything there not backed up). Boot to recovery is volume down twice and power I think.
anactoraaron said:
Check to make sure you have the newest drivers (there's a sticky in the general section with all the useful info). If you bought it from the play store see if you can get an RMA - Google seems to have a good rep with this. It wouldn't hurt to flash a factory image to erase everything either before sending it off (privacy and whatnot). If you have the newest TWRP (2.8.0.1) if you boot into recovery and you should be able to access the internal storage without having to select anything (in case there's anything there not backed up). Boot to recovery is volume down twice and power I think.
Click to expand...
Click to collapse
Well now that I used that tool I'm not sure if my recovery is still TWRP or if it's stock, it flashed a stock factory image I'm told, but that doesn't remove the Kernel and Recovery too does it? I wanna get it as stock as possible before I sent it out. At this point I believe it has a factory image but I can't say for sure about anything else
dynamo147 said:
Well now that I used that tool I'm not sure if my recovery is still TWRP or if it's stock, it flashed a stock factory image I'm told, but that doesn't remove the Kernel and Recovery too does it? I wanna get it as stock as possible before I sent it out. At this point I believe it has a factory image but I can't say for sure about anything else
Click to expand...
Click to collapse
See here http://forum.xda-developers.com/showthread.php?t=2513701.

[Q] XT925 killed during attempt of downgrade from OTA 4.4.2

Hello,
I've had recently broke my XT925 and have question if it’s possible to bring it back to life...
Well from the beginning... I've had glass smashed and during tearing screen from the glass I damaged it, so I've ordered new screen with glass and digitizer. When it arrived, after putting it all together it appears that screen doesn't respond on any touch. My friend read somewhere that it could be solved by flashing the phone again(now I don't know is it truth, and right now it feels like one of the smallest problem I have).
I flashed my Milestone 2 and Droid 4 before so I didn't suspect it be so troubling now.
Because my Motorola had been updated to 4.4.2 and I couldn't find firmware in that version I've decided to downgrade the version to 4.1.2. I found some video with how to modify XML file to be flashable. Unfortunately the video is in foreign to me language (Spanish I guess) and at the time I don't realize, that phone has to be unlocked to do that.
It, start to flash, but when it gets to "boot" it stop saying that it can't be downgraded. So right now My XT925 starts to AP Flash mod with text Flash Failure. I'm able to get to recovery mode and from there try to update phone but like in AP Flash it just don't want to flash Android 4.1.2.
Is there any way to bring it back to life?
I'm guessing that it should run if I could flash files for 4.4.2 but I don't know from where I can get them...
Please tell me do I have nice looking brick or there is a hope for my phone?
Phone is locked, has no other then stock tools installed, and it had system version 180.46.117.XT925.CCE-Retail.en.EU before I started to mess with it.
I tried flash it with 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC.xml. When it begin starting in AP Flash mode I have removed every line that cause stopping the process (technically everything except "partition", "tz", "boot" and "system" is loaded from 4.1.2) so now its very messy. Right now I don't know what I was hoping for. What's done is done, so now I can only hope that it can be fixed.
If its even fixable, there is no way to fix it without the stock kk fxz, unless you can get it unlocked using Moto's site.
Sent from my G3 Rockin Cyanogen
Thank you for your reply.
I'll try unlocking by web when I get home. I'm only hoping that it can be done without working properly touch screen, or buy connect keyboard via OTG. Otherwise I'm doomed...
Why the F would reflashing after changing the screen and/or digitizer magically bring back the touchscreen functionality to life ?
No touchscreen only means the digitizer was not installed properly, that's all. Open the phone again and check all flex cables and connection, they are really tricky to put back in connectors properly. (pro tip, use some very small pliers to manipulate flex cables and put them back in their connectors)
Unlocking does not require any touchscreen functionality though, it's just a matter of keyboard input from your computer. Just unlock, downgrade properly to say 4.1.2, and when you're done see if the touchscreen work. And when you find out it doesn't, tear the phone apart again and double-check all flex cables connectors on the motherboard
It works!! Thank you very much!!
At first I have problems to find the fastboot.exe in the downloaded SDK directory (for those who also have problems with finding that file it is in 'sdk\platform-tools' folder). The process of unlocking is very easy so I have no problem with that . After unlocking phone flash correctly.
CoinCoin88 said:
Why the F would reflashing after changing the screen and/or digitizer magically bring back the touchscreen functionality to life ?
No touchscreen only means the digitizer was not installed properly, that's all. Open the phone again and check all flex cables and connection, they are really tricky to put back in connectors properly. (pro tip, use some very small pliers to manipulate flex cables and put them back in their connectors)
Unlocking does not require any touchscreen functionality though, it's just a matter of keyboard input from your computer. Just unlock, downgrade properly to say 4.1.2, and when you're done see if the touchscreen work. And when you find out it doesn't, tear the phone apart again and double-check all flex cables connectors on the motherboard
Click to expand...
Click to collapse
Apparently when you have KitKat update it's necessary to flash phone again after replacing the screen and/or digitizer. After flashing digitizer is working properly. I didn't need to open the phone and correct any flex cables (there is only one common to the screen and digitizer so if that was wrongly connected probably I won't be seeing anything). To be honest I don't think that will work without opening the phone. I instinctively unlocked the phone and started to choose the language. Then I realized that I can do it. I'm really glad that the phone is working correctly.
Once again thank you very much for your help.
M_Kwiatkowski said:
It works!! Thank you very much!!
At first I have problems to find the fastboot.exe in the downloaded SDK directory (for those who also have problems with finding that file it is in 'sdk\platform-tools' folder). The process of unlocking is very easy so I have no problem with that . After unlocking phone flash correctly.
Apparently when you have KitKat update it's necessary to flash phone again after replacing the screen and/or digitizer. After flashing digitizer is working properly. I didn't need to open the phone and correct any flex cables (there is only one common to the screen and digitizer so if that was wrongly connected probably I won't be seeing anything). To be honest I don't think that will work without opening the phone. I instinctively unlocked the phone and started to choose the language. Then I realized that I can do it. I'm really glad that the phone is working correctly.
Once again thank you very much for your help.
Click to expand...
Click to collapse
Well, I'll be damned, it's the first time I hear of such behaviour, and i've ripped apart a long list of devices before my razr... Sometimes to replace the screen, sometimes to replace the battery, sometimes just for fun... and I've never seen that before.
(Although IIRC there are two flex cables going from the front assembly to the motherboard in the xt925 and not just one, but I don't remember which one is for what)
edit: OK just found out lcd and digitizer are glued together in most recent phones, including xt925, so there's probably only one flex cable for the whole assembly. They other one was probably for the led I guess...)
CoinCoin88 said:
Well, I'll be damned, it's the first time I hear of such behaviour, and i've ripped apart a long list of devices before my razr... Sometimes to replace the screen, sometimes to replace the battery, sometimes just for fun... and I've never seen that before.
(Although IIRC there are two flex cables going from the front assembly to the motherboard in the xt925 and not just one, but I don't remember which one is for what)
edit: OK just found out lcd and digitizer are glued together in most recent phones, including xt925, so there's probably only one flex cable for the whole assembly. They other one was probably for the led I guess...)
Click to expand...
Click to collapse
The second one is for front camera, speaker and light sensor. I don't count that one because is actually separate part from the screen witch is screwed to the front frame of the phone. To be clear I had problems with that cable and I had to put it few times before camera and sensor start work correctly. That is why I paid special attention to the good fitting of these cables to the motherboard. That was before I smashed software by trying downgrade locked phone so I was pretty sure that it was fitted correctly.
Now my Motorola still works fine. After replacing the screen it actually lived longer in one piece then when I bought it. I scratched the screen next day from purchase... then it fell of my hands few times(usually with the help of other people)... That is why I decided to change glass and front frame... and then during the peel-off old glass from screen I broke the screen... It all happened in period shorter than two months... I'm guessing this particular XT925 is very unlucky... or... it's just unlucky to have me as the owner...
I'm very careful with carrying it with me now, so I don't have to replace the screen again... it cost alto... :|
Well, at least now I know how to bring it safely back to life. And I must admit that my friends are quite impressed that I managed get it work again.

[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!

Completely and utterly bricked T95Z Plus - can it be saved?

His folks. Here's what happened...
Bought new T95Z Plus. The 3GB/32GB version. Looks funky.
Tried it, very nice, but wanted to install custom firmware.
Tried AMLogic Burning Tool. Not happening - disconnects device at 2% every time. Found about 50 different variations of how to connect, none work. Always stop at 2%.
Reads tutorial on other site about using Flashify to flash TWRP. Of course! Revelation! Installed Flashify from Google Play on stock ROM. It works!
Reboots to TWRP, standard wipe as directed, and installs Poison ROM from SD Card on device.
Success! Reboots into Poison ROM!
Very nice. But what's this? Wi-Fi doesn't work. Posts problem. No replies about Wi-Fi.
Searches around net for answer. Nothing, just a few people in same boat. Really needs Wi-Fi...
Decides to flash back to stock for Wi-Fi. OF COURSE NOT TAKEN ANY BACKUPS BECAUSE DAMN FOOL!
Gets file from post here in the Poison ROM thread. Gets both stock and the modified one just in case.
Tries Burning Tool again. Nope, still crap.
Watches tutorial on SD Card Maker. Decides hey why not?
Sticks SD card in, watches as box bricks. Poison logo flashes on screen, quickly followed by extremely brief Droid logo "updating". Then blackness...
Panics. Curses self for not being more careful I KNOW YOU DON'T HAVE TO TELL ME!
Cannot connect box to either PC or TV now. Computer says no device, and black screen on TV.
Holds paper down with it while crying.
That's my story. Hope it at least gave you a lol for the money! Yes it's my fault, you don't have to tell me. I didn't back anything up (what can possibly go wrong right?), but is there anything left for me to do here? I did also see a tutorial about shorting the NAND chip to get it started, and I have opened the box and attempted this with a little screwdriver but nothing happened beyond a slight buzzing noise on one of the strips and the LED briefly going out.
Any help, advice, well-wishing and general tomfoolery welcomed at this difficult time! Ta folks!
if the pc is not finding the device last chance is to short the pins from nand chip https://www.youtube.com/watch?v=fsyS3p5asZs
you can use the pc or sd card, search for it
K-Project said:
His folks. Here's what happened...
Bought new T95Z Plus. The 3GB/32GB version. Looks funky.
Tried it, very nice, but wanted to install custom firmware.
Tried AMLogic Burning Tool. Not happening - disconnects device at 2% every time. Found about 50 different variations of how to connect, none work. Always stop at 2%.
Reads tutorial on other site about using Flashify to flash TWRP. Of course! Revelation! Installed Flashify from Google Play on stock ROM. It works!
Reboots to TWRP, standard wipe as directed, and installs Poison ROM from SD Card on device.
Success! Reboots into Poison ROM!
Very nice. But what's this? Wi-Fi doesn't work. Posts problem. No replies about Wi-Fi.
Searches around net for answer. Nothing, just a few people in same boat. Really needs Wi-Fi...
Decides to flash back to stock for Wi-Fi. OF COURSE NOT TAKEN ANY BACKUPS BECAUSE DAMN FOOL!
Gets file from post here in the Poison ROM thread. Gets both stock and the modified one just in case.
Tries Burning Tool again. Nope, still crap.
Watches tutorial on SD Card Maker. Decides hey why not?
Sticks SD card in, watches as box bricks. Poison logo flashes on screen, quickly followed by extremely brief Droid logo "updating". Then blackness...
Panics. Curses self for not being more careful I KNOW YOU DON'T HAVE TO TELL ME!
Cannot connect box to either PC or TV now. Computer says no device, and black screen on TV.
Holds paper down with it while crying.
That's my story. Hope it at least gave you a lol for the money! Yes it's my fault, you don't have to tell me. I didn't back anything up (what can possibly go wrong right?), but is there anything left for me to do here? I did also see a tutorial about shorting the NAND chip to get it started, and I have opened the box and attempted this with a little screwdriver but nothing happened beyond a slight buzzing noise on one of the strips and the LED briefly going out.
Any help, advice, well-wishing and general tomfoolery welcomed at this difficult time! Ta folks!
Click to expand...
Click to collapse
I bricked my device as well a few weeks ago. Here's how to fix it -
Open the device and locate the NAND chip. On either side of it, there will be either pins or pads.
Grab a paperclip and bend it into a U shape.
Plug the device in to the PC as well as power and then slide the ends of the paperclip along the pins/pads (touching different ones) until the PC recognizes it.
The nice thing about the the T95z, is that it's very easy to short out the NAND and reset it.
Good luck!
Thanks for your replies and support people. Very much appreciated.
I have somehow magically managed to short the pins and reset the device. The laptop has now installed the device drivers and it sees the box no problem now, whereas before it was completely invisible to the computer. However, there doesn't appear to be any working firmware out there for this device. When I use the AMLogic Flash Tool it fails at 2% with one or two I downloaded, or at 4% with another one. I'm guessing this means there's no working firmware, nothing I can find anyway. I've taken a shot of the box inside while I had it open. Hopefully someone can point me in the right direction. It's attached below. I notice it's a recent board - 31st March 2018. On the Wi-Fi Strip it says IT6335.
Does anyone know which firmware I should try next? Thanks all.
Highly doubt its a complete brick, sounds more like a USB or USB port error, change ports or USB cords
If its detected by the PC its far from a brick, just for reference ive flashed completely incompatible firmware on a H96 Pro H3 and still couldnt brick it..
S912/S905w firmware on an S905x device and still could recovery it
Yes I agree now. I think before shorting the pins it was a goner, but now what with the PC at least recognising it I might have a chance of saving it!
Tried two different laptops with no success though. Maybe it is the cable but it is a new one. Hmmm. Think I'll buy another to be sure. Thanks for replying everyone!
I had the same problem with my T95z and I think it's the same as yours. I contacted the seller and he gave me the following link and I was able to retrieve it.
http://en.mail.qq.com/cgi-bin/ftnEx...514a315e1563&t=exs_ftn_download&code=a4d4081c
THANKS YOU SO MUCH! This flashed first time, same cable and everything. I suspect the AMLogic Flash Tool knows when the ROM is incorrect for the device...? Perhaps. Anyway, this flashed, and didn't show any errors.
However, I'm now stuck on the boot up "T95Z" logo. I figured on first boot up it may take some time to get itself ready, but I left it half an hour and it was still sitting there on the logo. I unplugged it and tried the toothpick solution to get to recovery but that doesn't seem to want to respond either. It just goes straight to the logo and sits there.
Anyone have any ideas at this stage? I'm amazed I got it this far tbh. Thanks to everyone, and particularly Narcoticx for the firmware.
K-Project said:
THANKS YOU SO MUCH! This flashed first time, same cable and everything. I suspect the AMLogic Flash Tool knows when the ROM is incorrect for the device...? Perhaps. Anyway, this flashed, and didn't show any errors.
However, I'm now stuck on the boot up "T95Z" logo. I figured on first boot up it may take some time to get itself ready, but I left it half an hour and it was still sitting there on the logo. I unplugged it and tried the toothpick solution to get to recovery but that doesn't seem to want to respond either. It just goes straight to the logo and sits there.
Anyone have any ideas at this stage? I'm amazed I got it this far tbh. Thanks to everyone, and particularly Narcoticx for the firmware.
Click to expand...
Click to collapse
flash a new stock firmwar, should boot after that
Thanks for replying. So, I can now flash this with a different stock firmware, yes? I'll give it a go. You have one linked in your Poison ROM thread so I'll try that.
Thanks again to all for your help.
K-Project said:
THANKS YOU SO MUCH! This flashed first time, same cable and everything. I suspect the AMLogic Flash Tool knows when the ROM is incorrect for the device...? Perhaps. Anyway, this flashed, and didn't show any errors.
However, I'm now stuck on the boot up "T95Z" logo. I figured on first boot up it may take some time to get itself ready, but I left it half an hour and it was still sitting there on the logo. I unplugged it and tried the toothpick solution to get to recovery but that doesn't seem to want to respond either. It just goes straight to the logo and sits there.
Anyone have any ideas at this stage? I'm amazed I got it this far tbh. Thanks to everyone, and particularly Narcoticx for the firmware.
Click to expand...
Click to collapse
Great, glad I could help Our T95Z looks like a new version. Try reflash again.
The developers can make an adaptation Poison rom with the firmware our original?
K-Project said:
Thanks for replying. So, I can now flash this with a different stock firmware, yes? I'll give it a go. You have one linked in your Poison ROM thread so I'll try that.
Thanks again to all for your help.
Click to expand...
Click to collapse
Yep or your can flash infected rom as its the most recent build specifically for the T95Z plus, but its based on ATV UI so either way whatever you feel is best
Infected rom does not work in our box, it gives an error when trying to flash amlogic usb.
Hi to you all this Sunday morning! Back again in desperation...
Unfortunately since flashing the ROM in this thread (which completed successfully with no errors), I have had no joy at all getting this box working. It boots up, you get the "T95Z PLUS" logo onscreen, and it just sits there. I have tried:
Reflashing with the same ROM and also other ROMS but it makes no difference. The PC now only recognises the box intermittently and the godawful AMLogic Burn Tool always spits errors (erase bootloader/identify/error). Can't even get it to the 2% I enjoyed before. It doesn't matter how you connect the box to it. Toothpick, no toothpick. Load image first, don't load image first. None of the various permutations of connecting this box seem to make a blind bit of difference.
SD Card Tool - but the box won't boot to it. Tried shorting the pins, nada.
I've shorted out those pins so many times I've probably fried the chip by now.
Ricky I looked at your own tools and would have liked to try them. Surely they MUST be better than the AMLogic crap! But it needs an IP address to continue (unless I'm reading it wrong). I don't have this as the box is bricked. Is there anything else I can do here?
Many thanks again for all your help.
K-Project said:
Hi to you all this Sunday morning! Back again in desperation...
Unfortunately since flashing the ROM in this thread (which completed successfully with no errors), I have had no joy at all getting this box working. It boots up, you get the "T95Z PLUS" logo onscreen, and it just sits there. I have tried:
Reflashing with the same ROM and also other ROMS but it makes no difference. The PC now only recognises the box intermittently and the godawful AMLogic Burn Tool always spits errors (erase bootloader/identify/error). Can't even get it to the 2% I enjoyed before. It doesn't matter how you connect the box to it. Toothpick, no toothpick. Load image first, don't load image first. None of the various permutations of connecting this box seem to make a blind bit of difference.
Click to expand...
Click to collapse
did you try another good power supply? maybe this is the problem?
drakulaboy said:
did you try another good power supply? maybe this is the problem?
Click to expand...
Click to collapse
Yes I bought a new one from MyVolts which has been the main PSU since receiving the item. I haven't used the one in the box hardly at all. I also bought two different USB cables - one is 1m and the other is 30cm. Tried three different Windows computers - same result. Also tried different versions of the Burning tool. The one that did the job initially is version 2.16, but like I say even now that isn't working either.
I'm now assuming the box is dead.
looking for this firmware.
any chance this file could be rehosted. i have the same device with same issue.
Narcoticx said:
I had the same problem with my T95z and I think it's the same as yours. I contacted the seller and he gave me the following link and I was able to retrieve it.
Click to expand...
Click to collapse
demiser said:
any chance this file could be rehosted. i have the same device with same issue.
Click to expand...
Click to collapse
https://drive.google.com/open?id=1IE1wW8ny9EBlAGf-aB1i7sOSyGNA_lnQ
thankz
has anyone else had any luck with finding a working firmware for these devices. mine has the same issue were it gets stuck at the boot logo with this firmware and wont burn any other firmware. errors out at ddr

Categories

Resources