So I have a possbile bad digitizer and wanted to return to stock before going to sprint. Phone shipped with 1.13 and 1.40 bootloader. I rooted s-off with revolutionary.
I downloaded the 1.13 ruu and tried to run it. It looked fine but then returned an error it couldnt complete. I assumed I had to set security to on first and ran the command "fastboot oem writesecureflag 3" without quotes. When I rebooted bootloader it then said s-on. I then rebooted system and now I seem to have a paper weight. The phone will not turn on or when plugged in the charging LED does nothing.
I do notice if I pull the battery and put it back in, the charging led is very very faint.
Is this phone now hard bricked or is there anyway to fix it?
uhhh try taking the battery out for like 10 mins and then try again. And if all fails again try running another ruu
splink7007 said:
I do notice if I pull the battery and put it back in, the charging led is very very faint.
Click to expand...
Click to collapse
Could it be that the battery is dead and needs to be charge...
Sent from my PG86100 using Tapatalk 2 Beta-2
splink7007 said:
So I have a possbile bad digitizer and wanted to return to stock before going to sprint. Phone shipped with 1.13 and 1.40 bootloader. I rooted s-off with revolutionary.
I downloaded the 1.13 ruu and tried to run it. It looked fine but then returned an error it couldnt complete. I assumed I had to set security to on first and ran the command "fastboot oem writesecureflag 3" without quotes. When I rebooted bootloader it then said s-on. I then rebooted system and now I seem to have a paper weight. The phone will not turn on or when plugged in the charging LED does nothing.
I do notice if I pull the battery and put it back in, the charging led is very very faint.
Is this phone now hard bricked or is there anyway to fix it?
Click to expand...
Click to collapse
Your bricked??? That's awesome! How many tries did it take you?
Sent from my PG86100 using Tapatalk
splink7007 said:
So I have a possbile bad digitizer and wanted to return to stock before going to sprint. Phone shipped with 1.13 and 1.40 bootloader. I rooted s-off with revolutionary.
I downloaded the 1.13 ruu and tried to run it. It looked fine but then returned an error it couldnt complete. I assumed I had to set security to on first and ran the command "fastboot oem writesecureflag 3" without quotes. When I rebooted bootloader it then said s-on. I then rebooted system and now I seem to have a paper weight. The phone will not turn on or when plugged in the charging LED does nothing.
I do notice if I pull the battery and put it back in, the charging led is very very faint.
Is this phone now hard bricked or is there anyway to fix it?
Click to expand...
Click to collapse
the phone doesnt turn on at all or wont boot up?....can you boot into hboot?
if you can get to the bootloader, we can fix it. if you cant, its a wrap unfortunately.
press and hold volume down & power with the phone off to get into bootloader.
phone would not boot at all. Not even to bootloader.
Had to get a refurb from Sprint yersterday
thats not a bad thing. refurbished devices are repaired by hand and are hand tested before being sold again. your device might be better than mine.
splink7007 said:
phone would not boot at all. Not even to bootloader.
Had to get a refurb from Sprint yersterday
Click to expand...
Click to collapse
My guess is you spanked your old one dunno how tho ..
Reaper midnight blue .
Hello!
When you put it to charger,the led turn red and after a sec turn off?
Put the camera button and the power together.
I had the some problem and I solved with this trick after 2-3 times.
P.s.: sorry for my English.
Sent from my HTC EVO 3D X515a using Tapatalk
manos_23 said:
Hello!
When you put it to charger,the led turn red and after a sec turn off?
Put the camera button and the power together.
I had the some problem and I solved with this trick after 2-3 times.
P.s.: sorry for my English.
Sent from my HTC EVO 3D X515a using Tapatalk
Click to expand...
Click to collapse
Lol he ended up getting a refurb cause the other one was spanked.
Try starting from step 3 in unknownforce's downgrade guide. Step 3 is UNbrick so it might just save you
Sent from my PG86100 using xda premium
It is possible to fix but first you would have to download the original ruu or close to it there floating around in here check the CDMA development section I found mine in the GSM development I'm sure you can't find it and if you do keep a copy on your desktop or laptop incase of emergency such as this good luck
Sent From my Evo 3D S-OFF using Xda premium
Try taking the battery for ten minutes and when you put the battery back in see if you can boot into bootloader that way.
Sent From my Evo 3D S-OFF using Xda premium
Related
I have a big problem !!! I had on my phone root s-off ROM Shooter Beats 1,7 and I flashed CWM 4.0.1.-shooteru via fastboot.
BUT when I was in fastboot USB I was thinking that I will try to have root with s-on on the screen on HBOOT. So I used command that I read in unroot section.
fastboot oem fastboot oem writesecureflag 3 and then reboot bootloader and my pfone is off and I cannot turn it on and dont know what to do :-( I am scared
you need to s-off your device again.using cmd
yes, I know, but I cannot turn on the phone.. I cannot do anything
Bricked
Sent from my HTC EVO 3D X515m using XDA App
There is nothing else to do?? :-(
What about warranty? If I cannot get to my phone, HTC cannot know if it doesnt work because of root, right? Do I have a chance?
What about a simple RUU? Just to try, and may it gives you s-on back and hboot and Kernel, so you maybe can boot into fastboot loader
Sent from my HTC EVO 3D X515m using XDA App
I cannot turn my phone on, I cannot go to bootloader, I cannot do anything. But when there is battery there is little red light on and when I remove battery it goes off. It is not blinking it is just permanent weak red colour (it is hardly to see).
When I connect Evo 3D to laptop, there is a sound that something is through USB connected, but the drivers are not regognized (in system there is only something QHUSB_DLOAD)
I was trying cmd and fastboot reboot and it is waiting for device
I was trying adb restart and nothing..
when I try RUU, it cannot find my device
Castellano2 said:
I cannot turn my phone on, I cannot go to bootloader, I cannot do anything. But when there is battery there is little red light on and when I remove battery it goes off. It is not blinking it is just permanent weak red colour (it is hardly to see).
When I connect Evo 3D to laptop, there is a sound that something is through USB connected, but the drivers are not regognized (in system there is only something QHUSB_DLOAD)
I was trying cmd and fastboot reboot and it is waiting for device
I was trying adb restart and nothing..
when I try RUU, it cannot find my device
Click to expand...
Click to collapse
try to use a RUU
If all fails send it back to HTC and say it stopped working overnight
Sent from my HTC EVO 3D X515m using XDA App
Did you have recovery? If you do, the problem you ran into might be an easy one.
1. Plug your phone to a power source (Long press the power button for few seconds and see if the light is on)
2. If the light is on, press the camera button (may be few times if first time doesn't work) and wait.
3. The first two steps should have already taken you into the boot screen. If it doesn't, then sorry.
thre3aces said:
If all fails send it back to HTC and say it stopped working overnight
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
Try to push camera, volume up+down and power Buttonand hold it down for a few seconds and see if the phone boots. Then plug in charger and charge it. So you can see if the battery was dead!
Thank you guys for advices but
1, I tried use RUU and as I said it doesnt find my device (there are not drivers anymore)
2, volume plus camera button and so on.. this problem I solved many times.. it was problem with CWM 5.0.2. but I have there 4.0.1. which has no battery bug.
My phone doesnt work and cannot go on.
I googled little bit and find out that people with Desire HD had the same issue and they sent it to service and got new phone. I hope it will be the same I love my phone so muuuuuuch..
I think the problem is that I would need to get drivers for my mobile to get sdk ready.. but :/
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Castellano2 said:
Thank you guys for advices but
1, I tried use RUU and as I said it doesnt find my device (there are not drivers anymore)
2, volume plus camera button and so on.. this problem I solved many times.. it was problem with CWM 5.0.2. but I have there 4.0.1. which has no battery bug.
My phone doesnt work and cannot go on.
I googled little bit and find out that people with Desire HD had the same issue and they sent it to service and got new phone. I hope it will be the same I love my phone so muuuuuuch..
I think the problem is that I would need to get drivers for my mobile to get sdk ready.. but :/
Click to expand...
Click to collapse
bricked...there are a few reports here that did the same procedure and bricked it too.
I really cant understand why people play with those things although they have no idea of what they are risking.
..i mean, you could have been very proud that you got a device which csn achieve s-off. Thousands still dteaming of it.
Why the hell you wanted to went back to son and root?
If you would read through the forums you should have nitice, that you cant flash custom kernels easily - just with flash img gui. And flashing radios is
Is completly not possible with son.
Son makes life so much more painful.
And you still did it...sry tried it
Sent from my HTC EVO 3D X515m using xda premium
j4n87 said:
bricked...there are a few reports here that did the same procedure and bricked it too.
I really cant understand why people play with those things although they have no idea of what they are risking.
..i mean, you could have been very proud that you got a device which csn achieve s-off. Thousands still dteaming of it.
Why the hell you wanted to went back to son and root?
If you would read through the forums you should have nitice, that you cant flash custom kernels easily - just with flash img gui. And flashing radios is
Is completly not possible with son.
Son makes life so much more painful.
And you still did it...sry tried it
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
I know, I read through forum and find out that problem with QHUSB_DLOAD is always dead end. You cannot understand why people do that? I read a lot of topic where people have written that I tried to unroot their phone because of warranty and in finally step - whitesecure flag 3 - it bricked. They do it exactly how it was in "manual", so they have just bad luck.
I want to have s-on because my cable conector was wrong and I was afraid when I won´t connect my phone to computer, I cannot remove root and my quarantee will finished.. But I didnt flash stock Rom because I want to give it on sd card and when my usb cable won´t work, I could just reflash to stock ROM from my backup..
Right now my phone is in service..
Hi.
I recently got a refurbished Evo 3D after my old one's digitizer broke. About 2 days afterwards, I was being stupid and accidentally dropped my phone. The back popped off and the battery came out. Now it shows a dim red light whenever it should be charging (via usb cable into my computer) and refuses to even turn on. However, whenever I plug it in, it makes the sound that windows recognizes that a USB device is plugged in. Is this a sign of hope that I can fix my phone? Please give me any suggestions.
Things I have tried:
-Holding power down (with the volume buttons and camera button etc.)
-Trying to use the command: adb reboot bootloader
-Taking out batter and using a different one from another phone.
-Charging the original battery to full using the spare Evo 3D and then attempting the above.
Before I dropped it I did root the phone and stupidly attempted to install the wrong ROM (used CDMA instead of the other one, can't remember the name off the top of my head, but it's the one used in Rogers phones), but it didn't brick the phone or anything.
One more thing to note is that right after I dropped it and tried to boot it up it made it to the white HTC screen, then turned off.
Hopefully this is enough information, and thanks in advance for any help.
Check out the thread in the dev section about downgrading hboot 1.5 at some point in it, you purposefully brick it to a faint red light. Try to follow instructions from there.
Sent from my PG86100 using xda premium
troublein420 said:
Check out the thread in the dev section about downgrading hboot 1.5 at some point in it, you purposefully brick it to a faint red light. Try to follow instructions from there.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Any other suggestions? I don't have a linux machine, and currently my ISP is not exactly cooperating with my internet connection, so it's extremely slow atm, and as a result will probably take too long to download.
troublein420 said:
Check out the thread in the dev section about downgrading hboot 1.5 at some point in it, you purposefully brick it to a faint red light. Try to follow instructions from there.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Not to just repeat what others have said, but the dim red light truly sounds like what happens when the phone is bricked. If it is, you may be able to save it by following that thread when your ISP cooperates. It is strange though that dropping it would cause it to brick.
If he is on Rogers, he has a GSM phone & can't use the Hboot 1.50 cdma downgrade thread. There are 2 stickied downgrade threads in the Gsm section.
Sent from my PG86100 using Tapatalk
Well you know the old saying once you drop it its over or you could turn it in and get a replacement
Sent from my HTC EVO 3D X515m using xda premium
out of warranty ? =.=
just 2 days after returning
Here's what I would try
Here's what I would try:
1. Take battery out of phone and make sure, 100% sure, the phone is off.
2. Once the phone is 100% powered down pop the battery back in.
3. Now what I would do is hold down power + volume up until the phone comes to HBOOT.
4. If HBOOT doesn't come up, idk. If you have a working nandroid, I would restore from it. If you don't, just select fast boot, then select the option to start up normally (which I forget what it is called...).
-cburk
okay! so I have a S-on amaze 4g. Unlocked bootloader and have clock work recovery, Im also on tmobile. I was running Bulletproof's rom v2.5
so yesterday I was looking at some roms and I came accross mike 1986's android revolution ROM that was based on tmobile's sense 3.6 and android 4.0. I decided to ditch my current ROM and go for mike's ROM instead
Well last night I followed his instructions. Put the PH85IMG, Rom and Super wipe to my phone's SD card. I booted into bootloader and it loaded the PH85IMG but it didnt seem to have done anything so it loaded back to bootloader. I selected "Recovery" and booted into recovery. I deleted my files and cache using clockwork recovery. Then applied the Superwipe zip then installed the ROM. It said it installed the rom and then I proceeded to reboot my amaze 4g. Ok I rebooted my phone and it got stuck on the HTC screen for some quit time WITHOUT THE QUIETLY BRILLIANT. So i decided to redo this all over again. and again the same problem happened. stuck on the HTC logo. so I took out my batterys and went to bed since i wanted to get some shut eye
now this is where my problem comes from. When ever I turn on my phone it wont turn on! i wanted to boot into bootlader but when ever i press on the power button with the volume rocker down it wont start up. So i plug in my USB cable and the LED that indicates charging comes on. and my computer detects the phone... i click on the search capacitive button and the phone disconnects from my computer and it boots into the HTC screen and the screen turns blank
if anyone can help me please help.
come on 43 views and no help
Leave your phone in the charger overnight. See what happens in the morning.
hasoon2000 said:
Leave your phone in the charger overnight. See what happens in the morning.
Click to expand...
Click to collapse
i dont think thats going to work but ill give it a try
Just curious. What version of CWM was installed?
Sent from my HTC_Amaze_4G using Tapatalk 2
So you cant get the the phone to turn on, but u were able to turn it on when it was connected to the computer?
Sent from my NRGized amaze
Via XDA premium
Ok. First don't panic. Can you explain by "I clicked the capactive search button". Have you really try power it on without your computer?
Sent from my HTC_Amaze_4G using XDA
jp2dj1 said:
Ok. First don't panic. Can you explain by "I clicked the capactive search button". Have you really try power it on without your computer?
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
what i mean by that is when i touch the search button (the magnifying glass icon on the far right) when its charging it would boot into the HTC screen then the screen would turn off
aj_2423 said:
So you cant get the the phone to turn on, but u were able to turn it on when it was connected to the computer?
Sent from my NRGized amaze
Via XDA premium
Click to expand...
Click to collapse
i cant get the phone to turn on when its connected to the computer or wall charger
i just noticed that my LED would blink when first charging then it boot into the HTC screen on its own then the screen would turn off or go blank. after that the LED wouldnt come on so i dont know if its still charging since the orange light isnt there
any more help it would be greatly appreciated
I tried the same rom yesterday and it failed for me also. I've seen quite a few fails on it. Mine didn't die like yours, mine just froze on the splash screen. I had to pull the battery and hboot and re install my recovery so I could restore my backup. Does anything happen if you pull the battery and try to get into bootloader?
jimczyz said:
I tried the same rom yesterday and it failed for me also. I've seen quite a few fails on it. Mine didn't die like yours, mine just froze on the splash screen. I had to pull the battery and hboot and re install my recovery so I could restore my backup. Does anything happen if you pull the battery and try to get into bootloader?
Click to expand...
Click to collapse
i cant even get my phone to get into hboot when i press down on the power and volume buttons.
it did work yesterday after i failed... but when i woke up today i cant even get into hboot for some reason.
You might have to get an external charger to charge your battery, or if you know anyone to swap batteries with to charge yours and try theirs to see if it's just a dead battery. Sounds like it might be.
Download the latest RUU for your phone. You said the computer detects the device see if the RUU will see it as well. Hoping that it does just run it and it will flash your phone back to stock stock and you may have to unlock and install clockwork again but if it works you'll have a working phone again good luck chief
Sent from my LG-P999 using Tapatalk 2
I believe the Rom u were trying to flash is for s-off only....I might be wrong though...
Sent from my HTC_Amaze_4G using XDA
If i recall, you were supposed to lock the bootloader before you placed the PH85.img, because it wouldn't recognize the file without it on an S-On device. Also, where you using Xboarder's Clockwork recovery touch? or an older version?
Try this and tell me what happens. Change your phone by your computer USB and turn it on by search button and "HOLD THE DOWN VOL BUTTON AT THE SAME TIME" try it a couple of times.
Sent from my HTC_Amaze_4G using XDA
I think it's a problem with the version of cwm installed, it won't charge the battery right if it dies all the way pull the battery then charge it for about 20 mins then battery pull again and charge for a minute or two and try and turn it on
Sent from my HTC_Amaze_4G using XDA
Thread Moved to Q&A. PM sent to OP.
Sent from my Galaxy Note i717, using XDA Premium.
You don't have to be a farmer to know what sh*t smells like.
WTF, so about 2 hours ago my evo just crapped out. Its S-off running Flex360s 1.72 rom. I was at the store and pulled out my phone, I hit the power button and nothing would happen. When I got home I noticed its stuck at the splash screen with no backlight. Held the power button till it restarted and it would vibrate and bootloop till it eventually get stuck at the splash screen. The whole time the backlight being off. It can go to bootloader but its like frozen and even then the backlight is still off. Too bad I cant pull the battery, also it will not just turn off
Time to plug in USB and run the latest RUU for Jewel?
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
Similar to mine,,,
boost happy said:
WTF, so about 2 hours ago my evo just crapped out. Its S-off running Flex360s 1.72 rom. I was at the store and pulled out my phone, I hit the power button and nothing would happen. When I got home I noticed its stuck at the splash screen with no backlight. Held the power button till it restarted and it would vibrate and bootloop till it eventually get stuck at the splash screen. The whole time the backlight being off. It can go to bootloader but its like frozen and even then the backlight is still off. Too bad I cant pull the battery, also it will not just turn off
Click to expand...
Click to collapse
Mine bricked itself too...
http://forum.xda-developers.com/showthread.php?t=1800686
michael.stollaire said:
Time to plug in USB and run the latest RUU for Jewel?
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
Click to expand...
Click to collapse
Already tried. It basically told me to screw myself lol.
EDIT: OK I've had it connected to my computer for awhile trying to communicate through ADB. I have fail, & in another attempt to power it off, I held power down for like 3 mins straight. After releasing power it stayed off, and now I have a charging light!!! In a few I will attempt going into bootloader again
still screwed
boost happy said:
still screwed
Click to expand...
Click to collapse
May sound like a dumb question but did you have it plugged into a car charger before going into the store?
Sent from my EVO using xda premium
mcvoss said:
May sound like a dumb question but did you have it plugged into a car charger before going into the store?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
You are not actually bricked since your device turns on and shows some responsiveness when doing so (i.e. bootloader) My phone is ACTUALLY BRICKED meaning it has no response of any type whatsoever. If you can successfully boot into bootloader then you'd want to select "fastboot" then run the Jewel RUU from your PC. You'll need all the necessary fastboot drivers installed beforehand.
Can't select anything in bootloader. Its unresponsive
boost happy said:
Can't select anything in bootloader. Its unresponsive
Click to expand...
Click to collapse
Smash it, TEP time.
Sent from my EVO using xda premium
shook187 said:
Smash it, TEP time.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
yes, I feel like going out back with the phone and 1911..
I do have TEP and Best Buy black tie. I may go to best buy and see what they will do.. I just hope like hell I dont end up with the new HBOOT
boost happy said:
yes, I feel like going out back with the phone and 1911..
I do have TEP and Best Buy black tie. I may go to best buy and see what they will do.. I just hope like hell I dont end up with the new HBOOT
Click to expand...
Click to collapse
bring it to best buy, you will get a loaner phone for 3 days and then get the new one. whats nice is there people at geek squad dont know how to check if the phone is even rooted, also you get the new one before the people get the broken one.
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.