I had been running liquidsmooth rom. There were issues when it booted up, would always boot twice then went into the system ok. I decided that I'd rather have a more stable rom on my phone, so I went into ez recovery and tried to flash back into cwm 6 recovery. When it came up, the restore backup option was not there, and I couldn't boot back into the rom. I tried several times, but to no avail
Since then I have tried Odin on the phone, and have gone through the soft brick recovery steps that I had to do one time before. I flashed both files and the stock file for the third step. I do get the error messages that I normally would where normally I would factory reset and clear cache, however I then get two more.
e: failed to verify whole-file signature
E: signature verification failed
Instalation aborted.
I cannot get beyond that, I do the wipe and reset each time, however when I reboot I just get funneled back to the same error message. I've scoured the forums and the internet but cannot find a solution to my problem. Am I SOL, or is there a solution I haven't found yet?
What you could do is on your computer, download a synergy ROM like 1.5 1.6 1.7 since those don't require an unlocked boot loader. Connect your phone via USB (I don't know if it will register in the state its in) or you can get a micro SD card reader and pop that into your computer, and transfer the synergyrom on your SD card and pop it back into your phone..get to your custom recovery wipe data/factory reset wipe cache and dalvik cache. Then install .zip from SD card and choose the synergyrom. From there it'll take a bit for your phone to boot up, but you should be up and running and then you can do what you want. I usually keep one ROM like this on my phone so if something doesn't work out I can start over. Let me know if you need more help, I'll try my best to see what I can do from work.
VZW SGSIII SynergyRom R60 w/Imoseyon's LeanKernel v0.5
95talondsm said:
What you could do is on your computer, download a synergy ROM like 1.5 1.6 1.7 since those don't require an unlocked boot loader. Connect your phone via USB (I don't know if it will register in the state its in) or you can get a micro SD card reader and pop that into your computer, and transfer the synergyrom on your SD card and pop it back into your phone..get to your custom recovery wipe data/factory reset wipe cache and dalvik cache. Then install .zip from SD card and choose the synergyrom. From there it'll take a bit for your phone to boot up, but you should be up and running and then you can do what you want. I usually keep one ROM like this on my phone so if something doesn't work out I can start over. Let me know if you need more help, I'll try my best to see what I can do from work.
VZW SGSIII SynergyRom R60 w/Imoseyon's LeanKernel v0.5
Click to expand...
Click to collapse
I actually had that on my sd card from last night when I was messing with it trying to fix it. I did try that and this is what I get
--Install /sdcard...
Finding update package...
opening update package...
verifying update package...
E:signature verification failed <in red type>
Instalation aborted.
Thanks for your suggestion, Part of the problem could be I'm not getting the traditional cwm loader, every time it starts it comes up in tiny type at the top: Recovery Booting.... dont know if that makes a difference or not?
signature verification error means your booting into stock recovery instead of cwm recovery...thats why there is no back up/ restore option.
droidstyle said:
signature verification error means your booting into stock recovery instead of cwm recovery...thats why there is no back up/ restore option.
Click to expand...
Click to collapse
I can't get it to do anything other than that. I've held the up and home button to try to get elsewhere, but it always goes to that. The only other thing I can do is get to the Odin download screens, but even then, after flashing it boots back to the same place with the above errors.
udrunner said:
I can't get it to do anything other than that. I've held the up and home button to try to get elsewhere, but it always goes to that. The only other thing I can do is get to the Odin download screens, but even then, after flashing it boots back to the same place with the above errors.
Click to expand...
Click to collapse
wipe data/factory reset then reboot from stock recovery. use my guide for proper instructions on flashing back to stock. research then flash, dont flash then research.
And Liquid is supposed to boot twice. It's kexec.
Sent from my SCH-I535 using Tapatalk 2
udrunner said:
I can't get it to do anything other than that. I've held the up and home button to try to get elsewhere, but it always goes to that. The only other thing I can do is get to the Odin download screens, but even then, after flashing it boots back to the same place with the above errors.
Click to expand...
Click to collapse
Why don't you Odin back CWM recovery, boot into cwm recovery and use this to toggle secure signature off and flash synergy rom?
buhohitr said:
Why don't you Odin back CWM recovery, use this to toggle secure signature off and flash synergy rom?
Click to expand...
Click to collapse
because it trips the flash counter when you odin anything custom.
droidstyle said:
because it trips the flash counter when you odin anything custom.
Click to expand...
Click to collapse
Gotcha! I forgot about the flash counter. Thanks.
buhohitr said:
Gotcha! I forgot about the flash counter. Thanks.
Click to expand...
Click to collapse
no problem...really its not a huge deal as the app triangle away can reset it, but i prefer to just use odin for stock purposes only.
droidstyle said:
wipe data/factory reset then reboot from stock recovery. use my guide for proper instructions on flashing back to stock. research then flash, dont flash then research.
Click to expand...
Click to collapse
I had actually followed those steps already, but still get the recovery booting problem and can't seem to get past that. I can try it again after work, but have done those steps at least 3 or 4 times to no different results.
Thanks for the help though. I'll keep trucking on, just missing my phone today....
year voldsou
droidstyle said:
because it trips the flash counter when you odin anything custom.
Click to expand...
Click to collapse
I'm willing to try it if it might help me get back, I just dont want to do anything that will mess it up anymore than I already have.
At this point I just want to get back to stock /synergy if I can and be happy with it. I've never had issues like this when rooting/flashing on other phones that I've had, but at this point will just be happy with a useable phone.
droidstyle said:
because it trips the flash counter when you odin anything custom.
Click to expand...
Click to collapse
I'm willing to try it if it might help me get back, I just dont want to do anything that will mess it up anymore than I already have.
At this point I just want to get back to stock /synergy if I can and be happy with it. I've never had issues like this when rooting/flashing on other phones that I've had, but at this point will just be happy with a useable phone.
udrunner said:
I'm willing to try it if it might help me get back, I just dont want to do anything that will mess it up anymore than I already have.
At this point I just want to get back to stock /synergy if I can and be happy with it. I've never had issues like this when rooting/flashing on other phones that I've had, but at this point will just be happy with a useable phone.
Click to expand...
Click to collapse
As droidstyle mentioned that when the flash counter tripped, it won't allow you to re odin cwm. My question is can you Odin back cwm (clockmod recovery) and boot directly to it?
droidstyle said:
because it trips the flash counter when you odin anything custom.
Click to expand...
Click to collapse
Then why is it that flashing a rooted "stock" /system partition, which is technically custom, through Odin, doesn't trip the flash counter?
Is there any other downside to tripping the flash counter besides having to use triangle away to reset it if you ever want to return your phone?
buhohitr said:
As droidstyle mentioned that when the flash counter tripped, it won't allow you to re odin cwm. My question is can you Odin back cwm (clockmod recovery) and boot directly to it?
Click to expand...
Click to collapse
No, I ran home on lunch and tried, and it wont let me do that. Odin wont flash it and I just get a FAIL, and the phone say security check fail.
I After trying a few differnt times with a couple versions of the stock rom I found, I got it back up and running.
As much as I love custom roms, I think I'm done playing with this phone. Thanks everyone for the help.
Related
My buddy has the inspire 4g. He bought it rooted by somebody else. I've flashed cynogenmod for him aqnd several updates over the past few months. We are trying to flash new roms and its constantly aborting. Ive rooted my droids and always flash roms and never run into this problem.
He has the newest clockwork mod should we possible get a different recovery?
I don't do anything with flashing a new radio, is that necesary and whats causing the problem?
I am trying to flash core droid or revolution, he wants the best sense rom any suggestions?
I would appreciate any help. If there is no way to fix it I planned to totally reset and unroot and then root it myself and make sure everything is done right, does that sound right?
dieseldank said:
If there is no way to fix it I planned to totally reset and unroot and then root it myself and make sure everything is done right, does that sound right?
Click to expand...
Click to collapse
Though probably not necessary, the peace of mind that comes with knowing what's been done to the phone from the ground up might be worth it.
As for a fix to your current issue, please provide a little more detail as to the error.
It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip
dieseldank said:
It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip
Click to expand...
Click to collapse
Is this the same SD card for every try? It might be a flakey SD card. Try a different card if you can.
I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.
dieseldank said:
I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.
Click to expand...
Click to collapse
Radio is not usually flashed as part of the ROM. As long as you have a valid radio, it should work. If you somehow managed to get an invalid radio flashed, then you've have bigger problems that you indicate (i.e. hard bricked).
The fact that you can boot into recovery indicates that all it well with the device from that perspective. That leaves only the ROM zip to be flashed which is why I suggested trying a different SD card (since you tried several, it's not likely that you always got a bad download).
If it still messes up with a new SD card, try complete wipe, then format system from nandroid before running the update.zip. System partition doesn't get formatted during a complete wipe, but most ROMs should format it as a matter of course before installing. It's unlikely, but it could be a corrupt system partition which should clean up with a format.
dieseldank said:
I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.
Click to expand...
Click to collapse
Wanna Save yourself some time and maybe some future headaches? Like posted above It helps when you know what has been done. I would start from the ground up. Get back to a stock base and go from there, this way you are not trying to track down something you may not have done but was done before he got it.
As for your issue, If a radio is recommended then it will/should state so in the thread.
I have threads on how to root his inspire but can anyone forward a link of how to completely unroot and reset. When i reset in recovery it still keeps cynogenmod on.
dieseldank said:
I have threads on how to root his inspire but can anyone forward a link of how to completely unroot and reset. When i reset in recovery it still keeps cynogenmod on.
Click to expand...
Click to collapse
There's no good reason to go through all that trouble. If you have S-OFF, then you're good to go as far as being rooted is concerned. Since you appear to have recovery too, then you're 95% rooted no matter what the current ROM is doing.
If you have S-OFF already, then going back to stock and rerooting is just going to waste time.
dieseldank said:
It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip
Click to expand...
Click to collapse
In cwm are you trying to "apply update from sdcard" or "install zip from sdcard"
install zip is what you want.... then choose the ROM. IF you're applying update.... it's gonna abort.
You could also try reflashing recovery in Rom Manager or flashing an older version of recovery.
Sent from my time waster.
Gene Poole said:
There's no good reason to go through all that trouble. If you have S-OFF, then you're good to go as far as being rooted is concerned. Since you appear to have recovery too, then you're 95% rooted no matter what the current ROM is doing.
If you have S-OFF already, then going back to stock and rerooting is just going to waste time.
Click to expand...
Click to collapse
Since it has s-off and is rooted correctly what do you advise I do to fix my abort problem? Didn't see an answer in there, thanks.
Nickovtyme said:
In cwm are you trying to "apply update from sdcard" or "install zip from sdcard"
install zip is what you want.... then choose the ROM. IF you're applying update.... it's gonna abort.
You could also try reflashing recovery in Rom Manager or flashing an older version of recovery.
Sent from my time waster.
Click to expand...
Click to collapse
I tried both ways and its aborts both ways. And Ive reflashed recovery in rom manager, should I maybe try a different recovery?
Since you are already rooted and having trouble flashing thru rom manager, why not try flashing to stock rooted thru bootloader? It's my understanding that attn1's Ace_Cingular_US rom will automatically do a full wipe and take you to the latest stock rom and radio. If that works, then you can install the latest rom manager and flash a custom rom. It's worth a shot.
Sent from my Desire HD using Tapatalk
dieseldank said:
Since it has s-off and is rooted correctly what do you advise I do to fix my abort problem? Didn't see an answer in there, thanks.
I tried both ways and its aborts both ways. And Ive reflashed recovery in rom manager, should I maybe try a different recovery?
Click to expand...
Click to collapse
It's not gonna hurt. it sounds like the recovery is having issues with the script so it's aborting... an older recovery may resolve that issue.
But that's a good idea also... flash the lastest stock rooted ROM thru hboot. Then reflash recovery. see If that don't solve it
Sent from my time waster.
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..
Ok so yesterday I received a cappy from someone on here that I told them I would try and fix. I am not charging them anything and am actually paying shipping back to them. When I received it and turned it on it was stuck at the end of the cornkernel bootlogo. I thought hey this will be easy and flashed the heimdall version of I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click. Phone rebooted and is now stuck at the att logo. So I flash cornkernel, its stuck at the end of cornkernel bootup. So I decided on a whim to try and flash this kernel Devil3_1.1.3_HB_cappy_CFS_BLN_VC_20120807, luckily that got me into recovery, so I did a full backup of all the stuff on his internal storage and completely wiped the phone, wipe data/factory reset, wipe dalvik cache, format boot, format system, format sdcard, format cache, format data, format datadata (yes I know I wiped some things twice) . Then I flashed my rom, it just reboots to recovery after the flash, still reboots after a reflash of the rom. I then wiped everything again and tried flashing CM9's latest nightly to see if I could get it to boot up. Still reboots to recovery. So far all together I have flashed I897UCJI6-OCD-REV02-Low-designgears, i897uckk4 Odin One Click CONTAINS Bootloaders, Re-partition, Full Wipe, I897UCKF1_withBL,SGH-I897_I897UCKJ3, KK4-SE-One-Click, JF6 With Bootloaders, SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click Followed By I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click both are heimdall. All of those either left it stuck at att or kernel screen after I flashed a kernel. Anyone got any ideas? I am almost to my wits end.
Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium
4-2ndtwin said:
Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Already have that is my go to file actually and I tried that before going the heimdall route. Thanks Anyways.
You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium
-SGA- said:
You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Thanks for the idea. It didn't work tho. I am still at the same spot, phone keeps rebooting to recovery.
have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd
stayintwisted said:
have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd
Click to expand...
Click to collapse
Not that I know of, It isn't my phone so I do not know the history other than him saying it didn't boot past the kernel screen and receiving it and seeing that and then what I have done. Normally the sd card data from what I have seen is wiped when the eu bug happens from what I have read, maybe I am wrong, but since I backed up his data off the sdcard that is why I do not believe it has had the eu bug.
Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.
cbalt said:
Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.
Click to expand...
Click to collapse
Long story short, recovery is iffy at best for me. I went through something similar to this when trying to go from CM10 back to CM9 for the first time. Ever since then recovery has not been right.
What I did was
Install a stock one-click with bootloaders, used odin to flash speedmod kernel and then used that recovery to flash CM9 in three successions wiping everything each time. Somehow it took, and now I am no longer a crack flasher because I have the same kernel splash screen problem every time.
So,
Use this http://www.mediafire.com/?5rcofbzusoor6mv
PDA button in Odin3 1.7: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Boot into recovery.
Flash your ROM
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Try to boot normally.
Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.
There is a place that has rogers stock roms
cbalt said:
Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.
Click to expand...
Click to collapse
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way
sunfirestorm said:
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way
Click to expand...
Click to collapse
I have already tried all three of the Rogers One Clicks with none of them actually doing anything more than the Captivate One Clicks, It still doesn't boot past the first screen. Thanks for the input though.
You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work
fohdeesha said:
You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work
Click to expand...
Click to collapse
I'm going to do your steps again which is more or less what I have already done. I am waiting to hear back from the person so I can ship him the phone back and he can send it to MTV or someone or just junk it, its his phone and his choice. At this point I would say it needs Jtag or Unbrickable mod + repair. Although I am still trying ideas of mine and anyone elses lol.
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery
Well if the one clicks are successfully writing primary and secondary bootloaders and it's still not working, a jtag isn't going to do anything else. It almost sounds like the memory has a few corrupt blocks, but I can't say until you flash 2.3.5 BL's and see what happens
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
cbalt said:
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery
Click to expand...
Click to collapse
Oh jeez looks like the memory is failing then
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.