[Q] Clockworkmod Recovery updated, can't enter recovery mode - Samsung Infuse 4G

Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!

VyCariously said:
Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
Click to expand...
Click to collapse
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.

qkster said:
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
Click to expand...
Click to collapse
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.

VyCariously said:
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
Click to expand...
Click to collapse
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.

That does remove root access. However, root isn't really necessary, at least for the stock ROM, if you have no intentions of staying stock. The ROM .zips you'll subsequently flash are pre-rooted. After you Heimdall back to stock, and flash it again with "flash bootloaders" selected, then use Heimdall to flash this kernel:
http://d-h.st/6KA
That'll flash both a new kernel and CWM Red recovery. It'll take a few minutes to boot up the first time, as it's installing the lagfix. Once it boots up, just shut it down and boot back up in recovery. From there, you can do whatever you need to do.

VyCariously said:
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
Click to expand...
Click to collapse
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl

qkster said:
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse

Thanks guys
It's been a crazy busy week and I just didn't have time to deal with the phone. I've been dealing with stock gingerbread. It's getting kind of annoying, though, it seems less stable than the custom ICS that I had on it before. Not sure when I'm going to have time to play with it again and try to get it to where I want it. I think I'm going to try to totally wipe all of the old stuff out of the memory before I do it again, though. There's something that wasn't allowing me to do what you guys are telling me to do successfully. I'm also thinking of finding a GS2 and just selling the Infuse, not because of my confusion, but because the GS2 was what I was originally looking for anyway.
I'll try to get this one set up first, though, as it's just a matter of me being obsessive about it.
qkster, I'll look into the JB, too, lol.
qkster said:
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse

Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app

XperiaNeoVNoob said:
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome

VyCariously said:
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
Click to expand...
Click to collapse
No probs...
:thumbup:
Sent from my MT11i using xda app-developers app

Related

CWM: A thread of its own

OK, it goes without saying that to do rooting and flashing you need to have at least a basic understanding of the English language, a decent IQ and the ability to follow basic instructions.
However, with the CWM mod that's out there for this phone, there are dangers in trying to use for anything other than flashing. IMO, the problem is that those discussions are getting buried in long threads that were originally meant for other Subjects. I feel that CWM needs to have a thread of its on to benefit EVERYONE, especially the newbies. So I am starting it off with this simple instruction:
DO NOT TRY TO USE A ROM MANAGER AT THIS TIME! THE DEVS WILL LET YOU KNOW WHEN YOU CAN USE IT
ALSO; DO NOT USE CWM TO RESTORE AT THIS TIME YOU WILL BE BRICKED
#2 IF YOU WANT TO GET INTO CWM FROM START-UP TO FLASH A ROM - HOLD DOWN THE VOL UP BUTTON + HOME BUTTON + POWER BUTTON, WHEN YOU SEE THE SAMSUNG LOGO, RELEASE THE POWER BUTTON.
TO END THE CONSTANT QUESTIONS ABOUT THE "GO BACK" MENU OPTION: SCROLL COMPLETELY THROUGH ALL MENU OPTIONS TWICE, THE GO BACK OPEN WILL THEN APPEAR
I ask the devs to post info. here even if it has been posted in one of the threads.
Forum Management FTW!
If one of the devs could throw up the file to flash CWM and the instructions, that might be helfpful as well.
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?
kejar31 said:
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?
Click to expand...
Click to collapse
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.
hoppermi said:
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.
Click to expand...
Click to collapse
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?
kejar31 said:
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?
Click to expand...
Click to collapse
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...
boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
I have found pressing the vol up and vol down at the same time enables the "go back" option. It will state that it is enabled.
It will pop up when you select another option first.
Sent from my voodoo Droid Charge ED2
On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
And ShotgunSam you might as well add don't restore w/ CWM in your big red warning.
boostedjti said:
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...
Click to expand...
Click to collapse
Well, I'm already stuck there, if your idea isn't too complex, I can try it out
I have one that was bricked for this reason. If anyone has any ideas I will test them out. I am good with adb shell and have been trying to figure out how to change the bootmode=7 which I think is the sdcard to 6 which I think is the nand. Can't find where the file is in the system because I can't boot. Or a signed update zip that boots Android of the sdcard like the hd2 might work.
stranula said:
Well, I'm already stuck there, if your idea isn't too complex, I can try it out
Click to expand...
Click to collapse
Go to the epic 4g forums and in development you'll find a thread that contains an update.zip that will use cwm 3.0.2.x. adb push that update to your sd card or just transfer it. Flash jts cwm compatible kernel through odin then try applying the update.zip.
Just a theory. If cwm boots, you can then flash a rom and that may work.
hoppermi said:
On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
Click to expand...
Click to collapse
That was something I mentioned on irc the other day lol great minds think alike.
Has anyone with bricked phones tried to reach out to Koush?
Sent from my ADR6400L using Tapatalk
kejar31 said:
Has anyone with bricked phones tried to reach out to Koush?
Click to expand...
Click to collapse
Koush has been worse than useless for the Galaxy S.
Well he does have the Charge listed as a supported device on his website.. if its bricking he might help.. so if my phone were bricked I would at least try and start with him
Sent from my ADR6400L using Tapatalk
I tweeted at him and said the problem. No response yet. Ill keep posted. Everyone should tell him
Sent from my SCH-I510 using XDA Premium App
Koush is looking into it.
Sent from my SCH-I510 using XDA Premium App
Thanks OP for this tread. I agree 100%.
1) I think some "bootloopers" have had success entering download mode when their SD card was pulled.
2) Have any brickers/bootloopers tried the JIG method to force download mode?
Google JIG:
http://forum.xda-developers.com/showthread.php?t=819551
http://www.youtube.com/watch?v=iSaeaAcJHqw
http://www.youtube.com/watch?v=GjDkShT-65Y
http://samsungjigs.blogspot.com/
http://shop.ebay.com/skisky1/m.html
3) Also, I *think* someone who had bootloops was able to clear his data/cache folder somehow/someway. And I *think* he was either able to stop the bootloops or at least get into download mode. But maybe I am thinking of something else here.
Would empty cache/dbdata/movinand.bin files be helpful for Odin? We could rip them out of one of the Fascinate Odin packages to be included with a "Restore to stock" Odin package. Based on the error I've seen of someone that tried to restore, it looks like /data is getting FUBARd and that's causing the problem, but it's not something I want to personally test since my phone is working.
Anyone having issues after a restore, please see if you have adb shell access. If so, please grab a logcat and post it here.
Sent from my SCH-I500 using XDA App

[Q] cannot install ANY rom or restore! help please!

So I tried to flash two of the new Roms in the dev section and now I cant boot anything at all nor can I restore my old Rom through recovery. I get to the MD5 checking then it says MD5 mismatch and doesn't let me restore. Anyone have any ideas? My phone wont boot....
After the massive googling that took place after this post I decided to just ODIN this sucker back to stock. Stock restored, root added, and CWM working again in under 10 minutes. Gonna make another backup and try reflashing again
DarkKnight worked fine for me except for some known bugs... i could'nt get the Noble Series 8.0 or 8.1 to boot at all though weird just stay at the blaze 4g splash screen
dispozable said:
After the massive googling that took place after this post I decided to just ODIN this sucker back to stock. Stock restored, root added, and CWM working again in under 10 minutes. Gonna make another backup and try reflashing again
Click to expand...
Click to collapse
I'm not to familiar with odin, this is the first time i had to use it with my blaze. how do return back to stock from odin? i don't need to at the moment, just good knowledge to have, if i got stuck in same scenario as you.
trevor7428 said:
I'm not to familiar with odin, this is the first time i had to use it with my blaze. how do return back to stock from odin? i don't need to at the moment, just good knowledge to have, if i got stuck in same scenario as you.
Click to expand...
Click to collapse
Its the same procedure you use to root your device. Put the phone in download mode and plug in usb cable. But instead of selecting blaze-root-kernel.tar (the rooted kernel you used), you'll instead select SGH-T769-UVLB7-hitsquad.tar. I have not needed to restore my device yet, so I have no experience. Just knowledge from reading. So don't take me for granted!
Sleeps17 said:
Just restore back to stock firmware using Odin. You need to download a file called SGH-T769-UVLB7-hitsquad.tar and blaze.pit, load those up in Odin and unselect all options except Reboot. And carefully make sure Repartition is unchecked as well.
Click to expand...
Click to collapse
To return back to stock I used this link: http://forum.xda-developers.com/showthread.php?t=1591601
After that I used this link: http://forum.xda-developers.com/showthread.php?t=1591598
I'm sure it wasnt the roms (I tried flashing both) that caused it because I couldn't restore my backups either, though I still don't know what happened. Safe to say the restore to stock was very fast, and now I have no worries if I soft brick again.

i am new here and i am in big problem for my infuse 4g after install custom rom

i have rooted my infuse 4g using odin using this thread http://forum.xda-developers.com/showthread.php?t=1613523. but after installing this my phone was okay, then after i took backup thru cwm, after that i installed rom of jellybean and after installing it my phone cant start, so i took battery out and again go to recovery mod and try to restore it but i m facing same problem, my phone not starting, even usb mount also not working,
i have format my infuse again and try to do it with odin again but it shows that
E: failed to mount/dbdata(file exist)
E: copy_dbdate_media:cant mount /dbdate
your storage not prepared yet, please use UI menu for format and reboot action.
media files copy failed.
please help me. i m worried about it coz just yesterday i bought it new. so please please help me.
i dont know what is UI menu also.
If you had read the OP, you can't go directly to JB, you have to be on ICS, then flash JB.
Which option did you use from that page? I've used "I997UCLB3-root.rar" many times. But sometimes it gets stuck and I have to pull the usb cable and start over.
So, use I997UCLB3-root.rar, to go back to stock GB. Then flash an ICS rom, reboot. Then flash a JB rom.
Truckerglenn said:
If you had read the OP, you can't go directly to JB, you have to be on ICS, then flash JB.
Which option did you use from that page? I've used "I997UCLB3-root.rar" many times. But sometimes it gets stuck and I have to pull the usb cable and start over.
So, use I997UCLB3-root.rar, to go back to stock GB. Then flash an ICS rom, reboot. Then flash a JB rom.
Click to expand...
Click to collapse
Thank you for your reply but i have tried directly to go to jellybean from GB 2.3.6 and i also tried now to root again using I997UCLB3-root.rat but then also my phone giving same error that E: cant mount and samsung logo come only
huseniezzaz said:
Thank you for your reply but i have tried directly to go to jellybean from GB 2.3.6 and i also tried now to root again using I997UCLB3-root.rat but then also my phone giving same error that E: cant mount and samsung logo come only
Click to expand...
Click to collapse
Flashing JB is a big leap. Some reading, specially when you are new, could have saved you the trouble. But well, now is time to learn the hard way.
Download any uclb3 back to stock pack, either Odin or heimdall. Put your phone in download mode:
1) take out battery and place it back.
2) while holding vol + & - , connect your phone with a usb cable already inserted into the Pc.
Once in download mode, see if your phone is detected by odin or heimdall. If not you may need to install the drivers.
When all is ready, hit start.
*you probably don't have GB bootloaders. That will cause rainbows in your recovery when flashing ics and jb. If you feel you cant live with them, you will need to flash them.*
To flash jellybean, 1st flash any ics rom following directions coming from GB in the OP. Once you have blue recovery, flash JB with the directions in the rom OP.
Sent from my sweet & buttery Infuse
huseniezzaz said:
Thank you for your reply but i have tried directly to go to jellybean from GB 2.3.6 and i also tried now to root again using I997UCLB3-root.rat but then also my phone giving same error that E: cant mount and samsung logo come only
Click to expand...
Click to collapse
read this, should help
http://forum.xda-developers.com/showthread.php?t=1776129
This too
http://forum.xda-developers.com/showthread.php?t=1437548
Thank you thank you thank you
andros11 said:
Flashing JB is a big leap. Some reading, specially when you are new, could have saved you the trouble. But well, now is time to learn the hard way.
Download any uclb3 back to stock pack, either Odin or heimdall. Put your phone in download mode:
1) take out battery and place it back.
2) while holding vol + & - , connect your phone with a usb cable already inserted into the Pc.
Once in download mode, see if your phone is detected by odin or heimdall. If not you may need to install the drivers.
When all is ready, hit start.
*you probably don't have GB bootloaders. That will cause rainbows in your recovery when flashing ics and jb. If you feel you cant live with them, you will need to flash them.*
To flash jellybean, 1st flash any ics rom following directions coming from GB in the OP. Once you have blue recovery, flash JB with the directions in the rom OP.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
I got my phone back. its working in 2.3.6 very nicely once again. thank you so much for response. i am very happy to see my phone start and i am smiling after 3 hours. huh. now i rooted it with odin I997UCLB3-CWM-root-deodex-extras.rar. now can you please tell me how can i install JB? i m curiously waiting to JB in my infuse. please make it JB.
huseniezzaz said:
I got my phone back. its working in 2.3.6 very nicely once again. thank you so much for response. i am very happy to see my phone start and i am smiling after 3 hours. huh. now i rooted it with odin I997UCLB3-CWM-root-deodex-extras.rar. now can you please tell me how can i install JB? i m curiously waiting to JB in my infuse. please make it JB.
Click to expand...
Click to collapse
The first link I posted for you will walk you through it. Read all the instructions, re-read, look up anything you don't understand, and then follow the directions.
huseniezzaz said:
I got my phone back. its working in 2.3.6 very nicely once again. thank you so much for response. i am very happy to see my phone start and i am smiling after 3 hours. huh. now i rooted it with odin I997UCLB3-CWM-root-deodex-extras.rar. now can you please tell me how can i install JB? i m curiously waiting to JB in my infuse. please make it JB.
Click to expand...
Click to collapse
As others mentioned, you first need to install an ICS ROM, like CM9 or Uniporn. The first time you flash you will prob get stuck in a boot loop and will need to use the three finger method to get back to recovery. In case you don't know what that means, you hold the volume keys and power button to turn phone on and then release only the power button when the Samsung logo shows. When u get back to recovery, flash the same ROM a second time and then it will boot.
You will now have blue recovery so you can flash the jb ROM of choice by following the method in the OP for that ROM. Remember to pull out the external sdcard if you have one.
Also, as others have mentioned, you may not have GB bootloaders. To get them, go to the "ISET infuse everything thread" which is stickied in the dev section. You will find Odin and Heimdall packages which have the bootloaders there. Be very careful when installing bootloaders (test usb with a kernel or something less dangerous first) bc if it fails while trying to flash the bootloaders, it can hard brick your phone. And then thank bigjoe for putting together the ISET thread so all infuse users can find everything we need in one place.
Sent from my SGH-I997 using xda app-developers app
Thank you thank you thank you
benbos_06 said:
As others mentioned, you first need to install an ICS ROM, like CM9 or Uniporn. The first time you flash you will prob get stuck in a boot loop and will need to use the three finger method to get back to recovery. In case you don't know what that means, you hold the volume keys and power button to turn phone on and then release only the power button when the Samsung logo shows. When u get back to recovery, flash the same ROM a second time and then it will boot.
You will now have blue recovery so you can flash the jb ROM of choice by following the method in the OP for that ROM. Remember to pull out the external sdcard if you have one.
Also, as others have mentioned, you may not have GB bootloaders. To get them, go to the "ISET infuse everything thread" which is stickied in the dev section. You will find Odin and Heimdall packages which have the bootloaders there. Be very careful when installing bootloaders (test usb with a kernel or something less dangerous first) bc if it fails while trying to flash the bootloaders, it can hard brick your phone. And then thank bigjoe for putting together the ISET thread so all infuse users can find everything we need in one place.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Thank you so much, i have flashed JB successfully and GAPPs also. thank you once again. i followed your method and its very easy. first CWM was red i flash JB and after that i pull battery and start CWM at that time it was Blue and i flashed, now its installed.
One more HAPPY INFUSE OWNER.
Is this forum group great, or what!!!!!!
benbos_06 said:
As others mentioned, you first need to install an ICS ROM, like CM9 or Uniporn. The first time you flash you will prob get stuck in a boot loop and will need to use the three finger method to get back to recovery. In case you don't know what that means, you ...
Click to expand...
Click to collapse
I think if you don't know what "that" means...it means you have not read anything you probably need to read on this forum. and probably should not even be thinking about JB let alone trying to flash it.
No slight on you benbos_06, I thought it was funny reading uninformed posts about "rainbow colors" in their their recovery a few months ago...now it's almost kind of sad to see the uninformed trying to go JB...and needing double flash and 3 finger to recovery detailed in step by step instructions. Jeeze!!! That's a little scary.
Sent from a de-FUNKt Infuse
Smokestack360 said:
I think if you don't know what "that" means...it means you have not read anything you probably need to read on this forum. and probably should not even be thinking about JB let alone trying to flash it.
No slight on you benbos_06, I thought it was funny reading uninformed posts about "rainbow colors" in their their recovery a few months ago...now it's almost kind of sad to see the uninformed trying to go JB...and needing double flash and 3 finger to recovery detailed in step by step instructions. Jeeze!!! That's a little scary.
Sent from a de-FUNKt Infuse
Click to expand...
Click to collapse
+ 100... right on, Smoke !!

Need help pushing gapps with odin ASAP!

I installed paranandroid and gapps but it was the wrong gapps which caused it to error out during install. so now I have the correct gapps on my SD card but do not know how to access it through my phone since I have no recovery. How do I get gapps back on phone so I can get into recovery?
damn....
PHUCK! ok now I'm really freaking out... flashed gapps and says framework as stopped. wont let me past the front screen saying touch android to begin...
1Android said:
PHUCK! ok now I'm really freaking out... flashed gapps and says framework as stopped. wont let me past the front screen saying touch android to begin...
Click to expand...
Click to collapse
OK, don't panic yet! Basic questions first:
Did you flash a recovery like CWM (Clockworkmod) before trying to flash the rom?
Are you able to get into recovery mode via volume up+power+home?
Why dont you reflash the ROM and then do the right Gapps? That way you wont have any screwed up files at all. If you really screwed it up just Odin back to stock and start again.
just flash the rom over the top then flash the right gapps
I went into panic mode and my head went cloudy. I kept olding down volume instead of volume up. Got into recovery and just doing a restore for now till I can make sure I have all the right files...
thanks guys for answering so quickly.
1Android said:
I went into panic mode and my head went cloudy. I kept olding down volume instead of volume up. Got into recovery and just doing a restore for now till I can make sure I have all the right files...
thanks guys for answering so quickly.
Click to expand...
Click to collapse
Good, now when that's done, lets get you up and running with paranoid. It is alot easier, and generally safer to flash through CWM on the phone itself then through odin on your desktop or even the odin app. What method were you using? And more importantly did you do a IMEI backup?
Haven't done the imei backup yet. Need to though asap. I always flash through cwm but once I installed the wrong gapps (didn't even think of grabbing a JB gapps until after I got my phone into recovery and restored) I had no idea how to get into recovery. Once I found the goo manager in system settings I was able to get into recovery. Tried flashing another gapps file (which again was the wrong file) which is where I really freaked out with my framework and setup no working. Was able to clear my head and remember the volume UP not down. I'm restored now and will leave it on synergy till I do my imei backup. Haven't even looked into it to be honest. Is it difficult? Is paranandroid really much better as far as battery life to worry about taking the time to do it?
Sent from my SCH-I535 using xda app-developers app
1Android said:
Haven't done the imei backup yet. Need to though asap. I always flash through cwm but once I installed the wrong gapps (didn't even think of grabbing a JB gapps until after I got my phone into recovery and restored) I had no idea how to get into recovery. Once I found the goo manager in system settings I was able to get into recovery. Tried flashing another gapps file (which again was the wrong file) which is where I really freaked out with my framework and setup no working. Was able to clear my head and remember the volume UP not down. I'm restored now and will leave it on synergy till I do my imei backup. Haven't even looked into it to be honest. Is it difficult? Is paranandroid really much better as far as battery life to worry about taking the time to do it?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The IMEI is very easy to do, especially if your running Synergy. There are 3 methods in the link I'll attach. The first uses any terminal emulator app (free in play store) and simply typing in a code: su (enter) then: reboot nvbackup (enter)...done! Then there is the next way to create a second easier to install if something were to happen way using a Synergy recovery zip. You must do the first method first or the zip way will backup the wrong IMEI. On the link there is another link to the Synergy Key zip file (its right in the directions with HERE in bold as the link). Download zip, run it in recovery ONCE to create the backup, thats it! The synergy backup can then be used on other roms. Overall its super easy, I spent 2hrs researching and 5 min creating the backup. IT really is as simple as that, just do it in order. As far as paranoid goes, I don't have hands on with it, too many bugs for me to bother with it yet, but yes it generally should use less battery due to JB's unmatched efficiency.
Here's the link: (only need to read the first page for making the backups, read further to restore which hopefully won't be needed!)
http://forum.xda-developers.com/showthread.php?t=1852255
I will look into it tomorrow. Thank you so much for your help!! Very much appreciated.
I need/want a fully functional Rom without a bunch of bugs. Might stay with synergy till some bugs can be worked out.
Sent from my SCH-I535 using xda app-developers app

Methinks I hath killed it....

Sooo....
Been reading, researching and studying for a little more than two weeks now on rooting my S3, flashing roms, kernels, etc. Most of the 2 weeks my S3 has been rooted. I felt brave enough early on to do that, but only worked up the courage to flash my first rom this morning. Using the guide found here...
http://forum.xda-developers.com/showthread.php?t=1762709
...I flashed the newly updated "SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-10-13 r169" and to my delight it worked like a charm! For most of the day today I've been learning the ins and outs of my new rom and loving it!
This evening I decided that due to my success I'd give flashing a kernel a try. I apparently should've quit while I was ahead. I found this kernel : "SGS3-VZW-kernel-jb-cm-u-10312012" I followed the above mentioned guide again and followed all of the instructions up through step 6. I unzipped the kernel, and prior to rebooting I was unexpectedly asked a question about if I wanted to restore the stock recovery (if I remember it correctly). I chose the "go back" option (to see if I could just reboot without worrying about that question) in CWM and my S3 rebooted itself at that point.
Unfortunately the reboot process got through the quick glimpse of "Samsung", then the "Galaxy S3" screen then went black and that was it. I waited a while, removed the battery to be sure it was off and tried starting up again. Same result. I've tried rebooting into recovery (vol down/ home/power) but it just shows me the same two screens and goes black, never going into recovery and never taking me to the download screen.
I decided to plug the S3 into my computer to see if I could see it in Windows Explorer (I couldn't) but I fired up Odin and it is showing that it recognizes the S3 is plugged in in the ID:COM box.
Should I attempt flashing the stock rom through Odin even though I can't get the S3 into the download screen and even though it seems the kernel is what caused my problem? Or does it not really matter at this point....is it hard bricked? I survived a soft brick last week so I have the stock rom all ready to go, but I don't want to just try Odin'ing it in without the advice of those more schooled in this than I am.
I'm not a complete idiot. My device is a Verizon Galaxy S3, I535. I've been very careful about choosing the correct roms and kernels for my device....at least I thought I had.
Any suggestions and/or advice? Perhaps I should blow the dust off my Droid X to use until I send the GS3 out for JTAG repair. Heh.
Thanks in advance from a very humbled Noob.
Well did you try to put it in download mode not recovery but download
I don't believe it's hard bricked i think you can get past this of you did put it in download mode and Odin sees it i would push the ROM
Sent from my SAMSUNG-SGH-I577 using xda premium
---------- Post added at 07:48 PM ---------- Previous post was at 07:44 PM ----------
On my phone i have to take the battery out hit the volume down button and power button at the same time then plug into the computer then it goes into download mode. It sounds like you know how to do it..
Sent from my SAMSUNG-SGH-I577 using xda premium
djteague said:
Sooo....
Been reading, researching and studying for a little more than two weeks now on rooting my S3, flashing roms, kernels, etc. Most of the 2 weeks my S3 has been rooted. I felt brave enough early on to do that, but only worked up the courage to flash my first rom this morning. Using the guide found here...
http://forum.xda-developers.com/showthread.php?t=1762709
...I flashed the newly updated "SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-10-13 r169" and to my delight it worked like a charm! For most of the day today I've been learning the ins and outs of my new rom and loving it!
This evening I decided that due to my success I'd give flashing a kernel a try. I apparently should've quit while I was ahead. I found this kernel : "SGS3-VZW-kernel-jb-cm-u-10312012" I followed the above mentioned guide again and followed all of the instructions up through step 6. I unzipped the kernel, and prior to rebooting I was unexpectedly asked a question about if I wanted to restore the stock recovery (if I remember it correctly). I chose the "go back" option (to see if I could just reboot without worrying about that question) in CWM and my S3 rebooted itself at that point.
Unfortunately the reboot process got through the quick glimpse of "Samsung", then the "Galaxy S3" screen then went black and that was it. I waited a while, removed the battery to be sure it was off and tried starting up again. Same result. I've tried rebooting into recovery (vol down/ home/power) but it just shows me the same two screens and goes black, never going into recovery and never taking me to the download screen.
I decided to plug the S3 into my computer to see if I could see it in Windows Explorer (I couldn't) but I fired up Odin and it is showing that it recognizes the S3 is plugged in in the ID:COM box.
Should I attempt flashing the stock rom through Odin even though I can't get the S3 into the download screen and even though it seems the kernel is what caused my problem? Or does it not really matter at this point....is it hard bricked? I survived a soft brick last week so I have the stock rom all ready to go, but I don't want to just try Odin'ing it in without the advice of those more schooled in this than I am.
I'm not a complete idiot. My device is a Verizon Galaxy S3, I535. I've been very careful about choosing the correct roms and kernels for my device....at least I thought I had.
Any suggestions and/or advice? Perhaps I should blow the dust off my Droid X to use until I send the GS3 out for JTAG repair. Heh.
Thanks in advance from a very humbled Noob.
Click to expand...
Click to collapse
I think you flashed the kernel for cm, and not for touchwiz.
djteague said:
Sooo....
"SGS3-VZW-kernel-jb-cm-u-10312012"
Click to expand...
Click to collapse
This is an AOSP kernel. You only flash kernels if they match your rom. Synergy is a TouchWiz rom, so you would only flash a kernel if it states it's for TouchWiz. CM =CyanogenMod, an AOSP rom. AOSP = Android Open Source Project. Basically, AOSP is stock Android but on phones that don't ship with stock Android like a Nexus device.
Should I attempt flashing the stock rom through Odin even though I can't get the S3 into the download screen and even though it seems the kernel is what caused my problem?
Click to expand...
Click to collapse
Yes, Odin flash a stock image then re-rooted and unlock your bootloader again. Just like what the other folks have said above. "Fool me once..." as the saying goes.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
This is an AOSP kernel. You only flash kernels if they match your rom. Synergy is a TouchWiz rom, so you would only flash a kernel if it states it's for TouchWiz. CM =CyanogenMod, an AOSP rom. AOSP = Android Open Source Project. Basically, AOSP is stock Android but on phones that don't ship with stock Android like a Nexus device.
Yes, Odin flash a stock image then re-rooted and unlock your bootloader again. Just like what the other folks have said above. "Fool me once..." as the saying goes.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Get him SlimSnoop. :laugh:
So reflashing the stock rom will in essence erase the AOSP kernel? It won't still be there to continue to cause problems after I Odin in the stock rom?
I'm getting an education now! Thanks so much for the continued help!
djteague said:
So reflashing the stock rom will in essence erase the AOSP kernel? It won't still be there to continue to cause problems after I Odin in the stock rom?
I'm getting an education now! Thanks so much for the continued help!
Click to expand...
Click to collapse
Odin flash will reset everything to factory settings. You'll just have to reroot and unlock once again.
Edit: Since I re-read your post. Volume down, home, and power will take you to download mode. This still works correct?
SlimSnoop you are turning what was a rather bummer of a night around! One final question before I push the start button in Odin...
I can flash the stock rom even though my S3 doesn't appear to be in dowload mode? (although the ID:COM box shows that Odin sees my phone)
Thanks again!
djteague said:
SlimSnoop you are turning what was a rather bummer of a night around! One final question before I push the start button in Odin...
I can flash the stock rom even though my S3 doesn't appear to be in dowload mode? (although the ID:COM box shows that Odin sees my phone)
Thanks again!
Click to expand...
Click to collapse
What do you mean it "doesn't appear to be in download mode"? When you pull the battery/reinsert then hold volume down, power, and home for like ten seconds, what does it do? Do you get the prompt to to boot into download mode?
SlimSnoopOS said:
What do you mean it "doesn't appear to be in download mode"? When you pull the battery/reinsert then hold volume down, power, and home for like ten seconds, what does it do? Do you get the prompt to to boot into download mode?
Click to expand...
Click to collapse
Don't hit no button if not in download mode.
Nevermind...my bad. Now my noobness is really starting to show. I had tried putting it into download when I first realized there was a problem, but apparently did something wrong. It worked this time, the stock rom is flashed and all is well.
Now, all that remains to be seen is whether or not this little adventure has scared me into being satisfied with my stock GS3 or if I go back to tinkering.
I truly thank you guys for holding my hand and getting me through this! Much obliged!
djteague said:
Nevermind...my bad. Now my noobness is really starting to show. I had tried putting it into download when I first realized there was a problem, but apparently did something wrong. It worked this time, the stock rom is flashed and all is well.
Now, all that remains to be seen is whether or not this little adventure has scared me into being satisfied with my stock GS3 or if I go back to tinkering.
I truly thank you guys for holding my hand and getting me through this! Much obliged!
Click to expand...
Click to collapse
Go back to custom roms and flash Synergy again!

Categories

Resources