So I was rooted on synergy r72 then went to jellybean...tried flashing back to clean rom and s*it hit the fan...I ended up Odin back to stock and started from square 1...unlocked and rooted I made a nandroid and tried to flash clean rom once again...it installed but when it got to the boot animation it looked strange and the screen where it said Samsung had a bunch of different colors and then it rebooted...battery pulls didn't work...restored my root66 from Odin but can't flash any new roms! Any ideas what is going on!?!? I would greatly appreciate the help!
Did you check the md5 hash of the file you downloaded? Either way try downloading it again and check the hash.
Brian Gove said:
Did you check the md5 hash of the file you downloaded? Either way try downloading it again and check the hash.
Click to expand...
Click to collapse
Yes... I haven't done anything differently from when it worked prior to this
Sent from my SCH-I535 using xda app-developers app
So heres an update...I flashed back to root 66 in odin and everything is normal...when I go to flash a rom in CWM it goes into bootloop and i have to restore my back up...What do I do ?
Did you try downloading the file again? It could have corrupted. Just a thought. Make sure your bootloader is still unlocked(You can tell because it will boot by the first 'Samsung' screen in a split second then go onto the 'Samsung Galaxy SIII' screen.). And before you flash cleanrom wipe everything, data, cache, davlik. Run the fix permissions too just to be sure.
pschatz12 said:
So heres an update...I flashed back to root 66 in odin and everything is normal...when I go to flash a rom in CWM it goes into bootloop and i have to restore my back up...What do I do ?
Click to expand...
Click to collapse
I think your boot loader is relocked when you flash factory stock. Try to flashed back to root 66, then do unlock..the rest should be straight forward.
buhohitr said:
I think your boot loader is relocked when you flash factory stock. Try to flashed back to root 66, then do unlock..the rest should be straight forward.
Click to expand...
Click to collapse
This. If you ODIN back to stock, you need to unlock again.
I have odined back to stock, unlocked, made a nandroid & tried to flash clean rom...I got it flashed but it bootlooped and i had to do 3-5 battery pulls and let it sit for a while in between pulls...I then flashed the kernel and had to do the same thing...then i tried to flash dirty tweeks and then it sat and bootlooped again...Any time i try and flash a rom it does the same thing...Do you guys think that something is wrong with the internal storage and the phone is defective now? Should I get it back to factory stock and try and return it to verizon?
pschatz12 said:
I have odined back to stock, unlocked, made a nandroid & tried to flash clean rom...I got it flashed but it bootlooped and i had to do 3-5 battery pulls and let it sit for a while in between pulls...I then flashed the kernel and had to do the same thing...then i tried to flash dirty tweeks and then it sat and bootlooped again...Any time i try and flash a rom it does the same thing...Do you guys think that something is wrong with the internal storage and the phone is defective now? Should I get it back to factory stock and try and return it to verizon?
Click to expand...
Click to collapse
Please list the steps you took step by step so we can see what's going on here. Don't embellish, don't exaggerate, tell us what you did and what you didn't do. Based on your steps you shouldn't be bootlooping. I would follow droidstyle's guide step by step in each category that is relevant (going back to stock, unlocking, flashing ROMs, etc.). Follow each step closely in whatever ROM you're flashing as well. Don't take shortcuts.
You sure you're unlocked? Maybe try unlocking again. It doesn't seem to bother anything if unlock an unlocked phone. If that makes sense...
+1 to listing your exact steps to help troubleshoot.
mustbepbs said:
This. If you ODIN back to stock, you need to unlock again.
Click to expand...
Click to collapse
Using Odin to go back to stock does not re lock the boot loader.
Unlocking it again doesn't hurt as was just mentioned.
@OP are you sure you're using the correct variant? You are on Verizon and do not have one of the developer phones, etc?
Brian Gove said:
Using Odin to go back to stock does not re lock the boot loader.
Unlocking it again doesn't hurt as was just mentioned.
@OP are you sure you're using the correct variant? You are on Verizon and do not have one of the developer phones, etc?
Click to expand...
Click to collapse
I swore that it did. Are you sure?
http://forum.xda-developers.com/showthread.php?t=1842830 - Yes it does. It rewrites the aboot.img to the secure one.
Positive, I tested it out and that's why droidstyles guide has changed.
I odined back to stock...unlocked...made nandroid...tried to flash clean Rom...it worked...flashed the clean kernel...went into bootloop...restores backup...copied synergy r72 to sd and installed with everything working perfect...I came from synergy 72 before I tried to get to clean Rom...when synergy gets installed does it do anything special in the installation process?
Sent from my SCH-I535 using xda app-developers app
Boot loop sounds like a kernel issue. Are you sure you're not using a TW kernel on AOSP, etc?
Also have you tried redownloading the files that are giving you problems? Try redownloading the kernel to see if that makes a difference. If you're successful in flashing ROMs then I think a fresh download might fix your issue.
pschatz12 said:
I odined back to stock...unlocked...made nandroid...tried to flash clean Rom...it worked...flashed the clean kernel...went into bootloop...restores backup...copied synergy r72 to sd and installed with everything working perfect...I came from synergy 72 before I tried to get to clean Rom...when synergy gets installed does it do anything special in the installation process?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
When you install synergy it installs a custom kernel. It used to detect if you are unlocked before the kernel was flashed but later versions assume you are unlocked. Watch the text as you flash in CWM and see if it gives you any error message or if ziggy's kernel was flashed successfully.
Thats a wired problem I would try going back to the stock rooted image again
Wontfinishlast said:
When you install synergy it installs a custom kernel. It used to detect if you are unlocked before the kernel was flashed but later versions assume you are unlocked. Watch the text as you flash in CWM and see if it gives you any error message or if ziggy's kernel was flashed successfully.
Click to expand...
Click to collapse
Ziggys kernel was flashed successfully and synergy r72 running successfully... Do you guys think I should try dirty flashing clean rom? Idk what else to try... From synergy I can do a full wipe and try install clean rom but I doubt it will work
Sent from my SCH-I535 using xda app-developers app
cleanrom doesn't come with their own kernel baked into it already??? Why would they make you flash the ROM then the kernel..... And if you're getting the bootloop after installing the kernel then it's as mustbepbs said, re-download the kernel file.
Related
I rooted my Nexus S 4G and was running MIUI but decided to go back to the stock ROM for awhile. When attempting to go back over to MIUI, I can no longer get into Recovery and now the stock ROM won't boot either, stuck on loading animation.
I'm on a Mac, is there anything I can do? Thanks
redsprocket said:
I rooted my Nexus S 4G and was running MIUI but decided to go back to the stock ROM for awhile. When attempting to go back over to MIUI, I can no longer get into Recovery and now the stock ROM won't boot either, stuck on loading animation.
I'm on a Mac, is there anything I can do? Thanks
Click to expand...
Click to collapse
Boot into boot loader. Use fastboot to flash a recovery. Reinstall your rom of choice.
Thanks, I was able to get Recovery working again and after trying a few things was able to get back into my ROM, but I'm still not able to flash back and forth different ROMs. Seems my root isn't sticking with this method:
http://forum.xda-developers.com/showthread.php?t=970237
The root file on there is for ecalir/froyo only. Go into rm>download rom> superuser and download "superuser 2.3.6.3 efgh" and that should work.
Sent from my Nexus S 4G using xda premium
redsprocket said:
Thanks, I was able to get Recovery working again and after trying a few things was able to get back into my ROM, but I'm still not able to flash back and forth different ROMs. Seems my root isn't sticking with this method:
http://forum.xda-developers.com/showthread.php?t=970237
Click to expand...
Click to collapse
did you wipe data(factory reset) before flashing different roms? you have to. you dont need to wipe data only when updating the same rom.
Ahhh, that must be my problem. I got so used to not wiping on MIUI that I assumed I could jump between ROMs without wiping. Thank you and apologies for the remedial posts.
redsprocket said:
Ahhh, that must be my problem. I got so used to not wiping on MIUI that I assumed I could jump between ROMs without wiping. Thank you and apologies for the remedial posts.
Click to expand...
Click to collapse
no apologies needed, thats why we're here
So I used to run the CM7 rom, then upgraded to a ISC WIP. Well, it was pretty unstable, and wanted a stable rom, so tried restoring my old CM7 backup, and now when I turn on my phone, it shows the HTC splash screen, the goes black (screen still on), and won't go past that. I realize now I downgraded the firmware, and you can't do that.
My buddy said I need to get some toolkit and reset EVERYTHING back to stock roms, re-root and all that. So can some generous person link to all that? I see a lot of it in the Inspire 4G forums, but want to make sure I have it all. And after I flash all the stock stuff, can I restore that CM7 backup (clockwork recovery mod)?
Thanks in advance for the help/reply, much appreciated.
If you can get into hboot, this may help you:
http://forum.xda-developers.com/showthread.php?t=1396229
pazzo02 said:
If you can get into hboot, this may help you:
http://forum.xda-developers.com/showthread.php?t=1396229
Click to expand...
Click to collapse
That's what I was looking at, wasn't 100% sure if it's the right tut for me. Thanks for the reply!
Do I need to reinstall recovery, or flash the stock rom?
Oathdynasty said:
Do I need to reinstall recovery, or flash the stock rom?
Click to expand...
Click to collapse
You should follow the steps to reinstall recovery, then go to flashing a rom. You only need to go through the "flashing a stock rom" section if you had problems reinstalling recovery. Just read through all the steps and you'll get it.
Oathdynasty said:
Do I need to reinstall recovery, or flash the stock rom?
Click to expand...
Click to collapse
If you are S-OFF you just can flash a new recovery image and then flash any rom you want. You will have to do it from command prompt...
if you need help in doing that, just let me know...
glevitan said:
If you are S-OFF you just can flash a new recovery image and then flash any rom you want. You will have to do it from command prompt...
if you need help in doing that, just let me know...
Click to expand...
Click to collapse
I could use some help haha. I tried downloading the stock rom (PD98IMG.zip) from multiupload, but it'd down, and the mirror says it'll take several hours.
Oathdynasty said:
I could use some help haha. I tried downloading the stock rom (PD98IMG.zip) from multiupload, but it'd down, and the mirror says it'll take several hours.
Click to expand...
Click to collapse
Look in the second post in that thread. The OP noted last month that there were probs with multiupload and posted an alternate dl.
pazzo02 said:
Look in the second post in that thread. The OP noted last month that there were probs with multiupload and posted an alternate dl.
Click to expand...
Click to collapse
I got it. I went on the cyanogenmod irc, and they helped me. I didn't have to flash anything stock, I rebooted into my bootloader, went into recovery, wiped system, data, dalvik, cache.... All that, flashed cm7 and restored
Sent from my Desire HD using Tapatalk
Good. Glad you got it fixed
Oathdynasty said:
I got it. I went on the cyanogenmod irc, and they helped me. I didn't have to flash anything stock, I rebooted into my bootloader, went into recovery, wiped system, data, dalvik, cache.... All that, flashed cm7 and restored
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Glad you got it sorted out, To be honest that is the first thing you do when a rom wont boot. Whenever you restore a backup it is best to wipe first
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
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
confusedman112 said:
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
Click to expand...
Click to collapse
What methode did you use to unlock it? I'm running the stock no nonsense rom and I belive unlocked with no problems
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
lazarus2405 said:
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
Click to expand...
Click to collapse
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
Click to expand...
Click to collapse
Install EZ-Recovery from the play store and flash 6.0.1.0?
PJnc284 said:
Install EZ-Recovery from the play store and flash 6.0.1.0?
Click to expand...
Click to collapse
Thanks. Flashing Synergy now to test it...let's see what happens.
EDIT: Flashed just great, but still isn't working. But, it's cool, CM10 mods work and I got what I needed (exported Verizon contacts and improted them to Google Contacts using My Verizon's webstie)
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x.
Click to expand...
Click to collapse
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
lazarus2405 said:
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
Click to expand...
Click to collapse
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
droidstyle said:
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
Click to expand...
Click to collapse
Because I am at work and don't have time to find and locate? Could you reference it, please?
PJnc284 said:
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
Click to expand...
Click to collapse
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
newuser134 said:
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
Click to expand...
Click to collapse
Just to be safe. Wanted to get rid of the sprint related elements from the original root so I Odin'd back to stock with cwm installed using the VRALF2 tar found here. Tried to boot into recovery to factory reset prior to first boot and had 0 recovery (not stock nor cwm). Luckily the rom booted and I used the simple root method to root and install EZ-Recovery to install CWM.
If I flashed synergy v1.7 and used rom manager v5.x.x and then unlocked the boot loader how would I flash a new rom? Do I have to use ez recovery with clockwork mod v6.x.x since it is now unlocked or can I continue using rom manager with clockwork mod 5.x.x. I'm a noob and won't be looking to switch roms until synergy gets jellybean. Thanks for the help and hopefully I made sense with my question
synergy to beans to synergy bootloop
I think my issue might be related to the issues stated above.
So after after having unlocked my bootloader with EZ unlock & installing beans custom Rom via TWRP , I decided to go back to synergy. I made a nandroid of my synergy which was origianlly installed with CWM and figured I could just wipe and restore that with TWRP. Total bootloop.
OK, so I pulled the battery, tried it again...bootloop.
SO I pulled the battery, wiped and installed the synergy zip thinking I could try a fresh install. I got a message in TWRP that E:sd-ext was not found, but wipe seemed to happen so I continued the process.
installation said it was successful but now when I try to boot up, I either get stuck in the android is upgrading applications (looping over and over) or it gets through there and tells me all teh com.android.xxxx applications unexpectedly stop.
is this a soft brick? can I recover from this? are there incompatibilities between the kernels of bean's custom rom and synergy for verizon samsung galaxy s3?