I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
t1op said:
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Click to expand...
Click to collapse
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
WayTooGosu said:
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
Click to expand...
Click to collapse
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
lumin30 said:
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
Click to expand...
Click to collapse
Ah I see. But my point was that some ROMs state that the user must be on an ICS ROM/Kernel to flash this. I guess I wasn't very clear as I am new here and lack understanding.
champ1919 said:
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I used Odin to return to stock. I used Super One Click to root. I used root explorer modify the recovery to allow me to boot into "CWM final for Froyo". That much each and every time.
The first time I installed
[TFQ - 30/12/2012]X.A.O.K[Kanged - Xperia Style]
That is an ICS rom. Installed fine with a new CWM.
The second time I installed the same.
The third time I installed
ROM-MTD-TWRP-ICS-4.x-Audiophile
That is another ICS rom. Installed fine with TWRP.
Each and every time, when returning to recovery to flash more, I got stuck. I can't boot to anything except recovery.
My brother suggested that the problem is using the Volume up and down and power button ("three finger salute") to return to recovery instead of from OS power down menu.
For a fourth time I started over again. Now, using the reboot>recovery, everything works fine.
One thing, you need to have ginger bread bootloaders. So, when you say Odin back to stock, are you referring to kj6?
You could cut down some of the work by using Odin to flash a kernel with recovery & root in it. Antonx & drhonk both have kernels that will do that with odin.
I flash bhundven's cm9 Rom before jumping to any of the others(and wipe between). I believe some of the Rom authors have that in their instructions.
Sent from my SGH-T959V using xda app-developers app
Yeah... GB bootloaders, not Froyo. Your return to stock should be a return to GB stock, not Froyo... and your return to stock can be a return to a rooted stock. If you want to make your life less painful.
It's about MTD to BML, not really about the base version. You just don't want to wipe out what allows later stuff to actually work properly...
Thanks for the advice. I haven't used custom roms very much. Trying to figure out which ones to choose was difficult. I started on stock Gingerbread, but everything I encountered in searching indicated that I needed to go back to Froyo to get CWM then go from there. ...Perhaps I kept running into very old instructions? In any case, should I need to go back to stock again some day, I'll try to figure out which GB roms I could use, including root and custom recovery.
I guess the solution to my problem is: 1) flash back to Froyo or Gingerbread; 2) after flashing an ICS+ rom, only go to recovery from OS reboot menu (never "three finger salute").
I'm actually surprised that people don't run into this problem more often, enough to create a sticky about it. I'm sure I'd still be pulling my hair out if my brother hadn't run into the problem on his Fascinate a year ago.
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Theraze said:
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Click to expand...
Click to collapse
Interesting... Perhaps if I went back to a gingerbread stock then upgraded to ICS the problem wouldn't occur?
I'll have to try that the next time I might need to return to stock.
Hello,
First I just want to say thank you to the mods for running a great forum and to the devs for keeping this device current.
I just struggled over a period of days with this issue.
The end result being, that you need to go to CM9 BEFORE you try JellyBean or later!
Just hope this helps someone else who missed that instruction.
Thanks devs/mods/everyone for keeping this device alive!!!! :good::good::good:
*EDIT* correction... i THINK you need to go CM9 Before trying something else
Not all ICS ROMs require CM9, but you must have at least CWM5 recovery to be able to flash CM9 or these ROMs. Follow ROMs' OP instructions.
I personally tested HebMIUI flash over Stock GB with CWM5 (Basic with a twist kernel) without going through CM9.
Related
Sorry for dumb question.. as I am really novice for installing custom rom..
I read similar contents from [BIONIX BIUI] but there is no Q&A of [BIONIX BIUI] here so allow me to post here...
I was in Darky Rom and switched to FusionXII direct through CWM qithout any problem and now hope to flash BINIX BIUI...
Do I have to flash UCKL2's stock bootloader first through ODIN then should flash KJ2 based custom rom or can flash direct through CWM ???
Anything should I be careful when switching from one rom to another ??
Thanks, guys...
Pls consider I am learning step by step...
Yes you still have bootloadets
Sent from my SGH-I997 using xda premium
Loaders
Sent from my SGH-I997 using xda premium
You should avoid messing with bootloaders whenever possible.
The only reason EVER to flash a bootloader on Infuse is to transition from Froyo to Gingerbread - once you're on a Gingerbread bootloader, if you're staying with a Gingerbread ROM, keep the bootloader.
Entropy512 said:
You should avoid messing with bootloaders whenever possible.
The only reason EVER to flash a bootloader on Infuse is to transition from Froyo to Gingerbread - once you're on a Gingerbread bootloader, if you're staying with a Gingerbread ROM, keep the bootloader.
Click to expand...
Click to collapse
I had GB running. Last night I flashed Infused 1.6.0 (Froyo), and then came back to GB rom, with no issues. So I think once we are on GB, we can switch back and forth while being careful not to mess with CWM.
Or maybe I was lucky 'cos the the line in Infused 1.6.0 changelog:
"Removed recovery binary to prevent the phone from booting into green CWM"
stick with gingerbread bootloaders after you install them
I'd avoid Bionix for the time being. I've been doing this for a while and I it's taking some work to get back.. flash around with the others for a while and get some experience.. Doesn't mean you don't have good work nopco..
Ok, thanks guys...
Sorry again for novice question again..
I want to "Stick" to GB bootloarder... the problem is "HOW?"
I read through forum and found out there is no way to check whether I am in GB' bootloader or not...
Already flashed with UCKL2 Stock Rom once, so can I consider I have GB bootloader now ???
I flashed other rom such as MaxQ, FusionXII and re-flash to BIONIX without Rainbow problem so this is ok now ?
Thanks again for advice again, duds..
diablo009 said:
I had GB running. Last night I flashed Infused 1.6.0 (Froyo), and then came back to GB rom, with no issues. So I think once we are on GB, we can switch back and forth while being careful not to mess with CWM.
Or maybe I was lucky 'cos the the line in Infused 1.6.0 changelog:
"Removed recovery binary to prevent the phone from booting into green CWM"
Click to expand...
Click to collapse
During switch between one rom to another, my device also booted in "Green Recovery" then I ODIN with community kernel to get Red CWM recovery to re-flash other rom.
Did I do something wrong ??
Paxunion said:
During switch between one rom to another, my device also booted in "Green Recovery" then I ODIN with community kernel to get Red CWM recovery to re-flash other rom.
Did I do something wrong ??
Click to expand...
Click to collapse
Everyone has their way of installing roms. What's weird is I have no idea how everyone is getting different color recovery screens other than red. The only recovery I've ever had has always been red in Cwm. Simple if your on Froyo if you flash the community kernel v8 reboot into recovery, you'll be in red Cwm and can flash any rom you want without issues. You don't need to worry about changing the kernel cause most roms come with a kernel and will erase the community kernel v8. Why is this all so difficult?
Sent from my SAMSUNG-SGH-I997 using xda premium
Yes, I also though as you explained...
I have flashed GB based rom as I believe... never flashed to Froyo Rom.
So there should be no worries about bootloader or kernel.
But when I flashed BOINIX which is based on stock Kernel, things messed up with shown Rainbow affect and this was caused because I was in Froyo Kernel as I read.
Ok, so now I want to make really sure I am in GB bootloader.
Question is,
If flashed successfully to GB based Rom, bootloader is not to be concerned ??
Is there anyway to flash ONLY GB BOOTLOADER with ODIN to make sure I am on GB bootloader ?
Sorry again for dumb question again...
I am really, really newbie not only for Infuse but for ANDROID totally so need help and advice.
Thanks, Axiomkid and all...
Paxunion said:
Yes, I also though as you explained...
I have flashed GB based rom as I believe... never flashed to Froyo Rom.
So there should be no worries about bootloader or kernel.
But when I flashed BOINIX which is based on stock Kernel, things messed up with shown Rainbow affect and this was caused because I was in Froyo Kernel as I read.
Ok, so now I want to make really sure I am in GB bootloader.
Question is,
If flashed successfully to GB based Rom, bootloader is not to be concerned ??
Is there anyway to flash ONLY GB BOOTLOADER with ODIN to make sure I am on GB bootloader ?
Sorry again for dumb question again...
I am really, really newbie not only for Infuse but for ANDROID totally so need help and advice.
Thanks, Axiomkid and all...
Click to expand...
Click to collapse
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Sent from my SAMSUNG-SGH-I997 using xda premium
Axiomkid said:
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Edit: community kernel v8 works for both froyo and gb. I flash it using sgs kernel flasher from the market and then I'm able to flash gb roms without getting bootloops and other issues. You can't flash a gb kernel over Froyo cause it will cause bootloops and it won't load and you'll have to gtg to stock again.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using xda premium
@Axiomkid,
Thanks for kind advice, now I know clearly,
1) Bootloader is in the kernel so unnecessary to flash separately.
2) Community kernel V8 works both for Gb and Froyo so it will be ok to flash Community kernel v8 to get Red CWM to re-flash other GB Rom from existing GB Rom.
Another question is,
If I want to flash Froyo Rom from existing GB Rom, what is the right way to do and if flash to Froyo Rom, I am on Froyo Bootloader, right ??
Thanks again & Merry Christmas !
If you wanna go back to Froyo use Odin and flash GTG ultimate unbrick to reformat the phone back to original Froyo.
Sent from my SAMSUNG-SGH-I997 using xda premium
It is very important if you install a rom and you don't like the kernel, sometimes it can be flashed with a different kernel but chances are it will screw your phone up. I tried using a different kernel on someone's rom and I had a tint of yellow on my screen. The Devs give us a kernel that works specifically for their rom and should not be replaced with another kernel unless told otherwise. People get errors cause of this and fill up a lot of forum space asking why their phone is screwed up. You just need to read before installing a rom. Each rom includes each own set of directions.
Most kernels allow overclocking and under volting your phone, and to be honest I don't mess with the settings so I don't end up with a burnt CPU
Sent from my SAMSUNG-SGH-I997 using xda premium
Axiomkid said:
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
WRONG. DEAD WRONG.
The bootloader is a COMPLETELY different entity than the kernel.
Custom Gingerbread kernels (such as Infusion-GB and Daily Driver) have a workaround that allows operation with Froyo bootloaders.
However, working video acceleration in the latest leaks can only be obtained with a stock kernel from one of those leaks. If you flash a kernel and system image from a leak (such as UCKL2) and you get rainbows, you need to flash new bootloaders. If you don't get rainbows - you don't need new bootloaders and should avoid flashing them if at all possible.
(Basically, don't flash anything with boot.bin or sbl.bin using Heimdall or Odin once you're on GB bootloaders.)
Entropy512 said:
WRONG. DEAD WRONG.
The bootloader is a COMPLETELY different entity than the kernel.
Custom Gingerbread kernels (such as Infusion-GB and Daily Driver) have a workaround that allows operation with Froyo bootloaders.
However, working video acceleration in the latest leaks can only be obtained with a stock kernel from one of those leaks. If you flash a kernel and system image from a leak (such as UCKL2) and you get rainbows, you need to flash new bootloaders. If you don't get rainbows - you don't need new bootloaders and should avoid flashing them if at all possible.
(Basically, don't flash anything with boot.bin or sbl.bin using Heimdall or Odin once you're on GB bootloaders.)
Click to expand...
Click to collapse
Boy, I wish I read this yesterday.
I had struggled with this yesterday trying to install Bionix using heimdall.
Managd to boot loop in 3e blue recovery several times until I flashed bootloaders in heimdall to get back to a working stock.
Paxunion, if I may suggest, if you are on froyo,
I think it'll be easier for you to use Adam outler's heimdall uckj4 return to stock.
Put your phone in the download mode. Flash it once then flash it again with the bootloader checked.
Go to his second post and flash the kernel to get recovery and then you will have gb bootloader and be able to flash the ROM of your choice.
If you did want Bionix, very nice, use the heimdall package that Dani included in the bionix thread. You won't have to flash the kernel step if you use Dani's heimdall package.
Do not check the repartition or partition box with the bionix flash.
qkster said:
Boy, I wish I read this yesterday.
I had struggled with this yesterday trying to install Bionix using heimdall.
Managd to boot loop in 3e blue recovery several times until I flashed bootloaders in heimdall to get back to a working stock.
Paxunion, if I may suggest, if you are on froyo,
I think it'll be easier for you to use Adam outler's heimdall uckj4 return to stock.
Put your phone in the download mode. Flash it once then flash it again with the bootloader checked.
Go to his second post and flash the kernel to get recovery and then you will have gb bootloader and be able to flash the ROM of your choice.
If you did want Bionix, very nice, use the heimdall package that Dani included in the bionix thread. You won't have to flash the kernel step if you use Dani's heimdall package.
Do not check the repartition or partition box with the bionix flash.
Click to expand...
Click to collapse
I was wondering if anyone actually used that...
good to know it worked out. I've wanted to do a rom with stock kernel for a while but nop can do it better. just glad I could help in a way.
Dani897 said:
I was wondering if anyone actually used that...
good to know it worked out. I've wanted to do a rom with stock kernel for a while but nop can do it better. just glad I could help in a way.
Click to expand...
Click to collapse
I ran into some problem due to checking of the repartition box and screwed up everything. Had to reflashed bootloader to get the phone working again.
I found it was easiest to flash adam's uckj4. Then heimdall fronend your package.
Two steps. Simple. If i have some time, i might do a faq step guide thread in the q a
So i was just wondering but how does CM9 have a kernal if we dont have an ICS kernal?
bradman117 said:
So i was just wondering but how does CM9 have a kernal if we dont have an ICS kernal?
Click to expand...
Click to collapse
It is in the boot.img. So far all Infuse cm9 is based of jt or entropy branching off jt. If you want just the kernel, after you f flash the ROM, you can dump the kernel from bml 7 using dd commamd.
Jt recover ics is such a kernel. Check my thread for the heimdall packed.
Jscott also extracted entropies kernel and i packed into a heimdall 1 click also. I haven't had a chance to test it yet. Pm me if you want a shot at it.
I think having these kernel in a heimdall makes flashing and recovery from cm9 simple.
Dl mode. Flash. factory reset. And it's ready for cm9 ROM.
qkster said:
It is in the boot.img. So far all Infuse cm9 is based of jt or entropy branching off jt. If you want just the kernel, after you f flash the ROM, you can dump the kernel from bml 7 using dd commamd.
Jt recover ics is such a kernel. Check my thread for the heimdall packed.
Jscott also extracted entropies kernel and i packed into a heimdall 1 click also. I haven't had a chance to test it yet. Pm me if you want a shot at it.
I think having these kernel in a heimdall makes flashing and recovery from cm9 simple.
Dl mode. Flash. factory reset. And it's ready for cm9 ROM.
Click to expand...
Click to collapse
I've used your heimdal package of the ics kernel multiple times as I constantly brick my phone trying to port and have to go back to stock...I then flash the ics kernel and I'm back up and running ready for ics...I just wish I could only flash the kernel...always gotta go back to stock first...but with your heimdal I'm back up and running in no time
Sent from my SGH-I997 using XDA
As for the kernel...as far as I know it isn't a full on ics kernel...it is a gingerbread kernel that has been heavily modified to run ics however it will not work with gingerbread any longer...
So its an ics kernel created from a gingerbread kernel...insane development going on there...got tons of respect for jt and entropy getting that done...
Sent from my SGH-I997 using XDA
mg2195 said:
I've used your heimdal package of the ics kernel multiple times as I constantly brick my phone trying to port and have to go back to stock...I then flash the ics kernel and I'm back up and running ready for ics...I just wish I could only flash the kernel...always gotta go back to stock first...but with your heimdal I'm back up and running in no time
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
I don't think you need to go back to stock with system files that you will overwrite anyway.
Flash just the kernel. Wipe.
And flash the ics.
Maybe use entropy kernel flash then a jt kernel if you can't recover with only jt.
qkster said:
I don't think you need to go back to stock with system files that you will overwrite anyway.
Flash just the kernel. Wipe.
And flash the ics.
Maybe use entropy kernel flash then a jt kernel if you can't recover with only jt.
Click to expand...
Click to collapse
What do you mean by an entropy kernel flash then a jt? I've tried just flashing the jt one you have and no matter what rom I flash...when I hit that reboot button it will always boot back to recovery...
Anyways im back up and running in under 10 minutes...so its nothing to complain about...
Sent from my SGH-I997 using XDA
mg2195 said:
What do you mean by an entropy kernel flash then a jt? I've tried just flashing the jt one you have and no matter what rom I flash...when I hit that reboot button it will always boot back to recovery...
Anyways im back up and running in under 10 minutes...so its nothing to complain about...
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
I'm not sure if we're talking about the same thing but:
Let say you tried a port or build and got into a boot loop. Or lost recovery, you don't necessarily have to flash the whole stock package.
In my kernel root thread, post #3. Flash the Jt kernel in download mode. That should bring you n back to recovery from boot loop or lost recovery with the three finger combo.
I've noted that since Jt kernel has the cwm 5.xxx sometimes it doesn't do the trick. If that was the case, I would flash the entropy in download mode..post #2..in the uclb3 thread.
That will also give you cwm recovery without having to flash the whole stock base.
Boot into recovery, wipe and/or mount and you are set to flash the next experimental build. Just be sure to have a couple of different builds to test on your sdcard.
Once you flash what ever build or ROM, it had it's own kernel and system file to write over your current. In this case, it would not matter, as you are not working with a system file...only the recovery.
Edit: it would also make sense of you created a mg_lite ROM for debug if you needed to have the phone system. Make a ROM with minimal stuff. Turn off boot ani. Have only minimal apps..no email or gmail or bt fb or any crap that would allow down the boot and dalvik process. Only a few system files and libs are needed. That way you can save some time instead of going back to the whole stock process
qkster said:
I'm not sure if we're talking about the same thing but:
Let say you tried a port or build and got into a boot loop. Or lost recovery, you don't necessarily have to flash the whole stock package.
In my kernel root thread, post #3. Flash the Jt kernel in download mode. That should bring you n back to recovery from boot loop or lost recovery with the three finger combo.
I've noted that since Jt kernel has the cwm 5.xxx sometimes it doesn't do the trick. If that was the case, I would flash the entropy in download mode..post #2..in the uclb3 thread.
That will also give you cwm recovery without having to flash the whole stock base.
Boot into recovery, wipe and/or mount and you are set to flash the next experimental build. Just be sure to have a couple of different builds to test on your sdcard.
Once you flash what ever build or ROM, it had it's own kernel and system file to write over your current. In this case, it would not matter, as you are not working with a system file...only the recovery.
Edit: it would also make sense of you created a mg_lite ROM for debug if you needed to have the phone system. Make a ROM with minimal stuff. Turn off boot ani. Have only minimal apps..no email or gmail or bt fb or any crap that would allow down the boot and dalvik process. Only a few system files and libs are needed. That way you can save some time instead of going back to the whole stock process
Click to expand...
Click to collapse
Taking a vacation for memorial weekend...but I'll give what you suggested a try Monday night...if I happen to soft brick...
Sent from my SGH-I997 using XDA
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
ok so long story short i tried to flash my samsung infuse 4g with a rom from this website (ROM][Jellybean] CNA 3.5.0 for Samsung Infuse [PORT] ) i used to have froyo 2.2. all was well and then my phone just stopped working and wouldnt pass boot screen. but i saved my old rom's data with clockworkmod on my sd card. the thing is there are like 5 .tar files and i want to know if i can recover my old rom using odin since i cant even get passed the boot screen??? pls someone help me i'm freaking out, ive been googleing all night and i'm totally burnt out. the files i have are .android_secure.vfat.tar, cache.rfs.tar, data.rfs.tar, efs.rfs.tar, nandroid.md5 and system.rfs.tar...... pls someone show me how to fix my phone
thanks in advance
Don't think you can flash those files, but you should be able to go back to stock.
Sent from my sweet & buttery Infuse
Follow these instructions. I would use the zip that takes you back to stock with root.
Keep one thing in mind.....you CANNOT go from Froyo to JB.
http://forum.xda-developers.com/showthread.php?p=27286083#post27286083
I keep this thread bookmarked. I have soft bricked my phone so many times, it's not funny!!!
http://forum.xda-developers.com/showthread.php?t=1700416
Lack of reading/research caused your error :/
Anyways go back to stock with heimdall.or Odin, get red cwm again and you should be able to restore your backups
If you want to go to jb in the future....then you must first follow go to ics, then jb...you have to have ics before you can flash gb
Sent from my HTC PH39100 using Tapatalk 2
thanks again to all the comments, yes this was a big Noob mistake, i guess i was just way to excited to jump on the JB wagon. i have since returned to stock froyo using one of the kernals from this site (Stock_Root-Mod3e-UCKD5_Odin), so this is what i have now... although a little phased i still want to give this a second attemp. the rom i wanted to flash was [ROM][JellyBean] CNA 3.5.0 / Nightly 9/20 for Samsung Infuse [PORT]....
just to get things straight so i don't mess up again, i have to flash froyo with ics (is there a specific ics version i should get? on a how to guide on flashing jb i found this info: Entropy512's CM9 Kernel / Blue CWM Recovery 2012.05.02-ODIN-Entropy-CM9-zImage.rar) can i use this one, i prefer odin b/c i've never used heimdall. then after i flash ics then i can flash to jb.... but reading some threads i saw that....
"Currently on stock Froyo:
1) Use Heimdall or Odin to flash stock UCLB3 (GB)
*Reccomendation: Also flash GB bootloaders. See first post for links and warnings.*
2) Flash Entropy's DD kernel to obtain root and red CWM recovery.
Currently on stock GB:
1) Flash Entropy's DD kernel to obtain root and red CWM recovery."
do i have to do this step or can i go forward with the current Stock_Root-Mod3e-UCKD5_Odin that i now have installed....?
secondly, after i install ics, right before i flash jb it states i have to do an aroma prep....then flash jb.....
all flashes are done with clockworkmod and i wipe only cache and dalvik? or is there anything else i have to wipe?
sorry for all the questions, i have read and researched many threads but they are all pretty overwhelmingly full of lots of info.....just wanna get it in order....
thanks again
from froyo to ics i use odin, from odin to jb i use cwm, correct?
marielacvn said:
thanks again to all the comments, yes this was a big Noob mistake, i guess i was just way to excited to jump on the JB wagon. i have since returned to stock froyo using one of the kernals from this site (Stock_Root-Mod3e-UCKD5_Odin), so this is what i have now... although a little phased i still want to give this a second attemp. the rom i wanted to flash was [ROM][JellyBean] CNA 3.5.0 / Nightly 9/20 for Samsung Infuse [PORT]....
just to get things straight so i don't mess up again, i have to flash froyo with ics (is there a specific ics version i should get? on a how to guide on flashing jb i found this info: Entropy512's CM9 Kernel / Blue CWM Recovery 2012.05.02-ODIN-Entropy-CM9-zImage.rar) can i use this one, i prefer odin b/c i've never used heimdall. then after i flash ics then i can flash to jb.... but reading some threads i saw that....
"Currently on stock Froyo:
1) Use Heimdall or Odin to flash stock UCLB3 (GB)
*Reccomendation: Also flash GB bootloaders. See first post for links and warnings.*
2) Flash Entropy's DD kernel to obtain root and red CWM recovery.
Currently on stock GB:
1) Flash Entropy's DD kernel to obtain root and red CWM recovery."
do i have to do this step or can i go forward with the current Stock_Root-Mod3e-UCKD5_Odin that i now have installed....?
secondly, after i install ics, right before i flash jb it states i have to do an aroma prep....then flash jb.....
all flashes are done with clockworkmod and i wipe only cache and dalvik? or is there anything else i have to wipe?
sorry for all the questions, i have read and researched many threads but they are all pretty overwhelmingly full of lots of info.....just wanna get it in order....
thanks again
from froyo to ics i use odin, from odin to jb i use cwm, correct?
Click to expand...
Click to collapse
Follow all steps, don't skip a thing. As for wiping, wipe Cache, Data, Dalvik, and format /System when going from GB to ICS and ICS to JB. That UCLB3 file is Gingerbread stock and you have to go to gingerbread before you go to ICS.
Also, if you are confident that your phone won't get disconnected from Odin while flashing the UCLB3 file, flash the GB bootloaders while you're at it. If the flash fails while flashing bootloaders then your device is bricked so be sure about Odin before you flash them.
Sent from my SGH-I997 using xda app-developers app
Since you have already used Odin, I would use option "C". The best thing you can do is read everything two or three times. There are also many vids on YouTube that are helpful.
Once you are on GB.....just pick out any ICS ROM an flash it. Once it installs, I wouldn't even bother sitting it up and then you can go to JB.
Th3Bill uses an Aroma installer in his ROMs and the first time you use it, you will have to flash his aroma-prep first.
Hang in there....go slowly...and read. This gets easier and easier the more you do it. I always just d/l the zips to my phone and never even have to mess with the PC.
http://forum.xda-developers.com/showthread.php?t=1613523
Edit: All of his ROMs for the Infuse can be found and d/l at Jokersax.com
Edit: I just reread your post......once you are on GB, you won't use Odin again. You will use whatever ICS zip to flash your ROM using CWM. Same thing with JB.
Shawn said:
Follow all steps, don't skip a thing. As for wiping, wipe Cache, Data, Dalvik, and format /System when going from GB to ICS and ICS to JB. That UCLB3 file is Gingerbread stock and you have to go to gingerbread before you go to ICS.
Also, if you are confident that your phone won't get disconnected from Odin while flashing the UCLB3 file, flash the GB bootloaders while you're at it. If the flash fails while flashing bootloaders then your device is bricked so be sure about Odin before you flash them.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
okay i think i understand....never has my phone disconnected during a flash with odin, ive always gotten a straight pass...exactly how important are the bootloaders anyways? if failures happen b/c of faulty usb cords, then im good...if bricking happens b/c of "unlucky chance" then id rather avoid it.... either way ill start the whole process tonight after i put the kiddos away so i can concentrate 100%.
thanks again for the tips
dparrothead1 said:
Since you have already used Odin, I would use option "C". The best thing you can do is read everything two or three times. There are also many vids on YouTube that are helpful.
Once you are on GB.....just pick out any ICS ROM an flash it. Once it installs, I wouldn't even bother sitting it up and then you can go to JB.
Th3Bill uses an Aroma installer in his ROMs and the first time you use it, you will have to flash his aroma-prep first.
Hang in there....go slowly...and read. This gets easier and easier the more you do it. I always just d/l the zips to my phone and never even have to mess with the PC.
http://forum.xda-developers.com/showthread.php?t=1613523
Edit: All of his ROMs for the Infuse can be found and d/l at Jokersax.com
Edit: I just reread your post......once you are on GB, you won't use Odin again. You will use whatever ICS zip to flash your ROM using CWM. Same thing with JB.
Click to expand...
Click to collapse
okay, ill take ur advice and use option c. froyo to gb using odin and possibly bootloaders, then from gb to ics, ics to jb using cwm
wish me luck!
Bootloaders prevent Rainbow fault I guess you could call it in ICS. You don't have to flash them but its recommended. If you have any problems, post and you'll get help pretty quick.
Sent from my SGH-I997 using xda app-developers app
Shawn said:
Bootloaders prevent Rainbow fault I guess you could call it in ICS. You don't have to flash them but its recommended. If you have any problems, post and you'll get help pretty quick.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
so far so good, it seems i need to do the gb bootloader after all...got the rainbow screen....i have my gbbootloader file ready to go....only thing is i want to confirm where i put the file, i've searched and i can only find a procedure for heimdall not odin...do i put the md5 file in PDA or bootloaders?? also it says in heimdall to tick bootloaders, do i do the same in odin??? it also says to flash twice....?? ok im really not risking a hard brick, i'll be patient and wait
http://forum.xda-developers.com/showthread.php?t=1878458
i'll wait for your answer before i proceed....after this i'll continue to flash ics and then jb...
btw, am i supposed to flash ics twice?? that's what the [GUIDE] How To Flash JB says,
"9. Flash ICS Rom, then ICS Gapps"
but when i tried to flash ics a second time i couldn't (because of rainbow screen, and because it didn't show up in my directory....and where does ICS Gapps show up?
thanks again
If you downloaded the bootloaders linked in the guide, then yes, they go on the pda slot. You only have to flash once.
Heimdall-one click is the one you must flash once before it allows you to flash the bootloaders too.
Edit: to fully install ics you must flash twice, because I believe that what it does when coming from GB is that it just flashes the ics kernel on the first flash, requiring you to run it a second time after rebooting for it to install the complete rom.
Ics gapps are often linked in the rom OPs, although you don't need to flash them if you are headed to JB.
Sent from my sweet & buttery Infuse
andros11 said:
If you downloaded the bootloaders linked in the guide, then yes, they go on the pda slot. You only have to flash once.
Heimdall-one click is the one you must flash once before it allows you to flash the bootloaders too.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
That's odd, I flashed GB bootloaders in Odin from a rooted stock GB. But andros is right about going in the PDA slot. Maybe its just me that didn't have to flash with heimdall first.
Sent from my JellyBeaned Infuse, unofficial cm10
Shawn what I meant is that heimdall one-click wont allow you to flash bootloaders the 1st time, so you must run it once and then a 2nd time but with "flash bootloaders" ticked on.
There's no need to use heimdall before flashing them with Odin.
Sent from my sweet & buttery Infuse
Oh, I see what you mean. My mistake.
Sent from my JellyBeaned Infuse, unofficial cm10
Alright guys, I'm officially a jelly beaner!! Thanks again to all who replied and helped me out, couldn't have done it without your help everything seems to we working fine (with the exception of a few apps that aren't compatible, but they weren't that important ) only issue I have now is that I can't use my data plan and surf the web I configured everything just as I had it before according to my carrier and nothing ...... could it have something to do with the change in modem? When I scan for available network operators I get two options one says :NICMS and the other is just a number 71021... any ideas?
Also, when installing jb in the initial setup it asked which would be the defualt location to save I think I chose the sdcard instead of the emmc directory. ..can I change that setting?
I'm pretty sure you can change the setting, but not sure how. Also, your APNs might be messed up. There's a thread with working APNs. One sec and I'll link it.
Edit: http://forum.xda-developers.com/showthread.php?t=1791526
Sent from my JellyBeaned Infuse, unofficial cm10
Shawn said:
I'm pretty sure you can change the setting, but not sure how. Also, your APNs might be messed up. There's a thread with working APNs. One sec and I'll link it.
Edit: http://forum.xda-developers.com/showthread.php?t=1791526
Sent from my JellyBeaned Infuse, unofficial cm10
Click to expand...
Click to collapse
Thanks for the link Shawn, I looked it over, not sure it could apply since I don't live in the states.. but I'll use it as a start.
marielacvn said:
Thanks for the link Shawn, I looked it over, not sure it could apply since I don't live in the states.. but I'll use it as a start.
Click to expand...
Click to collapse
It probably won't but you never know.
how is [ROM][JellyBean][4.1.1]Unofficial CM10 - Updated CM10 9/14 Butter - MTD - OC Kernel working out? since ive gotten cna nightly my camera and video are extremly buggy, more than id like...what works and doesnt work in unofficial cm10
So I rooted my brother's infuse 4G because it was slow as sin and needed A. a data/cache wipe and B, I wanted to give him Jellybean
I followed all the instructions I could; rooted, installed the modded 3e (or thought I did), got a CWM installed afterwards, and then set about installing first CM9 (as the Jellybean ROM post says I should) followed by the actual ROM and its Gapps. Well, I installed CM9 (although it seemed to take all of 30 seconds, rather fast...) when I tried to wipe data/factory reset, CWM froze. I rebooted and from then on I had it softbricked. Stuck booting at the samsung logo, and when I tried to return to the recovery, the recovery was a garbled mess that looked like a scrambled TV channel. I used Heimdall and did the one-click reset to stock, and here I am. The phone boots to stock just fine, but my recovery is still completely boned.
Do I re-root? How do I install CWM again without being able to install 3e? (can't install 3e without a working recovery in the first place, after all..)
One anomaly of note - when I was going about all this, booting the phone into recovery always got me 3e, even after installing CWM. I had to manually install CWM by using an update.zip and "reinstall packages" every time I wanted to use CWM. ROM manager would boot me to CWM, but it took several reboots and a flashable CWM zip before I could even get CWM installed in the first place - ROM manager refused to do it the easy way.
What did I do wrong, and more importantly, how do I get back on track? What do I do to put a fixed recovery back on this thing? Odin? ADB?
Today was the first time I ever used Heimdall, I've been a fair weather flasher since the beginning, I've never had to ADB or Odin.
It sounds like you didn't install cwm recovery properly, but I'm not sure I've never ran into this problem before. If you go here
http://forum.xda-developers.com/showthread.php?t=1524081 and carefully read over the first and second post you should end up with gb and red cwm recovery. The way I've done it was to put the phone in dl mode and flash the first package (the stock gingerbread att rom). After it is installed and booted up, I then power it off and go back into dl mode. Then flash the second package, which is just the kernel and red cwm recovery, (be patient because it takes awhile). Once that is done then go into recovery and wipe data/factory reset, wipe dalvik cache, wipe system, and install cm9. I think it only installs the kernel and recovery the first installation after formatting and creating the partitions, but after its done you have to go through the menus and tell it to reboot. After it reboots it will be stuck at the cyanogenmod galaxy s logo, so you will have to go into recovery once more. When you're there you should have blue cwm (only continue if you do) and install jb, without actually having to install the full cm9. When you navigate to which ever jb rom you want to install, a prompt will appear stating that there is incompatible partition layout and to confirm installation you will have to reselect the jb zip again to install. It will flash pretty quick because at this point its doing the same thing as when you went from gb to cm9 and only installs the kernel, recovery, and reformat/creates the partitions, (I think). It will reboot on its own but it will take you back into recovery. At this point all you have to do is navigate to the same jb zip you want to install and flash it, followed by gapps, and then reboot system. This process has worked for me but I highly recommend reading and following the instructions given in the post above.
Use goo.I'm app. Also you need to flash GB bootloaders in Odin . is recovery all colorful? If you see recovery fine just get goo app on play store and install a recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I would go the ODIN route, I have bricked so many times because i try to make the impossible possible. Just search for a already rooted pda,mdr file. I skipped the cm9 part idk if that would make things better or not but as my post says im a risk-taker
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
UnhoIy said:
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
but if don't have any problems i'm good right or should i go back and do it
MajorLeagueROM said:
but if don't have any problems i'm good right or should i go back and do it
Click to expand...
Click to collapse
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
UnhoIy said:
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
MajorLeagueROM said:
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
Click to expand...
Click to collapse
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
UnhoIy said:
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
Click to expand...
Click to collapse
lol it happens to the best of us