I decided to fastboot flash the rpm.img file from the OTA update, and now the phone will no longer boot. When its plugged in, the red light on the trackpad lights up.
What can i do?
Remove battery, keep unplugged, hold volume down and power and see if you can get into hboot
what was the command you entered into fastboot?
Blue6IX said:
what was the command you entered into fastboot?
Click to expand...
Click to collapse
fastboot flash rpm rpm.img
Connecting it to the PC it displayed as a Qualcom COM port, and I installed the driver from another site. The Qualcom QDLoader 9008.
Are there any manufacturer tools used to communicate via this port to perhaps reformat the entire nand chip to correct partition errors like this?
I think you are in a situation similar to this. I did not have the guts to try flashing something on my phone. There might be something possible but you are on the wild unexplored area right now.
The good thing here: lol my phone won't boot up today, wtf happen? Tmo proceeds to replace your phone
Sent from my RubiX ICS Infused using Tapatalk
leoilios said:
The good thing here: lol my phone won't boot up today, wtf happen? Tmo proceeds to replace your phone
Sent from my RubiX ICS Infused using Tapatalk
Click to expand...
Click to collapse
Lol, best advice of the day xD
Adding more to the conversation. "This isn't the first time this has happened. can you offer any other phones?"
Well I ordered a replacement. I was hesitant in asking for another phone. And to be honest there aren't any I'd really want for T-Mobile other than the MT4GS.
First I love having a physical keyboard, I use it often.
Also Sensation has had a lot of problems, the Amaze probably wouldn't qualify for an equal exchange due to a higher price, it would be nice, but the Roms on that seem even slower.
I'm not as lucky since I'm on a second-hand no-contract phone, so no easy freebie replacement option.
I tried flashing what turned out to be a bad PG59IMG.zip (looks like maybe a corrupt upload or download, but I didn't figure that out until too late).
Phone now shows (almost) no signs of life. Looks completely dead and silent, and pressing and holding the power button does nothing. I said almost because I got the orange charging light to come on once by clicking the track pad, but the experiment did not hold up to a second try.
Any ideas, besides the usual jokes about doorstops and target practice?
wjcarpenter said:
I'm not as lucky since I'm on a second-hand no-contract phone, so no easy freebie replacement option.
I tried flashing what turned out to be a bad PG59IMG.zip (looks like maybe a corrupt upload or download, but I didn't figure that out until too late).
Phone now shows (almost) no signs of life. Looks completely dead and silent, and pressing and holding the power button does nothing. I said almost because I got the orange charging light to come on once by clicking the track pad, but the experiment did not hold up to a second try.
Any ideas, besides the usual jokes about doorstops and target practice?
Click to expand...
Click to collapse
Next time your best bet would be to check an md5 sum of a zip before its flashed. Also i think its situations like this that forces us to use the HTC Unlock tool, so we dont have the power to brick our phones when we dont know what we are flashing or dont follow simple steps to insure your not bricked. There are unbricking projects out there
Maybe this http://forum.xda-developers.com/showthread.php?t=1627881 will help, i dunno i dont read that thread because i HOPE to never end up in bricktown
Sent from my myTouch_4G_Slide using Tapatalk 2
wjcarpenter said:
I tried flashing what turned out to be a bad PG59IMG.zip (looks like maybe a corrupt upload or download, but I didn't figure that out until too late).
Click to expand...
Click to collapse
FWIW, I'm now pretty convinced that it was not a bad PG59IMG.zip. I later DL'd from the same place and did check the MD5. I thought it was corrupt because it wouldn't open in WinZip, but 7Zip handled it fine. It flashed fine on a different MT4GS.
So, I think my MT4GS just decided to die as part of that flashing process. I may give the JTAG folks a try when I run out of patience for staring at it.
wjcarpenter said:
FWIW, I'm now pretty convinced that it was not a bad PG59IMG.zip. I later DL'd from the same place and did check the MD5. I thought it was corrupt because it wouldn't open in WinZip, but 7Zip handled it fine. It flashed fine on a different MT4GS.
So, I think my MT4GS just decided to die as part of that flashing process. I may give the JTAG folks a try when I run out of patience for staring at it.
Click to expand...
Click to collapse
Well because a new download had a good md5 does not mean the first one was a good download. Which still leaves you wondering if you bricked due to not checking the md5 of a potentially dangerous zip.
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
Well because a new download had a good md5 does not mean the first one was a good download. Which still leaves you wondering if you bricked due to not checking the md5 of a potentially dangerous zip.
Click to expand...
Click to collapse
In general you are right, but in this specific case I disagree. The vast majority of "bad downloads" are actually OK downloads of something pooched on the server, either a bad upload or bit rot while it was up there. A TCP download on reliable hardware is a pretty reliable thing. Since I refetched it from the same server location, it is IMHO overwhelmingly more likely to be some other problem than a bad DL.
I agree, it's still possible the first DL was bad. I'm just not inclined to think it probable.
wjcarpenter said:
In general you are right, but in this specific case I disagree. The vast majority of "bad downloads" are actually OK downloads of something pooched on the server, either a bad upload or bit rot while it was up there. A TCP download on reliable hardware is a pretty reliable thing. Since I refetched it from the same server location, it is IMHO overwhelmingly more likely to be some other problem than a bad DL.
I agree, it's still possible the first DL was bad. I'm just not inclined to think it probable.
Click to expand...
Click to collapse
You bricked your phone lol so you might want to start blaming yourself. I mean you are the careless one that wants to blame the brick on everything but the obvious. A bad download. You yourself said winzip told you it was corrupt.
Sent from my myTouch_4G_Slide using Tapatalk 2
wjcarpenter said:
FWIW, I'm now pretty convinced that it was not a bad PG59IMG.zip. I later DL'd from the same place and did check the MD5. I thought it was corrupt because it wouldn't open in WinZip, but 7Zip handled it fine. It flashed fine on a different MT4GS.
So, I think my MT4GS just decided to die as part of that flashing process. I may give the JTAG folks a try when I run out of patience for staring at it.
Click to expand...
Click to collapse
Just because you can't open the zip doesn't mean its corrupted. HTC signs there PGZIPs in a way that in most cases only bootloaders can open them.
xmc wildchild22 said:
Just because you can't open the zip doesn't mean its corrupted. HTC signs there PGZIPs in a way that in most cases only bootloaders can open them.
Click to expand...
Click to collapse
Right. That was the point I was making. I concluded the ZIP was corrupt simply because WinZip couldn't handle it. It was an HTC-signed ROM, so the WinZip failure is not meaningful.
(7Zip opens those ZIPs with no problem, but I also checked the MD5 the second time I downloaded it.)
Maybe it's due to the Alan Turing centennial stuff, but last night I witnessed some kind of Android phone religious miracle or something. Without (much) warning, my formerly dead phone sprang back to life!
CAUTION: This is a tale of uninformed adventure. If you try the same stuff, instead of the miracle of life, you might witness the miracle of smoke or other calamites.
So, there is hope. I wish I could tell you precisely how I did it, but I was just fooling around with this boat anchor, trying various desperate measures, when it suddenly greeted me with an hboot screen. In case others are in a similar "no harm in trying" state, here is the sort of stuff I was fiddling with last night.
I've tried the HTC Unbricking Project for MT4GS literally dozens separate times: http://forum.xda-developers.com/showthread.php?t=1627881 I've tried lots of variations of ways of getting the phone to be recognized (battery in, battery out; go fast, wait a while; push various buttons, push no buttons; full moon, new moon; ...). All dismal failures, so I've concluded -- rightly or wrongly -- that I don't have the kind of bricking that that stuff can cure.
Just on a whim, I thought there would probably be something I could do if I got the phone into Qualcomm download mode. That goes by various names (which is very confusing), but the phone gets recognized over USB as "QHSUSB_DLOAD". You can read a bit about that here: http://forum.xda-developers.com/showthread.php?t=1464711 I had tried this in the past without success (don't remember what techniques I tried), but I thought I would give the "wire trick" a shot. (On reflection, it might be just a mis-remembering on my part thinking that the wire trick would get me into download mode.)
You can read about the "wire trick" here: http://unlimited.io/ I only did the physical part of the wire trick, the timed shorting of the contact. I didn't run any of the software mentioned on that site. (The reason is simple: I wasn't really sure what I was trying to do. I was just trying to get the danged phone to come to life somehow. In fact, last night, I didn't even go to that site. I just remembered how to do the wire trick from reading about it some time ago. I figured that if I got any interesting result, I would study up at that point.)
Well, lo and behold, when I did the wire trick (the timing is tricky, for sure), my Windows PC made that noise like it had noticed a new USB thing. Huh? What? Totally unexpected (by me). Sure enough, Windows device manager showed it with the messed-up-device icon, and properties showed the magical QHUSB_DLOAD.
(At that point, I took a little side excursion and did the same thing with a Linux PC. I could see the phone recognized in dmesg, but no new storage devices showed up, and nothing in dmesg would match the strings that the HTC Unbricking Project script is looking for. So, I went back to Windows. I'm skipping over the frustrating part where I would sometimes go 10-15 minutes without doing the wire trick correctly.)
What Windows wanted was drivers, and it didn't know how to find them. I found and tried these: http://forum.xda-developers.com/showpost.php?p=14386994&postcount=14 (It's really sort of taking a chance installing random stuff on my PC, but you know ... adventure!) After I installed the drivers, Windows recognized my phone as a working Qualcomm something-or-other (failed to make a note of it). It also showed up as a pseudo-serial device on port COM19:.
I was getting pretty excited and started researching the many zillions of threads about what you can do once you have access to a phone in the Qualcomm download mode. Unfortunately, it turns out you can't do much unless you have some secret mumbo jumbo that is likely only had by the hardware vendors. I trolled non-stop through the waters of "maybe someone found some magical binary that does ... something", but no joy. As far as I can tell, there is no known way for us outsiders to do anything productive through this interface on MT4GS or most other HTC phones. Most advice is that if this is all you can get, your next step is JTAG.
Along the way, though, I saw many mentions of a program called QPST (Qualcomm Product Support Tool). If you search around, you can find copies of this tool, though the most recent I found was from 4-5 years ago and runs on Windows. (I didn't look very hard because I wasn't too sure what it did, and I figured I'd look harder for a newer copy if it seemed promising.) With only a little fooling around, I got the tool to recognize my phone on COM19:. There are lots of mysterious subcommands to try. However, pretty much everything I tried failed with a message to the effect that whatever-it-was wouldn't work while the phone was in "download mode". The tool comes with some hex files that might be suitable for downloading to a phone, but nothing for MT4GS (not surprising considering the age of the software). Subcommands included a couple of things with names like "reset device" and "shutdown port". I tried them; they said no-go.
When I was done with all that fooling around, I unplugged the USB from the phone, popped a battery in, and ... as I had done maybe 50-60 times since the Great Calamity ... I tried to bring up hboot. I wasn't expecting it to work, but it did! I quickly put an HTC-signed image on my SD card and popped it in. hboot recognized it and went to work on it. (I was sweating a little bit since I had no idea how much juice was in the battery. I was careless because I didn't expect anything useful to be happening.)
So, I hope someone has enjoyed this tale of adventure. I don't know if any of the assorted things I did actually led to the hboot deciding to show itself, or if it was just random. Whatever, the phone is now re-animated, and I can get back to the original hardware problem I was trying to figure out for this phone: http://forum.xda-developers.com/showthread.php?t=1664506
wjcarpenter said:
Maybe it's due to the Alan Turing centennial stuff, but last night I witnessed some kind of Android phone religious miracle or something. Without (much) warning, my formerly dead phone sprang back to life!
CAUTION: This is a tale of uninformed adventure. If you try the same stuff, instead of the miracle of life, you might witness the miracle of smoke or other calamites.
So, there is hope. I wish I could tell you precisely how I did it, but I was just fooling around with this boat anchor, trying various desperate measures, when it suddenly greeted me with an hboot screen. In case others are in a similar "no harm in trying" state, here is the sort of stuff I was fiddling with last night.
I've tried the HTC Unbricking Project for MT4GS literally dozens separate times: http://forum.xda-developers.com/showthread.php?t=1627881 I've tried lots of variations of ways of getting the phone to be recognized (battery in, battery out; go fast, wait a while; push various buttons, push no buttons; full moon, new moon; ...). All dismal failures, so I've concluded -- rightly or wrongly -- that I don't have the kind of bricking that that stuff can cure.
Just on a whim, I thought there would probably be something I could do if I got the phone into Qualcomm download mode. That goes by various names (which is very confusing), but the phone gets recognized over USB as "QHSUSB_DLOAD". You can read a bit about that here: http://forum.xda-developers.com/showthread.php?t=1464711 I had tried this in the past without success (don't remember what techniques I tried), but I thought I would give the "wire trick" a shot. (On reflection, it might be just a mis-remembering on my part thinking that the wire trick would get me into download mode.)
You can read about the "wire trick" here: http://unlimited.io/ I only did the physical part of the wire trick, the timed shorting of the contact. I didn't run any of the software mentioned on that site. (The reason is simple: I wasn't really sure what I was trying to do. I was just trying to get the danged phone to come to life somehow. In fact, last night, I didn't even go to that site. I just remembered how to do the wire trick from reading about it some time ago. I figured that if I got any interesting result, I would study up at that point.)
Well, lo and behold, when I did the wire trick (the timing is tricky, for sure), my Windows PC made that noise like it had noticed a new USB thing. Huh? What? Totally unexpected (by me). Sure enough, Windows device manager showed it with the messed-up-device icon, and properties showed the magical QHUSB_DLOAD.
(At that point, I took a little side excursion and did the same thing with a Linux PC. I could see the phone recognized in dmesg, but no new storage devices showed up, and nothing in dmesg would match the strings that the HTC Unbricking Project script is looking for. So, I went back to Windows. I'm skipping over the frustrating part where I would sometimes go 10-15 minutes without doing the wire trick correctly.)
What Windows wanted was drivers, and it didn't know how to find them. I found and tried these: http://forum.xda-developers.com/showpost.php?p=14386994&postcount=14 (It's really sort of taking a chance installing random stuff on my PC, but you know ... adventure!) After I installed the drivers, Windows recognized my phone as a working Qualcomm something-or-other (failed to make a note of it). It also showed up as a pseudo-serial device on port COM19:.
I was getting pretty excited and started researching the many zillions of threads about what you can do once you have access to a phone in the Qualcomm download mode. Unfortunately, it turns out you can't do much unless you have some secret mumbo jumbo that is likely only had by the hardware vendors. I trolled non-stop through the waters of "maybe someone found some magical binary that does ... something", but no joy. As far as I can tell, there is no known way for us outsiders to do anything productive through this interface on MT4GS or most other HTC phones. Most advice is that if this is all you can get, your next step is JTAG.
Along the way, though, I saw many mentions of a program called QPST (Qualcomm Product Support Tool). If you search around, you can find copies of this tool, though the most recent I found was from 4-5 years ago and runs on Windows. (I didn't look very hard because I wasn't too sure what it did, and I figured I'd look harder for a newer copy if it seemed promising.) With only a little fooling around, I got the tool to recognize my phone on COM19:. There are lots of mysterious subcommands to try. However, pretty much everything I tried failed with a message to the effect that whatever-it-was wouldn't work while the phone was in "download mode". The tool comes with some hex files that might be suitable for downloading to a phone, but nothing for MT4GS (not surprising considering the age of the software). Subcommands included a couple of things with names like "reset device" and "shutdown port". I tried them; they said no-go.
When I was done with all that fooling around, I unplugged the USB from the phone, popped a battery in, and ... as I had done maybe 50-60 times since the Great Calamity ... I tried to bring up hboot. I wasn't expecting it to work, but it did! I quickly put an HTC-signed image on my SD card and popped it in. hboot recognized it and went to work on it. (I was sweating a little bit since I had no idea how much juice was in the battery. I was careless because I didn't expect anything useful to be happening.)
So, I hope someone has enjoyed this tale of adventure. I don't know if any of the assorted things I did actually led to the hboot deciding to show itself, or if it was just random. Whatever, the phone is now re-animated, and I can get back to the original hardware problem I was trying to figure out for this phone: http://forum.xda-developers.com/showthread.php?t=1664506
Click to expand...
Click to collapse
I really wish I can replicate these results because I am in the exact same situation as you were, except that QPST is not registering my phone via any COM listing. I was using Uniflash, and I was trying to flash a custom ROM. A separate process was created, and boom. Download mode.
mrbubs3 said:
I really wish I can replicate these results because I am in the exact same situation as you were, except that QPST is not registering my phone via any COM listing. I was using Uniflash, and I was trying to flash a custom ROM. A separate process was created, and boom. Download mode.
Click to expand...
Click to collapse
So a quick update: I was not able to restore this bricking via the Unbricking Project. However, I did send the phone off to Mobiletechvideos, and the dude performed a JTAG. And now, IT'S ALIVE!! I had to unlock the bootloader, and get S-Off again, but hey: I got my doubleshot back.
Moral of the story: when all else fails, JTAG.
Related
Ok, I know lots of people brick their phones, and like in my case hard-bricked as well. But everycase is unique but I'd really appreciate if you guys could look over what I did and see if my plan of action is the right thing to do.
So, basically I came across ICS on youtube by chance and it looked to be really cool for my S2. I have no experience with romming and such and I'd only ever heard of it. Then after about only 3 hours of research I set to work to romming it. The instructions said I had to get a clockwork mod to flash the drive to get ICS. I think I messed this up as I'm not entirely sure I unzipped the folder properly to get the .tar. on pda.
So, my phone would turn on but only get to the samsung logo with the warning sign. By this time I was fed up and worried and such and decided it was too much effort and just wanted my phone back. So I set out to put the original firmware back on. I downloaded the stuff and put the in their respective slots, pit,pda and mobile I think. I pushed start and it was if odin had frozen (no progress bar either), I couldn't click anything and the log script in the corner showed nothing.
I was quite annoyed and closed odin and unplugged my phone,put it back in download and such to try again. This time the same thing happened and I unplugged the phone first, Big mistake! My phone went completely black and effectively hard bricked.
Okay that's what happened. I just want advice to see if what I'm going to do is right.
1- Imma try to go through the simple workarounds to try to get my phone back into download mode.
2- This will probably fail, so I will purchase a USB jig from amazon, this will give me 3 potential results
one. My phone will get back into download mode and there will be no warning sign under the samsung logo and custom counter at 0.
two. My phone will get back into download mode but there is still the warning sign and the custom counter is at 0
three. Nothing will happen or my counter will be at one
3- okay so if scenario one happens I will send my phone to samsung and they should repair as they have already told me through e-mail they believe it to be a motherboard problem
scenario two, I will send my phone to vodafone,as I've learnt from the forums their techies should not care as much about that kind of thing.
scenario three, I will send my phone to mobile tech videos in Texas from the UK as everyone seems to trust them and they look pretty legit.
Okay, so that's basically my plan of action. All I want is for you guys is to just go "yeah, good idea thats probably right" or show me what I've misjudged or if you are aware of another option for me.
Thanks,
Adam
Bump, please I know some of you guys can help me out
Hi everyone,
I'm experiencing really wierd behaviour with my HTC Desire S. I'll try to tell the story as it happened, so you may have the best grasp on what's happening to me. Here's the thing: yesterday, I charged my HTC on the wall plug as almost every night (y'all know how it is with smartphones, always needing to be charged ). When I unplugged it on the morining, the green LED stayed on. Not cool. I can't really remember if it was turned on and stuck or already turned off at that time, but I had to reboot the phone. Okay, that can happen, phones have to reboot sometimes.
And then, it did not boot. Instead, it was stuck on the bootscreen. I looked around on the internets, but people seemed to have boot loops or devices stuck after the "quietly briliant" part. Actually, mine was stuck before that part. It didn't even play the funny sound and show the fancy animation: it was stuck on the blank screen with only the HTC logo.
I tried many things, like praying pagan gods and removing the battery, let it cool for a while, boot and wait to see what happens for more than 30 minutes, boot it while plugged on the wall plug... I think I was about to get to the "I'll have to make a factory reset, then" line when I tried to see what dmesg would tell me if I plugged the phone on my computer. Note to self: always try to plug to computer. It did boot completely. The victory dance was almost completed when I was invited to enter my PIN code. My touchscreen did not respond. Damn.
So I had to reboot. Again had to remove the battery (I don't like that, but what choice do I have?). Now it always boots completely (that's a good start), but my touch screen seems completely unresponsive. I can't access anything, can't enter my PIN code or unlock the phone when there's no SIM.
That's where this forum comes in: I've not given up. You see, my phone has USB debugging activated (yeah I know, the thread's title spoiled all the story). I'm pretty sure this means adb can help me in some way to troubleshoot my device. adb shell gives a nice UNIX-like shell, yay, that is relevant to my interests.
My phone has never been rooted. I've looked into it (that's why USB debuging was activated), but I wasn't 100% confident it would work, so I gave up before ending up bricking my phone (duh, too late, haha). It's running the last Gingerbread version distributed by HTC in Belgium (2.3.5, I think, without any certainty), with the last Sense version related (could it be 3.0.3?).
tl;dr: Unrooted phone with unresponsive touch screen, debugging mode enabled, trying to find what's wrong.
So here's what I'd like to know: is there any way to try to force start my touch screen with the help of adb? Where's the related log, the one that should display the error(s) that occur(s)? Should Bill Murray play in the next Batman? If root is needed, do I have a way to use a temproot exploit in order to fix my phone once and for all?
Any attempt to help will be greatly appreciated. This is my first post here, I hope it's clear enough, and not too nooby for you guys. Also, that I didn't break any rule (I watched/lauged at that video about noobs to xda). Btw, I'm quite confortable with UNIX shells, so don't avoid cli-related answers if that may happen to be helpful. Also, I'm not at home right now, but I'll follow this thread with a lot of interest anyways. I'm back on a regular connection next sunday.
Have a nice day! And sorry for the long post (but believe me, I'm even more sorry to admit I can't investigate further on my own, now that is frustrating).
Okay, I'm back.
It makes no sense. I let my phone on for a few days, then suddenly, probably out of boredom removed the battery, put it back and rebooted. I distractingly tried to unlock it… and it worked.
I have absolutely no single clue on what happened. And I'm still quite concerned, because this means it can happen again without any warning.
I'm gonna give a shot at HTC's support in order to ask them what I can do to locate the problem if there are traces. I'd really, really like to read all the logs (and logcat didn't show anything interesting).
If anyone has a suggestion, feel free to shoot it. I'll try to keep this thread updated in case someone has the same problem.
Duh, just got an anwser from HTC's support. Totally useless, they told me to try to reboot in Safe Mode in order to see if the problem happens again. Well, even in normal mode it has not failed for two days. GJ, guys.
I'm really willing to meddle in my system in order to see what could have gone wrong. I'd especially like to see if there is any way to see whether there are HW faults or not, since I'm suspecting a temporary TS chip failure, which can happen again at any moment. I'll be reading some documentation about Android's system and its logs.
Yeah, I know I'm talking a lot alone, but if someone ever has the same problem, he might be able to see what I've gone through, so I'm documenting as much as possible. =)
adb bugreport
Been a watcher on the forums for awhile, now I actually had to sign up and get some help, LOL.
Anyway, dropped my s2 skyrocket, noticed that it kept trying to reboot every now and then when I used it the same day. The next day, I plugged it in in the evening, and shut off, rebooted, but the screen would go black and the phone would vibrate with 2 seconds in between vibrations. It gets to the "Samsung" word, then the screen goes black in the style of an old tube TV (with the thin white line at the end). Then the vibrations start. So far a useless phone. Took it apart and checked connections carefully (I'm used to working with processor boards quite a bit).
What do you guys suggest? Damaged memory? Should I attempt to reflash? Stuck power button (seemed ok, though)? Bad screen?
Well, probably some kind of physical damage, but hard to say. Anyway, you posted in the forum for SGH-I777 but you have the SGH-I727, so I would suggest that you look in the correct forum.
creepyncrawly said:
Well, probably some kind of physical damage, but hard to say. Anyway, you posted in the forum for SGH-I777 but you have the SGH-I727, so I would suggest that you look in the correct forum.
Click to expand...
Click to collapse
Oh, thanks for the heads up. Yeah I just figured out that the i727 isn't in "Top Devices" or "Legacy," so you have to go to all forums. Ugg. Already moved. Thanks to whoever notified mod.
Anyway, yeah, any help would be AWESOME. What physical damage would prevent booting past the "Samsung" screen and default to a black screen that intermittently vibrates?
I'll be honest, if ur asking that question probably something u don't have the current skill set to fix. Try to Odin back stock, but if it started post-drop you may be SOL and in need of a new phone.
Got it into download mode after multiple failed attempts. Each time I would get it into download mode, the screen would shut off after about 5 seconds of being on. I tried several combinations of plugging it in first, then installing the battery, or holding down the button while I plugged it in with no battery, etc. I had just given up after getting it into download mode briefly for the 20th time, when I gave it one more go while rocking the on and off button. Technically that is recovery mode, but I let off right before plugging the phone in and it hit download mode and stuck.
So what I am thinking is the power button got jammed internally. I have heard of it happening on other forums. Even though it looks good and clicks upon external examination, the pressure circuit on the inside might be in contact. Anyway, just one theory.
For future though, I did discover that you don't HAVE to have the USB unplugged prior to getting into download mode. On the contrary, a power source must be present in order to register that the keys are pressed PRIOR to initiating USB input. Thus, you can actually remove the battery, plug in the USB (power source), then hold the volume keys while replacing the battery. Goes into download mode that way, too.
Will keep you guys updated. Might need a bit more help if the phone starts acting up again.
At this point, if the Download mode still holds ok, should I consider CyanogenMod, or is it easier to get back a good ROM from stock?
icenight:
Thanks for the reply. I don't understand much about smart phones or how they work, but trust me when I say I have had AMPLE experience with electronics, circuit boards, hardware, etc., particularly in the computer/laptop world. I code quite a bit of websites, and understand almost all things networking and OS. Just never really got into it with the phones.
Getting super excited to see the sheer amount of modding you can do though. Would love to break into a hardware modding world if it ever comes available. That's where it's at with electronics for me.
Well glad u got it sorted, lucky guy you are lol.
As for boards and the like, if it didn't work I would've suggested replacing the motherboard and/or power daughter board. But for a skyrocket may not be worth the money.
Since you're a hardware guy, maybe mess around with the phone and JTAG? Finding a way to unbrick without it would be very helpful
Since the problems started after a physical damage (fall) , I wonder how would Odin or wipe and flash might work !
Definitely a hardware damage...
Yeah, it kinda puzzled me, too. I believe the power button might have been internally stuck, but that's just one idea. Could have been a loose connection, too.
Can you lose some solid state memory with firmware on it, but the SS memory still be OK to right another copy on?
More than likely it was your power button
Sent from my SAMSUNG-SGH-I727 using xda premium
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