Hey,
I wanted to flash the new stock I9500XWUBMG1,
I have quite a bit of experience doing it so I plugged my phone and odin wouldn't recognize it.
Tried a few things, and found out that it was recognized while not using download mode (but just having the phone on).
So I connected it to odin while it was on and then turned it off and put it to download mode, at this point the phone was recognized but appeared twice (the COM of the turned on phone and the one of the download mode).
I proceeded to try and flash it, and got an error quite qucikly.
After that error I can still get into download mode but no recovery or anything.
Tried flashing stock ROM again with/without PIT file, tried flashing CWM recovery with/without PIT file.
Right now I'm basically lost with nothing to do.
Is there a way to fix this that I haven't tried? What are the chances that hardware went bad and in need for replacement?
You could try...
Maybe it is just a soft brick that has occurred and nothing wrong with your actual phone hardware. Have you tried a different usb port? The only other thing I can think of is maybe having a look at http://forum.xda-developers.com/showthread.php?p=41072426
Using a different USB port I was able to repartition while flashing only a recovery (Philz touch),
Still I'm getting errors trying to flash the entire ROM.
I am now thinking of trying to flash a custom ROM (wanamlite) from the recovery mode.
What do you guys think?
EDIT: That did it, running on wanamlite.
Related
Hello guys i was trying out the new Kangabean 4.3. ROM for my AT&T and after flashing it in TWRP it appears I has softbricked my device. I can only boot into download (odin) mode and it stays on "downloading now".. Anyhow i cannot boot into recovery it just vibrates to confirm my input and just revibrates and revibrates... Looked all over for guides and tried to return it to factory settings on Kies but it does not detect my phone... Any help would be great i need this phone for work everyday!!!
Karbooo said:
Hello guys i was trying out the new Kangabean 4.3. ROM for my AT&T and after flashing it in TWRP it appears I has softbricked my device. I can only boot into download (odin) mode and it stays on "downloading now".. Anyhow i cannot boot into recovery it just vibrates to confirm my input and just revibrates and revibrates... Looked all over for guides and tried to return it to factory settings on Kies but it does not detect my phone... Any help would be great i need this phone for work everyday!!!
Click to expand...
Click to collapse
Please search for similar threads. This same issue is being posted over and over and over again. When you were making this post, what "similar threads" or "similar topics" showed up? Did you check them for a solution?
yes sorry i looked at all of them and they all involved well just flashing the stock rom but i cant get my computer to see my gs4 on download mode...i got the drivers and odin installed.
Well, this thread has a couple of ideas...
http://forum.xda-developers.com/showthread.php?t=2405991
or maybe here...
http://forum.xda-developers.com/showthread.php?t=2405127
You might also want to look at the TWRP thread in the development section.
Try again to get into recovery, the key sequence can be tricky, make sure you are doing it just right. "Doing it just right" has been discussed many times.
Also, look at this thread, maybe it will help...
http://forum.xda-developers.com/showthread.php?t=2398336
Yea, I realize that thread is about MF3, but it still has ideas that might help you.
There are also a ton of threads about how to get your PC to recognize ODIN.....search.......good luck.
yeah ive been at it for hours man those links can all access the recovery i cant... i tried everything got the drivers up tried all the odins and its just stuck on "downloading do not turn off target" and my pc doesnt see it...
Odin finally recognized it on the pc in download mode and i was able to flash the stock rom but it seems it wasnts successful...it still just vibrates and vibrates when i press the power...
Try flashing the open recovery.
Sent from a jedi extacy note II
If you mean the CWM recovery I tried it on Odin and it failed.... :""(
Sent from my Nexus 7 using xda premium
Take battery out, back in, power+volumedown, download mode, Install Samsung Kies, do Kies update, connect to PC, Tools-> firmware initialization, take battery out and type model/serial Number, wait patiently until it finishes.
Try different USB port or different PC. Use stock USB cable comes with original box.
If Kies screen get stuck at model number section, you did flash MF3 triangle thingy -> unsolveable brick. Have to go thorugh warranty replacement.
Sent from my SGH-I337 using Tapatalk 4
the Kies Emergency firmware utility worked it put my phone like the day i bought it...also rooted it successfully and installed TWRP on it thanks guys
Dear all,
I have only recently lost my IMEI und tried everything to recover it. As a matter of fact I had made a backup before and tried to restore it and it didn't work. Today, I tried doing that another time and after that I wanted to reboot my phone but after it shut down it just doesn't boot up anymore. It shows nothing, only the black screen. It seems like it doesn't react to anything, I also tried to pull the battery but that also wasn't successful. I also can't get into Download Mode.
Any ideas what I could do?
Charge the battery or try another battery first .
I did both, I charged the battery but it didn't help and I also tried another (fully charged) battery, without success.
try to connect with kies 3
Kies doesn't recognize my phone.
Service centre repair your next step .
I'll let my carrier send it to Samsung and tell them that it crashed after trying to update to Lollipop via Kies, I read that this worked in some cases. If it doesn't I'll have to have it repaired.
What do you guys think about those "USB jigs"? Do you think those could help me with my problem?
YAAAAY!
Thanks to this thread http://forum.xda-developers.com/showthread.php?t=2625332 I was able to unbrick my device and by flashing a new PIT-File and a Stock ROM even my IMEI came back. I think my partition was somehow messed up because after flashing the PIT-File it began to work properly, but I flashed the Stock ROM to have a "clean" system again and installed Cyanogenmod afterwards with success.
So how does this fix work if the phone is unable to connect or power on ..
OP yes try the usb recovery jig to see if it boots to download mode .
Well, it did help. After I had put the Image on my SDcard and removed my SIM card I was able to boot my phone, this was the main issue. The rest was child's play, I flashed the PIT-file and a stock ROM and everything was working fine again.
flash new PIT file
hi you got to flash a new pit flie. maybe something damaged your phone boot. look in here
http://forum.xda-developers.com/showthread.php?t=2625332
Hi!
I have a Samsung Galaxy S4 i9505, which is not booting anymore after I tried to change the sim card tray. It gets stuck on the Samsung logo at boot. Recovery won't boot either. (says recovery booting but does not boot) I can only get it to download mode. I tried reflashing recovery with heimdall. Is there any way to recover data or fix the phone? I know it could be a hardware fault that's practically impossible to fix. Strange symptoms for a hardware fault though. Just looking for any ideas. It would be nice to at least dump data from it or get recovery booting.
Thank you for your help!
Try a different bootloader.
Or flash another rom with Odin.
GDReaper said:
Try a different bootloader.
Or flash another rom with Odin.
Click to expand...
Click to collapse
Where can I find a bootloader to install? I tried googling a bit but couldn't find a clear answer. Do the modem files also have the bootloader, should I flash a new modem file?
Modem and bootloader are different files.
You can find modems and bootloaders this thread. You may have to scroll through the comments to find what you're looking for.
GDReaper said:
Modem and bootloader are different files.
You can find modems and bootloaders this thread. You may have to scroll through the comments to find what you're looking for.
Click to expand...
Click to collapse
Tried flashing a new bootloader. Now I get a message that "Recovery is not seandroid enforcing" It still does not boot into TWRP recovery. I tried flashing another version of TWRP, but no difference.
Try this:
Open Odin, uncheck everything except f.reset time, flash TWRP, when you see the word "reset" in the status window, remove USB cable, remove battery, wait 5 seconds, replace battery, use button combination to boot into recovery. When the phone starts to boot, release the power button but keep holding the volume up and home.
audit13 said:
Try this:
Open Odin, uncheck everything except f.reset time, flash TWRP, when you see the word "reset" in the status window, remove USB cable, remove battery, wait 5 seconds, replace battery, use button combination to boot into recovery. When the phone starts to boot, release the power button but keep holding the volume up and home.
Click to expand...
Click to collapse
Which version of odin would you suggest me to use? I tried with 1.85 and that didn't help. I'm starting to think that this might be a hardware fault, perhaps I broke something when tearing off the old sim card tray. Or the new part was faulty and somehow fried my phone. I have a backup from about a month ago. It was stupid not to take a backup before attempting to replace the sim card tray, but I tought it wouldn't be so dangerous.
Its not hardware problem. Hoy have a bootloop and Thats software problem. If you had stock recovery then the cause of bootloop also broken your recovery mode.
You will have to flash a full stock rom (Sam mobile web has them) or search here on xda.
A full stock rom has updated bootloader and módem, also stock recovery built in.
BraianV said:
Its not hardware problem. Hoy have a bootloop and Thats software problem. If you had stock recovery then the cause of bootloop also broken your recovery mode.
You will have to flash a full stock rom (Sam mobile web has them) or search here on xda.
A full stock rom has updated bootloader and módem, also stock recovery built in.
Click to expand...
Click to collapse
That also means losing all my data if I can't boot recovery beforehand. But perhaps I have to try that.
If you had usb debugging enabled you might be able to pull the data from the phone.
Odin 1.85 seems really old. I mean really old. You should use Odin 3.x. I had success with Odin 3.09 in the past.
GDReaper said:
If you had usb debugging enabled you might be able to pull the data from the phone.
Odin 1.85 seems really old. I mean really old. You should use Odin 3.x. I had success with Odin 3.09 in the past.
Click to expand...
Click to collapse
Would it be enough if I flashed just stock recovery+modem+bootloader or something like that? I had usb debugging enabled, but since I cant get the system to boot at all it's of no use.
Can I use adb in stock recovery? I think the stock rom won't boot with my current data still on the device. I had cyanogenmod 12.1 installed. Haven't had stock rom in ages.
Ilumod said:
Which version of odin would you suggest me to use? I tried with 1.85 and that didn't help. I'm starting to think that this might be a hardware fault, perhaps I broke something when tearing off the old sim card tray. Or the new part was faulty and somehow fried my phone. I have a backup from about a month ago. It was stupid not to take a backup before attempting to replace the sim card tray, but I tought it wouldn't be so dangerous.
Click to expand...
Click to collapse
I prefer Odin 3.07 for all of my flashing needs. I have used it on a note 2, note 3, s4, s3, and s2.
If the flash fails, try different USB cables and different USB ports.
Hello!I need urgent help.I tried to install TWRP on my friend's phone using an app called Rashr.After it is installed it says that I need to reboot my device.So I did that.After rebooting it went straight to Download mode.It just stuck there.I have tried everything,from using odin (It won't detect my friend's phone),to using ADB (It also won't detect my friend's).I really has to fix his phone ASAP.Thanks!
(Note #1: Sorry for my terrible English )
(Note #2:I have used ADB before to fix my phone (Core Prime) when it was stuck in bootloop)
There's no way to get it working without Odin.
So try everything you can find online to make the PC detect the phone.
After that you should try flashing a bootloader (the same one that's already on the phone if possible). I'm almost certain that it will make the phone boot.
And then you can also proceed to flash the recovery with Odin.
And maybe this a silly question, but did you install the Samsung USB drivers?
Download the latest stock ROM from sammobile. Use the original Samsung USB cable and a USB 2.0 to flash the phone.
I like using Odin 3.07 as it has always been very stable for me: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNEdxqAS5QWImOPDJboTA_V3D5S9eA
Stock gt-i9500 firmware here: https://www.sammobile.com/firmwares/database/GT-I9500/
Get USB phone drivers from here: https://www.xda-developers.com/where-to-download-android-usb-drivers/
Hello! all. Im really nervous. THis never happened before, i dont know what to do. I was using an Custom Rom Miui Eu. And i decided today to went back to the official one for good. And when i was flashing the firmware in Miflash, the phone never reboot and MiFlash showed as "Flash Complete" in green color, so i removed the usb and the went all black and there is no way tu turn on the picture, i cant go to bootloader or fastboot. When i connect the phone to the PC. My PC recognize the phone as Qualcom 9008. But i cant flash and do anything. What can i do? i tried replacing the auth .elf file but im still having the error in MiFlash. The only way to fix this brick is doing that "test point" thing ?
First download the latest firmware and the correct one (global, chinese or whatever you had) for your device because you can only install higher version firmware using flash tool.
It seems your phone already is in EDL mode, hence there is no need for test point method.
Try another usb port. Try using a different PC. Change the location of the firmware folder to a shorter path like C:\ and try to reboot the phone a few times and then try.