Related
So I got my Z yesterday. thought i root it today, the easy way with the terminal so downloaded:
wpthis-Z.ko and
hboot_7230_0.84.2000_100908.nb0
I Had over 50% battery and full root access. Everything was going great until I try reboot the phone and it would not start up again. Now it's completely dead no lights when I charge, no buttons work. Dead.
Oh no !
Which guide were you following to do it ? Do you think you might have type the wrong destination partition when you did the "dd" to copy the hboot across ?
This One http://forum.xda-developers.com/showthread.php?t=835777it is very strange . i dont understand
So how far did you get ? Did all the rooting go ok ? And then it only went wrong after you dd'd the new hboot and then rebooted the phone ?
steviewevie said:
So how far did you get ? Did all the rooting go ok ? And then it only went wrong after you dd'd the new hboot and then rebooted the phone ?
Click to expand...
Click to collapse
Rooting whent ok but after the dd and try to reboot . dead.
I can only guess that either the hboot image was corrupted, or you somehow typed the "dd" command wrong, so that something else was overwritten.
Either way, it doesn't sound good, but I hope someone else can come up with some sort of miracle for you.
I presume leaving it on charge doesn't help ? Just in case the battery has died too much (and the 50% charge it said wasn't really accurate).
steviewevie said:
I can only guess that either the hboot image was corrupted, or you somehow typed the "dd" command wrong, so that something else was overwritten.
Either way, it doesn't sound good, but I hope someone else can come up with some sort of miracle for you.
I presume leaving it on charge doesn't help ? Just in case the battery has died too much (and the 50% charge it said wasn't really accurate).
Click to expand...
Click to collapse
I have rooted some phones in the past. but nothing like this has happened to me before.
most likely corrupt img I tink.
but its very strange that it comply dead !
stian230 said:
I have rooted some phones in the past. but nothing like this has happened to me before.
most likely corrupt img I tink.
but its very strange that it comply dead !
Click to expand...
Click to collapse
Do you still have a copy of the hboot that you downloaded ? Because you could compare the MD5 checksum on that to see if it was corrupted.
steviewevie said:
Do you still have a copy of the hboot that you downloaded ? Because you could compare the MD5 checksum on that to see if it was corrupted.
Click to expand...
Click to collapse
right I have on my pc, thanks steviewevie. hm back to the old N1. crappy ****
I think its send to htc time, just say you was flashing a ruu and it turned off and went dead plead ignorance always
JD
Sent from my HTC Desire Z Beast
JupiterDroid said:
I think its send to htc time, just say you was flashing a ruu and it turned off and went dead plead ignorance always
JD
Sent from my HTC Desire Z Beast
Click to expand...
Click to collapse
Yes I gess you right JD. waiting for Monday to come .
Is it possible that the hboot-file doesn't work with the nordic DZ's?
I probably have the same batch of the norwegian model like Stian, and got perm-root without any problems using the same guide.
S-OFF on the other hand didn't work.. It made my phone enter a infinite boot loop, so it didn't get any further than the "Quietly brilliant"-screen... Luckily, the phone wasn't bricked, so I could enter bootloader and reset to factory..
For the record; i checked the MD5 checksums, and used adb shell on my computer so that I could copy/paste the "dd"-command hence preventing any typo's...
Duppsko said:
Is it possible that the hboot-file doesn't work with the nordic DZ's?
I probably have the same batch of the norwegian model like Stian, and got perm-root without any problems using the same guide.
S-OFF on the other hand didn't work.. It made my phone enter a infinite boot loop, so it didn't get any further than the "Quietly brilliant"-screen... Luckily, the phone wasn't bricked, so I could enter bootloader and reset to factory..
For the record; i checked the MD5 checksums, and used adb shell on my computer so that I could copy/paste the "dd"-command hence preventing any typo's...
Click to expand...
Click to collapse
I'm very keen on finding an answer to this. I'm getting my Finnish version and would like to get it rooted etc but if the hboot does no work we will be out of luck? Unless someone finds a new one somewhere?
AnyDone said:
I'm very keen on finding an answer to this. I'm getting my Finnish version and would like to get it rooted etc but if the hboot does no work we will be out of luck? Unless someone finds a new one somewhere?
Click to expand...
Click to collapse
I'm sure VISIONary r14 has perm root without flashing a new hboot.
Sure about that? Seems I missed it completely that it can be done without flashing hboot? Doesn't hboot mount it r-o again after restart?
Duppsko said:
Is it possible that the hboot-file doesn't work with the nordic DZ's?
I probably have the same batch of the norwegian model like Stian, and got perm-root without any problems using the same guide.
S-OFF on the other hand didn't work.. It made my phone enter a infinite boot loop, so it didn't get any further than the "Quietly brilliant"-screen... Luckily, the phone wasn't bricked, so I could enter bootloader and reset to factory..
For the record; i checked the MD5 checksums, and used adb shell on my computer so that I could copy/paste the "dd"-command hence preventing any typo's...
Click to expand...
Click to collapse
I don't have the nordic edition , I order my from expansys.
AnyDone said:
Sure about that? Seems I missed it completely that it can be done without flashing hboot? Doesn't hboot mount it r-o again after restart?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=846223
r12 [test version]
Temproot is now the default
Added option to try to Permroot (test on Desire HD, Desire Z and G2)
After permroot, required kernel module is placed in /data/local for your convenience
Added option to unroot
Note: this does NOT rewrite your hboot - you will need to do this manually to get S-OFF.
Click to expand...
Click to collapse
It is now r14 - but perm root was incorporated in r12.
MD5 checksums:
2ce1bdd5e4c1119ccfcecb938710d742
2CE1BDD5E4C1119CCFCECB938710D742 so the file was not corrupt. does anyone have new theories ??? going to call htc to tomorrow
Just call me Mr.Brick or "the Bricker boy"
Can you get into fastboot?
If not then you probably wont be able to do a thing. Except JTAG.
Have you tried a power cycle by any chance? Take out battery, hold power button for 10 seconds with NO battery installed. Sometimes it works miracles.
I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Call ahead of time and see what they say on the phone?
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)
I don't know what the policy is.... most likely, as soon as they see where you're at, the tech will figure out that you were trying to root your phone, and you'll be SOL.
Have you tried booting your phone via ADB? Maybe you can go into recovery via adb shell and see if you can go from there....
if you can get it to power up all is not lost, try pushing AMON's recovery via fastboot
Fastboot
Copy recovery-RA-evo-v1.8.0.img in your android-sdk-windows\tools\ folder
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)
Since your phone turns on and you can boot into fastboot. Bricked would mean nothing happens period. There's still hope. Try this thread: http://forum.xda-developers.com/showthread.php?t=780141. There's a video walk-through showing you how to unroot and return to s-on. Then you may be able to start over.
Good Luck!
-kp
Edit: Try GMan's suggestion above 1st.
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
indagroove said:
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
Click to expand...
Click to collapse
Sprint Insurance right? I don't... I might do that but that's my last resort.
josh4trunks said:
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Click to expand...
Click to collapse
If you can boot into the hboot just run a ruu and restore the factory Rom, if all fail pm me your number and I will walk you thru it
Sent from my PC36100 using XDA App
shameless bump - completely changed opening post
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week.
What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.)
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
haplo1818 said:
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week. What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
Click to expand...
Click to collapse
Tried this multiple time with different PC36IMG.zip, always get Failed-PU
Partition Update Error, I might try the 3.30 version though just to make sure.
Won't like my opinion but, you knew the risks of rooting. If you can't fix your phone then you should add the insurance and suck up the deductible fee. You don't deserve (or anyone for that matter) a free replacement for ****ing up your phone. It sucks but that's the risk. They'll normally have you one the next day.
Your phone is definitely not bricked and is fixable. Do you have adb drivers installed on your PC? If not find them and install them then try this: http://forum.xda-developers.com/showthread.php?t=829045?
Since you are already s-off you won't have to do all the steps, but by reading the entire OP you could figure out where to start and what to do. Just to be on the safe side you may want to start at the beginning using HBOOT USB from this screen you posted ftp://eto.homeip.net/shared/IMAG0004.jpg and start completely over. you are not bricked. Just hang in there and someone here will get you hooked up. You are in the right place my friend.
Evo's are really not that easy to fully brick.
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Have you tried using a different SD card? Is it possible that something is corrupt with it? I also hear that you need to have at least 1GB of free space on the card when your trying to flash it.....
Let me just say myself and this guy stayed up late last night working on this phone trying every possible root/unroot method you can think of.
The pc he is using has adb drivers installed but the computer wont recognize his device as a adb device. Fastboot on renders certain commands and we tried all with various recoveries. I hit up a dev and we went thru different things and cant seem to figure this one out
As I told the Josh it can not be bricked because we get the bootloader and fastboot screen, I think its not even the partition but the recovery. Also he has a modified hboot by someone on xda (josh please post the link) which I believe that pc36img is whats causing all the problems.
If anyone could help it would be appreciated!!
Jbcarrera said:
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Click to expand...
Click to collapse
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
I'm sure he thought you needed the engineering SPL to be able to flash roms. When I rooted mine back in June with toast's method, that was the way to do it. I rooted my girl's new Evo last month using Unrevoked, and I also downgraded the hboot because I thought I had to in order to flash a custom rom. Fortunately, I was able to do so with no issues.
Cleared all the caches?
craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
The partition table is screwed but there has to be a way to reset it I knew that method was risky told my friends to stay away from it
Sent from my EVO at the edge of hell
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...
Hi everyone,
I am in a big problem it seems. This is what happened: My phone was working fine with CM7 and latest version of CW Mod but suddenly everything started force closing. So what I did was to factory reset the phone from recovery wiping cache and davlik cache. After doing factory reset it stopped at splash screen itself and not booting up. Does factory reset removes rooting for mt4g?
After that, I tried to install ADB and root again but adb devices doesnt show my device when I am in recovery. But when I go to fastboot it, fastboot devices cmd shows my device.
I then tried to go back to stock by applying PD15IMG and it successfully applies it but now it gets stuck at "my"splash screen. What should I do now?
Thanks in advance.
Uh oh... Sounds like bad eMMc chip which no, can't be fixed. I'd see if you can check your eMMc but if not I believe your screwed and will have to send back to tmo.
Sent from my HTC Glacier using XDA Premium App
Do you get any cache errors in recovery when wiping?
Did you upgrade your radio to a version other than stock before attempting to restore to factory using PD15IMG?
It's starting to sound like a bad eMMC at this point though. Those things are starting to fail left and right!
I will check eMMC and post it here. But yes, while wiping cache I get error E: cant open /cache/ or something like that so i assumed that it might be because i got unrooted and I wanted to root again (but i cant adb). When applying ROM, it exits saying Status 1. No, I didn't upgrade radio images.
Fc followed by bootloop followed by cache errors...definitely eMMc
Sent from my HTC Glacier using XDA Premium App
Because of applying PD15 image I got original h-boot version (not engineering h-boot) so couldn't check eMMC. But I have radio version which is 26.03.02.26_M
If I assume that eMMC is gone then, Is there any other option of doing ANYTHING except sending it to TMobile as I am using it outside US.
sagarparmar said:
Because of applying PD15 image I got original h-boot version (not engineering h-boot) so couldn't check eMMC. But I have radio version which is 26.03.02.26_M
If I assume that eMMC is gone then, Is there any other option of doing ANYTHING except sending it to TMobile as I am using it outside US.
Click to expand...
Click to collapse
Bootloader version has nothing to do with being able to check eMMC version.
http://forum.xda-developers.com/showthread.php?t=1081243
Somewhere in there there's instructions for checking without root if you've lost it already.
Thanks for the link but I can't adb. fastboot shows my device but adb doesn't. I don't know if there is any problem with my drivers. because when i plug the phone in is shows ADB Interface in Device manager. Still I will check them again will try to put eMMC version ASAP.
sagarparmar said:
Thanks for the link but I can't adb. fastboot shows my device but adb doesn't. I don't know if there is any problem with my drivers. because when i plug the phone in is shows ADB Interface in Device manager. Still I will check them again will try to put eMMC version ASAP.
Click to expand...
Click to collapse
Someone posted some instructions a while back that allowed you to check your eMMC version using terminal commands, so you could do it without root or ADB, but for the life of me I can't find them! I thought they were in the main eMMC serial thread, but maybe not. I'll keep looking.
TeeJay3800 said:
Someone posted some instructions a while back that allowed you to check your eMMC version using terminal commands, so you could do it without root or ADB, but for the life of me I can't find them! I thought they were in the main eMMC serial thread, but maybe not. I'll keep looking.
Click to expand...
Click to collapse
This is the terminal cmd it seems:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
But right now, my phone is not even booting up. how would I go to terminal emulator?
sagarparmar said:
This is the terminal cmd it seems:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
But right now, my phone is not even booting up. how would I go to terminal emulator?
Click to expand...
Click to collapse
I'm suffering from brain fade today. I forgot about the fact that your phone wasn't booting. If memory serves, there is a terminal option in CWM recovery. If your recovery is still usable, try selecting the terminal feature and enter those commands there. Honestly though, this would only serve to confirm what we already know. Your eMMC has failed, so there's isn't much hope. The good news is most people have had no trouble doing a warranty exchange, even when sending in a rooted phone. Good luck!
As I tried to flash PD15IMG it is now into stock recovery. Need to flash CWM using fastboot but dont know whether it would work or not because last time I tried (before applying PD15) it failed saying Status 1. Need to check that.
But you know what the bigger problem is, I bought it from Swappa.com and I don't even know whether I can exchange it or not. I will have to send it to my friend who is in the US as I am outside.
Do they give warranty card or something when you buy (I dont know as I am not the original buyer ) ??
TeeJay3800 said:
I'm suffering from brain fade today. I forgot about the fact that your phone wasn't booting. If memory serves, there is a terminal option in CWM recovery. If your recovery is still usable, try selecting the terminal feature and enter those commands there. Honestly though, this would only serve to confirm what we already know. Your eMMC has failed, so there's isn't much hope. The good news is most people have had no trouble doing a warranty exchange, even when sending in a rooted phone. Good luck!
Click to expand...
Click to collapse
There's a terminal in cwm...? Since when?
Sent from my HTC Glacier using XDA Premium App
Nope, bought mine from eBay and htd fixed it when mine quit. Just called for a rma, advised it was bootloopimg then went blank, shipped it and got another or it back fixed. Call it won't hurt.
sagarparmar said:
As I tried to flash PD15IMG it is now into stock recovery. Need to flash CWM using fastboot but dont know whether it would work or not because last time I tried (before applying PD15) it failed saying Status 1. Need to check that.
But you know what the bigger problem is, I bought it from Swappa.com and I don't even know whether I can exchange it or not. I will have to send it to my friend who is in the US as I am outside.
Do they give warranty card or something when you buy (I dont know as I am not the original buyer ) ??
Click to expand...
Click to collapse
knothead said:
Nope, bought mine from eBay and htd fixed it when mine quit. Just called for a rma, advised it was bootloopimg then went blank, shipped it and got another or it back fixed. Call it won't hurt.
Click to expand...
Click to collapse
Hey I'm in the situation where my phone won't even turn on now... I called HTC already and they're actually mailing in a battery thinking that it's the reason the phone won't charge or turn on...
What were the steps you went through to get the to take it in? Did you end up getting a new one or the one you sent in for repairs? You paid for shipping or any repair fees? Any input would be useful... let me know!
Thanks!
Nicgraner said:
There's a terminal in cwm...? Since when?
Click to expand...
Click to collapse
It doesn't. As I said in that post, I wasn't sure. It turns out I was thinking of Amon-RA's recovery which does have a terminal option.
TeeJay3800 said:
It doesn't. As I said in that post, I wasn't sure. It turns out I was thinking of Amon-RA's recovery which does have a terminal option.
Click to expand...
Click to collapse
CWM does have adb shell though.
Sent from my HTC Glacier using Tapatalk
knothead said:
Nope, bought mine from eBay and htd fixed it when mine quit. Just called for a rma, advised it was bootloopimg then went blank, shipped it and got another or it back fixed. Call it won't hurt.
Click to expand...
Click to collapse
Yeah, It would be great if you tell the procedure. You directly called HTC guys or TMobile? What else do you need to ship along with the phone?
Flashing CWM??
Guys,
As I described my phone is in a boot loop but I can see it in fastboot but when i go to recovery it jst goes to bad state and have to remove battery. Is there a way to flash CWM recovery and opening adb shell as I might want to see what is eMMC and need to try this out http://forum.xda-developers.com/showpost.php?p=15299273&postcount=66 and http://forum.xda-developers.com/showthread.php?t=1039504&page=2
I know we can flash recovery from fastboot but when i tried that it gave me an error saying you remote not allowed (android sdk on Win 7).
You weren't in fastboot mode, but in hboot mode.
Choose "fastboot" to be able to flash.
Hey guys, a few days ago I finally decided to root my phone and flash cynagen mod 7...
However yesterday evening my touch screen suddenly stopped working, so I can't unlock my phone...
its still showing screen but its not responding when I press anything...
Things ive tried: removing battery for 20 sec, removing battery to turn off the phone and start it up again.
Is it possible to fix this?
or does anyone have the stock Vodafone firmware so I can try flashing it and return it for warranty?
Try reflashing the Rom from recovery again maybe that will help, I think I saw a thread on here about a fix for that problem a few months ago but not sure as I never needed it so didn't read it.
Sent from my HTC Wildfire using XDA Premium App
Scratch0805 said:
Try reflashing the Rom from recovery again maybe that will help, I think I saw a thread on here about a fix for that problem a few months ago but not sure as I never needed it so didn't read it.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
You mean re flashing the stock Vodafone rom?
Any place where I can find it?
Btw even clockworldmod doesn't seem to respond to my buttons(the ones below the screen)
Only the physical buttons work...
Sorry I meant try reflashing your cm7 Rom again from recovery, use the volume buttons and the trackball to navigate in clockwork.
Sent from my HTC Wildfire using XDA Premium App
Scratch0805 said:
Sorry I meant try reflashing your cm7 Rom again from recovery, use the volume buttons and the trackball to navigate in clockwork.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
ill give it a shot, by the way when I tried to flash with RUU it didn't detect my phone.
Also when I boot up my phone with charge cable it stops responding and only the red charging light will burn(even when the battery is full, because it did this for hours a few days ago)
Also in clockwork when I go to advanced and key test it doesn't do anything when I press a key, It doesn't show anything in the log.
So I think its really broken.
Update: reflashed with cyanogen didn't fix it
And when I try to flash with WUU it says my phone is not connected
ofc I can't access my usb settings on the phone...
The charging bug comes with clockwork, when the phone is off if you plug in the charger it happens so I always make sure to hit the power button first wait till the splash screen has gone and then plug it in, its annoying but just pop the battery out and then reboot the phone. There's a fix for that too but it didn't work for me.
As for the other problems I'm not sure as I've never come across them on my phone before, I would definitely try reflashing first before using an ruu. If that doesn't help hang fire till someone a bit smarter than me sees this.
Sent from my HTC Wildfire using XDA Premium App
Scratch0805 said:
The charging bug comes with clockwork, when the phone is off if you plug in the charger it happens so I always make sure to hit the power button first wait till the splash screen has gone and then plug it in, its annoying but just pop the battery out and then reboot the phone. There's a fix for that too but it didn't work for me.
As for the other problems I'm not sure as I've never come across them on my phone before, I would definitely try reflashing first before using an ruu. If that doesn't help hang fire till someone a bit smarter than me sees this.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
I just tried re flashing and that didn't help, I think my screen is really broken.
Including those home, menu back and search button.
only the power and the volume buttons and track ball work...
Update: sometimes my screen seems to work for a few seconds and then it doesn't again...
Depends on how I hold my phone...
gijs007 said:
I just tried re flashing and that didn't help, I think my screen is really broken.
Including those home, menu back and search button.
only the power and the volume buttons and track ball work...
Update: sometimes my screen seems to work for a few seconds and then it doesn't again...
Depends on how I hold my phone...
Click to expand...
Click to collapse
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin
ErwinP said:
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin
Click to expand...
Click to collapse
I would give it a try, but im not out of warranty, its just voided until I re flash a stock Vodafone firmware.
So if anyone could give me one id be really happy.
Preferably a Dutch/nl one with hboot 1.02
There's links to some ruu's in here, hope you find what your looking for.
http://forum.xda-developers.com/showthread.php?t=1029318
ErwinP said:
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin
Click to expand...
Click to collapse
I've changed the touchscreen on mine and can confirm the softkeys are attached to it, there's 2 separate cables though I think the one from the softkeys is only for the led's as mine broke, the buttons work fine but I have no lights behind them.
Sent from my HTC Wildfire using XDA Premium App
gijs007 said:
I would give it a try, but im not out of warranty, its just voided until I re flash a stock Vodafone firmware.
So if anyone could give me one id be really happy.
Preferably a Dutch/nl one with hboot 1.02
Click to expand...
Click to collapse
As you are looking for a ROM with hboot 1.02, I assume that before rooting you had the same hboot? Because then you must have gained root using AlphaRevX/Revolutionary, which installs a custom bootloader. This hboot can, to my knowleadge, not be downgraded to the original one. In other words: you have voided your waranty and there is no way to cover it up...
Erwin
ErwinP said:
As you are looking for a ROM with hboot 1.02, I assume that before rooting you had the same hboot? Because then you must have gained root using AlphaRevX/Revolutionary, which installs a custom bootloader. This hboot can, to my knowleadge, not be downgraded to the original one. In other words: you have voided your waranty and there is no way to cover it up...
Erwin
Click to expand...
Click to collapse
Damn, will they figure this out or is their a change they are just like oh yeah the screen is broken lets fix it?
As its clearly a hardware issue and not a software issue...
Other whys ill just fix it my self or go to a phone store...
update: I tried flashing SUU but it keeps giving me a message that my phone is not connected...
But the phone store told me rooting does not void my warranty as its a hardware issue and not a software issue.. they told me they could send it for me to a special company that repairs phones and is qualified by mayor factories like HTC,Samsung,etc.
But they also told me it would be easier to just contact Vodafone for repairs as that is free and if not I could always come back.
I'd send it back to Vodafone, best case they'll switch the touchscreen power it up for a quick test then send it back, worst case is they may check your software versions... then send it back unrepaired.
I used to fix iphones and ipads for an insurance company and hardly ever had enough time for checking software, just fix it, send it out and crack on with the next one!
Sent from my HTC Wildfire using XDA Premium App
dont panic your phone is all right
It also happened in my case.Go to the following link
http://shipped-roms.com/index.php?category=android&model=Buzz
and flash a suitable ruu rom .it will definitely fix ur phone.or u can just boot into recovery by pressing volume and power button simultaneously during the boot and flash cm 7 rom.
rashmifantasy said:
dont panic your phone is all right
It also happened in my case.Go to the following link
http://shipped-roms.com/index.php?category=android&model=Buzz
and flash a suitable ruu rom .it will definitely fix ur phone.or u can just boot into recovery by pressing volume and power button simultaneously during the boot and flash cm 7 rom.
Click to expand...
Click to collapse
I already re flashed cm7, and at first it didn't help then suddenly it did help and now its doing nothing all over again...
Update: re flashed again and still nothing.
AFAIK reflashing a custom rom from a custom recovery should not solve the issue.
But reflashing a stock ROM (= RUU) should solve that. Also reflashing a stock ota update will solve that. Ota update needs to be flashed from stock recovery. Do either of these things depending on what your hboot version is (if hboot is latest then ota will be option for most times) Also remember PC49IMG method if you presently have custom recovery.
P.S : what all I said is thinking that it is software issue. this shouldn't help if it is related to hardware.
Sent from my Blade using XDA App
I was wondering if there was a way to flash using that method, as I said I never needed to flash an ruu yet so don't know much about em. Just saw your other post explaining how to use PC49IMG to flash an ruu. Thought i'd copy it here as it may help.
bharatgaddameedi said:
If it still had the issue, then install the RUU by pc49img method. Download the correct ruu for your phone. Donot connect phone to PC. On windows PC click on start and type %temp% and enter. This opens the user temporary folder of your PC. Now run the ruu. Now if you observe the temp folder, there will be extra folders created which have folder name enclosed in {} brackets. Search in these folders for the file ROM.zip. Copy the ROM.zip to a safe location. Now format your memory card to fat32 (must) and put the ROM.zip to the root of memory card. You should use memory card reader. Then rename the ROM.zip to PC49IMG.ZIP . Then insert memory card in phone and reboot to hboot menu from where you can update/reflash the partitions. If still not working, clear storage again from hboot menu.
Sent from my Blade using XDA App
Click to expand...
Click to collapse
if ur stock screen is showing a date of 1980(after flashing a custom rom)
Just flash the RUU_Buzz_Froyo_hTC_Asia_WWE_2.24.707.1_Radio_13.55.55.24H_3.35.20.10_release_161113_signed.exe
it will help
Scratch0805 said:
I was wondering if there was a way to flash using that method, as I said I never needed to flash an ruu yet so don't know much about em. Just saw your other post explaining how to use PC49IMG to flash an ruu. Thought i'd copy it here as it may help.
Click to expand...
Click to collapse
Did that and now its on stock Vodafone firmware
But the touch screen still isn't working.
Oh well now I can send it back to Vodafone for repairs.
Thanks for the help
Btw: is their anyway to get the original hboot back?
For maybe some more like me that want to go back to what it use to be with the hboot S-OFF, S-ON issue.
I had my phone S-OFF with alpharevx beta. Used CM7 -stable for couple days but decided i wanted to go back to all original. I first RUU my phone with the RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed.exe file. Boot it up, made sured it runs, then did what is instructed below here;
To be able to do this you need HTC USB drivers installed. Install the HTC pakage, reboot, uninstall the HTC-
Sync software, keep the drivers! reboot PC again.
Power off your phone. Plug in your USB cable to phone. Press volume down and powerup your phone. After it
settle navigate down and choose fastboot option.
1. Unpack these files to your c:\fastboot
2. Open up your windows command promt (WinVista/7 users rightclick choose run as Administrator)
3. in command promt type CD\ then press enter
4. then your should be in C:\
5. type cd fastboot
6. then you should now be in dir C:\fastboot
7. Im bored to death typing, look below. Beware of each command ends with enter. After success, reboot.
C:\fastboot>fastboot oem mb 9C068490 1 30
... OKAY
C:\fastboot>fastboot flash hboot hboot_buzz_7225_1.01.0001.nb0
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... OKAY
Files needed (Windows version): megaupload.com/?d=UO9L74I9
Works perfectly for me.
* NOTE: Im not responsible for your phone if you brick/kill it. These steps worked for me!