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?
Related
Step by step what I did:
I rooted my tab via this tutorial: http://forum.xda-developers.com/showthread.php?t=812367
I then installed bootstrap (http://forum.xda-developers.com/showthread.php?t=981307), and after going through the steps and restarting I can't get into recovery or anything. It just sits at the logo.
How do I just reset it to factory?
If I completly broke this I think I'm going to puke... Can somebody give me a little bit of hope or help?
obihann said:
Step by step what I did:
I rooted my tab via this tutorial: http://forum.xda-developers.com/showthread.php?t=812367
I then installed bootstrap (http://forum.xda-developers.com/showthread.php?t=981307), and after going through the steps and restarting I can't get into recovery or anything. It just sits at the logo.
How do I just reset it to factory?
Click to expand...
Click to collapse
1st question .. is your tab unlock ?
2nd if not , means you gonna reflash your stock rom again via odin
3th . maybe you can use P1_add_hidden.pit via odin and press start and maybe its work , but 80% its work if didn't work u have to go for step 2
k0sh said:
1st question .. is your tab unlock ?
2nd if not , means you gonna reflash your stock rom again via odin
3th . maybe you can use P1_add_hidden.pit via odin and press start and maybe its work , but 80% its work if didn't work u have to go for step 2
Click to expand...
Click to collapse
My tab is unlocked. So I'm going to have to reflash my stock rom using odin? Where is the best place to track down the froyo rom for my tab?
obihann said:
My tab is unlocked. So I'm going to have to reflash my stock rom using odin? Where is the best place to track down the froyo rom for my tab?
Click to expand...
Click to collapse
I just found these links which may help:
http://forum.xda-developers.com/showthread.php?t=889165
http://forum.xda-developers.com/showthread.php?t=888071
Am I correct these should help?
Obihannm, I did the same yesterday.
You need the original stock firmware for your galaxy and Odin for flash it again.
Look for sam firmware in the google to grab your stock kernel, tools and guides for recovery.
With luck and patience, it is possible ressurrect your tab, but It will back unrooted and maybe you get a locked bootloader.
Just go here and follow attached guide guide.
Thanks guys, I will be up late trying this for sure. I noticed that this probably should live within the QA area not Genreal, so if a Mod or Admin wants to move it, please do.
TheATHEiST said:
Just go here and follow attached guide guide.
Click to expand...
Click to collapse
That would end up with me having gingerbread correct? Should I try to first restore it to factory since right now I can't even enter recovery? Or is it a moot point and I may as well go forward get gingerbread on it?
k0sh said:
1st question .. is your tab unlock ?
2nd if not , means you gonna reflash your stock rom again via odin
3th . maybe you can use P1_add_hidden.pit via odin and press start and maybe its work , but 80% its work if didn't work u have to go for step 2
Click to expand...
Click to collapse
wait by unlocked do you mean rooted? it is rooted but that is it...
obihann said:
That would end up with me having gingerbread correct? Should I try to first restore it to factory since right now I can't even enter recovery? Or is it a moot point and I may as well go forward get honeycomb on it?
Click to expand...
Click to collapse
You dont need to enter any recovery at all. Just "download" mode.
Go and read the guide.
TheATHEiST said:
You dont need to enter any recovery at all. Just "download" mode.
Go and read the guide.
Click to expand...
Click to collapse
OK, a few deep breaths and some "reading" (a new concept for me it seems) later I think I have a bit of a better understanding.
So reading through the overcome guide and a few other threads I think my issue is I must have had a protected bootloader, and that bootstrap program would have frigid that up (there probably was a warning if I slowed down). So that means my issue is my bootloader... Am I correct thus far?
If this is true, does this mean my current rom is actually fine, and fixing my bootloader is my #1 goal?
From there I can insteall the overcome rom, the normal gingerbread rom, or go back to stock? As I see it overcome/gingerbread is the best option.
Just install the stock rom, once back to normal if you have a locked bootloader patch it
All that you need in one handy page
http://forum.xda-developers.com/wiki/index.php?title=File:SamsungGalaxyTab.png
TheATHEiST said:
You dont need to enter any recovery at all. Just "download" mode.
Go and read the guide.
Click to expand...
Click to collapse
I read through the guide you linked to as well as this one (http://forum.xda-developers.com/showthread.php?t=1078622). You suggest I only need to access "download" mode, which I discovered how to do last night. Should Heimdall or other applications be able to see my device via download mode? Or is there a step I am missing.
As well I noticed in the guide you linked me it references patching the bootloader if it is locked, do I need to patch my bootloader or replace it completely as it seems to be broken?
I want to learn this stuff, this I read, and now I am asking. Again all help is appreciated.
Heimdall doesn't seem to do anything at all. I followed the guides as I best understood, and when it came time to hit the start button it instantly said completed with no actual results...
Any ideas?
a coworker was nice enough to help me out, using the stock rom with an unlocked bootloader he was able to bring it back for me. I'm now running froyo, rooted, and a unlocked boot loader so I should have no issues putting overcome on it.
Hey guys, I'm new to this forum and I got my Galaxy Note a few weeks ago.
And today I tried to root it, but I think somehow it went wrong, now my Note could be turnned on, but the screen just stayed black. No logo, just sounds. The two 'buttons' below would light up too.
Any suggestions on how to fix it?
Try to go into download mode and reflash a gb stock rom via odin
Sent from my GT-N7000 using xda app-developers app
Jestina said:
Hey guys, I'm new to this forum and I got my Galaxy Note a few weeks ago.
And today I tried to root it, but I think somehow it went wrong, now my Note could be turnned on, but the screen just stayed black. No logo, just sounds. The two 'buttons' below would light up too.
Any suggestions on how to fix it?
Click to expand...
Click to collapse
Why do you not give us a few more details?
What did you do, where did you start, what went wrong?
ThaiDai said:
Why do you not give us a few more details?
What did you do, where did you start, what went wrong?
Click to expand...
Click to collapse
Okay, I tried to root it using a pre-rooted rom, N7000DXLC2 and some md5 and tar file that came along with it, but I'm not sure if I'm doing it correctly, my actual baseband is LR1 and the kernel is LR2.
At first, after attempting to root it, I kinda of did it successfully, I reached the green android alien place, but there's alot of pop up saying that this progress ended (something like that, couldn't remember.)
So I decided, to find and download my actual baseband's stock rom and try to use Odin to flash it, it succeeded, but the problem is, my screen is staying black this time, But I know that my phone is still working, just that the screen is not displaying anything..
Are you able to get into download mode?
When you tried to flash the rooted ROM in ODIN was it a 3 part file or a single file?
Did you setup ODIN correctly as per instructions on this site?
CJSlim79 said:
Are you able to get into download mode?
When you tried to flash the rooted ROM in ODIN was it a 3 part file or a single file?
Did you setup ODIN correctly as per instructions on this site?
Click to expand...
Click to collapse
Yeah I did get into the download mode, the first ROM was 3 part file, second one was a single file.. and yeah setup correctly.
Nobody knows a fix for this?
Jestina said:
Nobody knows a fix for this?
Click to expand...
Click to collapse
Ok -
You can get back into download mode - what happens when you try to flash a stock GB ROM in PC Odin, *Use a 1 part file from here*
http://forum.xda-developers.com/showthread.php?p=26455511#post26455511
You need to provide as much info as you can otherwise it is hard to help...
In ODIN - You said it was setup correctly? Where did you confirm this?
Jestina said:
Nobody knows a fix for this?
Click to expand...
Click to collapse
Read here. http://androidadvices.com/update-galaxy-note-n7000-gingerbread-xxlc1-236-firmware/2/
Read it carefully and do it at your own risk if you decide to flash it.
I don't think it'll work.. I'm already back on my actual baseband, its just the problem with the screen, its black and it won't display anything. My phone is still working.
Jestina said:
I don't think it'll work.. I'm already back on my actual baseband, its just the problem with the screen, its black and it won't display anything. My phone is still working.
Click to expand...
Click to collapse
Are you on a complete STOCK setup? or custom kernel?
This is very odd - sounds like possible hardware fault if your phone is working but no screen - You definitely flashed the correct ROM yeah? I would still give a try to reflashing the STOCK GB via PC Odin..
Question - When you goto Download Mode - Do you see the Android Guy? If so there's something wrong with your flashed ROM and not a screen fault so a re-flash should resolve that..
+1, Definitely not a screen problem if you are able to go in download mode & see the green guy.
Just try to reflash via PC odin a GB ROM.
CJSlim79 said:
Are you on a complete STOCK setup? or custom kernel?
This is very odd - sounds like possible hardware fault if your phone is working but no screen - You definitely flashed the correct ROM yeah? I would still give a try to reflashing the STOCK GB via PC Odin..
Question - When you goto Download Mode - Do you see the Android Guy? If so there's something wrong with your flashed ROM and not a screen fault so a re-flash should resolve that..
Click to expand...
Click to collapse
I will try re-flashing it again, the problem is now I can't see whats on my screen, but I can get to download mode by prediction though...
Jestina said:
I will try re-flashing it again, the problem is now I can't see whats on my screen, but I can get to download mode by prediction though...
Click to expand...
Click to collapse
Ok but in download mode - do you see the Android guy?.....or girl..........
If not there's a chance you've a screen problem.. or you flashed something you shouldn't have...
Give the Stock GB Flash a go through ODIN and report back..
Black Screen
Jestina said:
I will try re-flashing it again, the problem is now I can't see whats on my screen, but I can get to download mode by prediction though...
Click to expand...
Click to collapse
First sorry for my english.
If your phone is open but screen is not open. TRY following steps.
Flash this rom with Odin ( N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar )
Kernel: CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5
if loading stop to hidden.img dont worry. try again loading rom.
i think solving the problem.
CJSlim79 said:
Ok but in download mode - do you see the Android guy?....or girl..????........
..
Click to expand...
Click to collapse
Seriously... your kidding right??
geist_100 said:
First sorry for my english.
If your phone is open but screen is not open. TRY following steps.
Flash this rom with Odin ( N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar )
Kernel: CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5
if loading stop to hidden.img dont worry. try again loading rom.
i think solving the problem.
Click to expand...
Click to collapse
I would go with this route as well
@OP, I think what messed up your phone is you inadvertently flash either a wrong kernel..(a kernel meant for GB but your already on ICS or the other way around as well)
had the same issue you have before... **** I flashed a kernel not design for our NOTE....
After that, my phone just stays black.. but I could actually go to download mode... so what I did? Flashed it back to GB stock and work my way from there...
Hope that helps something bud
Cheers!
CJSlim79 said:
Ok but in download mode - do you see the Android guy?.....or girl..........
If not there's a chance you've a screen problem.. or you flashed something you shouldn't have...
Give the Stock GB Flash a go through ODIN and report back..
Click to expand...
Click to collapse
lol that cracked me up thanks,
Thought android was androgenious, mwahahah
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
lol that cracked me up thanks,
Thought android was androgenious, mwahahah
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I'm pleased a couple of people picked up on it
Erm.. I've downloaded the CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5, but when I open it up its a zImage file.
What am I suppose to do with it? x_x
Edit; Nvm, got it!
letters_to_cleo said:
Seriously... your kidding right??
I would go with this route as well
@OP, I think what messed up your phone is you inadvertently flash either a wrong kernel..(a kernel meant for GB but your already on ICS or the other way around as well)
had the same issue you have before... **** I flashed a kernel not design for our NOTE....
After that, my phone just stays black.. but I could actually go to download mode... so what I did? Flashed it back to GB stock and work my way from there...
Hope that helps something bud
Cheers!
Click to expand...
Click to collapse
I did what you said, but now my note still stays black.. I guess its my screen problem now huh.. Weird..
Today I bought an ATT galaxy s6 edge for about $350, I was told it wouldn't boot past the powered by Android screen. I thought it would be an easy flash in odin. So I flaBootscreem ock 0I2 firmware and it passed successfully. But it still won't pass the Samsung logo. I've tried a few other methods people have posted. Like wipe data and cache but it still won't work. Now I feel bad that I spent the money on a paperweight. Anyone have any ideas?
Did you try to flash the latest firmware, with all 4 files via odin?
Here is the link for the latest. https://drive.google.com/file/d/0B6SkpQCi70hHY2NnZExnbThTblE/view
GayCasper said:
Here is the link for the latest. https://drive.google.com/file/d/0B6SkpQCi70hHY2NnZExnbThTblE/view
Click to expand...
Click to collapse
I tried OI2 which is what is on it. And I did flash all 4 files. I'll try the newest one. But I believe the efs file is corrupted
Ok, can you get to the recovery in the phone? Tell me if you see anywhere in the bottom "dm verify verification failed".
xhhb said:
Ok, can you get to the recovery in the phone? Tell me if you see anywhere in the bottom "dm verify verification failed".
Click to expand...
Click to collapse
Yes it does say that at the bottom. I'm in the process of trying to sell it as I don't have the time right now to deal with it. But if its something simple I can download to fix I would. As I also don't have home Internet all download are through my carrier
Oh then its really easy, reflash latest software via odin with the 4 files. In options tab make sure you select the clean efs folder and there you go my friend
SmokeyTech1 said:
Yes it does say that at the bottom. I'm in the process of trying to sell it as I don't have the time right now to deal with it. But if its something simple I can download to fix I would. As I also don't have home Internet all download are through my carrier
Click to expand...
Click to collapse
Were you able to bring it to life?
xhhb said:
Were you able to bring it to life?
Click to expand...
Click to collapse
Yes, I took it into a store and they flashed it for me. The only problem is the efs folder is corrupt and I don't have an imei number and have to manually connect to my carrier, also there's a battery drain
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/
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!