I think the internal is corrupt and screwed - Sprint HTC EVO 4G LTE

hey guys,
few days ago, my girlfriends evo lte was jacked up while she was on a trip. she told me she kept having FC's and all kinds of errors and stopped in a sprint store and they couldnt do anything, so she picked up an htc one.
i scooped up her evo lte.
it had twrp and cm 10. i activated it on my account, so i needed to throw meanbean or something similar on there so it could update data profile etc...
cool. it got activated.
anytime i try and wipe the device it fails, anytime im in android trying to transfer to internal, it locks up. i go in twrp and try mounting and transfering to it, and its jacked and hangs. again, i try to format the thing, and it says error mounting sdcard.
reading through some stuff i guess sometimes the internal goes corrupt, and i think the partition tables bugged. im trying to do viperuu to bring it to stock and redo the internal partition table. it keeps hanging on the pre-update. i tried an official ruu and it always says it cannot connect.
any suggestions? before i throw this thing against the wall and then flush it down the toilet? ive sunk about 8 hours reading and messing with it and im getting really plssed off

What happens when you connect the phone to a computer and mount the internal storage via recovery? Also, is the phone S-off?
Sent from my EVO using XDA Premium 4 mobile app

when i mount it, it can be read in windows. thing is, if i try to delete move copy anything, it looks like it wants to start, but it will just stay there. it doesnt seem to do anything so inevitably i have to disconnect and pull the plug because it locks up windows until i restart.
i found out with that viperruu, i rename the rom.zip in there to PJ4876.zip or something like that, and when i pop into bootloader i was able to use it to put stock on my phone. thing is, seems it wiped the recovery. im going to go s-off again, and hopefully have some more luck. seemed when i checked to load into recovery, it wiped and went back like i did a factory reset. I know the recovery was wiped because it has a phone with red exclamation triangle

Related

pg86img blocking recovery

So I had the miui rom, but the phone calls sucked, so I decided to download the new senseless rom to my phone.
At this time, I had CWM 5,but every time I would try to install, the installation would abort and say (status 1), and stuff like that.
So I got the twrp pg86img to my phone, went into the white screen where you can be directed into recovery.
It flashed successfully, but trying to reboot, my phone is stuck at the HTC screen.
I cannot enter recovery because the pg86img blocks everything, my only option on the white screen with the skating androids is to install the img, or press power to reboot.
Ive tried adb with phone on white screen, and off, everytime the system/bin/sh is not found.
I really need some help.
Do you have a micro SD card adapter that you can put into your computer to just delete the PG86IMG ? That's what I do when stuff like that happens.
No i dont, I ended up taking out the micro sd from my old instinct, and loading a nandroid onto it.
No cord for the instinct though, still figuring out how I'm going to get that thing off of the card.
Thanks anyways
thecalitree said:
No i dont, I ended up taking out the micro sd from my old instinct, and loading a nandroid onto it.
No cord for the instinct though, still figuring out how I'm going to get that thing off of the card.
Thanks anyways
Click to expand...
Click to collapse
Just put that card in another phone/tablet that is already running android. (AFTER it's booted into whatever rom, and it doesn't even have to be your phone). Its gonna act like a card reader. Then, just go into a file manager, and delete it., then unmount it, and remove it. (Something with an easily accessible sd card, like the Nook Colors they have laying out at Best Buy, lol)
Or there's about 20 other ways, as well.
<<It ain't over till the fat guy swings.>>

Rooted phone gone bad! Can I just wipe to factory?

Some of you might have seen my earlier thread, my ReZound is rooted. HTC sent out the ICS update my phone attempted to install it and afterwards it would not advance past the white HTC screen. After many hours of playing around with it (being semi-noobish to all things rooting, but decently knowledable with technology) I realized that on the H-boot screen it was telling me that the Image was missing. I assumed that the HTC update deleted it? After thinking about it, I thought that maybe installing a custom ROM would fix this, so I grabbed Scotts Clean ROM. Sure enough I did and I was finally able to advance past the white HTC screen. It looks as if everything is working fine with the phone now EXCEPT I have no data and no calling connection. Im assuming that my phone is just that messed up from the attempted upgrade this morning that im missing files needed for the connection.
My next thought was to just say heck with it and do a factory reset hoping to get back to a bone stock phone that at least functioned, but when I try the factory reset it doesnt work....
Any ideas of what I should do next? Ive spent 5-6 hrs trying to fix this phone today, I really hope to get something figured out. Thank you everyone for your help!
EDIT: I feel like an idiot... Because of putting the battery in and out for resets I left the back off the phone. I now have service. Main issue now is that when I try to call out, as soon as I type a number on the dialer it freezes up and restarts itself....
The phone still tries to look for the old image on the restart and gives me issues every time on startup still also. Id like to be able to get this back to not needing a ROM....
If it were me, I would download the official RUU for ICS found here: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ IIRC, mirror #3 was the fastest. Then follow the directions from that site:
After downloading the file, rename it to "PH98IMG.zip" (no quotes)
Place the renamed file onto the root of the SD Card
Power down your device
Reboot into the bootloader by holding VOL DOWN + Power
The flashing process should begin automatically
Let the device reboot, and you should be done.
That will get you up and running. Then you can go about rooting it again if you like.

[Q] Help... Stuck in recovery :(

So here is the deal, i went to flash a new ROM last night. I usually do everything on my phone as my computer does not normally recognize my USB for some reason, but anyways, i tried flashing last night and the flash failed. and i have no back ups nor can i plug in a USB and transfer anything to my "sd" portion of my phone because it does not work. Oh and when i go back to stock (Factory reset), when i try to boot into system. It just shoves me back into recovery mode, someone please help. I'm usually pretty good with this stuff and if i don't know a quick Google search is sufficient. But i have found nothing. This is my last resort.
FYI: I believe it failed because my recovery is an old version, I'm using team win recovery touch. not sure if that changes anything
Dylerium said:
So here is the deal, i went to flash a new ROM last night. I usually do everything on my phone as my computer does not normally recognize my USB for some reason, but anyways, i tried flashing last night and the flash failed. and i have no back ups nor can i plug in a USB and transfer anything to my "sd" portion of my phone because it does not work. Oh and when i go back to stock (Factory reset), when i try to boot into system. It just shoves me back into recovery mode, someone please help. I'm usually pretty good with this stuff and if i don't know a quick Google search is sufficient. But i have found nothing. This is my last resort.
FYI: I believe it failed because my recovery is an old version, I'm using team win recovery touch. not sure if that changes anything
Click to expand...
Click to collapse
Well u need to get something on the phone to flash. I suggest you work on the usb issue or get a micro sd reader.
Well the "sd" card is the integrated one i cant remove. And i have tried fixing the usb but nothings seems to remedy it. Very rarely i can get it to work but it will stop working the next time i try to plug it in. I have a ROM i can flash, but the recovery fails to flash it every single time, even after clean install. im fairly sure its my recovery that wont let me flash the rom but i also cant update that till i figure out how to at least get the phone to a homescreen. I honestly dont know much about odin but it looks like i may be able to try and flash it there, is this correct?

Starting to really hate EVOs, 2 Phones Bricked today

This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
oceanisbleu said:
This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
Click to expand...
Click to collapse
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
goliath714 said:
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
Click to expand...
Click to collapse
Yes of course I tried, the phone has been absolutely unresponsive. No amount of button holding is going to fix QHSUSB_DLOAD
Correct me if I'm wrong but http://forum.xda-developers.com/showthread.php?t=1948485 is the only known solution for QHSUSB_DLOAD due to firmware issue (I'm pretty sure this is what happened) or Jtag.
Here's the kicker, the files in that thread are no longer there so as it stands phone's just a Brick.
So for now I'm giving up on it and going samsung.
When I have the energy I may try working on the second one I have which turns out wasn't bricked instead the power button is unusable 90% of the time, but for now that's going to be left out of commission. Ultimately I need a backup because sprint techs seem to only operate on a 3 day basis when it comes to physical repairs therefore I plan to revive the second phone just to keep it as plan-b.
May all be user error but frankly what takes me minutes with a samsung seems to take days on the past couple of HTC phones I've had, so the ranting aspect of my post is merely in these regards and that only and out of frustration, this sucks because I'd take HTC build quality over samsung any day. I've been an HTC faithful since their first windows phone (5 years ago or so).
I know I have to fix the power button on the second phone but have any idea why it fails halfway through a factory RUU?
that's where I left off with it, it's S-On Unlocked running TWRP 2.8.0.1 I was trying to return it to full stock so I can have a go with facepalm S-Off procedure.
Did you relock the bootloader prior to attempting to run the RUU?
Magnum_Enforcer said:
Did you relock the bootloader prior to attempting to run the RUU?
Click to expand...
Click to collapse
out of 3 different RUUs I donwloaded only one worked, bootloader was relocked, ran RUU, Error 132 "Signature Error"
the one that did work the installer said finished, phone reboots but goes right back to bootloader where it says "Relocked" & "Security Warning" won't do anything else.

Phone died for no reason. Need help.

I had MultiROM on my phone, 2 roms, AOSP+RRO and SkyDragon GPE. I was booted into my AOSP+RRO ROM on MultiROM. I was calling someone. I missdialed and tried to hang up. The screen was black and there was still audio coming out, assmuning it was a small detection bug, I tapped the screen a few times, then I hard reset it after it didn't turn the screen back on, when I hardreset, it booted straight into SkyDragon and not MultiROM, When SkyDragon booted it said my phone was encrypted. I typed in random gibber(I didn't have the phone encrypted in the first place) and it said the password was correct however my data was corrupt. It booted into TWRP to try and factory reset, TWRP could not mount /data or /data/media. I tried erasing from fastboot, however I got the error FAILED (command write failed (Bad file descriptor)).
I have tried everything I know I can do to fix this, I think it may be a hardware issue, however, before I give up hope on the device, can anyone here, anyone, help me in the recovery process, or atleast find a way to salvage what is now an expensive paperweight?
I just dealt with some weirdness with my M8 last week. Let the battery go completely dead, I mean completely. Then connect the phone to computer and wait about half an hour. If it's a Windows machine it will probably do the chime thing when it actually resets itself.
In my case it took about thirty minutes of it being connected then ding, I looked over at the phone and it said charging 1% in the off screen.
Mine just died out of the blue. It was doing weird stuff the night before and I figured I'd just so a clean flash in the morning. I woke up and it was completely dead I wasn't able to do anything with it. I bought a cheap phone since I was waiting for the new phones coming out in a month anyway.
A couple days later I was working on a couple of phones and I pulled my sim out the m8 since I was sitting at one of my computers I figured what the hell I'll plug it in just in case...
When all this happened I let it get to 15% then attempted to boot it which it did. It acting like I had wiped all the caches doing the android apps update thing at first but now it's working fine.
I really don't know if this will help you, but I hope it does...
dank101 said:
It booted into TWRP to try and factory reset, TWRP could not mount /data or /data/media. I tried erasing from fastboot, however I got the error FAILED (command write failed (Bad file descriptor)).
Click to expand...
Click to collapse
Try booting into TWRP, pick the Wipe option, select Advanced, and try the option to format internal storage; and see if that helps.
redpoint73 said:
Try booting into TWRP, pick the Wipe option, select Advanced, and try the option to format internal storage; and see if that helps.
Click to expand...
Click to collapse
/data/media IS the internal storage.
dank101 said:
/data/media IS the internal storage.
Click to expand...
Click to collapse
I know. The format I suggested is a known fix for not being able to mount (corrupted) internal storage; at least in some cases.
redpoint73 said:
I know. The format I suggested is a known fix for not being able to mount (corrupted) internal storage; at least in some cases.
Click to expand...
Click to collapse
Did nothing.
I have a replacement One M8 on it's way!

Categories

Resources