Well here's a good one for you xda folk... So here is what happened in a nutshell... I unlocked my bootloader, flashed 4ext and supersu, then booted my phone fine. I didn't want to s-off. So I skipped the jbear process. After messing around and installing some apps I decided to flash a "modified" stock Rom. That booted fine but I didn't want to keep the Rom. I restored back and then I was in a bootloop. So I relocked the bootloader and flashed the RUU through fastboot. It booted fine. Then I reunlocled rerooted and attempted s-off but sadly failed hard at it. The phone was bootlooping from that so I then relocked the bootloader and did the RUU process again. However this didn't fix the boot loop so I ran it twice more. And it booted up. My sd card was unreadable and I formatted it and it works now. Later that night before I went to bed I always change my dead battery with a full one. ( I have a dock battery charger) And when I attempted to power on the phone was yet again, bootlooping. I booted into bootloader and selected recovery. It went to a screen with a triangle and android guy then a loading bar with a picture of the sd card at the end. It fixed and booted but wiped everything. I powered down today and powered back up fine. I am afraid to remove the battery. What can cause the phone to bootloop by removing the battery??? Any help is most gratefully appreciated.
Sent from my PG86100 using xda app-developers app
Nothing?
Sent from my PG86100 using xda app-developers app
AGoogleUser said:
Well here's a good one for you xda folk... So here is what happened in a nutshell... I unlocked my bootloader, flashed 4ext and supersu, then booted my phone fine. I didn't want to s-off. So I skipped the jbear process. After messing around and installing some apps I decided to flash a "modified" stock Rom. That booted fine but I didn't want to keep the Rom. I restored back and then I was in a bootloop. So I relocked the bootloader and flashed the RUU through fastboot. It booted fine. Then I reunlocled rerooted and attempted s-off but sadly failed hard at it. The phone was bootlooping from that so I then relocked the bootloader and did the RUU process again. However this didn't fix the boot loop so I ran it twice more. And it booted up. My sd card was unreadable and I formatted it and it works now. Later that night before I went to bed I always change my dead battery with a full one. ( I have a dock battery charger) And when I attempted to power on the phone was yet again, bootlooping. I booted into bootloader and selected recovery. It went to a screen with a triangle and android guy then a loading bar with a picture of the sd card at the end. It fixed and booted but wiped everything. I powered down today and powered back up fine. I am afraid to remove the battery. What can cause the phone to bootloop by removing the battery??? Any help is most gratefully appreciated.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
What a long story
there is good tutorials in the forum to get s-off , follow them , my HBOOT was 1.49.0018 , an i got s-off easily , and bootloops got disappeared
Sajijun said:
What a long story
there is good tutorials in the forum to get s-off , follow them , my HBOOT was 1.49.0018 , an i got s-off easily , and bootloops got disappeared
Click to expand...
Click to collapse
I plan on s-off but I just want to take this back to sprint to get the firmware reinstalled. The front camera is done for as well and that's a hardware problem. My upgrade is in Feb so I'm just getting a new phone but I just wish I knew what is causing bootloop from a battery pull.
Sent from my PG86100 using xda app-developers app
I brought my phone to sprint. Dun dun dunnnn. I explained the problem and they said, "Sorry but your screen is cracked so we can't do anything." I said Dafuq??? I know I have insurance and all. I just wanted them to reflash The firmware but I guess they can't due to a crack in my screen. (They said it could have been when I dropped it. But I bought the whole front faceplate and installed it myself cause my LCD broke. I have a white housing but everything else is black. So maybe they noticed. I don't know. Just gotta wait a month.
Sent from my PG86100 using xda app-developers app
AGoogleUser said:
I brought my phone to sprint. Dun dun dunnnn. I explained the problem and they said, "Sorry but your screen is cracked so we can't do anything." I said Dafuq??? I know I have insurance and all. I just wanted them to reflash The firmware but I guess they can't due to a crack in my screen. (They said it could have been when I dropped it. But I bought the whole front faceplate and installed it myself cause my LCD broke. I have a white housing but everything else is black. So maybe they noticed. I don't know. Just gotta wait a month.
Click to expand...
Click to collapse
Cracked screen. Broken camera. White housing. It's no wonder you are having problems. There's usually more to the story than what we see here.
Why didn't you just get it replaced if you have insurance? Good luck with your new phone when you get it.
ramjet73
Yea I'm just going to wait ramjet. Although now I can pull and switch batteries without bootlopping. Must-have been fixed when I chose recovery.
Sent from my PG86100 using xda app-developers app
EDIT: Nevermind...pulling battery still results in a freaking bootloop. This phone...smh. Never had a problem before i failed the jbear soff. Its to bad how much i love HTC, and i am deffinitly not getting one february. Galaxy Note 2 here i come. Goodbye HTC
AGoogleUser said:
EDIT: Nevermind...pulling battery still results in a freaking bootloop. This phone...smh. Never had a problem before i failed the jbear soff. Its to bad how much i love HTC, and i am deffinitly not getting one february. Galaxy Note 2 here i come. Goodbye HTC
Click to expand...
Click to collapse
There is a lot to be said for the other vendors, but it sounds like you brought all this on yourself. It's not HTC's fault you broke the screen, swapped out hardware, and failed an unsupported hack. Any other phone would act the same way given the circumstances.
As far as your actual problem, I wouldn't be surprised if you shorted out the phone when attempting to ground out to the SD slot. If you accidentally connect the wire a bit above the case, you'll instead short out to some internal phone circuitry. You can see some leads in there if you remove the shell. That's just a guess, so take it with a grain of salt.
Since nothing else seems to be working, I would once again attempt to go for s-off. It's not unheard of to have to try it dozens of times before it works, so just keep at it. Try starting from the beginning. Verify you're still unlocked, reinstall twrp/4ext, do the s-off project, change your hboot, flash the latest Sprint radio firmware if you want, all of it. Don't skip a single step. Treat it as though it's a brand new phone and you're ready to start rooting it.
If that doesn't work, maybe someone else has some other ideas. But I don't think there's anything more that can be done beyond that.
Related
This time I have really f***ed up guys. I really think this time I have actually bricked my Thunderbolt. I was on Bamf Remix 1.63 I believe and everything was running great. I was obviously rooted also. I was bored and decided to flash Protekks Battery Sipper Kernel. Right after I flashed it, the phone would not boot. I pulled the battery and booted up again and it got stuck in a boot loop. So after a few tries I finally got it to boot into the bootloader. I got into recovery and tried to flash a backup and it rebooted in the middle of restoring it. I tried that a few more times. I then let the battery die. Then I charged it up a lot and tried to power it on and got nothing. The screen will not even turn on. When plugged into my computer it sometimes vibrates and my computer detects it and then my computer makes the sound like it was disconnected. I think it is still stuck in the boot loop with the screen off though. BTW the charging light does light up when plugged in. I tried the stock and extended battery to make sure it was not a battery problem. I finally called up Verizon and after I told them it would not turn on he said he is shipping me a free replacement. I told them that after a OTA update the phone would not boot. He warned me that if there is any evidence that the phone was rooted or hacked, I would be charged the retail price for the phone. That is really the only thing I am scared of. Any help would be greatly appreciated!!! Sorry for the long post, I wanted to get in all the details that I could.
Thanks
Adam
Try putting it in download mode and flash back to gongerbread using odin
Sent from my GT-I9000 using XDA Premium App
srkoza said:
Try putting it in download mode and flash back to gongerbread using odin
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Wtf? This isn't Samsung. OP do you bootloop in bootloader? I recommend you go to the irc and give them any info you can.. you will probably end up flashing a stock ruu through the bootloader but first go to irc.
Sent from my ThunderBolt using XDA Premium App
Thanks for the quick reply! How would I get into download mode. And I was on froyo before.. Shouldn't I download a froyo based rom?
Yeah I did not think we have Odin for HTC phones, and I already have the stock zip file on my MicroSD card but my screen will not turn on at all. I can not get into anything. Any advice?
Talk to jcase. Hopefully you have some adb knowledge.
Sent from my Thunderbolt using XDA Premium App
itsdubai said:
Yeah I did not think we have Odin for HTC phones, and I already have the stock zip file on my MicroSD card but my screen will not turn on at all. I can not get into anything. Any advice?
Click to expand...
Click to collapse
Go to irc.. someone with actual Dev experience can help you there try #thunderbolt
Sent from my ThunderBolt using XDA Premium App
OK thanks for the replies. Do you think the Verizon warranty center people will actually go to the trouble of getting it to work and then charge me full retail for a new one if they see it is rooted. I already have the stock zip on the SD card so when it does boot up, it will return everything to stock. I have read online that some people have been charged retail because there phones have been rooted but most of them have gotten away with with it..
itsdubai said:
OK thanks for the replies. Do you think the Verizon warranty center people will actually go to the trouble of getting it to work and then charge me full retail for a new one if they see it is rooted. I already have the stock zip on the SD card so when it does boot up, it will return everything to stock. I have read online that some people have been charged retail because there phones have been rooted but most of them have gotten away with with it..
Click to expand...
Click to collapse
I think you're almost certainly fine. It's a lot of work and time for big red over one phone. Plus, your etf is less expensive than a replacement device
Sent from my Thunderbolt using XDA Premium App
thanks for the response man. etf= early termination fee? I might not have said in my original post but they are sending me a free replacement device. The rep on the phone specifically said that if they find my phone to be rooted or hacked, that I will be charged around 629$ for the refurb replacement. I really cannot afford that (
Call back and tell em you accidentally dropped it out of moving vehicle and that it was run over 5 times...and that it was raining outside. Then pay your deductible.
ddgarcia05 said:
Call back and tell em you accidentally dropped it out of moving vehicle and that it was run over 5 times...and that it was raining outside. Then pay your deductible.
Click to expand...
Click to collapse
I decided that if I ever bricked, that I'd post on here asking what horrible things I should do previous to sending it in to get a replacement. Then post pics. XD
Sent from my Thunderbolt using XDA Premium App
Please check out this thread when you get a moment, might help the community and we would greatly appreciate it.
http://forum.xda-developers.com/showthread.php?t=1130407
Sent from my ADR6400L using XDA App
I got out of a bootloop on my friend's Insipre 4G (which is very similar to the TB) by mounting the microSD on my computer, and then putting a stock ROM on it. I had to rename the stock ROM PG98IMG (PG05IMG on Thunderbolt), and flash it through the bootloader, but it did work.
Thanks for the post man but the Thunderbolt does not show any signs of life at all besides the flashing orange LED at the top blinking and the computer detecting it on and off every 5 minutes. The stock zip is already on the SD card so when it finally boots up it will flash and hopefully Verizon won't charge me out the @ss for a replacement.
powered on! for a second...
UPDATE: I just had it hooked up to my laptop and it booted on the the white HTC screen and I almost had a heart attaack :O but then it powered off and wont come back on. FML
itsdubai said:
UPDATE: I just had it hooked up to my laptop and it booted on the the white HTC screen and I almost had a heart attaack :O but then it powered off and wont come back on. FML
Click to expand...
Click to collapse
how long have you had your phone and what hardware revision was it? did you try to run the RUU yet?
i think some people just got a batch of faulty phones because this doesn't seem to affect many.
I highly doubt verizon is going to receive your broken phone and boot it up and it will magically work. The only way it will auto-update is if they boot it into HBOOT. If they somehow just power it on it won't automatically apply anything. Keep that in mind. But I really wouldn't worry too much about it. If they charge you call them and tell them wtf I wasn't rooted. I don't even know what that means lol.
I have had the phone since the very first days it was released. Another slight annoying thing I have had happening prior is the glue on the screen has not been holding it down very well and and I can easily get a nail under it. And it wont let me do anything. I have a Droid X as a backup for now but I miss my beast
itsdubai said:
I have had the phone since the very first days it was released. Another slight annoying thing I have had happening prior is the glue on the screen has not been holding it down very well and and I can easily get a nail under it. And it wont let me do anything. I have a Droid X as a backup for now but I miss my beast
Click to expand...
Click to collapse
that's what im starting to think as htc has since released a revision 2 thunderbolt. i know as i just bought mine a few weeks ago. im wondering if the faulty phones were version 1 phones and have since been fixed. i also do not experience the high battery drain most of you guys do either.
I am having lots of issues with my phone, touchscreen going crazy, touchscreen locking up until I turn the screen off and back on, phone randomly rebooting and then locking during reboot requiring battery pull, etc, etc. I have tried wiping everything, even using superwipe and tried several different roms and stock and still having issues. I am going to take it to Sprint but I am sure the first thing they are going to do is to apply the latest updates, but I don't want that because I don't want HBOOT 1.5. Any way around this?
I was having a similar issue and i installed a new kernel with a new ROM that works great together. I'm not having any more issues. Try a kernel that marries your ROM.
My money making shooter in 3D.
Just tell then not to apply the updates.
aFoodStampBaby said:
I was having a similar issue and i installed a new kernel with a new ROM that works great together. I'm not having any more issues. Try a kernel that marries your ROM.
My money making shooter in 3D.
Click to expand...
Click to collapse
I don't think that is the issue. I have tried many different kernels and ROMs and even completely stock and still having issues.
Sent from my PG86100 using xda premium
I'm probably screwed regardless as they will probably want to replace the device. If a full wipe and return to stock didn't fix it I don't know what else they can do. I see that you can now flash Roms with hboot 1.5. Is there any reason I should be trying to avoid it anyway?
Sent from my PG86100 using xda premium
i have hboot 1.5 and avoided rooting for a long time after i got my refurb that was shipped with it. I haven't had any problems the only thing that is different is you can't currently gain s-off so you will need img gui from market to flash kernels with out having to plug your phone up to a computer and booting into recovery through command but i haven't had any issues. just a small annoiance of having the plug the phone o a pc when i want to flash a new ROM
I have a friend with a non rooted phone and his digitizer went nuts after the most recent update(VOICEMAIL) sound like the same issue. He took his into Sprint and they confrirmed it was the update that fried his digitizer. He asked me about it and I said never heard of that issue, I told him I will check. Looked on XDA and here it is. Unroot and take it back to sprint. He is receving a new 3vo tommorow.
Sent from my PG86100 using xda premium
Mine does this same thing .. no matter which ROM setup I use. However it only does it when I have bad service, like the radios are causing it idk its driving nuts at times LOL
Sent from my PG86100 using XDA App
bnl552 said:
I am having lots of issues with my phone, touchscreen going crazy, touchscreen locking up until I turn the screen off and back on, phone randomly rebooting and then locking during reboot requiring battery pull, etc, etc. I have tried wiping everything, even using superwipe and tried several different roms and stock and still having issues. I am going to take it to Sprint but I am sure the first thing they are going to do is to apply the latest updates, but I don't want that because I don't want HBOOT 1.5. Any way around this?
Click to expand...
Click to collapse
Doubtful you won't get the HBOOT update if you take it in; try one last thing: Wipe everything and reformat your SD card, there's another thread somewhere around here that was talking about the SD card being a culprit for those type of issues.
If you're STILL having problems, then bite the bullet, you can ask for them to not update your phone but most of the time (read: not all of the time) they'll either refuse to troubleshoot your phone or will update it anyway.
Hope for the best, prepare for the worst.
Bondue said:
i have hboot 1.5 and avoided rooting for a long time after i got my refurb that was shipped with it. I haven't had any problems the only thing that is different is you can't currently gain s-off so you will need img gui from market to flash kernels with out having to plug your phone up to a computer and booting into recovery through command but i haven't had any issues. just a small annoiance of having the plug the phone o a pc when i want to flash a new ROM
Click to expand...
Click to collapse
You don't need to plug in to the pc to flash a new rom. You can do everything with hboot 1.50 except change kernel. And as you mentioned you can use flash image GUI. I never connect to pc anymore.
Sent from my PG86100 using XDA App
JayDaKissEP said:
You don't need to plug in to the pc to flash a new rom. You can do everything with hboot 1.50 except change kernel. And as you mentioned you can use flash image GUI. I never connect to pc anymore.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
agree, no need for a pc anymore, kernal is changeable too,
http://forum.xda-developers.com/showthread.php?t=1192527
lchupacabras said:
Doubtful you won't get the HBOOT update if you take it in; try one last thing: Wipe everything and reformat your SD card, there's another thread somewhere around here that was talking about the SD card being a culprit for those type of issues.
If you're STILL having problems, then bite the bullet, you can ask for them to not update your phone but most of the time (read: not all of the time) they'll either refuse to troubleshoot your phone or will update it anyway.
Hope for the best, prepare for the worst.
Click to expand...
Click to collapse
SD card may have been the issue. I haven't had access to a computer to backup and format the card so i just removed it. So far its working fine, but its only been an hour or so.
Sent from my PG86100 using xda premium
I am not a newbie to rooting or at least I think that
But, my EVO 3d has been acting very wierd since rooting in december. I used the HTC method with hboot 1.5 and used reliable roms (infected, miui, mikrunny)
It has never been the same, I have to periodically reflash new roms because the phone would freeze up, ghosts start typing on the touchscreen, certain part of the screen I can't touch, pressing power button would wake the phone and start the music
I have used various recoveries (twrp 1, twrp 2.0, twrp touch, cwm 4, cwm 5, cwm touch) with most stable being twrp 1 except for the fact that turning off the phone and restarting it causes it to be stuck on the HTC splash screen.
Just to explain the severity of the situation, the volume and power button have almost been fully pressed inside the phone from starting recovery and bootloader menus, the back case tabs are broken
I am soo bogged down with the phone, that I just want STOCK HTC software with 100% reliability and nothing else.
Sounds like your digitizer is going. I had the same problem. Bring it in and they will either replace the digitizer or the phone.
Sent from my PG86100 using Tapatalk 2
There is a sticky for going back to 100% stock and s-on. Or u could wait for the next official update and just take it
Sent from my PG86100 using XDA
Yeah that's what I was wondering, can I just accept the newest HTC update and be "fully back to stock"
i personally belice its either you or the phone ( most likely the phone) doing weird things..... just go stock and get it replaced brother man
ktrotter11 said:
i personally belice its either you or the phone ( most likely the phone) doing weird things..... just go stock and get it replaced brother man
Click to expand...
Click to collapse
Ya don't say?
Sent from my PG86100 using XDA
Just take it to sprint, its your digitizer, I had to have mine replaced saturday.! Its simple and those ppl at sprint barely know what rooting is, let alone what an unlocked bootloader or custom rom is.... js!
ognimnella said:
Just take it to sprint, its your digitizer, I had to have mine replaced saturday.! Its simple and those ppl at sprint barely know what rooting is, let alone what an unlocked bootloader or custom rom is.... js!
Click to expand...
Click to collapse
I had yo get mine replaced 2 weeks ago
Sent from my PG86100 using xda premium
OK. This might sound like a dumb question... But when was the last time you pulled the battery and left it out for thirty seconds? An all voltage clear is sometimes all it takes. Also... Do you use a screen protector?
Sent from my PG86100 using Tapatalk 2
personal experience
I had the same problem with the ghost typing. the problem was the digitizer. If you have insurance on the phone then set it back to a stock ruu and bring the phone in to sprint. this is what i did and i got a new phone overnited and had it the next day.
Its as I feared I dropped my phone in water like a month after I got it on launch day, I just didnt want any bias if I told you guys first.
BUT the problem was NEVER there when I had stock HTC, it only started after rooting since december, where can I buy this digitizer?
I do have a screen protector so I'll remove that and put a new battery in, maybe it'll fix the problem
ninten5 said:
Its as I feared I dropped my phone in water like a month after I got it on launch day, I just didnt want any bias if I told you guys first.
BUT the problem was NEVER there when I had stock HTC, it only started after rooting since december, where can I buy this digitizer?
I do have a screen protector so I'll remove that and put a new battery in, maybe it'll fix the problem
Click to expand...
Click to collapse
that literally is what happend to me. all was well for a little bit but then it got out of control. Good thing I got it at BBY Mobile and they got it replaced with a new one. Luckily it had HBOOT 1.4
Sent from my PG86100 using xda premium
Update: I have taken off the screen protector and there was some water left in it
I have installed a new battery too and most of the ghost touching problems have gone away.
But I have a new issue, I cannot get any rom to reboot for some reason, I have tried all the recoveries (ext4, twrp, cwm) I have to flash boot.img from fastboot if I want to load the rom after turning off the phone. Is there a solution for this problem?
ktrotter11 said:
i personally belice its either you or the phone ( most likely the phone) doing weird things..... just go stock and get it replaced brother man
Click to expand...
Click to collapse
You sure? It could be one of the ghosts doing it.
S3nt from my 3D wond3rland
So, long story short, took the Phone into Sprint so they could look at my headphone jack (was cracked and left ear bud would constantly cut in and out) because its acting up.
Gave the Tech the phone without the battery in it (since he didn’t need to power up the device to clearly see the headphone jack has a huge crack in it) but I left my SD card installed. As he was walking away, I asked him if I could remove my SD card and he let me, then seen that I gave him the phone without a battery. So, I ended up giving it to him (praying he didn’t turn it on and see ViperBoys sick ass ROM booting up) and he accidently pressed the power button turning the phone on. Promptly short after, he removed the battery when the phone was on the HTC screen, didn’t even get the boot animation. I was like OHH $h!t, that gonna mess up my phone & sure as $h!t, it did… Just loops in and out of that screen resetting each time with a little vibrate then looping.
I can get into Fastboot and use ADB, I’ve flashed RUU’s, put Stock image on root of SD and let recovery restore (losing my CWM & my HBOOT 1.400), unlocked, relocked, wiped, thrown, and screamed at it with no luck.
I did do a CWM backup before even setting foot in the Store, so I do have a backup. The 1st thing I tried was restoring it through CWM recovery and that didn’t stop the looping. I can still get into fastboot via power + vol down and adb functionality is still there.
HBOOT is 1.50 and s-on is enabled..
Been reading through threads since lunch and tried many different solutions without success. It seems once a phone is this far gone, people stop responding.
Anyone have any ideas?
New phone will be here tomorrow (free of coarse courtesy of Sprint insurance) but I’ve been without a phone all day and most of yesterday. I’d like to get this one back to stock and booting before I trade it in for the replacement tomorrow
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
yousefak said:
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
Click to expand...
Click to collapse
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
lessegr said:
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
Click to expand...
Click to collapse
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
yousefak said:
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
Click to expand...
Click to collapse
BUMMER! In case the question comes up I ran "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed" and it ran just fine.
Hmm, hardware issue. Dont see how I can check for that if it doesnt boot.
Guess I'll just have to wait for the new Phone
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
jdeoxys said:
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Click to expand...
Click to collapse
The HTC unlock went as expected. Followed the directions to the "T", then relocked, checked in fastboot (not that I could check anywhere else, LOL) and the phone says "*** RELOCKED***". Ran 2.17.651.5 RUU successfully to the finish. Still looping
WEIRD!
DarkManX4lf said:
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
Click to expand...
Click to collapse
Because I just want to know WTF happened!!! Had this Phone since release, abused\used the hell out of it by flashing ROMs constantly, restoring backups, tethering like crazy, emailing, texting, FBing...
No reason for it to crap out on me from a simple mistake, not even of my responsibility, lol!
The only issue I've had with this Phone is that damn headphone jack 1/2 way failing..
Got new phone, terrified to even think about trying to flash new ROM though
lessegr said:
Got new phone, terrified to even think about trying to flash new ROM though
Click to expand...
Click to collapse
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Threevo said:
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
DONT TEMPT ME DAMMIT! lol! Just been without a phone for almost 3 days. I'm also seeing a lot of new threads about people experiencing what I've gone through.
Woops, sprint\HTC! once again rooted, and running viperROM.... SWWWWWET!
HBOOT 1.5 and s-on is a *****!
Not to mention... But in Linux, I never got revo recovery to flash... You can do it in windows just do it via fastboot.
Took my Orig cwm bsckup "recovery" & "boot" .img and threw them @ the phone via command prompt.
After cwm was restored, I restored my 4\29\2012 backup that I made before I entered the Sprint store, now my phone is back to the exact same way
It was. Pretty Damn sweet!
So much info here!! I'm truly thankful!!!
Sent from my PG86100 using xda premium
I found a guy via a local classifieds website selling a Thunderbolt with clean ESN/MEID. He explained he got the phone wet (aparently it didn't get wet enough to trigger the moisture stickers), it worked for a few days and then would no longer power on.
I live 30 miles away from him, so I had a family member meet this person and pay the $20 for the phone. I had him make sure it came with the 32gb micro sd and it did! He is coming to my house this weekend, so I'll get the phone then.
I'll try my wifes Thunderbolt's charger and battery to see if either of these are the problem, but if it is water damaged, would the rice trick do any good at this point? Would leaving it on a heater vent do any good? Any other tricks to try?
Water's already done it's damage, vent nor rice would help.
Maybe open it up and check the internals
You'd have to replace it completely from the logic board, up.
A pain, but if you're that patient, you could repair it. But you don't want to put more money into it than its worth. Especially if its not worth a lot.
Sent from my ADR6400L using xda premium
Open the phone up - remove battery and cards.
disassemble according tot he videos on youtube. remove the screen from the motherboard (its just two cables.
Soak the motherboard in 98% isoproopyl alcohol. let it soak (it can't hurt) and try cleaning the water deposits with a soft brush. The alcohol will displace the water and it evaporates cleaner than water. Make sure the motherboard is out of the plastic frame of the phone when you do this.
Then put it all together and try charging.
As a last resort u soul try taking to a nationwide chain called Cell Phone Repair (CPR). I took my Thunderbolt that got soaked in a heavy rainstorm and they took it apart, treated it with something (for all I know, it could have been rubbing alcohol as the previous poster suggested ) and returned it to me good as new for $100.
Sent from my cm_tenderloin using xda app-developers app
This is exactly why I posted this question, I figured someone would have something I can try.
Thank you, thank you, thank you, I'll let you guys know if it works!!!
No worries, btw, there are dis-assembly videos floating around. eg:
http://www.youtube.com/watch?v=zdPiT82gWKw
and
http://www.youtube.com/watch?v=ywDkNUxULSQ&feature=fvst
It appears that if you (1) get something that helps you pry it apart (without damaging the phone) and (2) take your time and go step-by-step then taking the phone apart yourself is doable. That said, it might be worth it to have someone who has done a few tackle it if you aren't comfortable with the process shown in the videos. Good luck!
Ok, so I got the phone today. I used my wifes Thunderbolt battery and the phone powered up (YAY!!!) however the touchscreen doesn't seem to work and as soon as the screen goes to sleep, I can't get it to turn on again without pulling the battery and restarting.
My question is...I've read that rooting the phone can cause this issue and noticed that there was a "clockworkmod" folder. Does this mean the phone was rooted?
UPDATE - I just restarted the phone again and as soon as I saw the unlock rainbow thing (for lack of the right word) I was able to drag it down and unlock the phone and it immediately went to a screen asking me to pick my language, both English and French were selected and it seemed to be frozen and eventually the screen went to sleep. I've got the phone plugged into my computer because now it seems to want to charge it's own battery (YAY) and I noticed that the 4 buttons at the bottom of the screen were still illuminated after the screen went to sleep. Then I noticed that the lights at the bottom went out, so I pressed the power button and the phone came on and I was able to use it for about 4 seconds at which point it stropped responding to touch again.
Does this seem like a software issue or should I just replace the digitizer?
I was able to get it to work long enough for me to enable usb debugging, so tomorrow I'll download a program that lets me use my pc as the phones screen. I figure if I can use the phone through the computer without it locking up, then I know for sure it's a digitizer issue rather than a software issue.
Somebody correct me if I'm wrong or should try something else.
I would try reflashing a new ROM and go from there. Can u boot into recovery? If it is a touch recovery, u could test digitizer there.
Sent from my MB860 using xda app-developers app
JPBeard21 said:
I would try reflashing a new ROM and go from there. Can u boot into recovery? If it is a touch recovery, u could test digitizer there.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
When I hold the "volume down" and "power" I get the following info:
LOCKED
MECHA XD SHIP S-ON (THIS MEANS IT'S NOT ROOTED...CORRECT???)
HBOOT-1.05.0000
MICROP-/
RADIO-1.49-00-0406w_1
Jul 19 2011, 14:51:08
HBOOT
VOL UP
VOL DOWN
POWER
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
HBOOT USB
IMAGE CRC
vetteguy112233 said:
When I hold the "volume down" and "power" I get the following info:
LOCKED
MECHA XD SHIP S-ON (THIS MEANS IT'S NOT ROOTED...CORRECT???)
HBOOT-1.05.0000
MICROP-/
RADIO-1.49-00-0406w_1
Jul 19 2011, 14:51:08
HBOOT
VOL UP
VOL DOWN
POWER
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
HBOOT USB
IMAGE CRC
Click to expand...
Click to collapse
No, its not rooted at all.
Delete the clockworkmod folder and ANY PG05IMG files from the root of the SD. In fact, I'd reformat the SD entirely.
Sent from my ADR6400L using xda premium
---------- Post added at 11:51 AM ---------- Previous post was at 11:37 AM ----------
Or might I add that because it says S-On doesn't mean that its not rooted. S-On just means the bootloader is locked; S-Off means the bootloader is unlocked. If you can, download root checker from the playstore and see if it gains root access... which I doubt it will, but you never know.
There are phones out there with S-On that are rooted.
If this is the case, you'll want to S-Off and install a custom ROM before the ICS OTA drops or you'll have a paper weight.
But I highly doubt this may be your case.
Sent from my ADR6400L using xda premium
Are you sure it has water damage and not a botched unrooting try? I ask this because you say it has a clockwork folder on the sd card that came with it.
Dark Jedi said:
Are you sure it has water damage and not a botched unrooting try? I ask this because you say it has a clockwork folder on the sd card that came with it.
Click to expand...
Click to collapse
Thats my question..... I was told he got the phone wet and a few days later it wouldn't turn on, but when going throuth the SD card I noticed the clockworkmod folder and thought this was only created when the phone has been rooted and or flashed.
I did some research on the touchscreen not working and see that there are numerous threads stating that a bad rom/flash can cause this, so I'm wondering what my next step would be?
Should I try rooting the phone and just flashing a different rom or would connecting to the phone with a remote control program be a better option? It doesn't appear that the phone is frozen, because the time stays accurate, but sometimes the screen will not turn on after pressing the power button to wake it up, so I just sit it down and after a few minutes try it again, sometimes it works, sometimes it doesn't????
Delete/reformat the SD card entirely. Reset the phone to factory.
Reroot the phone, get S-off, flash a recovery, and then flash a ROM.
May as well try it out.
It won't hurt anything.
Just a note to get a clean ROM flash:
Clear data/factory reset 3x, clear cache, clear dalvik, and then flash the ROM.
Sent from my ADR6400L using xda premium
RBarnett09 said:
Just a note to get a clean ROM flash:
Clear data/factory reset 3x, clear cache, clear dalvik, and then flash the ROM.
Click to expand...
Click to collapse
I would also suggest to format system. I usually always include system but one morning after too many sleepless nights and trying to rush things, I formatted sdcard, not system, as they are one after the other in the list in CWM and both begin with 's'. So now I double check and switched to 4EXT.
Sent from my MB860 using xda app-developers app
In 4ext you can just use the format all except sd card and get the same result as a superwipe. Works everytime for me.
Sent from my ADR6400L using Tapatalk 2
I would try and load 4ext and get rid of CWM. Seen to many people have issues with that recovery. Then wipe everything but your sd card. In your case I would wipe that to. Then just install a new rom. He might have gotten the phone wet but if none of the moisture stickers are triggered then most likely the water didnt reach the internals. So if that does work you just made a hell of a deal. I wouldnt tell the person that you got the phone working as he could call verizon and say his phone was lost or stolen and then the phone would be useless to you and might as well have water damage.
That lying son of a *****!
Oh well, that's craigslist for ya, besides the 32GB SD card is worth it.
Sent from my Galaxy Nexus using xda app-developers app