Hi! I've been using CM13 for my device until recently when I decided that I would like to go back to the stock samsung ROM. Having decided, I've tried to flash the SM-G900F firmware through Odin but it didn't work; I've tried 4 different firmware packages from different countries and android versions, yet they all resulted in failure. My phone is currently soft-bricked with access to (stock-samsung) recovery and download mode.
I've noticed, however, that on the back label, my device is the SM-G900F, but in download mode, it reads SM-G900P. I figured that maybe the Odin flashes were failing because my device is actually the G900P. I was wondering if I could try flash the G900P firmware through Odin, but I'm hesistant. If the flashing fails, will my device be hard-bricked?
It is a G900P if it says that in download mode, ignore the rest, they're faked
*Detection* said:
It is a G900P if it says that in download mode, ignore the rest, they're faked
Click to expand...
Click to collapse
THANK YOU!!
I've just flashed the SM-G900F Firmware and it works great!! It fixes issues I've had previously with CM13, probably because I was running a G900F rom on a G900P.
I still find it strange how my device could be so carelessly mislabeled.
THANK YOU AGAIN!
It's not carelessly mislabeled, it's purposely deceitfully mislabeled in order to sell a less popular model as one of the most popular models
Happening very regularly
And I assume you mean you flashed a G900P firmware, not G900F?
Related
I have a Samsung S5 G900F, bought from vodafone on payg. Long story short, it is under warranty, but when I took it to Samsung they said the knox had been tripped. I'm going to pursue this with them, as this phone is used by the mrs and (as far as we know) has never had custom software on it.
Anyway, it started randomly rebooting a while ago, and I tried updating the software with kies, which seemed to fix it for a while. It has now gotten progressively worse, to the point that it is not even getting past either the boot logo, or as part way through the boot process (samsung logo etc). Occasionally, after a cold start, it makes it to the OS, but then reboots shortly after.
I've now tried using odin to install the stock firmware (vodafone branded - G900FXXU1BOJ1_G900FVFG1BOJ1_G900FXXU1BOJ1_HOME.tar.md5). I've also installed philz custom recovery (tried twrp too), and then to install a custom rom. Ive tried cyanogen and phoenix. They install fine, but the phone continues to reboot when starting up. I've not yet managed to get to the OS for either custom rom.
The phoenix rom also came with a bootloader/modem package, which I have installed.
I've run out of ideas. It's probably a hardware fault. But is there anything else I can try before binning it?
Thanks.
KNOX is definitely tripped now even if it was not before (Custom ROMs, and Recovery trip KNOX)
Anyway, you could try flashing the G900F PIT file along with the stock ROM, and see if that helps, the PIT file will 100% delete and recreate the phones partitions, before flashing the ROM, so if it was a firmware bug, that should fix it, if it still does it after that, I'd say hardware
Google G900F PIT file
Add it to the PIT section in ODIN
Add the stock ROM to the PDA or AP section in ODIN
Flash and hope for the best
I tried the PIT file. It flashes successfully. However, the stock rom still fails with "auth SIZE" (cant remember the exact message). Does that mean I've used the wrong PIT? I can still successfully flash custom recovery and then a custom firmware, but the boot loops continue.
Can you double check in download mode, which model S5 is shows?
I expect it to be G900F, but a few people have had something other than what the sticker and box say
And as long as you downloaded the G900F PIT file, then you flashed the correct one
If everything matches G900F, and it's still doing it after flashing PIT, Custom and Stock, and stock is complaining about the wrong size, it looks like something corrupted your phones internal storage
There are manual ways to recreate partitions etc, but you'll have to search them out
I have a Canadian SM-N900W8 Note 3, that I wish to revert to complete stock, lollipop. I mostly have been using custom roms, and have recently reverted back to Stock using Kies. I rooted the device using this file.
After the rooting process, the softkeys do not function properly. The 'back' key does not function, and the 'menu' key acts as if I am holding it when I press it. The home key functions normally. Using the S-Pen, pressing on the softkeys, they work as intended. I have tried reflashing(and clearing cache) the stock rom from both kies, and sites like sammobile, but the issue persists.
After reading around, I found out that the file I used is not intended for my Canadian SM-N900W8, but for another model. The intended file for my device does not support lollipop, but only supports 4.4.2. After even more reading, I found the issue was related to the kernel. I flashed idlekernel, and the issue was resolved. The issue is, I want to have everything stock on the device, that includes stock rom, and kernel(or atleast appear stock). Upon booting with idlekernel, 2 messages, "KERNEL IS NOT SEANDROID ENFORCING" and "Set Warranty Bit: kernel" appear. I want to get rid of the messages.
So, my question is, is there a way to either:
1) Fix the softkeys without a custom rom/kernel(essentially reverse the root), or,
2) Get rid of the SEANDROID and warranty messages, while running idlekernel
Thanks!
Flash the latest stock ROM from sammobile.com using Odin.
audit13 said:
Flash the latest stock ROM from sammobile.com using Odin.
Click to expand...
Click to collapse
As said in the OP, I have already tried this, multiple times.
You used kies or Odin? Your post doesn't mention Odin.
The file linked in your post looks like the same file from chainfire's website which does support LP: https://autoroot.chainfire.eu
audit13 said:
You used kies or Odin? Your post doesn't mention Odin.
The file linked in your post looks like the same file from chainfire's website which does support LP: https://autoroot.chainfire.eu
Click to expand...
Click to collapse
I used both, at different attempts. Sorry if I was not clear.
Here is where I read the file incompatibilities
hlteub is for LP, hltevl is for MM.
The Mexican and Canadian Note 3 may be exactly the same model just like it is for the s3.
Did you try smartswitch?
You used the emergency firmware recovery option in kies?
Flashes of the stock ROM were successful in Odin? You performed a factory wipe before booting the stock ROM for the first time? You were flashing the latest LP rom?
Did you try different versions of Odin?
The SEAndroid message cannot be removed if the phone is running a custom recovery.
audit13 said:
hlteub is for LP, hltevl is for MM.
The Mexican and Canadian Note 3 may be exactly the same model just like it is for the s3.
Did you try smartswitch?
You used the emergency firmware recovery option in kies?
Flashes of the stock ROM were successful in Odin? You performed a factory wipe before booting the stock ROM for the first time? You were flashing the latest LP rom?
Did you try different versions of Odin?
The SEAndroid message cannot be removed if the phone is running a custom recovery.
Click to expand...
Click to collapse
If hlteub is for LP, and hltevl is for MM, should I ignore the android versions listed?
If they were the same model, why is there a softkey issue that this post is about?
Yes, I used the emergency recovery option in Kies.
All flashes I did were successful(Softkey issue is present always, even in setup wizard, and throughout the device).
Before installing new firmware, I factory wiped every time.
I have made sure what I flashed is latest, and have confirmed every time through Software Updates in about phone settings.
Smart Switch did nothing that Kies didnt already do.
Other people who have the same issue have said that flashing stock 4.4.2 fixes the issue(but upon upgrading back to 5.0, issue occurs), but I do not want to go back to that version.
Both the ub and vl are for the am-n900w8.
When rooting, it appears that you used a kk root file on an lp rom. Is this correct?
So the soft keys work on kk? If yes, did you flash to lp via Odin or did you run the ota update? Did you try flashing with a pit file?
audit13 said:
Both the ub and vl are for the am-n900w8.
When rooting, it appears that you used a kk root file on an lp rom. Is this correct?
So the soft keys work on kk? If yes, did you flash to lp via Odin or did you run the ota update? Did you try flashing with a pit file?
Click to expand...
Click to collapse
I initially tried the hlteub file(for lp). This is what caused the issue. I later tried the vl file, and nothing different happened. 4.4.2 works, but upon using the OTA update the issue comes back when on lollipop. Same goes for Odin. I have not tried using a PIT file, how would I go about finding one that I will need?
The issue has been resolved!
Here is the solution.
I have galaxy S5 with lollipop 5.0 showing model G900F under the battery sticker and in about device and other my phone info apps but when I switch to download mode it shows model G9006V. what is all this? what actually is my model. I tried to root using kingo pc file but it failed giving error "recovery is not seandroid". I recovered using samsung kies 3 now device is working but still can not go to recovery mode giving same error. When I try to update using device setting software update it gives error as "u have tried to modify ur OS in an un authorised way.
Hi!
Label in battery is the actual model. I think a wrong ROM was flashed.
Download from sammobile the right version ROM.
You can flash MM
Then flash TWRP recovery and flash superSUxxxxx.zip to root your phone
Reyse said:
Hi!
Label in battery is the actual model. I think a wrong ROM was flashed.
Download from sammobile the right version ROM.
You can flash MM
Then flash TWRP recovery and flash superSUxxxxx.zip to root your phone
Click to expand...
Click to collapse
If wrong ROM were flashed it would not match with the lablel. I tried to flash the firmware from sammobile that matches with the label i.e. G900F but it failed. When I connect with Kies it shows G900F but while upgrading with Kies I have to write G9006V and S/N otherwise Kies says model is incorrect. I think its actually G9006V flashed with G900F but I am confused.
Samsung Knox app shows baseband and bootloader as, G9006VZNU1B0E3. PDA G900FXXU1P0EC. CSC G900F0JV1POF1
iffi765 said:
If wrong ROM were flashed it would not match with the lablel. I tried to flash the firmware from sammobile that matches with the label i.e. G900F but it failed. When I connect with Kies it shows G900F but while upgrading with Kies I have to write G9006V and S/N otherwise Kies says model is incorrect. I think its actually G9006V flashed with G900F but I am confused.
Samsung Knox app shows baseband and bootloader as, G9006VZNU1B0E3. PDA G900FXXU1P0EC. CSC G900F0JV1POF1
Click to expand...
Click to collapse
Did you try with Odin?
G9006V
I had the same problem. I had lollipop 5.0 international version, with all Google apps and all features. In "about phone" was info that is G900F. Every G900F root, or stock upgrade via Odin failed. What I've found out Is that only I can do is flash stock rom of G9006v, and that is only I can do. And I done it. But when I done it, I had only English and Chinese option for language. And I could not install any Google application, I did not had Play store. Everything from Google was blocked. In "about phone" now shows the info G9006v. I root it, install aptoide, but what I need is Google can enyone know what is the problem. Also I found out, when I searched for network and country to I can download stock rom is,in application Phone info *SAMSUNG* was showed that my phone is from UAE, xsg network, but stock ROM from sammobile didn't work. And now in same application is showed that my phone is from China, network " unicom"... WTF!? I worked with so many fones,I never saw anything like this.
I have Maximum OvrDrive 7.1 installed on my Note4 I've downloaded 6.0.1 firmware from sammobile, tried to flash via Odin, install different roms all with fails. Last night I noticed while trying to flash in Odin the screen on my phone says it's the model 910t3. In the settings it says 910t. I have not tried downloading the t3 versions from sammobile and was wondering if this is the problem. I'm at work now and can not test this theory and was hoping one of you could help so I can upgrade when I get home. Thanks in advance
Nightcatfisher said:
I have Maximum OvrDrive 7.1 installed on my Note4 I've downloaded 6.0.1 firmware from sammobile, tried to flash via Odin, install different roms all with fails. Last night I noticed while trying to flash in Odin the screen on my phone says it's the model 910t3. In the settings it says 910t. I have not tried downloading the t3 versions from sammobile and was wondering if this is the problem. I'm at work now and can not test this theory and was hoping one of you could help so I can upgrade when I get home. Thanks in advance
Click to expand...
Click to collapse
Whatever it says in download mode is the correct model of your phone. Go by download mode not settings
I've been using my S8 G950F for one week (Nougat Stock, don't recall which specific rom, no root nor nothing) until it suddenly froze, tried to reboot but couldn't get past the Samsung logo screen. I tried to flash a stock firmware using Odin but got a Fail with the Device Info error which I could successfully fix with the so well known trick of getting back to download mode real quick.
Now I can flash any rom I want (downloaded from Updato) without any issues (PASS on odin), but no matter what ROM I flash I still can't get past the Samsung logo. I tried flashing both Nougat (AQF7 and AQL5), Oreo (CRAP, CRC7 and CRD7) using Oding 3.12.3 and 3.13.1 (for Oreo roms).
I also tried using Prince Comsy's Odin and once again got the Device Info error but using the same trick as before I could flash a Nougat rom but still can't get past the Samsung logo.
Is there anything I'm doing wrong? Should I flash any particular ROM or in a specific order? Should I try with other Odin version? KIES doesn't detect my device.
Any help is greatly appreciated! I just don't know what else to try and I can't find nobody nobody that has had the same issue I'm facing.
Thanks in advance! Any additional info you may need just ask me!
PS: one thing that caught my attention is that when I go to download mode it says: Knox 0x0 and "System Status: Custom". Is that alright?