Related
So the screen of my g2 is all black, and Tmobile has allowed me to do a warranty exchange of the phone, it is s off and clock work recovery with a OTA non rooted file system (did a factory reset in clock work so my personal info wouldnt still be there, but did a back up before so i can still restore. i dont believe i had usb debugging enabled). Can someone help me to get it back to s-on with normal recovery... I have been trying to think how to do it, but cant figure it out. I have another g2 that i do all the same steps with. Any help is appreciated.
Dont worry about it. If your screen is broken they cant see it either! They will wipe the phone replace the screen and give it to someone with a loose hinge. If you still want help did you try to use adb? Does it connect?
Sent from my HTC Vision using XDA App
shortlived said:
Dont worry about it. If your screen is broken they cant see it either! They will wipe the phone replace the screen and give it to someone with a loose hinge. If you still want help did you try to use adb? Does it connect?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
That's stupid. They can tell by diagnosing the phone when they plug it in. They are going to see whether or not you have the factory rom
Sent from my T-Mobile G2 using XDA App
It is not looking like it is going to connect, but if you are pretty sure that they arent gonna look, i wont even sweat it.
I think this thread might work:
http://forum.xda-developers.com/showthread.php?t=835971
But it might be tricky getting past the first step without a screen... but fastboot and adb usually solve most problems...
What hboot do you have installed? Did you install the hboot-eng.img when you rooted?
My theory is that you can use fastboot to flash the parts of the rom, in the right order. Again, this is just my theory and I've never tried this.
http://forum.xda-developers.com/showthread.php?t=838484
The stock ROM has all the parts on it, but it flashes hboot first, which does version checking and will fail when it tries to install the later parts. If you extract the system, recovery, boot images out of the stock rom, you can use fastboot flash {partition} to restore these, then use fastboot flash hboot {hboot} to restore the bootloader. I don't think there will be any way to verify that this works without a screen*.
*While you are at it, you might be able to use the new G2 to backup a rom with debugging enabled and then flash the system.img (and maybe userdata.img) to the broken one, so that you can verify that everything worked.
Hopefully, someone who knows more about flashing that I do can verify if this has a shot at working or not.
Disclaimer: I have no idea if this will work or not. Flash at your own peril.
i have the s-off eng hboot. clock work recovery and i have stock rom installed, i was kind of thinking i could use something to restore the recovery to stock, and somehow flash original hboot, but i really have no idea to actualy do this.
is there any way that i can hex edit the partition on the other phone do a nandroid, then restore the nandroid on the broken phone, then use hboot to flash the ota update and get the hboot and recovery back to original?
Throw it against the wall until it doesn't connect anymore or turn on. Problem solved.
I'm not sure if this will work anymore... I tried to flash the .img parts from a nandroid backup and it seems to get hung up. My terminal has been "sending system.img" for the last 10 minutes. I wonder if this has something to do with how the bootloader was patched to get root?
DJAeroX26 said:
That's stupid. They can tell by diagnosing the phone when they plug it in. They are going to see whether or not you have the factory rom
Click to expand...
Click to collapse
You really think T-Mobile are going to plug in and do diagnosis on a phone with a broken screen ? We're talking about a phone carrier, not HTC themselves
use screencast, its simple to use and puts your screen on your pc..I have used it several times for issues such as this.
how do i install it if i dont have usb debugging enabled.
bobsfoot said:
how do i install it if i dont have usb debugging enabled.
Click to expand...
Click to collapse
hmmm...wait 1, will research it
Of course they can tell if its rooted my point is they wont care to take the time. I am no authority for sure but i will ask this... have you seen one single person who has been denied because they rooted they're phone?
Sent from my HTC Vision using XDA App
I was in a similar situation as you but with a Desire Z, Somehow the screen decided to give up on me so have sent it back to where I bought it from in the UK.
I am fairly sure the RUU changes it to s-on doesn't it? I just ran the RUU and sent it back after screencasting to do a backup of my rom. Still unsure as to what the end result will be with my phone however.
so today the new phone comes, should i just fastboot a new recovery then do a ruu update to put s on, and leave the phone broke and be like no idea, or is there a way to edit the partition version in fast boot?
or do i leave it alone, and just hope they dont care.
They wont care.
steviewevie said:
You really think T-Mobile are going to plug in and do diagnosis on a phone with a broken screen ? We're talking about a phone carrier, not HTC themselves
Click to expand...
Click to collapse
I'm just saying, I work in retail and usually when someone brings something back to exchange when there is a problem...I thouroughly check to make sure if the problem was the user's fault, then i deny the return. They do lose money even if it is a warranty exchange
Sent from my T-Mobile G2 using XDA App
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.
Few days ago, my G2's screen just went blank (dark blueish if I press any buttons on it). I live in Canada, so can't send it back to Tmobile since I'm not with them. But, I can send it back to HTC since it's still under warranty. Only problem is that I rooted the phone and s-off and then flashed Virtous Rom on it couple of months ago.
With the help of a senior member (eunkipark92), i was able to install ADB, and using that I can see that it recognizes my device when connected with PC. Now, I don't know whether the problem is with my phone's software or with the hardware (screen) itself.
I say that because I had a pattern set up to unlock the code before the screen went blank and even now I can swipe my finger on the screen in the specific manner that I used to before and it would unlock the phone. The screen still remains blank (dark blue) ofcourse, but I can change the phone's profile from vibration to loud etc after unlocking the screen by pressing the volume key up or down.
I was told by another member (PaganAng31) that if I can totally brick the phone using a command in ADB something like "dd = /dev/block/mmblk1p3" there will be noway for HTC people to figure out whether or not the phone was rooted before. But he wasn't sure and asked me to post here.
Now my first attempt will be to fix it somehow or unroot the phone and put the stock rom back in using ADB and then send it back to HTC. If I can't do that, then I would totally brick it (only if it's 100% sure that HTC won't figure out that this phone was rooted before) so that they can totally flash it or change the screen or send me a replacement. Also what's the exact command that is used in ADB and how do you use it for totally bricking the phone?
Any kind of help will be appreciated. Thanks
Its probably hardware issue. I heard that g2 screen will just stop working...display failure..
I read this somewhere before I purchased g2 but I still bought it anyway.
Anyways..
Have you downloaded the hboot engineer and recovery.img?
I would like to give you step by step instruction but I haven't used adb since I got rid of my nexus one...so I don't really rememebr the commands to flash stuffs:/ sorry.
If it is software issue you can fix it since you were able to get adb working
But if it doesn't work flashing a new hboot,recovery and a new rom its mostly lcd failure or ribbon is damaged.
U can use hboot pc10img method to put ur stock rom and radio. But I don't know a way to unroot it if you can't see the screen.
When I had nexus one and when I had to send it for repair.
(My bootloader was unlocked with stock rom)
They didn't charge me for rooting. Just my experience with htc.
If there is anything I can help pm me.
Sent from my HTC Desire Z using Tapatalk
eunkipark92 said:
Its probably hardware issue. I heard that g2 screen will just stop working...display failure..
I read this somewhere before I purchased g2 but I still bought it anyway.
Anyways..
Have you downloaded the hboot engineer and recovery.img?
I would like to give you step by step instruction but I haven't used adb since I got rid of my nexus one...so I don't really rememebr the commands to flash stuffs:/ sorry.
If it is software issue you can fix it since you were able to get adb working
But if it doesn't work flashing a new hboot,recovery and a new rom its mostly lcd failure or ribbon is damaged.
U can use hboot pc10img method to put ur stock rom and radio. But I don't know a way to unroot it if you can't see the screen.
When I had nexus one and when I had to send it for repair.
(My bootloader was unlocked with stock rom)
They didn't charge me for rooting. Just my experience with htc.
If there is anything I can help pm me.
Sent from my HTC Desire Z using Tapatalk
Click to expand...
Click to collapse
Ok. So what's the first step now? Do we reflash hboot and recovery? I flashed it 3 months ago using this method:
http://forum.xda-developers.com/showthread.php?t=833965
Now to reflash it, do we use this method on the wiki and just follow it. It looks pretty straight forward?
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
If that's the one, then the link to Engineering hboot for Tmobile G2 is broken. Any alternative?
Also do you know the command to completely brick the phone in ADB in case we are unable to fix it?
I am interested as well. Coincidentally my screen just went completely black 3 hours ago. I think the lcd is dead. Last thing I did earlier today was that I flashed from the ..04.30 radio to the ..02.26 while troubleshooting HSDPA issues.
I think I could settle for adb shell commands to flash the roms if anyone can point me to a link. Closest i've found is a link to the G1 forums (I used to have one) but that shows how to a manual nandriod restore which is a bit different.
Last resort as the OP is asking, will creating a typo while following a rooting guild do the trick?
icruisin said:
I am interested as well. Coincidentally my screen just went completely black 3 hours ago. I think the lcd is dead. Last thing I did earlier today was that I flashed from the ..04.30 radio to the ..02.26 while troubleshooting HSDPA issues.
I think I could settle for adb shell commands to flash the roms if anyone can point me to a link. Closest i've found is a link to the G1 forums (I used to have one) but that shows how to a manual nandriod restore which is a bit different.
Last resort as the OP is asking, will creating a typo while following a rooting guild do the trick?
Click to expand...
Click to collapse
Good luck buddy. Let me know if you find a way to get it fixed or brick it. From another thread I found the command is something like:
dd if=/dev/zero of=/dev/block/mmcblk0p*
Where * = the partition number.
But I just don't know how to apply it.
Did you guys get this going? Op sent me a pm for help a few days back and I just got this. I had the same thing happen.
You can brick using the dd= command. You would follow the OLD eng hboot root guide except instead of having the real hboot.img you would have a random text file named hboot.img inplace of it. HOWEVER, YOU DO NOT WANT TO DO THAT.
You can put back to stock. Make sure phone has a good charge or it won't flash properly.
First things first. If there is anything you want to save off the phone first, ie good (bad) pic mess from your gf or similar , then search on googl.code or xda for screencast. It allows you to see the phones screen on your comp screen (requires adb installed and working). It works in the os, and in recovery, but unfortunatly doesn't work in fastboot.
After everything you want is saved, backup your sdcard to your comp, and clean off sdcard. If you are rooted per gfree use it to revert back to s-on (if you are old eng hboot only method, skip that step). Replace the misc.img as per the unroot guide. Then put the stock shipped PC10IMG on the root of your sdcard. Boot into fastboot by holding down vol and power. Give it few mins to read and load pcimg, let's say 5 mins to be safe. Press vol up to confirm to reflash ( I know u can't see screen, but have faith). It will reboot in the middle of process to flash radio, then will finish flashing. It should only take 10 mins, but leave it for like 30 to be safe. Then press power button to reboot.
At this time it should boot into stock os. Remember first boot take awhile, so give it a min. To confirm it worked, do 2 things. On comp type adb remount and should say not allowed. Also try using screencast should not work since usb debugging is required for it, and its turned off by default on stock os.
Goodluck, hope this helps. If anyone finds this usefull of needs any help, let me know.
fastludeh22 said:
Did you guys get this going? Op sent me a pm for help a few days back and I just got this. I had the same thing happen.
You can brick using the dd= command. You would follow the OLD eng hboot root guide except instead of having the real hboot.img you would have a random text file named hboot.img inplace of it. HOWEVER, YOU DO NOT WANT TO DO THAT.
You can put back to stock. Make sure phone has a good charge or it won't flash properly.
First things first. If there is anything you want to save off the phone first, ie good (bad) pic mess from your gf or similar , then search on googl.code or xda for screencast. It allows you to see the phones screen on your comp screen (requires adb installed and working). It works in the os, and in recovery, but unfortunatly doesn't work in fastboot.
After everything you want is saved, backup your sdcard to your comp, and clean off sdcard. If you are rooted per gfree use it to revert back to s-on (if you are old eng hboot only method, skip that step). Replace the misc.img as per the unroot guide. Then put the stock shipped PC10IMG on the root of your sdcard. Boot into fastboot by holding down vol and power. Give it few mins to read and load pcimg, let's say 5 mins to be safe. Press vol up to confirm to reflash ( I know u can't see screen, but have faith). It will reboot in the middle of process to flash radio, then will finish flashing. It should only take 10 mins, but leave it for like 30 to be safe. Then press power button to reboot.
At this time it should boot into stock os. Remember first boot take awhile, so give it a min. To confirm it worked, do 2 things. On comp type adb remount and should say not allowed. Also try using screencast should not work since usb debugging is required for it, and its turned off by default on stock os.
Goodluck, hope this helps. If anyone finds this usefull of needs any help, let me know.
Click to expand...
Click to collapse
Thanks. I know what to do next time if my G2 is messed up But I already bricked my phone last week and sent it back for repair, since I couldn't find any other to way fix it.
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!
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?