I wouldn't post normally but I've tried everything.
Odin EB01 with PIT JT's CWM Wipe CM7 build 4 nothing
From ComRom 2.0 JT'S CWM Wipe CM7 build 10 nothing
Those aren't the only one's I've tried but numerous variations of each. I get everything from status 7 errors with build 10 to SD card mount errors with build 4. I really want to try CM7 but I just can't get there.
Can anybody help or just throw some ideas out there?
By build 4, do you mean 7/4? If not, the 7/4 build seems to be the best to start with. That is what I had to do. Also, did you flash the CWM fix?
Sent from my SCH-I500 using XDA App
Yes that's what i meant.
I followed the same procedure and got a boot loop the first couple of times. Finally I read something about not wiping data (factory reset), that did the trick. I just wiped cache and dalvik when going to build 9 (I guess it should work with 10 as well)
Kazba1626 said:
I wouldn't post normally but I've tried everything.
Odin EB01 with PIT JT's CWM Wipe CM7 build 4 nothing
From ComRom 2.0 JT'S CWM Wipe CM7 build 10 nothing
Those aren't the only one's I've tried but numerous variations of each. I get everything from status 7 errors with build 10 to SD card mount errors with build 4. I really want to try CM7 but I just can't get there.
Can anybody help or just throw some ideas out there?
Click to expand...
Click to collapse
I've gone back and fourth three times between com rom 2.1 and cm7 and
Every time I just odin eb01 and the atlas pit, fully boot, odin cwr 3-30 fix all, immediately three finger boot into recovery, wipe everything, flash cm7 build 7/04, boot fully, back into recovery via power menu, flash test build 9 ...(don't remember the date) without wiping...hope this helps?!
Sent from my SCH-I500 using XDA App
So you flashed CM7 build 4 not using JT's CWM?
Sent from my SCH-I500 using XDA App
efan450 said:
I've gone back and fourth three times between com rom 2.1 and cm7 and
Every time I just odin eb01 and the atlas pit, fully boot, odin cwr 3-30 fix all, immediately three finger boot into recovery, wipe everything, flash cm7 build 7/04, boot fully, back into recovery via power menu, flash test build 9 ...(don't remember the date) without wiping...hope this helps?!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thanks man-this worked for me when nothing else would.
This is crazy how I can't get absolutely anything to work
I was in the same desperate situation you are until i did the following (worked on mine and my brother's phone):1- odin back to eb01 with the atlas 2.2 pit file and let it load
2- odin the cwm recovery.all file
3- install Evil Fascination 3.6 though cwm (wipe data factory reset, cache partition, and dalvik first). Evil will do the voodoo conversion don't touch it until it loads completely.
4-Flash jt1134's cwm fix thats found in his cm7 op. Reboot recovery and make sure you're on it. I think it is 3.0.7x
5- On jt's recovery, do a factory reset, cache partition and dalvik wipe
6- Install cm7 09-04 build and let it do the conversions and load. I swear it installed in less than 5 min.
7- Once it loads up get into recovery which at this point should be4.0.x. Flash gapps. Reset and let it load
8- Go back to recovery(always through power button) and flash build 10 09-13 NO WIPES.
9-profit
I tried that didnt work I just gave it up at this point I'd been trying for hours. Thanks
Sent from my SCH-I500 using XDA App
Thank you very much. I thought I was screwed. I was able to get back to stock. Now I will be eventually making my way to CM7.
Edit: I followed the steps perfectly and was able to get to CM7 7/13. Thanks again.
Related
I have been searching for a while, but does anyone have issues installing Miui 1.7.8? I can get to CM7 and install GAPPS for it no problem. On CWM 4.0 I have been trying to install Miui from SD card after wiping data and both caches. When it tries to load Miui I get a boot loop with the exclamation mark and quickly written words that I can't decipher quickly. I read earlier about pulling battery in this instance, but that didn't help. I want to test out the phone.apk, but I'm having some issues.
fsuagentsmith said:
I have been searching for a while, but does anyone have issues installing Miui 1.7.8? I can get to CM7 and install GAPPS for it no problem. On CWM 4.0 I have been trying to install Miui from SD card after wiping data and both caches. When it tries to load Miui I get a boot loop with the exclamation mark and quickly written words that I can't decipher quickly. I read earlier about pulling battery in this instance, but that didn't help. I want to test out the phone.apk, but I'm having some issues.
Click to expand...
Click to collapse
For future use, if anyone is having issues like this...
1. Booted using volume controls to recovery 3.0 posted by JT in CM7.
2. Used the ext4 formatter_all from navenrob
3. Used the CM7 install from JT
4. Booted CM7
5. ReBooted recovery from CM7
6. Wiped Cache from CWM 4.0
7. Installed current verison of Miui from CWM 4.0
Thought I would post how I figured it out.
fsuagentsmith said:
I have been searching for a while, but does anyone have issues installing Miui 1.7.8? I can get to CM7 and install GAPPS for it no problem. On CWM 4.0 I have been trying to install Miui from SD card after wiping data and both caches. When it tries to load Miui I get a boot loop with the exclamation mark and quickly written words that I can't decipher quickly. I read earlier about pulling battery in this instance, but that didn't help. I want to test out the phone.apk, but I'm having some issues.
Click to expand...
Click to collapse
I was having problems flashing 1.7.8 too. I downloaded 1.7.1.3 from goo inside me. The site where you download the rom. I flashed that with no issues on red CWM. Then i booted and went to orange recovery from the power menu. Flashed 1.7.8 perfectly. Don't really know if this would solve the problem but its worth a shot.
I had to odin eb01 with atlas 2.2, odin cm recovery fix for cm7, flash cm7signed in red recovery, rebooted into orange recovery, reflash cm7signed, reboot into rom, reboot recovery, wipe, flash cm7 0704, reboot, wipe, flash miui. finally worked after much trial and error
Could someone please help me with a little more details on installing simply honey? i would try it again myself but i just fixed my phone from the phone ! computer sign and id rather not again. im stock 2.1 enclair now. my biggest problem is odin. which boxes do i check (reset time, reboot, partition) and where should i put tar file (phone or pda) and lastly it says to use pit 512 file. where is this? Thanks in advance!!
derek210 said:
Could someone please help me with a little more details on installing simply honey? i would try it again myself but i just fixed my phone from the phone ! computer sign and id rather not again. im stock 2.1 enclair now. my biggest problem is odin. which boxes do i check (reset time, reboot, partition) and where should i put tar file (phone or pda) and lastly it says to use pit 512 file. where is this? Thanks in advance!!
Click to expand...
Click to collapse
you could go the way i went (which i thought was easier, might be abit longer but not much) or the odin way
the way i did it:
flash simply honey 3.3 though recovery like normal, wipe data/fact reset, wipe cache http://www.megaupload.com/?d=ITORJOGK
reboot when its done
then flash which ever 3.9.1 package you want through the CWM app (if its there, cant remember) or rom manager, dont think it matter about doing the light first now cos they're all full roms (they weren't when i first did it)
when it reboots wait 15 min then reboot again then you're good to go
odin (not 100% sure though):
flash the GB bootloaders http://forum.xda-developers.com/showthread.php?t=1117990 (READ THAT CAREFULLY)
then get the odin_heim file whatever its called from SH thread, open the .zip and extract the .tar and that goes in PDA in odin, the .pit file i think is the one you would use to odin to stock
have fact reset ticked and reboot, dont know about re-partition, some people said it completely wiped their internal SD so back up what you dont want to lose then click start and let it go through (if you get the voice saying not enough space or something when its rebooting pull battery, go to recovery and disable voodoo then reboot)
then flash whichever package you want through recovery then reboot
let it sit for 15 min then reboot again
i think thats it
if you go the way i went and flash the bootloaders anyway first or after to get rid of the rainbow and to be able to see recovery for the future, its up to you
thanks! im going to try this as soon as i get off work.
i was on stock rooted with clockwork recovery. grabbed the 3.3 simply honey link, renamed it update.zip and put it at the root of the internal sd. did a factory wipe, cleared cach, and davik cache. and then installed and it put me in a boot loop. im using odin to get back to stock, any ideas?
derek210 said:
i was on stock rooted with clockwork recovery. grabbed the 3.3 simply honey link, renamed it update.zip and put it at the root of the internal sd. did a factory wipe, cleared cach, and davik cache. and then installed and it put me in a boot loop. im using odin to get back to stock, any ideas?
Click to expand...
Click to collapse
didnt need to rename it anything, thats a full rom, cant flash 2.3.4 over froyo without the GB bootloaders but can flash 2.3.3 so thats why you have to do that 1st
did you wipe dalvik after or before ??
i wiped it after the 1st time i did it and because its in advanced menu in recovery it wouldnt go back to the normal page of recovery to reboot and that put me in a bootloop
when you're rooted again after stock......
-put 3.3 and the 3.9.1 package you want on sd and leave them named as they are
-go to recovery, wipe data/factory reset and wipe cache
-flash 3.3
-reboot
-flash 3.9.1 in rom manager (it'll factory reset again even if you dont have that ticked, could tick wipe dalvik and cach aswell while you're there)
-when it reboots leave for 15 min then reboot again
thats the exact way i did it i think and works fine for me
Thanks soooo much it finally worked! I feel bad asking another question but I can't seem to find the answer. I installed the GB bootloaders and have the full version of the simply honey loaded now but everytime I get a call I have to reboot after or I wont be able to receive calls. Thanks again!
Sent from my GT-I9000 using XDA Premium App
I just found a post by you in the simply honey thread that answered my question. So I reflash and wipe. Do I flash all the way back to 2.1 or just reflash the full version of simply honey and wipe all data?
Sent from my GT-I9000 using XDA Premium App
You may want to consider trying some of the more tried-and-tested 2.2 and 2.2.1 ROMs until you have more experience with modding in general. When you start messing with bootloaders, it doesn't take much screwing up to permanently and irrevocably (apart from a JTAG) brick your phone.
derek210 said:
I just found a post by you in the simply honey thread that answered my question. So I reflash and wipe. Do I flash all the way back to 2.1 or just reflash the full version of simply honey and wipe all data?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
wipe in recovery and flash 4.0
uuuuuuuuggg!!! I've posted dozens of replies with explanations of how to do this! lol
sorry for all my noob questions and not being able to find post that have already been made about this. however, its working perfect now and i appreciate everyone's help!
Hey All,
I had been having troubles with 4.0.3 multi-dpi, so I thought I'd flash Saurom. I flashed this, but upon reboot, I got stuck at the samsung screen. It never went past there, just sat there forever. So, I went back into cwm (holding down vol up/vol down/power), and wiped everything again, and tried to flash saurom again, but same thing happened.
I then tried to flash back to 4.0.3 multi-dpi, with same results. I can get into CWM just fine, but it seems any rom I flash hangs at the samsung boot screen.
Does anyone have any ideas? Right now I'm completely down :/
Thanks in advance for any assistance,
Sebastian
Hi sounds like a bad kernel flash.i would go into cwm, do the usually wipes, go to mounts and storage. Format data. Format system. Format cache only. Pull battery. Install any of the odin install Roms through download mode, That should fix your problem. Then you can start over and flash whatever Rom you want
Sent from my SAMSUNG-SGH-I717 using xda premium
You should restore the latest good backup you created before you flashed whatever is giving you problems.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Just a reminder, when you go to mounts and storage, do not fformat sd storage, this will wipe everything in your memory of your phone
Sent from my SAMSUNG-SGH-I717 using xda premium
A backup restore should do the trick.
-Once you go NOTE, you'd say 4 inches a Joke
Worse comes to worse you can flash stock Odin. If you one clicked for ICS, remember to flash bootloader first
Sent from my SAMSUNG-SGH-I717 using XDA
From my gathering, Saurom & ICS 4.0.3 DPI are incompatible. Meaning you can't flash one on top of the other without doing a full wipe data/factory reset. Having said that, I think the best move then would be to flash back to stock via ODIN, install cwm, redownload whatever ROM to your ex sd card, mount system & data then re-flash.
Shdowalker said:
From my gathering, Saurom & ICS 4.0.3 DPI are incompatible. Meaning you can't flash one on top of the other without doing a full wipe data/factory reset. Having said that, I think the best move then would be to flash back to stock via ODIN, install cwm, redownload whatever ROM to your ex sd card, mount system & data then re-flash.
Click to expand...
Click to collapse
I "believe" all you need to flash through Odin is the GB bootloader, then you can flash GB roms, the ICS bootloader is what causes the hang up with ROM incompatibilities
Sent from my SAMSUNG-SGH-I717 using XDA
Be sure the ROM has the radio load and remember a Nandroid does not flash the radio load. That has to be done manually.
VonEsch said:
I "believe" all you need to flash through Odin is the GB bootloader, then you can flash GB roms, the ICS bootloader is what causes the hang up with ROM incompatibilities
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
I'm not very familiar with Saurom but from what I've read I think that's correct. ICS needs a clean slate to operate from is all I was saying.
I was having trouble with my CM9 [THS] rom, I was on build 13 so I thought I'd update to build 15. So every app was crashing and what-not, so I reboot it and put it in my pocket. 30 minutes later I take it out and it's warm, it was on the boot screen the whole time.
So I remember I can't use 3-finger recovery for ICS.. but at this point I didn't know what else to do [I was trying to get it done in a hurry]. So I did 3 finger recovery.
Then as I expected, it would not boot normally, it kept booting into recovery.
So I tried to flash CM9 build 15, but at "checking state of bml/mtd" it immediately rebooted and was in what seemed a bootloop.
So I heimdall a old recovery.bin, back from a Gingerbread ROM, hoping it would fix it like it did last time I had the bootloop.
It did, and it tried to boot up the CM9 now. I let it alone for a few minutes and realized it wasn't gonna finish booting, so I booted into windows [primary OS is Ubuntu] and did a complete ODIN, back to verizon Gingerbread firmware. I used atlas2.2.pit or something.
So I left it and came back and it said "PASS!" and it was now stock Gingerbread ROM.
So I heimdall'ed recovery.bin as stated on this page: http://wiki.cyanogenmod.com/wiki/Samsung_Fascinate:_Full_Update_Guide
And I did 3-finger recovery [because it says to if you are on stock GB], and so I did a full Wipe, and then I installed from .zip, and chose CM9 THS build 15 [ http://rootzwiki.com/topic/16630-romicsimm76d-teamhacksungs-ics-port-for-fascinate-build-15-071012/ ]....and it started to install but when it came to "Checking state of BML/MTD" it immediately rebooted, and looks like it's bootlooping now.
What's wrong? How do I get CM9 installed again?
I'm going to the dentist and I hope when I get back someone has posted the solution..
Thanks!
1) odin to stock and let boot then odin cwm fixed for cm7
2) 3 finger to recovery
3) wipe data, cache, and dalvik
4) install THS build 2 and let it fully boot
5) reboot recovery using power menu
6) wipe data, cache, and dalvik
7) flash build 15 + gapps
8) enjoy
Thanks.. That worked.
I had forgotten that you have to flash specific roms in order to bridge the gap from GB to ICS.
I'm not entirely sure why THS build 2 is so magical.. but whatever.
The thread on rootzwiki did not have build 2 linked, so I found it on another forum.
I am going to upload it to mediafire so if anyone wants THS build 2 mirror, they won't have to hunt!
Here is a dropbox mirror: teamhacksung-ota-eng.BUILD2.zip
I am trying to mirror it on mediafire but it quits uploading after the first MB.. :S
I have a sch-i500 that is rooted with cwm working.
I am very interested in running liquid smooth v 2.9 found here: http://forum.xda-developers.com/showthread.php?t=2245120
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
http://forum.xda-developers.com/showthread.php?t=1026746
seems to be the best way for me to recover from this (looks like I flashed a non voodoo rom without removing voodoo) but I am unable to get the phone into download mode with or without the battery in the phone.
please help......(update) Alright, I am a moron. needed to have a powered usb port. on my way to recovery. thanks for having all this great info in one place.
aircooledbusses said:
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
Click to expand...
Click to collapse
Oh so close.
When coming from 2.3.x ROM you will need to flash the rom (liquid: or other 4.2.x) you will need to flash 2 more times...
The 1st flash get you into the new recovery only,,, as you found out.
2nd flash will pop up with an error message about incompatible partition and telling you to re-flash again,,,
So 3rd flash actually installs your new ROM
Then install a current/compatible Google gapps
.
Enjoy
.
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
aircooledbusses said:
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
Click to expand...
Click to collapse
what does the error say besides status 7?
did you odin the CWM4 fixed for cm7 then install the ROM 3 times?
can you get a pic up for us to see?
just to be sure......using odin, I repartitioned with the pit, and flashed a E03 rom. rebooted the phone fine.
flashed the CWM4 fix for 7 and redid the GB bootloaders as well.
went into recovery and factory reset, wiped cache, and dalvik.
installed liquid-JB-v2.7-Official-fascinatemtd.zip this time first time took me directly to clockwork where I flashed again. prompted with install from sdcard complete. repeated and got same message.
factory reset, wipe, wipe and flashed gapps. Everything seems to have worked this time with the v2.7Official instead of 2.9. I will play with this for just a bit and probably try it again tonight with a fresh downloaded copy of v2.9. I really do appreciate your assistance and help and I would not have gotten this far without the forum.
update:
flawless installation of v2.9 since 2.7 was already installed. (installed via cloclwork mod recovery)
It was most likely an operator error that prevented me from installing 2.9 after E03. But I don't see the benefit of going back to recreate why it didn't work. Thanks again all is good and right.