Black screen. Help! - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

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

Related

Flickering screen while flashing via ODIN

Any help with this? I rooted & installed CWM on my Wildfire with no issues, but it seems like this phone's a tough nut. Can't start it up now, screen keeps flickering if I try to turn it on, don't think it can even boot up.
Your prompt reply is much appreciated!
Serenadier said:
Any help with this? I rooted & installed CWM on my Wildfire with no issues, but it seems like this phone's a tough nut. Can't start it up now, screen keeps flickering if I try to turn it on, don't think it can even boot up.
Your prompt reply is much appreciated!
Click to expand...
Click to collapse
Wildfire wrong section, this mini thread
apisfires said:
Wildfire wrong section, this mini thread
Click to expand...
Click to collapse
I mean I've done it before on my Wildfire, but there's a problem with this on the Galaxy Mini. Problem phone in question is the Galaxy Mini now.
Sorry for the misunderstanding.. any help you can offer me?
installed from where and how?
kandros said:
installed from where and how?
Click to expand...
Click to collapse
Okay so first I downloaded the OPS, Gingerbread firmware and ODIN. Then I installed Kies for drivers, and then I opened ODIN, inserted the OPS and Gingerbread firmware file, started the process.
Somehow when it came to the reboot part, the phone just kept rebooting (screen lights up, turns off, pause, repeats again) and it hasn't worked since.
Then now there's an error with setup connection which presumably has something to do with the drivers, so I reinstalled it but now setup connection keeps occurring...
Okay, now, I tried doing the whole process again... I'm stuck at 'Close serial port and wait until rebooting' as the phone constantly flickers on and off repeatedly with no sign of anything going on.
Somebody please help :/
Still the same?
Firmware from Sammobile.com?
Wait...prob is while installing cwm or GB?
Are you using the right version of odin,i think it's 4.31...?
Sent from my GT-S5570 using XDA App
Small_town_boy said:
Are you using the right version of odin,i think it's 4.31...?
Sent from my GT-S5570 using XDA App
Click to expand...
Click to collapse
Yup, 4.31, TASS v1.0 as OPS. S5570DXKPD_S5570OLBKPD for the firmware.
Problem now is I think the flashing works.. but somehow, the phone is somehow corrupt in a way that boot is not possible - nothing's possible except download mode.
I haven't played around with Samsungs, mostly HTCs so this is uncharted territory for me.
roofrider said:
Still the same?
Firmware from Sammobile.com?
Wait...prob is while installing cwm or GB?
Click to expand...
Click to collapse
Yup, firmware from Sammobile.com. Problem is while installing GB. Will trying to install CWM first at least alleviate some of the problem?
In fact... I can't even boot into the original recovery. All that happens is the phone boots... and goes into an insane loop. Can't do anything else other than that.
Thanks guys..
download again the firmware Nd retry.. till downloading mode works you are safe.. in general section FAQ post there is link and guide
Sent from my GT-S5570 using Tapatalk
Serenadier said:
Yup, 4.31, TASS v1.0 as OPS. S5570DXKPD_S5570OLBKPD for the firmware.
Problem now is I think the flashing works.. but somehow, the phone is somehow corrupt in a way that boot is not possible - nothing's possible except download mode.
I haven't played around with Samsungs, mostly HTCs so this is uncharted territory for me.
Yup, firmware from Sammobile.com. Problem is while installing GB. Will trying to install CWM first at least alleviate some of the problem?
In fact... I can't even boot into the original recovery. All that happens is the phone boots... and goes into an insane loop. Can't do anything else other than that.
Thanks guys..
Click to expand...
Click to collapse
list full name file you downloaded
1?
2?
3?
sometime, the name is wrong
Fixed?
Try flashing a multi package 2.3.x file if the latest is a one package...
Btw are u Latin and using a Latin version?
kandros said:
download again the firmware Nd retry.. till downloading mode works you are safe.. in general section FAQ post there is link and guide
Sent from my GT-S5570 using Tapatalk
Click to expand...
Click to collapse
Even when the firmware is being flashed, the screen constantly flashes on and off. Is this normal?
I'd try that, but I don't know if it would work...
roofrider said:
Fixed?
Try flashing a multi package 2.3.x file if the latest is a one package...
Btw are u Latin and using a Latin version?
Click to expand...
Click to collapse
I'm on Asia version, I downloaded a 2.3.4 Asian version too.
apisfires said:
list full name file you downloaded
1?
2?
3?
sometime, the name is wrong
Click to expand...
Click to collapse
1. From ODIN 4.38 + Tass.Ops.rar -
a. Tass_V1.0.ops
b. S5570_Odin Multi Downloader v4.38.exe
2. S5570DXKPD_S5570OLBKPD.zip
I don't think it's wrong, is it...?
Check for Tass_ops file sometimes it might be a possibility that ur using a wrong one.
dkn91 said:
Check for Tass_ops file sometimes it might be a possibility that ur using a wrong one.
Click to expand...
Click to collapse
I downloaded everything again from the Gingerbread update thread, redid everything as instructions... the phone is still in a really fast bootloop.
Serenadier said:
I downloaded everything again from the Gingerbread update thread, redid everything as instructions... the phone is still in a really fast bootloop.
Click to expand...
Click to collapse
Try flashing a 2.3.3 multi package firmware
roofrider said:
Try flashing a 2.3.3 multi package firmware
Click to expand...
Click to collapse
Doing that right away.
Is it normal for the phone to flicker on and off during the flash process, and after the flash process is complete, with ODIN showing PASS?
Okay, so installing a multi package firmware didn't work either. Now what. )': at wit's end here.
It won't flicker.
And when it's done it'll show pass.
While in download mode, Odin shows connected rite? A yellow box Appears?

Bricked via CWM

I flashed via CWM MUI v.3 cuz the v.4 needed v3 due a bug but it hang on flashing boot.IMG. so i had to took out battery. Since then no charging / detection / download mode by buttons. Possible Ultimate brick?
Can access recovery mode?
Thanks
dr.ketan said:
Can access recovery mode?
Click to expand...
Click to collapse
Dr. Ketan,
Black screen no detection no recovery
First make sure your battery is not completely empty. Try to charge with external charger or manage for other battery
Still nothing then manage for JIG as last option
Dr. KEtan,
I bricked the note with 95% then removed battery to prevent drain while briked. Will try JIG tonight., Will let u know
jeroen180 said:
Dr. KEtan,
I bricked the note with 95% then removed battery to prevent drain while briked. Will try JIG tonight., Will let u know
Click to expand...
Click to collapse
Jigged it... Its confirmed. It is the SUPER-brick. Superbrick via CWM wattaf...
jeroen180 said:
Jigged it... Its confirmed. It is the SUPER-brick. Superbrick via CWM wattaf...
Click to expand...
Click to collapse
What do you think it is related with brick? Is it your fault of kernel or ROM fault. It is really annoying situation... Im sorry for your loss man...
Im not really an expert on android, but i would consider myself an advanced user so correct me if im wrong....
Couldnt it be, that the boot.img from the rom got corrupted somehow and thats the reason why it hanged while flashing it? Coz as of how i understood what the boot.img is used for, it would explain why u cant boot in recovery/dl-mode. Simply coz there is no bootloader on ur phone. Just an idea...
Sent from my GT-N7000 using xda premium
shrooms90 said:
Im not really an expert on android, but i would consider myself an advanced user so correct me if im wrong....
Couldnt it be, that the boot.img from the rom got corrupted somehow and thats the reason why it hanged while flashing it? Coz as of how i understood what the boot.img is used for, it would explain why u cant boot in recovery/dl-mode. Simply coz there is no bootloader on ur phone. Just an idea...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Well, im not a pro too to understand that since CWM erased bootloader and did not replaced it with the other version. How about SSC? Will they notice since my counter was not reset?
Worth a try
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
Worth a try
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
If they found out its my fault.. .will they charge or call me to fix it foor like.... 200 ~ 300 EU?
I have warned in hydracore thread that CWM 6.0.1.2 caused me and another user from a different thread to softbrick.
I got bashed by the fanatics in return.
Sorry to hear about your incident.
praetorius said:
I have warned in hydracore thread that CWM 6.0.1.2 caused me and another user from a different thread to softbrick.
I got bashed by the fanatics in return.
Sorry to hear about your incident.
Click to expand...
Click to collapse
LoL i should read that..... Im getting JTAGGED soon..
jeroen180 said:
Well, im not a pro too to understand that since CWM erased bootloader and did not replaced it with the other version. How about SSC? Will they notice since my counter was not reset?
Click to expand...
Click to collapse
Looks like MIUI bug
Look hère : http://miuiandroid.com/community/index.php?threads/17408/
Envoyé depuis mon GT-N7000
@jeroen180 send it in, they wont notice, just tell them ur phone got slow sow u did a factory reset and now it refuses to boot send my sgs in that way, before the jig was know, and my gf sent her sgs plus in abot 2 weeks ago with the same story
Sent from my GT-N7000 using xda premium
Yeah, I agree, if you tell them you just had to do a factory reset because it got really slow and laggy than they shouldn't have a problem. They wouldn't bill you either unless they had prior authorization.
netopyr said:
Looks like MIUI bug
Look hère : http://miuiandroid.com/community/index.php?threads/17408/
Envoyé depuis mon GT-N7000
Click to expand...
Click to collapse
First off before you start quoting other threads in other fourms, take a minute to get your facts in order.. Miui for the note has not been released to the public as of this date because it has the possibility to brick you device as it has the unsafe Samsung kernel (yes the same kernel as your stock note ), so if your running Miui on your note than your running a leaked version (then in that case you should know the risk involved) that is either running the stock kernel or it has one of the hydracore versions as it is the only option miui has at the moment unless your on one of the cm versions. So not defending either the rom/kernel he was trying to flash or what he was coming from as he really doesn't state either .. it would help if he provided such information. Sorry to the owner but before you get your device JTAGGED you may want to check with a samasung service center because the JTAGGED will void your warranty..
jeroen180 said:
Well, im not a pro too to understand that since CWM erased bootloader and did not replaced it with the other version. How about SSC? Will they notice since my counter was not reset?
Click to expand...
Click to collapse
No ,CWM will not erase or even touch the bootloaders ,only PC ODIN can do that ,boot.img refers to the kernel ,I've had a corrupted boot.img flash once ,easily solved via PC ODIN ,the phone would start up and show the logo but nothing more if that happens .I doubt that's the case here but you could try a blind flash in PC odin and see if that works .
MR.change said:
No ,CWM will not erase or even touch the bootloaders ,only PC ODIN can do that ,boot.img refers to the kernel ,I've had a corrupted boot.img flash once ,easily solved via PC ODIN ,the phone would start up and show the logo but nothing more if that happens .I doubt that's the case here but you could try a blind flash in PC odin and see if that works .
Click to expand...
Click to collapse
How you explain the phone stays black screen after hanging in CWM with boot.img? U suggest my board broke by accident? Someone can explain?
Could it be,
that,,,, i forgot to reboot after flashing the Hydrakernel... and eMMC bricked the bootloader perhaps? since the bootloader is stored on the chip as well?

Galaxy Note Big Problem

Guys i have a big problem. Every time i turn of my phone or try to put it on download mode or recovery mode it stucks in black screen and dont responding like it's been bricked. But when i remove the battery for 2 min and place it again it's opening normaly. Im in stock filmware and just rooted. Can u tell me why this is happening? Maybe i have to flash the official filmware again or somethink?
bagelismar said:
Guys i have a big problem. Every time i turn of my phone or try to put it on download mode or recovery mode it stucks in black screen and dont responding like it's been bricked. But when i remove the battery for 2 min and place it again it's opening normaly. Im in stock filmware and just rooted. Can u tell me why this is happening? Maybe i have to flash the official filmware again or somethink?
Click to expand...
Click to collapse
Are you on stock kernel? If so then flash some safe kernel and try full wipe, if that too doesn't help, then flash stock firmware using pc odin.
I am assuming you are on ICS, as you didn't provide any info. You should have mentioned the method used for root and everything.
jeetu1981 said:
Are you on stock kernel? If so then flash some safe kernel and try full wipe, if that too doesn't help, then flash stock firmware using pc odin.
I am assuming you are on ICS, as you didn't provide any info. You should have mentioned the method used for root and everything.
Click to expand...
Click to collapse
Sorry man your right. I used cursed4eva way that i found on a youtube video and im in ICS your right. All my broblems start when i wanted to flash a custom rom and with android recovery i tried to install AbyssNotekerne.zip from my external sd. Since i couldn't cause i was getting some kind of error i think somethink about licence i stop cause i didnt want to brick my phone and after this all problems began. So any help is welcome thank you
bagelismar said:
Sorry man your right. I used cursed4eva way that i found on a youtube video and im in ICS your right. All my broblems start when i wanted to flash a custom rom and with android recovery i tried to install AbyssNotekerne.zip from my external sd. Since i couldn't cause i was getting some kind of error i think somethink about licence i stop cause i didnt want to brick my phone and after this all problems began. So any help is welcome thank you
Click to expand...
Click to collapse
Now i cant even get to download mode to use odin to flash GB rom. I tried flashing abyss kernel using srock ICS recovery and that's the main reason for current situation i think. Any help?
bagelismar said:
Now i cant even get to download mode to use odin to flash GB rom. I tried flashing abyss kernel using srock ICS recovery and that's the main reason for current situation i think. Any help?
Click to expand...
Click to collapse
Take it to a samsung service center and ask them to reset the phone. Tell them its too slow after the latest update using kies. If there is a problem with the motherboard they will report back and replace under warranty.
Else they will install the OS completely new and you can start from scratch to root and install other custom roms.
Try using USB jig to go to download mode, try it first. Jig is not expensive.
Sent from my U1 using xda premium
heavenhated said:
Take it to a samsung service center and ask them to reset the phone. Tell them its too slow after the latest update using kies. If there is a problem with the motherboard they will report back and replace under warranty.
Else they will install the OS completely new and you can start from scratch to root and install other custom roms.
Click to expand...
Click to collapse
Will my warranty be still active cause my phone is rooted...? Somehow my phone start up this morning but im afraid trying to flash somethink like GB official with odin or somethink like that cause i dont know if it will open again That means that my phone isn't bricked yet cause it's open now? Thanks a lot for help
jonpaslim said:
Try using USB jig to go to download mode, try it first. Jig is not expensive.
Sent from my U1 using xda premium
Click to expand...
Click to collapse
because he tries the jig before it cost anything
bagelismar said:
Will my warranty be still active cause my phone is rooted...? Somehow my phone start up this morning but im afraid trying to flash somethink like GB official with odin or somethink like that cause i dont know if it will open again That means that my phone isn't bricked yet cause it's open now? Thanks a lot for help
Click to expand...
Click to collapse
No it's not bricked. Yes you lose your warranty, but you can unroot your Note. Don't warry Note is so good phone, that you don't need warranty
notko said:
No it's not bricked. Yes you lose your warranty, but you can unroot your Note. Don't warry Note is so good phone, that you don't need warranty
Click to expand...
Click to collapse
Then if it's not bricked why i need to remove the battery for 1 hour and wait an other 2 hours to finally open my phone after a simple turn off? Thats why i want the warranty so i can take the phone to samsung and fix this issue. And im afraid to unroot it cause when ever i try to put my phone on recovery mode its stucks and take for ever to open againm\

[Q] About Baseband and Odin SGM

Why Odin cant detect my Galaxy Mini?
I wanna flash New Experience stock rom, but Im always stuck at White android logo...
1.) I followed the instructions PERFECTLY
2.) I pulled my battery many times and rebooted.. still nothing..
so I think of a solution, I wanna change my baseband S5570XXKPI to S5570XWKTN.. Im in the process of this... BUT! Odin cant detect my SGM... I tried rebooting it many times, it is also on USB debugging.. I also tried reinstalling the required drivers
are you on windows 8 :-/
iSeraphiel said:
Why Odin cant detect my Galaxy Mini?
I wanna flash New Experience stock rom, but Im always stuck at White android logo...
1.) I followed the instructions PERFECTLY
2.) I pulled my battery many times and rebooted.. still nothing..
so I think of a solution, I wanna change my baseband S5570XXKPI to S5570XWKTN.. Im in the process of this... BUT! Odin cant detect my SGM... I tried rebooting it many times, it is also on USB debugging.. I also tried reinstalling the required drivers
Click to expand...
Click to collapse
What does Odin have to do with flashing a Custom ROM?
Under Flashing ROM you can find the instructions.
You must have CWMR to do this. Here are the instructions for downloading and installing CWMR.
Make sure your phone is rooted.
Reaper's Scythe said:
What does Odin have to do with flashing a Custom ROM?
Under Flashing ROM you can find the instructions.
You must have CWMR to do this. Here are the instructions for downloading and installing CWMR.
Make sure your phone is rooted.
Click to expand...
Click to collapse
"I wanna flash New Experience stock rom, but Im always stuck at White android logo..."
so I think of a solution, I wanna change my baseband S5570XXKPI to S5570XWKTN.. Im in the process of this... BUT! Odin cant detect my SGM... I tried rebooting it many times, it is also on USB debugging.. I also tried reinstalling the required drivers
Please read properly.
iSeraphiel said:
"I wanna flash New Experience stock rom, but Im always stuck at White android logo..."
so I think of a solution, I wanna change my baseband S5570XXKPI to S5570XWKTN.. Im in the process of this... BUT! Odin cant detect my SGM... I tried rebooting it many times, it is also on USB debugging.. I also tried reinstalling the required drivers
Please read properly.
Click to expand...
Click to collapse
Excuse me. I missed a night worth of sleep.
I thought you tried to flash a Custom ROM via Odin.
What version of Odin are you using?
Also, changing the baseband version will not do anything good.
Can you clarify "stuck at white android logo"?
Reaper's Scythe said:
Excuse me. I missed a night worth of sleep.
I thought you tried to flash a Custom ROM via Odin.
What version of Odin are you using?
Also, changing the baseband version will not do anything good.
Can you clarify "stuck at white android logo"?
Click to expand...
Click to collapse
Oh okay 4.38
New Experience Stock rom, it has a white Android logo, just like the "android" word before the bootanimation starts..
after this, for a long time, it will become black screen, and I tried to wait for the black screen to stop, but it doesnt I waited overnight..
iSeraphiel said:
Oh okay 4.38
New Experience Stock rom, it has a white Android logo, just like the "android" word before the bootanimation starts..
after this, for a long time, it will become black screen, and I tried to wait for the black screen to stop, but it doesnt I waited overnight..
Click to expand...
Click to collapse
This is the ROM you're talking about if I'm not mistaken.
That's quite odd, if you don't mind waiting for 10 minutes so I can test it out myself. I will reply to you if I encounter the same problem
Reaper's Scythe said:
This is the ROM you're talking about if I'm not mistaken.
That's quite odd, if you don't mind waiting for 10 minutes so I can test it out myself. I will reply to you if I encounter the same problem
Click to expand...
Click to collapse
Yeah! thats it Thank you
Im still finding the fix for it..
Reaper's Scythe said:
This is the ROM you're talking about if I'm not mistaken.
That's quite odd, if you don't mind waiting for 10 minutes so I can test it out myself. I will reply to you if I encounter the same problem
Click to expand...
Click to collapse
Well it seems I can't help you, I can't even get it past the samsung.com at the beginning.
After flashing it, I suggest you wipe cache and data. From here, post it in the development thread.
Reaper's Scythe said:
Well it seems I can't help you, I can't even get it past the samsung.com at the beginning.
After flashing it, I suggest you wipe cache and data. From here, post it in the development thread.
Click to expand...
Click to collapse
Oh I almost forgot! I also experienced that ... right now im experiencing it
BTW thanks for replying
If you want to try this rom, I'll post the fix for it
iSeraphiel said:
Oh I almost forgot! I also experienced that ... right now im experiencing it
BTW thanks for replying
If you want to try this rom, I'll post the fix for it
Click to expand...
Click to collapse
Go ahead, I wouldn't mind
iSeraphiel said:
Why Odin cant detect my Galaxy Mini?
I wanna flash New Experience stock rom, but Im always stuck at White android logo...
1.) I followed the instructions PERFECTLY
2.) I pulled my battery many times and rebooted.. still nothing..
so I think of a solution, I wanna change my baseband S5570XXKPI to S5570XWKTN.. Im in the process of this... BUT! Odin cant detect my SGM... I tried rebooting it many times, it is also on USB debugging.. I also tried reinstalling the required drivers
Click to expand...
Click to collapse
Hey changing baseband wont work, i wont recommend you to change your baseband. You mite end up into hardbrick or no network problems.
Try install another rom first (try any)
then flash your desired rom.
Always DO full WIPE.
I helped you? Wow, lol., then Don't thank me, rather follow me on twitter
www.twitter.com/_aakashasaj
Sent from XDA Premium.
aakashasaj said:
Hey changing baseband wont work, i wont recommend you to change your baseband. You mite end up into hardbrick or no network problems.
Try install another rom first (try any)
then flash your desired rom.
Always DO full WIPE.
I helped you? Wow, lol., then Don't thank me, rather follow me on twitter
www.twitter.com/_aakashasaj
Sent from XDA Premium.
Click to expand...
Click to collapse
oops I already changed my basband, luckily its working fine... and autoradio said, if problem persists, try changing baseband..
my problem now

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?

Categories

Resources