Related
Hello friends I am on the latest Russian 4.3 firmware and am flashing the PIT and the old bootloader and then a stock 4.2.2 indian Firmware to check if the warranty bit can be reinstated !!!!!!!! Because here in India the service centers dont know or dont bother to check the hidden counter.......
I know I am taking a risk but opening this thread so that I can post my observations and maybe we can work something out.....fingers crossed!!!!!
UPDATE 1 : Was Unable to flash the MG1 bootloader getting failed on odin and unsupported !!!!!
UPDATE 2 : Flashed UBUBMH1 4.2.2 successfully no IMEI loss all working fine so yes we can downgrade to 4.2.2
The bootloader though remains unchanged and shows device status as custom!!!!!
UPDATE 3 : Flashed the leaked 4.3 and device status says official binary also official only warranty bit says 1
UPDATE 4 : Device is able to check for OTA updates and not given an error saying your device has been modified
**********************************************************************************
STEPS TO REVERT I9500 TO 4.2.2 WITH OFFICIAL STATUS
**********************************************************************************
1) Download South African FW 4.2.2 http://samsung-updates.com/details/14135/Galaxy_S_4_Exynos_Octa/GT-I9500/XFE/I9500XXUBMH1.html
2) Go to recovery wipe data factory reset and wipe cache and then flash the firmware that you downloaded above
NOTE : If you are on the russian 4.3 and having issues flashing this FW then first flash the leaked 4.3 from here
http://forum.xda-developers.com/showthread.php?t=2488155
3) After flashing leaked 4.3 go to settings and check device status it should say official
4)now go to download mode and flash the 4.2.2 rom you downloaded
5) NOTE : IF YOU ARE STILL HAVING TROUBLE GOING BACK TO 4.2.2 YOU CAN DOWNLOAD THE
ATTACHED PIT FILE AND FLASH IT ALONG WITH THE 4.2.2 ROM
IN ODIN SELECT THE PIT FILE IN PIT SECTION AND SELECT THE FW IN PDA SECTION
AS A LAST RESORT IF NOTHING WORKS THEN FOLLOW THE STEPS FROM STEP 1 AGAIN USING ODIN
1.85 attached below!!!!!!
PLEASE EXTRACT THE ODIN AND PIT FILES BEFORE USING.
Trying other things now!!!!!!!
I will be posting detailed steps with links soon!!!!!!!
Hey,
When I was in 4.2.2, root and kernels and Cwm were already flashed so my binary and system were custom. But when I flashed 4.3 leak all become official and warranty bit: 0, I was happy that I kept my warranty.
But now, my warranty bit is 1 because I flashed cf root. And downgrading to 4.2.2 and flashing again 4.3 didn't change anything. I really want to know how to remove that knox bootloader.
Envoyé de mon GT-I9500 en utilisant Tapatalk
speed s said:
Hey,
When I was in 4.2.2, root and kernels and Cwm were already flashed so my binary and system were custom. But when I flashed 4.3 leak all become official and warranty bit: 0, I was happy that I kept my warranty.
But now, my warranty bit is 1 because I flashed cf root. And downgrading to 4.2.2 and flashing again 4.3 didn't change anything. I really want to know how to remove that knox bootloader.
Envoyé de mon GT-I9500 en utilisant Tapatalk
Click to expand...
Click to collapse
Well as the title states right now there is no way to do that its been three hrs i have tried all sorts of crazy things to go back to the old bootloader but it just refuses to flash so we will have to wait.....I created this thread so that at least we can have the binary and status official because most of the places that will be ok like in india if i go to the svc center and it says official all will be ok!!!!
hey @hypergamer1231,
what is the procedure to revert back to 4.2.2, am currently CF-Rooted on 4.3?
can you please tell me what all things are required ?(will be thankful if you provide the links)
and after that again upgrading to 4.3 will i be able to use Knox container app???
i don't have any problem with bit 1, just want to use container app !
Thanks in advance
nish983 said:
hey @hypergamer1231,
what is the procedure to revert back to 4.2.2, am currently CF-Rooted on 4.3?
can you please tell me what all things are required ?(will be thankful if you provide the links)
and after that again upgrading to 4.3 will i be able to use Knox container app???
i don't have any problem with bit 1, just want to use container app !
Thanks in advance
Click to expand...
Click to collapse
Sure mate OP updated with detailed steps let me know if it works and also if you dont root after gaining official status knox should work as well!!!!!!!
hypergamer1231 said:
Hello friends I am on the latest Russian 4.3 firmware and am flashing the PIT and the old bootloader and then a stock 4.2.2 indian Firmware to check if the warranty bit can be reinstated !!!!!!!! Because here in India the service centers dont know or dont bother to check the hidden counter.......
I know I am taking a risk but opening this thread so that I can post my observations and maybe we can work something out.....fingers crossed!!!!!
UPDATE 1 : Was Unable to flash the MG1 bootloader getting failed on odin and unsupported !!!!!
UPDATE 2 : Flashed UBUBMH1 4.2.2 successfully no IMEI loss all working fine so yes we can downgrade to 4.2.2
The bootloader though remains unchanged and shows device status as custom!!!!!
UPDATE 3 : Flashed the leaked 4.3 and device status says official binary also official only warranty bit says 1
UPDATE 4 : Device is able to check for OTA updates and not given an error saying your device has been modified
**********************************************************************************
STEPS TO REVERT I9500 TO 4.2.2 WITH OFFICIAL STATUS
**********************************************************************************
1) Download South African FW 4.2.2 http://samsung-updates.com/details/14135/Galaxy_S_4_Exynos_Octa/GT-I9500/XFE/I9500XXUBMH1.html
2) Go to recovery wipe data factory reset and wipe cache and then flash the firmware that you downloaded above
NOTE : If you are on the russian 4.3 and having issues flashing this FW then first flash the leaked 4.3 from here
http://forum.xda-developers.com/showthread.php?t=2488155
3) After flashing leaked 4.3 go to settings and check device status it should say official
4)now go to download mode and flash the 4.2.2 rom you downloaded
5) NOTE : IF YOU ARE STILL HAVING TROUBLE GOING BACK TO 4.2.2 YOU CAN DOWNLOAD THE
ATTACHED PIT FILE AND FLASH IT ALONG WITH THE 4.2.2 ROM
IN ODIN SELECT THE PIT FILE IN PIT SECTION AND SELECT THE FW IN PDA SECTION
AS A LAST RESORT IF NOTHING WORKS THEN FOLLOW THE STEPS FROM STEP 1 AGAIN USING ODIN
1.85 attached below!!!!!!
PLEASE EXTRACT THE ODIN AND PIT FILES BEFORE USING.
Trying other things now!!!!!!!
I will be posting detailed steps with links soon!!!!!!!
Click to expand...
Click to collapse
Thks 4 this tutorial, Perfect in My S4 TTT Region.
Congrats Bro
Just got the official 4.3 OTA update (INS). Not going to update coz of warranty bit. It should be 0 when I update, but as soon as I root it would become 1. Will be waiting for AOSP or MIUI for i9500, say a month or so. Then will use it and update to 4.3 next yr (or maybe 4.4 then?) When warranty anyway would expire.
Edit - this is similar to Knox on i9505, hence even downgrading your official software doesn't remove the boot loader, and in fact triggers it.
yashvchauhan said:
Just got the official 4.3 OTA update (INS). Not going to update coz of warranty bit. It should be 0 when I update, but as soon as I root it would become 1. Will be waiting for AOSP or MIUI for i9500, say a month or so. Then will use it and update to 4.3 next yr (or maybe 4.4 then?) When warranty anyway would expire.
Edit - this is similar to Knox on i9505, hence even downgrading your official software doesn't remove the boot loader, and in fact triggers it.
Click to expand...
Click to collapse
well thanks for the headsup abt the indian fw dloading it now!!! Also in india most of the svc centers wont trouble you because they hardly even check!!!!
sorry wrong thread post edited
hypergamer1231 said:
well thanks for the headsup abt the indian fw dloading it now!!! Also in india most of the svc centers wont trouble you because they hardly even check!!!!
Click to expand...
Click to collapse
in india we dont have locked bootloader. is it is safe to flash the 4.3 without bootloder provided in pre rooted thread.
thanks
mateen5997 said:
in we dont have locked bootloader. is it is safe to flash the 4.3 without bootloder provided in pre rooted thread.
thanks
Click to expand...
Click to collapse
i am not sure but thats a very good idea i would have tried that but i am already on the new bootloader if you can try that would be great make sure you have a nandroid backup and efs backup!!!!!! Do it at your own risk at the most u will have basic issues try and revert if poss
thank you,it works like a charme even if a had the russian 4.3, no need to go back to the indian version ,just used odin 1.85 with the.PIT and the south african 4.2.2
My experience:
My GT-I9505 was a Hongkong version with its stock firmware version I9505ZHUAME3, then OTA to ZHUDMI1.
After flashed the CWM recovery, the KNOX warranty set to 0x1. As you know, ZHUDMI1 cannot be fully rooted now.
Then I tried to flash the phone by ODIN with I9505ZHUBMF4 (includes PIT, PHONE, MODEM, CSC). The phone showed "OFFICIAL" and can OTA again, but I disabled auto upgrade.
And rooted the phone with CF-Auto-Root-jflte-jfltexx-gti9505. Now its status is "CUSTOM". Anyway, maybe I lost the warranty, but I can use this phone with fully rooted now.
I have nothing useful to add except that I find it funny that my country's firmware is allowing for downgrades :lol:. Congrats on finding the exploit BTW .
Anakha56 said:
I have nothing useful to add except that I find it funny that my country's firmware is allowing for downgrades :lol:. Congrats on finding the exploit BTW .
Click to expand...
Click to collapse
What about the warranty bit
Sent from my GT-I9500 using Tapatalk
hypergamer1231 said:
What about the warranty bit
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
I learnt from the S2 days never, ever flash the latest leaks until a work around has been found. So yeah I have not gone the 4.3 route just yet but its nice to know that the firmware I already have could downgrade me should the need arise .
My experience:
So I have a I9500, and its on the russian 4.3, and I root it, it says both binary and status official except the Warranty Bit is 1, and Knox won't work on my phone, It goes " Your device is not authorised to enter knox mode". It shows the same thing after I unroot it ( Flash the 4.3 rom again). Just wonder is there any way that I can use Knox again??
Frigedaeg said:
So I have a I9500, and its on the russian 4.3, and I root it, it says both binary and status official except the Warranty Bit is 1, and Knox won't work on my phone, It goes " Your device is not authorised to enter knox mode". It shows the same thing after I unroot it ( Flash the 4.3 rom again). Just wonder is there any way that I can use Knox again??
Click to expand...
Click to collapse
Install the stock ROM via odin. It's solve the problem, try another ROM from another country.
Sent from my GT-I9500 using Tapatalk
Braulio00 said:
Install the stock ROM via odin. It's solve the problem, try another ROM from another country.
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Well, I tried to install the 4.3 Russian Stock rom again, it still wont work, still says Your device is not authorised to enter knox mode
Frigedaeg said:
Well, I tried to install the 4.3 Russian Stock rom again, it still wont work, still says Your device is not authorised to enter knox mode
Click to expand...
Click to collapse
Same thing happened to me knox won't ever work till warranty bit is reset or motherboard is replaced
Sent from my GT-I9500 using Tapatalk
I bought a new note edge
I am currently working on kit kat version however an update is available but every time I try to update the device it shows registration failed and I am not able to update it
umesh shah said:
I bought a new note edge
I am currently working on kit kat version however an update is available but every time I try to update the device it shows registration failed and I am not able to update it
Click to expand...
Click to collapse
Hold down Volume down and power button and home button. When you get to bootloader see if knox warranty void is 0x1 and if the binaries are "official" or "Custom":...
If they are custom and Knox warranty void is 0x1 then your device has been rooted and as such can't be OTA'd...
i got the same problem , what shall i do ????
my galaxy note is official ..
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 cant flash stock rom (INS) pie version using oding 14.1, i did try using xtc firmware it says sw rev. check fail(bootloader) device 8 binary 6 too. how to fix this?? please help
Hello! sw rev. check fail(bootloader) device 8 binary 6 means that the ROM you have downloaded has a binary 6 while the device has a binary 8. In Android, or at least Samsung phones you cannot go to a lower binary than the one present in your device. Basically the only fix I believe is to download a ROM that has a binary of 8. If you do not know what binary it has I will leave a screenshot showing which number signifies a binary (Only mind the number in the binary, the U is a part of that but you just need to look at the number when you're downloading the correct ROM).
download latest stock
You have updated your device to Binary 8. Which means you have an updated bootloader. Samsung no longer allows the bootloader to be downgraded so you are stuck there. Anyways there's no worries. There are alot of ROMs and mods to use that you may enjoy.
Bootloop
Hi. Sorry for my bad English.
My problem is that despite uploading the rom, my phone is in a loop and uploading the rom does not help. Please help.
AdamAnd said:
Hi. Sorry for my bad English.
My problem is that despite uploading the rom, my phone is in a loop and uploading the rom does not help. Please help.
Click to expand...
Click to collapse
Flash last ROM latest release of your country
Test latest releases of your country
Downgrade not possible
hacker812c said:
Flash last ROM latest release of your country
Test latest releases of your country
Downgrade not possible
Click to expand...
Click to collapse
Hi. Thanks for the suggestion, but unfortunately after successfully uploading the latest software from my region (XEO) nothing changes. The phone is rebooting and it's still looped.
Region - firmware:
sammobile.com/samsung/galaxy-j6/firmware/SM-J600FN/XEO/download/J600FNXXU8CTF5
I can go to Download Mode and Recovery.
I guess there is something wrong with Recovery.
The recovery on my phone looks like this:
Android Recovery
samsung/j6ltexx/j6lte
10/QP1A. 190711.020/J600FNXXU8CTF5
user/release-keys
Android Recovery
samsung/j6ltexx/j6lte
10/QP1A. 190711.020/J600FNXXU8CTF5
user/release-keys
Sorry, but I connected to the topic and I think I should start a new topic with my problem.
I am asking the moderator for information or to move my posts to the right place. Thank you.
SirDoz said:
You have updated your device to Binary 8. Which means you have an updated bootloader. Samsung no longer allows the bootloader to be downgraded so you are stuck there. Anyways there's no worries. There are alot of ROMs and mods to use that you may enjoy.
Click to expand...
Click to collapse
I cannot find a Saudi Arabia KSA region rom for my SM-J730F ( I can't use my sim because of that)
The rom I can find on sammobile is at u4, and my phone has s7 so it gives the error. However there is another rom that is latest but that rom is Saudi Arabia ACR Please help me
got the same issue on a s10... device 9, binary 8
Fanges4033 said:
got the same issue on a s10... device 9, binary 8
Click to expand...
Click to collapse
any solution for this?
Fanges4033 said:
got the same issue on a s10... device 9, binary 8
Click to expand...
Click to collapse
find the latest and cointain number 9
at middle
Can't we downgrade using Combinational rom?
Aleks Skuber said:
Hello! sw rev. check fail(bootloader) device 8 binary 6 means that the ROM you have downloaded has a binary 6 while the device has a binary 8. In Android, or at least Samsung phones you cannot go to a lower binary than the one present in your device. Basically the only fix I believe is to download a ROM that has a binary of 8. If you do not know what binary it has I will leave a screenshot showing which number signifies a binary (Only mind the number in the binary, the U is a part of that but you just need to look at the number when you're downloading the correct ROM).
Click to expand...
Click to collapse
My SM G950F shows binary 12,but i cant find any b12 files
rtyuakatsuki said:
find the latest and cointain number 9
at middle
Click to expand...
Click to collapse
where can I find the binary 8 for the S7 SM-G930F, the samobile firmware page sucks
marinson said:
where can I find the binary 8 for the S7 SM-G930F, the samobile firmware page sucks
Click to expand...
Click to collapse
Find it in samfw
Hello after rooting my device i seem to have lost imei on both slots.Baseband version says unknown i tried some threads i found on the xda site but no luck.Also i removed rooting/relocked bootloader and reflashed latest firmware for my device nothing seems to work.
komninoskom said:
Hello after rooting my device i seem to have lost imei on both slots.Baseband version says unknown i tried some threads i found on the xda site but no luck.Also i removed rooting/relocked bootloader and reflashed latest firmware for my device nothing seems to work.
Click to expand...
Click to collapse
Have you tried flashing a imei/baseband repair file
maybe your phone's baseband IC (hardware) was damaged, same like me after splashed by rain
Allehandro said:
Have you tried flashing a imei/baseband repair file
Click to expand...
Click to collapse
What is that file?
komninoskom said:
What is that file?
Click to expand...
Click to collapse
Since a certain firmware version, the IMEI just disappeared...I thought it was a bug in the firmware. There was a file that fixes it
Allehandro said:
Since a certain firmware version, the IMEI just disappeared...I thought it was a bug in the firmware. There was a file that fixes it
Click to expand...
Click to collapse
i try that file but nothing works
Jayke770 said:
i try that file but nothing works
Click to expand...
Click to collapse
Yeah I've heard from others that it didn't wirk for them but it works for me. New firmware versions from Samsung still don't fix the issue but I use the file and it always works
Allehandro said:
Yeah I've heard from others that it didn't wirk for them but it works for me. New firmware versions from Samsung still don't fix the issue but I use the file and it always works
Click to expand...
Click to collapse
it works because your binary is U1 not U2
Jayke770 said:
it works because your binary is U1 not U2
Click to expand...
Click to collapse
Yeah that's what I heard others saying...don't know what it means though
The firmware loses its baseband version from around the July update
anyone know where the file can be found?
Unfortunately is a common problem on MTK Ax2 Family phones I see in the Argentinian samsung forum's and the galaxy A32 has the same problem once you trip the Knox warranty all newer firmware updates whit the secure by Knox splash will not get signal anymore (Baseband corruption idk) and the another problem is the binary once you update to binary 2 say bye bye to your signal (for now if some can patch this bug)
MauriJ2001 said:
Unfortunately is a common problem on MTK Ax2 Family phones I see in the Argentinian samsung forum's and the galaxy A32 has the same problem once you trip the Knox warranty all newer firmware updates whit the secure by Knox splash will not get signal anymore (Baseband corruption idk) and the another problem is the binary once you update to binary 2 say bye bye to your signal (for now if some can patch this bug)
Click to expand...
Click to collapse
But this person (I founded in Samsung Community) he updates his A12 to binary 2, and the signal is working, and no bug after he updates his A12
MauriJ2001 said:
Unfortunately is a common problem on MTK Ax2 Family phones I see in the Argentinian samsung forum's and the galaxy A32 has the same problem once you trip the Knox warranty all newer firmware updates whit the secure by Knox splash will not get signal anymore (Baseband corruption idk) and the another problem is the binary once you update to binary 2 say bye bye to your signal (for now if some can patch this bug)
Click to expand...
Click to collapse
I'm on binary 2 now, cant downgrade or anything so basically goodbye to my phone.
At least for now is there a way to make phone don't shutdown because of missing imei/baseband?
Jerffelly said:
I'm on binary 2 now, cant downgrade or anything so basically goodbye to my phone.
At least for now is there a way to make phone don't shutdown because of missing imei/baseband?
Click to expand...
Click to collapse
Did you fix it now because mine has also the problem after i update to u2 version febuary update
Sheepmister said:
Did you fix it now because mine has also the problem after i update to u2 version febuary update
Click to expand...
Click to collapse
not yet.
Holidi16 said:
But this person (I founded in Samsung Community) he updates his A12 to binary 2, and the signal is working, and no bug after he updates his A12
Click to expand...
Click to collapse
Knox 0x0 this problem is for now in 0x1 devices
MauriJ2001 said:
Knox 0x0 this problem is for now in 0x1 devices
Click to expand...
Click to collapse
Ooh I see
MauriJ2001 said:
Unfortunately is a common problem on MTK Ax2 Family phones I see in the Argentinian samsung forum's and the galaxy A32 has the same problem once you trip the Knox warranty all newer firmware updates whit the secure by Knox splash will not get signal anymore (Baseband corruption idk) and the another problem is the binary once you update to binary 2 say bye bye to your signal (for now if some can patch this bug)
Click to expand...
Click to collapse
It's actually because rooting said phones with certain MTK chipsets, it's been around since 2020.
Deleted member 12039295 said:
Hello after rooting my device i seem to have lost imei on both slots.Baseband version says unknown i tried some threads i found on the xda site but no luck.Also i removed rooting/relocked bootloader and reflashed latest firmware for my device nothing seems to work.
Click to expand...
Click to collapse
knox_warrenty_void at 0x1 means warrenty is voided. 0x0 means enabled which then translates to warrenty is valid. 0x1 switched on because of running custom firmware (you're magisk modifications).
Issue that you are expiriencing is pretty normal and is pritty much nothing new. Can you provide some info on what firmware are you running and what method of rooting have you followed. I would recommend to grab the "IMEI repair file" which you can find on the forum (works as a modem file). Either do that or downgrade to a older firmware version, to something more stable like BUF9. I've made planty of guides and threads where I have allready explained all of this.
If none of what I've said has worked for you, be sure to ask furter questions without any fear xD.
Have a good day,
Krypton
LAST_krypton said:
knox_warrenty_void at 0x1 means warrenty is voided. 0x0 means enabled which then translates to warrenty is valid. 0x1 switched on because of running custom firmware (you're magisk modifications).
Issue that you are expiriencing is pretty normal and is pritty much nothing new. Can you provide some info on what firmware are you running and what method of rooting have you followed. I would recommend to grab the "IMEI repair file" which you can find on the forum (works as a modem file). Either do that or downgrade to a older firmware version, to something more stable like BUF9. I've made planty of guides and threads where I have allready explained all of this.
If none of what I've said has worked for you, be sure to ask furter questions without any fear xD.
Have a good day,
Krypton
Click to expand...
Click to collapse
I used to use the IMEI repair file but when I was flashing the new BVE3 Firmware, I got an error "SECURE CHECK FAIL: md1img.img" "SECURITY ERROR. THE PHONE HAS BEEN FLASHED WITH UNAUTHORISED FIRMWARE AND IS LOCKED"
I think it's because of the U2 Binary, so now I can't downgrade to BUF9 since it's U1. So now IMEI is missing and the only fix is to delete the NVD_IMEI folder which requires root. I am unable to root my device since the OEM Unlock option is missing from the developer options and I can't login to my samsung account as I get a meesage "IMEI(or MEID) is empty". So I don't know how to get the OEM Unlock option to show so I can root the device and use the NVD_IMEI Fix