Was running a restore via CWM this morning, but there was nothing happening for a good 20 minutes, restoring from Darkstar to Calkulins (GB), so I left the phone alone for a while. An hour later, says is restoring data (no progress bar) and so after another minute, I rebooted the device. Of course, now I only get a blue LED(nothing on screen) and I cannot seem to get into ODIN mode or recovery. Any ideas?
Its bricked. You need to jtag or take it to sprint.Have you read what everybody is saying?.....if you want to restore gingerbread use odin first
shiftr182 said:
Its bricked. You need to jtag or take it to sprint.Have you read what everybody is saying?.....if you want to restore gingerbread use odin first
Click to expand...
Click to collapse
Sure as **** did not. I have a buddy at the sprint store I guess I need to see.
have u tryed using a usb jig
Sorry man, same thing happened to mine a week ago.
sergioperalta81 said:
have u tryed using a usb jig
Click to expand...
Click to collapse
What's that?
Its a little usb thing that you plug into your phone, it is supposed to put it in download mode/reset your odin counter automatically. I used it on mine when it bricked and it did nothing.
what shiftr said, im goin through this right now, sprint employee might say the screen is dead and make u wait a bit...
T.C.P said:
what shiftr said, im goin through this right now, sprint employee might say the screen is dead and make u wait a bit...
Click to expand...
Click to collapse
So you are getting a replacement T.C.P?
Sent from my Nexus S 4G using xda premium
Have we come to any consensus on what is causing these bricks? It seems to happen often when using CWM to restore between ICS and GB. Or is it something else entirely? I've always just used Odin and haven't had any issues yet.
OP. Could you provide a little more information on your setup? Specifically ...
1) The recovery (specific version) you were using at the time you made your GB Nandroid backup
2) The method you used to flash Darkstar, and how you obtained custom recovery after flashing it and the version of said recovery
3) The recovery (specific version) you tried to use to restore your GB Nandroid backup
We need to find out what is corrupting the data partition and making it un-usable and un-repartitionable (yeah I made up a word).
ajs2677 said:
Have we come to any consensus on what is causing these bricks? It seems to happen often when using CWM to restore between ICS and GB. Or is it something else entirely? I've always just used Odin and haven't had any issues yet.
Click to expand...
Click to collapse
from what I've read, it sounds like its either people coming from ics to gb like you said, or (and I'm really not sure on this one) they are trying to restore a backup from a different kind of recovery and there is being an incompatability at some point. Like restoring a backup made in rogue recovery in cwm recovery. I really don't know though and I'm kinda scared to test it as you can imagine.
Sent from my SPH-D710 using xda premium
Dchibro said:
OP. Could you provide a little more information on your setup? Specifically ...
1) The recovery (specific version) you were using at the time you made your GB Nandroid backup
2) The method you used to flash Darkstar, and how you obtained custom recovery after flashing it and the version of said recovery
3) The recovery (specific version) you tried to use to restore your GB Nandroid backup
We need to find out what is corrupting the data partition and making it un-usable and un-repartitionable (yeah I made up a word).
Click to expand...
Click to collapse
1) CWM Touch 5.8.1.5
2) CWM 5.0.2.7 (sensing a variable)
3) CWM Touch 5.8.1.5
I started with darkstar this morning, from calkulin's via cwm 5.0.2.7, then did a flash from rom manager, via cwm, to cwm touch. From there, without rebooting, I backed my ROM and attempted to reflash to calkulin's via cwm touch. That's when things went icky.
thebenshow said:
1) CWM Touch 5.8.1.5
2) CWM 5.0.2.7 (sensing a variable)
3) CWM Touch 5.8.1.5
Click to expand...
Click to collapse
So touch recovery is involved yet again. I'm assuming this was Koush's CWM Touch recovery, and not Team Rogue's version? If it was Koush's recovery, did you download it and flash it or did you install it via ROM manager?
---------- Post added at 09:17 AM ---------- Previous post was at 09:14 AM ----------
thebenshow said:
I started with darkstar this morning, from calkulin's via cwm 5.0.2.7, then did a flash from rom manager, via cwm, to cwm touch. From there, without rebooting, I backed my ROM and attempted to reflash to calkulin's via cwm touch. That's when things went icky.
Click to expand...
Click to collapse
Okay ... VERY VERY VERY likely that this was your issue.
Lesson learned I guess, but this info is all over the place here on XDA. DO NOT use ROM Manager to flash CWM Touch. In fact, do not use ROM Manager at all, and I'd go further and say avoid any Touch Recovery for now. If if you insist on using Touch Recovery, use Steady Hawkins' version (although I believe he took the link down until this gets sorted out).
Don't know what the issue with the recovery and restore is but I've been dealing with galaxy s phones from all different carriers since they came out and its impossible to brick them. Like the other guy in the thread stated you need a USB jib. You plug it into your phones micro USB port and it automatically puts it in download mode and then you can use ODIN to flash what you want.
Sent from my ADR6300 using xda premium
Better still, my sprint guy said he'd just swap it.
droidboy29 said:
Don't know what the issue with the recovery and restore is but I've been dealing with galaxy s phones from all different carriers since they came out and its impossible to brick them. Like the other guy in the thread stated you need a USB jib. You plug it into your phones micro USB port and it automatically puts it in download mode and then you can use ODIN to flash what you want.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
That's the problem. People are getting stuck at an in between point where Odin won't complete as well.
Sent from my Nexus S 4G using xda premium
droidboy29 said:
Don't know what the issue with the recovery and restore is but I've been dealing with galaxy s phones from all different carriers since they came out and its impossible to brick them. Like the other guy in the thread stated you need a USB jib. You plug it into your phones micro USB port and it automatically puts it in download mode and then you can use ODIN to flash what you want.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Not in this case man. I know it defies all previous knowledge, but this problem is stopping even Odin from being able to re-partition and write to /data.
When using ics 3.0 kernel to flash or restore you have a good chance of a brick .....Odin back before restore ....please read people
And don't use cwm touch
Sent from my SPH-D710 using xda premium
Related
My phone was constantly rebooting so i went into CWM and did a factory reset and it froze while wiping and since then it wouldnt reboot. I went to this thread http://forum.xda-developers.com/showthread.php?t=1551901&page=11 and followed the directions for the one click recovery using odin 1.81 but it stopped updating on the data.img. I kept it connected for over an hour. I disconnected the cable and rebooted the phone. now when i turn it on it says "firmware upgrade encountered an issue please select recovery mode in kies and try again" i tried holding power and volume down and it briefly boots up but then goes to the firmware upgrade screen. Kies isnt recognizing the phone as being connected. Any help would be greatly appreciated!
you are not the first one today (yesterday) reporting the same problem. There were about 3~4 incidents reported during today. So, don't go further at this time. I hope some more Devs joining to give more helps.
During the time you are waiting, read the almost same case -
http://forum.xda-developers.com/showthread.php?t=1554392
http://forum.xda-developers.com/showthread.php?t=1549382
Also, please describe the full details about what you did and how you did -
where did not download the rom, what's your rom/kernel version before installing the rom, how did you proceed to odin the rom, etc...
You mentioned that you tried to flash the rom using the one click recovery using odin 1.81. Can you please be more details about this?
Before flashing the rom, you said that your phone was constantly rebooting. What was your rom and kernel at that time? Do you think there was anything suspicious causing the rebooting?
Maybe the solution would be simple but I saw many people reported same thing, there would be common issue in here. So, we need to find out what that is....
Sorry for not giving you the suggestion at this time.
This isn't an ODIN issue. ODIN is just the messenger in this case.
There is a problem between the ICS kernels and custom recovery where it will sometimes corrupt your /data partition if you reset/wipe/restore/format/etc. Any large partition operations are suspect. Copying files seems fine. It doesn't necessarily do it every time so it'll work for some but brick others. Even if it works a couple of times, it can brick at any time.
The EMMC memory actually becomes damaged and even JTAG repair will not fix. By the time you get to ODIN the damage is already done. ODIN won't be able to write to /data even using a .pit file with repartition set, ODIN one-click won't write to it, CWM will hang writing to it, JTAG will have issues also.
Your best bet is to get a replacement.
There are multiple threads about this, which is why people suggest you go back to a GB-based kernel+CWM to do your ROM flashing.
This is one thread where the data.img corruption is discussed:
http://forum.xda-developers.com/showthread.php?t=1504808
Well i tried QBKings how to unbrick video and used the stock el29 stock rom through odin. It looks like it was going to work. it finished all the way but now it just gets stuck in a boot screen loop
i get update logfile does not exist deleteing cryption meta data
#manual mode#
updating application....
Maybe try using odin to flash a kernel with recovery, and get into recovery before it reboots(or pull battery since it won't boot after odin is done doing its thing). then restore a nandroid, or flash a Rom?
Sent from my SPH-D710 using xda premium
(Duplicate post - person above asked already)
sleshepic said:
Maybe try using odin to flash a kernel with recovery, and get into recovery before it reboots(or pull battery since it won't boot after odin is done doing its thing). then restore a nandroid, or flash a Rom?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I think we are in synch - http://forum.xda-developers.com/showthread.php?t=1556609 (the suggestion that I provided).
Adding to this, I personally recommend to format the sdcard before installing anythig - there's a option to format sdcard.
sleshepic said:
Maybe try using odin to flash a kernel with recovery, and get into recovery before it reboots(or pull battery since it won't boot after odin is done doing its thing). then restore a nandroid, or flash a Rom?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Well i managed to be able to get it to boot into rogue recovery or power + down so i can flash through odin. I tried flashing a rom but it cant get past formatting system.
im going to try to restore to a previous rom now
armandosal said:
Well i managed to be able to get it to boot into rogue recovery or power + down so i can flash through odin. I tried flashing a rom but it cant get past formatting system.
im going to try to restore to a previous rom now
Click to expand...
Click to collapse
It will never get past the data its corrupted and bricked ... There is no fixing it you should have never done anything in cwm with a ics kernel there are multiple threads that well tell you that ...read read ....you will now hope that sprint will replace your phone or you have insurance...good luck with sprint
Read this thread its what is wrong with your phone
http://forum.xda-developers.com/showthread.php?t=1504808
Sent from my SPH-D710 using xda premium
I'll add on to Epix4G's comment with another link:
How Not To Brick Your E4GT
I finally ended up getting another phone from my insurance company. Is there a way to get any of my data from the phone?
Sent from my SPH-D710 using XDA
armandosal said:
I finally ended up getting another phone from my insurance company. Is there a way to get any of my data from the phone?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Nope once it's data partition is screwed it's done for and not recoverable
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Ok. Thanks. on the plus side I got Cyanogenmod 9 on my phone.
Sent from my SPH-D710 using xda premium
Hi i used the wrong recovery to backup my Samsung epic touch and now all I get is a blue light it won't start or boot to recovery or odin any help will be appreceiated. I'm using EL26 kernal to flash ICS roms I went to cwm touch recovery instead of rouge recovery and now I'm stuck.
I do also have the FE02 plus recovery I forgot to mention that with having all my stress.
Sounds like another hard brick... Your only small hope would be in a usb jig and then a jtag service, but both might fail and you now have an expensive paperweight.
Sent from my SPH-D710 using Tapatalk 2
Try the manual method to get into download mode (copied from sfhub's TAR posts):
Code:
Method #1
Power down phone
Wait for capacitative button lights to turn off
Simultaneously Press and Hold [Power] [VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode
Without getting into download mode you're probably a victim of the eMMC lockup. But to know for sure, what kernel version were you on when you last tried a CWM restore or wipe?
I was using EL26 kernal. I should have booted into recovery manually but I used rom manager it booted me into cwm touch instead of rouge recovery. I was going to flash a new ICS rom so I wiped everything and formated system and when I pressed reboot recovery, and rather then just going back it froze so I waited a bit then pulled the battery that's when it wouldn't do anything except the blue light.
I used the e4gtauto file to flash FE02+recovery. Which I understand is the one you need if you are flashing ICS roms but i used cwm touch before I realized it was the wrong recovery it was to late.
BTW it won't go into download mode
bigdaddy619 said:
I was using EL26 kernal. I should have booted into recovery manually but I used rom manager it booted me into cwm touch instead of rouge recovery. I was going to flash a new ICS rom so I wiped everything and formated system and when I pressed reboot recovery, and rather then just going back it froze so I waited a bit then pulled the battery that's when it wouldn't do anything except the blue light.
Click to expand...
Click to collapse
OK, the behavior - specifically that the phone froze and wouldn't respond until you pulled the battery - matches the eMMC lockup. Unfortunately yours appears to be locking up during the boot process which is why you can't get to download mode. Only way to fix is to take to Sprint for replacement.
Still curious how you did it though - and let's try our best to find it so that others don't suffer the same fate:
bigdaddy619 said:
I used the e4gtauto file to flash FE02+recovery. Which I understand is the one you need if you are flashing ICS roms but i used cwm touch before I realized it was the wrong recovery it was to late.
Click to expand...
Click to collapse
Can you link to the post containing the file you used to flash? I'm not aware of an FE02 build - maybe Agat's FF02 repack? And can you also include source of CWM touch if from a different ROM?
Sounds like he used CWM Touch on an ICS build. It flashed the recovery through rom manager, but the recovery isnt built correctly for our phones. Its a hard brick and will need to get a replacement. YOU HAVE TO USE A GINGERBREAD RECOVERY FOR IT TO WORK RIGHT
shiftr182 said:
Sounds like he used CWM Touch on an ICS build. It flashed the recovery through rom manager, but the recovery isnt built correctly for our phones. Its a hard brick and will need to get a replacement. YOU HAVE TO USE A GINGERBREAD RECOVERY FOR IT TO WORK RIGHT
Click to expand...
Click to collapse
Yea even then he stated fe02? Isnt that an ics kernal and also used touch which neither is good for flashing a new rom.. either way people make mistakes and like said already you have a nice paperweight.. to sprint you must go lol
Sent from my SPH-D710 using XDA
http://forum.xda-developers.com/showthread.php?t=1342728 this the link where i got the e4gtauto.
If you want CWM use Option C in the Auto Root Package to install EL26+CWM (you are already rooted so Option A is not necessary)
OOOOOPS it was the FD02+recovery sorry
bigdaddy619 said:
OOOOOPS it was the FD02+recovery sorry
Click to expand...
Click to collapse
There's your culprit. Once you get it replaced you'll want to stick with GB or FF02 repack which was done with care to avoid triggering the lockup for now. Sorry you had to find out this way...
Sent from my SPH-D710 using XDA
Close please
Sent from my MB855 using xda app-developers app
where did you find cmw touch?
I've been looking all over for it!
emottau said:
I've been looking all over for it!
Click to expand...
Click to collapse
Looking for what?
Sent from my MB855 using xda app-developers app
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
SysAdmNj said:
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
Click to expand...
Click to collapse
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
U have to make sure u are rooted first.
Sent from the TermiNOTEr!
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
SysAdmNj said:
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
Click to expand...
Click to collapse
Yes. CWM and ported ROM. Everything works well I just want TWRP. But I guess I'll do with CWM. If it aint broke then why fix it. It works I guess. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium
Check your build prop for device name. Maybe its not correct because of the Rom you're on. Whats the error you're getting?
Did you ever get TWRP on your phone?
I've had goofy issues with TWRP but much prefer it to CWM. Originally rooted using CWM and SuperSu and switched to TWRP when I flashed CleanRom several times via Romtoolbox pro I've flashed updated Twrp it said it was successful but when it rebooted was soft bricked! Had to use Odin and original CWM to get back in and re-install everything (nandroids were twrp backups) found file downloaded to sdcard that worked fine! Odd...
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
wargear said:
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
Click to expand...
Click to collapse
If by "installed" you are referring to the recovery program itself (and not your backups), you can only have one recovery 'installed' at one time as there is only 1 "Recovery" partition on the device (/dev/block/mmcblk0p9). So if you want to install CWM instead of your current TWRP (or visa-versa), either flash the appropriate new recovery zip via your current recovery... or Odin3 flash your desired new recovery tar. Either way, it will write to the same recovery partition. If you are referring to your backups... these are stored in the designated path you selected (either internal sd or external sd)... in the TWRP/BACKUPS folder. In that folder, you will have a device id #... in that folder are your backups.
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
wargear said:
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
Click to expand...
Click to collapse
Which version of Odin3 are you using? When I used Odin3 v1.85 I would get the "PASSED" but with Odin3 v3.07, I also only got "RESET" (on an WindowsXP box)... but both flashed it correctly (and auto rebooted after flash)
Galaxy Note2 TOOLKIT V3.0.0 ATT]
I tried the [Galaxy Note2 TOOLKIT V3.0.0 ATT] http://forum.xda-developers.com/showthread.php?t=2052779 out of curiosity sake. Worked for me installing TWRP 2.3.2.3 without a hitch. Great tool from what I can see, and that's just one of it's many features. Great for simplifying things for new Android users just entering the customizing scene and regulars alike. Big ups to mskip for making this available. I can foresee myself grabbing the donate version here real soon.
And to get yourself SIM unlocked, get yourself back to 4.1.1 and give this a whirl.http://forum.xda-developers.com/showthread.php?t=2014982 Bought my device used, was supposedly unlocked, wasn't. Even came with an unlock code that the previous owner purchased. Firstly it's a no go on 4.1.2, secondly still didn't work when I dropped back to 4.1.1. But this http://forum.xda-developers.com/showthread.php?t=2014982 will set you free. Big thanks owl74 for posting. Once again XDA forums saves my hair from being pulled out.
Hello everyone, this is my first post. I am not a complete noob I had a Motorola Triumph I flashed dozens of roms and never bricked it or anything. I have an epic 4g touch, of course, and it was running the Blu Kuban rom , I think 1.5.1 or something, the one beofre the latest update. So i wanted to try the 'Jellyverse" fk23 since I loved the ICS Universe rom, great battery life, better than the kubans. I flashed the rom first with the recovery the blu kuban had, and then I dont know why i flashed an acs fk23 recovery, I didnt read the instructions right, dont know what i did there. Phone boots, and stays on welcome screen, nothing more.
Yes, I have tried Odin, phone isn't recognized. Have tried two pcs, reinstalling drivers, 3 different usb cables, and odin cant recognize it.
or the pc for that matter.Phone does get in android system recovery 3e, and does read sd card.tried flashing ff18 update and get signature not valid etc. Forgot to mention the usb port may be defective cause it did get wet with milk a bit the other day, i dired it but left it on most of that day anyway, but it still charges.
What can i do? I went to best buy but I am scared they will notice what happened, the welcome screen is obviously jellybean...
How can i save this phone? adb, fatboot? Sorry I am a noob when it comes to these things i Just mentioned. And sorry in advance if this was posted somewhere else. I am really grateful to all epic 4g touch devs, they make awesome roms. I know its my fault, etc, I just want to know if theres anyway i can revert to stock anything or get it working, or if i have to jtag it, or I will just have to travel 2 hours to visit my sister who works at best buy and ask her to play dumb that the phone is rooted and replace it with the best buy insurnace i have.
did you make a nandroid backup before you flashed?
brandan14 said:
did you make a nandroid backup before you flashed?
Click to expand...
Click to collapse
NO, stupidly, i didnt. With that have worked even with the stock android recovery?
All I did was backup my apps with titanium pro.
WIth the E4GT I have never done nandroid as I never had any problems, with the Motorola Triumph I used to though...
Read... read... read!
Your best chance is to flash the recommended recovery kernel via Odin then reflash the ROM.
Sent from my SPH-D710 using xda premium
Mattix724 said:
Read... read... read!
Your best chance is to flash the recommended recovery kernel via Odin then reflash the ROM.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thats the thing I cant use Odin. Phone isn't recogized when before it used to be recognized.
Can you get it in download mode?
Sent from my SPH-D710 using xda premium
yea I think a nandroid would work on stock recovery I've personally never have tried it. if you could get it into download mode it should recognize it.
brandan14 said:
yea I think a nandroid would work on stock recovery I've personally never have tried it. if you could get it into download mode it should recognize it.
Click to expand...
Click to collapse
No odin doesnt recognize the phone, and yes it goes into download mode thats how I know Odin cant recognize it.have tried 3 pcs and usb cables.
Are you plugging in the phone after you open Odin?
Sent from my SPH-D710 using xda premium
Mattix724 said:
Are you plugging in the phone after you open Odin?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
maybe i have tired both ways, i dont know. which is the correct way?
I usually plug the USB in after I have Odin up and ready to flash. Sometimes it just doesn't show the COM port when you have it plugged in before.
Sent from my SPH-D710 using xda premium
Mattix724 said:
I usually plug the USB in after I have Odin up and ready to flash. Sometimes it just doesn't show the COM port when you have it plugged in before.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
yea that's what I do. and I would just try going into recovery and see if there is a backup you can restore.
Is there anyway I can restore a nandroid with stock recovery (3e it says), and can it be from another e4gt? ANy of you have one I can use? Sorry if its noob question. or anyway i can save this phone without odin or a custom recovery? Can I flash a kernel on stock recovery?
brandan14 said:
yea that's what I do. and I would just try going into recovery and see if there is a backup you can restore.
Click to expand...
Click to collapse
I didnt make a backup....arghh im screwed.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Use Mobile Odin....Flash EL26 found here https://www.dropbox.com/s/f83s6y8wsnzqjau/EL26_StockCWM.tar.md5 (I will link to original in a little bit) ...Then reboot phone into custom recovery (power button and vol up until phone reboots)...Ohh wait, your stuck in a bootloop?? You're definitely going to need to utilize Odin on the PC to get out of it
Edit: Follow the instructions here.....Have you tried a One-Click odin? If your PC won't recognize the phone...restart everything. Try a different USB port, make sure your drivers are installed. I can't think of any other troubleshooting steps.....Maybe a different computer?
Hello,
So I've been rooted for a while now, i was going to install a custom rom but decided not to a few months ago. Tonight, i decided to install aokp, however my phone would not go into cwm, only stock recover. I could have sworn it was installed, but fine, so i installed it once again with auto reboot in odin checked, and it still wouldnt enter cwm. I then tried to install it again with auto reboot checked off so i could see if i could enter it without the reboot. I ended up getting into it, but then when i was taking a NANDROID, it just froze on one of the first steps. Fine, reboot, try to enter cwm again. Nope, just stock android recovery. I am sure im installing it correctly and pressing the right button combos. I am at a total loss for what is stopping me from being able to enter cwm. I hope you guys know/help me find whats going on.
Thanks!!!
Zay
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
pcshano said:
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
Click to expand...
Click to collapse
Yes my phones rooted.
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Zay48 said:
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Click to expand...
Click to collapse
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
pcshano said:
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
Click to expand...
Click to collapse
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
if you still want cwm then i guess you can try flash stock rom and root it again and see
since you're going to flash a custom rom which will delete all your data anyways
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Zay48 said:
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Click to expand...
Click to collapse
Bump
what version of CWM are you currently running?
you could always try to download GooManager or ROM Manager from the Play Store.
then from one of those, install the custom recovery, GooManager for TWRP or ROM Manager for CWM.
xBeerdroiDx said:
what version of CWM are you currently running?
Click to expand...
Click to collapse
3.0.7
Zay48 said:
3.0.7
Click to expand...
Click to collapse
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
zetsui said:
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
Click to expand...
Click to collapse
He's not having a problem restoring images, he's having a problem making his first nandroid.
Sent from my SGH-I747 using xda app-developers app
Zay48 said:
3.0.7
Click to expand...
Click to collapse
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
RPelham said:
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Download rom manager and update your cwm and then try making a nandroid again.
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
That said... If you insist in CWM, this is the guide I followed to get a successful CWM flash. (This was the CWM I was running successfully for the brief time TWRP disbanded.)
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
The above is for the ATT variant only. If you have a different variant and can't find the link, post back and I'll find it for you
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
apparently it's still around because new android users who want to root use those guides with outdated files
RPelham said:
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Preach brother!