Develop Bugs

[Q] Hard bricked ... what do u think ?

So am running stock 4.1.2 rooted and suddenly phone restarts and gets stuck at Samsung bootscreen
Factory reset and cache wipe from recovery didnt help
Tried to odin flash a firmware (4.1.2) odin says failed and never starts the flashing
Then I tried a 4.1.1 flashed perfectly. Though at first boot, it gets stuck at the working android logo and keeps restarting
what could be the problem ?

nabilbek said:
So am running stock 4.1.2 rooted and suddenly phone restarts and gets stuck at Samsung bootscreen
Factory reset and cache wipe from recovery didnt help
Tried to odin flash a firmware (4.1.2) odin says failed and never starts the flashing
Then I tried a 4.1.1 flashed perfectly. Though at first boot, it gets stuck at the working android logo and keeps restarting
what could be the problem ?
Click to expand...
Click to collapse
Its boot loop?
Sent from my GT-N7100 using xda premium

nabilbek said:
So am running stock 4.1.2 rooted and suddenly phone restarts and gets stuck at Samsung bootscreen
Factory reset and cache wipe from recovery didnt help
Tried to odin flash a firmware (4.1.2) odin says failed and never starts the flashing
Then I tried a 4.1.1 flashed perfectly. Though at first boot, it gets stuck at the working android logo and keeps restarting
what could be the problem ?
Click to expand...
Click to collapse
Is the handset rooted?
If so you need to download samsung note 2 toolkit. this is here >> http://forum.xda-developers.com/showthread.php?t=1923956
ensure you have the correct adb drivers but the toolkit can also do this aswell. you then need to put the system into recovery mode. (I assume you know how to boot up recovery.) You need to install a customer recovery specifically TWRP so boot up the toolkit. select your device and make sure you choose the current version of android you have on it not the version you wish to install. You then need to flass an insecure boot image for correct adb access so choose option 3, follow the instructions select TWRP as your recovery and complete as directed.
Once this has finished you then need to download your rom, if its stock it can be located here.
http://forum.xda-developers.com/showthread.php?t=2032849 for n7105 (lte version) and here
http://forum.xda-developers.com/showthread.php?t=1896696 for original.
Download the zip and place into the "push_files_here" of the toolkit folders.
Boot into your new twrp recovery
Reload the toolkit, choose your device, choose the option to push the file to your device, select the device, for destination type"/sdcard/" and follow onscreen options until file is finished.
Your file should now be on your phone in the home folder.
Go to "wipe", select "factory reset" now to "install" select your new spangly rom, wipe dalvik cache once completed and wala you should have one shiny new rooted odexed note 2 that sould load fine. Any issues get back to me and i will be happy to help.
I deliberately bricked my device about 8 times to find the best way to recover.
Kris

Try a pit file.
Sent from my GT-N7100 using xda app-developers app

a guy said something about a hardware/board defective ? I dont believe it ... could it be true ?

klashnikoff said:
Is the handset rooted?
If so you need to download samsung note 2 toolkit. this is here >> http://forum.xda-developers.com/showthread.php?t=1923956
ensure you have the correct adb drivers but the toolkit can also do this aswell. you then need to put the system into recovery mode. (I assume you know how to boot up recovery.) You need to install a customer recovery specifically TWRP so boot up the toolkit. select your device and make sure you choose the current version of android you have on it not the version you wish to install. You then need to flass an insecure boot image for correct adb access so choose option 3, follow the instructions select TWRP as your recovery and complete as directed.
Once this has finished you then need to download your rom, if its stock it can be located here.
http://forum.xda-developers.com/showthread.php?t=2032849 for n7105 (lte version) and here
http://forum.xda-developers.com/showthread.php?t=1896696 for original.
Download the zip and place into the "push_files_here" of the toolkit folders.
Boot into your new twrp recovery
Reload the toolkit, choose your device, choose the option to push the file to your device, select the device, for destination type"/sdcard/" and follow onscreen options until file is finished.
Your file should now be on your phone in the home folder.
Go to "wipe", select "factory reset" now to "install" select your new spangly rom, wipe dalvik cache once completed and wala you should have one shiny new rooted odexed note 2 that sould load fine. Any issues get back to me and i will be happy to help.
I deliberately bricked my device about 8 times to find the best way to recover.
Kris
Click to expand...
Click to collapse
hi kris, been on a vacation now am back
thanks for your reply, but when I am flashing the insecure image "boot-insecure-dlk7-N7100.tar"
it gives there is no pit partition

UtkarshGupta said:
Try a pit file.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
could u be more precise ? cuz i tried at first flashing with a pit and bootloader, csc, modem, code

nabilbek said:
could u be more precise ? cuz i tried at first flashing with a pit and bootloader, csc, modem, code
Click to expand...
Click to collapse
Did you try the method i mentioned using the note 2 toolkit. You need to have a customer recovery and bootloader to install certain thinkgs. Try the noet 2 toolkit and follow the instructions i sent you. This should fix it.

Put stock rom in pda and pit in partition and check repartition.
Then hit start
this is XXXDDDAAA

nothing solved it ... sent it to samsung they fixed it. they said they changed the internal memory and an ic ...

[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] "Kernel is not seandroid enforcing" :(

I have PayPal for which I will use to donate an amount to the person(s) who can help me.
I just recently got a new GS4 becuase of an insurance replacement. I looked at the specs before I flashed TWRP. After failing to install 4.2.2 ROMS, I finally found a 4.3 mk2 stock ROM to install. I have the phone working. But TWRP is not installed. My phone tests positive for ROOT with Rootchecker
Currently I'm getting this message everytime I boot "Kernel is not seandroid enforcing"
I have multiple 4.4.2 and 4.3 ROMs I like to use on my SD card, I'd like to continue from a TWRP backup i've made using that recovery.
Here are my current specs:
Model
SGH-M919
Android Version
4.3
Baseband
M919UVUEMK2
Kernel Version
[email protected] #1
Build Number
JSS15J.M919UVUEMK2
SELinux status
Permissive
Secure boot status
Type: Samsung

The replacement phone was probably already on the MK2 bootloader and modem when you received it. Which means you had Knox pre-installed and tripped it when you rooted the phone. The "kernel is not seandroid enforcing" error message does not affect the functioning of your phone in any way. It's just a part of the Knox bootloader. You can continue to re-install TWRP recovery and flash any ROM you want. Your phone will function as normal. Just don't try reverting to the 4.2.2 MDL baseband/modem because it won't work. There's currently no way to revert to 4.2.2 MDL if you're on MK2 or higher. If you want to get rid of the message just flash the stock kernel in a recovery.
Try to be careful with your replacement phone now since you tripped Knox. It might be harder to get a replacement depending on how T-Mobile is.
No donations are needed for these kinds of things.

Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Did I miss a step? All my actions were using odin to flash the twrp recover, and then flash another ROM, or restoring a Previous Back. Should I have flashed a rooted bootloader, or rooted firmware or anything besides those two?

nopotential said:
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Click to expand...
Click to collapse
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.

brian117 said:
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
Click to expand...
Click to collapse
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?

nopotential said:
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
Click to expand...
Click to collapse
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.

brian117 said:
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Chain's Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
Click to expand...
Click to collapse
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.

nopotential said:
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
Click to expand...
Click to collapse
Like I said donations are not needed. It does take a while for it to flash through Odin so that's normal.

It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.

nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous

nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
nopotential said:
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
Click to expand...
Click to collapse
If you continue to have WiFi problems, flash this via recovery.

brian117 said:
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
If you continue to have WiFi problems, flash this via recovery.
Click to expand...
Click to collapse
It looks like everything is looking good by following your list. Thank you.

nopotential said:
It looks like everything is looking good by following your list. Thank you.
Click to expand...
Click to collapse
Awesome! Good to hear man. Enjoy KitKat and the newest modem. The new modem has gave a significant reception boost for a lot of people. Hope it's the same for you. And please check your PM.

-Deleted-

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

SGH-I747 Samsung S3 stuck at samsung logo screen

Hello
I have been doing a bunch of reading to figure out what I did and how to fix it. I have a Samsung S3 SGH-I747 and had philz touch installed and was running the custom cyagogenmod rom 12.1 but was having trouble with the screen going black during phone calls and wanted to fix this.
I did some more reading and found out that a fix for this was updating the modem. I then proceed to SamMobile and grabbed the firmware for my phone and proceed to install it using ODIN. I didn't notice that I grabbed the wrong firmware (I747M) instead of (I747). Odin said everything installed properly so the phone rebooted and now It looks like I installed the stock rom (which I wasn't trying to do but oh well). The phone hangs on the samsung logo screen now.
The phone will boot into download mode
The phone will boot into the stock recovery, I lost my philz touch.
I am not sure what to do now to get the phone working again? Is it soft bricked? I don't think it Hard bricked.
Can anyone point me in the correct direction?
I was thinking I should grab the correct firmware and try installing that via ODIN again?

Which rom did you flash?

I flashed the firmware from SamMobile which is 4.4.2 but for 747M not 747. I accidentally grabbed the wrong one.

Boot into recovery and wipe data/factory reset, wipe cache, and reboot.

audit13 said:
Boot into recovery and wipe data/factory reset, wipe cache, and reboot.
Click to expand...
Click to collapse
I will try that this evening, thanks.
I will let you know how it goes.

If you were able to flash an i747m ROM onto an i747 with everything working, that would be great as you won't have to worry about using different methods to get back to a stock ROM because all you have to do is flash with Odin.

audit13 said:
If you were able to flash an i747m ROM onto an i747 with everything working, that would be great as you won't have to worry about using different methods to get back to a stock ROM because all you have to do is flash with Odin.
Click to expand...
Click to collapse
Boot into recovery and wipe data/factory reset, wipe cache, and reboot.
I want to clarify a bit.
When I get home I will turn phone on and wipe those two thing then just let the phone reboot?
I never got into the operating system after I did the flash.
I also noticed that all my cyanogenmod flashy screens were gone during boot-up.

Yes, boot directory into recovery, wipe those two items, then select reboot system from stock recovery.
The CM screens are gone because they have been overwritten with the stock Samsung boot logos, pictures, animations, and sounds.

audit13 said:
Yes, boot directory into recovery, wipe those two items, then select reboot system from stock recovery.
The CM screens are gone because they have been overwritten with the stock Samsung boot logos, pictures, animations, and sounds.
Click to expand...
Click to collapse
Yes that worked, my phone is up and running, Thank-you.
Now I would like to install a custom ROM again but want the modem fixed.
The fact that I have did a firmware install would that mean the modem has been updated?
Or do I need to install a recovery, custom rom, gapps and modem files?

i'm not sure if sammobile firmware includes modem. excuse me @ arthur and @ pet , if you ; @PowerjacK15 dont already know your bootloader and modem version (if you do just ignore this post) may want to download this app
http://forum.xda-developers.com/showthread.php?t=2609045
"samsung info" to find out. i think ¿ starting with 4.4.2 they are suppose to match. and i believe (maybe @audit13 knows better) , but enewman used to have a thread with bootloader/modem flashable zips. makes it much easier (for me it did anyway).
anyway just a thought. good luck.
"err on the side of kindness"

What is wrong with the modem? No signal, no data, and/or wifi?
The i747m modem should give you LTE on att as Rogers, bell, and Telus in Canada support the same frequencies as att.

I was having trouble with the phone screen going black when making calls. A few threads mentioned that updating the firmware for the modem fixes this problem.

audit13 said:
What is wrong with the modem? No signal, no data, and/or wifi?
The i747m modem should give you LTE on att as Rogers, bell, and Telus in Canada support the same frequencies as att.
Click to expand...
Click to collapse
I also want to switch to a custom rom like cyanogenmod or slimkat. I may not be going about it the right way. But I thought if I updated the firmware from SAMmobile it would fix the modem then I could proceed with installing a recovery and ROM.

During a call, the screen goes black when you put the phone to your ear? When you remove the phone from your ear, does the screen light up? If the answer is yes to both questions, there is nothing wrong with the modem.
Does the phone function properly? If not, I recommend resolving these issues before moving to a custom rom as not all custom ROMs work well with i747m or i747.

No when I make a call using the cyanogenmod the screen went black and stayed black until call ended. It didn't matter if the phone was near my ear or laying flat it stayed black. Other than that one issue the custom ROM worked perfectly.

Does the screen work properly with the stock ROM? What is the baseband (last 4 characters) on the phone? Baseband can be found under settings.

Yes the phone works properly with the stock ROM that I installed yesterday. I will have to check tonight and see what the baseband is on the phone. thanks for helping me understand this.

The baseband will help determine what can and can't be flashed to the phone. Since you flashed a stock i747m ROM, the baseband will also reveal the bootloader.

The baseband is I747MVLUFOB3

Looks like you successfully converted an i747 to an i747m which is a good thing IMHO. To confirm this, boot into recovery and you should see FOB3 somewhere on the recovery screen.
If you want a custom ROM, do this:
1) download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=j...07763241,d.dmo
2) download the tar version of TWRP 2.8.7.0 from here: https://dl.twrp.me/d2att/
3) download the latest cm12.1 for the phone from here ( http://www.cmxlog.com/12.1/d2att/) and save it to a micro SD card;
4) download the version of cm12.1 gapps you want from here (https://wiki.cyanogenmod.org/w/Google_Apps) and save it to the same sd card where you saved CM12.1;
5) place the micro SD card into the phone;
6) boot the phone into download mode;
7) open Odin 3.07 and uncheck everything except f. reset time;
8) click on PDA and browse to the tar TWRP file and select it;
9) connect the phone and it should show up as a com port in Odin;
10) flash TWRP;
11) when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
12) perform a full wipe of system, data, and cache;
13) flash CM12.1 and gapps from the micro SD card;
14) reboot and enjoy