Develop Bugs

Can't reach other recovery than android system recovery3e

Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
Anyone can help me ? Thank's
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2

Revert back to recovery problem
hazzel said:
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
Anyone can help me ? Thank's
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Click to expand...
Click to collapse
Having same issue with SGH-T889. Any help? Heard of similar issue with Nexus 4. They have revert recovery disabler. Not tried on my Note 2. Is similar solution available for T889?

After flashing recovery in Odin are you booting up the phone (or is odin - i.e. auto reboot is checked)? There is a file (/system/etc/install-recovery.sh) that you need to disable to have recovery "stick". There are a few ways to do this, but my preference has been to do it within cwm/twrp recovery via adb after flashing in odin but prior to first bootup of phone.
Hope that helps!

Ive had luck un-checking auto-reboot in odin, flashing recovery, wait for it to say pass, unplug USB, pull battery, and boot straight into recovery by holding home + vol up when powering on.
This can be dangerous so make sure odin is completely done before unplugging.
Sent from my GT-N7105 using Tapatalk 2

^^ this

same prob
hazzel said:
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Click to expand...
Click to collapse
I have the same problem :/ i tried going back to odin and unchecking auto root as suggested, but whenever i clicked start it just stayed stuck at "Setup Connection" or whatever... i'm trying to install a custom rom and i just cant access CMW! I have the AT&T model by the way.

Nintendoassasin64 said:
I have the same problem :/ i tried going back to odin and unchecking auto root as suggested, but whenever i clicked start it just stayed stuck at "Setup Connection" or whatever... i'm trying to install a custom rom and i just cant access CMW! I have the AT&T model by the way.
Click to expand...
Click to collapse
I know you can't access CWM Recovery..
Allot of us use TWRP Recovery and it works great. I think it is safe to say it is a Superior Recovery now. I suggest you use that Recovery.
You can get it installed easily by downloading GooManager from the play store, opening the app, hit your menu button and tap Install Open Recovery Script. That's it. Quick and easy!

For the people having a hard time, are you rooted? If you are just download goomanager and use it to install twrp
Sent from my SGH-T889 using xda app-developers app

Finally got fixed
I tried by un ticking the "Reboot" in Odni and manually pulled out battery and cable and tried Recovery mode... it went smoothly as expected... thanks dude

This works when everything else fails!
dj_spore said:
Ive had luck un-checking auto-reboot in odin, flashing recovery, wait for it to say pass, unplug USB, pull battery, and boot straight into recovery by holding home + vol up when powering on.
This can be dangerous so make sure odin is completely done before unplugging.
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Been looking for a solution for hours and the android system recovery was feeling like a thorn in the foot that will never go away. But surprise, surprise, your simple suggestion did the trick!
Thanks a ton!! :good:

stock retrival not possible from Cyanogenmod 11 on Samsung Galaxy Grand duos

I own a Samsung Galaxy Grand duos GT - I9082, running on CM 11, PHILZ 6.0.4.5 Recovery, I used Solo launcher as default, now its not getting out of it,My concern is now I am not able to go to stock, I have tried flashing JB 4.1.2 tar.md5 file thru odin 3.07, One thing I am noticing while flashing in odin is it says not responding until the file appears in the pda box, after that every thing works fine, pass msg comes on the screen, but after that it re-boots to the same CM 11, I have also tried doing factory reset, cache & dalvik cache wipe after the flashing, but it never comes back to stock. I am even trying to flash the selinux support recovery, but the same thing happens, after odin pass msg, if i check the recovery its the same PHILZ 6.0.4.5 Recovery. I am really worried that has my phone been bricked.
I have even tried doing format/system, factory reset, cache & Dalvik wipe. usb debugging is selected in the developer section. Can i get the original stock flashed from the samsung ? pls help asap, thank you.

Strange. Have you tried flashing stock 4.2.2?

naufalhadyan said:
Strange. Have you tried flashing stock 4.2.2?
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------------------
yeah but in vain, same prob exists ?

nandaleo72 said:
---------------------------------------------------------------------------------------------------------------------------------------
yeah but in vain, same prob exists ?
Click to expand...
Click to collapse
If you still can't get to stock it means Odin hasn't even downloaded the firmware into the device. Could be hardware problem (check your USB cable) driver installation (make sure you installed the drivers correctly) or you simply didn't follow the correct procedure.
http://forum.xda-developers.com/showthread.php?t=2616816
Btw, it helps if you manage to post a screenshot of what's written in Odin's log box and post it here...

cm
naufalhadyan said:
If you still can't get to stock it means Odin hasn't even downloaded the firmware into the device. Could be hardware problem (check your USB cable) driver installation (make sure you installed the drivers correctly) or you simply didn't follow the correct procedure.
http://forum.xda-developers.com/showthread.php?t=2616816
Btw, it helps if you manage to post a screenshot of what's written in Odin's log box and post it here...
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
png attached, I also wld like to add that in my download mode, it says current bin as custom & system status as official, whereas I am on CM 11

nandaleo72 said:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
png attached, I also wld like to add that in my download mode, it says current bin as custom & system status as official, whereas I am on CM 11
Click to expand...
Click to collapse
Now that is really weird... :/ I don't know how to solve it, sorry. Looking at Odin's logs, it's supposed to flash correctly. Maybe someone more knowledgable than me can help?

cm
naufalhadyan said:
Now that is really weird... :/ I don't know how to solve it, sorry. Looking at Odin's logs, it's supposed to flash correctly. Maybe someone more knowledgable than me can help?
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
can u tell me how can i post the same to pawitp

I can suggest one thing only
Format /system and /data first from Philz and then try flashing it
Sent from my GT-I9082 using Tapatalk

CM 11
akiratoriyama said:
I can suggest one thing only
Format /system and /data first from Philz and then try flashing it
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------
I have done that also, first format sys/data & cache wipe via philz, and flashed ,same result, the strangest part is its not even accepting zipping of the delta's of CM 11 by pawitp., pls help or else need to go to the service centre samsung 2morrow

nandaleo72 said:
------------------------------------------------------------------------------------------------------------------------------
I have done that also, first format sys/data & cache wipe via philz, and flashed ,same result, the strangest part is its not even accepting zipping of the delta's of CM 11 by pawitp., pls help or else need to go to the service centre samsung 2morrow
Click to expand...
Click to collapse
I have never ever seen such strange problem in the 1.5 yrs of my XDA years
Something is telling me that the system partition is not writable (hence not accepting delta file?)
Can you try to copy a file to /system partition ?
I think you may need to flash a .PIT file
@k2wl @iceyhotguy kindly provide your suggestions
Sent from my GT-I9082 using Tapatalk

I am finding one prob while doing factory reset, it says E : unknown volume for path [ sd-ext], what does this suggest ?

nandaleo72 said:
I own a Samsung Galaxy Grand duos GT - I9082, running on CM 11, PHILZ 6.0.4.5 Recovery, I used Solo launcher as default, now its not getting out of it,My concern is now I am not able to go to stock, I have tried flashing JB 4.1.2 tar.md5 file thru odin 3.07, One thing I am noticing while flashing in odin is it says not responding until the file appears in the pda box, after that every thing works fine, pass msg comes on the screen, but after that it re-boots to the same CM 11, I have also tried doing factory reset, cache & dalvik cache wipe after the flashing, but it never comes back to stock. I am even trying to flash the selinux support recovery, but the same thing happens, after odin pass msg, if i check the recovery its the same PHILZ 6.0.4.5 Recovery. I am really worried that has my phone been bricked.
I have even tried doing format/system, factory reset, cache & Dalvik wipe. usb debugging is selected in the developer section. Can i get the original stock flashed from the samsung ? pls help asap, thank you.
Click to expand...
Click to collapse
nandaleo72 said:
I am finding one prob while doing factory reset, it says E : unknown volume for path [ sd-ext], what does this suggest ?
Click to expand...
Click to collapse
The delay in Odin, or the stopped responding moment, like you mentioned is from the md5 check Odin performs to make sure the firmware is valid. And the sd-ext partition is something that isn't used anymore since JB, nothing to worry about we all get that warning when we wipe in recovery.
Sadly, it's hard to tell what could be wrong, or what you could be doing wrong, just from the problem. But the main thing is, phone is always recoverable, just make sure your data is safely backed up on your computer.
If you haven't already taken your phone into the service center, can you list each and every step you are taking to revert to stock? And I do mean, each step, even boot into recovery, boot into download mode, flashed this recovery/firmware etc, more the details, the better. This way me or other members can analyze more accurately what could be the possible problem.

where can i find this .pit file it's of cm 11 or.........?

It's always better practice to have a recovery before trying things that may ruin your precious time.......
Look for stock files for your smartphone galaxy grand ..... Put files sometimes comes within that file or you have to find it manually by googling...... ?????
Sent from my Nexus 7 using XDA Premium HD app

CM 11
can u suggest any of the knowledgable senior member to solve this problem, bcoz I luv my SGG.

Thank u so much for the concern shown. I have regularly been switching b/w roms [ stock & custom ], my favorites are cm & carbon, i have used recoveries of chotu CWM-TOUCH & Philz touch both ver. 5.15 & cwm - selinux support, now i am on 6.0.4.5. I am running CM 11 now. launcher is solo kikat. I have done nandroid backup of all Roms, I have tried the restore option from clockwokmod / backups, not working out. I am using the following procedure to revert to stock :
1. check debug mode in developer mode
2. to the download mode by pressing volume key downwards & power key & home button at same time wait for the logo to appear, Followed by ODIN Mode, & then press the vol button upwards.
3. open odin, i have a version of 3.07, check only Auto Reboot & F. Reset Time, nothing else, clicking on the PDA, selecting the 4.1.2 I9082XXAMC7_I9082OJVAMC1_I9082XXAMC4_HOME.tar.md5 file, and pressing start.
4. normally doing a factory reset & cache wipe & re-boot.
hope, i am following the procedure properly, not yet given the handset to samsung service, pls help me out, thnk u once again, pls reply asap.

CM 11
iceyhotguy said:
The delay in Odin, or the stopped responding moment, like you mentioned is from the md5 check Odin performs to make sure the firmware is valid. And the sd-ext partition is something that isn't used anymore since JB, nothing to worry about we all get that warning when we wipe in recovery.
Sadly, it's hard to tell what could be wrong, or what you could be doing wrong, just from the problem. But the main thing is, phone is always recoverable, just make sure your data is safely backed up on your computer.
If you haven't already taken your phone into the service center, can you list each and every step you are taking to revert to stock? And I do mean, each step, even boot into recovery, boot into download mode, flashed this recovery/firmware etc, more the details, the better. This way me or other members can analyze more accurately what could be the possible problem.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thank u so much for the concern shown. I have regularly been switching b/w roms [ stock & custom ], my favorites are cm & carbon, i have used recoveries of chotu CWM-TOUCH & Philz touch both ver. 5.15 & cwm - selinux support, now i am on 6.0.4.5. I am running CM 11 now. launcher is solo kikat. I have done nandroid backup of all Roms, I have tried the restore option from clockwokmod / backups, not working out. I am using the following procedure to revert to stock :
1. check debug mode in developer mode
2. to the download mode by pressing volume key downwards & power key & home button at same time wait for the logo to appear, Followed by ODIN Mode, & then press the vol button upwards.
3. open odin, i have a version of 3.07, check only Auto Reboot & F. Reset Time, nothing else, clicking on the PDA, selecting the 4.1.2 I9082XXAMC7_I9082OJVAMC1_I9082XXAMC4_HOME.tar.md5 file, and pressing start.
4. normally doing a factory reset & cache wipe & re-boot.
I am also finding that when I try to install any zip from sdcard1 thats my expandable memory slot in philz touch 6.0.4.5 it says E: can't open/storage/sdcard1/cm-10.1-20130412-unofficial-i9082.zip (bad) installation aborted any reasons & also png attached, I also wld like to add that in my download mode, it says current bin as custom & system status as official, whereas I am on CM 11
hope, i am following the procedure properly, not yet given the handset to samsung service, pls help me out, thnk u once again, pls reply asap.

I have made a thread on how to unroot and revert to stock. You can find it here: http://forum.xda-developers.com/showthread.php?t=2639894 . hope this piece of information helps you...

nandaleo72 said:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thank u so much for the concern shown. I have regularly been switching b/w roms [ stock & custom ], my favorites are cm & carbon, i have used recoveries of chotu CWM-TOUCH & Philz touch both ver. 5.15 & cwm - selinux support, now i am on 6.0.4.5. I am running CM 11 now. launcher is solo kikat. I have done nandroid backup of all Roms, I have tried the restore option from clockwokmod / backups, not working out. I am using the following procedure to revert to stock :
1. check debug mode in developer mode
2. to the download mode by pressing volume key downwards & power key & home button at same time wait for the logo to appear, Followed by ODIN Mode, & then press the vol button upwards.
3. open odin, i have a version of 3.07, check only Auto Reboot & F. Reset Time, nothing else, clicking on the PDA, selecting the 4.1.2 I9082XXAMC7_I9082OJVAMC1_I9082XXAMC4_HOME.tar.md5 file, and pressing start.
4. normally doing a factory reset & cache wipe & re-boot.
I am also finding that when I try to install any zip from sdcard1 thats my expandable memory slot in philz touch 6.0.4.5 it says E: can't open/storage/sdcard1/cm-10.1-20130412-unofficial-i9082.zip (bad) installation aborted any reasons & also png attached, I also wld like to add that in my download mode, it says current bin as custom & system status as official, whereas I am on CM 11
hope, i am following the procedure properly, not yet given the handset to samsung service, pls help me out, thnk u once again, pls reply asap.
Click to expand...
Click to collapse
I was curious if this problem wasn't with what you were doing but with kitkat ROMs, so I looked through XDA and found people having similar issues. Apparently downgrading to JB from KitKat CM is an issue for a lot of users with Samsung phones.
Try this,
1.Go to your recovery, Wipe data/cache and dalvik cache. Format /system under Mounts and Storage.
2. Download and flash a 4.2.2 based stock based ROM (like GENNXT or any you want), this would bring you back on 4.2.2 kernel and stuff, so let it boot up completely.
3. Just to be sure, flash 4.2.2 based recovery with Odin from here - http://forum.xda-developers.com/showthread.php?t=2315529
I honestly don't think recovery should make any difference, but I noticed a thread where the user said it was so just be sure. Then reboot back into recovery, and wipe data/cache and dalvik.
4. Go to download mode, use Odin to flash your 4.1.2 firmware, after it passes, boot into recovery (it should be stock recovery now), clear data and cache and reboot.
I think the problem is arising from all the new SE Linux support in KitKat, so a gradual downgrade should work. You can add a step of flashing 4.2.2 firmware after booting up stock based ROM but shouldn't be needed.
Let me know how it goes.

not working out ?

[Q] SOFT BRICKED! and can't FLASH STOCK ROM on S3 AT&T

Before I started here is tech infomation I do know.
Model: SGH-I747 (Samsung Galaxy S3 for At&t)
OS before bricked: kitkat 4.4.2
Rooted: Yes
Recovery: Clockworkmod v.6.0.4.7/Phiz touch 6
Bootloader: "I have no clue." Help me find?
Alright so basically how I got soft-bricked or bricked was because I deleted everything in the system. I think I wiped it somehow, I don't know thought I was just factory resetting. Then I flashed a custom rom via cwm recovery from my sdcard.
Quick question also, does cwm "Install from zip" option mean to "flash" from? Anyways, I am pretty new to all this techical stuff so don't judge me.
I then download a stock rom from "other places-sorry totally forgot where" and tried flashing it from inside cwm and it fails. I found a .tar stocked rom file and tried it with Odin 3.07 of course with my phone in download mode.
Oh yes and when I put it in download mode the info writes:
Odin Mode
Product Name: SGH-I747
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit: 1
Bootloader RP Swrec: 3
"
This is my first time, doing all of this so I wouldn't know what these mean. Furthermore, when I try flashing any of the stock rom for my SGH-I747 with Odin v3.07 it always "FAIL" to succed.
Other than that my phone obviously has no os but I can't still run "Recovery mode" and "Download Mode" except that everything I do never is a success.
ALSO I HAVE TRIED THIS THREAD AND IT DIDN'T HELP EITHER: http://forum.xda-developers.com/showthread.php?p=53572812#post53572812
AND THESE ROMS JUST DON'T WORK, I DOWNLOAD THEM BUT THEY STOPPED 3/4 OF THE WAY GIVING ME A CORRUPTED FILE? I TRIED DOWNLOAD 4 TIMES: http://stockroms.net/file/GalaxyS3/SGH-I747
Please anyone, any of the devs member help me! I Really need to fix this issue! I just want back my stock rom.
If anyone has any other questions, just reply to this post. Thank you so much!

Do not flash anymore ROMs using Odin until you know the bootloader version on your phone.
To quickly get your phone up and running, I recommend doing this:
download the latest CM11 from here and save it to your external sd card: https://download.cyanogenmod.org/?device=d2lte
download CM11 Gapps from here and save it to your external sd card: http://wiki.cyanogenmod.org/w/Google_Apps
download the latest tar.md5 version of Philz Touch for the d2lte from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
place SD card into the phone;
open Odin 3.07, uncheck everything except f.reset time, flash Philz to your phone, remove the USB cable when you see the word "reset" in the status window, remove battery, replace battery, boot into recovery, wipe data partition, cache partition, and Dalvik, flash CM11, flash Gapps.

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

galaxy note 4 SM-N910P won't flash any ROm file

HI Please i have this ERROR ON mY N910p it wont flash any custom or stock firmware i don't know what to do . my Note 4 can't boot in to recovery mode. it boots at times and goes off after but in the download mode it boots well and it show the error in the images on Odin and on my phones screen ..i have tried soo many tricks but yet it didn't work .i'm confuse please some one should help me get back my N910p to Life please

If you're trying to flash a ROM from the stock recovery, that could be one of your issues. You would need to have a custom recovery like TWRP in order to flash from recovery.
As for using ODIN to flash a stock ROM, make sure you have the correct drivers installed to your computer before attempting to flash anything. Make sure you are choosing the correct slot in ODIN to load your .tar file as well. I've never seen eMMC errors in download mode before but that doesn't look good. I'm not that knowledgeable about Android phones yet to be able to troubleshoot very many issues.

johnwiz said:
HI Please i have this ERROR ON mY N910p it wont flash any custom or stock firmware i don't know what to do . my Note 4 can't boot in to recovery mode. it boots at times and goes off after but in the download mode it boots well and it show the error in the images on Odin and on my phones screen ..i have tried soo many tricks but yet it didn't work .i'm confuse please some one should help me get back my N910p to Life please
Click to expand...
Click to collapse
Flash this QI5 firmware it will flash without errors because as i can see "fuse 5 binary 4" means you are on QI5 BL/BB so you cannot flash older firmware because its locked bootloader/baseband.
Must do factory reset from stock recovery after finish flashing.
https://androidfilehost.com/?fid=674106145207497529

Trex888 said:
Flash this QI5 firmware it will flash without errors because as i can see "fuse 5 binary 4" means you are on QI5 BL/BB so you cannot flash older firmware because its locked bootloader/baseband.
Must do factory reset from stock recovery after finish flashing.
https://androidfilehost.com/?fid=674106145207497529
Click to expand...
Click to collapse
First of all thanks for your reply.. I just flashed the QI5 firmware but the phone is rebooting in to recovery Mode without sucess .. it is just going to recovery and after some fewer second it goes off and on again .. i have tried to install the QE1 but it cant flash it gives me the error on the image below..please assist me solve this problem...Thanks in advance
i taught it was a mother board problem but now that it has flashed the Qi5 firmware i have a Hope ..Help me please

Psilocelium said:
If you're trying to flash a ROM from the stock recovery, that could be one of your issues. You would need to have a custom recovery like TWRP in order to flash from recovery.
As for using ODIN to flash a stock ROM, make sure you have the correct drivers installed to your computer before attempting to flash anything. Make sure you are choosing the correct slot in ODIN to load your .tar file as well. I've never seen eMMC errors in download mode before but that doesn't look good. I'm not that knowledgeable about Android phones yet to be able to troubleshoot very many issues.
Click to expand...
Click to collapse
thanks for your reply .. yes it is the correct firmware ..i saw in one post that it is due to the fact that i have updated to a firme with E-fuse protection ..i just flashed the Qi5 firmware but it bootloops .. it can't start corectly ...its just rebooting and the phone goes off after some secondes ..im confuse but i have Hope ..help me thanks

Did you flash the QI5 firmware and then do a factory reset right away from stock recovery like Trex888 said to do?
So it bootloops and then powers off completely by itself after a few seconds?

johnwiz said:
First of all thanks for your reply.. I just flashed the QI5 firmware but the phone is rebooting in to recovery Mode without sucess .. it is just going to recovery and after some fewer second it goes off and on again .. i have tried to install the QE1 but it cant flash it gives me the error on the image below..please assist me solve this problem...Thanks in advance
i taught it was a mother board problem but now that it has flashed the Qi5 firmware i have a Hope ..Help me please
Click to expand...
Click to collapse
Do a wipe data factory reset & wipe cache then reboot system.
If that doesn't work then follow this steps and be patient.
1,downloaf twrp recovery for n910p
2 open odin options and uncheck autoreboot (MUST USE ODIN 3.10 OR HIGHER)
3 choose AP TAB and choose twrp
4,connect device to pc in download mode
5,hit start
6,once twrp flashed remove battery and insert again
7,boot into twrp by 3 button combo
8,go to wipe/advance wipe/choose (dalvic cache+data+system+cache+internal storage) you have to wipe 7 times .
9,now go to odin again and choose AP and choose QI5 firmware.
10,go to odin options and check on "nand eraseall" & "re partition"
11,connect device in download mode & hit start.
Once flashed go to stock recovery and do factory reset.
12,Reboot and wait 10 to 15 min.
Done
TWRP LINK
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar

Trex888 said:
Do a wipe data factory reset & wipe cache then reboot system.
If that doesn't work then follow this steps and be patient.
1,downloaf twrp recovery for n910p
2 open odin options and uncheck autoreboot (MUST USE ODIN 3.10 OR HIGHER)
3 choose AP TAB and choose twrp
4,connect device to pc in download mode
5,hit start
6,once twrp flashed remove battery and insert again
7,boot into twrp by 3 button combo
8,go to wipe/advance wipe/choose (dalvic cache+data+system+cache+internal storage) you have to wipe 7 times .
9,now go to odin again and choose AP and choose QI5 firmware.
10,go to odin options and check on "nand eraseall" & "re partition"
11,connect device in download mode & hit start.
Once flashed go to stock recovery and do factory reset.
12,Reboot and wait 10 to 15 min.
Done
TWRP LINK
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Click to expand...
Click to collapse
THanks ... i will do that right Now and will tell you the result

for anyone not new to rooting , unbricking, stock flashing , twrp , etc ive had this very same problem after nights of screaming and confusion cause i KNOW im doing everything correct .. exact problems as lots have had here .. i replaced my cord with a cheap gas station android cord and borrowed a friends battery that was only a few days old .. and everything worked as it should .. moral of this story .. i assumed my hardware was fine cause independently both worked fine .. but for whatever reason it just wasnt good enough to flash stock FW problem solved .. it only took me a month to come to this amazing discovery (-_-) hope this helps someone ...... SM-N910P