Related
Ok guys, I feel this is just the end of the games... I was flashing back the Roto JME fw with the swype keyboard issue fixed that I have just made, when I accidentally unplugged the tab while starting flashing and in downloading mode.
Now all I get is a logo with a phone an alert symbol and a computer .
Windows as well as Odin see it, but I can't do anything, as Odin hangs on waiting for connection, or something like that.
Is there anything I can do?? Or do I really have to take it to the warranty? And if I will have to take it to the warranty will they see I have previously flashed a beta rooted image on it??
Here's what I am talking about
Please I need some help..
Thanks
Is there no recovery mode by buttons like the captivate? I hate seeing all the bricks
Sent from my SPH-P100 using XDA App
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...
Segnale007 said:
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...
Click to expand...
Click to collapse
Ops, it was the driver... damn windows ...
Solved btw.. I just realized I have lots of things to learn ... I have almost died of heart attack when I saw my tab stucked on that logo.. and now its back again..
Thank u falks
You need to make sure samsung kies are not running for sure unistall it and try it again
use odin. that is still download mode. might take you a couple of tries but works. i was in your shoes the other day
Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Segnale007 said:
Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
I've heard plenty of goofy stories about bricking devices over the years. You must conclude the following:
1.Flash your device in a locked room to avoid your wife/ child pulling cables or pressing buttons.
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
3.Read instructions carefully and write the procedure out in your own words if its your first time.
I've been flashing for years and haven't had a brick yet. Not crossing my fingers either because it has little to do with luck and much to do with care. In this way its a lot like making babies...
ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Good advice.
My only semi-bricks (that involved an hour or two of trial and error to unbrick) resulted from some manner of overzealous cable unplugging.
zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
This is what I have done
Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse
ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Well, first of all thanks for ur nice words. Let me just say that I was about to disconnect another device from the hub where the GTAB was attached and flashing at that time, and yea, I accidentally unplugged the GTAB instead of the other device. I may be a moron, thanks, and thankfully not everyone believes themselves as god, which is a good reason to not help other people who are in troubles, even if for stupid things sometimes... If everyone were thinking like u we were probably still at the age of 1400 ...
Mate it wasn't a barb directed at you personally, but you weren't exactly careful were you?
I'm no god... but I've never bricked a device either, and I've been flashing for over five years now. To top it off I've almost never owned a device which could be taken back to the shop (90% of them come from other countries, not my local retailers). Perhaps this has taught me to be careful.
In any case, what I said holds true, and if you ask around I'm certain you find most will agree.
Dude, you have the best avatar! I can't keep my eyes away! Good luck, and don't worry about mistakes - that is one reason this forum exists.
Cannot start my Gtab after trying update JMC
...Hello everybody,
I am really worry about the fact my Gtab doesn't want to switch on after trying to flash it. I tried all process to put it on download mode or recovery but nothing work.
Do you have any idea about it ? Is there a specific procedure to switch on (eg : press power for 1 minutes + blablabla).
My provider doesn't want to take my Gtab in warenty before my contract is activated (the 4th of february).
Thank you for your answer
HELP, I have same problem, please explain how Hemidall can fix it?
Thanks
[email protected]
zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
I also had a semi-bricked VZW Tab, with the phone-triangle-computer warning graphic at start up. (I flashed a new boot loader, and failed to read the instructions closely enough. Either the file was incorrect for my device, or the drivers were not loaded correctly, but my tablet was borked.)
Using heimdall 1.3.2 (with the correct drivers, on a 32-bit windows system), I clicked the "close pc screen" option to clear the warning.
I then held the power button until it turned off, then held vol+ and power to re-enter download mode. Once in download mode, I used heimdall 1.1.1 to flash the zImage from SCH-I800-Stock-Rooted-2.3.5. My tablet (still unrooted, and still stock?) booted, but sat at the SAMSUNG logo for ten minutes or more. (It announced its progress, telling me periodically "five minutes remaining", etc.)
Once it finished, my tablet was revived. I will now follow the above advice and read all instructions very carefully, re-writing them in my own words to ensure I understand what I'm doing, before I try this again.
One year old thread......do you guys ever watch posting dates???
Sent from my GT-P1000 using Tapatalk 2
...like REALLY bricked
bumping this old thread in hopes that someone can point me in the right direction...
Got my p7510 (10.1" wifi retail) stuck pretty badly when trying to restore stock ROM coming from Overcome (it came rooted from ebay). From what I gather from the forums, seems like my bootloader is still locked.
whenever I attempt to flash a BOOTLOADER, PIT, or PDA using ODIN it connects, initializes, and gets stuck on "Flashing boot.img"
I think the recovery partition is damaged. When I boot using Power + Volume Down, I can get to the screen where you select recovery mode or download mode but recovery mode will not load. The screen flickers when I select recovery, but goes nowhere. Download mode works.
I tried using nvflash to force the right software onto it but I get error 0x4 (usb write failed).
There has to be a way to restore the stock bootloader and get this thing running again. Tablet will not boot android at this point. I have been searching the forums for about a week now, anyone have any ideas?
The story so far...
Bought a new Optimus Black and gave it to my girlfriend for her birthday a couple of days ago. After playing with it for about an hour she put it down, I picked it up and decided to have a tinker. I installed Cyanogen mod 3.5.1 after rooting it with Gingerbreak. So far so good but I didn't really like the look of the ROM and the absence of a Market seemed like hassle so I used ClockworkMod to restore the backed up stock ROM.
It's still working fine but now I see there is an official update from inside the phone. I presume it's the upgrade to Android 2.3 so run it and reboot the phone. That's when it all goes wrong. I'm now stuck in the CWM recovery screen. I try all the options, following any online guides I can find that were supposed to have worked for people. I try restoring the backup, restoring cyanogen, clearing the cache, dalvik, everything but nothing happens and I keep booting back into the CWM recovery screen.
Next day I try the LGUnitedMobileDriver and the phone recovery option but despite trying several times I can get no further. A friend tried to use Odin to restore it but got no success. Finally, we tried restoring with a KDZ file with
KDZ_FW_UPD_EN, Windows Enabler and LG B2CTool and now the phone got stuck in yet another loop - a black screen with 'updating firmware'. The LEDs flash for a minute and it reboots and does the same again.
What's more, the phone will now no longer charge or turn on without being connected to the mains.
What are my options here?
Follow the tutorial given below.
http://forum.xda-developers.com/showthread.php?t=1275315
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
pickarooney said:
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
Click to expand...
Click to collapse
have you tried the CS_EMERGENCY option in R&D TOOLS? Wait I'll find the link..
Here >>> http://forum.xda-developers.com/showpost.php?p=18841596&postcount=8
http://forum.xda-developers.com/showpost.php?p=18740082&postcount=45
The CS_EMERGENCY is the only thing worked, he used a german V10A ROM. If you managed to unbrick it, you can flash it again with your desired KDZ, or use CS_EMERGENCY and flash directly your desired KDZ. TRIAL AND ERROR.
Emergency c-section... nope, I will try that now!
Said that it will get stuck at 4% but it is still flashing. Just wait for the phone to reboot by itself.
It just crashes with a fatal error as soon as it gets to the second tab (downloading) on both PCs I tried it on. I tried several KDZ files with the same result.
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
pickarooney said:
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
Click to expand...
Click to collapse
Does it have warranty? Why not RMA it, I think it has a hardware problem now since you mentioned it doesn't charge anymore. Also, have you tried a different USB cable?
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
pickarooney said:
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
Click to expand...
Click to collapse
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
gabwerkz said:
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
Click to expand...
Click to collapse
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
darkzorn said:
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
Click to expand...
Click to collapse
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
Fingers crossed for you !!!
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
IT will mostly work..Good luck though and please do reply here and let us know if it worked..
I'm a complete noob in dire need of help. I wanted to root my phone, and read the 3 procedures mentioned in the sticky thread. The 2nd one (nvflash) seemed very well explained and was sure to work with 2.3.4 so I decided to use that. As I was in my friend's house I used his pc and installed the drivers while my phone was connected in apx mode. Then I double clicked the "install internal xp" batch file which resulted in a black window with some texts, but seeing this my friend freaked out and closed the window before the process was finished. I told him he shouldn't have done that. I then disconnected the phone and switched it on. It seemed to switch on properly. So I then switched it off again and pressed and held the power and vol down switches to see if I got cwm. This showed LG screen for a few seconds and then the screen went off.
Now whatever I try to do I can only see the LG screen for a few seconds and then the screens goes off. No power on, no recovery, no nothing. And I can only attempt to even power on once, after the screen goes off I must remove the battery before the power button does anything again.
I tried to freshly nvflashing the recovery many times, but it made no difference. Does this mean my phone is bricked? Please tell me how I can solve this as I'm really worried.
NVFlashing the recovery again *should* have worked. So we first need to make sure you're trying to start CWM the correct way.
1) Unplug phone
2) Remove battery for 10 seconds.
3) Insert battery
4) Hold volume-down, do not let go, keep pressing it.
5) Press power button, keep it pressed.
If/when you get the second LG-logo, bluish halo, you can release both buttons, not before.
Nope, that was exactly what I was doing to access the recovery. I tried it again just now and it didn't work.
It just displayed the regular LG logo and then the screen went off. I'm not sure the phone completely shuts down 'cause if I keep it like that it gets quite hot and I can't use the power button again to try to power up. Only removing and re-inserting the battery gives me another attempt.
Is there any chance this is a hardware issue?
Hardly any chance this is hardware related if it was working before the first NVFlash.
Good, next step will be to NVFlash a complete stock ROM. You will unfortunately lose any data you might have on it, but that's the price to pay.
Go here, follow the instructions precisely, skip installation of apx-driver. Report back.
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
sean8000 said:
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
Click to expand...
Click to collapse
It works, yes, but is the original Froyo. This is just a way to get the phone up and running again.
Later you have a few choices. Either install CWM, then install you ROM of choice, or upgrade it to the latest for your region by using the LG Update tool.
EDIT. Oh, and btw, it is better to open a command-window and type the flash.bat command. If there are any errors you will still have them on-screen.
Thank you for all the help and support. I didn't get a chance to flash the rom till now (being on a vacation without a smartphone sucks). But I'll try it asap and report back.
So, how did it go?
TrymHansen said:
So, how did it go?
Click to expand...
Click to collapse
I haven't flashed it yet. I've decided to do it after I return home. I'm at my friend's house for 2 more days.
Ok, bad news. I flashed the stock rom you linked. The process went pretty smoothly. After the window got closed and the lg logo on the phone was visible 2 times, I unplugged it and installed the battery. But switching it on wasn't fruitful. It just displayed the LG logo for a couple of seconds and then the screen went off (just like before, only faster). I tried repeating the whole process, even tried to nvflash cwm once again, but nothing happened.
So is it a hardware issue? My phone is no longer in warranty period, so a hardware problem would be really bad...
So is it a hardware issue?
Click to expand...
Click to collapse
I don't know.
What would be helpful is to get a copy of the output you get when you NVFlash, it's simply the only way to verify that the flash process went ok. If you have an aborted flash it of course won't work, and may display the behaviour you describe.
EDIT: Btw, early on there were some ROMs which refused to boot properly unless the baseband was of an early variety as well.
If you feel confident the NVFlash has been successfull, smartflash an old baseband as well, see if it boots then.
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
gabriel2anjos said:
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
Click to expand...
Click to collapse
Now what's this "Jtag service"? (edit- I googled it and it seems to be a method of un-bricking stuff with specialized hardware or something, but I'm not sure I can have that done where I live)
Is there any way to fix the bootloader by myself?
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
sean8000 said:
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
Click to expand...
Click to collapse
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
TrymHansen said:
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
Click to expand...
Click to collapse
Ok, I'll try that when I have the time.
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
sean8000 said:
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
Click to expand...
Click to collapse
If it is you're only the second person in this forum to ever brick his phone. Anything's possible I guess. Some flash cells may have been damaged the first time the power was yanked. But then we should presumably get some verification errors during flashing.
Anyway, I'm at my wits end, and I really do hope you get it up and running, but I don't have anything more to contribute. Good luck.
Corrupted bootloader means that your cellphone simply don't know what to do when you hit the power button, due to the damage. As the cell phone can't turn, the pc can't recognize it. If your cell phone were a samsung, you could try to use a jig to have acesso to the download mode. But I don't know if it would work for a LG. You could try anyway.
And if you live at big city, usually it's common to have some jtag services.
Please, dont be afraid of hitting thanks
Please, dont be afraid of hitting thanks
Ok, so I took the phone to the service center today. The guys there said its battery terminals are messed up. They said replacement terminals are not easily available, but they'll try to find some. And of course I'll have to pay for it. I guess it's still better than using the phone as a paperweight.
What do you guys think?
Good luck I managed to mess up my phone like you too. I'm from India. But the difference was that I was covered by warranty. I managed to get a bunch of hardware replaced and was up and running again.
Morning all,
I apologise if this is in the wrong section but I am new to the forum and in a bit of pickle.
Around a week ago I rooted my lovely new note 3 to hopefully one day install some nice new ROM to get rid of the horrid touch wiz and actually see the full potential of the phones power. However, for some silly reason while I was using titanium backup on my phone I thought it would be a good idea to uninstall touch wiz thinking it would magically go back to basic android however it didn't. It is completely broken now, woops. The first issue I had was it would boot up and stick to the Samsung logo and just glow so I thought it would be an idea to install stock ROM via ODIN to try and revert it back to normal. Once I downloaded the correct stock ROM it was uploading through download mode however at the last minute it failed with a ext4 error which I think it means it's bricked? Not sure, completely new to this. I am now a bit stuck as I am not 100% sure what to do next.
The phone will only boot into either the firmware upgrade has encountered an issue, basically Odin mode or download mode. I have tried recovering it through kies however it cant connect to it. It knows it is there as it will start searching for it when it's connected however says it can't find it.
My phone is a note 3 SN SN-9005. The system status is custom, reactivation lock is off, Knox kernel lock 0x0, Knox warranty void 0x1 and write protection is enabled.
Obviously I would like to get the phone back to normal, I don't care if it has to be completely wiped and brought back to normal I would like it to just work. I've been an complete idiot and fiddled with something I'm not 100% sure on and I would like to not have a 600 quid paper weight hehe.
I will greatly appreciate any help or feedback.
You won't get the best feedback for a 9005 model here. We are the 900A version stuck on AT&T. Yes, however, we have plenty of intelligent people here. It's best to post your question here in the main Samsung Galaxy Note 3 thread next time:
http://forum.xda-developers.com/galaxy-note-3/help
Next, since you've voided your warranty as Knox being 0x1 - you're pretty much screwed for a refund or replacement based on PRESENT development from what I have read all over the AT&T threads. Understand this. Now, that being said, did you install a custom recovery or have your original recovery?
Here's my input/help. Forget about ODIN. You don't need that if all you did was remove your touch wiz.
Take out your battery, put it back in and hold VOLUME UP, POWER, and HOME together until you reach a recovery. Then if it's the stock recovery, wipe your cache partition, then wipe data/factory reset. Then reboot and you're good back to starting over. Check with a rooting application to see if you still have or not. If not, then obviously reroot
Also, don't ever do anything like that again without thinking what it could do, lol . Always tread carefully whenever you are new to something. Just my two cents for you. If you came here to root and learn it, don't be afraid to ask questions about applications and expanding your knowledge. No one will ignore you if you ask a simple question in the right manner/thread.
Good luck!
Thank you for the feedback. I have defiantly learnt from my mistake with this one. I have usually been lucky diving into things blindly hehe. I have tried to put it into recovery mode however it just vibrates like it should and then comes back up to firmware upgrade issue with the two computer screens an a attention sign in the middle. Is there anyway to get recovery mode back.
apdnote said:
Thank you for the feedback. I have defiantly learnt from my mistake with this one. I have usually been lucky diving into things blindly hehe. I have tried to put it into recovery mode however it just vibrates like it should and then comes back up to firmware upgrade issue with the two computer screens an a attention sign in the middle. Is there anyway to get recovery mode back.
Click to expand...
Click to collapse
Wish you had come here when you deleted touchwiz only instead of playing with Odin. Looks like you messed it up even further and have to now use Odin to reinstall your firmware. I'm about to go to sleep, but do this.
1) Take out battery and put it back in. Then press and hold VOLUME DOWN + HOME + POWER at the same time until you reach DOWNLOAD MODE.
2) Follow the steps here and use your odin or latest odin (shouldn't matter):
http://www.androidrootz.com/2013/10/how-to-unrootunbrick-galaxy-note-3.html
Oh, and google is your friend. It's how I learned things over the years...READING, then tinkering....you're welcome .
I wish I did as well. I will try this when I get back from uni this evening and post back results.
Thank you again.
apdnote said:
I wish I did as well. I will try this when I get back from uni this evening and post back results.
Thank you again.
Click to expand...
Click to collapse
You're very welcome, bro.
opasha said:
You're very welcome, bro.
Click to expand...
Click to collapse
I used what you have said to do and downloaded the correct firmware however when I try and install it via odin in download mode I get a FAIL(SIZE!) message at the end. Its not an ext4 error anymore but im worried at what is going on now. I have tried searching it up on google however nothing has come up. Looks like ive completely broken it... ='(
apdnote said:
I used what you have said to do and downloaded the correct firmware however when I try and install it via odin in download mode I get a FAIL(SIZE!) message at the end. Its not an ext4 error anymore but im worried at what is going on now. I have tried searching it up on google however nothing has come up. Looks like ive completely broken it... ='(
Click to expand...
Click to collapse
You have the 9005 right? I think you have the wrong file to odin. What is the exact model number of your phone and where are you located in the world? (reason I ask is there are different regions to choose from)
agent929 said:
You have the 9005 right? I think you have the wrong file to odin. What is the exact model number of your phone and where are you located in the world? (reason I ask is there are different regions to choose from)
Click to expand...
Click to collapse
SSN: SM-N9005GSMH
S/N: RF1D96B6ELB
United Kingdom Vodafone.
Im sure I downloaded the 9005 for samsung in the uk but I wil try again from a different site that specficly says what country and code.
If not would you be able to post me a link to the exact one?
Many thanks
Thank you so much everyone for your input. I hunted out the correct EU snapdragon firmware and booted it on, emptied the cache and restored to factory settings and its finally running! Only took 2 days hehe but at least its working. Thanks again everyone
Good to hear!
apdnote said:
Thank you so much everyone for your input. I hunted out the correct EU snapdragon firmware and booted it on, emptied the cache and restored to factory settings and its finally running! Only took 2 days hehe but at least its working. Thanks again everyone
Click to expand...
Click to collapse
Your welcome, don't forget to hit the thanks button for anyone that helped you!
apdnote said:
Thank you so much everyone for your input. I hunted out the correct EU snapdragon firmware and booted it on, emptied the cache and restored to factory settings and its finally running! Only took 2 days hehe but at least its working. Thanks again everyone
Click to expand...
Click to collapse
Hi, I am using same SSN. Can you please confirm the working rom download URL? Appreciate your help.
Thank you.
Yesterday evening my phone was on the charger then it suddenly stopped and it is completely dead. It isn't showing any signs of life ever since, even if I charge it. It doesn't even show offline charging and I can't send it to Samsung as it's rooted so my warranty it VOID. It seems to me that it has Sudden Death Syndrome because it has been recently been switching off and now it's completely dead. What should I do? I'm pretty much screwed!
KoolKid98189 said:
Yesterday evening my phone was on the charger then it suddenly stopped and it is completely dead. It isn't showing any signs of life ever since, even if I charge it. It doesn't even show offline charging and I can't send it to Samsung as it's rooted so my warranty it VOID. It seems to me that it has Sudden Death Syndrome because it has been recently been switching off and now it's completely dead. What should I do? I'm pretty much screwed!
Click to expand...
Click to collapse
Can you enter download mode?
robintjeuuu said:
Can you enter download mode?
Click to expand...
Click to collapse
Well... I managed to just get it into offline charging. When I boot it up in normal mode it shows Samsung Galaxy S3 mini then after a few seconds the bottom lights flash for half a second and shut down. When I try to boot to recovery, model name then shut down. Yes it can just about make it into download mode.
KoolKid98189 said:
Well... I managed to just get it into offline charging. When I boot it up in normal mode it shows Samsung Galaxy S3 mini then after a few seconds the bottom lights flash for half a second and shut down. When I try to boot to recovery, model name then shut down. Yes it can just about make it into download mode.
Click to expand...
Click to collapse
If you get into download mode, go to sammobile en download the firmware for your phone and flash it with odin. if that worked, open stock recovery and do a fatory reset to make sure everything is back to stock... Then you can just hope it won't happen again.
robintjeuuu said:
If you get into download mode, go to sammobile en download the firmware for your phone and flash it with odin. if that worked, open stock recovery and do a fatory reset to make sure everything is back to stock... Then you can just hope it won't happen again.
Click to expand...
Click to collapse
I tried flashing stock recovery and ROM through Odin, it said pass but nothing actually seemed to fix and it still has the same problem that it shuts down after showing logo and when I boot to recovery it just shows TeamWin for a few seconds and shuts down so looks like I'm screwed and I have to use my BlackBerry :'(
KoolKid98189 said:
I tried flashing stock recovery and ROM through Odin, it said pass but nothing actually seemed to fix and it still has the same problem that it shuts down after showing logo and when I boot to recovery it just shows TeamWin for a few seconds and shuts down so looks like I'm screwed and I have to use my BlackBerry :'(
Click to expand...
Click to collapse
Ok, can't help you, maybe search this forum for unbrick device. I know there are fixes that can be used with some bricks.
robintjeuuu said:
Ok, can't help you, maybe search this forum for unbrick device. I know there are fixes that can be used with some bricks.
Click to expand...
Click to collapse
And I don't think Samsung will repair it as my warranty is void and I doubt if my parents would get me a new phone as this phone is only 3 months as well! And I have seen an unbrick thread and I tried it and it didn't work :'(
Well, I know how you feel. My charging port died once after I changed rom. Samsung asked me 200 for repair. Maybe you can give it a try and send him in... You never know Samsung loves you more than me..
Sent from my GT-I8190 using Tapatalk
robintjeuuu said:
Well, I know how you feel. My charging port died once after I changed rom. Samsung asked me 200 for repair. Maybe you can give it a try and send him in... You never know Samsung loves you more than me..
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
My dad took it to the service centre and they said they can't fix it as it's rooted so I'm screwed :'(
sunny296 said:
thanks,this index help me out very much.
Click to expand...
Click to collapse
What do you mean?
Zamoro1 said:
it is not samsung galaxy problem. it was your problem. you must close your downloading and other working while it is on charging.
Click to expand...
Click to collapse
It wasn't downloading anything?
Don't worry everyone I sent it to a repair shop (not Samsung) so I hope they manage to fix it.
Mine also dead
KoolKid98189 said:
Don't worry everyone I sent it to a repair shop (not Samsung) so I hope they manage to fix it.
Click to expand...
Click to collapse
Have you any news about the problem in your phone?
Mine (i8190 with one of the mclaws roms from previous week) also appeared in the morning shut down and there's no way of starting it. It does not even vibrate when power button pressed, as if the battery was completely empty.
Tried with another battery and checked that the original one had charge, but no luck. It does not start (normal, download or recovery, makes no difference).
Any ideas?
PelosBi said:
Have you any news about the problem in your phone?
Mine (i8190 with one of the mclaws roms from previous week) also appeared in the morning shut down and there's no way of starting it. It does not even vibrate when power button pressed, as if the battery was completely empty.
Tried with another battery and checked that the original one had charge, but no luck. It does not start (normal, download or recovery, makes no difference).
Any ideas?
Click to expand...
Click to collapse
Well mine was dead for a day then I plugged it into the charger (this was after a day and I left it on charge all night and it wouldn't start) and I held the power button for 10 seconds while it was on the charger it showed offline charging so I let it charge for a bit and then I powered it on and it seemed to be bricked so I sent it to a phone repair shop (not Samsung as my warranty is void). If it doesn't show any signs of life then it's bricked. If it comes to life then it is also probably bricked. I tried flashing many recoveries, ROMs, kernels and params and nothing happened.
In the S III Mini General forum there are topics about getting your phone back to stock so that it is covered by warranty.
james.faction said:
In the S III Mini General forum there are topics about getting your phone back to stock so that it is covered by warranty.
Click to expand...
Click to collapse
I tried to flash stock ROM and recovery but nothing actually worked!
1. Did you follow the instructions in detail?
2. What does "nothing actually worked!!" mean??
Maybe you need to work out what is the problem and why it is failing. Then you will be able to figure out if it is actually fixable, and if so how to fix it. "Trying everything" doesn't really work unless you make an effort to analyse the results you get every time you try something.
You could try posting in one of the threads about taking the phone back to stock. The people who posted them might be able to help you, they are more experienced at this sort of thing.
james.faction said:
1. Did you follow the instructions in detail?
2. What does "nothing actually worked!!" mean??
Maybe you need to work out what is the problem and why it is failing. Then you will be able to figure out if it is actually fixable, and if so how to fix it. "Trying everything" doesn't really work unless you make an effort to analyse the results you get every time you try something.
You could try posting in one of the threads about taking the phone back to stock. The people who posted them might be able to help you, they are more experienced at this sort of thing.
Click to expand...
Click to collapse
I tried those solutions and they didn't work.
Kid, can you read?
What did you try? What was the result?
"didn't work" isn't a result, it's you giving up. Without even trying to find out why it didn't work.
james.faction said:
Kid, can you read?
What did you try? What was the result?
"didn't work" isn't a result, it's you giving up. Without even trying to find out why it didn't work.
Click to expand...
Click to collapse
I read all instructions, and when I flashed it via Odin, nothing actually changed even with the params!