Develop Bugs

[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.

4.4.2 Update via Kies: Stuck on Recovery Booting...

Hi all,
Did the 4.4.2 update via Kies on an unrooted stock 4.3, now it's stuck on "Recovery Booting..." in blue up top. Doing a battery pull, as well as trying to boot to recovery (volume up, home, power) produces the same result.
Any idea how to get out of this, what I presume is a soft brick?
EDIT: Cancel that, downloaded the 4.4 image and installed via Odin. Phone loads up fine now. Gonna do a factory wipe.
Anybody have the flashable or Odin file for restoring stock 4.4 recovery, unless restoring pda in Odin already did that? No need for TWRP, gonna stick with stock.

I have the stock 4.3?
Sent from my SM-N900T using xda premium

howetechnical said:
Hi all,
Did the 4.4.2 update via Kies on an unrooted stock 4.3, now it's stuck on "Recovery Booting..." in blue up top. Doing a battery pull, as well as trying to boot to recovery (volume up, home, power) produces the same result.
Any idea how to get out of this, what I presume is a soft brick?
EDIT: Cancel that, downloaded the 4.4 image and installed via Odin. Phone loads up fine now. Gonna do a factory wipe.
Anybody have the flashable or Odin file for restoring stock 4.4 recovery, unless restoring pda in Odin already did that? No need for TWRP, gonna stick with stock.
Click to expand...
Click to collapse
Same thing happened to me, now when you say the 4.4 image, you mean like the update.zip?? You mind directing me to this image.
Edit: Nevermind, figured it out lol

makavelicruz said:
Same thing happened to me, now when you say the 4.4 image, you mean like the update.zip?? You mind directing me to this image.
Edit: Nevermind, figured it out lol
Click to expand...
Click to collapse
For anybody else here:
http://forum.xda-developers.com/showthread.php?t=2465764
Also, this overwrites the recovery, so that's returned to stock.

just went throught that same thing lol

kies not reseting the note 3
is me but befor on 4.3 i could use kies would reset everything on my note 3
now with kikat it wont

[Q] Bricked my I747 - Please Help?

Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?

loc626 said:
Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?
Click to expand...
Click to collapse
\
Yeah. Should be fixable. First, can you try booting to recovery and doing a wipe/reset? I presume you have custom recovery? If this doesn't work, then you can try flashing a complete compatible stock restore image via recovery to get the phone working or flash a custom ROM? What Android version were you on prior to the attempt to flash CM? This would let us know what stock version to revert to.

I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.

loc626 said:
I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.
Click to expand...
Click to collapse
If you were already on 4.3, please do not try to flash 4.1.1 now otherwise you could risk bricking your phone. If you tried doing the hard wipe/reset via (custom) recovery and this did not work, you can try flashing a complete stock restore image via recovery. See the instructions in the following thread ....
http://forum.xda-developers.com/showthread.php?t=2658486
Unfortunately, you would need to load the stock restore zip to a (micro) SD card. Unless you are able to save files to your phone, there is no other way. Once you have the restore zip ready, boot your phone to recovery mode and flash. You can revert to a custom ROM once your phone is back to working normally.

I had this problem TeamWin Recovery. I put Philz recover on there and it worked fine. You will probably have to ADB philz recovery to your phone, if you chose to try Philz. This is what worked when I rooted my girlfriend's phone.

An easy way to install Philz Touch recovery would be to download and install the latest tar version for the d2lte and flash it via Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte

Thanks to everyone for your help and solutions.
My co-worker, who flashed my root and recovery, was able to get it back to 4.3 stock. Unfortunately, the backup that he made before rooting did not work in recovery [twrp]. So I lost all my pics from the last two months since getting my phone.
As sad as I was that I couldn't recover the pics, I am happy to have my phone back to normal+root.
I'm not sure, but maybe it bricked from trying to flash cm11 thru twrp?! Can't really say, but the recovery did not go thru either.... It went thru "successfully" but after I would reboot then it would stay on ATT splash.
Oh well... all is good now. I will steer away from custom roms for now and wait until the 4.4 update comes out for my i747. Or if i get another phone later on, I can use the s3 as a lab rat.
Again, thanks to everyone!

[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] Bricked? Note 8 GT-N5110 stuck on boot loop

Hi all,
I've looked through several of the existing threads on the Note 8 and I've not gotten anywhere yet. I had the device happily rooted and working for months and then, stupid me, I used ROM manager to flash a new ROM this morning and on boot, it's stuck on the logo.
I CAN get to the recovery menu, but reset to factory default does nothing. I have wiped the cache from recovery and then tried to factory reset again; still stuck on logo at boot.
I can also get to download mode and have tried using KIES 2.6 (since KIES 3 is for Android 4.4.2 and up) and every time I try to do the update firmware/recovery, it starts, stops and says 'there is a problem with the download file' and then it quits.
I have tried using ODIN 3.7 and a few different recovery files but although it will say 'passed', on reboot, it's stuck on the logo.
Can someone help me, please? This is the only tablet I own and I really need it to not be a door stop
:crying:

not bricked yet, maybe. for now, try to download latest firmware from sammobile.com for n5110 and use odin to flash it.
about the factory reset of course it would still boot loop, you are trying to factory reset a bootlooped rom so it doesnt matter. you should flash a new zip through recovery.

Mr.201 said:
not bricked yet, maybe. for now, try to download latest firmware from sammobile.com for n5110 and use odin to flash it.
about the factory reset of course it would still boot loop, you are trying to factory reset a bootlooped rom so it doesnt matter. you should flash a new zip through recovery.
Click to expand...
Click to collapse
Hi Mr.201,
Thank you for the suggestion. Question, when you say download the latest firmware, will it matter if I don't use the original? I ask because I've been trying to find the original firmware (stock) and while I've found many sites with GT-N5110 FW's, they are all coded for other countries; I can't seem to find one for US. So, if I use a newer firmware, will that work?
I can still get to recovery mode and download mode. I don't know if USB debugging is on, though, which I hope won't matter at this point. I can't remember if it was on when it died on me.
I appreciate your advice! Hopefully, I can get this thing going again. That would certainly make me a happy camper!

For some reason, the US version is labelled as "Cellular South" but in general, any 5110 rom will work, although there are some quirks with wifi frequencies between the North American and European roms.

My Note 8 got stuck in a boot loop. It was rooted/custom recovery/custom ROM. I tried some of things you did, and nothing worked. I ended up downloading and installing the ODIN one click recovery/un-rooted stock image from this thread:
http://forum.xda-developers.com/showthread.php?t=2773712
This restores everything to stock (including the recovery). After flashing, it was still stuck in the boot loop. I booted into the factory recovery, and did a data wipe. After doing that, my note is working now. So ... doing this might be worth a try.

May I make a suggestion when flashing firmware... If you are flashing to something notreviously installed on the device. First flash with philz recovery and perform a full wipe for flashing new ROM. This way everything is clean for your flash to work properly.
A factory reset is not going to work as well for the new flash to take.