Related
After painstaking deliberation, they had reached the decision to eat gingerbread. Cautious and deliberate by nature, they opted to install stock 2.3.6 using Kies, presumably the safest choice. KB5 had been having a hard time connecting to the pc via usb with debugging active - no choice was given how to connect to pc, and Kies was not recognizing the phone. Finally bypassing the usb hub allowed Kies to recognize the device, and after a long download, a usb error message flashed up and process failed. Removed phone battery and reboot, all is well but SCREW KIES
Odin from now on
Probably the most creative thing I've seen here all night. Kudos to you my friend!
Sent from my SGH-T959V using XDA App
Downloaded the stock ODIN version of GB 2.3.6 KJ6 .tar here to flash via ODIN but phone will not connect via usb at all now. I think I reverted it's firmware back to the paleolithic era somehow. Could someone share the link the newest ODIN? I have v1.85 and I think also 4.03?
Unless anyone has any ideas, looks like CWM may be my only chance. How can I upgrade firmware if the method used to update is inoperable? Whenever I go into download mode it will not connect with USB. Instead windows says
"USB Device Not Recognized
One of the USB devices attached tho this compter has malfunctioned and windows does not recognize it. For help with this problem, click here."
Great bricked in a factory reset version of kb5 ugh. And this all happened because I tried to use stupid Kies!
Son of a ginger biscuit I figured out why it would not connect it was the 6 FOOT CORD I had hooked up for convenience it WILL NOT GO INTO ODIN OR KIES without the original 3' cord wow
Don't know if it was related to the Kies failure or not but now I am up and running though I cannot flash any .zip with cwm, says signature not verified, and I cannot find a toggle, I have 2.3.6 running now, rooted with super one click zerg, recovery 3e, is there a difference between "rom manager" and "cwm"?? How do I fix this I'd like to install the custom debloater .zip... upgraded from kb5
Farlander said:
Don't know if it was related to the Kies failure or not but now I am up and running though I cannot flash any .zip with cwm, says signature not verified, and I cannot find a toggle, I have 2.3.6 running now, rooted with super one click zerg, recovery 3e, is there a difference between "rom manager" and "cwm"?? How do I fix this I'd like to install the custom debloater .zip... upgraded from kb5
Click to expand...
Click to collapse
Definitely stay away from ROM Manager, from what I've read. You're getting that signature verification error probably because the phone now has standard recovery vs. CWM. That's an assumption on my part, though. You would have to ODIN one of Drhonk's modded kernels that comes with voodoo/cwm/root to get CWM installed. Within the standard recovery there is not a place to toggle the signature verification.
Considering you're on KJ6 now, go to http://forum.xda-developers.com/showthread.php?t=1194032 and grab drhonk's KJ1 kernel. Put it into the PDA section of ODIN and flash it. Then you'll have CWM.
Farlander said:
is there a difference between "rom manager" and "cwm"??
Click to expand...
Click to collapse
I had the same issue when I first started. ROM Manager is an app used to download & install custom ROMs, make backups, etc., but it does not work correctly on our phones. "CWM" (as used in the context of the SGS4G) is the custom recovery menu we install to do basically the same things. Anyway, follow stephen_w's instructions to install a custom kernel and that will solve your issues.
Awesome response stephen_w. A link! So much info out there I'm compiling a small database but when I need something it's usually back to search!
I was up and running KJ6, trying to install .zip files from root of sd card using cwm. Did not work - error was E:\ signature verification failed
So, decide to ODIN back to KB5, and try to load cwm, upgrade via cwm, and see if there was a glitch there. Did not work. Upon ODINING back to KB5, download screen has different look, and phone bootloops at Galaxy S logo. I'm about to ODIN flash 2.3.6 again and hope that it works....
This all started because Kies failed (presumably due to length of cord) the KJ6 from Raver that I ODIN'd in I THOUGHT was all stock actually came with CWM and super user preloaded. CWM did not recognize su.apk in the root and was therefore less functional. I fixed permissions and the error went away, but many icons were still greyed out. I wanted to bring back my apps/data from rom manager backup, but my recovery would not work. It would not open the .zip files, and there was no toggle to enable/disable signature verify. This may have been because I did not buy the pay version of CWM, or I don't know how to use it properly. Do you have to somehow flash the recovery to enable CWM? Is there a particular recovery designed for KJ6 SGS4G??
Also, what is the "bootloader update" option for in ODIN?
Farlander said:
Awesome response stephen_w. A link! So much info out there I'm compiling a small database but when I need something it's usually back to search!
I was up and running KJ6, trying to install .zip files from root of sd card using cwm. Did not work - error was E:\ signature verification failed
So, decide to ODIN back to KB5, and try to load cwm, upgrade via cwm, and see if there was a glitch there. Did not work. Upon ODINING back to KB5, download screen has different look, and phone bootloops at Galaxy S logo. I'm about to ODIN flash 2.3.6 again and hope that it works....
Click to expand...
Click to collapse
Weird; I've not had the signature verification error with CWM, only with the standard recovery.
When you went back to KB5 you went from a Gingerbread (GB) ROM to a Froyo ROM. Froyo & GB require different boot loaders so if the ROM you flashed did not have both boot loaders, then you get stuck in a boot loop. Going back to KJ6 will probably get you going again.
This all started because Kies failed (presumably due to length of cord) the KJ6 from Raver that I ODIN'd in I THOUGHT was all stock actually came with CWM and super user preloaded. CWM did not recognize su.apk in the root and was therefore less functional. I fixed permissions and the error went away, but many icons were still greyed out.
Click to expand...
Click to collapse
I thought Raver's ODIN version of KJ6 was pure stock. I didn't think it had CWM or Superuser.
I wanted to bring back my apps/data from rom manager backup, but my recovery would not work.
Click to expand...
Click to collapse
You might have problems recovering to GB ROMs. This is due to an error in CWM for GB. The problem prevents the /system partition from unmounting. From what I've been told, you have to flash back to a Froyo ROM, like Bali, to do the recovery then flash back to the GB ROM afterward. Not sure if that's your problem here, though, as I've never used ROM Manager.
It would not open the .zip files, and there was no toggle to enable/disable signature verify. This may have been because I did not buy the pay version of CWM, or I don't know how to use it properly. Do you have to somehow flash the recovery to enable CWM? Is there a particular recovery designed for KJ6 SGS4G??
Click to expand...
Click to collapse
I've never paid for a version of CWM. I've always used one of drhonk's modded kernels to get CWM. Installing the KJ1 kernel I mentioned earlier should do that for you.
Also, what is the "bootloader update" option for in ODIN?
Click to expand...
Click to collapse
My best ODIN advice: Let ODIN decide what needs to be checked and what should not. I've not used the "Phone Bootloader Update" feature. Don't go anywhere near the "Phone EFS Clear", either. I've a feeling that would wipe out your IMEI and other things.
See if you can get Raver's ODIN Stock KJ6 to install, then install drhonk's KJ1 kernel. Once done, reboot into recovery mode and see if it is CWM Red recovery, which is should be. Note the version number at the top and report it back here.
If all of that works well and the right version of CWM is there, then maybe we need to examine what ZIP you're trying to flash. Maybe it's a corrupt file.
Thank you very much, succesfully flashed GB 2.3.6 KJ6, succesfully flashed Drhonks KJ1, had a hard time entering recovery boot mode
RECOVERY BOOT MODE 3 BUTTON SGS4G 959V
HOLD: vol up, vol dn, power
RELEASE: power
RELEASE: vol up, vol dn
Disabled voodoo and I'm about to load up busy box, (CWM i.e. rom manager???) per the instructions......
UPDATE 20:02 ownloaded "rom manager", re-enabled VOODOO, rebooting. I think I get what's going on here. The file system is being reformatted / partitioned every time voodoo is enabled/disabled. I'm assuming the enabled mode is ext4 partitioning. However, cwm must be installed during fat32 mode, thus the reasoning for enable/disable voodoo. Can't wait to try this out, is it really faster than stock KJ6?? Love the look and feel of the rom already!
Farlander said:
Thank you very much, succesfully flashed GB 2.3.6 KJ6, succesfully flashed Drhonks KJ1, had a hard time entering recovery boot mode
RECOVERY BOOT MODE 3 BUTTON SGS4G 959V
HOLD: vol up, vol dn, power
RELEASE: power
RELEASE: vol up, vol dn
Disabled voodoo and I'm about to load up busy box, (CWM i.e. rom manager???) per the instructions......
Click to expand...
Click to collapse
Yeah, since being on GB I've been unable to get into recovery unless I use an app like Quick Boot or using ADB from the Android SDK.
Rom Manager and CWM, to my knowledge, are different animals. Good luck getting it going; it sounds like your 95% of the way there.
Heck yea workin good now to restore those apps I lost and debloat and play with boot animations!!!
UPDATE: Just also flashed via CWM .zip the debloater file, SWEET
Bloatware remover flashed with cwm works awesome, just browse to find the .zip doesn't even need to be in root dir
So far no noticeable deficiencies and without even installing app killer I have 165 used and 343 megs of ram free!!
I'm about to try to backup progs using rom manager, but when I click "backup/restore" it tells me I have to flash clockwork mod, which I'm pretty sure is already flashed??
Farlander said:
Heck yea workin good now to restore those apps I lost and debloat and play with boot animations!!!
Click to expand...
Click to collapse
Awesome, glad you got it working
MY PHONE IS NOW ALL THAT IS PERFECT
Thank you EVERYBODY
This took me about 2 weeks of 3-4 hours a day research and thumb work
now operating
2.3.6 KJ6 GB w/
KJ1 drhonk stock + voodoo + cwm
debloater.zip
Titanium Backup to restore all apps (adfree, app killer, etc. etc.)
Icons and background are gone but no bigggy
mine got unplugged in odin download screen can anyone help?
Andrew.80 said:
mine got unplugged in odin download screen can anyone help?
Click to expand...
Click to collapse
That blows. Does ODIN recognize it when you plug it back in? If so, just reflash.
Sent from my SGH-T959V using XDA App
When in doubt take the battery out! (to dinner)
UPDATE: I want to make a total phone backup (of all my current settings) using rom manager. When I go to "backup current ROM" it says cwm needs to be installed and gives me options for several phones, including the i9000. Should I do this even though cwm red is already installed on my phone? Need a workaround here...
thanks in advance
Farlander said:
When in doubt take the battery out! (to dinner)
UPDATE: I want to make a total phone backup (of all my current settings) using rom manager. When I go to "backup current ROM" it says cwm needs to be installed and gives me options for several phones, including the i9000. Should I do this even though cwm red is already installed on my phone? Need a workaround here...
thanks in advance
Click to expand...
Click to collapse
ROM manager doesn't work on the SGS4G. Your best bet right now is titanium backup, or flashing the bali kernel for 2.2 if you want to make a full backup using cwm recovery.
stephen_w said:
Definitely stay away from ROM Manager
Click to expand...
Click to collapse
ultimakillz said:
ROM Manager is an app used to download & install custom ROMs, make backups, etc., but it does not work correctly on our phones.
Click to expand...
Click to collapse
FBis251 said:
ROM manager doesn't work on the SGS4G.
Click to expand...
Click to collapse
Man, this should really be posted somewhere.
stephen_w said:
That blows. Does ODIN recognize it when you plug it back in? If so, just reflash.
That fixed it
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Sent from my SGH-T959V using xda premium
I am on stock(P3113 rooted+cwm)...I am getting an OTA for 4.0.4 but for that i'll need to go back to stock recovery...Should i :
1) Flash stock rom n then take the OTA
2) Flash 4.0.4 through odin [ http://samsung-updates.com/device/?id=GT-P3113 ]
3) Flash stock recovery n then take the ODA.
I would like to go with option 3 cuz it will require the min. amount of downloading....But for that i need stock recovery...So what should i do n is there any other way??
On my 5113 the only thing that worked for me was to flash with Kies and then reroot. It was well worth it though.
There doesn't seem to be an easy way to get just the recovery and I think (not sure) that only Odin can unlock that partition anyway. There are some stock images in Odin format and I have been meaning to pick through them to see if I can find the stock recovery image, but since no one has posted such, I am guessing you can't.
wd5gnr said:
On my 5113 the only thing that worked for me was to flash with Kies and then reroot. It was well worth it though.
There doesn't seem to be an easy way to get just the recovery and I think (not sure) that only Odin can unlock that partition anyway. There are some stock images in Odin format and I have been meaning to pick through them to see if I can find the stock recovery image, but since no one has posted such, I am guessing you can't.
Click to expand...
Click to collapse
But the problem is that i can't update vie kies...It keeps on disconnecting, so OTA is my only option n for that i need to get rid of CWM.
I am curious too, I rooted using this method, and have CWM installed.
http://forum.xda-developers.com/showpost.php?p=25480291&postcount=137
I guess I can just flash the stock image and loose root, upgrade, then reroot. Hopefully, someone will drop a stock, rooted and deodexed 4..0.4 rom for the P3113.
Also, I have not used Kies before, so I guess I don't even know how to flash the stock image for this tablet. Can anyone help with that?
fillyo said:
I am curious too, I rooted using this method, and have CWM installed.
http://forum.xda-developers.com/showpost.php?p=25480291&postcount=137
I guess I can just flash the stock image and loose root, upgrade, then reroot. Hopefully, someone will drop a stock, rooted and deodexed 4..0.4 rom for the P3113.
Also, I have not used Kies before, so I guess I don't even know how to flash the stock image for this tablet. Can anyone help with that?
Click to expand...
Click to collapse
To flash stock you'll have to use the stock rom n flash using odin,,, But i was hoping that there is way around it...
I've updated today my rooted P3113 to 4.0.4
This is the only way to upgrade rooted P3113 (with CWM), because the samsung official upgrade scenario doesnt works on CWM
1. Backup with Titanium
2. Wipe/factory reset with CWM
3. Download and unzip stock 4.0.4 firmware from here, then flash it with odin (PDA button)
4. Configure your device (now it's clean stock apps and stock recovery)
5. Restore your apps with Titanium
6. Install CWM and root - If you wish so (just as you installed on 4.0.3)
barmalei7 said:
I've updated today my rooted P3113 to 4.0.4
This is the only way to upgrade rooted P3113 (with CWM), because the samsung official upgrade scenario doesnt works on CWM
Click to expand...
Click to collapse
I would imagine this is just like the 5113. If you use Keis instead of the OTA update it works. Apparently Keis uses the USB instead of the recovery. However, a lot of people are having trouble getting Keis to stay connected. But I used it with no problems. Just reflashed CWM and rerooted as you say, but did not have to reflash to stock.
Just updated manually from 4.0.3 + Rooted + CWM 5.5.0.4 (GT3113)
Sorry too young to post links
Went very simple (10 minutes)
Returned to Stock Recovery: h://theunlockr.com/2012/06/02/get-samsung-galaxy-tab-2-7-gtp3113-back-stock
REBOOTED
Applied Update (not 4.0.4, not sure what it was)
Downloaded 4.0.4 from Samsung directly: h://samsung-updates.com/device/?id=GT-P3113
Unzipped to Desktop
Updated to 4.0.4 using ODIN (PDA)
REBOOTED
System applied update on startup
Asked me to select language, date, Goodle backup, etc
It loaded all existing Apps, Wi-Fi, etc automatically no TiRestore needed
Up and running, seems faster- smoother, new keyboard (old keyboard was good, this one is as good better for big fingers?)
:laugh:
Back to CWM & Root
h://forum.xda-developers.com/showthread.php?t=1722304
I downloaded the file from the Samsung site, launched Odin and updated. It kept all my apps and settings since I did not wipe. Flashed recovery, then rerooted, did not take long. If it gets yucky, I will do a factory reset.
Very helpful!
Very helpful guide.
On a semi-related note, I really like 4.0.4 it's certainly an improvement over the last and seems to have cured the stupid interface lag.
Ok flashed mine using mobile odin...no need to wipe data..
JacRyan said:
Just updated manually from 4.0.3 + Rooted + CWM 5.5.0.4 (GT3113)
Sorry too young to post links
Went very simple (10 minutes)
Returned to Stock Recovery: h://theunlockr.com/2012/06/02/get-samsung-galaxy-tab-2-7-gtp3113-back-stock
REBOOTED
Applied Update (not 4.0.4, not sure what it was)
Downloaded 4.0.4 from Samsung directly: h://samsung-updates.com/device/?id=GT-P3113
Unzipped to Desktop
Updated to 4.0.4 using ODIN (PDA)
REBOOTED
System applied update on startup
Asked me to select language, date, Goodle backup, etc
It loaded all existing Apps, Wi-Fi, etc automatically no TiRestore needed
Up and running, seems faster- smoother, new keyboard (old keyboard was good, this one is as good better for big fingers?)
:laugh:
Back to CWM & Root
h://forum.xda-developers.com/showthread.php?t=1722304
Click to expand...
Click to collapse
Your steps are so easy. I wish I could follow you on this, but I can't figure out how to revert back to stock recovery only. The theunlockr.com link shows how to completely revert the entire firmware. How do you revert recovery ONLY?
Hasn't someone made a .zip file that can be flashed with CWM? Why is it different than flashing a 3rd party rom?
____________________________________Solved, thanks for all who offered help.___________________________________
Hi All, I have just flashed the RemICS ROM 1.3 and i have followed the set of directions for Gingerbread users, which I previously was. The installation had been successful until I did the final Reboot, where it loops back into the Recovery mode even after numerous of re-flash and reboots. I'm pretty sure the ROM is installed, yet it would not load into the OS, thoughts? Thanks everyone in Advance.
http://forum.xda-developers.com/showthread.php?t=1613523 I had the option C installed initially, for everyone's info.
________________________________________________Solution________________________________________________
Finally got my ICS working now. Can't thank you enough for qkster Heimdall One Click Gingerbread ROM.
For everyone's reference, the following is what I've done;
1) Flashed the Heimdall One Click GB Stock rom, a big thanks to qkster,
2) Flashed the CWM Recovery just under the same thread,
3) Flashed the RemICS rom with factory wipe and formatting data, system and cache, again after reboot.
4) >Bootlooped at the SAMSUNG screen,
5) Followed the solution of bootlooping under the RemICS thread and flashed Heimdall GB Stock again,
6) Flashed Clockworkmod again,
7) Installed RemICS rom again (Step 3) & WORKING LIKE A CHARM NOW!
I suspect my initial problem was caused by internal conflicts between the Rooted ROM and ICS, yet it is not evident nor I'm experienced to make such conclusion. Anyway, glad that my Infuse is finally able to run on Ice Cream Sandwich and I really dont care about what had caused the problem prior.
Big Thanks to rkkaranrk and qkster.
Post sent to dev thread of this ROM, just hang tough, tell the storm troopers arrive....
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Do u have the GB boot loaders ? If not flash them......will solve ur problem.
Sent from my SGH-I997 using Tapatalk 2
rkkaranrk said:
Do u have the GB boot loaders ? If not flash them......will solve ur problem.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Gb bootloaders would not cause this problem...it only causes rainbow...I've had this happen to me countless times when I was porting Roms back when I had an infuse...I just came to the conclusion the the ics recovery is buggy and is borked easily
The fix, flash back to stock via heimdal or Odin, then get cwm recovery and flash the Rom using gingerbread instructions (double flash) (unless you flash the ics kernel...in that case one flash)
If you want detailed instructions on flashing or getting gb bootloaders (in case you have rainbow recovery) then check out my infinitum port thread (in my signature) at the bottem of the OP you will find some good instructions...I wouldn't reccomend flashing it though as it is old and doesn't have the latest fixes...but the flashing instructions are still good
Sent from my HTC PH39100 using Tapatalk 2
I had faced this same issue last night when I was trying to flash REM ics on my friends phone and it don't have the GB boot loaders I tried to flash the recovery from the OP and after flashing recvery I was not able to RAF anything the fonts were so tiny and were in pink color.
After all this I flashed it back to lb3 thanks to Scott and from there I flashed it again and this time lost recovery was not able get the phone to recovery, So finally I decided to flash the GB BL with heimdall (thanks to qkster) flashed stock one more time with BL ticked and the REM ICS, All good.
Sent from my SGH-I997 using Tapatalk 2
rkkaranrk said:
I had faced this same issue last night when I was trying to flash REM ics on my friends phone and it don't have the GB boot loaders I tried to flash the recovery from the OP and after flashing recvery I was not able to RAF anything the fonts were so tiny and were in pink color.
After all this I flashed it back to lb3 thanks to Scott and from there I flashed it again and this time lost recovery was not able get the phone to recovery, So finally I decided to flash the GB BL with heimdall (thanks to qkster) flashed stock one more time with BL ticked and the REM ICS, All good.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
The bootloaders fixed the rainbow recovery, what fixed your whole problem was that you flashed stock...so you pretty much killed two birds with one stone, you fixed your rainbows and you fixed your soft brick...
The pink recovery you referred to is known as rainbow recovery
Sent from my HTC PH39100 using Tapatalk 2
Mate u missed the part i said i flashed stock twice first time with out the BL and then with the BL, When i flashed stock without the BL and from there when i flashed REM i lost recovery so and flashed again with the BL this solved.
I had read all aver that BL does not mess with flashing only gives u messed recovery on ICS and rainbow boot but i don't know how this worked for my friends phone.
Edit: i know how rainbow recovery looks like but the fonts are still in blue color but in this case the blue fonts were pink in color and were too small if the normal size of the font say 10 then the size in this recovery was like 2/3.
rkkaranrk said:
I had faced this same issue last night when I was trying to flash REM ics on my friends phone and it don't have the GB boot loaders I tried to flash the recovery from the OP and after flashing recvery I was not able to RAF anything the fonts were so tiny and were in pink color.
After all this I flashed it back to lb3 thanks to Scott and from there I flashed it again and this time lost recovery was not able get the phone to recovery, So finally I decided to flash the GB BL with heimdall (thanks to qkster) flashed stock one more time with BL ticked and the REM ICS, All good.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yes i have flashed the original stock gingerbread (the one listed in the OP) back onto my infuse last night. The phone is working flawlessly at this moment under the stock GB.
And the ICS Rom was flashed twice everything worked, cache cleared, factory reset, no rainbow, and the only problem was recovery looping. Im considering reflashing the rem ICS rom sometime soon but i doubt I'd see any difference, any chance i can get ICS working? Thanks for all the above replies
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
There is no reason for it not to work if done properly u will boot in to a new world.
Sent from my SGH-I997 using Tapatalk 2
RemICS kernal question
I am currently using version 1.3 on my infuse. I have noticed that the past couple of days that the phone seems to be slowing down and doing soft reboots every once in awhile. I have gone through and deleted a bunch of apps and moved some to my sdcard and it has gotten faster, however I still have some slow downs and reboots, especially when coming back to the homescreen after exiting an app (It seems to take a few seconds to redraw the homescreen) or if an app locks up. I also have RemICS version 1.3.1 on my Captivate and it has a different kernel (Devil Kernel). I was wondering if there was a version of this kernel that would work with the Infuse as my Captivate seems to be rock-steady and fast. I have not overclocked or messed with the memory settings on the Infuse, but I have noticed that no matter what Rom I use on it (even stock Gingerbread loaded by ATT repair center), it seems to slow down and mess up over time. RemICS so far has seemed to last the longest and I would like to keep it going smoothly. Any suggestions would be extremely helpful. Thanks!
Chris Veverka
[email protected]
cx831 said:
Hi All, I have just flashed the RemICS ROM 1.3 and i have followed the set of directions for Gingerbread users, which I previously was. The installation had been successful until I did the final Reboot, where it loops back into the Recovery mode even after numerous of re-flash and reboots. I'm pretty sure the ROM is installed, yet it would not load into the OS, thoughts? Thanks everyone in Advance.
http://forum.xda-developers.com/showthread.php?t=1613523 I had the option C installed initially, for everyone's info.
Click to expand...
Click to collapse
yes it happens with me when i flash ics over gb and after every thing phone just struck up in blue recovery it happens coz some previous system files sometimes not completely deleted, dont worry just do following as what i do.
search and download infuse toolkit v1.10 and when u got in bootloop in cwm just flash this toolkit from cwm and follow the instructions till option full wipe or complete wipe after that it will again boot up in cwm recovery now wipe cach system and again install ur rom.
cx831 said:
Yes i have flashed the original stock gingerbread (the one listed in the OP) back onto my infuse last night. The phone is working flawlessly at this moment under the stock GB.
And the ICS Rom was flashed twice everything worked, cache cleared, factory reset, no rainbow, and the only problem was recovery looping. Im considering reflashing the rem ICS rom sometime soon but i doubt I'd see any difference, any chance i can get ICS working? Thanks for all the above replies
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
be positive, you can get ICS running in no time. follow our directions and you shouldnt come up with any complications
1. wipe data, cache, and dalvik
2. flash remICS
3. after reboot you will be stucked at samsung. pull out the battery and place it back in
4. enter recovery with 3 finger combo (vol up & down, and power). release power when samsung appears
5. flash rom again, and reboot
hopefully you should now see your phone booting up into ICS
http://forum.xda-developers.com/showthread.php?t=1783899
rkkaranrk said:
There is no reason for it not to work if done properly u will boot in to a new world.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
babamanan said:
yes it happens with me when i flash ics over gb and after every thing phone just struck up in blue recovery it happens coz some previous system files sometimes not completely deleted, dont worry just do following as what i do.
search and download infuse toolkit v1.10 and when u got in bootloop in cwm just flash this toolkit from cwm and follow the instructions till option full wipe or complete wipe after that it will again boot up in cwm recovery now wipe cach system and again install ur rom.
Click to expand...
Click to collapse
Thanks for the tip and I have made 3 more attempts today, which all failed. I have returned to the stock rooted GB as mentioned at the initial thread each time to return to a working OS. I have recorded my last attempt of the day throughout the duration, including the method you have mentioned. I'll list what I have done in short below;
youtube.com/watch?v=RGCEkRVlHog (Unable to embed links, my apologies for any inconvenient)
1. Factory Format, Wipe Cache, Wipe Delvik Cache,
2. Flash rom from internal SD,
3. Advance > Reboot Recovery,
4. Flash again after re-enter Recovery,
5. Boot-looped as expected, thus flashed Infuse Toolkit v1.1,
6. Wipe Cache and Complete Wipe,
7. Quit and automatic reboot,
8 -Stuck at Cyanegen Mod Screen, wont enter Recovery Mod again-, no matter what i do. I tried pulling battery out and reboot into recovery, stuck anyhow.
Then I entered Odin and flashed stock GB back and my phone is working fine. Please point out any missing steps or mistakes to the installation. I suppose it's a conflict with the internal SD rather than system error, welcome to any suggestions. Again, thanks for all the replies so far. Anything is appreciated!
ps: I will give other Ice Cream Sandwich ROMs a shot this weekend, hope the above would not occur on the other roms. :/
Don't use the reboot option from recovery and did u tried downloading the ROM file again.
Sent from my SGH-I997 using Tapatalk 2
Sorry for the late update, but no luck for any other ICS roms available for infuse. All ended up the same, blue recovery bootlooped.
I'm wondering if there's any way that I can wipe all the data, including the stuff on internal SD like an ultimate factory reset with only the running ROM left so I can do a clean ICS flash? Thanks all.
cx831 said:
Sorry for the late update, but no luck for any other ICS roms available for infuse. All ended up the same, blue recovery bootlooped.
I'm wondering if there's any way that I can wipe all the data, including the stuff on internal SD like an ultimate factory reset with only the running ROM left so I can do a clean ICS flash? Thanks all.
Click to expand...
Click to collapse
It is possible that reboot recovery while in cwm got you in this recovery loop.
There may be a misc recovery img created.
You have to delete that misc with a prepare cwm-flashable script.
On the infuse, mounting usb in cwm doesn't work.
If you can get at it in adb, this command may work:
C:\> adb shell erase_image misc
You will have better luck in factory/data reset in cwm.
Put the phone in DL mode.
Odin or Heimdall back to stock with repartition and start over.
This time around, remember not to reboot into recovery while in cwm
I had the OP's exact issue when I upgraded from CM7 to remics last week. I was running froyo bootloaders and LB's CM7 (http://forum.xda-developers.com/showthread.php?t=1195525) with whatever kernel came with that (it had blue CWM).
I followed the instructions for "coming from Gingerbread" in the original remics thread (before it was updated this week) and I ran into OP's *exact* problem with looping back into recovery. I got on the #infuse4g IRC and got help from Aerema(sp?) and entropy. I learned some new things and tried everything they suggested (a lot of which I'm reading in this thread)... but none worked for me.
To get to the point, in the end... and I know this doesn't seem to make sense, but what worked for me was using Odin to "return to stock", then flashing the kernel from the remics package and flashing remics.
I had been using qkster's Heimdall OneClick return-to-stock (http://forum.xda-developers.com/showthread.php?t=1524081). Heimdall always worked and didn't report any problems. I even used heimdall command line interface when I upgraded from froyo to gb bootloaders.
To this day, I don't understand why using Odin return-to-stock (http://forum.xda-developers.com/showthread.php?t=1705260) got me out of the recovery loop.
I *think* my upgrade path went like this.
Starting with CM7Kang/froyo BL
1) download remics1.3.zip, followed instructions exactly & flashed remics1.3.zip from blue CWM.
2) rebooted, ROM worked just fine but had rainbow recovery.
3) attempted qkster's heimdall OneClick GB BL upgrade (update bootloader checkbox). It failed.
4) updated to GB bootloader using heimdall command line (http://forum.xda-developers.com/showpost.php?p=24901128&postcount=3)
5) ** recovery loop ** seemingly tried everything from double-flashing kernel-only using heimdall command line to reverting back to stock (heimdall), format /system, Infuse Toolkit, etc and so on.
6) used ODIN return-to-stock and from there the upgrade went perfectly.
I, too, would like to express my gratitude to bradman117 and everyone else involved in making this ROM available to the general public. I'm really liking it. Nice to have ICS on a > 1 yr old device. Thanks to those who still visit the #infuse4g IRC chan as well.
TL;DR - I had to use the Odin return-to-stock to fix recovery looping, even though Heimdall return-to-stock appeared to be doing everything correctly.
Problem Solved.
qkster said:
It is possible that reboot recovery while in cwm got you in this recovery loop.
There may be a misc recovery img created.
You have to delete that misc with a prepare cwm-flashable script.
On the infuse, mounting usb in cwm doesn't work.
If you can get at it in adb, this command may work:
C:\> adb shell erase_image misc
You will have better luck in factory/data reset in cwm.
Put the phone in DL mode.
Odin or Heimdall back to stock with repartition and start over.
This time around, remember not to reboot into recovery while in cwm
Click to expand...
Click to collapse
Finally got my ICS working now. Can't thank you enough for qkster Heimdall One Click Gingerbread ROM:good::good::good:.
For everyone's reference, the following is what I've done;
1) Flashed the Heimdall One Click GB Stock rom, a big thanks to qkster,
2) Flashed the CWM Recovery just under the same thread,
3) Flashed the RemICS rom with factory wipe and formatting data, system and cache, again after reboot.
4) >Bootlooped at the SAMSUNG screen,
5) Followed the solution of bootlooping under the RemICS thread and flashed Heimdall GB Stock again,
6) Flashed Clockworkmod again,
7) Installed RemICS rom again (Step 3) & WORKING LIKE A CHARM NOW!
I suspect my initial problem was caused by internal conflicts between the Rooted ROM and ICS, yet it is not evident nor I'm experienced to make such conclusion. Anyway, glad that my Infuse is finally able to run on Ice Cream Sandwich and I really dont care about what had caused the problem prior.
Big Thanks to rkkaranrk and qkster. :laugh:
New to xda, so I'll just let you in everything in the last 2 hours. I flashed Bugless Beast (2002-06-09), wiping cache and dalvik cache and it ran fine. Then I installed the Matr1x bfs v22.5 from bootloader and rebooted once more. After that, it stayed on the Google screen until I removed the battery. So far the only possible solution that I've looked into is this thread called [HOW TO] Return to Stock Using Odin (VZW and GSM) -- you can google the link to see what I'm talking about. I can't seem to get the process to succeed. The attempts always end up as successful: 0 failed: 0 I tried using both the VZW from the first link given and the GSM: CF_ODIN_YAKJU_IMM76D_full for the PDA button on Odin. Nothing comes up on Odin when I mount the phone to the PC so I'm not sure if I'm even connecting, although I was able to connect the phone to the PC early today to transfer files. Could I be using incorrect files to start Odin? Am I connecting to Odin? Are there any other possibilities besides using Odin to return this phone to normal?
I was running early versions of Bugless Beast and Matr1x before flashing the new versions. Please, I need to get this phone fixed before this weekend. Thanks, in advance.
itsTnTg said:
New to xda, so I'll just let you in everything in the last 2 hours. I flashed Bugless Beast (2002-06-09), wiping cache and dalvik cache and it ran fine. Then I installed the Matr1x bfs v22.5 from bootloader and rebooted once more. After that, it stayed on the Google screen until I removed the battery. So far the only possible solution that I've looked into is this thread called [HOW TO] Return to Stock Using Odin (VZW and GSM) -- you can google the link to see what I'm talking about. I can't seem to get the process to succeed. The attempts always end up as successful: 0 failed: 0 I tried using both the VZW from the first link given and the GSM: CF_ODIN_YAKJU_IMM76D_full for the PDA button on Odin. Nothing comes up on Odin when I mount the phone to the PC so I'm not sure if I'm even connecting, although I was able to connect the phone to the PC early today to transfer files. Could I be using incorrect files to start Odin? Am I connecting to Odin? Are there any other possibilities besides using Odin to return this phone to normal?
I was running early versions of Bugless Beast and Matr1x before flashing the new versions. Please, I need to get this phone fixed before this weekend. Thanks, in advance.
Click to expand...
Click to collapse
you flash jelly bean kernel on ICS rom !(v.22.5 and higher are Jelly Bean, v.22.0 and lower are ICS)
you can boot on recovery ?
like leap said you flashed a JB kernel on a ICS ROM. Just download Matr1x v20 and flash it from the CWM recovery, it should boot right away. If not just go in CWM wipe factory reset and reflash Bugless Beast, or any other ROM, and the proper kernel (Matrix v20 for ICS, 20.5 for JB). Don't mess with Odin if you don't have experience or flash a wrong ROM stock into your Nexus, unless you want a nice paperweight.
Thanks
leap_ahead said:
you flash jelly bean kernel on ICS rom !(v.22.5 and higher are Jelly Bean, v.22.0 and lower are ICS)
you can boot on recovery ?
Click to expand...
Click to collapse
Wow, thanks! I run v. 22.0 and it works fine now.. I feel embarrassed of how simple it is to fix it.
Thanks
DeuXGod said:
like leap said you flashed a JB kernel on a ICS ROM. Just download Matr1x v20 and flash it from the CWM recovery, it should boot right away. If not just go in CWM wipe factory reset and reflash Bugless Beast, or any other ROM, and the proper kernel (Matrix v20 for ICS, 20.5 for JB). Don't mess with Odin if you don't have experience or flash a wrong ROM stock into your Nexus, unless you want a nice paperweight.
Click to expand...
Click to collapse
Thanks for the instructions! You saved me like a whole day of trying to fix this phone.
guys this is 4th day :angel:and i m trying to fix sgs4g t959v.......i downloaded a lot of roms but no one will go beyond boot screen except froyo kd1.....but in froyo after successfull boot it freezes very quickly and reboots...........i m very annoyed now and want someone to share his expertise......thank you in advance:good:
yes it always go into download mode easily and sometimes into recovery but freezes very soon...............
Hi
1. Please update your thread topic, no one will help an empty topicless [Q].
2. Go here and follow instructions. This will bring you to Gingerbread (with GB bootloaders) and from there it will be very easy to upgrade.
3. Once you have a rooted GB ROM with CWM recovery 3 and above, you will be able to flash an MTD ICS ROM such as CM9/MIUI/Ultragen and then JB...
already tried that
itzik2sh said:
Hi
1. Please update your thread topic, no one will help an empty topicless [Q].
2. Go here and follow instructions. This will bring you to Gingerbread (with GB bootloaders) and from there it will be very easy to upgrade.
3. Once you have a rooted GB ROM with CWM recovery 3 and above, you will be able to flash an MTD ICS ROM such as CM9/MIUI/Ultragen and then JB...
Click to expand...
Click to collapse
bro i already tried that......upgraded with kies mini and kies said upgrade is successful but it did not go beyond boot screen
If you used kies mini you did not try that at all.
uninstall all Samsung drivers and actually try that.
itzik2sh said:
If you used kies mini you did not try that at all.
uninstall all Samsung drivers and actually try that.
Click to expand...
Click to collapse
the link you provided said first upgrade from stock froyo to stoc gb, then onwards....i did so......everything went fine but didnt boot
I think if you have the kies drivers installed you should try using gremlin remover.
dervash said:
the link you provided said first upgrade from stock froyo to stoc gb, then onwards....i did so......everything went fine but didnt boot
Click to expand...
Click to collapse
No. You need to read better. The link I sent allows you to upgrade to GB without kies and then further on. Now what you can do is uninstall kies and any other Samsung driver from PC, switch USB port and use heimdall to flash to rooted GB. From there zip flash ICS and then JB...
If you say you don't have boot you probably don't have bootloaders. Please follow instructions and read them well.
sent from me
Did you do the factory reset between?
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
champ1919 said:
Did you do the factory reset between?
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
Click to expand...
Click to collapse
nothing comes beyond boot screen.......how can i do a factory reset.....the one stock rom kd1 i m able to boot but it freezez after seconds.......let me try
i managed to do a factory reset but to no avail
You might be getting confused. Please go back to the link provided by itzik2sh and study the guide on using Heimdall. It's fairly lengthy but completely accurate. It will show you how to use Heimdall to get to stock GB, how to use Heimdall to root your phone by flashing AntonX's kernel, how to flash the necessary bootloaders, and even how to get your device into download mode. It's pretty much foolproof...and it works...please do your homework...we will be grading you.
DickyG said:
You might be getting confused. Please go back to the link provided by itzik2sh and study the guide on using Heimdall. It's fairly lengthy but completely accurate. It will show you how to use Heimdall to get to stock GB, how to use Heimdall to root your phone by flashing AntonX's kernel, how to flash the necessary bootloaders, and even how to get your device into download mode. It's pretty much foolproof...and it works...please do your homework...we will be grading you.
Click to expand...
Click to collapse
bro i did all heimdall one clicks...stock kj6, stock+root, stock kf1..,,but nothing happened........the only thing worked is i downloaded this starter pack http://forum.xda-developers.com/showthread.php?t=1223765 and installed both but nothing happened...then again i flashed first which is kc1 with pit file then i flashed stock froyo rom downloaded from sammobile.....it boots up but suddenly freezes after 20 or so seconds......i erased to factory but the result was same.......then i flashed bali 3.03 kernel and booted to cwm recovery and tried to flash icbinb.....as required i flashed ext4 converter then immediately as i try to flash icbinb....recovery freezes randomly.....and i m unable to complete process.......may be it has some hardware issue
One final thought...looks like you've tried kies, Odin, & Heimdall. There is the possibility that you might have some conflicting drivers wandering around your computer. Why don't you try another computer (if one's available). Run Heimdall...be sure to follow the instructions on verifying your Java version and Microsoft Visual C. If you are successful, be sure and flash the bootloaders and then the basic-with-a-twist kernel.
Hope this works...I'm out of ideas.
i did so.....but no difference......i think it has some hardware problem.....because even if i m in recovery....it freezes after some tine....be it stock recovery or cwm......also i mentioned earlier that only rom which i was able to boot was stock froyo.....but it also freezes after a couple of minutes. and if i dont turn off during it is frozen it becomes very hot and gives over heat signal at next restart..................so assuming it had a hardware problem i returned back the device