Database Info

[Q] Nexus S bricked. Now what?

Hi,
I wanted to update my Nexus S from SlimBean 4.2.1 1.0 to 1.1 this morning.
I didn't do a full wipe which basically ruined my OS so I wanted to back it all up, full wipe and start all over again.
I had big problems with backing up as Titanium Backup either crashed or was stuck at it's initializing SQLite stage.
The phone process and System UI were crashing all the time if that matters.
So I tried to back it up through CWM which first failed while backing up the data partition, but it worked the second time.
I turned the phone off and since then it's not doing anything anymore.
Won't turn on, doesn't show the charging animation when plugging it in.
I tried to recover it several times.
It doesn't show up in Windows' Device Manager and UnBrickableRessurrectorR40 doesn't see it.
Is there anything I can do?
Thanks a lot.
land.apfel

why don't you try to get it to download mode and flash via odin ?

I would do it that way if it was possible. The Nexus won't do anything. Neither fastboot, nor Download nor recovery nor anything else.
The only thing it does is getting hot when being connected to AC.
But I'll try to do the UnbrickableMod and see if it helps.
land.apfel

Did you make the hardware modification? I have to do it with mine to be recognized.

samcortez said:
Did you make the hardware modification? I have to do it with mine to be recognized.
Click to expand...
Click to collapse
hardware modification is so difficult so as to be impossible for most people. it seems to be the only solution though. i only just bought my nexus s (for $150) second hand .. flashed cwm 10 on it and it bricked a few days later when i swapped a battery. i have disassembled the phone but the modification required needs minute tools and expertise beyond my ability. any suggestions? sending it in to experts in the USA will cost me nearly $100 and I'm afraid the diagnosis might mean I will lose that as well.

Without the hardware modification you can trash your Nexus S right now, as the chance that you recover it for some reason is probably 0.01%.
For doing the hardware modification you really need to know what you're doing. If you don't, look out for someone you know and who would do it for you.
After you did the UnbrickableMod, the chance that you can recover your phone is about 60% (maybe).
If you can't recover the phone, you need to exchange the eMMC chip as well.
I found eMMC chips in China for $19, but you still need to assemble it.
This is where I'm stuck at the moment.

my phone is in same condition please someone solve this and share with us

If you haven't already applied the UnBrickableMod you should try that first.
If you have, I have no idea what to do.
land.apfel

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.

Digitizer works in TWRP recovery but not after normal boot

I'm new to this forum and this is my 2nd attempt to get help to solve my problem. I have read ALL the rules posted in the XDA New User Guide - Getting Started On XDA, as well as all of the linked pages that are suggested to read before posting. It was very informative but I'm more confused then ever about the right place to seek help. This is all very overwhelming and I'm afraid I'm going to say something to offend someone or post in the wrong place and get in trouble, or worse, ignored. I suspect I did just that in my last post because I never got a response. I apologize in advance if I have done something wrong.
Ok, I'll do my best to explain my problem. I have an LG K20 Plus (I'll refer to this as my original phone) that I bought, brand new, from T-Mobile in May. In August I cracked the screen but continued to use it because besides the crack, it worked fine. By September the crack had worsened significantly and I decided to replace the outer glass as I had successfully done that with my older LG G3.
In that process, while trying to get that dreadful glue off, I scraped off some of the black stuff under the glue on the LCD which caused a white spot, about the size of a 1/2 dollar, on my screen. Although it was bothersome, the phone itself still worked fine. I continued to use it while I searched for the easiest way to fix it within my budget. After reading posts here and realizing it would work, I bought a used LG K20 Plus (I'll refer to this as my used phone) with a bad esn. The plan was to put my original logic board into the used phone and be on my way. That didn't happen.
When the used phone arrived, I turned it on to verify everything worked. I then put my original logic board into the used phone and turned it on. I saw my orignal wallpaper and was so happy I had my phone back. Then I tried to swipe to unlock and nothing happened. I booted it up a couple more times and still nothing. I connected a mouse via an OTG cable and verified that there were no more obvious issues with the phone except the digitizer. To confirm the dispaly wasn't faulty on the used phone, I put the used logic board back into the used phone it came with and booted it up. The digitizer was back to working again. I ran through as much as I could on a locked phone and the digitizer worked like new.
I, carefully, put my original logic board back into the used phone and, again, no touch capability. Again, I researched this problem to no avail. I realized I was way over my head and I decided to ask for help instead of making things worse by trying to fix it without knowing what I was doing. So, I put the phone in a drawer and asked for help here. That was a month ago. I know you are all very busy and, like I said earlier, I'm sure it's my fault and I messed up somewhere because my post didn't receive any replies.
I can't use my original phone because I have no touch ability and I can't use the used phone because it has an esn lock. At this point I decided to try and (I'm sure I'm using the wrong terminology here) flash the used phone and root it to bypass the bad esn lock. After researching that and seeing the word "illegal" A LOT, I decided I just didn't know if it was legal or not, so I decided to not take the risk of doing something that may get me into trouble.
At this point I decided I didn't have much to lose so I backed up my original phone and, with only the display of the used phone attached, I started the process of flashing it with TWRP and rooting it via this guide https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248 So, it is now successfully rooted but it still has no touch ability. The really weird thing is, while I was in TWRP Recovery mode, the touch ability worked again. But as soon as I rebooted the phone into regular mode, the digitizer stopped working again. I'm so confused and I don't even no where to start looking because I can't define the problem or the exact thing that is failing. I don't even know if it's hardware or software related.
So, I guess my question is, does anybody have any experience with this kind of problem you could share with me. I'd settle for someone being patient enough to explain to me exactly what is going on so I could research it better myself. Asking for help was not my first step. I have been looking and looking for 6 weeks now. I'm way out of my league with this stuff. It's really difficult to find a solution to a problem you don't quite understand. It's a little bit like being told to look up a word in the dictionary to find the spelling.
*LG K20 Plus
*LG-TP260
*T-Mobile
*Rooted
Baseband: MPSS.JO.
2.0c1.2-00012-8937_GENNS_PACK-1.85468.1
I think it's my original ROM
Kernel Version 3.18.31
I flashed TWRP
USB debugging enabled
OEM Lock Off

Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.

zelendel said:
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
Click to expand...
Click to collapse
I'm so sorry but I have run into a few problems .. firstly, on my phone I have to use a mouse connected via OTG cable because I have no touch ability and my usb connection is set to "charge only". Apparently you can't change that until the phone is plugged in and obviously I need the mouse so I can't connect to computer. I downloaded an app called LogCatX and made a log file but I don't know how to attach a file and when I copy/paste it into the reply it says it is too long and reduce by 30000 characters. Any advice?

HelpNeededPlz said:
I'm so sorry but I have run into a few problems .. firstly, on my phone I have to use a mouse connected via OTG cable because I have no touch ability and my usb connection is set to "charge only". Apparently you can't change that until the phone is plugged in and obviously I need the mouse so I can't connect to computer. I downloaded an app called LogCatX and made a log file but I don't know how to attach a file and when I copy/paste it into the reply it says it is too long and reduce by 30000 characters. Any advice?
Click to expand...
Click to collapse
I think the new touch screen will need a calibration.
PS: i liked how you explained your problem

Sorry for my confusion but I'm not sure if you were telling me what I should do to figure out where the incompatibility issue may be or if you were asking me to upload the catlog so you could look at it and help me. I don't know what a catlog is, nor how to interpret it. At any rate, 6 hours later, I have, finally, figured out how to upload a file. :victory: I've been looking at how to fix a kernel incompatibility issue and I've read you can flash a custom kernel. If I did something like that, would that resolve my problem. Are they specific to the version of operating system your phone has (ie nougat, marshmallow etc) or do you need to use one for your specific phone model? Would flashing a custom ROM do the same thing? And is that model specific or OS specific? Where would I go to find something like that?
NOTE... In looking for differences in my phone to try and figure out where this kernel compatibility issue might be, I noticed that there are two different numbers on the midframe of my phones. I don't know if this means anything. I'm just trying to help someone help me.

zelendel said:
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
Click to expand...
Click to collapse
Hello? Was this the extent of your help? I'm not sure if you were asking me to run a catlog to upload so you could help me figure out what was wrong or if you were just telling me what to do and then moving on. Because if it was the later, all you've done is piled more stuff on my steadily growing mound of confusion. To make matters worse, my posts is showing as getting a response, so, I fear, nobody else will look at it and I will be left in the same place as before. If someone happens upon this post, could you give me advice that will actually help me solve my problem, along with instructions on how to do whatever I need to do. Thank you in advance. Until then, I'll be anxiously awaiting your reply....

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

In Need Of Some Assistance With SM-G930F Is It Dead?

Hello, First time poster long time user of XDA, I some what experienced with flashing roms, recovery, kernels and modems but I ran into my first major issue.
I will start with how I obtained the phone and go from there, I think the more you know the more you could help.
I got the phone on ebay relatively cheap, its apparently google locked as he forgot his password, no biggie for me ill get around that.
He claimed he was replacing the screen and cracked the new glass while trying but not the lcd.
Anyway once I received it I turned it on and tried to see how far I could get in the initial set up.
I only got to the wifi selection screen, It would not turn on and when the button moved to the on position it would indefinitely load.
I assumed faulty rom flash.
I downloaded the latest rom from sammob and flashed to oreo, same Issue, I should point out at this point I had no data left on my sim to proceed on the phone without internet.
My friend who very experienced with the flashing seen suggested the modem.
I flashed one he suggested then no sim reception def no wifi.
ok damn.
I went to flash the oreo once again and for some messed up reason I wiped the nand only.
Well I wasnt to happy with myself to say the least.
To further ad to the pain, I can no longer access recovery or download mode to salvage this.
No button input seems to work.
It gets to the pulsing samsung logo and that its.
I even resorted to making a usb jig, It has no response to that but my spare note 2 boots to download no worries with it.
It does charge via usb, The buttons were working correctly when I was first in android at the beginning.
Does anybody have any suggestions or ideas?
Many thanks in advance, I will be following this post regularly and reply with feedback and report progress.
Cheers. r3al77