Installing Magisk using ODIN - Magisk

Basically what the title says. I'm using ODIN to flash a patched boot.img, since apparently that's the only way to install this on a samsung device, and... well, I'm at a total loss about what to do. I'm using version 3.13 of ODIN. I tried installing it by putting the file where it said AP (since the .tar file I took the original boot.img from also had that name), but it just failed.
Does anyone have any idea as to how I should use ODIN to pull this off? I would appreciate any tips you could give me, since I'm a total novice on this

Okay, I've looked into this a bit further. It seems I'm not doing anything wrong, but when I try flashing the patched boot.img, a message appears on my phone saying "Only official released binaries are allowed to be flashed(BOOT)". And it fails outright.
Is there any way to circumvent this aside from custom recoveries?

AndreM962 said:
Okay, I've looked into this a bit further. It seems I'm not doing anything wrong, but when I try flashing the patched boot.img, a message appears on my phone saying "Only official released binaries are allowed to be flashed(BOOT)". And it fails outright.
Is there any way to circumvent this aside from custom recoveries?
Click to expand...
Click to collapse
There is enough info on xda already, why don't you just look for it?
your message is related to oem unlock. Seek for it.
Sent from my SM-A605FN using Tapatalk

pr1jker said:
There is enough info on xda already, why don't you just look for it?
your message is related to oem unlock. Seek for it.
Click to expand...
Click to collapse
My phone is in fact already oem unlocked. I made sure of it.
I should probably have mentioned that in the first post... oh well.
If it's OEM unlocked, then it shouldn't have this problem, right?

AndreM962 said:
Okay, I've looked into this a bit further. It seems I'm not doing anything wrong, but when I try flashing the patched boot.img, a message appears on my phone saying "Only official released binaries are allowed to be flashed(BOOT)". And it fails outright.
Is there any way to circumvent this aside from custom recoveries?
Click to expand...
Click to collapse
There is a patched ODIN that is much more chill with binaries that may not be official.

blazzer12 said:
There is a patched ODIN that is much more chill with binaries that may not be official.
Click to expand...
Click to collapse
Excellent, thanks! I'll test it out when I have time and then get back to you

blazzer12 said:
There is a patched ODIN that is much more chill with binaries that may not be official.
Click to expand...
Click to collapse
Um, first of all, sorry to reply to you so late. I had a lot of stuff to take care of.
However, I want to say that the patched ODIN that you told me to use did not work. In fact, everything ocurred the same way as when I used the official version. It's very confusing.
Regardless, any further help with this would be greatly appreciated, especially if it doesn't involve using a custom recovery
I really want to install Magisk, it seems really useful...

When I boot into download mode, it also says that RMM state is "prenormal". Does that help?

AndreM962 said:
Um, first of all, sorry to reply to you so late. I had a lot of stuff to take care of.
However, I want to say that the patched ODIN that you told me to use did not work. In fact, everything ocurred the same way as when I used the official version. It's very confusing.
Regardless, any further help with this would be greatly appreciated, especially if it doesn't involve using a custom recovery
I really want to install Magisk, it seems really useful...
Click to expand...
Click to collapse
What is your phone model? Which magisk image are you trying to flash? Did you enable "OEM Unlock" in developers settings?

blazzer12 said:
What is your phone model? Which magisk image are you trying to flash? Did you enable "OEM Unlock" in developers settings?
Click to expand...
Click to collapse
My phone is a Samsung Galaxy J6, model SM-J600GT.
The Magisk I'm trying to flash is the most recent one, version 18.1, I think.
And I have indeed enabled OEM Unlock.

AndreM962 said:
My phone is a Samsung Galaxy J6, model SM-J600GT.
The Magisk I'm trying to flash is the most recent one, version 18.1, I think.
And I have indeed enabled OEM Unlock.
Click to expand...
Click to collapse
Are you patching the boot.img as a .tar? Maybe as .tar.md5

madbat99 said:
Are you patching the boot.img as a .tar? Maybe as .tar.md5
Click to expand...
Click to collapse
I am indeed patching it as a .tar. How would I go about turning it into a .tar.md5 file?
I'm actually starting to suspect it has to do with that RMM state being prenormal thing based on a few things I've read. I'm going to try waiting 7 full days of activity and attempt to patch it again, unless I can find a better solution.

AndreM962 said:
I am indeed patching it as a .tar. How would I go about turning it into a .tar.md5 file?
I'm actually starting to suspect it has to do with that RMM state being prenormal thing based on a few things I've read. I'm going to try waiting 7 full days of activity and attempt to patch it again, unless I can find a better solution.
Click to expand...
Click to collapse
Probably a good idea. I've seen ppl simply add .md5 at the end to get Odin to recognize it.

Alright, then it's settled. When I finally try it out, I'll come back to you guys.

Well, then. I'm back, and have nothing to show for it.
RMM State continues to be prenormal, despite me keeping the phone active through 7+ days of activity. Booted it into download mode, same problem: a message saying "Only official binaries are allowed to be patched" and then nothing. I've waited way too long for this.
I need help. Any suggestions would be greatly appreciated. I don't have any other ideas.

Seems down.

Erm... what do you mean by that?

AndreM962 said:
Erm... what do you mean by that?
Click to expand...
Click to collapse
Jesus, I was about to comment on the thread about the patched Odin without being logged in.
After logging in I got somehow redirected to this thread and didn't check. Sorry. :silly:

testguest said:
Jesus, I was about to comment on the thread about the patched Odin without being logged in.
After logging in I got somehow redirected to this thread and didn't check. Sorry. :silly:
Click to expand...
Click to collapse
S'okay. It's not like anyone but me checks this thread anyway, heh

AndreM962 said:
S'okay. It's not like anyone but me checks this thread anyway, heh
Click to expand...
Click to collapse
I just got my new Samsung Tab S5e today and was having the exact same error as you trying to flash it. I was able to "fix" it by unselecting "Auto Reboot" in the Odin options.
HOWEVER! After it "successfully" flashed my Magisk-generated patched_boot.img.tar, I bootlooped hardcore until I restored the stock firmware. It was difficult to get the tablet back into Download mode it was looping so much (had to force it into Recovery first, then select "Reboot to bootloader").
Your mileage may vary, so go ahead and try unselecting Auto Reboot, but beware there's a good chance you'll bootloop like me.
Edit:
Yeah, okay, assuming you're on any Samsung device that shipped with Android Pie, installing Magisk got a lot more complicated. Read these two things to get a lay of the land before proceeding:
https://topjohnwu.github.io/Magisk/samsung
https://forum.xda-developers.com/galaxy-s10/development/magisk-root-galaxy-s10-series-t3918699/

Related

[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

CF-Auto-Root

The first S6 Edge roots are available from the repository: http://autoroot.chainfire.eu/ !
Note that the stock kernel currently has an issue preventing the device from going into "deep sleep" if a custom recovery is flashed (which is what this does). A fix for this issue can be found here: http://forum.xda-developers.com/showpost.php?p=60383471&postcount=49. This fix will also work if you replace the recovery with for example TWRP.
im trying to root my tmobile sm-g925t s6 edge and in odin it is stuck on nand write start.. what should i do?
yubby said:
im trying to root my tmobile sm-g925t s6 edge and in odin it is stuck on nand write start.. what should i do?
Click to expand...
Click to collapse
is your bootloader unlocked..?
yubby said:
im trying to root my tmobile sm-g925t s6 edge and in odin it is stuck on nand write start.. what should i do?
Click to expand...
Click to collapse
Same issue here. I've tried all the "Odin" tricks.. different cables, different PCs, latest drivers, several reboots, different Odin versions, etc.... All the same, stuck on "NAND Write Start". Hoping for a fix soon.
Yes the sm-g925t is on the list
From looking at the other threads, specifically the non-edge S6 auto root thread, everyone is in the same boat. We just need to wait for Chainfire to update. Like an idiot, I accepted the out-of-the-box OTA although others are saying they are having the same issue without the OTA update.
Alex-V said:
is your bootloader unlocked..?
Click to expand...
Click to collapse
All t-mobile phones have unlocked bootloaders
mmayhew said:
From looking at the other threads, specifically the non-edge S6 auto root thread, everyone is in the same boat. We just need to wait for Chainfire to update. Like an idiot, I accepted the out-of-the-box OTA although others are saying they are having the same issue without the OTA update.
Click to expand...
Click to collapse
mine is bricked. i tried to root and it wont get passed the first screen. cant even access recovery. i cant even get the phone to turn off
Damn I bricked mine too. Used Odin 3.10.6, got a successful flash but it won't get past the booting screen, won't shut off, can only really access Download Mode. Which I've tried using different suggestions but still failed to get it to boot up or put into recovery to complete the root process.
shadowk91 said:
Damn I bricked mine too. Used Odin 3.10.6, got a successful flash but it won't get past the booting screen, won't shut off, can only really access Download Mode. Which I've tried using different suggestions but still failed to get it to boot up or put into recovery to complete the root process.
Click to expand...
Click to collapse
I would be really pissed if my new edge will be stuck before i even got to play with it...... Hope you guys get it working back asap
How did you get it to be successful flash? I tried ODIN 3.10.6 with the available CF-Auto_root and continue to get stuck at NANO WRITE! Of course i accepted the OTA right out of box also.
Wonder why we have different results of "same task"
FieldsInc said:
How did you get it to be successful flash? I tried ODIN 3.10.6 with the available CF-Auto_root and continue to get stuck at NANO WRITE! Of course i accepted the OTA right out of box also.
Wonder why we have different results of "same task"
Click to expand...
Click to collapse
I didn't actually take the OTA, because I wanted to be sure that I would be able to root the phone for sure without needing to wait too long for an update to the Auto Root Utility that would work with the newer version.
shadowk91 said:
Damn I bricked mine too. Used Odin 3.10.6, got a successful flash but it won't get past the booting screen, won't shut off, can only really access Download Mode. Which I've tried using different suggestions but still failed to get it to boot up or put into recovery to complete the root process.
Click to expand...
Click to collapse
I had the same problem but then I flashed the non-edge S6 auto root (SM-G920T) and it worked flawlessly. Good luck.
mmayhew said:
I had the same problem but then I flashed the non-edge S6 auto root (SM-G920T) and it worked flawlessly. Good luck.
Click to expand...
Click to collapse
OMG! THAT'S IT!, IT WORKED!!! YOU SAVED MY STUPIDLY EXPENSIVE PHONE (and from some seriously painful beatings from the wife had she found out the $1100+ phone died).
Okay enough of my excitement. Thanks for the advice, and helping me revive my phone. I hope Chainfire updates his first page post to ensure other people don't accidentally semi-brick their phones.
shadowk91 said:
OMG! THAT'S IT!, IT WORKED!!! YOU SAVED MY STUPIDLY EXPENSIVE PHONE (and from some seriously painful beatings from the wife had she found out the $1100+ phone died).
Okay enough of my excitement. Thanks for the advice, and helping me revive my phone. I hope Chainfire updates his first page post to ensure other people don't accidentally semi-brick their phones.
Click to expand...
Click to collapse
and after this you installed the OTA..?
mmayhew said:
I had the same problem but then I flashed the non-edge S6 auto root (SM-G920T) and it worked flawlessly. Good luck.
Click to expand...
Click to collapse
Alex-V said:
and after this you installed the OTA..?
Click to expand...
Click to collapse
Yes, I installed the OTA and successfully rooted the S6 Edge (SM-925T) by using Odin 3.10.6 and the non-edge auto root (SM-G920T). It will trip KNOX as expected.
Alex-V said:
and after this you installed the OTA..?
Click to expand...
Click to collapse
The Updater recognizes that my phone has been modified so it won't even allow me to download the OTA.
shadowk91 said:
The Updater recognizes that my phone has been modified so it won't even allow me to download the OTA.
Click to expand...
Click to collapse
Has anyone successfully updated OTA first and then flashed AutoRoot?
martinezma99 said:
Has anyone successfully updated OTA first and then flashed AutoRoot?
Click to expand...
Click to collapse
Yes, several of us have had success flashing Auto Root after installing the OTA.
I have took OTA and rooted, using the 920t auto root.
Sent from my SM-G925T using XDA Free mobile app

custom binary blocked by frp lock SM-N920p

Well i flashed Tdunham's rom on the SM-N920P also flashed the second version of Freeza's beastmode kernel and twrp all is well after that unfortunately after doing some looking i found that i must have clicked oem unlock and turned it off and didnt know and shut it off now i get a custom binary blocked by frp lock in the upper left hand corner and i cant boot up the phone or access the bootloader because of it but i can switch to download mode but everything i try to flash comes up as failed can anyone tell if i can fix this?
T9EX said:
Well i flashed Tdunham's rom on the SM-N920P also flashed the second version of Freeza's beastmode kernel and twrp all is well after that unfortunately after doing some looking i found that i must have clicked oem unlock and turned it off and didnt know and shut it off now i get a custom binary blocked by frp lock in the upper left hand corner and i cant boot up the phone or access the bootloader because of it but i can switch to download mode but everything i try to flash comes up as failed can anyone tell if i can fix this?
Click to expand...
Click to collapse
I honestly have no clue what you're saying here. I'm not trying to be the grammar police, but there's not a single comma or period in that entire paragraph.
Are you suggesting that you flashed something (with TWRP) when "OEM unlock" was turned off? Then when you reboot the phone nothing happens except immediately seeing "frp lock" in the upper left corner (and nothing else whatsoever?)
Can you power down the phone? (press/hold volume down and power.) If so, after it's powered down, what happens when you try to boot into bootloader/download/odin mode? What steps are you performing to boot into odin mode from a power off state?
Are you able to boot directly into recovery mode from a powered down state? What steps are you performing to boot into recovery from a powered down state? What happens as a result of those steps?
PLEASE use periods, commas and line breaks to help format your message. Help us to help you...
Gary
garyd9 said:
I honestly have no clue what you're saying here. I'm not trying to be the grammar police, but there's not a single comma or period in that entire paragraph.
Are you suggesting that you flashed something (with TWRP) when "OEM unlock" was turned off? Then when you reboot the phone nothing happens except immediately seeing "frp lock" in the upper left corner (and nothing else whatsoever?)
Can you power down the phone? (press/hold volume down and power.) If so, after it's powered down, what happens when you try to boot into bootloader/download/odin mode? What steps are you performing to boot into odin mode from a power off state?
Are you able to boot directly into recovery mode from a powered down state? What steps are you performing to boot into recovery from a powered down state? What happens as a result of those steps?
PLEASE use periods, commas and line breaks to help format your message. Help us to help you...
Gary
Click to expand...
Click to collapse
i flashed a custom rom, kernel, and twrp everything worked after that, but somehow i wasnt paying attention and turned off oem unlock before i tried to restart my phone. Now when i try and turn it on or boot into recovery i get to the Samsung logo and it says frp lock in the corner. I am holding power, home, and volume up for recovery. And im holding power, home, and volume down for odin. Once i get into odin everything seems ok, but i cannot flash anything else to it. Sorry about the grammar it was kind of late
T9EX said:
i flashed a custom rom, kernel, and twrp everything worked after that, but somehow i wasnt paying attention and turned off oem unlock before i tried to restart my phone. Now when i try and turn it on or boot into recovery i get to the Samsung logo and it says frp lock in the corner. I am holding power, home, and volume up for recovery. And im holding power, home, and volume down for odin. Once i get into odin everything seems ok, but i cannot flash anything else to it. Sorry about the grammar it was kind of late
Click to expand...
Click to collapse
First, I don't think I'll be able to help you myself. However, I'm hoping that my questions might prompt enough information that someone else can...
How do you know that you turned off OEM unlock? Are you SURE that OEM lock was turned off?
I did a quick search on your behalf, and came up with some threads that may (or may not) be useful. At the very least, you might be able to pursue the people who posted in those threads to see what resolution they came up with:
This guy seems to have resolved his issue, but didn't mention how:
http://forum.xda-developers.com/s6-edge-plus/help/bricked-frp-lock-help-to-t3209788
This one seems to think that a stock flash with ODIN should recover:
http://forum.xda-developers.com/sprint-galaxy-s6-edge-plus/help/frp-lock-t3215940
Here's another one that did a stock ODIN flash to recover:
http://forum.xda-developers.com/tmo...ompletely-bricked-s6-edge-g925t-help-t3146069
Based on these, I'd try to get my hands on a full SM-N920P ODIN image and use ODIN. It would have to be a real "P" model tar.md5, probably. Sprint might also be able to re-flash an image on there for you.
You mentioned that you tried ODIN and it didn't work. What did you try to flash with ODIN? Was it an actual Sprint ODIN file? With OEM lock, I believe that the ONLY thing you'll be able to flash is a true n920p image...
Edit: I did a quick search on sammobile for your device type, and here's a link to n920p firmware. (Note to Mods: If this link violates any XDA rules, please edit it accordingly, but if possible leave enough information that the OP can get what he/she needs to recover their device.)
http://www.sammobile.com/firmwares/database/SM-N920P/
Another thought might be to use Samsung's "smart switch" software to do an emergency recovery of the firmware. (I've never used it for that, or anything else, but others have posted that something like this is possible.)
garyd9 said:
First, I don't think I'll be able to help you myself. However, I'm hoping that my questions might prompt enough information that someone else can...
How do you know that you turned off OEM unlock? Are you SURE that OEM lock was turned off?
I did a quick search on your behalf, and came up with some threads that may (or may not) be useful. At the very least, you might be able to pursue the people who posted in those threads to see what resolution they came up with:
This guy seems to have resolved his issue, but didn't mention how:
http://forum.xda-developers.com/s6-edge-plus/help/bricked-frp-lock-help-to-t3209788
This one seems to think that a stock flash with ODIN should recover:
http://forum.xda-developers.com/sprint-galaxy-s6-edge-plus/help/frp-lock-t3215940
Here's another one that did a stock ODIN flash to recover:
http://forum.xda-developers.com/tmo...ompletely-bricked-s6-edge-g925t-help-t3146069
Based on these, I'd try to get my hands on a full SM-N920P ODIN image and use ODIN. It would have to be a real "P" model tar.md5, probably. Sprint might also be able to re-flash an image on there for you.
You mentioned that you tried ODIN and it didn't work. What did you try to flash with ODIN? Was it an actual Sprint ODIN file? With OEM lock, I believe that the ONLY thing you'll be able to flash is a true n920p image...
Edit: I did a quick search on sammobile for your device type, and here's a link to n920p firmware. (Note to Mods: If this link violates any XDA rules, please edit it accordingly, but if possible leave enough information that the OP can get what he/she needs to recover their device.)
http://www.sammobile.com/firmwares/database/SM-N920P/
Another thought might be to use Samsung's "smart switch" software to do an emergency recovery of the firmware. (I've never used it for that, or anything else, but others have posted that something like this is possible.)
Click to expand...
Click to collapse
do you happen to know specifically which image i will have to flash? I'm still kinda new to this world and slowly teaching myself everything through trial and error.
T9EX said:
do you happen to know specifically which image i will have to flash? I'm still kinda new to this world and slowly teaching myself everything through trial and error.
Click to expand...
Click to collapse
I posted a link. There's only one image available at that link. If it's zip'd, unzip it to a file with an extension of "tar.md5"
That goes into the "AP" (or "PDA") slot for ODIN.
Now, I'm going to get on my soapbox for a moment:
Don't flash stuff on your phone without knowing ahead of time the steps to get it back to stock, AND having the tools/files needed to do so. If you ignore this "advice", you have only yourself to blame for any troubles. You're lucky that sammobile has a stock firmware file. (You won't find any AT&T variant files there for this phone.) If they didn't have that stock firmware file, you'd be screwed.
Learn FIRST... and always be prepared for "Uh oh"
He fixed his problem friend I have the same problem.
Dark235 said:
He fixed his problem friend I have the same problem.
Click to expand...
Click to collapse
I fixed mine by extracting each .img file from the stock ROM, then re-compressed back into a .tar file, then flashed each one individually. I don't know if that's what fixed it but that's what I did.
T9EX said:
I fixed mine by extracting each .img file from the stock ROM, then re-compressed back into a .tar file, then flashed each one individually. I don't know if that's what fixed it but that's what I did.
Click to expand...
Click to collapse
Thank you very much for your answer I'll try.
T9EX said:
Well i flashed Tdunham's rom on the SM-N920P also flashed the second version of Freeza's beastmode kernel and twrp all is well after that unfortunately after doing some looking i found that i must have clicked oem unlock and turned it off and didnt know and shut it off now i get a custom binary blocked by frp lock in the upper left hand corner and i cant boot up the phone or access the bootloader because of it but i can switch to download mode but everything i try to flash comes up as failed can anyone tell if i can fix this?
Click to expand...
Click to collapse
To solve the FRP lock is actually very simple
I'll give you a reminder :“OTG cable”
Dark235 said:
Thank you very much for your answer I'll try.
Click to expand...
Click to collapse
Did you ever manage to fix it?
T9EX said:
Did you ever manage to fix it?
Click to expand...
Click to collapse
Not no fix
Dark235 said:
Thank you very much for your answer I'll try.
Click to expand...
Click to collapse
Dark235 said:
Not no fix
Click to expand...
Click to collapse
Must have been pure luck on my end then
T9EX said:
Must have been pure luck on my end then
Click to expand...
Click to collapse
You have a rom to try.
Dark235 said:
You have a rom to try.
Click to expand...
Click to collapse
I don't quite follow. What exactly do you mean?
T9EX said:
I don't quite follow. What exactly do you mean?
Click to expand...
Click to collapse
You repair you note?
Dark235 said:
You repair you note?
Click to expand...
Click to collapse
Yes I did.
T9EX said:
Yes I did.
Click to expand...
Click to collapse
How did please help?
Dark235 said:
You repair you note?
Click to expand...
Click to collapse
Dark235 said:
How did please help?
Click to expand...
Click to collapse
Well first do you have a software on your computer that has the ability to compress .img files into .tar files? And I would personally recommend having 7zip/WinRAR that way you can actually access the .img files on the stock ROM
T9EX said:
Well first do you have a software on your computer that has the ability to compress .img files into .tar files? And I would personally recommend having 7zip/WinRAR that way you can actually access the .img files on the stock ROM
Click to expand...
Click to collapse
First. Stock ROM img to. Tar =. Tar flash odio?

need help with sister in laws phone.

hey everyone...this is my first post on xda, i need a little help with my sisters in laws phone. basically shes got some crazy ex who has rooted her phone and im trying to fix it for her since hes making her life difficult. i can tell he has a custom bootloader installed. when i boot into recovery its odin not the normal bootloader. i can still boot into download mode but the phone wont boot up...when it does it just says that the firmware update encountered a problem and to use kies in recovery. im not super technically saavy but have flashed a tablet or too. nothing major. any help would be greatly appreciated. i just want this thing back to stock bootloader and firmware like when it came from att. does that sound like its possible. i tried to use some write ups i found online to rewrite the stock firmware and thats when it quit booting up. thanks in advance for any help people!
wigglesrewind said:
hey everyone...this is my first post on xda, i need a little help with my sisters in laws phone. basically shes got some crazy ex who has rooted her phone and im trying to fix it for her since hes making her life difficult. i can tell he has a custom bootloader installed. when i boot into recovery its odin not the normal bootloader. i can still boot into download mode but the phone wont boot up...when it does it just says that the firmware update encountered a problem and to use kies in recovery. im not super technically saavy but have flashed a tablet or too. nothing major. any help would be greatly appreciated. i just want this thing back to stock bootloader and firmware like when it came from att. does that sound like its possible. i tried to use some write ups i found online to rewrite the stock firmware and thats when it quit booting up. thanks in advance for any help people!
Click to expand...
Click to collapse
Scroll down to the notes section in the OP of this link. http://forum.xda-developers.com/showthread.php?t=3149146
Grab ye file from step for and follow instructions. If she is rooted then this will work. It'll take her back to 4.4.2 unrooted.
dirtydodge said:
Scroll down to the notes section in the OP of this link. http://forum.xda-developers.com/showthread.php?t=3149146
Grab ye file from step for and follow instructions. If she is rooted then this will work. It'll take her back to 4.4.2 unrooted.
Click to expand...
Click to collapse
Thanks for taking the time to help with this issue. that file didnt work, i flashed the G900A_OC4_Stock_Partitions firmware and its at least working again. thanks again to everyone who looked and especially dirtydodge for taking time.
Phone is working again guys but was wondering if anyone knows why it keeps giving me this security notice pop up...says that unauthorized actions have been detected and gives me the option to restart or cancel. Sounds like it has something to do with KNOX from my searching. Trying to solve this without rooting. When i check the KNOX counter in D/L mode it says 0x0. Ive updated firmware and security updates to latest versions and it hasnt helped. Anyone have any pointers? As always any help is greatly appreciated. Searched around the web and xda and didnt find what i was looking for.
@wigglesrewind. Chances are is that the phone is still rooted and that's why your getting the notification. Go to the pay store and download "root checker" and see what it says. Also what is your version & baseband. I'm not sure why the "downgrade to nce" file didn't work for you. It might have been a bad download but you should be able to use it if your still on 0C4.
Thanks again dirtydodge for contributing. I did a check with root checker and it says root is not installed. Also used terminal emulator and get a dollar sign in the terminal, not the hash tag. Any ideas?
wigglesrewind said:
Thanks again dirtydodge for contributing. I did a check with root checker and it says root is not installed. Also used terminal emulator and get a dollar sign in the terminal, not the hash tag. Any ideas?
Click to expand...
Click to collapse
I'm not familiar with terminal emulator. The only time I've ever gotten the notification that you talking about is when i have root apps on the phone and certain things aren't froze. But you need to be rooted and have titanium backup to freeze them. What version is on the phone.
Sorry, forgot to add that in the last post...
Baseband version oc4
Kernel 3.4.0
Build number LRX21T.G900AUCU4BOF3
Let me know if you need any other info. Like i said im not very experienced in this
But thanks again for your help. Its greatly appreciated.
wigglesrewind said:
Sorry, forgot to add that in the last post...
Baseband version oc4
Kernel 3.4.0
Build number LRX21T.G900AUCU4BOF3
Let me know if you need any other info. Like i said im not very experienced in this
But thanks again for your help. Its greatly appreciated.
Click to expand...
Click to collapse
Ok well it sounds like your on the latest firmware version. The phone may still have a trace of root somewhere. After you flashed the oc4 Kernel did you do a factory reset. Other than that I'm not sure what to do. But that does explain why you can't use the "downgrade to nce" file. The oc4 build can not be downgraded. I'd do a factory reset from the stock recovery menu and then wipe the cache. If that don't fix it then I'm out of options. Lol. Hope this helps.
Ive tried everything you mentioned except wiping the cache so I'll give that a try. Cross your fingers for me!
you flashed oc4 firmware which is why your baseband is oc4 (baseband is modem.)
What you need to do is download and odin a full odin tar file.. this will wipe everything clean and make it brand new...
Sent from my SM-G925V using XDA Free mobile app
If i were to find a full tar file would i just use the ap box in odin or would i have to do it differently? Usually those full dowloads have multiple files in them (BL and whatever the other ones are... CS maybe? Cant remember and not near the computer right now. Is that what your talking about?
wigglesrewind said:
If i were to find a full tar file would i just use the ap box in odin or would i have to do it differently? Usually those full dowloads have multiple files in them (BL and whatever the other ones are... CS maybe? Cant remember and not near the computer right now. Is that what your talking about?
Click to expand...
Click to collapse
Yup.. youre build is of3 or w.e which to my knowledge not downgradeable.. if you dont plan on keeping it rooted then you can flash latest full tar in odin using the AP slot..
I would recommend trying the oc full tar first if you plan on rerooting it.. the full tar will have multiple files including system, csc, boot etc.
Sent from my SM-G925V using XDA Free mobile app
Thanks alot! I'll find a full tar on here and odin it and see if that fixes it
does anyone have that oc4 one click file or know where i can find it. see it in my searchs but its always the same google drive share and they all say the file doesn't exist.
what do you mean one click?
elliwigy said:
what do you mean one click?
Click to expand...
Click to collapse
G900AUCU3BOC4_OneClick..exe was the file name i kept coming across with links to a google drive account but the file is no longer on there. I'll keep looking. I appreciate you guys lending a hand. I know it can be frustrating trying to help someone with limited understanding of something remotely. You guys are great.
wigglesrewind said:
G900AUCU3BOC4_OneClick..exe was the file name i kept coming across with links to a google drive account but the file is no longer on there. I'll keep looking. I appreciate you guys lending a hand. I know it can be frustrating trying to help someone with limited understanding of something remotely. You guys are great.
Click to expand...
Click to collapse
i understand.. just dont know if thatll work for you lol.. you need a full odin tar.. the one click might just be for root.. try to find a full oc4 tar file

[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

Categories

Resources