So i installed the zip via these instructions:
Install using your existing recovery like you would any other zip.
Reboot and select TWRP from the boot menu.
There is NO boot menu and when I do a volume up menu power Teamwin pops up then it restarts and it simply doesn't frickin work at all.... wtf
The Android Market App Install Method (GooManage) worked flawlessly for me. I'd highly recommend that.
Try the Odin method as well if you can't seem to boot to your system.
So for the odin just hold volume down plug it into the pc then run the odin.exe on the pc and its that easy?
Actually, it's run Odin first. Then make sure the phone is completely powered off. (Remove battery if necessary, then put it back in.) Then press and hold the home button, down volume rocker button and power button until it takes you to download mode. Then you can plug it to the PC. Once Odin says "Added!" at the side, you're ready to upload/install (reinstall in your case) custom recovery.
I just updated my TWRP Recovery from 2.3.3.1 to 2.3.3.2 by flashing the 2.3.3.2 openrecovery zip from my 2.3.3.1 Recovery. What is your current Recovery? Go to TeamWIN website and search for appropriate recovery for your device... then download the "zip" file to your ext sd if you wish to flash via your current recovery. You can also download the "tar" and flash via Odin3.
In odin use pda option to load the default stock rom
Easy peasy
Do this http://androidromupdate.com/2012/11...y-note-2-sgh-i317-original-factory-stock-rom/
Sent from GN2 using XDA app
Yeah I put the correct zip from the twrp site the latest for the note 2 att and when the teamwin pops up it just restarts ....
Okay just flased odin 2.3.3.2 and teamwin pops up and restarts... maybe 2.3.3.2 is COMPLETELY FRICKIN Screwed ill try a different version
This is where im getting the data for my note 2 att
http://teamw.in/project/twrp2/124
What exact things DO I need to check in ODIN since I just flashed 2.3.3.1 and getting the same issue just restarts after Teamwin pops up
I FIXED IT ALL BACK TO NORMAL AND TWRP is working thanks everyone
So, what was the final solution you came up with?
Go to play store. Download goo manager.
In goo manager hit menu button and select "install openscriptrecovery" then ensure it says your device name. And if it does hit OK/yes. It will say it installed almost immediately. And you're good to go.
Sent from GN2 using XDA app
had to re-partition in odin with an sgh-i317 pit file to stock then went to stock recovery cleared data then flashed twrp odin and installed cm10 jellybeer and all is well.
New rom is looping
Rooted galaxy note 2 no problems.
Flashed criskelo rom, seemed to except and load no problem
ran all the way to end now says upgrading apps then loops
and repeats wont finish the set up.
Any suggetions?
sargexda said:
Rooted galaxy note 2 no problems.
Flashed criskelo rom, seemed to except and load no problem
ran all the way to end now says upgrading apps then loops
and repeats wont finish the set up.
Any suggetions?
Click to expand...
Click to collapse
What kind of phone do you have ? ATT i317 ?
Did you get the ROM from Samsung Galaxy Note II GT-N7100, N7105 forum?
Related
ATT Galaxy S3 stuck at boot (Guys rename the thread)
Guys,
I have a rooted AT&T Galaxy S3. While doing a nandroid recovery, I got an error and the phone was stuck on Samsung Logo. I did the following:
1. Booted into download mode
2. With ODIN I uploaded the stock rooted tar file root69.stock_ATT_I747UCALG1.tar
3. The ODIN passed just fine, however the phone would boot, AT&T logo and than stuck at small SAMSUNG screen with blue light blinking
Found the solution to my problem here:
hxxp://rootgalaxys3iii.com/galaxy-s3-stuck-at-boot
However the 1 click root with CWM installed is for i9300 on the above thread. I need a way to root my phone with ODIN and get CWM installed using AT&T image. I dont care about flash counter. Right now, its just about making my phone alive.
Please help!
http://forum.xda-developers.com/showthread.php?p=28175452
Check this thread.
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
hxxp://forum.xda-developers.com/showthread.php?p=28175452
Check this thread.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This thread didnt help. However I was able to fix my phone. Since I was not able to boot the phone, I was not able to turn on USB debugging that many softwares inluding the link you have mentioned required. So this is what I did for the benefit of those who may face this in the future:
1. Booted into the download mode vol- + power+ home key
2. When in download mode, I installed clockwork recovrey for ATT Samsung S3 which can be found at many links. I cant paste her as I dont have the rights to post links yet. But the filename was CF-SGS3-CWM-v5.5-v1.0.tar. The file I downloaded had a .tar.md5 ext, I just deleted the.md5 extension so I was left with CF-SGS3-CWM-v5.5-v1.0.tar
3. Than I used Odin and selected the above file as PDA and left everything else at default
4. The phone rebooted but again was going to go into the unending samsung logo. So shutdown the phone.
5. Than I did vol+ + home + power key and THANKFULLY booted into recovery
6. Thereone it was simple, that is restore factory defaults, wipe cache, wipe delvik cache etc etc. and boom. I am back in my phone.
Thank god, almost had a mini stroke!!!
P.S. Had lost root upon reboot. Did many things but device would keep loosing root. I went to CWM recovery and selected "fix permissions" bang.. phone back to how I used to like it rooted and booted!
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
Anyone can help me ? Thank's
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Revert back to recovery problem
hazzel said:
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
Anyone can help me ? Thank's
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Click to expand...
Click to collapse
Having same issue with SGH-T889. Any help? Heard of similar issue with Nexus 4. They have revert recovery disabler. Not tried on my Note 2. Is similar solution available for T889?
After flashing recovery in Odin are you booting up the phone (or is odin - i.e. auto reboot is checked)? There is a file (/system/etc/install-recovery.sh) that you need to disable to have recovery "stick". There are a few ways to do this, but my preference has been to do it within cwm/twrp recovery via adb after flashing in odin but prior to first bootup of phone.
Hope that helps!
Ive had luck un-checking auto-reboot in odin, flashing recovery, wait for it to say pass, unplug USB, pull battery, and boot straight into recovery by holding home + vol up when powering on.
This can be dangerous so make sure odin is completely done before unplugging.
Sent from my GT-N7105 using Tapatalk 2
^^ this
same prob
hazzel said:
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Click to expand...
Click to collapse
I have the same problem :/ i tried going back to odin and unchecking auto root as suggested, but whenever i clicked start it just stayed stuck at "Setup Connection" or whatever... i'm trying to install a custom rom and i just cant access CMW! I have the AT&T model by the way.
Nintendoassasin64 said:
I have the same problem :/ i tried going back to odin and unchecking auto root as suggested, but whenever i clicked start it just stayed stuck at "Setup Connection" or whatever... i'm trying to install a custom rom and i just cant access CMW! I have the AT&T model by the way.
Click to expand...
Click to collapse
I know you can't access CWM Recovery..
Allot of us use TWRP Recovery and it works great. I think it is safe to say it is a Superior Recovery now. I suggest you use that Recovery.
You can get it installed easily by downloading GooManager from the play store, opening the app, hit your menu button and tap Install Open Recovery Script. That's it. Quick and easy!
For the people having a hard time, are you rooted? If you are just download goomanager and use it to install twrp
Sent from my SGH-T889 using xda app-developers app
Finally got fixed
I tried by un ticking the "Reboot" in Odni and manually pulled out battery and cable and tried Recovery mode... it went smoothly as expected... thanks dude
This works when everything else fails!
dj_spore said:
Ive had luck un-checking auto-reboot in odin, flashing recovery, wait for it to say pass, unplug USB, pull battery, and boot straight into recovery by holding home + vol up when powering on.
This can be dangerous so make sure odin is completely done before unplugging.
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Been looking for a solution for hours and the android system recovery was feeling like a thorn in the foot that will never go away. But surprise, surprise, your simple suggestion did the trick!
Thanks a ton!! :good:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
I just rooted my Samsung s4 (SGH-M919) by (CF-Auto-Root method), and I have trying now to flash ''PhilZ Touch Recovery''' And I did everything, flashed this version ''philz_touch_5.18.2-jfltetmo.tar.md5'' through odin, and the phone restarted normally. Unchecked the ''auto-reboot'' in odin, and after flasing, did the manual restart to recovery (Vol. Up + Power +.Home) and still nothing..
Tried another version ''philz_touch_5.15.0-jfltetmo.tar.md5'' and still nothing happened.
What am I missing? Any help please?
Thanks.
re: recovery
D3sokA said:
I just rooted my Samsung s4 (SGH-M919) by (CF-Auto-Root method), and I have trying now to flash ''PhilZ Touch Recovery''' And I did everything, flashed this version ''philz_touch_5.18.2-jfltetmo.tar.md5'' through odin, and the phone restarted normally. Unchecked the ''auto-reboot'' in odin, and after flasing, did the manual restart to recovery (Vol. Up + Power +.Home) and still nothing..
Tried another version ''philz_touch_5.15.0-jfltetmo.tar.md5'' and still nothing happened.
What am I missing? Any help please?
Thanks.
Click to expand...
Click to collapse
You don't need to press the HOME key to get into recovery.
Just press the volumeUp and the power button at the same
time until you see tiny blue writing in the top left hand side
of the phone's screen then let go of the buttons and it should
go into recovery mode.
My suggestion is to use either TWRP or CWM recovery for best results.
Good luck!
I would first root then go into the play store and download ROM manager. After doing that install cwm through there then reboot into recovery and flash philz recovery (.zip) provided somewhere in his posts and you'll be fine. I do it every time this way.
Sent from my GT-I9505G using XDA Premium 4 mobile app
D3sokA said:
I just rooted my Samsung s4 (SGH-M919) by (CF-Auto-Root method), and I have trying now to flash ''PhilZ Touch Recovery''' And I did everything, flashed this version ''philz_touch_5.18.2-jfltetmo.tar.md5'' through odin, and the phone restarted normally. Unchecked the ''auto-reboot'' in odin, and after flasing, did the manual restart to recovery (Vol. Up + Power +.Home) and still nothing..
Tried another version ''philz_touch_5.15.0-jfltetmo.tar.md5'' and still nothing happened.
What am I missing? Any help please?
Thanks.
Click to expand...
Click to collapse
Rename the file. Just take off the .md5 at the end.
Make it just .tar at the end. It should work fine.
EDIT: Never mind. I spaced out and forgot to root before installing the recovery. Rooted, then installed recovery. Everything working fine.
Ok, I've used Odin plenty of times before, but I'm having issues getting CWM to install on my T320.
Basically, I open Odin as administrator, put the tablet in download mode and it shows up in Odin, I select PDA and select the tar.md5 CWM file. And click start. I see activity on the tablet, and it reboots after moving the file over.
Looks like everything worked. But if I reboot into recovery, it looks like the stock recovery - certainly not CWM.
Anything obvious I missed?
Jason
JasonJoel said:
EDIT: Never mind. I spaced out and forgot to root before installing the recovery. Rooted, then installed recovery. Everything working fine.
Ok, I've used Odin plenty of times before, but I'm having issues getting CWM to install on my T320.
Basically, I open Odin as administrator, put the tablet in download mode and it shows up in Odin, I select PDA and select the tar.md5 CWM file. And click start. I see activity on the tablet, and it reboots after moving the file over.
Looks like everything worked. But if I reboot into recovery, it looks like the stock recovery - certainly not CWM.
Anything obvious I missed?
Jason
Click to expand...
Click to collapse
Your prob its normal.
You must uncheck autoreboot at Odin.
If Odin says pass, you must directly boot into the flashed recovery.
If the Tab rebooted to the OS, it restore the Stock recovery.
How to boot into recovery:
Press and hold Home + Volume up and Power, if you the Samsung logo hold only Volume up and Home so long as the recovery menu starts up.
Don't forget to press the Thanks button is this helpful