Hey guys,
I've been trying to unlock my phone for a few days now. Long story short, I moved from Canada to Japan and now I want to unlock my S3 to use a Japanese SIM.
I bought an unlock code from eBay. I was previous running cyanogenmod but then I was told that rooting will cause issues, so I unrooted my phone after an unsuccessful SIM unlock attempt. (wiped the phone, installed stock TW)
Even after unrooting I still had issues, and was given directions for the Service mode. That did not work either. I have tried many different methods and troubleshooting tips and nothing seems to have worked.
Here are some screenshots of the debug mode, my phone details, and a simple root checker app I installed.
puu.sh/dPN0p.png
Here are some specs: SGH-i747m Samsung Galaxy S3 on Bell running official firmware 4.4.2
Thanks for reading, and I really hope someone can help ;_;
Does your phone display the correct imei as the one you provided to the unlocker? The imei using the dial pad is the same as the imei on label attached to the phone?
audit13 said:
Does your phone display the correct imei as the one you provided to the unlocker? The imei using the dial pad is the same as the imei on label attached to the phone?
Click to expand...
Click to collapse
Yes it displays the same IMEI on the label of the phone, and when using *#06# on the dial pad.
Despite my flashing back to stock, multiple sellers I have been through on eBay believe my phone is still rooted. One of my friends believed the people on eBay are at fault.
I then bought a code from a somewhat reputable looking website (cellunlocker.net) and received the exact same code. They had provided some additional troubleshooting methods but they did not work.
So it just won't accept the code or the prompt to enter the code doesn't appear on the screen?
audit13 said:
So it just won't accept the code or the prompt to enter the code doesn't appear on the screen?
Click to expand...
Click to collapse
The prompt appears on screen no problem. It won't accept the code. Please refer to the screenshots I posted in the OP (the puu,sh link)
Is there some extra step I can do to get my phone back to normal? I thought just flashing stock and wiping data/cache would do it but I'm still having problems and I can't figure them out.
I'm aware downgrading firmware is out of the question, but I really have no options left.
I haven't technically activated the Japanese SIM card yet. Could that be an issue?
Did you restore stock using Odin and firmware from sammobile.com?
Don't attempt to downgrade if you have a 4.4.2 bootloader as that could brick your phone.
audit13 said:
Did you restore stock using Odin and firmware from sammobile.com?
Don't attempt to downgrade if you have a 4.4.2 bootloader as that could brick your phone.
Click to expand...
Click to collapse
Yes I grabbed firmware from sammobile and flashed with Odin. I made sure to match the last four digits in the baseband of my phone which is FNH2 so I downloaded this one from sammobile
sammobile /firmwares/download/34795/I747MVLUFNH2_I747MOYCFNH2_BMC.zip/
On the Odin "Downloading..." screen, my warranty bit is 1. Could that be causing the issue?
If so how do I fix that
The warranty bit will not prevent your from unlocking the phone. When a phone is shipped, the warranty bit is set at 0. If a person flashes any non-Samsung approved software, it will change the warranty bit from 0 to 1. It cannot be reset to 0.
When flashing with Odin, I prefer 3.07. So you are just unzipping the file and flashing the tar.md5 file in PDA section? Try again but only check F reset time. Once you see reset in the status window, remove the usb cable, remove the battery, boot into recovery, do a factory wipe, and reboot.
audit13 said:
The warranty bit will not prevent your from unlocking the phone. When a phone is shipped, the warranty bit is set at 0. If a person flashes any non-Samsung approved software, it will change the warranty bit from 0 to 1. It cannot be reset to 0.
When flashing with Odin, I prefer 3.07. So you are just unzipping the file and flashing the tar.md5 file in PDA section? Try again but only check F reset time. Once you see reset in the status window, remove the usb cable, remove the battery, boot into recovery, do a factory wipe, and reboot.
Click to expand...
Click to collapse
Still no luck unfortunately ;_;
Blah. Might just sell this phone and buy a Japanese one.
The only other thing I can think of is a corrupt EFS folder.
Did you try re-injecting the imei?
audit13 said:
The only other thing I can think of is a corrupt EFS folder.
Did you try re-injecting the imei?
Click to expand...
Click to collapse
First time I've ever heard of that. Backup/restore?
I just did a quick google search and couldn't find a solid guide. Did you have a certain process in mind?
I appreciate all of your help.
http://forum.xda-developers.com/showthread.php?t=1804117
audit13 said:
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
Thank you for providing the guide. Unfortunately it's still not working. I uploaded a video just in case that might help, I also have to get a refund from an unlock website, lol.
https://www.youtube.com/watch?v=anrfCgMvBrw&feature=youtu.be
This is really weird as it looks like you are doing everything right.
audit13 said:
This is really weird as it looks like you are doing everything right.
Click to expand...
Click to collapse
Then you can understand why I am incredibly frustrated, hahaha.
It's cool. I just ended up buying a Japanese phone.
Thank you for all your help, hopefully no one else runs into thee issues in the future
Related
My problem:
My galaxy s3 takes a LONG time to connect to AT&T when it boots up (over 5 minutes), and then only has Edge:2 network service.
How I got here:
Had 4.1.2 installed from AT&T
I rooted my phone with the "no countering tripping method" as described here: http://forum.xda-developers.com/showthread.php?t=1739426 to 4.1.1 this downgrade apparently made something not work, I kept getting errors, something about acore process failures.
I re-installed the stock 4.1.2 from AT&T
Still getting process failures
Read that clearing the contacts sometimes works, it didn't
Read that factory reset helps, it did
I still wanted a rooted phone, so this time I used this method: http://forum.xda-developers.com/showthread.php?t=1746665
Again processes started crashing
Again had to reset to factory
Now I noticed my phone wasn't working at all
Found that my IMEI was set to 0
Fixed that by following these instructions: http://forum.xda-developers.com/showthread.php?t=1804117
Note: the link to the sgs3.nv.gen.zip was bad, I found another here: http://forum.xda-developers.com/showthread.php?t=2335951 but my virus checker freaked out on it. I ran it on my kids pc, and it worked, don't know if I infected them or not, but I got my IMEI data back
Decided all this was too much hassle, so I reset my flash count to zero with this: http://forum.xda-developers.com/showthread.php?t=1494114
Reverted to stock 4.1.2 from AT&T and reset to factory
Still stuck on Edge:2
Found this thread: http://forum.xda-developers.com/showthread.php?t=2036891 my phone won't let me change my band preference, also under *#197328640#>SIM>CHECK NV it say "Band perf: Unexpected value"
Question:
Where do I go from here?
Thanks!
thabin said:
My problem:
My galaxy s3 takes a LONG time to connect to AT&T when it boots up (over 5 minutes), and then only has Edge:2 network service.
How I got here:
Had 4.1.2 installed from AT&T
I rooted my phone with the "no countering tripping method" as described here: http://forum.xda-developers.com/showthread.php?t=1739426 to 4.1.1 this downgrade apparently made something not work, I kept getting errors, something about acore process failures.
I re-installed the stock 4.1.2 from AT&T
Still getting process failures
Read that clearing the contacts sometimes works, it didn't
Read that factory reset helps, it did
I still wanted a rooted phone, so this time I used this method: http://forum.xda-developers.com/showthread.php?t=1746665
Again processes started crashing
Again had to reset to factory
Now I noticed my phone wasn't working at all
Found that my IMEI was set to 0
Fixed that by following these instructions: http://forum.xda-developers.com/showthread.php?t=1804117
Note: the link to the sgs3.nv.gen.zip was bad, I found another here: http://forum.xda-developers.com/showthread.php?t=2335951 but my virus checker freaked out on it. I ran it on my kids pc, and it worked, don't know if I infected them or not, but I got my IMEI data back
Decided all this was too much hassle, so I reset my flash count to zero with this: http://forum.xda-developers.com/showthread.php?t=1494114
Reverted to stock 4.1.2 from AT&T and reset to factory
Still stuck on Edge:2
Found this thread: http://forum.xda-developers.com/showthread.php?t=2036891 my phone won't let me change my band preference, also under *#197328640#>SIM>CHECK NV it say "Band perf: Unexpected value"
Question:
Where do I go from here?
Thanks!
Click to expand...
Click to collapse
This just happened to me too. I backed up my IMEI but lost it and had to get a new phone. I used QPST tool to restore my IMEI , which is located behind your battery. I did not work. There is another tool called NV Generate or something like that and still it did not work. I did not like spending the money for a warranty replacement, of course, so looked and tried hard for a fix. Since nothing worked I am also thinking that its possible I had a hardware problem, but I can say that an IMEI issue can be as bad as hardbricking, so proceed with caution and follow to a T. Good luck bro. I hope you can fix it. Let me know if you have a chance.
Edit: I missed the part about you using NV tool. I spoke with a bunch of Att help and a Samsung guy as well. Nobody knew about it. Mine was 5 freaking days past warranty. Still sick from that. If you are under warranty. Take it back.
I'm also having these issues..
Anyone have a true fix? I would go back to Full Stock, but have already tried that and still had the data issues. Something is hosed that needs to be fixed..
Fixed!!
I bought a new phone from AT&T, copied the nv config using the instructions here:
http://forum.xda-developers.com/showthread.php?t=1804117
Changed the IMEI to my phone's IMEI, and EUREKA! It works!
I'm attaching the file I used (with the IMEI blanked out, so be sure to fill in our own IMEI or this won't work for you, it is section 550, see http://forum.xda-developers.com/showthread.php?t=1804117 for more details).
I hope this helps others, and they don't have to pay the $35 restocking fee.
thabin said:
I bought a new phone from AT&T, copied the nv config using the instructions here:
http://forum.xda-developers.com/showthread.php?t=1804117
Changed the IMEI to my phone's IMEI, and EUREKA! It works!
I'm attaching the file I used (with the IMEI blanked out, so be sure to fill in our own IMEI or this won't work for you, it is section 550, see http://forum.xda-developers.com/showthread.php?t=1804117 for more details).
I hope this helps others, and they don't have to pay the $35 restocking fee.
Click to expand...
Click to collapse
This is exactly what I need! Thank you! My usb is corroded so I cannot connect usb and will have to load this manually. Could you please tell me the exact process you used to add your EMEI # to the file? I have opened the text file and went to section 550, but I do not know if i'm properly changing the number.
bweyadn said:
This is exactly what I need! Thank you! My usb is corroded so I cannot connect usb and will have to load this manually. Could you please tell me the exact process you used to add your EMEI # to the file? I have opened the text file and went to section 550, but I do not know if i'm properly changing the number.
Click to expand...
Click to collapse
I fixed the IMEI using the following instructions:
http://forum.xda-developers.com/showthread.php?t=1804117
The link on that page for the utility to generate a new IMEI didn't work, but I found another copy here:
http://forum.xda-developers.com/showthread.php?t=2335951
*WARNING* my virus checker freaked out about this file. I ran in on my kids machine (not mine) and it seemed to work fine, but I want you to be warned about the royal freakout my virus checker gave me.
thabin said:
I fixed the IMEI using the following instructions:
http://forum.xda-developers.com/showthread.php?t=1804117
The link on that page for the utility to generate a new IMEI didn't work, but I found another copy here:
http://forum.xda-developers.com/showthread.php?t=2335951
*WARNING* my virus checker freaked out about this file. I ran in on my kids machine (not mine) and it seemed to work fine, but I want you to be warned about the royal freakout my virus checker gave me.
Click to expand...
Click to collapse
I got almost just the identical problem... However, I checked my phone and my IMEI number is still intact... yet im stuck on EDGE
story was that I brought my rooted S3 from ATT (but not unlocked) to China 2 weeks ago hoping to use the phone on China Mobile's network (though knowing that China Mobile doesnt support the same band for 3g/4g as the US).
It wasn't til after inserting the sim that I realized I havent unlocked the phone yet... and since ATT won't give me the unlock code, I ended up trying to use the *#197328640# method, which was unsuccessful because I was still on ICS and this method requires Jellybean.
So in a hurry I used odin to upgrade to a jellybean version that apparently wasn't compatible with my I747.
After taking to a local shop, the dude repairing my phone was able to get the OS running again but it was weird in that even with an ATT sim card the phone would ask for an unlock code.
So finally after doing the re-flash of the official ATT I747 Jellybean rom, I was able to get into the *#197328640# menu and unlock my phone using
the second method mentioned in here: http://www.wikihow.com/Unlock-Samsung-Galaxy-Siii-(S3)
I was happy to get it to work with China Mobile's sim even though I can only use EDGE over there, but I also realize the dreafully long wait time for the phone to get a signal from power on.
After coming back to the States today and inserting my original ATT sim card, I noticed that it still takes a long time for the phone to get a signal after power on and after it acquires the signal from ATT, Im only getting signal (feels almost like the phone is stuck in the international setting...)
I have tried to reflash to z999 rom with cwm, tried to reflash the modem firmware, nothing is working.
My IMEI is still showing up in the "status" under about this phone, and its the same number as it appears in the back of the phone...
but for some reason I feel like this might have something to do with the fiddling of the secret code menu during my unlock oversea... since I had to go into the UMTS menu (which I believe is for EDGE)...
Since my IMEI isnt lost... anyone have any ideas what could have been the problem? This is getting beyond frustrating... would really appreciate the help!
I just bought this metro s3 and wanted to root it, well supersu was giving error everytime I tapped it so I decided to try an unroot with many of the methods on here and along the way ended up where my phone will not get past the galaxy siii sgh-t999n boot screen.
I used odin to do this, my phone is not being recognized under auto play but pc makes the connection sound when I plug usb in to my pc.
anyways I'm stuck at that screen and can only enter odin recovery on my phone and I have tried factory reset and still end up at the same boot screen and left it like that all night an woke up to the same screen.
I'm hoping this is not not a $300. brick.
I did download the files from a thread that described the files below were for the "T999l & T999n" and IF there was any difference int he files then the OP would point that out he said and I tripple checked to make sure in the section of the listed files to download did not mention the T999n was not for those specific files but there was nothing mentioned..
Please link the said thread.
You have not specified the firmware and android version you had before all this happened. Please specify that. Next Course of action depends on as much information you could provide about previous setup, Bootloader, Rom, Kernel & Baseband.
I think you only have a Non-Bootable Rom. I'd call that as a soft-Brick and not Hard-Brick. So there's no chance of you getting a $300 Paperweight. :laugh:
Having said that, given that all you want is Root, then
1. Flash Root66 version of your Firmware.
Perseus71 said:
Please link the said thread.
You have not specified the firmware and android version you had before all this happened. Please specify that. Next Course of action depends on as much information you could provide about previous setup, Bootloader, Rom, Kernel & Baseband.
I think you only have a Non-Bootable Rom. I'd call that as a soft-Brick and not Hard-Brick. So there's no chance of you getting a $300 Paperweight. :laugh:
Having said that, given that all you want is Root, then
1. Flash Root66 version of your Firmware.
Click to expand...
Click to collapse
Well I have solved my boot issues my installing CWM (which before would not stick after boot) and flashing 3 files from Docholiday on a thread but now the phone boots up as a T999L 4g LTE and has changed the model number under about phone. I have to unlock the phone as I only have a tmobile sim for this said Metropcs T999N device so I will see what happens after I try to unlock it.
thanks you for your prompt response!!
If Settings > About > Model is the only problem you have, then use Build.prop Editor from Playstore and change the value for RO.BUILD.DISPLAY.ID. Set it to what your device is.
Im not bothered by it myself as long as it wont effect my device?? also effect any future updates or when a program tries to sync with my device or anything other??
I don't believe there would be issues of this nature.
So, I recently bought a galaxy s4 from ebay, and it seems to work on the network, so I don't think the IMEI is blacklisted. However, when I tried the steps here http://forum.xda-developers.com/showthread.php?t=2282683 and here http://forum.xda-developers.com/showthread.php?t=2283068, I am unable to complete the process. When I do the latter, which seems more like what I did with my S3, I get the same message "unable to process request". I remember I was getting this message on my S3 when I had the SlimKat ROM on it. But when I look at my S4, it looks like it has the OEM ROM on it, so I am not sure what is happening. I looked at my boot loader/baseband, and this is what I have: m919uvufnh7. I know that with my S3 I had to make sure I used the correct ROM to flash my phone, so I could get it unlocked the free method. So, does anyone know what bootloader and ROM could help me accomplish these steps in the second thread?
I am thinking I should flash a different ROM on my phone.
mji2015 said:
So, I recently bought a galaxy s4 from ebay, and it seems to work on the network, so I don't think the IMEI is blacklisted. However, when I tried the steps here http://forum.xda-developers.com/showthread.php?t=2282683 and here http://forum.xda-developers.com/showthread.php?t=2283068, I am unable to complete the process. When I do the latter, which seems more like what I did with my S3, I get the same message "unable to process request". I remember I was getting this message on my S3 when I had the SlimKat ROM on it. But when I look at my S4, it looks like it has the OEM ROM on it, so I am not sure what is happening. I looked at my boot loader/baseband, and this is what I have: m919uvufnh7. I know that with my S3 I had to make sure I used the correct ROM to flash my phone, so I could get it unlocked the free method. So, does anyone know what bootloader and ROM could help me accomplish these steps in the second thread?
I am thinking I should flash a different ROM on my phone.
Click to expand...
Click to collapse
Have you tried contacting T-Mobile? If the phone is paid for in full, they are supposed to unlock it for free.
This worked for me:
http://forum.xda-developers.com/showthread.php?p=58645651
Sent from my SGH-M919 using XDA Free mobile app
rlichtefeld said:
Have you tried contacting T-Mobile? If the phone is paid for in full, they are supposed to unlock it for free.
Click to expand...
Click to collapse
Thanks for the response, but I have not tried it, because I don't think it is that easy. I also purchased AT&T tablets and tried unlocking them, but AT&T said they were 'active' under someone else. They were not not showing as stolen, but active. I am not sure what that entails, but I am guessing I have to register it under my account first, before I can request to unlock it. So before I try going through the long process of figuring out how T-Mobile can unlock my device, I thought I would give this a try. It seems simpler and since I plan on modding my phone after I unlock it, I see it as just part of the process. (At least I hope so.)
radoo7701 said:
This worked for me:
http://forum.xda-developers.com/showthread.php?p=58645651
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
I will try this. But I was trying to make sure that there was no problem with downgrading, as I am currently on 4.4.4. And I know that on my S3 there was a big warning about downgrading from 4.3 to 4.1. To avoid bricking my phone, I thought I would ask and make sure.
So thanks again to both of you for the responses!
I will try this. But I was trying to make sure that there was no problem with downgrading, as I am currently on 4.4.4. And I know that on my S3 there was a big warning about downgrading from 4.3 to 4.1. To avoid bricking my phone, I thought I would ask and make sure.
So thanks again to both of you for the responses![/QUOTE]
You only have to downgrade the modem. This should not brick your phone.
Sent from my SGH-M919 using XDA Free mobile app
Would you please posts step by step on what you did to successfully unlock 4.4.4 T-Mobile which I assume is version M919UVUFNK2.
How to Unlock Samsung Galaxy S4 M919 4.4.4
c627627 said:
Would you please posts step by step on what you did to successfully unlock 4.4.4 T-Mobile which I assume is version M919UVUFNK2.
Click to expand...
Click to collapse
Alright, I was able to get mine to work, so maybe I will list my steps. However, I must say that I had some failed attempts (in part due to not understanding the post referred to by radoo7701) and some issues with my phone. But those steps wont be included. Also, my version was m919uvufnh7, not NK2. I would think it does not make a difference, as long as you reflash back to NK2 at the end.
1. I locaed the modem for M919UVUAMDL and m919uvufnh7 modem (as I did not make a backup of mine before starting)
2. I used Odin 3.07 to flash the AMDL modem
3. I tried the steps here http://forum.xda-developers.com/showthread.php?t=2283068, but this would not work, I could not even get the menu to pull up, as it would say request unable to complete. So I tried this http://forum.xda-developers.com/showthread.php?t=2282683 and that actually worked, so I went through these steps successfully.
4. Use cf-auto-root to root your phone
5. Download regionlockaway and transfer it to phone, then install it on phone and run it.
6. flash m919uvufnh7 modem and booted up with my AT&T sim, and it did not ask for unlock code. It just worked!
NOTE: I did have to use a T-Mobile sim card to do the menu process, but radoo claims that he did not do the menu portion. I had already done the menu portion when I finally got to reading his comment. So I can't say that it will work or not. Either way, his suggestion worked for me and I am content with the result!
Thanks radoo7701!
Please post link to files in step 1 you specifically used. And also links for step 5 you used.
Please help me with my situations.
It is almost 1 week phone start making this problem. From beginning my phone getting boot loop. I have not root the phone. It is originally stock rom. I thought that the system get corrupted and then try to flash the phone with stock rom N7100XXUFNG4_N7100OLBFNG1_N7100DXUFND2_HOME.tar with odin.
This was my first time flashing this phone so I did not know anything about any EFS backup. After successfuly flashing the stock rom, at first I feel glad but suddenly I have got emergency call only. Then after what I have been searching and reading for almost a week, it was my IMEI 0049.
I have tried flash the stock rom again but the problem still remain. I have tried downgrade to 4.1.2 but the odin won't let me flash it. I have tried delete the EFS folder and paste the backup nv_data.bin but the IMEI 0049 still there. I don't have any service box so I can't repair my EFS from my computer. Is there any solutions I really really appreciate if and you guys can help with my problem. Thank you :good:
Did the imei in the phone match the imei on the label under the battery?
audit13 said:
Did the imei in the phone match the imei on the label under the battery?
Click to expand...
Click to collapse
Of course not, usually IMEI starts with 3***.
I know your phone has a generic imei.
What I meant is this: did the imei in the phone matched the imei on label before the problem started.
The phone was new when you got it?
audit13 said:
I know your phone has a generic imei.
What I meant is this: did the imei in the phone matched the imei on label before the problem started.
The phone was new when you got it?
Click to expand...
Click to collapse
Ops sorry, yes it was matched and the phone working perfectly normal before it getting boot loop. Can my phone still can be save without sending to samsung?
You try using nvwriter to inject the imei.
Have you tried flashing the stock rom again? I assume nd2 is the latest rom for your phone.
audit13 said:
You try using nvwriter to inject the imei.
Have you tried flashing the stock rom again? I assume nd2 is the latest rom for your phone.
Click to expand...
Click to collapse
I have not try the other version firmware yet, is it possible the wrong firmware corrupted my imei?
It is possible that the ROM flashed is too old.
I see stock ROMs here: http://www.sammobile.com/firmwares/database/GT-N7100/
audit13 said:
It is possible that the ROM flashed is too old.
I see stock ROMs here: http://www.sammobile.com/firmwares/database/GT-N7100/
Click to expand...
Click to collapse
Can you suggest me stock firmware? I am from Malaysia
I don't see firmware specifically for Malaysia. What is the original country or carrier for the phone? Where did you get the firmware that you flashed to the phone?
audit13 said:
I don't see firmware specifically for Malaysia. What is the original country or carrier for the phone? Where did you get the firmware that you flashed to the phone?
Click to expand...
Click to collapse
Well my country carrier starts with +6. I just ask my cousin to download that firmware for me since my house internet always disconnected I don't know why. I just ask him to download the latest firmware for my country.
That nvwriter guide is not for my phone. Is it work also with my phone?
Sorry, I'm not too familiar with nvwriter. I just know that some people have used it with Samsung phones.
The nv writer look promising, but it cannot read my phone cause when I select the rmnet/rndis/+dm+modem, it is only showing unknown device. Hmm my samsung usb driver already up to date.
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