After upgrading to 2.3.3 on my captivate the three button fix was applied, is it hardbricked and needs to send to Samsung?
you didnt read instructions did you?
how do you go back to stock? ODIN ONE CLICK
THEN flash 3 button fix with odin3 flasher ONLY IF YOU NEED TO after 1 click (shouldnt need to)
WHY? well that was in the instructions too!
3button fix only has 1 of 2 original bootloaders.
is it hard bricked?... probab-****in-bly.... does it turn on? you tell us...
send back to samsung, yup but keep your mouth shut and play dumb (shouldnt be hard)
ALL YOU SAY: "it stopped working" and stick it to the back of a big speaker magnet for an hour. (take out your sim and sd card dummy!)
well that was an expensive lesson..
Haha yes you probably did brick. Is it really that hard to read instructions? I flash at least 3-4 times a week and have never even come close to bricking. If you do exactly what the devs tell you to do then its almost impossible to brick your phone. However you clearly didn't read. To answer your question, yes, you most likely did brick your phone.
Sent from my beloved Cappy running Continuum 5 RC3
Its not brick I did the same stupid thing but I was able to fix it whit a jig
Sent from my GT-I9000 using XDA Premium App
if you mix bootloaders, you are screwed.
Well I did. And it won't work whit the jig until I pull the battery out many times and reinstall drives
Sent from my GT-I9000 using XDA Premium App
reinstalling drivers has nothing to do with you phone bricking, so.. please just stop there,
but im not willing to thow out a 400$ brick just to prove you wrong... so fine you win! mix bootloaders all you want.
TRusselo said:
reinstalling drivers has nothing to do with you phone bricking, so.. please just stop there,
but im not willing to thow out a 400$ brick just to prove you wrong... so fine you win! mix bootloaders all you want.
Click to expand...
Click to collapse
lol backing up Tru here.. If you mess up with bootloaders, the ONLY way back is a JTAG.
If you can fix it with a JIG, your bootloaders are intact and have never been mixed/damaged.
There is no way around, that's just how it is..
J tag is no guarantee though, 99 % ya but it costs more than I paid for this phone...
And ya like I said no mixy de boot loaders
Related
First off there is no section to Continuum so I'm simply posting in here rather than android development. I have read up and am going out later today to buy some resistors in order to test if I can get into download mode that way.
Okay so I 1 click odin'd back to stock from firefly 2.8. I then tried to use the button combinations to get back into download mode after flashing stock. I lost the button combinations after using odin. So I one click rooted, installed terminal emulator and was able to get into recovery and download mode using that method. I began the process of flashing continuum and flashed the gingerbread bootloaders. It went fine. I9000 flash screen popped up and it booted into eclair. Stupidly I used an older update .zip to flash cwm and then flashed a 3 button fix .zip in order to get the 3 button combo back before moving forward. After I choose to reboot in cwm. Nothing happened. Phone is completely unresponsive (button combos, power, won't charge). Complete paper weight right? I already have a replacement coming from att but I just wanted some input as to how much I messed it up and if ATT can go through my files after they jtag the phone I send them back.
Bricked!! You DID NOT need the button fix on the new bootloaders, you had a working combo with the new ones its contained in the secondary bootloader its just a different series of buttons flashing the button fix mixed a gb primary bootloader and a eclair/froyo secondary= completely ****ed. No jig in the universe can save it.
Att won't be able to tell, they have to take it apart and flash it, thus erasing all evidence.
studacris said:
Bricked!! You DID NOT need the button fix on the new bootloaders, you had a working combo with the new ones its contained in the secondary bootloader its just a different series of buttons flashing the button fix mixed a gb primary bootloader and a eclair/froyo secondary= completely ****ed. No jig in the universe can save it.
Att won't be able to tell, they have to take it apart and flash it, thus erasing all evidence.
Click to expand...
Click to collapse
lol anything out of the universe that could fix it?... OH YEAH I KNOW, I KNOW! A JTAG
Then again, go for waranty 1st. Studa is right, once you mess up with the bootloaders, there's nothing you can do about it. Your phone is bricked.
studacris said:
Bricked!! You DID NOT need the button fix on the new bootloaders, you had a working combo with the new ones its contained in the secondary bootloader its just a different series of buttons flashing the button fix mixed a gb primary bootloader and a eclair/froyo secondary= completely ****ed. No jig in the universe can save it.
Att won't be able to tell, they have to take it apart and flash it, thus erasing all evidence.
Click to expand...
Click to collapse
Sent from my GT-I9100 using XDA App
Studacris,
I'm not a noob. I am running continuum on my other captivate and have flashed many times. I did try the other key combinations NOT the standard ones. They still would not work. I understand that is bricked. I figured as much. The jig was in case any of you asked if I at least tried. AlI needed to know.
I sort of did the same thing
http://forum.xda-developers.com/showthread.php?t=944418&page=63
The last post here, the guy said he used the All-in-one tool to load Continuum 5, so I tried it. Woops. At least my contract is up, may look into the Inspire.
I have not tried a jig, since ever post I've seen, if it don't even flicker with the buttons, it's a waste of time.
Later
I recently bricked mine as well. I believe you can walk into an att device repair center located in your town and let them play with it for a few minutes. After they figure they cannot fix it they will give you a replacement.
Least thats what they did years back with my htc kaiser (at&t variant). I even took apart that kaiser and messed with the internals. They said "you know it's out of warranty cause the void sticker is damaged?" I said "What? No I didn't know I didn't do that." They replaced it anyway. They are pretty nice when it comes to these things.
I currently have a bricked cappy. Gonna take it in friday.
Where in any of the GB bootloader instructions on any of the ROMS does it say flash 3 button fix. Its says read over and over how to flash and follow to the T. You failed nice job. That is why the dev write the instructions so that you can read and follow.
Sent from my GT-I9000 using XDA Premium App
BWolf56 said:
lol anything out of the universe that could fix it?... OH YEAH I KNOW, I KNOW! A JTAG
Then again, go for waranty 1st. Studa is right, once you mess up with the bootloaders, there's nothing you can do about it. Your phone is bricked.
Click to expand...
Click to collapse
HEY STUDA!!! doesnt this sound familiar??? lol dumb ass!
didnt i say what you did?
and you said what bwolf did?
couple days ago...
teach you for making me look dumb!
and +1 for dingokevin!!
keepin an eye on you!
TRusselo said:
HEY STUDA!!! doesnt this sound familiar??? lol dumb ass!
didnt i say what you did?
and you said what bwolf did?
couple days ago...
teach you for making me look dumb!
and +1 for dingokevin!!
keepin an eye on you!
Click to expand...
Click to collapse
wait what?
oops nevermind that was bwolf doing that to me the other day... lol
damn short term memory...
wait what?
Since nobody can read. I ALREADY HAVE a replacement coming. I DID read the instructions and have successfully installed roms since cognition. Mods please lock thread because everyone likes to jump down peoples throats and assume rather than reading my explanation and how I knew it was bricked already. Thanks for nothing.
Sent from my GT-I9100 using XDA App
thread locked by op request.
So I just got a replacement cappy through warranty. Of course stock is coming off real soon. However I was wondering is there a uckb2 odin package just in case there is something that goes wrong and I have to send it back to warranty? I'm going to do some research on how to make one but if there is one already it would be great.
-edit: I imagine these instructions can work for our captivates right...?
http://forum.xda-developers.com/showthread.php?t=1082288
http://forum.xda-developers.com/showthread.php?t=926546
OK. I think I got it from the instructions posted on the provided posts. Would anyone like to try it? According to the post it shouldn't have bootloaders so I'm not affraid of it bricking my device. Although I am scared because if I soft brick, I'm afraid I wont be able to get it back to stock if I need to
Sent from my SAMSUNG-SGH-I897 using XDA App
My phone is bricked by ROM manager. My phone can't boot into recovery mode, downloading mode nor normal phone. The phone charges the battery so there is still hope to fix it. I also have a JIG Usb just incase. if you got any questions you need to ask, please ask. I really want my phone back.
Darth343 said:
I also have a JIG Usb
Click to expand...
Click to collapse
see this video
Can someone answer me - WHY are you using ROM manager when it's known that it kills our Galaxy Mini? Is it really that hard to use Odin, or just flash CWM recovery through the stock one?
Guess some people love to learn it the hard way. You have a unrepairable (at least at home) BRICK!
domcale said:
Can someone answer me - WHY are you using ROM manager when it's known that it kills our Galaxy Mini? Is it really that hard to use Odin, or just flash CWM recovery through the stock one?
Guess some people love to learn it the hard way. You have a unrepairable (at least at home) BRICK!
Click to expand...
Click to collapse
Sorry! Just a thought came to my mind can it b there any solution for this evergreen problem? Like newbies r bricking their phone again & again. ( like warning in stickies) . Just thinking! !! That's all.....
Sent from my GT-S5570 using xda app-developers app
You have no reason to be sorry . It's a great idea to put a warning message about ROM Manager in a sticky. However, i once was a total noob too, and i flashed CWM using Odin, it didn't even came to my mind to use ROM Manager.
Reading a couple of different tutorials and educationg yourself before doing anything is the best possible thing someone can do to prevent situations like this.But, like i said, some people have money to waste
lol ... ROM Manager is screwing up everyones phone. Even my friend's mini bricked. He was unlucky that his warranty had got over. He asked the samsung service center and they told him that it would cost $90 for a new motherboard. He uses his galaxy mini as a paper weight now. Rather buy a new phone than buy a motherboard for $90.
If your phone is under warranty, you can get your phone fixed for free in samsung service center( free new motherboard ). Even I bricked my phone when I was a noob with ROM Manager thankfully my warranty was valid that time.
Although I was able to use ROM Manager with no problems.
domcale said:
You have no reason to be sorry . It's a great idea to put a warning message about ROM Manager in a sticky. However, i once was a total noob too, and i flashed CWM using Odin, it didn't even came to my mind to use ROM Manager.
Reading a couple of different tutorials and educationg yourself before doing anything is the best possible thing someone can do to prevent situations like this.But, like i said, some people have money to waste
Click to expand...
Click to collapse
One real problem is that Rom Manager comes by default on most CM7 based roms. So most new users while experimenting might brick their phone by accident.
TheWhisp said:
Although I was able to use ROM Manager with no problems.
Click to expand...
Click to collapse
You were lucky, I guess
anshul sood said:
One real problem is that Rom Manager comes by default on most CM7 based roms. So most new users while experimenting might brick their phone by accident.
Click to expand...
Click to collapse
I agree, but nobody forces them to experiment with something they have no knowledge of. Phones are not toys to play with (to some extent )
A big warning in the general and development section would be enough.
domcale said:
I agree, but nobody forces them to experiment with something they have no knowledge of. Phones are not toys to play with (to some extent )
A big warning in the general and development section would be enough.
Click to expand...
Click to collapse
Most new users don't browse the stickies, just notice the large no. of redundant and useless threads. They just open the thread pertaining to the rom they want and that's that. It would be nice if each Rom had either the rom manager removed or a warning with the download link itself
never say to anyone that rom manager's brick cannot be recovered in home, it can be
the only step is just press volume down home power button but without panicking, panicking is the main reason of can't able to get into download mode
then just flash with odin, dont think it cannot get into dl mode, dl mode is controlled by bootloader and bootloader is not removed by rom manager
Unsuccesfull flash of bootloader hard-bricks our device, so you can't enter DL mode.
You can always give it a shot with a USB JIG* tho. But in most cases, the only thing that helps is JTAG.
*USB JIG - a 301k resistor between the 4th and 5th pin on the microUSB connector.
Tried that.
I've seen that video like about a thousand times. No luck i even went to a repair men today, he said your phone is dead if it can't go in to recovery menu. Is there any other way i can repair my phone? Sorry for late VERY reply
Yes, either use JTAG or send it to the service center.
Brick caused by rom manager is absolute
Nothing can be done
Sent from my GT-S5570 using xda premium
Me to I used it for making backups, but currently, I'm using cm 10 without ROM Manager.
Same problem with me the board was not responding so Samsung service centre changed my board.
Sent from my GT-S5570 using xda premium
If there isn't really anyway, then i'll just buy a new phone.
Darth343 said:
If there isn't really anyway, then i'll just buy a new phone.
Click to expand...
Click to collapse
Sorry you had to learn it the hard way. When you're new in this world it's easy to 'trust' all CM standard apps. Nevertheless: using CM means you're a root user. Your phone is rooted which means you can seriously damage your phone when you don't know what youre doing. That's exactly the reason why your phone is NOT rooted when you buy it, and your garantee is void when you root it yourself!
Some of these apps provide a warning: with great power comes great responsability!
Nevertheless: the first thing i do when i buy a new Android is rooting it! But a general warning is at place: root apps can damage your phone. Especially those to install roms. Even with a proper CWM you can flash a wrong or faulty Rom. The risk of bricking your phone is always there.
So think twice when you buy a new phone and read all about flashing on XDA!
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.