Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Have you tried twrp?
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
this could happen when you didn't root it properly
anyways, if you are rooted(as you said), get twrp and see
+1 for twrp
athens71 said:
I still have root.
Click to expand...
Click to collapse
If you still have root, you might want to try installing CWM directly from your phone, using the dd terminal command to copy CWM into the right partition:
Download the latest CWM .img file from CWM's site: http://www.clockworkmod.com/rommanager
Put the file in your phone. For simplicity reason, I would suggest you put it in the root of your internal SD card. And because you will need to type the whole path+filename in the terminal in your phone, I would also suggest you rename the file to something simple, like cwm.img;
If you don't already have it, install Android Terminal Emulator;
Now, open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
(That is, if you rename the CWM file to "cwm.img" and you actually put it in the root of your internal SD card. If you put it somewhere else or did not rename your file, you will need to adapt the "if=" part of the command.)
Profit.
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm still using stock ROM, i'd like to install a custom ROM but i'm reading that you have to have Clockworkmod to do a successful install.
When i check in the files of the phone (sd card) i can see the clockwordmod folder in there there but still can't get it to boot into cwm recovery, only the Samsung recovery and I've tried the volume up home and power button so many times but no success.
Why do you think it worked when i first rooted the phone and not now?
this is frustrating, thanks for the help.
aybarrap1 said:
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
Click to expand...
Click to collapse
Yes I've tried 3 times via Odin, i can't remember where i got the cmw file from, it's a tar file (clockworkmod.TAR), the part i don't understand is why when i first rooted the phone in August cwm worked, i used it to install the root and now after trying to install it again 3 times i can't get it to work.
I'm using the stock ROM, not jelly bean.
thanks for any help
xBeerdroiDx said:
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
Click to expand...
Click to collapse
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
androidsavage23 said:
Have you tried twrp?
Click to expand...
Click to collapse
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
Click to expand...
Click to collapse
Download goo manager app and open that. There will be an option to "install open recovery" in the menu. Voilà a superior recovery that's easier to use
You can even use it to boot into recovery or install the new update for it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Click to expand...
Click to collapse
Easiest way to install TWRP is using GooManager from the Play Store.
1. Open GooManager.
2. Press the menu key to open the contextual menu, and select Install OpenRecoveryScript.
3. The app will ask you to confirm you really want to install a new recovery image.
4. GooManager searches for the correct TWRP build for your device. Look at the Filename line, it should display openrecovery-twrp-2.4.1.0-d2att.img for AT&T or openrecovery-twrp-2.4.1.0-d2can.img for Rogers/Bell/Telus. Again, confirm the installation.
5. Wait for the download to begin. TWRP will install. Done.
If it does not work or if GooManager does not find the correct build for your device -- in this latter case, this should raise a flag for you, as you may not have a SGH-i747/SGH-i747M; double check your phone model --, you can always install TWRP manually. From TWRP website (http://www.teamw.in/project/twrp2), you can grab the IMG file to manually install from the terminal emulator, and a TAR file to install using ODIN.
athens71 said:
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
Click to expand...
Click to collapse
Did you try it exactly as i said to?
drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So if that's the case (This will happen until you load a custom ROM) how can i back up my stuff before installing a new ROM? that's the reason i was trying to make cwm work so i could back my stuff.
Is there a different way to do a full back up?
thanks
xBeerdroiDx said:
Did you try it exactly as i said to?
Click to expand...
Click to collapse
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
athens71 said:
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
Click to expand...
Click to collapse
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
xBeerdroiDx said:
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
Click to expand...
Click to collapse
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
athens71 said:
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
Click to expand...
Click to collapse
you've created a backup already? if not, install cwm from ROM Manager, boot into cwm recovery and make your nandroid there. then you'll be all set to to try a new ROM
Related
Ok so i followed the instructions here. http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
I am all rooted and everything seems to be working until i tried to boot to CWM recovery to create a back up I realized I cannot boot into CMW. I was able do while following the instructions. It seems as thought my CWM flash is not sticking? I even tried to boot to recovery from ROM manger but it still takes me to stock recovery. I tried flashing from Rom Manger, it said it was successful and then I was able to boot to CWM, but after a reboot and trying to get back to it from rom manger again or by holding volume up, home and power I cannot get back to it. Why wont my flash stick.
Please help.
abandroid said:
Ok so i followed the instructions here. http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
I am all rooted and everything seems to be working until i tried to boot to CWM recovery to create a back up I realized I cannot boot into CMW. I was able do while following the instructions. It seems as thought my CWM flash is not sticking? I even tried to boot to recovery from ROM manger but it still takes me to stock recovery. I tried flashing from Rom Manger, it said it was successful and then I was able to boot to CWM, but after a reboot and trying to get back to it from rom manger again or by holding volume up, home and power I cannot get back to it. Why wont my flash stick.
Please help.
Click to expand...
Click to collapse
First, are you sure you are rooted?
Second, how are you trying to flash CWM?
You need to follow the method posted in the ATT Development forum and use the CWM that was developed for AT&T. I am using the d2att touch version.
id_twin said:
First, are you sure you are rooted?
Second, how are you trying to flash CWM?
Click to expand...
Click to collapse
Yes I am rooted. I am using Odin3 v3.04 to flash RecoveryGalaxyS3USCanada.tar. I remove the battery once it shows it passes. Hold down volume up, power and home button. It will let me boot to CWM recovery this one time but after that once I reboot I have to redo the steps to get back to CWM recovery. I just tried installing recovery-clockwork-touch-5.8.4.6-d2att.zip. It said it was successful but still no go.
Issues fixed! Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
[[SOLVED]]
Alright, so I checked through a few pages on the forums, and I didn't see anyone posting about this issue I am having..
I purchased my S3 a few days ago, and instantly rooted it. I used the Odin3 v3.07 method with "root66_SPR_L10VPBLJ7.7Z" ROM. That went well and fine. Then I tried flashing CWM recovery, and when I booted into recovery, it was still the stock. So I downloaded ROM Mangager and flashed the touch CWM recovery, after it finished, it asked if I wanted to boot into recovery. I agreed. Then the phone restarted, and upon starting, it showed the SAMSUNG logo, and "recovery booting" in the top left corner for about half a second. Then it just stayed on a black screen. I could do nothing after that. I then took the battery out for about 5 minutes, threw it back in, and the phone started. So I tried to manually boot into recovery, and the same issue. Took the battery out again, phone started properly, so I then tried to get into download mode. That worked fine, so I downloaded the CWM recovery on my laptop, and connected the phone through Odin, and flashed CWM onto my phone. Odin said it passed, but I still have the same issue when I try to boot into recovery.
Any ideas on something I'm doing wrong?
It is likely that your ROM is detecting the custom recovery and replacing it with the stock one. This was a change made to the stock ROM several versions ago. Before that you did not have to do anything extra to load the custom recovery.
The versions LG8 and later have code to detect an unsigned recovery and replace it with stock. You need to:
- Download TeamEpic-Root-from-Recovery-v5.zip and place it on your ineternal sdcard.
- Get into Download Mode and connect ODIN.
- Flash the custom recovery with ODIN but do not check the "Auto Reboot" box in Odin.
- Disconnect the phone from the PC once the recovery is flashed.
- Pull the battery to power down
- Boot directly into recovery (Hold Volume Up, Home and Power buttons until recovery appears. Do not allow the ROM to start).
- Once in the recovery you need to flash the Team Epic Root from Recovery.
- Reboot
All Done
m20120 said:
It is likely that your ROM is detecting the custom recovery and replacing it with the stock one. This was a change made to the stock ROM several versions ago. Before that you did not have to do anything extra to load the custom recovery.
The versions LG8 and later have code to detect an unsigned recovery and replace it with stock. You need to:
- Download TeamEpic-Root-from-Recovery-v5.zip and place it on your ineternal sdcard.
- Get into Download Mode and connect ODIN.
- Flash the custom recovery with ODIN but do not check the "Auto Reboot" box in Odin.
- Disconnect the phone from the PC once the recovery is flashed.
- Pull the battery to power down
- Boot directly into recovery (Hold Volume Up, Home and Power buttons until recovery appears. Do not allow the ROM to start).
- Once in the recovery you need to flash the Team Epic Root from Recovery.
- Reboot
All Done
Click to expand...
Click to collapse
Correct; and the reason for this is because the updated stock firmware as a script basically that re-flashes stock recovery upon boot if stock isn't detected. The team epic zip removes that. After doing that; I'd recommend flashing the twrp recovery.
Need some Help!
Ok guys got a problem! I have a new Samsung Galaxy Sprint S3 SPH-L710 4.1.1 and I flashed CMW ROM and did not do a back up of the stock OS. The phone still works with the ROM that I flashed cm-10.1m1. I already know befor you say it dumb right! Lol I'm kicking myself because I know better. I need help finding a mirror of the stock OS with all the drivers and kernels! Can anyone help out, thanks. :crying:
Re: [Q] Recovery Broken, Need Help
shadowcop9514 said:
Ok guys got a problem! I have a new Samsung Galaxy Sprint S3 SPH-L710 4.1.1 and I flashed CMW ROM and did not do a back up of the stock OS. The phone still works with the ROM that I flashed cm-10.1m1. I already know befor you say it dumb right! Lol I'm kicking myself because I know better. I need help finding a mirror of the stock OS with all the drivers and kernels! Can anyone help out, thanks. :crying:
Click to expand...
Click to collapse
So whats your issue? Why do you need the stock rom...? The drivers are the same and the stock kernel is for stock only, not aosp
Sent from my PG06100
Okay I did some research, and I found online that the Samsung phones need .tar.md5 not .img files for recovery.
http://forum.xda-developers.com/showthread.php?t=1484304
I did not use these directions since I don't run linux, and I wasn't going to download VMWare. Anyways, the way I fixed it, I purchased and downloaded Mobile Odin from the Play store. I put the recovery.img on my external SDcard, then opened the app. Under "recovery" I selected recovery.img and then scrolled down to "Flash" It flashed the recovery.img with no problems, then booted me into recovery. I then flashed mrRobinson_Ashaman.v2.20_signed.zip so I could uninstall some bloatware.
That last part was mostly for me, until I find a ROM I like.
CNexus said:
So whats your issue? Why do you need the stock rom...? The drivers are the same and the stock kernel is for stock only, not aosp
Sent from my PG06100
Click to expand...
Click to collapse
I'm selling my phone and getting the Galaxy S4 and the person wants the stock back on the phone.
shadowcop9514 said:
I'm selling my phone and getting the Galaxy S4 and the person wants the stock back on the phone.
Click to expand...
Click to collapse
Oh ok then, just run the latest Supersonic RUU (4.67 i think)
Sent from my PG06100
CNexus said:
Oh ok then, just run the latest Supersonic RUU (4.67 i think)
Sent from my PG06100
Click to expand...
Click to collapse
Ok, where do I find that ?
shadowcop9514 said:
Ok, where do I find that ?
Click to expand...
Click to collapse
WHOOPS. Sorry, I was thinking about another phone
Look up "flash back to stock galaxy s3" on google and you should get some good hits. Ignore the RUU thing, I thought I was on the OG evo forums
Sent from my PG06100
CNexus said:
WHOOPS. Sorry, I was thinking about another phone
Look up "flash back to stock galaxy s3" on google and you should get some good hits. Ignore the RUU thing, I thought I was on the OG evo forums
Sent from my PG06100
Click to expand...
Click to collapse
Ok thanks!
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.
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.
I've been having issue with my Sprint Note 2 for a while. I've also posted this to Reddit and other parts of the forum but so far have gotten no way to fix my issue. Here's the link to Reddit: http://www.reddit.com/r/techsupport...nt_note_2_sphl900_bricked_after_attempted_43/
Sorry, I didn't want to type that all up again and having to deal with formatting and such.
Basically, the gist of it, from what I can gather is that I have accidentally loaded the 4.3 bootloader with KNOX and it is currently preventing me from doing anything productive (flashing CWMR, rooting, installing stock, etc). I read here on the forum that there were ways to do so, especially this post: http://forum.xda-developers.com/showthread.php?p=46861777
I was wondering if there were steps for the Sprint Note 2 SPH-L900?
Any help in debricking my phone is appreciated.
Try these steps.
1. Boot phone into Odin/download mode
2. Flash twrp or cwmr via Odin.
3. When it reboots pull battery and then boot into recovery.
4. Flash this http://forum.xda-developers.com/showthread.php?p=36388145 it is mc2 bootloader, firmware, radio, etc...
5. Reboot phone. Things get weird for a few mins but it will boot.
You are now Knox free once again but you are also bone stock.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Try these steps.
1. Boot phone into Odin/download mode
2. Flash twrp or cwmr via Odin.
3. When it reboots pull battery and then boot into recovery.
4. Flash this http://forum.xda-developers.com/showthread.php?p=36388145 it is mc2 bootloader, firmware, radio, etc...
5. Reboot phone. Things get weird for a few mins but it will boot.
You are now Knox free once again but you are also bone stock.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried that multiple times. The problem here is that I can't load CWMR or TWRP. At first, I assume that I'd have to root so I downloaded the CF auto root file and flash it using ODIN. Then I tried installing CWMR (after converting to .tar using Caboomi's tool here on the forum). It would reboot and I tried holding down volume up + power + home button but nothing would happen. I try combinations of that and still nothing. I flashed the 4.3 sboot.bin to get it back to stock Samsung bootloader then retried with CWMR without rooting first this time and it still doesn't work. ODIN would tell me that it succeeds but I can't enter Recovery no mater the combination of keys that I press. I'm assuming this has to do with Knox in which case I'd just have to wait for the official 4.3 firmware on SamMobile to flash it since stock 4.1.2 won't work.
QuantumInteger said:
I've tried that multiple times. The problem here is that I can't load CWMR or TWRP. At first, I assume that I'd have to root so I downloaded the CF auto root file and flash it using ODIN. Then I tried installing CWMR (after converting to .tar using Caboomi's tool here on the forum). It would reboot and I tried holding down volume up + power + home button but nothing would happen. I try combinations of that and still nothing. I flashed the 4.3 sboot.bin to get it back to stock Samsung bootloader then retried with CWMR without rooting first this time and it still doesn't work. ODIN would tell me that it succeeds but I can't enter Recovery no mater the combination of keys that I press. I'm assuming this has to do with Knox in which case I'd just have to wait for the official 4.3 firmware on SamMobile to flash it since stock 4.1.2 won't work.
Click to expand...
Click to collapse
After flashing cwm do battery pull...Don't let it auto-reboot.
Also try different version of Odin maybe
louforgiveno said:
After flashing cwm do battery pull...Don't let it auto-reboot.
Also try different version of Odin maybe
Click to expand...
Click to collapse
I tried 3.07, 3.09, and even barebone 1.85 that came with CF auto root. It doesn't work. I can't load recovery just fine (according to ODIN) but I can't get into Recovery.
Here is the fix https://www.dropbox.com/s/s2clvyo4y6gar6s/4.3_Unbrick.tar
I promise this will fix your issue, but when you get done, you will be on MC2 with the 4.3 bootloader, but, it will boot, let you flash recovery and everything. I know this because I did the same thing as you and flashed the old cf-auto root and bricked my phone to, and I created this file to fix it and if you look in the help section, you will find my thread on how to unbrick after 4.3 update fail.
I promise though, this will fix your fone
Keithgordon said:
Here is the fix https://www.dropbox.com/s/s2clvyo4y6gar6s/4.3_Unbrick.tar
I promise this will fix your issue, but when you get done, you will be on MC2 with the 4.3 bootloader, but, it will boot, let you flash recovery and everything. I know this because I did the same thing as you and flashed the old cf-auto root and bricked my phone to, and I created this file to fix it and if you look in the help section, you will find my thread on how to unbrick after 4.3 update fail.
I promise though, this will fix your fone
Click to expand...
Click to collapse
...My God..... What ever you did, it worked. Turns out, Caboomi's file didn't work too well. I couldn't get CWMR working at all even after converting to .tar. I used TWRP instead and it works. Problem was that it asked me for my password, which I don't know since I tried everything, so I had to resort to wiping everything. I installed the file jlmancuso suggested, loading it onto SD card then flashing using TWRP, and now my Samsung Note 2 is debricked.
Your file was a godsend. Thank you!
No recovery stuck on bootloop
im having the same issue could you post that dropbox link again
So i was able to get recovery back but it wont let me mount my sd card so i cant flash anything through recover was hoping the file you have could be loaded through odin as it is a .tar file correct please help and thanks in advance.
Keithgordon said:
Here is the fix https://www.dropbox.com/s/s2clvyo4y6gar6s/4.3_Unbrick.tar
I promise this will fix your issue, but when you get done, you will be on MC2 with the 4.3 bootloader, but, it will boot, let you flash recovery and everything. I know this because I did the same thing as you and flashed the old cf-auto root and bricked my phone to, and I created this file to fix it and if you look in the help section, you will find my thread on how to unbrick after 4.3 update fail.
I promise though, this will fix your fone
Click to expand...
Click to collapse
rckingws6 said:
So i was able to get recovery back but it wont let me mount my sd card so i cant flash anything through recover was hoping the file you have could be loaded through odin as it is a .tar file correct please help and thanks in advance.
Click to expand...
Click to collapse
Yes, flash that file in Odin, it will downgrade you to MC2 with the MK4bootloader
Keithgordon said:
Yes, flash that file in Odin, it will downgrade you to MC2 with the MJA bootloader
Click to expand...
Click to collapse
MJA ? Isn't that an s4 bootloader?
louforgiveno said:
MJA ? Isn't that an s4 bootloader?
Click to expand...
Click to collapse
yep, sorry, I just woke up....I meant whatever version we are on with the note, what is it? MK4? I have both so I keep switching back and forth in the threads. Funny thing is, they are completely different, i will change that, thanks for pointing that out
my friend 's L900 bricked too ，but I cant download the file you provide , the error message is “Error (509) This account's public links are generating too much traffic and have been temporarily disabled”
may you provide another URL to download it or mail it to me ？ my email is [email protected] , thanks.
another question , how can i flash it into device with ODIN ？ from Pit ？ bootloader ？PDA ？PHONE ？ or others ？
Sent from my SPH-L900 using xda app-developers app
---------- Post added at 06:23 PM ---------- Previous post was at 06:14 PM ----------
Keithgordon said:
yep, sorry, I just woke up....I meant whatever version we are on with the note, what is it? MK4? I have both so I keep switching back and forth in the threads. Funny thing is, they are completely different, i will change that, thanks for pointing that out
Click to expand...
Click to collapse
my friend 's L900 bricked too ，but I cant download the file you provide , the error message is “Error (509) This account's public links are generating too much traffic and have been temporarily disabled”
may you provide another URL to download it or mail it to me ？ my email is [email protected] , thanks.
another question , how can i flash it into device with ODIN ？ from Pit ？ bootloader ？PDA ？PHONE ？ or others ？
Sent from my SPH-L900 using xda app-developers app
yea I still cant dowload it sorry for being a pest.
Keithgordon said:
Yes, flash that file in Odin, it will downgrade you to MC2 with the MK4bootloader
Click to expand...
Click to collapse
hello if you are online i need some help i dl the 4.3 note 2 update it has a different build than the one sprint has there are some features that are not on this build is there any way for me to get the ota from sprint
rckingws6 said:
yea I still cant dowload it sorry for being a pest.
Click to expand...
Click to collapse
rckingws6 said:
So i was able to get recovery back but it wont let me mount my sd card so i cant flash anything through recover was hoping the file you have could be loaded through odin as it is a .tar file correct please help and thanks in advance.
Click to expand...
Click to collapse
Try using TWRP instead. It gives you the option to mount an external SD card. Also try restarting into recovery again. I had Recovery bugged out on me once.
QuantumInteger said:
Try using TWRP instead. It gives you the option to mount an external SD card. Also try restarting into recovery again. I had Recovery bugged out on me once.
Click to expand...
Click to collapse
i need some help
yea i can get into twrp recovery now but my sdcard wont mount thats why im trying to use odin
QuantumInteger said:
Try using TWRP instead. It gives you the option to mount an external SD card. Also try restarting into recovery again. I had Recovery bugged out on me once.
Click to expand...
Click to collapse
For those of you who have bricked Note 2s (SPH-L900), I'm going to drop a DropBox link here to a folder of ALL of the files that I used to unbrick my phone. I experimented with multiple methods (and several sleepless nights). Some of them will be useful to you, not all. I have the Android SDK and Caboomi's converter for .img to .tar. It doesn't work too well for CWMR just FYI. ODIN-OC will attempt to load stock MC2 onto your phone but it won't work if it's bricked. Arc Converter is a program I used to try convert the MK4 .zip file to .tar to try and flash an update using ODIN. It didn't work. The steps that I took to unbrick my phone will be posted after the link.
https://www.dropbox.com/sh/c2bfpfdf0qbs6bu/ZiNC-BF5kf
Be patient. Some of the files are still updating.
Steps:
1) Put your phone into Download mode by holding volume down + power + home button at bootup
2) Use ODIN (3.07 or 3.09) to load the 4.3_Unbrick.tar file. This will take a bit of time so be patient. Once the phone boots up again, you'll get past the boot screen that says "Samsung Galaxy Note II" and you'll get the Samsung logo with the spinning icon but it will loop. This is normal.
3) Next, power off (yank the battery and cable, leave battery out but plug the cable back in) and reboot into download.
4) Flash the TWRP .tar file (don't try converting the CWMR to .tar, it won't work) then reboot.
5) Hold volume up + power + home button (be patient here)
6) You should see the Team Win logo. You're now in recovery. The TWRP may ask you for the password. It is NOT the passcode to your lockscreen or your Google password. I have no idea what it is. At this point, you'd have to wipe your phone (internal only) if you want to flash the stock recovery.
7) Load the MC2 stock recovery file with counter reset onto a microSD card and mount it onto the phone (play around with TWRP, if it doesn't see the SD card the first time, restart or play with the mount function). Just be careful not to wipe your microSD card.
8) Flash the stock recovery (give it time) and it'll restart. You should be back at 4.1.2.
EXTRA STEPS
If you're still interested in 4.3, load the MK4 update onto the microSD card as well. BEFORE you go through the activation process for the 4.1.2 firmware at boot, boot into recovery. Flash the 4.3 update using stock recovery. This should put you onto 4.3 after the phone reboots. You should now have stock 4.3 (no root).
Sorry for all the download errors, I am uploading to my websight right now and as soon as it uploads, I will post the URL, it should download much faster too. I didnt realize so many people needed it