I accidentally flashed the kernel for my old SGS II International to my Epic 4G Touch, but I managed to get it back to stock eventually. Everything was fine for the past couple months, and today I finally decided to install the system update(which I just put off for awhile despite all the prompts). Then it gave me that white triangle and when I rebooted into recovery mode. Now it just stays in recovery mode no matter what I do. Reboot option? Reboots back into recovery? Factory reset option? Boots back into recovery.
The ok button should be the power button right? This is a bit different from my old SGS
i would try pulling the battery and attempting to boot into download
yea, try & get into download mode... power off>vol dn+power until download mode is on the screen. then use ODIN/HEIMDALL to flash a stock tar file.
I should have mentioned that I did remove the battery and leave it out for a few minutes several times. It just kept booting back into recovery. I did eventually find the jig I made which was able to force it into download mode. But heimdall just keeps giving me this "ERROR: Claiming interface failed!" message even though it can detect the phone.
So no one has any idea what to do about this?
Did you try odin? If that fails put a rom(.zip) in sd card and flash from revovery.
Edit: if you are goin to switch from heimdall to odin you have to unistall heimdalls drivers. There are instructions on how to do this in heimdalls readme file.
javi_emma said:
Did you try odin? If that fails put a rom(.zip) in sd card and flash from revovery.
Edit: if you are goin to switch from heimdall to odin you have to unistall heimdalls drivers. There are instructions on how to do this in heimdalls readme file.
Click to expand...
Click to collapse
No, I didn't try Odin because I'm using OS X. I guess I'm going to have to make a windows boot partition. sigh
Well I guess I'll try to flash a rom from recovery first.
Well this is odd. It won't let me write anything to the sd card I normally use in it. It says it's read only. But uh....it always copied things fine if it was IN either this phone or my SGS II International when I tried to copy things.
I should just be able to put the rom on any micro SD card right? I have another 4 GB laying around here I can use if so.
Correct any sd should work!
Sent from my SPH-D710 using Tapatalk
And once again I highlight "apply update from sdcard" and hit the power button...just reboots into recovery mode for the millionth time without doing anything.
Gradius said:
And once again I highlight "apply update from sdcard" and hit the power button...just reboots into recovery mode for the millionth time without doing anything.
Click to expand...
Click to collapse
You may have to go the route of installing Odin and flashing a full stock tar that includes ROM, kernel, and modem so it overwrites everything in that one flash. I don't think it is something you can do by flashing in a recovery
Sent from my Nexus S 4G using xda premium
Gradius said:
And once again I highlight "apply update from sdcard" and hit the power button...just reboots into recovery mode for the millionth time without doing anything.
Click to expand...
Click to collapse
You have the stock recovery. That why. U can't flash an unsigned from from there. You are gonna have to Odin something. Either a full tar or maybe a kernel with cwm to flash something.
Sent from my Nexus S 4G using xda premium
Well anyone want to recommend/link me a tar? I'm making a windows partition right now so I can run Odin.
And yeah I figured it was because I put it back to stock that it wasn't working. But if it's back on stock why am I still getting the white triangle with the orange exclamation?
In fact if it's back to stock the past couple months and been working fine then why did it decide to screw up when I tried to install the OS update?
Gradius said:
In fact if it's back to stock the past couple months and been working fine then why did it decide to screw up when I tried to install the OS update?
Click to expand...
Click to collapse
The OTA updates are not always perfect. It is possible that there was something lingering from before. Let me try to find a link to a one click stock restore for you ...
Sent from my SPH-D710 using xda premium
Here is sfhub's EL29 full stock Gingerbread restore ...
http://forum.xda-developers.com/showthread.php?t=1433101
Sent from my SPH-D710 using xda premium
Haha, double post, haha
Sent from my SPH-D710 using Tapatalk
Related
so i decided the odin, to get back to stock so i can flash MIUI, coming from Frosty Jb, and Ktoonzer kernal. i used boot-insecure-tmo-t999uvalem-cwm to on ODIN, the phone rebooted, and then a blue LED started Flashing. it vibrated and kept rebooting. i took out battery, and goutt into Cwm, then wanted to flash MIUI, but it failed because of Build.prop, so i went back into download and flashed boot-insecure-tmo-t999uvalem-cwm again. now it wont boot, and let me get into Download mode or Cwm
Edit: im can get back into and CWM now, but not Download mode. it needed to run though one cycle of bootlooping before it let me in. So now im back on the Frosty jb, And i feel like my phone wont let me Flash anything else.
What happens when you try to go into download mode from Frostys reboot menu?
Maybe flash the UVALH2 deodexed stock rom and try odin again.
But use either the regular fw from sammobile or root66 from MrRobinson.
Where did you get the fw you've been trying to flash?
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 01:10 PM ---------- Previous post was at 01:07 PM ----------
boot-insecure-tmo-t999uvalem-cwm
Is this just a kernel? You had said you were trying to odin back to stock, but this looks to be a cwm flashable file which I doubt is gonna work in odin.
Sent from my SGH-T999 using xda app-developers app
A similar thing happened toe when I tried going to stock from JB. Try ODIN back to stock using mrRobinsons file. Then boot into the recovery and do a factory reset. Note that this will probably wipe your internal storage
Sent from my SGH-T999 using xda app-developers app
nicky9door said:
A similar thing happened toe when I tried going to stock from JB. Try ODIN back to stock using mrRobinsons file. Then boot into the recovery and do a factory reset. Note that this will probably wipe your internal storage
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I've never seen Odin wipe internal or external SD cards. As far as I know, it doesn't even have this capability, which is a good thing.
So i got back into Stock. i Rerooted and everything, i downloading Goomanager and the CodenameAndroid ROM From there. i installed the twcr recovery from goomanager. Then i flashed the CodenameAndroid. it has a boot animation but not booting, i cant get into Cwm or Download mode. it goes into Download mode for 2 seconds virbates and roots. Any Idea??
Aerowinder said:
I've never seen Odin wipe internal or external SD cards. As far as I know, it doesn't even have this capability, which is a good thing.
Click to expand...
Click to collapse
It wasnt ODIN that wiped my storage. It was running the factory reset from the Samsung 3e Recovery (which I got after I used ODIN to go back to stock)
ishred11 said:
So i got back into Stock. i Rerooted and everything, i downloading Goomanager and the CodenameAndroid ROM From there. i installed the twcr recovery from goomanager. Then i flashed the CodenameAndroid. it has a boot animation but not booting, i cant get into Cwm or Download mode. it goes into Download mode for 2 seconds virbates and roots. Any Idea??
Click to expand...
Click to collapse
Getting into recovery can be tricky as there's a short window where you have to release the buttons. The most successful way for me is, with the phone off, hold home+power+vol up. When you see the Samsung logo, look at the top of the screen for a line of blue text. If you see this line, immiediately let go of all buttons.
Another option (might be a longshot) would be to try using ADB during the CodenameAndroid (CNA) boot animation. Search for ADB standalone to get the files you need. While your phone is on the CNA bootscreen, plug it intop your computer and try running "adb devices" from the command line (you'll need to be in the same folder as the ADB executable). If you see a serial number, then try running "adb reboot recovery" which should get you into recovery mode
ishred11 said:
So i got back into Stock. i Rerooted and everything, i downloading Goomanager and the CodenameAndroid ROM From there. i installed the twcr recovery from goomanager. Then i flashed the CodenameAndroid. it has a boot animation but not booting, i cant get into Cwm or Download mode. it goes into Download mode for 2 seconds virbates and roots. Any Idea??
Click to expand...
Click to collapse
Did you remember to wipe everything including factory reset in recovery?
If you're already rooted just press reboot recovery in goo manager. Otherwise try what the above post says.
Sent from my SGH-T999 using xda app-developers app
ishred11 said:
so i decided the odin, to get back to stock so i can flash MIUI, coming from Frosty Jb, and Ktoonzer kernal. i used boot-insecure-tmo-t999uvalem-cwm to on ODIN, the phone rebooted, and then a blue LED started Flashing. it vibrated and kept rebooting. i took out battery, and goutt into Cwm, then wanted to flash MIUI, but it failed because of Build.prop, so i went back into download and flashed boot-insecure-tmo-t999uvalem-cwm again. now it wont boot, and let me get into Download mode or Cwm
Edit: im can get back into and CWM now, but not Download mode. it needed to run though one cycle of bootlooping before it let me in. So now im back on the Frosty jb, And i feel like my phone wont let me Flash anything else.
Click to expand...
Click to collapse
Did you make a Nandroid (Backup) of your ROMS? Always make a Backup before flashing anything on your phone. If the solutions the users have posted doesn't work, then USB JIG can be used as a last resort. I would also like to let you know some kernels corresponds to some ROMS. For an example, Frosty is based on TW (Touch Wiz) and can only be flashed with kernels that supports Touch Wiz. Flashing Ktoonzer kernel with, for an example, CM10 would only result in the phone not being able to boot due to CM10 ROM not supporting Touch Wiz. Make sure you flash a kernel that supports the ROM and before any flashing, make a backup via recovery.
Hello everyone i got a note 2 sprint bricked. I used odin and it keeps saying failed at sboot.bin right after recovery.please help if you can thanks.
carshass said:
Hello everyone i got a note 2 sprint bricked. I used odin and it keeps saying failed at sboot.bin right after recovery.please help if you can thanks.
Click to expand...
Click to collapse
You need to post more info if possible but it sounds like you are trying to downgrade from MA7 to an earlier firmware like LK8. The update included a security patch so it won't let you go back to insecure. Try pulling the sboot out of whatever you are trying to flash or stick with MA7
Sent from my SPH-L900 using xda app-developers app
Try downloading another .tar file for ljc. I had the same issue. I believe i got a working one directly from samfirmware
Sent from my SPH-L900 using xda app-developers app
oook,, so im new to the note2 just came from a gs2 with jellybam on it...soo im running jellybomb and i flashed venum ice reborn 1.5 it seemed to fash fine until reboot,, then it just hung on the note2 bootup screen. i hold down home and power and it says up to download custom rom down to restart... both jut hang. help?
i got as far as trying to find odin but i couldnt and stopped.
shangus1 said:
oook,, so im new to the note2 just came from a gs2 with jellybam on it...soo im running jellybomb and i flashed venum ice reborn 1.5 it seemed to fash fine until reboot,, then it just hung on the note2 bootup screen. i hold down home and power and it says up to download custom rom down to restart... both jut hang. help?
i got as far as trying to find odin but i couldnt and stopped.
Click to expand...
Click to collapse
umm ya i see why i didnt get a reply.. all i had to do was hold volume up home power and the n re flash... its amazing what you can figure out inhere when ignored lolz
carshass said:
Hello everyone i got a note 2 sprint bricked. I used odin and it keeps saying failed at sboot.bin right after recovery.please help if you can thanks.
Click to expand...
Click to collapse
I've been having the same problem for a couple days now. I can install a custom rom but I can't figure out how to get back to stock.
You need to post more info if possible but it sounds like you are trying to downgrade from MA7 to an earlier firmware like LK8
Click to expand...
Click to collapse
That might be the problem I'm having.
EDIT:
Yep, that was it. Thanks!
carshass said:
Hello everyone i got a note 2 sprint bricked. I used odin and it keeps saying failed at sboot.bin right after recovery.please help if you can thanks.
Click to expand...
Click to collapse
It's not brick cuz odin can still see your phone. If you dont have TWRP on it, go to www.twrp.com and download the tar file for sprint note 2. Then use Odin to flash it. Once you are done that, go here http://forum.xda-developers.com/showthread.php?t=2086769 to get either the old LJC or MA7 and put it in your phone either internal or external SD. Do the wipe cache/factory reset first. Then flash it. It will go back to stock rom.
Help
Hello even though its old I figured I would post here first instead of starting a new thread, my friend has a Note 2 for Sprint never rooted or custom ROM flashed and he said it was sitting on the charger and when he woke up in the morning it was off and after attempting to power the device on it stays stuck on the Samsung logo. I cant get Kies to recognize the device at all not matter what pc is use however it shows up in Odin but it fails everything from stock files ( older and current ) , different versions of Odin, recoveries and I even tried a " unbrick .tar file " . Any help at all would be appreciated I will include pics
demorik said:
Hello even though its old I figured I would post here first instead of starting a new thread, my friend has a Note 2 for Sprint never rooted or custom ROM flashed and he said it was sitting on the charger and when he woke up in the morning it was off and after attempting to power the device on it stays stuck on the Samsung logo. I cant get Kies to recognize the device at all not matter what pc is use however it shows up in Odin but it fails everything from stock files ( older and current ) , different versions of Odin, recoveries and I even tried a " unbrick .tar file " . Any help at all would be appreciated I will include pics
Click to expand...
Click to collapse
Can you odin a custom recovery and boot into it?
1. Put phone in download mode
2. In odin program uncheck reboot and flash recovery
3. After flash disconnect phone and pull battery
4. Quickly insert and remove battery multiple times (if you just reinsert battery it will automatically boot)
5. Boot phone into recovery backup any important data that is on your internal sdcard
6. Do factory reset then flash billards stock mc2 with counter reset (do not wipe cache after flashing this)
7. Flash superuser zip found in billards Op
8. Reboot phone and freakout when see the screen do odd things and reboot (this is normal)
Now it will bootup on stock rooted mc2.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Can you odin a custom recovery and boot into it?
1. Put phone in download mode
2. In odin program uncheck reboot and flash recovery
3. After flash disconnect phone and pull battery
4. Quickly insert and remove battery multiple times (if you just reinsert battery it will automatically boot)
5. Boot phone into recovery backup any important data that is on your internal sdcard
6. Do factory reset then flash billards stock mc2 with counter reset (do not wipe cache after flashing this)
7. Flash superuser zip found in billards Op
8. Reboot phone and freakout when see the screen do odd things and reboot (this is normal)
Now it will bootup on stock rooted mc2.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have tried but I never tried to uncheck anything in Odin, I will try it later and post the results thanks.
say my brother it still doesnt let me boot into recovery what do i do...
jlmancuso said:
Can you odin a custom recovery and boot into it?
1. Put phone in download mode
2. In odin program uncheck reboot and flash recovery
3. After flash disconnect phone and pull battery
4. Quickly insert and remove battery multiple times (if you just reinsert battery it will automatically boot)
5. Boot phone into recovery backup any important data that is on your internal sdcard
6. Do factory reset then flash billards stock mc2 with counter reset (do not wipe cache after flashing this)
7. Flash superuser zip found in billards Op
8. Reboot phone and freakout when see the screen do odd things and reboot (this is normal)
Now it will bootup on stock rooted mc2.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
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'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
Hello,
My unrooted At&T galaxy s3 will not go past the Samsung Galaxy SIII splash screen. When I enter recovery it just gives me a dead android guy.
I had this problem before and to fix it, I used odin to flash the stock 4.0.4, then I flashed 4.1.1 (I think these are the correct versions, I followed instructions here), then my phone wouldn't OTA update to touchwiz 4.3 so I flashed it using recovery mode using instructions and files I found here. The phone worked fine for a few weeks after that, but then started to reboot randomly and delete apps. Eventually it just stopped working all together which is where I am now.
I tried to install TWRP using odin which odin says worked but when I try to go to recovery mode I still just see the dead android guy. The phone did not have USB debugging mode turned on so I am not sure if I could install a custom recovery at all.
I tried the CF-auto root that I found here which got partway through and then failed.
Do you guys have any suggestions? Is there a stock touchwiz 4.3 rom that I could flash using odin??
Thank you very much, please let me know if you require any more information, I really want to get my phone working again.
korarchaeota said:
Hello,
My unrooted At&T galaxy s3 will not go past the Samsung Galaxy SIII splash screen. When I enter recovery it just gives me a dead android guy.
I had this problem before and to fix it, I used odin to flash the stock 4.0.4, then I flashed 4.1.1 (I think these are the correct versions, I followed instructions here), then my phone wouldn't OTA update to touchwiz 4.3 so I flashed it using recovery mode using instructions and files I found here. The phone worked fine for a few weeks after that, but then started to reboot randomly and delete apps. Eventually it just stopped working all together which is where I am now.
I tried to install TWRP using odin which odin says worked but when I try to go to recovery mode I still just see the dead android guy. The phone did not have USB debugging mode turned on so I am not sure if I could install a custom recovery at all.
I tried the CF-auto root that I found here which got partway through and then failed.
Do you guys have any suggestions? Is there a stock touchwiz 4.3 rom that I could flash using odin??
Thank you very much, please let me know if you require any more information, I really want to get my phone working again.
Click to expand...
Click to collapse
It almost sounds like you're dealing with a situation I'm having on my galaxy tab. It has the internal SD chip going bad. I had to use a rom specially made to boot from a partitioned external sd card. Sorry, I can't help more, but the symptoms seem similar.
Sent from my SCH-I800 using Tapatalk
Thank you for your reply. Where did you obtain a rom that could boot from the external sd card?
wrenhal said:
It almost sounds like you're dealing with a situation I'm having on my galaxy tab. It has the internal SD chip going bad. I had to use a rom specially made to boot from a partitioned external sd card. Sorry, I can't help more, but the symptoms seem similar.
Sent from my SCH-I800 using Tapatalk
Click to expand...
Click to collapse
Try flashing the TWRP again with Odin, but make sure the auto reboot option on the left is unchecked in Odin. After flashing, unplug the phone and then hold volume up + menu + power buttons at the same time until it reboots.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
shortydoggg said:
Try flashing the TWRP again with Odin, but make sure the auto reboot option on the left is unchecked in Odin. After flashing, unplug the phone and then hold volume up + menu + power buttons at the same time until it reboots.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just tried it with only F. Reset Time checked, it installs it and says a green Pass!. I then unplugged it, tried to hold volume up + menu + power buttons for a while but nothing happened. I pulled the battery and then did volume up + menu + power buttons and went straight back to dead android guy. Any ideas?
Only other thing right now is to make sure you have the latest odin, which is 3.09
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
shortydoggg said:
Only other thing right now is to make sure you have the latest odin, which is 3.09
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Trying everything with the new version of Odin results in all the same results.
Does anyone know if there is a tar (Odin flashable) version of update43.zip found in this thread?
http://forum.xda-developers.com/showthread.php?t=2387423
Thanks!
korarchaeota said:
Trying everything with the new version of Odin results in all the same results.
Does anyone know if there is a tar (Odin flashable) version of update43.zip found in this thread?
http://forum.xda-developers.com/showthread.php?t=2387423
Thanks!
Click to expand...
Click to collapse
No there's no Odin flash-able there.
Sorry, we don't seem to have any answers for your problem. It seems like it may be more of a hardware issue than software.
Did you phone boot after flashing stock 4.04?
audit13 said:
Did you phone boot after flashing stock 4.04?
Click to expand...
Click to collapse
Yes it did, the first time that this started happening. But I was unable to do that again, I thought since I flashed all the way to 4.3 and I read that once you go to 4.3 you can't go back. Is that correct?
Thank you for your help. I was hoping to try an odin flashable touchwiz 4.3 but I can't seem to find one.
So you had 4.04 on your phone and you used OTA updates to get to 4.3? If this is correct, then you can't flash a stock AT&T 4.3 ROM because it has never been made available to the public; therefore, the only 4.3 ROMs that may work are based on the leaked AT&T 4.3 ROM or compiled from an OTA update.
Once of these ROMs may get your phone going again: http://forum.xda-developers.com/showthread.php?t=2498233
audit13 said:
So you had 4.04 on your phone and you used OTA updates to get to 4.3? If this is correct, then you can't flash a stock AT&T 4.3 ROM because it has never been made available to the public; therefore, the only 4.3 ROMs that may work are based on the leaked AT&T 4.3 ROM or compiled from an OTA update.
Once of these ROMs may get your phone going again: http://forum.xda-developers.com/showthread.php?t=2498233
Click to expand...
Click to collapse
Thank you for your suggestion, all the ones I tried there need recovery to flash...not odin. Is it possibly to make an odin file from a recovery flash file??
Thanks!
korarchaeota said:
Thank you for your suggestion, all the ones I tried there need recovery to flash...not odin. Is it possibly to make an odin file from a recovery flash file??
Thanks!
Click to expand...
Click to collapse
Did you try installing Philz Touch from Odin? As was suggested earlier, don't use auto reboot. Once Philz has been installed and you see Reset in the window, disconnect the USB cable, remove the battery, replace the battery, boot into recovery, wipe and flash a custom ROM. This may help you get your phone working for now.
audit13 said:
Did you try installing Philz Touch from Odin? As was suggested earlier, don't use auto reboot. Once Philz has been installed and you see Reset in the window, disconnect the USB cable, remove the battery, replace the battery, boot into recovery, wipe and flash a custom ROM. This may help you get your phone working for now.
Click to expand...
Click to collapse
Thank you for your suggestion, but I still get the dead android guy after flashing and trying to go into recovery. Any other ideas??
korarchaeota said:
Thank you for your suggestion, but I still get the dead android guy after flashing and trying to go into recovery. Any other ideas??
Click to expand...
Click to collapse
Did you try philz or cwm? I am not sure why stock recovery is not being overwritten.
audit13 said:
Did you try philz or cwm? I am not sure why stock recovery is not being overwritten.
Click to expand...
Click to collapse
I tried twrp and philz, I haven't tried cwm yet, should I? Is it not working because I didn't enable USB debugging before it stopped working?
Thanks for your help!
korarchaeota said:
I tried twrp and philz, I haven't tried cwm yet, should I? Is it not working because I didn't enable USB debugging before it stopped working?
Thanks for your help!
Click to expand...
Click to collapse
Nope, USB debugging will not make a difference.
The latest Philz Touch is based on the latest CWM. After your flash Philz, are you letting the phone auto reboot on its own after flashing in Odin?
I know of no way to convert a custom ROM so it can be flashed in Odin.