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.
Related
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
GoonReb0rn said:
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
Click to expand...
Click to collapse
Update: I spent the past two days trying to solve this and I'm at a standstill in progress. It seems that my phone was one that suffered SDS with a corrupt eMMC chip so I've lost both my firmware and recovery but I can still get into Download mode. It also seems like I have lost my PIT table and I am just completely unable to flash the PIT file back to the phone for some reason. Does anyone have any ideas on how I could just factory reset my phone or reinstall my partition table so that i can get a simple recovery installed? Please help
Exact same issue!
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
dkinniburgh said:
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
Click to expand...
Click to collapse
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
GoonReb0rn said:
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
Click to expand...
Click to collapse
I was lucky having most of my info already backed up. I also had just upgraded another line, so I had a new phone to work with. It just sucks having to switch everything over to a new phone, reloading all the apps etc.
I was given a Galaxy Tab S by a relative who works in a cell phone store. It was a demo device, and it had demo mode enabled. I initially attempted to reboot into recovery and do a wipe from there, but an error came up informing me that "MDM" had blocked this option (I assume MDM to mean manufacturer demo mode). The tablet was still working at this point, so I rebooted and got the exact model number, SM-T700. I googled for a bit and found the recommendation to be to reinstall the firmware. I've done a lot of ODIN flashes before, so I downloaded the correct firmware from the official firmware post here on XDA, rebooted to download mode, and flashed it without issues.
After 30 minutes, the tablet still just showed the Samsung boot screen. I did a hard reboot with volume up + power, and left it. After another 30 minutes, it still didn't show anything. I rebooted to download mode and tried flashing again. Same result. I rebooted to recovery and tried to wipe the device from there. MDM block.
After more searching, I decided to use the PIT file and the firmware file in ODIN. I've had to use PIT files a couple times before, so I was very careful in checking to ensure I had the correct one. I am very confident I did. I flashed that, and still the tablet would not boot.
I then decided to install TWRP and see if I could wipe from there. TWRP gave me some useful information: it returned that it could not mount any of the partitions on the device. 'could not mount /system', 'could not mount /data', etc.
I've done a lot of googling and reading since then, but I can't seem to find anybody else with the result. The closest thing I can find is a similar situation on some ASUS tablets, but the solution would definitely not work here. The only other thing I can find is people recommending to flash the PIT file, which I have no tried a second time and still does not work.
Does anybody have any suggestions? I don't know what else to do.
You didn't need the pit file, so forget about that.
The first thing you should have done is disable the reactivation lock.
Then flash the stock firmware, after that immediately boot into recovery and factory reset.
I would reflash the stock KitKat firmware and immediately boot into recovery after the flash and wipe data/reset
Ensure that during the flashing process there are no errors.
Updating, I got it figured out.
I tried 3 different firmwares, all of which flashed with no errors but did not work. 2 were KitKat, one was lollipop. I tried a fourth firmware (a Korean one from sammobile on lollipop) and it flashed exactly the same as all of the others, but this time it worked. I have no idea what was different with this firmware compared to the other three, but it worked, and I'm happy.
Activation lock cannot be disabled via the demo mode software on Samsung devices (unless there is a method of doing so I am unaware of), so that wasn't an option. I was unable to get the stock recovery to allow a factory reset. Teamwin recovery did allow a factory reset.
Either way, its working now.
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
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Hyldran0 said:
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Click to expand...
Click to collapse
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
xdausernl said:
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
Click to expand...
Click to collapse
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Hyldran0 said:
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Click to expand...
Click to collapse
It is quite easy to turn the device off, for that to happen you have to press and hold the on/off button. You'll see that the device will shutdown and try to reboot and then finally shuts down again and stay off, then release the on/off button.
Are you sure trying to flash the correct firmware with correct changes, etc??
Please share with us the device and Android version, as well as the stock ROM version with changes you're trying to flash.
Put (copy and paste) the output of Odin below.
Another way to get the firmware flashed is by using Heimdall, but for that to happen you first need to rename the extension of the stock ROM (remove .md5 and leave .tar) and than extract all seperate pieces that are contained within the stock ROM.
All those extracted pieces from the stock ROM you have to upload seperately onto Heimdall and try to flash them to your tablet, one by one.
Heimdall you'll find 'here' or use FWUL instead which has Heimdall pre installed, download is to be found 'here' and install it on a USB medium a stick, to put FWUL onto USB, use Balena-Etcher and the download is to be found 'here'.
Micro USB cable does work, but if you're unsure, try another one and make sure using the correct drivers too.
Using Odin, make sure the tablet is recognised and 'connected' in Odin, also make sure 'repartitioning' is unchecked.
If you've used the wrong Odin version, flashing will fail!
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Hyldran0 said:
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Click to expand...
Click to collapse
You're welcome.
Hi, complete novice here, does anyone know where I can get a working Firmware for my Tab 3 v7 (SM-210)?
I have searched through various forum articles here, and tried to install with several builds but none will install. The only one that gets anywhere near is the JASBR build by gr8nole. It appears to install, but on restart, the TAB just sits on the "Samsung Tab3" start screen.
I read that I may need to flash the firmware 4.4.4 (Kit Kat), but can't find it!
The unit is not totally bricked (yet), as I can run TWRP 2.8, with which I created a backup of the original build, but when I try to restore the backup, it fails at just over 31%.
Can anyone help please?
Before I get going - yes I know I messed up. I do have plenty of experience flashing ROMs etc, albeit I'm absolutely not an expert. This was purely a not thinking moment.
So I flashed my Samsung Tab S4 with Kali Nethunter a while back, not really used the tab since. Without a great deal of thought, I decided to put the device back to factory. I went back into the OS and flicked the OEM toggle - utter braindead move. Obviously the device now comes up with a warning, the exact wording is:
"Security Error: This device has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair / return for this issue may have additional cost"
I can still access download mode.
Right, now you've finished laughing/cussing me I did some digging and apparently I can still flash with Odin if its the official ROM? I went to SAMMobile and downloaded the latest ROM and Odin fails with a write error.
What I need to know is:
How bad have I messed up?
Is this recoverable?
Any help appreciated.
Hello there,
So yes, pretty bad mistake but these things happen but it should be recoverable. Just follow the link to get your device booted up! Hopefully the link is for your variant, if not look into installing twrp recovery for your device. Once installed you can back up your data and flash the rom compatible using twrp. Then set up the device and restore your data but make sure it's unlocked or your error may repeat itself! Also you have to find the right version of Odin, they do vary some are patched. Have fun!!
Recovery
Hi,
Thanks for the reply Jedi.
It already has TWRP on it, but recovery is inaccessible since I turned the OEM lock back on. The only thing I can now access is download mode but it can't seem to write to it, which I'm guessing is because the OEM lock is back on. I thought I might still be able to write the official Samsung ROMs even with the OEM lock but it doesnt seem like its the case. Obviously no access to ADB to do a Fastboot unlock either. Fresh out of ideas.
Any other solutions?
bump - anyone? lol, really not looking for an expensive door stop.
It seems you're at the dead end. However, there might be a solution for this, not sure though does it work. But go to OnePlus forum and you'll find how to recover from bricked device. You still got hope because of TWRP. good luck bro
OK, so for anyone wondering if this is fixable, the answer is YES!
You can flash the standard ROM even with the bootloader locked. Clearly what I downloaded from SAMMobile wasnt compatible, however when I used Frija, it found and downloaded the correct ROMs.
Another sticking point of this was the infamous USB 2.0 issue, I assumed the ROM was failing again, however when I finally could be arsed to try it on my old PC, its worked like a charm.
So there you have it:
Latest version of Odin
Latest Samsung USB drivers
Latest ROM downloaded from Frija
Put the tablet into download mode and flash away.