Alright, so I'm not the greatest with phone tech, however normal computer tech is my thing so I can sorta get the idea of all this. But anyway...
So for ages I've had apps waiting to install updates, but I never get round to doing it. Today, at work, I was bored & decided to go through & install them. It was all going well, until my phone completely crashed whilst browsing Facebook in Opera. Updates were downloading/installing at this time, though as I say, they were all app updates, there were no OS updates or anything. So, I did what I'd normally do if it crashed or anything, I pulled out the battery & tried to turn it back on. Ever since, I now get to the "HTC Quietly Brilliant" screen, after which the phone cuts off, goes black, resets, & the cycle continuously continues until I remove the battery.
I am able to load it up into HBOOT (I think it's called, by holding down Vol Down + Power), with the following info at the top:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011, 23:36:27
Click to expand...
Click to collapse
With the following options:
Fastboot
Recovery
Factory Reset
Simlock
Image CRC
Click to expand...
Click to collapse
If I click on fastboot, it doesn't seem to work, as whilst it flashes through very quickly it says that it checks the SD & then can't find the images or something:
SD Checking...
Loading...[PC10DIAG.zip]
No image!
Loading...[PC10DIAG.nbh]
No image or wrong image!
Loading...[PC10IMG.zip]
No image!
Loading...[PC10IMG.nbh]
Click to expand...
Click to collapse
That's as best as I can tell, as it flashes through very quickly & is hard to catch what it says. Anyway, after that, it just returns to the original menu.
If I click onto Recovery, the phone instantly resets, goes to a white HTC screen, & then to a black screen with the phone & a red exclamation mark within a red triangle. I then press Up + Power & get the following text on my screen:
Android system recovery <3e>
Use volume key to highlight;
click power key to select.
Reboot system now
Apply update from sdcard
Wipre data/factory reset
Wipre cache partition
--------------
(a while down the screen)
E: Can't open /cache/recovery/command
Click to expand...
Click to collapse
If I restart the phone then, it just goes back to how it was. I would apply an update, but I don't know what update to apply or where to get them. And I've not tried to wipe anything as, well, I'll get onto that.
Now I've looked around various threads, & was only able to find one that was close enough to my exact problem & I saw that he was able to get his phone working, with your help, so I'm hoping you could help me too.
Now, the phone has never been rooted, or had any mods or anything of that kind installed. And, to be honest, I'd rather keep it that way.
I did have some backup apps installed on the phone (which, I think backed up to my SD Card), however I've never done a complete backup of the phone onto my computer. Therefore, I'd rather not have to factory reset my phone. Or atleast, I will, if there's a possible way of backing everything up first? Though, I'd much rather root the phone & keep everything, than keep it never-rooted & have to factory reset it; if that is an option?
I'm really at a loss as to what to do, & would hugely appreciate any & all help you can give me. As I say, this isn't my strongest area, but I can kinda work my way around it. I do have a Blackberry 9800 to use as a spare, however, I'm not sure which is worse: a broken HTC or that.
Oh, some other information that might be useful:
-The phone is British, bought from Phones4U (I think) early last summer & is on the Orange/T-Mobile network, with an Orange sim card.
-I saw on that other thread about using RUU, which I nearly went to go do, until I realised it wiped everything off the phone, so I stopped myself there.
-I can never remember which version of Android means what, but I'm pretty sure we've not had any major updates since I got the phone. There may have an update, but don't think I've had any of the major ones. I'd guess it was Android v. 2.2-ish? or 2.3ish?
That's all I can think of, though am happy to answer any questions you need to ask. Again, I'd be hugely greatful for your help. And sorry for the huge essay, however I wanted to try to give as much detail as possible, so you clearly knew the situation as best as I can describe. Thank you.
Edit: Could this work at all for me?
Unfortunately, as the phone is S-ON, you're really stuck with what you can do to the phone.
The symptoms you describe are fairly consistent with a fried emmc, in which case the phone is screwed and there is nothing you can do about it (except warranty return/sell for parts)
The only thing which might work would be an RUU, hoping it isn't a case of a fried emmc.
-Nipqer
Nipqer said:
Unfortunately, as the phone is S-ON, you're really stuck with what you can do to the phone.
The symptoms you describe are fairly consistent with a fried emmc, in which case the phone is screwed and there is nothing you can do about it (except warranty return/sell for parts)
The only thing which might work would be an RUU, hoping it isn't a case of a fried emmc.
-Nipqer
Click to expand...
Click to collapse
What does "S-ON" mean? Never heard of that before.
I'm assuming a "emmc" is some chip inside of the phone? What causes that to fry? Is there really nothing that can be done?
Any idea how long the warranty is for these phones? I really don't remember. I'd assume a year, but I dunno, may be longer? I do have insurance, I believe, on the phone but (as with the last time I had to claim, about 2 years ago) I don't want to get lumbered with a ****ty replacement & getting told the Desire Z range had been discontinued. I want my flip-out QWERTY full-size (well, not Blackberry-sized) keyboard, damnit!
Your only options @ this point is to attempt an ruu (rom utility update) you can go to the htc site for the latest. The s-on is security on (this you posted with your hboot info) or if you are lucky a simple factory reset will do. You won't be able to root your phone without a bootable os, so this is out of the question
Sent from my HTC Vision using xda premium
S-ON means the security flag is set to on, it means the emmc (embedded multimedia card/chip I think) has write protection on certain partitons (/system for example) and performs signature checks on everything that tries to get flashed, making sure its legit htc roms/updates.
There seem to have been a batch of dodgy emmc chips manufactured at some point, and they have a high chance of breaking, so that nothing can be written to it. No way to predict if/when it will break, but you can see (if you have a booting rom/recovery and shell access) whether your chip is more prone to breaking or not.
Standard manufacturers warranty should be about a year, though you can see if local consumer rights gaurantees extends that any? otherwise hope for the best with insurance.
-Nipqer
Alright so there's a bit of an update, albeit not positive. My phone now just sticks on the initial white screen with "htc" on it. Not even "quietly brilliant" appears. Doesn't reset anymore, just stays on until I remove the battery. Can still get to the HBOOT screen though.
Thanks for all the responses/help guys, I knew this would be the place to come to, as you've helped me alot in the past when I had my XDA Serra (HTC Touch Pro). I guess now there's not a lot really I can do? One person suggested trying the RUU, I guess I could try that? Failing that I'll have to contact HTC/phone carrier to see what they have to say about the matter. Is it certain then that there's nothing else that could potentially be done?
Related
I thought I had it all figured. Root, with Clockwork Recovery, Rom Manager. Nothing could go wrong. Now I am stuck at the splash screen with no Clockwork Recovery.
I searched fourum after forum to find a solution, but mine seems to be different. Just so you know I am 21, and a freelance computer technician so I am not afraid of the command line
What have I done to my device:
=Originally it had 2.1
=I rooted the phone via exploid method
=I installed CyanogenMod 6.1.1
+My computer only recognized my phone in HBoot mode, I think usb debugging is turned off though because I cannot acces my sd while it is in my phone.
I do have a microsd card reader
+I tried Esprimg.zip updates. It works .but I still cannot get into recovery mode.
For extra precaution, I backed up all of my sd card data on my pc.
Symptoms and problems:
+I am stuck at the white My tough slide 3g splash screen.
Holding up and power for at least 30 seconds does not get me in recovery mode. All I see is the white My tough slide 3g splash screen. No Black screen with a triangle(Biggest Problem)
+Holding down and power does get me into the HBoot.
+The recovery option will make the Mytouch slide reboot, but it will freeze at the splash screen.
+The clear storage option executed, but it did not solve my problems.
+I have also removed the battery, sim, and sd card.
Summuaray-
I need to get Into Recovery mode, but when I press up and power it does not work. I only see a white.I never though there would be a day where I could not get into recovery.
Also, I constantly charge the device so it wont turn off during an update.
Do you have S-OFF? If you do it should not be hard to recover.
If you don't I can't think of any other method now. But just to make sure which Esprimg.zip method did you tried? Because that should work in the first place.
Mine says S-On
Esprimg.zip
I used my microsd card reader to put esprimg.zip on the sd card. Boot the device while holding down and power. I let the phone check for the esprimg.zip and then the update was successful.
Conclusion:
I hold up and power and i cannot access recovery mode.
Possible causes:
By doing the clear storage, would that change my device to s-on. Honestly I never noticed s-on until now. However, I was able to root and get clockword mod 6.1.1 and it ran smoothly for a weeks.
darko4 said:
By doing the clear storage, would that change my device to s-on.
Click to expand...
Click to collapse
No. Only by flashing another bootloader will you get S-ON back. You probably did not have S-OFF before anyways but FYI Esprimg.zip does flash the bootloader so you're stuck on S-ON for now.
If the Esprimg.zip update method was successful it should have flashed back the stock recovery for you. I can't think of anything that could go wrong at this point except that u have a bad or corrupted Esprimg.zip. Did you use the champion build or the ENG build? If me I'd try to download it again and give it another go.
Good luck!
Ok so Esprimg.zip may be bad, and pretty much that is my only saviour;ok I understand.
I was using Esprimg.zip from other guides. Those were 137 mb
This time I used the one from here.
HOW-TO * Flash the Eng-Release to the Slide *6/15/2010
http://forum.xda-developers.com/showthread.php?t=703076
I am going to assume this the the eng build. It was 137.1 mb.
If this does not work the I guess I have to go champion build.
------------------------------------------------------------------
Failed
Champion build esprimg.zip is next.
A few more ideas.
manually install the recovery using fastboot.
troubleshooting without simcard?
My spl s-on so would that be possible?
Is there a way to maybe re root?
I read in one post that a guy sold it on ebay..i would hate to do that with just a month of ownership. would Htc make a warranty request even though I bought it used. Besides you only see bootloader and hboot spl s-on so how could they tell?
So you reach the screen where it asked you whether you want to install the update, you choose "yes" and it goes on to flash everything, radio, bootloader, yada yada, and it fails to boot?
Basically with S-OFF you can boot into fastboot and run
fastboot flash recovery recovery.img
in this case recovery img is CWM recovery. With S-ON fastboot flash is disable so it's not possible.
EDIT: If you do have the champion build on it's basically stock.
I have this exact same issue right now, I've tried the champion and engineering builds of ESPRIMG but with no success. I can't think of anything else that would be causing this in the first place, which is making it so difficult to troubleshoot. The only difference is that I was using CM7 instead of 6, but the exact same thing is going on. I have tried everything that the OP has with no luck. The only possible cause I can think of is that something was somehow corrupted while the phone was on and sitting on my table...because when I picked it back up, it was off and when I tried to boot, I got splash screen... Any other ideas?? I'm all out and just sitting here waiting for some genius light bulb to go off....attic's kinda dusty though..
With S-ON fastboot flash is disable so it's not possible.
So basically these are my options
esprimg.zip (if that does not work then use different)
Hboot clear memory,
with S-ON I have limited option
and keep it charged.
Although with fastboot and s-on is there something I could do?
Would rerooting be an option
darko4 said:
Would rerooting be an option
Click to expand...
Click to collapse
I don't see a root method in the forum that does not involve booting into a usable system.
Wait, you guys were able to flash the esprimg.zip right? Because in the guide when it says it requires root it's for flashing the mtd0.img first before rebooting into HBoot. Since you don't have a working system you cannot do that and if HBoot refuse to take your esprimg.zip then you need to do the Goldcard method. Otherwise I don't see why having root will make a difference.
So at this stage of the game I should do this..
1.get on my knees
2.put my hands together.
3.and just pray?
ok all jokes aside. Continue to try Esprimg.zip and update(all are successful but I still get splash)
I can't change my recovery since I have s-on
and no way of getting s off since i cant get in the phone, not even recovery,just h boot
So in a sense i have a lovely soft bricked mytouch 3g slide.
Later I might compose a list of the programs i had on the device, but i doubt that would make a difference. I appreciate the help and assistance, I am going to click the thank button for you gents.
In the mean while i got a tmobile comet for 136 one day shipping..No rooting on this one cause finals are coming and I do not have time to troubleshoot for hours. I love android cause of custom roms, but not being able to get in recovery mode...ah say no more. I am going to be one of those people who just downloads free software and complain to phone carriers about OTA.
Same here. I held off rooting and all until my exams were over because I know I'm going to go all the way until I get S-OFF.
I know many discourage S-OFF because it can potentially brick during the process but if you do read up and follow instructions very carefully it is really not that risky. And it'll be very useful in situations like this.
I'm sorry to hear you have a soft-brick. Maybe a dev will stumble upon and provides new insights but I afraid this is all we have in the forum for now.
to be honest i skimmed through the post, and im sure you did try this but just want to ask have you tried the official RUU update to see if you can get things back up running that way?
yeah I understand following directions carefully, but when you follow all of directions and get it working,and make backups, but then you turn the phone off and then turn it on. Then all of this happens.
ah let me stop my whining and download more esprimg.zip .
I just want to know what caused it. was it an application, cause if that is the case then I want to know so no one else get hurt.
(one interesting note, avg antivirus said my device was infected with viruses. It said with the apps, I did not clean it. i uninstalled avg. I presumed it was a false alarm cause the phone is rooted with applications with high privileged) Oh well
---------------------------------------------------------------------------------------------------------------------------------------------------
oh well. back to the esprimg.zip
never tried RUU, if it comes in a esprimg.zip then i guess i can try. if not then i do not know how to use it with mine in its current state
S on (so no advanced fast boot options
Hboot only
no recovery.
clear memory
only productive thing is successful esprimg.zip updates
its the official update to froyo, and need HTCsync and the RUU from htc how the installs procces goes i dont really know, but im sure there is a RUU update that you can use to update via bootloader,
ok i got htc sync
and the official exe.
my pc only detects the device in hboot. The device will read usb hboot.
1 might fiddle around for 20 mins to see whats what.
.
If it was like a esmprimg.zip then it would seem more feasible.
goood luck hope you get your phone back up and running
well a week ago it finally booted. I felt that it was a fluke so I pressed the power button to reboot. I tried to turn it back on then it was stuck at the splash screen.
I am now starting to think it is a hardware problem. Either way the unrooted tmobile comet,yes it is small, is doing wonders. The battery life is way better then a iphone 3g.
Just remember guys, if you get an android phone, make sure it is a popular one. That way you are more likely to get support because of the bigger fan base. Oh well it was fun while it lasted. The only thing I hate is that i could have gotten an xbox 360 for the same price. oh well, thanks for the assistance. i will lets you know any further updates.
Alright. For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read. That being said, this is my first post. I watched the newb video, read many forums (both xda and others), google searched, read some more threads, kept reading threads, tried some methods described in some threads, bookmarked some interesting threads for if my phone ever works again, and read some more threads.
I am not saying the answer is not already out there, I am saying I have reached my resourcefulness cap.
Anyway, to the root of the problem: I'm not entirely new to rooting, and am comfortable using recovery and hboot to flash roms. I also had a nandroid backup! for SOME SILLY reason, while in my clockworkmod recovery this morning (maybe slightly due to being half asleep which is why I now recommend being fully awake before entering hboot or recovery or rom manager....etc) I formatted the system on my phone. I THINK.
My phone will now load up to display the bootloader, and go into recovery mode, and flash roms, but when I flash a rom, nothing changes. If I boot my phone up, it will show a notification bar at the top like usual, a stock wallpaper, and that is IT! it will show a message notification and missed call icon since I have them, but the touch screen will not work. The rosie buttons at the bottom do not show up (i.e. phone button or all aps button) no apps appear, no clocks except for in the notification bar... hardkeys have no effect (home button search button menu or back) and volume keys will not work. The lock button will only lock and unlock the screen, not power off or reboot or anything. If plugged in at this point, it is charger only.
So, I can take the micro sd card out and put files on it from my PC via a microsd-usb converter thing...
I have tried putting new roms on the sd and flashing them from recovery, no effect. Tried the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe program, it always says that my phone has below 30% battery and will not continue (this is not the case as I have two batteries both have been fully charged because the phone will still charge them...)
And I have tried putting PC36IMG.zip files on my sd card to no avail.
I am thinking that the system was wiped because it seems like there is no boot image on the phones internal memory itself. I am currently looking for a way to place a boot image on the sd card to possibly flash it or some sort of update.zip so that my bootloader will ask me to update upon reading it.
Sorry for the long post, and ask any questions I will answer as best I can.
I am posting preemptively to the boot image adventure so that if it does not work, maybe I can have some help finding a solution by then.
I was going to take my evo to the sprint store since it is under warranty but if they go into recovery they will see clockworkmod recovery.
Thanks to all for any form of guidance!
I did just notice in my Bootloader menu (HBOOT-2.10.0001) that it says Supersonice evt2-3 **** S-ON
I don't know how because I thought it was a requirement that it says S-OFF to be rooted and flash roms, but I have definitely flashed roms before and gained su access to applications and such. BUT since it says S-ON would it then be covered by the warranty if it is not rooted?
Thanks again.
I you want to flash a boot image, you can take the boot.img from an RUU for the firmware you are, place it in your adb tools folder, then flash it using the commands:
fastboot flash boot boot.img
fastboot reboot
I'm not sure how to identify what firmware I am. Unless your talking about the Hboot version? and also, I can't place anything in any folder except onto my sd card. I have no access other than that to the phone. On the sd card there are no files except for what I put on there.
...aaand not to mention I don't know what adb is exactly...
Does your phone still go to clockwork when you go to recovery?
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Timeconsumer10 said:
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Click to expand...
Click to collapse
Welcome, but yes, you do need to have had usb debugging enabled, so we'll see how that goes.
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Timeconsumer10 said:
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Click to expand...
Click to collapse
Lol, it'd take you 200,000 days since you can only thank 5 times a day Though glad you're rooted now.
shortydoggg said:
Does your phone still go to clockwork when you go to recovery?
Click to expand...
Click to collapse
Yes it still goes to clockwork because its rooted.. now my screen legitimately does not work in certain areas of the screen (not responding to touch) so I'm going to try and get it stock stock stock unrooted and go for warranty replacement. Any ideas please let me know. Currently trying RUU Supersonic...
So, I got an ERROR [110] message from the RUU package its a file open error... :/ now i dont know what is up. Says I need a complete RUU package. Looking for another one or another option now.
If i boot phone normally now it just goes to a black screen with "htc" in the middle and "!" in a triangle in all four corners. Can't do anything from that screen.
If I boot into bootloader once where it says SHIP S-OFF at the top and instead of recovery and all those options it just says RUU but you cant do anything there... :/ I now, however cannot even get to the bootloader screen.
Could they tell it is rooted?
Maybe I could say I finally decided to do sprints OTA update that I've been denying for a while and this is the result.
Anyone agree disagree?
COCLUSION!
So. Since it has just the HTC logo and four error icons one in each corner... I took it into a sprint repair store. It would not boot into bootloader as a hard reset, so the guys at the store were stumped. They had actually never seen this before =). They asked me if I rooted it and all so I just played dumb. I told em I didn't know what that really was. They kinna explained it and I told em I didn't even have a computer (not a lie actually I sold mine and now use my dads or gfs lol). The logo on the screen was an oooold htc logo from like hero or so. So they just put it in the system as a wont even turn on type of thing and gave me a new phone since I was under warranty =) gonna see if I can live without root juuust for a little bit because work and school are gonna keep me busy for a while. I am certain to return though!
Can't wait to see what the devs can do by then!
Thanks to all for the help!
Hi there,
I had a very nice trip with my rooted desire with a miui rom on it for now maybe, 1 year smthg.
Recently, i bought a new µSD and wanted to prepare it for my phone ; i downloaded rom manager, and tried the "partition SD" functionality, which told me that i would have to update my clockworkmod, which i tried with the "update recovery" in it, which failed.
After a while, i found that i forgot to S-OFF my phone, and that was the reason why i couldn't update the recovery. So i decided to S-OFF. Unfortunately, my phone didn't went to the last step, and stayed stuck at the boot screen until its battery died, maybe an hour after.
I began a long journey trying to figure out if my phone was bricked or not, since i wasn't able to boot it up ; only the hboot was responding. I tried MANY ways, MANY posts, i tried to flash with a nand backup without success ('access denied'), i tried to flash just the recovery (same or 'signature failed'). I tried to put a PB99IMG.zip file from alpharev into my phone without any success...
BUT. I succeed in recovering my phone with putting a stock PB99IMG.zip from shipped-roms and it boots up very well on a crappy sense rom.
From that, i tried hard to root it again since i want to try again to S-OFF it, and after that, return back to my beloved miui rom. I'm stuck because of a mysterious problem into my phone. It looks like it doesn't like the third step which (i guess) requires a boot script. So nothing happens to it, it freezes to the bootscreen, while unrevoked says "waiting for reboot..." endlessly.
I succeeded once (only) in passing this step, but then unrevoked said to me something like : "Internal error: failed to unlock NAND flash?" which seems crazy since i'm in a 0.93 HBOOT (since the RUU reset). I hadn't any Superuser app nor signs of rooting ("su" command failed in terminal).
For now, i'm trying to root it via the Visionary app, but i don't think it will work.
If anyone has any suggestion in making things better, i'll be pleased to hear !
PS : I'm writing this post because i feel it could be full of useful infos for anyone else stuck with a "bricked" phone.
use this guide to S-OFF, install custom recovery and root.
read all the instructions, several times.
oh and rom manager is often not recommended for this phone as it can often cause usb bricks. once s-off you can flash different recoveries via fastboot or android flasher.
use gparted or 4EXT recovery to partition your sd card.
Unfortunately, it seems like the time for me to change phone has come.
While i was doing an other time a RUU reset because of loopboot created by an unrevoked related bug, my phone decided to stop, and die. The battery is still charged — i can feel the fuzz with putting my tongue on it — but the phone just doesn't turn on ; it doesn't show the charging led when i put it on charge...
I'm currently looking for an other device, such as the Desire S (because of the size, mainly ; others blockbusters are too big)
If someone has an idea to make my Desire turn on again, anything i can do, i will do.
Thx for the answer, the guide link, and all !
ynk said:
Unfortunately, it seems like the time for me to change phone has come.
While i was doing an other time a RUU reset because of loopboot created by an unrevoked related bug, my phone decided to stop, and die. The battery is still charged — i can feel the fuzz with putting my tongue on it — but the phone just doesn't turn on ; it doesn't show the charging led when i put it on charge...
I'm currently looking for an other device, such as the Desire S (because of the size, mainly ; others blockbusters are too big)
If someone has an idea to make my Desire turn on again, anything i can do, i will do.
Thx for the answer, the guide link, and all !
Click to expand...
Click to collapse
don't just go flashing RUU's randomly, you may get amoled/slcd incompatibility for instance, which is what this might be.
try reading the troubleshooting guide, you can probably save your phone.
read carefully before you do anything in future...this situation could probably have been avoided
Thanks a lot again
I should be more patient when trying to do things, but it's kinda annoying not to have it working...
Btw, i wasn't acting *that* randomly (at least, for me) : since anytime i was using unrevoked was blocking the phone onto the boot screen, the only way i found to restore it was flashing it again. But yeah, maybe it was done too randomly though...
The guide you gave me is full of good advices, but the only thing that could be matching for my case is a bad RUU flashing ; this doesnt look to be my case, since even if i put my phone on charge, the charging led doesn't turn on. The phone doesn't warm after pressing the power button... It looks like there's something related to electricity inside that have been broken somewhere... Don't you think so ?
[EDIT] I found some guys having my (new) problem here : http://www.htcdesireforum.com/htc-d...h-on-or-respond-to-a-charger-what's-happened/ I'm quite relax since it's not a "0day" problem : lots of people are talking about it, so i have some solutions : wait and pray, if not, try another battery, or let it dead.
ynk said:
Thanks a lot again
I should be more patient when trying to do things, but it's kinda annoying not to have it working...
Btw, i wasn't acting *that* randomly (at least, for me) : since anytime i was using unrevoked was blocking the phone onto the boot screen, the only way i found to restore it was flashing it again. But yeah, maybe it was done too randomly though...
The guide you gave me is full of good advices, but the only thing that could be matching for my case is a bad RUU flashing ; this doesnt look to be my case, since even if i put my phone on charge, the charging led doesn't turn on. The phone doesn't warm after pressing the power button... It looks like there's something related to electricity inside that have been broken somewhere... Don't you think so ?
[EDIT] I found some guys having my (new) problem here : http://www.htcdesireforum.com/htc-d...h-on-or-respond-to-a-charger-what's-happened/ I'm quite relax since it's not a "0day" problem : lots of people are talking about it, so i have some solutions : wait and pray, if not, try another battery, or let it dead.
Click to expand...
Click to collapse
that problem sounds different as that was posted ages ago, and they weren't messing around with rooting and RUUs...
i don't think you should 'wait and pray, try another battery, or let it dead'
can you get to recovery/bootloader/fastboot at all? please post more details. if you can then it's probably not bricked.
i'm unsure of whether you've actually tried anything in the troubleshooting guide. try [2] advanced boot problems, S-ON. create a goldcard and try the WWE RUU
if none of it makes sense ask directly in that thread
and if you get the RUU to boot, don't use unrevoked...follow my 1st reply...
I stopped all the things i was doing when i had your reply, trust me !
As i said, i can't get the device to be powered on ; since, i'm not able to have any access to hboot, fastboot, nor adb. The phone does not charge when plugged to a charger neither to a computer. The led stays black, and the battery doesn't get warm (which normally does when charging).
Since the phone doesn't turn on, the guide you gave me is useless (but i learnt a lot from it, so thanks for that). The only section which *could* have been useful was the one talking about wrong RUU flashing with SLCD off ; but since my screen was working, and the symptoms are different (my phone is not recognized by the computer), this is not describing my problem definitly.
Be sure that if i can boot that phone once again, i'll follow your 1st reply and won't use unrevoked on it ever...
I'm trying now to find an other battery, to know which from the battery xor the mobo of the phone is dead. If battery, i'll just buy a new one ; if mobo, i'll buy a Desire S, since my phone reached the warranty limit, and i would have to pay to repair it...
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
kbeezie said:
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
Click to expand...
Click to collapse
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
helstonrampersad said:
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
Click to expand...
Click to collapse
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
helstonrampersad said:
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
Click to expand...
Click to collapse
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
kbeezie said:
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
Click to expand...
Click to collapse
This is the boot loader screen that i see
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-26.13.04.19_M
eMMC-boot
Apr 13 211, 14:51:54
Im pretty sure the phone was never rootded before
The Android Manual said:
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
Click to expand...
Click to collapse
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
I don;t know what to do
helstonrampersad said:
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
Click to expand...
Click to collapse
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
The Android Manual said:
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
Click to expand...
Click to collapse
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
helstonrampersad said:
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
Click to expand...
Click to collapse
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
http://shipped-roms.com/index.php?category=android&model=Vision
Thats is the above link i used and i used all the ones that start with "PC10" I rename them to PC10IMG.zip so the phone can recognize it and it did. The only problem is that after it tries to install is say something along the lines of version is older or newer since i tried multiple packages. One package was going through the process and after that it didn't do anything, it didnt say failed or reboot or anything like that. Ive been trying to fix this for like a week and a half now. Ive even flashed custom PC10IMG.zip to see if it could help but nothing the furthest ive gotten is the phone boots for like 2 seconds the screen is blurry and the shuts off and there is an orange light in top right that wasn't lighting up before. Here are the links for the custom packages
http://forum.xda-developers.com/showpost.php?p=10583834&postcount=33
http://forum.xda-developers.com/showpost.php?p=10966727&postcount=63
Cant thank you enough for helping me this is really frustrating
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
If what i explained above is not what you were referring to then let me know your way
helstonrampersad said:
If what i explained above is not what you were referring to then let me know your way
Click to expand...
Click to collapse
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
I know it can be risky but im desperate for a fix. Ill try the package you linked. I download it and rename it to PC10IMG.zip? Ill get back after im done if you have any other suggestion please let me know.
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
Im confused on which one to flash I have a T-Mobile HTC G2 which one will i flash?
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
demkantor said:
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I am new to XDA how can i do that?
helstonrampersad said:
I am new to XDA how can i do that?
Click to expand...
Click to collapse
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
eboy_gb said:
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
Click to expand...
Click to collapse
Though ideally using an actual IRC client will work much nicer than a web chat one.
Same problem, but desire z S-ON
Hey guys.
I have the same problem with the boot loop /semi brick. Expect I never had any problem before, with the phone. I have tried taking out the sd card, starting it agian. I have tried without simcard. I have tried to flash the ROM with RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed
via Hboot Fastboot USB PLUG mode (which was the only mode the aplication was progressing in until it want to restart the phone in bootloader), but the phone frezzes and the aplication on the computer just keep working, without progress.
The factory reset just frezzes the phone.
The only thing reali seem to not frezze the phone is the revocery option. Here the phone react with restart showing a image of a phone with two green arrows bent around, over the phone. then it turns off the display and vibrate 4-5 times, og stays turn off not reacting to anything other then taking out the battery and you can start the phone once again.
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-26.10.04.19_M
eMMC-boot
Apr 11 2011, 23:36:27
Have no idea but the version of android. I know that usb debugging is NOT on Any hjelp is a big help. I'm a noob, And I have been searching for 3 days for a solution, so I just hope you can help my, otherwise it is going for a repair at the place I bought it.
Thanks
I need help you guys or I'm really screwed . My phone had been working perfectly fine on a rom that I had been running for a month, when out of nowhere I had a random reboot, don't know what could have caused it because I was just checking my messages on the facebook app, but ever since then my phone would not get past the boot screen, to make matters worse I could not get the phone to go to recovery doing the whole power+vol up. Don't know what happened to twrp but it would only show up when I would turn off the phone and plug it to charge. When the charging battery pops up with the percentage if I tapped the screen and hit the power button it would flash the twrp main menu for a quick second and it would disapear. I could not interact with twrp at all. After many attempts of turning off and doing the power+vol up I got the bootloader to come up and since everything at this point had failed I picked the factory reset option from the bootloader. Now my phone will only load straight to the bootloader and nothing else. To make matters worse no fastboot commands are working aside from getvar and show devices. I can't erase cache,flash a recovery or relock the bootloader or go back to S-On which means I cant use the warranty. Tried the RUU and it say's it can't communicate with the phone. So basically i'm looking at a paper weight with a bootloader that won't take any commands and no system image. I've been looking everywhere for a solution and the closest thing I could find is flashing the expanded 1.57 firmware in http://forum.xda-developers.com/showthread.php?t=2754063 from my sdcard but the link is dead
raphi809 said:
After many attempts of turning off and doing the power+vol up I got the bootloader to come up
Click to expand...
Click to collapse
Bootloader is power+vol down
raphi809 said:
since everything at this point had failed I picked the factory reset option from the bootloader.
Click to expand...
Click to collapse
I think this is your main problem. Factory reset in bootloader on a modded phone corrupts the internal memory. Use Windows explorer or Device Manager to find the phone's internal memory and format it.
Internal Memory cannot be mounted as USB on the M8 and hence it cannot be formatted from within Windows. Also, no TTY solution talks to the chip afaik. So this way is closed too.
The symptoms described sound like not only the System/Data/Recovery partitions got corrupted but also bootloader to some extend.
Something has happened while your phone was booted that corrupted large portions of your NAND. This does sound like a real hardware failure like a broken RAM to me. But then again RAM would not cause (corrupted) writes to bootloader. That partition only gets overwritten during a flash process. Not from within the phone so i would have no clue how that could get corrupted.
Are you dead sure the drivers on your PC are alright? Are you 101% sure the communication doesnt work because of the phone having an issue?
I would make totally sure drivers for fastboot are ok and then try to run (just any) RUU and try to rewrite the partitions. If you can't get that done, you will have to swallow that bitter pill and send it in. Well i would anyway. No idea what else you could try.
raphi809 said:
I need help you guys or I'm really screwed . My phone had been working perfectly fine on a rom that I had been running for a month, when out of nowhere I had a random reboot, don't know what could have caused it because I was just checking my messages on the facebook app, but ever since then my phone would not get past the boot screen, to make matters worse I could not get the phone to go to recovery doing the whole power+vol up. Don't know what happened to twrp but it would only show up when I would turn off the phone and plug it to charge. When the charging battery pops up with the percentage if I tapped the screen and hit the power button it would flash the twrp main menu for a quick second and it would disapear. I could not interact with twrp at all. After many attempts of turning off and doing the power+vol up I got the bootloader to come up and since everything at this point had failed I picked the factory reset option from the bootloader. Now my phone will only load straight to the bootloader and nothing else. To make matters worse no fastboot commands are working aside from getvar and show devices. I can't erase cache,flash a recovery or relock the bootloader or go back to S-On which means I cant use the warranty. Tried the RUU and it say's it can't communicate with the phone. So basically i'm looking at a paper weight with a bootloader that won't take any commands and no system image. I've been looking everywhere for a solution and the closest thing I could find is flashing the expanded 1.57 firmware in http://forum.xda-developers.com/showthread.php?t=2754063 from my sdcard but the link is dead
Click to expand...
Click to collapse
AFAIK, if you can boot into the bootloader, you can still fix it with a full RUU or .zip with all the partitions. (unless you have hardware damage), because if you have corrupt partitions your phone will have a black screen and can be flashed by directly communicating with Qualcomm chip with linux(tried it once on my HTC One X, didnt work as my partition table itself was corrupt)
raphi809 said:
I need help you guys or I'm really screwed . My phone had been working perfectly fine on a rom that I had been running for a month, when out of nowhere I had a random reboot, don't know what could have caused it because I was just checking my messages on the facebook app, but ever since then my phone would not get past the boot screen, to make matters worse I could not get the phone to go to recovery doing the whole power+vol up. Don't know what happened to twrp but it would only show up when I would turn off the phone and plug it to charge. When the charging battery pops up with the percentage if I tapped the screen and hit the power button it would flash the twrp main menu for a quick second and it would disapear. I could not interact with twrp at all. After many attempts of turning off and doing the power+vol up I got the bootloader to come up and since everything at this point had failed I picked the factory reset option from the bootloader. Now my phone will only load straight to the bootloader and nothing else. To make matters worse no fastboot commands are working aside from getvar and show devices. I can't erase cache,flash a recovery or relock the bootloader or go back to S-On which means I cant use the warranty. Tried the RUU and it say's it can't communicate with the phone. So basically i'm looking at a paper weight with a bootloader that won't take any commands and no system image. I've been looking everywhere for a solution and the closest thing I could find is flashing the expanded 1.57 firmware in http://forum.xda-developers.com/showthread.php?t=2754063 from my sdcard but the link is dead
Click to expand...
Click to collapse
Don't try to s-on if your s-off. Just get phone in fastboot bootloader mode and run ruu. I've done it several times so it will connect. Just go through the ruu setup and watch it work. If u can't find ruu for latest firmware then try a older one your s-off so u shouldn't have to do anything but plug the phone in fastboot bootloader mode and run ruu.
I never even relock the bootloader when I flash ruu. And I allways flash in fastboot bootloader mode.
I hope this helps. If not I will try to help u figure it out.
Sneakyghost said:
Internal Memory cannot be mounted as USB on the M8 and hence it cannot be formatted from within Windows. Also, no TTY solution talks to the chip afaik. So this way is closed too.
The symptoms described sound like not only the System/Data/Recovery partitions got corrupted but also bootloader to some extend.
Something has happened while your phone was booted that corrupted large portions of your NAND. This does sound like a real hardware failure like a broken RAM to me. But then again RAM would not cause (corrupted) writes to bootloader. That partition only gets overwritten during a flash process. Not from within the phone so i would have no clue how that could get corrupted.
Are you dead sure the drivers on your PC are alright? Are you 101% sure the communication doesnt work because of the phone having an issue?
I would make totally sure drivers for fastboot are ok and then try to run (just any) RUU and try to rewrite the partitions. If you can't get that done, you will have to swallow that bitter pill and send it in. Well i would anyway. No idea what else you could try.
Click to expand...
Click to collapse
Where in Germany do you live, SneakyGhost? My M8 has been giving me nightmares, It is S-Off and today I changed the CID/MID to that of developer edition and installed the relevant Android Marshmallow firmware.zip and then ran the MM RUU from HTC Dev page. No matter what ROM I tried on SuperCID or even on this new MM software, many apps keep on crashing. Unfortunately this has stopped working, unfortunately that has stopped working. I have 3 other friends with M8, never has their phone seen an app crash. I have to restart the phone many times daily to get it to work for some time, while another app randomly crashes. Can you help me?
Thanks
Well if it's crashing a lot after flashing a complete RUU I'm sure the device is faulty. Maybe bad NAND or bad ram. Send it in to HTC. Don't bother setting it back S-ON cuz a.) They'll know anyway and b.) Going back S-ON is dangerous and locks you out from most repair methods you could try in case HTC won't service your device. Just saying because a lot of people seem to be thinking that going back S-ON is increasing their warranty claim chances.
Sneakyghost said:
Well if it's crashing a lot after flashing a complete RUU I'm sure the device is faulty. Maybe bad NAND or bad ram. Send it in to HTC. Don't bother setting it back S-ON cuz a.) They'll know anyway and b.) Going back S-ON is dangerous and locks you out from most repair methods you could try in case HTC won't service your device. Just saying because a lot of people seem to be thinking that going back S-ON is increasing their warranty claim chances.
Click to expand...
Click to collapse
My phone is out of warranty, will HTC entertain me? How much will thay charge for repairs? I think out of warranty repairs cost more than getting a used working phone.
harri2cool said:
My phone is out of warranty, will HTC entertain me? How much will thay charge for repairs? I think out of warranty repairs cost more than getting a used working phone.
Click to expand...
Click to collapse
Super different from country to country. HTC Germany service is worse than it ever was. They contract Regenersis since January 2015 here, same company as in the UK.
You have to keep in mind that HTC's contractors do the checking and validating of your warranty and they go by very tight rules. You can argue and escalate as much as you want, they will charge you if your local HTC is in any way similar.
Globally, HTC has worsened their service approach a lot. I'm waiting for a service/warranty decision regarding an old M7 since half a year. A mate from our team waited six months too, but for HTC to find his M9 which they lost and refused to replace. He only just got it back, unrepaired despite full warranty eligibility.
To sum it up, if your device is older than six months, don't bother. Not worth the hassle and not worth the money. HTC won't do sh!t after six months usually. And the prices, like you guessed, are a nightmare too.
If your NAND turns out to be faulty like I assume, it'll be a mainboard replacement, which equals a new phone. And THAT can be had a lot cheaper on eBay or craigslist.
Motherboard replacement is 200 USD give or take 25 on model (DNA/butterfly was $150 and a m7wlv motherboard was $175. I priced my AT&T m8 and it was $215) for the HTC service centers here in the US. I assume the EU ones are similar in price.
Before blaming hardware, have you changed mid/cid back to stock and ran an ruu to be sure it wasn't a bad flash or compatibility?