Related
I am stock at tmobile screen, it doesnt go any further
i went in recovery it returns as
E:Can't Mount /cache/recovery
all the way down
the "fastboot erase recovery" returns with "FAILED (remote: not allowed)" and the "fastboot flash recovery recovery.img" returns the same thing. Any other suggestions???
I tried to restore pd15img and
it works little bit, and it asked me to upgrade, i pressed the volume up
1 BOOTLOADER - Fail-PU
partiton update fail!
update fail!
This has happened to quite a few people lately and I don't think they have been able to come back from it. Out of curiosity though, what caused this? Were you flashing something and this happened? Do you have the engineering bootloader? Attached is a thread of someone with the same problem, and like I said, there are a couple more out there.
http://forum.xda-developers.com/showthread.php?t=984790
I change roms many times, and recovery many times, this time i had been using 3.006 modified with battery charge.
didnt have a problem until i put the royalglacior 1.5 version.
than i could use the wifi, it gave me an error, i rebooted few times, and always error, and finally gave up.
I had the same fastboot errors when trying to flash from 3.0.0.5 to 2.5.1.2 after i mistakenly flashed 2.5.1.2 when i had cm7. You may need to update your sdk. I had to install my HTCdrivers on a new box and Download the tools folder from here http://forum.xda-developers.com/showthread.php?t=928370 to get it working.
theghazi said:
I change roms many times, and recovery many times, this time i had been using 3.006 modified with battery charge.
didnt have a problem until i put the royalglacior 1.5 version.
than i could use the wifi, it gave me an error, i rebooted few times, and always error, and finally gave up.
Click to expand...
Click to collapse
First, there is only RoyalGlacier v 1.2 as of the latest for now. Since you used that CWM 3.0.0.6 while battery charge off, there is a chance it might have reverted back to CWM 3.0.0.5 and RoyalGlacier requires 3.0.0.6 and stock restore requires 2.5.1.4 but your recovery may be 3.0.0.5. Try flashing a ROM that just requires 3.0.0.5. For future reference, use this version of CWM 3.0.0.6 from here (http://forum.xda-developers.com/showthread.php?t=944681). That sticks and never reverts back to .5.
Thanks for replies, n advices.
I have tried every which way possible to put the recoveries, and all failed.
I have had 3.0.0.6 modified for a while. was not going back and forth with 2.5.1.4
anyone else come out of this mess,
if not is there a way to get it to even at s - on and unroot?
I dont think so, but worth to ask
thanks
I'm having the same issue where it gets stuck at the Tmobile spash screen and when i boot into clockwork, it gives me the cache error. Formatting it through clockwork doesnt work, and when i try to restore it it also give me an error. I tried to format through adb but that hasn't worked either, unless I'm typing in the command wrong
I dnt believe there is a way to fix that issue,i had that issue awhile back on my 1st mytouch 4g,i had cm7 & made the mistake of tryin to nandroid restore a backup which I forgot was stocked froyo & everythin flashed ok but got stuck in bootloop,so battery pulled went to recovery & had all those errors u mentioned & never found a fix.....called tmobile,got a replacement no problems 2 mnth later & warranty still there..... Now I have clockwork 3.0.0.6 & havent ran into that issue yet,goodluck let us knw if u find a fix....
Permrooted s=off-MyTouch 4g-White
Eng-0.85.2007
Rom-RoyalGinger
I like balls
I am not using tmobile. I know it is covered under HTC but wont they refuse if they see s off?
Sent from my HTC Glacier using XDA App
theghazi said:
I am not using tmobile. I know it is covered under HTC but wont they refuse if they see s off?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Im not really to sure,a friend of mine had the same issue & went thru HTC & got a replacement so want im guessin is they dnt care but dnt hold it against me,it could of been 1 of those lucky times. All he said was that the phone wnt boot & they just sd it was a known issue & sent him another one...
well I think I've successfully bricked my mt4g. It was working fine until I installed the latest clockwork version and RoyalGinger, tried to restore some applications + data with mybackup root but it froze. Then it was stuck on a bootloop, went back into clockwork and started getting the "can't mount cache" errors. Now it's stuck on the T-Mobile splash screen if I try to do a normal boot, bootloader works and it also goes into clockwork, but it's not able to do any factory resets/wipe. Tried the factory image file and it fails on the first 5 or 6 items, skips another item and hangs at flashing the radio. Now it needs to be replaced and T-Mo is out of stock of the red mt4g's, so I have to wait until they have stock of red ones, then it's going to suck if I get one with a bad screen. I got offered a black one, but I just like my red one too much.
did you include the part file when flashing the PD15IMG.zip?
"there needs to be part7backup-1294463706.bin file on your sd card with the PD15IMG.zip file...both on the root of sd card."
I'm thinking that the file comes stock on the sdcard, but when we format our sdcard it wipes it. I know I personally ran the PD15IMG.zip file twice on my phone and both times it worked great, but both times I did it before I wiped my sdcard (and I do remember a ridiculous amount of extra stuff on the sdcard when it came with the phone).
darinmc said:
did you include the part file when flashing the PD15IMG.zip?
"there needs to be part7backup-1294463706.bin file on your sd card with the PD15IMG.zip file...both on the root of sd card."
I'm thinking that the file comes stock on the sdcard, but when we format our sdcard it wipes it. I know I personally ran the PD15IMG.zip file twice on my phone and both times it worked great, but both times I did it before I wiped my sdcard (and I do remember a ridiculous amount of extra stuff on the sdcard when it came with the phone).
Click to expand...
Click to collapse
That part7-xxxxx.bin file is created when u root with the gfree method,it doesnt come stock on the sd card... what method did u use to root...dnt use unlockr.com methods,its old & doesnt give true oerm root...
I made an assumption, i just used the basic root.sh script so I didn't read into the gfree method (see no need). I just know that people who have had trouble reverting to stock with the PD15IMG.zip fixed the issue by putting that part7backup file on the root of their sdcard.
darinmc said:
I made an assumption, i just used the basic root.sh script so I didn't read into the gfree method (see no need). I just know that people who have had trouble reverting to stock with the PD15IMG.zip fixed the issue by putting that part7backup file on the root of their sdcard.
Click to expand...
Click to collapse
gfree method would of gave u S off & that backup file,really I dnt think theres a fix for that just yet,without that file..... For future reference never restore data fron any backup app(ex.titanium,astro erc) u can only restore apps cause then u restorin data from a different rom & tryin to put it on a current rom that probably isnt the same...
cmdmilitia13 said:
gfree method would of gave u S off & that backup file,really I dnt think theres a fix for that just yet,without that file..... For future reference never restore data fron any backup app(ex.titanium,astro erc) u can only restore apps cause then u restorin data from a different rom & tryin to put it on a current rom that probably isnt the same...
Click to expand...
Click to collapse
no idea where this is coming from. I was just offering a suggestion to the op. As you can clearly see I am not the op. I do not have issues. I simply made an assumption about the gfree method, which was cleared up, though I still think it's a very real possibility that the op didn't put the part7 file on the root of his sdcard when he flashed the pd15img.zip. Either way, I thank you for your advice, but I'm not the one seeking it here.
darinmc said:
no idea where this is coming from. I was just offering a suggestion to the op. As you can clearly see I am not the op. I do not have issues. I simply made an assumption about the gfree method, which was cleared up, though I still think it's a very real possibility that the op didn't put the part7 file on the root of his sdcard when he flashed the pd15img.zip. Either way, I thank you for your advice, but I'm not the one seeking it here.
Click to expand...
Click to collapse
My fault I should of double read,i have an issue with just skimmin thru things & look what happens lol...
Has anyone found a fix for this? Same issue.
Isubbie said:
Has anyone found a fix for this? Same issue.
Click to expand...
Click to collapse
nope nothing yet,not that I knw off...
i installed a rom (royal ginger), it loads but after it loads it reboots the phone and does the same thing all over again, i rent to recovery to do a full wipe and re install and it comes up with "E: Cant open /cache/recovery/log" and some more errors, how do i fix this problem? i hope i havent bricked my phone
lanceydavid said:
i installed a rom (royal ginger), it loads but after it loads it reboots the phone and does the same thing all over again, i rent to recovery to do a full wipe and re install and it comes up with "E: Cant open /cache/recovery/log" and some more errors, how do i fix this problem? i hope i havent bricked my phone
Click to expand...
Click to collapse
What exactly did u do to get that error??? Did u wipe data,cache,delvik & format system,i always format sd card also in case the sd card has a currupt file... did it automatically give the errors once u flashed?? Did u check the mdsum on the file to make sure u had a full zip file??? What recovery did u use 3.0.2.4 or 3.0.0.6??Sorry need to ask questions in order to help lol.... Ive heard of people fixin their phones with the part7backup-xxxxx.bin file & the pd15 file....just stick those to the root of the sd card go into recovery & let the phone to its thimg..
@cmdmilitia13 Thanks so much for even trying to help! i have clockworkmod recovery 3.0.0.5 .... i flashed, worked perfectly, installed the rom the last night, woke up in the morning, phone wouldnt turn on, took out battery, and when it finally loaded, it kepts rebooting back to the loading screen.... i went back to recovery, tried to wipe data and cache, wont work, did delvik, and didnt say if it was successful or not but i formatted sd card, as soon as i try to format system it says:
E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log and etc.
as soon as i try a wipe it says the similar
lanceydavid said:
@cmdmilitia13 Thanks so much for even trying to help! i have clockworkmod recovery 3.0.0.5 .... i flashed, worked perfectly, installed the rom the last night, woke up in the morning, phone wouldnt turn on, took out battery, and when it finally loaded, it kepts rebooting back to the loading screen.... i went back to recovery, tried to wipe data and cache, wont work, did delvik, and didnt say if it was successful or not but i formatted sd card, as soon as i try to format system it says:
E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log and etc.
as soon as i try a wipe it says the similar
Click to expand...
Click to collapse
Royalginger requires recovery 3.0.0.6 or 3.0.2.4....3.0.0.5 was mainly for cm7 but clockwork updated to flash froyo & gingerbread now... I believe u can dwnload a cm7 rom to the sd card frm the pc then try to flash that if that dnt wrk then if u rooted by using gfree method & have the 0.85.2007 bootloader it should of created a part7xxxx.bin file & that will help unrootin the phne & startin frm scratch again...
Theres a couple threads on here that could help u out,ur not fully bricked tho... I had this issue about 3 months ago when there barely was a fix now at least u have a chance..
i have the 0.86.0000 bootloader, will that be a problem? if not if i google how to unroot i should be able to find it easily?
i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?
lanceydavid said:
i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?
Click to expand...
Click to collapse
I believe u need to have that 0.85.2007 bootloader but look around the Q&A threads & look for the subjects that says bricked or I think im bricked,those would help u out,im headin to wrk so cnt helo u now sorry...
lanceydavid said:
i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?
Click to expand...
Click to collapse
If you rooted with gfree, go back to the thread that guided you. It has instructions on how to unroot. Basically you want to place part7backupxxxxxx.zip on the root of your SD, download PD15IMG.zip, place on root of SD, then load bootloader and let it do it's thing, responding when prompted. If you can't mount the card you're going to have to find a way to mount it outside of the phone, either with an adapter or a card reader.
darinmc said:
If you rooted with gfree, go back to the thread that guided you. It has instructions on how to unroot. Basically you want to place part7backupxxxxxx.zip on the root of your SD, download PD15IMG.zip, place on root of SD, then load bootloader and let it do it's thing, responding when prompted. If you can't mount the card you're going to have to find a way to mount it outside of the phone, either with an adapter or a card reader.
Click to expand...
Click to collapse
Doesnt he need the eng 0.85.2007??
cmdmilitia13 said:
Doesnt he need the eng 0.85.2007??
Click to expand...
Click to collapse
Nope. I'm on 86 and have rooted and unrooted this phone about 30 times helping people and trying stuff.
Sent from my HTC Glacier using XDA App
cmdmilitia13 said:
Doesnt he need the eng 0.85.2007??
Click to expand...
Click to collapse
You need the engineering bootloader to use adb, both will run the PD15IMG.zip.
darinmc said:
You need the engineering bootloader to use adb, both will run the PD15IMG.zip.
Click to expand...
Click to collapse
Thanks good to knw,i just thought u needed it since everyone talks about it...
cmdmilitia13 said:
Thanks good to knw,i just thought u needed it since everyone talks about it...
Click to expand...
Click to collapse
The reason we talk about is pretty simple. .85 allows you to use ADB commands and flash stuff via the HBoot engine. Where .86 does not allow you to. So if you get in "semi-brick" mode you can 9/10 times get your self up and rocking.
had it happen earlier today as a matter of fact.
http://forum.xda-developers.com/showthread.php?t=1040463
and this one rings a bell....
http://forum.xda-developers.com/showthread.php?t=1035413
They were both what most people would call bricked, but since they had the .85 engineering screen we could get them up and running.
Edit: whoops, I meant to post this in Q&A - feel free to move it there if more appropriate.
So the surge in cant mount cache E errors peaked a last week it seems. The problems and solutions were all over the map. Where it came from, what caused it, how people recovered, what they were doing when it all started. Even in the dev forums, it's still a partial unknown. (Good ideas as to how to fix/avoid, but no nailed-down cause other than circumstantial evidence)
So the bottom line from what my still-beginner's eye tells me is that clockwork recovery is borked, it's linked with using rom manager, and previously having used the gfree rooting method, an much of this happens after flashing a new rom (and possibly not wiping every cache?).
In the main gfree thread
http://forum.xda-developers.com/showthread.php?t=858996
it does say that recovery might get borked (and you need to pull the battery to reboot) but you can fix it by reinstalling recovery through clockwork. Well, I never had a problem needing to pull the battery. Well, wait a minute. I did.
What I did:
visionary11 to temp
abd gfree files over
terminal: etc gfree -f, worked fine.
rebooted and say s=off at hboot screen
knew i wasnt rooted yet until i did visionary again, so i did.
black screen for too long, didnt come back as rooted, hung on black screen
Rebooted by taking battery out, did vis11 again and then it returned to the vis screen, and i was su ok in terminal.
now- that time i had to pull that battery, and having previously used gfree - do i have a borked cwm and i dont even know it?
i can boot into hboot then pick recovery, i even made nandroid. but the proof is when you do a restore or flash a new rom, im almost afraid to do a nandroid restore.... Ive just flashed a single time-- RG1.6 (working great)
now, are we supposed to ALWAYS, as a prevantative measure, reflash recovery 3.0.2.4 even if we havent had a problem?
Have those who received this error at one point or another-- have they ALL reflashed 3024 after using gfree to root?
my point is, that warning in the gfree root thread (second red text line) means more to me now that I know more of the moving parts. Is avoiding this soft/hard brick as easy as making it mandatory to reinstall/reflash a fresh CWM3024 after rooting or after every flash of a rom?
I know about pd15immg and part7 working for many people to restore from the error. i also know about the earlier ext3 CWM 2.x recovery version being needed to reflash pd15img with less problems than 3024. but those solutions, while a good bet, are still not shown to be slam dunk.
im just trying to come up with some steps that will almost guarantee avoidance of the cache error loop to begin with...
well for starters, i think that anyone who doesn't do a nandroid backup and then a full wipe before flashing a rom is asking for trouble. I run clockwork 3.0.2.4 and have had ZERO issues. here is what i do:
wipe...
/dalvik-cache
/cache
/data
/system
then...
factory data reset...no issues and i flash too often lol.
According to trueblue_drew he says to do this as far as wiping your stuff...
This is how you should wipe:
Main Recovery Menu:
1. Wipe data / factory reset
2. wipe cache partition
Advanced Recovery Menu:
3. Wipe Dalvik Cache
Mounts and Storage Recovery Menu:
4. Format System
Sent from my HTC Glacier using XDA App
It only happens to gfree users i think. If they reflash recovery after using gfree the issue is basically avoided.
1. i'm not super focused on the wiping part, so i dont want to make this thread into a wiping thread, although it is important. im trying to wrap my head around the entire gamut of causes and get some main ansers that are solid
2. "reflash recovery after using gfree the issue is basically avoided.". I'd like to get some data on this, and I'm hoping that people who DID reflash CWM after gfree ( reflashed it a second time after wiping everything and flashing a rom-- if they STILL got the error. I'm betting that only a small minority flashed CWM recovery TWICE. I'm hoping to find out if any of them STILL got the error ( i'm hoping not). I"m also wondering how many didnt reflash CWM (because there was nothing acting up to cause them to do so) but they still may have a latent problem there, waiting to creep up after some incomplete data wipe, or some SD card anomaly, and then surface...
I had the error once & had to replace the phone.. I made the mistake by usin recovery 3.0.0.5(this was before 3.0.0.6 & 3.0 2.4 came out)to go bck to a froyo rom but only because cm7 rc2 wasnt allowin me to do anythin with the phone(all forcecloses) so booted recovery wipe everythin & flashed froyo rom & there goes my phone.Fried.lol my mistake for not READING before flashin.. Anyway ive been readin lately that people have been tryin to restore apps & data with titanium,big no-no,with restorin data frm other roms...
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
Kernel-ckisgen-smartass-v1.1
I pulled that same mistake also when CM7 alpha previews first came out, I had the 3.0.0.5 recovery, installed the preview to test out,and then I restored a nandroid backup of my Iced Glacier rom and instead of being stuck at the mytouch screen or not booting up, I just got bootloops until I flashed the froyo capable version of Clockwork through adb. Mind you, that's when I had used the first method of gaining S-OFF. I haven't been using gfree method until I got this, my third replacement and first method wouldn't stick so I ended up using gfree.
I'm soo leaning over the gfree method being the culprit and ****ing up the paritions.
I have the same thread over in the general section and user "_ice_" said that gfree also alters you dev partition block which can also cause problems.
I'm also very scared to flash roms, I've tried flashing the new virtous rom the other day, my heart just dropped after it got stuck at the mytouch screen for 5 minutes, i wiped everything, and it still wouldn't boot, I did a nandroid it wouldn't pass the mytouch, obviously I could still enter the recovery so I knew I was good and had no errors about not being able to mount. I just flashed CM7 all over again after wiping system, data, cache, dalvik etc and then advanced restored data and it booted back up.
Here is what i would say.
To avoid these issues, do these things:
1. If you used gfree, reflash cwm recovery at least once. Preferably twice to make it stick.
2. If you used the visionary method with root.sh, don't worry about it as much. Reflashing cwm recovery isn't required, but it can't hurt.
Because of this I would recommend the root.sh method unless you want carrier unlock.
Sent from my HTC Glacier using XDA App
What if the root.sh method doesn't stick? Many have said if it doesn't work twice, then do a factory reset.
I'll be unrooting and trying the root.sh method again, and I'll update this thread as well as mine with how I did it and a step by step tutorial. Even though we have one, I feel like its vague and doesn't give much advice.
And also, this has been happening with G2 users as well, G2 users are looking into it and seems as there is a batch of chips that are bad and get corrupted after a while. That's just a possibility as what about the users who aren't rooted and or rooted with root.sh.
And also, those users were rooted via gfree. I'm going to read the logs from the irc channel and post a summary on my thread later on with my findings.
Sent from my HTC Glacier using XDA App
kimbernator said:
Here is what i would say.
To avoid these issues, do these things:
1. If you used gfree, reflash cwm recovery at least once. Preferably twice to make it stick.
Click to expand...
Click to collapse
What do u mean by reflashin cwr? Sorry for the dumb question..
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
Kernel-ckisgen-smartass-v1.1
Rom manager, and the top will say current recovery, click on it, confirm mytouch 4g, and then it'll flash. But the thing is, we still haven't been able to rule out and say that the recovery is causing this problem.
Sent from my HTC Glacier using XDA App
xdviper said:
Rom manager, and the top will say current recovery, click on it, confirm mytouch 4g, and then it'll flash. But the thing is, we still haven't been able to rule out and say that the recovery is causing this problem.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I thought that was what that meant lol.. I been on 3.0.2.4 since day 1 it came out & havent ran into those nasty forcecloses then the dreaded error YET.. Before I flash a rom now I always reflash recovery,then power off phone & go into recovery manually,then I wipe by 1st wiping data then cache then dalvik then format system(i do this 2 or 3 times dependin what rom im gonna flash)then I flash the rom..Another thing I never do is restore apps,i rather just dwnload them again..I dnt do nandroid restores cause I dnt trust it but always do bckups(would only nandroid restore if ABSOLUTELY have too) With my other mytouch that I screwed up,i wasnt careful enough now I make sure I have an empty phone before I flash
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
Kernel-ckisgen-smartass-v1.1
Funny, right after I posted this, bam!, like 3-4 threads appeared in various places talking about variants of this. This is what I was trying to improve upon, but oh well, we'll jump around from thread to thread I guess...
hey guys how you all are?
i have a mytouch 4g white right, but i think something went wrong when rooting (stupid thing probably because i have rooted about 14 mytouch) and now it acts stupid and the recovery is f----d up and it dont flashes well, also i tried to restore it back by flashing by hboot but it didnt work, im trying to get some help from you guys to see if i can recues this phone ....any help will be apreciated guys, thanks
bosina said:
hey guys how you all are?
i have a mytouch 4g white right, but i think something went wrong when rooting (stupid thing probably because i have rooted about 14 mytouch) and now it acts stupid and the recovery is f----d up and it dont flashes well, also i tried to restore it back by flashing by hboot but it didnt work, im trying to get some help from you guys to see if i can recues this phone ....any help will be apreciated guys, thanks
Click to expand...
Click to collapse
Do u have the cnt mount cache/data error?? How did u root,gfree or the other method?? What exactly was done to the phone that u think/knw the recovery is screwed? Being a lil bit more specific could help us help u : )
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.2
cmdmilitia13 said:
Do u have the cnt mount cache/data error?? How did u root,gfree or the other method?? What exactly was done to the phone that u think/knw the recovery is screwed? Being a lil bit more specific could help us help u : )
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.2
Click to expand...
Click to collapse
look bro i rooted with cm method.... the chache log mount error and i cant moutn cache,cant flash sense roms and the only that works it cm7 but bootloops and when it boots up, everything fc and reboots..... i did the cm method but i dont know what went wrong, the hboot does not recognize the pd15img, it just scans but nothing found, i was trying to get it back to redo the root but no luck
............guys please help me out
What recovery are you using?
Did u put the pd15 file to the root of the sd card? Thats the only way hboot will scan that file..
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.2
coupetastic-droid said:
What recovery are you using?
Click to expand...
Click to collapse
the lastest bro
cmdmilitia13 said:
Did u put the pd15 file to the root of the sd card? Thats the only way hboot will scan that file..
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.2
Click to expand...
Click to collapse
bro i know all that stuff, talk to me like talking to someone that knows a lot but made a little error that is costing much, yeah i put it in the sd and it scan but it does not find it?
Check THIS out. If your CWM looks like that screen shot, follow the method that fixed mine. BUT if the first line that comes up is COMMAND ERROR or something like that... your f*cked man, sadly. I feel your pain I have a glorified battery charger right now.
dcwiker05 said:
Check THIS out. If your CWM looks like that screen shot, follow the method that fixed mine. BUT if the first line that comes up is COMMAND ERROR or something like that... your f*cked man, sadly. I feel your pain I have a glorified battery charger right now.
Click to expand...
Click to collapse
yeah man thats what comes up in mine..
guys what is the fix for that.. ??
Sounds like your f*cked bro.
Help problem with mytouch 4g
Hi i have a MyTouch 4G rooted with Virtuous Fusion ROM. Everything was working until when I tried to install Miui Music Player on it. I did adb push but after doing it when i unplugged the phone from my computer several Force Close came up then i rebooted my phone then the MYTOUCH Tmobile logo start up screen came then the HTC logo came then my phone will shut down. I tried to start my phone again the same thing happen. I did Hboot and tried recovery from there but it didnt work. I tried Factory Reset but it failed. I go to clockwork recovery mode if i do backup and restore or factory reset nothing happens. Does it mean my phone is gone? Is there anything i can do to fix it? Please anybody help
If when you go into hboot it says you have s-off and you're able to get into recovery and its the latest like you say, then you should still be good.
From a pc just download any rom. I suggest downloading cm latest nightly just for the mean time.
-Go into recovery on your device.
-Plug your device to the pc go into mount and storage and mount sdcard.
-On your pc open your device sdcard and place the nighly rom you downloaded in it.
-Unmount your sdcard from your device, press the back button and from recovery flash the nighly rom.
Hope that works for you.
coupetastic-droid said:
If when you go into hboot it says you have s-off and you're able to get into recovery and its the latest like you say, then you should still be good.
From a pc just download any rom. I suggest downloading cm latest nightly just for the mean time.
-Go into recovery on your device.
-Plug your device to the pc go into mount and storage and mount sdcard.
-On your pc open your device sdcard and place the nighly rom you downloaded in it.
-Unmount your sdcard from your device, press the back button and from recovery flash the nighly rom.
Hope that works for you.
Click to expand...
Click to collapse
if that goes to me, i really did it all, i have s-off but when i try to flash by hboot it scans but never finds nothing and in recovery says the message about the cache not mounting and i try to mount cache but it shows error mounting cache.... if i flash a sense rom it flashes but when i but cm7 stills there and then it soft reboots without letting me go into the phone and if i flash cm7 again it goes into the phone and i try to open browser and it fc, also try to open dialer and it shows back screen and goes back... rom manager fcs... i tried flashing a new recovery but nothing.... if hboot could recognize the pd15img i just flash back and redo the work but it never finds noting... i dont know what going on guys.... tell me what i can do if there is some i can do
pching999 said:
Hi i have a MyTouch 4G rooted with Virtuous Fusion ROM. Everything was working until when I tried to install Miui Music Player on it. I did adb push but after doing it when i unplugged the phone from my computer several Force Close came up then i rebooted my phone then the MYTOUCH Tmobile logo start up screen came then the HTC logo came then my phone will shut down. I tried to start my phone again the same thing happen. I did Hboot and tried recovery from there but it didnt work. I tried Factory Reset but it failed. I go to clockwork recovery mode if i do backup and restore or factory reset nothing happens. Does it mean my phone is gone? Is there anything i can do to fix it? Please anybody help
Click to expand...
Click to collapse
did you try putting the PD15IMG on your sd for flashing thru hboot ?>
welll seems like clockworkmod is causing some serious problems
bosina said:
if that goes to me, i really did it all, i have s-off but when i try to flash by hboot it scans but never finds nothing and in recovery says the message about the cache not mounting and i try to mount cache but it shows error mounting cache.... if i flash a sense rom it flashes but when i but cm7 stills there and then it soft reboots without letting me go into the phone and if i flash cm7 again it goes into the phone and i try to open browser and it fc, also try to open dialer and it shows back screen and goes back... rom manager fcs... i tried flashing a new recovery but nothing.... if hboot could recognize the pd15img i just flash back and redo the work but it never finds noting... i dont know what going on guys.... tell me what i can do if there is some i can do
Click to expand...
Click to collapse
You're confusing me man. I thought the whole reason for this post was because you couldn't flash roms. But now you're saying it goes into cm7 but you have fc's. So I really do not see anything wrong. You're just probably doing some thing to cm7 that's not compatible with it.
I just say re-download cm7 and re-flash it. Before flashing though, clear all data l/factory reset, cache and dalvik.
coupetastic-droid said:
You're confusing me man. I thought the whole reason for this post was because you couldn't flash roms. But now you're saying it goes into cm7 but you have fc's. So I really do not see anything wrong. You're just probably doing some thing to cm7 that's not compatible with it.
I just say re-download cm7 and re-flash it. Before flashing though, clear all data l/factory reset, cache and dalvik.
Click to expand...
Click to collapse
noo bro the recovery is fuc--d up... it does not mount cache and it doesnt flash sense roms and nor other rom... it dont fix permissions, it freezes a lottttttttttttttttttttttttttttttttttttttttttttttttttttttttttt...... i just dont know what to do.
If you are getting the cant mount cache error fallow what I said (if you have hboot and know adb) Flash a 2.x.x.x CWM reboot recovery format cache. BUT if you get an error in adb when trying to flash the old CWM (something like write FAILED I think I don't remember exactly) but if you get that error...as stated above, you're f*cked. I have a glorified battery charger too so I feel your pain. But as of right now there isn't a cure for the EMMC failing (which is what causes this issue.)
Hope you can flash an old CWM. If so I recommend unrooting and rerooting with the root.sh method.
Mytouch 4g help
bosina said:
did you try putting the PD15IMG on your sd for flashing thru hboot ?>
welll seems like clockworkmod is causing some serious problems
Click to expand...
Click to collapse
no i did not do flashin through hboot. I downloaded a zip file for MIUI Music player then unzip it on my computer at C/: android-sdk-windows/tools Then i did the ADB push for miui apk to /system/app. After i did this several force close came up then i removed my phone from my PC and restarted my phone. Then start up logo comes out but my phone will not completely boot up. What can i do to fix this? Does this mean my phone is bricked.
Hello all,
I successfully rooted (temp rooted using Visionary) my phone: myTouch 4g 2 days ago, and had removed all stock apps. Then I felt I wanted the stock mail app back, so I tried to reinstall it. Since it was showing errors, I renamed the /system/lib/libm.so file to /system/lib/libm_orig.so thinking that it was related to the mail app. Realizing my mistake, I tried renaming it back but in vain. I restarted my phone and now it does not boot at all. (what was I thinking!!? just one rename caused all of this!)
To all experts here - Do I have a chance to get my phone working back? If so, what should I do?
I have tried the following:
- tried a factory reset (I have never flashed a custom rom on it), but no luck.
- fastboot a clockwork recovery image, but no luck. It says "writing recovery... FAILED (remote: not allowed)
- adb shell - does not find the device
- By the way, before I made the renaming-change, I had turned off 'USB debugging'.
Some info that shows on the screen after vol down + power:
GLACIER PVT SHIP S-OFF
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Please help!!!
adi20 said:
Hello all,
I successfully rooted (temp rooted using Visionary) my phone: myTouch 4g 2 days ago, and had removed all stock apps. Then I felt I wanted the stock mail app back, so I tried to reinstall it. Since it was showing errors, I renamed the /system/lib/libm.so file to /system/lib/libm_orig.so thinking that it was related to the mail app. Realizing my mistake, I tried renaming it back but in vain. I restarted my phone and now it does not boot at all. (what was I thinking!!? just one rename caused all of this!)
To all experts here - Do I have a chance to get my phone working back? If so, what should I do?
I have tried the following:
- tried a factory reset (I have never flashed a custom rom on it), but no luck.
- fastboot a clockwork recovery image, but no luck. It says "writing recovery... FAILED (remote: not allowed)
- adb shell - does not find the device
- By the way, before I made the renaming-change, I had turned off 'USB debugging'.
Some info that shows on the screen after vol down + power:
GLACIER PVT SHIP S-OFF
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Please help!!!
Click to expand...
Click to collapse
Did you make a nandroid backup of your rom before you removed anything and can you boot into recovery, not boot loader but recovery with all the orange text? If the answer is yes to both, then boot into recovery and select backup/restore and then select restore and restore the backup.
truckerdewd said:
Did you make a nandroid backup of your rom before you removed anything and can you boot into recovery? If the answer is yes to both, then boot into recovery and select backup/restore and then select restore and restore the backup.
Click to expand...
Click to collapse
That was my first thought, but then I remembered he only temp rooted. You can't install a custom recovery with only temp root. As for the problem, I don't know of a solution. It actually sounds kind of bad because there is no backup, no custom recovery to flash anything new, no engineering bootloader to use fastboot, and the phone won't boot which would allow the phone to be perm rooted with gfree or Visionary. This might be a PD15IMG.zip situation.
TeeJay3800 said:
That was my first thought, but then I remembered he only temp rooted. You can't install a custom recovery with only temp root. As for the problem, I don't know of a solution. It actually sounds kind of bad because there is no backup, no custom recovery to flash anything new, no engineering bootloader to use fastboot, and the phone won't boot which would allow the phone to be perm rooted with gfree or Visionary. This might be a PD15IMG.zip situation.
Click to expand...
Click to collapse
I missed the temp root part
Sent from my wickedly brilliant Virtuos Unity Sense 3.0 BluMagic HD Android powered black myTouch 4G with my fingers.
truckerdewd said:
I missed the temp root part
Click to expand...
Click to collapse
As you said before, we all miss stuff.
Thanks guys! That was real quick!
So when you say: "This might be a PD15IMG.zip situation.", do you mean the instructions below? (got it from androidforums.com/mytouch-4g-all-things-root/234246-mytouch-4g-roms-2.html)
The easiest way to unroot is to boot into HBOOT (the same place you check for S-OFF) and flash PD15IMG.zip (DO NOT TRY TO FLASH THROUGH RECOVERY!)
PD15IMG.zip will overwrite everything on the phone and turn S-ON, reinstall oem recovery, and reinstall the stock ROM as it was the very first time you turned on the phone. Truly one-click.
Unrooting is so easy I really can't think of any reason not to. Here's the guide.
theunlockr.com/2010/12/16/how-to-unroot-the-t-mobile-mytouch-4g
Download the file. Rename to PD15IMG.zip. Make sure it's pd15img.zip and not pd15img.zip.zip. Do you have file extensions showing in windows? Do you know what that means?
Copy file to root of sdcard. Not in a folder, just on the sdcard.
Power off phone and remove battery. Reinstall battery but do not power on phone.
Hold vol down + power until you get to a white screen. The phone should "detect" pd15img.zip.
Follow the on-screen instructions to update.
DO NOT TOUCH IT UNTIL IT'S DONE AND REBOOTS ON ITS OWN INTO THE STOCK ROM. This might take a while.
Yep, that's exactly it. There are a couple threads that have that file in it. The file is ~312MB in size. That will restore your phone to 100% out-of-the-box, post OTA status. Of course you'll loose any personal data stored in internal memory.
This is the original thread on restoring your phone to unrooted stock, but the download there doesn't seem to work anymore.
This thread has a working download link to the same file. Just make sure you rename it to PD15IMG.zip before trying to flash it.
Ok, thanks so much! I will let you guys know how it goes.
adi20 said:
Ok, thanks so much! I will let you guys know how it goes.
Click to expand...
Click to collapse
Good luck. Hope you get it all straightened out. Would hate to see you lose the use of an excellent phone
Sent from my wickedly brilliant Virtuos Unity Sense 3.0 BluMagic HD Android powered black myTouch 4G with my fingers.
truckerdewd said:
Good luck. Hope you get it all straightened out. Would hate to see you lose the use of an excellent phone
Sent from my wickedly brilliant Virtuos Unity Sense 3.0 BluMagic HD Android powered black myTouch 4G with my fingers.
Click to expand...
Click to collapse
Thanks so much guys! It worked as you said.. and it was so simple too!
One thing I checked though was that the s-off was not changed to s-on.. which is ok, right? I would like to root permanently (this time taking necessary backups . Does the s-off/on play any role in whether I can root or not?
S-off is a good thing young grasshopper..thats what ur attempting to do when you root