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
Related
So I tried everything in all the other threads and it's still a no go for me. This is extremely disappointing, I was really loving this thing.
I'm scared to even attempt going through Asus's terrible customer service, especially with my TF being rooted and all...
any advice on what I may be able to do?
what happens when you plug it in? Does charger get hot? Try leaving plugged into powered usb overnight.
I had an issue where I left my transformer a week ago plugged into the electricity, and when I came back home - it was out of battery and refused to turn on. I tried plugging into the computer directly but that didn't help either.
Today I went to best buy and plugged it into an adapter on display, and it started working..
When I came back home, I tried my cable again and it suddenly worked!
The moral of the story is it seems the power adaptors are quite flaky. Try to disconnect and connect again..
Also see this thread with some tips on fixing the power adaptor:
http://www.transformerforums.com/fo...er-no-longer-charges-wall-wart-adapter-4.html
I highly doubt the charger is the problem in my particular case because the dock seems to charge fine. Also, my TF died on my when it still had around 80% battery life.
Another thing is that my alarm clock that I have set up on my TF still goes off every morning and the only way for me to turn it off is by repeatedly pressing the power button (this is extremely annoying).
I'm assuming that the screen may have just completely died or something of that sort.
Do you guys have any other advice, or should I just go ahead and attempt to rma it?
thanks it advance
I had this same thing happen to my TF a few weeks ago. The solution for me was to use the tool in this thread: http://forum.xda-developers.com/showthread.php?t=1185104
I used v6.3 for my US 8.6.5.9 rom version. This basic steps I took were to install the APX driver (steps in the thread above), then run the batch file and do 4, 5, & 6. I didn't see anything on my TF screen until the above was completed and then turning it on.
Hope this helps you.
starplaya93 said:
So I tried everything in all the other threads and it's still a no go for me. This is extremely disappointing, I was really loving this thing.
Click to expand...
Click to collapse
Have you tried buying it a few drinks and whispering complements about how beautiful and smart it is into it's microphone?
jmolhava said:
I had this same thing happen to my TF a few weeks ago. The solution for me was to use the tool in this thread: http://forum.xda-developers.com/showthread.php?t=1185104
I used v6.3 for my US 8.6.5.9 rom version. This basic steps I took were to install the APX driver (steps in the thread above), then run the batch file and do 4, 5, & 6. I didn't see anything on my TF screen until the above was completed and then turning it on.
Hope this helps you.
Click to expand...
Click to collapse
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
starplaya93 said:
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
Click to expand...
Click to collapse
Bump /:
10char
starplaya93 said:
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
Click to expand...
Click to collapse
I am very interrested in this thread as I have the very same problem.
Asus proposed to RMA it but I fear that they might find some trace of the previous root as I unrooted "blindly"
blabox said:
I am very interrested in this thread as I have the very same problem.
Asus proposed to RMA it but I fear that they might find some trace of the previous root as I unrooted "blindly"
Click to expand...
Click to collapse
yeah, that is what i'm worried about as well.
What number did you contact for the RMA?
Well apparently my only option is to RMA the device.
I went ahead and un-rooted it with the BRK toolkit, however after un-rooting it said that I have to load a stock rom and recovery image onto it. How do I go about doing this without turning it on and flashing the zip in recovery?
Do you all think ASUS will even notice it is rooted and if so what steps should I take to ensure that there is no proof of root?
Please help me a bit on this one guys.
I had the same issue with mine last week. Appeare dead but would connect to PC APX mode and could view SD card contents.
When looking at the screen with a flashlight, the text was visible. The unit was actually working but the backlight had died.
Had to get it replaced with new one from place I bought it from on their product replacement scheme. great except its a new one that can't be rooted yet.
Sitting patiently for that to be released so I can go back to playing....
starplaya93 said:
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
Click to expand...
Click to collapse
Yes, my TF was rooted and running a custom ROM. When running the batch file that is in the package in the other thread I referenced, I did steps 4, 5, and 6. Then rebooted and it was fine. If you can get the APX driver installed and your computer will recognize it, then try those steps using the tool. Once I rebooted, it just loaded my same ROM as if nothing had happened.
Of course a hardware failure would cause the same thing (backlight or LCD not working, etc...) but in my case it was a software or booting issue and the above fixed it. If you try what I did and still nothing then RMA is probably your only option.
i had this problem too, in my case it was a defective power button. had to push it real hard to get the pad turned on ... rma fixed it ....
i have the same problem also and it turned out to be the power button my solution was just to keep pressing it haha and then it worked strangely enough. ive read somewhere that it it gets misalligned somehow. i guess i have 2 options either send it back or fix it myself at the moment im just living with it.
it works somedays then otherdays it takes a few pushes lol
My case seems to be none of the above.
I tried checking if it was an issue with the back light and put a flashlight up to it in a pitch black dark room but I can't see anything on the screen whats so ever, regardless of the angle I put it in.
I also don't think it is the power button because like I said, i'm able to put he tablet in APX mode and take it out of APX mode as well at will by pressing the power and volume up button.
Thirdly, I tried the root kit several times (version 7) and while it's doing it's job of rooting and un-rooting my TF, there still is no change in the functionality of the screen.
so i'm pretty much sol. I already placed in an RMA to asus, now I just have to ship it off (asus has by far the worst customer service that I have ever seen).
My final question would be is there anyway to load a stock rom and recovery image without being able to turn the tablet on? I'm able to unroot it with the rootkit, but it says that I still need to load a stock rom and whatnot.
If somebody can point me towards directions as to how I go about doing this, that would be great.
Thanks for all the help guys.
I was in a bootloop on my Nexus S. The phone was completely stock. It was never rooted and never ran any custom roms. I charged the battery, then turned on the phone and it went into a bootloop. I tried a battery pull, and nothing. So I finally decided to follow this tutorial and rooted the phone. Now the phone boots up and all is good again. Can anyone tell me what most likely would have caused this to begin with, and why rooting would have fixed it?
Corrupted file somewhere, likely in /data, otherwise maybe .android_secure. Unless its a battery related issue I'd put it down to this.
No idea what exactly it could've been and never heard of someone with the issue though. One of technologies mysteries in the end.
Harbb said:
Corrupted file somewhere, likely in /data, otherwise maybe .android_secure. Unless its a battery related issue I'd put it down to this.
No idea what exactly it could've been and never heard of someone with the issue though. One of technologies mysteries in the end.
Click to expand...
Click to collapse
Well I looks like it's mystery solved. I think it was a hardware problem, as it went back into bootloop at first, but now it's stuck on the Google logo. I can't even unlock the bootloader anymore. Each time I try fastboot oem unlock, it comes back as: Failed <remote: Erase Fail>. Everywhere I've searched for a solution, comes back as a hardware failure. The phone is only over a year old.
I've flashed my 2 galaxy s 4gs countless times and always kept this thing completely stock until I had to unlock and root this thing just to get it working. And now it seems it's totally bricked without even flashing a single rom with no more warranty left. Go figure.
More and more people getting that erase fail error. Speak to Samsung and let them know it seems to be a common problem with the nand chip they used. Plenty of others with the same issues, most lucky enough to get it fixed under warranty. Just maybe there is someone nice enough to help.
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....
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
Hello! So 6-7 months ago my phone dropped without a case on the ground and since then it couldn't boot up anymore. It didn't showed up the Samsung logo, the only thing that came was this little blue light that showed up if you wanna boot it up - that's it!
My PC doesn't recognize my phone and the DL-mode isn't working either. Plus the homebutton is broken.
Is there anyway possible to access the data and safe it somehow? There are really important pictures for me that I'd really love to save and see again
Thanks in advance!
ObamaObamaObama said:
Hello! So 6-7 months ago my phone dropped without a case on the ground and since then it couldn't boot up anymore. It didn't showed up the Samsung logo, the only thing that came was this little blue light that showed up if you wanna boot it up - that's it!
My PC doesn't recognize my phone and the DL-mode isn't working either. Plus the homebutton is broken.
Is there anyway possible to access the data and safe it somehow? There are really important pictures for me that I'd really love to save and see again
Thanks in advance!
Click to expand...
Click to collapse
you need a recovery boot image. Theyre sparse but they exist. you need someone with the same model S6 that is functioning to do a dump of its ISO. mount that ISO to a SD card, pop it in the phone and itll likely boot. I recovered a "hard bricked" S3 that way, and that method of recovery does indeed live on. @TheMadScientist you got anyone in your list who has this ISO he heeds? Ill also cal lin @AthieN but he isnt on here too much these days.
youdoofus said:
you need a recovery boot image. Theyre sparse but they exist. you need someone with the same model S6 that is functioning to do a dump of its ISO. mount that ISO to a SD card, pop it in the phone and itll likely boot. I recovered a "hard bricked" S3 that way, and that method of recovery does indeed live on. @TheMadScientist you got anyone in your list who has this ISO he heeds? Ill also cal lin @AthieN but he isnt on here too much these days.
Click to expand...
Click to collapse
If you are only getting a blue light, your EEPROM is most likely damaged and the only way to recover would be to have it serviced by a repair shop. Unless you feel like delving in to EEPROM recovery tools, which is not for the faint hearted...
Sent from my SM-G975U using Tapatalk
youdoofus said:
you need a recovery boot image. Theyre sparse but they exist. you need someone with the same model S6 that is functioning to do a dump of its ISO. mount that ISO to a SD card, pop it in the phone and itll likely boot. I recovered a "hard bricked" S3 that way, and that method of recovery does indeed live on. @TheMadScientist you got anyone in your list who has this ISO he heeds? Ill also cal lin @AthieN but he isnt on here too much these days.
Click to expand...
Click to collapse
IMo if it was dropped and not booting the issue lies elsewhere ive seen a load of them break and a no boot after dropping is normally a hardware issue i would check to make sure the battery is connected inside first making sure the device is getting power is key here since no connection on pc
AthieN said:
If you are only getting a blue light, your EEPROM is most likely damaged and the only way to recover would be to have it serviced by a repair shop. Unless you feel like delving in to EEPROM recovery tools, which is not for the faint hearted...
Sent from my SM-G975U using Tapatalk
Click to expand...
Click to collapse
TheMadScientist said:
IMo if it was dropped and not booting the issue lies elsewhere ive seen a load of them break and a no boot after dropping is normally a hardware issue i would check to make sure the battery is connected inside first making sure the device is getting power is key here since no connection on pc
Click to expand...
Click to collapse
And this is exactly why I call you guys in from time to time, and you both did not fail me. Thanks dudes