Database Users

Help! Korea Tab SHW-M180S Dead!

I tried to flash the Overcome Rom onto my Tab, but it didn't work. I would turn it on see the Samsung Galaxy Tab screen, but then immediately go to a black screen.
So I tried to download my stock .tar file (M180S.DL08.0204-REV3-UPGRADE-CL761350_user.tar) and flashed it again. I went into download mode and put it into the .pda slot, and tried again. Still nothing. The same Samsung Logo then a black screen.
Then I read something about using P1_add_hidden.pit and then flashing the Roto JME_Full to get it back to life. So I did this, and then rebooted. This definitely did not work. Now I saw just a red line on the screen when I booted.
So anyway, I am able to get into download mode, but NOT recovery mode.
Also, when I try to charge it or plug it into the computer I can see the battery come up for a second, then it automatically goes to a black screen.
PLEASE HELP ME! I am a noob and don't know what to do.
Thanks.
UPDATE:
I tried out that program Heinberg(?). I don't remember the name and I am at work now. I was able to get a tar file somewhere and take out all the parts and flash. i am now able to see the Samsung Galaxy Tab logo, then the blue progress bar under it but it seems to freeze up after that and goes nowhere. I am also still unable to boot into recovery mode.

Good Luck. I am in SK and when I found out the other countries didn't have the DMB TV antennae it was a simple guess to assume there was software that the devs in other countries didn't know about.
I took mine to Samsung this week and they asked if I had downloaded anything recently. They did a hard reset and brought back my WiFi. Seems there are some laws in place that you have 14 days buyer's remorse to return it, followed by 30 days (or maybe 90) to replace a bad unit, and then 1 year free repairs. If you are within the first 2 time frames I would find a reason to return it as broken.
If someone can help you, I really am a noob when it comes to rooting and etc, then remind them of the DMB TV section and to watch out for it when they suggest something.
Hope this helps!

deadhead85: Have you found a way to fix it? Can you please share the firmware or at least a download link so i can "ressurect" my Korean Galaxy Tab?
Thanks in advance!

what happened with you?!!!

May i Install KK Bootloader after having flashed Lollipop update?

Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!

alpha-ro said:
Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!
Click to expand...
Click to collapse
Did you ever try to buy it at Samsung Store? They maybe have it

I didn't consider that, i'll see if i can contact them directly, hopefully i can get the replacement i need. Thanks friend!

Boot help Galaxy S7 Edge

Folks I initially tried to root my phone *SM-G935F* using Odin and a CF hero2lte file. The flashing was all good to go with a green pass. Then upon rebooting the phone got stuck on the Samsung logo boot screen with red words at the top that said **Recovery Is Not Seandroid Enforcing**. This being the case all I was able to get into was (Download Mode). I tried to do the samething a few times and gave up after no successful attempts and the phone not being able to successfully reboot.
Fast forward to present I downloaded the phone's firmware which was a zip that contained 4 files (5 total actually because there was another CS file in the event that you wanted to preserve your data etc.). I loaded all of the files in Odin and made an attempt to flash the phone again however it got stuck on *System* and never go to Green *Pass*. So I figured I would try it a couple of more times in case Odin or something just got hung up on the first try. Any how that wasn't the case.
Now with the above being said what did change is when I would try to reboot into *Download Mode* again it said something along the lines of Emergency Smart Switch Recover. I downloaded Smart Switch onto my computer and went through the specific steps to try to Recover the phone using Smart Switch. Now after it was all done I got to the blue screen with the Android and it said *Erasing...* then the phone booted up and its now stuck at the Samsung animation screen. This being said as of current I can now access *Download Mode* and also boot into the black screen or *Recovery Mode* I think its called where I can reboot the phone through a bootloader, power off, factory data wipe / reset, etc etc.
The above being said I have tried the factory reset / wipe. The reboot in bootloader, reboot phone, all with no success.
Also would like to add that before doing all of the above I forgot to tick *USB Debugging* in Developers Mode when the phone was in its normal state. I must also mention that all of this was a first for me and I looked at doing so to try and recover lost data on my phone. Also wanna add that I am not too familiar with ADB or twrp or how to mess with any of that stuff given the limited access I have to my device because it can no longer bootup like it normally would.
I'm currently at a lost of words as to what I can do next as I am out of ideas and could really use some help. I would also be more than happy to donate a little to anyone who is able to help me boot my phone back up and get things back to normal.
Any and all help would be greatly appreciated.

Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.

Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
Bro would you tell pls , what you did to restore. Thanks

shah22 said:
Bro would you tell pls , what you did to restore. Thanks
Click to expand...
Click to collapse
After me not being successful with the root or with flashing the stock OEM firmware using Odin the phone would get hung up in download mode and the only difference when it would go into download mode it would say to use SmartSwitch Emergency Recover which is what was used and that fixed the issue and the phone rebooted completely fine.
However the above being said I honestly still feel the phone has some small minor issues that I did try to resolve all with no luck. First off when loading to my home screen the icons, and clock, etc etc take about 2 or 3 seconds longer for them to appear on screen than it used like when the phone was new out of the box.
Other thing to note is for some odd reason this issue was thought to be worked out by just booting into recovery mode and doing a factory reset from there, wiping the cache, etc etc. Well this also didn't solve the issue and for some odd reason when performing this the phone didn't reboot on its own.
Basically how it should be normally is after you select that you want to do a factory reset, wipe cache, etc etc, the phone should normally reboot and go through the entire process by itself, however this was not the case. The phone instead went back to the recovery screen and I had to select reboot rather than it normally rebooting on its own.
I've honestly given up on things and given that it is in working order with just a few small minor hiccups I've decided to give the phone to a family member which they plan to use as trade-in credit towards a new Galaxy Note 8.
That being said I will always have a soft spot for the S7 Edge being it was my first smartphone after I had bought a Sony Xperia Z during the same year but returned it the day after because what was to me being poor quality of the Sony phone.

Hmm, looks strange bro , your phone didnt worked after flashing stock rom with odin , and this is the last resort , but you said it was normal before you tried to root , so i guess it was still a software issue other than some hardware problem due to software , but anyways wish you good luck in future , another thing is that my s7 edge has also a very poor build quality , has front camera issues , paint peeling around usb port , wifi issue and high battery degradation , but that happens i guess with today's phones

The version of Odin I used was v3.10.6. I had tried the most current version and a few others, and from the get go for whatever reason this was the only version that would actually pickup the phone being added. Well wait hold on a second the other version would say added when the phone was in but when hitting start nothing would happen, even after waiting an extensive amount of time, also note that the com was highlighted that blue ish color indicating the phone was being recognized by Odin but once again for some odd reason it was only version v3.10.6 that carried out the process of my root attempt and also the attempt I made flashing the original firmware on it.
As for quality the phone had no paint chip or peeling, neither the silver aluminum frame around it either. The build quality was beautiful and up to par with mine. I had a soft spot for my S7 Edge also because it was in the white color which at the time of purchasing was a bit more scarce than the other colors. I purchased the phone from an Amazon.com seller, and during that time I also purchased 2 others from other Amazon sellers but returned those because they had carrier animations for them that were Band LTE or Brand LTE, whatever its called.
This one had no carrier animation upon boot and turned out to be a UK Nougat model. Haven't really seen or came across another one since that would be from a trusted seller or source. Nowadays you never know what you're getting both on eBay and Amazon from these third party sellers.

Yeah thats really strange with odin , its good that you dont have quality issues which struck heavily on me , but yes everyone should be quite careful when ordering online and only should do with trusted resellers

Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?

vini3237 said:
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?
Click to expand...
Click to collapse
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.

Hydranize said:
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.
Click to expand...
Click to collapse
Phone is SM-G935FD
I do not know what caused it, I already got the celuar so, in status it says Custom.
I already tried to blink for odin 3 different Stocks and the same thing continues.
When I got it it could not access the recovery mode, only the download mode was accessible, after flashing the Brazilian Stock 6.0.1 I was able to access recovery mode.
The phone turns on, and hangs at boot, Samsung logo, restarts and stays in infinite looping.
Can it be Hardware?

Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.

Hydranize said:
Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.
Click to expand...
Click to collapse
Ok now i think what was the problem , you didnt enabled usb debugging , and for flashing with odin its a must ! , for guys who want to flash firmware using odin .. please enable usb debugging in developer options or you will have much issues and may also brick your phone , so if you dont want to enable usb debugging or developer options , just use samsung smart switch on pc to flash your firmware.

Yeah that was my issue was I had OEM Unlock checked off and one other thing in Developer Options and forgot to enable USB Debugging leaving me stuck in the process when the phone couldn't reboot normally after the flash attempts. But yeah SmartSwitch Emergency Recovery should definitely be able to fix and resolve the issue if the phone can't reboot normally.

SM-G900F unusual brick

its a european 32gb version samsung galaxy s5 SM-G900F.
the device is just over 2 years old never used rooted, since it wasn't mine.
i once rooted the device and reverted it back to official half a year ago or more.
been using the exact same PDA numbers (since that didn't work also tried different) for the official rom etc.
now during normal use, to be specific in a viber call.
the device suddenly shut off and went into a bootloop mode.
there are times the device just shows a black screen and after holding the battery out for some time it opens up again.
prior to flashing another stock rom through odin i just managed to get it booting after a factory reset holding the vol down button (safe mode)
and that is not consistent at all.
same goes as for recovery, with a lot of inconsistency i got it to boot a couple of times in recovery and once in twrp flashed through odin, tried flashing lineageos.
as i left the phone and came back i found it in a bootloop wich is unusual because twrp doesnt automatically reboot after flashing.
tried:
-cf auto root
-the european 32gb pit file
-repartitioning
-flashing multiple stock through odin
-fastboot doesnt recognize the device
-adb used to recognize, doesnt anymore
-flashing recovery
-another battery
-flashing cyanogenmod through twrp with no success
-flashing bootloader (and all else AP/BL/CP/CSC)
-tried samsung kies
-wiping cache, dalvik cache/ data factory reset (when recovery did to happen work out of luck)
the only thing working quite consistent is the bootloader through odin (no fastboot console detection) right now thats about all
and even then sometimes the phones screen is black during boot but after having the battery out for some time it works.
if i plug the phone in the charger it boots up in android but with a black screen.
i can notice because the lower touch buttons on the screen get lightened up and once i've heard the screen reader through the speakers.
it doesnt happen to boot to android without being plugged in.
so in other words im stuck with a phone on which no matter what i tried only has a working bootloader after unpopping the battery for a bit.
forgot to mention also the device always acts as if its turning on so it vibrates, either that results in a visual bootloop/or black screen not even reaching the roms logo (in the beginning sometimes did).
lately if it shows something after holding the battery out its just the galaxy s5 first logo and no rom bootup.
so its not that i press the power button and its completely dead
according to all bootloop brick solutions none of them worked as it seems its more than just that in my rare case
advice would be extremely appreciated

here is a picture of the bootloader

There was a similar/same issue that was solved on the following thread.
http://forum.xda-developers.com/showthread.php?t=3505610
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Ibuprophen said:
There was a similar/same issue that was solved on the following thread.
http://forum.xda-developers.com/showthread.php?t=3505610
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I read this and many other threads before but most if not all were solved with one of the steps i mentioned, furthermore it has always used and worked with sm-g900f roms and also states its a 900f in the bootloader unlike the experience with this thread

thanas said:
I read this and many other threads before but most if not all were solved with one of the steps i mentioned, furthermore it has always used and worked with sm-g900f roms and also states its a 900f in the bootloader unlike the experience with this thread
Click to expand...
Click to collapse
Did you try posting your issue on the following thread?
http://forum.xda-developers.com/showthread.php?t=2700073
I have a G900V and this thread is very active for all the Variants.
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Ibuprophen said:
Did you try posting your issue on the following thread?
http://forum.xda-developers.com/showthread.php?t=2700073
I have a G900V and this thread is very active for all the Variants.
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
no since the only samsung i had was years ago an s2 im not familiar. thanks man i will right now!

did u try another batttery
could be bad hw such as memory

vincom said:
did u try another batttery
could be bad hw such as memory
Click to expand...
Click to collapse
yes i tried another battery, also popped out the sdcard and sim card.
the same happens with a battery which is functional in another SM-G900F most of the time it just shows a black screen unless i leave the phone without a power source for some minutes.
after it just goes into a bootloop. or if i just put the battery back in the bootloader is almost guaranteed to work.
of the so many times trying i just managed to get 4 times in recovery or so.
well it still boots within android i can hear the narrator etc. just not with screen on.
i dont know how i did it but 2 times i managed to get it fully functional into safe mode.. not until a reboot. wonder why

also tried within odin flashing after researching options: NAND erase all, Phone EFS clear, Phone bootloader update, Repartitioning.
all combined when flashing full BL,AP,CP,CSC plus pitfile although ive read the pitfile is in the CSC if its not HOME_CSC. just to be sure for avoiding a brick.
despite this still same.
there is no way to create a backup and create an odin flashable file from a workin g900f right? ive read samsung locks partitions such as bootloader etc.
im sure this complexity is just a samsung thing, ive debricked phones even worse than this and somehow nothing appears to work.
what im currently having is a working phone with a black screen.
i can only go to the bootloader with screen on. the phone boots normally with screen off.
ive done nand erase all and all the above options i named on the latest PHN update meant for this phone.
simple solutions dont work since ive tried all, i feel i need to find a way to restore every partition to its original state with an older bootloader since ive read lots of people were experiencing this after lollipop or onto marshmallow.
can anyone help me a bit with ideas on this?

G930A S7 -- Help! -- Phone stuck at Samsung screen + will not boot into recovery mode

Hello, all!
I have a Samsung Galaxy S7 (SM-G930A). I originally used the PrinceComsy post (https://forum.xda-developers.com/att-galaxy-s7/how-to/root-s7-att-g930a-g935a-t3410538) to root my S7. This was back about 6 months ago. I ended up using an iPhone (for change of pace) and came across my S7 again and wanted to go back. It was working at the time, no problem. Since then, however, I must have done something within Odin to break it as now it is stuck at the Samsung logo boot screen with the "custom"/unlocked padlock icon on it. I cannot boot to recovery mode as when I do, it simply flashes "recovery booting..." indefinitely.
I think I need help to get this thing working again. I don't necessarily care if it has to get wiped. That said, I am willing to do what I need to do in order to get this damned thing fixed. I have tried flashing a few different G930A firmwares, but Odin either just says "failed" or "model dismatch." I have no idea what to do and all the threads I've read so far seem to be different than what I am going through.
Any ideas? Anything is much appreciated. Take care!

As it would turn out, the only firmware that I got to actually successfully flash to the S7 was the SM-930U firmware. I can now get into recovery mode and I can at least get passed the initial logon logo. When I start the phone, it takes me to the setup as if it is a new phone, however, after a certain amount of time, the phone will randomly reboot. Hmmm... going to continue to tinker with it.

Here is how I fixed my issue:
1. Downloaded and flashed the SM-G930U firmware using Odin3 v3.12 to my SM-G930A S7. This fixed the issue with not being able to get into Recovery Mode and with the phone stalling at the first boot-up Samsung logo screen.
2. Once I was able to get into recovery mode (verify this... my original issue was that it would simply flash "recovery booting..." and go nowhere.
3. I downloaded the Nougat QE1 firmware from this post: https://forum.xda-developers.com/at...mware-g930a-qe1-android-7-0-6-4-2017-t3617101
4. Flashed above firmware.
5. Rebooted a couple of times and I got into first time setup within Android (I could also tell that it worked because the ATT chime came back after rebooting).
Hope this helps someone out there! Been working on this for a couple days and it is nice that it is now working

DentMan06 said:
As it would turn out, the only firmware that I got to actually successfully flash to the S7 was the SM-930U firmware. I can now get into recovery mode and I can at least get passed the initial logon logo. When I start the phone, it takes me to the setup as if it is a new phone, however, after a certain amount of time, the phone will randomly reboot. Hmmm... going to continue to tinker with it.
Click to expand...
Click to collapse
I'm also facing the same issue...
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
DentMan06 said:
Here is how I fixed my issue:
1. Downloaded and flashed the SM-G930U firmware using Odin3 v3.12 to my SM-G930A S7. This fixed the issue with not being able to get into Recovery Mode and with the phone stalling at the first boot-up Samsung logo screen.
2. Once I was able to get into recovery mode (verify this... my original issue was that it would simply flash "recovery booting..." and go nowhere.
3. I downloaded the Nougat QE1 firmware from this post: https://forum.xda-developers.com/at...mware-g930a-qe1-android-7-0-6-4-2017-t3617101
4. Flashed above firmware.
5. Rebooted a couple of times and I got into first time setup within Android (I could also tell that it worked because the ATT chime came back after rebooting).
Hope this helps someone out there! Been working on this for a couple days and it is nice that it is now working
Click to expand...
Click to collapse
And now I'm going to try this...
Btw thanks for your post...
Sent from my [device_name] using XDA-Developers Legacy app