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
Related
Bear with me, please...still learning.
Ok, so I rooted my s3 with the root66 method and installed TWRP as my recovery. Later I tried the unofficial CM10 rom, but I had to install CWM to do so.
My question is this: are both recovery's still on my phone? It only boots into CWM. If they are, and I no longer TWRP, how do I go about removing it?
Thanks.
Sent from an overpriced Verizon tower.
knifedroid said:
Bear with me, please...still learning.
Ok, so I rooted my s3 with the root66 method and installed TWRP as my recovery. Later I tried the unofficial CM10 rom, but I had to install CWM to do so.
My question is this: are both recovery's still on my phone? It only boots into CWM. If they are, and I no longer TWRP, how do I go about removing it?
Thanks.
Sent from an overpriced Verizon tower.
Click to expand...
Click to collapse
you can only have one custom recovery installed, the other will sit as a file on your sd card and do nothing.
knifedroid said:
Bear with me, please...still learning.
Ok, so I rooted my s3 with the root66 method and installed TWRP as my recovery. Later I tried the unofficial CM10 rom, but I had to install CWM to do so.
My question is this: are both recovery's still on my phone? It only boots into CWM. If they are, and I no longer TWRP, how do I go about removing it?
Thanks.
Sent from an overpriced Verizon tower.
Click to expand...
Click to collapse
you can only have one recovery at a time, so if you ever switch to a rom that needs a different recovery than the one you have, you need to push the correct recovery, in short, yes you can only have one at a time
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?
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
volume up/home/power button is recovery try that
and you used rom manger to flash rom?
j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.
not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
confuz said:
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
Click to expand...
Click to collapse
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
CyberdyneSystems said:
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
Click to expand...
Click to collapse
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
try this thread...otherwise...you need to RMA it to asus,or the store you bought it from
http://www.scottsroms.com/showthread.php/1637-Tf300t-sku?p=13102#post13102
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
probably the bootloader, looks for a simple command,file....its not there,so its stuck in a loop
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
First declare your bootloader. Have you ever been on a jb-rom, stock or otherwise?
Looking at git for cm it appears the kernel is 2.6, so I would expect that is not a jb rom.
cwm has some issues on this unit.
get into cwm and use fastboot to flash twrp for the proper bootloader you have.
or get into fastboot by use of power and volume down
at that point you can twrp a rom into place; probably not to restore your backup as twrp and cwm have issues reading each others backups.
Good Luck!
Note: If you can power up and access recovery (cwm in your case) you are not bricked and should be able to recover. I have as well as many others. Take your time and go a step at a time! Make back ups and make sure you have fastboot and adb access to your unit! If you are still ics bootloader consider nvflash once you have this mess sorted.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Dfanzz said:
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Click to expand...
Click to collapse
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
k4killer said:
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
Click to expand...
Click to collapse
Great that ur nandroid worked! I know they r working on it... dont really have a time frame... just be on the lookout
Please Help.
was running hyperdrive rls12 on a verizon sg3.. switched to baked. after that i cant get into recovery. i went all the way back to stock. unrooted and all.than i rooted again and unlocked bootloader i can boot into odin download. i can restart phone into rom. back to stock jellybean.. but every time i try to boot into recovery it says cant boot and puts me back in odin download. i tried through buttons and through rom manager. always the same outcome. phone is usable but i cant flash any new roms if i cant get into recovery. and i always to a clean flash. any ideas
Try flashing the recovery using odin
Thanks doesn't hurt....
ramdesai said:
Try flashing the recovery using odin
Thanks doesn't hurt....
Click to expand...
Click to collapse
Damn i feel dumb. feel like a noob. thanks. dont know why i didnt think of it. do the simple first i guess. thanks again
You are welcome...Happens sometimes... Take a break and then think again..