OK I'm not new to rooting or xda but I am new to this phone.
I'm not just jumping on here and asking either , I have been searching for the best root method and so far this looks like the best howto I can find.
http://wiki.cyanogenmod.com/wiki/HTC_Glacier:_Full_Update_Guide
I would just like to get a little info from a few people who have rooted this phone.
Also I've been reading about the bad emmc chip and that it may or may not have anything to do with the root method that is used , any thoughts on this would be great.
Any input would be great and or a link to a better guide to root this phone if there is one.
I just like to know as much as possible before I root.
TIA for any help or replies.
Edit: Forgot to mention I'm on 2.3.4 btw.
The guide you linked is the correct answer. Just be sure to follow the section on downgrading to 2.2.1, which is needed to permaroot.
If you're experienced with this stuff it takes about 15-20 minutes (if that) from start to finish.
It's a pretty painless experience.
The one catch you might run into is using ADB to push the update file to the phone. Sometimes it doesn't send the entire file, it leave off like 50 bytes for some oddball reason. So make sure to check the MD5SUMS and the exact file length. Or just avoid that part altogether by copying the file to your SD card in another way before starting the root process.
As for the eMMC chip, I'm convinced it's an overblown problem. If you have the 'bad' one it might break. It might not. I had the bad one and flashed it repeatedly and it never gave me a problem. Then I had the 'good' one and it borked the chip on my first attempt to flash. So while there's a higher probability of the 'bad' one breaking, it's not a guarantee nor is the good one immune. You can check it with a simple script in terminal emulator that's available somewhere in the forum but I forget where.
Skipjacks said:
The guide you linked is the correct answer. Just be sure to follow the section on downgrading to 2.2.1, which is needed to permaroot.
If you're experienced with this stuff it takes about 15-20 minutes (if that) from start to finish.
It's a pretty painless experience.
The one catch you might run into is using ADB to push the update file to the phone. Sometimes it doesn't send the entire file, it leave off like 50 bytes for some oddball reason. So make sure to check the MD5SUMS and the exact file length. Or just avoid that part altogether by copying the file to your SD card in another way before starting the root process.
As for the eMMC chip, I'm convinced it's an overblown problem. If you have the 'bad' one it might break. It might not. I had the bad one and flashed it repeatedly and it never gave me a problem. Then I had the 'good' one and it borked the chip on my first attempt to flash. So while there's a higher probability of the 'bad' one breaking, it's not a guarantee nor is the good one immune. You can check it with a simple script in terminal emulator that's available somewhere in the forum but I forget where.
Click to expand...
Click to collapse
OK so I can just put the update zip on the root of the sd card and just flash that from the bootloader from the phone?
Also is there another recovery for the my touch or is cwm the best one?
Edit: One more thing how often does this root method fail and if it does and the chip goes is the phone bricked ?
Yes, you can just put the file in the root directory of the SD card. That's all ADB does via the terminal on your computer as far as putting the file on your card. (It does a lot more in the overall process)
But no. You cannot just use the bootloader. You have to do steps 1-6 on the Wiki guide you linked first.
So basically....copy the PM15IMG.ZIP file to the root directory of the SD card.
Then do steps 1-6.
Skip step 7 because you've already done it.
Then do steps 8 and on.
And you don't have to do it this way. Sometimes ADB will push the entire PM15IMG file. But if you try to flash the update (downgrade) and it doesn't work, then try copying the PM15IMG in another way.
As for this root method failing, there are a couple ways to brick the phone.
If you pull the battery during the radio update....phone will be VERY bricked. Like won't even power to bootloader kind of bricked. So don't do that.
If the PM15IMG file just doesn't work for some reason, the phone will recognize that the file is bad and basically stop itself from updating. So it's pretty fool proof in terms of getting a corrupt file. Even if it goes through the update process and loads all the way but the phone still doesn't work (gets caught in a boot loop, sticks on the animation screen, has various other problems, etc) you're still good as long as you can get to the bootloader. You can always do a factory reset and start over. Or you can retry the update process and see if it works better the second time.
As for ClockworkMod, I love it. It gives you a lot of options in recovery to fix all or parts or things. It'll let you flash ROMs from the recovery screen so if you louse up a ROM install and can't get the phone to boot you can flash a new ROM from the recovery without having to go through the ADB console on your computer.
That's been helpful more than once. I tried to update a CM ROM. Something went wonky and the phone would just get stuck in the boot animation. So I restarted and went into recovery and reflashed my saved ROM backup and viola! Back to a working phone. That's handy because you can fix major ROM problems when you're away from home far away from your computer.
As fro the chip, if it breaks, the phone is dead. There is no fixing it. I have no idea what the actual odds are. But sometimes you've got to live a little and take your chances.
Enjoy! It's a great phone with a lot of great ROM options.
it's PD151IMG.zip
also, please read my guide here: http://forum.xda-developers.com/showthread.php?t=1388962
and also neidlinger's, posted in my thread.
Thanks guys I'm going to give it a go also I know all about recovery and flashing I just used Amon Ra recovery on my evo over cwm only cause cwm always gave me issues thats why I was wondering if there was something better.
I'll post back how it goes, I'm installing everything from scratch cause I lost my computer so I have to set up the sdk, adb and fastboot all over and now adb doesn't want to work LOL but it always works like that.
First you'll need to downgrade via this guide.
Then once you've done that you can either root via the root.sh method or the gfree method.
Good luck!
Follow macksters advice
Sent from my HTC Glacier using XDA App
Thanks for the ripples I still haven't got the chance to root yet but I did find out that I have the bad emmc chip, now I've never had a phone with one of these things in it and I'm wondering is this thing going to crap out on me?
I'm going to root it either way ad soon as I get the time.
Also I got my son the same phone and his has the bad chip as well what are the chances of that.
"bad" is just a name that people gave it. There might be roughly half of all existing MT4Gs with that chip.
Jack_R1 said:
"bad" is just a name that people gave it. There might be roughly half of all existing MT4Gs with that chip.
Click to expand...
Click to collapse
So its just more likely that those chips are the cause of people bricking their phones or just a couincidence?
Also I'm still not rooted yet and I'm having a few issues with the phone like apps fcing and the touch screen gets a little crazy at times like a ghost is messing with my phone, now is that just the stock ROM or can that be do to the "bad labeled" chip?
"Bad" chip has a bit higher failure rate, which means - statistically, if you take 100 people with "bad" chip and 100 with "good" chip, root their phones, and you'll get 1 total failure (probably less, but it's not number-accurate, just for demonstration) of "good" chip that will fail after rooting, and 2-3 failures of "bad" chip.
Again, chips that are really prone to failure ultimately WILL fail - rooted or not. Rooting just stress-tests them.
Jack_R1 said:
"Bad" chip has a bit higher failure rate, which means - statistically, if you take 100 people with "bad" chip and 100 with "good" chip, root their phones, and you'll get 1 total failure (probably less, but it's not number-accurate, just for demonstration) of "good" chip that will fail after rooting, and 2-3 failures of "bad" chip.
Again, chips that are really prone to failure ultimately WILL fail - rooted or not. Rooting just stress-tests them.
Click to expand...
Click to collapse
Not the process of rooting. It's the stuff you do AFTER rooting, flashing ROMs, themes, mods, radios etc that will speed up the process of the chip dying. This is because when you flash something, big chunks of data get written to the eMMC chip, and if you keep doing it constantly, there is a possibility that the chip will die. This is the reason behind the chips dying, not the actual rooting process, but the stuff that you do AFTER rooting it.
Sent from my HTC Glacier Sense 3.5 using xda premium
saranhai said:
Not the process of rooting. It's the stuff you do AFTER rooting, flashing ROMs, themes, mods, radios etc that will speed up the process of the chip dying. This is because when you flash something, big chunks of data get written to the eMMC chip, and if you keep doing it constantly, there is a possibility that the chip will die. This is the reason behind the chips dying, not the actual rooting process, but the stuff that you do AFTER rooting it.
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
From what I understand, it's the gfree exploit that stresses the eMMC and causes the fail.
But to the OP, what I've noticed is that people with the bad eMMC chip tends to fail rather shortly after they root. Many people that have had bad chips, including myself at one point, had it rooted and was flashing ROM's weekly for months with no issue. I think if it doesn't fail shortly after you root, you should be in the clear. But that's just my speculation.
mackster248 said:
From what I understand, it's the gfree exploit that stresses the eMMC and causes the fail.
Click to expand...
Click to collapse
It was pretty clearly defined, with help by the guy who wrote gfree, how gfee has nothing to do with it.
saranhai said:
Not the process of rooting. It's the stuff you do AFTER rooting, flashing ROMs, themes, mods, radios etc that will speed up the process of the chip dying. This is because when you flash something, big chunks of data get written to the eMMC chip, and if you keep doing it constantly, there is a possibility that the chip will die. This is the reason behind the chips dying, not the actual rooting process, but the stuff that you do AFTER rooting it.
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
Yes, this is correct, of course.
The rooting itself does only one potentially (arguably?) dangerous thing - it power-cycles the eMMC to intercept its initialization and prevent setting the read-only mode. eMMC seem to be sensitive to power-cycling while they're being accessed, some of the eMMC failures of both "good" and "bad" kinds were reported after pulling the battery on a working phone stuck in the middle of writing something. In any case there's nothing to do to avoid this power-cycling, though - any method of root has to include it.
This is sounding worse and worse lol.
I'm going to root no matter what but how does t-mobile insurance work I'm new to t-mobile but I'm paying for the insurance, or would it be possible to get a replacement through the warrant if this chip goes?
You call t mobile and tell them your new phone stopped working. Act like a dunce who doesnt know tghe difference vetween a phone and your butt and they will send you a new one.
Sent from my HTC Glacier using XDA App
Yeah I'm not usually a crook but they shouldn't really sell a phone with a faulty chip in it either.
This chip (the specific eMMC model) exists in at least 3 another phone models - Desire HD, Desire S, T-Mobile G2.
These chips fail in all of the phone models. There is one in my wife's Desire S (of course, rooted).
Their failure rate is VERY low. The problem is that on the forum you won't see the 99.99% of people that it works for them, you'll most probably see the 0.01% that has failures.
Related
First of all I just want to say WOW what an insightful and creative community you guys got going on around here. A lot of smart people on these boards. Thanks for the resources you guys provide to make having a cell phone into a hobby.
I have just successfully rooted my phone after hours of deduction and have flashed RC33 and a radio ending with 1.1. I've spent about 4 hours getting to this point and still feel behind the game. What motivated me to do this was the Official Hero Rom in the Android Development Thread and that is my ultimate goal insofar.
However, now that I've done this I don't want to take any unnecessary risks. I've used the dandy search feature and done hours of research as well as lurk on here since the launch of the G1 when I picked up the phone on launch day. I know about all of the informative links and they're great and I've reviewed them thoroughly but am still fuzzy on a few things.
I've read that there are different types of SPL's some brick and some don't. Please correct me if I'm wrong but my understanding of an SPL is that it is basically the update.zip file in my SD card. Currently that is a build of RC33 in my card along with recovery.img. For some reason I feel that this is not all as far as an SPL is concerned. If someone can concisely clarify this for me that would be great.
Also before I jump on Hero, what is a good cupcake ROM around here that is stable and not lacking many features that can easily be blinged out with one of the awesome themes you've got floating around here. I'm open to all enthusiastic suggestions. What tips do you guys have for me to move up to one of those?
I have not even begun to delve into App2SD or Nandroid but am getting a clearer image as to what they are and how they function. Any helpful tidbits on the two subjects would also be greatly appreciated, however they are not my main concern immediately.
Again thanks guys I've got work in about three hours now lol so I'm going to get some shut eye however I'll be back tomorrow. Soon, I hope to contribute to what you guys have got going on.
Unfortunately your hours of deduction did not lead you to this thread. Which has a link to this thread. Which has definitions, two I am posting here:
Bootloader – the SPL and IPL of a flash based device. See jashu’s description here.
SPL (Secondary Program Loader) - You get to the SPL by holding the camera button while powering on your phone. This is where you flash NBH images. See bootloader above.
Click to expand...
Click to collapse
Which links you to a greater explanation of what the SPL is.
Personally, I don't think the Hero builds compare with Cyanogen's Scary Experimental builds. I believe you sacrafice a lot of speed to gain very little (if any) functionality. Don't let the misnomer of "Scary Experimental" throw you off. His latest 3.5.3 blows everything else away. It's within a build or two of being declared stable. And most of the tiny little issues with 3.5.3 can usually be fixed with instructions being posted in that thread.
Moving over to Cyanogen's 3.5.3 is braindead simple too. Don't rush, follow the recommended upgrade path, and you'll be set. It does all the work for you, and it doesn't require the sometimes dreaded new SPL (which, BTW, is not nearly as risky as some will lead you to believe ... you just have to properly follow the required steps). Still, will this being your first attempt at any of this, you'll find it much less taxing on your nerves by sticking with a more straightforward upgrade. Cyanogen's is a great way to get your feet wet. And in the end, you'll end up with a blazing fast phone with all the bells and whistles too. Your phone will impress the moment it first boots. There are themes available now, and more will be coming once it hits stable. Apps2SD are automatically done for you if you have your sdcard formatted correctly. There are a myraid of ways to get the correct partitions on the sdcard, so do that before anything else. It will increase your chances of making this successful on the first attempt. Remember that a wipe is not necessarily a bad thing, it's usually that a failure to wipe is what caused your problem in the first place. Wipe if it's recommended. Read the comments to determine when it required, when it's just a recommendation, or when it's not necessary.
Be methodic. Since this is your 1st attempt at this, you'll be doing yourself a huge favor if you grab everything you need all at once. Don't try to take any shortcuts, follow the steps or instructions to the t. Make sure you have the latest radio installed (and the new SPL should you pick a build that requires it). Although they usually list the latest builds in the 1st post of a particular topic, occasionally they will release in intermediate fix within the thread itself. Check the last few 10 or so pages of comments for your build of choice to see what build is recommended at the time. Usually, you'll want to grab the latest build, but that's not always the case. Bleeding edge is not always best (althought with C's Scary Experimental, I've eagerly awaited each and every update because it's only gotten better each time).
Since you've done your research, go back and outline the entire upgrade path. Write it down for reference. Make sure your Windows driver are up-to-date, have the latest ADB installed on your computer (it makes things much easier if you use ADB if possible), don't do anything until you can devote a couple of uninterrupted hours to the upgrade process, and I cannot emphasize enough to WIPE as necessary. Hell, don't install any programs or fiddle with any settings. WIPE each step along the way until you get the final build installed. If something doesn't seem right any step along the way, don't proceed to the next step. WIPE again and re-flash. See if that fixes your problem. If it does, the proceed. If it doesn't, see if it's an issue that fixed with the next build you'll be flashing. If so, proceed. If not, look for another solution. Proceeding at that point _might_ be okay, just be aware that you might get yourself into a situation that requires re-rooting your phone.
Make sure that before you do anything else that you have one of the modified recovery images flashed to your phone. They're modified for a good reason.
If things go bad, don't panic and start posting that you've "bricked" your phone. Chances are you haven't. Very few phones get "bricked" to a point you can't fix it yourself. When people around here see the term "bricked" as a subject in a post's topic, it's a red flag that becomes a red herring for you. You may get into a boot loop or something, but it's usually fixable with a WIPE and an update.
Also, keep DREAIMG.img in the root of your sdcard at all times. Don't move it, don't delete it, don't rename it. It can, and will, save your ass if any of this hits the crapper. Carry it with you at all times. If you have DREAIMG in the root directory, you'll always be able to get your phone back to an operating condition, wherever you are, whenever you might need it, without the need for a computer. Yes, it would be starting all over again, but it would give your phone basic functionality if all goes to hell and you're not near a computer or don't have a USB cable or something.
None of this requires a PH.D. It's actually quiet simple. Most people that run into problems have simply missed or skipped a step, or failed to wipe as required. Knowing recovery proceeds in advance will be helpful, but even that is pretty straightforward and easy to follow. I've done all these flashings, re-flashings, recoveries, etc., so much that I --think-- I have the terminal commands etched in my memory. And I do. But I still refer to the on-screen steps to make 100% sure I'm typing things correct. I hit enter only after I'm confident I didn't type a 0 when it should be O (hehe). I look at the screens during the whole process for indications of success or failure. And I make sure that I am not distracted by anything when I upgrade. Lock yourself in a room by yourself after you've emptied your bladder. If you do get interrupted or have to take a bathroom break, write down the next step. Don't assume you'll remember. And don't even think of making or taking phone calls until you've finished this whole thing.
Read in advance.
Search as necessary.
Ask, in the appropriate forum and thread, when all else fails.
You'll do fine.
Good luck.
To start off with I have had my phone rooted since my g1 in 2009. I did not hesitate to root my mytouch earlier this month and it was successful. Unfortunately, my phone would no longer boot (not turn on at all) after a week of being rooted. I am not sure if rooting caused the error but now I am afraid to root my replacement. I wanted to at least flash my backup but I am afraid to even root for that. Also I should add that I root to flash roms not because I think it's "cool". Can anyone give me advice on if I should root again?
What did you flash right before the phone would not boot or turn on at all? Perhaps it is not the root but the roms that you are flashing. I certainly am not an expert but perhaps you might just try rooting and than wait a few days before trying to flash any roms. Also all that I have read states that you should read up on all the procedures and follow them to the letter. I have had that brought to my attention in a couple of instances. I just received my replacement (screen issues) and have rooted it again and so far things seem okay. I am going to wait and read and learn more before I flash a rom again. Good luck!!
tenbeau said:
What did you flash right before the phone would not boot or turn on at all? Perhaps it is not the root but the roms that you are flashing. I certainly am not an expert but perhaps you might just try rooting and than wait a few days before trying to flash any roms. Also all that I have read states that you should read up on all the procedures and follow them to the letter. I have had that brought to my attention in a couple of instances. I just received my replacement (screen issues) and have rooted it again and so far things seem okay. I am going to wait and read and learn more before I flash a rom again. Good luck!!
Click to expand...
Click to collapse
Yeah, I had flashed the hd port after using the z port and that's when the issues started. I think I will root again and just try to be more careful even though i am pretty sure I followed all instructions.m
Sounds like to me it was just timing between phone hardware and your flashing. Unless you are screwing around with with the ROMs prior to flashing without knowing what your doing you should have no issues. If it was ROM related you would see these boards all lit up with people having the same issues...and you simply dont see that.
Ok idk exactly what it is called but I know it has 777 in it. The file that is created on your SD card when you root using GFree. I saw someone had it posted on here somewhere a while ago but now I can no longer find it. Anyone have a link to that file? Please and Thank you! I think it may be my last chance at saving my myTouch with that stupid Cache error! The other way I fixed it last time isnt working this time
dcwiker05 said:
Ok idk exactly what it is called but I know it has 777 in it. The file that is created on your SD card when you root using GFree. I saw someone had it posted on here somewhere a while ago but now I can no longer find it. Anyone have a link to that file? Please and Thank you! I think it may be my last chance at saving my myTouch with that stupid Cache error! The other way I fixed it last time isnt working this time
Click to expand...
Click to collapse
part7backup-000000000.bin is created in root of your /mnt/sdcard/~ when you ran the gfree. If you lost it then sorry I don't think anyone ease's would work as I am not 100% sure if that is device specific but it may be leading to that.
Far as the cache error goes I hope it works out for ya as thats the closest soft-brick we have. But do you have adb installed? If so push and flash the CMWR2.5.1.2 manually. I didn't isolate the issue if it's gfree related as we still need data to verify those who are effected are only gfree users or folks who just simply did root.sh without gfree.
TmpUsr said:
part7backup-000000000.bin is created in root of your /mnt/sdcard/~ when you ran the gfree. If you lost it then sorry I don't think anyone ease's would work as I am not 100% sure if that is device specific but it may be leading to that.
Far as the cache error goes I hope it works out for ya as thats the closest soft-brick we have. But do you have adb installed? If so push and flash the CMWR2.5.1.2 manually. I didn't isolate the issue if it's gfree related as we still need data to verify those who are effected are only gfree users or folks who just simply did root.sh without gfree.
Click to expand...
Click to collapse
Yeah I know I had this stupid cache crap before and it was a b**ch to fix here is the link to my thread
http://forum.xda-developers.com/showthread.php?t=1043459
And I have ADB and EBL (Hboot 85.2007) and last time pushing the old CWM worked but this time no dice I get Write FAILED everytime. So I hear that the PMG15.IMG can possibly fix this issue as well but I need that part7 file and I dont have mine anymore thanks to CM7 killing my SD card a while back anyhow I have seen it posted for DL here before and I think it worked for the guy who used it, I mean its worth a shot. It's not like I can do ANYMORE damage to the phone! lol
dcwiker05 said:
Yeah I know I had this stupid cache crap before and it was a b**ch to fix here is the link to my thread
http://forum.xda-developers.com/showthread.php?t=1043459
And I have ADB and EBL (Hboot 85.2007) and last time pushing the old CWM worked but this time no dice I get Write FAILED everytime. So I hear that the PMG15.IMG can possibly fix this issue as well but I need that part7 file and I dont have mine anymore thanks to CM7 killing my SD card a while back anyhow I have seen it posted for DL here before and I think it worked for the guy who used it, I mean its worth a shot. It's not like I can do ANYMORE damage to the phone! lol
Click to expand...
Click to collapse
BTW it was me who posted the CMWR2.5.1.2 flash leak on another forum as I was here on XDA manually hacking the SLC-EUDA emmc block trying to replicate the issue the first person in MT4G to have in here. But if all you get now is fail partition update (fail-pu) then there is nothing else you can do. I still need more data to isolate if this is just gfree user based and not those who has s-off with eng boot without gfree. I try to do more test today but I can't roll the gfree maybe I am lucky? but ill post my finding if I ever able to get it and replicate the conditions. Only known meth to fix this is replacing the motherboard for now.
So you're saying PMC15.IMG wont fix this either? I don't understand why last time I was able to ADB push CWM 2.5.1.2 via Fastboot and then go into Recovery, Format cache and it was fine phone booted. I reflashed CWM 3.1.2.4 and went about my business...now it happens again and I can not flash CWM via recovery this time and thus I'm boned?? FML I JUST got this phone...my last ones screen peeled away, it was a referb from insurance so it was replaced with this one.
I work for T-Mobile so I really don't wanna bork my phone enough to hide root then send it in for a warrenty replacement cuz I don't think its right to screw my own company but damn I don't want to be out a phone, my back up phone's menu button doesn't work so it's really freaking annoying , guess I will deal till the Sensation 4g!
i dont rememeber which unroot thread but one of them has it, and supposedly it works with any mytouch 4g. not just the one it was created on
Well once you have fail-pu on hboot when you try to revert back to PD15IMG (rom/radio) both update will fail as you can't write to the partition block. Now far as I know this is only seen in CMWR3.0.0.0+ which at the time I flashed it manually though terminal. At this point there is way to many variables to consider mostly we need community input as those who is effected did use gfree as it could mean why the emmc simply gets -ro access now I am aware its using slc-euda so you can't low level format it this is the reason they replace the motherboard. We are not just talking about single partition here as it seems the recovery partition is first thing to be effected. I need to do some more work and atm I only have 1 phone and I don't feel like hacking it and end up with dead as I don't have any backup phones as I gave it away. Let me see if I can get another MT4G cheaper from ebay/cl and I can test on it.
VibrantOwnr said:
i dont rememeber which unroot thread but one of them has it, and supposedly it works with any mytouch 4g. not just the one it was created on
Click to expand...
Click to collapse
Thats the gfree revert meth which is the only place you use part7backup and then if you want to roll back to stock eng bootloader you do the unroot.sh which flash the eng.nb0 and turns S-OFF.
Alright so let me get this all played out in my terms so I can see if I understand it.
1. Do I actually need that part file? I rooted with gfree so I figure yes
2. Will PMG15.IMG work at all or no?
3. Should I just say F it all and try anyhow? If so anyone wanna throw me a link to the part file?
4. I STILL don't get why this happened the first time! And why the way I fixed it the 1st time isn't doing $hit the 2nd time...
UGH! Damn it why couldn't this happen the end of May closer to when the Sensation 4G is suppose to launch... :'( damn you CWM ghost...
i had ruu file with 2.3.3 and my phone in 2.2 when i try to flash it after 2 min the process rich 14% and(hboot updating) stay on it for 45 min .when i see nothing happend in such time i disconnect my phone and try too recover it but not sucsses .
i try to flash with other ruu files and get same result
Sounds like you might have the bad emmc chip.
Some info on the issue here
-Nipqer
Just a guess:
Wasn't there also an issue with flashing a official ruu (don't know wether this is the case here) when you're rooted and have s-off.
I believe I remember something along the ways of, that somewhere during the flashing process, s-on would be restored and your basically end up being stuck in between?
thomas_wlc said:
Just a guess:
Wasn't there also an issue with flashing a official ruu (don't know wether this is the case here) when you're rooted and have s-off.
I believe I remember something along the ways of, that somewhere during the flashing process, s-on would be restored and your basically end up being stuck in between?
Click to expand...
Click to collapse
this is the point hang my flash process and i am waiting for 1hour
did you finda fix to this problem i am haveing the same problem...
666
got phone to boot buy useing fastboot oem boot command than tryed installing rom mannager from market and flashed recovery but when i try to boot into recovery i get same screen and got to do the same command to get it to boot but still no recovery to load a new rom but i got adb and su access...going to do some searching on how to flash cwm with adb see if that helps...
666
there is really not too much to worry about, if you private message me, I can give you Josh's information here on XDA - he can unbrick pretty much any G2/Desire-Z for $40 and has done 100's of them - he has like almost 500 Thanks on here -
the only thing he can't fix is a fried emmc chip, but thankfully those are relatively rare!
(and if the emmc chip is fried, then HTC will fix it, because that truly is their fault, so no worries!)
(HTC knows of the emmc chip failures, and that is why in this case they are not going to give you a hassle about the warranty, sort of like when an auto company has done a silent recall, so to speak)
WTF? said:
there is really not too much to worry about, if you private message me, I can give you Josh's information here on XDA - he can unbrick pretty much any G2/Desire-Z for $40 and has done 100's of them - he has like almost 500 Thanks on here -
the only thing he can't fix is a fried emmc chip, but thankfully those are relatively rare!
(and if the emmc chip is fried, then HTC will fix it, because that truly is their fault, so no worries!)
(HTC knows of the emmc chip failures, and that is why in this case they are not going to give you a hassle about the warranty, sort of like when an auto company has done a silent recall, so to speak)
Click to expand...
Click to collapse
i like to learn to fix stuff myself I was evan looking at makeing a jtag for it ( made them for routors and sat recevers before) so sending it out to get fixed is not what i am looking for and seeing as if i use fastboot oem boot it starts up and works fine adb and all it should not be hard to fix with the info here
666
States lound and clear rooted phones should not flash official ruu's here on the site.
Sent from my HTC Vision using xda premium
Spastic909 said:
States lound and clear rooted phones should not flash official ruu's here on the site.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
read that after but seeing as i can use fastboot oem boot command from adb folder abd phone boots up fine and works and adb works when booted up i figure it should be easy to fix this problem...i think if i had the adb commands and loactions i should beable to send my cwm backup from my working DZ to the stuck one and reboot and all should be great but i dont know enough about adb and these phones to know how to do it...hopeing for some help...
ps devil 1234 did u try the fastboot oem boot command to get yours to boot???
tia
666
Phone sounds bricked, had similar issue until today with my old phone, got jtag adapter, used it and unbricked the phone
I'm getting into rooting and flashing and what not and I'm very stumped right now. I've read around but found nothing that directly pertains to my problems.
I'm reading this guide http://forum.xda-developers.com/showthread.php?t=1281085 and following it step by step but I'm already stuck.
So far all I have accomplished so far is getting adb to work. I followed TrueBlue Drew's guide and have successfully completed that. Next I wanted to check my eMMc chip to make sure I have a good chip, but I can't. When I try to reboot into recovery mode, I get sent to a red triangle and exclamation mark screen.
I looked into this and apparently it means that I have a stock recovery image. So I download Rom Manager to try to change that, but I get an "error occurred while attempting to run privileged commands." I'm not sure what I am to do now. Apparently to get rid of that error I need to root my phone first? But that would supercede the order of the guide which I am trying to ensure I have a good eMMC chip.
I am just so lost and over my head I think.
What am I doing wrong?
I think there's a way to check your chip using terminal emulator from the market.
I have the bad one but rooted my HTC Panache anyway
Sent from my HTC Panache / Darkside CM7.2 using xda premium.
choowielo said:
I'm getting into rooting and flashing and what not and I'm very stumped right now. I've read around but found nothing that directly pertains to my problems.
I'm reading this guide http://forum.xda-developers.com/showthread.php?t=1281085 and following it step by step but I'm already stuck.
So far all I have accomplished so far is getting adb to work. I followed TrueBlue Drew's guide and have successfully completed that. Next I wanted to check my eMMc chip to make sure I have a good chip, but I can't. When I try to reboot into recovery mode, I get sent to a red triangle and exclamation mark screen.
I looked into this and apparently it means that I have a stock recovery image. So I download Rom Manager to try to change that, but I get an "error occurred while attempting to run privileged commands." I'm not sure what I am to do now. Apparently to get rid of that error I need to root my phone first? But that would supercede the order of the guide which I am trying to ensure I have a good eMMC chip.
I am just so lost and over my head I think.
What am I doing wrong?
Click to expand...
Click to collapse
There is a way to check without root.
http://forum.xda-developers.com/showthread.php?t=1360915
However, I wouldn't worry about it. There has been no hard evidence that its the type of chip that is the issue. Its pretty circumstancial.
Sent from my HTC Mytouch 4G using XDA App
estallings15 said:
There is a way to check without root.
http://forum.xda-developers.com/showthread.php?t=1360915
However, I wouldn't worry about it. There has been no hard evidence that its the type of chip that is the issue. Its pretty circumstancial.
Sent from my HTC Mytouch 4G using XDA App
Click to expand...
Click to collapse
I wouldn't worry about it either. But like i said, one is problematic, and one is less problematic. Either one could last for ever, either one could last 30 seconds. The main reason why i posted that is for the rooting process.
But that link has been updated in my guide. Thanks.
As stated above, I've had 4 Mytouch's for various reasons all with the "bad" eMMC and only had one fail on me. Still, be cautious
Nicgraner said:
As stated above, I've had 4 Mytouch's for various reasons all with the "bad" eMMC and only had one fail on me. Still, be cautious
Click to expand...
Click to collapse
I agree, i also have a phone with the bad Emmc chip and my phone is still going strong. I personally used gfree to root my phone so i suggest you try that. Are you using fr3vo to downgrade?