Initially, this post was meant to fix people's phones after a bad restore from CWM, but now I'm changing it to be more general and pretty much be a guide for how to fix your phone from nearly any problem. The original reason for this post is this error:
Code:
-- bootmode=7 from cmdline...
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
--movi_checking done!...
# MANUAL MODE #
It was caused by a problem with /data and this guide helped fix that. Now that several other things have come along (leaks, voodoo, etc.) people are having a host of random errors show up with their phones. This guide will hopefully get you back to a working phone regardless of what is wrong with it. Take note though, that following this guide will delete all data not on the sdcard. So, with that being said, here is how you can fix your phone.
1. Download one of the packages below as well as the PIT file.
2. Open up Odin, click PDA, and select the package you downloaded
3. Click on PIT and select the PIT file that you downloaded.
4. Get your phone into Download mode.
4a. Pull out the battery, hold down on Vol Down, and plug in the USB Cable while still holding the button.
4b. After you are in Download Mode, put the battery back into your phone. This increases the reliability of flashing with Odin
5. Make sure your phone is recognized in Odin
6. Check the box for Re-partition (Odin will fail if you check this and don't use the PIT file) and un-check the boxes for Auto-Reset and F. Reset Time.
7. Press "Start" and flash the package.
8. After it is finished flashing, take the battery out, unplug the USB cable, put the battery back in, and start up what should now be a working phone.
Download descriptions. There are 3 files linked to below. The first is the PIT file, and required for this. The PIT file is the partition information table. It tells your phone where different packages go on the phone, as well as how big partitions are on the phone. Without this information, Odin cannot properly re-partition your device. The next two files are more or less the same and you will only need one of the two, not both (unless you want them just for fun). There is ED1, which is what the phone initially shipped with, and ED2, the update that was released just after the phone was. The ED1 package may be a little bit smaller for those that are concerned about download size as it is compressed. However, you will need 7-zip or similar to extract it after downloading. Also note that this cannot be done with Heimdall as Heimdall does not have the ability to re-partition your phone, thus, you need a Windows computer to be able to follow this procedure.
All packages are available here.
Sweet, as always thanks for the work/effort on this stuff. At least now we don't have to be AS concerned atm if a restore was done in CWR and someone hoses there device.
this work for anyone?
Updated this with what I believe to be the proper steps. I was in and out at work while papi was fixing his phone, and lost track of the exact files used, but some combination of the above Odin packages and the PIT should get you back to a working phone if you are having a problem.
Good sh|t man ... phone was bound to have growing pains.
papi92 said:
this work for anyone?
Click to expand...
Click to collapse
Unfortunately, I am trying to fix this very problem right now.
I was able to get rid of the error message with your method and I can now get into CWM again.. which is progress. I used the smaller file as it looks like the bigger one was corrupt for me (may just have been a bad dl on my end). I'm re downloading the full file now.
Anyway, I used odin. Selected the charge.pit and repartitioned. I allowed that to finish. I then restarted and flashed the smaller .md5 file. I then was able to reboot into CWM.. which is where I am now as the system just boot loops on the Samsung logo ATM.
Any words of wisdom to get me out of the boot loop would be great.. I'll check back later - hopefully with news that I fixed my phone.
trebores1 said:
Unfortunately, I am trying to fix this very problem right now.
I was able to get rid of the error message with your method and I can now get into CWM again.. which is progress. I used the smaller file as it looks like the bigger one was corrupt for me (may just have been a bad dl on my end). I'm re downloading the full file now.
Anyway, I used odin. Selected the charge.pit and repartitioned. I allowed that to finish. I then restarted and flashed the smaller .md5 file. I then was able to reboot into CWM.. which is where I am now as the system just boot loops on the Samsung logo ATM.
Any words of wisdom to get me out of the boot loop would be great.. I'll check back later - hopefully with news that I fixed my phone.
Click to expand...
Click to collapse
Can you flash anything in CWM? Or how about odin the Ed1 rooted package.?
hoppermi said:
Can you flash anything in CWM? Or how about odin the Ed1 rooted package.?
Click to expand...
Click to collapse
I'm going to try that next.. it's downloading now (slowly). It may just be me, but I can't get the full ED1_CWM_Fix.tar.md5 to flash at all. I have now downloaded it from multishare direct and rapidshare and both fail the same way (Write operation failed).
hoppermi said:
Can you flash anything in CWM? Or how about odin the Ed1 rooted package.?
Click to expand...
Click to collapse
And, yes - I was able to previously flash the ed2-debloat rom from CWM, but it wouldn't boot up... I may try that again while I'm waiting for the stock-ED1 root to finish downloading.
trebores1 said:
I'm going to try that next.. it's downloading now (slowly). It may just be me, but I can't get the full ED1_CWM_Fix.tar.md5 to flash at all. I have now downloaded it from multishare direct and rapidshare and both fail the same way (Write operation failed).
Click to expand...
Click to collapse
Pretty sure that papi flashed this http://forum.xda-developers.com/showthread.php?t=1085190 one the error message was gone, and he was good to go.
Hey after you flash the smaller package given by imnuts07 I flashed stock ed1 rooted thru odin and it worked.
Sent from my SCH-I510 using XDA Premium App
papi92 said:
Hey after you flash the smaller package given by imnuts07 I flashed stock ed1 rooted thru odin and it worked.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Yeah, that worked. It got rid of the error and I can now boot into stock recovery.. but I'm stuck in a droid eyeball bootloop now. Not sure what else to do. I factory reset everything. I think it's time to just return to the VZW store.
Don't return it. You got that far it can be restored. Try flashing altered beast thru odin o
Sent from my SCH-I510 using XDA Premium App
Also start up took about 10 minutes for me and make sure your phone still isn't on ext 4.
Sent from my SCH-I510 using XDA Premium App
Same here. Flashing altered beast fixed the problem and let me cwm flash debloatedv4. (4.1 seems really buggy)
Sent from my SCH-I510 using Tapatalk
papi92 said:
Also start up took about 10 minutes for me and make sure your phone still isn't on ext 4.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
I think I turned off ext4. In cwm I disabled the voodoo lagfix and the voice said that it was disabled. How else would I tell if it's off?
I tried your other suggestions too. Flashed altered beast, ed1 rooted, no luck getting past the bootup loop.
When you restored via Odin using the almost-everything.tar.md5, were you able to reboot and use your phone? I can't get that far. If I reboot it just hangs on the samsung logo. After that, I can flash altered beast or ed1-rooted and I get to the droid bootloop.
Trust me, I don't want to return it.. I'm sure there's a fix here somewhere.
You need to wipe data. You have too. And yes I got stuck at Samsung logo after. I had to flash stock ed1 rooted then wipe data
Sent from my SCH-I510 using XDA Premium App
trebores1 said:
I think I turned off ext4. In cwm I disabled the voodoo lagfix and the voice said that it was disabled. How else would I tell if it's off?
I tried your other suggestions too. Flashed altered beast, ed1 rooted, no luck getting past the bootup loop.
When you restored via Odin using the almost-everything.tar.md5, were you able to reboot and use your phone? I can't get that far. If I reboot it just hangs on the samsung logo. After that, I can flash altered beast or ed1-rooted and I get to the droid bootloop.
Trust me, I don't want to return it.. I'm sure there's a fix here somewhere.
Click to expand...
Click to collapse
To find out if lagfix is disabled run mount from a root terminal app, or adb shell mount if you're hooked up to your computer. If anything shows up as ext4, lagfix is still enabled. If it is all rfs/vfat/not ext4 then you're ok.
Progress has been made! I followed steps 1-8 on imnuts guide. On step 8, nothing happens(as it should). Rebooted into download mode, flashed almost-everything, rebooted, system hangs on samsung logo. Rebooted into download mode, flashed ed1-rooted. Rebooted, system boots into phone!
Now I get an error that my sim card is not supported or readable.. but at least I got back into the phone..
trebores1 said:
Progress has been made! I followed steps 1-8 on imnuts guide. On step 8, nothing happens(as it should). Rebooted into download mode, flashed almost-everything, rebooted, system hangs on samsung logo. Rebooted into download mode, flashed ed1-rooted. Rebooted, system boots into phone!
Now I get an error that my sim card is not supported or readable.. but at least I got back into the phone..
Click to expand...
Click to collapse
Did you activate another phone? I know someone w/ a TB who reactivated his Fascinate then wanted to switch back and his sim wouldn't work. Had to get a new one.
Sent from my SCH-I510 using Tapatalk
Related
I'm trying to flash my friend's Galaxy s 4g, but I'm having an issue with Odin failing to flash.
I originally used Vibrant 3g .pit and .tar files, not knowing it wouldn't work on the 4g model. Anyway, that semi bricked it, while still allowing it to get to the download mode.
So I figured I needed the "custom" .tar file to flash the 4g model. I booted up Odin and opened just the .tar that's in the noob guide. This time all I got from Odin is a red panel saying FAIL! It happened during the cache.rfs process. And now I get a new download mode screen. Before it used to be the android digging, now it's just an image of a phone and a computer with an exclamation mark in between the two.
When I get FAIL! on Odin, the progress bar on the phone freezes about 75% of the way.
So what am I doing wrong? Do I need a .pit file? Is it my computer? Should I try another computer? help me out please
I'm not sure about that second message you got, but did you make sure to open ODIN before flashing?
And do you also have the correct USB Drivers downloaded for your computer?
bustanut said:
I'm not sure about that second message you got, but did you make sure to open ODIN before flashing?
And do you also have the correct USB Drivers downloaded for your computer?
Click to expand...
Click to collapse
Yea, i had ODIN open before I connected the phone. And I made sure to install the correct drivers for it (It said "drivers installed successfully)
Another thing, is when I was trying to flash it thinking the regular vibrant 3g method would work, I had "Re-Partition" checked. Could that be part of the problem?
You're not supposed to have Re-Partition checked.
Refer to this guide to make sure you're doing everything right in the flashing process : http://forum.xda-developers.com/showthread.php?t=1001759
Well, I have been following that guide. Step by step.
But that was after I semibricked it.
Before, I thought using the method for rooting a vibrant 3g would work for the 4g model. I guess the "Re-partition" box was checked (before I started following that "Noobs guide") and that's why I'm having problems now.
The symbol you are now seeing on your phone means you have a currupt firmware. It was most likely caused by using the vibrants pit file. If you try everything else and it still doesn't work. You may have to wait until we either have a working pit. But follow the directions on the Odin flashing instruction and keep trying.
Good luck
Sent from my GT-I9000 using XDA Premium App
So, there's nothing I can do now besides keep trying? It's not my phone though... my friend was expecting it back today.
Is there a way I can get to the recovery menu and download somebody's nandroid backup to restore mine?
bryanoid said:
So, there's nothing I can do now besides keep trying? It's not my phone though... my friend was expecting it back today.
Is there a way I can get to the recovery menu and download somebody's nandroid backup to restore mine?
Click to expand...
Click to collapse
Sorry bud. Cwm doesn't work that way yet. And even so, I don't think you can even get into recovery mode with your problem. When you used the vibrant pit file you formatted the phone to be like the vibrant which its not. Its very similar, but different enough to cause issues.
Sent from my GT-I9000 using XDA Premium App
Can anyone help please? I was running stock ED1 and decided to update to EE4. I put Voodoo lagfix on, then flashed the EE4 update that was in the general forum through recovery as an update.zip. It stopped about halfway through for some reason, leaving me with an "unknown" baseband and thus, no way to get a signal. All attempts to flash different radio updates failed. So, I decided to flash everything over. I flashed the stock ED1 through Odin, but it keeps saying the MD5 checksum is invalid, so I flashed Altered Beast. This got me clockword mod, but still no baseband. Finally, I tried to flashed debloated EE4 through clockword and now, I'm stuck at the Samsung screen, with no way to get into recovery. Any suggestions for my noobness? :/ I can still get it to connect to Odin.
Ok, quick update. I got Altered Beast reflashed. CWM is still on there. I'd like to get back to stock, ED1, ED2, EE4; I don't care which, as long as I have a working baseband. Suggestions?
try redownlolading ed1 because the md5 has to do with the file itself not the phone. Then connect to wifi and update to ed2. after, try flashing the update .zip thats from the forums while you are stock, no custom recovery or anything other than root ed2. if none of this works, then you probably burnt out your sim card like i did accidentaly by activating my old droid x. so if you did burn the sim card, go to best buy or verizon or the costco wireless booth and have them activate a new sim card for you. this happened to me where i couldnt get data or anything and i got a new sim card and pow! it worked. try my initial instructions first. and make sure you are using the PDA button in odin
empyreandance said:
Ok, quick update. I got Altered Beast reflashed. CWM is still on there. I'd like to get back to stock, ED1, ED2, EE4; I don't care which, as long as I have a working baseband. Suggestions?
Click to expand...
Click to collapse
whenever you flash an update you need to be completely stock thats including the kernel
i would disable lag fix then flash ED1 downgrade and try to update if it doesnt let you i would unroot and bring your phone into VZW tell them the update failed and left you with unknown baseband.
you may be a good test subject to try out his idea on flashing a radio , if he is there yet
also you posted in the wrong section
rami98 said:
try redownlolading ed1 because the md5 has to do with the file itself not the phone. Then connect to wifi and update to ed2. after, try flashing the update .zip thats from the forums while you are stock, no custom recovery or anything other than root ed2. if none of this works, then you probably burnt out your sim card like i did accidentaly by activating my old droid x. so if you did burn the sim card, go to best buy or verizon or the costco wireless booth and have them activate a new sim card for you. this happened to me where i couldnt get data or anything and i got a new sim card and pow! it worked. try my initial instructions first. and make sure you are using the PDA button in odin
Click to expand...
Click to collapse
you cant get the update over wifi im pretty sure he will need to download the update.zip files for each update if he doesnt already have them
Hah im trying to figure out how to get outta bootloop forgot to disable voodoo odin'd back to ed2 w/root and now i have bootloop..
Sent from my SGH-I897 using XDA App
Ok, I'm still getting a MD5 mismatch on the third try with the stock ED1 file. any other ideas?
mv1luv said:
Hah im trying to figure out how to get outta bootloop forgot to disable voodoo odin'd back to ed2 w/root and now i have bootloop..
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
flash altered beast, then boot up , boot into recovery disable lagfix then try again
empyreandance said:
Ok, I'm still getting a MD5 mismatch on the third try with the stock ED1 file. any other ideas?
Click to expand...
Click to collapse
redownload the file
i've done that three times today. i think something else is going on
I would suggest reinstalling the Samsung drivers for the Charge, then open Odin, use a different USB port and try again. I had a lot of issues with flash ED1 and one of the ways I found worked around this (for me) was to make sure the drivers were messed up.
empyreandance said:
i've done that three times today. i think something else is going on
Click to expand...
Click to collapse
where are you downloading the file from?
RaptorMD said:
I would suggest reinstalling the Samsung drivers for the Charge, then open Odin, use a different USB port and try again. I had a lot of issues with flash ED1 and one of the ways I found worked around this (for me) was to make sure the drivers were messed up.
Click to expand...
Click to collapse
MD5 mismatch happens when a file is corrupt or not fully complete
ok, good news (sort of). the md5 mismatch was being caused by the way chrome was naming the multiple instances of the download. I renamed the file and got back to stock ED1. still no signal, but i got the pop up saying i had a system update waiting, i just have to wait for the battery to charge a bit. I'll check back in soon. in the meantime, thanks for all the help and patience everyone.
ok, installing the update didn't help. is it possible my sim card is fried?
empyreandance said:
I put Voodoo lagfix on, then flashed the EE4 update
Click to expand...
Click to collapse
wait i thought if you wanted to flash to stock you want the Voodoo lagfix off? i think your problem might be that your flashing non voodoo kernals to a system that has voodoo on i dont think you should do that, try flashing a voodoo kernal maybe instead of the stock stuff
Sent from my Transformer TF101 using Tapatalk
well, a trip to verizon and trying new sim cards didn't fix it. guess i'll need to wait for a replacement.
I flashed the 0817_charge_recovery.tar.md5. I didnt see that it worked and then went back into download, thru Odin, tried to flish cwm_Recovery4008.tar. Got a fail and now when i try to turn on it just shows an icon of a phone with a yellow triangle exclamation point between that and a computer icon. it still goes into download mode with volume down and usb connection but it wont flash the default VZW rom back.
Suggestions?
Battery in or out?
battery in = (phone) ... ! ... (cpu)
battery out = can still go into download mode
Did you come from another rom? I think if you want to flash back to stock from another rom via odin you need to also flash the pit file. At least thats what I had to do.
Sent from my SCH-I510 using XDA App
No i had reverted back to the stock (pentafive ee4 full factor tar).
Have you tried everything from imnuts Fix your Phone thread?
http://forum.xda-developers.com/showthread.php?t=1111486
Ya i got a fail for that as well on Odin. Also tried the Samsung PST and it said error download there as well
DRO1DZ1LLA said:
Ya i got a fail for that as well on Odin. Also tried the Samsung PST and it said error download there as well
Click to expand...
Click to collapse
Are you keeping the battery out during the entire process? You're using the PIT too with the Re-partition box checked (unchecked Auto Restart and F. Time)?
I left the battery in cause in step 4b he says to but anyways it worked. the first time i tried i was using the ed2 file cause for some reason the ed1 link wasnt loading. then i realized i had that file already from somewhere else and used that and it went through
DRO1DZ1LLA said:
I left the battery in cause in step 4b he says to but anyways it worked. the first time i tried i was using the ed2 file cause for some reason the ed1 link wasnt loading. then i realized i had that file already from somewhere else and used that and it went through
Click to expand...
Click to collapse
Nice, bro! Glad to hear you're back up!
thanks for all the help tho! so should i not try to re-root/rom/kernel this ***** or what?
DRO1DZ1LLA said:
thanks for all the help tho! so should i not try to re-root/rom/kernel this ***** or what?
Click to expand...
Click to collapse
Right now, your best bet is to apply whatever system updates there are. If your phone doesn't get you up to EE4 on its own, then you should follow imnuts' instructions here: http://rootzwiki.com/topic/10202-how-to-prepare-for-the-gb-ota/
At some point today, someone will be able to confirm whether the update.zip (leaked) is truly 100% identical to the update.zip that Verizon is pushing out for EP4. If it is, then we'll be safe update to EP4 ahead of the OTA, root, restore any backups, and apply working EP4 themes. I'm anxiously awaiting the ability to depoop my phone--rolled back to stock EE4 last night and have hated my phone ever since!
Haha same. I returned initially for the same reason and then was so sick of it i pushed ahead and messed it up. Still haven't gotten the update tho
Happened to me once. Used stock ee4 odin with the charge .Pit file imnuts posted and it brought me back to stock
Sent from my SCH-I510 using Tapatalk
I recently bought a charge off of ebay and it came in and I noticed it had an Gmail account still synced with it.
Ok I thought, I'll just remove it. I go to remove the account and it says that "some apps require this account to remove this account you need to reset phone to factory defaults".
Alright so I go to do that and the phone reboots after I wiped data/cache and I go to add my account and realize that the other account is STILL THERE. So I do the wipe a few more times and still stays there.
By this time I figured I would root the phone and install CWM and try and wipe data that way. That still didn't work and I just started trying to get a stock rom back installed and finally I did. Except the ACCOUNT WAS STILL THERE, but now I'm getting a ton of FC's ranging from google apps to other processes. I've tried to install different rom's/CWM's/kernels in ODIN on my Window's laptop and I would alwasy just get the talking voice saying things like "converting data partition" and then it would just boot back into the stock but keep force closing.
I am now using my Macbook Pro on spring break and am trying to fix this using Heimdall but i've still had no luck. Is there anyone that can help me with this?
Farbulus said:
I recently bought a charge off of ebay and it came in and I noticed it had an Gmail account still synced with it.
Ok I thought, I'll just remove it. I go to remove the account and it says that "some apps require this account to remove this account you need to reset phone to factory defaults".
Alright so I go to do that and the phone reboots after I wiped data/cache and I go to add my account and realize that the other account is STILL THERE. So I do the wipe a few more times and still stays there.
By this time I figured I would root the phone and install CWM and try and wipe data that way. That still didn't work and I just started trying to get a stock rom back installed and finally I did. Except the ACCOUNT WAS STILL THERE, but now I'm getting a ton of FC's ranging from google apps to other processes. I've tried to install different rom's/CWM's/kernels in ODIN on my Window's laptop and I would alwasy just get the talking voice saying things like "converting data partition" and then it would just boot back into the stock but keep force closing.
I am now using my Macbook Pro on spring break and am trying to fix this using Heimdall but i've still had no luck. Is there anyone that can help me with this?
Click to expand...
Click to collapse
Okay so it seems like you're sorta familiar with this kind of stuff so this shouldn't be too much trouble for you. You're going to need to go back to stock EP4D ROM and re-partition your device. Here is the link to where you can solve this problem: http://forum.xda-developers.com/showthread.php?t=1111486
You're going to have to use Odin (You're going to need Windows to run Odin) fit this because Heimdall just doesn't cut it and personally I've never used it. Get Odin 1.82, it works really well with the Charge. Download stock EP4D and also the charge.pit file from the posted link. Place stock EP4D md5 file in PDA in Odin and charge.pit in PIT. Make sure you have Re-Partition checked and Auto-Reboot and F.Reset Time UNCHECKED and press start. It will reconfigure everything and basically give you a brand new phone on the inside. Hope this helps and if you have any more questions just go back to the link to Imnuts' thread I posted.
Sent from my SCH-I510 using XDA App
Quick question
ewh1292 said:
Okay so it seems like you're sorta familiar with this kind of stuff so this shouldn't be too much trouble for you. You're going to need to go back to stock EP4D ROM and re-partition your device. Here is the link to where you can solve this problem: http://forum.xda-developers.com/showthread.php?t=1111486
You're going to have to use Odin (You're going to need Windows to run Odin) fit this because Heimdall just doesn't cut it and personally I've never used it. Get Odin 1.82, it works really well with the Charge. Download stock EP4D and also the charge.pit file from the posted link. Place stock EP4D md5 file in PDA in Odin and charge.pit in PIT. Make sure you have Re-Partition checked and Auto-Reboot and F.Reset Time UNCHECKED and press start. It will reconfigure everything and basically give you a brand new phone on the inside. Hope this helps and if you have any more questions just go back to the link to Imnuts' thread I posted.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Before I do that, which will be in a few days as I'm without a windows computer until at least wednesday. I am able to get into CWM. I installed a TweakStock but upon boot I get FC's like crazy. One after another continuously. I can't do anything. Is there anything I can do to get this working without using Odin? Thank you so much for your help as well.
Farbulus said:
Before I do that, which will be in a few days as I'm without a windows computer until at least wednesday. I am able to get into CWM. I installed a TweakStock but upon boot I get FC's like crazy. One after another continuously. I can't do anything. Is there anything I can do to get this working without using Odin? Thank you so much for your help as well.
Click to expand...
Click to collapse
No problem man I'm glad to help. If you want you can try a full data wipe. Boot into CWM and mount everything i.e. \system, \data, the whole nine yards and then wipe data/factory reset, and also wipe cache partitions and Dalvik cache. Then install whatever ROM you have available and see if that works. Otherwise you're SOL until you get a Windows computer and can Odin back to stock and re-partition everything.
EDIT: Just to clear something up, to mount everything scroll down to 'mounts and storage' in CWM.
Sent from my SCH-I510 using XDA App
Yeah, you need to run the pit file. Might be best to go back to original froyo + pit.
Tweakstock v1.4, XDA Premium
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Hindle1225 said:
Yeah, you need to run the pit file. Might be best to go back to original froyo + pit.
Tweakstock v1.4, XDA Premium
Click to expand...
Click to collapse
Froyo won't be necessary, just take the GB OTA file, the PIT, and use SamsungPST in bootcamp.
Sent from my SCH-I510 using xda premium
No bootcamp :/
kvswim said:
Froyo won't be necessary, just take the GB OTA file, the PIT, and use SamsungPST in bootcamp.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Looks like I'll be waiting till wednesday. I don't have bootcamp installed anymore because my wifi was always wonky. oh well.
Tried it.
kvswim said:
Froyo won't be necessary, just take the GB OTA file, the PIT, and use SamsungPST in bootcamp.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
I tried this, still didn't work. I've tried using both ODIN and PST.
You're not the only one.
http://forum.xda-developers.com/showthread.php?t=1534688
Sent from my SCH-I510 using xda premium
SOL.
kvswim said:
You're not the only one.
http://forum.xda-developers.com/showthread.php?t=1534688
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
So it looks like i'm SOL. Great.
Farbulus said:
So it looks like i'm SOL. Great.
Click to expand...
Click to collapse
Make sure you Odin Tweakstock and flash cwm imosey kernel 4.0 (http://rootzwiki.com/topic/3426-kernel-gb-imoseyon-kernel-stock-repacked-v400-11611/ ) installed on your phone. Download and install "voodoo control app". In this app go into advance and put 2 checks in for ext4 settings, reboot your phone and report back the results.
buhohitr said:
Make sure you Odin Tweakstock and flash cwm imosey kernel 4.0 (http://rootzwiki.com/topic/3426-kernel-gb-imoseyon-kernel-stock-repacked-v400-11611/ ) installed on your phone. Download and install "voodoo control app". In this app go into advance and put 2 checks in for ext4 settings, reboot your phone and report back the results.
Click to expand...
Click to collapse
It's actually not Voodoo Control anymore. Supercurio updated it to just Voodoo Sound.
Sent from my SCH-I510 using XDA
No luck.
buhohitr said:
Make sure you Odin Tweakstock and flash cwm imosey kernel 4.0 (http://rootzwiki.com/topic/3426-kernel-gb-imoseyon-kernel-stock-repacked-v400-11611/ ) installed on your phone. Download and install "voodoo control app". In this app go into advance and put 2 checks in for ext4 settings, reboot your phone and report back the results.
Click to expand...
Click to collapse
This didn't work. I installed TweakStock and the kernel booted up and I got instant force closes that didn't allow me to do anything.
Did you ever try the first froyo build with pit?
Charge-TwStock 1.4 / Bought this app!
Hindle1225 said:
Did you ever try the first froyo build with pit?
Charge-TwStock 1.4 / Bought this app!
Click to expand...
Click to collapse
Yes, I did. I've heard of "spamming the pit file". Does anyone know how to do this?
Farbulus said:
Yes, I did. I've heard of "spamming the pit file". Does anyone know how to do this?
Click to expand...
Click to collapse
I think he means he just tried it over and over again
Charge-TwStock 1.4 / Bought this app!
Farbulus said:
This didn't work. I installed TweakStock and the kernel booted up and I got instant force closes that didn't allow me to do anything.
Click to expand...
Click to collapse
I think your partition is mess up due to ext4. I have an idea, why don't you flash the new CM9 ICS rom, this will auto reconvert yours to ext4. You have nothing to loose at this point. Make sure you MOUNT SYSTEM before flashing.
http://rootzwiki.com/topic/19688-romkangicsiml74k-cm9-ics-port-for-droid-charge-build10306/
Good luck.
buhohitr said:
I think your partition is mess up due to ext4. I have an idea, why don't you flash the new CM9 ICS rom, this will auto reconvert yours to ext4. You have nothing to loose at this point. Make sure you MOUNT SYSTEM before flashing.
http://rootzwiki.com/topic/19688-romkangicsiml74k-cm9-ics-port-for-droid-charge-build10306/
Good luck.
Click to expand...
Click to collapse
I flashed it and now its been flashing the ICS boot screen for 10+ minutes. any ideas?
Farbulus said:
I flashed it and now its been flashing the ICS boot screen for 10+ minutes. any ideas?
Click to expand...
Click to collapse
wait for 1/2 hrs if still boot screen, pull the battery and put back the battery see if it boot correctly.
Ok so I've been rooted and unlocked for a while now, but stayed with the stock rom as when I tried out Synergy Nightlies it gave me some errors. So I went to try out CleanRom 2.1, people liked it and I didn't notice any flashing errors. So I flashed it through CWM 6.0.1 and it gave me the yellow exclamation mark saying I had unauthorized data on my phone. So I followed the sticky on how to unbrick my phone using the 2 boot loaders and the root66 stock image. My issue is that when running the root66 stock image through Odin it fails at _XmitData_Read, which seems to be somewhere in system.img.ext4. I've tried rebooting the computer, the phone, Odin, it just doesn't work. So when I reboot my phone after the failure I get Odin auto loading saying:
Odin Mode
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Then an image of a phone, 2 dots, a yellow exclamation, 2 dots and a computer are shown with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Anyone able to help me?
can you still get to odin mode? also if you have kies installed on the computer erase it.
kidhudi said:
can you still get to odin mode? also if you have kies installed on the computer erase it.
Click to expand...
Click to collapse
Kies isn't installed on the computer and yes I am still able to get into Odin Mode.
I'm under the impression that "unauthorized software" message comes from the locked bootloader (if I'm wrong about that someone plese correct me.)
Sounds like you're functional enough to be able to Odin back to stock and go from there - that's what I'd try. See the stickied thread in the Q&A forum.
I would run the FULL VRALF stock image through ODIN to return to stock. That is always the safest way out of a sticky situation.
Thanks guys, according to another post the version of EZ-Unlock I used most likely gave a false report and never actually unlocked my phone. The problem with going back to stock, which if what I'm trying to do, is that it fails.
Could be an USB issue - an intermittent connection would be most likely to cause problems while sending the system partition since that's the biggest. I've had problems using adb from time to time if I plug into one of the front-panel ports on my PC but no trouble with one on the back.
Maybe try switching ports or try a different cable ...
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Strange.... i was able to flash syergy on thefirst try. Never used odin during the whole process....
If youre rooted you need to make sure you have a custom recovery in place like cwm or twrp. Make sure you make a nand-backup.
I used casual to flash unsecure bootloader, with that and recovery in place you should be able to flash roms without any hitches....
I could never find a comprehensive guide on using odin so i never got around to testing it
kintwofan said:
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So far I've tried 3 different USB cables and both a desktop, both front and back ports and a laptop, each one fails on the write of XmitData under system.img.ext4
I had a custom recovery installed and Odin is only being used to get me back to a stock rom, otherwise I did all my flashing under CWM 6.0.1 or twrp. I think the whole fake unlocked bootloader just hard bricked the software.
EDIT: Come to think of it I remember waking up to my phone in download mode. I think Verizon tried to install the update to my phone while I was sleeping. Granted it failed at the end, but I'm wondering if that did something to brick me now.
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yea, I'm currently downloading at the speed of slug the newest update from the forums, will probably just redownload at home, since it's going to take over an hour >.<
EDIT:
Does anyone have a link for an older EZ-Unlocker, that is known to work, so that I don't get this problem yet again.
FIXED!
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
LlirasChosen said:
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
Click to expand...
Click to collapse
I personally suggest not using the app if you already had trouble. Just root your phone using the Debug Root method in Development, download the aboot.img from Adam Outlers thread HERE to your phone, and run the commands at the very bottom in Terminal Emulater app (from the market).
That way you know for sure your bootloader is unlocked. This is what I have done and never had an issue.
Edit: Glad you got your issue resolved!