Database Develop

[Q] Black screen glowing button

Phone was flashed to 2.2, however after shutting down the phone and booting it up again, I get Black SCREEN + glowing buttons.
Device : Samsung i9000 from Bell running flashed 2.2 Rom.
I've tried following this guide :
STAGE 1 (applies only if you are coming from an earlier Froyo build)
* We are now going to flash the XWJM8 firmware again (Éclair), so make sure that you load the files for this firmware in Odin.
* In PIT, load the 502.PIT file
* For PDA, select the ‘CODE_I9000XWJM8.tar.md5’ file and for PHONE, select the ‘MODEM_I9000XXJM4.tar.md5’ file. Leave all others blank.
* Make sure that the Re-partition box is checked. All other settings should be as shown in the screenshot below.
*Sorry can't post link, forum restriction*
After stage 1, Odin says Passed, my i9000 reboots with still a black screen+ glowing buttons.
I want to start Stage 2, however I can't find the file ‘JPO_JPO_U_JPP.tar’ file.
I've looked up for solution for the last 2 days and can't seem to find a solution anywhere.
Things I've tried on my own without sucess :
Flashed again this time with a CSC from bell, I've read that sometimes without CSC flashing can't be done, but even with the CSC files, my phone is still ''bricked''
Anyone have any idea how to fix this? Ultimately, I want to go back on 2.2 but for now, I just want my phone to boot again =(.

Hate to say it but it sounds like yout internal sd card is dead like MANY OTHERS who have flashed... No way to fix except to send for repairs to bell/samsung...
Sent from my GT-I9000M using XDA App

I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.

Isn't there a way to try and access internal sd card?

Have you try doing a factory reset?

Yeah, I've tried doing so, after reading and researching online, I think this could fix my problem.
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
see reply #7
However adb doesn't even reconize the phone =/

terranq said:
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Click to expand...
Click to collapse
I diddnt specifically mean that it was the flashing that did it but it is OBVIOUS that it happened after he flashed right???
It is known that flashing will sometimes "speed up" the death of an already faulty sd card and that is what I meant by my original post...
And PS... The number of people reporting their sd cards failing on stock firmware w/ no lagfix or no previous flashes to "unofficial firmware" is WAY lower than those reporting sd card death after flashing or adding lagfixes, etc...

Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing

terranq said:
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
Click to expand...
Click to collapse
And again... I did not specifically state that it was the "flashing" that killed the OP's phone. I simply stated that this seems to happen to MANY people after they flash. NOT the same thing...
Did you come to this thread to argue or to help the OP? I simply posted a reply last night stating that it seems his internal SD card is dead so that he could prepare himself for having to send it away for repairs. I did not respond to the OP to get into an arguement with anyone over "what causes the internal SD cards to fail".

Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.

cuem said:
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
Click to expand...
Click to collapse
@cuem,
Unfortunately... If it is an actual dead internal sd card (which it seems to be since the steps you followed already did not seem to fix the issue) the only way to fix it is to send it back to Bell who in turn will send it off for warranty repair.
IF you have just purchased the phone within the last 30 days (possibly 60 if Bell is still extending the DOA return policy) and you have a receipt you can take it back to Bell and get an exchange.
Again, unfortunately these are your only options to get this fixed...
Sorry to be the bearrer of bad news...

Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......

cuem said:
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
Click to expand...
Click to collapse
Ooooooo... That is not good. The American Vibrant is NOT the same as out i9000 models.
What you need to do now is search the forums for the homemade jig thread that will force your device into download mode. Search the forums and you will find it.
Be prepared to be "handy" as you will have to build the jig from scratch...
Sent from my GT-I9000M using XDA App

Yeah, I've read about the Jig thing, I've also read about heating your phone with a hairdryer,
I'm currently trying out the hairdryer, but it doesn't work =/
Might have to try the Jig thing, which seems a little complicated with ordering since I'm running out of time =/

Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.

This has happened to me, I just flashed with an older version, for me JM5 worked fine.

cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
I had the same thing after flash and spent many hours and tried many different methods to get it back up with no success.
I'm leaving the country for Europe on January 2nd for vacation. This was the last thing I needed... Hopefully I get it back before then, but I'm not holding my breath.

cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
Well... At the very least at least the firmware is now correct so you can send it away for repair if you need to...
Sent from my GT-I9000M using XDA App

I followed this guide
http://www.tunandroid.com/content/i...du-firmware-i9000xwjpa-pour-samsung-galaxy-s/
I believe now oneclicklagfix is installed on my device, can I flash again or that'll brick my phone, how do I uninstall oneclicklagfix if I can't boot up the phone but only acesss clockwork mod menu?

[Q] What fixes have you tried for your dead i9000m?

So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?

patman18 said:
So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?
Click to expand...
Click to collapse
i bricked my phone many times.i flash back to xxjm8 from samfirmwares.com, thats the password aswell you will have to register its free. if it does not work first time try flashinging again.use ordin 1.7 its good.you can get all your updates from ther without getting confussed on the fourm, i have been stuck on that screen many times trying to root my fone on the new 2.2.1 firmware.go to google type xxjpu galaxy root. the is a web site give you xxjpx rooted with voodoo + some cool tools follow all the steps to the letter,if you can print it off its only three pages .

what about adb ? Did tried it ?

a hammer
i flashed back to jh2 after it was in a boot loop from jk4 and then it wouldnt even turn on.. sent back for repair

bobekk said:
what about adb ? Did tried it ?
Click to expand...
Click to collapse
tried it
i can't get the phone to connect. keep getting the stupid "unmounted sd......." crap.
but the funny thing is i can get in to dnl mode reflash with odin, and everything works fine no error codes. But the phone won't boot. keep getting stuck at the s screen

workaround
I've tried everything i can find, i used adb and mounted the card in windows then formatted the card (there is a how to on here for that) but that didn't work. I've tried multiple roms and kernels but i still have the same problem. It seems that my only option is to send it in for warranty. But, if you want to use your phone over the holidays or wait for samsung to come out with an answer before sending your phone in for repair there is a little work around that you can try to get your phone to boot. The phone will be fully functional except that you cannot use the internal SD nor an external SD. Thus, you won't be able to install or save anything to your phone.
to do this workaround just flash the bell froyo rom (there was another froyo rom that i had working but i can't remember which one) then install the voodoo lagfix kernel. When it boots you will hear the "cool voice" state that it is converting it to the ext4 partition and then it will boot into the OS. there will be a program or two that require a "force close" but at least you're phone will work until you can get it repaired. In settings under SD card you'll notice that it says there is no internal or external disk space that's just because you still have the SD corruption and that this is only a work around to get your phone to boot.

I'm curious, for those having this problem and can get into recovery mode, can you report if you're seeing an error msg under the menu and if so, what does it state? Thanks.

Where can you find the official firmware for the i9000m? I had a custom rom installed but my phone decided to brick - jpu worked fine but the minute i upgraded to jpx... Anyway I want to flash the official firmware and take my phone back to bell.
Thanks

I've ran my phone with the original Eclair rom for a couple weeks. I then figured that I couldn't wait for the froyo rom. I've been running the Spike Speedy OC rom, with the JK4 modem and voodoo lagfix. The phone was running just great, very fast. I then changed the lagfix to overkill ext4. Some hours later, the phone hung up. When I rebooted it, it said that the configuration had changed. I saw that one of the options was back to RFS.
What?? It's formatted as ext4. Oh sh*t. Well it didn't boot back up.
I've tried flashing every different firmware I could find. I then tried to re-format the SD manually and found that the partition table was bad.
I've tried to reformat both SD card partitions. The system one (p2) formatted fine, but the "internal SD" (p1) storage one wouldn't format. When I ran fdisk on it, it told me that the partitions didn't end on cylinder boundaries.
Then, I (mistake) flashed a T959 firmware on it. At that point, I wasn't able to get into the download mode using the 3-button combo. Oh shi*... Now I really messed this up. I've managed to get it into download mode using ADB and flash the bell firmware back on it. Oh yeah!! Here we go again.
After the fact that I had installed the T959 and flashed back I9000 firmware, I couldn't find the /dev/block/mmc*** anymore. As if the SD didn't load up.
At that point I inserted a microSD in, and it was recognized as the internal SD. I managed to partition and use that external microSD card just like the internal one and got the phone to boot and work. However, no storage.
All of which I was trying to do while my USB connection was on-and-off, because the usb connector was damaged. It initially had corrosion because my car plug that was kept on the floor of the car, with all the dirt, water and snow. I used alcohol and a tooth brush to clean it, between flashes. As well, flashing it through a VirtualBox VM since I'm on Ubuntu. Sh*t..
This morning I figured I would stop trying, flashed the JH2 firmware on it and brought it to Bell. I tried to get a refund with the argument that this phone is badly designed - with the samsung movinand flash chip - and that it would fail again even if they fix it. It didn't work out for me since I bought the phone about 40 days ago. I was thinking of getting a refund and buy a Nexus S, when a compatible one comes out. It has a different flash chip - a iNand from Sandisk I believe. Oh well. If it fails again, I can still call VISA and give it a try through the purchase protection plan. I have to mention too that I tried calling bell with my concerns - nothing they would do too.
I don't recommend you take my approach. IMO, maybe try, as root, to check the partitions using fdisk /dev/block/mmc(something) and if they appear ok, try to format the SD card using fat.format /dev/block/mmc(something)p1 - but that's it. I'm an experienced linux user, but I'm not a developper. I don't even clearly understand this ODIN flashing stuff. It's like not all firmware you find on the net have the same amount of components inside. I'm thinking stuff from the other flashing is still remaining, not replaced by the later flashes.
I have to say that the next time I'll approach this using fdisk and fat.format only (If I've got a recovery mode working, with root and adb support). Perhaps I will write down the numbers for where the partitions start and end on this SD card when I get my refurbished phone.
Some might say that I had time to spare... I wrote this for you that might be thinking of fixing your 600$ brick yourself.

[Q] Please help.

Okay, so i got a problem a big one.
Today i came home from my night shift, turn on my pc and the download for stock ics rom was done.
My phone was running miui and i thought i'll flash stock rom because of battery drain on miui.
So i put my Note in download mode, connect it to PC Odin, select PDA file and press flash.
Everything went well until the phone didn't want to power on. (that's because i had less than 15% when i flashed). But that was not the first time i did that, Uselessly i just leave my phone turned off so that battery can get a bit of juice. But today i was a bit to sleepy and i went to recovery mode and pressed wipe data. Before the wipe was done i remember brickbug .
Then i quickly turned the phone off and put it download mode tried to flash the same rom with odin 2times but no luck. On odin it goes fine but gets stuck at 1/4 or so.
So the third time i unplugged the cable and now my phone is saying: Frimware upgrade encountered an issue. Please select download mode in Kies & try again.
But i still can put my phone in to the download mode and odin does recognize it.
So can someone help me?
Is my phone totally bricked (dead main-borad), or semi-bricked (flash drive gone).
And if i take my phone to the official repair service i don't have any counter and it say's that is a original Samsung firmware instaled. Will they now if i go there and play stupid, like what is recovery mode? and tell them that that hapend when i tried to install official update over kies?
I will press THANKS button for any help.
Thank you in advance.

If it constantly stuck at factoryfs or data.img then likely you became victim of super brick bug (as positive hystory is you have wiped) in that case better go to service centre.

Ok.
Ok. Thank you for your response.
Will the service repair my phone under the warranty as the bug is known thing?

If you have a 0 flash counter and the phone cannot boot into system they probably will accept to repair it under warranty, I presume. They will not listen to your arguments about brick bug at all. The principal is they will accept if you have no trace of rooted phone or increased flash counter.
btw, if they do not accept warranty, there is still someway to revive your phone, although will loose some memory space. cheers.

Thanks!
Yes I've read about that. +/- 5gb of internal storage..
Now, that's a tough decision, if i go and take my phone to the service i can get a full repair or i can get no warranty. I mean i only have phone for about 1month now. So i have 23 months of warranty left.
If i go and sacrifice 5gb of storage, and in future something goes wrong, will they at the service know that or am i safe?
And what about if i do that and then take it to the service like, where are 5gb? isn't that a 16gb phone? If you know what do i mean.

I am fairly certain that the last argument of "where has 5gb gone" will not work. Just need to make sure you comply with the conditions for warranty to have it repaired under warranty.
If you revive it using repartition, in most case 3gb will be gone. In some case only 1gb loss but some other case it is even >5gb depend on how much damage has been done to your internal memory. Re-partition is reversible, though. Still, it looks like your phone still meet conditions for warranty if I read correctly. cheers.

You have warranty, claim it.
Sent from my GT-N7000 using xda app-developers app

However i decided to take it to the service because i still have warranty.
But I'm concerned, i have a few questions for you guys!
1. Will they on the service know that the phone dose not have installed original rom from them (Open Europe rom) insted of that i did instaled rom from other mobile operator (I wanted to sell the phone). ??
2. If there is no flash counter, and triangle, they can not know that the phone was ever rooted, correct?
Thank you for your help! I will press the tnx button every time.

Bucika said:
However i decided to take it to the service because i still have warranty.
But I'm concerned, i have a few questions for you guys!
1. Will they on the service know that the phone dose not have installed original rom from them (Open Europe rom) insted of that i did instaled rom from other mobile operator (I wanted to sell the phone). ??
2. If there is no flash counter, and triangle, they can not know that the phone was ever rooted, correct?
Thank you for your help! I will press the tnx button every time.
Click to expand...
Click to collapse
AFAIK it doesn't matter which region is on the phone, so long as it's not rooted warranty still valid.
Yes correct.
It's a good idea to claim warranty for this, only true fix atm.
Sent from my GT-N7000 using xda premium

here it is mate, it happened to me yesterday and in my thread i have written how i solved it. try it : http://forum.xda-developers.com/showthread.php?t=1759446
but as the others said above, if possible send it to service.

Hard Bricked Galaxy Note GT-N7000 - Possible Fix?

Hello!
During flashing leaked kernel my phone was on soft brick, I wiped cache partition and data in CWM. This was the end of my beloved Note, it is 100% dead and none of the possible fixes posted works so far.
I have heard there is a possible fix by re partitioning and connection the phone in Linux environment, this way the computer reads the phone and can be fixed by repartitioning and could get into download mode. Please let me know if anybody confirms this.
Alternatively, what is the next step. My phone is still under warranty but I am scared if Samsung would find out the history of rooting or as my Phone is 100% dead they would not be able to find out, confused.......
If the motherboard needs to be replaced, how much would it cost, where should I take and most important if my phone recovers can I still play around with custom ROMs?
Look forward to suggestions bring my phone live as I purchased it on loan and it brings immense pain to pay emi for a dead phone.
Regards,
AK

Even it bricked by emmc bug, there shud be download mode still available
-First try to get other charged battery (or charge yours) and try to put in download mode, and look to Lt upper corner what is your flash score. If it is zero, simply reclain warranty.
-Otherwise try this
http://forum.xda-developers.com/showthread.php?p=26285877

dr.ketan said:
Even it bricked by emmc bug, there shud be download mode still available
-First try to get other charged battery (or charge yours) and try to put in download mode, and look to Lt upper corner what is your flash score. If it is zero, simply reclain warranty.
-Otherwise try this
http://forum.xda-developers.com/showthread.php?p=26285877
Click to expand...
Click to collapse
Thanks. I tried using charged batteries but still does not get into Download Mode also after reading somewhere I tried to connect using Odin assuming screen would be black but Odin detects. Even this did not work
So, no way of getting DM or looking at binary count.
Regards.
AK

Your phone is under warranty yet you are asking for costs? Those "recovery" method will give you a "crippled" device in terms of mem capacity.
So go and claim warranty. They wont know anything since your phone is totally dead anyway.
Sent from my GT-N7000 using xda app-developers app

praetorius said:
Your phone is under warranty yet you are asking for costs? Those "recovery" method will give you a "crippled" device in terms of mem capacity.
So go and claim warranty. They wont know anything since your phone is totally dead anyway.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Hey, I just cam back from SS service. they said it could be a motherboard issue and they are replacing the motherboard.
Does that mean they would install the Stock Rom from fresh, I am sure yes.
Waiting for my recovered phone and educating myself to safely play around with custom ROMs.
One last question, which is the best stable custom ROM available for Galaxy Note, in terms of UI and better battery life?
Many Thanks.
AK

avinay4you said:
Hey, I just cam back from SS service. they said it could be a motherboard issue and they are replacing the motherboard.
Does that mean they would install the Stock Rom from fresh, I am sure yes.
Waiting for my recovered phone and educating myself to safely play around with custom ROMs.
One last question, which is the best stable custom ROM available for Galaxy Note, in terms of UI and better battery life?
Many Thanks.
AK
Click to expand...
Click to collapse
Congrats on the replacement;
Custom ROM's are kind of personal preference, Best bet is to do your research now while you wait and you can decide for yourself which features you like / want / need in a ROM..
Suggestions to check would be ParanoidAndroid / CleaNote from my point of view, I've tried both but still run Stock ICS with custom Kernel.. Suits my needs...

while gaming, my phone suddenly hang and i decide to restart the device itself. upon booting, i am stuck at the "samsung" logo. I have tried flashing stock rom and kernel but to no avail. i can still go into download mode and recovery mode. Anybody know whats gone wrong?
And if i send for waranty, it is a one to one exchanged?

driftkids said:
while gaming, my phone suddenly hang and i decide to restart the device itself. upon booting, i am stuck at the "samsung" logo. I have tried flashing stock rom and kernel but to no avail. i can still go into download mode and recovery mode. Anybody know whats gone wrong?
And if i send for waranty, it is a one to one exchanged?
Click to expand...
Click to collapse
what is the current rom on your phone? have you tried going to recovery and wiping dalvik cache? still same thing? If it is, worst case you can try (since both Recovery and Download works still) is to wipe data in recovery and restart your phone again(Don't try doing this if your using an infected kernel and/or in ICS Rom)
Going back,
You have a soft bricked phone.. Why would you exchange it for warranty? you can easily fix your issue without returning it to Samsung.

letters_to_cleo said:
what is the current rom on your phone? have you tried going to recovery and wiping dalvik cache? still same thing? If it is, worst case you can try (since both Recovery and Download works still) is to wipe data in recovery and restart your phone again(Don't try doing this if your using an infected kernel and/or in ICS Rom)
Going back,
You have a soft bricked phone.. Why would you exchange it for warranty? you can easily fix your issue without returning it to Samsung.
Click to expand...
Click to collapse
i am currently using stock ics 4.0.4 with GL NOTECORE kernel. i have tried wipe dalvik cache but still didnt solve it. i will try wipe date later. thanks

ya, format data does solved it. i am wondering whether will soft brick cause any damage to the hardware?

help
hello

Same problem...pls HELP !!!
I tried to install a custom rom and then the horror began. I can't turn it on geto to download or recovery mode.. I sent it to service because I still have a warranty but I don't know will they see the history of installed roms. The man I talked to said to me that they can do it but I read a comment that it is impossible to see so I got a hope. They also told me that it could be about motherboard and that they will do everything they can to save it. I am really afraid of losing my Note. I hope you guys will help me and tell me sth good.. I am also interested is it possible to fix it with usb jig. ?
thanks, my regards..

Already it's with samsung. If they cant do anything to revive, its a motherboard replacement.
Sent from my GT-N7000 using xda app-developers app

ive been trying to get my note n7000 fixed now way to get it to work jtag just doesn't work boot loader wont go in the phone at all new phone it is

nedzad95 said:
I tried to install a custom rom and then the horror began. I can't turn it on geto to download or recovery mode.. I sent it to service because I still have a warranty but I don't know will they see the history of installed roms. The man I talked to said to me that they can do it but I read a comment that it is impossible to see so I got a hope. They also told me that it could be about motherboard and that they will do everything they can to save it. I am really afraid of losing my Note. I hope you guys will help me and tell me sth good.. I am also interested is it possible to fix it with usb jig. ?
thanks, my regards..
Click to expand...
Click to collapse
Don't worry, if it is with samsung alrd. They'll sure give you replacement of the motherboard if they can't do anything to your existing one. This is considered as the "manufacturing fault", and therefore, they must be able to replace it.
1st few batches, N7000 came out under gingerbread 2.3.6 technology, and it worked very well without the eMMC brick bug. It is happened only when they upgrade to ICS, with their own stock kernel, which triggered the brick bug.
So long as they are delaying the fix for their own stock kernel with the eMMC brick bug removed, I think samsung is still liable to give replacement to user, no matter what you did to your device. As long as it is eMMC brick bug, and you have your warranty.
Why ?
very simple... Even most of the samsung sales person on their respective outlets, they know a lil bit or perhaps don't know at all about this bug. Unless the sales person is those who likes to play with handphone like most of us here.
And if they do know... they won't tell you as well about this bug. Otherwise, will you buy it ? :fingers-crossed:
So as a consumer, we have the right to be replaced if the bug has been triggered due to factory reset / wipe of data, since no one told us about this. **peace**.
Really do hope you get your replacement once they call you to take your phone.
Good Luck !
Sent from the corner of this rounded earth.

antique_sonic said:
Don't worry, if it is with samsung alrd. They'll sure give you replacement of the motherboard if they can't do anything to your existing one. This is considered as the "manufacturing fault", and therefore, they must be able to replace it.
1st few batches, N7000 came out under gingerbread 2.3.6 technology, and it worked very well without the eMMC brick bug. It is happened only when they upgrade to ICS, with their own stock kernel, which triggered the brick bug.
So long as they are delaying the fix for their own stock kernel with the eMMC brick bug removed, I think samsung is still liable to give replacement to user, no matter what you did to your device. As long as it is eMMC brick bug, and you have your warranty.
Why ?
very simple... Even most of the samsung sales person on their respective outlets, they know a lil bit or perhaps don't know at all about this bug. Unless the sales person is those who likes to play with handphone like most of us here.
And if they do know... they won't tell you as well about this bug. Otherwise, will you buy it ? :fingers-crossed:
So as a consumer, we have the right to be replaced if the bug has been triggered due to factory reset / wipe of data, since no one told us about this. **peace**.
Really do hope you get your replacement once they call you to take your phone.
Good Luck !
Sent from the corner of this rounded earth.
Click to expand...
Click to collapse
Thanks man.. you really encouraged me.. So they should give me a replacement.. I am still worried because the man that I talked to told that this kind of problem where I installed a bad rom is not under warranty so that is what scares me the most..
thanks for help...
Just to say:
Galaxy Note GT-N7000, ICS 4.0.4
regards...

driftkids said:
while gaming, my phone suddenly hang and i decide to restart the device itself. upon booting, i am stuck at the "samsung" logo. I have tried flashing stock rom and kernel but to no avail. i can still go into download mode and recovery mode. Anybody know whats gone wrong?
And if i send for waranty, it is a one to one exchanged?
Click to expand...
Click to collapse
seems to be peculiar issue.. they should exchange for sure.. Sorry, I don't have much idea on this..

i'm very impatient..
Hey guys,
I just want to inform you that my Note is at service for 3-4 days... I am contacting them every day and they say it's not done yet.. So I hope it means that they're working on it... I will write if something new happens..
My Regards, Nedzad

Hey
I contaced service and they told they couldn't do anything yet.. Repairman told me that they will get a new JTAG repair box in 20 days and then they will fix it for free.. I think it is a good news

gr8

Unable to ODIN phone, owner tells me the unlock process wasn't fully completed

I previously post here https://forum.xda-developers.com/note-4-tmobile/help/910t3-failed-auth-attempting-to-odin-t3572175 about failed auth in odin.
When i gave the guy his phone back and explained everything, he told me a MetroPCS rep (after taking a look at a rooted phone running an S7 ROM) told him that it wasn't fully unlocked and that he would have problems with it, in his terms, degrade it until what happened to it (boots only into download and recovery mode).
I have no idea what the S7 ROM version was, baseband, bootloader, etc. .. nonoe of it.
Please read the link above as it fills the gaps of this post. Any ideas beyond the putting the phone into the freezer (IDK about this, phone is hot when starting ODIN, and I didn't try)?
P.S. I've also told him of the possibility that the his hardware is the problem. Phone does give an eMMC error with the auth fail on odin.

if you get an emmc error you need the pit file to repartition it. i've never used one and you can brick the phone doing so so do it at your own risk.
failed auth usually means what your trying to odin has not been signed by samsung. and t3 partitioning is different then the standard t model. i can't help anymore then this as i no longer have a n4 t or t3 varient. hope i have shed a little light and you can get it working again but i would call it a brick more or less atm

OvrDriVE said:
if you get an emmc error you need the pit file to repartition it. i've never used one and you can brick the phone doing so so do it at your own risk.
failed auth usually means what your trying to odin has not been signed by samsung. and t3 partitioning is different then the standard t model. i can't help anymore then this as i no longer have a n4 t or t3 varient. hope i have shed a little light and you can get it working again but i would call it a brick more or less atm
Click to expand...
Click to collapse
I've d/l the tar files from within this xda section that appear to be vetted. Assuming the tars are valid, and with the errors I am getting, does this point to an eMMC hardaware error or an error with t vs t3 tars (does this matter?).

d/led the tars from where?
xda. wrong place. get the official t3 firmware file from www.sammobile.com
if it still won't work i'd say it's got bad memory and thats why i called it a brick.
again i no longer have a samsung device so i can't help anymore then what i have. good luck with it. wish ya the best. but other then what i have mentioned i cannot help as i do not have a clue nor have i ever ran across this issue when i did have a sammy device

hammerchucker said:
I previously post here https://forum.xda-developers.com/note-4-tmobile/help/910t3-failed-auth-attempting-to-odin-t3572175 about failed auth in odin.
When i gave the guy his phone back and explained everything, he told me a MetroPCS rep (after taking a look at a rooted phone running an S7 ROM) told him that it wasn't fully unlocked and that he would have problems with it, in his terms, degrade it until what happened to it (boots only into download and recovery mode).
I have no idea what the S7 ROM version was, baseband, bootloader, etc. .. nonoe of it.
Please read the link above as it fills the gaps of this post. Any ideas beyond the putting the phone into the freezer (IDK about this, phone is hot when starting ODIN, and I didn't try)?
P.S. I've also told him of the possibility that the his hardware is the problem. Phone does give an eMMC error with the auth fail on odin.
Click to expand...
Click to collapse
well if you have bad memory like mentioned.. try https://forum.xda-developers.com/note-4-tmobile/general/ddi-mmcread-failed-boot-error-fix-t3434335