Related
So... I seem to be having the efs corruption issue with my co-worker's phone. I've been searching all over and have found how others have solved the problem, but it seems that our nv_data.bin is not located in our efs directory.
Does anyone have any idea where these files are? I need to check the last modified dates of their backup files to see if I can restore them >.<
Any help is greatly appreciated!!
Bump.. If anyone knows where these files are this could help us from running into the corrupt efs problem that many people have had. Usually backing up your efs prevents your phone from becoming unable to function as a phone.
I do remember reading something about our unlock code not being present in our nv_data.bin.. And when I check my efs folder in both my, as well as my co-worker's phone there is no nv_data.bin so maybe it has been relocated??
Anyone with knowledge on this subject.. your input would be greatly appreciated! I'm also gonna read over the unlock threads to see if there is any relevant info there.
I am having this problem now, I know you posted this over a month ago, but please tell me you know the location of the backup files or any other solution for this?'
Thank you,
[Q] T989 - Baseband and IMEI Unknown
I have searched and read many threads already. I understand the i9100 uses a file called nv_data.bin and requires its .bak file for a fix.
But, I dont think the t989 is the same because these files dont seem to exist, or at least not in the locations the threads for i9100 state. I am wondering if anyone has had this problem and/or how they fixed it. I know it was caused because of trying to unlock, but I'm looking for a solution.
Thanks!
just buy one of those $20 online unlock or go to your local phone kiosk to have it unlocked
any one with a machine to unlock Samsung phones can get this phone unlocked easily
there's no software unlock yet, as you have found on your searches
I have T-Mobile and don't really care for the unlock, it was a mistake. At this point, I just want to fix the unknown IMEI and unknown Baseband issue. Because of this problem my phone cannot get a signal... Will performing a machine unlock fix this problem?
Note: When I type in *#06# the response is not my IMEI number. It says "null"
svahora said:
I have T-Mobile and don't really care for the unlock, it was a mistake. At this point, I just want to fix the unknown IMEI and unknown Baseband issue. Because of this problem my phone cannot get a signal... Will performing a machine unlock fix this problem?
Note: When I type in *#06# the response is not my IMEI number. It says "null"
Click to expand...
Click to collapse
You can try to find someone locally with a SPT Box2. This unit can flash, unlock & repair IMEI on SGH-T989(d). I was gonna pick one up, but they are like $250 yikes !!
KillaHurtz said:
You can try to find someone locally with a SPT Box2. This unit can flash, unlock & repair IMEI on SGH-T989(d). I was gonna pick one up, but they are like $250 yikes !!
Click to expand...
Click to collapse
What does the (d) stand for?
And, how can I make sure this never happens again in the future? I know there are backup options out there (CWM, Nandroid), but are there any that make a complete clone of the phone's image? In case I mess up the efs or IMEI files again I can restore and be ok.
Thanks!
T989D = Canadian release of T989
they are identical, the just use the D for Canadian
AllGamer said:
T989D = Canadian release of T989
they are identical, the just use the D for Canadian
Click to expand...
Click to collapse
Would a Nandroid backup fix this in the future?
is hard to say, we have no idea where is the real IMEI information is being stored in the new models, but is no longer in the old EFS folder
AllGamer said:
is hard to say, we have no idea where is the real IMEI information is being stored in the new models, but is no longer in the old EFS folder
Click to expand...
Click to collapse
I wonder if the new Galaxy Nexus has its IMEI files stored similarly. If so, we can join forces with that forum group.
If Android is not mounting your firmware properly in the system this will cause no baseband and no imei detected. i would try and flash the stock rom to make sure.
-Mr. X- said:
If Android is not mounting your firmware properly in the system this will cause no baseband and no imei detected. i would try and flash the stock rom to make sure.
Click to expand...
Click to collapse
Did it twice, the stock rom, modem, and kernel.
The radio (modem firmware) might have got corrupted if somebody tried to flash international GS2 ROM or modem.
Try to flash only the Radio (KL1 is the latest for T-Mobile) via ODIN (use PDA slot).
cyberjam said:
The radio (modem firmware) might have got corrupted if somebody tried to flash international GS2 ROM or modem.
Try to flash only the Radio (KL1 is the latest for T-Mobile) via ODIN (use PDA slot).
Click to expand...
Click to collapse
Would the KL1 work any different than the older one? I tried ODINing the original one, and it didn't work and increased the count so I didn't try the KL1.
I just got my replacement phone yesterday for this same problem. Flashed the stock kernal, and also the modem just to be safe and nothing would fix it. From what I know its just a hardware issue, not software. I was chatting with samsung and t-mobile people about this trying all kinds of fixes to nothing left but hardware defect.
So I have a Telus I747M (Canadian) and I used ROM Manager to get CWM 6 on my phone. The thing is that I chose the Metro PCs version and I installed it. Now I have no signal at all. I flashed the firmware back to the stock telus one via USB and Odin. Still no service, anything to do now?
are you sure you flashed the right stock rom? Stupid question but it's always best to check. And did you get your phone from Metro or did you unlock it?
karmasblade said:
So I have a Telus I747M (Canadian) and I used ROM Manager to get CWM 6 on my phone. The thing is that I chose the Metro PCs version and I installed it. Now I have no signal at all. I flashed the firmware back to the stock telus one via USB and Odin. Still no service, anything to do now?
Click to expand...
Click to collapse
go to about setting ->status, does it say Metro PCs(if you're on metro pcs) under Network?
dima470 said:
are you sure you flashed the right stock rom? Stupid question but it's always best to check. And did you get your phone from Metro or did you unlock it?
Click to expand...
Click to collapse
pcshano said:
go to about setting ->status, does it say Metro PCs(if you're on metro pcs) under Network?
Click to expand...
Click to collapse
No, it's a Telus. I know I messed up but is there a way to fix this. I've tried to flash back to stock and my IMEI shows "0", no SMS or calling available too...
karmasblade said:
No, it's a Telus. I know I messed up but is there a way to fix this. I've tried to flash back to stock and my IMEI shows "0", no SMS or calling available too...
Click to expand...
Click to collapse
Try flashing any rom (like Cyanogenmod) and then use any of the many methods to re-unlock your phone to Metro and see if that helps.
karmasblade said:
No, it's a Telus. I know I messed up but is there a way to fix this. I've tried to flash back to stock and my IMEI shows "0", no SMS or calling available too...
Click to expand...
Click to collapse
If your IMEI shows 0, no amount of flashing will help you. You must restore you IMEI to have data working again. If you backed up your IMEI or EFS folder your set, just restore it.
If not see here: http://forum.xda-developers.com/showthread.php?t=1801997
Sent from my Galaxy S3 on AT&T
RPelham said:
If your IMEI shows 0, no amount of flashing will help you. You must restore you IMEI to have data working again. If you backed up your IMEI or EFS folder your set, just restore it.
If not see here: http://forum.xda-developers.com/showthread.php?t=1801997
Sent from my Galaxy S3 on AT&T
Click to expand...
Click to collapse
Hi, Thanks for helping me. I have not backed up the IMEI and do not have EFS. I have tried those instructions and I have one problem. I cannot find my phone in the "COM" Ports. There's simply nothing there related to my phone.
karmasblade said:
Hi, Thanks for helping me. I have not backed up the IMEI and do not have EFS. I have tried those instructions and I have one problem. I cannot find my phone in the "COM" Ports. There's simply nothing there related to my phone.
Click to expand...
Click to collapse
You need the Samsung keis drivers. You can get them by installing Samsung Keis.
karmasblade said:
Hi, Thanks for helping me. I have not backed up the IMEI and do not have EFS. I have tried those instructions and I have one problem. I cannot find my phone in the "COM" Ports. There's simply nothing there related to my phone.
Click to expand...
Click to collapse
Did you make sure you put your phone into RMNET +DM + MODEM mode before trying to find your phone in the COMs?
Also this:
dima470 said:
You need the Samsung keis drivers. You can get them by installing Samsung Keis.
Click to expand...
Click to collapse
Sent from my Galaxy S3 on AT&T
dima470 said:
You need the Samsung keis drivers. You can get them by installing Samsung Keis.
Click to expand...
Click to collapse
The phone is still not showing up under coms
RPelham said:
Did you make sure you put your phone into RMNET +DM + MODEM mode before trying to find your phone in the COMs?
Also this:
Sent from my Galaxy S3 on AT&T
Click to expand...
Click to collapse
I can't dial anything because there's no service. Is there a way to change it without using the dialpad?
karmasblade said:
I can't dial anything because there's no service. Is there a way to change it without using the dialpad?
Click to expand...
Click to collapse
you can still access *#xxxxx# (x are numbers ... but i forgot ;p go look it up)
pcshano said:
you can still access *#xxxxx# (x are numbers ... but i forgot ;p go look it up)
Click to expand...
Click to collapse
I got my IMEI number into my phone now. The IMEI SV is 01 still. No signal now still. What do I do?
karmasblade said:
I got my IMEI number into my phone now. The IMEI SV is 01 still. No signal now still. What do I do?
Click to expand...
Click to collapse
Fixed the problem, followed exactly this post and got it http://forum.xda-developers.com/showthread.php?p=32974433#post32974433
The data is slow now even after showing 4g connections. Sometimes the data shows its on but there's no connection at all. Any help? The speeds show 1mbps download and .2 for upload on 4g.
karmasblade said:
Fixed the problem, followed exactly this post and got it http://forum.xda-developers.com/showthread.php?p=32974433#post32974433
Click to expand...
Click to collapse
karmasblade said:
The data is slow now even after showing 4g connections. Sometimes the data shows its on but there's no connection at all. Any help? The speeds show 1mbps download and .2 for upload on 4g.
Click to expand...
Click to collapse
Great reply, but yeah, I'm left with the same problem of slow connectivity. Same problem as linked post, and followed his process to the letter. Oh well, spent most of my Sunday trying to fix this. As long as I can make calls and transceive texts, that'll have to do.
BadFoxtrot said:
Great reply, but yeah, I'm left with the same problem of slow connectivity. Same problem as linked post, and followed his process to the letter. Oh well, spent most of my Sunday trying to fix this. As long as I can make calls and transceive texts, that'll have to do.
Click to expand...
Click to collapse
Well if you have problems still and the imei is back, I don't see why there's anything wrong with taking it to the store to get it checked out.
karmasblade said:
Well if you have problems still and the imei is back, I don't see why there's anything wrong with taking it to the store to get it checked out.
Click to expand...
Click to collapse
I am in the same boat. Slow connection, rarely actually works. Had lost my imei, but restored it with the NV whatever.. Saved my QCN using QPST, then tried to use QCN restorer app, and am getting an error occurred blah blah.
I brought it in to AT&T yesterday, had a full restore completed and new sim card installed... no luck. guess i will keep trying stuff until its either bricked or back to normal haha
Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
artorelis said:
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Ya, I was asking this question on the Omega forum and I am waiting for the right response.
Sent from my GT-N7100 using xda premium
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
joshphilips said:
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Yes, I did downgrade from v17 back to 16 since something went wrong with Poweramp but I forgot that if I selected for the efs backup or not since I (stupidly) didn't think that efs is important...:banghead:
Sent from my GT-N7100 using xda premium
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
Click to expand...
Click to collapse
Thanks for replying, I should have a backup, but it probably be the wrong one. Anyway I will go for a full stock restore since I have the firmware with me now.
Sent from my GT-N7100 using xda premium
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
Good luck.
Click to expand...
Click to collapse
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Dan Law 001 said:
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Click to expand...
Click to collapse
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
muppetmania said:
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
Click to expand...
Click to collapse
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Dan Law 001 said:
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Click to expand...
Click to collapse
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
muppetmania said:
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
Click to expand...
Click to collapse
Thanks for information, but how do I know that if the EFS is "totally" corrupt, "partially" corrupt, or not corrupt at all? In fact, I never touch the EFS in the root. Also, as I am not quite sure that if I have any previous EFS(S) backup or not, so, if possible, where does the backup(s) most likely to be found?
If you haven't taken an EFS backup yourself, then you won't have any.
I don't know the difference between corruption levels either, all I know is I've read a number of forum posts where someone has reflashed stock and their EFS data (i.e. the right IMEI number) is back. So I'd consider that to be a partial corruption. Others have flashed back to stock and it's still a bogus IMEI
Basically, flash back to stock. If it doesn't work, you'll have to take it in for repair.
UPDATE: Please read on - this information is incorrect - it is possible to recover with the correct modem flashed.
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
NOTE: The information from me in this post below is wrong
Dan Law 001 said:
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
Click to expand...
Click to collapse
It's normal your device got unrooted, yes. If your IMEI is still the same after ODIN and stock flash, then you have major issues (sorry!)
Doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What IMEI does *#06# show?
muppetmania said:
it's normal your device got unrooted, yes. If your imei is still the same after odin and stock flash, then you have major issues (sorry!)
doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What imei does *#06# show?
Click to expand...
Click to collapse
004999010640000 / 01
Dan Law 001 said:
004999010640000 / 01
Click to expand...
Click to collapse
Type 004999010640000 into Google...
Sorry man. Good luck getting it fixed.
just flash ME4 modem everything will be alright
bhasg1007 said:
just flash ME4 modem everything will be alright
Click to expand...
Click to collapse
Interesting to know - why does that work? (I don't doubt you, I just like to know why things work)
Just go through this thread http://forum.xda-developers.com/showthread.php?t=2333216
Even i had the same problem no network no imei nothing after downgrading so i just changed the modem and now everything is fine as it should be
from what i have read from other forums i see that device rootkey causes the problem of stuck at logo. this is due to efs wipe or imei repair. So i am just wondering what is DRK (device rootkey) and how can it be repaired, so we can go back to fully stock ? Thanks
The only way to fix the rootkeys is to use the engineering software and serial cable. You have to send it somewhere to get fixed or if you know someone that has those those things.
Hopefully this is a lesson to you guys for flashing things you shouldn't flash. All devices can be sim unlocked from the original carrier. In the US it is the law. If you fully purchased your device then the carrier has to give you the unlock code by law. So if you guys are doing this then you are either not very informed and you went with flashing when it wasn't needed. Or you guys are trying to steal your devices without finishing the financing. Either way it is on you guys and deserve a broken device.
Same thing with trying to root bypassing knox. For those of us not in a security or government job, Knox only affects Samsung Pay. It it really worth messing up your phone just so you can use Samsung Pay? What is wrong with Android pay? It has been around for a long time. Samsung is throwing in little gimmicks. But not really worth it for me to put my banking info on yet another companies server farm. The more places you have your info the more likely you are to run into problems with data theft. All of us were already affected by this when Experian was hacked and got our T-Mobile info. Start using the brains that we were born with.
jmc302005 said:
The only way to fix the rootkeys is to use the engineering software and serial cable. You have to send it somewhere to get fixed or if you know someone that has those those things.
Click to expand...
Click to collapse
You are not right, DRK keys can be fixed without eng soft and serial cable. Keys are located in EFS partition and can be copied from other device with same model, after copy/chmod/chown - reboot and it works again.
magix01 said:
You are not right, DRK keys can be fixed without eng soft and serial cable. Keys are located in EFS partition and can be copied from other device with same model, after copy/chmod/chown - reboot and it works again.
Click to expand...
Click to collapse
I also posted that info last year. Things may have changed since then. I also don't have the S6 anymore so I am not current. So at the time my info was correct. Instead you can inform us that a new way has been found. Thanks for the info.
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now, suddenly I find there's the no SIM indication, and in settings -> about phone it says IMEI: unknown, and in software information it says bandbase version: unknown.
The firmware version I used was exactly the same as when I bought it, A325MUBU2AUJ4, with the right csc (ARO in my case).
EDIT: after a couple reboots, the bandbase version now shows, but still no IMEI or SIM detected.
Can anyone help me? What happened? What can I do? Thanks in advance!
flash all the with odin the correct rom. the twrp unstable and more like shell and who knows what bugs have magisk. until why have a good recovery i would no root my phone reallly if you want to unisstall the software from samsung and google i would say to use the universal debload https://github.com/0x192/universal-android-debloater.
UPDATE: it got unknown baseband againI
I relocked the bootloader and now in download mode I have an option to "show barcodes" pressing the side button. The barcodes show the right IMEI and serial number. Maybe stuff wasn't erased, just inaccesible by the rom?
I was told by a technician to flash the original ROM (already did) then root again. Tried several versions but not an older bandbase because downgrade is forbidden by the bootloader, apparently, to no avail. Would try a newer baseband but i'm afraid it will not work and will be unable to go back to the origial baseband version.
Weird thing is, there is the EFS directory but no /data/nvram or /dev/nvram
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
edukardo said:
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
Click to expand...
Click to collapse
How did you root it?
as I understand, after rooting, warranty is void since it implies flashing a magisk patched boot image or AP tar. In my case I was indeed able to relock the bootloader and flash the original firmware but upon entering download mode, it shows "warranty void 0x01".
was it the same in your case?
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
edukardo said:
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
Click to expand...
Click to collapse
most likely the warranty vod bit was on (you can check it yoursef by entering odin mode) and they didn't notice
so you got it fixed for free?
did they mention what did the fix consist in? I heard they say they change the motherboard, which is a lie, they just write the nvram or efs with the right stuff
ah sos de argentina? lol where did you take it? to a samsung store? I'm from neuquen and got it at musimundo, but here's a samgung store too
myself i was thinking of waiting for an update which should be soon, lock bootloader, flash some official rom and pull off the cable so it gives an upgrade error and doesn't enter download mode, then take it to the store
Unroot before update and unlock
wipe the cache partition . then reset the phone using recovery mode . this is at you own risk .
did you fix it?
applesucksLmao said:
did you fix it?
Click to expand...
Click to collapse
nope, went to samsung, got rejected cause warranty bit on, no choice but take it to a service and I suppose they could do something with Chimera Tool, Z3X or something like that, which, as I've seen, claims to fix it in minutes (and the client gets charged handsomely, like 100 USD)
From Samsung I got the same bullsh*t I read in some threads: "this phone has been tampered with and it's a hardware problem, the board must be replaced"
For the technically savvy, I got a strange Magisk log which kind of looks like it may be the problem. It seems to try to "unlock"* some devices on bootup but gets "permission denied". One of them may be the nvram or something like that. I have an EFS directory but no NVRAM directory anywhere or /dev/nvram.
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
or atleast use magisk with aug or even older firmware if you can... is your a32 A325M or A325F?
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
what's JTagged?
applesucksLmao said:
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
Click to expand...
Click to collapse
I found it impossible to downgrade, download mode doesn't allow it. Couldn't find a tutorial to do it either.
applesucksLmao said:
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
Click to expand...
Click to collapse
I did, I tried all combinations rooting/unrooting with the new magisk 24.1 the new version, A325MUBS2AVA1
It's a 325m btw