Database Info

Transformer won't turn on /:

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.

Help! I hard bricked my phone!

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.

[Q] Nexus S bricked. Now what?

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

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

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

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

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

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

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

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

Digitizer works in TWRP recovery but not after normal boot

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

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

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

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

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

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

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

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