Database Users

[Q] Stuck in boot animation-Can't mount \data after KK update with odinPc

Hi all,
After a looong night flashing and downloading again and again trying different methods, I'm out of ideas.
I have a uk n9005 (btu) that was happily running out of the box 4.3 stock until yesterday night. No root, no flash attempts before.
I started by flashing german 4.4 (dbt) without wiping before (big mistake, maybe) and without pit file and no repartition nor bootloader update checked. The error came out and I flashed again with the pit file. I let the phone reboot, but it didn't go further than the boot animation. I take out the battery and boot in the recovery. That is when I saw the can't mount \data error for the first time.
I tried to wipe, although it was impossible since the data was not mounted. However I could (and still can) wipe cache. I restarted the phone, and again the same situation, stuck in boot animation. From this moment I've tried many things:
- Flashing the bootloader separately and then the rom. no results (data not mounted and stuck in boot animation)
- Flashing custom recovery and after, official cm11 nightly and another cm11 based rom. no results (data not mounted and stuck in boot animation)
- Downgrading to 4.3. Not possible. Thank you Samsung!
- Firmware recovery with kies 3.0. no results since 4.4 has not been released for my region (maybe waiting for if to come out would be a solution)
- Flashing Polish and german (againg) 4.4 with and without pit file. no results (data not mounted and stuck in boot animation)
The only thing I can think of that I haven't tried yet is flashing a custom kernel, but I can't see any advantage in doing that. Next approach is taking it to the technical service to see if they can solve this situation. I'm afraid they're going to ask for almost as much money as a new note 3 costs...
P.D: I know I haven't taken part a lot in this forum, but I've been reading it for years, since I started playing with my SGS back in 2011. This is the first time I'm really lost after spending the night searching the forum (not only the note 3 section). This really pisses me off, with my previous phones I could always find a way to bring them back to life, but with SGS4 and SGN3 things are totally different thanks to samsung. (sorry for this looong post)
Thank you in advance

have you checked repartitioning when using the pit file?
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77

Hundsbuah said:
have you checked repartitioning when using the pit file?
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click to expand...
Click to collapse
Yes, in fact I think it is checked automatically after you select the pit file.
Thank you anyway.
Any other ideas?

Contruk27 said:
Yes, in fact I think it is checked automatically after you select the pit file.
Thank you anyway.
Any other ideas?
Click to expand...
Click to collapse
Did you try it with different Odin versions?

Pierre118 said:
Did you try it with different Odin versions?
Click to expand...
Click to collapse
Nope... I used last version, I read somewhere that it was safer...
I will try with an older one when I get home
Thank you for the idea!

Contruk27 said:
Nope... I used last version, I read somewhere that it was safer...
I will try with an older one when I get home
Thank you for the idea!
Click to expand...
Click to collapse
No problem. Let us know the result.

I'd try Odin 3.04, with the original stock polish rom.
I had no trouble using the Polish KK rom that came in 4 pieces, AP, BL, CP and CSC. I flashed 2 Note 3's using this with no problems whatsoever.
I can't say for sure you won't but it's worth a try...
Also, check to see if your Knox warranty has been tripped as this can happen when fooling around with roms.
You will have no love with Kies even when your region receives KK rom as Kies doesn't recognise bootloaders since MJ3... Good going Samsung, have had a few months to fix and have done NOTHING...

ultramag69 said:
I'd try Odin 3.04, with the original stock polish rom.
I had no trouble using the Polish KK rom that came in 4 pieces, AP, BL, CP and CSC. I flashed 2 Note 3's using this with no problems whatsoever.
I can't say for sure you won't but it's worth a try...
Also, check to see if your Knox warranty has been tripped as this can happen when fooling around with roms.
You will have no love with Kies even when your region receives KK rom as Kies doesn't recognise bootloaders since MJ3... Good going Samsung, have had a few months to fix and have done NOTHING...
Click to expand...
Click to collapse
I've been searching for a rom in 4 pieces but I haven't find it. I downloaded 2 polish roms and neither of them was in 4 pieces. Can you tell me where can I find it? Because at the moment it's impossible to download anything from sammobile... Thank you!
My knox warranty was tripped just after the fail size error in odin, the first time I attempted to flash. However that's not my main concern now... haha
"Nice" to know that about kies. At this moment, the only reason to buy another samsung phone is the big community behind it :victory:. I thought they were going to do something about the bloatware, but it's getting even worse every time a new phone is announced...

Contruk27 said:
I've been searching for a rom in 4 pieces but I haven't find it. I downloaded 2 polish roms and neither of them was in 4 pieces. Can you tell me where can I find it? Because at the moment it's impossible to download anything from sammobile... Thank you!
My knox warranty was tripped just after the fail size error in odin, the first time I attempted to flash. However that's not my main concern now... haha
"Nice" to know that about kies. At this moment, the only reason to buy another samsung phone is the big community behind it :victory:. I thought they were going to do something about the bloatware, but it's getting even worse every time a new phone is announced...
Click to expand...
Click to collapse
Not sure anymore, I no longer have the rom... And it was through Sammobile I got it.
Possibly someone might have it and share it with you....

ultramag69 said:
Not sure anymore, I no longer have the rom... And it was through Sammobile I got it.
Possibly someone might have it and share it with you....
Click to expand...
Click to collapse
It's going to be difficult that someone has it, since most people prefer 1 file roms. I will pray to sammobile haha
I'm not an expert, so I don't know if it's something critical for the phone (data mounted) to boot, but whenever I had this problem before with my previous phones, I was able to fix it by flashing a sock rom with odin or going back to the previous rom. So, my main concern now is that after all the flashing I've made, I still can't mount \data.

Need help on unfamiliar error screen. Image provided.

Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.

3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app

Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?

intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.

1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app

celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/

Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone

st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.

Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app

Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.

www.sammobile.com/firmwares/

I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.

sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.

So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse

HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!

permanent bootloop samsung note 4 sm-n910p

ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.

Primal instinct said:
ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.

You flashed a custom rom?
well did you check the bootloader and modem?
example: your old firmwara was based on a coh4 and the new custom is based on coj3.. then you get bootloops.
In this case please download the fitting bl & modem to your rom!

Primal instinct said:
ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.
Click to expand...
Click to collapse
what version are you from the start before you flashed? please provide complete information

Its easy as anything
Download your phones official firmware from sammobile.com
Flash through odin in pda/ap tab

ankahuja said:
Its easy as anything
Download your phones official firmware from sammobile.com
Flash through odin in pda/ap tab
Click to expand...
Click to collapse
well ive done that like 3 times and it still wont come out of bootloop. its as if the phones bricked...turns on then tries to start up but turns right back off. it sometimes goes as far as saying android is starting and optimizes a few apps and shuts off

kerbiii said:
what version are you from the start before you flashed? please provide complete information
Click to expand...
Click to collapse
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps

Primal instinct said:
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps
Click to expand...
Click to collapse
Trying going back to a 5.0.1 firmware
N910PVPU3BOF5 ( I pulled that from N910P) Didn't remember Sprint model number.
So if I'm wrong find the correct model of sammobile and download 5.0.1.
See what that does. Bootloader should not be locked so it should be possible,

Primal instinct said:
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps
Click to expand...
Click to collapse
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset

kerbiii said:
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset
Click to expand...
Click to collapse
I was on the correct firmware. but for some reason even if I use odin to flash newer firmware coj6 it still doesn't boot up.

kerbiii said:
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset
Click to expand...
Click to collapse
update: i can use cyanogenmod for a few minutes but then it shuts off again. my sprint sim card is not readable which is wierd since its a sprint rom cog5 baseband. any ideas :crying::crying:

deroyabun said:
You flashed a custom rom?
well did you check the bootloader and modem?
example: your old firmwara was based on a coh4 and the new custom is based on coj3.. then you get bootloops.
In this case please download the fitting bl & modem to your rom!
Click to expand...
Click to collapse
i downloaded and installed the correct bootloader and modem but still no bueno. i got cyanogenmod for trltespr to work and boot up but sim card not readable and it shuts down after a few minutes. thats really wierd considering its a sprint based rom. any ideas

I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.

Have you tried a new battery yet?
Sent from my iPhone using Tapatalk

amongunz said:
I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.
Click to expand...
Click to collapse
me too, i also have a bootloop for a couple of months now. tried literally every single combination of bootloaders/modems/kernels/ROMs . i can't even get into recovery, but can get into download mode.
do you guys think trying another battery may seriously help? how could a new battery help getting out of a bootloop if download and/or recovery mode work fine?

I don't think another battery will do anything. I think it is all software. I can flash CM11 btw, so you should try that. But my system is extremely unstable... it works... but is beyond frustrating. my smart watch wont work.. have to restart phone throughout day.... so many problems I cant even list them all.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Chasef254 said:
Have you tried a new battery yet?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
A battery? How in the world would that help? That makes no sense... no offense, just sounds like you are asking someone to unnecessarily to spend $$$ when it is clearly software.

I'm having the same problems and want to know if op has tried it so I'll know if it's been ruled out of the problem thats why. Ok so it's software. You have the solution. No offense.
Sent from my iPhone using Tapatalk

d0p3t said:
me too, i also have a bootloop for a couple of months now. tried literally every single combination of bootloaders/modems/kernels/ROMs . i can't even get into recovery, but can get into download mode.
do you guys think trying another battery may seriously help? how could a new battery help getting out of a bootloop if download and/or recovery mode work fine?
Click to expand...
Click to collapse
I think this is a samsung issue. I am going to try and see if i can replace motherboard bc thats the only logical option. I can remarkably download and run (for a few minutes) cm12.1 but my sprint sim card is unrecognized (wierdly). I dont think its the modem or bootloader....ill update yall if i find a fix. Thanks P.I

amongunz said:
I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.
Click to expand...
Click to collapse
The only solution i can find is to replace the motherboard or replace phone all together.

Primal instinct said:
I think this is a samsung issue. I am going to try and see if i can replace motherboard bc thats the only logical option. I can remarkably download and run (for a few minutes) cm12.1 but my sprint sim card is unrecognized (wierdly). I dont think its the modem or bootloader....ill update yall if i find a fix. Thanks P.I
Click to expand...
Click to collapse
Were you able to get it fixed? I'm probably going to go to a phonerepair shop this weekend or next week and see what they say or can do.

SM-G900F Downgrade problem

hello everyone
3 days ago I bought a Samsung Galaxy S5 SM-G900F and the pre-installed OS was Android 5.0 Lollipop
I wanted to downgrade to KitKat 4.4.2 but when I flashed the 4.4.2 firmware at the end of The Flash the phone Rebooted but but there was nothing on the screen and the phone was stuck on a boot loop so I reflashed the lollipop firmware and everything worked
The question is it possible to downgrade to kitkat 4.4.2 knowing that the preinstalled firmware was Android lollipop 5.0 for rooting purposes to keep knox 0x0
thank you very much

The problem with using Odin to downgrade is that it doesn't fully erase what was on there before, it just overwrites it......
Did you try to wipe data in recovery after the flash? Sometimes this is all that is needed.
If you did, and it didn't help, then it may be necessary to flash a pit file at the same time as the firmware.
Before you flash anything with Odin, go to download mode to double check which model you have.....There have been a number of cases recently where devices have been 'rebadged' so that what is displayed on the sticker under the battery does not match what is displayed in download mode (download mode is correct).......
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
The problem with using Odin........
Click to expand...
Click to collapse
yes it does show SM-G900F in download mode
where can I find a pit file
and just for info when I flashed the 4.4.2 firmware there was nothing on the screen even in download mode I could enter it because the keys combination is well known

You can get the pit file in post 3 here....
http://forum.xda-developers.com/showthread.php?t=2737448
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
You can get the pit file in post 3 here....
http://forum.xda-developers.com/showthread.php?t=2737448
Click to expand...
Click to collapse
Is there any risk on flashing the pit file
I just want to know before I proceed
Thank you very much for your help

There's a risk to any flash, but as long as your device matches the pit file you flash, you should be ok.....having said that, flashing a pit file carries a potentially greater risk than flashing a firmware/rom as it 're-maps' the data partitions.....In the case of a pit flash, if the flash is interrupted because of a power cut off or a premature device disconnection, the phone will be absolutely irrecoverably bricked......
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
There's a risk to any flash, but as long ............
Click to expand...
Click to collapse
the problem now is that when I flash kitkat 4.4.2 the phone does boot up but there is absolutly nothing on the screen
Do you have any idea?
thanks for all the help

When I downgraded from LP to KK, the first attempt was unsuccessful, the phone wouldn't boot at all
I did nothing else apart from flash it again exactly the same way, the next boot was fine and I was back on KK
You might need to factory reset after flashing, it's possible some apps are causing problems with the boot if they are not compatible from LP > KK

*Detection* said:
When I downgraded from LP to KK, ................
Click to expand...
Click to collapse
how can I do a factory reset without seeing anything on the screen?
the screen is completly black in all situations : normal boot - download mode - recovery mode

saktani said:
how can I do a factory reset without seeing anything on the screen?
the screen is completly black in all situations : normal boot - download mode - recovery mode
Click to expand...
Click to collapse
Factory reset first then
But if the screen is just black, not even the initial logo, then something else is wrong
Why flash KK anyway, there is a MM stock ROM port available for the G900F now

*Detection* said:
Factory reset first then
But if the screen is just black, not even the initial logo, then something else is wrong
Why flash KK anyway, there is a MM stock ROM port available for the G900F now
Click to expand...
Click to collapse
I know but I wanted to root the phone possibly without tripping KNOX

If I do trip knox what would I louse aside from warrenty?

saktani said:
If I do trip knox what would I louse aside from warrenty?
Click to expand...
Click to collapse
Nothing, I tripped mine ages back, everything still works
I read it might affect joining enterprise networks/domains, but never tried and don't use them
Try a different KK ROM, I assume you're trying the latest version atm?

It *might* affect OTA.....Some people say it does, others say it doesn't.....
But knox's main function is to prevent insecure devices from connecting to secure 'enterprise' business servers/networks.....basically if your employer expects you to be able to bring your device to work, and connect it as a business tool, you will no longer be able to do so.....*and* if the device was supplied by your employer, you could end up in all sorts of s**t with them too.....
http://i.imgur.com/rVnFwJM.jpg

Doesn't affect OTA, only custom (Root/Recovery) breaks OTA
Anyone saying tripped KNOX breaks OTA hasn't flashed back to 100% stock before trying to update OTA, unrooting doesn't reverse the custom status

Thank you very much for your help
I gave up I installed TWRP and flashed a custom rom
I couldn't resist any longer
I don't care about KNOX nor the warrenty anymore
Poeple are very kind in this forum
much appreciated for all your effort

Curious, why were you trying to downgrade to KK when Android 6 is available for g900f? I downgraded once myself (without pit file) to KK early on when LP was new, but Android 6 is a nice improvement over both imo. KK4.4.2 still has security issues, namely stagefright. If you're happy with custom rom, so be it, just curious if you were (or not) aware of Android 6 availability for your device, incl debloated, stock based knox-free ROMs.

saktani said:
I wanted to downgrade to KitKat 4.4.2 but when I flashed the 4.4.2 firmware at the end of The Flash the phone Rebooted but but there was nothing on the screen and the phone was stuck on a boot loop so I reflashed the lollipop firmware and everything worked
The question is it possible to downgrade to kitkat 4.4.2 knowing that the preinstalled firmware was Android lollipop 5.0 for rooting purposes to keep knox 0x0
thank you very much
Click to expand...
Click to collapse
Sorry, I know it is too late, but search is always your friend You would've had to follow these steps:
http://forum.xda-developers.com/showpost.php?p=57321061&postcount=1629

Help please, I bricked my J730f

Hi, I got a 2nd hand J7 pro with Android 7.0 on, no root or anything. I used Odin to install TWRP, and it worked just fine.
The next day I tried to install the official 8.1 update using odin, it took 4 minutes and passed on Odin . But the phone won't boot, it reaches 30% of Android updating progress then it reboots to a blue screen with a yellow triangle and an Android figure with an error no commend. I tried installing multiple ROMs, thinking that the ROM I installed wasn't the right one , no seccess.
After a while, I managed to reinstall TWRP with the touchscreen working, on an official 8.1 Android. but the phone is stuck at the black screen with Samsung J7 Pro. (Not boot looping, just stuck)
Please tell me if there is a hope to get it back, even to the 7.0 and how?
Thank you.

Can u boot to download mode? If yes try to downgrade to 7.1, or use twrp to wipe all the system and install one of the tw based roms avaiable here https://forum.xda-developers.com/galaxy-j7-2017/development
Edit: did you tried to wipe data and cache before boot? I've had a lot of struggle to boot samsung roms before doing that

Thank you for replying!
Yes I can boot to download mode. From what I read it's not easy to do downgrade.
No, I didn't wipe anything.
I'll try the TWRP method, I'm downloading this [ROM][8.0][TW][J730X]PrometheusLite A8+ Port V3.0 - EOL. And I'll keep you posted ?
Thanks again!

Doppler Effect said:
Thank you for replying!
Yes I can boot to download mode. From what I read it's not easy to do downgrade.
No, I didn't wipe anything.
I'll try the TWRP method, I'm downloading this [ROM][8.0][TW][J730X]PrometheusLite A8+ Port V3.0 - EOL. And I'll keep you posted
Thanks again!
Click to expand...
Click to collapse
I highly recommend you to get the note8 port first, since TW oreo roms may not work on some screens

Doppler Effect said:
Hi, I got a 2nd hand J7 pro with Android 7.0 on, no root or anything. I used Odin to install TWRP, and it worked just fine.
The next day I tried to install the official 8.1 update using odin, it took 4 minutes and passed on Odin . But the phone won't boot, it reaches 30% of Android updating progress then it reboots to a blue screen with a yellow triangle and an Android figure with an error no commend. I tried installing multiple ROMs, thinking that the ROM I installed wasn't the right one , no seccess.
After a while, I managed to reinstall TWRP with the touchscreen working, on an official 8.1 Android. but the phone is stuck at the black screen with Samsung J7 Pro. (Not boot looping, just stuck)
Please tell me if there is a hope to get it back, even to the 7.0 and how?
Thank you.
Click to expand...
Click to collapse
since you didnt root send it to samaung. make sure it says warranty 0x0 in download mode. i too bricked my phone but i did not trip the warranty and now i have a brand new phone with new display and everything

05Anjelly said:
since you didnt root send it to samaung. make sure it says warranty 0x0 in download mode. i too bricked my phone but i did not trip the warranty and now i have a brand new phone with new display and everything
Click to expand...
Click to collapse
It's not bricked so no need. As long as it boots to download and recovery mode it's possible to recover the device.
Warranty is already blown.
@Doppler Effect
Post a screen shot of download mode.

05Anjelly said:
since you didnt root send it to samaung. make sure it says warranty 0x0 in download mode. i too bricked my phone but i did not trip the warranty and now i have a brand new phone with new display and everything
Click to expand...
Click to collapse
oh yes i forgot. you should find your official firmware on sammobile.com

Somehow fixed!
I flashed the A8+ port, the touch didn't work but I was really happy seeing it boot, then I saw your 2nd reply.
The note8 port worked! with some bugs
I had to reroot using a SuperSU zip worked
The Sim is readable yet I can't make phone calls.
I think it has something to do with the CSC and OMC or something like that, working on it.
Thank you to everyone who has replied, much appreciated.