[Q] How to revive a hardbrick Samsung Galaxy S5 SM-G900P? - Device Repair

I would like to ask if there is any possibility to unbrick it as I just got myself into trouble.
Initial states of phone:
Model : SM-G900P (supposingly, as it was shown in Odin, but within the device info and backside label is SM-G900F)
PDA & CP & CSC : G900FXXU1BOK2 (reflected via *#1234#)
Android 5.0 Lolipop
*Just in case, you are curious why this phone was in this stage, that is the original state of phone which I bought, it is refurbished, sold to me as G900F (ofc, being cheated) and that time I was not geek in phone and didn't realize it is a problem.*
*G900FXXU1BOK2 is not available in any website download so far.
Potential Cause of hard brick:
I noticed there is something not right about the PDA so forth, so I attempted to update everything with Flashfire(Rooted) with G900FXXU1CPGK downloaded from sammobile. (the reason that I didn't use Odin is because bootloader of G900P will automatically reject it with aboot error). And so Flashfire did everything.
Current states of phone:
1. Power button : system won't boot
2. Power + Vol Up + Home : Blank, no power, no recovery
3. Power + Vol Down + Home : Blank, no power, no download mode
4. Charger : Not charging
5. Odin3 is unable to detect the phone
6. adb is unable to detect the phone
I searched around Google and notice there are several options might work under this circumstance:
1. G900F phone: Mount bootloader recovery and .pit file into sd card and boot it with sd card into download mode, then re-flash everything (but this is a G900P phone, I can't find any BL recovery file associated with this model)
2. JTag service
Much appreciate if anyone can enlight me with more viable options or ways to get this fix.

Related

[Q] Galaxy S doesn't boot!!!!! :'(

I was running Android 4.0 ICS custom rom on my Galaxy S I9000 (international version), and everything was okay.today, I turned it off, and then I tried to turn it on again normally, but it kept showing the vivd colors screen without continuing. I remembered that the same problem occurred with me before on 2.3.3, and the solution was a simple odin-flashing of just one file. The problem now is that I couldn't remember which exactly of the 4 files in odin this one is (it's the one responsible for mounting the sdcard), and I connected my device while in downloading mode and recklessly flashed only PIT file (with other fields empty). Now the device doesn't boot at all, as if there is no source of energy within. Can the Company's customer support here fix it anyway or is this its end?!!!!!!
Remove te battery and put it back in. With the 3 button combo go to download mode and flash a 3 file firmware.
Try to boot in download mode (vol down + Home + Power) and flash CWM again!

[GUIDE]T-Mobile 10.1 3g Unroot back to Stock!

Hi, I was searching for a long time how to unroot my T-mobile 10.1 Galaxy tab, and I couldn't find anything. Only for the 10.1 wifi only. Didn't find one for T-mobile USA so I just made it! (BAWZ!!)
So here you go!
***Disclaimer: I am NOT responsible for any damages you cause to your device what so ever. This method worked for me but ultimately it is your responsability if anything unexpected occurs while doing this process***
Now that we got that out of the way
*Download original T-Mobile 10.1 firmware from here!
Or from here:
Mirror 1
PREP:
*Basic knowledge of how to enter Download mode and Recovery with and with out CWM.
Just in case: if your already rooted with CWM turn your tab off, press and hold the volume down first and the power key until you get to the Recovery/Download screen.(Remember use volume down (left) to navigate back and fourth and Volume up(right) to make your selection in this screen.
*You must have ODIN on your computer. (you can find this in the development section if you don't have ODIN, which you should if your rooted but if not its back in the development area.
*Need Winzip/7zip or something to extract the zip file. (When you try to unzip it's going to ask you for a password "samfirmware.com" without the quotes.)
credit to who ever uploaded this file. Not really sure but Thanks...
* USB cable/Windows (I used windows 7 32 bit)
*Make sure you have enough battery power on your tab. Mine was at 99% not sure what the minimum required is but I didn't risk it.
3. Extract the zip file you downloaded
4. Open ODIN (I use version 1.85)
5. Put your 10.1 into download mode
6. Connect your tab to PC via USB cable (ODIN should recognize your device in the COMM box, should be in the first box to the left marked with com and then a number)
7. Then check mark PDA and press that button (PDA button), now direct to the MD5 file you extracted. Open it
8. Hit start (Make sure you do not interupt the process by removing the usb cable or anyother thing just wait!)
9. Once ODIN tells you everything was successful you can unplug your 10.1 from the computer
10. Be patient let the tab restart,your going to see the original boot animation from T-Mobile.
***Note***
If your stuck in a boot loop:
1.Press the power key until the tab turns off.
2.Press and hold the volume up, volume down and power key until you get to Recovery/Download screen (let go of all the buttons)
3.Using volume down make sure recovery is selected then press the volume up key to select it.
4.Wait while your tab sets up recovery properly
5.Once you see the recovery menu wipe data/factory reset (I did it three times)
6.Final step select reboot system now. Be patient at this point your tab should restart itself normally.
I wasn't able to find any help on this so I did some looking around and now I have my TAB 10.1 back to original factory without root. I came back from CM9 ICS (needed a working camera) so I'm sure if you do this properly it will work for you to!
You can use this method if you want to change roms from ICS back to honeycomb or what ever. It is highly recommended by the DEV's to unroot and reroot if your gonna be changing roms.
If this post was helpful hit the thanks button!

[Q] Sending to Samsung for repair Emmc Bug

Ever since recovering from Emmc brick my phone has been a little "buggy". Now the internal storage has stopped mounting and freezes are getting more and more frequent so I've decided to send it back to Sammy for repair but here's where it get tricky.
Because of Emmc recovery the phones partitions aren't how they should be, and I can't get them back to there original state. If I flash the original .pit then all partitions will be corrupt but the correct size, those that work and don't have bad blocks. Will Samsung notice the phones current partitions being a little strange? should I flash an original pit and send the phone in completely bricked?
Otherwise I know I should flash stock firmware for my region in Odin.
jamesjohnson said:
Ever since recovering from Emmc brick my phone has been a little "buggy". Now the internal storage has stopped mounting and freezes are getting more and more frequent so I've decided to send it back to Sammy for repair but here's where it get tricky.
Because of Emmc recovery the phones partitions aren't how they should be, and I can't get them back to there original state. If I flash the original .pit then all partitions will be corrupt but the correct size, those that work and don't have bad blocks. Will Samsung notice the phones current partitions being a little strange? should I flash an original pit and send the phone in completely bricked?
Otherwise I know I should flash stock firmware for my region in Odin.
Click to expand...
Click to collapse
What sammy wants is that binary status to be official and custom counter reset to No..
So go to download mode by this button combo: home button + vol down + power button at same time, a message will pops asking if you want to enter to download mode, press vol up. Now check those settings:
ODIN MODE:
PRODUCT NAME: GT-N7000
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
if all OK then you can reclaim warranty
majdinj said:
What sammy wants is that binary status to be official and custom counter reset to No..
So go to download mode by this button combo: home button + vol down + power button at same time, a message will pops asking if you want to enter to download mode, press vol up. Now check those settings:
ODIN MODE:
PRODUCT NAME: GT-N7000
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
if all OK then you can reclaim warranty
Click to expand...
Click to collapse
Thanks a lot off for repair then

Galaxy note 9 brick

Galaxy
https:// vimeo.com/ 348074653
I had this exact issue after failing to install firmware via Odin, which is what I am assuming happened to you. It is easily solvable. I was unable to enter even download mode while that bootloop happpened, so here is what I did, and suggest you do:
1) Wait until the battery is drained. Just be patient.
2) Enter download mode, which for me on an international N9600 model means holding Bixby and Volume Down at the same time (use right hand if right-handed, holding phone and pressing with two fingers wrapped around) and then plug into computer or laptop. It will enter Download mode. If buttons for you to do this are different, then use them.
3) Open Odin and make sure you have an updated firmware downloaded and unzipped that is compatible with your model. SamMobile is a good source:
https://www.sammobile.com/firmwares/
4) Just install and that should end your pain.

[Q] Stuck in bootloop after trying to install a custom ROM, unable to detect the device through ADB/Fastboot [Solved]

Title says it all. But for those that want to know a bit more in detail about what's going on, I tried to install this custom ROM: https://forum.xda-developers.com/t/rom-oneui-2-5-twrp-ncx-2-5-for-a71-sm-a715f.4174135/ Clearly I did something wrong (a bit more clarification in that guide would help people not used to rooting an Android device getting through that process easier), so now I want to go to square 1 by installing the stock ROM again. But the thing is, after installing multidisabler through TWRP, the phone is not permanently stuck into a bootloop and now I can't even go into safemode, nor download mode, and I can't enter the recovery mode, the only thing my phone is capable of doing is to restart by itself by holding the volume down and the power buttons at the same time, and now ADB nor Fastboot can't detect my device (the PC does a Samsung device being connected though, so it's not a hardbrick, I guess).
Samsung devices do not use Fastboot. You should restore through Odin instead.
Try the following:
1. Download Odin on your computer, you can get it from here. Extract it into a folder.
2. Download the firmware for your device. Find out your device model first and then look on http://samfw.com, I've downloaded from there a lot in the past, it works great.
3. Extract the firmware, you should get five files: AP, BL, CP, CSC, and HOME_CSC.
4. Make sure your device is powered off, and press power + volume down + bixby. You should be asked to confirm you want to enter download mode, press the volume up button.
5. Plug your device into the computer, then select the files for all the slots. Use CSC, not HOME_CSC for CSC (CSC is for fresh restore, HOME_CSC is for software update).
6. A device should show in the top bar, something like [COM:6]. This means your device is connected. If it isn't there, make sure your device is plugged in and in Download Mode.
7. Click flash. The firmware should start to flash and there should be a progress bar in Download Mode. Once it's finished your device should reboot into the system.
ChasTechProjects said:
Samsung devices do not use Fastboot. You should restore through Odin instead.
Try the following:
1. Download Odin on your computer, you can get it from here. Extract it into a folder.
2. Download the firmware for your device. Find out your device model first and then look on http://samfw.com, I've downloaded from there a lot in the past, it works great.
3. Extract the firmware, you should get five files: AP, BL, CP, CSC, and HOME_CSC.
4. Make sure your device is powered off, and press power + volume down + bixby. You should be asked to confirm you want to enter download mode, press the volume up button.
5. Plug your device into the computer, then select the files for all the slots. Use CSC, not HOME_CSC for CSC (CSC is for fresh restore, HOME_CSC is for software update).
6. A device should show in the top bar, something like [COM:6]. This means your device is connected. If it isn't there, make sure your device is plugged in and in Download Mode.
7. Click flash. The firmware should start to flash and there should be a progress bar in Download Mode. Once it's finished your device should reboot into the system.
Click to expand...
Click to collapse
Well, trying to reflash everything through Odin has been a thing I tried to do, but how am I supposed to shutdown a phone that is stuck at the Samsung logo (is there any combination to shutdown a Samsung during the boot process?)? And even after that, how am I supposed to press "power + volume down + bixby" if both the power and bixby buttons are the same buttons?
racer21 said:
Well, trying to reflash everything through Odin has been a thing I tried to do, but how am I supposed to shutdown a phone that is stuck at the Samsung logo (is there any combination to shutdown a Samsung during the boot process?)? And even after that, how am I supposed to press "power + volume down + bixby" if both the power and bixby buttons are the same buttons?
Click to expand...
Click to collapse
Long press vol+,vol- and power and in the same time plug in in your pc
geekmaster21 said:
Long press vol+,vol- and power and in the same time plug in in your pc
Click to expand...
Click to collapse
I tried entering Download Mode hours ago, but to no avail. Even before flashing mutidisabler through TWRP (and thus, the phone was working), I had to use ADB in order to make my phone be able to enter Recovery Mode, since the combo for recovery and download mode just made my phone make a loud noise and restart my phone onto safe mode.
Ok, here's an update, apparently pressing those buttons, makes the screen have the same, but at least Odin recognizes the drive, but now I'm stuck at this error: "Complete(Write) operation failed."
Something's weird here, I'm 99.9% sure I did activate USB debugging for this phone, although that was just before wiping the entire drive before the phone got stuck in this loop.
Fixed. Many thanks to @hainguyenthao for helping me out ^^
racer21 said:
Title says it all. But for those that want to know a bit more in detail about what's going on, I tried to install this custom ROM: https://forum.xda-developers.com/t/rom-oneui-2-5-twrp-ncx-2-5-for-a71-sm-a715f.4174135/ Clearly I did something wrong (a bit more clarification in that guide would help people not used to rooting an Android device getting through that process easier), so now I want to go to square 1 by installing the stock ROM again. But the thing is, after installing multidisabler through TWRP, the phone is not permanently stuck into a bootloop and now I can't even go into safemode, nor download mode, and I can't enter the recovery mode, the only thing my phone is capable of doing is to restart by itself by holding the volume down and the power buttons at the same time, and now ADB nor Fastboot can't detect my device (the PC does a Samsung device being connected though, so it's not a hardbrick, I guess).
Click to expand...
Click to collapse
I'm sorry to hear that you had trouble installing the ROM and I'm glad you were able to fix it.
I unfortunately can't see a way that I could make the tutorial on how to install the ROM any easier. I'm almost certain I covered all my bases going over the perquisites and how to install the ROM. I also have a Telegram group in that thread so that users can join if they are ever stuck in any of the steps so that either me or other users that have successfully installed the ROM can help people in doubt since I'm not available 100% of the time. If you ever decide to give it a try again, don't be shy, you can always join the group and request for help.

Categories

Resources