Hello
I'm new android and samsung user for about a year now ! I'm just wondering why this flash procedure contains risk while it should not !
I've bought my phone with 400€ and i'm scared like **** to brick it, a normal thing isnt ?
Well what i want to say is, arnt these companies able to create an unbrickable phone in which i can install any android version like in my pc without risking the brick since i'm not touching the hardware part ?
Why these powerfull little things in specs are weak concerning the updating part ?
For me, its illogic to get a 400€ useless phone just after touching to its software part !!!!!
Do you think that its right ?
Sent from my GT-I9000 using Tapatalk
doctor_vai said:
Hello
I'm new android and samsung user for about a year now ! I'm just wondering why this flash procedure contains risk while it should not !
I've bought my phone with 400€ and i'm scared like **** to brick it, a normal thing isnt ?
Well what i want to say is, arnt these companies able to create an unbrickable phone in which i can install any android version like in my pc without risking the brick since i'm not touching the hardware part ?
Why these powerfull little things in specs are weak concerning the updating part ?
For me, its illogic to get a 400€ useless phone just after touching to its software part !!!!!
Do you think that its right ?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I believe phones like the SGS are really sturdy/robust and cannot be easily bricked.However if the situation is like a person taking the wheels of an automobile for the first time without any preparation or guidance and driving through a crowded street and thereby generating a huge risk,that is another matter then!
Invest some time reading through the various initiation guides in these forums some of which 'spoonfeed',and you are good to flash as often as you wish without the risk of causing any hopeless bricks etc.
Happy flashing ahead,but after understanding what it takes!
Flashing is risky only if you flash bootloaders. Otherwise it's safe (well it's good to keep USB jig near just in case) as you can always just reflash if something goes wrong. But I think you'll find more info from flashing tutorials.
Sent from my CM'd SGS
It's hard to brick the SGS. You just hear more about bricks, because no one goes around posting "OMG GUYS SUCCESSFULLY FLASHED!!"
The only real risk is if you flash over the bootloaders. The bootloaders are the software that control how the phone gets flashed, so if these are corrupted obviously you can't really flash it anymore. Problems arise if a) you flash incompatible bootloaders (like from another model), b) the flashing procedure screws up (your computer crashes in the middle of flashing).
It's actually pretty unlikely.
Flashing is not so risky process if you know exactly what you do!
Very often the device behind the keyboard screws up the phone.
People need to read and also getting some basic knowledge how the flashing process works would not hurt them at all. That's the key to a successful flashing
Well thanks guys for the answers ! It was recomforting ;-)
But again for me, even the bootloader shouldnt fear the damage !! Well its a point of view no matter whats the thing between the keyboard does
At least Apple knows how to push their customer to update their iPhones ! I had one and i never feared the updating procedures !
Well concerning the odin software does it write somewhere that the bootloader flashing went perfectly ??
Thanks guys ! And is there any super android phone to buy and which its updating still not risky ?
Sent from my GT-I9000 using Tapatalk
flashing aint risky, only moment that it could fail is the part when its flashing bootloader and that takes like second of the whole flashing process (or if youve putted absolutley wrong model firmware to flash)
from anything else you should just simply take out battery, put it back on and 3 button to download mode =)
and now with unbrickable mod its even more safe =)
doctor_vai said:
At least Apple knows how to push their customer to update their iPhones ! I had one and i never feared the updating procedures !
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Well... this thing with ODIN is not an official way to update firmware. It is a way to flash ROMs other than what your phone was supposed to receive. The official way is using Samsung KIES and only Samsung KIES. That is fault-free. If anything wrong happens you have emergency firmware update or smth. Don't compare official update with ODIN.
KiretoX said:
Well... this thing with ODIN is not an official way to update firmware. It is a way to flash ROMs other than what your phone was supposed to receive. The official way is using Samsung KIES and only Samsung KIES. That is fault-free. If anything wrong happens you have emergency firmware update or smth. Don't compare official update with ODIN.
Click to expand...
Click to collapse
Actually I see more problems caused by Kies in these forums then I do Odin/Heimdall errors. Beyond that, because Kies is kept closed and limited by Samsung often times the user will have no idea why the Kies update failed, or how to resolve the problem. 99 percent of all Odin/Heimdall problems are due to user error or intensely bad luck while the bootloaders are being flashed and there is always plenty of support online for any error. I take Odin over Kies any day.
As for saying that the bootloader should be unbrickable, I know some people have recently been posting hardware mods that create unbrickable Galaxy devices. However, for most of us who are not adept with soldering irons and transistors, the bootloader is no different then the Bios on a PC. If something corrupts the Bios, all you can do is send it to the shop or replace the Bios chip yourself...just as all you can do with a corrupt Bootloader is use a Jig or sent it in for service.
doctor_vai said:
.... like in my pc without risking the brick since i'm not touching the hardware part .....
....
....Well thanks guys for the answers ! It was recomforting ;-)
But again for me, even the bootloader shouldnt fear the damage !! Well its a point of view no matter whats the thing between the keyboard does
Click to expand...
Click to collapse
Really??? So, please take your "unbrickable" PC, and unplug it in the middle of BIOS update (in case of laptop:unplug AND remove battery), and you'll see the results.
basicly you can not compare those two situations
Sent from my GT-I9000
Well, i'm talking guys based on information i learned from the unbrickable mod, these guys have created an unbrickable SGS, do you think Samsung or other companies aren't able to do that officially ? Yes sure they can, but they don't want to, aand i don't know why !!
And for the BIOS thing, i'm partially agree that it's also a dangerous procedure, BUT the difference is that no matter what OS you want to install, you aren't obliged to update the BIOS first, and again, for my 2 Years laptop, i remember well that i've installed Vista and 7 quitly without touching the BIOS
Well, this post wasn't a question at first but kind of "debate" bcause i wanted just to know how people are reacting in front of that situation !
Thank you all
So, who forces you to touch the SGS bootloader?
Same time, Win Vista and Seven are OFFICIALLY released systems.
To compare the situation fully, you should assume that:
- you have PC bought directly from Microsoft, branded by them;
- you want to install "homemade" Win 7 and 3/4;
- you are claiming that you are in problems.
By the way: BIOS and Win Vista or 7 are old systems already. Try to read what is planned and developed now with Win 8 and UEFI: Windows 8 Branded PCs Could Prevent Other Operating Systems From Being Installed, and then compare it with SGS.
Simply, Samsung develops the device with THEIR OS on board, and is not obliged in any way to support homebrew systems, possibly because of likely claims of home grown hackers, who would brick their stuff and then claim it as warranty issue. Flashing different OS'es is possible thanks to effort of the people who are not related with Samsung at all. To use an example going further, look here on the HTC HD2 thread. Device was originally supplied with Win Mobile 6.5, but Dev's managed to port Win Phone 7, Android, Ubuntu and MeeGo to this phone.
Do you think that this is supported by HTC, or the persons who flashed Android and bricked phone would claim that this is HTC's fault? Same is with the SGS: flash not even the stock, but official releases via KIES only, and if something will went wrong, then blame Samsung.
So, there is no situation. Just group of people, who have or not the knowledge what they are doing, while flashing.
dude.. its not about samsung and android problems.. when you're trying to update your phone OS, its risky on every phone. unless you know how to do it right. I just read that if your phone brick, you can bring it to life using USB Jig. I never try it tough, cause my phone is never brick.
Related
Hi,
I've flashed a rom with Heimdall under linux, and repartitioned too. By some accident, I selected boot.bin as Primary and as Secondary boot loader too! (I should have Sbl.bin as secondary). Now it wont boot, neither to recovery nor to download mode. Please help guys, I cannot do anything! Any ideas?
its off to the repair shop for you i think !!
should never play with bootloaders / .bin files
JIG wont work as bootloader is corrupt, only method of fixing is genuine samsung service centre.
harsh lesson learned i feel for you
sigh, thats what i was afraid of. By the way, it may sound a bit crazy, but isnt there such a bloody little JIG that has a built - in boot loader? I mean that it may load the necessary stuff from it?
And do you think, that the official samsung service can fix that? I mean I know that it's absolutely possible to repair it with the appropriate tools, but are they willing to be helpful with such a problem? :/ And should I say that it was getting updated through Kies when suddenly something went wrong or what?
Service can repair but its a chargeable job as warranty is void .
jje
94kram01 said:
sigh, thats what i was afraid of. By the way, it may sound a bit crazy, but isnt there such a bloody little JIG that has a built - in boot loader? I mean that it may load the necessary stuff from it?
And do you think, that the official samsung service can fix that? I mean I know that it's absolutely possible to repair it with the appropriate tools, but are they willing to be helpful with such a problem? :/ And should I say that it was getting updated through Kies when suddenly something went wrong or what?
Click to expand...
Click to collapse
Blaming it on KIES is your only hope of getting it repaired for free.
if they sniff out a tiny piece of customisation, they will charge or refuse.
there are such tools to fix the device, but only samsung (and really smart devs) have them... so i wouldnt look into making one, its easier to send it off for repair.
chances are, they will realise phone is f**ked, realise how upset and truth telling you are, feel sorry for you, plug it in to the super computer and KAPOW !!! its fixed.
keep fingers crossed and good luck
aight, anyway, thanks for the help!
I'm hoping that they will do it for free, or at least cheap. Maybe I have a good chance, because the rom flash was successful, which means it has the the base, original 2.3.3 on it now, hopefully. Erhm, time to get a friend at Samsung
2.3.3 is not available thru kies for all yet. so you may dig yourself a hole if you say its got 2.3.3 on it.
just say kies found an update, you dont know what build it was, you clicked update and phone powered off and never came back on
Yeah Act dumb just like a Nokia user you where updating through Kies and it failed to reboot .
Do not mention Roms Custom or XDA .
Ask daft questions like is it the sim card if they question you .
Act poor wear your old clothes .
jje
JJEgan said:
Yeah Act dumb just like a Nokia user you where updating through Kies and it failed to reboot .
Do not mention Roms Custom or XDA .
Ask daft questions like is it the sim card if they question you .
Act poor wear your old clothes .
jje
Click to expand...
Click to collapse
act poor ?? wtf ? is that just for your own amusement lol it certainly made me laugh out loud
JJEgan said:
Act poor wear your old clothes .
Click to expand...
Click to collapse
Some people pay top dollar for old looking clothes.
Anyway to the OP, good luck man.
thanks best advices ever XD
There are a lot of people who responded here who don't really know what they're talking about.
If it's only your secondary bootloader that's corrupt then you can use a custom jig to boot your phone. The reason for this is that your phone keeps a backup secondary bootloader. Although Heimdall does allow you to flash over the backup secondary bootloader I intentionally didn't include the option in the user interface (in order to try prevent permanent bricks). Anyway, using a custom jig causes the primary bootloader to hand over to the backup secondary bootloader and not the one you corrupted. As such as long as the primary bootloader you flashed is actually designed for your phone then a custom jig is all that is required.
Thank you! But the thing is, that I did not use the UI (frontend), but the command line of Heimdall only. It looked like:
heimdall flash --kernel zImage [...] --primary-boot boot.bin --secondary-boot boot.bin [...]
And here's the point, secondary-boot should've been sbl.bin if I'm right. So what do you think, will a JIG help it, or not? And could you name a specific JIG which is good, and working for sure? Thanks
94kram01 said:
Thank you! But the thing is, that I did not use the UI (frontend), but the command line of Heimdall only. It looked like:
heimdall flash --kernel zImage [...] --primary-boot boot.bin --secondary-boot boot.bin [...]
And here's the point, secondary-boot should've been sbl.bin if I'm right. So what do you think, will a JIG help it, or not? And could you name a specific JIG which is good, and working for sure? Thanks
Click to expand...
Click to collapse
That's fine, as long as you didn't include:
--secondary-boot-backup boot.bin
Click to expand...
Click to collapse
then it should be fine.
I can't recommend a particular jig because I just build them myself if I need them. It's fairly straightforward to build one yourself but any one of eBay should be fine also.
94kram01 said:
Now it wont boot, neither to recovery nor to download mode.
Click to expand...
Click to collapse
concerning the custom jig mentioned by benjamin: i used this method to unbrick my galaxy, after i bricked it on the very first day i had it
since this uses some playing around until you hit the right pins, you could also actually build a custom jig to do this, if you're not afraid of doing some soldering.
in both cases, the phone should be forced into download mode, then you can mess around with odin/heimdall again.
this is a failsafe built in by samsung, making use of the otherwise unused 5th pin in the micro-usb specification (thanks a lot to samsung for this )
don't be afraid, it won't damage your device since it should be off when you do this. if it works, you won't be forced to tell lies to the samsung service center
greetings,
kwantenmechaniker
Benjamin Dobell said:
That's fine, as long as you didn't include:
then it should be fine.
I can't recommend a particular jig because I just build them myself if I need them. It's fairly straightforward to build one yourself but any one of eBay should be fine also.
Click to expand...
Click to collapse
Wow, sweet safety-features there. Nice to see the devs thinking of us flashers. I guess we also can be thankful that samsung has this type of double bootloader backup-system...
Oh and if all else fails: Just dress poor..
Well, cool feature. I dont want to be looking smart-ass, but I had thought there would be such a feature (double backup stuff), since in nowadays computers, it's the same situation with BIOS. At least, hopefully. Anyway, I happened to have a friend who has a friend whose friend works at Samsung (hahah me wins), so I used my connection up But as soon as my phone gets home, I'll try these methods. By the way, do you think guys, it would work on Samsung Galaxy Spica i5700 ? I'm really into this subject now, and would try it.
By the way, do you think guys, it would work on Samsung Galaxy Spica i5700 ? I'm really into this subject now, and would try it.
Click to expand...
Click to collapse
feel free to try. worst thing that can happen is that it doesn't work
Hi guys,
Sorry if this is a stupid question, but I'm currently on Dark's 9.5, and want to upgrade to 10. I know this requires flashing bootloaders, and I hear this is where you can brick your phone if something bad happens. Just wondering how big the risk is?
Thanks for the reassurance!
Rob
Sent from my GT-I9000 using XDA App
the risk is 0% if you follow the instructions correctly
just be sure to double read and take your time.
and if for any reason you do brick your phone, providing you still have download mode, which is hard to lose, you can always re flash bootloaders to get the phone working again
Awesome! I was under the impression that failed bootloader flash = bricked phone. Thanks for the reply! I'll take a crack at it tomorrow!
Sent from my GT-I9000 using XDA App
It should be noted that download mode is part of the bootloaders, and if the flash gets messed up whilst installing that part then you are out of luck. In some cases a Jig can help but it's certainly possible to brick your phone during this process. In which point you will either need to send it back to samsung or be very, very good at soldering and have some expensive equipment to use the jtag. This is why most people don't recommend flashing roms with bootloaders unless you need to (ie upgrading).
If you follow a good set of instructions and understand what you are doing then you are quite unlikely to have any problems however.
Yeah, failed flash of bootloaders can lead to bricking the phone! I wouldn't worry to much coz bootloaders flash in seconds, so unless you decide to unplug your usb connector within the 10 seconds interval of the flash you'll be fine (unless your electricity decides to go down exactly in that period LOL). Any way a JIG always helps, so you can get one online for a couple of bugs (or have one made) in case an event like the abovementioned occurs.
(unless your electricity decides to go down exactly in that period LOL)
Click to expand...
Click to collapse
happend to me couple of days ago. but jig helped recovering my phone from dead
Thanks for all the reassurance everyone! I've decided that I'll probably do the flash on my MacBook (it has a native Win7 installation) so that I'm running on batteries, just wondering if there are any potential problems with using Odin in this way?
Ok! I bought a Samsung P1000N Galaxy Tab from ClaroPR this week. Like always with every android devices i have i rooted it with superoneclick. Yesterday i was trying to update the tablet to gingerbread since it had Froyo. Follow the tutorials in here to flash it(I guess i didnt read the warnings about the secure bootloaders or something like that) but the thing is that i ended up softbricking my device. The gingerbread i was trying to flash was the JQ1. Anyways, i tried to flash it using Odin 1.7, it ended up failing and now i just have the cell triangle and computer logo of dead on the screen. Thing is that i know its not supposed to be totally bricked. But then in the device manager it doesnt show as samsung composite device or anything like that. I need help from someone who has gone thru this already and knows what to do. Or is it just a brick and thats it? Thanks...
enelyam said:
Ok! I bought a Samsung P1000N Galaxy Tab from ClaroPR this week. Like always with every android devices i have i rooted it with superoneclick. Yesterday i was trying to update the tablet to gingerbread since it had Froyo. Follow the tutorials in here to flash it(I guess i didnt read the warnings about the secure bootloaders or something like that) but the thing is that i ended up softbricking my device. The gingerbread i was trying to flash was the JQ1. Anyways, i tried to flash it using Odin 1.7, it ended up failing and now i just have the cell triangle and computer logo of dead on the screen. Thing is that i know its not supposed to be totally bricked. But then in the device manager it doesnt show as samsung composite device or anything like that. I need help from someone who has gone thru this already and knows what to do. Or is it just a brick and thats it? Thanks...
Click to expand...
Click to collapse
If you get anything on the screen at all (Triangle, Download mode, Samsung logo, etc...) It's not bricked, just sponged. Unfortunately I don't have any experience with the P1000N, but in general, try reloading the samsung drivers and try another USB port. Once you get it to show up in device mangler you can push the right tar with Odin and you'll be cooking with gas again. Sorry I can't help with this specific model, but sammy devices in general are hard to truly "brick"
Okay i think now its dead. It turned off when it lost the charge and now not even Heimdall recognize it. So if someone knows about a good tutorial on Jtaging this i will appreciate.
Edit: Found useful guide in here to resurrect it so i will give that a try...
The Unbrickable Mod works like a champ! I know, because I had to resort to this over this last weekend.
However, it does require mods to the mainboard that require some skill. Once accomplished, it is virtually impossible to brick your Tab.
http://forum.xda-developers.com/showthread.php?t=1338073
enelyam said:
Okay i think now its dead. It turned off when it lost the charge and now not even Heimdall recognize it. So if someone knows about a good tutorial on Jtaging this i will appreciate.
Edit: Found useful guide in here to resurrect it so i will give that a try...
Click to expand...
Click to collapse
Why you want to go for Jtag just becoz battery is dead. Get the Tab Opened, Recharge the battery externally (Repair/Service Center should help). Follow the Team Overcome Guide to install the Stock Safe Rom and then you can either continue with it or move to any other ROM of your choice.
I would keep JTAG as the Last option.
If it's new Tab, it should still be under warranty.
wow, impressive post (the unbrickable mod).. Not sure I'd have the guts to do that though..
Ok....you have heard this many times before but Ill ask anyways in the event someone can help me.
I am a newbie to rooting although Ive had my Note for months.
This morning I rooted successfully .
I also dloaded clockwork mod and watched YouTube tutorials on it.
Then I thought id try flashing a new ROM and Paranoid Android looked the easiest. Just two files - the zip and the fix. So i downloaded them to my CD card and then booted from RomManager into recovery mode.
Here is where I truly stuffed am I am guessing.
First I went into the immediately available option of 'instal file form SD card" and tried loading both Paranoid Android rom files .
I got Signature not verified etc
So then I went a step further and went into the clockwork mod folder instead ( where all font is blue and it becomes a touch screen menu ) and both files were there also so I hit the Paranoid Android zip file and it seemed to be actually doing something so i thought you beauty ! Some white lines of text came out, it stalled for a few minutes and then the phone just turned off and that's the way it is. DOINK.
I cannot turn it on.
I cannot boot into recovery mode.
My pc doesn't recognize it as a drive.
Kies wont recognize it.
so I have two questions ;
A) Is it resuable ?
b) Of I cant do it will Samsung service center be able to re-load the OS or whatever or is the unit well and truly fried ?
thanks
You obviously did not read the OP since procedure is clearly explained. What you did is just nonesense.
Does download mode works?
Sent from my GT-N7000 using XDA
To the OP:
Did you flash Parnoid Android rom over an ICS rom, that's what I did and my Note was hardbricked. I got my Note back yesterday from the repair centre, its easy to forget to remember to read the instructions sometimes and it can happen, not to worry though...its not the end of the world, the repair centre is an option
Sell?
Sent from my LG-P999 using xda premium
you dont provide enough info..mainly exactly what rom and kernel you were on when you tried to flash Paranoid.
Maybe he should start writing in the correct forum (Q&A) and even better: read there first and find a lot of related threads and exact informations.
Take seals advice. He's an expert now lol. Btw glad to see you got your phone back! Get that rom going!
Sent from my GT-N7000 using XDA
g2tegg said:
Take seals advice. He's an expert now lol. Btw glad to see you got your phone back! Get that rom going!
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
You guys are going to keep teasing me about my bad rom aren't you's?
Btw...I didn't brick my phone due to my rom, I bricked my phone because I flashed a CM9 rom over a ICS rom (my rom was based on a ICS rom).
Can you get into download mode?
Service Center here you go!
Beretta93 said:
You obviously did not read the OP since procedure is clearly explained. What you did is just nonesense.
Does download mode works?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Actually i read up extensively on it . I am just useless at following instructions. Not all of us have propellers sticking out of our heads.
Dload mode ? What part of it doesn't turn on etc isnt clear......
SealsNavie said:
To the OP:
Did you flash Parnoid Android rom over an ICS rom, that's what I did and my Note was hardbricked. I got my Note back yesterday from the repair centre, its easy to forget to remember to read the instructions sometimes and it can happen, not to worry though...its not the end of the world, the repair centre is an option
Click to expand...
Click to collapse
I flashed from the recent android 4.0.3. Asian version ( I am in Cambodia ) . I believe the mistake i possibly made was going in to CWM files in recovery mode and doing it from there ?
Anyways....its back with Samsung RC now so hopefully they can rectify back to normal . I hope they dont see all the root files etc in the SD card. This is Cambodia so I doubt they'll care.
They'll be fixing the screen i cracked a few weeks ago too. Dropped it and it chatter like a bullet hole. So....my note will be all minty when i get it back....albeit $180 later !!
jgarnett said:
So....my note will be all minty when i get it back....albeit $180 later !!
Click to expand...
Click to collapse
Is that all, It'll cost me over $200 JUST to get the screen fixed...
jgarnett said:
I flashed from the recent android 4.0.3. Asian version ( I am in Cambodia ) . I believe the mistake i possibly made was going in to CWM files in recovery mode and doing it from there ?
Anyways....its back with Samsung RC now so hopefully they can rectify back to normal . I hope they dont see all the root files etc in the SD card. This is Cambodia so I doubt they'll care.
They'll be fixing the screen i cracked a few weeks ago too. Dropped it and it chatter like a bullet hole. So....my note will be all minty when i get it back....albeit $180 later !!
Click to expand...
Click to collapse
You cannot flash PA over ANY ICS rom. This is what caused your brick.
Sent from my GT-N7000 using xda premium
ultramag69 said:
Is that all, It'll cost me over $200 JUST to get the screen fixed...
Click to expand...
Click to collapse
Yes, i came from cambodia too, actually for that price over there it's quite expensive.
any way, good to know that some one from cambodia is using Galaxy Note, impressive!
EVERYONE is using the Note here. Especially the girls. They love it even though they can barely hang on to it
$180 is for the Screen only. I believe ill get the OS redone for free.
jgarnett said:
Actually i read up extensively on it . I am just useless at following instructions. Not all of us have propellers sticking out of our heads.
Dload mode ? What part of it doesn't turn on etc isnt clear......
Click to expand...
Click to collapse
Yeah you really suck at following instructions since you didn't do anything correctly.
You saying it does not turn on is indeed unclear, since you mention right after "it does not enter into recovery mode". So if you made the distinction., one can wonder...
So if you can't turn it on at all, including download mode, your phone is hard brick and needs to go to RMA, and since it is not due to emmc bug obviously, rma can be refused by Samsung because if they investigate they'll see that you flashed a different recovery.
Sorry dude, it's just about how lucky you are now...
Sent from my GT-N7000 using XDA
Beretta93 said:
So if you can't turn it on at all, including download mode, your phone is hard brick and needs to go to RMA, and since it is not due to emmc bug obviously, rma can be refused by Samsung because if they investigate they'll see that you flashed a different recovery.
Click to expand...
Click to collapse
Here is the rub.
Samsung rang me yesterday and said the phone needs;
New Screen at $150
New motherboard at $150
New front camera at $25.
Ouch
However....
Apart from the cracked screen (which happened weeks ago) up until I rooted and then ****ed the phone with my atrocious attempt at flashing the new ROM....the phone was working with no worries at all.
Can I ask the techs here as I have no idea ;
Would the motherboard be a victim of the flashing attempt ? If so....I am in the wrong and will pay all monies. I am guessing it is directly related as the phone was fine until the flashing attempt. If not......would the shock from the fall weeks ago have caused a failure in the MB ? Or could that just not be related at all ?
Basically, I am wondering if i have a leg to stand on with trying to claim warranty on the MB ....When they contacted me yesterday there was no mention of the phone having been rooted " you have been a naughty boy !! ". Actually what they said was " you dropped your phone and now the motherboard is broken "
thanks
jgarnett said:
Here is the rub.
Samsung rang me yesterday and said the phone needs;
New Screen at $150
New motherboard at $150
New front camera at $25.
Ouch
However....
Apart from the cracked screen (which happened weeks ago) up until I rooted and then ****ed the phone with my atrocious attempt at flashing the new ROM....the phone was working with no worries at all.
Can I ask the techs here as I have no idea ;
Would the motherboard be a victim of the flashing attempt ? If so....I am in the wrong and will pay all monies. I am guessing it is directly related as the phone was fine until the flashing attempt. If not......would the shock from the fall weeks ago have caused a failure in the MB ? Or could that just not be related at all ?
Basically, I am wondering if i have a leg to stand on with trying to claim warranty on the MB ....When they contacted me yesterday there was no mention of the phone having been rooted " you have been a naughty boy !! ". Actually what they said was " you dropped your phone and now the motherboard is broken "
thanks
Click to expand...
Click to collapse
your phone its super bricked due to wiping the phone in an ics kernel and its all samsung fault for the brick bug but you could avoid that flashing abyss kernel before wiping your phone and yes brick bug fry your motherboard.
You just superbricked a Super Phone
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