I have a Telus i717d note that is stock running Android 4.0.4.
I would like to root it.
I am attempting to install a custom recovery using ODIN and failing at that juncture. I have tried both CWM, TouchCWN and OpenRecovery .tar.mdf files and all have the same (non) effect... everything is green and successful from within ODIN but when I boot the phone into recovery I appear to get the stock recovery still.
The screen has the following message on it:
"-- Verifying internal MMC block...
checksum confirmation -> check(0)
Not need checksum confirmation
already executed!!....
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : TLS
Successfully applied multi-CSC".
Other than that, it is the normal blue-text "Android system recover <3e>". This remains no matter what I do in Odin and how often... and in Odin I get full on Green "Completed" status with no errors.
Any ideas appreciated.
Ah yes,
that nice little feature that Samsung left in there for us, basically reverting the 3e recovery every time..
Stand by, i'll dig up the fix for ya......g
This is resolved.
The resolution was yanking the battery at just the right time as per
http://forum.xda-developers.com/showthread.php?t=1775263
Thanks,
paulvallee said:
I have a Telus i717d note that is stock running Android 4.0.4.
I would like to root it.
I am attempting to install a custom recovery using ODIN and failing at that juncture. I have tried both CWM, TouchCWN and OpenRecovery .tar.mdf files and all have the same (non) effect... everything is green and successful from within ODIN but when I boot the phone into recovery I appear to get the stock recovery still.
The screen has the following message on it:
"-- Verifying internal MMC block...
checksum confirmation -> check(0)
Not need checksum confirmation
already executed!!....
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : TLS
Successfully applied multi-CSC".
Other than that, it is the normal blue-text "Android system recover <3e>". This remains no matter what I do in Odin and how often... and in Odin I get full on Green "Completed" status with no errors.
Any ideas appreciated.
Click to expand...
Click to collapse
paulvallee said:
This is resolved.
The resolution was yanking the battery at just the right time as per
http://forum.xda-developers.com/showthread.php?t=1775263
Thanks,[/QUOTE
Actually,
It may come back...
the fix is a modified kernel, as the stock GB/ICS kernels will revert the 3e recovery after reboot..
But it sounds like ya got it.....g
Click to expand...
Click to collapse
Related
My phone will not flash back to stock, well it does but still get black screen after boot.
The error in recovery is this:
Code:
-- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR ChekSum Confirmation Fail
-- Movichecking done!...
#manual mode #
-- Appling Multi-CSC...
Installing Multi-CSC
When booting to recovery there are also some errors that I cannot catch, a lot of "Fails"
I need to do a complete restore i believe. I am not quite sure how this works, or seems to be really different from the behold 2, but is there a way to get all three odin files? PDA, Phone, and CSC?
Any help and thoughts will be greatly appreciated.
These are the things I have tried flashing:
[ROM] OFFICIAL T-Mo Vibrant JFD ODIN/Nandroid Backup Images 7/29/10 (Tested/Working)
(Rom){ODIN} Froyo ~~~That does not Brick! Downgrading Is Fine
A few times either or. First works, second freezes.
Should be in the general section, not development. You need to flash the JFD using ODIN, using the 512pit file and the tar file in the pda mode. Search for more detailed instructions on how to use ODIN
odin is not that difficult, but thanks for your help.
Its quite easy when it works, but the program is very finicky and gives some people a really hard time (gets stuck, freezing, not recognizing device)
Moved to general section.
where do we get the phone and csc files?
I'll start at the top. I have a Vibrant. I rooted it with one click lag fix and than tried clock work. I tried to partition my phone using that, but by doing so, I created a bad bootloop. The phone would go through the booting very slowly and than hang on a black screen with 4 lights (settings, home, back, and search) on.
I have tried Odin and it has not worked. I believe the reason is not because I'm doing it wrong, but because of this clock work partitioning that was done with rom manager.
When I use odin to go back to the stock vibrant, it works, but than sends me into the recovery screen which than I get this message.
" -- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MRB Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC "
That's my recovery message. I believe it is like that do to the clockwork partition. I believe If I fix that, I can use Odin. I have also tried using Odin in the "re-partition" check box, but it didn't work still.
Yea, I have the same issue, though I can odin. I use odin and it reboots fine, but I keep getting that error on the recovery.
" -- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MRB Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC "
Is there a way to odin/flash a stock recovery, since I am getting this checksum error? I know I used to be able to do that on the behold II.
Anyone? No one knows if you can odin a stock recovery?
Hey everyone. I am on stock 2.1 rooted - samsung vibrant. I also have that same message. My phone is working normally. But just annoys me that message. There has to be a way to clear that. On the other hand, I flashed a custom froyo rom previously and that message goes away but one bad note is that you cannot flash another rom through clockwork instead you have to odin back to stock rom. Same error message as above.
Mazz35 said:
Is there a way to odin/flash a stock recovery, since I am getting this checksum error? I know I used to be able to do that on the behold II.
Click to expand...
Click to collapse
Yes you can use odin to go back to stock rom, if that is what you are asking, Look at the binoix rom release the OP has posted links on how to go back to stock and also update the phone to the new JI6 using ODIN. Bionix info is in development section.
Same issue here. The error goes away if I flash the Froyo that does not brick.
But it comes right back when I go back to stock. Anyone have a fix?
nobody kno how to fix this??
anybody find a fix for this. I have same problem and my phone is just constant boot loop with all hardkeys constantly lit up. Have tried forcing restore with ADB, deleting all user data, cache data etc and cant get phone to restore or boot up to original or anything. Please help!!!
in the same boat with everyone here, going to try to update to 2.2 to see what happens
okay found a solution for now, my issue was related to ROM manager with the SD card, kept getting wrong MD5 Sum!! Really pissed me off about this since I was running through ODIN correctly,
Temporary Solution...
Updated the rom with Eugene froyo!! This brought me out of boot looping and now I have a rom on my phone so I can at least have a phone, and be able to use data/talk BUT..... I can download anything!! Both sd cards are apparently full, try to go back to stock rom but no luck just the same issue with the MD5 Sum. Any way around the md5 sum????
Solutions??? Ideas???
Is there anything you can do in eugene froyo no brick ?
Push something into sd card , flash rom manager through ADB, flash custom rom through adb? put a different PDA in Odin.
I dont care about going back to stock I just want a working rom!!! and be able to download apps, and start flashing roms....
bump
I can access external SD. How can I install Rom Manager to external SD. Correct me if I'm wrong but isn't there a MOUNT FIX in RM? Would this fix the internal SD so that a normal Odin load would work again?
Otherwise, maybe we can fix the internal SD with Ubuntu but need to know what format/specs to use.
Okay here was my issue, I know I'm seeing more people trying to get this fixed but there isn't much information on this and it seems to be trial and error for majority of the people.
-- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MRB Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
This error has to do with clockwork recovery from flashing cwr and getting an error. My error was when I flashed CWR and replaced the sd card! This cause me to boot into boot loops. Searching around on this thread and there are a few people with this issue and haven't found a solution.
This is what I did to be able to get past the mbr check sum error. Note I couldn't boot into stock rom with this error nor could I boot any rom besides the following!
Eugene no brick froyo...located on eb productions forum
I updated to Eugene no brick froyo, using Odin 1.7,
pit=512
Pda= eugene
Ran the process, and now you have a semi working rom, note I was unable to install anything or download on this rom. This is where I placed the CWR as and update zip (http://forum.xda-developers.com/showthread.php?t=734164)
Reboot into stock recovery, REINSTALL package, this will locate the CWR "update.zip" was the name I used. It rebooted into stock recovery once again, and then reboot again into Clockwork Recovery. You now have CWR working,
Use the voodoo lag fix
1. CWM voodoo lagfix (http://project-voodoo.org/), placed on sd card and flashed through CWR
2. reboot
3. disable voodoo (disable it you just make a directory called "disable lagfix" wihout the quotes in the Voodoo directory on the SD)
4. Oden "no brick froyo" w/ repariton checked, now I had a working rom where I could down load items from the market.
I downloaded Rom manager, although probably not needed. I flashed the recovery in rom manager, just to see if it would work. It did work and now I can go from rom to rom, however I still have the mbr check sum error when I reboot into recovery.
Hope this helps out with this error, any suggestions in cleaning this post up let me know. THANKS TO ALL
osugsxr said:
Okay here was my issue, I know I'm seeing more people trying to get this fixed but there isn't much information on this and it seems to be trial and error for majority of the people.
-- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MRB Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
This error has to do with clockwork recovery from flashing cwr and getting an error. My error was when I flashed CWR and replaced the sd card! This cause me to boot into boot loops. Searching around on this thread and there are a few people with this issue and haven't found a solution.
This is what I did to be able to get past the mbr check sum error. Note I couldn't boot into stock rom with this error nor could I boot any rom besides the following!
Eugene no brick froyo...located on eb productions forum
I updated to Eugene no brick froyo, using Odin 1.7,
pit=512
Pda= eugene
Ran the process, and now you have a semi working rom, note I was unable to install anything or download on this rom. This is where I placed the CWR as and update zip (http://forum.xda-developers.com/showthread.php?t=734164)
Reboot into stock recovery, REINSTALL package, this will locate the CWR "update.zip" was the name I used. It rebooted into stock recovery once again, and then reboot again into Clockwork Recovery. You now have CWR working,
Use the voodoo lag fix
1. CWM voodoo lagfix (http://project-voodoo.org/), placed on sd card and flashed through CWR
2. reboot
3. disable voodoo (disable it you just make a directory called "disable lagfix" wihout the quotes in the Voodoo directory on the SD)
4. Oden "no brick froyo" w/ repariton checked, now I had a working rom where I could down load items from the market.
I downloaded Rom manager, although probably not needed. I flashed the recovery in rom manager, just to see if it would work. It did work and now I can go from rom to rom, however I still have the mbr check sum error when I reboot into recovery.
Hope this helps out with this error, any suggestions in cleaning this post up let me know. THANKS TO ALL
Click to expand...
Click to collapse
I think supercurio fixed that with his voodoo 5.0.4 release.
good to know, just a helpful fix to my issue which people still have.
Thanks to this post, it helped took me off the loop of not able to restore JFD over it or truly get back to stock. I think I got it all restored as I can now install app and stuff.
It all happened when I took wrong advice or misunderstood and did "Wipe Partition Cache" in CWR. problems...after problems...after problems...
Phone Symptoms: Vibrant S splash screen and noisy bootup sound were there, but it changed to black screen with all four buttons at bottom lit up for a little while then disappeared to all pitch black on phone screen and buttons. I guess you can call it black soft brick? When you odin back using Eugene_2E_JK2_Froyo.tar.md5, it gets your Vibrant in semi-bootable state. If you odin back JFD tar, it brings back to original problem. In the recovery screen you also see "MBR Checksum Error, Movinand Checksum Confirmation Fail"...and when you try to apply update.zip it shows "data wipe failed" somewhere in the screen.
Anyway, here's what I did to get it back where you can flash JFD or Kies mini to recognize your phone for Tmobile update etc. even though "MBR Checksum Error, Movinand Checksum Confirmation Fail" still exist. I can't tell if that is normal or not, but at least Kies upgrade works...and can still install app and no more black soft brick.
Files needed:
* i9000 Froyo file: Eugene_2E_JK2_Froyo.tar.md5 (from http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
in the link "Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed"
http://www.multiupload.com/12QAKU043I )
* s1_odin_20100512.pit ( also from same page above but in the pit link )
* T959UVJFD.tar ( from http://www.justanotherdev.slackdev.com/T959UVJFD.tar via http://forum.xda-developers.com/showthread.php?t=734475
* i9000 with cwr to disable voodoo lagfix (ext4) Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-odin-pda.tar (from http://dl.project-voodoo.org/Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-odin-pda.tar or whatever new files at http://project-voodoo.org/download for Froyo )
1) Get your phone into download mode, fire up ODIN ( I used 1.7)
2) In ODIN, load s1_odin_20100512.pit into PIT and Eugene_2E_JK2_Froyo.tar.md5 into PDA. Checked or unchecked repartition does not seems to make a difference. Hit start and wait till completion with a pass. Reboot. It'll boot but will you not be able to install ROM Manager or most other apps with error saying something about no diskspace.
3) Copy the Froyo 5.2 Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-unsigned-update.zip for i9000 to your Vibrant /mnt/sdcard/update.zip via phone file manager or adb push... Then do 'adb reboot recovery' to put the phone into recovery mode or the 3 button push method.
Boot will show i9000 and button will go in wrong direction on your vibrant in recovery mode...ignore the wrong direction...go to voodoo lagfix, disable it, reboot.
4) Go to download mode and fire up ODIN again. Load s1_odin_20100512.pit into PIT and T959UVJFD.tar into PDA. Make sure 'repartition' is selected/enabled. Hit start, reboot, now things back to normal. You can install app...or do Kies...whatever...
PS: Can someone who have normal working phone let me know if you still get "MBR Checksum Error, Movinand Checksum Confirmation Fail" when going to recovery mode?
PPS: Instead of Kies, you get back to official stock froyo via odin with this only file (load to PDA) and NO repartition checked: T959UVKA6_REV05_home_low_CL860813.tar.md5
( from http://www.multiupload.com/GZT6ZYFX46 via http://forum.xda-developers.com/showthread.php?t=919687 )
kobesabi said:
Thanks to this post, it helped took me off the loop of not able to restore JFD over it or truly get back to stock. I think I got it all restored as I can now install app and stuff.
It all happened when I took wrong advice or misunderstood and did "Wipe Partition Cache" in CWR. problems...after problems...after problems...
Phone Symptoms: Vibrant S splash screen and noisy bootup sound were there, but it changed to black screen with all four buttons at bottom lit up for a little while then disappeared to all pitch black on phone screen and buttons. I guess you can call it black soft brick? When you odin back using Eugene_2E_JK2_Froyo.tar.md5, it gets your Vibrant in semi-bootable state. If you odin back JFD tar, it brings back to original problem. In the recovery screen you also see "MBR Checksum Error, Movinand Checksum Confirmation Fail"...and when you try to apply update.zip it shows "data wipe failed" somewhere in the screen.
Anyway, here's what I did to get it back where you can flash JFD or Kies mini to recognize your phone for Tmobile update etc. even though "MBR Checksum Error, Movinand Checksum Confirmation Fail" still exist. I can't tell if that is normal or not, but at least Kies upgrade works...and can still install app and no more black soft brick.
Files needed:
* i9000 Froyo file: Eugene_2E_JK2_Froyo.tar.md5 (from http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
in the link "Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed"
http://www.multiupload.com/12QAKU043I )
* s1_odin_20100512.pit ( also from same page above but in the pit link )
* T959UVJFD.tar ( from http://www.justanotherdev.slackdev.com/T959UVJFD.tar via http://forum.xda-developers.com/showthread.php?t=734475
* i9000 with cwr to disable voodoo lagfix (ext4) Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-odin-pda.tar (from http://dl.project-voodoo.org/Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-odin-pda.tar or whatever new files at http://project-voodoo.org/download for Froyo )
1) Get your phone into download mode, fire up ODIN ( I used 1.7)
2) In ODIN, load s1_odin_20100512.pit into PIT and Eugene_2E_JK2_Froyo.tar.md5 into PDA. Checked or unchecked repartition does not seems to make a difference. Hit start and wait till completion with a pass. Reboot. It'll boot but will you not be able to install ROM Manager or most other apps with error saying something about no diskspace.
3) Copy the Froyo 5.2 Voodoo-stable-5.2-Froyo-2.2.1-GT-I9000-unsigned-update.zip for i9000 to your Vibrant /mnt/sdcard/update.zip via phone file manager or adb push... Then do 'adb reboot recovery' to put the phone into recovery mode or the 3 button push method.
Boot will show i9000 and button will go in wrong direction on your vibrant in recovery mode...ignore the wrong direction...go to voodoo lagfix, disable it, reboot.
4) Go to download mode and fire up ODIN again. Load s1_odin_20100512.pit into PIT and T959UVJFD.tar into PDA. Make sure 'repartition' is selected/enabled. Hit start, reboot, now things back to normal. You can install app...or do Kies...whatever...
PS: Can someone who have normal working phone let me know if you still get "MBR Checksum Error, Movinand Checksum Confirmation Fail" when going to recovery mode?
PPS: Instead of Kies, you get back to official stock froyo via odin with this only file (load to PDA) and NO repartition checked: T959UVKA6_REV05_home_low_CL860813.tar.md5
( from http://www.multiupload.com/GZT6ZYFX46 via http://forum.xda-developers.com/showthread.php?t=919687 )
Click to expand...
Click to collapse
Thank God, I found this post....just fixed this phone I got from eBay, this was the biggest issue, could not install nothing due to that checksum error thingy now all good. Now I need to figure out why the screen lights up 10 seconds after user presses the power button, thank you!!
Thank you for this, I am trying to help a friend and this was the only procedure that I found that worked.. Thank you, after 5 hrs of work.. its booting from the black screen... Thanks!
@ kobesabi thanks alot...
thanks alot my frnd...
my fone's back in action now..
thanks very much
than you so much!
the link is dead
phone boots now perfectly but i still get checksum error.
I got this error while I partitioned internal SD card for 4 GB data space using subzero 159 kernel. I tried above methods but can't get rid of checksum error. I never have had an issue flashing ROMs. only problem is that I loose baseband version on many kernels using jelly bean and kit kat. although some kernels with fine. my idea is partition internal card to 0 MB using subzero then flash Eugene and rest of process. may it work.
kobesabi said:
Boot will show i9000 and button will go in wrong direction on your vibrant in recovery mode...ignore the wrong direction...go to voodoo lagfix, disable it, reboot.
Click to expand...
Click to collapse
When I get to this step there is no option to disable the voodoo lagfix. Just the normal recovery options like reboot and reinstall packages.
Same old story: I'm new at this, I screwed something up, my phone is unusable and I'd love to undo whatever mistake I've made. I searched all the forums, I have about 50 tabs open in Chrome, and I'm more confused than ever. So I figured I'd post my question here directly. Thanks for any help ahead of time.
My Vibrant is stuck in a system recovery loop. Here's how I got here:
I had upgraded my Vibrant to 2.2 using the official update via Samsung Kies.
Then:
1. I rooted the phone using SuperOneClick
2. I installed Clockworkmod Recovery (using this walkthrough)
3. I flashed the Voodoo Lagfix.
The lagfix seemed to install fine (took a few minutes, apparently was successful), but when the phone was restarted, it booted into Android system recovery <2e>. And I can't get out of it. I'm given these options:
reboot system now
reinstall packages
delete all user data
delete cache data
In addition, I have the following text in yellow:
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
-- Movi_check already executed!!...
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
If I select "reboot system now", I get to the same screen.
If I select "reinstall packages", I get to the same screen.
Would appreciate any help. Thank you!
Taking a shot in the blue but have you tried to click reinstall packages then when it brings you to the screen click reinstall packages again. Then this sshould get you into clockwork mod recovery which will give you a choice to reboot now and then it should worK. If it doesnt then do the same thing tthen once in cwr try clicking clear cache..if none oof these work a fresh odin usually does the trick =]
Sent from my SGH-T959 using XDA App
Thanks for your reply. Yes, I've tried doing "reinstall packages" multiple times and it always brings me back to the same screen. Same with clearing cache.
Re: "a fresh Odin" - I'm reading up about this now. I've figured out how to put my phone into Download mode. Is there a stock set of files for Odin that I should be using?
goodcough said:
Thanks for your reply. Yes, I've tried doing "reinstall packages" multiple times and it always brings me back to the same screen. Same with clearing cache.
Re: "a fresh Odin" - I'm reading up about this now. I've figured out how to put my phone into Download mode. Is there a stock set of files for Odin that I should be using?
Click to expand...
Click to collapse
Look at this thread and use the files in here to take you back to stock via Odin....then start over with your rooting, flashing, etc..
http://forum.xda-developers.com/showthread.php?t=848737
I followed the procedures in
http://forum.xda-developers.com/showthread.php?t=848737
The Odin process kept getting stuck on modem.bin... After trying a few times, I'm now unable to trigger download mode. Nor does the [ Phone < ! > Computer ] screen come up. It's all black - I fear the worst. Is there anything else I can try?
I don't want to say the B-word yet, but I don't know what else I can do.
I have a Verizon S4 ME7 and since ive rooted my phone i am unable to boot into recovery mode, but download mode works fine.
I followed the root steps here (http://forum.xda-developers.com/showthread.php?t=2380325) and i got supersu and root does work.
Then i installed CWM recovery following these steps (http://theunlockr.com/2013/07/30/ho...od-recovery-on-the-samsung-galaxy-s4-verizon/) but everytime i try to manually boot into recovery or through the CWM app, it gives me this error:
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : VZN
Successfully applied multi-CSC.
other notes: before the error the green android is loading then he tips over with a red triangle and the code appears, im confused on the problem i have went back to stock and then rooted again and same error again.
randiandi said:
I have a Verizon S4 ME7 and since ive rooted my phone i am unable to boot into recovery mode, but download mode works fine.
I followed the root steps here (http://forum.xda-developers.com/showthread.php?t=2380325) and i got supersu and root does work.
Then i installed CWM recovery following these steps (http://theunlockr.com/2013/07/30/ho...od-recovery-on-the-samsung-galaxy-s4-verizon/) but everytime i try to manually boot into recovery or through the CWM app, it gives me this error:
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : VZN
Successfully applied multi-CSC.
other notes: before the error the green android is loading then he tips over with a red triangle and the code appears, im confused on the problem i have went back to stock and then rooted again and same error again.
Click to expand...
Click to collapse
If you rooted ME7 , the God's don't want recovery. If you rooted MDK they do...go figure.
ME7 has no recovery at this point, just root..
Sent from my SCH-I545 using Tapatalk 2
dang....
Pixelation said:
If you rooted ME7 , the God's don't want recovery. If you rooted MDK they do...go figure.
ME7 has no recovery at this point, just root..
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
So, does that mean i cannot install custom roms?
randiandi said:
So, does that mean i cannot install custom roms?
Click to expand...
Click to collapse
Yep.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
****HELP!**** I am having the same issue but I am on MDK build...
I am having the same issue... I was having the same error but,now I get the cwm recovery successful flash in rom mgr, go to reboot, and it just sits on recovery loading in the corner on the Samsung unlock screen... It is just stuck everytime I try it.help! I want something besides this stock rom.
Specifications:
Sch-i5454 (rooted)
4.2.2
Vruamdk
Kernel: 3.4.0-562219
I was previously rooted with hyperdrive rom and me wanting to try something new with cynagenmod 12 nightlies and it was too many bugs especially bluetooth. I tried to go back to hyperdrive and was unable to...that's why I am in this mess.