Database Develop

[GUIDE][ SCH-I705 ] Back to Stock - Relock, Unroot

Return your SCH-I705 back to factory stock (minus flash counter)
Flash these in ODIN 3.04
DO NOT CHECK RE-PARTITION, FLASH LOCK, OR LED CONTROL
ALL ANDROID VERSIONS ARE 4.1.2
VRBLL2
I705VRBLL2_I705VZWBLL2_VZW.zip
VRBMI1
I705VRBMI1_I705VZWBMI1_VZW.zip
Unfortunatley, I don't know of a way to reset the flash counter. Triangle Away may do it, and the manual method for resetting it on the Galaxy S3 may do it, but I've not confirmed nor do I want to try.
Don't forget to hit the thanks button!

I might want this one.

Is there a known way to go back to the rooted unlocked tab?

Yep. Just flash one of the stock rooted Odin system images in the root unlock recovery thread, then flash the aboot (bootloader)
Basically following the instructions like you would if you just bought the tablet.
Sent from my SCH-I535 using XDA Premium HD app

Triangle Away shows the correct flash counter on my tablet, so I'm going to assume it works, but no proof. I've sent chainfire a PM asking a couple questions and hopefully we'll have an answer

Updated links in OP.

BigBot96 said:
Return your SCH-I705 back to factory stock (minus flash counter)
Flash these in ODIN 3.04
DO NOT CHECK RE-PARTITION, FLASH LOCK, OR LED CONTROL
ALL ANDROID VERSIONS ARE 4.1.2
VRBLL2
I705VRBLL2_I705VZWBLL2_VZW.zip
VRBMI1
I705VRBMI1_I705VZWBMI1_VZW.zip
Unfortunatley, I don't know of a way to reset the flash counter. Triangle Away may do it, and the manual method for resetting it on the Galaxy S3 may do it, but I've not confirmed nor do I want to try.
Don't forget to hit the thanks button!
Click to expand...
Click to collapse
Quick question. Can I perform this return to stock process on my tablet or do I need computer?

jshawjr said:
Quick question. Can I perform this return to stock process on my tablet or do I need computer?
Click to expand...
Click to collapse
Computer with ODIN. Don't use Mobile ODIN as the locked bootloader will brick you. Either way you may not be able to use these depending on what version you're on.

BigBot96 said:
Computer with ODIN. Don't use Mobile ODIN as the locked bootloader will brick you. Either way you may not be able to use these depending on what version you're on.
Click to expand...
Click to collapse
That's good to know about ODIN. I am currently on Android Version 4.1.2 "DoubleShoot ROM", by Dr. Hyde. Will it work on thiss version?

WTF
So I was rooted and customized all except twrp and used flashify to flash twrp 2.8.7.0 and all the sudden i GET Verizon wireless has detected un...blahblah blah please take to a vedrizon store..... WTF is this and why in the heck do I have it comming up after root and everything???and now what?? I think just re flash stock recovery with 3.04 odin right?

nope its ir bootloader sorry man reflash to stock

[SOLVED] Bricked i9305? - No Recovery - "Get PIT for mapping" stuck - sboot.bin FAIL

[SOLVED] Bricked i9305? - No Recovery - "Get PIT for mapping" stuck - sboot.bin FAIL
Yo.
Basically been using this phone for ages, having random freezing issues for a while, so I decided to /****it and re-stock everything because it is likely that I have been an idiot with kernels/messing around with stuff once.
This freezing has persisted through stable, unstable, nightly CM 10.2/10.3/11 ROM's as well as pure stock and unrooted, so I figured it was something deeper down - the kernel, and I got a stock kernel for i9305 (attached). Everything basically went to ****, the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
No biggie, I'll just ODIN it up (3.0.7) and flash the stock firmware, except now (this did not happen before the kernel flash) it simply fails with "sboot.bin FAIL", which people claim to be a PIT error (Kies not open btw, no KiesTrayAgent either, it's on the PC though), so I grab a i9305 stock PIT that I try and flash with the stock firmware, except now it gets stuck at "Get PIT for mapping" and never moves onwards from there.
So I'm essentially stuck with a problem that can probably be fixed by a stock firmware ODIN flash, and a problem that prevents me from fixing the PIT stuff to get the stock firmware through.
I have tried ODIN-flashing CWM recovery as well as stock recovery (also attached), but I'm still stuck on the logo regardless.
Any help here? Kinda lost ATM.
EDIT: Can't link/attach the .rar with the files. :S

Just re-install your back up

Raistlin1158 said:
Just re-install your back up
Click to expand...
Click to collapse
Retarded answer.
@OP
We need more data... first, which kernel did you flash ? If you can't attach it, link to it.
Second, what stock rom did you try to flash ?
Third, are you knoxed?

Hey guys.
Cheers for the answers, I just figured it out though actually. The sboot.bin error was caused by some bootloader-stuff-thingy I could hardly explain if I got a book on it. I got ahold of another stock ROM which flashed fine, I cleaned up and all that (NAND erase all did the job), back to CM11 as TouchWiz didn't fix my problems.
To answer your questions (others might have the problem and find this thread):
http://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-odin-flashable-tar-t1971265 <- kernel
I tried to flash an "XXBMD1" stock ROM from SamMobile, it had worked previously.
I am Knoxed and have "tripeed the fuse" (trying to fix the crashing issues I went back to stock ROM, then it prompted for the 4.3 TouchWiz update which brings KNOX), so I'm without warranty (ODIN returns "KNOX Warranty Void: 1), but I guess I can consider this a learning experience as everything turned out good enough in the end.

There you go:
Based on JellyBean 4.1.2_XXBMD1 <--- You can't flash 4.1.2 because of the knox bootloader.
Had you tried a stick 4.3 you might have been sucessfull

daedric said:
Retarded answer.
Click to expand...
Click to collapse
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr

Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
soft bricks aren't fixed by restoring nandroids.

Update odin and change usb cable and port.

Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
chongc1996 said:
soft bricks aren't fixed by restoring nandroids.
Click to expand...
Click to collapse
A nandroid wouldn't do any harm as soon as he got a recovery working
Raistlin1158 said:
Update odin and change usb cable and port.
Click to expand...
Click to collapse
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]

daedric said:
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
A nandroid wouldn't do any harm as soon as he got a recovery working
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]
Click to expand...
Click to collapse
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved

.... the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
Click to expand...
Click to collapse
chongc1996 said:
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved
Click to expand...
Click to collapse
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.

daedric said:
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.
Click to expand...
Click to collapse
ok sir, you are right, calm down, I'm out of here.

Cheers for the helpful as well as not-so-helpful responses, all back up and running now.

NG2 update.zip file

For anyone who doesn't wanna wait for the OTA to hit your phone (because some phones might take awhile) just download this file and place it on your EXTERNAL SD CARD and then power off your phone and boot into stock recovery and apply update from external sd card.
You must be on unrooted stock NAE ROM and stock recovery to take the OTA update.
Also if your phones fails to update the baseband then just use Odin to flash the MK2 modem and then reflash the NAE modem and take the OTA again (that worked for me)
https://www.dropbox.com/s/1u83mpbu2j18qbp/Update.zip

Also you might need a computer to place the file on your external sd card because of the "Write to sd card issue" that was introduced in the Kitkat update.

I am rooted and i want this update.... How to do that?

Are you on stock recovery? What is your full setup and what mods do you have installed?

Worked perfectly. Updated baseband as well.
I was able to move the zip from internal memory to SD card using the stock My Files app as well.
Thanks @churchey360

buzzwyzr said:
Worked perfectly. Updated baseband as well.
I was able to move the zip from internal memory to SD card using the stock My Files app as well.
Thanks @churchey360
Click to expand...
Click to collapse
Its good to hear that lol

Has anyone who has taken the update been able to find the HD Voice icon as shown in the link?
https://community.sprint.com/baw/mo...ssion?content=/api/core/v2/discussions/167584

Idk where to look for it or what its even supposed to look like lol i tried making a call earlier but didnt see anything but i know you have to be in an area that has the hd voice calling

Thanks for the update
Towel root confirmed doesnt work on NG2.

churchey360 said:
Are you on stock recovery? What is your full setup and what mods do you have installed?
Click to expand...
Click to collapse
I am on phillz advanced recovery.
On NAE software and modem version.
On mf9 bootloader.
I have xposed mode.

farookh said:
Thanks for the update
Towel root confirmed doesnt work on NG2.
Click to expand...
Click to collapse
Fairly certain cf auto root does though

aviara said:
Fairly certain cf auto root does though
Click to expand...
Click to collapse
Yes it does. ?

anees02 said:
I am on phillz advanced recovery.
On NAE software and modem version.
On mf9 bootloader.
I have xposed mode.
Click to expand...
Click to collapse
Itll probably update you to the KNOX bootloader by doing the OTA.
Easiest way to do the update is to flash the rooted stock NAE ROM that Unknown Force posted, then flash mf9 recovery, go into supersu app and do a full unroot then reboot and follow the OP.
Also you can flash the NAE .tar file with Odin but you will get the KNOX bootloader by doing this, but the OTA will give you the KNOX bootloader anyway.

churchey360 said:
Itll probably update you to the KNOX bootloader by doing the OTA.
Easiest way to do the update is to flash the rooted stock NAE ROM that Unknown Force posted, then flash mf9 recovery, go into supersu app and do a full unroot then reboot and follow the OP.
Also you can flash the NAE .tar file with Odin but you will get the KNOX bootloader by doing this, but the OTA will give you the KNOX bootloader anyway.
Click to expand...
Click to collapse
Ok... I think that I will flash the NAE.tar via odin... Because i have nothing to lose... My device doesn't under any warranty.
So i will take the knox bootloader and then trip it in order to take root.
I will still flash custom recovery and kitkat roms or later.

anees02 said:
Ok... I think that I will flash the NAE.tar via odin... Because i have nothing to lose... My device doesn't under any warranty.
So i will take the knox bootloader and then trip it in order to take root.
I will still flash custom recovery and kitkat roms or later.
Click to expand...
Click to collapse
KNOX bootloader isnt all that bad. It only prevents you from downgrading bootloaders which i dont see why anyone would ever need to do that.. and also just shows a yellow and red warning in the upper left hand corner (like the blue warning when booting into recovery) when you boot up your phone when using custom kernels or aosp based ROMs.
Also even tho you cant reset the KNOX count on the bootloader as long as you use triangle away to reset everything else and unroot then you should be good sprint wont ever know you was rooted.

If anyone wants to use Hotspot on this update there is an app in the playstore that cost $2.50 that really works (im using it now) just type "wifi tether router" and it will be the first app.
You will need root for it to work tho.

Update worked perfectly for me! Because Im ocd,I took a few extra steps to ensure a clean and problem free install. 1:download update,and move to root of SDext. 2:booted into recovery,and did a (install new rom wipe) in philz newest,then manually wiped system and data again to ensure fully clean. 3: rebooted into download mode using volume down and power,not the option in philz recovery.4 ODINed the stock NAE tar.md5. 5:after 1st boot finishes,and device is ready to setup,power off and boot back into DL mode. 6 ODIN cf autoroot 7:let device boot and handsfree setup complete,and once more before setting up,power off,and boot back into DL mode. 8 ODIN Philz newest jflte recovery,let device reboot,then setup. This might seem lengthy and overly drawn out,but i would rather take these steps now,then run into any potential problems later. Hope this helps.

My build number says KOT49H. L720VPUFNG2 shouldn't it say JDQ39.L720VPUFNG2

prguzman1978 said:
My build number says KOT49H. L720VPUFNG2 shouldn't it say JDQ39.L720VPUFNG2
Click to expand...
Click to collapse
No. Mine says the same thing.

Any one wanna run a system dump.

[ROM][TAR] Stock NG2 Odin flashable

You will get the KNOX bootloader if you flash this.
YOU CANNOT UNDO THIS, ITS PERMANENT. FLASHING ANYTHING UNOFFICIAL AFTER FLASHING THIS TAR WILL VOID YOUR WARRANTY​
Just the NG2 FULL stock tar.
Do NOT rename the tar file. Even though it may be convenient to do so, Odin may fail the md5 check for no reason.
(L720VPUFNG2_L720SPTFNG2_L720VPUFNG2_HOME.tar.md5)
This is NOT ROOTED. Its the original TAR file for people who need an Emergency Recovery for their phones, and dont want to wait hours for it to download from slow file hosts.
Mediafire
Instructions:
1. Download and Extract tar above and download Odin
2. Put phone into download mode (power off, then power button + Volume Down, then volume up when prompted)
3. Open Odin (right click > open as administrator)
4. Load stock tar into the PDA slot
5. Start flashing
6. Grab some popcorn because it will take a while
7. Profit

Is this going to update bootloader into NG2?
Is NG2 bootloader unlocked?
Thank you so much,

will this work on rooted phone?
im looking to put my phone back to unrooted stock. will this flash right on a rooted phone? im guessing it will but just want to make sure.

jam97 said:
Is this going to update bootloader into NG2?
Is NG2 bootloader unlocked?
Thank you so much,
Click to expand...
Click to collapse
Yes this will update you to the new update NG2 and no the bootloader is still locked.
chriseboy said:
im looking to put my phone back to unrooted stock. will this flash right on a rooted phone? im guessing it will but just want to make sure.
Click to expand...
Click to collapse
Yes this will flash right on a rooted phone. The purpose of this is to go back to stock from either rooted or custom rom.
Sent from my SPH-L720

ROMANTiC KiD said:
Yes this will update you to the new update NG2 and no the bootloader is still locked.
Yes this will flash right on a rooted phone. The purpose of this is to go back to stock from either rooted or custom rom.
Sent from my SPH-L720
Click to expand...
Click to collapse
sorry for this stupid question , but will I be able to flash a custom recovery after flashing this image?
Thank you,
Sent from my SPH-L720 using XDA Free mobile app

jam97 said:
sorry for this stupid quastion , but will I be able to flash a custom recovery after flashing this image?
Thank you,
Sent from my SPH-L720 using XDA Free mobile app
Click to expand...
Click to collapse
You will need to re-root the phone after installing this file! Then you will be able to install a custom recovery..

Thanks for putting this on a speedy host. I just downloaded it tonight in under half an hour at my daughter's house, and she doesn't have a particularly fast internet connection.
A quick question - does this file leave your programs intact? Sometimes I like a total wipe (except for my SD card), and start fresh.
Thanks again

my wifi is broken after flashing. won't turn on

rtwrobert10 said:
my wifi is broken after flashing. won't turn on
Click to expand...
Click to collapse
same problem let me know if you find how to fix it

rtwrobert10 said:
my wifi is broken after flashing. won't turn on
Click to expand...
Click to collapse
biscojams said:
same problem let me know if you find how to fix it
Click to expand...
Click to collapse
Reflash it again
Sent from my SPH-L720

rtwrobert10 said:
my wifi is broken after flashing. won't turn on
Click to expand...
Click to collapse
biscojams said:
same problem let me know if you find how to fix it
Click to expand...
Click to collapse
ROMANTiC KiD said:
Reflash it again
Sent from my SPH-L720
Click to expand...
Click to collapse
Same here, I wiped then installed twice, no wifi. I'll try one more time,

DAFTEK said:
Same here, I wiped then installed twice, no wifi. I'll try one more time,
Click to expand...
Click to collapse
Try flashing the ng2 kernel after the install. Thru custom recovery.
https://www.androidfilehost.com/?fid=23622183712458388
Thanks to @ g_ding84

DAFTEK said:
Same here, I wiped then installed twice, no wifi. I'll try one more time,
Click to expand...
Click to collapse
That's odd.
I have installed this NG2 tar file with Odin on 2 different phones and WiFi works perfect on both..

2WhiteWolves said:
Try flashing the ng2 kernel after the install. Thru custom recovery.
https://www.androidfilehost.com/?fid=23622183712458388
Thanks to @ g_ding84
Click to expand...
Click to collapse
Thanks for the reply. I did try one more time and this time I went back in recovery and did the two wipes, went back in to download, opened odin3 3.09 via administrator and removed the auto reboot check. after it finished i manually rebooted and wifi worked.
---------- Post added at 10:06 PM ---------- Previous post was at 10:02 PM ----------
Now I have another problem. I am no longer with sprint and my phone is unlocked from sprint. I have been using the GOLDENEYE rom on Walmart Family Mobile and all was warning well except for sometimes not connecting calls so I thought i go back to stock with this rom. Problem now is I can make calls with the Walmart sim card, put in the APN settings but i am unable to remove the Hands Free Activation nagging.. Is there anyway to make it go away?

DAFTEK said:
[/COLOR]Now I have another problem. I am no longer with sprint and my phone is unlocked from sprint. I have been using the GOLDENEYE rom on Walmart Family Mobile and all was warning well except for sometimes not connecting calls so I thought i go back to stock with this rom. Problem now is I can make calls with the Walmart sim card, put in the APN settings but i am unable to remove the Hands Free Activation nagging.. Is there anyway to make it go away?
Click to expand...
Click to collapse
Have you tried to pull down the notification bar with two fingers > long press on Hands Free icon to see if something is turned on to make it show up on notification bar? If turned on, shut it off. Hopefully it is that simple. If not that simple, I have no clue how to make it stop. Maybe someone else does.
I haven't heard of anyone having that problem.

Yeah, I tried everything, it's part of the rom I think, nothing worked to make it go away..
I just went back to goldeneye rom, all working perfect again. Thanks.

I just flashed this rom through odin and it didn't wipe any of my programs, isn't is supposed to?

RTbar said:
I just flashed this rom through odin and it didn't wipe any of my programs, isn't is supposed to?
Click to expand...
Click to collapse
+1
also I confirm that everything is working great.

RTbar said:
I just flashed this rom through odin and it didn't wipe any of my programs, isn't is supposed to?
Click to expand...
Click to collapse
Nope. it doesn't wipe data unless stated by the OP that it does. It only restores any apps deleted, or reverses any mods made. Example if you are running Aosp and Odin back to stock. You will get bootloop. After Odin always go to stock recovery and do a factory reset to have a clean install.
Sent from my SPH-L720

Wifi didn't work for me on this rom, coming from a custom mf9 rom. So I odin mf9 bootloader package, and then flashed stock mf9 odexed rooted rom, then odin the mf9 kernel. And did NG2 upgrade through Kies. Now Wi-Fi finally works for me but it's impossible to root. But at least now I got everything working, when I get off of work I can flash the OP version of NG2 cuz at least I could root that 1.

MM Update (QI2) - TWRP Won't Install!!!

Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave

Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.

dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!

Zeuszoos said:
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Click to expand...
Click to collapse
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.

dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL

Zeuszoos said:
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Click to expand...
Click to collapse
Yes I have tried this. I changed my phone from a trip to a t2 and back again.

dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
There is an MM ROM that is Rooted and has TWRP built in, but I don't know if it would Flash over this with Odin or not
I am also considering trying the entire KK T2 ROM again to go down to KK and then Flashing that MM ROM.
It has both Odexed & DeOdexed. If I remember right, DeOdexed is the better choice, right?
Thanks for all your time and help!
Dave

Hi,
You know what's sad, is that if I could somehow Roog it without TWRP, then I could use the way awesome "Flashify" app to try to get TWRP on this phone! <lol>
Dave

dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave

Zeuszoos said:
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Click to expand...
Click to collapse
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps

dottyparent said:
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
Click to expand...
Click to collapse
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave

Zeuszoos said:
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Click to expand...
Click to collapse
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.

dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
No, I'm sorry, but you have to give me the answer.
All seriousness aside, I depreciate all your effort.
I can only think of one thing left to try... Go to Sammy's site and get the Lollipop 5.1.1 ROM and see what happens. It can't hurt to try, right?
I'll let ya know what happens and thank you again!
Happy Thanksgiving!
Dave

dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL

Zeuszoos said:
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Click to expand...
Click to collapse
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs

Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all

dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
ShaDisNX255 said:
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
Click to expand...
Click to collapse
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL

Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
That's because I have a n910t not a t3

Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
I upgraded from LL. The device was running 5.0.1 and now has 6.0.1

dottyparent said:
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Click to expand...
Click to collapse
Thank you for looking! I found out what it is.
It's "Factory Reset Protection" (FRP)
What it does, is keep someone else from Factory Resseting your phone if they steal it. When they reset it, during setup, they have to type in the last Google Email and Password that the phone used, before they can set up theirs.
After reading that, I remembered having to put my Google Info in at two separate points and seeing it telling me to "Verify", but I was just blowing right through setup, not reading all of the small print. I mean hey, I had no idea that even existed and was just annoyed that I had to type the same thing twice!
It will only be found on phones that already have Lollipop and up on them out of the box and probably not all of them yet. And you don't have to worry about downloadable ROMS, so those who have phones that started with KitKat, or even early versions of Marshmallow 6.0 or 6.0.1 would not have seen this happen to them. Even those who updated to the same version of Mm that my phone has won't, if they started with KK or an older MM and then updated to it.
Again, this is something that your phone would have "Out of the Box" and the phone (not all) would have at least L on it.
Just FYI, it's not just Samsung, either.
Just FYI, I have confirmed this info. It is a fact.
Once I have an easy to do, working fix, hopefully without having to perform a Factory Reset, I will "Create A Thread" and as normal for me, write clear and easy, step by step (not leaving any out) instructions on how to "Unlock FRP" and then come back here and post a link to the thread. Hopefully this week.
This phone will not beat me!!!
TTYL
Dave