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 a problem guys. while i was trying to restore a nandroid backup of cyanogenmod via clockworkmod recovery after trying out Fusion, i noticed that the rom would not go past the mytouch white screen... I wiped data and cache prior to doing so to have no issues but it wouldnt boot. So i boot up in recovery to find this....
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
As far as i know, i never messed with such directory so im puzzled
Can anyone tell me how to get up and running? Because no matter what i try to flash, it seems like something goes wrong since it wont go past the white screen
thnx
Lots of threads about this in the Q&A section. A few have been able to come back from it. This has been happening so much that I almost don't want to flash anything...
EDIT: http://forum.xda-developers.com/showthread.php?t=1071881
Hope that helps and please keep us updated.
lowandbehold said:
Lots of threads about this in the Q&A section. A few have been able to come back from it. This has been happening so much that I almost don't want to flash anything...
Click to expand...
Click to collapse
I flash ROMs frequently. Not to i say i'm immune to it. But i think alot of it might be tracking back from trying to use the "flash option" in the application.
And it must be something the end user is doing. You've never seen a developer have these problems. And if they did i'm sure they'd post their fix.
just my 2 cents
mike21pr said:
I have a problem guys. while i was trying to restore a nandroid backup of cyanogenmod via clockworkmod recovery after trying out Fusion, i noticed that the rom would not go past the mytouch white screen... I wiped data and cache prior to doing so to have no issues but it wouldnt boot. So i boot up in recovery to find this....
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
As far as i know, i never messed with such directory so im puzzled
Can anyone tell me how to get up and running? Because no matter what i try to flash, it seems like something goes wrong since it wont go past the white screen
thnx
Click to expand...
Click to collapse
Were u using recovery 3.0.2.4,3.0.0.6 or 3.0.0.5? Did u try formatting system via recovery before flashin the bckup?
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
I agree that it probably has to do with user error as well...I would just feel much better about it if we could figure out what causes it. I haven't followed the threads closely, but with the engineering bootloader is there a known fix?
neidlinger said:
I flash ROMs frequently. Not to i say i'm immune to it. But i think alot of it might be tracking back from trying to use the "flash option" in the application.
And it must be something the end user is doing. You've never seen a developer have these problems. And if they did i'm sure they'd post their fix.
just my 2 cents
Click to expand...
Click to collapse
I belive that also cause it happened to me while tryin to flash cm7 via the app & never recovered,learned frm my mistake tho lol
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
lowandbehold said:
I agree that it probably has to do with user error as well...I would just feel much better about it if we could figure out what causes it. I haven't followed the threads closely, but with the engineering bootloader is there a known fix?
Click to expand...
Click to collapse
Its a yes & no...people have recovered & others havent,so theres really not a way to tell what causes this & why some phones recover & others dnt
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
i had 3.0.2.4 version.
im gonna check out the link to see if i can fix it. thanx guys.
ill keep u posted
something is not right.... im flashing the zip and get this in the progress...
Parsing... [SD ZIP]
[1] BOOTLOADER -FAIL-PU
[2] BOOT -FAIL-PU
[3] RECOVERY -FAIL-PU
[4] SYSTEM -FAIL-PU
[5] USERDATA -FAIL-PU
[6] SPLASH -FAIL-PU
[7] TP
[8] TP -BYPASSED
[9] RADIO_v2 -UPDATING
[10] RADIO_CUST
its not done yet, but wanted to know if its normal to have the fail results, because its beginning to worry me
Do you have the engineering bootloader?
lowandbehold said:
Do you have the engineering bootloader?
Click to expand...
Click to collapse
i dont think so. I has root s-off using gfree methid
mike21pr said:
i dont think so. I has root s-off using gfree methid
Click to expand...
Click to collapse
boot into hBoot and see if you have the .85 screen or the .86 screen.
neidlinger said:
boot into hBoot and see if you have the .85 screen or the .86 screen.
Click to expand...
Click to collapse
.86
10 char
no bueno...
lowandbehold said:
no bueno...
Click to expand...
Click to collapse
so, this means im boned?
mike21pr said:
so, this means im boned?
Click to expand...
Click to collapse
I wouldn't say "boned". it just means the [solved] problems using the Engineering screen will not help since you do not have it.
Have you tried running the PD15IMG to restore back to 100% stock?
neidlinger said:
I wouldn't say "boned". it just means the [solved] problems using the Engineering screen will not help since you do not have it.
Have you tried running the PD15IMG to restore back to 100% stock?
Click to expand...
Click to collapse
yes. and it gives me the FAIL-PU after most steps
God dame, like someone else said, I'm getting scared flashing my phone too now. FAIL-PU, a lot of people have been getting those, and it seems to be the ones with the GFree method without the eng hboot. I remember another member saying that it's done and you have to get a warranty exchange as the motherboard needs to be replaced.
Don't quote me on anything I said above but that's what I think.
xdviper said:
God dame, like someone else said, I'm getting scared flashing my phone too now. FAIL-PU, a lot of people have been getting those, and it seems to be the ones with the GFree method without the eng hboot. I remember another member saying that it's done and you have to get a warranty exchange as the motherboard needs to be replaced.
Don't quote me on anything I said above but that's what I think.
Click to expand...
Click to collapse
Yea i saw that too... oh well, ill sell it as-is cheap to get me another phone or get a replacement. i guess i have made my peace with it lol. thanks for the help guys
keep me posted if anyone finds anything out
No, don't just give up yet. Did you try connecting it to your computer and wiping the whole phone via ADB? Try that, but I really don't know if it'll work with the stock bootloader or not and then try flashing PD151 image again.
I understand that there are similar threads out there but I still can't seem to figure it out. I apologize ahead of time for any wrong terminology, I'm pretty new to all of this. To give a background on what happend, I started my day off by rooting my phone with the following link (I had tried a different method with visionary plus and terminal but it wouldn't work)
http://forum.xda-developers.com/showthread.php?t=858996
this method worked just fine and gave me s=off, currently what I have is as followed:
Glacier PVT ENG S-OFF
HBOOT-0.85.2007 (pd1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
After gaining my root I was excited to try and flash a new rom. I installed the clockwork rom manager from the market, flashed the recovery then backed up my current in case of future problems.
Next step for me was to flash a new rom. for this I followed
http://forum.xda-developers.com/showthread.php?t=1070444
everything seemed to be going fine, phone restarted and I sat waiting (since I read the first boot could take 10min or so) after at least an hour I began to worry. Nothing happened, just stayed on the mytouch 4g startup screen and never changed.
I rebooted into recovery to try again, I can get into my hboot and into clockwork Mod Recovery v3.0.2.4 just fine. but there are a whole bunch of errors I cant fix. When clockwork starts I get the errors
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
If I try to format anything (cache, system...) it will say
Formatting /cache... (or system depending on what I am trying)
Error formatting /cache! (or system)
If I try to restore to a previous time it will start to do the restore, it will first do the boot which goes fine, but when it tries to format the system during the restore it fails just like if trying to format it individually.
At this point I would just like to get my phone working, any help would be much appreciated. (please try and use details so I can follow... still trying to learn alot)
I hate to be the bring of bad news, and remember don't kill the messenger, but it sounds as if your phone is truly bricked. There have been several threads on this already. As i know you are aware of. And very few, if any, have recovered.
There is a thread Posted here that boils down to the fact if the VISIONary.apk & root.sh method do not work then you have a bad eMMC.
Since it appears your phone does have a bad eMMC, hope you have insurance on it.
neidlinger said:
hope you have insurance on it.
Click to expand...
Click to collapse
neidlinger- i happen to have bought the insurance for 6 bucks a month or whatever it was - they said it extends the mfr warranty another year and then it gives you drop-in-toilet etc insurance with around a 120$ deduc.
I'm with t-mobile and got the phone thru the mail. If I take this back to a local TMO store for warranty claim, there's no difference is there? (i.e. you dont have to follow the mail route just because that's how you got it originally)
also- would these cache mount or failed -pu errors, essentially beyond repair - are we getting these to be recognized as hardware failure (i.e. no deductabel and counted as a mfr defect) or are these coming up as TMO insisting on counting them as some user fault, requiring the deductable to be paid??
acsi007 said:
neidlinger- i happen to have bought the insurance for 6 bucks a month or whatever it was - they said it extends the mfr warranty another year and then it gives you drop-in-toilet etc insurance with around a 120$ deduc.
I'm with t-mobile and got the phone thru the mail. If I take this back to a local TMO store for warranty claim, there's no difference is there? (i.e. you dont have to follow the mail route just because that's how you got it originally)
Click to expand...
Click to collapse
9/10 times if you buy a phone through the mail you will have to exchange it through the mail they will not allow you to walk into a store and do the exchange. I ran into that with my blackberry 9700.
acsi007 said:
also- would these cache mount or failed -pu errors, essentially beyond repair - are we getting these to be recognized as hardware failure (i.e. no deductabel and counted as a mfr defect) or are these coming up as TMO insisting on counting them as some user fault, requiring the deductable to be paid??
Click to expand...
Click to collapse
nope there is not way around it. once the eMMC fails it's down for the count.
neidlinger said:
I hate to be the bring of bad news, and remember don't kill the messenger, but it sounds as if your phone is truly bricked. There have been several threads on this already. As i know you are aware of. And very few, if any, have recovered.
There is a thread Posted here that boils down to the fact if the VISIONary.apk & root.sh method do not work then you have a bad eMMC.
Since it appears your phone does have a bad eMMC, hope you have insurance on it.
Click to expand...
Click to collapse
Is there any way to tell if the eMMC is bad. the visionary install went fine, just using the terminal to do the sh root.sh command wouldnt work, it would just keep saying failed (function not implemented) which is why I switched to visionary and adb gfree method... which worked like a charm, not a single hickup with it. the problems didnt start coming until after the rom instillation didnt work
hiddentalnt said:
Is there any way to tell if the eMMC is bad. the visionary install went fine, just using the terminal to do the sh root.sh command wouldnt work, it would just keep saying failed (function not implemented) which is why I switched to visionary and adb gfree method... which worked like a charm, not a single hickup with it. the problems didnt start coming until after the rom instillation didnt work
Click to expand...
Click to collapse
i see you didn't read the thread i posted.
The link i posted is to a thread here @ XDA, called "Post your eMMC serial number". It has alot of information regarding this very subject, including how to tell if your eMMC is indeed a faulty one [ by serial number ].
it really doesn't matter when the problem happens. it just matters that it happened.
./gfree is basically forcing the rooting process to happen while the root.sh is asking for it to happen. If the root.sh process doesn't allow you to proceed, then you may have a faulty eMMC. you forced the phone to root and opened up a bee hive in the process.
yeah sorry, I posted and then was just reading that forum as you replied... sorry about that.
hiddentalnt said:
yeah sorry, I posted and then was just reading that forum as you replied... sorry about that.
Click to expand...
Click to collapse
no need to tell me your sorry, . If you want to make me mad tell me Popeye's Chicken is out of business. we all start out somewhere. Just be willing to read prior to doing anything or asking anything. Chances are there is an answer somewhere. Sometimes we like what we read and sometimes we don't either way it's out there.
Hiddentalnt, please post your eMMC serial. We need people who have recovery errors to post what serial they have so we can actually pinpoint the problem being the chip. Thanks. The instructions are posted in the thread neidlinger posted above. Thanks
xdviper said:
Hiddentalnt, please post your eMMC serial. We need people who have recovery errors to post what serial they have so we can actually pinpoint the problem being the chip. Thanks. The instructions are posted in the thread neidlinger posted above. Thanks
Click to expand...
Click to collapse
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
hiddentalnt said:
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
Click to expand...
Click to collapse
after you got ADB installed and you punch in adb devices does it give you a serial number?
hiddentalnt said:
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
Click to expand...
Click to collapse
nevermind... just got it M4G2DE
so from what Im reading...theres no coming back from this, the chip is dead?
hiddentalnt said:
nevermind... just got it M4G2DE
so from what Im reading...theres no coming back from this, the chip is dead?
Click to expand...
Click to collapse
pretty much.
I do know one guy was able to via flashing an older recovery image via the hBoot, but you have to have the .85 engineering screen. Which you do not have.
neidlinger said:
pretty much.
I do know one guy was able to via flashing an older recovery image via the hBoot, but you have to have the .85 engineering screen. Which you do not have.
Click to expand...
Click to collapse
what is the .85 engineering screen, i do have hboot - 0.85.2007 but im assuing thats different.
So its time to call up TMO and have them send me out a new phone? do I need to unroot first so they dont find it?
hiddentalnt said:
what is the .85 engineering screen, i do have hboot - 0.85.2007 but im assuing thats different.
So its time to call up TMO and have them send me out a new phone? do I need to unroot first so they dont find it?
Click to expand...
Click to collapse
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
neidlinger said:
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
Click to expand...
Click to collapse
sorry for asking so many questions. but you really have been a great help. do you have any idea where i can find the 2.5.x.x recovery image, I've been trying to look but I cant find it, just didn't know if you already knew of a forum that had it.
hiddentalnt said:
sorry for asking so many questions. but you really have been a great help. do you have any idea where i can find the 2.5.x.x recovery image, I've been trying to look but I cant find it, just didn't know if you already knew of a forum that had it.
Click to expand...
Click to collapse
I've got it store on my Lunix computer at home. I do not have it on my phone or on my work computer.
sorry. I can post it later on tonight.
neidlinger said:
I've got it store on my Lunix computer at home. I do not have it on my phone or on my work computer.
sorry. I can post it later on tonight.
Click to expand...
Click to collapse
Thanks, I appreciate it. I'm off to class anyways so I have to put a pause on trying to fix it till then.
neidlinger said:
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
Click to expand...
Click to collapse
I would be that ONE case where this option did work. And the difference I have seen between the first time when flashing CWM worked and the second time (when it DIDN'T work) is the COMMAND error. If your CWM says anything about COMMAND error then flashing the old CWM isn't gonna work.
Here is a link to a post I made with a download for the old CWM
http://forum.xda-developers.com/showthread.php?p=14069400#post14069400
have any questions PM me if needed. Hit the Thanks button to if any of us have helped you at all.
Good luck man, I have a 450 dollar batter charger right now, so you'll need it :/
dcwiker05 said:
I would be that ONE case where this option did work. And the difference I have seen between the first time when flashing CWM worked and the second time (when it DIDN'T work) is the COMMAND error. If your CWM says anything about COMMAND error then flashing the old CWM isn't gonna work.
Here is a link to a post I made with a download for the old CWM
http://forum.xda-developers.com/showthread.php?p=14069400#post14069400
have any questions PM me if needed. Hit the Thanks button to if any of us have helped you at all.
Good luck man, I have a 450 dollar batter charger right now, so you'll need it :/
Click to expand...
Click to collapse
I'm not sure I fully understand your directions in the other thread. So when i download the zip, i get inside it and go all the way to recoveries to get out one of the disc image files. which one do I want, there is a 2.5.1.3 and 2.5.1.4 and a 3.0.0.5 but I'm assuming thats not it... but once I get one of those I rename it recovery.img then i use abd to push it... what is the command to push it? and i have to be in hboot then fastboot to push it?
hey guys... so i have a MT4G rooted n s-off
i rooted using the gfree method.. and after about two months started getting recovery cache errors. i dont have the eng hboot (stupid me! D
i just called t mobile n theyre sending me a replacement.. but the problem is, i got a custom splash screen install.. so when they turn the phone on itll show it (the screen says "rooted HTC glacier"...)
so im wondering if theres a way to make it so that the splash screen doesnt show AT ALL.. like show a blank white screen or something when u turn it on.
is that possible?
thx
remember.. i cant rly flash anything.. (cwm cache recovery errors ugh!)
and also...basically, i want to delete the splash screen
completely.
Run the pd15 zip through hboot. That will get rid of the custom splash and put the stock one back.
coupetastic-droid said:
Run the pd15 zip through hboot. That will get rid of the custom splash and put the stock one back.
Click to expand...
Click to collapse
possible.
If you load the PD15IMG on the device and it says anything about a "failed-PU" then you are stuck. with the splash image you currently have.
You can try going to /system/bin and deleting bootanimation
Xi2wiked said:
You can try going to /system/bin and deleting bootanimation
Click to expand...
Click to collapse
the boot Animation is different than the splash image. The splash image the the first image you see when the phone boots. That you cannot delete by removing the bootanimation.
LOL you people are way to funny... His problem escalated from can't mount recovery corruption to failed partition update. So PD15IMG.zip (stock rom/radio) is useless. I need to take some time and do extended research just on this and not get distracted. Maybe if I can get my hand on another 3rd MT4G I can compare both and see what happens. For now he is stuck only thing he can do is fry the mobo as suggest in his other thread so POS won't turn on period.
PermROOT said:
LOL you people are way to funny... His problem escalated from can't mount recovery corruption to failed partition update. So PD15IMG.zip (stock rom/radio) is useless. I need to take some time and do extended research just on this and not get distracted. Maybe if I can get my hand on another 3rd MT4G I can compare both and see what happens. For now he is stuck only thing he can do is fry the mobo as suggest in his other thread so POS won't turn on period.
Click to expand...
Click to collapse
yes THANK U for being the only one who read my post carefully.
hmmm... is there anyway to delete the bootloader? (splash screen is in there somewhere i think)
orr can i unlock the bootloader somehow?
I had a similar problem. so I ended up just frying my phone completely by connecting it to my car batter at the battery terminals! not the safest thing ever but it worked like a charm. if the board is fried they aren't going to investigate too much.
markmq said:
I had a similar problem. so I ended up just frying my phone completely by connecting it to my car batter at the battery terminals! not the safest thing ever but it worked like a charm. if the board is fried they aren't going to investigate too much.
Click to expand...
Click to collapse
lol yes... but then wudnt u have to pay 70 or so dollars for "hardware broken fee"?
thats wat t mobile said if they found any hardware broken
saranhai said:
lol yes... but then wudnt u have to pay 70 or so dollars for "hardware broken fee"?
thats wat t mobile said if they found any hardware broken
Click to expand...
Click to collapse
That's not true. If you're within the 1 year manufacture warranty, you do not pay a dime for a replacement. If you're over the 1 year warranty and you have insurance, then you pay a deductable of 150 I believe.
coupetastic-droid said:
That's not true. If you're within the 1 year manufacture warranty, you do not pay a dime for a replacement. If you're over the 1 year warranty and you have insurance, then you pay a deductable of 150 I believe.
Click to expand...
Click to collapse
uhh i got mine during the february free smartphone sale this year...
I need some help with this one.
I received a Mytouch 4g and have the following errors:
It will not boot past the Mytouch 4g logo screen. However; I can boot into Hboot and recovery just fine.
It is running CWM 3.0.2.4 which is supposed to be a 2.3 recovery. Whenever entering recovery or moving around and trying to flash something it says the following:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
The radio is 26.03.02.26_M which is supposed to be a 2.2 radio.
I have tried to flash the 2.3 radios but they all seem to freeze up at the very end. I have let them sit for 15+ minutes.
I have tried to flash a 2.3 rom and receive an error when flashing it. Also, I cannot format system under recovery, I receive an error saying: Error formatting /system! (Helpful I know)
I have also tried factory resets to no avail. I am currently going to try to get back down to a 2.2 recovery and go from there.
Please help as it is greatly needed and appreciated!
Mickyyy said:
I need some help with this one.
I received a Mytouch 4g and have the following errors:
It will not boot past the Mytouch 4g logo screen. However; I can boot into Hboot and recovery just fine.
It is running CWM 3.0.2.4 which is supposed to be a 2.3 recovery. Whenever entering recovery or moving around and trying to flash something it says the following:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
The radio is 26.03.02.26_M which is supposed to be a 2.2 radio.
I have tried to flash the 2.3 radios but they all seem to freeze up at the very end. I have let them sit for 15+ minutes.
I have tried to flash a 2.3 rom and receive an error when flashing it. Also, I cannot format system under recovery, I receive an error saying: Error formatting /system! (Helpful I know)
I have also tried factory resets to no avail. I am currently going to try to get back down to a 2.2 recovery and go from there.
Please help as it is greatly needed and appreciated!
Click to expand...
Click to collapse
all those cache errors definitely mean you have a bricked phone, with a bad emmc chip likely being the problem. currently, there isnt a way to recover from this brick
aznprodgy said:
all those cache errors definitely mean you have a bricked phone, with a bad emmc chip likely being the problem. currently, there isnt a way to recover from this brick
Click to expand...
Click to collapse
Ouch. Is there absolutely no possibility of anything? I'd be content with a stock rom at this point... If it's already bricked I could be a test dummy for anything risky that might work.
Mickyyy said:
Ouch. Is there absolutely no possibility of anything? I'd be content with a stock rom at this point... If it's already bricked I could be a test dummy for anything risky that might work.
Click to expand...
Click to collapse
not that I know of, I havent heard of anyone recovering their bricked phone with the bad emmc
Answered my own question. Any other ideas feel free to post away :/
HEY guys i saw the title and thought it should be appropriate to post here, sorry if i deviate from the original question but I recently flashed 2 Mytouch 4Gs and everything worked out great i used the instructions provided by grankin01 for true perm root using gfree method through adb with visionary for perm root unlock etc etc but i didnt flash the engineering bootloader as far as i know not really sure I flashed cm7 on both devices now one of the phones has given me trouble the other is still working.
The issue is that the defective phone worked for about 2 weeks, the owner said she accidentally let the phone use all battery and die, and after that the phone would get stuck at the cm7 boot animation. I rebooted into recovery just fine and reflashed the rom. That got it working for several minutes. Then it started crashing randomly and kept freexing at boot animation, i tried a cm7 kernal and that didnt work either so i flashed virtious unity sense 3.0 rom. That seemed to work but it was freezing when i tried to install certain games well long story shorter i finally ran fix permissions for apps from rom manager and that seemed to fix problem, the phone stabilized and actually worked flawlessly after so i gave it back.
The phone worked for about another week, owner tells me that she was trying to install games (8 at a time ) and the phone was not working, so she tried reboot and the phone wouldn't reboot at all in fact it dosent even go into recovery light up or show any signs of life except when i plug it in to my computer asks for this driver QHSUSB_DLOAD so i guess its not completely dead but adb does not recognize it with adb devices command but i am totally stuck dont know what to do please help and sorry for the huuuge post!
Read the Glacier Wiki, Troubleshooting guide. Link in my signature.
It'll answer the OP.
It would be wise to look for it before posting.
For the second answer - if the phone doesn't start booting, there's nothing you can do.
Yup +1 on the brick with the bad emmc chip, classic symptoms...
I sent this...
Yup guess so. I've been trying to at a minimum get the stock recovery back on but that seems impossible at this point. Can't flash from adb or even wipe/flash from fastboot.
Argh
Okay so apparently it is going back to HTC for repair.
My problem is that now I cannot seem to get CWM off of it or anything. I tried flashing the PD15IMG to stock but receive the fail-pu. I tried with ADB but had an error. Fastboot gave me an error as well.
Are there any recommendations? I would just send it like it is since it wasn't the rooting or flashing but a manufacture defect on the emmc it seems, but I am afraid they would reject and charge me to repair. Even if I declined, there would be a $35 fee for their hassle.
I would like to have it out the door tomorrow morning if possible, so please instruct me on any possibilities. I thank you all in advance.
There's nothing you can do besides trying to brick it completely - loading PD15IMG and pulling the battery while radio update is in progress.
or fry the thing and make it unbootable lol
aznprodgy said:
or fry the thing and make it unbootable lol
Click to expand...
Click to collapse
How would go about doing that? I can't seem to make it fully bricked by pulling while flashing a radio :/
aznprodgy said:
I had a spare charging USB cable so I just cut the end off of it. CAREFULLY took the phone apart and touched the hot wire to the motherboard, but only for a short amount of time. I wouldnt really recommend this, as you could electrocute yourself if not done properly or you could cause damage to the phone possibly making it unreturnable. but hey, times get hard sometimes...**not responsible for any damage done to you or your phone, should be done at YOUR OWN risk**
Click to expand...
Click to collapse
from another thread-----^^