Database Develop

[RECOVERY] ClockworkMod Recovery for Vibrant (FINAL! SAFE!)

First things first, if you flashed a previous version of Clockwork Recovery using Odin, FLASH BACK TO A STOCK KERNEL using this Odin package:
http://koush.tandtgaming.com//test/kernel-vibrant-stock.tar.md5
This recovery is *very* safe to use. It does NOT flash your kernel; it is a completely uninvasive recovery method.
How it works: The recovery is packaged as an update.zip that you run from STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original, unmodified, stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork.
HOWEVER, if you use ROM Manager, all of the recovery installation and management instructions are done for you!
Installation instructions:
Download ROM Manager from the Market.
Flash Recovery.
Choose Vibrant as your phone.
Accept the Superuser prompt.
On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
Watch the backup go!
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!

Failed the first time. Left me in the stock recovery menu and gave a recovery error when clockwork first started. Flashed again and tried to backup a second time. Looks like it worked perfect! Now we need some froyo!
Sent from my SGH-T959 using XDA App

youneek said:
Failed the first time. Left me in the stock recovery menu and gave a recovery error when clockwork first started. Flashed again and tried to backup a second time. Looks like it worked perfect! Now we need some froyo!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes! That is expected! The very first boot WILL FAIL, the recovery needs a kick start to complete installation.

little tip
after I downloaded Rom Manager and had it download the recovery for my Vibrant.
After the success message I waited nothing happened so you may have to select to manually reboot into the recovery, then select "reinstall packages" to finish the installation.

I don't see Vibrant in ROM manager. Do I need to buy premium or am I doin somethin wrong

metalfan78 said:
I don't see Vibrant in ROM manager. Do I need to buy premium or am I doin somethin wrong
Click to expand...
Click to collapse
he either took it down and is gonna release it later or something... just wait..

I don't even see "Vibrant" in that list
Nevermind....see above

lp894 said:
I don't even see "Vibrant" in that list
Click to expand...
Click to collapse
Vibrant is listed. "Galaxy S Vibrant". Make sure you are on wifi. Some carriers cache web pages.

Sweet I can't wait to have a real recovery

Koush said:
Vibrant is listed. "Galaxy S Vibrant". Make sure you are on wifi. Some carriers cache web pages.
Click to expand...
Click to collapse
I can confirm I used Wifi and have already completed my first backup using Clockwork
thanks Koush.. buying the prem version to show my support!

Bummer I guess ill have to wait until I can find a hotspot

I downloaded the clockwork Rom Manager premium and I press the pFlash Recovery button. But I don't see Vibrant in the list either.

Please make sure you guys are on wifi. T-Mobile is caching your webpages and serving you older versions.

when i flash the recovery.. and reboot it goes to the stock recovery i hit reinstall packages then it goes to clockwork.. but after that if i reboot it goes back to stock... hmm thats odd..

ElChibo said:
when i flash the recovery.. and reboot it goes to the stock recovery i hit reinstall packages then it goes to clockwork.. but after that if i reboot it goes back to stock... hmm thats odd..
Click to expand...
Click to collapse
That's how it is supposed to work. Recovery is not replaced permanently. It's safer that way. Just reinstall packages to get into clockwork. Or use ROM Manager to have it handle everything automatically.

metalfan78 said:
Bummer I guess ill have to wait until I can find a hotspot
Click to expand...
Click to collapse
No, you don't have to. Just go into your browser, go to menu-->more-->settings-->clear chache and that will get you going

Koush said:
That's how it is supposed to work. Recovery is not replaced permanently. It's safer that way. Just reinstall packages to get into clockwork. Or use ROM Manager to have it handle everything automatically.
Click to expand...
Click to collapse
ok i get it now... ive been used to always having Amon-RA recovery on my phone when ever i boot to it.. so what your saying is everytime your gonna flash a custom rom this is gonna have to take place?

ElChibo said:
ok i get it now... ive been used to always having Amon-RA recovery on my phone when ever i boot to it.. so what your saying is everytime your gonna flash a custom rom this is gonna have to take place?
Click to expand...
Click to collapse
If flashing manually, yes. Just flash using ROM Manager though, and it will handle that all for you automatically.
I can't permanently replace the recovery until the kernel source and whatnot is released for the Vibrant.

Hells yeah!!! Will someone PLEASE put a shipped firmware out now? Like the T959UVJFD. I appreciate the life saving effort from MS_Guru, but t959uvje8 is not jiving with me and my 3g and/or wifi...

Amazing work! Excellent idea for a 100% safe recovery! Kudos!!
Sent from my SGH-T959 using XDA App

I NEED to get Clockworkmod Recovery on my phone, but I can't seem to get it to work

I got my phone back just 3 days ago and figured i'd finally customize it. I FINALLY figured out a safe and full-proof way of rooting my samsung galaxy s i9000M. I FINALLY figured out that I need to switch the <3e> recovery to <2e> recovery so that I'm able to flash custom ROMs.
Here's the annoying part...
I STILL can't set up Clockworkmod recovery instead of the stock recovery menu. The tutorial I'm following specifies that I need this recovery in order to get everything workin.
I have the phone rooted and I have ROM manager installed too.
Won't someone tell me how to install it on my phone?
I've tried this website:
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-3-using-rom-manager/
didn't work many times
thanks in advance!

stacyluo said:
Hi, I'm new to this forum.
Click to expand...
Click to collapse
gotta start somewhere

I should point out, it keeps saying "can't open /sdcard/update.zip"
(no such file or directory) if that helps

You mean you don't have recovery yet or you can't install any zip files?
Sent from my GT-I9000 using XDA Premium App

You'll probably need to do it via Odin.
If you look at the guides here on XDA you'll see easily how to do this.
There are probably easier ways to do by now, but you can follow the more traditional method without much difficulty and not really with that many screw up chances.
Just grab a custom Kernel, like SpeedMod or so, for Odin installation.
Follow the steps that you'll see on the Odin guide to install just the Kernel. Once that is done the Recovery mode will be altered and you can start using CWM normally from there on (or until you install some other full ROM that replaces the kernel and recovers the official recovery mode).

[OFFICIAL UPDATE][ROM]EL01 HC 3.2 TW UX update file for the VZW LTE Galaxy Tab 10.1

Ok guys, for all of you who are STILL waiting for the official update to roll out to our tabs, wait no longer. Thanks to PCPIMP over on android forums who pulled the update file from /cache in his tab before installing, we now have it and can flash it ourselves. However, there are a few quirks to getting this thing to flash properly. First: It must be flashed from stock recovery, NOT cwm recovery. Also, once you download the file from the multiupload link, you must rename it to update.zip Be careful here. When I renamed it to update.zip, somehow it would automatically add "bin" on to the end of the file. So without being able to see it, the file ended up with the name update.zip.bin and it was not showing up in stock recovery to flash. Use a file manager like 7zip to change the name or open up the properties on your PC to do it properly. Once it's renamed properly, put it on the the SD card. Here is something I am not completely sure of......but I *think* it doesn't matter what build you're on when you flash this file. It appears to me to be very insecure. You can even open up the update.zip with 7zip and debloat the stuff you don't want. I did. I only see one "patch" file in the update.zip and that was the LTE modem. What that means I'm prettty sure is that it will only require one file to be present on your tab to flash properly. This *may* even be able to be flashed directly from the Leak I posted of this build, for those of you who are on it. As long as you are on the correct radio because that's what it looks for. When you flash this file, it even wipes your data for you, But it does NOT wipe the SD card. I actually flashed it twice to see how secure it was. I flashed it from EH04 and EH04 radios and then I reflashed it directly over itself (EL01 and the EL01 radios) and it worked fine. So, I hope everyone understands all of that long winded babble I just spewed.
Step 1. Download update http://goo.gl/6XtFD (<--Huge thanks to PCPimp for hosting this) and rename it PROPERLY with 7zip or something to update.zip and place it on the root of your SD card. Make sure you don't have any other files named update.zip already on your SD, as that could get confusing, lol.
Step 2. Odin flash this recovery: http://dl.dropbox.com/u/20070269/lterec.tar.md5
Step 3. Boot into the stock recovery you just flashed and select apply update from SD card. Then scroll until you find update.zip. If it is not there, that means you didn't properly rename it. It most likely added the letters bin to the end of the name and can't be recognized by the recovery. So reboot and fix that and then start step 3 back over.
Step 4. When it is named properly and you flash it, most likely you are immediately going to see the dreaded Yellow exclamation point on the android signifying that there is an error or that you did something wrong.......Just wait. Keep watching it. It will eventually flash and your tab will reboot and you will be on EL01 and updated. Now, if you want root, see step 5
Step 5. Download both of these files: Kernel - http://droidbasement.com/galaxy/ker...36.4_lte_hc32-oc-xtra-vfpv3-d16_fp-010912.zip SU.zip - http://dl.dropbox.com/u/20070269/Superuser-3.0.7-efgh-signed.zip and put them both on your SD card.
Step 6. Open up odin program on your PC and click PDA and you will need to quene up this file in PDA: http://dl.dropbox.com/u/20070269/recovery.tar.md5 also, uncheck Auto Reboot in odin. YOU DO NOT WANT AUTO REBOOT TO HAVE A CHECK IN IT IN ODIN. REMOVE IT. Then power off tab and then boot into download mode by holding the power button until you see the samsung galaxy tab screen, then quickly let go of the power button but then immediately after and at the same time, hold power button and volume up until you are given two choices: A white box or the android. Careful, volume down at this point will choose for you. You will already be on the one you want to choose, which is the full sized android. BUT, make sure that odin is completely ready to go first. Make sure the recovery.tar that you just downloaded is quened up in PDA. On your tab push the volume down button and then follow the screen instructions. When the "Downloading" screen comes on, you need to move kinda quickly but you can relax. Just plug it in and hit start in odin. When you see the green pass in odin, unplug the tab and use the volume and power buttons again to boot into the other option, the white box and the little android. THIS IS VERY IMPORTANT! Once you have flashed the recovery.tar file, you must NOT let the tablet boot up fully and normally. You must directly into recovery. If it fully boots first, then the stock kernel will overwrite the cwm recovery with the stock recovery.
Step 7. So once you boot into to the turquoise cwm recovery, flash the 2 files you downloaded in step 5 in this order: The awesome kernel first, credit to Pershoot. Then flash the SU.zip file credit to ChainsDD: <------sometimes this SU.zip file will give you an error in CWM recovery when flashing it, just try it again and it will work.
Step 8. Reboot your tablet and enjoy a rooted EL01 updated tab with an AWESOME OC kernel from Pershoot.
Credit
Pershoot for the sweet kernel and recovery used in my guide
PCPIMP for pulling the update file from his tab and uploading it for us all
ChainsDD for root in general and the Superuser.zip used in my guide

Minor bloat removed...pretty darn fast without deodexing or kernel changes. I may just keep it stock with SU access.

Thanks for the files and the guide, everything is working great. I didn't wipe and am really surprised how well it's working, but still wish I could get rid of the TouchWiz stuff.
If I might make a suggestion, it'd be good to know to copy SU and the kernel to the device before flashing the CWM Recovery via ODIN. After flashing CWM, I had to let the tablet start up, copy the files, re-flash with ODIN, then load CWM and flash the kernel and SU. Not a big deal, just could have saved a step for me (although, I also could have read ahead...).

So i odin'd back to factory stock to use this, and it did push this update to me at the end of it, so it wound up not being necessary, thanks though!

Installation of the ROM failed. I did initially get the yellow exclamation mark you spoke of in step 4, but it went away and the moving gears appears showing progress. The yellow exclamation mark reappeared, however, and after 15 minutes I powered off. A bootloop ensued... downloading a TAR file of the stock shipped Verizon ROM to use in ODIN.

Is the ota update radios the same as in the leak?
sent from my 4g galaxy tab

inline6power said:
Is the ota update radios the same as in the leak?
sent from my 4g galaxy tab
Click to expand...
Click to collapse
No they are not.
Sent from my SCH-I905 using Tapatalk

ifiweresolucky said:
Installation of the ROM failed. I did initially get the yellow exclamation mark you spoke of in step 4, but it went away and the moving gears appears showing progress. The yellow exclamation mark reappeared, however, and after 15 minutes I powered off. A bootloop ensued... downloading a TAR file of the stock shipped Verizon ROM to use in ODIN.
Click to expand...
Click to collapse
Hmmm......interesting. What build and radio were you on when you flashed the update zip?
Sent from my SCH-I905 using Tapatalk

ifiweresolucky said:
Installation of the ROM failed. I did initially get the yellow exclamation mark you spoke of in step 4, but it went away and the moving gears appears showing progress. The yellow exclamation mark reappeared, however, and after 15 minutes I powered off. A bootloop ensued... downloading a TAR file of the stock shipped Verizon ROM to use in ODIN.
Click to expand...
Click to collapse
Had the exact same results using leaked 3.2 Baseband i905.02V.EIO2 Build HT85B.EIO3.SCH-I905.EI03 pershoot Kernal

Psean said:
Had the exact same results using leaked 3.2 Baseband i905.02V.EIO2 Build HT85B.EIO3.SCH-I905.EI03 pershoot Kernal
Click to expand...
Click to collapse
Yea, it seems that we do in fact have to be on at least the EH04 radios to flash the update. I noted in the OP that the update.zip contains an LTE modem patch, meaning it first has to detect the prior official radio so that it can patch the update to the modem. If it doesn't detect the correct modem, it errors out.
Sent from my SCH-I905 using Tapatalk

Is it any better or different than the leaked version though? I'd rather not go through the hassle if I'm not getting any changes over what I already have. Currently supercharged and zipaligned so I don't have any performance complaints right now, looking ahead to ics if there's nothing new in this ROM.

muzzy996 said:
Is it any better or different than the leaked version though? I'd rather not go through the hassle if I'm not getting any changes over what I already have. Currently supercharged and zipaligned so I don't have any performance complaints right now, looking ahead to ics if there's nothing new in this ROM.
Click to expand...
Click to collapse
Way better. Radios are ten times better and the nice thing is now ypi can view the market in portorit and not just landscape
sent from my 4g galaxy tab

muzzy996 said:
Is it any better or different than the leaked version though? I'd rather not go through the hassle if I'm not getting any changes over what I already have. Currently supercharged and zipaligned so I don't have any performance complaints right now, looking ahead to ics if there's nothing new in this ROM.
Click to expand...
Click to collapse
I have to agree that the radios are better. And, to me, it actually seems a little more snappy. And I don't think it's placebo either because at first, the update seemed a little buggier. But now that a few days has passed, I guess it's settled and it appears the bugs are gone. I would suggest updating.
Sent from my SCH-I905 using Tapatalk

kidserious said:
Step 5. Download both of these files: Kernel - http://droidbasement.com/galaxy/ker...36.4_lte_hc32-oc-xtra-vfpv3-d16_fp-010912.zip SU.zip - http://dl.dropbox.com/u/20070269/Superuser-3.0.7-efgh-signed.zip and put them both on your SD card.
Step 6. Open up odin program on your PC and click PDA and you will need to quene up this file in PDA: http://dl.dropbox.com/u/20070269/recovery.tar.md5
Click to expand...
Click to collapse
Question for you. I was already updated before this was posted, but if I odin in the recovery file in step 6, then flash in the 2 files from step 5, the end result will still be the same right? Rooted, with CWM and Pershoot's kernel installed, on the official update?
EDIT: NVM. I followed step 6 to the letter, then flashed in files from step 5. Of course next stop was SetCPU... Everything working fine.

eXiled Killah said:
Question for you. I was already updated before this was posted, but if I odin in the recovery file in step 6, then flash in the 2 files from step 5, the end result will still be the same right? Rooted, with CWM and Pershoot's kernel installed, on the official update?
EDIT: NVM. I followed step 6 to the letter, then flashed in files from step 5. Of course next stop was SetCPU... Everything working fine.
Click to expand...
Click to collapse
Yep, that works, lol. Cool deal
Sent from my SCH-I905 using Tapatalk

Bah . . stuck at bone stock 3.2 with stock recovery.
Tried flashing CWM 5.0.2.7 both from the dropbox link and from pershoot's site but when I try to boot into it I just get a blank screen. Rebooting into 3.2 gets me back the stock recovery but I'm unable to get CWM to work.
Open to ideas.
Odin flash of the CWM recovery file goes perfectly smoothly. I reboot and pick it and immediately get a blank screen (can see the bleed through of the backlight) and it sits there for as long as I let it (left it for 5 minutes waiting).
Long story short, I didnt realize the issue with the modems before trying the procedure coming from the leaked 3.2 which forced me to do a full wipe and reset using stock 3.1 and doing OTA updates normally to get to 3.2. That all went okay after spending an hour figuring out what was wrong . .

muzzy996 said:
Bah . . stuck at bone stock 3.2 with stock recovery.
Tried flashing CWM 5.0.2.7 both from the dropbox link and from pershoot's site but when I try to boot into it I just get a blank screen. Rebooting into 3.2 gets me back the stock recovery but I'm unable to get CWM to work.
Open to ideas.
Odin flash of the CWM recovery file goes perfectly smoothly. I reboot and pick it and immediately get a blank screen (can see the bleed through of the backlight) and it sits there for as long as I let it (left it for 5 minutes waiting).
Long story short, I didnt realize the issue with the modems before trying the procedure coming from the leaked 3.2 which forced me to do a full wipe and reset using stock 3.1 and doing OTA updates normally to get to 3.2. That all went okay after spending an hour figuring out what was wrong . .
Click to expand...
Click to collapse
Apply rooted kernel, because stock kernel keeps on flashing stock recovery. then flash custom recovery. sounds like recovery is being stupid/corrupted. Or odin back to stock then reroot etc.

magneticzero said:
Apply rooted kernel, because stock kernel keeps on flashing stock recovery. then flash custom recovery. sounds like recovery is being stupid/corrupted. Or odin back to stock then reroot etc.
Click to expand...
Click to collapse
Not sure why I had to but I rebooted my PC and tried again. What I noted is after updating to 3.2 via OTA my pc stopped recognizing the tablet on the USB port I normally used to flash. Other ports worked so I switched but as you suggested the recovery being flashed by Odin was going in corrupted.

muzzy996 said:
Not sure why I had to but I rebooted my PC and tried again. What I noted is after updating to 3.2 via OTA my pc stopped recognizing the tablet on the USB port I normally used to flash. Other ports worked so I switched but as you suggested the recovery being flashed by Odin was going in corrupted.
Click to expand...
Click to collapse
So you got cwm flashed eventually?
Sent from my SCH-I905 using Tapatalk

kidserious said:
So you got cwm flashed eventually?
Sent from my SCH-I905 using Tapatalk
Click to expand...
Click to collapse
Yep, all back to normal. We'll see how it goes. Out of the box it was noticably better than the leak, like perhaps it was zipaligned or something. Leaked rom with zipalign and v6 supercharger was pretty sweet already though.
Running fine right now.
Most irritating thing for me is the wifi toggle is gone from notification menu, replaced instead with mobile data toggle. Why someone would do this is beyond me. Leaked version had both a wifi toggle and an airport mode one. Now, I have to add a toggle onto a home screen, run extended controls or dive into settings manually to toggle it.
Also I'm not 100% sure if I hit it by mistake but I could have sworn I turned off auto brightness this morning and yet it was back on during lunch today.
All in all I'll agree its worthwhile to move from leaked to this but only marginally so, for stability sake and getting the latest modem drivers. If it puts you closer to the next OTA then its worth it.

[Q] Install CM for Galaxy S i9000 stuck

Hi All,
I've tried to find the answer but cannot see one specific to what I am experiencing.
I followed the guide from wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Semaphore's ClockworkMod Recovery was not working so I used the file from Replicant's recovery.img as per instructions at bottom of the page.
I followed the instructions. I rooted the phone, but I'm stuck. I can get into the recovery mode but I cannot mount the phone back to the PC so I can put the CM zip file onto the sdcard.
As soon as I turn on the phone, it goes into the CM Recovery menu.
Anyone know how to get the phone to mount to the PC and how I can get a CM image to the phone to install?
Thanks, please help. Need to get this phone working as I want to give it to my daughter to use in Italy.

malvic88 said:
Hi All,
I've tried to find the answer but cannot see one specific to what I am experiencing.
I followed the guide from wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Semaphore's ClockworkMod Recovery was not working so I used the file from Replicant's recovery.img as per instructions at bottom of the page.
I followed the instructions. I rooted the phone, but I'm stuck. I can get into the recovery mode but I cannot mount the phone back to the PC so I can put the CM zip file onto the sdcard.
As soon as I turn on the phone, it goes into the CM Recovery menu.
Anyone know how to get the phone to mount to the PC and how I can get a CM image to the phone to install?
Thanks, please help. Need to get this phone working as I want to give it to my daughter to use in Italy.
Click to expand...
Click to collapse
Put ur phone in download mode return to stock 2.3.6 then root it again and flash a different ROM or flash a differant kernel using Odin should fix ur problems
Sent from my GT-I9000 using xda premium

kevtrysmoddin said:
Put ur phone in download mode return to stock 2.3.6 then root it again and flash a different ROM or flash a differant kernel using Odin should fix ur problems
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Thanks, but I figured it out late last night. In recovery mode, there is an option to turn on USB mode. With USB on, the PC will see the phone. I downloaded the CM image (zip) to install. Put this into the root folder. Also downloaded the correct Google App as described in the link and put this into the root of the phone.
Turn off the USB. Leave phone plugged into the pc. With recovery mode, select install zip and select the CM zip file you put onto the root. This will install the CM. It will do this twice to convert the phone file system.
Phone will boot up and your in with CM. Now turn off and boot phone into recovery mode again using 3 button method. Select the Google apps zip file to install. This will install the Google Play and other software. Reboot and setup the phone!
Got the Galaxy S i9000 working again!

My phone is stuck on twrp after failed flashing 12.1 cyanogenmod

I followed all the steps to flash a rom onto my s3 mini. See this picture to see the problem: http://postimg.org/image/j4invhd0v/ I can transfer files using adb, but when i boot the phone, it goes automatically to TWRP. And when i try to flash the rom, that thing in the photo happens, basically my phone is gone now... Please help, this is quite urgent.

Leonardo Yip said:
I followed all the steps to flash a rom onto my s3 mini. See this picture to see the problem: http://postimg.org/image/j4invhd0v/ I can transfer files using adb, but when i boot the phone, it goes automatically to TWRP. And when i try to flash the rom, that thing in the photo happens, basically my phone is gone now... Please help, this is quite urgent.
Click to expand...
Click to collapse
fix permissions in clockwork mod menu, install a newer version of cwm.

mark-1978 said:
fix permissions in clockwork mod menu, install a newer version of cwm.
Click to expand...
Click to collapse
No, i'm using Twrp not CMW. And i can't get onto my phone, i can only boot into recovery.

Leonardo Yip said:
No, i'm using Twrp not CMW. And i can't get onto my phone, i can only boot into recovery.
Click to expand...
Click to collapse
in twrp you can also fix permissions. It's in advanced or some menu like that. Good luck!

It says failed to fix permissions.

Leonardo Yip said:
It says failed to fix permissions.
Click to expand...
Click to collapse
I would try to delete as much (wipe) as possible from your phone to make it work again. Wiping doesn't remove your recovery. Or flash another recovery tar if you can get into download mode.
install odin on windows pc: http://depositfiles.com/files/m2n77b1vc
install samsung drivers on windows pc: http://developer.samsung.com/technic...000000117#none
get cyanogenmod 12.1: http://novafusion.pl/
get the odin version
when mobile powered off, hold volume down, home and power button. You get the downloadmode option on your screen, let go all buttons and press volume up button.
Now connect the phone to your pc with the usb cable and let odin find it.
Load the tar file in the downloaded zip file as pda and flash it.
If you want clockwork mod, install this as tar, also in pda flash option: https://www.androidfilehost.com/?fid=95887005526789241
If your samsung doesn't work but you can still get into download mode, view next page: http://forum.xda-developers.com/show....php?t=2122548
and install a fail safe firmware according to your type of phone.

What I don't understand is why the flashing went wrong, I did everything right, at least I think. Wipe everything and flash the rom, why didn't it work?