Rooted my Note now it wont boot up - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

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 ..

Related

HELP! I can't boot my tab and I can't get into recovery!

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.

Flashed Germany 4.3 Stuck on Samsung Screen

Hello Guys i flashed the Germany Version of 4.3 lte last night and in doing so i have Temporarily killed my Phone.
I have tried all the Recoveries processes via Kies and Odin and i am having no luck.
I think the reason why it won't flash is because the Germany 4.3 is a Newer Version than the Stock 4.1.2.
When i'm in Odin i get sboot.bin Fail when trying to Flash the Latest Stock rom. I am able to Flash the Germany 4.3 again and that flashes but then the Phone Stays on the Samsung Flash Screen.
Could someone please Help? I have been on with this for Hours now. I think what i need is a 4.3 Version of any rom in Odin .tar format so i can at least get the phone to boot up and then maybe i can get CWM Recovery on there and flash a Stock rom that way.
Thanks in Advance
You have to remove sboot.bin and tz.bin when downgrading. Be careful, downgrading will give you Knox warranty void 0x1!
Sent from my GT-I9305 using xda app-developers app
.NetRolller 3D said:
You have to remove sboot.bin and tz.bin when downgrading. Be careful, downgrading will give you Knox warranty void 0x1!
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
I have already seen that Message in Tiny Writing. What does that mean if i get that and how do you remove sboot.bin and TZ.bin
Do i remove them from the Stock 4.1.2 or the Germany 4.3?
My head is well and truely done in. I was up till 5am trying to fix it and then when i woke i went straight back to it and i still havn't got it working.
Thanks for your help in advance.
marti4578 said:
I have already seen that Message in Tiny Writing. What does that mean if i get that and how do you remove sboot.bin and TZ.bin
Do i remove them from the Stock 4.1.2 or the Germany 4.3?
My head is well and truely done in. I was up till 5am trying to fix it and then when i woke i went straight back to it and i still havn't got it working.
Thanks for your help in advance.
Click to expand...
Click to collapse
I am in the same boat if u found a solution help me also
Currently i flashed philz recovery upon which i have flashed tgp 11.30 but have no imei baseband.
marti4578 said:
I have already seen that Message in Tiny Writing. What does that mean if i get that.
= warranty void and no way so far to remove the count .
Click to expand...
Click to collapse
AMoizK said:
I am in the same boat if u found a solution help me also
Currently i flashed philz recovery upon which i have flashed tgp 11.30 but have no imei baseband.
Click to expand...
Click to collapse
Have you got any efs backup made by yourself? Or have you ever used boeffla kernel or any other that backups efs partition?
Hbohd said:
Have you got any efs backup made by yourself? Or have you ever used boeffla kernel or any other that backups efs partition?
Click to expand...
Click to collapse
Hello I don't have any EFS Backups done by Myself and i have never used Boeffla Kernel or any other Backup. I am so at my Witts end it unreal.
I have tried to do Kies recovery and i am back at the Firmware Upgrade Encountered an Issue. Please select recovery mode in Kies and Try again.
I have no idea which way to go or what to do. I know it will be fixed but i have little Faith at the Moment.
Thanks for your help in advance.
marti4578 said:
Hello I don't have any EFS Backups done by Myself and i have never used Boeffla Kernel or any other Backup. I am so at my Witts end it unreal.
I have tried to do Kies recovery and i am back at the Firmware Upgrade Encountered an Issue. Please select recovery mode in Kies and Try again.
I have no idea which way to go or what to do. I know it will be fixed but i have little Faith at the Moment.
Thanks for your help in advance.
Click to expand...
Click to collapse
THE kies frimware intilition doesnt work as you have 4.3 bootloader and knox blocks older boot loader
dont worry when 4.3 becomes available in your area it wont have to downgrade and ultimately this method will work but still things are looking pretty bad dor the intermediatory days.
PS is ther anyway to restore baseband imei without any backup
AMoizK said:
THE kies frimware intilition doesnt work as you have 4.3 bootloader and knox blocks older boot loader
dont worry when 4.3 becomes available in your area it wont have to downgrade and ultimately this method will work but still things are looking pretty bad dor the intermediatory days.
PS is ther anyway to restore baseband imei without any backup
Click to expand...
Click to collapse
What if i download the Germany Version again and try flashing. I thought it would of worked? I am now in this situation surely the Country it comes from wouldn't make a difference? Could someone take the Germany 4.3 and make it a Working Version .tar file to flash with Odin3?
marti4578 said:
What if i download the Germany Version again and try flashing. I thought it would of worked? I am now in this situation surely the Country it comes from wouldn't make a difference? Could someone take the Germany 4.3 and make it a Working Version .tar file to flash with Odin3?
Click to expand...
Click to collapse
I ment through kies.
Hello Guys i have Fantastic News!!
I have no idea what i did different, However i have reflashed the German 4.3 on my GT-I9305 and this time to my Total Surprise it worked!!
I wish i could say what i did and it worked but i have absolutely no idea what was done differently.
Thanks all for your Help.
I will say i installed the drivers manually and just on the off chance i flashed it again with the file i downloaded last Night. I also flashed a recover trying to get it to load a recover so i could flash a zip file.
marti4578 said:
Hello Guys i have Fantastic News!!
I have no idea what i did different, However i have reflashed the German 4.3 on my GT-I9305 and this time to my Total Surprise it worked!!
I wish i could say what i did and it worked but i have absolutely no idea what was done differently.
Thanks all for your Help.
I will say i installed the drivers manually and just on the off chance i flashed it again with the file i downloaded last Night. I also flashed a recover trying to get it to load a recover so i could flash a zip file.
Click to expand...
Click to collapse
Which file can u specify pls and also which recovery also is wifi and data working
AMoizK said:
Which file can u specify pls and also which recovery also is wifi and data working
Click to expand...
Click to collapse
which file????:crying:
AMoizK said:
which file????:crying:
Click to expand...
Click to collapse
Please read the rules .
JJEgan said:
Please read the rules .
Click to expand...
Click to collapse
Can u point me to the rules
AMoizK said:
Can u point me to the rules
Click to expand...
Click to collapse
http://forum.xda-developers.com/announcement.php?f=256
5. Create a thread or post a message only once.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer. (Also refer to Rule 16)
Finally
I am so feeling sucessful right now although i didnt got 4.3 but i was sucessful in getting my imei and baseband and network back.:good:
Sorry for the late response but when you get stuck on the Samsung boot screen all you have to do is boot into Recovery and do a Factory Reset and Wipe Cache.
Another thing to remember is to flash the modem for your country otherwise you might accidently disable some frequencies and enable other useless ones.
xkwizt said:
Sorry for the late response but when you get stuck on the Samsung boot screen all you have to do is boot into Recovery and do a Factory Reset and Wipe Cache.
Another thing to remember is to flash the modem for your country otherwise you might accidently disable some frequencies and enable other useless ones.
Click to expand...
Click to collapse
Doesn't work I will syill be stuck at boot screen
AMoizK said:
Doesn't work I will syill be stuck at boot screen
Click to expand...
Click to collapse
Which 4.3 update did you flash? I used the DBT German one.
Did you flash the right modem too? It worked for me and i was using a i9305T. All i did was flash the latest modem (from the brand of phone i have which is Telstra) and did a wipe data and wipe cache.

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

[SOLVED] Bricked i9305? - No Recovery - "Get PIT for mapping" stuck - sboot.bin FAIL
Yo.
Basically been using this phone for ages, having random freezing issues for a while, so I decided to /****it and re-stock everything because it is likely that I have been an idiot with kernels/messing around with stuff once.
This freezing has persisted through stable, unstable, nightly CM 10.2/10.3/11 ROM's as well as pure stock and unrooted, so I figured it was something deeper down - the kernel, and I got a stock kernel for i9305 (attached). Everything basically went to ****, the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
No biggie, I'll just ODIN it up (3.0.7) and flash the stock firmware, except now (this did not happen before the kernel flash) it simply fails with "sboot.bin FAIL", which people claim to be a PIT error (Kies not open btw, no KiesTrayAgent either, it's on the PC though), so I grab a i9305 stock PIT that I try and flash with the stock firmware, except now it gets stuck at "Get PIT for mapping" and never moves onwards from there.
So I'm essentially stuck with a problem that can probably be fixed by a stock firmware ODIN flash, and a problem that prevents me from fixing the PIT stuff to get the stock firmware through.
I have tried ODIN-flashing CWM recovery as well as stock recovery (also attached), but I'm still stuck on the logo regardless.
Any help here? Kinda lost ATM.
EDIT: Can't link/attach the .rar with the files. :S
Just re-install your back up
Raistlin1158 said:
Just re-install your back up
Click to expand...
Click to collapse
Retarded answer.
@OP
We need more data... first, which kernel did you flash ? If you can't attach it, link to it.
Second, what stock rom did you try to flash ?
Third, are you knoxed?
Hey guys.
Cheers for the answers, I just figured it out though actually. The sboot.bin error was caused by some bootloader-stuff-thingy I could hardly explain if I got a book on it. I got ahold of another stock ROM which flashed fine, I cleaned up and all that (NAND erase all did the job), back to CM11 as TouchWiz didn't fix my problems.
To answer your questions (others might have the problem and find this thread):
http://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-odin-flashable-tar-t1971265 <- kernel
I tried to flash an "XXBMD1" stock ROM from SamMobile, it had worked previously.
I am Knoxed and have "tripeed the fuse" (trying to fix the crashing issues I went back to stock ROM, then it prompted for the 4.3 TouchWiz update which brings KNOX), so I'm without warranty (ODIN returns "KNOX Warranty Void: 1), but I guess I can consider this a learning experience as everything turned out good enough in the end.
There you go:
Based on JellyBean 4.1.2_XXBMD1 <--- You can't flash 4.1.2 because of the knox bootloader.
Had you tried a stick 4.3 you might have been sucessfull
daedric said:
Retarded answer.
Click to expand...
Click to collapse
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
soft bricks aren't fixed by restoring nandroids.
Update odin and change usb cable and port.
Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
chongc1996 said:
soft bricks aren't fixed by restoring nandroids.
Click to expand...
Click to collapse
A nandroid wouldn't do any harm as soon as he got a recovery working
Raistlin1158 said:
Update odin and change usb cable and port.
Click to expand...
Click to collapse
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]
daedric said:
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
A nandroid wouldn't do any harm as soon as he got a recovery working
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]
Click to expand...
Click to collapse
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved
.... the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
Click to expand...
Click to collapse
chongc1996 said:
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved
Click to expand...
Click to collapse
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.
daedric said:
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.
Click to expand...
Click to collapse
ok sir, you are right, calm down, I'm out of here.
Cheers for the helpful as well as not-so-helpful responses, all back up and running now.

Urgent help. Have I bricked my new s10?

Fixed now ? I formatted data in twrp and rebooted. All is well. I'll leave these pics here for anyone having the same panic as I did!
Could you explain it how you've bricked it, and then what have you done to fix it ?
phone is not bricked. those screen shots just imply your data cant be viewed. easy fix, flash new firmware in odin and if you want to root and flash twrp, just follow the normal steps to do so. you shouldnt have any issues doing that
Nikola Jovanovic said:
Could you explain it how you've bricked it, and then what have you done to fix it ?
Click to expand...
Click to collapse
I've fixed it now. Details in the 1st post. Thanks
Geekser said:
phone is not bricked. those screen shots just imply your data cant be viewed. easy fix, flash new firmware in odin and if you want to root and flash twrp, just follow the normal steps to do so. you shouldnt have any issues doing that
Click to expand...
Click to collapse
Thanks for that. I did fix the issue as I've mentioned in the first post.
Before facing this issue, I'd already followed an online guide and already flashed TWRP_S10_Magisk_Prepatched.tar and Encryption_Disabler_S10_S10_S10E.zip as that's what I did before flashing custom roms with my S9. Having reformatted data and successfully rebooting, I'm now ready to try and root the ROM but having read more guides, I'm not sure I can!
I'm looking for some advice as to the best way to proceed. I'd like the phone rooted, is this possible as I've already flashed TWRP_S10_Magisk_Prepatched.tar and Encryption_Disabler_S10_S10_S10E.zip?
Cheers for the replies.
?

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!

Categories

Resources