Database Develop

[Resolved] Stuck in Download Mode after failed flash attempt.

Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.

timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
Oh god are you on the US version (SGH-I537)? If you're on the international version (I9295) ignore this post but otherwise, you need to read and take in my short rant. Trust me I wish this weren't the case, but it is, and it's important:
The Galaxy S4 Active i537 has a locked bootloader. There is no way around this, no ifs ands or buts. You simply cannot flash custom ROMs or recoveries. That's it, end of story as far as CM, CWM, AOSP and such things are concerned. That being said there is a sort of recovery called SafeStrap which you can use to make nandroid backups, flash mods and STOCK-BASED roms, but it's not a true custom recovery in the sense that we had been used to, because of this locked bootloader nightmare.
OK so I think you're gonna want to check out this thread. It's all about how to install any firmware from download mode, I think you're gonna have to go with NE3 or NH3.
Let me reiterate. NO CUSTOM ROMS. NO CWM. No Paranoid, no cyanogenmod, no AOSP, no crossing go before going directly to jail. Sorry for the stupid joke but seriously, you have got to keep your phone on stock-based roms (of which there are unfortunately few).
Firmware download links

timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
What phone do you have (i537 or i9295) and what version of firmware were you on?

Devo7v said:
What phone do you have (i537 or i9295) and what version of firmware were you on?
Click to expand...
Click to collapse
i537 and second to last, I537UCUCNE3

Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?

Web browser login, edit, advanced.
Add "solved" to title?

same problem with my i537, need help
timmytron said:
Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?
Click to expand...
Click to collapse
Need help, having the same problem

baddhabbitz88 said:
Need help, having the same problem
Click to expand...
Click to collapse
Have you used ODIN before?

i537 Stuck in download mode
timmytron said:
Have you used ODIN before?
Click to expand...
Click to collapse
yes I have use odin but I think I have the same issue you did, need to know where to get the files .

baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?

baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Did you get my PM?

timmytron said:
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?
Click to expand...
Click to collapse
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.

baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
Well AT&T decided to completely lock us out on this particular version on this particular phone. At least we have *ROOT*.

baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.

Devo7v said:
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.
Click to expand...
Click to collapse
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
timmytron said:
Did you get my PM?
Click to expand...
Click to collapse
yeah I got it thanks but it didn't work still digging

baddhabbitz88 said:
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
yeah I got it thanks but it didn't work still digging
Click to expand...
Click to collapse
Always check the stickies.
http://forum.xda-developers.com/showthread.php?t=2892445

[SOLVED]I installed the SlimROM by SlimShady. LOST ALL CELLULAR ABILITIES

I NEEED HELP. After installing the rom I think it installed some sort of radio image or something. Because afterwards I couldn't use data. Even after going back to stock. Even tried factory reset. With ZERO LUCK. It detects the sim card. It even reads the contacts. It says it has bars. But it says emergency calls only. It says No service. Next thing I will try is getting a new sim. I'll keep this updated. I hope that fixes it.

Probably wrong aboot/bootstack. Root and flash the correct bootstack for your phone model and ROM version. Be very careful about phone model or you may hard brick it. Bootstack zips also contain unlocked aboot as far as I know...

i have the same problem. can you help me?
lfom said:
Probably wrong aboot/bootstack. Root and flash the correct bootstack for your phone model and ROM version. Be very careful about phone model or you may hard brick it. Bootstack zips also contain unlocked aboot as far as I know...
Click to expand...
Click to collapse
i have the same problem, my device is d400hn, the roms its very good but i cant do calls or power on data usage. reading a little i found a thread from here where are all the bootstack for all phones less for mine. and other thread i found that a man can get up the phone with bootstack of d405n, i want to know if the bootstackk is the same for lollipop and marshmallow? anybody ? thanks.

jacs117 said:
i have the same problem, my device is d400hn, the roms its very good but i cant do calls or power on data usage. reading a little i found a thread from here where are all the bootstack for all phones less for mine. and other thread i found that a man can get up the phone with bootstack of d405n, i want to know if the bootstackk is the same for lollipop and marshmallow? anybody ? thanks.
Click to expand...
Click to collapse
There is no stock Marshmallow ROM from LG, so only custom ones, and all use the same Lollipop bootstack.

lfom said:
There is no stock Marshmallow ROM from LG, so only custom ones, and all use the same Lollipop bootstack.
Click to expand...
Click to collapse
Thanks by your time, i have already fixed the problem with the bootstack of the d405n, yes i said the bootstack of the d405n works perfect on d400hn, in my case is from telcel México. Sorry for my bad english, and i wait to help someone

[Q] Can't boot into TWRP and my phone got unrooted

Hello!
I have a Huawei Mate 9 (MHA-L29C432B190). Yesterday I tried to root my Phone to play Pokemon Go with fake gps. After I managed to root my phone, I couldn't boot into TWRP Recovery Mode anymore.
Because I still had some files I needed to flash I installed Flashfire from the PlayStore. I think after I flashed the newest Magisk version(The flash failed because of Error:1), my device got unrooted. But I think my device is still partly rooted because I can't get into Pokemon Go. Everytime I try to start it I get stuck the loading screen. So right now I can't flash anything to get my root back and I don't have the root to use alternative flash applications. I also tried to start return my phone to stock back with a update.app But it can't be installed. I also can't use "fastboot flash recovery twrp.img" I always get " Writing 'recovery'...FAILED (remote:command can't be used/allowed)". And also after some reboots my oem unlock got turned off and I can't turn it on anymore.
I don't have any ideas anymore what to do. I thought I could root my device, so I could unroot properly with superuser. I tried some other application like KingRoot oder OneClickRoot but both of them don't have a rooting method for the Huawei Mate 9 yet. Btw I don't have a backup because of my naivety.
I hope you guys can help me . I appreciate any ideas
Thanks in advance

In summary what do u want???
Sent from my iPhone using Tapatalk Pro

abuk91 said:
In summary what do u want???
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
Either way I want a method to root my phone without some flash application or I want a way to return my phone to stock. Or a method to fix TWRP would be fine too.

Kyranix said:
Either way I want a method to root my phone without some flash application or I want a way to return my phone to stock. Or a method to fix TWRP would be fine too.
Click to expand...
Click to collapse
Do a Google search for:
"Return to stock (your model number)"
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Do a Google search for:
"Return to stock (your model number)"
I already did and everything I found didn't work

Kyranix said:
Do a Google search for:
"Return to stock (your model number)"
I already did and everything I found didn't work
Click to expand...
Click to collapse
What did you find? What have you tried?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

What did you find? What have you tried?
I tried to do Upgrades with many different stock firmwares for my model

Kyranix said:
What did you find? What have you tried?
I tried to do Upgrades with many different stock firmwares for my model
Click to expand...
Click to collapse
That doesn't tell me anything. That just tells me that you tried flashing.
It doesn't tell me anything about exactly what you tried to flash or what errors you got when you flashed. I need more precise information to help you. Your simple answers aren't helping me understand anything about what you have going on with your device.
What tools have you used? What guide/instructions did you use? What files have you used? What errors did you get? What results did you get. What do mean "didn't work"? "Didn't work" can mean many things.
I might be able to help you fix your device but I can't fix ignorance.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

That doesn't tell me anything. That just tells me that you tried flashing.
It doesn't tell me anything about exactly what you tried to flash or what errors you got when you flashed. I need more precise information to help you. Your simple answers aren't helping me understand anything about what you have going on with your device.
What tools have you used? What guide/instructions did you use? What files have you used? What errors did you get? What results did you get. What do mean "didn't work"? "Didn't work" can mean many things.
I might be able to help you fix your device but I can't fix ignorance.
First I tried to do a force upgrade with a "dload" folder with a update.app file on my sdcard . After booting into this upgrade mode by pressing vol up + vol down + power button my device starts to install the stock firmware, but after it reaches 5% I get the message "Error with installing" and a Link to the same site when you boot into twrp. This always happens no matter which file I use. Next I tried to do a normal upgrade by calling this number "*#*#2846579#*#*" (The dload folder is still on my sdcard). But when I start the software upgrade I get booted into twrp and like I said in my post, always when I try to get into twrp I get stuck on the "Your device is booting screen". This is what I tried and basicly every site on google is saying I should try to do one of these two methods
(Here a guide for example: https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/)
(My file in my last try: https://www.getdroidtips.com/huawei-mate-9-stock-firmware-collections/)

Kyranix said:
That doesn't tell me anything. That just tells me that you tried flashing.
It doesn't tell me anything about exactly what you tried to flash or what errors you got when you flashed. I need more precise information to help you. Your simple answers aren't helping me understand anything about what you have going on with your device.
What tools have you used? What guide/instructions did you use? What files have you used? What errors did you get? What results did you get. What do mean "didn't work"? "Didn't work" can mean many things.
I might be able to help you fix your device but I can't fix ignorance.
First I tried to do a force upgrade with a "dload" folder with a update.app file on my sdcard . After booting into this upgrade mode by pressing vol up + vol down + power button my device starts to install the stock firmware, but after it reaches 5% I get the message "Error with installing" and a Link to the same site when you boot into twrp. This always happens no matter which file I use. Next I tried to do a normal upgrade by calling this number "*#*#2846579#*#*" (The dload folder is still on my sdcard). But when I start the software upgrade I get booted into twrp and like I said in my post, always when I try to get into twrp I get stuck on the "Your device is booting screen". This is what I tried and basicly every site on google is saying I should try to do one of these two methods
(Here a guide for example: https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/)
(My file in my last try: https://www.getdroidtips.com/huawei-mate-9-stock-firmware-collections/)
Click to expand...
Click to collapse
Stock upgrades are not going to work if you are rooted and have TWRP.
Stock updates require stock recovery and an unmodified system partition(no root).
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
Stock upgrades are not going to work if you are rooted and have TWRP.
Stock updates require stock recovery and an unmodified system partition(no root).
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Yeah I have already seen, but I can't find an other method to return my Huawei Mate 9 to stock and I don't really have an root.

Kyranix said:
Yeah I have already seen, but I can't find an other method to return my Huawei Mate 9 to stock and I don't really have an root.
Click to expand...
Click to collapse
But you have TWRP, that won't work. You need stock recovery, custom recovery can't flash stock updates.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
But you have TWRP, that won't work. You need stock recovery, custom recovery can't flash stock updates.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
And can you please tell me how to do it then. You can also send me a guide

Kyranix said:
And can you please tell me how to do it then. You can also send me a guide
Click to expand...
Click to collapse
I am not sure why you are not doing this in your device forum?
https://forum.xda-developers.com/mate-9
It seems that there would be more assistance specific to your device.
or did I miss something?

Moscow Desire said:
I am not sure why you are not doing this in your device forum?
https://forum.xda-developers.com/mate-9
It seems that there would be more assistance specific to your device.
or did I miss something?
Click to expand...
Click to collapse
Well thats because I already had problems to post this thread because I am new to xda

Moscow Desire said:
I am not sure why you are not doing this in your device forum?
https://forum.xda-developers.com/mate-9
It seems that there would be more assistance specific to your device.
or did I miss something?
Click to expand...
Click to collapse
Well thats because I already had problems to post this thread because I am new to xda But thanks for pointing it out, I will probably try it there again. Maybe there I will have more luck

Kyranix said:
Well thats because I already had problems to post this thread because I am new to xda [emoji14] But thanks for pointing it out, I will probably try it there again. Maybe there I will have more luck
Click to expand...
Click to collapse
Even new members(less than 10 posts) can post in device specific Q&A fora, new members are only blocked from posting in "development" fora and threads.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

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

Stuck on the black screen - power on doesn't work, only Recovery and Download works

Hello.
I've been playing with some custom ROMs, recoveries, etc. on S10 SM-G973F. Every time something went wrong I was able to flash stock Android 11 ROM with Odin and run the system after that. But not anymore...
At this moment I have access to Recovery Mode (stock, TWRP, LineageOS... whichever I flash with Odin) and Download Mode. When I try to power on the phone with button or with an option Boot to System from Recovery the phone turns off and nothing else happens. Black screen only, no vibration, etc.
I tried to format data and cache in Stock Recovery and TWRP. I tried to flash many time, changed USB cable, change USB port... nothing helps.
What is strange that after I flash the stock recovery the phone boots one time displaying the unlocked bootloader warning, Samsung logo and Android robot icon with an Erasing sign... but just for a 1-2s, very short time. Before the problem occurred the Erasing took much much more time. After that one time I cannot make to display bootloader unlocked warning and Samsung logo any more, no matter which ROM or recovery I flash.

Maybe you can try installing the original firmware and start over again.

That is what I do in the first place, I try to flash the original firmware with Odin. I use the same files as before. The only difference I can see is that after the flashing the Erase progress was very long and now it is only 1-2s and the phone turns off.

Ok, I've found my mistake and a solution. I will post it here if anyone else has a similar problem.
So while I was playing with different ROMs one of them had an instruction to flash G973FXXSCFUH5-twrp_flashable.zip that included:
modem.bin
dt.img
dtbo.img
cm.bin
sboot.bin
up_param.bin
keystorage.bin
uh.bin
The zip included was to an older firmware G973FXXSCFUH5, while I was already on newer G973FXXSEFUJ2. But the TWRP that I used to flash the zip did not protest and the process finished well. Causing the problems above of course.
Don't know why but flashing the whole original G973FXXSEFUJ2 firmware with Odin was not enough. But when I flashed G973FXXSEFUJ2-twrp_flashable.zip from the TWRP worked and made the phone operational again.

hello, I am in the same situation after having wanted to install blastui I find myself with the possibility of starting only in dow load or in twrp. Can you help me

FabienGege said:
hello, I am in the same situation after having wanted to install blastui I find myself with the possibility of starting only in dow load or in twrp. Can you help me
Click to expand...
Click to collapse
0. Make sure your phone is charged!
1. Check your current SW# in Download mode (the number stands for the number or letter in firmware code, the 5th sign from the end in hexadecimal, for example SW# 14 is E in G973FXXSEFUJ2_G973FOXMEFUJ2)
2. Find the proper version of bootloader and modem in ....-twrp_flashable.zip format (check here: https://github.com/corsicanu/9820-bootloaders_and_modems/releases)
3. Flash and run TWRP recovery.
4. Flash the zip file from #2.
Flashing the stock firmware with Odin was not enough for me. Flashing with TWRP made the S10 back to alive.

.

Doman said:
0. Make sure your phone is charged!
1. Check your current SW# in Download mode (the number stands for the number or letter in firmware code, the 5th sign from the end in hexadecimal, for example SW# 14 is E in G973FXXSEFUJ2_G973FOXMEFUJ2)
2. Find the proper version of bootloader and modem in ....-twrp_flashable.zip format (check here: https://github.com/corsicanu/9820-bootloaders_and_modems/releases)
3. Flash and run TWRP recovery.
4. Flash the zip file from #2.
Flashing the stock firmware with Odin was not enough for me. Flashing with TWRP made the S10 back to alive.
Click to expand...
Click to collapse
Hello brother can you please explain it again to me? My English is terrible and i hope you understand that.

Mohammed_9564 said:
Hello brother can you please explain it again to me? My English is terrible and i hope you understand that.
Click to expand...
Click to collapse
There is not much more to explain, just follow the steps I pointed. If any of them are not clear enough just ask, but I tried to make them as simple as possible If your English is not to well just try to use Google Translator.

Doman said:
There is not much more to explain, just follow the steps I pointed. If any of them are not clear enough just ask, but I tried to make them as simple as possible If your English is not to well just try to
Doman said:
There is not much more to explain, just follow the steps I pointed. If any of them are not clear enough just ask, but I tried to make them as simple as possible If your English is not to well just try to use Google Translator.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Oh man Thanks a lot for your reply i actually managed to do it 2 days ago and it worked thanks to your help again, but i have another question if it's not too much trouble for you, how can i go back to the stock room ? Can i just do it via Odin or is there another way to do it.

Mohammed_9564 said:
Oh man Thanks a lot for your reply i actually managed to do it 2 days ago and it worked thanks to your help again, but i have another question if it's not too much trouble for you, how can i go back to the stock room ? Can i just do it via Odin or is there another way to do it.
Click to expand...
Click to collapse
Best way to go back to stock rom is simply flash it with Odin from original files available from Samsung, for example on SamMobile:
https://www.sammobile.com/samsung/galaxy-s10/firmware/#SM-G973F

Doman said:
Best way to go back to stock rom is simply flash it with Odin from original files available from Samsung, for example on SamMobile:
https://www.sammobile.com/samsung/galaxy-s10/firmware/#SM-G973
Click to expand...
Click to collapse
Thanks for the help brother I appreciate it

For months I've tried searching for a solution to fix my SM-N976U that stopped booting up. None of the symptoms shared fully matched what I was experiencing, so every fix I attempted didn't get her fully functioning again, eventually I gave up trying, stuffed the phone in a drawer and just bought another one. Today I stumbled upon your post and every symptom you described fit exactly with what happen to me, I mean to the T, minus the model and fw version. So I grabbed my SM-N976U one more time and followed your solution... and guess what??? I am now a proud owner of 2 note 10 plus'!!!
Thank you so much for taking the time to share your experience and solution!! Cheers to you bud! Have a great New Year!

Thank you~! my s10 plus is back!