Develop Bugs

[Q] Flashing the SyndicateROM seems to freeze for me

For the last two nights, I've tried to flash with this ROM (first ROM flash, the phone was purchased Saturday) and everything seems to going just like the YouTube video provided by qbking77, until the restart. On restart, the phone will stay on the screen that says, "Samsung" that you get when you restart the phone normally. the night before last, I lost patience after about 30 minutes and Odined everything back to stock. Last night, I let the phone try to restart all night and this morning, it was still stuck on the same screen.
Two questions about this. One, is this a normal length of time for the first time flashing a ROM? If not, what is? Two, What am I doing wrong?
Thanks in advance for your advice (for course, I will give a "thanks" to answers).

Did you use cw3?

shook187 said:
Did you use cw3?
Click to expand...
Click to collapse
Yes, I did.

Did you covert to ext3 first, then flash then reboot?

shook187 said:
Did you covert to ext3 first, then flash then reboot?
Click to expand...
Click to collapse
I was running EC05. I coppied the ZIP file to my SD card, set the handset to UBS Diagnostics, ran the "run.bat", in CW3.whatever from my PC, cleared all three caches, three times, and loaded the ZIP file from the SD chip. I thought that CW3 converted to ext4.

charliehorse1967 said:
I was running EC05. I coppied the ZIP file to my SD card, set the handset to UBS Diagnostics, ran the "run.bat", in CW3.whatever from my PC, cleared all three caches, three times, and loaded the ZIP file from the SD chip. I thought that CW3 converted to ext4.
Click to expand...
Click to collapse
If you're capable of using Odin, then just use the Odin CWM link in my signature. From there, you can flash a pre-rooted EB13 Deodexed Stock with CWM 3. You can update it to EC05, before you flash, after, or never, and you'll be fine.
I also have Syndicate Rom Frozen linked in my signature.
That should work for you.

I'll give that a shot when I get home and let you know how that works.

One of the things I did, was just reflash the ROM right overtop itself.
I have flashed this ROM many times, and every now and then the first flash wont take for whatever reason, I just pull the battery, go back into CWM, and reflash the ROM again right overtop itself, and it normally works.
note: boot times longer than 5-10 and you got an issue
Also, make sure you are using Clockwork Mod version 3.0.0.6 and not version 2.5.5, as 2.5.5 does not support EXT4, and I think that the ROM is EXT4

Odin a prerooted ec05 ext4 tar, I have 2 diff packages here on xda.. then flash srf over that.. good to go. I wouldn't even mess with the eb13 tar, because then you have to odin the modem again seperately...
Sent from my SPH-D700 using XDA App

chris41g said:
Odin a prerooted ec05 ext4 tar, I have 2 diff packages here on xda.. then flash srf over that.. good to go. I wouldn't even mess with the eb13 tar, because then you have to odin the modem again seperately...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That might be my issue, since the version that I was Odining was EB13 and then the carrier updated to EC05. That actually makes sense (although, I don't really know what the "under-the-hood" differences between the two are).

charliehorse1967 said:
That might be my issue, since the version that I was Odining was EB13 and then the carrier updated to EC05. That actually makes sense (although, I don't really know what the "under-the-hood" differences between the two are).
Click to expand...
Click to collapse
You would think, but I actually got a better official update to EC05 during my tests. Regardless, I actually have found EB13 to have better signal.
Either way, pre-rooted should make it easy for you.

Random,
Once I figured out exactly the steps to take, everything worked! WOOT! A thousand thanks to everybody who input in this!
For anybody out there having the same problem, follow these steps:
0) Download and install the drivers for your Samsung Epic 4G (Found here).
1) Download the ROM
2) Either copy the whole ZIP file onto your microSD Chip by using your USB cable or by unmounting it and using the SD slot adapter and plugging into the appropriate slot on your computer. (Just place it in the root directory)
3) Click on RandomKing's link above in his signature that says "CWM Odin" (this is a pre-rooted Sprint stock ROM)
4) Uncompress the file onto your Desktop (it's an RAR file, so you're going to need either WinRAR or 7ZIP).
5) Turn your phone off and unplug your USB Cable.
6) While holding the "1" key, power up the handset (you'll get a funny looking icon of the Android shoveling)
7) Plug in your phone in to a soldered USB port (as in ON THE BACK of the machine).
8) Double click the Odin3+v1.61 file.
9) Add the .pit file to the "pit" box.
10) Add the other file to the "PDA" box.
11) Click "Start" button.
12) Wait for it to finish and reboot.
13) Reboot again, this time your going to use the "3-button-power-on" (While holding the down volume button and the camera button, power on the phone)
14) Clear your caches (three times each: data/factory reset, cache partition and Dlavik cache [that's under advanced], by scrolling to them in the menu and pressing the camera button)
15) Select "Install zip from SD Card"
16) Choose your ROM and press the camera button
17) This should take something less than 15 minutes total, including restart
18) Enjoy your New Phone!

What version of the ROM are you trying to flash? I was having the same issue when I tried to flash the "journaling" version of the rom that is posted over on ppc geek. No matter what I did It would hang at the Samsung logo.
.

jpeepers said:
What version of the ROM are you trying to flash? I was having the same issue when I tried to flash the "journaling" version of the rom that is posted over on ppc geek. No matter what I did It would hang at the Samsung logo.
.
Click to expand...
Click to collapse
I was using EC05, but I used the Odin in the post above mine to get a pre-flashed EB13 build of Froyo. Then I just did exactly what I wrote. I hope this helps and I'm sorry about taking so long to get back to you.

how come roms dont like me?

i got a new epic from assurion so it had nothing on it so i odined el30 flashed su odined acclaim and that was it then i put A rom on top of it ( the peoples rom ) and as usual it lags and doesn't open up things for up to a minute . i have always had problems with roms. what can i be doing wrong? are these the correct steps? are they incompatibility issues? or is el30 not stable yet. any help woiuld be appreciated. i really like using your masterpieces but i seem to have issues wit all of them, so clearly its me. thanks

If you don't like aosp but want stock rooted, Odin el30 ( victory pit in pit section, el30 .tar in PDA section, only have auto reboot checked), then OTA to fc09 then Odin cwm 5.x ( pit in pit section, cwm .tar in PDA section, leave everything unchecked), pull battery when Odin finishes, boot cwm, flash su.zip, boot fc09, use es file explorer(free in play store) launch es, navigate to settings> check use root explorer, grant su, check mount /system, delete /system/etc/ recovery-install.sh (or something like that to disable the script from reinstalling the stock recovery.) , Odin cwm again and your good.
Edit: or an easier way would be to Odin cwm once and flash this lol http://forum.xda-developers.com/showthread.php?p=24419155
Sent from my cm_tenderloin using Tapatalk 2 Beta-5

Also download Spare Parts and set Window and Transition Animations to FAST. You would be surprised at the difference that makes. You will lose CRT off but with that speed, who cares...LOL.

ok this was a bit much for me. i dont need stock rom i dont care about anything. i just thought i had to odin to start fresh . all id like is whatever it takes to get peoples rom (for instance) to work on my phone. btw, i can not even get the screen to turn back on now without pulling the battery. i can follow the directions but i was hoping for something alittle more simple. if thats not possible i will try to figure out those directions

Unfortunately Samsung's Gingerbread update killed the one click root option so Odin is needed to at least put on a custom recovery and then install a prerooted ROM.
Sent from my SPH-D700 using xda premium

ok i apologize i was half alseep when i read the first reply, so i opted for the second option and odined \cwm-5.0.2.7-epic4g.tar.md5
i also have a cwm 3.1.0.1
should i have used that? i usually do the acclaim in odin but i just odined the cwm but when i went into recovery of course the deoxed fc09 didnt work because it wasnt rooted but the su.zip doesn't show up on my sd card in recovery. it always does when i odin acclaim. what am i doing wrong?

When you odin cwm 5, uncheck reboot. Odin will complete but your phone will still have the triangle showing. Disconnect the cable, pop battery out and in, 3 finger salute into cwm5 and flash The People's Rom. That will put you on MTD. Then if you don't like that you can flash the deodexed FC09 from there.
Sent from my PantechP4100 using xda premium

Listen, I think most of the devs in this community work really hard to put out some great ROMS. The insight they have given me is much appreciated. But now that I've said that, here is my answer to your original question.
I have yet to use a ROM that is as reliable as stock ROMs. If you read the threads about each ROM you will see lots of comments like:
"Wow, this ROM is awesome. It's absolutely perfect.....also, sometimes my speaker doesn't work, and the system panel FCs all the time, but THIS ROM is PERFECT! Thanks".
See my point? People get religiously attached to their favorite ROMs and easily ignore the problems to avoid admitting that they aren't using the hot sh*t.
I've tried lots of ROMs, but I always end up going back to a lightly modified stock ROM because for me reliability is the number one item with me. I have yet to find one dev's ROM that doesn't have a fatal flaw, IMHO.

gorelow said:
ok i apologize i was half alseep when i read the first reply, so i opted for the second option and odined \cwm-5.0.2.7-epic4g.tar.md5
i also have a cwm 3.1.0.1
should i have used that? i usually do the acclaim in odin but i just odined the cwm but when i went into recovery of course the deoxed fc09 didnt work because it wasnt rooted but the su.zip doesn't show up on my sd card in recovery. it always does when i odin acclaim. what am i doing wrong?
Click to expand...
Click to collapse
this might help some ...look below

[Q] ghost device autoroot trouble?

I've used SFHubs Odin OC to move from ICS back to GB, and then the auto root tool to inject custom recovery. Specifically EL29 Odin OC and then Auto root Rogue Recovery. Several times, no trouble. From my laptop. Recently I used the same laptop to root my friends E4GT with El29 Odin OC (worked just fine) and then Auto root to install Rogue recovery. When I boot into recovery it looks and acts typical. But the recovery cannot properly flash any roms or properly restore a nandroid. It looks normal, but flashes zips too quickly and upon reboot I get a soft brick (hangs at splash screen). Luckily I was able to pull battery and get back to Odin mode.
Does anyone know why this happened? Is the auto root failing because I'm using the same laptop for two different E4GTs? Is there a ghost device borking the recovery installation? Thanks in advance for your help.

issues
Ive had the same thing happen to me.I did 2 things different at the same time so I dont know which one actually helped.
Used a difderntt USB cable(the cable that came for the.phone)
Deleted Odin the downloaded it again.
Worked after that I hope this helps.

Dr. Fed said:
I've used SFHubs Odin OC to move from ICS back to GB, and then the auto root tool to inject custom recovery. Specifically EL29 Odin OC and then Auto root Rogue Recovery. Several times, no trouble. From my laptop. Recently I used the same laptop to root my friends E4GT with El29 Odin OC (worked just fine) and then Auto root to install Rogue recovery. When I boot into recovery it looks and acts typical. But the recovery cannot properly flash any roms or properly restore a nandroid. It looks normal, but flashes zips too quickly and upon reboot I get a soft brick (hangs at splash screen). Luckily I was able to pull battery and get back to Odin mode.
Does anyone know why this happened? Is the auto root failing because I'm using the same laptop for two different E4GTs? Is there a ghost device borking the recovery installation? Thanks in advance for your help.
Click to expand...
Click to collapse
Are you sure your friend's phone has an external sdcard?
If not, pay attention to commands that work on internal or external cards. Some areas you toggle internal/external mode. Some areas you choose specific options that work with internal or external.

sfhub said:
Are you sure your friend's phone has an external sdcard?
If not, pay attention to commands that work on internal or external cards. Some areas you toggle internal/external mode. Some areas you choose specific options that work with internal or external.[/QUO
**********************
First of all, thank you for all your awesome work. I am honored by your reply.
I am not sure exactly what you mean by toggling external vs internal. Rogue gives you the option to choose where to read from or nandroid to; I typically use the external SD.
Yes, my friend's E4GT does have an external SD card. Rogue recovery did write to it when I nandroided her EL29 setup, and it did read the install zip from the SD card as well. I wiped with Calkulin's format-all, then installed the rom (in this case Phantom's excellent Blazer). I knew something was wrong when it flashed, because it flashed way too quickly. After the reboot and subsequent Galaxy S2 splash screen to infinity, I pulled the battery, booted to Odin mode, restored EL29 thanks to your fantastic Odin OC, injected Rogue thanks to your swanky Autoroot tool, attempted another rom flash, same result, Odin OC, back to EL29 stock, Autooot again. Then I attempted to restore the nandroid of her EL29 setup, and that resulted in an MD5 error, which also led to a soft brick. So I Odin OC'd once again and called it a day.
My phone has never had this problem. I think I'll Odin OC and Autoroot tonight, and then restore one of my nandroids just to see if it works. I don't know whats up, but the trouble started when a second phone was added to the equation.
Click to expand...
Click to collapse

Basically when CWM comes back right away from an operation, usually some error occurred. One error might be using an external sdcard when it isn't present. There are other possible errors, but that was the most obvious one to ask about.

sfhub said:
Basically when CWM comes back right away from an operation, usually some error occurred. One error might be using an external sdcard when it isn't present. There are other possible errors, but that was the most obvious one to ask about.
Click to expand...
Click to collapse
I appreciate your help. Thanks for FD10 btw, i just got done OC'ing it...awesome!

Ok i had this same problem. After OCing back to stock rooted EL29 Reinstall CWM rogue with adb auto root. This will give you a fresh copy of CWM rogue and shouldn't throw you into a boot loop. Also make sure you do a full data wipe and wipe all cashes then run Calkins format all zip prior to running the nandroid backup. Should be good. Hope this helps.

Really weird problems.

This has become quite infuriating.
I was on The Hybrid 1.3 when by phone was randombly freezing. I needed to pull the battery to reset it. This caused ALL of my apps to lose their data. (Facebook was logged out, netflix was logged out, Titanium backup lost its direction to the folder on my SD card)
I thought this was odd, so I downloaded another ROM to try and fix the problem. I downloaded the new rom and went into recovery. Flashed new rom, cleared cache, cleared dalvik, but then as I tried to do a factory reset in CWM my phone resets and comes back to recovery. This happens every single time I try to do it in CWM.
ROM booted fine but has many wierd problems (probably that go with being unable to factory reset)
So i downloaded TWRP and tried flashing that by odin, only to get an unfixable bootloop.
So odin'd back to CWM, factory reset problem still persists.
So at this point I decided to go back to stock and turn this phone in because there is no reason it should be doing this.
And now my frustration about trying to get back to the stock ROM. WHY THE HELL IS THERE NOT AN ODIN FLASHABLE STOCK ROM?! Or any rom for that matter.
In CWM i have to put all .zips on my external SD, because the internal one REFUSES to mount.
The .zip from HERE is not working for me at all. I try to flash it and it says it completes in about a second. I reboot and it just stays at the samsung screen and never goes any further.
I remember back with my Captivate, if anything went wrong as long as you got back into download mode, you could one click odin your way back to normal and start all over. It's like every thread in this devices forum is purposefully vague and confusing, things are not explained well at all and people talk about mysterious version of files and things without ever actually providing a link.
This is becoming a real pain in the ass to try and get my phone back to stock or even useable again. Does anyone have any ideas?

I just tried looking for you and wow, i didn't realize that we really don't have a flashable ODIN stock rom....
best thing i found was...
http://forum.xda-developers.com/showthread.php?t=1992303

Use this toolkit to go back to a stock att galaxy note 2.....http://forum.xda-developers.com/showthread.php?t=2052779

lmike6453 said:
I just tried looking for you and wow, i didn't realize that we really don't have a flashable ODIN stock rom....
best thing i found was...
http://forum.xda-developers.com/showthread.php?t=1992303
Click to expand...
Click to collapse
We do have ODIN flashable stock firmware...(stock rom, kernel, modem, recovery). go the Android DEV forum.. STICKY "One Stop Shop for Note2". In there you'll find everything you need. Look under section 5 "FIRMWARE". You can also go to SamMobile.com website... under "Firmware", and in the search box, type "I317". The downloads are "zip", but those are not flashable zip... download that file and use 7-ZIP to extract the tar (xxxxxx.tar.md5"). Use that tar in Odin. Follow instructions in sticky for how to load file/use Odin if not familiar.

Did i softbrick my device? Please help!

So i reset my GS3 yesterday. I am running a stock rooted phone.. My phone has always been fine but after a reset through the phone the phone never loaded back up. It was stuck on the samsung screen. I tried pulling the battery out a few times. I went into my CWM recovery and tried wiping both caches with no luck. I tried restoring the phone and that didn't work. I finally tried wiping all data and now the phone won't boot at all. It says phone can not boot and will go into odin mode. Odin will recognize my phone though. What should i do? Should I try to restore my phone to factory through odin? I can't find the stock sprint version tar file. I could only find the verizon one. Can someone help me and tell me what is the best step for me? I can get into CWM but the phone won't boot.

wings9130 said:
So i reset my GS3 yesterday. I am running a stock rooted phone.. My phone has always been fine but after a reset through the phone the phone never loaded back up. It was stuck on the samsung screen. I tried pulling the battery out a few times. I went into my CWM recovery and tried wiping both caches with no luck. I tried restoring the phone and that didn't work. I finally tried wiping all data and now the phone won't boot at all. It says phone can not boot and will go into odin mode. Odin will recognize my phone though. What should i do? Should I try to restore my phone to factory through odin? I can't find the stock sprint version tar file. I could only find the verizon one. Can someone help me and tell me what is the best step for me? I can get into CWM but the phone won't boot.
Click to expand...
Click to collapse
If you can get into recovery mode, you can just restore a nandroid backup (if you have one made). If you don't have one, you can wipe /system, /data, and the caches and reflash your Rom (provided you have it saved on your SD card).
If none of the above work, download mode is your best friend.
You can get into Download (Odin) Mode. That's a good thing. Sextape has the md4 TAR file for your over in their thread (warning, outside link). They have the stock unrooted as well as stock rooted file. Since you have already wiped your data, you might as well flash the "Restore" version:
"Restore" Versions - Wipes your user data
SPH-L710_MD4_1130792_Stock_Restore [EXE|TAR.MD5.GZ]
SPH-L710_MD4_1130792_Rooted_Restore [EXE|TAR.MD5.GZ]
Click to expand...
Click to collapse
If you know how to use Odin, you can just downlaod the TAR file, but I recommend using their auto-extractor (the exe file), since it's well tested and there's less chance of user error.
All that being said, I'm curious to how your phone became "softbricked." Did you install any apps or mods recently that could've caused it? Custom Kernel?
It sounds like you eventually ended up wiping /system, which would be why you can't boot up now. I haven't heard of it automatically going into download mode because of that, but I haven't tested it on my phone, either.

try rwilco 12's android file repository. he has everything you will need
http://www.rwilco12.com/

You can also take the sd card out plug into a computer download a rom zip put it on the sd card pop it back into the phone and flash through the custom recovery which should be there.
Sent from the future via Xparent Green Tapatalk 2

Thanks for the help everyone. I guess I didn't soft brick the phone I just wiped it and there was no rom on it.