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!
Related
Was wondering which recovery everyone likes and why. Been using Ra since my G1 and I love it. (searched around for one of these and didnt see it. Mods delete if there was already one of these polls)
Amon all the way
Sent from my EVO using the Earths core to power my death ray
So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.
sablesurfer said:
So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.
Click to expand...
Click to collapse
Thats true. As far as I know, there have been issues with Clockwork not wiping correctly(I know someone like that)and causing bootloops after flashing. I dont know of any roms that dont work with Ra, but I believe Rom Manager will only work with Clockwork.
Clockwork since it is compatible with ROM Manager.
Clockwork since it has a back option in the menus. It's also updated frequently.
I've been running clock on the evo. I tried putting amon in but I guess I'm too stupid cause when I tried following the directions, I borked the phone good and it took me awhile to get everything back into working order. I could flash it now with rom manager but I'm kinda afraid after the last fiasco.
Sent from my PC36100 using XDA App
I've found that using both have worked for me the best. If I'm running Fresh Rom I will use Amon Ra's but I'll use clockwork for cm6. Its so easy to jump back and forth between recoveries using rom manager its never really an issue. Either way both developers are awesome and their recoveries both have good things to offer
anyway to switch back to Amon? not feelin the Clockwork im too use to it...
seriousblack25 said:
anyway to switch back to Amon? not feelin the Clockwork im too use to it...
Click to expand...
Click to collapse
Use ROM Manager to "flash alternate recovery."
another poll
dglowe343 said:
Was wondering which recovery everyone likes and why.
Click to expand...
Click to collapse
i was wondering the same thing exactly!! So a few days ago i asked the question on the Cyanogen forums... I got a lot of good responses and summarized the comments on the first post... check it out here: http://forum.cyanogenmod.com/topic/2562-best-recovery-for-evo-to-use-with-cm6/
I haven't had one single problem with clockwork recovery.
I like the recovery originally included with toastcfl's root found here. it's very similar to Armon's (don't know if things have to be signed or not), but you use the power button to go back instead of the double-press volume (which I find annoying to do).
I just don't like clockwork as much as the other two, that's just the way it is.
Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?
oblivion0 said:
Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?
Click to expand...
Click to collapse
I'm using clockwork with Damage Control I've had zero problems so far.
I hate Amon recovery... always have to move my ROM downloads to the root of the SD card... forget it 90% of the time and have to reboot to fix it... and that doesn't work so well if I borked my ROM.
I use Clockwork and have zero issues unless I'm trying to autoflash theme updates and such so I have to do those manually. Otherwise no complaints. And no signing issues with Clockwork either.
Amon_RA's recovery FTW!
Well, since rooting 24 hours ago, I've been using Clockwork via recovery boot (not through ROM Manager) and it's worked flawlessly so far. Backed up my rooted stock setup, flashed Fresh, DC, CM6, and then back to Fresh, wiped between every flash, and I've had no problems. Even flashed some Fresh Tweaks in the recovery boot. I actually flashed Amon Ra to see how I liked it . . . and I didn't. Mostly just navigating was a pain with the volume up+down thing, everything else seems like a wash. My only question is whether the Dalvik cache is really being wiped by Clockwork, since it takes half a second to complete when I select the option. I'm going to test it in a few minutes here.
Going to give Baked Snack a run for a while, we'll see how that holds up.
I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App
herbthehammer said:
I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Okay, I decided to test. Fired up ADB and booted into recovery from Android. Mounted /data and looked inside /data/dalvik-cache. There was a long list of .dex files. Then I unmounted /data and used the Clockwork menu to wipe the Dalvik-cache (this option is located under the "advanced" menu, NOT just the "wipe cache" option). Re-mounted /data and looked inside . . . and the dalvik-cache directory was gone. It took *slightly* longer than normal when I actually hit the button to wipe it (more like .7 seconds instead of .5), but it does appear that my Clockwork v2.5.0.1 is wiping dalvik just fine. And, of course, when I rebooted back into Android (rooted .6 stock at the moment) it took a long time to boot at the 4G screen, as the cache was being rebuilt. Once I was back in, I checked the /data directory again and dalvik-cache was back and full of .dex files again.
So there. No more speculating, just science.
And if you're ever worried about it, you can just use ADB to wipe the dalvik-cache yourself:
Code:
adb shell
mount /data
rm -rf /data/dalvik-cache/*
Then you can use the Clockwork menu to wipe everything else and flash your ROM. These three commands actually just delete everything inside the dalvik-cache directory, whereas Clockwork appears to remove the directory entirely. Doesn't really matter either way, the system will replace the directory if it gets deleted.
Mmm . . . terminal code.
Apologies for the double post but I'm dying to get my wildfire back working.
Rooted it yesterday with unrevoked, attempted to add the Openfire ROM this morning with everything going fine untill the reboot. I'm now stuck on the white HTC screen and have been for the last hour. Any help would be great, cheers.
did u do nandriod back up first
Sent from my Archos5 using the XDA mobile application powered by Tapatalk
I backed up the stock firmware I already had manually, before it prompted on the flash.
did you do a full wipe before flashing the rom?
No i didn't, thought it would be safer incase something went wrong?
run your restore then I couldn't get it to work either
Sent from my Archos5 using the XDA mobile application powered by Tapatalk
if you did a nandroid backup of your stock rom then you should be fine to wipe, since you did not wipe and flashed the new rom over your stock rom, apps and settings will conflict, therefore not work...
Right I see, I'm currently going through what I'm guessing is the restore....recovery - Nandroid, I'll let you know how I get on.
Thanks again.
Nope I seem to be getting nowhere here, can someone point me in the direction of the restore?
you didn't do nandroid backup did you haha, you'll have to install an RUU file to return to stock rom, or just do a full wipe and flash a new rom like openfire or wildpuzzle.
Where can I find the RUU file and how do I access my SD card? USB won't let me get to it, I'm guessing the phone is in charge mode?
go into recovery - partitons menu - mount sd card (or somthing like that) to open your memory card
Spot on, I'm on downloading an ruu file now, going to load it up with a stock rom then try flashing it again, but wiping it this time.
Infact how do I do a full wipe? I'm after the easiest way to get the phone booting up so I can flash it properly?
Anyone?
I'm still no further than I was three hours ago!
EDIT:
BREAKTHROUGH!!! =D
Restored it to before I flashed it incorrectly. Nearly threw the phone across the room in excitement.
go into clockwork recovery and click the title "wipe data/factory reset" and then flash the ROM you want to use.. to install a ROM:
- "install zip from sdcard"
- "Choose zip from sdcard"
- "click the zipfile"
- "yes"
- "reboot"
and if you want to install RUU dont ask me never done that
Reggie24 said:
Anyone?
I'm still no further than I was three hours ago!
EDIT:
BREAKTHROUGH!!! =D
Restored it to before I flashed it incorrectly. Nearly threw the phone across the room in excitement.
Click to expand...
Click to collapse
How did u restored it .....????
sunny_16977 said:
How did u restored it .....????
Click to expand...
Click to collapse
From the HBOOT screen go to recovery, then nandroid, restore, and to the appropriate time/date.
I've still had no luck with actually flashing the phone though. Back to Android 2.1 for me.
I'm 99% percent sure you have the OC issue some ppl incl myself on here have - try reinstalling openfire if thats what you wanna use - and then go to wildpuzzle thread - dl 0050 and flash it. If i'm correct phone will be fine and use openfire - but will NOT be overclockable. I wish Jacob had my phone or got hold of a phone w that problem...
I had problems with the Wildpuzzle 8.0.11 ROM, it would just sit there (did a ADB logcat on it, but I've lost the actual log... sorry! ) ignoring a duplicate entry (yeah, I did a full wipe . Removed WP and put on the latest OpenFire ROM... omg... what a difference to the stock ROM! Soooo much faster, even before I overclocked it.
I'd say, if you have boot issues with WP give OpenFire a go. Certainly worked a treat on my Wildfire.
This is what I did:
1) Made a backup
2) Wiped cache partition/davlik
3) FLashed CM nightly 111
4) Flashed wildmonks kernel 2.6.38.8
5) Reboot
Everything was fine, the phone booted up. Home was defaulted in landscape for some reason, so I adjusted the settings but everything remained in landscape, so I rebooted. The phone wouldn't reboot though. It stuck in bootloop. I tried to go into CWM to revert to a backup. I could get the main menu of CWM, but any action would just make it hang. So no CWM and am stuck in bootloop (after it originally booted fine!).
Not sure how best to proceed here, or what the problem is. Help! Thanks.
That's not enough info for this thread--we don't know your history
What version CWM? Don't use 3.+
Recommend Amon_Ra 2.2.1
Is this the first time you flashed this rom?
What did you flash it over?
Either way if problems persist:
Wipe system 3X and data/caches 5
If no luck--reformat card with sdformatter outside of phone and rewipe as mentioned above
Also, try a new download--did you check md5?
You can also try an earlier nightly or an RC release
Ken
Also, this is the wrong thread
You will be moved to the Q&A section
And try the CM7 thread in Android Development section
Ken
rugmankc said:
That's not enough info for this thread--we don't know your history
What version CWM? Don't use 3.+
Recommend Amon_Ra 2.2.1
Is this the first time you flashed this rom?
What did you flash it over?
Either way if problems persist:
Wipe system 3X and data/caches 5
If no luck--reformat card with sdformatter outside of phone and rewipe as mentioned above
Also, try a new download--did you check md5?
You can also try an earlier nightly or an RC release
Ken
Click to expand...
Click to collapse
CWM is 3.+.
I was coming from an earlier nightly, 80-something.
I can't wipe or flash because I can't get CWM to do anything. I'll try reformatting card later. Thanks.
Not sure about your bootloop
I usually do the 3 finger:
Hold down pwr/vol-/trackball at same time and it takes me to the bootloader screen with the 3 androids then I can get into recovery. It may take awhile to boot into bootloader screen. So, don't release buttons too soon.
From there I wipe all including system 3 to 5 times and do a nandroid
Ken
Do card as I suggested
Probably too many nightlies in between not to do fresh flash and full wipe
Definetly go back to a pre 3. CWM
I had good luck with 2.5.1.4--can flash it from Rom Manager
rugmankc said:
Not sure about your bootloop
I usually do the 3 finger:
Hold down pwr/vol-/trackball at same time and it takes me to the bootloader screen with the 3 androids then I can get into recovery. It may take awhile to boot into bootloader screen. So, don't release buttons too soon.
From there I wipe all including system 3 to 5 times and do a nandroid
Ken
Click to expand...
Click to collapse
I can get into bootloader fine. CWM is just unresponsive. Trying to format SD right now. Thanks for the input!
rugmankc said:
Do card as I suggested
Probably too many nightlies in between not to do fresh flash and full wipe
Definetly go back to a pre 3. CWM
I had good luck with 2.5.1.4--can flash it from Rom Manager
Click to expand...
Click to collapse
Re-formatting SD card didn't accomplish anything. Think I'll try next to re-flash a recovery (Amon-RA) via fastboot and see what happens. Ack.
Good idea--I didn't know if you had fastboot setup--so didn't mention it
rugmankc said:
Good idea--I didn't know if you had fastboot setup--so didn't mention it
Click to expand...
Click to collapse
Didn't have fastboot set up, but once I could shake the family I threw myself in. I only used fastboot once before, a year and a half ago when I unlocked and rooted my phone.
Anyhow, re-flashing a recovery image did the trick. Then I was able to restore a nandroid backup and move on from there. Not sure why the universe went awry, but hey, live and learn. Always backup kids.
Glad you got it.
Used ROM Manager and downloaded Leedriod 3.0, ran Terminal Emulator and did everything by the book. Went into ClockWork Recovery mode and everything looked okay. Then went to HTC boot animation screen and that's where it has been ever since. Every five minutes or so I get the delightful sound of HTC and a permanently on HTC, Quietly Brilliant Boot screen. It's been going like that for about 25 minutes now.
Any help would be appreciated.
No its not bricked, its in bootloop.
This is what i do when it happens to me:
Pull out the battery. If the phone is off, turn it back on with volume down + power on button. Wait till you get the bootloader screen. Now select recovery. In ClockWork Recovery you can set your backup back. (if you had made one before).
I hope its helps you. Goodluck.
Or just copy another rom file to the sd card and flash again.
Unfortunately I made the classic error of not backing up first, was trying to do this while in work (not good) so I presume at this point I'm screwed
joooe said:
Or just copy another rom file to the sd card and flash again.
Click to expand...
Click to collapse
Thanks, will try that tonight.
It doesn't hurt to try to flash the rom you already have once again.
Just what joooe said. Use super wipe to clear data. just for sure.
Good luck.
Sent from my Desire HD using XDA Premium App
Just a quick thanks to you guys, did Super Wipe and installed Android Revolution 6.20 last night and all went well. It was worth the screw up to have the small learning curve in the end
I did this one of the first times i flashed roms
i did have abackup first but its a scary experience lol
Hi, I used the paid version of ClockWorkMod Recovery to backup, then download the 'Cyclonic Rom'. Well, it rebooted to a 'Cyclonic Rom' startup screen (animated lettering) - but that's it. I'm wary to unplug the battery if it's actually flashing, but this has been going on for 20 minutes or more. Can I pull the battery and see what happens? How long does a new ROM take to install, this is my first one. Thanks.
BTW: These CAPTHCA's are getting tough! This will be the 4th try!
fixed it
I unplugged the battery and did a factory reset/format in ClockWorkMod. I rebooted and all seems well so far.
20 minutes is a looong time for Cyclonic to boot. Is it still working ok? As far as CW goes, I only use Rom Manager to downlod what I want/need. When it comes to flashing I wipe everything manually and flash from recovery. I don't trust the app. But thats me.
Sent from my PG06100 using xda premium
+1 to that. I always use the same Method for Flashing Roms ( The one linked in my Sig ) . Clear everything Manually. I try to never deviate from that. Reason being, after Flashing literally hundreds of times I've found it to be the most reliable way to Flash a Rom. Meaning the least amount of possibilities for issues later on down the road .
alarmpro said:
Hi, I used the paid version of ClockWorkMod Recovery to backup, then download the 'Cyclonic Rom'. Well, it rebooted to a 'Cyclonic Rom' startup screen (animated lettering) - but that's it. I'm wary to unplug the battery if it's actually flashing, but this has been going on for 20 minutes or more. Can I pull the battery and see what happens? How long does a new ROM take to install, this is my first one. Thanks.
BTW: These CAPTHCA's are getting tough! This will be the 4th try!
Click to expand...
Click to collapse
Flash newsense.
And don't forget to wipe dalvik.
I have been searching (as in using the 'search' function) for a solution or answer to this, but couldn't find anything. This seemed to be the best thread to dig up instead of starting a new one.
Within Clockworkmod, whenever I try to go into recovery (either trying to 'reboot into recovery' or installing a ROM from SD card), it always throws me into Android System Recovery 3e instead of CWM recovery. Of course the stock recovery doesn't recognize my downloaded ROM.
I've also noticed that trying to update a ROM in HBOOT via a new PG06IMG.zip file on SD root is not working, except to wipe all my system and apps data, and then returning me back to rooted 2.2. HBOOT seems to read the new zip file fine, but when I reboot nothing has changed.
I've read wiki and lots of other stuff, but I can't seem to find an answer except that MAYBE that I need a new kernel first??? Okay, let the flaming begin.
jdjohn said:
I have been searching (as in using the 'search' function) for a solution or answer to this, but couldn't find anything. This seemed to be the best thread to dig up instead of starting a new one.
Within Clockworkmod, whenever I try to go into recovery (either trying to 'reboot into recovery' or installing a ROM from SD card), it always throws me into Android System Recovery 3e instead of CWM recovery. Of course the stock recovery doesn't recognize my downloaded ROM.
I've also noticed that trying to update a ROM in HBOOT via a new PG06IMG.zip file on SD root is not working, except to wipe all my system and apps data, and then returning me back to rooted 2.2. HBOOT seems to read the new zip file fine, but when I reboot nothing has changed.
I've read wiki and lots of other stuff, but I can't seem to find an answer except that MAYBE that I need a new kernel first??? Okay, let the flaming begin.
Click to expand...
Click to collapse
You need to flash recovery first, it is the first option in ROM Manager. You can't update a ROM with PG06IMG.zip, nor can you do it in the bootloader. Flash the recovery, wipe everything (data, cache, dalvik cache, system, sd-ext) then flash a ROM.
Did you get this sorted?
bilgerryan said:
You need to flash recovery first, it is the first option in ROM Manager. You can't update a ROM with PG06IMG.zip, nor can you do it in the bootloader. Flash the recovery, wipe everything (data, cache, dalvik cache, system, sd-ext) then flash a ROM.
Click to expand...
Click to collapse
Chad The Pathfinder said:
Did you get this sorted?
Click to expand...
Click to collapse
No, still having trouble. I have flashed ClockworkMod Recovery (version 5.0.2.0) in the ROM Manager app, but when I 'reboot into recovery' within the app, it goes to the Android System Recovery. I'm also confused about the 'apply sdcard:update.zip' option in ASR...seems like that would update something if the file was set up properly.
I guess I need to search for a tutorial on how ASR and HBOOT work. Sorry to bother you guys with the basics.
Try this onehttp://forum.xda-developers.com/showthread.php?t=1663531
bilgerryan said:
Try this onehttp://forum.xda-developers.com/showthread.php?t=1663531
Click to expand...
Click to collapse
Will check it out, thanks! I'm leaving town today, so not sure if I will be able to experiment before I go, but I will not give up!
The only thing I use Rom Manager for is to get the recovery. The way I go into recovery is to turn my shift completely off (do a battery pull to make sure its completely off) then hold the volume down and power buttons at the same time until the bootloader screen comes on. (While there see if it says S-off near the top) then using the volume buttons highlight the recovery option and push the power button. Then when you're there use the volume buttons to navigate through the various fields and hit enter to select. I hope this is helpful to you. Good luck!
Edit: by the way, when you first get to the bootloader screen, it will automaticly do a check showing a few green lines. Thats ok. Just wait until its finnished then go into recovery the way I stated.
jdjohn said:
Will check it out, thanks! I'm leaving town today, so not sure if I will be able to experiment before I go, but I will not give up!
Click to expand...
Click to collapse
How did you root? It seems as if you have a locked bootloader and/or S-ON if the custom recovery is not taking
Sent from my PG06100 using xda premium
CNexus said:
How did you root? It seems as if you have a locked bootloader and/or S-ON if the custom recovery is not taking
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
jdjohn said:
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
Click to expand...
Click to collapse
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
bilgerryan said:
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
Click to expand...
Click to collapse
Was thinking that myself. Will have to wait til I get back, though...headed out of town. Thanks guys!
jdjohn said:
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
Click to expand...
Click to collapse
Hmm, never mind then, it seemed as if your bootloader was still locked if the recovery wouldnt flash
bilgerryan said:
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
Click to expand...
Click to collapse
Yeah, just do what bilgerryan said (make sure that you download the one that says "flash through bootloader" or something along those lines)
Before flashing, download some md5sum tool and make sure it matches the one given on there
Sent from my PG06100 using xda premium
Finally got back to this and was able to install and use Dread's CW-Enhanced. So far I have only flashed the Speedy Rooted OTA 2.77.651.8 (bascially 2.3.4 rooted). GB had some features I was wanting, but missing, after rooting back to Froyo.
But before continuing on to other ROMs, I was wondering how you guys handle restoring basic apps and data each time you flash a new ROM. Or, do you only use extra play phones for new ROMs and not your daily user? It would seem that every time you flash, you need to restore SuperUser, Titanium, ROM Manager (ClockworkMod, then probably Dread's enhanced image file), Terminal Emulator, etc. And of course contacts and messaging history and other stuff like that.
So far, after flashing a ROM, I usually download Titanium (or MyBackup) and restore apps and data from backups before continuing. Do you just keep certain APK files on your SD card and install from ADB instead of re-downloading from Google Play Store each time?
I flash ROMs on my dd. Usually when I falsh a new ROM (not a nandroid) I fresh install my apps through the play store. Especially if switching between GB, ICS and JB! Some apps work well if carried over by tb but not all. You'll just have to experiment to see what works with your shift and what doesn't.
Also, the recovery only ever needs to be flashed once
What I used to do is backup my current rom with all my data and settings and then wipe + flash a new rom. If i liked it, then I would move my full box of apps and data to the new rom, but restoring data can go wonky so I always made a backup before doing that too. If i didnt like it, I would either restore my original backup for a bit or keep flashing new roms until I either found one I liked or got tired and restored my backup lol