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
Related
My wife's EVO 3D, completely stock, S-ON, never installed the OTA update.
The phone was on and she had it in her pocket and felt it vibrate, when she looked at the phone, it was booting up but it appeared to be stuck in a boot loop. She said she saw it rebooting itself (just the initial sprint splash screen) several times before she pulled the battery.
She re-installed the battery, but the phone wouldn't turn on. So she left it alone and brought it home.
The reboot loop was a bit concerning to me, but the phone not turning on sounds like a drained battery. So, I put it on the charger (AC power adapter) for about an hour (orange led is lit).
When I turn it on, I see the boot screen (HTC -> Sprint -> 3D -> Sprint) and then the screen goes black. The soft key LEDs are stuck on the entire time. but nothing happens. I let it sit like that for 10 minutes and it never boots. I've tried several times with the same result.
I can get into hboot (Volume-down + Power)... Almost feels like a corrupt stock ROM?? I can check the CRC, but I don't know the correct values... And no one has tried to root or flash it. I asked if she might have accidentally started the OTA update, but she says not likely...
I've searched the forums here and various others, and it seems all not-booting and endless-boot-loop issues are all due to people trying to root or flash an image.
So.... I don't have a whole lot of experience with Android... What's the next step before attempting a factory reset or bringing it back to Sprint?
Thanks!
EDIT: Typos
Wow, this is very weird. My advice is if you still have 30 day return use it or insurance, bring it to sprint. If not both call HTC and complain but I doubt they cover software issues, idk I might be wrong. Why fix it? Get a brand new one, you paid for it to be working, not broken.
Sent from my PG86100 using XDA App
You said you can do a factory reset? I'd say do that first before trying anything else. If it works, then the only thing she has to worry about is taking 30 minutes of her time to re-set up her phone.
Sent from my PG86100 using XDA App
^^^You can do that or you can take it back to sprint store or a repair spot and possibly get a new one. Custom firmware would knock those bugs right out, so maybe its a sign. Your wifes' phone is ready to be rooted. Hey, I'm just saying...
My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_
Try removing the SD card and see if it will boot up properly. I had that happen to me once (boot loop and all). Phone would boot fine without the SD card.
I ended up having to format the SD card (connected to my PC with a card reader). That solved the problem.
This happened to my phone once. A factory reset from the bootloader fixes it good as new. It's been like a month and a half since then and I have had no problems since then.
boom!! from my shooter
Quick update -- phone finished charging... Green LED now... and still same behavior... Thanks for all the replies guys!
iModMM said:
Wow, this is very weird. My advice is if you still have 30 day return use it or insurance, bring it to sprint. If not both call HTC and complain but I doubt they cover software issues, idk I might be wrong. Why fix it? Get a brand new one, you paid for it to be working, not broken.
Click to expand...
Click to collapse
I want to see if I can get her a working phone tonight instead of sending her off to the Sprint store tomorrow, waste a bunch of time, and having them just do a factory reset anyhow.
DDiaz007 said:
You said you can do a factory reset? I'd say do that first before trying anything else. If it works, then the only thing she has to worry about is taking 30 minutes of her time to re-set up her phone.
Click to expand...
Click to collapse
Yeah... This was my first instinct, but just wanted a sanity check here on the forums first...
r0cky0790 said:
^^^You can do that or you can take it back to sprint store or a repair spot and possibly get a new one. Or maybe this is a sign. Custom firmware would knock those bugs right out, so maybe its a sign. Your wifes' phone is ready to be rooted. Hey, I'm just saying...
Click to expand...
Click to collapse
I know! I had her not install the OTA because I had intended to root the phone... I'm so tempted to just root the thing and flash something nice, but I don't want to risk it in case it is a more serious problem and we need Sprint to replace it... Maybe if the factory reset fixes it for a couple of weeks, then I'll consider again...
mvansomeren said:
Try removing the SD card and see if it will boot up properly. I had that happen to me once (boot loop and all). Phone would boot fine without the SD card.
I ended up having to format the SD card (connected to my PC with a card reader). That solved the problem.
Click to expand...
Click to collapse
Sorry I forgot to mention it in the original post, but did try re-seating the SD card and without the SD card... both exhibit the same behavior.
DJ1994 said:
This happened to my phone once. A factory reset from the bootloader fixes it good as new. It's been like a month and a half since then and I have had no problems since then.
Click to expand...
Click to collapse
This is what I wanted to hear.... Someone else with the exact same issue and a fix... I think I'll factory reset it now... I warned my wife that she will lose high scores and text messages. She didn't care about the texts, but was sad about losing her progress in Angry Birds! lol.
---------- Post added at 10:57 PM ---------- Previous post was at 10:34 PM ----------
Okay.. Factory reset went well... Restoring settings and apps now... Thanks for the help guys!
To get rod of those problems you should take the ota's if you haven't rooted it yer then no reason in leaving inferior firmware on the device
Sent from my PG86100 using Tapatalk
ktrotter11 said:
To get rod of those problems you should take the ota's if you haven't rooted it yer then no reason in leaving inferior firmware on the device
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Noooo, he can root and solve the problem that way. Just visit Haus's stock ROM thread, and he'll have everything there for you. A stock rooted ROM with all the OTA firmware fixes available for download. Just root first.
This is assuming you live in the U.S, and own the Sprint Evo 3D (CDMA).
ktrotter11 said:
To get rod of those problems you should take the ota's if you haven't rooted it yer then no reason in leaving inferior firmware on the device
Click to expand...
Click to collapse
Is this kind of failure a known issue with the original stock firmware? I'm not going to take the OTA to keep my options open for rooting in the near future.
DDiaz007 said:
Noooo, he can root and solve the problem that way. Just visit Haus's stock ROM thread, and he'll have everything there for you. A stock rooted ROM with all the OTA firmware fixes available for download. Just root first.
This is assuming you live in the U.S, and own the Sprint Evo 3D (CDMA).
Click to expand...
Click to collapse
Yeah.. I know not to take the OTA... I'm going to root it eventually.
I looked through the complete list of ROMs and didn't see Haus mentioned anywhere... Am I missing something?
Also, is there a common consensus on the top two or three Sense ROMs for the EVO 3D?
ken830 said:
Is this kind of failure a known issue with the original stock firmware? I'm not going to take the OTA to keep my options open for rooting in the near future.
Yeah.. I know not to take the OTA... I'm going to root it eventually.
I looked through the complete list of ROMs and didn't see Haus mentioned anywhere... Am I missing something?
Also, is there a common consensus on the top two or three Sense ROMs for the EVO 3D?
Click to expand...
Click to collapse
Here http://forum.xda-developers.com/showthread.php?t=1223979
Sent from my PG86100 using XDA App
iModMM said:
Wow, this is very weird. My advice is if you still have 30 day return use it or insurance, bring it to sprint. If not both call HTC and complain but I doubt they cover software issues, idk I might be wrong. Why fix it? Get a brand new one, you paid for it to be working, not broken.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
*14 days if bought on the 16th.
Try these things:
- Take batter off and hold power button down for like 10 secs, put battery back in.
- Download the RUU from a thread in the development section and flash it (it will replace everything back to stock).
That SHOULD fix it, if its a software issue, if it doesn't, or it still continues to act funky, just take it back to Sprint and demand a new one since you're within your 14/30 days.
Make sprint replace it the phone will be doing the so thing after resting it or trying any other trick its a software issue belive me I had 5 replacements because of software issues
Sent from my PG86100 using xda premium
So, I've been jumping back and forth between Atrix CM9 and CM7 roms and running the .36p radio. Yesterday on CM9, i started getting a large amounts of random reboots and finally got things settled by doing a factory reset in CWM and flashing a clean cm9 rom. However, whenever I turned on wifi, the phone would crash and reboot to the Dual Core logo. I tried flashing another CM9 rom and it didn't crash, but the wifi radio would never seem to pick up any AP's (i'm at home).
I've gone as far as changing to the .37p radio and going back to cm7 to no avail... I'm a bit worried I might have "fried" the wifi radio on the phone.
Did you do a full wipe? Use fastboot to wipe properly before flashing any ROM. Plenty of threads with instructions.
Sent from my MB860 using xda premium
Looking at the fast boot command, I'm not sure how that does anything different then the clockwork mod wipe... but I will give it a shot.
Sent from my NookColor using xda premium
Sorry, but your wifi/bluetooth card is dead. My Atrix got the exact same symptoms a few days ago. Both WiFi and bluetooth are on the same chip. When the system tries to reference them, it fails to locate the hardware and crashes/reboots.
In fact, in researching this topic, I found dozens of threads about this. We should make a sticky about it at this point. Best Buy was kind enough to take back my phone (unlocked bootloader, rooted, cwm, custom fonts, startup, etc.) if I restored it all to stock. If you want Motorola/AT&T/the store you purchased it at to not void your warranty, you should flash the 2.3.6 SBF. Just be cautious and read all about it. But that is the only way that Motorola will service a modded phone
xandr115 said:
Looking at the fast boot command, I'm not sure how that does anything different then the clockwork mod wipe... but I will give it a shot.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Nothing like the same. Clockwork wipe only does data and cache. You erase boot, system, preinstall, cache, user, webtop, etc., via fastboot. I've posted the procedure probably more than 20 times before.
Sent from my MB860 using xda premium
Yeah unfortunately even after a fastboot wipe, the phone's bluetooth and wifi were gone. I was also over the year warranty. Luckily, I picked up a barely used one on Craigslist and restored my backup to it. Now i've got an expensive battery charger (and spare phone should i need it).
If there were any tips you'd have on restoring to a new phone? I've restored my phone a lot and worked on a lot of android phones (I work at a repair shop), but I've never restored data/settings from one phone to another. Of course its the same model, but I can only imagine the issues that could arise out of such an operation
Thanks!
I just made sure I did a fastboot full wipe of the new phone, then placed my clockworkmod directory on the internal (external should be ok too) storage and did a restore. After the restore, I re-flashed the latest version of the rom I was running on top of it with Google apps and it booted fine. Afterwards, I made sure to do a permissions repair and reboot.
Yeah, it seems like a lot of people are having this problem. Like me for example :[
So far there is no solution that I'm aware of, after trying practically everything I could think of and find on the internet... I'm pretty sure it's hardware related. I bet the phone just isn't very high quality. How much did it cost again? $600? + all of the dumb accessories for it. Normally when you see a pattern of failures you would call it a design flaw, but apparently when it comes to expensive electronics they call it out of warranty.
xandr115 said:
So, I've been jumping back and forth between Atrix CM9 and CM7 roms and running the .36p radio. Yesterday on CM9, i started getting a large amounts of random reboots and finally got things settled by doing a factory reset in CWM and flashing a clean cm9 rom. However, whenever I turned on wifi, the phone would crash and reboot to the Dual Core logo. I tried flashing another CM9 rom and it didn't crash, but the wifi radio would never seem to pick up any AP's (i'm at home).
I've gone as far as changing to the .37p radio and going back to cm7 to no avail... I'm a bit worried I might have "fried" the wifi radio on the phone.
Click to expand...
Click to collapse
did your wifi
For anyone interested, here is a supposed solution to the problem:
http://www.youtube.com/watch?v=SYz_RiuFVRk
It will require you to open the phone up, and solder the "wifi battery" into place. I'm not sure what the hell that thing is, but that guy in the video called it a battery. Voids warranty etc. Good luck.
cafe. said:
For anyone interested, here is a supposed solution to the problem:
http://www.youtube.com/watch?v=SYz_RiuFVRk
It will require you to open the phone up, and solder the "wifi battery" into place. I'm not sure what the hell that thing is, but that guy in the video called it a battery. Voids warranty etc. Good luck.
Click to expand...
Click to collapse
I'd give it a try, if I could understand what exactly he does. It looks like he just pries it up with a screwdriver and then pushes it back down.
Meursau|t said:
I'd give it a try, if I could understand what exactly he does. It looks like he just pries it up with a screwdriver and then pushes it back down.
Click to expand...
Click to collapse
If I ha some solder I might try it
Sent from my NookColor using xda premium
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
So I was on SOS Rom with Chad's linux 3 kernel and did the wire trick. I got s off, yay!!!!
So, now my wifi stinks, 3g stinks, my touch screen was affected, I have slight dead areas. I can't flash kernels, but I can flash boot screens. Totally not worth the trade off, lol. I have tried CWM, 4Ext, fastboot and flash image GUI. None work
Anyone have any ideas WTF is going on? Or what I need to do? I was thinking about using google to find out how to get s on and try the wire trick again, or just stay s on.
Would I need to flash a firmware from Frieza to possibly fix the kernel issues? I have no idea how that would help at all, lol.
If anyone else has had issues like this,.what did you do?
XDA senior techs, any ideas?
Not saying the wire trick stinks, just saying I ran into an issue I cant figure out
Sent from my PG86100 using XDA
Well I'm deeply sorry for your issues but I also believe that the issues your experiencing is not totally related to the "wire trick".
The effects of the wire tricks can't do much damage because the voltage going out of the pin#1 is not enough to cause massive effects with the small amount of time you make contact with ground.
Questions :
what kind of wire did you use?
How long did you place the wires in full contact?
I would say as well that disclaimers are posted and there are risks with following any prodcedures written in this site.
Try flashing a RUU and see what happens, perhaps that could be a way out?
Sent from my PG86100 using Tapatalk 2
Nametaken said:
So I was on SOS Rom with Chad's linux 3 kernel and did the wire trick. I got s off, yay!!!!
So, now my wifi stinks, 3g stinks, my touch screen was affected, I have slight dead areas. I can't flash kernels, but I can flash boot screens. Totally not worth the trade off, lol. I have tried CWM, 4Ext, fastboot and flash image GUI. None work
Anyone have any ideas WTF is going on? Or what I need to do? I was thinking about using google to find out how to get s on and try the wire trick again, or just stay s on.
Would I need to flash a firmware from Frieza to possibly fix the kernel issues? I have no idea how that would help at all, lol.
If anyone else has had issues like this,.what did you do?
XDA senior techs, any ideas?
Not saying the wire trick stinks, just saying I ran into an issue I cant figure out
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Oouch! I hope there is a fix for you, I'm sure you are going to try everything.
I don't know how to fix this but I do know a little bit about electronics. Actually quite a bit. Sounds like this trick shorted out or caused a voltage spike internally. Generally when an electronic component is damaged, there is no fix.
When you let out that factory installed smoke, you can't get the Genie back in the bottle.
I had a laptop once where the fan stopped working. I bought a new one. New one was not getting any voltage. A friend of mine was sitting at the bench with me. He decides lets just find another spot with same voltage and tap in there. Starts jumping wires around on the mother board and poof -- $1,000 dollar laptop on sale for parts on Ebay. Took me a long time to get over that one.
I was just looking around and found a problem similar to yours, in the "wire trick" thread. http://forum.xda-developers.com/showthread.php?p=26390751
Yeah... I totally noob bombed that dev thread so o started up a qna here lol
Sent from my PG86100 using XDA
Just a little more info. I can flash other kernels, but on sense Roms, it just shows up as the same name as the other stock kernel. I was able to fully flash other roms, like AOSP. Once I flash AOSP, I can see the other kernels I flash.
Flashing AOSP:
While I can flash it and other kernels, I get stuck on being able to activate my phone on the device. It gets stuck saying airplane mode is on. Totally sucks. Haven't tried activating online or by calling sprint. I have been busy with family stuff.
If anyone else has issues, post em up! Perhaps we can all help each other out
Sent from my PG86100 using XDA
So Here's what I ended up doing. After wire trick got me the S-Off, I had that ICS HBoot and thought hey, maybe this has something to do with my weird AOSP issues (for background please see my post in the CDMA developers section in the JBear thread), so I flashed my 2.17 RUU that I had handy. After that, I updated PRL and Profile (hoping this would do something). Then to my surprise, everything was stock again, bootloader read hboot 1.5.0 again instead of the 1.57 one, however no root because it's an RUU! Anyway, I kept reading through the thread like some of these folks told me, however I didn't find much, I did see that most people with success were using the JBear GB version. So, I flashed the jb_hboot from the GB version (I actually took another guy's advices and simply renamed the jb_hboot.zip file to PG86IMG.zip, this worked! Got me the Jbead modified GB bootloader on 1.50. SO I guess since we're S-Off, I was able to go back to hboot 1.50 and then did a fastboot flash recovery recovery.img and flashed the Ext4 recovery image I had. From there, I restored the nandroid I had (Nocturnal ICS Xi36 r105) and it all booted up fine. Later I will try flashing back to CM9 and see what happens, perhaps I'll be able to get out of this "sort of Airplane mode" that isn't really airplane mode (where the phone htinks it's deactivated.)
The key here is that while I was on GB RUU, I updated PRL and Profile, then went to the 1.5 hboot hoping that would be enough for the CM 9 rom and other AOSP ICS roms to activate upon install. I'll keep you posted.
Thanks for starting this thread man, we need a place to sort all this out. With all the info that floods the OPs of development threads, it's hard to really find what is even relevant. So, glad to see one in the Q and A that we can ask questions.
Well what i can say is that after trying the wire trick my device would randomly turn off and stop working. No charge, No light. Nada. Completely dead then it would randomly come back to life. Anyways. I took my phone to sprint today and ill be going back in two hours to see what the problem with my phone is.
I personally think its a hardware issue. Maybe i used a bad wire? Or i touched the wire during the process which is known to mess up your device.
Thinking about it . I don't see why people don't downgrade instead of the wire trick.
Update- Sprint told me my device had hardware issues and will send me a new phone within 4 days.
There is a possibility that, as someone else has pointed out, that we are indeed hurting our phones. Not so insulated wires, paperclip with tape etc, is the culprit. Too much static getting in and possibly hurting our phones. Something to think about.
To RUU Paul, lol,
I was thinking of uprooting using a similar method like you and gaining root again to ensure it isn't permanent. While it seems you could make it back, this could mean it is a software issue then, but it is too early to tell. Hopefully we cab get enough of the anomalies in to pin point this.
Sent from my PG86100 using XDA
cmbaughman said:
Anyway, I kept reading through the thread like some of these folks told me, however I didn't find much, I did see that most people with success were using the JBear GB version. So, I flashed the jb_hboot from the GB version (I actually took another guy's advices and simply renamed the jb_hboot.zip file to PG86IMG.zip, this worked! Got me the Jbead modified GB bootloader on 1.50. SO I guess since we're S-Off, I was able to go back to hboot 1.50 and then did a fastboot flash recovery recovery.img and flashed the Ext4 recovery image I had.
The key here is that while I was on GB RUU, I updated PRL and Profile, then went to the 1.5 hboot hoping that would be enough for the CM 9 rom and other AOSP ICS roms to activate upon install. I'll keep you posted.
Thanks for starting this thread man, we need a place to sort all this out. With all the info that floods the OPs of development threads, it's hard to really find what is even relevant. So, glad to see one in the Q and A that we can ask questions.
Click to expand...
Click to collapse
Thanks for pointing this all out! I can confirm that doing this allows us to flash back to AOSP with Airplane mode off and get it all up and going.
Once in there, you can change out your kernel and see that it is changed under About Phone! I loves you so much!
Now, if anyone has a way to verify if a kernel was changed or not, we can see if my idea was right about it flashing the kernel, just not showing the correct name of the kernel that was flashed
Thank you all the effort you guys have put into this. I too ran into this issue, and simply flashing the GB hboot resolved my issue. Just so everyone knows, that it is not necessary to revert to stock first. Just simply flash the other hboot, and you should be good to go.
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.