Related
I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.
CZ Eddie said:
I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.
Click to expand...
Click to collapse
I dont know what ALOT of investment is.......but what i think happened here is this<<
You were on Gingerbread right, Infused v2.x.x and you made a Nandroid(thats fine)
u installed miUi and didnt have the luck you wanted...Thats fine
You went back to stock, and rooted and modded the Recovery so you could restore your nandroid....Thats fine
But if you went back to stock(Froyo Right) and try to load up a Gringerbread Nandroid on top it shouldnt work. Nandroids only back up the ROM not the Kernel......so you were in a sense trying to run a Gingerbread Rom on a Stock Froyo Kernel......
Go into CWM flash your Kernel, or use odin and flash a Ginger Kernel then go into CWM and RESTORE.
Happy FLashing
Didn't know that! That may explain a lot of my ROM frustrations.
I'll try this and report back.
Off to go find a suitable kernel....
I really should get my post count up so I can get past this horrible 10 post restriction.
Did you try initiating the flash through CWM or through ROM Manager? Honestly I don't prefer to do any work via ROM Manager, I always have more luck going through CWM and starting a flash from there. Kernel is the first place I'd start but you should also Factory Wipe and Cache Wipe each time you move between ROMs, sometimes you get very lucky and don't need to, most times you bork your phone, and if you're nandroiding back from a backup wiping before you restore is good practice just to make sure you don't leave anything behind from your old ROM.
I installed a gingerbread kernel:
http://forum.xda-developers.com/showthread.php?t=1212485
Version 1.1.
But it didn't work out.
So now I'm fighting with trying to get a stock Infused V2 ROM on there.
No luck yet. Once I do, I'll try the recovery again.
Btw, I'm using CWM for everything.
Go to mounts and storage in clockwork recovery then select format system then do your nand restore ...
Sent from my Samsung Infuse 4G - 1.6ghz
Wow, I was totally making some rookie (which I am) Android mistakes today.
Every time I tried to restore the backup image, I was doing it in CWM by selecting "install .zip from SD card". When I SHOULD have been using the "backup/restore" function.
I'm up & running again. All original apps/settings are restored. Great!
Now to start breaking things again, since I know how to restore from backup now.
Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab
ihabelnaccash said:
Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab
Click to expand...
Click to collapse
Hi there,
I recently experienced the same thing, and it was a hassle to fix--but I have got my phone working each time. The downside being that I /had/ to switch over to Odin. Mind you, I am not necessarily experienced with Android, so I can't really say that this is the only way.
At any rate, here's what I did to get it back to normal:
Load up Odin
Put it in download mode -- I assume you know to hold the volume keys and then plug in the USB.
Flash either the ICS leak or the stock 2.3.5 Gingerbread.
You should be back to good. I hope you backed everything up in either Kies or some other resource...else you're in for a hell of a time setting stuff up.
Oh: bad news about the 2.3.5 stock is that, as far as I can tell, you're unable to upgrade to 2.3.6. In turn, you're then unable to update to the official ICS through Kies or OTA. I assume you don't mind, considering you're trying to flash a new rom anyway.
Anyway, I do hope there is some bit of clarity on getting CM9 on the Skyrocket. As of now I have still been unable to do it. Just as you, no matter the settings I try, I end up being stuck at that screen. The only difference between your method and mine is that I completely did mine through CWM...nothing through ROM Manager. (Actually, I believe I tried a few differing methods involving the CWM touch and non-touch...followed many different guides but still no good.)
Hope you get it back to a functioning state. If you get CM9 working on the Skyrocket, I'd appreciate you sending a bit of details on how to do so.
EDIT: I am now on CM9. Through magic, ponies and friendship I have failed to accomplish this feat. But by pure science and the blood of a pony, I have successfully installed CM9.
After you've restored to 2.3.5 or the ICS leak (the one I was on), do the following:
- Grab the recovery-clockwork-touch U27 described below. Flash it.
- Download both the newest CM9 build from their website, as well as Google Apps, and then copy those to your external SD.
- Follow this guide: http://www.teamchopsticks.org/p/install-guide.html. Here's what's relevant to you:
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the CM9 zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
Click to expand...
Click to collapse
After ~10 minutes you should be fine. Mine took less, but I'd bet it could take longer. Please follow those directions above EXACTLY. I'll be happy to help you in any way I can if you reply to this thread/ send me a PM.
When I softbricked with the latest CWM I wasn't able to return back since it wouldnt detect my SDcard so I just loaded up odin and used recovery-clockwork-touch-5.8.1.3-hercules.tar and was able to read my SDcard again which had all my backups and CM9 files. I have flashed every version of CM9 every since and still using this CWM version and havent had any problems. :good:
All better now- I used ODIN to restore to stock, then used it again to put CWM (non-touch) back on, then added superuser, then just did a restore from SDcard! Muchas Gracias all!
Should I be able to then use a restore of when I had a working CM9 (and backed up with CWM)? Or would I have to do all the cache wiping/ factory reset like I did to install it the first time before using such a recovery? (and I will try that recovery- clockwork touch hercules... latrer tonight from home)
ODIN tar to restore back to factory. I got the boot loop too. Only until after I flashed CM9 then flashed dark side wipe cache only would CM9 work for me. Only on regular CWM though. Try and give that a go.
Sent from my SAMSUNG-SGH-I727
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
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
lonoguge said:
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
Click to expand...
Click to collapse
Where did you get twrp?
lonoguge said:
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
Click to expand...
Click to collapse
What is "another rom"?
lonoguge said:
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
Click to expand...
Click to collapse
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
bhundven said:
Where did you get twrp?
What is "another rom"?
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
Click to expand...
Click to collapse
I got it from what I thought was the official XDA TWRP thread but I'm not sure if it was official or not
at first I tried reinstalling codename but now I'm trying Beam (Tuk edition) and it seems to be working
TWRP Major Boot Loop
hey guys, im new here and i desperately need help with my phone!
the other day i was flashing a rom on my samsung galaxy s 4g. Things were turning out fine, until i had some complications on my phone.. so, i removed the rom. when i rebooted my phone, it went directly into the team win recovery project boot loop and every time i try to reboot my phone, it goes into the twrp. I also can't wipe anything and i can't delete anything! Does anybody know how I can solve this or is my phone basically bricked
more details would be helpful..
As in what rom, or what kernel.... etc... and make sure you have the corret phone.
Same problem with t959p
Looks like I'm not alone.......here's my story
the other day I wanted to switch from a stock rom to a custom, so I flashed redux 1.3 which was actually a froyo rom, and it started draining my batt like crazy so I flashed another rom on top of the froyo rom not realizing what I was doing and somehow messed it up cuz now it will only boot into recovery.
Now just to be clear I know this was my fault, I know I should have odin'd back to stock first, but I wasn't thinking at the time.....Ohh and just so you know I've flashed this sucker hundreds of times and was always able to get out of any mess I got in.
So here is the situation as it stands now, 3 button combo to enter download does not work. I can only get it into download with the jig I made. the problem is even in download mode none of my pc's will detect the device as a Samsung composite device, so odin will not see it. I've installed every possible 32 n 64 bit driver I could find including reinstalling kies. Kies wont even see it. I've tried flashing a few roms that I know worked and still it just boots into recovery. Now one thing I'll tell you is that depending on which rom I flash I can get recovery to switch from cwm to twrp. right now I left it with cwm 6.x.
what I need is a cwm flashable stock telus t959p rom complete with bootloaders or at the very least a cwm flashable zip file containing the bootloaders to see if I can recover the phone.
ohh and if your thinking about telling me to google search for the answer then don't bother.......I've spent the last 4 days reading posts and going to different websites and repositories trying to find something that would help me and so far nothing has.
the only thing that might work as a last resort is pushing the bootloaders as per one of raver's or whitehawks posts but it's a little more complicated for me as I would have to set up a laptop with Linux as I don't think i'll be able to pull it off with any of my windows pc's, win7 and win 8 only.
so if anyone has the files I need or can make them please let me know....or if you think you have another solution I could try i'm all ears err eyes.
thanks
Jedi
Have you tried heimdall one-clicks? Maybe it's showing up as gadget or something like that. I've had luck using zadig and heimdall to bring it back from the brink of death.
http://forum.xda-developers.com/showthread.php?t=1358498
EDIT
Woops replied to the wrong thread .
Nothing to see here, move along
Would like to revive a slightly dead thread.
I upgraded to a Galaxy S3 and no longer use my SGS4G for daily use. I had AOKP and disliked it, FC's and didn't like the feel. I have been trying to install a new rom ( old rom, VH Black Ed. ). Every time It loads into TWRP I have the ability to select the zip, install, it says complete, but reboots right back to TWRP menu. I've tried flashing CWM and it will install, flash the rom, reboot, and right back to this TWRP B.S... what am I doing wrong? I want to continue to use this SGS4g for music and internet duties.
How can I install CWM and have it stay even after a reboot? This TWRP is starting to me off
Did you happen to one click to stock before you went ham at the recovery?
Sent from my SGH-T959V using Tapatalk 4
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