hey guys im having a big and really annoying problem i cant fix hopin in can get some help...
i have the iced glacier 1.1.6 with clockwork 3.0.0.5(rom managerv3.0.1.0). i want to make a backup nanDroid.. so i do and it completes and everythings fine... until i to the restoring part. after it "successfully" restores(yes, i did wipe cache, wipe dalvik, and even wiped eveything in everyorder possible. i restart my phone and it freezes on the mytouch 4g bootup logo. everytime. no matter what. it does let me reinstall the fresh ice glacier rom...
note: when i wipe the dalvik, its almost instantaneous wipe, like it doesnt do it?
there is an error about e:/ not mounted (sd-ext) or something close to that. but still says it worked.
things ive tried...
renaming the file.
moved the file.
reformatted SD.
wipe data...etc twice in a row to make sure it wiped.
any ideas?
You have to revert back to older Recovery 2.5.1.2 or you can install the new 3.0.0.6 as normal CWM won't able to handle it. This same issue has been covered many times. Read the quote below to better understand if you still have problem well then post back ill help.
jggimi said:
you are using the wrong version of Recovery to install the new kernel. I'm guessing #2, because it's very common for people to assume a higher number is better, and use CWM Recovery 3.0.0.5 with Froyo-based ROMs and hose things up really well.
Restoration options, if you are using CWM 3.0.0.5:
a) Restore from the Nandroid backup you made before overlaying your kernel. Oh, yeah, you can't, you didn't make one, otherwise you'd have already done that and wouldn't have posted....
b) Flash the appropriate CWM Recovery (2.5.1.2 for Froyo-based ROMs) using adb from your PC. Reboot into it, find the kernel you wanted to use, and reinstall it.
c) Install a Gingerbread-based ROM, such as CM7.
Pick a,b, or c. If you have any specific questions, please ask.
Click to expand...
Click to collapse
i did the 2.5.1.2 first but it didnt work so i thought id try the newest one...but 3.0.0.6? where do i get 3.0.0.6? its not in rom manager. ( i really hate rom manager it never works for me...) and ive never done adb? or anything on my pc. everything ive done is on my phone...
drpepper4lf said:
i did the 2.5.1.2 first but it didnt work so i thought id try the newest one...but 3.0.0.6? where do i get 3.0.0.6? its not in rom manager. ( i really hate rom manager it never works for me...) and ive never done adb? or anything on my pc. everything ive done is on my phone...
Click to expand...
Click to collapse
Sorry I was asleep but if you still looking for the solution.
http://forum.xda-developers.com/showthread.php?t=952433
Go to option's thread and follow his instructions on howto install 3.0.0.6 as it works also.
This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!
Ive got the following on the HBOOT screen
GLACIER PVT ENG S-OFF
HBOOT=0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Clockwork v3.0.0.6 (using this method http://forum.xda-dev...ad.php?t=944681 )
Okay so with that for reference, I'd like to find out why I can't flash CM7 without the blue Andy bootloop. I understand that a fresh install takes time to load, I gave it 30mins before a battery pull, I then returned the battery, hit the top power button and let that sit for another 20. Before I flashed the ROM (through recovery) I made the following wipes in this order; wipe data/factory reset and then wipe cache partition. I've flashed other ROMs that have flashed without issue (Ice Glacier 1.1.6 themed and Royal MIUI) but, lets face it CM owns. Any help would be appreciated. Thank you for reading this.
DHSdrone said:
Lets face it CM owns.
Click to expand...
Click to collapse
No, Sense owns.
With that out of the way, the only thing I can think of is a corrupt download. Try re-downloading the zip to your PC and copying it to your SD. My other thought was a bad recovery, but since you've successfully flashed other ROMs, that doesn't seem likely.
you didn't wipe dalvik in advanced, do that and bootloop will stop...
darinmc said:
you didn't wipe dalvik in advanced, do that and bootloop will stop...
Click to expand...
Click to collapse
Little known fact, if you wipe data, you already wiped dalvik.
option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Mmmhmm, the only thing it could be is bad download or some other mysterious gremlin lol
Sent from my HTC Glacier using XDA Premium App
option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Well then I retract my statement...
when you say bad or corrupted download I assume your talking about the recovery. I thought the same as well, Ive tried both versions of what was posted as the correct, best, and or easiest method of clockworkmod recovery. Im not sure if both versions were in fact the same recovery.img but they both worked for the roms Ive flashed except for cm (nightly 29, cm7-rc2, rc3,and rc4). The fact tjat I cant get this to work, only makes me want it more.
DHSdrone said:
when you say bad or corrupted download I assume your talking about the recovery.
Click to expand...
Click to collapse
No, I mean the CM7 download. The actual ZIP file that you flash.
As far as recovery versions, only 3.0.0.5 and 3.0.0.6 can flash CM7.
Ive tried flashing several different versions of cm7, starting with rc-2 through rom manager. When that gave me my first boot loop I went back to the method I was more familiar with. With trying the different versions I don't see how they were all currupt or broken downloads. I haven't tried any of the cm froyo roms yet.
As far as my earlier statement of "cm owns" I mean no disrespect of any of the other rom developers (including those that did work properly the first time). Ive just came from the G1 and cm is the only rom I ran. Sense may be the best way to go, it's not something Ive given much consideration or time.
I have had the same issue except mine seems to be all 2.3 (Gingerbread) based roms, they all go to bootloop. I have no problem however flashing any of the 2.2 based roms. I also have cwm 3.0.0.6
I had the same issue everytime with different nightly releases. After wiping everything and formatting boot and system still would do it. I found if you wipe then install cm7 only the phone boots fine then reboot setup wifi if your using it the go back into recovery install gapps and it works fine.
Sent from Teh retardarded duc using XDA Premium App
Im unable to get a full boot. After reading several similar sorties I've always turned off all wireless radios. Will post a logcat later today.
Ok so was able to get mine to Boot completely Finally!!! I am somewhat of anoob so sorry if it seems confusing.
1.From recovery wipe data/ factory
2. Wipe cache
3.Advanced > wipe dalvik
4.Mounts>format boot
5.Mounts>format system
6.Advanced> partion SD card (I believe I used 256) No swap partition(dont know if it matters)
7.Mount USB and transfer cm7 and Gapps
8.Flashed cm7 only not apps.
9.Reboot phone (should boot all the way up)
10.Go back to recovery and flash Gapps
11.Reboot phone
My phone booted up very quickly. I hope this helps anyone else out there with the same issue
no more loop da loops
After searching google, and then to various forums, and finally giving up and posting to 2 separate forums, Ive come to say THANK YOU !!! You are all evil geniuses of the highest degree and I bask in your greatness. Ive been overlooking one thing, that is the "if things go bad, try the sd-card format" well I did and it worked. Now that the derp has left my head, and the panic has subsided I can see now that my problem was in fact like many others, and the answers were right in front of me. Again thanks for being patient and coming together as a community to help me out.
My phone died and when I plug it in and it goes into clockworkmod I hit reboot system now. Then it will start to boot, show my main screen and bang it bootloops, I tried doing a full reset, installed a different CM7 rom and it still does it. Can you guys give me some advice? I have no idea what would've happened.
can you guys plz help I really need my phone
AriaUSer_ said:
can you guys plz help I really need my phone
Click to expand...
Click to collapse
Since you are dead in the water you might as well try these steps:
1. Format the system, data & cache partitions of your device. This is done from CWM using the Partitions menu.
2. Perform a factory reset.
3. Flash CyanogenMod.
Ok to anyone that has a problem like this, this is how I fixed it.
1) Plug in usb charger to your computer, go on to recovery and mount to usb storage.
2) Then go onto here and download a rom (I downloaded attn1's liberated rom)
3) Then factory reset
4) Reboot and then reinstall your CM7 rom and put in gapps.
This is what I did and somehow it worked, no idea why it didn't do anything when I just factory resetted and rebooted the phone, but installing any other rom and then install the CM7 rom it works.
Hope this helped!