Related
Hello,
My Galaxy Nexus went in to a boot loop for some reason on it's own, it's been working fine for the last few months (I'm on AOKP b24) but today during the middle of the day it just rebooted and then went in to a boot loop. No matter what I do, I can't get it to boot up without hard wiping it. I've pulled the battery for a while, charged it up etc but it's still stuck in the boot loop.
I can still get in to CWM, so that's the good news.
The BAD NEWS is that I don't know how pull my Titianium Backup files from the phone. I'm trying to use the Galaxy Nexus Toolkit, but when I go to option 15 to pull the files, it asks me if I'm running a custom ROM. I answer yes and then it asks me for a path. I've tried entering these: /sdcard, /sdcard/, /mnt/sdcard/titaniumbackup, /mnt/sdcard/titaniumbackup/ etc. but no matter what I enter, it gives me an error saying I'm not running an insecure boot image.
How can I pull down my nandroid backups from the phone so that I can wipe it and then get my data back? Please help..
have you tried clearing the cache partition and delvik cache? lots of bootloops can be fixed by just doing this.
if you have a nandroid backup theres no need to wipe anything before doing the restore.
Nandroid's won't restore? The correct path is: /sdcard/TitaniumBackup/ but if the toolkit is giving you no love I'd try it via adb.
adb pull /sdcard/TitaniumBackup/
For nandroids: adb pull /sdcard/clockworkmod/backup/
BUT
If you do a wipe data/factory reset your backup folders aren't lost, so a completely fresh ROM install won't affect your existing b/u's as long as you don't format your sd card.
neotekz said:
have you tried clearing the cache partition and delvik cache? lots of bootloops can be fixed by just doing this.
if you have a nandroid backup theres no need to wipe anything before doing the restore.
Click to expand...
Click to collapse
Yep, tried wiping cache and dalvik a few times, no dice. I also tried a nandroid restore from CWM but it errors out and doesn't restore..
CMNein said:
Nandroid's won't restore? The correct path is: /sdcard/TitaniumBackup/ but if the toolkit is giving you no love I'd try it via adb.
adb pull /sdcard/TitaniumBackup/
For nandroids: adb pull /sdcard/clockworkmod/backup/
BUT
If you do a wipe data/factory reset your backup folders aren't lost, so a completely fresh ROM install won't affect your existing b/u's as long as you don't format your sd card.
Click to expand...
Click to collapse
Thank you. I managed to get the files pulled, just had to manually kill adb and restart it and then I could pull the files.
Now I have also done a factory reset through CWM and the flashed the same ROM again, it's still in a boot loop!!
I'm at a complete loss.. what else can I try?
Could a part of the internal memory be corrupted or something like that?
was the phone a yakju build? if so you can use fastboot or the toolkit to flash them, this will flash the stock bootloader, recovery, kernel and system image.
https://developers.google.com/android/nexus/images#yakju
neotekz said:
was the phone a yakju build? if so you can use fastboot or the toolkit to flash them, this will flash the stock bootloader, recovery, kernel and system image.
https://developers.google.com/android/nexus/images#yakju
Click to expand...
Click to collapse
Thanks, that's exactly what I just did and it worked. No more bootloop! Phone booted up and I'm now in process of flashing my old rom and then hopefully restoring the nandroid.
I have no idea what caused all this after months of stable operation, but at least the phone is alive now..
Thanks all!
Is there a way to pull files/photos from a boot looping phone that's unrooted? :-/
lKoRTy said:
Is there a way to pull files/photos from a boot looping phone that's unrooted? :-/
Click to expand...
Click to collapse
Install the Galaxy nexus Toolkit (search for this on xda), then get it connected to your phone by following instructions in the tool.
Then select the option to pull files and give it the right path, which should be \sdcard\DCIM\Camera\.
This will pull the files to your computer where the Toolkit is installed.
Hope this helps!
the7thson said:
Install the Galaxy nexus Toolkit (search for this on xda), then get it connected to your phone by following instructions in the tool.
Then select the option to pull files and give it the right path, which should be \sdcard\DCIM\Camera\.
This will pull the files to your computer where the Toolkit is installed.
Hope this helps!
Click to expand...
Click to collapse
For some reason while reading about toolkit last night I gathered that it wouldn't work.. Perhaps I was wrong so this morning went ahead and did a reset to factory :-/
Thanks for the suggestions - I will definitely look into it if it occurs again. If it does, I will be posting a video on YouTube of burning it down
Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you
Try the cache clean up after the nandroid is restored.
Also try to install some other compatible kernel (if it's stock it should be also to find on the forums) after the restore with its modules if the cache clean up doesn't help.
Sent from my HTC One X using Tapatalk 2
Wipe the cache and dalvik cache again.
shadehh said:
Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you
Click to expand...
Click to collapse
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat
Thanks for the help guys. I mentioned all the suggestions on this thread to him and it he was able to get it running
Sent from my HTC One X using xda app-developers app
bradmax57 said:
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat
Click to expand...
Click to collapse
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong
squirrelbo1 said:
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong
Click to expand...
Click to collapse
The file shouldn't be on the phone, but on the PC.
Place it in the folder in which you have your fastboot files.
oh of course. I'm being a moron again.
I cant believe I did that. so very very simple. sorry for being a numpty guys. wasn't thinking strait. Done a few custom rom installs but never flashed a backup. Didnt even think. You even have to type the directory into command prompt.sorry guys I can't believe I didn't think that. (was thinking along the lines of installing from zip way)
to be fair the only reason I'm doing all this is because my screen is playing up and I need to return it so getting everything as close to stock as possible so got other things on my mind
everything is working now. Thanks guys. My god stock rom on HTC one x from orange is ugly.
No worries mate. You're not a moron, just a beginner.
TToivanen said:
No worries mate. You're not a moron, just a beginner.
Click to expand...
Click to collapse
thanks heaps for the thread guys, this has been a great help as I'm doing a similar thing and had the same problem.
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
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.)
Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!
dallinrigby said:
Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!
Click to expand...
Click to collapse
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
I have already tried to clear the cache and the dalvik and then did a reboot but it didn't change anything.
shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
I was running the stock jellybean before I installed cryogenmod...my phone is a galaxy s3 it47 (AT&T) network unlocked phone. Also, at the bottom in recovery mode it says
ClockworkMod Recovery v6. 0. 4. 5
I'm not sure whether or not this is important but it is the only thing that I can think of to tell you about my phone.
I don't care whether we keep my data, I just want it to be able to turn on! Can I just restore it using Odin somehow? I tried the wipe user memory option in recovery mode and that didn't help...
Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.
shortydoggg said:
Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.
Click to expand...
Click to collapse
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?
dallinrigby said:
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?
Click to expand...
Click to collapse
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Go to http://download.cyanogenmod.org/?device=d2att&type=
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Go here and download 10.2: http://wiki.cyanogenmod.org/w/Google_Apps and put it on your SD card with the above .zip.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.
ChinDaChin said:
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.
Click to expand...
Click to collapse
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
It says on that second link to download Torrent or via It Vends, is this the right place, and if so what do I pick?
Thanks by the way, also is there a way I could do this with Odin?
dallinrigby said:
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
Click to expand...
Click to collapse
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).
ChinDaChin said:
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).
Click to expand...
Click to collapse
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Do i need to unzip it?
dallinrigby said:
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Click to expand...
Click to collapse
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)
ChinDaChin said:
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)
Click to expand...
Click to collapse
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Where do i get TWRP? It doesn't say that I have Clockwork anymore, since I factory reset it
dallinrigby said:
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?
Click to expand...
Click to collapse
Sorry.
I'm kind of conflicted on what's going on with your phone. It is partially a problem with going through Rom Manager to flash cyanogenmod.
audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I guess you can try TWRP. I haven't used TWRP so I can't comment on it. I'll try finding an explanatory video that is simple to follow. (Don't throw out Cm10.2, or the gapps. You will need those to get Cyanogenmod on your phone!)