Related
Hi guys, I bought a Vodafone-branded unlocked S7 here in Ireland.
Never used it with Vodafone and I've never received any updates for it.
OTA, Smart switch and Updato they all say my device is up to date but I can see there are more recent firmwares for my CSC.
Here are my details:
PDA: G930FXXU1DQEI
CSC Version: G930FVFG1DQE3
BASEBAND Version: G930FXXU1BPJJ
CSC Code: VDI
Am I missing something or is it possible that under VDI there are more update channels and my phone is not supposed to receive the other updates?
It's working fine and everything, I'm only concerned about security patches to be honest.
Hope you can give me a hint.
Cheers guys.
Boot into download mode and double check it is definitely the G930F
If it is, then just flash the latest firmware with ODIN 3.12.3 or newer
*Detection* said:
Boot into download mode and double check it is definitely the G930F
If it is, then just flash the latest firmware with ODIN 3.12.3 or newer
Click to expand...
Click to collapse
It is definitely G930F. Would I be safe using HOME_CSC in order not to lose any data?
Also would you have any idea on why this is happening?
Thanks!
alediaferia said:
It is definitely G930F. Would I be safe using HOME_CSC in order not to lose any data?
Also would you have any idea on why this is happening?
Thanks!
Click to expand...
Click to collapse
If the device is showing as "Custom" system status it won't OTA
Otherwise no idea, and yes just use HOME_CSC, it'll update it as if you got an OTA
*Detection* said:
If the device is showing as "Custom" system status it won't OTA
Otherwise no idea, and yes just use HOME_CSC, it'll update it as if you got an OTA
Click to expand...
Click to collapse
Thanks for your help. I guess I'll end up flashing the firmware manually. System status is showing as original BTW.
Any chance I might have screwed up accidentally denying an update once and losing the "updateability" of my device forever? Although it's weird Updato is detecting my device as up-to-date too. This story is really weird to me.
Thanks again anyway!
alediaferia said:
Thanks for your help. I guess I'll end up flashing the firmware manually. System status is showing as original BTW.
Any chance I might have screwed up accidentally denying an update once and losing the "updateability" of my device forever? Although it's weird Updato is detecting my device as up-to-date too. This story is really weird to me.
Thanks again anyway!
Click to expand...
Click to collapse
Actually it's usually the other way around, people trying to deny the updates and asking for help to permanently disable them, so it's unlikely you broke it
Possibly just a bug of some sort, or the firmware you think you are on is not the actual firmware?
What security patch does it state in settings > about > software info > scroll to bottom
The updato app is getting extremely bad reviews lately so I wouldn't trust that anyway
A lot of people update manually, this isn't the first case I've seen with your problem either so I wouldn't worry too much, just flash it yourself
*Detection* said:
Actually it's usually the other way around, people trying to deny the updates and asking for help to permanently disable them, so it's unlikely you broke it
Possibly just a bug of some sort, or the firmware you think you are on is not the actual firmware?
What security patch does it state in settings > about > software info > scroll to bottom
The updato app is getting extremely bad reviews lately so I wouldn't trust that anyway
A lot of people update manually, this isn't the first case I've seen with your problem either so I wouldn't worry too much, just flash it yourself
Click to expand...
Click to collapse
Security patch level is May 2017.
The firmware the phone says I'm on in the software update section reconciles with what Phone INFO detects which is the firmware released for VDI the 2017-06-11 on sammobile.
alediaferia said:
Security patch level is May 2017.
The firmware the phone says I'm on in the software update section reconciles with what Phone INFO detects which is the firmware released for VDI the 2017-06-11 on sammobile.
Click to expand...
Click to collapse
Yea definitely a strange one, should be seeing an update
Could be anything though, some change within the OS that's not reporting something to the update servers correctly
The flash should fix it, if not, backup and factory reset for the next OTA, or just keep flashing manually
*Detection* said:
Yea definitely a strange one, should be seeing an update
Could be anything though, some change within the OS that's not reporting something to the update servers correctly
The flash should fix it, if not, backup and factory reset for the next OTA, or just keep flashing manually
Click to expand...
Click to collapse
Sorry for going back to this. I just want to clarify another doubt I have. My phone is Vodafone-branded but I've always used it with another carrier. Is this affecting my ability to receive either OTA or updates at all using smart switch ?
Thanks!
alediaferia said:
Sorry for going back to this. I just want to clarify another doubt I have. My phone is Vodafone-branded but I've always used it with another carrier. Is this affecting my ability to receive either OTA or updates at all using smart switch ?
Thanks!
Click to expand...
Click to collapse
You can test this by borrowing a Vodafone sim.
Or better just backup and flash an unlocked stock Rom to your device.
Aashish.007 said:
You can test this by borrowing a Vodafone sim.
Or better just backup and flash an unlocked stock Rom to your device.
Click to expand...
Click to collapse
Hi, I'm finding it hard to get someone with a Vodafone sim. Anyway, do I risk anything flashing an unbranded firmware? Knox tripping, custom status showing up or other not-so-nice things ?
alediaferia said:
Hi, I'm finding it hard to get someone with a Vodafone sim. Anyway, do I risk anything flashing an unbranded firmware? Knox tripping, custom status showing up or other not-so-nice things ?
Click to expand...
Click to collapse
I guess if the boot loader is unlocked then you're good to go.
---------- Post added at 10:14 PM ---------- Previous post was at 10:11 PM ----------
alediaferia said:
Hi, I'm finding it hard to get someone with a Vodafone sim. Anyway, do I risk anything flashing an unbranded firmware? Knox tripping, custom status showing up or other not-so-nice things ?
Click to expand...
Click to collapse
And Stock firmware won't trip Knox.
For the sake of completeness, I have explained my solution in here: https://forum.xda-developers.com/galaxy-s7/help/wrong-modem-cp-version-t3743284
Thanks everyone for your help
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.
solamente said:
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.
Click to expand...
Click to collapse
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.
DeadRatGames said:
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.
Click to expand...
Click to collapse
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.
solamente said:
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.
Click to expand...
Click to collapse
Do I really need to wait 168 hours lol?
DeadRatGames said:
Do I really need to wait 168 hours lol?
Click to expand...
Click to collapse
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.
solamente said:
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.
Click to expand...
Click to collapse
How do I downgrade though?
DeadRatGames said:
How do I downgrade though?
Click to expand...
Click to collapse
At this time its impossible to downgrade from a binary 3 towards 2 or from 2 to 1.
You can only upgrade, Samsung has blocked the downgrading from a higher to a lower binary, therefore it is useless to try it with Odin, it won't succeed.
Maybe someone else knows a way around to downgrade, but I don't.
DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)
BlackMesa123 said:
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)
Click to expand...
Click to collapse
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?
DeadRatGames said:
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?
Click to expand...
Click to collapse
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone
BlackMesa123 said:
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone
Click to expand...
Click to collapse
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.
Reformat system.
DeadRatGames said:
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.
Click to expand...
Click to collapse
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.
solamente said:
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.
Click to expand...
Click to collapse
Ok. Thanks
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
same questions
vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E
amazing. youre the man. cheers.
samalderon said:
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E
Click to expand...
Click to collapse
omg youre the best. thanks so much.
the phone was initially on android Nougat 7.1.1, I updated it officially to android Oreo
after that, I flashed new STOCK ROM Oreo too, by Odin for the first time for this phone after unpacking and updating it from Nougat to Oreo
now I cannot flash anything by Odin TWRP, ROOT, STOCK ROM, COMBINATION FILE .... nothing pass
I can't even flash any other stock ROM beside the one i flashed before, either it's the same android version or not
odin always fail
I Waited 190 hours (more than 7 days) of continuous up time without restarting to have access and Remove FRP Lock but no luck at all, still the same
SEE ATTACHMENTS For Photos
SM-A530F/DS
Odin3 v3.13.1
Android 8.0.0 Oreo
Country / Region : Morocco (MWD)
PDA : A530FXXS4BSB1
Product Code : MWD
CSC : A530FOJM4BSB1
Phone : A530FXXU4BRL8
COMBINATION_OXM_FA71_A530FXXU4ASB1_BoxWares.tar
Which file are you trying to flash?
If I'm not wrong you could flash any firmware with version 4 or upper. For example you could not flash A530FXXU3BSA3 (Version 3) but it should be fine with A530FXXS4BSB1 (Version 4).
emovere said:
Which file are you trying to flash?
If I'm not wrong you could flash any firmware with version 4 or upper. For example you could not flash A530FXXU3BSA3 (Version 3) but it should be fine with A530FXXS4BSB1 (Version 4).
Click to expand...
Click to collapse
It looks like your trying to down grade to a version 3 and you can't do that.
Sorry wrong person.
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
Pro Cal said:
the phone was initially on android Nougat 7.1.1, I updated it officially to android Oreo
after that, I flashed new STOCK ROM Oreo too, by Odin for the first time for this phone after unpacking and updating it from Nougat to Oreo
now I cannot flash anything by Odin TWRP, ROOT, STOCK ROM, COMBINATION FILE .... nothing pass
I can't even flash any other stock ROM beside the one i flashed before, either it's the same android version or not
odin always fail
I Waited 190 hours (more than 7 days) of continuous up time without restarting to have access and Remove FRP Lock but no luck at all, still the same
SEE ATTACHMENTS For Photos
SM-A530F/DS
Odin3 v3.13.1
Android 8.0.0 Oreo
Country / Region : Morocco (MWD)
PDA : A530FXXS4BSB1
Product Code : MWD
CSC : A530FOJM4BSB1
Phone : A530FXXU4BRL8
COMBINATION_OXM_FA71_A530FXXU4ASB1_BoxWares.tar
Click to expand...
Click to collapse
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
Samsung updated the binary from Nougat to oreo. Its impossible to downgrade. Its thr same with pie, you can downgrade to oreo for now as it still has the same binary on the latest security patch.
Dantar0 said:
Samsung updated the binary from Nougat to oreo. Its impossible to downgrade. Its thr same with pie, you can downgrade to oreo for now as it still has the same binary on the latest security patch.
Click to expand...
Click to collapse
You can from Pie to Oreo some country received Oreo now so they come with BL 4
emovere said:
Which file are you trying to flash?
If I'm not wrong you could flash any firmware with version 4 or upper. For example you could not flash A530FXXU3BSA3 (Version 3) but it should be fine with A530FXXS4BSB1 (Version 4).
Click to expand...
Click to collapse
thanks a lot for the feedback, appreciated
if I understood it correctly the version number is the tow characters that comes after XX like U3 or S4 right ?
how to know the version number you mentioned exactly ?
and what about TWRP then, why even TWRP won't pass
mchlbenner said:
It looks like your trying to down grade to a version 3 and you can't do that.
Sorry wrong person.
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
Click to expand...
Click to collapse
actually I already did waited 190 of continuous up time, then after directly tried to flash TWRP and still no pass in Odin fail
I did tried to flash stock rom for 7.1.1 but even with same current version "Oreo" nothing pass
how can I know the version you mentioned please ?
Dantar0 said:
Samsung updated the binary from Nougat to oreo. Its impossible to downgrade. Its thr same with pie, you can downgrade to oreo for now as it still has the same binary on the latest security patch.
Click to expand...
Click to collapse
how to know please the exact binary version or locate ot on the PDA File for example PDA : A530FXXS4BSB1
Pro Cal said:
how to know please the exact binary version or locate ot on the PDA File for example PDA : A530FXXS4BSB1
Click to expand...
Click to collapse
For that, the binary is 4 (after the FXXS)
https://www.sammobile.com/firmwares/galaxy-a8/SM-A530F/MWD/
As you can see, Samsung updated the binary on the latest security update for your region. Its impossible to downgrade to a previous OS due to having different binaries. You'll also find that even though it's oreo, the binary updated from the January security patch to February's. Probably to make way for android 9 One UI.
The only option is to flash oreo but with the February security patch
Dantar0 said:
For that, the binary is 4 (after the FXXS)
https://www.sammobile.com/firmwares/galaxy-a8/SM-A530F/MWD/
As you can see, Samsung updated the binary on the latest security update for your region. Its impossible to downgrade to a previous OS due to having different binaries. You'll also find that even though it's oreo, the binary updated from the January security patch to February's. Probably to make way for android 9 One UI.
The only option is to flash oreo but with the February security patch
Click to expand...
Click to collapse
many thanks for the feedback and effort
so basically it means nougat is out of the question
and tell me please why country si important, I can flash any other firmware for another country as longer it the same binary version, right ?
and what about root for this binary version or TWRP why it won't pass either ?
Pro Cal said:
many thanks for the feedback and effort
so basically it means nougat is out of the question
and tell me please why country si important, I can flash any other firmware for another country as longer it the same binary version, right ?
and what about root for this binary version or TWRP why it won't pass either ?
Click to expand...
Click to collapse
You can flash a different regions firmware as long as you download the right variation. (SM-A530F)
Sorry but I don't know much about rooting this phone though
Pro Cal said:
thanks a lot for the feedback, appreciated
if I understood it correctly the version number is the tow characters that comes after XX like U3 or S4 right ?
how to know the version number you mentioned exactly ?
and what about TWRP then, why even TWRP won't pass
Click to expand...
Click to collapse
Read post if you had read before you jump this would not have happened.
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
mchlbenner said:
Read post if you had read before you jump this would not have happened.
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
Click to expand...
Click to collapse
I did read it and did answer you but it's you who didn't read mine otherwise you wouldnt repeat the same thing
*********************
actually I already did waited 190 of continuous up time, then after directly tried to flash TWRP and still no pass in Odin fail
I did tried to flash stock ROM for 7.1.1 but even with same current version "Oreo" nothing pass
Pro Cal said:
I did read it and did answer you but it's you who didn't read mine otherwise you wouldnt repeat the same thing
*********************
actually I already did waited 190 of continuous up time, then after directly tried to flash TWRP and still no pass in Odin fail
I did tried to flash stock ROM for 7.1.1 but even with same current version "Oreo" nothing pass
Click to expand...
Click to collapse
Is your phone branded.
Post this info screenshot example .
I will see if I can figure this out.
mchlbenner said:
Is your phone branded.
Post this info screenshot example .
I will see if I can figure this out.
Click to expand...
Click to collapse
Nop i dnt think so
Pro Cal said:
Nop i dnt think so
Click to expand...
Click to collapse
That as far that you can down grade to.
I recently purchased a P40 Pro (ELS-N04 or ELS-lgrp4 base) which had .148 firmware on it. I used the firmware finder to find an approved firmware for my device: ELS-LGRP6-OVS 10.1.0.136 and performed the downgrade using the hisuite method. My device now reboots every 20 seconds and has no cellular connectivity. Can anyone point me in the right direction to correct this please?
I think if someone pointed me to the correct firmware, I could probably fix this through fastboot... Maybe?
Thank you.
Fastboot wont work unfortunatley. What you can do is go to androidhost.ru and find your firmware ( can be the same aswell ) Its roughly a 3 - 4 gb download.
1. Download the firmware of your choice from the link below:
https://androidhost.ru/
2. Put the ''dload'' folder found in the zip at the root of a usb stick
3. Attach the usb stick to you phone. I take it anyone knows how to do it. Shutdown your phone. Then press and hold volume up and power button until you get to the recovery menu
4. Select Update mode, then select Memory card/OTG update mode
5. The phone will verify and install the firmware
Make sure that your Emui 10.0.1.***(C********) Matches otherwise the update will fail.
Is there an easy way to identify the "correct" firmware? It looks like https://androidhost.ru/ only has one file available which isn't the same model version as mine.
viffer_man said:
Is there an easy way to identify the "correct" firmware? It looks like https://androidhost.ru/ only has one file available which isn't the same model version as mine.
Click to expand...
Click to collapse
Can u post your Device info by anychance then I can try to find a firmware for your phone
Billabomb75 said:
Can u post your Device info by anychance then I can try to find a firmware for your phone
Click to expand...
Click to collapse
They are replacing my mainboard under warranty. As soon as I get it back, I will post the details and hopefully you can assist in identifying the correct firmware to downgrade?
Thanks!
Deleted - Duplicate
OK, I have my phone back... Can someone please tell me which firmware I should use to downgrade please?
Current version loaded:
Base Software Version: ELS-LGRP4-OVS 10.1.0.148
Cust Software Version: ESL-N04-CUST 10.1.0.7(C792)
Preload Software Version: ELS-N04-PRELOAD 10.1.0.1(C792R3)
Thanks!
Billabomb75 said:
Can u post your Device info by anychance then I can try to find a firmware for your phone
Click to expand...
Click to collapse
viffer_man said:
OK, I have my phone back... Can someone please tell me which firmware I should use to downgrade please?
Current version loaded:
Base Software Version: ELS-LGRP4-OVS 10.1.0.148
Cust Software Version: ESL-N04-CUST 10.1.0.7(C792)
Preload Software Version: ELS-N04-PRELOAD 10.1.0.1(C792R3)
Thanks!
Click to expand...
Click to collapse
Think you should be fine now with that frimware to load GMS
Billabomb75 said:
Think you should be fine now with that firmware to load GMS
Click to expand...
Click to collapse
No, I still get the failure when launching the LZPlay app...
viffer_man said:
No, I still get the failure when launching the LZPlay app...
Click to expand...
Click to collapse
Ok, I managed to downgrade to .131 after throwing caution to the wind lol.
Hello good someone from the forum can help me? I have a huawei p40 lite 5g firmware cdy-lgrp2-ovs 10.1.1.131 model cdy-nx9a, is there any firmware version to be able to install google services on is model? Thank you
Hey everyone hope you're all well. I have an s8 plus that's not booting. Here's the events that transpired....
My nephew wanted it wiped so I went into recovery and it immediately started to install an update for some reason and wouldn't boot, so I told his brother to flash a stock ROM which he did and booted fine, but with one issue, it showed as 16gb instead of 64gb. At this point I downloaded a pit file and flashed it. I then flashed the stock ROM and it won't get past the Samsung logo.
This is the stock ROM I flashed, AP_G955FXXSADTI1_CL18920278_QB34109287_REV00_user_low_ship_meta_OS9
I'm guessing I need to flash the correct pit file and then the stock ROM?
Any advice would be appreciated
Thanks!
thedan55 said:
Hey everyone hope you're all well. I have an s8 plus that's not booting. Here's the events that transpired....
My nephew wanted it wiped so I went into recovery and it immediately started to install an update for some reason and wouldn't boot, so I told his brother to flash a stock ROM which he did and booted fine, but with one issue, it showed as 16gb instead of 64gb. At this point I downloaded a pit file and flashed it. I then flashed the stock ROM and it won't get past the Samsung logo.
This is the stock ROM I flashed, AP_G955FXXSADTI1_CL18920278_QB34109287_REV00_user_low_ship_meta_OS9
I'm guessing I need to flash the correct pit file and then the stock ROM?
Any advice would be appreciated
Thanks!
Click to expand...
Click to collapse
Flash full firmware not just AP file. Flashing AP file only is more than likely the reason for difference in storage size.
No need for pit file. If it is needed it can be exacted from the firmware that you have downloaded.
I did flash all 4 files not just the ap. I only wanted to show the version etc
Now when I try to flash Odin says failed
What Odin version are you using
What errors in Odin
Can you post a copy of download mode and error in Odin
spawnlives said:
What Odin version are you using
What errors in Odin
Can you post a copy of download mode and error in Odin
Click to expand...
Click to collapse
Absolutely. Odin3 3.13
I've also attached a picture of the rom files. For some reason there's 2 CSC files. I tried using both but same issue.
thedan55 said:
Absolutely. Odin3 3.13
I've also attached a picture of the rom files. For some reason there's 2 CSC files. I tried using both but same issue.
Click to expand...
Click to collapse
1. CSC files
CSC file will wipe all apps and data ( same as out of the box )
HOME_CSC file will keep apps and data
2. The reason Odin is failing is you are trying to downgrade your firmware.
You are on bootloader version 11 the firmware you are flashing is on version 10. You can check in download mode to check bootloader version. There will be a line saying AP SWREV. The number after the letter B is your bootloader number.
Also in download mode down the bottom ( in red ) will tell the reason why it is failing.
You will have to find what firmware was flash before or wait for samsung to upgrade it's bootloader version.
spawnlives said:
1. CSC files
CSC file will wipe all apps and data ( same as out of the box )
HOME_CSC file will keep apps and data
2. The reason Odin is failing is you are trying to downgrade your firmware.
You are on bootloader version 11 the firmware you are flashing is on version 10. You can check in download mode to check bootloader version. There will be a line saying AP SWREV. The number after the letter B is your bootloader number.
Also in download mode down the bottom ( in red ) will tell the reason why it is failing.
You will have to find what firmware was flash before or wait for samsung to upgrade it's bootloader version.
Click to expand...
Click to collapse
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Why do I get this message every day? Throw the darn thing out already.
thedan55 said:
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Click to expand...
Click to collapse
Flashing the pit file should only fix the partition size and is generally not needed. Flashing the wrong pit file will cause issues. Doesn't effect the issue of trying to downgrading firmware.
As far I'm aware official samsung firmware is up to bootloader 10. Firmware should be downloaded from official site like sammobile or updato or pc apps like samfirm or frija
In regards to bootloader version ( official firmware ) it can be found in the firmware being downloaded.
Bootloader version will be the fifth number/letter from the right of firmware name.
eg:
G955FXXSADTI1 - A - bootloader version 10. I'm assuming the next bootloader version number will start with B
G955FXXU9DTF1 - 9 - bootloader version 9
The higher the number the higher the bootloader version.
Due to samsung anti róll back bootloader version cannot be downgraded.
Buy your nephew a damn phone
thedan55 said:
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Click to expand...
Click to collapse
pego99 said:
Buy your nephew a damn phone
Click to expand...
Click to collapse
I did buy him this phone. Just because it's a little messed up right now doesn't mean I should just thrown it out. This entire forum is dedicated to invigorating devices and keeping them going. XDA didn't accept the philosophy of throwing out devices when they can be repaired. I've been here long enough to know that.
Ffs people are still developing for the hp touchpad and m7 Windows devices!
Unsubscribe from this thread mate. Delete your replies so you don't notifications.
There's no need for your unhelpful comments when others are trying to be of assistance.
spawnlives said:
Flashing the pit file should only fix the partition size and is generally not needed. Flashing the wrong pit file will cause issues. Doesn't effect the issue of trying to downgrading firmware.
As far I'm aware official samsung firmware is up to bootloader 10. Firmware should be downloaded from official site like sammobile or updato or pc apps like samfirm or frija
In regards to bootloader version ( official firmware ) it can be found in the firmware being downloaded.
Bootloader version will be the fifth number/letter from the right of firmware name.
eg:
G955FXXSADTI1 - A - bootloader version 10. I'm assuming the next bootloader version number will start with B
G955FXXU9DTF1 - 9 - bootloader version 9
The higher the number the higher the bootloader version.
Due to samsung anti róll back bootloader version cannot be downgraded.
Click to expand...
Click to collapse
Thank you very much for your replies. It's very much appreciated mate.
I did flash the pit file and subsequently got errors in odin. I want aware that I was trying to downgrade. I've download from official site and will try flashing today.
Again thanks for the help. Been a while since I've had to do this lol I think the last device I was rooting and roming was my note 3! The support for it is still going strong though!
Cheers
I guess at some point its best to move on. My grandsons S8 had the digitizer go bad tried to fix unsuccessfully bought him a used on on fleabay for $150.
@spawnlives thank you very much. Phone is back up running perfectly. Appreciate it mate
@pego99 that's a judgment call. Fair enough buying an s8 screen is 100 and new is 150 it would be reasonable to buy a new device. However this was a software issue which costs nothing to fix. Your posts in this thread are redundant and useless.
thedan55 said:
@spawnlives thank you very much. Phone is back up running perfectly. Appreciate it mate
@pego99 that's a judgment call. Fair enough buying an s8 screen is 100 and new is 150 it would be reasonable to buy a new device. However this was a software issue which costs nothing to fix. Your posts in this thread are redundant and useless.
Click to expand...
Click to collapse
OK it costs nothing money wise but time but time is valuable. i.e. If you spend the next 6 months on this has it cost anything? Nope no out of pocket but a lot of time and nephew has no phone to use. BTW If you bought the phone in working condition how did it get screwed up anyway?
pego99 said:
OK it costs nothing money wise but time but time is valuable. i.e. If you spend the next 6 months on this has it cost anything? Nope no out of pocket but a lot of time and nephew has no phone to use. BTW If you bought the phone in working condition how did it get screwed up anyway?
Click to expand...
Click to collapse
It took less than an hour to fix this phone, that's a cost I can stomach.
if you had actually READ the post instead of commenting asinine remarks them you would know how the phone for corrupted in the first place.
Please stop replying to this now.