NEED HELP! GT-I9190 Hard bricked, currently stuck in a bootloop - Galaxy S 4 Mini Q&A, Help & Troubleshooting

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

Related

[Q] HELP!!!!

I cannot get my phone to boot up. It loads the splash screen and gets stuck there. It doesn't move past that screen. I've tried multiple times going into recovery mode but it won't go. I can get into download mode though. I've tried using Odin 3.07 to reflash the KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar.md5 from the back to stock rar I found here http://forum.xda-developers.com/showthread.php?p=41340941 and I do not know what to do next. I've even tried flashing a recovery tar file I found here http://forum.xda-developers.com/showthread.php?t=2533333. I've also tried removing the battery, replacing the battery (I have a second battery), and even if I power off the device and plug it up to my charger it loads the splash screen and stays there. I've looked around online and found this http://www.note2forum.com/forum/galaxy-note-2-help/1530-troubleshooting-samsung-galaxy-phone-bootloop.html#post20381 but can't even get to recovery mode to do a data wipe. The last thing I was able to do successfully with my phone was get it back to stock so and do the update to 4.1.2 because it was on 4.1.1 and I've seen something called SDS while searching. Is that what happened here? Is my phone able to be repaired? When I'm in download mode the upper left corner shows the following information:
ODIN MODE
PRODUCT NAME: SGH-I317
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV
I'm doing some serious reaching here because this is my primary phone, and I'm not familiar with PIT files but what I briefly read stated something about identifying which files go to which partition. I have no experience or knowledge of bootloader functions/changes and I've never checked more than auto reboot and reset time in ODIN. Any help is greatly appreciated.
Update!!! OMG I'm so happy to make progress. I flashed in ODIN the 4.3param_tz.tar file found herehttp://forum.xda-developers.com/showthread.php?t=2497994 and it successfully rebooted me into CWM. I will post the results of a ROM restore I'm attempting shortly. I was able to complete a full restore of a previous ROM and my phone is now currently booting up as I type this. Hopefully nothing goes wrong, but I've gotten farther now than I have in the past 5 hours I've been glued to my laptop. Time for a cig and beer.
Assassyn said:
I cannot get my phone to boot up. It loads the splash screen and gets stuck there. It doesn't move past that screen. I've tried multiple times going into recovery mode but it won't go. I can get into download mode though. I've tried using Odin 3.07 to reflash the KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar.md5 from the back to stock rar I found here http://forum.xda-developers.com/showthread.php?p=41340941 and I do not know what to do next. I've even tried flashing a recovery tar file I found here http://forum.xda-developers.com/showthread.php?t=2533333. I've also tried removing the battery, replacing the battery (I have a second battery), and even if I power off the device and plug it up to my charger it loads the splash screen and stays there. I've looked around online and found this http://www.note2forum.com/forum/gal...-samsung-galaxy-phone-bootloop.html#post20381 but can't even get to recovery mode to do a data wipe. The last thing I was able to do successfully with my phone was get it back to stock so and do the update to 4.1.2 because it was on 4.1.1 and I've seen something called SDS while searching. Is that what happened here? Is my phone able to be repaired? When I'm in download mode the upper left corner shows the following information:
ODIN MODE
PRODUCT NAME: SGH-I317
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV
I'm doing some serious reaching here because this is my primary phone, and I'm not familiar with PIT files but what I briefly read stated something about identifying which files go to which partition. I have no experience or knowledge of bootloader functions/changes and I've never checked more than auto reboot and reset time in ODIN. Any help is greatly appreciated.
Update!!! OMG I'm so happy to make progress. I flashed in ODIN the 4.3param_tz.tar file found herehttp://forum.xda-developers.com/showthread.php?t=2497994 and it successfully rebooted me into CWM. I will post the results of a ROM restore I'm attempting shortly. I was able to complete a full restore of a previous ROM and my phone is now currently booting up as I type this. Hopefully nothing goes wrong, but I've gotten farther now than I have in the past 5 hours I've been glued to my laptop. Time for a cig and beer.
Click to expand...
Click to collapse
Good for you! FYI, I think u can do a wipe through adb (adb wipe) I think. Nothing should go wrong after restoring your nandroid. (BTW, it's not sds.)
P.S. get a good beer and relax.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
Sadly ...we still can't dump that pathetic Knox bootloader ...yet...but progress is being made...
And if not...we can downgrade and still flash any rom we want...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Revived my bricked SGH-T999 and now its stuck again?

So I tried to search online for a solution but nothing is helping. What happened was I woke up one day and my Tmobile galaxy s3 4.3 was showing the samsung logo for about 5 minutes. I removed my battery and turned the phone on. It turned on and then instantly the screen died. I'm somewhat of a newbie to phones...but i tried everything...download mode, recovery, safe mode, connecting to a computer cant recognize my device, and its not charging, no vibration when holding power button (hard bricked). I tried custom ROMs a while back and it messed up so i went back to stock with just root access. I found a video on YouTube that "helped" me. I followed his steps correctly and the phone did come alive...but it came alive to a screen I've never seen before. His video talked me through downloading a debrick file specific for T999 4.3 and then using a program called Win32 disk imager. His instructions were to extract the file and place it on my 16gb micro sd card and then place into my phone, so the file revived my phone because the phone finally turned on but I cant access the phone. Which leads me to my question (sorry for length, thought i would clarify all)... the screen I'm seeing right now is an all black screen with words in the top left, no android recovery logo or yellow triangle logo. I've tried to turn on and off the phone and download and recovery mode etc but nothing works. The screen reads as following:
BOOT RECOVERY MODE
CHECK BOOT PARTITION. .
COPY FROM T-FLASH. .
BOOT RECOVERY. .
WRITE 159488 sectors. .
FLASH WRITE FAILURE
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: NONE
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 1
So any advice to help me unbrick my T999? Is it still bricked? Is my only option a JTAG? I checked that i had root access with a root checker and I've had many apps that require root access so does that mean the file i downloaded unrooted my phone? If so, since my phone reads as official and not custom, could Tmobile fix my phone even if I'm without warranty.
Any help would be appreciated, thanks!!
Hi
Thank you for using XDA assist
Please wait for moderation team to move this thread to T Mobile Galaxy S 3 Q/A section for better support
http://forum.xda-developers.com/galaxy-s3-t-mobile/help.
Good day!
I am in the same boot as you. My Tmobile S3 T999 just went black the other night all of sudden. It wouldn't not power up or do anything. Complete brick. I too loaded the image to SD card and the phone did turn on with the same message you got. But when I tried to flash with ODIN I get the "No pit partition" error every time. If anyone can help that would be great. Just need to be able to get my date off the phone such as photos and videos.
XDA Visitor said:
So I tried to search online for a solution but nothing is helping. What happened was I woke up one day and my Tmobile galaxy s3 4.3 was showing the samsung logo for about 5 minutes. I removed my battery and turned the phone on. It turned on and then instantly the screen died. I'm somewhat of a newbie to phones...but i tried everything...download mode, recovery, safe mode, connecting to a computer cant recognize my device, and its not charging, no vibration when holding power button (hard bricked). I tried custom ROMs a while back and it messed up so i went back to stock with just root access. I found a video on YouTube that "helped" me. I followed his steps correctly and the phone did come alive...but it came alive to a screen I've never seen before. His video talked me through downloading a debrick file specific for T999 4.3 and then using a program called Win32 disk imager. His instructions were to extract the file and place it on my 16gb micro sd card and then place into my phone, so the file revived my phone because the phone finally turned on but I cant access the phone. Which leads me to my question (sorry for length, thought i would clarify all)... the screen I'm seeing right now is an all black screen with words in the top left, no android recovery logo or yellow triangle logo. I've tried to turn on and off the phone and download and recovery mode etc but nothing works. The screen reads as following:
BOOT RECOVERY MODE
CHECK BOOT PARTITION. .
COPY FROM T-FLASH. .
BOOT RECOVERY. .
WRITE 159488 sectors. .
FLASH WRITE FAILURE
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: NONE
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 1
So any advice to help me unbrick my T999? Is it still bricked? Is my only option a JTAG? I checked that i had root access with a root checker and I've had many apps that require root access so does that mean the file i downloaded unrooted my phone? If so, since my phone reads as official and not custom, could Tmobile fix my phone even if I'm without warranty.
Any help would be appreciated, thanks!!
Click to expand...
Click to collapse
Were you able to figure this out or find something that could help fix this problem? I ran in to the same situation about a week ago. I cant find any threads on any forums that seem to be able to solve this.
Yeah ive been looking for a solution just to be able to revive it only once more to resave all my data. But then i got my s6 so now my s3 is just collecting dust until someone finds a new method

[Q] Help! Fix Stuck on Boot Logo

Hello there, all xda members.
I got Ace 2 to fix from my friend. He doesnt know exactly why did the phone becoming stuck on bootlogo. Maybe messing up with flashing GB or JB. or maybe wrong terminal command.
Ace 2 Condition :
- Its unable to pass boot logo samsung galaxy ace 2
- Its unable to enter recovery mode
- Its able to enter download mode, and its custom binary download : No, Current binary : Samsung official
Here all the thing that i have tried to fix the phone :
1. Flashing the phone with Russian Gingerbread with 3 files, Pit, CSC, and PDA. But it still stuck on bootlogo and unable to enter stock recovery. it shows succeed though on Odin, but it can't boot.
2. Flashing the phone with Latest Jelly bean, with Jelly bean pit file. Odin displaying succeed, but it doesnt boot either.
Can someone help me how to solve this problem?
Is there a condition where phone completely unable to recover from hardbrick such as stuck on bootlogo, but still able to enter download mode?
I'm going to download jelly bean mb2 or mb4 which include pit and csc from jelly bean and try to reflash it. Hope it gonna work.
Thanks for any help.
Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
And if it really doesnt have a solution, maybe i'll just give it up. And doesnt continue researching to fix this phone. Thanks
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
It got the same case. Successfull flashing, but still doesnt boot, it just like flashing is fail. or it just like it reverted the way it was before flashing. Your help is very appreciated.
riyosakura said:
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
Click to expand...
Click to collapse
Very strange. And more strange is that several people have this "only boot to logo / only downloadmode issue"
Up to now I have no Idea - I asume that ADB is not working, because of missing recovery mode? With ADB there are plenty of possibilities.
An complete Factory reset could be helpfull - But how to do it out of downloadmode ?! Don't know.
Up to now I didn't had a Phone with this behaviour for repair at home. If it would be reproducible how this all happens, I would bring my phone to this state to find out how to repair it (riff box here - so dead ACE 2 is not a problem) - But even this is unclear - Every report regarding this said only "suddenly" "without any reason" "flashed this or that" - But no exact infomation what happend acctually.
I'm out of Ideas. Sorry!
Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.
riyosakura said:
Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.
Click to expand...
Click to collapse
Another try:
Flash with ODIN Ace2Nutzers Stock Kernel (search on FTP)
Do not let the Phone boot
After Flashing pull usb und press drictly the 3 keys to get into Rec. Mode
riyosakura said:
Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
Click to expand...
Click to collapse
No, I haven't had the phone in such condition as described above. But I have heard that any odin-flashable file that's wrongly flashed via "Phone" entry can lead brick which is similar to this. I remember only one case - one user from 4pda has flashed some file via odin, wrongly putting file to the "phone", and wasn't able to restore it anyhow - but he also had some brick on GPIO side - vol.up worked like vol.down, and the real vol.down didn't work at all. I don't know however, what memory partitions / any devices capable of storing data would be messed after this operation, and whether it's reparable at all. I mentioned devices, that can also store data, I know only that touchscreen has small memory for its firmware(that what I had broke one day in the past after accidental firmware change in the kernel) - but maybe some other devices also has it?!
There are also some chances that it's dead flash memory - chances are pretty small, but should also be taken into account.

Bootloop? /Enters Recovery Stock/Enters Download Mode/Odin fails/HELP

I'm having a big trouble with my Galaxy Note 2 GT N7100. Everything was going well, I have an spare battery, so I changed it when the other one died. When I turned on my phone, it didn't boot. It keeped showing the Galaxy Note II GT-N7100 screen.
I can't remember if I was on 4.3 or 4.4.4. It wasn't rooted, and it had an stock recovery.
So I proceeded to flash an stock ROM via Odin. This didn't work. I downloaded different ROMs. 4.4.4 and 4.3. None of those worked. I tried different USB cables and USB ports. Different PCs with different windows version. Odin still failing.
The phone enters recovery without any problems, takes like 1 minute to enter into recovery mode, but at the end goes by. But this appears when I go into the recovery:
failed to mount cache/efs
failed to mount/system
can't mount/cache/recovery/last_install
I tried a wipe factory reset, nothing happens, those error (failed to mount cache, etc) keeps showing up.
I even tried with different Odin versions, 3.07, 3.09, and 3.10.7. It keeps failing.
When I go into download mode this is shown:
product name: GT-7100
Current Binary: Samsung Official
System Status: Official
Knox Warranty VOID: 0
AP SWREV:2
Then I tried to flash a custom recovery and flash a custom rom. Nothing. I tried with this custom recovery
- philz_touch_6.07.6-jfltexx.tar
- philz_touch_5.15.0-n7100.tar
- recovery-clockwork-touch-6.0.4.3-n7100
- recovery-clockwork-6.0.4.3-n7100
Then I decided to flash this one
- twrp-2.3.1.1-n7100.img . tar
Aaand something interesting happened, Odin didn't show an error. RESET was blue, and then PASS on green. BUT when I do vol+, power button, home button it keeps going into stock recovery.
So I tried to flash the TWRP recovery again but unchecking the autoboot option. PARTITION WAS NOT CHECKED. Odin said RESET on blue then PASS on green, didn't auto reboot, so I did the combo keys. Vol+, power button, home button.
Still entering on stock recovery.
I dont know what else to do. I'm desperate. I mean the phone turns on, but it freeze on the Samsung Galaxy Note II screen. There has to be something to do right?
I really hope you could help me!
Thank you in advanced.
robertofelce said:
I'm having a big trouble with my Galaxy Note 2 GT N7100. Everything was going well, I have an spare battery, so I changed it when the other one died. When I turned on my phone, it didn't boot. It keeped showing the Galaxy Note II GT-N7100 screen.
I can't remember if I was on 4.3 or 4.4.4. It wasn't rooted, and it had an stock recovery.
So I proceeded to flash an stock ROM via Odin. This didn't work. I downloaded different ROMs. 4.4.4 and 4.3. None of those worked. I tried different USB cables and USB ports. Different PCs with different windows version. Odin still failing.
The phone enters recovery without any problems, takes like 1 minute to enter into recovery mode, but at the end goes by. But this appears when I go into the recovery:
failed to mount cache/efs
failed to mount/system
can't mount/cache/recovery/last_install
I tried a wipe factory reset, nothing happens, those error (failed to mount cache, etc) keeps showing up.
I even tried with different Odin versions, 3.07, 3.09, and 3.10.7. It keeps failing.
When I go into download mode this is shown:
product name: GT-7100
Current Binary: Samsung Official
System Status: Official
Knox Warranty VOID: 0
AP SWREV:2
Then I tried to flash a custom recovery and flash a custom rom. Nothing. I tried with this custom recovery
- philz_touch_6.07.6-jfltexx.tar
- philz_touch_5.15.0-n7100.tar
- recovery-clockwork-touch-6.0.4.3-n7100
- recovery-clockwork-6.0.4.3-n7100
Then I decided to flash this one
- twrp-2.3.1.1-n7100.img . tar
Aaand something interesting happened, Odin didn't show an error. RESET was blue, and then PASS on green. BUT when I do vol+, power button, home button it keeps going into stock recovery.
So I tried to flash the TWRP recovery again but unchecking the autoboot option. PARTITION WAS NOT CHECKED. Odin said RESET on blue then PASS on green, didn't auto reboot, so I did the combo keys. Vol+, power button, home button.
Still entering on stock recovery.
I dont know what else to do. I'm desperate. I mean the phone turns on, but it freeze on the Samsung Galaxy Note II screen. There has to be something to do right?
I really hope you could help me!
Thank you in advanced.
Click to expand...
Click to collapse
Sounds like a hard emmc corruption (very common in earlier Galaxy devices note 1,2 and S2) but I can't be so sure
did you try flashing a new recovery from stock recovery ? if I remember correctly philz recoveries should work even from stock
if you didn't try please download a recovery from this thread http://forum.xda-developers.com/showthread.php?t=2028103 and try flashing it in stock recovery let's hope that works
I am afraid you have the SDS problem that so may Note 2's experience. Mine included. Try the methods above, but i feel they will also fail.
Only fix is to replace eMMC chip or motherboard.
Sorry for your loss
Droid_Angel said:
Sounds like a hard emmc corruption (very common in earlier Galaxy devices note 1,2 and S2) but I can't be so sure
did you try flashing a new recovery from stock recovery ? if I remember correctly philz recoveries should work even from stock
if you didn't try please download a recovery from this thread http://forum.xda-developers.com/showthread.php?t=2028103 and try flashing it in stock recovery let's hope that works
Click to expand...
Click to collapse
I haven't try that, I didn't know that I could flash a custom recovery from stock recovery. But I don't know Hoy to do that. I should save the recovery I'm going to flash on my SD card and then look for it and flash it? Or there is another way to do so?
If the problem is a hardware problem, and replace the motherboard is needed, how come the phone turns on? I thought that if the motherboard is broken or something the phone doesn't boot at all.
grwalker said:
I am afraid you have the SDS problem that so may Note 2's experience. Mine included. Try the methods above, but i feel they will also fail.
Only fix is to replace eMMC chip or motherboard.
Sorry for your loss
Click to expand...
Click to collapse
Replacing the motherboard would fix the problem? There are some motherboard on ebay for 25-40 $. Is it worth to give it a try? or it would be better to buy another phone? Like moto g 2nd gen for 99$ for example.
Why the phone boots if the motherboard is damaged?
thanks in advanced for your response! :good:
robertofelce said:
I haven't try that, I didn't know that I could flash a custom recovery from stock recovery. But I don't know Hoy to do that. I should save the recovery I'm going to flash on my SD card and then look for it and flash it? Or there is another way to do so?
If the problem is a hardware problem, and replace the motherboard is needed, how come the phone turns on? I thought that if the motherboard is broken or something the phone doesn't boot at all.
Click to expand...
Click to collapse
to flash a recovery ,yes download the .zip version put it on external sd card and flash it from stock recovery (I used to do this all the time on my old Note 2 but that was a long time ago ) ,it's the only way to flash any thing to your phone right left right now
emmc corruption doesn't put your phone on a "DEAD" state ,sometimes when the corruption affect data or last few blocks from system the phone work normally but the second the system writes the corrupted blocks it get's boot loops
robertofelce said:
Replacing the motherboard would fix the problem? There are some motherboard on ebay for 25-40 $. Is it worth to give it a try? or it would be better to buy another phone? Like moto g 2nd gen for 99$ for example.
Why the phone boots if the motherboard is damaged?
thanks in advanced for your response! :good:
Click to expand...
Click to collapse
because not the whole motherboard is damaged but only the emmc ship ,you can't change emmc ship without replacing the whole motherboard
edit :
I can't put external links because apparently I am a 'noob' here otherwise I would've put the direct link to the need recovery
Droid_Angel said:
because not the whole motherboard is damaged but only the emmc ship ,you can't change emmc ship without replacing the whole motherboard
Click to expand...
Click to collapse
yes he can change emmc chip without replacing whole motherboard, . It's a common thing in phone service, so just ask in a few places to get the quote and see if it makes sense to repair
you can google "note 2 emmc" on youtube to see how it looks. The chip itself is very cheap, like 5$, so if you know someone with the tools, then I'd just try to repair it
yaro666 said:
yes he can change emmc chip without replacing whole motherboard, . It's a common thing in phone service, so just ask in a few places to get the quote and see if it makes sense to repair
you can google "note 2 emmc" on youtube to see how it looks. The chip itself is very cheap, like 5$, so if you know someone with the tools, then I'd just try to repair it
Click to expand...
Click to collapse
really I didn't know that ,I will double check this

SM-G925F Stuck at factory reset, unable to enter the recovery mode and flash firmware

Hello and sorry if this is the wrong category...
It's my first time making a thread on xda.
I've been looking for an answer for the past 2 hours, but I still have a bricked phone... As the title says, I can't enter the recovery mode anymore. I tried to do a factory reset (when I could enter the recovery mode) and the phone got stuck at erasing. Now I can't enter the recovery mode anymore. I downloaded a new firmware from sammobile for the SM-G925F. The firmware works since I used it on an other phone and everything worked just fine. The problem is, when I open Odin and add the .tar file to AP, it gets stuck at nand write and sometimes on boot.img. The phone isn't showing that it's downloading anything (it has no progress bar). At this point I have no idea what to do...
Some extra info that could be helpful:
The phone was bootlooping when I got to fix it;
I work in a kind of phone repair store where customers bring their phones for hardware and software repair. I do the software;
I've installed new firmwares on multiple phones and I never had something like this... Normally some time with google and xda could help me to find a working way to fix the problem, but as I said... I've been looking for 2 hours and the problem is still here;
I'm not a pro with Android and phones. I just like to learn new things and I'm still learning.
Could it be a hardware problem?
Can you show me your phone's download mode image to see where could be the problem?
Also, make sure you are flashing latest firmware, if you are downgrading it - than you will get such boot errors.
*Update*
I found out what was wrong. The eMMC chip was broken.

Categories

Resources