I've tried to get back to Com Rom several times. All I ever get is bootloops or it just freezes on Samsung.
Anybody care to give me the play by play on how to get there?
Thanks
Sent from my SCH-I500 using Tapatalk
........I happened to do it successfully. I don't know what could be your problem...
Which recovery are you on?
Currently on the one packaged with Nameless.
Sent from my SCH-I500 using Tapatalk
I also Odin'd timesinfinity's recovery from 4.22.11, booted straight into recovery, then flashed ComRom 2.0. Bootloop.
I must be missing something.
Sent from my SCH-I500 using Tapatalk
I have been having problems also since Nameless V4
http://forum.xda-developers.com/showthread.php?t=1138145
I may be wrong, but I was always under the impression when going backward in OS, you have to use ODIN. So you would need to ODIN the full EB01 package, then build your way up from there. Or ODIN to DL09, then OTA to ED04, then flash Comm ROM
Thanks Landshark, I'll give it a try when I get home.
Sent from my SCH-I500 using Tapatalk
Steps I took going from nameless to evil.
reboot recovery
Wipe data, cache, dalvik 3 times. Flashed evil and kernel. Boot to os. Reboot recovery. Enable voodoo. Done. Zero problems
ahh thats my issue.......i forgot to enable voodoo in Recovery....did that the robot ladie did her thing and now bam im all good no more kernel panic issues
Dalamar1320 said:
Steps I took going from nameless to evil.
reboot recovery
Wipe data, cache, dalvik 3 times. Flashed evil and kernel. Boot to os. Reboot recovery. Enable voodoo. Done. Zero problems
Click to expand...
Click to collapse
No Odin?
Sent from my SCH-I500 using Tapatalk
bgoodwin said:
No Odin?
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
try his method first...if a no go still then odin back down to DL09(make sure re-partition is checked) and ota or flash to current ED04....then odin recovery and then flash your rom and kernel of choice
bgoodwin said:
No Odin?
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
No. No Odin.
Dalamar1320 said:
Steps I took going from nameless to evil.
reboot recovery
Wipe data, cache, dalvik 3 times. Flashed evil and kernel. Boot to os. Reboot recovery. Enable voodoo. Done. Zero problems
Click to expand...
Click to collapse
^^This^^
Worked great, I escaped Nameless with my sd card intact.
Thanks, y'all
Sent from my SCH-I500 using Tapatalk
Related
It keeps rebooting itself at random times, is there a fix
Sent from my SCH-I500 using XDA App
dco717 said:
It keeps rebooting itself at random times, is there a fix
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Odin back to DJ01 stock, re-root, reflash Superclean after WIPING data and cache.
i was on stock 2.2 eb01 after a wipe
why would i got back to stock dj01
dco717 said:
i was on stock 2.2 eb01 after a wipe
why would i got back to stock dj01
Click to expand...
Click to collapse
I don't care what anyone else says, the stock all-in-one EB01 has issues. Do it or not, the choice is yours, but it's the only way to TOTALLY wipe and fix the force reboots. You're not the only one with this problem, read around. Odin the all-in-one DJ01, then flash whatever EB01 you want if you want to fix it.
They say its because of the music widget on lock screen that's why they sent out 2.9.1 but i can't get into red recovery mode
Sent from my SCH-I500 using XDA App
dco717 said:
They say its because of the music widget on lock screen that's why they sent out 2.9.1 but i can't get into red recovery mode
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Here, flash this in Odin. Attached it for you. Sorry if I came across as a tool. And I forgot about the music controls as I don't even use them. But flash this in Odin, then boot into recovery, VOILA, then flash the patch for SuperClean 2.9. Hope this helps.
So i have to flash red recovery in odin? do i need the update file on my sd card still
Sent from my SCH-I500 using XDA App
I can't say for 100% sure that you don't need it AFTER flashing the red. I currently am running S.C. 2.9.1 voodoo EB16 kernel with RED CWR and I do not have the update.zip on my SDcard.
After you ODIN using the PDA button in odin (if you didn't already know ^_^), your phone should automatically boot into CWR red bypassing the stock recovery.
hope that helps!
ima try it
it worked for the red recovery and it said update complete i hope it fixed the random reboots
I odined the new ed01 radio last night and all went well until I went to odin a new clock work. it says pass and everything but when I reboot into recovery with the three finger solute it's the same old blue clock work. Any ideas?
Sent from my SCH-I500 using XDA Premium App
Headcase8911 said:
I odined the new ed01 radio last night and all went well until I went to odin a new clock work. it says pass and everything but when I reboot into recovery with the three finger solute it's the same old blue clock work. Any ideas?
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Where did you get you cwm odin tar?
Sent from my SCH-I500 using XDA App
Flash another kernel. Stock kernel reflashes stock recovery every boot.
Sent from my SCH-I500 using XDA App
times_infinity said:
Where did you get you cwm odin tar?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I downloaded your sexy new blue recovery. I'm using odin3 1.7 from nitro's evil fascination OP.
Sent from my SCH-I500 using XDA Premium App
iwasaperson said:
Flash another kernel. Stock kernel reflashes stock recovery every boot.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
that's the problem I can't flash another kernel because I only have stock recovery. for some reason I can't oden a new recovery. it acts like it goes through but then I reboot with the 3 finger salute and it's in the stock recovery again.
Sent from my SCH-I500 using XDA Premium App
iwasaperson said:
Flash another kernel. Stock kernel reflashes stock recovery every boot.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
what if I pull the battery directly after oden finishes and then do the 3 finger to boot into recovery, would that keep it from going back to stock recovery?
Sent from my SCH-I500 using XDA Premium App
That'll work.
See, you aren't supposed to have the battery in when you use Odin anyways, that way, when it is done flashing, your phone just powers off making it easy to slap in the battery and do the three-finger into cwm at first boot.
Sent from my SCH-I500 using XDA Premium App
agsded said:
That'll work.
See, you aren't supposed to have the battery in when you use Odin anyways, that way, when it is done flashing, your phone just powers off making it easy to slap in the battery and do the three-finger into cwm at first boot.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
I'll try it thanks so much
Sent from my SCH-I500 using XDA Premium App
Headcase8911 said:
I'll try it thanks so much
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
make sure you unplug the phone before you put the battery in. if not, it'll just boot as normal.
There is no ED01 radio that we have available, so I'd be wary of whatever radio file you're flashing. Also, Odin 1.7 doesn't always work properly, try using version 1.3.
imnuts said:
There is no ED01 radio that we have available, so I'd be wary of whatever radio file you're flashing. Also, Odin 1.7 doesn't always work properly, try using version 1.3.
Click to expand...
Click to collapse
it's from adryns thread per his instructions. he calls it ed01, not sure. any idea where I could get odin 1.3?
Sent from my SCH-I500 using XDA Premium App
Side note on this, is there any practical barrier to bundling a kernel with a recovery Odin?
I noticed in the kernel packages that they generally modify /system when they install. So perhaps you would have to odin over data also to run in a script to complete the kernel install at boot. Meh, it would just be nice if installing recovery didn't require immediately wiping kernel and then odining recovery again.
I figured a compromise would be to CWM recovery with the kernel in the same step, then I noted I was just being lazy and it really isn't much trouble to go through once per factory restore.
Side note on this, is there any practical barrier to bundling a kernel with a recovery Odin?
I noticed in the kernel packages that they generally modify /system when they install. So perhaps you would have to odin over data also to run in a script to complete the kernel install at boot. Meh, it would just be nice if installing recovery didn't require immediately wiping kernel and then odining recovery again.
I figured a compromise would be to CWM recovery with the kernel in the same step, then I noted I was just being lazy and it really isn't much trouble to go through once per factory restore.
Click to expand...
Click to collapse
So will the battery pull idea get me a new infinity recovery? I'm bloated here people!!!
Sent from my SCH-I500 using XDA Premium App
Headcase8911 said:
So will the battery pull idea get me a new infinity recovery? I'm bloated here people!!!
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
I would download a CWM Odin file and one of the two odin files from here. Flash one of the two (doesn't matter which you do first) and once it completes, unplug the phone, and then plug it back in holding volume down to get back into recovery and flash the other file. You'll then have a stock kernel that won't re-flash recovery, so if you boot normally, it won't matter. You can also download Odin 1.3 from here
So will the battery pull idea get me a new infinity recovery? I'm bloated here people!!!
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
I would download a CWM Odin file and one of the two odin files from here. Flash one of the two (doesn't matter which you do first) and once it completes, unplug the phone, and then plug it back in holding volume down to get back into recovery and flash the other file. You'll then have a stock kernel that won't re-flash recovery, so if you boot normally, it won't matter. You can also download Odin 1.3 from here
Click to expand...
Click to collapse
Thank-you sir
Sent from my SCH-I500 using XDA Premium App
Let me give some info on my situation:
The phone has unlocked boot loader
I got a replacement phone and wanted to odin back to stock to send back my original phone.
I used Odin to flash back to stock but the phone will not boot and I cannot get into recovery.
I am able to use Odin with success every time. I have followed instruction on how to return to stock and everything goes perfectly until I try to reboot or go into recovery. I just get the Samsung splash screen and it blinks every couple of seconds.
Any ideas?
so you pulled battery, reinsert, three finger combo(vol up/home/power) until you see recovery booting and it wont boot into recovery?
droidstyle said:
so you pulled battery, reinsert, three finger combo(vol up/home/power) until you see recovery booting and it wont boot into recovery?
Click to expand...
Click to collapse
correct, I am able to get into download mode but not into recovery and I have tried everything. I am not a noob but am totally lost here.
I can use Odin without any issue.
droidstyle said:
so you pulled battery, reinsert, three finger combo(vol up/home/power) until you see recovery booting and it wont boot into recovery?
Click to expand...
Click to collapse
I have been using your instructions to go back to stock using odin from any rom. Do I need to flash the PIT with any stock odin file?
I have successful used the route66, Revision3 and Imuts files. all flash in Odin gave me the "SUCCESS" but then I cannot boot into recovery or start the phone.
Could it be because I had an unlocked bootloader? Is there a way to reinstall just a bootloader and/or recovery.
mzimand said:
I have been using your instructions to go back to stock using odin from any rom. Do I need to flash the PIT with any stock odin file?
I have successful used the route66, Revision3 and Imuts files. all flash in Odin gave me the "SUCCESS" but then I cannot boot into recovery or start the phone.
Could it be because I had an unlocked bootloader? Is there a way to reinstall just a bootloader and/or recovery.
Click to expand...
Click to collapse
If you're returning it use the OTA jb image (full wipes and locks boot loader) and the pit file.
Sent from the dark on a Note 2
kintwofan said:
If you're returning it use the OTA jb image (full wipes and locks boot loader) and the pit file.
Sent from the dark on a Note 2
Click to expand...
Click to collapse
I just tried this and got the same results. I got the "PASS" in Odin after flashing the PIT and the stock JB Image. I am still stuck at a slow blinking Samsung screen.
I am open to any ideas
wizeguydesigns had the same problem...you didnt flash the jedi rom prior did u?
droidstyle said:
wizeguydesigns had the same problem...you didnt flash the jedi rom prior did u?
Click to expand...
Click to collapse
Yes, this was my problem exactly!! I know you weren't saying this, but it wasn't the Jedi ROM that did it just to clear that up. It was a ROM that I was beta testing that hasn't been released yet. I was on Jedi ROM prior to flashing the beta test ROM which I think is what you meant.
OP, did you happen to be testing a ROM and this happened? I won't name it but at least tell me that much.
Sent from my SCH-I605 using xda premium
WizeGuyDezignz said:
Yes, this was my problem exactly!! I know you weren't saying this, but it wasn't the Jedi ROM that did it just to clear that up. It was a ROM that I was beta testing that hasn't been released yet. I was on Jedi ROM prior to flashing the beta test ROM which I think is what you meant.
OP, did you happen to be testing a ROM and this happened? I won't name it but at least tell me that much.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
ahh thanks for clearing that up.
WizeGuyDezignz said:
Yes, this was my problem exactly!! I know you weren't saying this, but it wasn't the Jedi ROM that did it just to clear that up. It was a ROM that I was beta testing that hasn't been released yet. I was on Jedi ROM prior to flashing the beta test ROM which I think is what you meant.
OP, did you happen to be testing a ROM and this happened? I won't name it but at least tell me that much.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Yes I was flashing a ROM. It was a sprint rom that i was trying to patch. It was whompasrus. Where you able to fix the issue?
Sent from my SCH-I605 using Tapatalk 2
mzimand said:
Yes I was flashing a ROM. It was a sprint rom that i was trying to patch. It was whompasrus. Where you able to fix the issue?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Yep, that was the ROM that I was testing as well. I know you won't want to hear this, but I wasn't able to fix the issue.
Sent from my SCH-I605 using xda premium
WizeGuyDezignz said:
Yep, that was the ROM that I was testing as well. I know you won't want to hear this, but I wasn't able to fix the issue.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
I had a feeling that is was bricked as I have tried everything I could to fix it. It is not that big of a deal because the screen was shattered on it last week and I paid the insurance for a replacement and was sending it back anyways.
Ok guys I'm on stock rooted right now. Was on rls 7 hyper and the blue kubatan* rom and when rebooting trying mods it froze on custom splash. So I boot into twrp and wipe dalvik and cache. Reboot from twrp and no issues. Restore to stock no problem. Swap batteries on stock and boom custom splash. Went through wipe in recovery and fine but any reboot from stock tw goes straight to custom splash. Did the kernel get messed up or recovery what? Any ideas?
Sent from my SCH-I545 using Tapatalk 2
Fixed it by odin
Sent from my SCH-I545 using Tapatalk 2
oneandroidnut said:
Ok guys I'm on stock rooted right now. Was on rls 7 hyper and the blue kubatan* rom and when rebooting trying mods it froze on custom splash. So I boot into twrp and wipe dalvik and cache. Reboot from twrp and no issues. Restore to stock no problem. Swap batteries on stock and boom custom splash. Went through wipe in recovery and fine but any reboot from stock tw goes straight to custom splash. Did the kernel get messed up or recovery what? Any ideas?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I'm having a similar issue. I did a full wipe and installed Hyper Rls 7 and it was working great. I made no changes or flashed anything new, but when trying to reboot it gets stuck at the Samsung Custom screen. I've waited 30 minutes with no change. I wiped with CWM and reflashed the rom with the same results multiple times. Any ideas short of going back to stock would be appreciated.
rickt1152 said:
I'm having a similar issue. I did a full wipe and installed Hyper Rls 7 and it was working great. I made no changes or flashed anything new, but when trying to reboot it gets stuck at the Samsung Custom screen. I've waited 30 minutes with no change. I wiped with CWM and reflashed the rom with the same results multiple times. Any ideas short of going back to stock would be appreciated.
Click to expand...
Click to collapse
I don't think there is another way. I flashed numerous roms in hope of something that would work and no. Phone also ran hot like over 100°+ at idle or screen off and lagged bad when I did get it to boot. After flashing back to stock rerooting and restoring my backup it runs like brand new. Wonder is rls 7 is screwing with something?
Play it safe and go back to stock man
Sent from my SCH-I545 using Tapatalk 2
You must flash your Verizon loki kernel after you flash any rom, not all of the roms are loki'ed, so it will hang at the boot screen.
Thanks you...
TheAxman said:
You must flash your Verizon loki kernel after you flash any rom, not all of the roms are loki'ed, so it will hang at the boot screen.
Thanks you...
Click to expand...
Click to collapse
Doesn't apply to us or rom wouldn't have booted first time after install. And a quick wipe of cache boots it so can't be that issue thanks though
Sent from my SCH-I545 using Tapatalk 2
Wrong, it is a kernel issue, try another. I have seen it boot once, then hang the next. Whatever.
TheAxman said:
Wrong, it is a kernel issue, try another. I have seen it boot once, then hang the next. Whatever.
Click to expand...
Click to collapse
Then why would wipe cache make it work? & no issues before with it. Had to be a mod we tried to install
Sent from my SCH-I545 using Tapatalk 2
After running just about every ROM for this device, I recently flashed my first stock based ROM (cooked 1.8). However since this time I've been unable to flash back to any aosp ROM. I get boot looped on every one. I've tried everything. Yet, I can flash cooked again no problem. I know there's something I'm missing. Any help would be great.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
You have a nandroid backup right? Restore that then flash whatever you want.
Sent from my SGH-I777 using Tapatalk 2
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
adrock74 said:
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Search for Siyah kernel v4.3.3 in the forums and install, restart recovery and flash away. Should take care of it.
T
Sent from my SGH-I777 using Tapatalk 2
I always have kept that kernel on standby but that didn't work. I've tried every kernel. Can't believe backups won't even boot. I flashed cook's ROM wipe before his ROM the first time, wonder if that did something.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Try Odin to stock and start from scratch. A lot of work but hey what do you have to lose. :beer:
Sent from my SGH-I777 using xda app-developers app
First find a compatible Kernel for the AOSP ROM your trying to flash. Flash that Kernel.
Second, after the flashing is done, reformat the device; cache, dalkiv cache and system and system settings.
Third, reboot into recovery mode from the recovery menu itself.
Fourth, flash the kernel one more time.
Fifth, flash the AOSP ROM of your choice.
Sixth, reboot back into recovery menu.
Seventh, reformat once more.
Eigth, reboot the device.
As you should know, the first boot up after flashing a ROM takes the longest. Give it like a minute or two.
If this doesn't work, you have to flash a kernel that was compatible with the "cooked" rom you were using. Then from there do a reformat from the recovery menu. Once reformat is done, flash the AOSP kernel, then flash the AOSP ROM right after. Then reformat once more and reboot as normal.
If that doesn't work, flash compatible kernel with the "cooked" ROM your using now and also relay the cooked ROM, and then use Odin to bring it back to stock un-rooted. From there, do as you wish.
Butchr said:
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
Click to expand...
Click to collapse
That is exactly what needed to be done. Mr cook actually has another thread with cwm flashable wipe scripts that would have done that. Quite handy :thumbup: