I can't flash anything because when I go to my recovery menu I'm getting rainbows. I'm thinking this is due to the kernel that is flashed with infused v2.0.0. I just downloaded root tools and was going to use the pulldown editor, but when it said not to use on anything other than a Verizon phone, I accidentally hit the ignore button I guess? So I rebooted my phone and nothing was happening, so I pulled the battery and booted into red CWM and reflashed the serendipity rom. I rebooted out of red CWM and phone did not boot, so I went back to red CWM and flashed another rom I had, infused v2.0.0. My phone still did not boot, so I flashed the backup, update.zip and when it finished, I had green CWM, not red anymore. So just to try and get my phone working again, I flashed infused again, and this time it booted, along with the rainbows, as noted in the changelog with infused v2.0.0. So since I knew I could boot now, I rebooted into recovery to flash serendipity again, but the menu is just a rainbow, like on boot. I can navigate the CWM but I can't see anything, and the only reason I know is because I hit the power button, and I rebooted, and the first option in recovery is reboot. I wanna know if there is anyway to replace the kernel so I can see my CWM? or a way to flash serendipity with odin, because the kernel included with that contains no rainbows. Thanks in advance.
pr621 said:
I can't flash anything because when I go to my recovery menu I'm getting rainbows. I'm thinking this is due to the kernel that is flashed with infused v2.0.0. I just downloaded root tools and was going to use the pulldown editor, but when it said not to use on anything other than a Verizon phone, I accidentally hit the ignore button I guess? So I rebooted my phone and nothing was happening, so I pulled the battery and booted into red CWM and reflashed the serendipity rom. I rebooted out of red CWM and phone did not boot, so I went back to red CWM and flashed another rom I had, infused v2.0.0. My phone still did not boot, so I flashed the backup, update.zip and when it finished, I had green CWM, not red anymore. So just to try and get my phone working again, I flashed infused again, and this time it booted, along with the rainbows, as noted in the changelog with infused v2.0.0. So since I knew I could boot now, I rebooted into recovery to flash serendipity again, but the menu is just a rainbow, like on boot. I can navigate the CWM but I can't see anything, and the only reason I know is because I hit the power button, and I rebooted, and the first option in recovery is reboot. I wanna know if there is anyway to replace the kernel so I can see my CWM? or a way to flash serendipity with odin, because the kernel included with that contains no rainbows. Thanks in advance.
Click to expand...
Click to collapse
holy textwall, I can barely read what you typed...
Looks like you flashed an ancient version of Infused (2.0.0 beta - 2.0.0 final fixed the rainbows).
Odin or Heimdall can flash a fixed kernel - http://forum.xda-developers.com/showthread.php?t=1240136 covers how for Heimdall, I'm less familiar with Odin. Watch out, I've heard that Heimdall and Odin can interfere with each other if installed at the same time on Windows.
Related
OK, so I was in the process of trying to flash Infused V2 beta 3, and just downloaded the 3e recovery and put it in system/bin and rebooted and all was good, was trying to install CWM from ROM Manager. ROM Manager said it sucessfully installed CWM 2.5.0.1 or whatever the latest version is. I decided to try to reboot into recovery from within ROM Manager and now I'm stuck at the Samsung logo. What do I do?
dufrenbk said:
OK, so I was in the process of trying to flash Infused V2 beta 3, and just downloaded the 3e recovery and put it in system/bin and rebooted and all was good, was trying to install CWM from ROM Manager. ROM Manager said it sucessfully installed CWM 2.5.0.1 or whatever the latest version is. I decided to try to reboot into recovery from within ROM Manager and now I'm stuck at the Samsung logo. What do I do?
Click to expand...
Click to collapse
hold the three button combo till it reboots and let go when you see samsung. (power and both volumes)
if that doesnt get you into recovery(3e blue recovery once here you reinstall packages twice) then hold three buttons again but let go when the screen goes black. if the phone doesnt boot it is in a semi brick situation . likely a premission problem or a corrupt recovery file.
odin may be needed to flash the phone.
a voodoo kernel like "defuse" may fix it as it will redirect the phone to cwm recovery not 3e (get the .tar file not the .zip file) it will do a voodoo conversion you will hear robot voices and it may take 10min so dont jump to conclusions.
if the kernel doesnt work then flash the unbrick package.
Well I just used odin to get me back. Thanks.
Ok now I have another problem. I just noticed that every time I reboot the phone, Handcent SMS basically reinstalls itself or something. Any setting or theme changes I make don't stick when rebooted. Any ideas? Man I'm angry. All I want is to flash Infused V2 Beta 3!
EDIT: and Tango does the same thing. I'm sure others will do it too, just havent reinstalled everything yet
ttttthhhhhiiisssss ssssssssuuuuuuuuuuxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
FYI, I'm trying a factory reset right now
Factory reset got me back to... well... factory unfortunately
So I rooted my phone and flashed Krylon360's Stock + Root rom using this thread ( http://forum.xda-developers.com/showthread.php?t=1001759 ). Everything went perfectly until I rebooted from recovery mode. It sits there in the boot screen trying its hardest but just keeps randomly vibrating. Not sure what to do about this since It will not go back into download mode to retry again. Any help would be greatly appreciated.
Go back into download mode and try flashing kc1 instead
Sent from my SGH-T959V using xda premium
Nothing ended up working. Just kept sitting in the boot screen, vibrating some more. So I just flashed the original stock back onto it. Thanks for your help though.
caprisun5 said:
Nothing ended up working. Just kept sitting in the boot screen, vibrating some more. So I just flashed the original stock back onto it. Thanks for your help though.
Click to expand...
Click to collapse
Put your phone in download mode and flash the SMS-KJ6 one-click from here: http://forum.xda-developers.com/showthread.php?t=1358498
(yea, I need to update the kernel in that package... everything moves so fast)
Leave the one-click open, after the phone reboots from the first flash take the battery out (let it reboot all the way to the pink t-mobile screen, then pull the battery. It does boot into recovery and tries to do some csc update, just ignore any errors in that). put the battery back in and the battery case back on, hold vol+ and vol-, plug in the usb cable and let go of vol+ and vol- when you see the download mode screen come up.
Check the flash bootloaders and click flash again. This gets your phone on GB bootloaders, which if you're coming from froyo, you will need it (you can also get the same bootloaders from FBis251's ext4 starter kit).
After that is done, you should download octane 3 cwm zip and my latest kernel to your sdcard, reboot to recovery, wipe everything, flash octane 3 then my kernel. Let it sit for 30 minutes after rebooting to let everything juice up and soak in.
Also, never odin/heimdall flash on a low battery. Always charge your phone all the way up before doing this as not to brick because your battery died.
caprisun5 said:
So I rooted my phone and flashed Krylon360's Stock + Root rom using this thread ( http://forum.xda-developers.com/showthread.php?t=1001759 ). Everything went perfectly until I rebooted from recovery mode. It sits there in the boot screen trying its hardest but just keeps randomly vibrating. Not sure what to do about this since It will not go back into download mode to retry again. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I had the same problem. I booted into recovery cleared the cache and user data then restarted the ODIN process and it worked and booted fine.
Hey all,
My phone was acting up and had a lot of clutter so I ODIN'ed to stock WITH root and e3. I downloaded Rom manager and flashed recovery. Seemed to work. I did the double install deal. Loaded green recovery: great. Reboot the phone. Turn it off to boot back into recovery. As i do the two volume plus power button combo, phone boots and i come to the blue and yellow install screen for recovery. Happens everytime.
I even tried going back to entirely stock. No root or anything. I then rooted, added e3, and flashed. Same deal.
Whats going on?!
I'm flashing a rom right now to see if that fixes anything.
It can't be normal to have to reinstall the package everytime i reboot into recovery.
And it only boots into green. Not blue or red.
Help!
Just finished flashing Zeus and went into recovery. Booted right into red. I guess problem solved?
galaxy s phones and the infuse don't conform to the android standard. they use a kernel with initramfs for boot in place of a boot.img partition. the initramfs can't be modded short of compiling a kernel and flashing it to the phone. the behavior you described is absolutely normal for high end Samsung phones. there isn't really any other safe or easy way to do it. the green recovery is the one designed for the i9000 with the stock kernel. the red/blue versions are themed and modded version that are baked into the kernel. once you flash a rom with a custom kernel you will have red unless it is cm7 or miui which will have blue.
Thanks for the explanation! Makes sense now.
After flashing the latest ROM I was messing around with (WajkIUI 2.1.6) the phone would crash and reboot within 30 seconds of booting up. The previous ROM that was running was FAUXMIUI_RG2xV2.0.0 (01/08/2011 [v2.0.0]OVERCLOCK) that was stable except for when I’d turn wi-fi on after being off for 8 hours or so phone would reboot.
I figured I would boot into ClockworkMod Recovery and restore one of the nandroid backups, I tried booting into recovery I found out that I could not. When I hold the volume down and press the power button I see the screen that says software update (like when flashing with OneClickRecoveryFlasher).
Whenever I flash a new ROM I will Wipe data/factory reset, wipe cache partition, and then wipe dalvik before installing zip. I’ve always run cyanogenmod nighties; FAUXMIUI_RG2xV2.0.0 was the first MIUI ROM I’ve used.
When I run OneClickRecoveryFlasher, I do not see any errors on the command prompt so I am assuming it was successful, or at least thinks it was.
I tried to Restore LG G2x Stock Recovery using OneClickRecoveryFlasher and then flashing v5.0.2.0 and still no ClockworkMod Recovery, also tried v4.0.1.5 and still no ClockworkMod Recover.
I then tried http://forum.xda-developers.com/showthread.php?t=1248644 and with that I was able to get back to stock 2.3.3, tried to use OneClickRecoveryFlasher to flash ClockworkMod, still no go.
I tried LG Mobile Update and that proceeded to install something, not really sure what the update was, after the update finished, phone rebooted into stock 2.3.3. Shut the phone down and tried to flash ClockworkMod and still nothing.
I did a hard reset following http://mobilephonerepairguides.blogspot.com/2011/04/lg-g2x-hard-reset.html
I also tried http://forum.xda-developers.com/showthread.php?t=1183168, that got me to stock 2.3.3 but I still could not boot in to ClockwordMod Recovery.
I’m having a hell of a time wrapping my head around what I screwed up. Did I somehow destroy the recovery partition, is that possible? Any ideas what I broke and how to fix it? Can I used adb to view the partition table, would that tell me if something was corrupt?
Any help and ideas would be appreciated, I have tried doing my due diligence and I apologize if I missed something obvious.
Thanks,
-Matt
Faux never made a miui
Did you nvflashed recovery? If no then do that first.
NVIDIA NEVER AGAIN!
If you did the LG Updater it returned your phone to stock everything, including recovery. You need to use NVFlash (One Click method okay) to reflash CWM and then you should be good to go.
When the phone is completely off, hold volume down, then hold the power button and don't let go of both until the second lg logo.
If you hold volume down too early it'll give you the software update screen.
Well that's embarrassing, thanks buru898 that did the trick and got me into CWM Recovery. I never remember holding the power button for that long but it worked and I'll remember that for next time.
Thanks
fcisco13 said:
Faux never made a miui
Did you nvflashed recovery? If no then do that first.
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Sorry, I only wrote in the actual zip file name, I meant RG2x-MIUI v2.1.6-MultiLang/Powered by Faux Kernels CM v0.4.8(01/08/2012)[v2.0.0].
Thanks
I updated to newest CWM via Rom Manager. Went into recovery to make a back up and try a new mod to flash. After installing I hit reboot system now and it goes right back into recovery. I even pulled battery then hit power button and it takes me right back into recovery. I also restored a back up and still the same thing. Should I try to go back to the older version of recovery? Any help would be appreciated!
Now when its off and I plug it in it doesnt charge or anything it just vibrates over and over
same thing here/
you have a zip file of the older cwm version?
TokedUp said:
I updated to newest CWM via Rom Manager. Went into recovery to make a back up and try a new mod to flash. After installing I hit reboot system now and it goes right back into recovery. I even pulled battery then hit power button and it takes me right back into recovery. I also restored a back up and still the same thing. Should I try to go back to the older version of recovery? Any help would be appreciated!
Now when its off and I plug it in it doesnt charge or anything it just vibrates over and over
Click to expand...
Click to collapse
I thought I was going crazy...
Here's how you get it to boot... boot up into odin mode and select cancel.
At the same time I noticed I cannot mount external sd either :/
I found these. one has an IMG file the other is a zip
http://forum.xda-developers.com/showthread.php?t=2096735
http://forum.xda-developers.com/showthread.php?t=2153408
OK the Odin mode/hit cancel works. WOW I was worried for a minute there. WTF!!!!
TokedUp said:
I found these. one has an IMG file the other is a zip
http://forum.xda-developers.com/showthread.php?t=2096735
http://forum.xda-developers.com/showthread.php?t=2153408
OK the Odin mode/hit cancel works. WOW I was worried for a minute there. WTF!!!!
Click to expand...
Click to collapse
The 6.0.2.8 from first post works fine. I still cannot mount external sd tho
in the meantime I found this file here & applied it & now my phone is dead/
not even the jig thing with the usb-plug works/
https://www.dropbox.com/sh/bbdr01ccc5qa99y/C8o3Zu7_k4/exitrecovery.zip
i just ran into the exact same issue as the OP. i pulled the battery, booted into DL mode, volume- (Cancel), and it booted up into my ROM. i wonder if CWM is the issue?
Yes the new update must have something to do with it.
same thing happened to me today. I keep an older copy on my laptop though and just reverted to an older version using odin.
Same happened here. Was mega pissed until I found the odin fix.
What's weirder is I factory reset, formatted everything but the kitchen sink, and upon the reboot after odin, all user data was intact.
looks like this CWM update is messed up, reverting.
CMW 6.0.2.9 is broken, I think. I'm stuck in CWM reboot.
Rom Manager pulled it. If u need to revert back .8 is listed as latest. You can go back thru there.
Yep, reverted to 6.0.2.8 and restored from my Nandroid. Whew!
And yes, I used the boot to Odin and select Cancel method to get out of Recovery bootloop.
Same here. Updated to 6.0.2.9 and got stuck in recovery mode. The only way out was go to ODIN and cancel. This was bad update from clockwork team