Database Develop

[Q] [URGENT] Odin question (doesnt specify anywhere))

Hey guys ive been trying to get all i need to flash xxjpy firmware just one question?
i saw (by complete accident i might add) a guide to ''how to flash with odin'' and the guy or whatever said i need an unlocked sgs - simlock free phone as it wer, is that true? Mine is a branded vodafone 100% locked on it. Will something unspeakable happen if i try to flash it this way? (Brand new phone so im kinda nervous)
Any help may be exchanged for sexual favors xD
ps: Only hot women are elligible for the above

It's probably safer to unlock your phone before you flash it using ODIN, for obvious reasons..
P.S. I pass on thy offer.
EDIT: To unlock your phone, try this tool: http://forum.xda-developers.com/showthread.php?t=803682

So i should unlock then flash with odin......ok
one last questio Is it a permanent unlock or is it more like the iphone ultrasn0w type of deal? which needs to be unlocked everytime you update/restore?

Might be easier just to reg hack kies to get xxjpy?

jgclifton said:
Might be easier just to reg hack kies to get xxjpy?
Click to expand...
Click to collapse
Its not like i diddnt think of that, i wanted the bujp5 modem
So.... im on froyo, need to backup my rom(warranty reason if i screw anything up) before i unlock and root the phone can i do that without flashing with odin?

calexus1182 said:
Its not like i diddnt think of that, i wanted the bujp5 modem
So.... im on froyo, need to backup my rom(warranty reason if i screw anything up) before i unlock and root the phone can i do that without flashing with odin?
Click to expand...
Click to collapse
which rom version are you on now ? you can always get the same version from samfirmware.com(you need to sign up to d/l the firmware) that your currently on.
If you really need to back up your rom then you'll need ROM manager & the phone needs to be rooted as well, the easiest way is to use One click root.
You don't need to have an unlocked/unbranded phone to use odin, you just need to have kies installed for the usb drivers & for kies to be exited whilst using odin.
Here is a pretty good guide for how to use odin, take you time read it throughly, make sure you understand it & remember your doing this at your own risk

calexus1182 said:
Its not like i diddnt think of that, i wanted the bujp5 modem
So.... im on froyo, need to backup my rom(warranty reason if i screw anything up) before i unlock and root the phone can i do that without flashing with odin?
Click to expand...
Click to collapse
If its just the modem your after check Docs thread he has a list of modems for download.

where can i find th csc files you know the ususal bloatware crap?

calexus1182 said:
where can i find th csc files you know the ususal bloatware crap?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=787163

tragusman said:
http://forum.xda-developers.com/showthread.php?t=787163
Click to expand...
Click to collapse
Thanks With this im all set right? If for any reason i have to take it to the store for repair or whatever

Well ive done it sgs is stuck on the blackscreen right after booting animation GAAHHHH

[Q] How to root galaxy note GT-N7000BDULB3 version

Hello xda developers
I am wondering if someone can answer a few questions i have about rooting my samsung note?
I'm in Australia and just got my note with vodafone on Saturday. I have been doing some searching in the dev section and I haven't found my kernel version (2.6.35.7-N7000BDULB3-CL977082) to download from dr.ketan I have also searched for it on sammobile.com with no luck also.
So from the above statement does anyone know where i can get a copy of it from or know how i can backup mine from my phone atm?
I have found a root solution however It is for the GT-N7000 model which is at rootgalaxynote.com/galaxy-note-root/how-to-root-galaxy-note-gt-n7000-method-2odinheimdall
If I followed this above method would I end up bricking the phone as the phone version are different? I found nothing on a search when comparing the two
Sorry for an the essay of a post too.

Looks like you're the only guy in the whole wide world with the exotic N7000BDULB3 GB, mate.
https://www.google.com/search?client=opera&rls=en&q=N7000BDULB3&sourceid=opera&ie=utf-8&oe=utf-8
Anyway, you can always flash and root and older Rom, then upgrade to whatever you want whilst keeping your root. Here's a little guide to downgrading and rooting I wrote some time ago, hope it helps.
You'll have a rooted KK9 rom after you're done. Then you can download any new GB version (LC1 is the latest) from here and flash it with Mobile Odin, with Everroot and Inject Superuser options ticked. That will keep your root.
Good luck.

chasmodo said:
Looks like you're the only guy in the whole wide world with the exotic N7000BDULB3 GB, mate.
https://www.google.com/search?client=opera&rls=en&q=N7000BDULB3&sourceid=opera&ie=utf-8&oe=utf-8
Anyway, you can always flash and root and older Rom, then upgrade to whatever you want whilst keeping your root. Here's a little guide to downgrading and rooting I wrote some time ago, hope it helps.
You'll have a rooted KK9 rom after you're done. Then you can download any new GB version (LC1 is the latest) from here and flash it with Mobile Odin, with Everroot and Inject Superuser options ticked. That will keep your root.
Good luck.
Click to expand...
Click to collapse
Thanks for your help I will try it as soon as I get some more free time.

I have read your post y'day, but have not replied b'coz, i was waiting for input.
As you have describe method is not safe, It will give you raise flash counter
here is review of one user from thread you have mentioned.
raj says:
March 26, 2012 at 9:42 pm
Thanks so much, and your posts are one of the easiest to follow and gives a great head start for noobs! Great Job really!
I used this method and now I see a yellow triangle.
1. Will this yellow triangle during boot up, disappear if I follow your unroot method?
2. Will my phone can be updated to ICS once Samsung officially provides upgrade to ICS for Galaxy Note?
3. I tried SetCPU, the phone became very hot, when I over clocked and it just hang. I brought it back to normal.
4. What are all the other useful, important things we can do after root, other than installing Titanium Backup etc.
Click to expand...
Click to collapse
So just follow what chasmodo have advised you.

dr.ketan said:
I have read your post y'day, but have not replied b'coz, i was waiting for input.
As you have describe method is not safe, It will give you raise flash counter
here is review of one user from thread you have mentioned.
So just follow what chasmodo have advised you.
Click to expand...
Click to collapse
Thanks for all the input really appreciated, will let ya know how i go on the weekend when i have some time to do it

chasmodo said:
Looks like you're the only guy in the whole wide world with the exotic N7000BDULB3 GB, mate.
https://www.google.com/search?client=opera&rls=en&q=N7000BDULB3&sourceid=opera&ie=utf-8&oe=utf-8
Anyway, you can always flash and root and older Rom, then upgrade to whatever you want whilst keeping your root. Here's a little guide to downgrading and rooting I wrote some time ago, hope it helps.
You'll have a rooted KK9 rom after you're done. Then you can download any new GB version (LC1 is the latest) from here and flash it with Mobile Odin, with Everroot and Inject Superuser options ticked. That will keep your root.
Good luck.
Click to expand...
Click to collapse
This might be a stupid question chasmodo so bare with me.
With the KKA firmware when extracted I get the 2 files like you said the .tar.md5 and the dll file.
In odin do i just select the .tar.md5 file under the pda option? or do i have to put the dll file in an option as well.

mattybxda said:
In odin do i just select the .tar.md5 file under the pda option? or do i have to put the dll file in an option as well.
Click to expand...
Click to collapse
Just load .tar.md5 in PDA and you're good to go.

chasmodo said:
Just load .tar.md5 in PDA and you're good to go.
Click to expand...
Click to collapse
Just tried it and it FAILED please help?

mattybxda said:
Just tried it and it FAILED please help?
Click to expand...
Click to collapse
Ok so Im trying to flash to the new UK firmware now and see if it loads up if it does i will try replace the kernel to get root that way and report back.

mattybxda said:
Ok so Im trying to flash to the new UK firmware now and see if it loads up if it does i will try replace the kernel to get root that way and report back.
Click to expand...
Click to collapse
Didnt work guys , any ideas on what i can do now.

dr.ketan said:
I have read your post y'day, but have not replied b'coz, i was waiting for input.
As you have describe method is not safe, It will give you raise flash counter
here is review of one user from thread you have mentioned.
So just follow what chasmodo have advised you.
Click to expand...
Click to collapse
Hi dr ketan
Have you got any advice for me im stuck atm, my downgrade didnt work :'( it fails at the kernel part is there away around this?

mattybxda said:
Hi dr ketan
Have you got any advice for me im stuck atm, my downgrade didnt work :'( it fails at the kernel part is there away around this?
Click to expand...
Click to collapse
Do you have Sammy drivers installed on your PC? This is important. From Dr Ketan's guide:
"Install Kies on your computer, connect your phone and make sure that all the drivers installed correctly."

chasmodo said:
Do you have Sammy drivers installed on your PC? This is important. From Dr Ketan's guide:
"Install Kies on your computer, connect your phone and make sure that all the drivers installed correctly."
Click to expand...
Click to collapse
Yeh i have kies on the computer, all was working when i was using kies before.
I
'm tried a different firmware version now so once it downloads i hope it works fingers crossed anyways. If that doesnt any more ideas?

mattybxda said:
Yeh i have kies on the computer, all was working when i was using kies before.
I
'm tried a different firmware version now so once it downloads i hope it works fingers crossed anyways. If that doesnt any more ideas?
Click to expand...
Click to collapse
Yeah...try a different PC Odin version if it fails again.

chasmodo said:
Yeah...try a different PC Odin version if it fails again.
Click to expand...
Click to collapse
Thanks I will try that now I think i am also going to try uninstalling Kies then reinstalling it just as a per-caution. Will let ya know how i go.

mattybxda said:
Thanks I will try that now I think i am also going to try uninstalling Kies then reinstalling it just as a per-caution. Will let ya know how i go.
Click to expand...
Click to collapse
Also make sure that Kies is not running when you are PC Odining (ctrl+alt+del+end process).

chasmodo said:
Also make sure that Kies is not running when you are PC Odining (ctrl+alt+del+end process).
Click to expand...
Click to collapse
Thanks for the tip before about the process seemed to get further now.
Problem now it seems to be getting stuck at setup connection in odin?
the set that seems to be stuck is the setupconnection... should i just close odin and re-try?

mattybxda said:
Thanks for the tip before about the process seemed to get further now.
Problem now it seems to be getting stuck at setup connection in odin?
the set that seems to be stuck is the setupconnection... should i just close odin and re-try?
Click to expand...
Click to collapse
Did you start Odin first, then plug your Note into USB slot? Does Odin show the yellow field with the COM number in it?

chasmodo said:
Did you start Odin first, then plug your Note into USB slot? Does Odin show the yellow field with the COM number in it?
Click to expand...
Click to collapse
I have got the yellow com box wich on my computer says com4.
using odin v1.87 instead odin 1.85 like before.
using the firmware like u suggested to downgrade too as well.
seem to fail when it goes to boot.ini and the kernel section just fails there?
Think I should try flash a kernel or something?

mattybxda said:
I have got the yellow com box wich on my computer says com4.
using odin v1.87 instead odin 1.85 like before.
using the firmware like u suggested to downgrade too as well.
seem to fail when it goes to boot.ini and the kernel section just fails there?
Think I should try flash a kernel or something?
Click to expand...
Click to collapse
Don't know what else to suggest at this point. I'd leave it as it is and wait for Dr. Ketan to bail you out.
@Dr. Ketan:
Mum, help us, we're stuck here!

Rooted my Note now it wont boot up

Its been a while since ive been on these forums, i used to root and install custom roms on my X10 all the time..... but a Few days ago i rooted my Galaxy Note, following a tutorial from root galaxy note .com and my phone rebooted fine and after doing a root check my phone showed as being rooted, then last night in bed i installed lcd density and changed the settings upon restart my note is hanging on the Samsung bootup logo, i can get into odin mode where it stays on Downloading...Do not turn off target!!, i can also get it into Android System Recover, but cannot get the method of both buttons and power to work
I have been googling online for the last hour finding an answer and most seem to say i need to reflash the whole phone back to normal in odin but was wondering if there is any easier way to get back up and running especially as i didnt install any custom firmware on my phone
please help ??

This question dosn't belong to dev-forum.
But here's the quick answer:
LCD Density changes only one line that blongs to DPI in build.prop file. But you have to alter 2 lines.
So the quick way to revert your bootloop: go to recovery, make a full wipe and reflash your ROM.
If you want change your DPI: Alter it by manually change the lines in build.prop or grab ROM-Toolbox from market and make the changes.

hi thanks for the answer, when you say your rom ? ive been trying to find a custom uk 4.04 rom for the note for the last 45 mins but cant seem to find one, any ideas where ? also how would i change the build.prop without my phone being able to boot up, is it possible?
webwatcher said:
This question dosn't belong to dev-forum.
But here's the quick answer:
LCD Density changes only one line that blongs to DPI in build.prop file. But you have to alter 2 lines.
So the quick way to revert your bootloop: go to recovery, make a full wipe and reflash your ROM.
If you want change your DPI: Alter it by manually change the lines in build.prop or grab ROM-Toolbox from market and make the changes.
Click to expand...
Click to collapse

if your on ics do not ...i repeat do not wipe anything or factory reset...you will brick your phone ..search for bodivas pre rooted stock firmware and flash on odin...read the instructions very carefully
http://forum.xda-developers.com/showthread.php?t=1535025&highlight=bodivas

oh !! i did actually click wipe last night but on the android revoery not clockwork
does that mean its bricked ???
@denny said:
if your on ics do not ...i repeat do not wipe anything or factory reset...you will brick your phone ..search for bodivas pre rooted stock firmware and flash on odin...read the instructions very carefully
http://forum.xda-developers.com/showthread.php?t=1535025&highlight=bodivas
Click to expand...
Click to collapse

liamb2001 said:
oh !! i did actually click wipe last night but on the android revoery not clockwork
does that mean its bricked ???
Click to expand...
Click to collapse
if it was on android recovery you might of escaped , you will find out when you flash firmware...if it gets stuck at factory fs its bricked...good luck

thanks for your advice, feel like giving myself a big slap honestly !!!! i was going to try a custom rom and see if it allowed that to work, where would i find an original 4.04 rom for the uk and o2 ?
@denny said:
if it was on android recovery you might of escaped , you will find out when you flash firmware...if it gets stuck at factory fs its bricked...good luck
Click to expand...
Click to collapse

liamb2001 said:
oh !! i did actually click wipe last night but on the android revoery not clockwork
does that mean its bricked ???
Click to expand...
Click to collapse
For info about the Emmc Brick bug have a check here:
http://forum.xda-developers.com/showthread.php?t=1698977

liamb2001 said:
thanks for your advice, feel like giving myself a big slap honestly !!!! i was going to try a custom rom and see if it allowed that to work, where would i find an original 4.04 rom for the uk and o2 ?
Click to expand...
Click to collapse
some handy torrents here for stock
http://forum.xda-developers.com/showthread.php?t=1590284
in future i would do a bit more reading before you muck around with your phone , and dont bother with the other sites this site has the best info

If I were you I flash a GB stock rom with pc odin. If it pass you are ok and you can wipe again but if stuck on factoryfs.img you are hardbricked.
Please put here also the link for the tutorial that you used.

i managed to use odin to reflash the original firmware and im back up and running
thanks for the help guys

Now spend some time first and read this guide.
http://forum.xda-developers.com/showthread.php?t=1424997
Don't follow other sites different than XDA. It can leave you to a eMMC hardbrick.

Thread Moved​
Dont post questions in the dev section! Read the stickies for guidelines!​

Lucky you.. Read , read and Read before you act ..
All the Best to which ever ROM you move ..

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?

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

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

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

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

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

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

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

.

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

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

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

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

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

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

Thank you~! my s10 plus is back!