Database Users

Flash problems

OK I have a problem. I had a difficult time flashing to DI18, figured out it was the pc not installing all the drives. Got there, went to backed snack 1.6 without a problem. I try anything else and I get the same error no matter what I wipe or anything.. tried DJ29 and DK05 and a few of the custom roms based n those 2 and I end up with can't symlink system/bin/dumpcrash, error at line 6..
I flashed DI18 with odin, fresh, didn't install any apps or sync with google, and same thing when I clockwork.. rom manager won't boot into clockwork, only android.. Is it me? Am I doing something wrong? I read someone flashed DJ29 or a DK05 rom over baked snack and I can't seem to find a solution.
Any help is appreciated.. I can't find any topics or posts that offer help or guidance in what to do with errors..
Sent from my SPH-D700 using Tapatalk

I had that same sot of problem. Rooted the epic flashed clockwork and woudnt boot in to the proper recovery. So here is what I did: with any file manager go onto your sd card and delete the update zip from the sd root directory. Then go into rom manager and reflash clockwork. Then manually boot into recovery by holding down volume down, power, and camera button. This should get you into clockwork recovery.
Sent from my SPH-D700 using XDA App

OK I tried but rom manager wont boot into any recovery now. I still have to boot in manually.. Not a problem, but I tbought booting from RM would be better for installing the .zip. gonna change the battery and try flashing but I am more concerned with how to flash any DJ29 or DK05 rom cuz I haven't been able to no matter what.
Sent from my SPH-D700 using Tapatalk

Sent from my SPH-D700 using XDA App

Tried it and same symlink error, should I rename to update.zip?
Sent from my SPH-D700 using Tapatalk

Sloopjoshb said:
I had that same sot of problem. Rooted the epic flashed clockwork and woudnt boot in to the proper recovery. So here is what I did: with any file manager go onto your sd card and delete the update zip from the sd root directory. Then go into rom manager and reflash clockwork. Then manually boot into recovery by holding down volume down, power, and camera button. This should get you into clockwork recovery.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Exactly. You HAVE to go to Clockwork from the 3 button boot. STOP using Rom manager.

Elazgar said:
Tried it and same symlink error, should I rename to update.zip?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
If you are actually in Clockwork via the 3 button boot (green text) and you can't install a zip, any zip as that is an option to actually choose the zip no mater what the name. THEN you need to re-root the phone
http://forum.xda-developers.com/showthread.php?t=770388
and re-install Clockwork
http://forum.xda-developers.com/showthread.php?t=782300
Also, this is a general topic that should be in the General forum, not in the development section as you aren't developing anything in this thread.

Ok thanks, wasn't sure where it belonged.. I have installed baked snack 1.6 and I can keep doing it no matter what I do, I don't even need to wipe. But anything else won't install. Root is there, I use apps that need it and the only one that has given me problems is root manager about su and not etting permission even though it has permission, so I will removethe permissions and see what happens.
Thanks a lot for the help, it's highly appreciated.
Sent from my SPH-D700 using Tapatalk

I *CANNOT* boot into ClockWork recovery!

I am on a rooted Samsung Vibrant running Froyo and CWM 2.5.1.2. I cannot boot into CWM's recovery. I tried flashing CWM again and again, but I didn't work. I tried reinstalling packages at least 5 times and nothing. I just boot into the normal recovery. It worked the very first time I tried it, right after I rooted it and I installed CWM for the first time, then I had to reinstall packages twice. I used super-one-click to root my phone. I am using the latest version of busybox. I have given ROM Manager superuser access. I reinstalled ROM Managed. I deleted the clockworkmod folder and update.zip and installed CWM again. I have tried re-rooting twice with no success. What's the problem? It worked the very first time I rooted. But why not now?

I have this happen from time to time with ROM Manager....I just go clear down to the bottom and install an older version...say 2.5.1.1, hit reboot into recovery and it does, and then I update back to 2.5.1.2 and it will work after that on the newer version

jmcghee1973 said:
I have this happen from time to time with ROM Manager....I just go clear down to the bottom and install an older version...say 2.5.1.1, hit reboot into recovery and it does, and then I update back to 2.5.1.2 and it will work after that on the newer version
Click to expand...
Click to collapse
Sorry, that didn't work.

Opps didnt see the Froyo..you need a modded 3e recovery here http://forum.xda-developers.com/showthread.php?t=833423

Yea you have to use the "froyo" version, but you will also need to delete slacker radio from your phone via titanium first. That is the only way it would work for me.

jmcghee1973 said:
Opps didnt see the Froyo..you need a modded 3e recovery here http://forum.xda-developers.com/showthread.php?t=833423
Click to expand...
Click to collapse
Sorry, that didn't work either. Should I just restore to the stock 2.2 on my Vibrant? If so, where would I get the Stock 2.2 Vibrant files?

How do you feel abt voodoo?? You can install one of Supercurios kernels with voodoo and it will give you CWM recovery and root

jmcghee1973 said:
How do you feel abt voodoo?? You can install one of Supercurios kernels with voodoo and it will give you CWM recovery and root
Click to expand...
Click to collapse
Damn...Im still half asleep.....I re-read your post...the update.zip has to stay on your internal sd... I saw you deleted it which is why CWM isn't working. ROM Manager adds to that file when installing CWM Recovery.

jmcghee1973 said:
Damn...Im still half asleep.....I re-read your post...the update.zip has to stay on your internal sd... I saw you deleted it which is why CWM isn't working. ROM Manager adds to that file when installing CWM Recovery.
Click to expand...
Click to collapse
It is in my internal SD. It's at /update.zip It added that every time I downloaded CWM. Should I Odin back to the stock 2.2?

You can.. that way you start out fresh and eliminate the chances for errors

jmcghee1973 said:
You can.. that way you start out fresh and eliminate the chances for errors
Click to expand...
Click to collapse
Sorry, I'm a noob to the Android scene, How would I restore to Stock 2.2 for Vibrant? Is there a guide or tutorial?

http://forum.xda-developers.com/showthread.php?t=848737

When you ran the script to get the recovery to 2e, did you put the phone into shell root first using super one click?
Guide: http://forum.xda-developers.com/showthread.php?t=925400

I am having the EXACT SAME PROBLEM AS THIS GUY. And it's really frustrating, I have been working at getting this ****ing phone updated to some version of 2.2 for about 5 hours now.
Just had to say that.

you on 2.1?

UPDATE:
I flashed 2.1.1.0 clockwork... whichever one was at the bottom of the list. AND I uninstalled Slacker Radio (dont know if that helped it for sure)
But After reinstalling the packages, then booting to recovery with the volume buttons down, I reinstalled package AGAIN and then CLOCKWORK INSTALLED OR WHATEVER! So now I'm flashing a new rom from it! thanks!

checktheemails said:
UPDATE:
I flashed 2.1.1.0 clockwork... whichever one was at the bottom of the list. AND I uninstalled Slacker Radio (dont know if that helped it for sure)
But After reinstalling the packages, then booting to recovery with the volume buttons down, I reinstalled package AGAIN and then CLOCKWORK INSTALLED OR WHATEVER! So now I'm flashing a new rom from it! thanks!
Click to expand...
Click to collapse
I ve had to downgrade ROM manager before also...so you might be ok to move back to 2.5.1.1 after your flash

Also, earlier today I did this: http://forum.xda-developers.com/showthread.php?t=804305
So that may be part of his issue.
Clockwork seems to be hanging on installing my ROM right now...
is it normal for the progress bar to not move once it hits "Formatting DATA:..." ?

yea as long as it keeps saying Formatting, Copying, deleting...it will move if it flashes good..

checktheemails said:
Also, earlier today I did this: http://forum.xda-developers.com/showthread.php?t=804305
So that may be part of his issue.
Clockwork seems to be hanging on installing my ROM right now...
is it normal for the progress bar to not move once it hits "Formatting DATA:..." ?
Click to expand...
Click to collapse
When you did this where you on 2.2 (kA6) or 2.1 (JI6)?
im asking because im on 2.2 but for the life of me i havent been able to get clockwork to run. ive done almost every single step there is out there and have had no luck, but im thinking that my phone is HW locked so that may be my problem.
i can flash any stock rom through odin (JFD) (JI6)
and (KA6) through kies mini
but i cant get into clockwork recovery in any of those rom's.

CWM Problems

UPDATE: To fix 3.0.2.4 from not formatting /system
Open rom manager and select settings, and check erase recovery. hit menu again and select clear cache, then flash 3.0.2.4 again.
now if your in recovery and you cant boot back up to use rom manager, use the file below. It will allow you to restore your backup then once booted back up use the method above to fix 3.0.2.4.
The reason im leaving custom over 3.0.2.4 is bc i know fastboot flash with this one will allow you to restore without wiping recovery or clear cache or anything else.
http://www.mediafire.com/file/b8ejhqbf3tgnsoe/recovery.img - this is CMW 3.0.1.4 just altered for installing zips. linking for people needing a recover img to boot up
To install:
1. If in recovery, open ur terminal on ur pc and type adb reboot boatloader
2. Once in bootloader it will load fast boot and say fastboot usb in red
3. cd to the folder with fastboot.exe and also place recover.img in that folder
4. then enter fastboot flash recovery recovery.img
5. adb reboot recovery
6. restore your backup and boot up

RafficaX said:
Little FYI for all, cwm recovery wont format system on a restore. made a backup, tried a flash and went to restore and it fails formatting system.
So be careful with flashing and all bc yo may not be able to restore currently with cwm.
UPDATE: format system in menu also fails! be careful bc you pretty much cant restore or flash atm!
Click to expand...
Click to collapse
Oh how I miss Amon_Ra

jlevy73 said:
Oh how I miss Amon_Ra
Click to expand...
Click to collapse
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.

RafficaX said:
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
Click to expand...
Click to collapse
QFT
can't wait for amon-ra

raffica, what version of CWM worked for you?

MYxdaUSERNAME said:
raffica, what version of CWM worked for you?
Click to expand...
Click to collapse
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.

Thanks for the heads up I agree I always loved CWM on my N1 but it started giving me all kinds of grief for several different reasons so I finally went to Amon Ra.

RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
Can you help me out and provide it because right now i cant even boot

RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes

superchilpil said:
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
Click to expand...
Click to collapse
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...

nosympathy said:
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
Click to expand...
Click to collapse
See that's what I thought, but wasn't sure
Sent from my ADR6300 using XDA Premium App

Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.

jgrimberg1979 said:
Can you help me out and provide it because right now i cant even boot
Click to expand...
Click to collapse
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically and I followed the steps from 7 on to regain root. Worked for me, but now I have to start over. Hopefully they will get CWM working again. I will be much more careful about what I delete from now on. I think I will freeze it in TiBackup first to make sure everything is still working correctly. Hope this helps.

lynseyw said:
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically
Click to expand...
Click to collapse
This is the exact procedure I used when the same thing happened on my N1

i added the recovery.img i used to OP with instructions for those stuck in recovery or bootloader.

jeffnucci said:
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
Click to expand...
Click to collapse
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App

miketoasty said:
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.

My battery died and am in the same position. Got an expensive paperweight at the moment. I'll try to get another battery today and give this a try. After fooling around with it last night, the computer wouldn't even recognize the phone. Ughh!

RafficaX said:
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
Click to expand...
Click to collapse
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App

miketoasty said:
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Where did you get 3.2? 3.0.2 you mean?

Why is cwr 3.0.0.6 not persistent?

I have installed it while in '0.5, and when I go back in, its always gone. Has rom manager been updated for this? Because I think that's they problem. I choose CWR from within rom manager (which is .0.5), and when it reboots I am back in 0.5.
Just wondering if there was an update or a fix/patch I missed.
Sent from my HTC Glacier using XDA App

I don't know what you are doing, so I will just tell you what I have done.
1) Download 3.0.0.6 and save to sd.
2) Flash 3.0.0.5 from within rom manager.
3) reboot into recovery 3.0.0.5.
4) Flash 3.0.0.6 file
5) reboot until rom loaded
6) Once rom loaded reboot again into recovery and should be 3.0.0.6 (do not reflash 3.0.0.5 again, otherwise will see 3.0.0.5 in recovery again)
If that doesn't work, I don't know what to tell you except to use adb.
Sent from my HTC Glacier using XDA App

syntropic said:
I have installed it while in '0.5, and when I go back in, its always gone. Has rom manager been updated for this? Because I think that's they problem. I choose CWR from within rom manager (which is .0.5), and when it reboots I am back in 0.5.
Just wondering if there was an update or a fix/patch I missed.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Sometimes when you flash a new ROM, CWM 3.0.0.6 doesn't stick. When that happens, just downlaod and install a clean CWM recovery file again from here (http://forum.xda-developers.com/showthread.php?t=944681) and follow instructions and 3.0.0.6 should stick.

syntropic said:
I have installed it while in '0.5, and when I go back in, its always gone. Has rom manager been updated for this? Because I think that's they problem. I choose CWR from within rom manager (which is .0.5), and when it reboots I am back in 0.5.
Just wondering if there was an update or a fix/patch I missed.
Click to expand...
Click to collapse
I'm not sure what the other posters mean when they say CWM doesn't "stick". The problem is that 3.0.0.6 is not an officially supported version, and therefore even when it's installed, ROM Manager will continue to say you have 2.5 or 3.0.0.5 installed. Once you've successfully installed 3.0.0.6, don't worry what ROM Manager says about versions. Just boot into recovery and you'll see that 3.0.0.6 is there.

I flashed once and its been there ever since. I dont see y its resetting
Sent from my HTC Glacier using XDA Premium App

charlieb620 said:
I flashed once and its been there ever since. I dont see y its resetting
Click to expand...
Click to collapse
It's not resetting. He just thinks it is since 3.0.0.5 is the latest version supported by ROM Manager.

TeeJay3800 said:
It's not resetting. He just thinks it is since 3.0.0.5 is the latest version supported by ROM Manager.
Click to expand...
Click to collapse
I actually realize that Rom manager merely says 3.0.0.5 and 0.6 is actually "installed". The problem is it doesn't "stick". Even if I boot from recovery not using rom manager, 0.5 is always still there. I am going to download it again and see what happens.
Thx!
Sent from my HTC Glacier using XDA App

Just an FYI for any who had any problems.
Originally, the file I had a link to (and downloaded) was something like clockworkmod-recovery-3.0.0.6.zip (or similar). This apparently is a one shot flash to put you into the 3.0.0.6 recovery while you are already in the 3.0.0.5 recovery. The file that I just downloaded (given above in this thread) actually creates a permanent 0.6 recovery. Just install the file from 0.5 recovery, reboot, and then flash clockworkmod recovery from within rom manager.
At that point, whenever you boot into recovery from RM, it be 3.0.0.6. NOTE: RM will continue to say that you have 3.0.0.5 installed, so ignore that.... 0.6 will be installed.
Sent from my HTC Glacier using XDA App

based on your original post (unless I'm miss reading it) you are flashing the zip file from within recovery, when phone reboots you are going into ROM Manager and flashing CWR which shows as 3.0.0.5 if you use the method in the link "NeverAlwaysEver" posted 3.0.0.6 over writes 3.0.0.5 so it should stick... however I did notice after flashing the newest version of 3.0.0.6 (the one that keeps phone from booting into recovery if plugged in while off) if I selected 3.0.0.5 in ROM Manager it would flash back to 3.0.0.5, I don't know why but that is the only one I have had the same problem you laid out.

One thing I realize is all the posts about these topics can be confusing because it is not always clear whether a poster is starting that they "flashed" cwr, ot merely booted into cwr.
But my problem was solved when I flashed/installed the file from the link by NeverAlwaysEver above when I was in CWR (3.0.0.5). This file is a substitute file which RM uses to flash to a new recovery. So when you flash again from within RM, you are "installing" the 3.0.0.6 recovery. I didn't write RM, so I do not know why it doesn't recognize that 3.0.0.6 is installed and report this as the actual version after you do this, but its a minor issue.
I dint know what zip version you are referring to other than the one in this thread and the "one-shot" one I had (which I got from SoltyPK in some post), but the later one could have utility if you need more than 2 recovery versions (e.g., if for some reason you wanted to have the ability to use the stock recovery (2.5.1.7), cwr 3.0.0.5, and cwr 3.0.0.6., the last one you actually install while in 3.0.0.5, and it thereupon immediately puts you into 3.0.0.6.
Sent from my HTC Glacier using XDA App

syntropic said:
Just an FYI for any who had any problems.
Originally, the file I had a link to (and downloaded) was something like clockworkmod-recovery-3.0.0.6.zip (or similar). This apparently is a one shot flash to put you into the 3.0.0.6 recovery while you are already in the 3.0.0.5 recovery. The file that I just downloaded (given above in this thread) actually creates a permanent 0.6 recovery. Just install the file from 0.5 recovery, reboot, and then flash clockworkmod recovery from within rom manager.
At that point, whenever you boot into recovery from RM, it be 3.0.0.6. NOTE: RM will continue to say that you have 3.0.0.5 installed, so ignore that.... 0.6 will be installed.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Good to know you have it straighten out now hehe I wouldn't mind if you hit thanks button

RavenWulf said:
based on your original post (unless I'm miss reading it) you are flashing the zip file from within recovery, when phone reboots you are going into ROM Manager and flashing CWR which shows as 3.0.0.5 if you use the method in the link "NeverAlwaysEver" posted 3.0.0.6 over writes 3.0.0.5 so it should stick... however I did notice after flashing the newest version of 3.0.0.6 (the one that keeps phone from booting into recovery if plugged in while off) if I selected 3.0.0.5 in ROM Manager it would flash back to 3.0.0.5, I don't know why but that is the only one I have had the same problem you laid out.
Click to expand...
Click to collapse
If you mean CWM 3.0.0.6 off mode charging from this thread (http://forum.xda-developers.com/showthread.php?t=1014554), it says that one is modified from the original CWM 3.0.0.6 and not the newest CWM 3.0.0.6 that TrueBlue_Drew posted (link I gave in previous post). I haven't tried that off mode charging CWM modified from original CWM .6 but maybe that is the reason why it goes back to .5.

Ra recovery?

I used rom manager to flash Ra recovery 2.3 and when I booted into recovery, it's still clockwork... any help?
Evo 4G
Cyanogenmod 7

you'll want to do it threw the bootloader...run the update once its found and your have ra recovery

I flashed ra through Rom manager fine
Sent from my PC36100 using XDA App

What do I name It to flash through bootloader
Evo 4G
Cyanogenmod 7

I put the zip file and install it automatic with bootloader, very easy.

http://goo-inside.me/amon_ra/supersonic/PC36IMG.zip
Drop that file on your sdcard, don't rename it or anything, and just boot into the bootloader. It'll ask if you want to apply the update, so pick yes. Ta-da!

did you follow the instructions for flashing Amon or are you trying to do it thru the software. Best bet is to do it thru bootloader like suggested

n8te_1 said:
you'll want to do it threw the bootloader...run the update once its found and your have ra recovery
Click to expand...
Click to collapse
Did sloth write this?

Blameme said:
I used rom manager to flash Ra recovery 2.3 and when I booted into recovery, it's still clockwork... any help?
Evo 4G
Cyanogenmod 7
Click to expand...
Click to collapse
Make sure rom manager is up to date. A recent version had this problem.
Sent from my PC36100 using XDA Premium App

Put this file on the root of your SD card....
Hold Power button and down volume, Bootloader will autodetect and ask if you want to apply the update. Say yes, then reboot into recovery.
You should have a good copy of AMON RA 2.3 BTW...the screen tears are normal.