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!)
Related
I have a Samsung Galaxy Nexus GSM and have been trying to install the Paranoid Android flavor custom ROM, I had 2.22 installed not long ago but managed to screw it up when I updated it without clearing my security settings (I had a 4x4 pattern swipe which I couldn't enter with the update which restored it to 3x3 pattern) so I wiped and restored to stock 4.2. I'm now trying to re-install with any custom ROM but it's not working.
Whenever I install a ROM it seems to install ok but when I get to the boot screen it just hangs on the nexus/PA logo.
I've tried with:
Goo Manager
TWRP 2.2
TWRP 2.3
CWM 6.0.1.5
and with
PA 2.22
PA 2.99.1
PA 2.99.5
PA 2.99.6
PA 2.99.7
and I always get the same error, I've tried wiping all options within TWRP and CWM and going from there but that doesn't seem to work, the strange thing for me though is that if I re-install a stock Google ROM it works perfectly fine.
I'm fairly new so please be gentle.
flash the latest twrp and move the rom and gapps to your sdcard then follow this..
1. factory reset
2. wipe system
3. wipe cache
4. wipe dalvik
5. flash rom
6. flash gapps
7. reboot
if it still freezes at boot animation pull battery reboot to recovery wipe cache/dalvik and reboot
Thanks for the suggestion but that didn't work.
Any other suggestions?
When you say TWRP 2.3 do you mean 2.3.2.1? http://teamw.in/project/twrp2/90
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
zephiK said:
When you say TWRP 2.3 do you mean 2.3.2.1?
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
Click to expand...
Click to collapse
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Using TWRP, wiping cache, dalvik, and system should wipe everything except the sdcard contents. So doing these wipes should make your phone "bare stock" again as you described
Why don't you try downloading another custom ROM or download the same ROM again because maybe it is corrupted or something
osiris231 said:
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Click to expand...
Click to collapse
RANT: huh..... seriously? you couldn't have browsed around, searching for this COMMON issue (which usually comes down to user "error"), read the STICKIES, before posting?
first, internal storage = /data/media aka /storage/sdcard0/ aka /sdcard/
Please read all of this
http://forum.xda-developers.com/showthread.php?t=1626895
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Copy the ROM to your device (some storage folder)
Boot directly to TWRP
Manually install the ROM and the appropriate GAPPS
(watch the script window and see what it says.. look for errors)
Clear caches and dalvik
reboot
LuckyColdJohnson said:
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Click to expand...
Click to collapse
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
I think its my recovery Twrp. I changed something.
adam_wingert said:
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
Click to expand...
Click to collapse
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
LuckyColdJohnson said:
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
Click to expand...
Click to collapse
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
What have I done ?
Android The Greek said:
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
LuckyColdJohnson said:
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
Click to expand...
Click to collapse
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
I figured it out!!!!!!!
Doggydude said:
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
Click to expand...
Click to collapse
It was the settings in TWRP. One of the boxes was checked. Sim actions for theming. I unchecked that and was on my way. Rocking The Collective AoCP now !!!!! Yes.....Thanks to all of you for your input. I'm going back to each and will hit thanks right now! Thanks again XDA members.
Lucky
I'm glad things worked out... isn't it amazing how attached we get to our toys
Sent from my GT-N7105 using Tapatalk 2
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.)
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
redheadplantguy said:
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
Click to expand...
Click to collapse
most stable version would be 2.6.3.3
buhohitr said:
most stable version would be 2.6.3.3
Click to expand...
Click to collapse
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
redheadplantguy said:
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
Click to expand...
Click to collapse
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
buhohitr said:
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
Click to expand...
Click to collapse
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
redheadplantguy said:
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
Click to expand...
Click to collapse
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
buhohitr said:
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
Click to expand...
Click to collapse
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
redheadplantguy said:
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
Click to expand...
Click to collapse
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Hi,
This post saved me, I installed TWRP 2.8 and my system froze, I couldn't get past the Samsung 10.1 screen.
But found this post and flashed 2.6.3.3 via Odin and it all went smoothly.
PS Goo.img.com dosen't have the files anymore
buhohitr said:
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Click to expand...
Click to collapse
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
redheadplantguy said:
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
Click to expand...
Click to collapse
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Is 2.6.3.3 more reliable / stable in terms of making / restoring nandroids? I just got my new Note last week (p607t) and flashed xKat with TWRP at one point, restoring apps from (some with data to avoid re-entering account info or redoing complex settings...) I have had one problem however, when I was almost done restoring, I noticed that I was getting fc's, particularly with games that required an internet connection. I wiped dalvik and cache in TWRP, then hit fix permissions, which I think screwed everything up (maybe due to the bootloader / firmware base mismatch). Anyway, my most recent nandroid was with the fresh xKat install, but fixing permissions caused this weird "hot"-bootloop where it skipped the boot animation but start loading immediately after rebooting, but then freezing before all boot tasks had completed (ex. some optimizations on boot with Android Tuner Pro, FolderMount mounting folders, loading xposed modules...)
Not wanting to re-restore, I first just tried dirty-flashing the ROM again (only wiped dalvik and cache, but did something I hadn't tried before: in the wipe menu I hit "repair partition" for system and data, pre-flash). Luckily it worked and set everything straight... but just want to make sure, 2.6.3.3 is still recommended as the most stable version (in my experience, fixing permissions in recovery can be very hit or miss on any version)?
2 questions before I roll back my recovery, I think these "killer features" (totally serious, #2 has been huge since I got a couple of the newish flash drives with micro usb on one side and regular usb on the other) of TWRP were implemented in 2.6.3.3, but just want to make sure: can you 1) compress nandroids and 2) mount a USB OTG drive and flash from or backup to it? Thanks all, really loving my new Note (massive upgrade from my Note 8!)
buhohitr said:
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Click to expand...
Click to collapse
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
redheadplantguy said:
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
Click to expand...
Click to collapse
How about wipe cache/davikcache/data with your stock recovery (just reflash your stock recovery). After that let it boot up, then power down and flash twrp. Once done, don't boot up, boot back to twrp . Let me know how it goes.
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
redheadplantguy said:
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
Click to expand...
Click to collapse
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
buhohitr said:
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
Click to expand...
Click to collapse
THANK YOU SO MUCH! TWRP booted right up, and nandroid in progress. now I'll be able to try some custom ROM's and play in system.
:laugh: