Database Users

Reset my incredible!

Ok so I am having some serious issues with my phone. I have rooted it before the 2.2 update was out for the incredible and I have messed around with it since. I have used unrEVOked's s-off patch and because of it now my phone will not do a couple of things. The system update keeps bothering me to update but when i tell it to do so it fails to restart. Also the My Verizon app doesn't work at all, it fails to recognize my phone (surprise surprise). My phone currently works fine as a phone and data device but those things really bother me and I want to get it back to a factory image. When I go to switch the S-ON with Clockwork Recovery, as I select the update.zip file that switches the S-ON the screen goes black and resets to the menu. I have no idea what to do from here. Does anyone have any ideas?

You need to use the unrevoked s-on tool if you want to go back.
See the faq section at this link.
http://unrevoked.com/rootwiki/doku.php/public/forever
Also, if you've flashed a custom rom you'll need to install an ruu to get back to stock.
Do a lot of reading first and proceed at your own risk!
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01

I am just going to restate that in using the S-ON tool clockworkmod recovery resets and goes back to the main menu. That was the other problem that I could not even use RUU's to reset my phone. It won't even recognize it attached

Sorry. Sounds like you have issues beyond my ability.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01

Have you tried this thread;
http://forum.xda-developers.com/showthread.php?t=786436
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01

I gave that a shot, but unfortunately after following each step i came to the same problem that it will not apply the S-ON.zip file in clockworkmod recovery. DAH! I think i messed it up pretty bad.

SerenadeX said:
I gave that a shot, but unfortunately after following each step i came to the same problem that it will not apply the S-ON.zip file in clockworkmod recovery. DAH! I think i messed it up pretty bad.
Click to expand...
Click to collapse
Just curious. What radio are you on? I remember reading somewhere that S-Off and on don't support the 9-1 + radios. And what clockworkmod version are you on?
Sent from my ADR6300 using XDA App

I am using 2.15.00.07.28. Following the guide linked in a previous post on this thread, I changed it to this to make S-ON work but to no avail. I assume i have the latest clockworkmod because i just barely reflashed it with unrevoked. It is vers. 2.5.1.2

Have you tried the official one posted here?
http://unrevoked.com/rootwiki/doku.php/public/forever
It looks like they have updated it for the new radios. And the one on the guide might be an older version.
Sent from my ADR6300 using XDA App

You will need to go back to a stock recovery in order to get the VZW OTA to work
the lack of that recovery will make the phone update fail to reboot.

Soopafly Incredible said:
You will need to go back to a stock recovery in order to get the VZW OTA to work
the lack of that recovery will make the phone update fail to reboot.
Click to expand...
Click to collapse
Yeah I gave that a shot when I was trying the guide posted previously. It reset my recovery to stock but when it tried doing the OTA it still failed to reboot. I'll try using the latest S-ON tool. Worked!! Wow! I have never got this far. Now lets see if it solves the problem...

Out of curiosity why even bother going back to stock? You could have most likely fixed all of your issues just by flashing a newer rom.

[Q] Can't Mount Cache error: let's collect all the answers here

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...

bad emmc preventing me from flashing now..

is there anything else i can do to flash roms still? or am i stuck on my icecoldsandwich backup forever?

Bootloader version?

how would one go about locating this?

Reboot. When your screen goes black and backlight on keys goes out hold down volume down to boot into bootloader. Write down the info displayed at the top of the screen and post it here.

estallings15 said:
Reboot. When your screen goes black and backlight on keys goes out hold down volume down to boot into bootloader. Write down the info displayed at the top of the screen and post it here.
Click to expand...
Click to collapse
Is bootloader even relevant here? Anyway, are you sure its the eMMC? Usually symptoms for bad emmc include lag and ending up with a shiny paperweight. Why domt you try reflashing cwr?

THEindian said:
Is bootloader even relevant here? Anyway, are you sure its the eMMC? Usually symptoms for bad emmc include lag and ending up with a shiny paperweight. Why domt you try reflashing cwr?
Click to expand...
Click to collapse
Yes it is relevant. Very. Ever since the HTCdev unlocked boot loader came about I've seen some weird things. By telling us what bootloader he has we know exactly what he is dealing with.

+ 100
Sent from my MyTouch 4G using XDA Premium App

Glacier pvt eng s=off
H-boot .85.2007 (pd1510000)
Microp-0429 radio- 26.11.04.03_m
Emmc-boot
Oct 11 2010 12:44:14

Engineering bootloader. So you should be good to flash another rom. Reflash CWM recovery using ROM manager, just in case there is sonething wonky with your recovery. Download your desired rom. Reboot into recovery. Make a backup. Go to mounts and storage. Format system and data, and wipe cache. Go back to main menu and hit wipe data/factory reset. Then install your rom.
If you have tried those steps before to no avail then.... I don't know.

Tried flashing cwm again through rom manager again. I was getting hopeful when I noticed the bootanimation was lasting longer then usual...then my heart sank when it froze.
Just to make sure I did it right
I reflashed cwm using the rom manager app
Formatted system data and cache under mounts and storage
Factory data and full wipe them cache and dalvik
Flashed the latest version of the ice cold sandwich rom
And then freeze..

No, that was pretty frickin thorough. Man.... what a drag. I don't get it. Does anyone have any ideas at all?

Flash a non ics Rom, that might be it
Sent from my HTC Glacier using XDA

what if you tried flashing one of those RUU files at least to get hte phone back to stock.
You know where you hook your phone up to the computer and then run the .exe file from your computer?

[Q] Stuck on Boot logo after updating radio

Hi
I am currently on DARKSIDE CM7.2.0 rc1 and was experiencing quick battery loss during calls. So I decided to update the radio but after following the instructions and flashing few radios I am still stuck on boot logo.
Following are details of Bootloader
GLACIER PVT ENG S-OFF
HBOOT-0.85.2007
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010,12:44:14
I tried following radios
http://www.androidinsomnia.com/r-and-r/
Download: 12.28b.60.140e_26.03.02.26 - T-Mobile MyTouch 4G
Download: 12.58.60.25_26.11.04.03
Download: 12.62.60.27_26.13.04.19
Can anybody suggest how to fix this. I hope I haven't bricked the phone.
Thanks.

Flash 2.2.1 PD15IMG.zip. If you get a failed-PU update, you're bricked.

Issue fixed
Actually after the Radio update some how access to cache partition was not available. I booted in to recovery from ADB and got an alert regarding formatting cache.
So to be on safer side I formatted all partition except SD and restored it from my ROM backup.
For past 30 mins my heart was in my mouth and I was already planning to buy Galaxy S3 but I guess Glacier is quite robust and with such a wonderful developer community it has a long way to go.
Thanks for responding.

archangel25 said:
Actually after the Radio update some how access to cache partition was not available. I booted in to recovery from ADB and got an alert regarding formatting cache.
So to be on safer side I formatted all partition except SD and restored it from my ROM backup.
For past 30 mins my heart was in my mouth and I was already planning to buy Galaxy S3 but I guess Glacier is quite robust and with such a wonderful developer community it has a long way to go.
Thanks for responding.
Click to expand...
Click to collapse
Ok good you fixed it! And you posted how in the response right? It might be helpful to people in the future.

Boot Loop Issue

Hi,
I am having an issue with my phone where the phone keeps on boot looping. I have read the brick guide and I tried the solutions in there but I am still stuck with a boot loop.I managed to install clockwork and cm 7.2 on the phone but it still boot loops and it has the good emmc chip as well. I also flashed the pd15img in hboot it doesn't return any errors and still loops. Any help/direction would be greatly appreciated. Thank you.
Glacier PVT Ship S-Off
HBoot-0.86.0000
Radio -26.03.02.26_M
eMMC-boot

make sure u have the correct .img. I got it from here. Did u make any backups?
try flashing the .img from the link. Follow "I - 4) Downgrading" I used 4b after that. so try that...it will help u get to stock froyo

Me too
trollimammoth said:
Hi,
I am having an issue with my phone where the phone keeps on boot looping. I have read the brick guide and I tried the solutions in there but I am still stuck with a boot loop.I managed to install clockwork and cm 7.2 on the phone but it still boot loops and it has the good emmc chip as well. I also flashed the pd15img in hboot it doesn't return any errors and still loops. Any help/direction would be greatly appreciated. Thank you.
Glacier PVT Ship S-Off
HBoot-0.86.0000
Radio -26.03.02.26_M
eMMC-boot
Click to expand...
Click to collapse
Mine boot loops with just about every ICS rom except (so far) the new chameleon one. It does the thing where if I get an incoming text when I try to check it it restarts the phone, and after a few days it boot loops permanently. What I mean by that is I'll try to use the phone and it's in the rom's splash screen just looping and looping and doesn't stop until I turn off the phone.. So when that happens I have to hold the volume down, turn the phone on, and wait until the boot menu comes up.. Then go into recovery and wipe data, cache, dalvik, and flash a new rom and gapps. It really sucks because I love PACman rom's and they boot loop the most.
Oh also my phone kept not booting once because my back button got stuck down.. So check your buttons too? Hopefully something there helps. I'm still trying to find out why PACman rom's hate me! Good luck!

Everybody please read the op in the developer's roms they all tell you to wipe cache/dalvik this what I do when I install any rom I throws out all the bugs and gets the rom moving normally
Sent from my HTC Glacier using xda app-developers app

that's not it..
aliamin86 said:
Everybody please read the op in the developer's roms they all tell you to wipe cache/dalvik this what I do when I install any rom I throws out all the bugs and gets the rom moving normally
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
That's not it.. I wipe my data, cache, and dalvik cache 3x before flashing a new ROM. I think the problem may have something to do with the kernel the devs are using because both Pacman and evervolv roms do it the worst, and I noticed Pacman is using evervolv's kernel. chameleons ROM doesn't restart or boot loop on me at all..

I had same problem. I installed 4EXT recovery and formatted everything ext 4 +full wipe.Then installed a different kernel other than stock.That solved all issues.
Sent from my HTC Glacier using xda app-developers app

Had success with factory data reset
Hello. I had the boot loop problem and tried everything (even the wierd twisting thing which worked for others, not me). I ended up fixing the problem by using the factory data reset solution. This is done by holding the power and volume up button until the screen lights up with options. Then select the factory data reset option.
THIS WILL WIPE OUT EVERYTHING except whats on your SD card. So you'll have to redownload all your favortie apps. But i actually liked that new phone feeling after the reset. Hope this helps someone.