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 ?
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,
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
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?
TL,DR:my s4 mini got a random android update and when it finished updating the evie launcher and touchwis stopped working then android stopped working, got frozen and then shut down after, some time i got it to enter odin mode put the stock rom and got into boot loop with samsung logo, i turn it off after some time, now it wont boot into anything, if a put a sd card with debrick img this apear and only this, if reboot and that msg show again
Boot recovery mode
check boot partitions
copy from t-flash
boot recovery
write 1390008 sections
reboot
_________________________________
Long explanation:
My movistar brand samsung S4 mini (the phone contract ended so i change service provider so they did gave me a code and the phone was free from the contract and now it can accept any service provider) gt-i9190 2 year ago died after a chash in the system, i did have the evie launcher and a different keyboard (not using touchwis) the evie launcher stopped working then touchwis stopped working the phone home menu got to the simple layout then the phone freased and after a couple of second it shut down all this in less than 1 min t and never turn on again, i have a new phone but i will like to use the s4 mini for a proyect but its not starting,
i put an SDXC UHS-I class 10 A1 with a debrick.img(i did try 2 .img from this forum and the phone enter boot recovery mode and show this
__________________________
Boot recovery mode
check boot partitions
copy from t-flash
boot recovery
write 1390008 sections
reboot
________________________
then reboot and the same msg this for more than 30 mins then it stopped until i reconnect it to the pc or the charger or try to turn it on using the power botton, when the phone stop rebooting the normal convinations of keys make it vibrate for 3-4 times but nothing shows in the screen, the bottom convination make it vibrate just after the reboot part and the boot recovery mode dont show again until i stop pressing the bottom comvination then it start the boot recovery loop again, the boot dont fail or at least it do not say it, it just stop trying to rebootafter a long time, its like if its waiting for something to be done by me, like using the botton combination to enter download mode but well idk what to do plz help
Time line of what happened so far
2018
phone died after random update of android OS , though it was his time as i own it for + 5 years
2019
got a new phone and got curious about what happened so i started looking the internet , ended in this website almost everytime.
i left the phone chargin while i searched for answers, i connected the phone to my pc, try the botton combination to get to download mode and recovery(not succesfull) , removed the battery, try to turn it on without baterry to drain all power of phone and restart volatile memory (multiple times) and put it again without gettin anywhere try to connected to a netbook that was freshly formated and with fresh windows 10 intall, odin in that pc recognise the phone just as Qloader-9008 com (x) continued searching and from nowhere the phone started vibrating and then stoped and the chargin icon apeared on the screen i left it to charge as that was the first time i was 100% sure it was chargin after 10+ hours chargin while i was sleeping i try the botton to enter download mode and it worked, try the stock rom from my model, country and service provider and the phone got stuck on a boot loop showing the movistar intro then the s4 mini intro and vibratin each time it was to late so i stupidly turn it of, next morning i got back to try make it work but now it was totally unresponsive odin didn recognize the phone, didnt enter download mode or recovery , no boot loop, nothing is only make a sound in my pc when i try the botton combinations but nothing more just a sound of something connecting and disconnectingx2 got frustrated and left it there collecting dust, also the usb jig dont work
2020
4 months ago i got back to try to make the s4 mini work so i searched the internet again and found the sd card way i did try it and now im here with the phone in a loop of rebootin an starting the same boot recovery mode, it do not say "Flash write failure Ddi : mmc_read dailed" as i did read on other threads in this forum so as i stated before
i put an SDXC UHS-I class 10 A1 with a debrick.img and the phone enter boot recovery mode and show this
__________________________
Boot recovery mode
check boot partitions
copy from t-flash
boot recovery
write 1390008 sections
reboot
________________________
then reboot on a loop and the same msg this for more than 15 mins then it stopped until i reconnect it to the pc or the charger or try to turn it on using the power botton, when the phone stop rebooting the normal convinations of keys make it vibrate for 3-4 times but nothing shows in the screen, the boot dont fail or at least it do not say it, it just stop trying to reboot,
what can i do to at least get it to a point that kies or smart switch can take the controll or be able to use odin, the battery is at 3.78volts
If you can get your S4mini into Download mode, you should try Odin again. But this time, under the Options tab, UNcheck the box for Auto Reboot as well as the box for F. Reset Time. And then when Odin gives the green success indication, immediately disconnect USB and remove battery. Re-insert the battery after a minute or so. Another suggestion; flash the Movistar firmware only if you intend to use their carrier service. Otherwise, it would be better to use firmware not specific to any one carrier. Be sure the 3rd letter of the baseband code is "U" (for "unspecified" carrier). Good luck, hopefully your troubles are not due to faulty hardware.
HY to me happend tha Same my S4-Mini has showing Error in instand and after a tryed to Reboot the Phone was Complete DEAD , tryed the to Boot From SD- Card BOOT RECOVERY MODE it Says FLASH WRITE FAILURE ddi MMC read Failed ! Via odin same happens cant Write Read and NO PIT Partiion FOUND a Tryed also WiTH PIT FAIL .. IT LOOK MY S4- Mini Is Complete DEAD at least the emmc Chip
Happened to me aswell... When i put my SD card with debrick.img on then it bootloops the exackt same way. Cant find any prog or any help to avoid this. Cant even see the phone in Odin no matter with or without the sd card - Or get it to download mode either... i only see the Qualcomm 9008 port as open in device manager
Titanity said:
Happened to me aswell... When i put my SD card with debrick.img on then it bootloops the exackt same way. Cant find any prog or any help to avoid this. Cant even see the phone in Odin no matter with or without the sd card - Or get it to download mode either... i only see the Qualcomm 9008 port as open in device manager
Click to expand...
Click to collapse
How long your has lasting until it died myn was 8 Jears
DEXXO said:
How long your has lasting until it died myn was 8 Jears
Click to expand...
Click to collapse
I need a solution, not a competition in the fails
Titanity said:
I need a solution, not a competition in the fails
Click to expand...
Click to collapse
It was just a question plz dont Cry , and there is no solution your emmc sandisk memory is death 99% buy new or repair good luck
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.