Related
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
I'm making this post because the fix, and the cause for the problem seems to be different.
My friends captivate was rooted with the latest cm7 rom for about a month now, and just last night after he performed a reboot a message that stated{ phone.android.not.found} started to flash on, and off it wouldn't allow him to do anything.
I booted his phone in to recovery to flash his backup but it failed, after I did another reboot. It just froze on the white at&t world phone screen. I've tried to boot in to recovery by using all button methods. Odin3 failed to recognize the phone. Drivers are installed.
its a I897 version. I really don't know what my next step should be.
In hindsight I should have just pulled the sim and put it back in. I think that would have fix the warning sign.
I'm going to try the jig option today, but any other advice would be helpful.
The backup in question: was it a 2.2 backup?
Sent from my Inspire 4G
I'm not 100% sure but I think it was just a stock root 2.1 back up.
mentalchaos03 said:
I'm not 100% sure but I think it was just a stock root 2.1 back up.
Click to expand...
Click to collapse
Sounds like you need to flash a stock ROM with Odin. If you tried to load rfs based ROM over the cm7 file system (I think its a combination of ext4 and yaffs), it won't work.
mrhaley30705 said:
Sounds like you need to flash a stock ROM with Odin. If you tried to load rfs based ROM over the cm7 file system (I think its a combination of ext4 and yaffs), it won't work.
Click to expand...
Click to collapse
also, kernels/modems dont backup on nandroids, therefore they dont restore either
OP, you are on a 2.3.3 cm7 kernel with a 2.1 rom
ODIN flash a 2.1 kernel
done
So I finally got my jig in. so it goes in to boot mode which is awesome, but odin still won't recognize the phone. I've tried 3 different computers.
mentalchaos03 said:
So I finally got my jig in. so it goes in to boot mode which is awesome, but odin still won't recognize the phone. I've tried 3 different computers.
Click to expand...
Click to collapse
try heimdall. its better
mentalchaos03 said:
So I finally got my jig in. so it goes in to boot mode which is awesome, but odin still won't recognize the phone. I've tried 3 different computers.
Click to expand...
Click to collapse
Make sure you are using a USB port on the back of the PC and/or is on the main board.
Sent from my SGH-I9000 using XDA App
I took my phone from stock, unrooted, flashed new kernal, and then put on a new ROM, and everything worked fine.
I needed to send my phone back under warranty (bluetooth hardware isn't functioning), so I tried to flash the backup of my kernal in hopes of walking it back to stock. When my phone rebooted I'm in the boot screen and unable to re-boot.
If I download the original stock ROM such as http://forum.xda-developers.com/showthread.php?t=1183413 will I be able to flash it from this boot screen? It wouldn't let me install the new ROM I had in my root, probably because it wasn't the correct kernal.
After that, could I use this http://forum.xda-developers.com/showthread.php?t=1333423 Back-To-Stock Heimdall One-Click to take my phone back to true stuck condition?
Sorry for the new questions. I've searched the forum, just not sure which option to chose and don't want to brick a phone.
Thanks,
-Rob
That one you pointed out for ODIN is not a stock ROM; it was a leaked version. I'm not sure what screen you're stuck on, though. Can you get the phone into download mode? If so, go with the Fully Back-To-Stock UVKJ6. That puts the phone at stock 2.3.6 (KJ6) and you should be fine.
stephen_w said:
That one you pointed out for ODIN is not a stock ROM; it was a leaked version. I'm not sure what screen you're stuck on, though. Can you get the phone into download mode? If so, go with the Fully Back-To-Stock UVKJ6. That puts the phone at stock 2.3.6 (KJ6) and you should be fine.
Click to expand...
Click to collapse
stephen_w,
Thanks for your quick reply, much appreciated, and what was listed above worked flawleslsly.
Thanks,
-Rob
Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
VyCariously said:
Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
Click to expand...
Click to collapse
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
qkster said:
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
Click to expand...
Click to collapse
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
VyCariously said:
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
Click to expand...
Click to collapse
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
That does remove root access. However, root isn't really necessary, at least for the stock ROM, if you have no intentions of staying stock. The ROM .zips you'll subsequently flash are pre-rooted. After you Heimdall back to stock, and flash it again with "flash bootloaders" selected, then use Heimdall to flash this kernel:
http://d-h.st/6KA
That'll flash both a new kernel and CWM Red recovery. It'll take a few minutes to boot up the first time, as it's installing the lagfix. Once it boots up, just shut it down and boot back up in recovery. From there, you can do whatever you need to do.
VyCariously said:
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
Click to expand...
Click to collapse
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
qkster said:
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse
Thanks guys
It's been a crazy busy week and I just didn't have time to deal with the phone. I've been dealing with stock gingerbread. It's getting kind of annoying, though, it seems less stable than the custom ICS that I had on it before. Not sure when I'm going to have time to play with it again and try to get it to where I want it. I think I'm going to try to totally wipe all of the old stuff out of the memory before I do it again, though. There's something that wasn't allowing me to do what you guys are telling me to do successfully. I'm also thinking of finding a GS2 and just selling the Infuse, not because of my confusion, but because the GS2 was what I was originally looking for anyway.
I'll try to get this one set up first, though, as it's just a matter of me being obsessive about it.
qkster, I'll look into the JB, too, lol.
qkster said:
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
XperiaNeoVNoob said:
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
VyCariously said:
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
Click to expand...
Click to collapse
No probs...
:thumbup:
Sent from my MT11i using xda app-developers app
aight so ive searched and searched for all kinda different methods. and done all of them. is it possible to have a permanent brick?
heres the story. i had been running cm10 for prolly 4 or 5 months. no problems. i wanted to check out liquid smooth rom. so i flashed it. no problems. had been running it for a month or so then one day at work when i went on break my network was gone. my apn's were deleted. came home inspected some more and my imei was unknown as well as baseband and many others were unknown. i took it back to stock many times using. gtg method. using heimdel. using odin. with different stock files. from different websites. including xda. i have tried just about everything to re do the phone. including going back to cm10. and other known working roms. ive *#*#4636#*#* and manually switched to gsm which wont change when i click it it still says unknown.
i dont belive it is a rom problem. i have been overclocked 1300mhz. what else is out there can i try. \
\
any help will be very appreciated
Have you by chance odined back to stock then reupgraded to JB? If not I can get you the necessary steps to do so...let me know
Sent from my SGH-I997 using xda premium
FauxAffliction said:
Have you by chance odined back to stock then reupgraded to JB? If not I can get you the necessary steps to do so...let me know
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
yea i went to stock and back to cm10. still nothing. buttt now im unable to do any kinda flashes. im on rooted 2.3.6 threw odin. and no matter what i flash it will say somthing on the lines of failed to find file signature or what ever that code is. i tried changing the cwm in different ways still wont get off the what is it 2.5.2 cwm blue. ive basicly gave up. it seems its to far bricked or whatever the case may be
im sorry i need to correct that. i have not been able to flash to any other roms. i didnt go to stock and then cm10, due the the signature deal on cwm. i was thinking of another time i had problems. so no i have no been able to go to jb after the imei has went unknown
Did you flash a custom kernel to get cwm after going back to stock?
andros11 said:
Did you flash a custom kernel to get cwm after going back to stock?
Click to expand...
Click to collapse
im in able to flash anything.....
really? no one can help me?
Are you trying to flash through Odin? Or through CWM?
Sent from my SGH-I997 using xda premium
psal217050 said:
Are you trying to flash through Odin? Or through CWM?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
dont know how to flash a cwm threw odin. i tried loading a cwm threw rom manager and manually
kritz84 said:
dont know how to flash a cwm threw odin. i tried loading a cwm threw rom manager and manually
Click to expand...
Click to collapse
but im pretty sure the problem isnt with cwm im more interested in why and how to the imei isnt known and how to fix this problem if theres a cure
Download a heimdall one-click or odin back to stock pack. Open either one up and put your phone in download mode:
- turn off and have the usb cable connected to the pc.
- remove and reinsert battery
- hold both volume buttons and connect usb. Phone should now boot into download mode.
Run program and you will be good. Then look for entropy's dd kernel and flash it in download mode to get cwm.
andros11 said:
Download a heimdall one-click or odin back to stock pack. Open either one up and put your phone in download mode:
- turn off and have the usb cable connected to the pc.
- remove and reinsert battery
- hold both volume buttons and connect usb. Phone should now boot into download mode.
Run program and you will be good. Then look for entropy's dd kernel and flash it in download mode to get cwm.
Click to expand...
Click to collapse
i guess u didnt read my first post. ive already done that. ive done many things....
but anyway weirdest thing just happend. i have been using my phone via wifi. so its been on a while without a sim card inside of it.
\
i noticed i had signal bars. i looked at the imei and its was a number. it was a different iemi then what its supposed to be but there was a imei. baseband was still unknown but anyway i shut the phone done and inserted my sim card. btw its a straight talk sim. and restarted it now im back to unknown imei......
ok so im back on cm10. before i was on cm10 its was giving me the imei which wasnt my original imei. i guess cuz i flashed a efs.tar. but anyway i was able to make a phone call. now im flashed on cm10. and no imei no baseband nothin. i tried flashing the efs again with odin and still nothing. when i do the *#*#4636#*#* it still wont let me switch to gsm. and i cant add a apn.
kritz84 said:
ok so im back on cm10. before i was on cm10 its was giving me the imei which wasnt my original imei. i guess cuz i flashed a efs.tar. but anyway i was able to make a phone call. now im flashed on cm10. and no imei no baseband nothin. i tried flashing the efs again with odin and still nothing. when i do the *#*#4636#*#* it still wont let me switch to gsm. and i cant add a apn.
Click to expand...
Click to collapse
odin or heimdall back to stock.
follow andros11's guide on how to flash jb
he spent the time to write the guide; spend the same amount to time to read the guide
Seems IMEI was kidnapped about a month after Liquid
Ironically, I seem to have EXACTLY the same issue that this original poster has. I have been flashing my Infuse for a little over a year now and I Flashed Liquid, I'd say about 3 weeks ago, maybe end of November. Everything has been smooth sailing. About a 2 days ago I started noticing that my network would just drop - for no reason. But at first it came back. Ok, no problem, probably just a glitch. However yesterday morning it happened again and then I was without the use of data for most of the day until around 6pm. It came back but the bars were grey but I was able to make a phone call. Once I made another call it did not go through, I tried to hangup and it just hung there. there was nothing I could do to get it to hang up. Rebooting the phone resulted in no bars at all. Nothing, nada, ziltch. So last night I reflash it a couple times and notice that there was an update to Liquid (2.1 beta). cool. I wipe, flash 2.1b and it is beautiful. EXCEPT for the fact that I have no network. wifi works fine, but no carrier whatsoever. GRRRR. I decided to back every thing up (have done so several times in the past), stock back down to 2.3.6. Barebones and all it all looked great until I hung up the phone... Same thing. So I went all Rambo on the phone, wiped it down to the very last compound. AT&T wouldn't know the wiser if they took it from me. Master Reset, wiped files, data, I think I took an IC out with all of the wiping I did... Result? No IMEI, circle with the slash. Upset, disappointed and dejected I slumped back to XDA (after I went on Craigslist feeling my phone was broke) to see if I missed anything. That was where I found some links about missing IMEI. To make a long story short, I DO have an old copy of EFS thanks to QKSTER, but I have no idea how to restore. I swear I have been on this since 6:30am and just now am I finding these threads. Must have gone through about 50 others... Sigh. BTW, along the way of my flashing experience today, my network came back temporarily, but I have not relied on it because I knew it would leave me. Just don't know how to use Heimdall to restore. To make a long story short, using Windows, could someone please help me with how to restore my EFS to see if this would solve my dilemma?
808
Dnice808 said:
To make a long story short, I DO have an old copy of EFS thanks to QKSTER, but I have no idea how to restore. I swear I have been on this since 6:30am and just now am I finding these threads. Must have gone through about 50 others... Sigh. BTW, along the way of my flashing experience today, my network came back temporarily, but I have not relied on it because I knew it would leave me. Just don't know how to use Heimdall to restore. To make a long story short, using Windows, could someone please help me with how to restore my EFS to see if this would solve my dilemma?
808
Click to expand...
Click to collapse
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
Then put it into download mode.
Use the heimdall 1 click uclb3 and flash it once, then without closing heimdall, check the bootloader box and flash it again.
After this, check your imei and band. If it works, no further back up is needed.
If you're still missing the imei, you can flash one of the gb kernel in the second post to get cwm.
Then use the root pack in post #2,
http://forum.xda-developers.com/showthread.php?t=1629079 to install root and su.
install a root tool like root explorer (remember to toggle the r/o r/w) or adb and copy the /efs into the phone's root efs folder,
reboot
check the baseband.
you can also check this thread
http://forum.xda-developers.com/showthread.php?t=1895500
qkster said:
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
So it is in the .tar format that your script backed it up in. Finding another link on the we (which he also linked back to XDA, http://forum.xda-developers.com/showthread.php?t=1264021 I was able to take my backup (that I used with your script) and follow his steps -mostly- (my/your backup had a 'root' folder that had the nv_data.bin file in the afs/settings folder while the instructions did not mention that. I followed the backup location settings (which in turn was also the same as the default that I had backed up)) and replace the EFS folder. It still did not restore it in any flash image just like that. Still had the the circle w/slash. However while I was still searching and typing out that loooong last passage I wrote, my phone network came back for a little while. I know this because I began receiving a bunch of texts. I was able to make a phone call. But it still happened again when I made another, it did not go through and when I hung up, it just stayed there looking at me with its grey, blank look. Even killing the phone app did not work. I rebooted back to the same drama.
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
I actually was on 2.3.6 using your posts, first the basic rooted flash having to then using the Entropy kernel and then I did the lazy flash that was already rooted and just having to add the vold file to /system/etc/blah/blah. I do want to add that I DID have wifi active at this time and it may not be associated, but the first poster did mention he felt it may have had something to do with it. With wifi on, after awhile of me NOT looking at the phohe (actually doing so made me want to HULK SMASH), the network came on and my texts came in. I was able to look in settings and see ATT, and my IMEI. I was almost finished with my passage to you so I decided to update to Liquid 2.1 beta, but moving up to JB, then to LiquidSmooth. Of course doing so I got the circle w/slash, but wifi started restoring my apps.
Earlier I mentioned that I did a whole rubba dub dub, meaning I did do the /settings/privacy -reset thingy, wiping the phones carcass. I will do it again (at this point nothing to lose), following everything you ask to a 'T'.
808
Click to expand...
Click to collapse
qkster said:
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
Then put it into download mode.
Done.
Use the heimdall 1 click uclb3 and flash it once, then without closing heimdall, check the bootloader box and flash it again.
Done
After this, check your imei and band. If it works, no further back up is needed.
Sigh, did not do a darn thing. Circle w/slash.
If you're still missing the imei, you can flash one of the gb kernel in the second post to get cwm.
Done.
Then use the root pack in post #2,
http://forum.xda-developers.com/showthread.php?t=1629079 to install root and su.
install a root tool like root explorer (remember to toggle the r/o r/w) or adb and copy the /efs into the phone's root efs folder,
reboot
check the baseband.
Went in Root Explorer, did the toggle, deleted the contents of efs then copied the contents of my backup into there. Rebooted. Nada.
you can also check this thread
http://forum.xda-developers.com/showthread.php?t=1895500
I then was going to try the other link using Odin, but I cannot get Odin to see my phone. I read some thread talking about if I use Heimdall I will have problems using Odin because they use the same ports? How frustrating. The weird part is now that I have the flashed, rooted 2.3.6 image and using wifi, at some point tonight my network may come back on. Or it may not.
808
Click to expand...
Click to collapse
Bugged out, huh?!!???
Dnice808 said:
Bugged out, huh?!!???
Click to expand...
Click to collapse
I wasn't sure if there was a question there.
From my experience, flashing to JB (MTD partition) from GB without going through ICS may result in lost of imei.
Sometimes, it just happens. I had very limited experience with JB.
The few methods that I've tried worked for me. Just simply flashing back to stock with a re-partition ( (Heimdall -1-click for me) usually brings back the /efs and imei without doing anything extra.
If you haven't, and if you can, I would try the heimdall-1-click a few times.
If you want to use Odin, you may need to reinstall samsung drivers and use a different usb port on the PC than the one you used for heimdall.
You may also want to check the signal of the phone at your location. you may be getting poor signal and it has nothing to do with the phone's OS
qkster said:
I wasn't sure if there was a question there.
Click to expand...
Click to collapse
Me stating that it is bugged out, was me just confirming that it is Weird!
qkster said:
From my experience, flashing to JB (MTD partition) from GB without going through ICS may result in lost of imei.
Sometimes, it just happens. I had very limited experience with JB.
Click to expand...
Click to collapse
Ok just to explain myself better. I have been saying that I was going from GB to JB when in fact I meant to say that I was going from GB to ICS. Sorry for that. Also, the reason my responses have looked wacky is that I was trying to select the multi quote button and getting no response. Hopefully this response is a little more organized.
qkster said:
The few methods that I've tried worked for me. Just simply flashing back to stock with a re-partition ( (Heimdall -1-click for me) usually brings back the /efs and imei without doing anything extra.
If you haven't, and if you can, I would try the heimdall-1-click a few times.
Click to expand...
Click to collapse
See that is what confuses me too. I have flashed back and forth several times at this point, and sometimes the /efs and imei do come back, but now they have never stayed. It is the only reason why I have tried to pretty much rule out a hardware issue. Even when I flash and there is no imei, there is the same /efs folder. And when I wipe the whole thing sparkling clean, even the newly formed /efs folder has the correct imei but it is just not being recognized on the phone.
qkster said:
If you want to use Odin, you may need to reinstall samsung drivers and use a different usb port on the PC than the one you used for heimdall.
Click to expand...
Click to collapse
Of course what I did was accidentally leave my phone home preventing me from testing it out with Odin on another machine. Its all good though.
qkster said:
You may also want to check the signal of the phone at your location. you may be getting poor signal and it has nothing to do with the phone's OS
Click to expand...
Click to collapse
I have an AT&T prepaid phone and the sim from the Infuse works in it flawlessly...
808