Hi,
Unfortunatelly I started playing with my I9000 without reading enough and bricked my phone completely (?). If anyone can help please do so.
Description:
1. I tried to flash with Odin new firmware but after flasing and rebooting got message "unable to update media ...." (or something like that) When powering on I got only welcoem screen with phone name
2. I wanted to repeat flashing but Odin could not start reflashing (I still could go into Download mode)
3. I found at xda forum [STOCK ROM] Odin3 One-Click Downloader,
but I didn't notice that it was for Captivate (I thought it is just another name for I9000,now I don't know why)
4. I reflashed my i9000 and after reflashing got only At&t screen turning on and off, without possibility to enter into download mode.
Actually I'm stuck with this situation I feel really stupid, but by mistake I did what I did.
Is there any chance to help ?
Thanx in advance.
according to some users, you might get lucky, and might be able to recover
let your phone stay on on that loop, wait until it turns itself off
then try the 3 button combo again
if all else fail, contact samsung tech support, which will simply send you back to your cell phone place
I'll try but I'm not very optimistic
Waiting doesn't help - I tiried all possible 3 or 2 button configurations unsuccesfully.
Anyone has any other idea if antyhing can be done with the issue ?
The exact same thing happened to me. There is nothing you can do except to bring it back to Samsung. I brought mine back and they have to replace the whole motherboard
what did you tell them? is it going to cost you?
diehard2222 said:
what did you tell them? is it going to cost you?
Click to expand...
Click to collapse
I told them my phone cannot boot. Can they help to reflash the FW and see if it helps. They did and said phone still cannot boot after reflashing. Hence they have to change the motherboard. I asked and they say it's under warranty...
The shop where I had bought my I9000 sent it to Samsung - I will see what they do with it.
I have flashed a vibrant with a i9000S software but the radio did not work quite well. Since the two have different keys, now i cant get it to boot mode. i was able to get into recovery mode via ADB but all i can do is use vol to go up or down and not select an option. the device wont even get out of recovery mode.
Any help will be greatly appreciated.
Same
I did the exact same thing and couldnt get it to go past the AT&T logo i took mine to the samsung authorised repair centre and after 3 days and 49 dollars they fixed it. I dont know how they did it because i couldnt get USB to reconginise or download mode or anything just stuck on white screen but they managed to get it up and running.
So even though it cost 49 dollars to fix it via software method it is better then spending 800 on a new phone or 300 for a new chip which they originaly qouted me. So there is hope with proffessional services
now, the magic usb plug is avaliable in ebay, it can turn your bricked phone into download mode in a few seconds. really good!!!
Hehe... ...the magic is one usb connector an 301 kohm resistor
Br:25011
h***://factoidz.com/how-to-unbrick-your-samsung-vibrant-galaxy-s/
So for awhile I used a droid as my main phone and I flashed countless different roms on it. One day though it just went kaput on me, the led flash started flashing on and off whenever I tried to reboot it and I could not access anything including recovery or boot loader. Eventually the battery died and it would not charge again.
I recently was messing around with it and was able to revive it, would not boot up still but was able to get in the boot loader and eventually sbf it. The battery still wont charge(normally) which tells me at least one issue still exists with hardware. Other than that the phone works fine now on android 2.0. The problem is that I cannot upgrade it to anything higher than that.
The only .sbf I could get to both load and boot up successfully was esd20 anything else would just boot loop indefinitely, after rooting that and trying to go from there anything else also boot looped. I installed every recovery I know of from clockwork to spr to that rzr mod of it but none could flash without the same results(restoring a nandroid of that esd20 still worked though). I've tried different kernels as well to no avail. The first steps I did were an exact procedure that I had done before on the same phone successfully with a 2.2 sbf but now it just wont work.
I don't know if there could be some hardware issue causing these problems though I cannot fathom how when one firmware still works and would appreciate any insight that anyone has as to what may be the problem. Was planning on giving the phone to a young family member to play games on as soon as I managed to boot it back up but I don't want to deal with the compatibility issues with such an old version of android.
Hi......so unlocked bootloader and rooted phone according to here - theunlockr.com/2013/03/16/how-to-root-the-motorola-razr-i/[/url]
All great but had been getting problems with the phone not recieving txts.........virgin are sending out a replacment but taking the old one back now obviously this does not bode well for me as it is rooted, especially with that riduculous warning screen motorola have incorparated..........tried using the stock.img flashboot work around to get rid of that at least, but just end up soft bricking the phone and it stays in flash mode(non signed img)...........managed to reflash it and use recover to restore phone settings but im still stuck with that problem........if i could at least just get rid of that stupid warning message on reboots i would be happy to give it back as these phones probably just get sent to a factory to be refurbed and re flashed anyway, but i feel the message just makes it far too glaringly obvious!!(the point of it i suppose)
I've seen the thread on reflashing with stock roms using rsd lite on this site but also seen it has a high chance of hard bricking the phone.
SO!!
My question(s)is........is there actually a way of getting rid of just the logo and does it def work?
Should I try and unroot the phone using the rsd lite method?
Do you think it will matter if I hard brick the phone when I give it back or could this actually be a good thing to do and just plead ignorance if Im asked and just say it suddenly died on me, therefore covering my tracks.
Does it really matter anyway since they are already sending me a new phone out?
And would I be right in assuming that this phone isn't as straightforward for rooting/unrooting as other phones out there are?
My system version is 91.2.26001.XT890.Retail.en.EU
My Kernel version is 3.0.34 [email protected]#1
Android 4.1.2
Thanks for reading if your still with me and not nodded off!!And yes I have already scoured the net and threads for answers and even phoned my mother to find out why I'm special!!
I'm not sure if this will work but you can try downgrade to ics with mattlgroff's homemade fastboots and then try to flash locked logo but this won't probably help you if JB was installed through OTA as its bootloader replaces unlocked logo back
(While I was in a rooted DOK2 FW - Tmobile SM-910T3)
So heres the deal, trying to walk around I wanted to mock my location but was interrupted and placed my phone in my pocket which "locked" the bootload.
I managed to flash the stock image and unlocked the bootloader loaded TWRP and restored from my backup
Now this is where hell starts. It looked fine until I rebooted my phone.
Symptoms:
On a reboot the phone will not turn back on after I opt to reboot my phone
At this time the phone will not turn back on (i noticed this when i rebooted while plugged in the charging light was not on) I pull the battery for a few minutes to turn it back on
When I power the device back on sometimes it is stuck in the Bootloader Screen (unable to get into recovery and download) so I need to pull battery wait and turn back on
When the device does boot I can get into recovery and download mode on when it boots properly
Sometimes its stuck on the tmobile screen and I need to reboot it.
When the phone is operational it will occasionally lock up and I will need to wait a few minutes before the device is able to respond.
Any ideas what I can do? I had thought flashing a stock rom (from sammobile) would fix the boot issues
As of now:
I've recently flashed to the new Tmobile marshmallow stock via odin. I am still seeing these symptons. I'm currently installing the Maximum Overdrive Rom hoping it will fix some issues
Still seeing some of the same issues. Stock romantic and a deflated romantic did nothing. Is there a way to reflash a bootloader?
I'm having the same issues....I have odined back to stock dok2 twice....I think the pe3 bootloader files are floating around the forums somewhere...http://forum.xda-developers.com/showpost.php?p=67514260&postcount=4
When my N4 boots up I occasionally get the emmc boot error...I brought it to tmobile and explained the issue to the rep. She brushed it off as being my battery. I know its not my battery as its a 3 month old 10000mah zerolemon. So I'm going to just limp this phone along until its time to jump to the Note 7. I've been flashing roms since the golden era of windows mobile/palm os days and on android since my G1...And some rookie rep who doesn't even know how to put a phone in recovery or download mode tries to brush it off as the battery.... My girl has the sprint note 4 and hers did the same thing, she took it to a store the rep ended up giving her a fully functional refurb... (which is the right thing to do if the phone has emmc failures) Anyways I hope you have better luck than I've had
i had the exact same issue as you guys started 2 months ago got worse overtime now my emmc is dead it wont write anything or even go into recovery or download i had tried all types of roms stock firmwares even took the phone apart swapped the power button and bought a new battery now my memory is dead and i can actually say its the emmc chip, seems to me these note 4s are starting to die i bought mine when it first came out in 2014 kind of feel ripped off but best phone i ever had imo
So ive just recieved an s3 8190 mini not an n or l model labled as sapres repairs, i have some experiecne flashing phones including a s3 mini-n so thought i'd grab this one to fix it and sell on...boy was i wrong
many hours later of various flash attmepts and reading troublshooting methods on the problems this phone does little else but restart a lot!
it wont accept anything ive flashed, i cant boot into recovery or root it sucessfully, however it will boot into download mode (a ray of hope perhaps?) after flashing various recoveries and trying to boot into it the bottom leds flash and it restarts again and it just wants to boot up normally no matter what, ive tried the 3 buttons then releasing only the power after i see the logo as ireads that worked for a few
the phone requires a pin to be entered at start which was in the box on a piece of paper, once in the time i get varies before it resets again and any settings i changed are restored things like wifi mode etc are all back...wtf is this? also apps cant be uninstalled!! and more importanly i cant factory reset, i press the first few buttons and then the final one does nothing....there is a missed call dated last year some time that shows up in the notifications area...
im currently flashing official firmware via link on this site that matches the baseband so hoping that might do something, but that seems like bind mans hope in hell, ive tried a few things from this site like a flash that makes the 3 buttons "work" which it did for some, thought not done anyhting with adb/fastboot being new to it, the phone wasnt recognised the few times i tried it.
where now then just what is wrong wiht this phone and can i get it up & running?