Related
Hi guys,
This is probably a dumb question, but can someone point me to a tutorial on how to back up my stock ROM before I flash to a custom ROM? I do have clockwork recovery installed through Odin, I did follow the guide on installing Voodoo lagfix and I am running JT's 11/16 UV kernel on the stock ROM. Now I want to flash BlackHole or perhaps SuperClean, but I don't want to take any risks, and for some reason I haven't been able to find instructions on how to perform a backup. Do I just remove voodoo, boot into Clockwork from ROM Manager, and then make a backup?
Also, I guess I need instructions on how I would restore that backup if I needed to. I only see instructions on restoring a stock image using ODIN, but I want specifically the current state that I have right now (apps and everything) when I restore. Thanks!
Yes make sure you uninstall voodoo before creating a backup, voodoo does not play nice with clockwork. To restore a backup simply boot into recovery then select "backup and restore" then choose restore then choose which restore you would like. I loved voodoo at first and all of jt's work is great imo but I prefer geeknik's stupid fast kernels now just because I think they are just as fast and you don't have to deal with uninstalling voodoo...sorry for the rant...
Sent from my SCH-I500 using XDA App
Nand Backup
So iN My recovery thunderg 2.2.1 RA i Go 2 backup and it only says nand back up and nand restore????? do i have to download nandroid backup..?
Nand back up is Nandroid backup.
Sent from my SCH-I500 using XDA Premium App
My samsung fascinate has VooDoo on it. I did not put it there, I am not comfortable with ADB shell and the commands that go with it. Its a D101 that HAS to run at 800Mhz with Voodoo (Not the 1.2 the specific voodoo is) at 1.2 nothing runs and constantly redraws the homescreen.
I tried the automatic uninstaller, and the red recovery stays to haunt. I've tried other kernels while disabling Voodoo.
My phone was running fine up until recently where it would have random reboots and have trouble booting back up.
I came across flashing back to stock with ODIN. the system file went over fine, and I even did the stock kernel and (PIT)
i Just flashed them all through ODIN.
The phone boots up fine to the main screen, where then I get the error message about a UID ? (Sounds dirty) it says to wipe data or my phone will have inconsistencies. Then gives me a button that says "feeling lucky"
Message as follows "UIDs on the system are inconsistent, you need to wipe your data partion or your device will be unstable" Only button to click is I'm feeling Lucky
everything force closes, red voodoo still shows up in recovery. What am I missing or doing wrong?
I bought this phone this way and like i said i know NOTHING about ADB or all those commands, etc.
Can somebody help me out? I'd even gladly send it to a trusted member for repair with a donation, of course.. until then I'm using my OLD bb curve
http://forum.xda-developers.com/showthread.php?t=867648
thats full d101 thread
http://forum.xda-developers.com/showthread.php?t=885262
thats full dj05 thread
both should be able to get you back to stock through odin then you can restart what you did. personally i keep both handy since i already had to use them due to an error that cause the phone to freeze up completely at the samsung logo. hope that helps
make sure you use the pda option in odin and not the phone..aparantly using the phone option can really screw things up
I did another factory data reset, and my UID message vanished. Although, VooDoo is still in recovery even after flashing D101 through ODIN.
My phone gave me the notification of an update (DL09) It downloaded it, and when it went to install it - it booted right into the red VooDoo recovery.
I'm going to flash DL09 through ODIN now, but I'm thinking VooDoo isn't about to go anywhere.
BrianWM said:
I did another factory data reset, and my UID message vanished. Although, VooDoo is still in recovery even after flashing D101 through ODIN.
My phone gave me the notification of an update (DL09) It downloaded it, and when it went to install it - it booted right into the red VooDoo recovery.
I'm going to flash DL09 through ODIN now, but I'm thinking VooDoo isn't about to go anywhere.
Click to expand...
Click to collapse
are you disabling voodoo before flashing these new kernels?
Powell730 said:
are you disabling voodoo before flashing these new kernels?
Click to expand...
Click to collapse
Yes, VooDoo is disabled.
BrianWM said:
Yes, VooDoo is disabled.
Click to expand...
Click to collapse
so did you use the odin files and flash it via PDA in odin? if so, did that revert you to total stock? i believe those .md5 files contain the stock recovery.
EDIT:
do you know what version of voodoo you're using?
http://forum.xda-developers.com/showthread.php?t=804784
that guide should help you, if you're using voodoo 5 there is a guide there that specifcally says "if you're still getting the red voodoo menu flash this file then flash a nonvoodoo kernel." check that article out by ady if you havent already.
flash voodoo boot right into recovery. adb shell into the device and type
cat /voodoo/partition_tables/fascinate > /dev/block/mmcblk0
And then reflash everything with Odin.
Also one of adrynalyne's di01 packages doesnt flash recovery. So either flash my dj05 or go to adrynalyne's cwm odin thread and flash a regular update.zip cwm tar.
Sent from my SCH-I500 using XDA App
A proper, 100% full Odin tar will replace everything on the phone, including voodoo, and the partitions that it formatted as ext4 will now be RFS again. Since the full DJ05s and DL09s came out I use it as a first resort instead of a last resort. Flash the full tar, CWM, the kernel, then nandroid and I am good to go in about 15 minutes.
Just to throw my two cents' worth in here, red CWM is not synonymous with Voodoo. It's just the version of Clockworkmod recovery that is capable of working when the lag fix is enabled. It's normally installed with Voodoo kernels, but the Voodoo lagfix itself can be completely disabled, and red CWM will still work just fine. If you got the OTA notification for DL09, it sounds like you have a stock ROM, which means Voodoo is actually gone, so you just need to restore the recovery from red CWM back to stock so that the OTA patch will be able to install properly.
ivorycruncher said:
Just to throw my two cents' worth in here, red CWM is not synonymous with Voodoo. It's just the version of Clockworkmod recovery that is capable of working when the lag fix is enabled. It's normally installed with Voodoo kernels, but the Voodoo lagfix itself can be completely disabled, and red CWM will still work just fine. If you got the OTA notification for DL09, it sounds like you have a stock ROM, which means Voodoo is actually gone, so you just need to restore the recovery from red CWM back to stock so that the OTA patch will be able to install properly.
Click to expand...
Click to collapse
Presentation is everything, thanks for the info!
[RED-CWM] (not orange)
Alright sick of scanning 3 different threads trying to help people with the new Clockwork manager I decided to write up this guide. This was tested from stock, I flashed back to stock to test both these methods, and they should work for everyone.
Stock versions tested: DI01 (stock), DJ05 (stock), odin method works flawlessly on these versions. cwm was not replaced by sammy kernel.
Stock DL09 will remove cwm on reboot, install a different kernel adryn's should work, pick your poison here: http://forum.xda-developers.com/showthread.php?t=915709 flashed cwm via odin. install kernel, then rebooted, if you get stock recovery flash via odin one more time.
Nonvoodoo EB01 currently some people report it will boot to blue recovery after installing new roms. nonoodoo users should leave, http://dl.dropbox.com/u/2056318/update.zip on the root of there sdcard that way after a new install of a rom you can get back to cwm. after applying udate.zip, install cwm-recovery-ALL.zip. (Thanks Landshark68)
To get to stock use adrynalyne's DI01 package get it here: http://forum.xda-developers.com/showthread.php?t=867648 flash via odin.
First I would like to thank jt1134 for fixing up the new cwm get your perferred version here: http://forum.xda-developers.com/showthread.php?t=942021
Odin method (preferred method stock users do this one!)
1. Alright let’s do this, head over to jt’s original post and download the cwm-recovery-ALL odin:
2. Plug phone into PC and turn off phone
3. Pull battery in phone and then press the down volume button
4. Open odin on PC and press PDA load cwm-recovery-ALL.tar, DON’T MESS WITH ANY OTHER SETTING! Then hit the start button.
5. Boot into recovery (cwm) do this by holding both volume keys plus the power button till you see Samsung screen, you can let go then.
6. Congrats your done now install your custom roms, kernels, radios, and other various things!
Clockwork manager method (only if you have cwm installed already)
1. Copy new cwm-recovery-ALL.zip to root of SD card. (do not need to rename!)
2. Boot into recovery
3. Choose install zip from sdcard
4. Choose cwm-recovery-ALL.zip
5. Reboot your phone and delete update.zip from root of SD card, and recovery-update.zip from clockworkmod folder.
The cwm should be red, and should say voodoo no matter if you have a voodoo kernel or not.
Rom manager will not boot your phone to recovery, install a new shutdown menu that includes boot to recovery or do a manual boot to recovery.
The new clockwork manager installs to the boot partition of the phone that's why you no longer need the update.zip file. Do not flash the cwm from Rom manager, it’s not needed folks, and will put your phone into an endless boot. The cwm jt gave us is customized for our phones.
Post your questions here I will be happy to answer them.
Below I attacked the clockwork manager files, plus odin3 v1.3 but visit jt's OP and give him a thanks, I'm just the translator, hes got plenty of other crap to do rather than test this out.
I am not responsible for any bricked, broken, or abducted phones.
Tried it, works fine. Took a bit on that first boot into recovery after the install was run (already had cwm installed), you know that held breathe of "did it work"!
vlucchetti said:
Tried it, works fine. Took a bit on that first boot into recovery after the install was run (already had cwm installed), you know that held breathe of "did it work"!
Click to expand...
Click to collapse
just be sure not to flash cwm from rom manager application, or you'll be holding your breath till you black out
Takafiji said:
just be sure not to flash cwm from rom manager application, or you'll be holding your breath till you black out
Click to expand...
Click to collapse
Seriously thinking of deleting ROM Manager altogether. I did dl Adryn's revised ROM Mgr but may switch to doing everything through cwm.
I think the slight delay after the double samsung flash is the program working through blue in the background so it jumps right to red afterward.
Adryn's kernel isn't working for me. But that's what searching is for.
I also owe you a huge thanks for all your help earlier.
Sent from my SCH-I500 using XDA App
lfrench0 said:
Adryn's kernel isn't working for me. But that's what searching is for.
I also owe you a huge thanks for all your help earlier.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
no prob thats what we're here for.
any custom kernel built for dj09 will work. only use a kernel for your raidio/rom version ie: dI01, dj05, dj09, dl30, ebo1 etc...
Hey Takafiji,
I posted a similar thread over at Android Central about the same time as yours here at xda. I discovered this ability to boot directly to red cwm, and I put together the how-to thread and everything was great until I booted to recovery one time and saw stock blue (2e) recovery. I played around with different options, but couldn't completely get rid of blue recovery. I decided to do some research in jt1134's thread and saw the link to yours and read everything here. I have tried every method in your thread and jt1134's thread and I keep running into the same problem. I can install the new cwm just fine and I can keep booting directly into red cwm just fine until.........I flash a new ROM. I can flash themes, patches, add-ons no problem, still able to boot to red cwm. As soon as I flash a new ROM, I boot to stock blue recovery. The only ROM I have been flashing is Adrynalyne's superclean 2.4. I read in jt1134's post that flashing a stock kernel will revert you back to stock blue recovery. The kernel in Adrynalyne's sc 2.4 is the farthest from stock we can currently get in nonvoodoo EB01. My guess is we will not be able to boot directly to the new red cwm on nonvoodoo until the devs get their hands on the source code and we get some custom nonvoodoo kernels. Any thoughts? Thanks
landshark68 said:
Hey Takafiji, Any thoughts? Thanks
Click to expand...
Click to collapse
ummm not sure here, you could try a voodoo kernel, they work wonderfully. how are you rebooting to recovery? rom manager doesn't work all too well in that area, try using the power menu and reboot to recovery that way. i will do some more testing but ive been jumping around on different eb01 roms just fine. Is it all roms or just superclean ones?
Takafiji said:
ummm not sure here, you could try a voodoo kernel, they work wonderfully. how are you rebooting to recovery? rom manager doesn't work all too well in that area, try using the power menu and reboot to recovery that way. i will do some more testing but ive been jumping around on different eb01 roms just fine. Is it all roms or just superclean ones?
Click to expand...
Click to collapse
I got rid of Rom Manager as soon as we got the long press power button menu with recovery in it. The only ways I boot to recovery are long press power and holding volume down, volume up, and power buttons.
ummm have you tried applying a older cwm after booting to blue recovery? maybe if you booted to that then installed jt's new cwm you'd be set. just a thought. http://dl.dropbox.com/u/2056318/update.zip should work, if it comes up unsigned we will have to explore different options. I'm trying to figure out why its going blue with a non-stock kernel, the new cwm installs to the boot partition.
Takafiji said:
ummm have you tried applying a older cwm after booting to blue recovery? maybe if you booted to that then installed jt's new cwm you'd be set. just a thought. http://dl.dropbox.com/u/2056318/update.zip should work, if it comes up unsigned we will have to explore different options. I'm trying to figure out why its going blue with a non-stock kernel, the new cwm installs to the boot partition.
Click to expand...
Click to collapse
Already tried that if the old cwm you are linking me to is the new red cwm for froyo we had before the current one. Loaded that cwm via ODIN, had new red on base of sd card, installed via old red cwm, no luck, went back to blue as soon as i flashed sc 2.4. The only thing I'm thinking is I don't think the kernel in sc 2.4 is truly a custom kernel. I believe I read the kernel in 2.4 is still the stock kernel, just slightly modified by Adrynalyne. Thanks.
landshark68 said:
Already tried that if the old cwm you are linking me to is the new red cwm for froyo we had before the current one. Loaded that cwm via ODIN, had new red on base of sd card, installed via old red cwm, no luck, went back to blue as soon as i flashed sc 2.4. The only thing I'm thinking is I don't think the kernel in sc 2.4 is truly a custom kernel. I believe I read the kernel in 2.4 is still the stock kernel, just slightly modified by Adrynalyne. Thanks.
Click to expand...
Click to collapse
have you tried flashing stock di01, then jumping to a stock eb01, maybe that would work. not sure but i know the dl09 recovery overwites cwm. maybe you just got parts of it still stuck there...
Sorry wish i was a c programmer i'd jump on board and start helping create a custom kernel.
Takafiji said:
have you tried flashing stock di01, then jumping to a stock eb01, maybe that would work. not sure but i know the dl09 recovery overwites cwm. maybe you just got parts of it still stuck there...
Sorry wish i was a c programmer i'd jump on board and start helping create a custom kernel.
Click to expand...
Click to collapse
No problem. I'm just going to keep going through blue recovery to get to red cwm until we get some custom nonvoodoo kernels. I updated my OP to advise everyone there on nonvoodoo to put update.zip back on the root of their sd card and do the same for now. Thanks again for the brainstorming and ideas.
EDIT- Also to let you know, yes I already tried flashing back to DI01 then to EB01. We are definitely thinking along the same lines.
Well now I'm totally gorked up. I followed Zacisblack's method with your addition of doing the ODIN install first. Now when I get blue recovery and hit apply sdcard:update.zip I go to green cwm. Trying to figure out a solution to that now.
EDIT - fixed that problem. Fortunately I still had a copy of the cwm_froyo.tar
I also have the same issue when flashing a new rom. It always goes to blue recovery.What I have to do every time is in blue cwm go to apply sdcard/update.zip which gets me in green cwm. Then I go to choose zip and scroll down to clockwork and choose cwm-recovery-all and flash it again then scroll down to update.zip and flash it then i go to applysdcard/update.zip and flash that then i reboot. Then next time i boot into recovery it always goes straight to red cwm. Sounds like a pain (and sometimes it is) but in reality it only takes like 5 minutes. I wish i didn't have to do that every time i flash a new rom but thats just part of my routine now as its what works for me.
I might not have to do all of those to get back to red but thats the way i originally got red cwm on my phone from a great write up on jt's thread (sorry but don't remember who did the write up). Maybe I'll experiment with just flashing one of those zip's next time i flash a rom to see if there's a faster way.
But I would really like it if there was a way to just always go to red cwm with a new rom instead of going thru all that.
Fantastic tutorial! Just what I was looking for! Thanks a million!!
Thanks Takafiji! I had just installed the Superclean v2.6 non voodoo and got the stock blue (2e) recovery as well. I tried to apply the update.zip and it took me to orange. I read your original post and it worked wonderfully!
Takafiji Quote from OP:
"Nonvoodoo EB01 currently some people report it will boot to blue recovery after installing new roms. nonoodoo users should leave, <drop box link to update.zip> on the root of there sdcard that way after a new install of a rom you can get back to cwm. after applying udate.zip, install cwm-recovery-ALL.zip. (Thanks Landshark68)"
...now, if I could just figure out why Google Voice can't seem to find my contacts, i.e. voice command "Call Mark Davis", nothing found and defaults to looking on the web.
My phone won't even update the app. When I try it d/l's, starts then aborts saying it isn't properly signed. Guess I'll stay with Adrynalyne's modified one for now.
I used ODIN to flash the new-CWM, but it always seems to boot into blue recovery. Using update.zip gets me into green, which seems to work fine for flashing roms. I've occasionally seen red recovery, but when using update.zip takes me right back to green.
Am I doing anything wrong here?
Thanks for the write-up I flashed recovery with ODIN
In read recovery and working great
again THANKS for the writeup
Had a eco5 rooted epic with rfs file system tried installing bonsai
used master key and flashed to 4.1.3 U get assert failed run_program("tmp/install-script)==0
E:error in sdcard/bonsai_SPHD700_4.1.3.zip
(Status 7)
Installtion aborted
tried doing a restore in cwm and it just hangs at the samsung logo........I think it converted it from rfs to ext 4 and screwed up somehow......what should i do?
Odin? Then, restore a backup once your back on stock RFS (assuming you don't want to lose anything. Otherwise, don't restore.
Also, you might have gotten a bad download
Sent from my SPH-D700 using XDA Premium App
thanks can u walk me through this a bit its been a while. How do i odin back to eco5 and keep root? i have everything i need. I guessi just need to odin to eco5 and convert to ext4?
If you're on RFS trying to install an EXT4 ROM, it won't run because of the edify script. Best bet is to either convert to EXT4 or find an RFS ROM... First you'll have to Odin of course, but after that, aim for either RFS-EXT4 capable ROMs or you'll have to choose which one. Also, I don't really know about his ROM's that much, but is it EC05 or newer?
eco5 at this point i just want to get back to stock eco5 and get root
newguy0804 said:
thanks can u walk me through this a bit its been a while. How do i odin back to eco5 and keep root? i have everything i need. I guessi just need to odin to eco5 and convert to ext4?
Click to expand...
Click to collapse
You wont be able to keep root. You'll have to Odin back, then re-root your phone. It's a process, but it's what'll have to be done. It'll take maybe 10 minutes total. Just search the dev section for Odin, and follow the directions.
Here's the link... Just follow the instructions.
http://forum.xda-developers.com/showthread.php?t=1052813
Thanks dude your a lifesaver. So once I get that part done I need to root. My apps im not worried about I have titanium backup and a nandroid backup through rom manager. never used it after somthing like this though so what is the next step after I odin to eco5?
After you Odin, run the new root with the new cwm so you're completely up to date... then you will have root and recovery, and you just flash a ROM, or a backup ...just make sure it's EC05 and RFS or you'll have the same issues.
hmmm.....do u have a link by any chance? also when I 1st start this up how long should I wait for this to start? any ideai oh how to use rom manager of titanium back up comes into play with this?
You got asserts error because you used ROM Manager. If you download the EB13 stock tar from Bonsai site, use Masterkey unlocker on that, then power down, 3 finger into recovery and flash 4.1.3, Boot up, power down, 3 finger, Advance Restore Data you will be fine. Stay away from Rom Manager and Quick boot for backup, restore or flashing.
Look at the sticky posts in the dev section. You're looking for 3.1.0.1 one click root. Download and run that. And yes, don't use ROM manager. Just power off and use volume down+ camera+ power to boot into clockwork mod.
Sent from my SPH-D700 using XDA Premium App
I just rooted my girlfriend's year old fascinate that was bone stock from day 1. In CWM I am unable to make a nandroid (I get an error). I've heard I need a modded stock kernel in order to successfully make a backup in CWM 3.x or something along those lines.
I looked in the developer forum under the sticky with the list of everything, but it only shows three or so kernels (none of which hint at stock).
I have a Thunderbolt and before that a Droid 2 so I know a lot about rooting and flashing with those two devices, but I am new to the Fascinate. I messed around a bit with Odin when I rooted the phone, but I'm still learning.
Any help is greatly appreciated.
Older recoveries supported amend scripting (2.x.x) while newer ones support edify scripting (3.x.x)...depending on which rom your running it may cause problems with backups and restores if you don't have the right recovery...unless you plan on going to an Mtd build (cm7, Miui, ect) I would recommend using the (2.5.1) recovery also called the 3/30 fix all recovery because this version supports both amend and edify scripting..so you make a nandroid with out issues....if you can get to recovery still I would install this zip and then select reboot recovery...it will bring you to the 3/30 fix all recovery where you should be able to backup and restore your nandroid...link to follow shortly...
Scroll down in the first page to the .zip file, download and continue with the steps I listed...I know its confusing at first mainly because development has happens rather quickly which is a good thing! its just a lot to catch up on!
http://forum.xda-developers.com/showthread.php?t=942021
Sent from my SCH-I500 using XDA App
What would you recommend if my plan was to install MIUI or OMFGB?
I'm deciding between those two because I use OMFGB on my Thunderbolt all the time, but MIUI is very good for my girlfriend I think because it's very straight forward and simplistic.
http://forum.xda-developers.com/showthread.php?t=1124391
Its not hard to get in to these roms, but you must be sure if you have problems or want to go to anything non Mtd you will have to Odin an official VZW tar and pit file to repartition before going to any non Mtd rom
http://forum.xda-developers.com/showthread.php?t=1124391
Sent from my SCH-I500 using XDA App
So basically:
1. Flash the CWM you posted in your original reply
2. Nandroid her current stock setup
3. Flash MIUI
4. If I ever want to return to stock or a non-mtd rom I have to do what's posted in your second reply?
If all that is correct please let me know. Also lets say she doesn't like MIUI, can I simply flash that nandroid or will I have to do what's posted in the second reply?
When I try to flash that older CWM in CWM I get this message:
http://i.imgur.com/3QiwQ.jpg
want a droid said:
So basically:
1. Flash the CWM you posted in your original reply
2. Nandroid her current stock setup
3. Flash MIUI
4. If I ever want to return to stock or a non-mtd rom I have to do what's posted in your second reply?
If all that is correct please let me know. Also lets say she doesn't like MIUI, can I simply flash that nandroid or will I have to do what's posted in the second reply?
Click to expand...
Click to collapse
Yes you will have to do what's in the second reply.
You have it all correct, if you nandroid her current stock setup you can only restore it on a non Mtd build you would have to do what I linked to in the second post to use a vzw rom with pit file to repartition...boot fully, flash recovery then you could restore her stock nandroid..for example you get her on Miui you can only do a nandroid with the recovery that comes with it...I think its a 4.x.x recovery...trying to restore the stock nandroid before repartitioning back to stock will cause problems...so basically you only want to restore a nandroid on the same build (Mtd to Mtd nandroid, or ext4/rfs to ext4/rfs nandroid) and if all else fails and you run into big problems, doing the VZW restore (although can be a lengthy process) will get the phone back running to start over!
Sent from my SCH-I500 using XDA App
Did you see my reply before this? I was unable to get CWM 2.x to flash so I'm still on CWM 3.x.
want a droid said:
Did you see my reply before this? I was unable to get CWM 2.x to flash so I'm still on CWM 3.x.
Click to expand...
Click to collapse
I did see it after I replied, is her phone on ed05? I'm surprised that neither the 3/30 fix all or 3.x.x is working
Edit after looking at the pick again you're using times infinity's recovery....you would need to Odin the 3/30 fix all recovery and immediately three finger boot into recovery without letting the phone boot or if you installed the 3/30 fix all via .zip file, you need to choose reboot recovery to enter the fix all one, it should be 2.5.1 I believe
Sent from my SCH-I500 using XDA App
Here's a picture of her phone info:
http://i.imgur.com/rs1Jd.jpg
And as you can tell from the other photo, both making a backup and flashing the CWM 2.x doesn't work.
Trying a backup results in: "Error while backing up boot image!"
Trying to flash CWM 2.x results in that long information message.
That sucks man i'm sorry I've never been on ed05 so I don't know if that why your having problems my suggestion...back up all her contacts by exporting them to sd card, download titanium backup its free in the market, backup all of her apps and screw the nandroid, flash what you want, restore her apps with titanium, but do not restore data, restore get contacts and then boot into the recovery that comes with the rom/kernel and then do a nandroid and that WILL work..again sorry for the trouble, just trying to help.
Sent from my SCH-I500 using XDA App
I appreciate all your help. I'll let you know how it goes.
ed05 is not the problem...You have to use cwm 2.5.1.x if your trying to nandroid backup a stock rom. This version of cwm works on all froyo roms and powerwashed gingerbread. After you make a nandroid with cwm2.5.1.x, then flash cwm4 and proceed to installing miui.
Read this link for flashing mtd based roms such as miui, cm7, vgb...etc
http://forum.xda-developers.com/showthread.php?t=1212239
That was my first reply to him...to use 2.5.1 but he said he still got errors? I don't have a clue what the problem is...he's said he's used ti's 3x.x, and the 3/30 fix all still with errors? confused?
Sent from my SCH-I500 using XDA App
droidstyle said:
ed05 is not the problem...You have to use cwm 2.5.1.x if your trying to nandroid backup a stock rom. This version of cwm works on all froyo roms and powerwashed gingerbread. After you make a nandroid with cwm2.5.1.x, then flash cwm4 and proceed to installing miui.
Read this link for flashing mtd based roms such as miui, cm7, vgb...etc
http://forum.xda-developers.com/showthread.php?t=1212239
Click to expand...
Click to collapse
I guess you skipped the entire thread, but we already went through all that.
want a droid said:
I guess you skipped the entire thread, but we already went through all that.
Click to expand...
Click to collapse
I think you skipped a step... Are you flashin cwm via the PDA function in ODIN?
If not you need to:
ODIN the cwmAll.tar here: http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1238070&v=1&libid=1316306736482&out=http%3A%2F%2Fwww.mediafire.com%2F%3F6x5utoca59et7o9&title=%5BGUIDE%5D%20Installing%20a%20rom%2F%20cwm%20recovery%2F%20or%20going%20back%20to%20stock%20for%20NEWBIES!%20-%20xda-developers&txt=http%3A%2F%2Fwww.mediafire.com%2F%3F6x5utoca59et7o9&jsonp=vglnk_jsonp_13163071702031
make a nandroid back up of the stock rom.
go back to odin and flash the jt's cwm4
boot into recovery
wipe data, cache, dalvik
install miui.zipfrom sd card
Follow the rest of the directions in the link I provided
+1 there ya go. Beat me to it.
Plus, I wouldn't even worry about backing up your stock ROM. Just flash the full official package. This will wipe your slate clean if you run into problems. Restoring nandroid backups leads to glitches eventually from what I've seen.
Sorry, I didn't see there was a second page here...I'm a bum.
want a droid said:
I guess you skipped the entire thread, but we already went through all that.
Click to expand...
Click to collapse
Should probably try not being a **** when you're begging for help from people.
Sent from my SCH-I500 using XDA App
Personally, I thought his reply was honest and effective. I commend him on his frankness, and respect him for his boldness.
grenade01 said:
Personally, I thought his reply was honest and effective. I commend him on his frankness, and respect him for his boldness.
Click to expand...
Click to collapse
Really? Snide, snarky comments are respectable? At the very least, they shouldn't be coming from the person asking for help.
Sent from my SCH-I500 using XDA App