My friend wanted me to root his phone. Everything went fine. Then I restarted the phone, got into CWM recovery and now it keeps bootlooping. I can't do anything because the volume keys are missing for some reason. Any ideas on how to fix this?
Try wiping cache and Dalvik in recovery.
Still not working. I think it's because I tried installing a custom ROM? Idk.
Did you do a full wipe before installing the custom ROM? You can try going back into recovery and wiping cache, Dalvik, and data.
Yup. I did all 3 of em like 5 times already. And I'm assuming there's no fix for it. I can't use the volume keys so I can't do download or safe mode.
Since the phone is still able to boot except for being able to use the volume keys, you could use a jig to get into download and flash a stock ROM via Odin as long as the phone was not running the stock 4.3 bootloader.
Where can I find a stock ROM? I've tried sam mobile but it keeps saying the file could not be found.
Search here for the i747 firmware: http://www.sammobile.com/firmwares/
Related
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
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.
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.)
I flashed a rom and then this problem started happening since. My phone tries to go to the samsung boot animation screen but never goes through it, it vibrates and then reboot, i tried installing stock rom, etc, i can now go to recovery and download mode.
You might need a jtag
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
errusdan said:
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
Click to expand...
Click to collapse
I Can install firmware through download mode.!""
Me too, i tried installing stock firmware and all that. Even i am able to use the aroma filemanager from recovery, to see all my files, and when i delete system, preload, data, cache, etc i can see that in fact the device deletes them correctly.
Sorry I miss understand, you can go in download and recovery, my bad.
Have you tried factory reset, Flash original firmware, factory reset, let it boot
What was your original firmware which file(s) did you use?
When the thing you said happened i went on the store and Luckly they replaced my phone. Your phone probably ruined thats what happens when you play with it:cyclops:
Yeah i know that there are risks when you install another roms and such. I've read that it can corrupt your internal sd card, maybe that is what happened to me? because i tried installing different firmwares, kernels, recoveries, wipe data, wipe cache, wipe dalvik cache, wipe system, wipe preload, etc, even i tried installing boot animations, and it stucks at the boot animation screen samsung galaxy, it tries to load but then it vibrates and restart like a loop.
I am now with the russian 4.4.2 rom, and yes i know that i cannot downgrade because of the bootloader version. But i tried installing modified roms with zip (like cm 11) in recovery, and it installs correctly without errors, the problem is with the bootloop.