Database Info

Need serious help immediately

I tried to flash a aokp rom and before flashing made a back up. Now when I flashed the rom and rebooted the phone im stuck at samsung boot. I can get into recovery. At first it was a messed up recovery i tried to get to an old rom and reinstalled inimitable on reboot still stuck at samsung but can get into red recovery. Backup when reinstalling says cant mount system/! please help me asap I cant do anything I need my phone I am in panic mode.

Have tried reflashing The ROM again...or if you just want to go back to stock see my signature for links to the one click method
...btw your in the wrong section to post this...
The OP for aokp does state to flash twice...did you?...first time with wipes, then you can pull battery ...go back to cwm and reflash...again.

going back to stock is your way. clear all that crap out

http://forum.xda-developers.com/showthread.php?t=1524081

Post one to stock.....
Post two to put cwm back on....
Read with detail...the thread I provided....

Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.

soulysephiroth said:
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
Click to expand...
Click to collapse
We have no ics boot loaders...froyo boot loaders make the recovery look funky...gingerbread boot loaders fix that problem and can be used with froyo, gingerbread and ics ...not trying to be rude or a jerk just informing you
Sent from my SGH-I997 using XDA

Actually the "messed up" or rainbow recovery is from the lack of gingerbread boot loaders, just figured this out this morning when I attempted to flash aokp uniporn. Once I did the heimdall one click with bootloaders checked (gingerbread boot loaders) I was able to successfully flash the aokp rom and recovery works perfectly. Its really better not to reply when one does not know what they are talking about oh and I was still able to reflash a gingerbread rom as well although I probably won't go back to gingerbread again since aokp is the **** and runs super smooth
Sent from my SGH-I997 using xda premium

Please move this thread from the Development Section.
edit- Thanks for moving it.

Sorry about posting so quickly in wrong section. I just know the guys who post in here are pros. I used heimdall and everything is back to stock, no superuser. Should that be right, am I now not rooted? I havent tried to boot into recovery, but I think I have it still. Can I just follow root methods if I want to go back to root? Thanks again.

I my experiences, I've noticed our phones use a form of "Cumulative" Upgrade system, where You have to essentially go from Froyo to GB to ICS or things go haywire when you actually start using your ICS Rom..
I've tried using Heimdall to flash back to stock, but it doesn't seem to fix all my files from time to time, so I still use GTGs Ultimate Unbrick, and once it starts up as you're in Recovery Mode do a Factory Reset/Wipe Cache Partitions, it helps with not having the "Google Authentication Failed".
It's a long process from start to finish either way, so i figure save yourself the hassle for the long run and wipe it fresh...

I used heimdall without clicking the GB bootloaders checkbox. Upon reboot after sucessfully flashing everything, my phone shows the rainbow color thing then boots normally. I have no seen any issues other than that, however I only got it back up and running about an hour ago. I will see as the day progresses what happens. I just would like to know where I go from here to reacquire root priveleges. When I try to boot into recovery with the button combo I get a rainbow colored screen and nothing else showing, should I re-run heimdall with gb bootloaders box checked?

IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...

drnecropolis said:
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
Click to expand...
Click to collapse
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA

Cjohns8792 said:
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....

bigjoe2675 said:
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
Click to expand...
Click to collapse
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.

Cjohns8792 said:
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Click to expand...
Click to collapse
Aft your 1st flash...dont close program...but put your phone back into download mode again and then it should allow you to check the box...then..

You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.

Axiomkid said:
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Click to expand...
Click to collapse
Can't access recovery, it just shows a full rainbow screen.

Cjohns8792 said:
Can't access recovery, it just shows a full rainbow screen.
Click to expand...
Click to collapse
my suggestion is do the method i mentioned..

Need Help Fixing Someone's Cappy

Ok so yesterday I received a cappy from someone on here that I told them I would try and fix. I am not charging them anything and am actually paying shipping back to them. When I received it and turned it on it was stuck at the end of the cornkernel bootlogo. I thought hey this will be easy and flashed the heimdall version of I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click. Phone rebooted and is now stuck at the att logo. So I flash cornkernel, its stuck at the end of cornkernel bootup. So I decided on a whim to try and flash this kernel Devil3_1.1.3_HB_cappy_CFS_BLN_VC_20120807, luckily that got me into recovery, so I did a full backup of all the stuff on his internal storage and completely wiped the phone, wipe data/factory reset, wipe dalvik cache, format boot, format system, format sdcard, format cache, format data, format datadata (yes I know I wiped some things twice) . Then I flashed my rom, it just reboots to recovery after the flash, still reboots after a reflash of the rom. I then wiped everything again and tried flashing CM9's latest nightly to see if I could get it to boot up. Still reboots to recovery. So far all together I have flashed I897UCJI6-OCD-REV02-Low-designgears, i897uckk4 Odin One Click CONTAINS Bootloaders, Re-partition, Full Wipe, I897UCKF1_withBL,SGH-I897_I897UCKJ3, KK4-SE-One-Click, JF6 With Bootloaders, SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click Followed By I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click both are heimdall. All of those either left it stuck at att or kernel screen after I flashed a kernel. Anyone got any ideas? I am almost to my wits end.

Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium

4-2ndtwin said:
Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Already have that is my go to file actually and I tried that before going the heimdall route. Thanks Anyways.

You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium

-SGA- said:
You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Thanks for the idea. It didn't work tho. I am still at the same spot, phone keeps rebooting to recovery.

have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd

stayintwisted said:
have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd
Click to expand...
Click to collapse
Not that I know of, It isn't my phone so I do not know the history other than him saying it didn't boot past the kernel screen and receiving it and seeing that and then what I have done. Normally the sd card data from what I have seen is wiped when the eu bug happens from what I have read, maybe I am wrong, but since I backed up his data off the sdcard that is why I do not believe it has had the eu bug.

Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.

cbalt said:
Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.
Click to expand...
Click to collapse
Long story short, recovery is iffy at best for me. I went through something similar to this when trying to go from CM10 back to CM9 for the first time. Ever since then recovery has not been right.
What I did was
Install a stock one-click with bootloaders, used odin to flash speedmod kernel and then used that recovery to flash CM9 in three successions wiping everything each time. Somehow it took, and now I am no longer a crack flasher because I have the same kernel splash screen problem every time.
So,
Use this http://www.mediafire.com/?5rcofbzusoor6mv
PDA button in Odin3 1.7: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Boot into recovery.
Flash your ROM
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Try to boot normally.

Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.

There is a place that has rogers stock roms
cbalt said:
Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.
Click to expand...
Click to collapse
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way

sunfirestorm said:
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way
Click to expand...
Click to collapse
I have already tried all three of the Rogers One Clicks with none of them actually doing anything more than the Captivate One Clicks, It still doesn't boot past the first screen. Thanks for the input though.

You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work

fohdeesha said:
You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work
Click to expand...
Click to collapse
I'm going to do your steps again which is more or less what I have already done. I am waiting to hear back from the person so I can ship him the phone back and he can send it to MTV or someone or just junk it, its his phone and his choice. At this point I would say it needs Jtag or Unbrickable mod + repair. Although I am still trying ideas of mine and anyone elses lol.
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery

Well if the one clicks are successfully writing primary and secondary bootloaders and it's still not working, a jtag isn't going to do anything else. It almost sounds like the memory has a few corrupt blocks, but I can't say until you flash 2.3.5 BL's and see what happens
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
cbalt said:
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery
Click to expand...
Click to collapse
Oh jeez looks like the memory is failing then

[Q] issues installing liquid smooth rc7

I've been using liquid smooth since rc3 and have had no issues upgrading until the most current version--rc7. I downloaded the ROM several times to ensure there wasn't any issues with my download, but I encounter the same issue after a clean flash which is the inability to get past the black screen after the Samsung logo. I've performed factory/data resets prior to flashing rc7 but to no avail. I even flashed the latest cm10 nightly build with no issues. I've restored my rc5 nandroid but really want rc7. Any suggestions will be appreciated.
BTW, I posted this here because I'm not allowed to post in the liquid smooth developers forum

try formatting system after the data wipe, then flash rc7.

dmalikyar said:
I've been using liquid smooth since rc3 and have had no issues upgrading until the most current version--rc7. I downloaded the ROM several times to ensure there wasn't any issues with my download, but I encounter the same issue after a clean flash which is the inability to get past the black screen after the Samsung logo. I've performed factory/data resets prior to flashing rc7 but to no avail. I even flashed the latest cm10 nightly build with no issues. I've restored my rc5 nandroid but really want rc7. Any suggestions will be appreciated.
BTW, I posted this here because I'm not allowed to post in the liquid smooth developers forum
Click to expand...
Click to collapse
wipe before flashing, and after flashing again just to make sure, and if that doesn't work, you can always odin back to stock rooted and drop the rc7 files back on your sd card (or unless you drop them on your external sd card, you can flash it immediately after getting the pass notification from odin)

droidstyle said:
try formatting system after the data wipe, then flash rc7.
Click to expand...
Click to collapse
Tried that and it made no difference.

dmalikyar said:
Tried that and it made no difference.
Click to expand...
Click to collapse
try using odin......just remember after you odin back to the root66 image, you have to reinstall CWM and doesn't hurt to make sure ur bootloader is unlocked using the 1.2 version of the ez unlock then flash again

digitalsynner85 said:
wipe before flashing, and after flashing again just to make sure, and if that doesn't work, you can always odin back to stock rooted and drop the rc7 files back on your sd card (or unless you drop them on your external sd card, you can flash it immediately after getting the pass notification from odin)
Click to expand...
Click to collapse
I'll try the Odin route. I'll go back to root66 and try it from there.

dmalikyar said:
I'll try the Odin route. I'll go back to root66 and try it from there.
Click to expand...
Click to collapse
i was having issues with nfc not working and a few other items that other people weren't having and decided that after approximately 500 different flashes that something i flashed for nfc fixes on jellybean or ics roms that didn't support the libs for nfc could've borked something up and just wasn't noticeable until i went to an aosp based rom, and sure enough it worked, so if anything you'll have a nice crispy fresh stock device to play with again if the same issue shows up w/ liquid

digitalsynner85 said:
i was having issues with nfc not working and a few other items that other people weren't having and decided that after approximately 500 different flashes that something i flashed for nfc fixes on jellybean or ics roms that didn't support the libs for nfc could've borked something up and just wasn't noticeable until i went to an aosp based rom, and sure enough it worked, so if anything you'll have a nice crispy fresh stock device to play with again if the same issue shows up w/ liquid
Click to expand...
Click to collapse
now the truth comes out...if you would of gave this information from the get go I too would of said to simply flash back to stock and start fresh. its all in the details folks.

imklaho your
droidstyle said:
now the truth comes out...if you would of gave this information from the get go I too would of said to simply flash back to stock and start fresh. its all in the details folks.
Click to expand...
Click to collapse
I Odin'd root66 and installed the ez unlocker as well as clockworkmod via rom manager. I went into recovery and wiped data/factory reset/wiped cache/wiped dalvik cache. I then installed LS RC7. It went through the installation and indicated that it completed. After I reboot, I briefly see the Samsung logo, then the screen is completely black. No boot animation. I let it set for over 20 mins. and nothing happens. This is absolutely bizarre. I've tried 3 different downloads. I'm at a loss. Is there a way to convert the zip to an img and odin it on?

KT747-Kernel-AOSP-JB-VZW-10-31-2012.zip
I'm still unable to install RC7. However, when I try the KT747 Kernel, I get the same symptoms (black screen after flash). I'm wondering if the symptoms are related. Anyone have this issue flashing KT747?

dmalikyar said:
I'm still unable to install RC7. However, when I try the KT747 Kernel, I get the same symptoms (black screen after flash). I'm wondering if the symptoms are related. Anyone have this issue flashing KT747?
Click to expand...
Click to collapse
I've had a similar situation. I flashed RC7 and afterwards it booted to the liquid not animation and afterwards just went black, I had never experienced that before so I left it for 10 mins and the hit the power button and got no response. I finally did a battery pull and then booted into CWM and fixed permissions, yet again, and it finally booted. I don't know if this will help you any but I hope so. Honestly the way it boots and then stops and starts over reminds me of kexec. Also after having this problem on RC7 I decided to flash PA 2.52 and had the same issue with it and had to do the same steps to make it boot the first time. I am going to odin completely back to stock tonight because I am experiencing a crap load of issues after I flashed RC7.
And yes I clean flash everything, even when I just go to a newer release of what I'm currently running.
Sent by one of my many Anthromorphic Personifications

shangrila500 said:
I've had a similar situation. I flashed RC7 and afterwards it booted to the liquid not animation and afterwards just went black, I had never experienced that before so I left it for 10 mins and the hit the power button and got no response. I finally did a battery pull and then booted into CWM and fixed permissions, yet again, and it finally booted. I don't know if this will help you any but I hope so. Honestly the way it boots and then stops and starts over reminds me of kexec. Also after having this problem on RC7 I decided to flash PA 2.52 and had the same issue with it and had to do the same steps to make it boot the first time. I am going to odin completely back to stock tonight because I am experiencing a crap load of issues after I flashed RC7.
And yes I clean flash everything, even when I just go to a newer release of what I'm currently running.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
Thanks for the tip. I did as you instructed by fixing the permissions after a failed boot but to no avail. I've gone through the process of odin and root66 and then installing ez unlock and CWM but it just won't boot into RC7. I had no issues with RC3 and RC5. I'm at a loss.

dmalikyar said:
Thanks for the tip. I did as you instructed by fixing the permissions after a failed boot but to no avail. I've gone through the process of odin and root66 and then installing ez unlock and CWM but it just won't boot into RC7. I had no issues with RC3 and RC5. I'm at a loss.
Click to expand...
Click to collapse
Have you tried TWRP recovery as opposed to CWM?

shangrila500 said:
Have you tried TWRP recovery as opposed to CWM?
Click to expand...
Click to collapse
I installed twrp and I really like the interface but it didn't resolve the issue of flashing RC7. I've installed paranoid android and can install aokp and cm10 with no problems. I can't install RC7 or slim beans.

Cannot install Liquid Smooth
Yah the guy at Liquid Smooth is kind of a butt wipe. I understand the desire to have a screen capture and a logcat but if the user can't even install the flash how is a screen capture going to help. Maybe a logcat could. But either way why be an A hole about it.
I am having the same issue, I even formatted my system and still LiquidSmooth says it flashed but it just refuses to boot. I have used Odin to install the stock JB 4.1.1 from Poland but I still get the same problem. I do believe it has something to do with having tried CaponMod4NSS_3.0 the day before. Still I would think formatting the system would resolve that.
Any ideas? I will try to install the Samsung 4.1 ROM with Odin to see if that helps.

[Q] Stuck on boot from embryo 6

I'm stuck on the fuzzy samsung logo right after the sharp one, and right before the colorful boot animation.
Not vibrating repeatedly, but I checked and cleaned the power button.
It was acting buggy after having embryo 7 for a long time with no problems.....Then things started happening a lot, so I changed back to 6. Then one day recently embryo 6 locked up on boot and here I am!
I don't know what caused all this, but I can't get in to recovery either. It looks like it's going to, but then it freezes on the CWM start up screen. Never could get it in to recovery, but I was able to get it in to download mode, AND it looked like I successfully flashed the stock firmware according to Odin. BUT then it froze on at&t screen during start up. AND THEN went back to being frozen on mohans fuzzy samsung screen.
I really was trying to search, but I can't find it.... Help? Anyone....?

Dogs you do factory reset after Odin?

jd1639 said:
Dogs you do factory reset after Odin?
Click to expand...
Click to collapse
It looked like it was trying to restart after Odin finished the install, and the phone never made it past the water drop. Froze in the middle of that part. After a long time I finally unplugged it, and touched the power button. Then it went back to the original screen I was stuck on, and I could never get it to go in to CWM. It starts to, and then gets stuck.

I'm guessing you flashed cymbaline 3.8 on embryo 6. That kernel has issues. Reflash with 3.5 and see what happens. Should be stable then

icenight89 said:
I'm guessing you flashed cymbaline 3.8 on embryo 6. That kernel has issues. Reflash with 3.5 and see what happens. Should be stable then
Click to expand...
Click to collapse
I was just trying to go back to stock. Are you saying that the kernel will still be different even though I was going back to stock through Odin?
I liked mohan's ROM's, but I guess he got a different phone. I never had problems before, but if it's a kernel I can flash will that work through Odin?
Sorry if my questions are annoying, but I just want to make sure I can do it through Odin, AND I don't want to flash it if I'm too far gone for it since I can't even get in to recovery.

jwtruth35 said:
I was just trying to go back to stock. Are you saying that the kernel will still be different even though I was going back to stock through Odin?
I liked mohan's ROM's, but I guess he got a different phone. I never had problems before, but if it's a kernel I can flash will that work through Odin?
Sorry if my questions are annoying, but I just want to make sure I can do it through Odin, AND I don't want to flash it if I'm too far gone for it since I can't even get in to recovery.
Click to expand...
Click to collapse
I dont know whats the problem, but why you no try embryo 7?, i installed it yesterday with cymbaline 3.8 and not issues at the moment. I flashed it with CWM, i dont know why you are talking about odin, but if im wrong its ok, i installed embryo 7 with cwm.
Hope you understand me, english its not my first language.

-LuVaN- said:
I dont know whats the problem, but why you no try embryo 7?, i installed it yesterday with cymbaline 3.8 and not issues at the moment. I flashed it with CWM, i dont know why you are talking about odin, but if im wrong its ok, i installed embryo 7 with cwm.
Hope you understand me, english its not my first language.
Click to expand...
Click to collapse
I can't get in to recovery mode. Only recovery mode.
That's what I'm trying to figure out is just how to get to recovery, or anything else besides download mode.
And yes. I liked embryo 7 a lot. But something started happening about 2 1/2 months after I flashed it with no problem before that.
I love the arms at boot up..

jwtruth35 said:
I can't get in to recovery mode. Only recovery mode.
That's what I'm trying to figure out is just how to get to recovery, or anything else besides download mode.
And yes. I liked embryo 7 a lot. But something started happening about 2 1/2 months after I flashed it with no problem before that.
I love the arms at boot up..
Click to expand...
Click to collapse
You can have "the arms at boot up" without that rom.
To get into recovery, which seems like it's damaged for you, flash TWRP from odin.
http://forum.xda-developers.com/showthread.php?t=1773659

jwtruth35 said:
I can't get in to recovery mode. Only recovery mode.
That's what I'm trying to figure out is just how to get to recovery, or anything else besides download mode.
And yes. I liked embryo 7 a lot. But something started happening about 2 1/2 months after I flashed it with no problem before that.
I love the arms at boot up..
Click to expand...
Click to collapse
Ok, maybe a solution could be install TWRP, or my solution could be installing the oficial android 4.1.2 from odin and then download the CWM recovery and proceed to flash Embryo.

-LuVaN- said:
Ok, maybe a solution could be install TWRP, or my solution could be installing the oficial android 4.1.2 from odin and then download the CWM recovery and proceed to flash Embryo.
Click to expand...
Click to collapse
I appreciate the help, and I did try to install the official 4.1.2 from Odin. Twice. Both times the screen from odin looked exactly like it was supposed to if it was successful. It then tried to restart my phone as part of the install process, and then the phone freezes on start up screen......and done.
CANNOT get the phone in to recovery mode every time I try, but it goes in to download mode no problem.
That's why I'm here and still scratching my head. I'm stuck using a fusion I usually just have for my kid as a toy around the house.

lingowistico said:
You can have "the arms at boot up" without that rom.
To get into recovery, which seems like it's damaged for you, flash TWRP from odin.
http://forum.xda-developers.com/showthread.php?t=1773659
Click to expand...
Click to collapse
I just saw this. Time to try it, thanks.

jwtruth35 said:
I appreciate the help, and I did try to install the official 4.1.2 from Odin. Twice. Both times the screen from odin looked exactly like it was supposed to if it was successful. It then tried to restart my phone as part of the install process, and then the phone freezes on start up screen......and done.
CANNOT get the phone in to recovery mode every time I try, but it goes in to download mode no problem.
That's why I'm here and still scratching my head. I'm stuck using a fusion I usually just have for my kid as a toy around the house.
Click to expand...
Click to collapse
So u need to use Odin and flash a stock image back on the phone, go to sammobile.com and DL the firmware for ur device then place the phone in download mode load the tar file in Odin and click start, when it's done DL the latest twrp as its a little better than cwm because its updated more regularly, then use Odin to flash the recovery to the device and now u are back to stock rooted and from there with twrp, all is possible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

lingowistico said:
You can have "the arms at boot up" without that rom.
To get into recovery, which seems like it's damaged for you, flash TWRP from odin.
http://forum.xda-developers.com/showthread.php?t=1773659
Click to expand...
Click to collapse
Thank you so much!!! It's been a miserable 4 or 5 days, but I was able to get my phone back up and running!

soupysoup said:
So u need to use Odin and flash a stock image back on the phone, go to sammobile.com and DL the firmware for ur device then place the phone in download mode load the tar file in Odin and click start, when it's done DL the latest twrp as its a little better than cwm because its updated more regularly, then use Odin to flash the recovery to the device and now u are back to stock rooted and from there with twrp, all is possible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks to you also. Everything's right with the world again.

[Q?] Rebooting issues

Ok so I have quite a strange problem. Whenever I try to reboot my phone, either from holding the power button and choosing the "reboot" option on the screen, or by turning the phone off physically, and then turning it back on, my phone does not boot. When I try to turn it on, it shows the Samsung image, and then the screen turns black and nothing happens afterwards. The only way I found around this, is that I have to put my phone into recovery and then do a factory reset.
Currently, I'm running BeanStalk v4.3.1009, but I've also flashed the latest version of Slimbean and the samething happens. I used Odin to flash back into the stock Rogers GB firmware and I've gotten the phone to successfully reboot.
I then flashed Beanstalk and I was again unable to successfully reboot the phone.
Any ideas what's going on? I'm using TWRP v2.5 and then updated to v2.6 after going back to the original Rogers GB firmware, if that matters.

bluecrush69 said:
I'm using TWRP v2.5
Click to expand...
Click to collapse
This is the problem.

Should I be using CWM? I updated to TWRP 2.6.3 and flashed the roms, but I'm still getting the same issue when trying to install the latest version of Slimbean/Beanstalk. The problem doesn't occur if I try an older version of Beanstalk though.
Oh well, I'll just stick with the version that's working for me.

bluecrush69 said:
Should I be using CWM? I updated to TWRP 2.6.3 and flashed the roms, but I'm still getting the same issue when trying to install the latest version of Slimbean/Beanstalk. The problem doesn't occur if I try an older version of Beanstalk though.
Oh well, I'll just stick with the version that's working for me.
Click to expand...
Click to collapse
Flash it once with cwm. That'll clear things up then you can go back to twrp

jd1639 said:
Flash it once with cwm. That'll clear things up then you can go back to twrp
Click to expand...
Click to collapse
Can someone explain what's technically wrong with twrp 2.6.3 I've flashed a ton of these 4.3 Roms without issue. Why is everyone saying it's bad?
Sent from my XT1080 using Tapatalk