Related
EC01 must be old, right? Not so. I cannot give you the build date however, per request of...someone else. Its considerably newer than EC10, however. For some it may be hard to take my word for it, but I have never lied to anyone here.
In here you will find a new shiny radio, a voodoo or non voodoo EC10 kernel, courtesy of JT1134, and...a ROM!
No more hacking pieces together from other devices. No more crappy radios (hopefully). No more poor GPS (hopefully).
Please do not ask where it came from. I will not tell you. All file dates have been changed, the build.prop has been masked.
Please do not ask for an Odin. I will not give you one at this time.
Please enjoy yourself, I insist.
This ROM is ever so slightly tweaked. It is not a quality release by my standards (mostly because its stock). I recommend folks wait for the community rom to be finished. If you can't wait, by all means, flash away.
Does not include a kernel.
Debinged, browser included.
Debloated, yet contains most stock apps.
Custom boot animation, because I am not including the original kernel.
Dialer voicemail button points to Google Voice.
Your current kernel will be retained. So if you are using a Froyo kernel, you will be just fine.
Xoom boot animation because you will be using a custom boot animation supporting kernel.
Installation Instructions (read carefully)
---------------------------------------------------------
Make a nandroid backup.
Odin back to EB01 stock.
http://adbdev.com/danknub/CI500_VZW_EB01_FROYO_REL.tar.md5
Boot once, then Odin clockwork recovery.
http://adbdev.com/danknub/cwm-recovery-ALL-3-30-FIX.tar
Boot straight to clockwork recovery, and flash my kernel of choice from here:
http://forum.xda-developers.com/showthread.php?t=1003017
Boot once, convert to voodoo if need be.
Boot back to clockwork recovery and flash rom.
Boot once, then Odin the radio.
Please follow these directions. There are apparently some kernel/cwr issues that are causing boot loops. If you decide to flash another kernel afterwards, be my guest. Don't wipe, however. The above directions are after hours of testing by IRC folks, and I THANK all of them!!!!!
Radio:
http://adbdev.com/danknub/ec01_radio.tar
Rom:
http://www.multiupload.com/ETEG610SJR
Reserved.
Edify compatible version coming out tomorrow.
<3 your the man
Much thanks man. You're always coming through for us. Thanks for continuing to work on the fascinate.
Sent from my SCH-I500 using XDA App
excellent work man, i new you werent going to give up on us, im gonna have to get the tbolt just so i can continue to use your work. ive been with your roms since my omnia
edit-kernal links are down, both of them.
NM me. I followed your post to a T and I was able to flash a diff kernel then. THanks guys
Great work! Thank you for the work. I'll take your advice and wait for the community rom, but VERY much appreciate your work.
jrobinsky said:
for me, only your kernel works dude. I tried a few other ones after my initial boot and i get stuck on boot loops. IDK about anyone else, but thats my results.
Click to expand...
Click to collapse
I was able to get times_infinity's comavolt voodoo to work, but only if I ODIN'd back to EB01 stock, then ODIN'd ec01 radio, ODIN 03/30 cwm fix, boot directly to recovery, flash ec01 rom, flash comavolt kernel, boot was successful. Going to play with it a bit tomorrow.......errr later today after I get some sleep.
Copied from my "Most Thorough Method of Fixing Every Problem You Might Have" section in the recovery thread, and adapted to this post.
This will wipe your data, btw, so be sure to backup any important info. You can make a nandroid backup, but you will probably have issues if you try to restore the data to use with this ROM.
[SIZE=+2]Bestest Best Way to Install This ROM[/SIZE]
Download to PC
CWM-Recovery 3-30 Odin Package
MD5 Checksum: 00e90e790a70e2d66b6cba6a152de504
ec01_radio.tar Odin Package
MD5 Checksum: 099c7cf67e14fea5c9bbd886a83e48b1
CI500_VZW_EB01_FROYO_REL.tar.md5
MD5 Checksum: d04733ce540ab1af291cfa44d42c768e
atlas_v2.2.pit
MD5 Checksum: a0eaf496375cf72b90f7ceef4f0a4538
Place on /sdcard
ec01_rom.zip
MD5 Checksum: 30849feb8d53b05c611fc9b03263a414
The kernel of your choice
Step-by-Step Installation - Important!
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package
Close odin, Unplug/replug the phone from USB, re-enter download mode, Re-open odin.
ODIN the modem
Unplug USB Cable, THEN reinsert your battery
Hold both of the volume keys and the power button down until a second after you see the Samsung boot logo, then let go
It should now boot into red CWM recovery
Wipe Cache only. Flash the ec10_rom.zip
Flash the kernel of your choice
Reboot. If you have installed a voodoo kernel, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
I can't stress enough how important it is to check your files for the correct checksum to verify that your download did not get corrupted (you can also use it as a way to make sure you have the right version). Also, follow these instructions exactly. You could potentially be wasting your time and anyone else's who is trying to help you fix whatever random issue you might be having, merely because you didn't follow the instructions.
I've been scanning threads for news of this mystery drop since your first hint and just as I'm about to cash out for the night... OMFG! You f'ing rock mate! Now, if I can only find the strength to hold out for the community brain child... I know it will be worth the wait. Oh, but a tasty new radio sure sounds delicious right now!
Thanks again Adryn for everything you've done to make this phone great!
Sent from my #@&$ing SCH-I500 using my %!#@ing XDA App
justin94 said:
excellent work man, i new you werent going to give up on us, im gonna have to get the tbolt just so i can continue to use your work. ive been with your roms since my omnia
edit-kernal links are down, both of them.
Click to expand...
Click to collapse
For now you can just get them from the superclean thread. Same ones.
Might be a silly question, but is it safe to odin just the modem and nothing else? I want to hold off on flashing the ROM and kernel.
Sent from my SCH-I500 using XDA App
tripacer99 said:
Might be a silly question, but is it safe to odin just the modem and nothing else? I want to hold off on flashing the ROM and kernel.
Click to expand...
Click to collapse
Yes, I believe it was verified to work just fine.
is there a reason why after i odin in the first step then go to odin recovery ... it just sits on "setup connection..."
lucas.scott said:
is there a reason why after i odin in the first step then go to odin recovery ... it just sits on "setup connection..."
Click to expand...
Click to collapse
Are you using Adrynalyne's steps or GizmoDroid's steps? Did you reboot phone and let it fully boot into OS before powering down to pull battery to start new ODIN session?
of course ... and im no stanger to odin or anything .. new problem for me
lucas.scott said:
of course ... and im no stanger to odin or anything .. new problem for me
Click to expand...
Click to collapse
Oh, ok, sorry. I didn't run into that problem when testing it before release so that's a new one on me. Only thing I can think of is trying to download the cwm-fix file again and try flashing it in ODIN again. Maybe you got a bad download. Try this one, different link location:
http://www.mediafire.com/file/06al8prkgj29gps/cwm-recovery-ALL-3-30-FIX.tar
landshark68 said:
For now you can just get them from the superclean thread. Same ones.
Click to expand...
Click to collapse
Which kernel are you using from the superclean thread? eb01 or eb16?
DeezNotes said:
Which kernel are you using from the superclean thread? eb01 or eb16?
Click to expand...
Click to collapse
Neither. EC10
landshark68 said:
Oh, ok, sorry. I didn't run into that problem when testing it before release so that's a new one on me. Only thing I can think of is trying to download the cwm-fix file again and try flashing it in ODIN again. Maybe you got a bad download. Try this one, different link location:
http://www.mediafire.com/file/06al8prkgj29gps/cwm-recovery-ALL-3-30-FIX.tar
Click to expand...
Click to collapse
thanks for the link man . that did the trick . bad DL i guess . thanks .
Hello,
I want to go back to gingerbread from resurrection v7.4 ics rom.
I made a backup before i flashed the rom, via CWM, do i just wipe everything and flash the backup? or any extra steps?
also now i cannot load files into my phone, i turned on usb debugging and can access files but when i try to copy a file into the phone it says "can not copy items" "the device either stopped working or has been disconnected"
Help please, many thanks.
To restore you dont have to wipe anything.Use CWM app or boot to recovery and restore.After that Id wipe cache pratition and dalvik cache just in case.Factory reset may be a good idea seeing as your coming back from ICS but thats your choice.After that see how mass storage is.Ive read a few threads about people having trouble getting back from ICS.Hope it all goes well.
cooza said:
To restore you dont have to wipe anything.Use CWM app or boot to recovery and restore.After that Id wipe cache pratition and dalvik cache just in case.Factory reset may be a good idea seeing as your coming back from ICS but thats your choice.After that see how mass storage is.Ive read a few threads about people having trouble getting back from ICS.Hope it all goes well.
Click to expand...
Click to collapse
Thanks Cooza,
but i think i made a stupid mistake, im getting an MD5 mismatch when i try to restore, im searching for the reason, im not sure its true but i think its because i renamed the backup folder from its original date/time to a name i gave it. does that cause MD5 mismatch?
the rest of my backups are with ICS not Gingerbread . is there another way to go back to my version ( i dont mind reformatting the whole phone if i have to)
my former gingerbread Version was
Baseband: XXKI4
Kernel: JPKJ2
android 2.3.5
Flash stock rom then CF root with the exact same CWM kernel you used to backup .
jje
flash via odin the stock rom and custom kernel if you want to have root
otherwise just flash the stock rom, id suggest the original android dev subforum
Ive read that you shouldnt change the name of a nandroid backup but I dont know if that could be the problem.You could Flash the old bootloader and try the nandroid but I dought now that it would work so the best is to flash a custom ROM as the other posters have been advising although like I said ealier Ive read alot of threads with people having this problem of coming back to Gingerbread from ICS.Thats the risk of flashing a test ROM as no ICS ROM is full complete yet.Dont worry mate,theres still hope
ab.riyami said:
Thanks Cooza,
but i think i made a stupid mistake, im getting an MD5 mismatch when i try to restore, im searching for the reason, im not sure its true but i think its because i renamed the backup folder from its original date/time to a name i gave it. does that cause MD5 mismatch?
Click to expand...
Click to collapse
Renaming it will cause a mismatch, if you can't recall the original name, don't worry. You can use Advanced Restore from recovery to restore the b/u.
Thanks guys,
Ill be honest, the only time i flashed my phone was when Cf-rooting then i downloaded the .zip files for resurrection ics and it was easy cuz done via CWM.
so ive never flashed a rom on my fone using odin, i fell intimidated i bit, dont know the difference in flashing a rom and a kernel (i know what they are but donno how to flash individually)
anyways i went to sammobile.com, downloading the stock firmware now.
by searching online i now think the zip file from sammobile will have some files and i gotta load the files provided in their proper places (dont know if .pit file will be provided with it, nor if i need to load .pit)
please tell me if what ive mentioned above is correct, sorry for the noob questions but i just dont wanna screw up.
after all of that ill then back up properly and try some gingerbread roms and kernels. but i just wanna get it back to the original first to be safe, dont know if i can just flash gingerbread roms and kernels with my ics phone.
ab.riyami said:
also now i cannot load files into my phone, i turned on usb debugging and can access files but when i try to copy a file into the phone it says "can not copy items" "the device either stopped working or has been disconnected"
Click to expand...
Click to collapse
adb push, or Droid Explorer, or QTAdb, et al, will allow you to get those files to your phone.
mudferret said:
Renaming it will cause a mismatch, if you can't recall the original name, don't worry. You can use Advanced Restore from recovery to restore the b/u.
Click to expand...
Click to collapse
Thanks mate,
Tried Advance restore option, it said "no file found"
I went back myself from ics to a stock ROM. It's really easy
What I did first was fully wipe cache, dalvik etc in cwm. Next up: put your phone in download mode (volume down, home and power)
Start odin and add the tar file or tar.md5 file with the PDA button. That should be the only file in the zip, if there are more: look at the file names, they'll say where to add them in odin.
Next up, connect your phone to your computers usb port (odin should tell you that it has added your phone) and hit the start button.
After the flashing is done your phone will reboot and it should be back to normal. Now you can flash a kernel to get root again if you like
Good luck, it will work out just fine
Sent from my GT-I9100 using XDA App
Excellent, thanks guys it worked
Flashed stock via Odin, not rooted now but will do when i flash CF-root again
waiting for sam to finally release ics!
ab.riyami said:
Excellent, thanks guys it worked
Flashed stock via Odin, not rooted now but will do when i flash CF-root again
waiting for sam to finally release ics!
Click to expand...
Click to collapse
Well done.Better to wait for the official release of ICS
Okay, so after installing the kang build 25 ICS for the vibrant, everything went fine. Randomly I get a random reboot and my phone says there was an "encryption error" and that I have to do a factory reset. Since I already had everything backed up, I didn't mind the data wipe. When it went rebooted the CWM screen came up and started wiping everything but when it got to the "formatting data" part, it failed. I tried this many times and it kept failing... SO, I decided to ODIN back to JFD. After doing so, all I get is the Vibrant screen, then an instant shut down. I even tried Eugene's old No Brick Froyo PDA, then tried to reinstall the JFD image, but got no luck.
Question is: What should I do now?
Any help will be GREATLY appreciated. Thanks!
Its a little involved but It's all I could find to help buddy
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Perhaps it could be a bootloader problem? If you're sure you are doing Odin right, including repartition with the pit file, you could look at your SBL.
.
Sorry but what is SBL?
lolrus101 said:
Sorry but what is SBL?
Click to expand...
Click to collapse
I dont know how to explain it very well lol but to check if the rom you are trying to odin has the sbl in it. Rename it and put a .zip at the end. Then extract to see if its in there it should be named "sbl". To change it back simply delete the .zip off the original file.
JFD
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Try odining a rom that has the sbl file in it thats probably why its not working.
---------- Post added at 04:14 AM ---------- Previous post was at 04:09 AM ----------
Here http://forum.xda-developers.com/showthread.php?t=1278683 you need to have java installed to open it
Just tried the Heimdall thing. No luck. As soon as it says rebooting, it goes to the vibrant screen, then the battery charging screen, then continues to bootloop. Same thing happened with Odin
why don't you try what I did
http://forum.xda-developers.com/showpost.php?p=23056603&postcount=10
lolrus101 said:
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Click to expand...
Click to collapse
The SBL is the Secondary Boot Loader, which is loaded by the Primary Boot Loader.
I haven't personally encountered any roms which also flash bootloaders.
I did manage to get my phone bootlooped in some weird way which apparently could only be fixed by reflashing the SBL. Note: flashing bootloaders is more dangerous than regular roms.
I am presently running a GB SBL from this thread:
http://forum.xda-developers.com/showthread.php?t=1117990
ian577416 said:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Click to expand...
Click to collapse
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Flashed the GB bootloader and no luck either . Flashed back to the froyo one, and got the data wipe error again, the phone rebooted, and now its at "KERNEL PANIC - UPLOAD MODE"
AdamOutler said:
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Click to expand...
Click to collapse
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
lolrus101 said:
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
Click to expand...
Click to collapse
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
cashmundy said:
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
Click to expand...
Click to collapse
SO the thing is I used the GLITCH kernel with vibrant build 25... I dont think I was supposed to... could that have caused the problem? maybe a voodoo problem?
There are two glitch kernel series that I know of, one for CM7 and one for CM9 and ICS (I think, not sure, that all ICS builds and CM9 use the same basic filesystem scheme).
All stock builds use a Samsung FS scheme which is different from the two above. So there are at least three mutually-incompatible families of FS+kernel pairs.
I used the CM9 kernel I think...
After the installation went fine, I got the encryption error which told me to reboot. as soon as I did, I got the Data wipe fail. Any ideas?
Encryption Error
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
tabthelab said:
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
Click to expand...
Click to collapse
If you are still able to access Clockworkmod Recovery CWM (NOT STOCK RECOVERY) then try this:
http://forum.xda-developers.com/showthread.php?t=1447303
Otherwise just give up. There is currently no fix for this bug as of now.
This is really getting out of hand ICS rom devs should put a big caution sign on their thread(s) stating the following:
WARNING THIS ROM WILL BRICK YOUR DEVICE!!!
Goodluck... in the meantime find yourself a spare phone like i did cuz you certainly ain't fixing this one.
Sent from my Galaxy Nexus using XDA
mother of god
I hope this helps you. I finally, after hours of nothing, tried to use Odin to flash to 2.2 froyo. cha ching. got in.
tar file I used here: http://forum.xda-developers.com/showthread.php?t=833024&page=49
worked for me. I hope it helps you
Whenever I try to flash a ROM, it says:
E: Can't open /sdcard/*romname*.zip (bad)
I tried flashing kernels with ODIN, I tried downloading the ROMs again, I tried with multiple recoveries. How can I fix this?!
Have you rooted your phone first?
Redownload the file
sahibunlimited said:
Redownload the file
Click to expand...
Click to collapse
I did, and I said that too.
stubradley1 said:
Have you rooted your phone first?
Click to expand...
Click to collapse
Yes, I am rooted
juliuslucas said:
Whenever I try to flash a ROM, it says:
E: Can't open /sdcard/*romname*.zip (bad)
I tried flashing kernels with ODIN, I tried downloading the ROMs again, I tried with multiple recoveries. How can I fix this?!
Click to expand...
Click to collapse
Flash a rom how with Odin ??? if so are the files Odin flashable or CWM zip files .
This reads as you are flashing the wrong files with the wrong format .
zip bad means bad file its that simple .
What file are you trying to flash and with what is the basic question .
jje
JJEgan said:
Flash a rom how with Odin ??? if so are the files Odin flashable or CWM zip files .
This reads as you are flashing the wrong files with the wrong format .
zip bad means bad file its that simple .
What file are you trying to flash and with what is the basic question .
jje
Click to expand...
Click to collapse
Sorry if I was being unspecific, but I mean I tried flashing other kernels to see if it fixed my problem. I can open the .zip files that I am trying to flash on my computer, but I just can't seem to make them flash to my phone.
But what are you flashing the zip files with on the phone CWM 4 if so use a later CWM and root from Chainfires thread .
jje
JJEgan said:
But what are you flashing the zip files with on the phone CWM 4 if so use a later CWM and root from Chainfires thread .
jje
Click to expand...
Click to collapse
I am flashing with CWM, of course
I am on CF-Root kernel. I did try multiple recoveries, including the one in Siyah kernel. I'm sure that my phone is rooted, since I can do regular rooting stuff on it.
I just tried downloading the ROM again, and it still gives me that same error. There should be nothing wrong with my USB cable or connection, since I can transfer other files that work to my phone. I did try multiple ROMs, but they all just seem to not let me flash. It just stopped working all of a sudden.
I just looked at a thread with a guy having the same problem on his Transformer, and it turned out it was CWM corruption. He used something called Gnufabio RecoveryInstaller to fix it. Is there anything like this on the SGS II?
juliuslucas said:
I just tried downloading the ROM again, and it still gives me that same error. There should be nothing wrong with my USB cable or connection, since I can transfer other files that work to my phone. I did try multiple ROMs, but they all just seem to not let me flash. It just stopped working all of a sudden.
Click to expand...
Click to collapse
most probable case is your downloading everytime gettiing correpted..
try to download a ROM which has got MD5 checksum....and check the MD5 check sum after puting it into SD card using AFV tool market...
if you are on GB rom, download Siyah kernel Odin version and flash from Odin and see
zaheedahmed said:
most probable case is your downloading everytime gettiing correpted..
try to download a ROM which has got MD5 checksum....and check the MD5 check sum after puting it into SD card using AFV tool market...
if you are on GB rom, download Siyah kernel Odin version and flash from Odin and see
Click to expand...
Click to collapse
Good idea, I'll just have to find a ROM like that then I will try and downgrade to GB with ODIN and then flash Siyah with ODIN first, to see if that'll work.
juliuslucas said:
Good idea, I'll just have to find a ROM like that then I will try and downgrade to GB with ODIN and then flash Siyah with ODIN first, to see if that'll work.
Click to expand...
Click to collapse
Downgrading to GB and trying there didn't work, I'll have to find a ROM with a MD5 Checksum then. How was it that I checked the MD5 after it's on the phone?
juliuslucas said:
Downgrading to GB and trying there didn't work, I'll have to find a ROM with a MD5 Checksum then. How was it that I checked the MD5 after it's on the phone?
Click to expand...
Click to collapse
another option to try is....even chances are very less to work...download ROM manager and flash Clockworkmode from that and reboot into recovery from Rom manager, if flashing of update.zip seccess you will get a recovery, then you try to install rom from that...
this worked for me once when my CWM gave me a treble
zaheedahmed said:
another option to try is....even chances are very less to work...download ROM manager and flash Clockworkmode from that and reboot into recovery from Rom manager, if flashing of update.zip seccess you will get a recovery, then you try to install rom from that...
this worked for me once when my CWM gave me a treble
Click to expand...
Click to collapse
I'll try that. I just checked the MD5s, and it appears that the data I transfer to my phone gets corrupted. Maybe I should try downloading it from the phone.
MD5 before: FF9D66AB7449EF30360D0A5982338F97
MD5 after: 3C2AE2984024421FDF1A204315BE3CD0
juliuslucas said:
I'll try that. I just checked the MD5s, and it appears that the data I transfer to my phone gets corrupted. Maybe I should try downloading it from the phone.
MD5 before: FF9D66AB7449EF30360D0A5982338F97
MD5 after: 3C2AE2984024421FDF1A204315BE3CD0
Click to expand...
Click to collapse
hmmmmm, thanks to CWM for preventing bad files from flashing and bricking the phone
zaheedahmed said:
hmmmmm, thanks to CWM for preventing bad files from flashing and bricking the phone
Click to expand...
Click to collapse
I will try and download the ROM directly from my phone. This is getting on my nerves. I'm hoping that it's got nothing to do with my phone, and that it's just something to do with my computer or something. I'm running out of options here.
I am very, very, very, very, very, very relieved to inform you that it was indeed something with the connection from my computer to my phone! It worked! I wasted about three hours, but anyway. Thanks for sticking with me. Thanks to you!
juliuslucas said:
I am very, very, very, very, very, very relieved to inform you that it was indeed something with the connection from my computer to my phone! It worked! I wasted about three hours, but anyway. Thanks for sticking with me. Thanks to you!
Click to expand...
Click to collapse
we are glad........thank god
if you dont want to have to download the roms directly on youre phone, you can use Xlink to transfer them from your computer wirelessly, you download an app from the play store and get a client for your computer.
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem