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
Related
I tried to flash a aokp rom and before flashing made a back up. Now when I flashed the rom and rebooted the phone im stuck at samsung boot. I can get into recovery. At first it was a messed up recovery i tried to get to an old rom and reinstalled inimitable on reboot still stuck at samsung but can get into red recovery. Backup when reinstalling says cant mount system/! please help me asap I cant do anything I need my phone I am in panic mode.
Have tried reflashing The ROM again...or if you just want to go back to stock see my signature for links to the one click method
...btw your in the wrong section to post this...
The OP for aokp does state to flash twice...did you?...first time with wipes, then you can pull battery ...go back to cwm and reflash...again.
going back to stock is your way. clear all that crap out
http://forum.xda-developers.com/showthread.php?t=1524081
Post one to stock.....
Post two to put cwm back on....
Read with detail...the thread I provided....
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
soulysephiroth said:
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
Click to expand...
Click to collapse
We have no ics boot loaders...froyo boot loaders make the recovery look funky...gingerbread boot loaders fix that problem and can be used with froyo, gingerbread and ics ...not trying to be rude or a jerk just informing you
Sent from my SGH-I997 using XDA
Actually the "messed up" or rainbow recovery is from the lack of gingerbread boot loaders, just figured this out this morning when I attempted to flash aokp uniporn. Once I did the heimdall one click with bootloaders checked (gingerbread boot loaders) I was able to successfully flash the aokp rom and recovery works perfectly. Its really better not to reply when one does not know what they are talking about oh and I was still able to reflash a gingerbread rom as well although I probably won't go back to gingerbread again since aokp is the **** and runs super smooth
Sent from my SGH-I997 using xda premium
Please move this thread from the Development Section.
edit- Thanks for moving it.
Sorry about posting so quickly in wrong section. I just know the guys who post in here are pros. I used heimdall and everything is back to stock, no superuser. Should that be right, am I now not rooted? I havent tried to boot into recovery, but I think I have it still. Can I just follow root methods if I want to go back to root? Thanks again.
I my experiences, I've noticed our phones use a form of "Cumulative" Upgrade system, where You have to essentially go from Froyo to GB to ICS or things go haywire when you actually start using your ICS Rom..
I've tried using Heimdall to flash back to stock, but it doesn't seem to fix all my files from time to time, so I still use GTGs Ultimate Unbrick, and once it starts up as you're in Recovery Mode do a Factory Reset/Wipe Cache Partitions, it helps with not having the "Google Authentication Failed".
It's a long process from start to finish either way, so i figure save yourself the hassle for the long run and wipe it fresh...
I used heimdall without clicking the GB bootloaders checkbox. Upon reboot after sucessfully flashing everything, my phone shows the rainbow color thing then boots normally. I have no seen any issues other than that, however I only got it back up and running about an hour ago. I will see as the day progresses what happens. I just would like to know where I go from here to reacquire root priveleges. When I try to boot into recovery with the button combo I get a rainbow colored screen and nothing else showing, should I re-run heimdall with gb bootloaders box checked?
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
drnecropolis said:
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
Click to expand...
Click to collapse
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Cjohns8792 said:
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
bigjoe2675 said:
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
Click to expand...
Click to collapse
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Cjohns8792 said:
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Click to expand...
Click to collapse
Aft your 1st flash...dont close program...but put your phone back into download mode again and then it should allow you to check the box...then..
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Axiomkid said:
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Click to expand...
Click to collapse
Can't access recovery, it just shows a full rainbow screen.
Cjohns8792 said:
Can't access recovery, it just shows a full rainbow screen.
Click to expand...
Click to collapse
my suggestion is do the method i mentioned..
____________________________________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:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
volume up/home/power button is recovery try that
and you used rom manger to flash rom?
j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.
not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.
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
Good morning...
Right now, my phone (Galaxy S III on Verizon) will not boot past the "Galaxy S III" logo. Odin will not flash a stock Jelly Bean ROM from StockRoms.net. It gets stuck on the first .img, boot.img. I am downloading a new stock ROM right now and will try a full wipe.
Being silly and ambitious, I do not have a nandroid before it wouldn't boot. On Monday (two days ago) I rooted it. I flashed the VRALEC boot chain, rebooted, flashed ClockworkMod recovery, and installed the SuperSU bootloader and root patch through recovery. I rebooted, allowing CWM to disable the automatic re-flashing of the recovery. With my newly rooted phone, I jumped at trying to install Google Wallet. I went with the route of using Wallet Installer as found on the app store. And, being silly, I checked all three OS options (JB, ICS, and one other). After authorizing the superuser request, my phone almost immediately shut off. I think I made a nandroid through CWM after that, but not one that would run.
I thought it was going to be just build.prop having issues, so I went on a wild quest trying to find a working one online and get it on the device. I worked it into the updater script of my SuperSU patch. Nonetheless, nothing there fixed it. I've tried a bunch of things, including (get this) extracting the stock system.img.ext4 image, mounting it, tarring the device, creating an MD5 for it, and wrapping it up like a nandroid to "restore" with CWM.
I'm thinking I'm going to try and wipe the entire device, maybe leave /recovery, and flash a new I-535 ROM with Odin, see if that works. I don't know if it will. Any advice?
My flash counter is at about 5 after many attempts to get back to something that will boot, so warranty is not an option. Not that they've ever been a whole lot of help anyways.
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Sent from my SCH-I535 using Tapatalk 2
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Sent from my SCH-I535 using xda app-developers app
joaquinla1 said:
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Click to expand...
Click to collapse
My phone has CWM recovery on it, but I don't see any reason CWM's factory reset and cache wipe would be any different. I'll give it a shot.
mentose457 said:
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Click to expand...
Click to collapse
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Thanks for all your help. The ROM I'm going to try and flash now is the official stock from stockroms.net. I can't post the link as I'm new but it's I535BLK_nowipe.zip. I'll keep this updated.
sworld said:
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Click to expand...
Click to collapse
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Sent from my SCH-I535 using Tapatalk 2
mentose457 said:
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Click to expand...
Click to collapse
That makes more sense.
UPDATE: I "factory reset" the data partition and formatted /system and /cache through ClockworkMod. Turned it off, flashed VRALEC through Odin, rebooted, flashed the stock ROM, and then CWM. I'm restoring my nandroid of /data right now, and I'm awaiting an OTA firmware update to bring it up to the latest VZW JB. Then I'll root.. finally.
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
z06mike said:
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
Click to expand...
Click to collapse
Really? I've only odined once on the s3 and didn't have to wipe. On the fascinate and an older version of Odin after the flash before it booted it would automatically wipe.
Sent from my SCH-I535 using Tapatalk 2
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
So, the phone is functioning now. Of course, I am running a slightly older version and once I connect to a solid Wi-Fi network I'll request the newest update again.
However, I did already try to download the software update from Verizon, and it seemed to work fine. It rebooted into recovery and CWM seemed to handle it okay, although it claimed the signature was bad. It installed though, rebooted, and updated some app databases. And then, it said the update failed with "Code 401."
Right now I'm not too worried. Hopefully I can apply the update properly soon. It is worth noting that simply using CWM "advanced restore" on only the /data partition, without exactly matching the ROM build, has seemed to leave it hanging at the "4G LTE" logo.
Thanks for all of your help!
The phone will not install a Verizon update with a custom recovery installed.