Database Users

Have to admit I need some help with rooting

Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.

This means you are on the leaked version now and there is nothing that can be done as of right now.

K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?

ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.

sounds like you got a bad pb001.img file.

ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?

nevermind addressed my issue

As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5

ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.

af man...seriously!

out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"

HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA

ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!

Rooting New Evo

How do I root this thing I've tried just about every tutorial I've seen they all fail either because of permission errors or update failed in the stock bootloader menu.
This is a brand new Evo that just came back into stock today.
Hardware 003
Software: 1.47.651.1
Build: 1.47.651.1
Baseband: 2.05.00.06.10
I just got this replacement due to my old phone being defective but no root methods seem to work correctly. Any ideas?

Just did it last night with my replacement.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=706411
Download your favorite ROM to your SD card.
Then follow this guide under recovery instructions: http://forum.xda-developers.com/showthread.php?t=690762
When you load it up, flash your rom you downloaded on your SD card.
Enjoy!

UrbanMuppet said:
Just did it last night with my replacement.
Follow this guide: link removed since I can't post them.
Download your favorite ROM to your SD card.
When you load it up, flash your rom you downloaded on your SD card.
Enjoy!
Click to expand...
Click to collapse
Tried that multiple times, it was the first method I used it copies the PC36IMG file then when it goes to check it it gives me a "Main version is older Update failed!" error, if I try to manually copy and do it by hand like I'm used to I get the same problem.

I don't get it.... Redownload it again, maybe corrupt/old? Make sure your version matches?
Download Simple Root, run the .exe and make sure your phone is in USB Debugging. It does it all for you. Once it's done you have a half-ass rooted stock rom. At that point power down and boot into recovery and run recovery-windows.bat and it loads a temp recovery. Use that to install whatever rom (Wipe first) and then use rom manger to install clockwork and enjoy.

UrbanMuppet said:
I don't get it.... Redownload it again, maybe corrupt/old? Make sure your version matches?
Download Simple Root, run the .exe and make sure your phone is in USB Debugging. It does it all for you. Once it's done you have a half-ass rooted stock rom. At that point power down and boot into recovery and run recovery-windows.bat and it loads a temp recovery. Use that to install whatever rom (Wipe first) and then use rom manger to install clockwork and enjoy.
Click to expand...
Click to collapse
You can't get past part one in simple root again when it copies the zip file from the simple root folder in adb (this is done automatically) and it attempts to scan the file in the stock bootloader I end up with a "Main version is older, Update Fail" error message, you cannot get past that at this point my only options are to either reboot or shutdown. Again it does not install the zip file like it's suppose to,I've rooted my old Evo countless times without the need for this simple root GUI stuff I'm perfectly capable of root in adb but again both give me the same error.

My guess is that you're trying to use the same PC3IMG in both parts and that's why you're getting the "Main version is older" error. You have to use the engineering PC3IMG in the second part, not the PC3IMG used in the first part (of toast's tutorial). You have to remove that one and rename the engineering version to PC3IMG and then run that.
Basically, read the tutorial and follow it exactly.

ultron said:
My guess is that you're trying to use the same PC3IMG in both parts and that's why you're getting the "Main version is older" error. You have to use the engineering PC3IMG in the second part, not the PC3IMG used in the first part (of toast's tutorial). You have to remove that one and rename the engineering version to PC3IMG and then run that.
Basically, read the tutorial and follow it exactly.
Click to expand...
Click to collapse
Nope wrong, I never got to part two since I never got part one to finish how could I use it twice if I couldn't even use it once? I knew exactly what was wrong the problem is I didn't know how to fix it. At least until I found this gem:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7410421
The fix is in the link above in case anyone has the same problem, note that this only really happens with the newer batches of Evos that have been patched to 1.47 by Sprint and you'll have to trick the phone into downgrading from 1.47 back to 1.32 and then back to 1.47 rooted again.

[Q] Recovery can not open updates

I will preface by saying that I am new to the modding scene. Been learning all I can to get the most out of my glacier. Have it rooted with s=off, running CWR 3.0.0.5 with orange text and coming from stock. When I get into recovery and follow all the steps, it gives me E:can't open /sdcard/update-cm-7.0.0-rc2-glacier-signed.zip (bad). Just need a little guidance after searching the forum and not finding anything along these lines. Thanks!

balquin said:
I will preface by saying that I am new to the modding scene. Been learning all I can to get the most out of my glacier. Have it rooted with s=off, running CWR 3.0.0.5 with orange text and coming from stock. When I get into recovery and follow all the steps, it gives me E:can't open /sdcard/update-cm-7.0.0-rc2-glacier-signed.zip (bad). Just need a little guidance after searching the forum and not finding anything along these lines. Thanks!
Click to expand...
Click to collapse
When you download a ROM you should see a MD5sum. Make sure to check the MD5Sum of the download to make sure you got a valid download. A hardwired connection is preferable, or a STRONG wi-fi connection. But always check that.

I downloaded all the files onto my pc then moved them over to the phone. I will try downloading them right on the phone as I have never had to check md5's before. I was trying to also load from CWR but it will not connect to lists. Also when trying to go thru CWR it will not go to recovery after making all the selections, so maybe the file is corrupt. Thanks for the quick response!

balquin said:
I downloaded all the files onto my pc then moved them over to the phone. I will try downloading them right on the phone as I have never had to check md5's before. I was trying to also load from CWR but it will not connect to lists. Also when trying to go thru CWR it will not go to recovery after making all the selections, so maybe the file is corrupt. Thanks for the quick response!
Click to expand...
Click to collapse
Checking the MD5Sum should be done whenever you see the those. It only takes a few seconds.
This is the method i use

Well, I must be doing something wrong because things seem to check out OK, but I just can't seem to flash a new ROM. I may have to post a new question for my new issue. I try to flash and tell it to clear everything before the flash, but it only resets everything to stock and I have to reload all my programs again. Done this thru CWM and recovery. I could have swore I rooted it correctly, as all my settings seem to be where they need to be to flash a new ROM.
S-off
hboot-85.2007
running the latest version of CWM - with orange text
I will start searching thru some other posts with different questions...

Just finished checking the md5's as well...all good. So I must be missing something as when I go to flash via recovery, it states that it is bad and aborts install.
*updates:
md5's are good on the pc, check md5's on sdcard and they do not match. Now need to get a good one on the sdcard...
Been DL'ing files to phone, still can't get a matching md5. Trying to DL from the mirror.
Finally! Got a md5 match... here goes the flash attempt!

Well I have a good file on the sdcard root, but when trying to install from recovery it aborts stating that it is bad. Any suggestions? Thought I was doing everything correctly, but this is a tad frustrating.
*Thought I would double check the md5 and what do you know, it didn't match yet again. What would cause the md5 to keep changing?

[Q] current rooting/2.3 instructions

As the thread title states, I'm looking for info on the steps to root my stock MT4g, and install the new ROM that's floating around. I'm pretty technically capable, but the info I've found looks slightly dated. When I was active in the iPhone jailbreak scene, using old directions could brick a phone pretty easy, or prevent future jailbreaking. I haven't kept up with this scene enough to be able to know what's dated and what isn't.
This is my current plan, please correct it if I'm missing anything or have it wrong.
(based on wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide)
I've got ADB going
I need a backup solution for app data right? What's my best option here?
Once backed up, I plan to install busybox, Superuser package & Temporary Root package via ADB
Use gfree to make that root permanent
Install ClockworkMod recovery
Reboot into recovery, and install faux123's ROM
Does that sound correct, and did I skip anything? Any input at all is welcome, I'd like to stand tall on the backs of giants.

There are two popular methods floating around
You can either use the Root.sh method [ Found Here ]
Or the ./gfree method [ Found here ]
Either method will work perfectly. I've used both and can say with confidence they work.
The Cyanogen method can be goofy at times. I've see alot of people say they cannot get it working for them. I'd rock one of the two above. You shouldn't have a problem either way.

Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?

lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
For backing up apps and data, use titanium backup. for backing up your whole phone, use the backup feature in clockworkmod recovery after you've flashed it via rom manager after permarooting.

lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
The best way to back up your Data and Applications is like mentioned above is Titanium Backup. The free version will work well but i recommend the paid one.
as far as a snap shot of the entire ROM incase you want to go back to it. reboot into recovery > backup/restore > backup. And it will do the rest.

Well I made it halfway there, but didn't nail the whole thing. I've got permanent root access (yay) now, and was able to make backups via Titanium. I then rebooted the phone into "recovery" using the ROM Manager from Clockwork. First boot had a red exclamation mark, I unplugged the handset from the USB and tried a second time. After that, I was greeted with the Orange and black interface, and selected "restore to factory". I then started searching for the cache clearing, which changed verbage between 3.x and 4.x releases of Clockwork. After exploring the menus a little, the phone reboots itself from this screen. My blood-pressure goes up, and I worry my toy just became a b-word. Not all was lost though, and the phone happily booted into the stock t-mobile welcome wizard.
I still have superUser installed, and still have root (S=OFF I guess?). I install ROM Manager again, and do the "Flash ClockworkMod Recovery" (which now shows both current and latest recovery as ClockworkMod 3.0.2.4). When I choose Reboot into Recovery however, it reboots back to the MyTouch 4G logo screen (non-animated one), and hangs. After some reading I tried to force recovery boot via ADB, which produced the same result as the soft reset from ROM Manager. After that I tried doing it the manual way with holding the volume button, which launched me into what I believe is a stock recovery console (white with colored options, uses vol +/- and power to navigate). Choosing "recovery" from that screen *also* produces the white logo screen hang.
So my question now is, in it's current state; how can I get to the Clockwork recovery again? From there I bet installing the image will be easy street, but I believe I'm stuck for now.
Side-note: the phone functions fine on regular boots and pure vanilla mode; I just don't want to stop here when I'm pretty close to my 2.3 goal

Well good news and bad news. I was able to get Clockwork going by reverting it to 3.0.0.5 and just using that version. Was able to install ROMs, tested a few. Phone started freezing after/during installing packages. Started the clear cache/install ROM process, ran into this:
Code:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
http://forum.xda-developers.com/showthread.php?p=14389074
Totally stuck at boot screen, but able to get into Clockwork. All ROM zips off the sdcard produce this or an invalid zip error.

Other guy smight tell you what a status 7 might be, but with the flurry of flashing youre doing, you may have gotten some corruption on your sd
try formatting your sd card in the pc, or use another one so you dont have to back everything up on this one. put one rom zip on the root and see if that helps
also, i would make super sure you wiped/factory resetted every possible data/cache in CWM before flashing the zip
lastly, i would md5 test the download to make sure it matches the web page. Plus, after it's transferred to the cleanly-formetted sd, check it again either thru adb, or do the trans on the pc using an sdcard reader and check it once it's on the sdcard, then pop it into back your phone.
good luck

Thanks a ton for the uber fast reply. When I format on the PC, what format do I use, or is there a specific tool to properly format it for the phone?
When I'm wiping /data it's taking forever and I get the following message back:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log/last_log
E:Can't open /cache/recovery/log/last_log
Don't have an adapter at the office today for the sdcard, but I guess I can just grab a new one at lunch? All it would need is a fresh format then the .zip of the ROM in question at the root?

Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.

Jack_R1 said:
Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.
Click to expand...
Click to collapse
So I use the same PD15IMG.zip i did to start, flash it using Clockwork, then start the root > rom process over? I think that it currently tells me it can't find that zip anymore on the white screen pre console, is that expected? I just xfer it to the sdcard prior to fixing?

Yes, that's the right procedure. Move it to the card and start from scratch. Beware not to use the newer Panache/MT4G Gingerbread RUU, otherwise you'll be left with no way to root, or at least harder way.

Ok, so I didn't have a PD15IMG.zip to begin with, I see this thread:
http://forum.xda-developers.com/showthread.php?t=1059347
and that's proper that I'm flashing the radio itself for this process? Which of those images do I want to grab? I always like to double check when I read warnings that are pretty specific about bricking the device

No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.

acsi007 said:
No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.
Click to expand...
Click to collapse
Jesus, glad I asked before getting in there.
So I was going to offer you a beer sometime, I think I owe you a few rounds at this point...
Edit: this one right http://forum.xda-developers.com/showthread.php?t=924923 ?

Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...

acsi007 said:
Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...
Click to expand...
Click to collapse
I rooted gfree originally, and think I may be in the bad place
Fail-PU errors running the update from pd15img. Do I have any options at this point? I bought the phone from Wirefly.com, and since I can't get a recovery image going, I may be fuct here on a return eh?

looks like i'm moving to: http://forum.xda-developers.com/showthread.php?p=14487111#post14487111

Good luck Lars. Let us know that they did and if you had to pay.

[Q] Clockworkmod not Recoverying/Doing anything useful

So I had Cyanogenmod 7.1.0-RC1 flashed on my phone and working fine. Then one day it was all frozen up and wouldn't boot or do anything. So I decided to use Clockworkmod (3.0.2.4) to restore to an old backup I have of Cyanogen 7.0.3. It came up with a silly error saying it could not format /cache, but everything else worked so I shrugged it off and rebooted. Cyanogen 7.0.3 loaded fine, but I could not download apps from the marketplace. (They would never "start" - I even tried installing the new marketplace update). So then I decided to restore the SAME backup again, with the same error, and after struggling I tried restoring to a backup I have of the stock rom. Which worked. Magically. No errors. So then, being stupid and unsatisfied I reflashed the Cyanogen 7.0.3 backup again. This time it said "error while formatting /system!" And now I've been stuck trying to figure out how to fix this error.
I can still boot into ClockworkMod, so I assume my phone is not bricked. I've read that updating to ClockworkMod 3.0.2.5 may actually fix my problem, but I can't seem for the life of me to find a tutorial that can tell me how to flash a new recovery image on the MT4G without Rom Manager (since I can't boot a rom, I can't open rom manager).
Thank you for your time, any help is appreciated. (I also apologize upfront if this error has been reported and solved before, I can't seem to find it though.)

Sorry, but your phone is bricked. Those errors indicate that your eMMC chip has failed. Your only hope is to flash the PD15IMG.zip file from the bootloader. That will unroot your phone and flash the stock ROM. It's unlikely to work, however. Some people will swear up and down that eMMC failure doesn't brick the phone, but I have yet to see anyone save their device once those errors appear in recovery mode.

Thanks for you quick response. I am going to try what you suggested and update what happens.
Do you know what may cause this error? So I can avoid it in the future. Granted, I may not have a phone for a while now.

crebu said:
Thanks for you quick response. I am going to try what you suggested and update what happens.
Do you know what may cause this error? So I can avoid it in the future. Granted, I may not have a phone for a while now.
Click to expand...
Click to collapse
Some MT4G's have a different brand of eMMC chip that is prone to failure after the phone has been rooted. See this thread for a little more info.
Make sure you flash the correct PD15IMG.zip file. Any file flashed in the bootloader has to be named that, so a search could easily turn up a radio. Search the dev section for the stock TMOUS RUU. It will be around ~328MB in size (roughly).

Not every "can't open /cache/recovery/log" error means your eMMC is dead. My phone gave that error after a bad ROM flash. Flashing PD15IMG.zip in hboot fixed it.

TeeJay3800 said:
Some MT4G's have a different brand of eMMC chip that is prone to failure after the phone has been rooted. See this thread for a little more info.
Make sure you flash the correct PD15IMG.zip file. Any file flashed in the bootloader has to be named that, so a search could easily turn up a radio. Search the dev section for the stock TMOUS RUU. It will be around ~328MB in size (roughly).
Click to expand...
Click to collapse
When I try to use Clockwork to update from the zip I get the error
E:Can't open /sdcard/PD15IMG.zip
(bad)
Installation aborted.
Maybe I don't understand the correct procedure for flashing a PD15IMG.zip file?
**EDIT** I'm dumb, I had to boot into the bootloader. Hehe.

crebu said:
When I try to use Clockwork to update from the zip I get the error
E:Can't open /sdcard/PD15IMG.zip
(bad)
Installation aborted.
Maybe I don't understand the correct procedure for flashing a PD15IMG.zip file?
Click to expand...
Click to collapse
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.

TeeJay3800 said:
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.
Click to expand...
Click to collapse
Thank you so, so much.
What you suggested absolutely worked. I'm not back to the stock rom working seemingly perfectly. Does this mean I don't have a bad eMMC chip? Would it be safe to continue flashing custom ROMS?
Thanks again.

TeeJay3800 said:
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.
Click to expand...
Click to collapse
Thank you so, so much.
What you suggested absolutely worked. I'm now back to the stock rom working seemingly perfectly. Does this mean I don't have a bad eMMC chip? Would it be safe to continue flashing custom ROMS?
Thanks again.
Edit: changed "not" to "now". Quite a misleading typo.

crebu said:
Edit: changed "not" to "now". Quite a misleading typo.
Click to expand...
Click to collapse
Haha, yeah it was! I'm glad your phone is not (now) working. As far as where to go from here, find out what eMMC you have. The thread I linked to has ADB instructions in the OP, and there are instructions to run commands via a terminal emulator throughout the thread. If you have the "good" eMMC, there's no reason you can't re-root and start over. Because of the errors you got in recovery, I'm afraid you have the "bad" eMMC in which case rooting is risky. Essentially, once you've rooted a phone with the bad chip, it's only matter of time until it fails and the phone is bricked. It could be a few days, few months, or few years, but the evidence shows it likely eventually will. Good luck!

TeeJay3800 said:
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.
Click to expand...
Click to collapse
hi, could you help me on this?
Even if I hboot my phone ( by hold power and vol down), the phone still gets to CWM. Could you help me to boot PD15img.zip in the bootloader.
Thank you so much,