Related
I made a wipe data/factory reset while on CWM Touch (I didn't know about the issues yet) and, of course, it didn't work. So now, everytime I try and flash an Odin ROM (because it doesn't work with the recovery), it gets stuck at data.img/datafs so there's no way I can boot my phone although it does have recovery, download and it gets to the Samsung bootscreen (I flashed a stock ROM).
Has anyone got any ideas on how to fix this? Thanks
Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA
praetorius said:
Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I was on AOSP ICS v04 with the infamous AbyssNote 1.2 kernel (but I don't have the same factoryfs problem as the others) with Touch CWM (that's where the problem comes from I believe) and the only problem is that neither Odin nor CWM can access the /data partition. So a wipe doesn't work.
I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.
chasmodo said:
I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.
Click to expand...
Click to collapse
Are you sure? Even though it's never stuck at factoryfs and it only bootloops? Because the problem is I have no service center I can go to so sending it via La Poste (in France) isn't exactly what I'd call safe... Or is there a way to send iut directly to Samsung and get a new one?
Up.............
Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?
Akiainavas said:
Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?
Click to expand...
Click to collapse
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
nico53laval said:
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?
Click to expand...
Click to collapse
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."
no id agree with what the guys have told you, looks like a service center job, did you just flash this recently or were you one of the users who flashed it weeks back, and youve only just attempted a wipe now??
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.
graemeg said:
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.
Click to expand...
Click to collapse
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.
chasmodo said:
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.
Click to expand...
Click to collapse
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...
dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
Too late ^^ I sent it to a repair center.. But I don't think it would have worked. I already did a wipe on a tock rom with stock recovery and it worked but the phone still couldn't boot.
Akiainavas said:
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."
Click to expand...
Click to collapse
The problem is that in France the repair centers have an agreement with Samsung but they're not directly related to Samsung so do you think it'll only be 14 days (even though I might neeed a new mobo or a new phone)?
Not sure how youre postal system works there but make sure you get recorded delivery or france similar so you have proof of posting etc.
Also considering the issue ive read most times lads have had a quick turn around, but who knows, depends how fast samsung receive it, i would suggest UP TO 2 weeks, more likely a week, but then it me be 2 week, depends what they have to do to repair it.
I recently took a phone to the o2 shop to be repaired, i received it back via post 4 days later, that was really fast, and im quite lucky here that theres an abundance of walk in repair centres around the uk, it just made me wonder if there one close to you and would it be economical to take it in person, samsung repair shop where i live if ya take your phone in by hand theyll usually say come back in a couple of hours and then they fix it there and then, that would be better for you because you arent messing around with posting then, i know a lot of countries guys dont have that option but i would have thought france and germany would be similar to the uk as they are both quite large mobile manufacturing countries so my fingers are crossed for you that you can find a quick solution.
No idea mate, but you shouldn't wait more than 2 weeks. The repair will take one hour probably, the rest is testing, posting, filling papers etc.
You'll probably have it back after 1 week or so. So let's hope you'll received it fixed as soon as possible.
nico53laval said:
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...
Click to expand...
Click to collapse
Oh, I see. Should've read angelom 1.2 thread first.... sorry
Good luck with service.
dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
what stock rom? which version you used?
Hi,
I have got my Gnote super bricked and I used pit file method to revive it but now these freezes are killing me. I have bought it 9 months ago from mediamarkt in Germany.
Do you think they will accept it now? I mean it is working but every several hours it freezes. What should I tell them about the problem?
I revived my note using the pit files but it isn't giving me problems as you say
I really have no idea where these freezes are coming from. I think sooner or later I should give it for warranty
have you tried already doing the 3 wipes on your phone in CWMR?
if you have tried it already and still getting the hangups on it.. my reasonable suggestion is.... just BORK it more. I mean what have you got to lose if Samsung can't boot your phone anymore right? No more explanations to them other than your phone got toasted when you tried to update via KIES....
end of discussion.
ashkan_mc said:
I really have no idea where these freezes are coming from. I think sooner or later I should give it for warranty
Click to expand...
Click to collapse
As long as the binary counter is set to 0 and there's no yellow triangle you should be able to take it to warranty. Of course unroot it first and leave no trace of any customization.
So I'd they ask you what's the problem with your note what shall you say?
letters_to_cleo said:
have you tried already doing the 3 wipes on your phone in CWMR?
if you have tried it already and still getting the hangups on it.. my reasonable suggestion is.... just BORK it more. I mean what have you got to lose if Samsung can't boot your phone anymore right? No more explanations to them other than your phone got toasted when you tried to update via KIES....
end of discussion.
Click to expand...
Click to collapse
You mean again I try to make it bricked? Just like the last time or with another method? Can they find out I did it deliberately?
The problem is now my internal sd is showing 9.33 GB and if they dig in more, they will find out what I have done to it.
Of course samsung is responsible for this matter cause it is they fault not mine.
Now my phone is unroot and has official LRQ on it.
ashkan_mc said:
You mean again I try to make it bricked? Just like the last time or with another method? Can they find out I did it deliberately?
The problem is now my internal sd is showing 9.33 GB and if they dig in more, they will find out what I have done to it.
Of course samsung is responsible for this matter cause it is they fault not mine.
Now my phone is unroot and has official LRQ on it.
Click to expand...
Click to collapse
Yeah sure why not... I mean it may seem ridiculous to advice you this but bricked it back until you can't turn it back on again. I know most other users before who have bricked their phone big time (can't boot up their phone anymore) and they've return it back to Sammy to have the mobo replace. No questions asked. If they try to ask you what you did.. just give them an innocent smuck and say.. "My phone's not turning ON after I tried to update it thru Kies. I dunno what's the problem with it." Give them a casual after stupid innocent look. Most likely they won't drill you anymore.
letters_to_cleo said:
Yeah sure why not... I mean it may seem ridiculous to advice you this but bricked it back until you can't turn it back on again. I know most other users before who have bricked their phone big time (can't boot up their phone anymore) and they've return it back to Sammy to have the mobo replace. No questions asked. If they try to ask you what you did.. just give them an innocent smuck and say.. "My phone's not turning ON after I tried to update it thru Kies. I dunno what's the problem with it." Give them a casual after stupid innocent look. Most likely they won't drill you anymore.
Click to expand...
Click to collapse
Do they give a new phone or just replace its motherboard?
And btw what did you mean by 3 wipes? I did not wipe the whole internal and external sd though
Thanks alot
ashkan_mc said:
Do they give a new phone or just replace its motherboard?
And btw what did you mean by 3 wipes? I did not wipe the whole internal and external sd though
Thanks alot
Click to expand...
Click to collapse
No, they're just going to replace your motherboard.
3 wipes is Wipe DATA, Wipe Cache Partition and Wipe Dalvik... all of these are in CWMR (if your still able to boot in recovery).
hmm, on a lighter point, before you begin the steps above(if you would like to try though), try to format your external SD card and try to place it back again to your phone. See if you still have the hangups.. If you do have it still, then go with the 3 wipes I mentioned above.
letters_to_cleo said:
No, they're just going to replace your motherboard.
3 wipes is Wipe DATA, Wipe Cache Partition and Wipe Dalvik... all of these are in CWMR (if your still able to boot in recovery).
hmm, on a lighter point, before you begin the steps above(if you would like to try though), try to format your external SD card and try to place it back again to your phone. See if you still have the hangups.. If you do have it still, then go with the 3 wipes I mentioned above.
Click to expand...
Click to collapse
If I try to get it bricked and mediamarkt in germany won't accept it, is it possible that I revive it with pit file method again?
Like I've said..skip the 3 wipes for now and just format first your SD card and see if the hangups wouldn't be there after.
If it's not there anymore then GOOD.. if it's still there, then you do the 3 wipes. I would assume your already using a safe kernel already right?
letters_to_cleo said:
Like I've said..skip the 3 wipes for now and just format first your SD card and see if the hangups wouldn't be there after.
If it's not there anymore then GOOD.. if it's still there, then you do the 3 wipes. I would assume your already using a safe kernel already right?
Click to expand...
Click to collapse
I did use hydracore kernel for a while but with that I had freeze more. Now I am in unroot condition with stock kernel. So I can not do the 3 wipes now.
I will try to remove my external sd card and see without that what is gonna be ...
sure, just post back later on your results.
I did all kinds of wipes and formats but again freeze don't know what to do
Well, it's apparent that your phone's boot partition has some bad sectors on it still. That's why everytime your phone reads those particular bad sectors.. it freezes itself up.
try to repartition your phone back to remove those bad sectors or you can try the link here http://www.alliance-rom.com/communi...-superbricked-stage-from-ics-kernel-bug.8018/ , as your reference to remove those bad sectors and scan for possible partition errors as well.
letters_to_cleo said:
Well, it's apparent that your phone's boot partition has some bad sectors on it still. That's why everytime your phone reads those particular bad sectors.. it freezes itself up.
try to repartition your phone back to remove those bad sectors or you can try the link here http://www.alliance-rom.com/communi...-superbricked-stage-from-ics-kernel-bug.8018/ , as your reference to remove those bad sectors and scan for possible partition errors as well.
Click to expand...
Click to collapse
I have tried this thread before ... The one which belongs to forest1971 ... Again nothing ...
Mate best thing is return to gb stock with counter 0... ensure everything is stock... give the mobile to ur girlfriend and ask her to take it to sammy center...
Ull get the replacement for sure... tell them updating from kies did this...
Why GB? If it would be ICS it has problem? I mean I want to tell them that I was on LRK and I updated it to LRQ via Kies and then my phone got bricked. Do you think it is ok? GF idea is perfect
ashkan_mc said:
Why GB? If it would be ICS it has problem? I mean I want to tell them that I was on LRK and I updated it to LRQ via Kies and then my phone got bricked. Do you think it is ok? GF idea is perfect
Click to expand...
Click to collapse
Bro u have already revived ur mobile... so best thing to do is take it sammy and tell them that ur mobile lags a lot and u have some lost space on ur memory card... (play innocent).... they'll check it and replace ur mobo if needed... so doesnt matter if u r on gb or ics
I've just got my processor replaced by Samsung. Apparently according to the technician the processor is corrupted. Mine me it cost me almost USD 250 to replace it because the phone has been rooted so its not covered under warranty. I've rooted my phone, flash some kernels (Abyss and latest Franco Kernel) a few times and changed several ROMS (Kingdroid, ROCKETROM). I've no idea how to processor can be corrupted but according to the technician because when i rooted it i deleted some files cause the processor settings to malfunction and therefore processor got corrupted. I' pretty sure i did not deleted any files from the root folders. Can someone please explain to me the truth behind what the technician said. I believe its a whole lot of gibberish. I believe i should be able to change ROMS and Kernels as i please but i really don't want to spent another USD 250 to replace another processor after i changed ROMS or Kernels. Please advise.
michaelw1979 said:
I've just got my processor replaced by Samsung. Apparently according to the technician the processor is corrupted. Mine me it cost me almost USD 250 to replace it because the phone has been rooted so its not covered under warranty. I've rooted my phone, flash some kernels (Abyss and latest Franco Kernel) a few times and changed several ROMS (Kingdroid, ROCKETROM). I've no idea how to processor can be corrupted but according to the technician because when i rooted it i deleted some files cause the processor settings to malfunction and therefore processor got corrupted. I' pretty sure i did not deleted any files from the root folders. Can someone please explain to me the truth behind what the technician said. I believe its a whole lot of gibberish. I believe i should be able to change ROMS and Kernels as i please but i really don't want to spent another USD 250 to replace another processor after i changed ROMS or Kernels. Please advise.
Click to expand...
Click to collapse
If you have ever flashed a ICS rom which didn't have a safe kernel and made a factory reset,there are chances of your getting super bricked.As to confirm that,switch on your phone and see if it gets past the splash screen.If doesn't,its 50% confirmed.
Next is to boot into download mode and flash some rom with Odin.If it gets stuck at factoryfs,its confirmed.Please do note that it may take 10mins to flash factoryfs.If it take longer than 15mins,I'm sorry you have super bricked.
There are guides in general section to revive it.you could refer that if you need
Sent from my GT-N7000 using xda app-developers app
corrupt processor.. ? not sure what he meant by that... u should have asked to give the more info as in if it was an emmc chip issue...
if that was the case possibly a wipe on stock kernel mite have caused it and they mite have changed the motherboard.. which costs around that kinda money if not under warranty.
When i asked him all he said "u rooted ur phone. You could have erase some processor setting files..so processor malfunction therefor corrupted so no warranty". He did gave me back the motherboard though. of course since the motherboard and processor is a single piece therefore the replace it. But till now i still dont know how that happens or what i did might ha e lead to this when i asked the tech he said dont root your and i was lile "duh"
hmmm... not root an android.., its like keeping all the goodies in a locked room... but personally i have not encountered any such problem till now,,, i have unrooted and rooted the phone so many times..
may be a bad move mite have caused it
I guess you had done a wipe on an unsafe kernel which lead to a super brick
I too had the same experience but luckily got it replaced under warranty
He he .. U lucky guy.
Sent from my GT-N7000 using xda premium
After days of searching and googling i believe like some more experienced users here said i might have caught the bug. But what i dont understand is i've also reflash the kernel to Abyss 4.2 kernel that changed my initial affected Kingdroid Rom to Rocketrom in hope to solve the problem, but unfortunately that didnt work. So basically if so unfortunately it happens to me in the future again, i guess ill just have to unroot and rrset the.binary counter..but by then the warranty might have expired already.
Sent from my GT-N7000 using xda premium[/QUOTE]
michaelw1979 said:
After days of searching and googling i believe like some more experienced users here said i might have caught the bug. But what i dont understand is i've also reflash the kernel to Abyss 4.2 kernel that changed my initial affected Kingdroid Rom to Rocketrom in hope to solve the problem, but unfortunately that didnt work. So basically if so unfortunately it happens to me in the future again, i guess ill just have to unroot and rrset the.binary counter..but by then the warranty might have expired already.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
[/QUOTE]
Maybe here will help you figure out
http://forum.xda-developers.com/showthread.php?t=1827394
.
michaelw1979 said:
When i asked him all he said "u rooted ur phone. You could have erase some processor setting files..so processor malfunction therefor corrupted so no warranty". He did gave me back the motherboard though. of course since the motherboard and processor is a single piece therefore the replace it. But till now i still dont know how that happens or what i did might ha e lead to this when i asked the tech he said dont root your and i was lile "duh"
Click to expand...
Click to collapse
Might relate to some kernel tweaking ... did often use processor O/C-ing???
Sent from my GT-N7000 using xda app-developers app
fr3ker said:
Might relate to some kernel tweaking ... did often use processor O/C-ing???
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Nope never oc my processor n ive always flash kernel from normal odin. Dont know how thos affected the emmc bug
Your technician is partly credible when he said you fried your procie....
perhaps he wasn't keenly elaborating it but he may have meant it to be your eMMC chip on your Note.
There are myriads of discussions already all over our beloved Note's forum regarding the eMMC chip which has most high end experts believe to be a faulty chip case and so henceforth, this chip would be toasted when a right scenario or pre-conditions are met thereof,, would trigger the superbrick bug.
Your tech guy might not be good in the right explanation of words.. but he is partly good in saying your 'procs' were fried... What I don't agree on him was that it was because 'you root' your phone... rooting does not in anyway enable the eMMc bug.... it is thru using an unsafe kernel and doing a full wipe of your phone that triggers it. Some are lucky they're not bitten first time when doing the wipe (with an unsafe kernel), few are not that lucky and the minute they wipe their device, instantaneously the bug would be triggered rendering their Note unbootable or stuck at data.img or factoryfs.img.
letters_to_cleo said:
Your technician is partly credible when he said you fried your procie....
perhaps he wasn't keenly elaborating it but he may have meant it to be your eMMC chip on your Note.
There are myriads of discussions already all over our beloved Note's forum regarding the eMMC chip which has most high end experts believe to be a faulty chip case and so henceforth, this chip would be toasted when a right scenario or pre-conditions are met thereof,, would trigger the superbrick bug.
Your tech guy might not be good in the right explanation of words.. but he is partly good in saying your 'procs' were fried... What I don't agree on him was that it was because 'you root' your phone... rooting does not in anyway enable the eMMc bug.... it is thru using an unsafe kernel and doing a full wipe of your phone that triggers it. Some are lucky they're not bitten first time when doing the wipe (with an unsafe kernel), few are not that lucky and the minute they wipe their device, instantaneously the bug would be triggered rendering their Note unbootable or stuck at data.img or factoryfs.img.
Click to expand...
Click to collapse
I have a super-bricked note too. What if I go to them with my counter reset? Will they refuse to replace my motherboard for free?
Well it depends entirely on the discretion of your SSC and the tech handling it. Normally most techs are not that stingy to repair your Note just as long as they've check your warranty and is satisfied that you really did not tinkered your phone. Just act and answer sheeply to them that you've bricked while upgrading thru Kies.
Word of advice. Never ever give yourself away... Never ever instigate in anyway to tell them first hand that you've rooted already your phone or have flashed any custom roms on it. They might think otherwise of voiding your warranty if you blurt them what you really did to your phone. Act and think plausibly.
Kapish? Ok..good.
Sent from my GT-N7000 using xda premium
letters_to_cleo said:
Well it depends entirely on the discretion of your SSC and the tech handling it. Normally most techs are not that stingy to repair your Note just as long as they've check your warranty and is satisfied that you really did not tinkered your phone. Just act and answer sheeply to them that you've bricked while upgrading thru Kies.
Word of advice. Never ever give yourself away... Never ever instigate in anyway to tell them first hand that you've rooted already your phone or have flashed any custom roms on it. They might think otherwise of voiding your warranty if you blurt them what you really did to your phone. Act and think plausibly.
Kapish? Ok..good.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I'd just tell them I've just received and OTA notification then the phone rebooted and didn't boot up again
Enviado desde mi GT-N7000 usando Tapatalk 2
kzshantonu said:
I have a super-bricked note too. What if I go to them with my counter reset? Will they refuse to replace my motherboard for free?
Click to expand...
Click to collapse
If you clrar your flash counter,they must do it under warranty
Just act like you never know what rooting is
rajsekhar.300 said:
If you clrar your flash counter,they must do it under warranty
Just act like you never know what rooting is
Click to expand...
Click to collapse
letters_to_cleo said:
Well it depends entirely on the discretion of your SSC and the tech handling it. Normally most techs are not that stingy to repair your Note just as long as they've check your warranty and is satisfied that you really did not tinkered your phone. Just act and answer sheeply to them that you've bricked while upgrading thru Kies.
Word of advice. Never ever give yourself away... Never ever instigate in anyway to tell them first hand that you've rooted already your phone or have flashed any custom roms on it. They might think otherwise of voiding your warranty if you blurt them what you really did to your phone. Act and think plausibly.
Kapish? Ok..good.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
msedek said:
I'd just tell them I've just received and OTA notification then the phone rebooted and didn't boot up again
Enviado desde mi GT-N7000 usando Tapatalk 2
Click to expand...
Click to collapse
Cool then... I'll flash angelom 1.2 kernel to reset the counter. Then take it to SSC and see what happens. Wish me best of luck pls. I miss my Gnote :crying:
kzshantonu said:
Cool then... I'll flash angelom 1.2 kernel to reset the counter. Then take it to SSC and see what happens. Wish me best of luck pls. I miss my Gnote :crying:
Click to expand...
Click to collapse
All the best:good:
@OP
don't fret, you'll get your polished Note soon with a brand new mobo inside... So it's all good bud.
there is no way to fire your processor in software level, may be oc'ng it may hurt it, but any modification in software will not affect the processor by any mean, he meant the emmc chip for sure, any way as long as you are using safe kernel, and reading before flashing, you are safe to go, and i think your processor is safe as far as you don't overclock it too much.
Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere
Rom manager flash the wong recovery fr other devce
Sent from my GT-S5830 using xda premium
DeadSp1d3r said:
Rom manager flash the wong recovery fr other devce
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
+10000000 it's so easy
Thanks. Just downloading a Rom for the S5830i to try out. Wouldn't you be able to re-flash the correct rom this way and get it to work again? Also if it does brick this way, would it leave traces when Sammy Techs investigate?
Gizmotech said:
Thanks. Just downloading a Rom for the S5830i to try out. Wouldn't you be able to re-flash the correct rom this way and get it to work again? Also if it does brick this way, would it leave traces when Sammy Techs investigate?
Click to expand...
Click to collapse
if you use rom manager samsung will not find out anything
if you flash other devices rom like acei on ace then it might brick but not for 100% sure but there is lots and lots of change that it will brick since it uses other flash scripts and binarys
Gizmotech said:
Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere
Click to expand...
Click to collapse
Just download a galaxy s3 ROM and kernel...bricked right there.
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok Just tried to load up the firmware file for a Ace Plus on odin 4.38 but it wont accept it and comes back with "out of memory" error on the PC screen. Will try Rom Manager.
Bingo! Bricked it. I take it there's no way that I can attempt to revive it? Also I hope there is no traces of CWM Rom Manager, Superuser or Busybox
I don't know about the traces. But the only way to revive it is JTAG or replacement motherboard.
Sent from my GT-S5830 using xda premium
Next time, I'd rather make a backup in CWM and then restore it from another Recovery. What this does is delete the boot.img, so now your phone can't do anything and Samsung can't get any logs etc. from the device.
Also REMEMBER! Play dumb when taking it to the Samsung store! Don't mention Roms etc..
PulseDroid said:
Next time, I'd rather make a backup in CWM and then restore it from another Recovery. What this does is delete the boot.img, so now your phone can't do anything and Samsung can't get any logs etc. from the device.
Also REMEMBER! Play dumb when taking it to the Samsung store! Don't mention Roms etc..
Click to expand...
Click to collapse
Or rename a text file to boot.img and flash it as a ROM. This gives a totally faulty ROM.
Sent from my GT-S5830 using xda premium
Thanks guys, gonna give it in to service today and will keep you guys updated. I like the above method as it definitely would not leave traces of CWM, Superuser or Busybox. Duh, why didn't I think of that:silly: but too late now. maybe next time or someone else.
Gizmotech said:
Thanks guys, gonna give it in to service today and will keep you guys updated. I like the above method as it definitely would not leave traces of CWM, Superuser or Busybox. Duh, why didn't I think of that:silly: but too late now. maybe next time or someone else.
Click to expand...
Click to collapse
Do you not ever think there is someone in samsung softwere development reading this...
Sent from my GT-S5830
Best way to hardbrick your phone is to use rom manager
I got transformed into a potato while writing this post
athe_s said:
Do you not ever think there is someone in samsung softwere development reading this...
Sent from my GT-S5830
Click to expand...
Click to collapse
I do. That's the good thing about having a screen-name
Updates!!!
Gizmotech said:
Thanks guys, gonna give it in to service today and will keep you guys updated.
Click to expand...
Click to collapse
Any updates dude?
Wow. No wonder phone manufacturer doesn't honor warranty nowadays.
Seriously if u want to do such scam u should do it quietly without creating thread asking howto do so.
This is nice.... You can brick your phone in the last month of you year warranty and get a new phone/motherboard
Once my friends phone switched off suddenly... Non rooted stock
It happened suddenly and also out of warranty
She had to pay 5k to the Samsung people to get it repaired... And the plus point she got 14GB internal memory with the new motherboard
Her phone was the Samsung galaxy S i9000
it would've been done in free if she had warranty
So maybe you might get the GT S5830i.. The new version mother board or something
Best of luck
Gizmotech said:
Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere
Click to expand...
Click to collapse
ohh !!!! so easy !!! install rom manager... 100% sure samsung won't find out what went worng with your ace ...
ysrini said:
Any updates dude?
Click to expand...
Click to collapse
Yes, the phone was repaired. They apparently replaced the motherboard.
an0nym0us_ said:
Wow. No wonder phone manufacturer doesn't honor warranty nowadays.
Seriously if u want to do such scam u should do it quietly without creating thread asking howto do so.
Click to expand...
Click to collapse
I would have done it quietly if I didn't need the help. Duh! Besides, I doubt this is the reason why they don't honour warranty. I think it is more to do with that they are greedy corporate companies who would rather save at any cost irrespective of whose fault it is. I mean why should they penalise someone because of something someone else done? After all you are all paying customers. They scam people everyday and no one complains. I guess people only complain when it happens to them. You can buy a new phone and have it go faulty within 2 months. Do you think you can get a new phone under warranty from them? No it will be a refurbished one and doesn't mater how much you scream and shout for a new one, they don't care. A neither do I.
jumbobombo said:
So maybe you might get the GT S5830i.. The new version mother board or something
Best of luck
Click to expand...
Click to collapse
No, I think it is the same motherboard. What I don't understand is, whether it is the same motherboard they repaired or a replacement one, as this phone was initially locked to the Three network. I had it unlocked. So a new motherboard would have meant that the phone would be locked again. But when I received it back, it would still accept any sims.
I know this is a shot in the dark, but I would really be interested in hearing what people have to say.
I am finding that I am having issues with my Galaxy Note - the main problem being the phone getting stuck and the screen not turning on - needing a soft reset or at times, needing the battery to be taken out. This problem is despite what ever rom I am using - the issue is also with almost all kernels tried.
I did have superbrick issue and I have tried going back to the original rom with the pit method, however, no luck.
I can confirm that this is happening with ICS/GB/MUIU/AOKP roms... there seems to be no obvious solution...
Does anyone else have this problem?
What is the solution if any - its frustrating when the phone becomes stuck randomly.
Is there a rom/radio/kernel combination that's highly stable??
Your phone is probably accessing a corrupt part of your Emmc.
You will need to take out a larger part of memory using a modified pit.
See HG42's thread for information
superbrick? what's that? sorry im a newbie
eidecedie03 said:
superbrick? what's that? sorry im a newbie
Click to expand...
Click to collapse
Ha! its best you are aware of the issue - but best not to know it personally - I would recommend not to flash any roms without a good understanding of it.
eidecedie03 said:
superbrick? what's that? sorry im a newbie
Click to expand...
Click to collapse
Read up on super brick stickies and ics kernels before you go any further. Does indeed sound like you've damaged your Emmc and will need to repartition. Stock roms will likely not work anymore as you'll lose around 3gb of internal storage.
Sent from my GT-N7000 using xda premium
I did a manual check for corrupt areas and despite that, still having reset issues.
Any solutions??
Mediaserver is the culprit who try to access the bricked emmc part and get stuck there.. do freeze it and tell us the results?
Sent from my GT-N7000 using Tapatalk 2