Hello,
My gf s4 mini is having some strange problems.
First it suddenly shutted down and doesn't give any signs of live, so I maked debrick sdcard and it booted, showing that there is something wrong with mmc.
Tried to flash with odin, but it failed... so left it for some time. When i tried another time it booted and showed s4 mini boot logo, so i wanted to flash it with stock firmware.
Progress bar is moving to end, Odin display: PASS! and then it is rebooting and not booting.
I tried booting recovery, and it shows twrp and rebooting about 5sec after showing twrp logo.
So i repeated this process and it still shows twrp logo...
I haven't seen something like this, so there is my question:
Is there something I can do, cause i read lots of threads and nothing works?
I guess it is dead mmc chip, but maybe i'm wrong and there is some solution.
Thanks in advance!
refresh
Maybe you can try jtag. But if your phone's warranty still continues, I recommend you give it Samsung service
Sorry for my bad English
Sent from my GT-I9190 using Tapatalk
Related
Hi all,
I'm on Rogers GS3 (i747m)
I've searched and searched. I cannot find a fix to my problem.
Last night I downloaded the AOKP 10.16 update and was trying to flash it above my 10.03.
It gave me an error while flashing, but then the phone would boot and stay stuck at the glowing samsung logo.
I downloaded the stock rogers rom and tried to flash it using oding. Same thing would happen, glowing samsung logo.
I was finally able to flash a recovery image but now it won't recognize my internal sd and keeps telling me that there was an error mounting external sd. I can't format /data because of that.
When I try to flash another recovery through Odin 3.07, it keeps telling me "Odin downloader has stopper working." With Odin 1.85, it says "Odin communicator has stopped working."
I'm about to give up. Will keep searching. But I'm losing hope at this point.
have you tried this http://forum.xda-developers.com/showthread.php?t=1828152
http://forum.xda-developers.com/showthread.php?p=28175077
Try this toolkit. It may help you. You can also try to flash twrp recovery. And do you have a nandroid backup?
Sent from my SGH-I747 using xda app-developers app
any solution
hello, has anyone found a solution to this "odin has stopped working"? i have a gnex that has bad "volume down" and "power" buttons. so if my phone dies i usually charge it and then flash a recovery via odin to boot it back up without having to redo my whole phone. now everytime i try to use any version odin, the program crashes. i've seen a lot of people with this issue lately but since i do not have working buttons, odin is the only way i can boot my phone. please help ps. i know i don not have a s3 but i am going through the same issue and i need the odin to work so i can fix a s3 as well.
tswtech2 said:
hello, has anyone found a solution to this "odin has stopped working"? i have a gnex that has bad "volume down" and "power" buttons. so if my phone dies i usually charge it and then flash a recovery via odin to boot it back up without having to redo my whole phone. now everytime i try to use any version odin, the program crashes. i've seen a lot of people with this issue lately but since i do not have working buttons, odin is the only way i can boot my phone. please help ps. i know i don not have a s3 but i am going through the same issue and i need the odin to work so i can fix a s3 as well.
Click to expand...
Click to collapse
that used to happen to me what version are you on?? ill give you the attachment that worked for me
2oublethink said:
Hi all,
I'm on Rogers GS3 (i747m)
I've searched and searched. I cannot find a fix to my problem.
Last night I downloaded the AOKP 10.16 update and was trying to flash it above my 10.03.
It gave me an error while flashing, but then the phone would boot and stay stuck at the glowing samsung logo.
I downloaded the stock rogers rom and tried to flash it using oding. Same thing would happen, glowing samsung logo.
I was finally able to flash a recovery image but now it won't recognize my internal sd and keeps telling me that there was an error mounting external sd. I can't format /data because of that.
When I try to flash another recovery through Odin 3.07, it keeps telling me "Odin downloader has stopper working." With Odin 1.85, it says "Odin communicator has stopped working."
I'm about to give up. Will keep searching. But I'm losing hope at this point.
Click to expand...
Click to collapse
You arent hard bricked dont give up YOUR PHONE IS STILL ALIVE xD
This will keep all your data!
Unbrick:http://www.youtube.com/watch?v=ypmqJbZqOaU&feature=relmfu
Obviously you'd want to root again (;
Root:http://www.youtube.com/watch?v=XoEVDgjTTdg&feature=plcp
2oublethink said:
Hi all,
I'm on Rogers GS3 (i747m)
I've searched and searched. I cannot find a fix to my problem.
Last night I downloaded the AOKP 10.16 update and was trying to flash it above my 10.03.
It gave me an error while flashing, but then the phone would boot and stay stuck at the glowing samsung logo.
I downloaded the stock rogers rom and tried to flash it using oding. Same thing would happen, glowing samsung logo.
I was finally able to flash a recovery image but now it won't recognize my internal sd and keeps telling me that there was an error mounting external sd. I can't format /data because of that.
When I try to flash another recovery through Odin 3.07, it keeps telling me "Odin downloader has stopper working." With Odin 1.85, it says "Odin communicator has stopped working."
I'm about to give up. Will keep searching. But I'm losing hope at this point.
Click to expand...
Click to collapse
Whenever I get stuck at the Samsung logo boot animation, I reboot into recovery, factory reset, reboot into download mode and flash again with Odin. Works every time.
resrevni said:
Whenever I get stuck at the Samsung logo boot animation, I reboot into recovery, factory reset, reboot into download mode and flash again with Odin. Works every time.
Click to expand...
Click to collapse
The thing is he doesnt have to lose all his data
amzi said:
The thing is he doesnt have to lose all his data
Click to expand...
Click to collapse
i was using version 3.07 from the toolkit. yes , i was trying not to lose my data. after trying all night, i was able to load a stock image and bring my phone back. all data was lost but at least my phone is working. i guess i just need to stop being cheap and get another phone but, we all know the outrages prices guys charge for phones on craigslist. does anyone know if the gnex is available through google still?
I've been having a problem with an S4 Mini recently. A few weeks ago, it stopped booting whatsoever. I tried the "debrick.img" method but it only said that there was an error flashing to the eMMC. At that point in time, I was assuming it had a dead eMMC and I had to buy a new motherboard. I brung it out again a few hours ago and it booted, except it is stuck in a bootloop. If I try to enter recovery mode, it says "BOOTING RECOVERY MODE..." in the top left corner, then says "No command.". After a few seconds it then reboots.
I have attempted using Odin to flash TWRP but the same error occurs with the device, like it wasn't even flashed with TWRP. I did also try to flash a stock ROM, but to no avail. It's just stuck in this boot loop.
The Odin logs say that the flash was successful, so I don't see how it could be failing. Right now, it is sitting right next to me, vibrating, showing the manufacturers screen and then rebooting. All I can assume at this point is the eMMC is dead, and I should buy a new motherboard.
If there is any fix to it, I would really appreciate you could tell me so I can attempt to get it working again.
UPDATE: I just attempted to take the battery out to try and reflash the Stock ROM but now, it's showing the QHSUSB_DLOAD driver. This happened the last time and a friend told me that this is a dead eMMC and the device is basically now a brick. Hopefully this is just temporary and the device decides to be nice and function again. Fingers crossed!
UPDATE 2: I was doing some research and something appeared in Device Manager called "Qualcomm HS-USB QDLoader 9008 (COM5)". I googled the driver and apparently it is a sign of a bricked Qualcomm Snapdragon. I'm going to try the unbricking steps and hope that this is the problem, and I don't need to buy a new mainboard.
I can only say good luck man, hope you fix it without changing motherboard.
Funey__ said:
I've been having a problem with an S4 Mini recently. A few weeks ago, it stopped booting whatsoever. I tried the "debrick.img" method but it only said that there was an error flashing to the eMMC. At that point in time, I was assuming it had a dead eMMC and I had to buy a new motherboard. I brung it out again a few hours ago and it booted, except it is stuck in a bootloop. If I try to enter recovery mode, it says "BOOTING RECOVERY MODE..." in the top left corner, then says "No command.". After a few seconds it then reboots.
I have attempted using Odin to flash TWRP but the same error occurs with the device, like it wasn't even flashed with TWRP. I did also try to flash a stock ROM, but to no avail. It's just stuck in this boot loop.
The Odin logs say that the flash was successful, so I don't see how it could be failing. Right now, it is sitting right next to me, vibrating, showing the manufacturers screen and then rebooting. All I can assume at this point is the eMMC is dead, and I should buy a new motherboard.
If there is any fix to it, I would really appreciate you could tell me so I can attempt to get it working again.
UPDATE: I just attempted to take the battery out to try and reflash the Stock ROM but now, it's showing the QHSUSB_DLOAD driver. This happened the last time and a friend told me that this is a dead eMMC and the device is basically now a brick. Hopefully this is just temporary and the device decides to be nice and function again. Fingers crossed!
UPDATE 2: I was doing some research and something appeared in Device Manager called "Qualcomm HS-USB QDLoader 9008 (COM5)". I googled the driver and apparently it is a sign of a bricked Qualcomm Snapdragon. I'm going to try the unbricking steps and hope that this is the problem, and I don't need to buy a new mainboard.
Click to expand...
Click to collapse
Did you solve it? I'm having the same problem
Symptoms: Over a period of weeks, possibly months, the phone started rebooting itself more and more frequently. Now I have reached the point where my phone bootloops, often at the Note II logo, sometimes it goes on and gets stuck on the ROM's logo for ages then bootloops again. Occasionally after an age (hours) and if I am lucky the ROM may load up but then it soon starts bootlooping again. I also noticed that one time there was some graphical distortion on the ROM's animated logo. TWRP Recovery and Download Mode both work perfectly fine.
What I have done Wiped everything, reinstalled the ROM through recovery which achieved nothing. I then tried a fresh install of the stock ROM with ODIN (update bootloader ticked). Although the ODIN install went fine, I still have exactly the same problem.
What should be my next step? Repartion with PIT?
Well I went ahead and re-partitioned with a PIT file, still no luck. I guess this must be a hardware issue.
makeyourself said:
Well I went ahead and re-partitioned with a PIT file, still no luck. I guess this must be a hardware issue.
Click to expand...
Click to collapse
You have what is known as Sudden Death Syndrome (SDS). In short the eMMC chip has failed. It or the motherboard needs to be replaced.
Flashing PIT will not help
Sorry about that
Check battery , update phone software .go to a repair centre , u may fry it like me .
Sent from my GT-N7100 using XDA-Developers mobile app
Hello! this is my first thread on this forum, which im making because I ran out of options, and don't know what to do...
It looked like my Galaxy S4 mini (GT-I9190) died last weekend (april 29) I was watching a video on youtube and suddendly it ''ran out of memory'' (the screen froze) and it turned completely black, the audio was still playing and I decided to force it to shut down (holding the power buttom)
The audio stopped, and I tried to boot it back but it wouldn't answer at all, so I removed the battery, put it back on, still nothing after many attempts (also trying download mode and recovery mode, none of them worked).
So I decided to plug it into the computer, and that's how I found it wasn't ''completely dead''
My computer detected the device as ''QHSUSB_DLOAD'' which was a good sign, meaning I wouldn't have to put my s4 mini to sleep forever.
So after some research, coming across people using 300 kohm resistors to force a bricked phone to dl mode, people using weird hardwares, Jtags and whatnot (all of these methods involved extra hardware) I found this:
http://forum.xda-developers.com/showthread.php?t=2625628 and this http://forum.xda-developers.com/showthread.php?t=2660566
The .img in the scard method, links up there.
So I gave it a try and guess what, it actually worked, my phone actually responded after placing back the sdcard and the battery, I didn't even had to press the power buttom.
My phone booted, but displaying this screen:
Boot recovery mode
Check boot partitions
Copy from T-Flash
Boot recovery. .
Write 139008 sectors. .
Flash write failure
Ddi : mmc_read dailed
ODIN MODE
Product name: GT-I9190
Current binary: Samsung official
System Status: Custom
Knox kernel lock: 0x0
Know warranty void: 0x1
csb-config-lsb: 0x30
Bootloader Rp swrev: 2
Write protection: Enabled
Click to expand...
Click to collapse
after this point, It wouldn't go further
I tried download mode at least 10 times, I't didn't work, the phone booted back to that screen again.
So I switched the vol- for vol+ to see what happen (I was doing download mode: power vol- and home)
And It worked, my phone went to the ''Galaxy S4 mini GT-I9190'' Screen, the first screen you see when it actually boots.
but after this point, It bootlooped turning off and back on to this screen and so.
when the phone turned off, I tried download mode once again and IT FINALLY WORKED.
At this point I believed that everything was over, I would connect it into odin a flash a stock firmware.
But it just started... (here comes the interesting part)
I tried to flash a stock firmware with odin, yeah, the blue progress bar and everything, my phone rebooted, but nothing, the same bootloop again. Here comes an important question: Do I need to flash a specific region firmware? or any region should work? First, I flashed an argentina region firmware (ARO was the code), results: Bootloop
After that, I tried the Russian firmware (I dont know if the region of my phone is Rusia, but I believe so because after doing a factory reset, the default language was russian, please answer this as well) and BOOTLOOP again...
So basically, The main problem is a bootloop, but I dont know what is causing this
After this point, I'm stuck, and not knowing what to try...
I'm looking for answers, what should I do? what can I try?
If you can answer any of these questions please do it...
Do I need a specific region firmware? (I already tried argentina(ARO), and Rusia (SR)) oh yeah, I tried Rusia SR, should I try XE? XE seems to be a multi-region format (?) I don't have a clue actually... I really need the opinion of someone who knows about this
If the default language when doing a factory reset is russian, this means my phone's region is Rusia?
Is there a way to know the region of my phone, when hard bricked? I dont have the box, manuals, nothing...
What was that weird screen my phoned displayed after booting with the .img sdcard? (read the quotes higher in this post)
Is there a posibility that the bootloader is corrupted, and is causing the bootloop?
I want to try everything before a JTAG service, what are these hardwares? What do they do?
Oh here is an important question:
I read that the baseband of unbrick.img has to match the baseband of my phone... is this completely true? if so, what can I do? where can I get a specific baseband .img file, and what can I do since I already used another .img (I dont know if the baseband was the same) and im already stuck on a bootloop? If a use a correct baseband .img file will the phone stop the bootloop?
Im looking forward to see your posts...
If you need any aditional information feel free to ask...
If you don't have a clue, just like me, please send this thread link to someone who could help...
Thanks in advance!
EDIT: Also recovery mode NOT working, when trying to enter this mode, the galaxy s4 mini gti9190 screen displays ''entering recovery mode'' on the upper left screen, and after that it turns off and the bootloop continues
Still with the same problem and i cannot flash any Recovery like CWM or TWRP, cuz it does Pit File partition table error
Try a NAND-Erase, I dont suggest it but it could fix your problem. Goodluck
Hi,
I have Galaxy S4 Mini VE GT-i9195i. The phone was a bit laggy, so I decided to factory reset. When I did it, the phone didn't booted. It was showing Odin download screen with red text "Could not do normal boot, odin mode" (or something like that). In thread [index] Galaxy S4 mini i9195i were some recoveries, so I used odin to recovery it. Now, when booting, it shows "Kernel is not seandroid reinforcing, set warranty bit:kernel" and when it boots up, there is setup screen (the one which shows when you firt turn the phone on), but the phone is spamming with message boxes "<random process or app> stopped working", so I can't do anything(by fast taping OK, I manage to get through few screens, but when it come's Google account choose, the screen goes black).
I tried another recovery, but none of them worked.
In the forum, there is also link to stock ROM, I think wiping all the data and flashing the phone with stock ROM could help, but last time I did something like this was about 5 years ago with Xperia, and I couldn't find any guide how to do this, so could you guys please tell me what to do?
Thanks.
adamjezek98 said:
Hi,
I have Galaxy S4 Mini VE GT-i9195i. The phone was a bit laggy, so I decided to factory reset. When I did it, the phone didn't booted. It was showing Odin download screen with red text "Could not do normal boot, odin mode" (or something like that). In thread [index] Galaxy S4 mini i9195i were some recoveries, so I used odin to recovery it. Now, when booting, it shows "Kernel is not seandroid reinforcing, set warranty bit:kernel" and when it boots up, there is setup screen (the one which shows when you firt turn the phone on), but the phone is spamming with message boxes "<random process or app> stopped working", so I can't do anything(by fast taping OK, I manage to get through few screens, but when it come's Google account choose, the screen goes black).
I tried another recovery, but none of them worked.
In the forum, there is also link to stock ROM, I think wiping all the data and flashing the phone with stock ROM could help, but last time I did something like this was about 5 years ago with Xperia, and I couldn't find any guide how to do this, so could you guys please tell me what to do?
Thanks.
Click to expand...
Click to collapse
Sorry to hear about your situation. I think flashing the stock rom is the last best option. Anyways here r the steps:
1. Download Odin 3.1x.x version( its the program via which you can flash samsung stock roms, modems,recoveries and caches etc,...google it)
2.If possible, before doing anything to your phone, take a nandroid backup from recovery like TWRP or CWM)
3.Hold power+home+volume down button to boot into bootloader menu. Once booted, it will ask you to press volume up button to continue, do that.
4.Now connect your phone to your pc via data cable( kindly confirm that your pc usb ports are working properly otherwise the flashing will corrupt)
5. Open Odin. If connected properly, you will see the ID:COM tab turn blue mentioning the port name you connected.Now click AP on right hand side and search /select the location where your Stock rom(md5) file is located. Now on left side panel(logs) you will see something is going on. Wait for a few minitues and after processing is done (when you see the lines "leave cs...") Click start and relax.
6.It will take some time to flash the rom. If everything went well, there will be a "PASS" message on top left of Odin. The phone will boot into recovery and do some cleaning and reboot again.......................................................Congratulations!!
Note: I follow this method on GT-9192 and i think its same with your model.
I think the message "Kernel is not seandroid reinforcing" means incompatible recovery software for this device. Try different one.
The only working recovery for our phone is TWRP recovery. Flash the .img through flashify after rooting with Kingroot / Supersu me and you are done . Be sure to flash the stock rom through odin to fix any hiccups with app not responding and after proceed normally.