Related
All working again! Thanks to all that helped!
Ok, five hours later and I'm about to bash this damn phone!
So, being new to the sgs4g i was trying to flash miui self kang (didn't work, not sure why) then when I restored back via cwm it wouldn't boot past the galaxy logo. So long story short I used heimdall (sp) to get to where I am now. Phoene boots, it's usable, kies states it's up to date. Problem is it won't go into any recovery.
vol down + power= download mode
Vol up and down + power= nothing
vol up + power=nothing
I flashed the subtly modded stock kernal. No recovery, same issue
I copied and pasted the cwm recovery file to the /system/bin file and still same problem.
Here is the about phone
Model Number= sgh-t959v
Firmware=2.3.6
Baseband= t959vuvkj6
kernel version=2.6.35.7-sms-kj6-v0.1.1-rc1+
build number= gingerbread.vuvkj6
Rooted using super one click.
Please help keep me from going back the my WP7 HD7!
http://db.tt/N5vW0Z1m
Install quickboot, run it, select recovery
Awesome!! That worked and I can still flash, but I don't understand why I have hold any volume buttons to boot into recovery.
You can use the buttons it's just a little tricky. Hold volume up & down. Hold power. Galaxy spalsh screen comes up. In a few seconds it gets brighter. As soon as it get brighter let go of power only. Keep holding volume up and down until you get recovery. Quickboot just makes it really easy.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
No dice, still doesn't boot into recovery. Can't even get into stock recovery.
tnygigles66 said:
No dice, still doesn't boot into recovery. Can't even get into stock recovery.
Click to expand...
Click to collapse
Go flash bhndven's SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders. That particular ROM has CWM, root, and voodoo lagfix. Flash it twice and the 2nd time around ensure "Flash Bootloaders" is checked. That way you know you're on a stable ROM with proper, working boot loaders.
All you need to install it is Java. You can read the OP on how to flash it here.
tnygigles66 said:
No dice, still doesn't boot into recovery. Can't even get into stock recovery.
Click to expand...
Click to collapse
When you use quickboot what version of cwm are you in? Should be v5.0.2.7 with that kernel. I don't think you'd still have stock recovery available. If it it v5 than you should be able to use the botton combo I posted above. Make sure to let go of power. If it still is giving you issues I agree with steven. Reflash.
5.0.2.7.......
will reflash
Let us know how it goes.
Sent from my SGH-T959V using xda premium
Reflash went well! Can boot into recovery holding volume keys. Flashed Valhalla Final and all is well.
Had to use the HD7 yesterday, nothing compares to the sgs4g screen!
Awesome, glad you're working again. Please edit the OP & add [SOLVED] to the title. Thanks!
Sent from my SGH-T959V using xda premium
hi, i have a nexus s 4g and it has ClockWorkMod 5.0.2.0. when ever i try to boot into recovery by holding the volume up and power buttons at the same time, i get the stock android recovery, then i scroll down to recovery and then a picture of the android comes up, then after that a big yellow triangle with an exclamation point comes up and ClockWorkMod doesnt come up. but sometimes it works. i just want to be absolutely sure that i can boot to recovery so i can recover a nandroid backup when i am flashing roms just in case something goes wrong. please help
fastboot flash recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-crespo4g.img
are you using stock rom? stock rom erases your custom recovery every time you reboot your device.
if you are running stock rom flash this after you flash recovery and your custom recovery will stick
sean1984 said:
fastboot flash recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-crespo4g.img
are you using stock rom? stock rom erases your custom recovery every time you reboot your device.
if you are running stock rom flash this after you flash recovery and your custom recovery will stick
Click to expand...
Click to collapse
now it makes sense! thank you!
steineronie said:
now it makes sense! thank you!
Click to expand...
Click to collapse
anytime
sean1984 said:
fastboot flash recovery
are you using stock rom? stock rom erases your custom recovery every time you reboot your device.
if you are running stock rom flash this after you flash recovery and your custom recovery will stick
Click to expand...
Click to collapse
I am having the same problem as the OP, but this post doesn't make any sense to me. It seemed to have worked for him though, so could I ask you to elaborate?
I never had clockworkmod work for me, and I get to the same screen when I use the vol up button and the power button. I am not sure what to do with that file you posted though.
suncross said:
I am having the same problem as the OP, but this post doesn't make any sense to me. It seemed to have worked for him though, so could I ask you to elaborate?
I never had clockworkmod work for me, and I get to the same screen when I use the vol up button and the power button. I am not sure what to do with that file you posted though.
Click to expand...
Click to collapse
I had this exact same problem on 2.3 .. I'd have to flash CWM everytime I wanted something flashed. If it doesn't do it the first time and it shows u the stock recovery, reboot and open CWM and flash again. Then flash the Fix and ull be fine . For me it fixed itself once I got to 4.0.x
- Google
Reason: on a stock ROM the /system/etc/install-recovery.sh script will replace any custom recovery on each boot. Feel free to rename or delete this file, the next recovery you flash will stick until you flash another Stock ROM.
Harbb said:
Reason: on a stock ROM the /system/etc/install-recovery.sh script will replace any custom recovery on each boot. Feel free to rename or delete this file, the next recovery you flash will stick until you flash another Stock ROM.
Click to expand...
Click to collapse
I know this is a little bit of a older post but it seems relevant. I have a epoc 4g touch running AOKP Milestone 5 and I am unable to make CWM Stick keeps reverting to the stock android recovery. Any Ideas?
bsxed said:
I know this is a little bit of a older post but it seems relevant. I have a epoc 4g touch running AOKP Milestone 5 and I am unable to make CWM Stick keeps reverting to the stock android recovery. Any Ideas?
Click to expand...
Click to collapse
Well i don't have an Epic 4G Touch so i can't say for sure, but it's probably exactly what i said before. Rename or delete the file: /system/etc/install-recovery.sh
No harm will be done, all the script does is replace the stock recovery on boot if it finds that a non-stock one is present. You can do this with ES File explorer, FX or whatever file manager you please (or terminal if you know how).
To whoever can help me -- I'm trying to use kexec to install CM10 on my SGS3, but i've been hearing that when you hard-reboot your phone, AKA battery pull/death, or using the power button, you go right back to the recovery. This isn't a problem, as long as I don't have to re-flash CM10 every time I boot, or I have no choice but to go to the stock ROM. I'd like to be able to either boot to the CM10 or go to my currently flashed version of CM10 from the recovery.
Any clarification on how kexec works on the SGS3 or any advice might help.
Thanks!
Bumping... could really use help here.
Just reboot from recovery and it will bootloop a couple times then boot up.
DonSagiv said:
Any clarification on how kexec works on the SGS3 or any advice might help.
Thanks!
Click to expand...
Click to collapse
Flash a recovery that supports kexec. You'll find this in the OP of the CM10 threads. Then make a backup, wipe data/cache, flash CM10, and flash Gapps, reboot. When your phone boots, it will appear to bootloop once or twice. Ignore it and give it a few minutes, longer after a new flash. Expect that every time. Once in a while, a cold boot may boot you into recovery. In recover, just tell it to reboot and you'll be back in CM10. That's all there is to it, for an end user. It won't force you to go back to stock, and you don't have to flash anything every boot.
You may have heard conflicting information from outdated threads. Before some smart cookies automated the kexec process, you had to do some manual flashing every reboot. This is no longer the case.
lazarus2405 said:
Flash a recovery that supports kexec. You'll find this in the OP of the CM10 threads. Then make a backup, wipe data/cache, flash CM10, and flash Gapps, reboot. When your phone boots, it will appear to bootloop once or twice. Ignore it and give it a few minutes, longer after a new flash. Expect that every time. Once in a while, a cold boot may boot you into recovery. In recover, just tell it to reboot and you'll be back in CM10. That's all there is to it, for an end user. It won't force you to go back to stock, and you don't have to flash anything every boot.
You may have heard conflicting information from outdated threads. Before some smart cookies automated the kexec process, you had to do some manual flashing every reboot. This is no longer the case.
Click to expand...
Click to collapse
In which cases would someone lose kexec and need to reinstall it?
Zalithian said:
In which cases would someone lose kexec and need to reinstall it?
Click to expand...
Click to collapse
When u flash back to stock.
droidstyle said:
When u flash back to stock.
Click to expand...
Click to collapse
Or any rom.
jaymattt said:
Or any rom.
Click to expand...
Click to collapse
not necessarily...if your flashing a custom rom/kernel like beans custom stock, cm10, paranoidandroid, aokp, or imosyeons Touchwiz leankernel, kexec is always there...kexec is built into the kernel, cwm 6.0.1 is compatible with kexec.
Question though. Could cwm touch be modified to make it kexec enabled?
Sent from my SCH-I535 using xda app-developers app
Vorfidus said:
Question though. Could cwm touch be modified to make it kexec enabled?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used cwm touch for the very first kexec kernel release(boosted v.1 https://www.dropbox.com/sh/mv3gz6skad1nsnx/-oUr708Bc2), where you had to reflash the emmc in recovery on each reboot in order to stay on the custom kernel. Not sure if cwm touch works for the later kexec builds...
droidstyle said:
Just reboot from recovery and it will bootloop a couple times then boot up.
Click to expand...
Click to collapse
Thanks! CM10 works beautifully on here.
droidstyle said:
I used cwm touch for the very first kexec kernel release(boosted v.1 https://www.dropbox.com/sh/mv3gz6skad1nsnx/-oUr708Bc2), where you had to reflash the emmc in recovery on each reboot in order to stay on the custom kernel. Not sure if cwm touch works for the later kexec builds...
Click to expand...
Click to collapse
There is a kexec cwm touch recovery some where here on xda.sorry don't have the link. There is also a kexec twrp 2.2 recovery but it didn't work for me.
piiman said:
There is a kexec cwm touch recovery some where here on xda.sorry don't have the link.
Click to expand...
Click to collapse
yea i know, thats what I used in reference to my previous post.
droidstyle said:
yea i know, thats what I used in reference to my previous post.
Click to expand...
Click to collapse
would love the link, all i have is 6.0.1.0. if anyone needs a kexec (old) CWM, i posted it here:
techneesh.com/recovery.tar
err, looks like this post has touch kexec cwm?
http://forum.xda-developers.com/showthread.php?t=1773514
Triskite said:
would love the link, all i have is 6.0.1.0. if anyone needs a kexec (old) CWM, i posted it here:
techneesh.com/recovery.tar
err, looks like this post has touch kexec cwm?
http://forum.xda-developers.com/showthread.php?t=1773514
Click to expand...
Click to collapse
let this thread die....there is no need to use anything kexec. stick to cwm 6.0.1.0 or 6.0.1.2
after unlocking thru the ez tool installed twr recovery and installed the synergy rom and its just stuck on samsung galaxy s logo please help what do i do?
flameinthefire said:
after unlocking thru the ez tool installed twr recovery and installed the synergy rom and its just stuck on samsung galaxy s logo please help what do i do?
Click to expand...
Click to collapse
Sounds like an bootloop, just odin back to stock and try again.
If you remove the battery and turn it back on, will it boot into recovery?
power+vol up+home button
Karl said:
power+vol up+home button
Click to expand...
Click to collapse
yes it turns back on but i have unlocked it and its on twp recovery which rom would work with it?
i tried flashing mr beans rom that didnt work beacuse i am on twp recovery and i tried flashing synergy rom that didnt work either so wat should i do. since i unlocked the phone can i still do odin? or will that brick my phone
guys please help!
flameinthefire said:
guys please help!
Click to expand...
Click to collapse
is there any rom that i can use for my unlocked s3
flameinthefire said:
guys please help!
Click to expand...
Click to collapse
Someone already told you what to do. Find a stock ROM, boot up Odin and flash.
the roms you tried work with TWRP... ive used TWRP since release
Karl said:
the roms you tried work with TWRP... ive used TWRP since release
Click to expand...
Click to collapse
I don't think they work with TWRP. They will flash fine but they wont boot. I had the same problem as the OP when i flashed them. I guessing its because they aren't setup for unlocked phones yet. OP all you need to do is wipe using TWRP then flash the cyanogen mod 10 leak posted by CVPS. Make sure you flash gapps and you will be good to go.
Locked or unlocked phone shouldn't matter as far as the Rom is concerned, it's been stated many times that the kexec kernels will boot fine on an unlocked phone. I would suggest starting fresh, stock ODIN, root, unlock, then flash CWM 6.0.1.0 with ez recovery and go from there.
Some people are not having any issues with the touch recoveries and others are, in my experience the CWM recovery has been the most stable and I could really care less about "touching" my recovery, buttons do the same thing. Just my 0.02
Sent from my Galaxy S III using Xda Premium
feel like an old man hearing these stories......we all know them...when we first started out flashing and **** went wrong....freak outs..panics....sweating..pacing..anger....regret.........BUT then you work through them and look back and say "**** that was easier than I thought"....and we come across them again without panic or hesitation........................dude relax........
1-grab a stock image...chose anyone you want in these forums..some are even prerooted.....i personally got competely back to stock
2-i use the one click root method..so root
3-flash cmw...any version you want as long as it is made for your model phone.....you can use e-z recovery app from market
4-MAKE A ****ING BACKUP!!! very important...
5-download e-z unlock from the play market..use...and done..now you are stock, rooted, unlock bootloader......if you plan on flashing cm10 or aokp or aosp....please make sure to read the thread "how to backup your imei" before flashing any of those roms.............boom goes the dynamite:laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh:.............................
King_tee said:
I don't think they work with TWRP. They will flash fine but they wont boot. I had the same problem as the OP when i flashed them. I guessing its because they aren't setup for unlocked phones yet. OP all you need to do is wipe using TWRP then flash the cyanogen mod 10 leak posted by CVPS. Make sure you flash gapps and you will be good to go.
Click to expand...
Click to collapse
Kexec roms don't but synergy should have. I use twrp and Synergy no problem. There isn't anything special that has to be setup for an unlocked bootloader.
Op you should be able to flash any non kexec rom. Did you do a wipe factory reset? If not you may want to give that a try
I'm running into a problem with flashing kernels, for example the ktoon kernel will say it's flashed however the phone only shows the word Samsung then dies. any ideas? sorry for potentially reposting something already discussed.
renesoul said:
I'm running into a problem with flashing kernels, for example the ktoon kernel will say it's flashed however the phone only shows the word Samsung then dies. any ideas? sorry for potentially reposting something already discussed.
Click to expand...
Click to collapse
What ROM are you on?
Sent from my SCH-I535 using xda app-developers app
Sounds like you're flashing the wrong kernel version or one that is incompatible with new ROM code.
jakereeves31 said:
What ROM are you on?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I was trying to flash liquidsmooth rom, the newest available, and that wouldn't boot either which I'm guessing is because it didn't run on a stock kernel. But when i was trying in the OP i was trying Galaxy Mod rls 7 and it wouldn't get past the first Samsung boot screen whenever i would chose ktoon kernel but would work whenever stock kernel was chosen
Zalithian said:
Sounds like you're flashing the wrong kernel version or one that is incompatible with new ROM code.
Click to expand...
Click to collapse
That's possible but both kernels were provided by the rom itself so is it that likely?
renesoul said:
That's possible but both kernels were provided by the rom itself so is it that likely?
Click to expand...
Click to collapse
When certain merges are incorporated into a ROM, it is required that the kernel has that same code, or it will make the phone unable to get past the boot screen. If it's not working with the kernels provided by the ROM, then maybe you have some bad downloads, or an unfortunately special phone.
I think i might be having this problem also?
I had the latest stable version of CM10 and using EZ Recovery, i flashed the hybrid invisiblek and tried to reboot into recovery. Now all my phone does is flash the Samsung logo, then the Samsung Galaxy SIII logo and then stays black with the navigation buttons lit up. I can't seem to boot into any recovery mode by holding the power, home and volume up buttons.
Not sure how to fix this. Any help would be appreciated!
TwoGunsABlazin said:
I think i might be having this problem also?
I had the latest stable version of CM10 and using EZ Recovery, i flashed the hybrid invisiblek and tried to reboot into recovery. Now all my phone does is flash the Samsung logo, then the Samsung Galaxy SIII logo and then stays black with the navigation buttons lit up. I can't seem to boot into any recovery mode by holding the power, home and volume up buttons.
Not sure how to fix this. Any help would be appreciated!
Click to expand...
Click to collapse
You're hosed until you replace the ICS-based kernel (invisiblek hasn't come out with v3 yet - for one reason there's no source code, yet) on a JB-based ROM. Use Odin to flash a new recovery (CWM 6.0.1.2 works well) until somebody comes out with a Jelly Bean compatible kernel.
I'm told that K747 works, but I haven't tried it. By the way: read the dox a little better: if you use invisiblek's KEXEC-based kernel, then you don't have a recovery to boot into - until you flash over it. (again, I'm told you can from ADB, but I haven't tried it).