Related
I have never bricked it before, and I cannot go into download mode... I tried the the Vol up and vol down, didn't work, so I have been using ADB and just ****ed something up....
Now I need to know a way how I can revert back to stock, please and thank you, I will forever owe you one.
EDIT: Okay there is some confusion, to simplify it I will take it step by step:
I replaced an APK file from my system/apps and ever since it has been force closing process.android.acore, so I tried reflashing to stock, it froze while doing so now I have a picture of a caution sign, a phone and a computer coming up on my Vibrant, it will not start up.
It is hardware locked because I have never been able to access download mode via hardware keys(I have always been using ADB).
Is there any way I can reinstall stock? Or is my vibrant now destroyed?
what exactly were you doing when your phone stopped working? "just ****ed something up" makes it hard to pinpoint problems...
I don't know I replaced my phone.apk with another one then ever since then it keeps saying process.android.acore has stopped working. It wouldn't stop showing up so I tried to reflash with Odin to stock but it froze and now it is bricked.
bumping a little bit, I have never bricked it before so I have 0 experience.
What do you mean by froze? On what screen? How far can you get into booting?
bigragu said:
What do you mean by froze? On what screen? How far can you get into booting?
Click to expand...
Click to collapse
Alright let me start over with more detail:
I tried to replace the dialer so I replaced the phone.apk and then process.android.acore kept force closing so then I tried reflashing with stock, during that I don't know what happened but I think my phone froze, so then it shut off and turned back on, I only found a screen with a computer on it... I am assuming it is bricked.... I also know it is hardware locked because I tried going into debug mode with vol up and vol down, how can I unbrick it?
Try moving the stock rom into the phones internal memory via adb. And flash it after a wipe.
I am Also having this same problem
I Flashed my Vibrant through Rom Manager to Froyo 2.2 from eugene373 and sombionix.
After flashing to both ROMS for Froyo I wanted to revert back to 2.1.
I tried to put sombionix 1.3 eclair ROM back on to my phone using clockwork mod.
The flash was not successful it stopped in the middle but the phone came on with a Force close error of an android process.
I tried to reboot through adb reboot recovery with usb debugging enabled.
The phone shut down like it would reboot into recovery mode and now it gets stuck on boot at the samsung vibrant screen.
I tried to use ODIN to flash back to the stock Rom but the phone is recognized in ODIN but will not flash.
ODIN sees the phone but will not get past flash analysis. (Sat for 8 Hours)
I believe this is the definition of bricked. Please Help!!!!!
sheek360 said:
Try moving the stock rom into the phones internal memory via adb. And flash it after a wipe.
Click to expand...
Click to collapse
It isn't even being read by my computer... nothing...
sympala said:
I Flashed my Vibrant through Rom Manager to Froyo 2.2 from eugene373 and sombionix.
After flashing to both ROMS for Froyo I wanted to revert back to 2.1.
I tried to put sombionix 1.3 eclair ROM back on to my phone using clockwork mod.
The flash was not successful it stopped in the middle but the phone came on with a Force close error of an android process.
I tried to reboot through adb reboot recovery with usb debugging enabled.
The phone shut down like it would reboot into recovery mode and now it gets stuck on boot at the samsung vibrant screen.
I tried to use ODIN to flash back to the stock Rom but the phone is recognized in ODIN but will not flash.
ODIN sees the phone but will not get past flash analysis. (Sat for 8 Hours)
I believe this is the definition of bricked. Please Help!!!!!
Click to expand...
Click to collapse
Excuse me sir, make your own thread, don't jack mine...
Smokexz said:
It isn't even being read by my computer... nothing...
Excuse me sir, make your own thread, don't jack mine...
Click to expand...
Click to collapse
lol Sorry Smokexz didn't mean to jack your thread just trying to consolidate phone bricked threads. I will create my own NO PROBLEM.
sympala said:
lol Sorry Smokexz didn't mean to jack your thread just trying to consolidate phone bricked threads. I will create my own NO PROBLEM.
Click to expand...
Click to collapse
Thanks, regardless both our situations are bad .
Please? I really need help with this.
Smokexz said:
Please? I really need help with this.
Click to expand...
Click to collapse
If there is an answer, which I am not sure that there is, it would be here: http://forum.xda-developers.com/showthread.php?t=782739. You may have already seen it, but if not it gives many different processes to try. Good luck!
hourst2 said:
If there is an answer, which I am not sure that there is, it would be here: http://forum.xda-developers.com/showthread.php?t=782739. You may have already seen it, but if not it gives many different processes to try. Good luck!
Click to expand...
Click to collapse
Yep, I'm screwed thanks for the help though.
Can you get the phone in download mode?
Did you try this:
Pull battery
hold the volume up and down
reinsert the battery whiles still holding down the volume up n down
plug in usb cord
it should put you back in to DL mode
Open ODIN and unplug phone from PC and plug back in hopefully it will notice it then.
I am not sure if you can get in DL mode and it just wont let you do anything, but if you have already tried this my apologies.
gthmcty1 said:
Can you get the phone in download mode?
Did you try this:
Pull battery
hold the volume up and down
...
Click to expand...
Click to collapse
Did you even read the OP? He is HARDWARE LOCKED ie BUTTONS DON'T WORK geeze people learn how to read!
And on topic, if you can't ADB and you are Hardware Locked, you are SOL. Try to get an exchange from T-Mobile since it appears that they regard being Hardware Locked as a defect.
Alright thanks
Sent from my Motorola_i1 using Tapatalk
gravis86 said:
Did you even read the OP? He is HARDWARE LOCKED ie BUTTONS DON'T WORK geeze people learn how to read!
And on topic, if you can't ADB and you are Hardware Locked, you are SOL. Try to get an exchange from T-Mobile since it appears that they regard being Hardware Locked as a defect.
Click to expand...
Click to collapse
Your a dumb ass, His thing actually does work.. I was "hardware locked" like 5 times That DOES work, you sir are a DUMB ASS < Had to say it again
(Make sure that your USB is plugged into your computer & not your phone)
Remove the back cover & remove the battery along with your sim & micro SD
Hold the VOL Up & VOL Down
(Keep holding those buttons) Now insert the battery
Plug the usb into your phone.
It will put you back in to DL mode
Open ODIN and unplug phone from PC and plug back in hopefully it will notice it then.
^^Do that
gravis86 said:
Did you even read the OP? He is HARDWARE LOCKED ie BUTTONS DON'T WORK geeze people learn how to read!
And on topic, if you can't ADB and you are Hardware Locked, you are SOL. Try to get an exchange from T-Mobile since it appears that they regard being Hardware Locked as a defect.
Click to expand...
Click to collapse
Wow you come in and try to offer up help and you get some one that feels the need to police the "suggestions"........ Have a coke and a smile my friend...and relax!
gthmcty1 said:
Wow you come in and try to offer up help and you get some one that feels the need to police the "suggestions"........ Have a coke and a smile my friend...and relax!
Click to expand...
Click to collapse
Not to mention that what that guy said actually works...
Some people just make me laugh
(Make sure that your USB is plugged into your computer & not your phone)
Remove the back cover & remove the battery along with your sim & micro SD
Hold the VOL Up & VOL Down
(Keep holding those buttons) Now insert the battery
Plug the usb into your phone.
It will put you back in to DL mode
Open ODIN and unplug phone from PC and plug back in hopefully it will notice it then.
^^Do that
My problem is that I had no idea that i9000 and Fascinate are complete diffrent firmwares. I flashed the 2.2 i9000 onto my Fascinate, I didn't find out this was a huge FUBAR until after the phone wasn't turning on and then I did some extensive searching. So now flashed the CWMRecovery and then the Stock-i500 files. Except for the Recovery file which fails when I try to run it on Odin... I'm completely lost. If anyone knows if it's possible to fix my phone, I would appreciate the help
its bricked. is it still under warranty? tell them it froze and wont turn on. are u stuck in a boot loop?
It was.. it would try to boot up into i9000 then the regular Samsung logo and then I'd get a blue pixelated mess... now when I hit the power buitton there's a cell phone and PC picture with a triangled exclamation mark in the center.
AdventXD said:
It was.. it would try to boot up into i9000 then the regular Samsung logo and then I'd get a blue pixelated mess... now when I hit the power buitton there's a cell phone and PC picture with a triangled exclamation mark in the center.
Click to expand...
Click to collapse
Sounds like it wants to be hooked back up, like it's not out of download mode. That's happened to me when I've unplugged the USB cable when it wasn't expecting me to. Dunno, there is a thread here somewhere about flashing the wrong image, then flashing an intermediary image, then the VZW image and getting things back. Not sure if it applies here, though... Good luck...
Boot in Download mode again
Dont Use Samsung MicroUSB Cable use any Good Quality MicroUSB instead
Flash the Clockwory Kernal and Recovery using ODIN
Copy ClockworkMod Recovery in update.zip format to SDCard
Boot into Recovery in Default Samsung Recovery Apply Update this will take you to clockwork
Flash any Compatible Clean ROM and you are in business,For me this Worked
You see the cable / triangle icon, it means your flash failed to take, and was incomplete. You need to re-flash, start with the kernel. I would use the CWM kernel as mentioned. If that fails let us know.
The only real thing you can do to "brick" this phone is to overwrite bml12 (modem.bin). For example, if you flashed anything with the "phone" box in odin, that will kill your modem. Other than that it will take a little work, but it's all recoverable.
Ok. For one, i have posted warnings all over the place to not do what you did.
And two, if what you flashed an Odin restore file with a modem in it, you will no longer have a working phone. We don't have a way to fix it. Sorry dude, best bet is to take it back to verizon and beg for a warranty replacement. If you are at the phone and computer icon right now, i would just leave it and take it into vzw like that.
namebrandon said:
Other than that it will take a little work, but it's all recoverable.
Click to expand...
Click to collapse
Nope, there are other things you can do to brick it / make it into just a fancy PDA
fallingup said:
Ok. For one, i have posted warnings all over the place to not do what you did.
And two, if what you flashed an Odin restore file with a modem in it, you will no longer have a working phone. We don't have a way to fix it. Sorry dude, best bet is to take it back to verizon and beg for a warranty replacement. If you are at the phone and computer icon right now, i would just leave it and take it into vzw like that.
Click to expand...
Click to collapse
Yeah. Problem is this isn't the first site I went to. There were no warnings in the other guides... Just said "Upgrade Galaxy S to 2.2" It never mentioned it was only for the i9000 model... I've learned my lesson tho. Luckily my buddy works at Verizon and I don't have to jump through rings of fire to get a replacement. Thanks everyone
fallingup said:
Nope, there are other things you can do to brick it / make it into just a fancy PDA
Click to expand...
Click to collapse
Yeah, like put it in a microwave. Which I'm going to do with you shortly if you keep it up. I can always cancel that $97 during my free trial, you know..
I think I've bricked my Galaxy S II.. I got it yesterday and tried to flash 2.3.5. When I was flashing with Odin, the program went unresponsive and crashed. There was nothing else to do but take out the battery.. I shouldn't have done it, but I did. And now it won't turn on at all. I've tried the 3 button method, for download mode, and a jig from my old i9000. Nothing has worked. The screen wont even turn on. I don't know what to do... Help Please??
you need a jtag.If it wont go into download or recovery its gone.
What do you, Jtag? I've got a usb jig, does that work? Or are they the same thing?
*What do you mean
aren't jigs phone-specific?
Any new info on this? Did jtag worked or whatever. I keep eye on this thread but looks like OP disappeared. Genuinely curious what happened with the phone.
Hmm .. very wierd that phone wont turn on ... i have broken Odin flashes purposedly many times myself but always I can get back into it ...
You could try power drain ... remove battery ... press power on button for 10 seconds (WITHOUT BATTERY IN) ... now put battery back in and try to go into Download mode.
Sorry but i got busy with other stuff but wanted to explain to him about the JTag.Its a special box called a RiffBox JTag and what it does is basically wipes the motherboard/bootloader and in most phones repears the bootloader aswell of a fully bricked phone so it can be put into download mode again letting you re-flash via Odin and thus saving your phone.A little miracle that means no more bricked phones.There doesnt seem to be that many around and to buy they aint cheap at all but if you can find a dealer or a phone shop who has one they can do it for you.For example.I bicked my phone and was going to buy the box on ebay.es imported (in spain there isnt any for sale) for 160euros complete or 140 without cables.Searched this site:
http://www.jtagbox.com/riff-jtag-bo...s-unbrick-bricked-phone-riff-box-owners-list/
and found a shop in Barcelona who did it for me for 35euros plus postage "BARGIN!!!!".If you search youtube and google for RiffboxJtag in your country you should find someone with a unit willing to help out or check the link ive given as it has a list of users worldwide.
EDIT:A jig is not a JTag.A jig will boot your SEMI-BRICKED(phone showing some kind of life ex.classic icon of phone/arrow/computor,menu and back arrow lights work e.t.c.) phone into download mode.A FULLY-BRICKED(dead,no signs of life.wont start.no download,recovery,lights nothing.DEAD!!!) phone needs a JTag
@cooza , Thanks for that explanation and site I even found one near me, that some day might come handy.
I must ask now to further clear my doubts, this riffjtag box, like you said is able to "revive" or "unbrick" _any_ bricked SGS2? No matter how bad is it? Im kinda new around these things and trying to suck up as much info/knowledge possible, before I decide to flash/root/?brick? xD haha ( hope not for last one) my phone.
Devourz said:
@cooza , Thanks for that explanation and site I even found one near me, that some day might come handy.
I must ask now to further clear my doubts, this riffjtag box, like you said is able to "revive" or "unbrick" _any_ bricked SGS2? No matter how bad is it? Im kinda new around these things and trying to suck up as much info/knowledge possible, before I decide to flash/root/?brick? xD haha ( hope not for last one) my phone.
Click to expand...
Click to collapse
Hi.As i said before there are semi and hard bricked phones.A semi bricked phone can normally be booted into download mode with the 3 button combo or a jig and your away again.It has the usuall symbol of a phone and a PC with a warning sign in the middle of them.Hard bricked is when the bootloader is damaged and there is basically no return.You got yourself a very expensive paper-weight for the office desk.Its like trying to turn on your phone with no battery in it.Dead,gone and not coming back.Before the Riffbox the only solution was the rubbish bin or maybe change the motherboard(but a few years ago that was an extremely pricey task if possible).Now we have the box.You can screw you phone to the point of no return and still the box will bring it back to life as it wipes the motherboard and in the case of the SGS2 also repears the damaged bootloader which is what boots your phone to start with.One thing to know,and i dont know if it happens to everyone but mine came back with 2.3.3 installed but there was no recovery mode.If this happens all you have to do is re-flash via Odin a more reciente firmware WITHOUT PIT FILE and yourll get recovery mode back at reboot.Obviously youll need to plug in your phone before hand to re-install the drivers.Same with Odin.boot to download,plug in,installs,unplug,then open Odin and flash.
EDIT:yourve got my name there so if something ever happens and you need a hand to re-flash after a jtag just send me a private message.Here to help.
SamBroomby said:
I think I've bricked my Galaxy S II.. I got it yesterday and tried to flash 2.3.5. When I was flashing with Odin, the program went unresponsive and crashed. There was nothing else to do but take out the battery.. I shouldn't have done it, but I did. And now it won't turn on at all. I've tried the 3 button method, for download mode, and a jig from my old i9000. Nothing has worked. The screen wont even turn on. I don't know what to do... Help Please??
Click to expand...
Click to collapse
im not juding you...but next time is better to flash with CWM.
Odin only for root kernel...
cooza said:
Hi.As i said before there are semi and hard bricked phones.A semi bricked phone can normally be booted into download mode with the 3 button combo or a jig and your away again.It has the usuall symbol of a phone and a PC with a warning sign in the middle of them.Hard bricked is when the bootloader is damaged and there is basically no return.You got yourself a very expensive paper-weight for the office desk.Its like trying to turn on your phone with no battery in it.Dead,gone and not coming back.Before the Riffbox the only solution was the rubbish bin or maybe change the motherboard(but a few years ago that was an extremely pricey task if possible).Now we have the box.You can screw you phone to the point of no return and still the box will bring it back to life as it wipes the motherboard and in the case of the SGS2 also repears the damaged bootloader which is what boots your phone to start with.One thing to know,and i dont know if it happens to everyone but mine came back with 2.3.3 installed but there was no recovery mode.If this happens all you have to do is re-flash via Odin a more reciente firmware WITHOUT PIT FILE and yourll get recovery mode back at reboot.Obviously youll need to plug in your phone before hand to re-install the drivers.Same with Odin.boot to download,plug in,installs,unplug,then open Odin and flash.
EDIT:yourve got my name there so if something ever happens and you need a hand to re-flash after a jtag just send me a private message.Here to help.
Click to expand...
Click to collapse
Thank you mate! I am getting my SGS2 this week so ive been doing alot of reading and research about everything. Thanks for your contribution and kind offer to help if ever comes to that. Very appreciated.
No worries mate.truth is its very hard to fully hard-brick an i9100.The main thing to watch out for,and its a mistake that first-time users/flashers have done,is to flash there i9100 phones with i9000 firmware by mistake.An SGS is not an SGS2 and if they are mixed you WILL hard-brick your device.Here on XDA everything is clearly marked and on their right pages so you cant go wrong if you take your time dont rush-in.But just in case you havnt seen it heres the thread:
Firmwares:
http://forum.xda-developers.com/showthread.php?t=1075278
CF-Root Kernels: (if you feel the need)
http://forum.xda-developers.com/showthread.php?t=1103399
Hi, dont bother faffing with it mate, if you have only had it a day take it back and tell them it wouldnt boot after an automatic Kies update. If they cant turn it on they wont know you bricked it until it gets back to the factory and to be honest after selling 10 million of these babies they wont even bother checking it out, they'll just put it into spares or straight recondition it.
I did the same thing to my xoom, PC world couldnt turn it on so they just gave me another.
Hi, everyone, I've recently HARD BRICKED my Samsung Galaxy MODEL: T959V with T-mobile. First off, I got pattern locked on my phone, yea I know I'm an idiot, LOL. Next I totally forgot my gmail password so I could not log back into my phone. So then I next decided to flash back to stock with odin 1.7 and T959UVJFD. tar file from this thread: http://forum.xda-developers.com/showthread.php?t=1047087. As a result, my phone would boot to the loading screen with the dashed circle and a battery display in the background and thus would not finish booting all the way. So I figured I would do more research and found that people would try flashing with the Eugene_2E_JK2_Froyo from this thread: http://forum.xda-developers.com/showthread.php?t=833024&page=49 and after flash back to stock. After I flashed with the Eugene rom this was when the phone completely died and would not turn on. I tried the take out the battery, holding down and up volume button and plugging into computer method but the computer would not detect it anymore. Now I don't know what to do. It won't turn on anymore and can't boot into download mode. Please help.. Thanks, and appreciate it.
I just got bricked too...Went to update my vibrant that was on eclair still...Try to update to froyo on Samsung Kies Mini...download went fine...then when finished...it wouldnt turn on....just ordered a JIG....should be here Tuesday...http://www.amazon.com/SainSmart-Don...73JQ/ref=sr_1_1?ie=UTF8&qid=1321751047&sr=8-1
and yes...my family on XDA...i tried every finger combination to try to get to download mode...Sitting outside waiting for ups as we speak...
You might need to look into a jtag, I wouldnt give up getting into download even if the screen is black. Some members have had sucess by pulling the battery, sim card and letting the vibrant settle for an hour or so. reset in odin and keep trying, your phone wont respond but odin may recognize it by the yellow com bubble.
im guessing u've tried this:
http://forum.xda-developers.com/showthread.php?t=848737
also read post #5 in this thread:
http://forum.xda-developers.com/showthread.php?t=1352334
be sure u understand what he says: he's basically just pretending the screen doesnt work and holding the buttons for the amount of time it would take to enter download mode. even tho the screen never responds, odin will suddenly recognize the phone. u can tell when this happens cuz that box in odin turns yellow. then flash JFD like normal or whatever ur gonna do.
good luck
Thanks for replying everyone.
Sugartibbs : I've been working on this all day. Yea, I definitely can't get it to work on odin. It's not being recognized at all. where can i get a jtag?
crypkilla : Yea I definately tried those two things already. I've searched all over the forum. I think it's time to take it in..... LOL. Is there a difference between the two models T959UV vs. T959V, in terms of the stock rom I was originally suppose to use?
that's a bummer.
i havent had a completely unresponsive phone before, but ive thought ive been pretty screwed a few times and the only other thing i know is that ive read people say that they've tried the same thing a hundred times and on the hundred and first time it worked and that's been my experience.
be sure and post if u do get lucky and fix it.
ascensi0n said:
Thanks for replying everyone.
Sugartibbs : I've been working on this all day. Yea, I definitely can't get it to work on odin. It's not being recognized at all. where can i get a jtag?
crypkilla : Yea I definately tried those two things already. I've searched all over the forum. I think it's time to take it in..... LOL. Is there a difference between the two models T959UV vs. T959V, in terms of the stock rom I was originally suppose to use?
Click to expand...
Click to collapse
You flashed wrong ROM and you're in wrong forum.
T-mobile Vibrant is T959
T-mobile Galaxy S 4G is T959V
T959UV is just a baseband not model number.
Sent from my T959 using XDA App
Yea I figured that I flashed the wrong rom after....so is there a way to fix it?
ascensi0n said:
Yea I figured that I flashed the wrong rom after....so is there a way to fix it?
Click to expand...
Click to collapse
First you need to get to download mode. Then try this
http://forum.xda-developers.com/showthread.php?t=1353176
Sent from my T959 using XDA App
ascensi0n said:
Yea I figured that I flashed the wrong rom after....so is there a way to fix it?
Click to expand...
Click to collapse
LOL i did the same thing ended up selling the phone :laugh:
Hey guys,
I have a galaxy s3 (I9300) and I've had it rooted for some time now. I started using CyanogenMod 10.2 nightlies a few months ago and they've mostly been fine. The odd issue comes up but I've been able to work it out. So, a few hours ago my phone just turned off of its own accord and started to bootloop, but on the "Samsung Galaxy S3 GT-19300" screen, not the CyanogenMod screen (to clarify, this screen comes up first then the cyanogenmod one usually). I've tried booting into recovery (CWM 6) but it just shows the CWM boot logo thing (that cog with the hat) and then loops back to the galaxy s3 page. I've also tried putting it in download mode, and it seems to stay on the warning page longer than it does anywhere else, but it wont let me actually put in it download mode from there.
I had a look around google and saw people have had the same problem, but everything I could find was when people had flashed a new rom/kernel etc. and something had gone wrong in the process. The weird thing about mine is that I haven't changed anything, even downloaded any new apps, for maybe a week, so it's not like something suddenly changed. I also wasn't using it when it started, it was just sitting on the table next to me.
Usually I can work these things out, but I'm stumped here. Any help would be really appreciated.
Thanks in advance!
danielbollom said:
Hey guys,
I have a galaxy s3 (I9300) and I've had it rooted for some time now. I started using CyanogenMod 10.2 nightlies a few months ago and they've mostly been fine. The odd issue comes up but I've been able to work it out. So, a few hours ago my phone just turned off of its own accord and started to bootloop, but on the "Samsung Galaxy S3 GT-19300" screen, not the CyanogenMod screen (to clarify, this screen comes up first then the cyanogenmod one usually). I've tried booting into recovery (CWM 6) but it just shows the CWM boot logo thing (that cog with the hat) and then loops back to the galaxy s3 page. I've also tried putting it in download mode, and it seems to stay on the warning page longer than it does anywhere else, but it wont let me actually put in it download mode from there.
I had a look around google and saw people have had the same problem, but everything I could find was when people had flashed a new rom/kernel etc. and something had gone wrong in the process. The weird thing about mine is that I haven't changed anything, even downloaded any new apps, for maybe a week, so it's not like something suddenly changed. I also wasn't using it when it started, it was just sitting on the table next to me.
Usually I can work these things out, but I'm stumped here. Any help would be really appreciated.
Thanks in advance!
Click to expand...
Click to collapse
can you at least enter download mode after a long time you said? if not, try pulling out the battery for 5 minutes or more and re-insert and enter download mode. i hope it's not sds! good luck
sriram231092 said:
can you at least enter download mode after a long time you said? if not, try pulling out the battery for 5 minutes or more and re-insert and enter download mode. i hope it's not sds! good luck
Click to expand...
Click to collapse
Nope, if I press the volume up button to go into it, it just goes back to the bootloop. I'll try the battery thing though, thanks!
Nope, it didnt work, I left it out for maybe half an hour and nothings changed :/ anyone else got any ideas?
SDS thread and BootLoop identical questions posted .
What does Product Code say in download mode .
But if you cannot get to download mode then you need a service centre repair .
looks like u are facing SDA but a bit diffrend than a normal SDS.. mine still can go into download mode with blank product name..
If product name is blank in download mode then you got sudden death, consider a phone as a brick. Nothing will help, including repartitioning.
You need to contact service centre.
I'll check it in a minute, but if it is bricked, will any service center actually help me seeing as it's rooted and all?
danielbollom said:
I'll check it in a minute, but if it is bricked, will any service center actually help me seeing as it's rooted and all?
Click to expand...
Click to collapse
AFAIK if it's sudden death then it's not possible to detect root and other modified things, or in other words - nobody has money to prove that you have been using unofficial firmware .
JustArchi said:
AFAIK if it's sudden death then it's not possible to detect root and other modified things, or in other words - nobody has money to prove that you have been using unofficial firmware .
Click to expand...
Click to collapse
Ahhhh, well that is handy then
In terms of a service centre, will samsung have a list of them somewhere so I can find one near me?
So I contacted samsung and they gave me the link to book into a service centre etc, but I just realised that when I try to go into recovery mode, the CWM recovery logo comes up before going back to bootloop. Is there any way to get rid of that so that my root is completely untraceable?
danielbollom said:
So I contacted samsung and they gave me the link to book into a service centre etc, but I just realised that when I try to go into recovery mode, the CWM recovery logo comes up before going back to bootloop. Is there any way to get rid of that so that my root is completely untraceable?
Click to expand...
Click to collapse
If you can't flash anything with Odin (stock software) then you're screwed. Eventually you can try to enter recovery and flash "eraser" of recovery, but this requires working recovery... So if you actually can enter recovery then you can also flash anything, which will literally delete everything.
In other case, no, no way. But if you're lucky enough you may break it just by leaving your phone on for some hours in bootloop, haha.
JustArchi said:
If you can't flash anything with Odin (stock software) then you're screwed. Eventually you can try to enter recovery and flash "eraser" of recovery, but this requires working recovery... So if you actually can enter recovery then you can also flash anything, which will literally delete everything.
In other case, no, no way. But if you're lucky enough you may break it just by leaving your phone on for some hours in bootloop, haha.
Click to expand...
Click to collapse
Is there any way to wipe it with magnets or anything? hahah I'm clutching at straws now, but otherwise I'm just left with an expensive paperweight so I'm trying to find anything I can
danielbollom said:
Is there any way to wipe it with magnets or anything? hahah I'm clutching at straws now, but otherwise I'm just left with an expensive paperweight so I'm trying to find anything I can
Click to expand...
Click to collapse
To be honest think twice before physically crashing your internal memory, as it may void your warranty at all.
I'd try flashing stock firmware through odin, if it doesn't work I'd try flashing anything through recovery. If both of these methods fail just leave your phone in bootloop and hope that it'll automatically destroy everything... :laugh:
Seriously though, you can either physically destroy internal memory or leave it in bootloop and hope for the best, eventually send them device in current status. Up to you, because you won't have a possibility to do anything else.
JustArchi said:
To be honest think twice before physically crashing your internal memory, as it may void your warranty at all.
I'd try flashing stock firmware through odin, if it doesn't work I'd try flashing anything through recovery. If both of these methods fail just leave your phone in bootloop and hope that it'll automatically destroy everything... :laugh:
Seriously though, you can either physically destroy internal memory or leave it in bootloop and hope for the best, eventually send them device in current status. Up to you, because you won't have a possibility to do anything else.
Click to expand...
Click to collapse
If I send it back to them as it is now it'll take them about 20 seconds I reckon before they see the CWM logo, realise its rooted and send it straight back, so I dont know what I'm gonna do hahah