Related
Hey guys,
I need help. Badly. My trusty SCH-I535 has pretty much gone to pot over the last three days. It started with the lockscreen/power button becoming so loose and sensitive, that the screen was perpetually turning on and off. However, my warranty expired last Thursday. Aside from that, the software was functioning beautiful (Carbon ROM, unknown August 4.3 nightly). Today however, the phone decided to freak out. Suddenly, it began displaying the incorrect time, wouldn't show me new messages, and applications were incredibly unstable. In an attempt to fix the issue, I decided to re-flash the ROM. This however, made no change. Therefore, I made the decision to finally update to the most recent stable version. After doing this, the phone wouldn't boot past the carbon boot animation. I rolled back to an older build, and had the same issue.
Here's where it gets sucky. After rolling back didn't do anything, I was in the process of re-flashing 1.8. During install process, TWRP crashed. This left me without a bootable system partition. As the night has worn on, it's become worse and worse. Now, TWRP is crashing often before the splash screen, at the "Samsung Galaxy SIII" screen. Occasionally it will load, but always locks up and crashes before finishing the install process. Same deal with CWM. I have tried several versions of both recoveries and none have made a single bit of difference. I've scoured the forums, and can't seem to find an identical problem/working fix. I've tried everything I can find, and so far, nothing productive has happened. It's 3:25AM over here, and I'm exhausted. I'm at my wits end. Any input would be fantastic.
Thanks so much,
The_Unofficial
Did you try to flash via ODIN? Maybe it will help you to boot it to normal.
The_Unofficial said:
Hey guys,
I need help. Badly. My trusty SCH-I535 has pretty much gone to pot over the last three days. It started with the lockscreen/power button becoming so loose and sensitive, that the screen was perpetually turning on and off. However, my warranty expired last Thursday. Aside from that, the software was functioning beautiful (Carbon ROM, unknown August 4.3 nightly). Today however, the phone decided to freak out. Suddenly, it began displaying the incorrect time, wouldn't show me new messages, and applications were incredibly unstable. In an attempt to fix the issue, I decided to re-flash the ROM. This however, made no change. Therefore, I made the decision to finally update to the most recent stable version. After doing this, the phone wouldn't boot past the carbon boot animation. I rolled back to an older build, and had the same issue.
Here's where it gets sucky. After rolling back didn't do anything, I was in the process of re-flashing 1.8. During install process, TWRP crashed. This left me without a bootable system partition. As the night has worn on, it's become worse and worse. Now, TWRP is crashing often before the splash screen, at the "Samsung Galaxy SIII" screen. Occasionally it will load, but always locks up and crashes before finishing the install process. Same deal with CWM. I have tried several versions of both recoveries and none have made a single bit of difference. I've scoured the forums, and can't seem to find an identical problem/working fix. I've tried everything I can find, and so far, nothing productive has happened. It's 3:25AM over here, and I'm exhausted. I'm at my wits end. Any input would be fantastic.
Thanks so much,
The_Unofficial
Click to expand...
Click to collapse
Your broken power button is probably the issue. The reason your recoveries are crashing is likely because the power button is triggered and it's making the phone turn off in the middle of the process.
It's unfortunate your warranty just expired, but you can get it fixed through a website, then you should be good from there. Also I would try to call up Samsung and tell them what you think the problem is, they might give you a break and fix your phone anyway since it's only a week after warranty.
Sent from my SCH-I535 using Tapatalk 2
Details...
Alright guys. More details. Sorry it took so long to reply. Apparently I had Gmail set to send XDA emails to spam. Silly me.
The more times I attempt to boot to recovery, the earlier TWRP will freeze.
TWRP rarely makes it beyond the "Installing System" process
TWRP NEVER makes it beyond the "Creating Symlinks" phase
I'm using TWRP 2.6.3.0
If I let the phone sit, it gets farther in the installation process before hanging
Bad Username, I tried contacting Samsung and Verizon. Neither one of them would replace , or fix it for me. Have any specific resources for repairing the button? That would be excellent. I just ordered a cheap $3 case on Amazon to see if that would help fix the problem. I don't, however believe this is causing the problem. TWRP has a lockscreen. It never goes to the lockscreen, it just hangs, then eventually force reboots. Almost as if some temporary RAM storage is being filled up. It's quite strange.
skyss07 I would REALLY prefer not to flash to stalk. Like, REALLY. This would mean losing all my files and pictures. I'm not too keen on that. I'm saving that as a final resort only.
The_Unofficial said:
Alright guys. More details. Sorry it took so long to reply. Apparently I had Gmail set to send XDA emails to spam. Silly me.
The more times I attempt to boot to recovery, the earlier TWRP will freeze.
TWRP rarely makes it beyond the "Installing System" process
TWRP NEVER makes it beyond the "Creating Symlinks" phase
I'm using TWRP 2.6.3.0
If I let the phone sit, it gets farther in the installation process before hanging
Bad Username, I tried contacting Samsung and Verizon. Neither one of them would replace , or fix it for me. Have any specific resources for repairing the button? That would be excellent. I just ordered a cheap $3 case on Amazon to see if that would help fix the problem. I don't, however believe this is causing the problem. TWRP has a lockscreen. It never goes to the lockscreen, it just hangs, then eventually force reboots. Almost as if some temporary RAM storage is being filled up. It's quite strange.
skyss07 I would REALLY prefer not to flash to stalk. Like, REALLY. This would mean losing all my files and pictures. I'm not too keen on that. I'm saving that as a final resort only.
Click to expand...
Click to collapse
Mobile tech videos would do it, not sure what the cost would be, I'd try contacting them.
Sent from my SCH-I535 using Tapatalk 2
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
kimber015 said:
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
Click to expand...
Click to collapse
Before I start: DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR ACTIONS BY FOLLOWING MY INSTRUCTIONS. YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Now we got that out of the way...
Try upgrading to 4.4.2: http://sbf.droid-developers.org/phone.php?device=14 (Get the firmware here)
Use the thread you mentioned: http://forum.xda-developers.com/showthread.php?t=2542219
Hi guys, I'm sincerely apologizing if this is the wrong place to open a thread about something like that, I couldn't figure out where else to write down my issue. I've been told here are people that know the most about devices and that someone might be able to solve an issue I got with my Samsung s6 Edge. The samsung support has been not helpful at all and it's either sending it to them to repair it and loose all my files or at least before doing that at least trying to save some of my personal files. The problem yet is that I can't even get into my phone. I was charging it at night and suddenly I saw a flashing Samsung Logo on screen with a blue LED that flashes as well. So the device had to be turned itself off and then it was restarting but it couldn't get pass the 2nd SAMSUNG loading Screen and got stuck. That's all. From then on I wasn't able to do anything with it. First I thought it may be making some updates, but then again I turned off my wifi before going to sleep. So that can't be the case. I waited hours, because I was hoping it might get pass it at some point but it didn't. While waiting I looked up tutorial to fix it but nothing seemed to work out and then I called the samsung support which basically just told me to turn it on and off without any real solving advice. So here I am. desperate to just save up the last photos and that's it. Does anyone know a solution that won't mess with my guarantee.
Again, I'm really sorry if this isn't the right place to ask.
Thanks for reading if you made it up to here,
Erika
EriBerry said:
Hi guys, I'm sincerely apologizing if this is the wrong place to open a thread about something like that, I couldn't figure out where else to write down my issue. I've been told here are people that know the most about devices and that someone might be able to solve an issue I got with my Samsung s6 Edge. The samsung support has been not helpful at all and it's either sending it to them to repair it and loose all my files or at least before doing that at least trying to save some of my personal files. The problem yet is that I can't even get into my phone. I was charging it at night and suddenly I saw a flashing Samsung Logo on screen with a blue LED that flashes as well. So the device had to be turned itself off and then it was restarting but it couldn't get pass the 2nd SAMSUNG loading Screen and got stuck. That's all. From then on I wasn't able to do anything with it. First I thought it may be making some updates, but then again I turned off my wifi before going to sleep. So that can't be the case. I waited hours, because I was hoping it might get pass it at some point but it didn't. While waiting I looked up tutorial to fix it but nothing seemed to work out and then I called the samsung support which basically just told me to turn it on and off without any real solving advice. So here I am. desperate to just save up the last photos and that's it. Does anyone know a solution that won't mess with my guarantee.
Again, I'm really sorry if this isn't the right place to ask.
Thanks for reading if you made it up to here,
Erika
Click to expand...
Click to collapse
You may get more help by getting the thread moved to Galaxy S6 Edge Q&A, Help & Troubleshooting.
To do so, simply click the "report button" and select "thread/post moving".
Now, on with the issue. What you're having seems to be a bootloop.
One thing you could try is booting into recovery and wiping the cache.
I'm not exactly sure how booting to recovery works on the S6, but it generally is: turn the phone off, then hold the power button + volume up button until the phone vibrates. If that doesn't work, try adding the home button to that combo, or just Google how to boot into recovery.
Anyway, if that doesn't work, then I'm afraid there won't be any other solution than reinstalling the firmware yourself or sending it to warranty (where they will probably reinstall the firmware).
Your photos shouldn't be affected in the process, as they are saved on the internal memory and, unless somebody wipes it, you shouldn't lose your files.
But you will definitely lose your apps and app data in the process.
Flashing the firmware yourself should not void the warranty.
The process can be done with Odin (a software also used by Samsung). I'm not sure how familiar you are with flashing, but you may want to do some reading or watch video guides on the subject of using Odin. Since the S6 is pretty much a new device, I'm sure you will find lots of video tutorials for the S6 specifically.
And, as I said, your internal storage stuff should be safe too.
Hey!
So, today my gf charged her OPO for 30 min, turned off. When she tried to turn it back on afterwards, the phone went into bootloader. She tried to restart it, but everytime it only restarts to bootlader. The first time there was also a picture of the android figure, but with an error message or sth like that, but she cannot remember exactly.
The phone is not rooted, stock firmware and stock bootloader, latest update of the official CM firmware (not oxygen OS).
We tried wiping cache only. No difference. We tried wiping all data. No difference.
Any other ideas?
probably there is a corruption happened in software. Suggest you to went fully stock cm13s via fastboot. You can find necessary tutorials in general section.
zaoms said:
probably there is a corruption happened in software. Suggest you to went fully stock cm13s via fastboot. You can find necessary tutorials in general section.
Click to expand...
Click to collapse
Ty for your suggestion. After coming home and thoroughly examining the phone (that is, taking of the back plate among other things), I found the problem. The volume up key got stuck in the housing and was therefore constantly pressed; however, due to the shallow keys, it was barely noticable and easily missed. This was also the reason why every restart resulted in bootloader. Everything working now
Zigurat said:
Ty for your suggestion. After coming home and thoroughly examining the phone (that is, taking of the back plate among other things), I found the problem. The volume up key got stuck in the housing and was therefore constantly pressed; however, due to the shallow keys, it was barely noticable and easily missed. This was also the reason why every restart resulted in bootloader. Everything working now
Click to expand...
Click to collapse
Wow good thinking back there. Most of users(including me) thinks software issue but you found it nice amd easily. Happy to know it is ok now.
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