So I got Galaxy S4 mini that experienced common problem. Some eMMC cells died and phone won't boot up. I got Odin, USB drivers, stock rom/firmware and debrick.img. I flashed debrick.img on SD Card and phone booted into recovery mode outputting:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY..
WRITE 139008 sectors..
But when I connected phone to a PC, PC doesn't recognize the phone at all. Odin shows nothing and device manager doesn't detect anything. Has anyone experienced this problem or know how to fix it?
Related
Hi I managed to to get to SDCARD Download mode from a dead boot N7105 using the SD Boot Repair SD. Odin recognizes this and phone was previously on 4.3 JellyBean already. Now when I'm trying to flash with Odin 3.09 , it says "There is no PIT partition" . Should I click the Phone Bootloader Update checkbox also? Need some advice from all the gurus here to guide me along this, thank you very much
Hi guys,
I have a very similar scenario but with an Samsung Galaxy S3 i9300:
Couple of days ago my phone went into booting loop but after removing the battery for a couple of minutes the issue was solved.
Then 3 days later it restart out of the sudden and was stuck on the Samsung Galaxy S III splash screen.
I rebooted and tried putting the phone in Download mode. The phone went into the Samsung Galaxy S III screen twice and turn off not to boot again. Seems like a hard bricked, no response with any buttons combinations.
I read other posts here saying that I could probably boot the phone with an micro sd card. So I donwloaded image I9300UBUGML1_I9300UWHUGMK1_I9300UBUGMK1_HOME from SamMobile and mouted in a 16 Gb type 10 micro SD (my phone is also 16 Gb version)
At first I tried booting the phone pressing the power button for about 10 seconds and the screen ligthted up very quickly (less than a second) saying
SDCARD MODE
UP KEY: NORMAL BOOTING
DOWN KEY: DOWNLOAD MODE
But it was so quick that I was not able to press anything.
A day later I figure out that if I was quick enough I could press down key and put the phone on Download mode (SDCARD)
After putting the phone on Download mode I connected the phone to the PC and tried flashing it with ODIN v3.07
Odin is able to see the device but when trying to flash the phone (selecting PDA and the image mention before) a message came up saying:
There is no PIT partition
And failed.
Reading about this error in this forum, I have tried using different PIT files to re-partion the phone but no success so far.
GT-I9300_mx_20120220.pit
GT-I9300_mx_20120322.pit
GT-I9300_mx_20120329.pit
mx.pit
Odin stays on Get PIT for mapping after initializing the process.
I would like to know if anyone here have an idea on what else to try (before talking about JTAG reparing the phone as I am not 100% the phone is hard bricked)
I have not attempted to use a USB Jig yet, should I?
Other details:
I am not able to get the download with any other image file in the sd card.
If the phone is on download mode and connected to the PC, the battery can be removed and the phone stays on.
If I press up key in the SD CARD Mode the phone freezes.
Do you guys have any ideas here?
Thanks,
Hi guys!!!
I m new here and i have a big problem and i think you can help me.
My galaxy S4 mini (gt-i9190) dead. I wasnt able to turn in on, charge it, there was no respond so it was completely dead. Only when I connect to pc recognized driver.
I found some solution with debrick image here on forum (debrick_4.4.2, but when i putted debrick.img (found some for I9190 android 4.4.2 on web) into sd card via win32diskmanager and inserted it into my phone i was able to get some respond by a phone.
Withou debrick image on sd cart i can't turn my phone on at all but with inserted debrick image i have a chance to turn it on but with some kind of boot loop.
With debrick image on sd cart i can put my phone in odin mode but i can t do nothhing with it. When I connect my phone in ODIN, it recognizes, i can install a rom (firmware 4.4.2 by sammobile) satisfactorily. But my phone now when i try put it in recovery booting only i see this .... (recovery booting ... set warranty bit: recovery after see android imagen lying and this phrase ... any commands)
Help meeeee pls!!!
Hi mate.....did u find the solution?
Its been a long time since I booted my Galaxy Note-II (GT-N7100) as I use an iPhone and Nexus 5 as my daily drivers.
The phone wont boot past the Samsung Galaxy Note II GT-N7100 logo. I am able to access the recovery and download mode as well, and I have flashed the latest stock rom from Sammobile using the Odin. The flashing was successful. however the phone doesn't boot past the logo. Also the phone will not power up unless connected to a PC, it wont power up even when connected to a charger and will immediately shut down when the USB cable is disconnected from the PC. I flashed TWRP 3.0.2 Custom Recovery using the Odin and tried installing CM 13 based Rom through the mem card, however the log reads patching image unconditionally and also that "Failed to mount /system" (invalid argument). The phone when restarted into recovery can no longer mount the /system partition. However on flashing the stock rom using Odin, the /system partition is available for mounting. The recovery log also shows MTP enabled, but my PC doesn't detect the phone when in recovery, it only detects the phone in Download mode. I have the Samsung drivers installed. Since the phone is not being detected in recovery I am unable to use the adb.
I am out of ideas and request your suggestions other than approaching a service centre.
If I can somehow access the phone via ADB, I might be able to check the memory partitions for corrupt units, and possibly create a custom PIT file to repartition and suit the available memory units.
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
audit13 said:
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
Click to expand...
Click to collapse
Thanks a lot.
Tried your method and finally the phone has booted into the OS.
Had to replace the battery with another spare one in the process.
However the phone is still not being detected by the PC unless it's in Fastboot/ Download mode.
When connected to a computer, does anything appear on the phone screen? If you're using Windows, nothing new appears in device manager?
sorry to jump in this thread but i am having a similar problem
my completely stock tmobile note 2 is stuck on the samsung logo
i have never flashed it or done anything to it
my phone was working really slow, freezing up and battery draining fast
so i did a hard reset and it fixed the problem of running slow and freezing up for a week or so but battery drained fast
so i bought a replacement battery from ebay and installed it and the next day i restarted my phone and it froze on the samsung logo
i tried turning it off and on and still the same thing
any suggestions or should i start a new thread?
fyi i am a noob
Hey, all
New to this forum. My wifes samsung S4 mini La Fleur just died one day and looking it up i found that it was hardbricked. I bought the USB-JIG for the phone and used win32diskimager to write the debrick.img to the SDcard (16gb). It did boot up but it keeps looping the Revocery mode on and on and on.
Text i get is :
BOOT RECOVERY MODE:
CHECK BOOT PARTITIONS.
COPY FROM T-FLASH
BOOT RECOVERY
WRITE 138008 SECTORS
REBOOT
And this just keeps looping over and over. Odin does not detect a device. Windows however keeps giving me the sound that something is connected and then disconnected. Have tried other I9195 debrick.img but non of them even boot the device to recovery. Also installed the Qhsusb_DLOAD driver. Without the SDcard in device manager does detect the phones dloader but not Odin.
Any ideas ?
Hi, hope someone can help me!
I accidentally got my Samsung Galaxy J2 Prime SM-G32M stuck in a boot loop, it happened after i tried to put a micro-sd card in it, after i removed the micro-sd it stayed on boot loop and couldn't boot into recovery (in Enigma NL for J2 Prime there is a bug where you need to enter TWRP and reboot into system for it to turn on properly because when you turn it off the Kernel dies)
It seemed like it couldn't boot into download mode as well but i eventually got it to enter download mode, my computer does not recognize the device, i am not sure but i assume usb debugging is not enabled due to that, it doesn't have root and it uses Enigma NL Custom ROM: https://forum.xda-developers.com/t/rom-6-01-stable-g532xx-enigmanl-port-rom-for-j2-prime.3951387/ and this TWRP port: https://forum.xda-developers.com/t/...axy-j2-grand-prime-plus-sm-g532f-g-m.3616589/
The home button is a little bad and doesn't work from time to time but i don't think it is the reason of it not being able to enter TWRP. The only thing i've got is download mode, no recovery and probable no usb debugging as well, i really need the data inside but i haven't found a way of rescuing it that doesn't require USB debugging or entering recovery mode . Is there a way that i can either access recovery mode or rescue the data inside the phone without it?
I really need the data inside the phone and programs like Samsung Switch said they couldn't connect to the phone properly, plsss help
(I also tried ADB to enter recovery mode using the command line but ADB does not recognize my device even when it is turned on(on boot loop) and also when it is on download mode.)
My computer does not recognize the device.
Click to expand...
Click to collapse
Did you install Samsung drivers correctly on your PC? If not then this would explain why your PC failed to recognize your device.
I suggest you install those drivers right away, and test to see if it works.