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
Related
Hey all, I just want to say thanks in advance for any/all help!
I'm trying to install the UnNamed v2.0.1 ROM on my E4GT and it's not going so well.
I've rooted and installed CWM, installed the CRT screen off animation mod (just to check if things are working), done a Titanium Back-up, and even installed Calkulin's E4GT v2.8 ROM, but for some reason this ROM refuses to cooperate.
I rooted and installed CWM per these instructions: http://forum.xda-developers.com/showthread.php?t=1342728
I have gotten the same problem at least half a dozen times, once I hit "Reboot" from CWM after successfully installing the ROM, my phone stays stuck on the "Samsung Galaxy S II" boot up screen indefinitely.
I've tried to install from the stock EK02 ROM to the UnNamed ROM, used Rogue's Recovery (v1.1.1 if i'm not mistaken) to try to install it, and finally install it over Calkulin's ROM, all to no avail. I can recover using ODIN, but that's all that works, I can't even get to the CWM screen after I reboot my phone.
Like I said, any and all help would be appreciated! Thanks!!
P.S. I downloaded the ROM twice just in case something went wrong, still nothing.
EDIT: I've just installed the Starburst ROM over my stock EK02 without a problem, but the UnNamed ROM still fails.
Download Calk's Format_All.zip from his ROM thread. Run it 2x before installing UnNamed. I always install my kernel directly after UnNamed, before rebooting - I use EL29 by Team Rogue.
I noticed that it doesn't wipe the Dalvik Cache. Should I do that separately or leave it be?
Thanks for the help! I'll try it right now and let you know how it works
TheHighlightGuy said:
I noticed that it doesn't wipe the Dalvik Cache. Should I do that separately or leave it be?
Thanks for the help! I'll try it right now and let you know how it works
Click to expand...
Click to collapse
Go ahead and wipe that too. I usually wipe data & Dalvik manually, then format all zip, then install rom + kernel. Then reboot
nibrwr said:
Go ahead and wipe that too. I usually wipe data & Dalvik manually, then format all zip, then install rom + kernel. Then reboot
Click to expand...
Click to collapse
This is a good method to use. Good luck buddy.
Running EK02 I rooted, installed CWM for EK02, went into CWM v 5.0.2.7, installed the EL29 modem and kernel, rebooted, went back into CWM, wiped data, wiped dalvik, ran Format_ALL 2x, installed unnamed, and STILL get stuck at the "Samsung Galaxy S II" screen. WTF?
EDIT: Reading Comprehension FAIL. Let me do it again with the kernel after unnamed.
After I try and install the EL29 rogue kernel after installing the ROM I get the error:
file_getprop: failed o stat "/system/build.prop": No such file name or directory
E:Error in /emmc/Rogue_ET-Stock-1.1.4.zip
(Status 7)
Installation aborted.
Here is an md5 checksum of the ROM I'm using, if that could help.
662676707ED611FB967469841B1016E3
TheHighlightGuy said:
After I try and install the EL29 rogue kernel after installing the ROM I get the error:
file_getprop: failed o stat "/system/build.prop": No such file name or directory
E:Error in /emmc/Rogue_ET-Stock-1.1.4.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
You tried to install the kernel directly after the ROM? Not before?
If so, reboot into the ROM and let it sit. Then reboot into recovery and install.
If that doesn't work, try rebooting into recovery directly after the ROM install.
Yup, still got the same problem.
If I reboot, I get stuck on the "Samsung Galaxy S II" screen indefinitely. I can't get into recovery or anything else, I have to use ODIN.
Here's what I'm going to do to try and flash it again, step by step, let me know if anything is wrong.
1.) Flash EK02 using ODIN (after getting stuck)
2.) Root using sfhub's method
3.) REBOOT to home screen
4.) Install BootIMG + CWM for EK02 (v5.0.2.7)
5.) REBOOT to home screen
6.) REBOOT to CWM
7.) Recover to my nandroid backup
8.) REBOOT to home screen
9.) REBOOT to CWM
10.) Wipe data/factory reset
11.) Wipe Dalvik cache
12.) Install Calkulin's FLASH ALL, twice
13.) Install UnNamed's v2.0.1 ROM
14.) Install Rogue's v1.3 Kernel
15.) REBOOT to home screen.
How's that?
TheHighlightGuy said:
Yup, still got the same problem.
If I reboot, I get stuck on the "Samsung Galaxy S II" screen indefinitely. I can't get into recovery or anything else, I have to use ODIN.
Here's what I'm going to do to try and flash it again, step by step, let me know if anything is wrong.
1.) Flash EK02 using ODIN (after getting stuck)
2.) Root using sfhub's method
3.) REBOOT to home screen
4.) Install BootIMG + CWM for EK02 (v5.0.2.7)
5.) REBOOT to home screen
6.) REBOOT to CWM
7.) Recover to my nandroid backup
8.) REBOOT to home screen
9.) REBOOT to CWM
10.) Wipe data/factory reset
11.) Wipe Dalvik cache
12.) Install Calkulin's FLASH ALL, twice
13.) Install UnNamed's v2.0.1 ROM
14.) Install Rogue's v1.3 Kernel
15.) REBOOT to home screen.
How's that?
Click to expand...
Click to collapse
Just use sfhub's auto root to root and install CWM. After CWM installs reboot the phone. Then, reboot to recovery, wipe, and install UnNamed + kernel of your choice.
Good luck
Finally installed! Idk what happened differently, but it worked! Thanks!!
TheHighlightGuy said:
Finally installed! Idk what happened differently, but it worked! Thanks!!
Click to expand...
Click to collapse
Nice! Welcome to the UnNamed community
Thanks for the welcome, but I spoke too soon -_- It got past the "Samsung Galaxy S II" boot screen and played through the ICS animation, but now it's stuck on a black screen. I can't get to the home screen. Agh! I can get to CWM, but it won't get to the home screen, no matter how long I wait.
TheHighlightGuy said:
Thanks for the welcome, but I spoke too soon -_- It got past the "Samsung Galaxy S II" boot screen and played through the ICS animation, but now it's stuck on a black screen. I can't get to the home screen. Agh! I can get to CWM, but it won't get to the home screen, no matter how long I wait.
Click to expand...
Click to collapse
did you remove anything from the rom. It sounds like it does not have a home launcher chosen.
playya said:
did you remove anything from the rom. It sounds like it does not have a home launcher chosen.
Click to expand...
Click to collapse
Nope, I downloaded and installed everything as is, I didn't attempt to customize anything.
TheHighlightGuy said:
Nope, I downloaded and installed everything as is, I didn't attempt to customize anything.
Click to expand...
Click to collapse
I'm running out of ideas... maybe reflash the ROM without wiping.
I'll try that next.
I've been attempting to install from the internal SD card if that's of any help. I just got a microSD card that I'll be attempting to install from soon.
TheHighlightGuy said:
I'll try that next.
I've been attempting to install from the internal SD card if that's of any help. I just got a microSD card that I'll be attempting to install from soon.
Click to expand...
Click to collapse
Shouldn't be an issue
Was looking to make a new thread but I'll jump in for a noob question....
Right now, I'm running Calk's v.2.8.1 rom with Rogue Kernel 1.3 and modem el29. theme is team venum ICS..
If I were to stay with the exact same set up as above, except put UnNamed ROM, would it function correctly?
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
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
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.
Hi guys,
I have a Samsung Galaxy S3 I747m, running Cyanogen Mod and as of right now, it will not turn on. It will begin the boot animation and the freeze once it reaches the end. I cannot access Recovery Mode but I can access Download Mode. This all began when my version of gapps started glitching, or at least Google play Store. I downloaded a new gapps and tried to install it without wiping out the dalvik cache or uninstalling the old gapps. Yes I am a noob at this and an idiot.
Please guys if anyone of you has the patience to tell me what I need to do to get my phone operational again. please do so. My family is not doing well financially right now and can't afford another phone. Please give me some hope. Please.
Well.....I'm not expert but I can tell you its not hard bricked. So you're safe for now. I suggest checking out how to flash another OS using download mode. I believe it involves using your sd card as a "bootable media". (Like, usb stick for windows 7)
Do some research about that. And I think it should work.
Try this!
ABCordova said:
Hi guys,
I have a Samsung Galaxy S3 I747m, running Cyanogen Mod and as of right now, it will not turn on. It will begin the boot animation and the freeze once it reaches the end. I cannot access Recovery Mode but I can access Download Mode. This all began when my version of gapps started glitching, or at least Google play Store. I downloaded a new gapps and tried to install it without wiping out the dalvik cache or uninstalling the old gapps. Yes I am a noob at this and an idiot.
Please guys if anyone of you has the patience to tell me what I need to do to get my phone operational again. please do so. My family is not doing well financially right now and can't afford another phone. Please give me some hope. Please.
Click to expand...
Click to collapse
I would try and flash a new recovery image either twrp or cwm through download mode using Odin and try getting back into recovery and clean flash cyanogenmod and gapps all over again. Basically start from scratch and see if it fixes the problem, if you can get in to recovery mode after flashing a new image you may only need to wipe cache/dalvik to fix it but I'd start with trying your best to get a recovery image reflashed and the ability to get into recovery mode. You can find the images for recovery at the official sites either twrp or clockwork recovery and the instructions on how to flash them anywhere by searching through Google! Hope this helps you
From download mode you can flash a stock firmware with Odin unless you have installed the stock 4.3 update. This will wipe your phone but you will have it booting and recovery back.
NightyNineNights said:
I would try and flash a new recovery image either twrp or cwm through download mode using Odin and try getting back into recovery and clean flash cyanogenmod and gapps all over again. Basically start from scratch and see if it fixes the problem, if you can get in to recovery mode after flashing a new image you may only need to wipe cache/dalvik to fix it but I'd start with trying your best to get a recovery image reflashed and the ability to get into recovery mode. You can find the images for recovery at the official sites either twrp or clockwork recovery and the instructions on how to flash them anywhere by searching through Google! Hope this helps you
Click to expand...
Click to collapse
Thank you so much! However, in the Clockwork Mod website, it does not say anything about downloading Clockwork Recovery. What should I do from this point? Also, some people suggest installing an entirely new OS. Would this be a better or worse solution compared to flashing Clockwork Mod Recovery?
Thank you once again!
BCSC said:
From download mode you can flash a stock firmware with Odin unless you have installed the stock 4.3 update. This will wipe your phone but you will have it booting and recovery back.
Click to expand...
Click to collapse
Another user here suggested flashing Clockwork Recovery. Which one one in your opinion is the best option and what are the disadvantages/advantages of both?
ABCordova said:
Another user here suggested flashing Clockwork Recovery. Which one one in your opinion is the best option and what are the disadvantages/advantages of both?
Click to expand...
Click to collapse
As for your previous post, the Clockwork downloads are under the 'Rom Manager' tab here: http://www.clockworkmod.com/.
Twrp recovery here: http://teamw.in/project/twrp2 (Hit 'Get TWRP for your device' then this link at bottom of page 'Download - Odin Flashable Tar:').
Which you chose depends on which you had before the issue and whether you want to restore a previous backup once recovery is restored. If you are not going to be restoring a back up, I'd recommend the TWRP file as it can be flashed with Odin.
Your other option is to Flash a stock firmware from Odin and start from scratch. This can be the more labor intensive way because you then need to setup the phone again and get it back to how you like it. The benefit of this method is that it wipes absolutely everything, including whatever problem had you screwed in the first place. Because I tinker with my phone a lot, I always have everything important stored on an external SD. Pictures, Titanium Backup, Nandroid, etc. If you have backups of everything you need off the phone, I'd recommend that you Odin it. If you do not have things backed up try installing recovery first and getting the phone to boot. In the end if you do chose this method you should still wipe as there was obviously something that really buggered your phone and a wipe will be the best way to fix that so it doesn't recur. That's my opinion anyway.
Update!
Apparently I can access Recovery Mode now!! However, it still does not boot up. I backed up all my filed to my external 8GB SD card, and then wiped the dalvik Cache. Nothing. I did a full Factory reset and still nothing. AM I missing a step? Is there a step I should take before or after clicking full wipe? The phone boots all the way to cyanogen mod logo, where an arrow spins around it. However, that's all it does.
Any ideas?
ABCordova said:
Apparently I can access Recovery Mode now!! However, it still does not boot up. I backed up all my filed to my external 8GB SD card, and then wiped the dalvik Cache. Nothing. I did a full Factory reset and still nothing. AM I missing a step? Is there a step I should take before or after clicking full wipe? The phone boots all the way to cyanogen mod logo, where an arrow spins around it. However, that's all it does.
Any ideas?
Click to expand...
Click to collapse
So you can access recovery mode?
*Before you follow the next steps, understand everything will be deleted from your PHONE, NOT sdcard.*
You have to wipe everything clean. That means(in recovery mode):
Wipe Data/factory reset
Wipe cache partition
Wipe dalvik cache
Then you would install your rom. From there everything should work. Also, are you installing CM10.2? 10.1? 11? (I personally suggest 10.2.)