Develop Bugs

[Q] TWRP 2.6.3.1 Asks for password

I woke up this morning to my phone perpetually rebooting.
I was running a nightly of CM 11.
Now when I try to go into Recovery I get a screen that asks for a password. I have no idea what that password is as I did not set one. I tried wiping data to no avail. I tried flashing a new recovery via Odin this did not work (Odin said successful but the screen on the phone never showed the transfer of the file). No matter what wipe method I use in recovery it just says fail, doesn't work at all and hangs or will say it can't mount. I have searched and searched and tried and tried and I'm stuck. I even tried ADB that didn't work either. Please help!

Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att

audit13 said:
Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Click to expand...
Click to collapse
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.

therecker said:
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.
Click to expand...
Click to collapse
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

theramsey3 said:
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This did not work. When I use ODIN all that is happening is that ODIN says it has succeeded but the little progress bar that usually shows up on the phone when you are in download mode never comes up. I did try this method though and it didn't work.
I restarted the phone in ODIN mode then opened ODIN then connected the USB cable then unchecked the two boxes you mentioned then flashed a new non TWRP recovery then waited for ODIN to say successful then the phone never showed the progress bar so I waited 2 mins until I pulled the battery then I restarted phone directly to recovery and still have the password prompt. Even after hitting cancel I cannot interact with recovery because every option I choose just says fail. I cannot even mount external sd card.

What phone do you have? What was the most recent stock ROM on your phone? Maybe you can flash a stock ROM.

There is a copy of the stock Samsung 3e recovery (which we can't use to flash zips with) I'm curious if maybe it can overwrite what you have going on? On the password screen I wasn't hitting cancel I was simply hitting the back arrow key. I will see if I have a copy of the stock recovery, just maybe you can flash it then flash another recovery after that so you can fix your phone.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have Samsung Galaxy S 3 At&T (d2att) SGH-I747 whichever one of those you want. The most recent stock rom on the phone was when I bought it brand new a few months after it came out. I tried installing a stock rom. I tried this using ODIN and it failed. The issue here is that TWRP somehow encrypted the entire file system so NOTHING at all in recovery works. When I use ODIN mode it never shows on my phone that it is accepting a transfer from the computer. When I tried the stock rom via ODIN method it actually failed in ODIN instead of telling me it succeeded and then just not work. It failed at the point when it says Firmware Update Start...aboot.mbn...NAND Write Start!...Complete(Write) operation failed. I am up for any suggestions but I need them to be detailed instructions because I have tried so many things I need to know what exact steps to follow.

I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.

audit13 said:
I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.
Click to expand...
Click to collapse
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?

therecker said:
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?
Click to expand...
Click to collapse
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?

audit13 said:
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?
Click to expand...
Click to collapse
It was a CM11 Nightly ROM from the very beginning of February. And before that it was a CM10.2 Stable ROM.

Which stock ROM was on your phone before you loaded a custom ROM?

audit13 said:
Which stock ROM was on your phone before you loaded a custom ROM?
Click to expand...
Click to collapse
I have no idea. It was when I first got the phone in November of 2012.

Sounds like your phone may be running a 4.3 bootloader which means your bootloader is locked and cannot be downgraded. This may explain why you are getting errors when trying to flash Odin. There is no stock AT&T 4.3 ROM that can be flashed via Odin.

[Q] Help CWM Recovery not working

I have successfully installed Omni ROM with Android 4.4.2 to my Note 2 and I don't like it and want to go back to stock. Before installing the ROM I made a CWM recovery using version 6.0.4.3. When I boot the phone into restore I am able to restore everything but system data. When I try to restore system data I get a message that says .android_secure . img not found skipping restore. How do I fix this so I can have my phone back?

RyanGN2 said:
I have successfully installed Omni ROM with Android 4.4.2 to my Note 2 and I don't like it and want to go back to stock. Before installing the ROM I made a CWM recovery using version 6.0.4.3. When I boot the phone into restore I am able to restore everything but system data. When I try to restore system data I get a message that says .android_secure . img not found skipping restore. How do I fix this so I can have my phone back?
Click to expand...
Click to collapse
Did your restore boot?

Yes, I have restored boot. After I perform the restore everything seems to be normal during, but it gets stuck on the ATT screen during boot.

RyanGN2 said:
Yes, I have restored boot. After I perform the restore everything seems to be normal during, but it gets stuck on the ATT screen during boot.
Click to expand...
Click to collapse
Try this.
From Zen Arcade's [ROM][4.3][Dec-2013] AT&T I317-UCUBMK6/MJ4 *Stock* Rooted Odex/De-Odex/Odin thread
After flashing one of the stock packages, you may need to flash the MK6 tz.img and optionally the param.bin from the MJ4 leak. The zip below contains two Odin packages.
Try flashing the tz only package first (in Odin), then the tz+param package to see if this gets your phone to boot. You may also need to boot recovery and do a factory reset.
AT&T i317 ODIN 4.3 UCUBMK6 TZ.IMG & UCUBMJ4 (Leak) PARAM.BIN (AT&T Note 2 ONLY)
I317UCUBMK6-TZ-PARAM.zip
http://d-h.st/CDK
- Run Odin3 v3.07.exe
Download Link http://www.mediafire.com/download/77...x2/Odin307.zip
Unzip to where you can run it.
- Put your Note 2 in Download Mode
Entering download mode is very simple. First you will need to turn off your device. Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device.
Plug into a RELIABLE usb port and a RELIABLE usb cable (preferably the white Samsung cable) and wait for it to show up in Odin (COM5 or something like that)
Unzip the I317UCUBMK6-TZ-PARAM.zip file you downloaded
- Click the PDA slot in Odin and locate the I317UCUBMK6-TZ.tar.md5 that you downloaded and unzipped
The filename that goes into the PDA Slot is I317UCUBMK6-TZ.tar.md5
MAKE SURE IN THE OPTION AREA ONLY AUTO REBOOT AND F.RESET TIME ARE CHECKED!!!
- Click START and wait. It will complete and reboot.
Try flashing the tz only package first. See if it boots.
If not, repeat the above steps using I317UCUBMK6-TZ-PARAM.tar.md5.
You may also need to boot recovery and do a factory reset. Do this after second ODIN flash.
If your phone still hangs after second flash, pull the battery, and boot into recovery mode.Just hold down UP volume button and power button until recovery screen pops up.

Ok, I did all of that perfectly and my phone is still booting with Omnirom. I want to put the phone back to stock. I understand that at this point the android_secure.img cant be fixed but before rooting I backed up with Kies so putting the phone back wont be hard. I want the stock rom back and unroot and be done with it.

RyanGN2 said:
Ok, I did all of that perfectly and my phone is still booting with Omnirom. I want to put the phone back to stock. I understand that at this point the android_secure.img cant be fixed but before rooting I backed up with Kies so putting the phone back wont be hard. I want the stock rom back and unroot and be done with it.
Click to expand...
Click to collapse
Since you tried everything above and it didn't HELP..
I'm wondering have you tired the kies emergency firmware recover. I taught I screwed my phone up flashing a Odin file. Then the phone was stuck not doing anything. Couldn't boot up, nada.
But after running it thru that set up, the phone was back to completely stock...
Look HERE»»»http://goo.gl/J0P1ZX
Not sure if it'll help but worth a try right. It helped me when I was in need.
Sent from my SAMSUNG-SGH-I317 using Tapatalk

I did not know kies had a recovery option as I rarely use it. I did find a CWM stock rom but it has 4.1.2 but its working and I going to try an OTA 4.3 update and see what happens. It looks like I will manually have to restore everything which I was hoping to avoid but I thank you for your help.

RyanGN2 said:
I did not know kies had a recovery option as I rarely use it. I did find a CWM stock rom but it has 4.1.2 but its working and I going to try an OTA 4.3 update and see what happens. It looks like I will manually have to restore everything which I was hoping to avoid but I thank you for your help.
Click to expand...
Click to collapse
I'm beyond lost of what you have done and where you're at.
Appears after doing the stuff in my post #4, your phone is booting past ATT screen ???? Understand it booted into OMNI, but at least it booted.
That's all I was trying to do was to get it past the ATT screen.
If I would have know you wanted to go back to stock 4.3, you could have done this....
http://forum.xda-developers.com/showthread.php?t=2618447
You may still have too, if the OTA does not work from the CWM stock 4.1.2 ROM.
Whenever you flash ROMs rule of thumb is back up apps and anything else you want to save, with Titanium Backup or MyBackup, etc. etc. Then restore apps after new ROM is installed.
Doing a wipe/factory rest prevents residual crap from the previous ROM leftover.
Unless its an update to a ROM you already have running, and the OP says no worries, dirty flash.
69%+ of problems with ROM flashes is the flasher didn't follow instructions or half-a$$ed it and didn't wipe or factory reset.
I've been guilty of that also, so not trying to be combative or accusatory.
Good luck with OTA.

When I did the steps in post #4 it never did anything it stayed in omnirom, which I have not had a problem getting to boot. It doesn't boot when I restore from my backup created before I installed Omni with CWM. I don't like Omni and I am tired of everything root. I'm a heavy jail breaker and thought I could do this however its more learning than I wanted and want to be done with root entirely. The OTA update did fail. Should I still use the 4.3 rom above or is there something else I should that will also remove root? I did backup apps with titanium and I also backed up everything with Kies.

[Q] T-Mobile Note 2 (SGH-T889 on CM11) Unable to Boot into Recovery, Forgot GAPPS

Phone: T-mobile Samsung Galaxy Note 2 SGH-T889
1. Rooted phone using Zedomax instructions with CWM Recovery 6.
2. Afterwards, unable to boot into recovery.
3. Installed ROM Manager from Playstore, and used it to successfully boot into Recovery.
4. Flashed Nightly CM11 Rom from XDADevelopers site, but forgot to flash GAPPS.
5. Afterwards, booted into CM11 but phone model is listed as N7105 (or something like that). It is not listed as SGH-T889 anymore.
6. Unable to boot into Recovery using Vol Up + Power + Home. The Samsung logo flashed and scrolls vertically twice.
7. Tried installing the GAPPS APK files one at a time, but some files would not install and as a result I was unable to get any GAPPS working.
8. I would like to flash back to stock and have an image, but scared if I do, then I might get stuck if I am unable to boot into Recovery again.
What should I do to get GAPPS applications back on the phone?
What is the correct firmware file named?
Thanks for any help you provide.

cardinal35 said:
Phone: T-mobile Samsung Galaxy Note 2 SGH-T889
1. Rooted phone using Zedomax instructions with CWM Recovery 6.
2. Afterwards, unable to boot into recovery.
3. Installed ROM Manager from Playstore, and used it to successfully boot into Recovery.
4. Flashed Nightly CM11 Rom from XDADevelopers site, but forgot to flash GAPPS.
5. Afterwards, booted into CM11 but phone model is listed as N7105 (or something like that). It is not listed as SGH-T889 anymore.
6. Unable to boot into Recovery using Vol Up + Power + Home. The Samsung logo flashed and scrolls vertically twice.
7. Tried installing the GAPPS APK files one at a time, but some files would not install and as a result I was unable to get any GAPPS working.
8. I would like to flash back to stock and have an image, but scared if I do, then I might get stuck if I am unable to boot into Recovery again.
What should I do to get GAPPS applications back on the phone?
What is the correct firmware file named?
Thanks for any help you provide.
Click to expand...
Click to collapse
Can you post a link to what you used. That method doesn't sound familiar and might possibly be part of the problem.
The N7105 model is not unexpected. It is the model for the intl Note 2.
It can mess with stuff if you use auto installing software such as Goo Manager and *maybe* Rom Manager. It might try to install the wrong recovery based on your inaccurate build prop device ID.
Which version of bootloader are you running? If you had official 4.3 you have fewer options for going back to stock. If when you boot into download (home+vol down+power) you see the word "knox" anywhere you have the 4.3 bootloader.
Look in the Development stickies and check for root66 by MrRobinson. Install Odin on a PC, make certain your phone communicates with the computer, the factory reset it. Install the appropriate version of root66 (UVBMC1 if you are non Knox, UVUCMK7 if you are on the Knox bootloader) following the instructions in the thread.
This should get you back to stock.
Once you can breathe again (getting stuck like that sucks) only flash roms from around here until you become comfortable with the nuances of going elsewhere.
Hastily spouted for your befuddlement

Procedures used to root and clarification
Coug76 said:
Can you post a link to what you used. That method doesn't sound familiar and might possibly be part of the problem.
The N7105 model is not unexpected. It is the model for the intl Note 2.
It can mess with stuff if you use auto installing software such as Goo Manager and *maybe* Rom Manager. It might try to install the wrong recovery based on your inaccurate build prop device ID.
Which version of bootloader are you running? If you had official 4.3 you have fewer options for going back to stock. If when you boot into download (home+vol down+power) you see the word "knox" anywhere you have the 4.3 bootloader.
Look in the Development stickies and check for root66 by MrRobinson. Install Odin on a PC, make certain your phone communicates with the computer, the factory reset it. Install the appropriate version of root66 (UVBMC1 if you are non Knox, UVUCMK7 if you are on the Knox bootloader) following the instructions in the thread.
This should get you back to stock.
Once you can breathe again (getting stuck like that sucks) only flash roms from around here until you become comfortable with the nuances of going elsewhere.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
The link to the root method I used:
galaxynote2root dot com galaxy-note-2-root how-to-root-galaxy-note-2-easiest-method
I only used ROM manager when I was unable to boot into Recovery after using the above procedure. ROM manager was used only to boot into recovery when I was unable to boot into it using the Vol Up + Power + Home keys method. It has an option to boot into recovery.
If I use the root66 method, is there a chance that I may get a boot loop upon boot after flashing? I read that moving from CM roms to stock might require booting into recovery after flashing the stock firmware file. That being the case, then I was afraid after flashing the right file, I still would not be able to boot into recovery.
Is there a way to simply get the GAPPS installed without recovery? I tried adb and unzipping to use File Manager to install each individual apk...no luck. The CM 11 ROM seems to work just no google apps.
But it would be nice to get back to stock fully too. Am looking into the bootloader version and root66 instructions. Thank you for the direction to follow.

Root66 will get you to a rooted stock beginning place. It will start you out with a bone stock device including bootloader and recovery (if done properly).
At this point if you reset the flash counter via triangle away, unroot the device, and factory reset it looks warranty eligible (unless you have the Knox bootloader tripped).
The reason you would do this: somewhere along the line something got screwed up and starting fresh is in order. Back up your data and start over.
Once you have a stock device, use the resources available here to guide you step by step. Tool kits are all well and good. If you take the steps yourself carefully after learning what they do and why, the mystery of a tool kit is gone. You can be confident into what you put into your device.
I would download the most recent version of TWRP recovery from their website (2.7.0.1) and flash it in Odin while I was at it. Recovery Odin flashes just like the root66 files.
Hastily spouted for your befuddlement

cardinal35 said:
The link to the root method I used:
galaxynote2root dot com galaxy-note-2-root how-to-root-galaxy-note-2-easiest-method
I only used ROM manager when I was unable to boot into Recovery after using the above procedure. ROM manager was used only to boot into recovery when I was unable to boot into it using the Vol Up + Power + Home keys method. It has an option to boot into recovery.
If I use the root66 method, is there a chance that I may get a boot loop upon boot after flashing? I read that moving from CM roms to stock might require booting into recovery after flashing the stock firmware file. That being the case, then I was afraid after flashing the right file, I still would not be able to boot into recovery.
Is there a way to simply get the GAPPS installed without recovery? I tried adb and unzipping to use File Manager to install each individual apk...no luck. The CM 11 ROM seems to work just no google apps.
But it would be nice to get back to stock fully too. Am looking into the bootloader version and root66 instructions. Thank you for the direction to follow.
Click to expand...
Click to collapse
there are more files than just apks in a gapps package.

How do I know which version of boot loader is running? I am currently on CM 11 Nightly.
Then which root66 T-Mobile ROM should I flash using Odin? I did not understand the Mobilicity, Videotron, etc., ROMs.
Sent from my SPH-D710 using xda app-developers app

cardinal35 said:
How do I know which version of boot loader is running? I am currently on CM 11 Nightly.
Then which root66 T-Mobile ROM should I flash using Odin? I did not understand the Mobilicity, Videotron, etc., ROMs.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
to find out your bootloader version you need to boot into download mode. if you see the word knox on that screen you are on 4.3 bootloader. if you are on tmobile then you have no use for the other carriers roms (mobilicity etc)

Boot Loop after root66 UVBMD1
Coug76 said:
Can you post a link to what you used. That method doesn't sound familiar and might possibly be part of the problem.
The N7105 model is not unexpected. It is the model for the intl Note 2.
It can mess with stuff if you use auto installing software such as Goo Manager and *maybe* Rom Manager. It might try to install the wrong recovery based on your inaccurate build prop device ID.
Which version of bootloader are you running? If you had official 4.3 you have fewer options for going back to stock. If when you boot into download (home+vol down+power) you see the word "knox" anywhere you have the 4.3 bootloader.
Look in the Development stickies and check for root66 by MrRobinson. Install Odin on a PC, make certain your phone communicates with the computer, the factory reset it. Install the appropriate version of root66 (UVBMC1 if you are non Knox, UVUCMK7 if you are on the Knox bootloader) following the instructions in the thread.
This should get you back to stock.
Once you can breathe again (getting stuck like that sucks) only flash roms from around here until you become comfortable with the nuances of going elsewhere.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
1. Checked bootloader by going into Download Mode (Vol Down, Power, Home) and did not see Know anywhere.
2. I downloaded root66_TMO_T889UVBMD1.7z.
3. Installed using Odin after checking MD5 checksum.
Now the phone goes into a loop. It displays the Samsung logo, then goes to the T-Mobile Splash screen, then returns to Samsung logo...
Any ideas how I should proceed?

Solved!
cardinal35 said:
1. Checked bootloader by going into Download Mode (Vol Down, Power, Home) and did not see Know anywhere.
2. I downloaded root66_TMO_T889UVBMD1.7z.
3. Installed using Odin after checking MD5 checksum.
Now the phone goes into a loop. It displays the Samsung logo, then goes to the T-Mobile Splash screen, then returns to Samsung logo...
Any ideas how I should proceed?
Click to expand...
Click to collapse
Disregard last reply. I solved by:
1. Booting into Stock Recovery (Vol Up + Power + Home) and Factory Data Wipe/Reset.
2. Everything works on boot!
Thanks for all the help guys. What a relief...I will update if any problems are seen later.

[Q] Note 2 bricked after 4.4 update, can't get into recovery

After trying to update to kit kat my note 2 will not get past the "note 2" splash screen. What sucks even worse is that I can't get into recovery to install a new rom. I've been searching tons of threads and whatnot across XDA and other websites but nothing has worked.
What I've tried:
-Flashing TWRP, CWM, Philz recoveries. Odin says they succeeded but I still can't get to any of them.
-Flashing srock roms downloaded from multiple sources. When I try this I get an error in odin, usually fails right after sboot.bin
-Using other versions of Odin, different usb's, etc. Same stuff happens no matter what.
-Kies, but it won't connect and says device is unsupported.
-Android toolkit, but i couldn't really do much with it in this state
-I even tried re-partitioning with some t0lte pit file. This really didn't change anything.
-I found an "mk4_recovery.tar" file in a thread on here. That finished and succeeded, but I still can't get anywhere, However I did notice that this changed the "current binary" on my phone from "custom" to "official samsung binary." I'm not sure if that is important or not.
I feel like I am running out of options and my phone is hard-bricked. You guys are my last hope and I'm hoping there's something you guys can help me with!! If you have anything I can try please let me know!!!

SCAND1UM said:
After trying to update to kit kat my note 2 will not get past the "note 2" splash screen. What sucks even worse is that I can't get into recovery to install a new rom. I've been searching tons of threads and whatnot across XDA and other websites but nothing has worked.
What I've tried:
-Flashing TWRP, CWM, Philz recoveries. Odin says they succeeded but I still can't get to any of them.
-Flashing srock roms downloaded from multiple sources. When I try this I get an error in odin, usually fails right after sboot.bin
-Using other versions of Odin, different usb's, etc. Same stuff happens no matter what.
-Kies, but it won't connect and says device is unsupported.
-Android toolkit, but i couldn't really do much with it in this state
-I even tried re-partitioning with some t0lte pit file. This really didn't change anything.
-I found an "mk4_recovery.tar" file in a thread on here. That finished and succeeded, but I still can't get anywhere, However I did notice that this changed the "current binary" on my phone from "custom" to "official samsung binary." I'm not sure if that is important or not.
I feel like I am running out of options and my phone is hard-bricked. You guys are my last hope and I'm hoping there's something you guys can help me with!! If you have anything I can try please let me know!!!
Click to expand...
Click to collapse
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.

michael85tx said:
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
Click to expand...
Click to collapse
What a nightmare!
I odined back to stock MK4, did the 4.4.2 OTA last night. Then did the CF Auto Root via odin, installed custom recovery. The phone is currently on pageplus network. I started messing around, did the GSM Mod, then tried the international and domestic sim unlock procedures. The result was not satisfying, so I tried flashing different modems. Eventually CDMA works, but GSM not. So I made a huge mistake by attempting to downgrade from NE2. And of course failed. Now the phone can't register on either CDMA or GSM.
So once I flash M2 Stock with Count Reset, I can play with the 4.4.2 OTA zip again to get a 100% 4.4.2 system?

michael85tx said:
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.
Click to expand...
Click to collapse
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!

SCAND1UM said:
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!
Click to expand...
Click to collapse
I did the procedure everything went well but is there any way to update lastest firmware kitkat as i tried to and keep having to do the same procedure to unbrick it? thanks

brooklynman2020 said:
I did the procedure everything went well but is there any way to update lastest firmware kitkat as i tried to and keep having to do the same procedure to unbrick it? thanks
Click to expand...
Click to collapse
The best way to do the upgrade (since you know how to get your phone back if it happens again) is to just simply use Odin now to flash the 4.4.2 tar file thanks to "garwynn" for taking the time in making it.
http://forum.xda-developers.com/showthread.php?t=2780984
since most of my links don't work after I post lol I'm giving the download too. I tried uploading it but the file size is too big to post. So I hope this link works let me know and I'll re-upload it and post another link if the link stops working. 4.4.2 stock rom .tar
---------- Post added at 03:05 AM ---------- Previous post was at 02:55 AM ----------
lilila said:
What a nightmare!
I odined back to stock MK4, did the 4.4.2 OTA last night. Then did the CF Auto Root via odin, installed custom recovery. The phone is currently on pageplus network. I started messing around, did the GSM Mod, then tried the international and domestic sim unlock procedures. The result was not satisfying, so I tried flashing different modems. Eventually CDMA works, but GSM not. So I made a huge mistake by attempting to downgrade from NE2. And of course failed. Now the phone can't register on either CDMA or GSM.
So once I flash M2 Stock with Count Reset, I can play with the 4.4.2 OTA zip again to get a 100% 4.4.2 system?
Click to expand...
Click to collapse
sorry for the late reply but yes you can. I have gone back and forth trying to decide which 4.4.2 works best for service and style. lol right now I'm on 4.4.2 stock rooted (took FOREVER to get rooted I think it just finally clicked in I had given up). but there's already a .tar file for 4.4.2 you can just flash the .tar file and you have a OTA STOCK (unrooted) version of 4.4.2 for SPRINT only. It's the easiest way to get your phone back to working if it' soft bricked or just won't load recovery.
...NOTE... you can UPGRADE flash your bootloader (i.e. ... M2 .. MK4 ...N2) from Odin. You just CAN NOT downgrade firmware via Odin if you're going to go back to 4.1/4.2/4.3 versions. You will 99% of the time get "failed" at write to sboot .. for recovery I recommend Philz as it clears your cache and such when you flash roms and gapps and such for you.
---------- Post added at 03:10 AM ---------- Previous post was at 03:05 AM ----------
SCAND1UM said:
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!
Click to expand...
Click to collapse
You're welcome lol when it happened to me I wanted to punch a wall or something because I couldn't make a call to help me and there was no way Sprint would have helped me. It took me 8 hours to find it that day lol I had almost started giving up hope

You may already know this, but you also want to read up and see what versions of odin people are having success with. As well as what custom recoverys (and versions) seem to be working.
I used Odin v3.09 with no problems. Heard that others had success with v3.07
Flashed and running Philz custom recovery v6.0.4.5
I flashed update-supersu-v1.94.zip (originally flashed cwm-supersu-v0.94.zip, which DID NOT work). Supersu is a little buggy. On both the note2 and s3, after install apk would fc. Went to play store and updated supersu, supersu will then work (even "partially" disables knox for you)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

g_money said:
You may already know this, but you also want to read up and see what versions of odin people are having success with. As well as what custom recoverys (and versions) seem to be working.
I used Odin v3.09 with no problems. Heard that others had success with v3.07
Flashed and running Philz custom recovery v6.0.4.5
I flashed update-supersu-v1.94.zip (originally flashed cwm-supersu-v0.94.zip, which DID NOT work). Supersu is a little buggy. On both the note2 and s3, after install apk would fc. Went to play store and updated supersu, supersu will then work (even "partially" disables knox for you)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Yeah that's true I use Odin 3.09 Philz Recovery (latest version if that doesn't work the 6.07.09 has had some good success) and SU v1.93 is the one I have.

Stuck with 4.4.2 OTA
michael85tx said:
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.
Click to expand...
Click to collapse
Followed this procedure after accepting OTA and couldn't get chainfire autoroot to work. This worked flawlessly for me and I'm flashing again !!!!

lewisyiv said:
Followed this procedure after accepting OTA and couldn't get chainfire autoroot to work. This worked flawlessly for me and I'm flashing again !!!!
Click to expand...
Click to collapse
Where is the fix file for download? I cant flash the tar file, all time show fail in odin, I was try with firmware 4.4.2, 4.2, 4.1.2 and nothing my note 2 enter in download mode but not in recovery mode, alwais is in bootloop in logo... maybe I have brick?

vegitamaster66 said:
Where is the fix file for download? I cant flash the tar file, all time show fail in odin, I was try with firmware 4.4.2, 4.2, 4.1.2 and nothing my note 2 enter in download mode but not in recovery mode, alwais is in bootloop in logo... maybe I have brick?
Click to expand...
Click to collapse
Two post above you or in the quote above you has the link for fix. You need to follow the first link (xda thread link) and it will take you to my post that has the upload.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Second post in this thread helped me immensely. Thank you!
I broke my note 2 that I had rooted and was running rwilco's mostly stock rom on.
Got another note 2 off craigslist and decided I should root it too for speed and for tethering. Tried the liquid smooth rom and it failed leaving me with no ROM.
Every ROM I tried failed until I found this thread and used Odin to flash "ALL_SPT_L900VPUCNE2_L900SPTCNE2_1561791_REV04_user_low_ship.tar.md5" that was linked.
So phone is now running 4.4.2 can I safely try again to load a custom ROM?
What do I need to do to make sure I don't have the same problem?
I'm not really savvy with this stuff but I can follow destructions

does any of the above steps wipe internal data?

[Q] Help me fix this phone...

Some background here. My son has screwed up his phone.
S3 i747 AT&T
was rooted using Kingo Root.
No custom ROM.
He tried to update to 4.3 OTA a couple days ago. Now it will boot to the Galaxy SIII logo then go black. I can get to ODIN mode and stock recovery mode. I am just at a loss as to what to do next. Reading the forum has gotten a little overwhelming as to exactly what I need to do to get it back.
Can someone give me some instructions as to what to do?
If you need more info I will check this thread and provide it. As far as any specifics that can be found in the 'About phone' menu, I cannot remember what the specs were so that isnt possible for me to provide.
Thank you very much for any help.

First of all, don't panic. If you still have download mode and recovery working the phone is very fixable. Second of all, don't start flashing stuff willy-nilly. You have to be a little careful with this phone once it is on 4.3 and later firmware, and from what you've posted it is not entirely clear how far the update proceeded.
I don't think download mode or stock 3e recovery will tell you what firmware your phone is running, and it is important to know that before proceeding. Do you see anything about "warranty bit" when you're in download mode? If you see warranty bit then you successfully updated to a 4.3 (or higher) bootloader. Definitely don't try to use Odin to flash any full firmware updates if you see warranty bit in download mode. It would probably just fail, but if it actually proceeded it would attempt to downgrade the bootloader and hard brick the phone.
At this point, my recommendation is to use Odin to flash the latest TWRP recovery on the phone. Just in case, don't let the phone auto-reboot after flashing with Odin, uncheck everything but f.reset time in Odin. Upon success unplug the USB cable and pull the battery. Replace the battery and boot straight to recovery by pressing and holding vol up + home + power and releasing when you see the blue text in the upper left that says recovery booting.
Once up in TWRP go into Advanced -> Terminal and enter:
Code:
getprop ro.bootloader
Report back the output of that command here, and that will set what to flash next to fix the phone.
Another thing you can do with the phone booted in TWRP is connect it to a PC via USB and transfer files from the phone to the computer in case anything needs backed up. The PC should automatically mount the phone as a media device. It might end up being necessary to format the phone's internal storage to get it booting a ROM normally again, so this wouldn't be a bad pre-planning step.

How do I download the recovery file from the TWRP link you provided? I cant really tell how to download but I can see the file I need.

Here is what is displayed in Odin mode
Odin mode
Product name: sgh-i747
Current binary: custom
System status: custom
Qualcomm secureboot: enable
Warranty Bit: 1
Bootloader rp swrev: 3

peckaldee said:
Here is what is displayed in Odin mode
Odin mode
Product name: sgh-i747
Current binary: custom
System status: custom
Qualcomm secureboot: enable
Warranty Bit: 1
Bootloader rp swrev: 3
Click to expand...
Click to collapse
Since you see warranty bit, you're definitely on a 4.3+ bootloader. Do not download and try to flash the full firmware file from sammobile.com to restore the phone. It would either fail or or hard brick the phone if it did proceed due to attempting to downgrade the bootloader.
Download this TWRP https://dl.twrp.me/d2att/twrp-2.8.7.0-d2att.img.tar. Flash the tar file using the PDA menu from Odin. Most people recommend Odin 3.07 for use with this phone. If you've never used Odin before, you'll have to get the samsung USB drivers working on the PC too.
Get Odin and the samsung drivers from this thread if you need them.
It would be nice if you could just restore the phone using Odin, but AT&T never let a firmware past jellybean 4.1.1 be released. And since you now appear to be on a 4.3 bootloader you cannot downgrade.

I will try this when I get home from work in the morning and report back. Thanks for the detailed help!

jason2678 said:
Once up in TWRP go into Advanced -> Terminal and enter:
Code:
getprop ro.bootloader
Report back the output of that command here, and that will set what to flash next to fix the phone.
Click to expand...
Click to collapse
It outputs:
I747UCUFNJ2

I would like to flash this ROM if possible.
S3Rx 4.0 TouchWiz 4.4.2 UCUFNE4 (11-9-14) || UCUFNJ2 (10-04-15)
http://forum.xda-developers.com/gal...x-4-0-touchwiz-4-4-2-ucufne4-8-12-14-t2848080

peckaldee said:
I would like to flash this ROM if possible.
S3Rx 4.0 TouchWiz 4.4.2 UCUFNE4 (11-9-14) || UCUFNJ2 (10-04-15)
http://forum.xda-developers.com/gal...x-4-0-touchwiz-4-4-2-ucufne4-8-12-14-t2848080
Click to expand...
Click to collapse
That ROM should be a good choice. This is easiest if you have a microSD you can use with a PC adapter to store the ROM on, but it can be done without a microSD if need be. If you don't have a microSD you'll have to copy the ROM zip to the phone from PC via USB.
To get it running, first go into Wipe -> Advanced Wipe and tick Dalvik Cache, System, Data, and Cache and wipe them. Then go to Install, flash the ROM zip and reboot. Since you're coming from a stock ROM that should be all you have to do. First boot will be long, maybe 10 minutes or so.
Sometimes touchwiz ROMs are a bear to get to boot. If it hangs on boot for more than 15 or 20 minutes its not going to boot. Pull the battery and boot back into TWRP. Repeat the wipe of dalvik, system, data, and cache. Then go into Wipe -> Format Data and type "yes" to confirm formatting the internal storage. At this point you'll have to copy over your ROM zip again unless it is stored on an external microSD. Flash the ROM and reboot again. Usually formatting the internal storage is enough to get touchwiz ROMs to boot, but there are a few more tricks if it still hangs.

jason2678 said:
That ROM should be a good choice. This is easiest if you have a microSD you can use with a PC adapter to store the ROM on, but it can be done without a microSD if need be. If you don't have a microSD you'll have to copy the ROM zip to the phone from PC via USB.
To get it running, first go into Wipe -> Advanced Wipe and tick Dalvik Cache, System, Data, and Cache and wipe them. Then go to Install, flash the ROM zip and reboot. Since you're coming from a stock ROM that should be all you have to do. First boot will be long, maybe 10 minutes or so.
Sometimes touchwiz ROMs are a bear to get to boot. If it hangs on boot for more than 15 or 20 minutes its not going to boot. Pull the battery and boot back into TWRP. Repeat the wipe of dalvik, system, data, and cache. Then go into Wipe -> Format Data and type "yes" to confirm formatting the internal storage. At this point you'll have to copy over your ROM zip again unless it is stored on an external microSD. Flash the ROM and reboot again. Usually formatting the internal storage is enough to get touchwiz ROMs to boot, but there are a few more tricks if it still hangs.
Click to expand...
Click to collapse
Following that ROM thread is confusing. Not sure if I need to install the recommended bootloader in the first post of that thread. It mentions NJ1 but not NJ2. I assume my NJ2 will work since it is the newer version but I'm still unsure.

peckaldee said:
Following that ROM thread is confusing. Not sure if I need to install the recommended bootloader in the first post of that thread. It mentions NJ1 but not NJ2. I assume my NJ2 will work since it is the newer version but I'm still unsure.
Click to expand...
Click to collapse
At NJ2 you seem to have updated to the newest bootloader for the AT&T S3. Never ever try to downgrade it. You're stuck :silly:
enewman rebased his ROM to NJ2 shortly after it came out. Download this one https://www.androidfilehost.com/?fid=24052804347829298

That ROM is up and running. Cannot imagine how grateful I am for your help in this matter.

peckaldee said:
That ROM is up and running. Cannot imagine how grateful I am for your help in this matter.
Click to expand...
Click to collapse
No problem. Happy to help. Hope it works out well for you.