I have the Sprint S3 with 4.1.2. Last night I rooted it and it worked fine. I then flashed CWM Recovery and rebooted, all was fine. Tried to put on Liquid Smooth rom and didn't have gapps, attempted to flash gapps but came up with error. Got fed up with it and tried to flash the Synergy Rom. I cleared dalvik and cache, made a backup and flashed. Went through the whole process and auto rebooted afterwards. Went to SAMSUNG on boot and screen went black before finishing and will not go further. I can get into stock recovery but not CWM Recovery. I'd like to have the liquidsmooth rom on there but i also downloaded the stock 4.1.2 rom just in case. How can I get past this to get into either CWM recovery or somehow flash a rom from Odin? I'm stuck.
jsaye2002 said:
I have the Sprint S3 with 4.1.2. Last night I rooted it and it worked fine. I then flashed CWM Recovery and rebooted, all was fine. Tried to put on Liquid Smooth rom and didn't have gapps, attempted to flash gapps but came up with error. Got fed up with it and tried to flash the Synergy Rom. I cleared dalvik and cache, made a backup and flashed. Went through the whole process and auto rebooted afterwards. Went to SAMSUNG on boot and screen went black before finishing and will not go further. I can get into stock recovery but not CWM Recovery. I'd like to have the liquidsmooth rom on there but i also downloaded the stock 4.1.2 rom just in case. How can I get past this to get into either CWM recovery or somehow flash a rom from Odin? I'm stuck.
Click to expand...
Click to collapse
So you were able to get into the custom recovery (CWM) a couple of times before flashing Synergy Rom, but now it's reverted to stock recovery? When you turn your phone off and hold Volume up, menu, and power it boots into the stock recovery? I've never heard of that happening before.
The best way is to re-do your root process through Odin a-la qbking77's tutorial. This will install CWM again and then you can flash away. Make sure you check your md5sums on the Rom files you downloaded before flashing them. That's the most common cause of bad flashes around these parts.
topherk said:
So you were able to get into the custom recovery (CWM) a couple of times before flashing Synergy Rom, but now it's reverted to stock recovery? When you turn your phone off and hold Volume up, menu, and power it boots into the stock recovery? I've never heard of that happening before.
The best way is to re-do your root process through Odin a-la qbking77's tutorial. This will install CWM again and then you can flash away. Make sure you check your md5sums on the Rom files you downloaded before flashing them. That's the most common cause of bad flashes around these parts.
Click to expand...
Click to collapse
I've ended up fixing it but had to flash stock 4.1.1 on it from Odin and then it automatically went to 4.1.2 after reboot. Thanks
But yes, it was going to CWM just fine before I flashed Synergy after Liquidsmooth. Thats how I put on Synergy. But at least it was just a soft-brick.
Did you wipe (everything) between flashes? Even roms of the same version can have issues if you flash one over the other
By everything I mean /system, /data (factory reset), dalvik cache, and cache
Related
Hey guys,
I was installing the synergy rom r484 onto my galaxy s3 att variant and in the aroma installer it says that my device is d2spr but my device is actually d2att and I think that is why when I install the synergy rom it doesn't let me use my data and 4g. Can anyone help with this?
update your recovery with a d2att one. are you cwm or twrp?
I'm using cwm. Can you please guide me how to update the recovery to the d2att one? haha sorry I'm kind of a noob
let's see if this gets you straightened out. flash this in recovery, go to advanced and select reboot recovery. once back in, give synergy a shot again. do you know what version you're on now and where you got your current cwm from? just curious
xBeerdroiDx said:
let's see if this gets you straightened out. flash this in recovery, go to advanced and select reboot recovery. once back in, give synergy a shot again. do you know what version you're on now and where you got your current cwm from? just curious
Click to expand...
Click to collapse
When I tried to flash that file it started and then said "Installation aborted"
I've attached a picture
Oh and I'm not sure what version I'm running
can you boot into your device? if so, use Rom Manager to update your recovery.
if not, here is the previous version of CWM if you want to see if this takes care of you.
also, twrp is recommended for aroma installers. i'll attach a recovery flashable twrp zip. let me know if either flashes. if not, you may have to restore a backup (if you cant boot in now) and update your recovery that way.
xBeerdroiDx said:
can you boot into your device? if so, use Rom Manager to update your recovery.
if not, here is the previous version of CWM if you want to see if this takes care of you.
also, twrp is recommended for aroma installers. i'll attach a recovery flashable twrp zip. let me know if either flashes. if not, you may have to restore a backup (if you cant boot in now) and update your recovery that way.
Click to expand...
Click to collapse
I flashed the twrp.zip and then I tried installing synergy again and it finished and started rebooting and now it's in a continuous loop of rebooting
get it fixed?
if not, wipe cache and dalvik in recovery and reboot. if you're still looping, boot into recovery and wipe data/factory reset and reboot. report back, buddy
xBeerdroiDx said:
get it fixed?
if not, wipe cache and dalvik in recovery and reboot. if you're still looping, boot into recovery and wipe data/factory reset and reboot. report back, buddy
Click to expand...
Click to collapse
I've tried rebooting into recovery multiple times but it goes to the Team Win recovery screen and then goes back into the boot loop :crying:
odin back to stock, buddy. thats what i would do.
here's a link to the stock firmware with root already injected: http://forum.xda-developers.com/show....php?t=1739426
flash the tar in odin. make sure the auto reboot box is unticked. if you get a PASS after flashing, unplug the device, pull the battery, replace it and press the recovery button combo. once in recovery, wipe data and wipe cache. reboot.
you will be on rooted stock. you can install cwm or twrp from rom manager or goo manager from there.
otherwise, your other option is to flash recovery from odin via this link: http://forum.xda-developers.com/showthread.php?t=2042775
download the root kit and flash the recovery.tar from odin. boot into recovery and flash that cwm 6.0.3.1 update i linked you to earlier. reboot recovery (under advanced) and proceed with flashing synergy or flash this recovery-flashable stock rom to get you started. you can decide where you want to go from there.
xBeerdroiDx said:
odin back to stock, buddy. thats what i would do.
here's a link to the stock firmware with root already injected: http://forum.xda-developers.com/show....php?t=1739426
flash the tar in odin. make sure the auto reboot box is unticked. if you get a PASS after flashing, unplug the device, pull the battery, replace it and press the recovery button combo. once in recovery, wipe data and wipe cache. reboot.
you will be on rooted stock. you can install cwm or twrp from rom manager or goo manager from there.
otherwise, your other option is to flash recovery from odin via this link: http://forum.xda-developers.com/showthread.php?t=2042775
download the root kit and flash the recovery.tar from odin. boot into recovery and flash that cwm 6.0.3.1 update i linked you to earlier. reboot recovery (under advanced) and proceed with flashing synergy or flash this recovery-flashable stock rom to get you started. you can decide where you want to go from there.
Click to expand...
Click to collapse
If I odin back to stock will it delete all my music and pictures and etc.?
Okay I'll try the second thing and I'll report back in a bit. Thank you so much for taking the time to help me.
Okay so I got that recovery that you gave me earlier installed (the cwm 6.0.1.3) after using odin and the att gs3 root and then flashing after that. Then when I went back into recovery and tried to install the synergy rom it started and then the aroma installer froze and my phone went back into the loop. I can get into recovery now though but I don't know how I should install synergy
Honestly? This is a picky rom. I would abandon it for a more stable install and operational rom, whether that be a touchwiz base or aosp. It doesn't seem to be working with you at all.
Okay I installed the cyanogen mod stable build and now I'm just waiting for it to finish booting up. Thank you so much for all your help!!!
That's what we're all here for. Lemme know if that did/didn't boot up for ya :good:
Okay it's still at the same booting screen where it says CyanogenMod and the blue circle is spinning around it.
Wipe data/factory reset, wipe cache and dalvik. Reflash rom and gapps. Wipe data and cache again. Reboot and give it a few minutes.
That's my suggestion.
Routed by Galaxy S3
xBeerdroiDx said:
Wipe data/factory reset, wipe cache and dalvik. Reflash rom and gapps. Wipe data and cache again. Reboot and give it a few minutes.
That's my suggestion.
Click to expand...
Click to collapse
My Galaxy at&t phone had the same problem after flashing with Synergy (my first flash on my new Galaxy S3 phone). It lost its identity and though it was a Sprint phone. Next I tried installing a different custom ROM, but I couldn't install CM10.1 (and still can't now) because it thinks it was not a d2att.
There were only two ROMs I was able to do installed since then. They were the Serenity 1.2 and its predecessor. I had to restored phone back to stock, root, and flash ROM. For a while, it was pretty grim as my phone had gotten very unresponsive and lethargic with all the fixes I tried during the time my phone thought it was a d2sp (no data).
After going back to stock using Odin, the phone finally could accessed the data network again and showing SGH-I747 instead of the Sprint version. I tried flashing CM10.1, but it still didn't think it is a d2att since it aborted when it did the check for d2att.
Nest, I flashed the DrewGaren's JellyBean747 version 1. Then I flashed DrewGaren's Serenity 1.2. Both were mostly working OK, but there are still some bugs.
Unfortunately, the DrewGaren's series seem to be dead projects since he didn't seem to be doing anymore improvement since Jan 2013.
Samsung S3 had me routed. My previous phone was HTC Inspired, and I rooted it instead of it routing me
Hi
I was flashing back to Stock from task650 to fix my gps. Well something blew up and when the phone reboots the screen goes black but I hear the AT&T start-up tune. Essentially I can't get to enable USB debugging to reflash. I can get to download or recovery, but there are no files to recover<?> and busybox never got installed.
What do I do now?
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
CZ Eddie said:
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
Click to expand...
Click to collapse
Yes I have stock recovery. Odin is of no use because it hangs waiting for the USB debug to respond. And i can't turn it on because the screen is black and I can't navigate
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
xBeerdroiDx said:
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
Click to expand...
Click to collapse
Thanks. I created an emergency tool kit on an SD, I wiped data, wiped cache and Davlik and formated system. Flashed the stock rom. When I rebooted it now hung at the Samsung Galaxy S III screen.
How do I get out of this mess?
Try wiping data and cache again in recovery
xBeerdroiDx said:
Try wiping data and cache again in recovery
Click to expand...
Click to collapse
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
BertMor said:
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
Click to expand...
Click to collapse
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
xBeerdroiDx said:
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
Click to expand...
Click to collapse
When it rains it pours. Now I can't get into recovery. I get the empty battery graphic cycling on and off, and its very warm to the touch. I think the battery is not charging.
I tried using Odin and flashed a stock rom but I kept getting verification errors and status 7 errors. Things just are not taking. I fear I've got a hard brick and I don't know what to do to fix it.
I appreciate your help
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
xBeerdroiDx said:
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
Click to expand...
Click to collapse
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
it might indeed be drained. leave it plugged in for a while and report back.
you were getting the error/status 7 messages after you flashed cwm back on it likely because the cwm wasnt up-to-date.
what was the last thing you tried before it stopped working altogether?
It gets really hot if I leave it plugged in. But it seems like I can get into recovery again. The last thing I flashed was CMW 6.0.3.1. But what is on it now is CMW 5.5.0.4
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
BertMor said:
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
Click to expand...
Click to collapse
xBeerdroiDx said:
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
Click to expand...
Click to collapse
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
BertMor said:
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
Click to expand...
Click to collapse
Well I think I managed it!. First I tried to install an update d/l'ed from Dropbox and that did nothing. Then I flashed an old .tar that was a rooted stock and it rebooted!
I tried editing the updater-script but I couldn't getit to save the changes properly.
Well I will now re flash the RM and CWM and hope for the best
Thanks for all your help, greatly appreciated
I rooted my phone, downloaded the jedi mind trick rom and attempted to flash it. I deleted and format my phone in CWM and i installed the rom from an internal sdcard. Now it keeps resetting and wont turn on. What should I do now?
Have you tried jamison's cache wipe?
Sent from my HTC One using xda app-developers app
Im downloading the stock telus rom in an attempt just to start from the beginning. When I flash it I'll get back to you. I was rushing when I rooted it the first time I guess.
Okay so I've done that and have rooted it using the s2 toolkit. what steps should I take to ensure the jedi mind trick rom can be successfully flashed?
Okay I tried reflashing it again... Didn't work, I have the same problem. I did the factory settings, and wiped the cache and flashed the rom. I then went into advanced and cleared the Devac (sp) cache and fixed permissions. I rebooted and it didn't work. It starts, gets to about the loading circle graphic and just resets
I used Darkside super wipe and it worked for me...
ive done it like this.
flashed original stock rom via odin
Root via S2 toolkit
flash cmw with toolkit as above
and flash custom rom via s2 toolkit
and after that used darkside superwipe
thanks for the tip, I tried the darkside wipe but it still is happening.
I have the same exact thing. But for me it's different. It started with the PACman 22.0.1. Whenever I press the power button to turn on/off the screen, it would restart a couple of seconds later being stuck in an infinite reboot loop. Can't get into recovery mode (used TWRP 2.3.3.1 and 2.5). I somehow managed to revert back to stock which worked properly. Rooted and installed PACman 22.1.1 ROM and it's still stuck on a reboot loop.
I don't know if it's a hardware problem (wiring off power button to the circuit is damaged) or a software code that messed up the machine code in the circuit.
i had the same when i installed wrong kernel and radio...try it like this..instal stock
http://forum.xda-developers.com/showthread.php?t=1513359
and then try cwm recovery version from the s2 toolkit (try non touch ver.)
and then try flashing
try doing a factory reset, wipe cache and install rom. don't wipe cache or anything after that until after it boots. btw don't use cwm wipe cache, try the one that is stickied in development forum.
my s2 was being glitchy so i went into recovery to wipe cache and dalvik and then rebooted from recovery. i waited and then it just boooot loops and shuts off. im currently using cwm recovery 5.2.7 or something like that. will i be able to flash the newer roms like CyanogenMod 10.2 with that current recovery? and why did the wiping of cache and dalvik booot looped my phone? i thought wiping those just makes my phone less glitchy
You probably had some other issues to cause phone to be glitchy in the first place.
When flashing a new ROM it's recommend you wipe data, system cache and dalvik cache.(cache and dalvik can be wipe after the ROM install before rebooting)
nooob 4 ever said:
im currently using cwm recovery 5.2.7 or something like that. will i be able to flash the newer roms like CyanogenMod 10.2 with that current recovery?
Click to expand...
Click to collapse
No, you are going to have to update to either the newest TWRP or CWM to flash 4.3 ROMs.
I'm gonna jump in and hope this isn't a hijack. I had a similar experience but I wanted to update to the latest TWRP so I could flash a 4.3 ROM (Simbean) .
I Odined in and flashed TWRP 2.6.3. Was able to flash the Slimbean ROM but on first reboot I can't make it past the Samsung screen.
I can get back into TWRP but everything fails. - typical process. "Fix permissions- Success", then "Full wipe - Success" then "Fix permissions (cause I'm trying anything at this point)- Failed"
In TWRP Restoring backups "Failed" Flashing new image "Failed" In between I've tried Erasing everything but the MicroSD card and starting fresh but Noting will install.
I've reflashed TWRP through ODIN but same issue. A couple of times I've got a restore to work but if the phone sleeps it won't wake up. I can only get back to TWRP.
What is the Nuclear Option? Or have I done that already? I've been flashing for years. I've never seen anything like this.
Help.
pairustwo said:
In TWRP Restoring backups "Failed" Flashing new image "Failed" In between I've tried Erasing everything but the MicroSD card and starting fresh but Noting will install.
I've reflashed TWRP through ODIN but same issue. A couple of times I've got a restore to work but if the phone sleeps it won't wake up. I can only get back to TWRP.
What is the Nuclear Option? Or have I done that already? I've been flashing for years. I've never seen anything like this.
Help.
Click to expand...
Click to collapse
Some people have problems with 2.6.3.0. Try to Odin 2.6.1.0 and see if it helps.
http://techerrata.com/browse/twrp2/hercules
help
so what are my options to fix my phone with the current cwm 5.0.27?
nooob 4 ever said:
so what are my options to fix my phone with the current cwm 5.0.27?
Click to expand...
Click to collapse
i can get into cwm and thats it
nooob 4 ever said:
i can get into cwm and thats it
Click to expand...
Click to collapse
Nothing, that recovery is good for 4.1.2 and lower, of u want newer roms u can go to my beanstalk thread or @ThdDude's hellybean thread and the new recoveries are posted...
Sent from a soup'd up Herc while climbing a giant beanstalk to crazy heights.....
what I did is to hold the power button/ remove the battery of your phone. Open it again and wait for it to start. no bootloop.
I have a T-Mobile SGH-T989 (Galaxy S2), and for a while I had an ICS darkside ROM on it with CWM 5.0.2.4. This evening, though, I decided to upgrade to an Android KitKat ROM (Beanstalk). I first upgraded CWM to the latest version, and then flashed the ROM. Everything seems to have flashed correctly, and I get the Beanstalk splashscreen, but it never seems to go any further than that. It's hung (for around 30mins) on the Beanstalk splash screen with the beanstalk and rain.
When I go into CWM, I can re-flash just fine, but when I try to do a full wipe or a cache wipe, it also gets hung (I eventually rebooted after about a 10 minute cache wipe attempt). It says that it can't open /cache/recovery/last_install, and that the cache file system is read-only. I also attempted to use the super wipe/cache wipe tools here: http://forum.xda-developers.com/showthread.php?t=2235141&nocache=1 but they also hung.
I'm wondering what the best course of action is at this point? I have a full backup, but since it was made with the previous version of CWM, it also appears to not be working.
Thanks,
~j
jwir3 said:
I have a T-Mobile SGH-T989 (Galaxy S2), and for a while I had an ICS darkside ROM on it with CWM 5.0.2.4. This evening, though, I decided to upgrade to an Android KitKat ROM (Beanstalk). I first upgraded CWM to the latest version, and then flashed the ROM. Everything seems to have flashed correctly, and I get the Beanstalk splashscreen, but it never seems to go any further than that. It's hung (for around 30mins) on the Beanstalk splash screen with the beanstalk and rain.
When I go into CWM, I can re-flash just fine, but when I try to do a full wipe or a cache wipe, it also gets hung (I eventually rebooted after about a 10 minute cache wipe attempt). It says that it can't open /cache/recovery/last_install, and that the cache file system is read-only. I also attempted to use the super wipe/cache wipe tools here: http://forum.xda-developers.com/showthread.php?t=2235141&nocache=1 but they also hung.
I'm wondering what the best course of action is at this point? I have a full backup, but since it was made with the previous version of CWM, it also appears to not be working.
Thanks,
~j
Click to expand...
Click to collapse
When all fails always use ODIN, if you know what you're doing. IDK which ROMs here are flashable via ODIN but use any you can find in the dev section in which somebody has uploaded a flashable .tar version (usually it will be rooted stock). If that doesn't save you, you have big trouble.
Also you should still be able to restore backups between different CWM versions, so yeah there is potentially something wrong with your phone.