Related
Here goes the story
I have an HD7 from Bell Mobility and unlocked as soon as i got it with chevron unlocker. Updated officially to pre-NoDo with phone still unlocked as usual.
Then just about a week ago i got impatient and flashed my phone with custom NoDo rom which was working fine without any issue.
After reading alot about the possibility of still having an unlocked (with work aound)phone after Updating through Zune. I decided to flash back the original rom from Bell (7004).
Issue is after flashing, i tried unlocking using chevron unlocker but it does not work and i get this error message (attached).
I have tried all the trouble shooting i can find here and through googling still same error message
Anyone have this problem and what is the solution to getting my phone unlocked again.
thanks
redoxy said:
Here goes the story
I have an HD7 from Bell Mobility and unlocked as soon as i got it with chevron unlocker. Updated officially to pre-NoDo with phone still unlocked as usual.
Then just about a week ago i got impatient and flashed my phone with custom NoDo rom which was working fine without any issue.
After reading alot about the possibility of still having an unlocked (with work aound)phone after Updating through Zune. I decided to flash back the original rom from Bell (7004).
Issue is after flashing, i tried unlocking using chevron unlocker but it does not work and i get this error message (attached).
I have tried all the trouble shooting i can find here and through googling still same error message
Anyone have this problem and what is the solution to getting my phone unlocked again.
thanks
Click to expand...
Click to collapse
try install the certificate again to see if works
jgcaap said:
try install the certificate again to see if works
Click to expand...
Click to collapse
tried that again but still same error message
thanks anyway
redoxy said:
tried that again but still same error message
thanks anyway
Click to expand...
Click to collapse
Did you also switch your phone off and back on and then try to unlock? My experience is that certificates only work after restarting the phone.
Heathcliff74 said:
Did you also switch your phone off and back on and then try to unlock? My experience is that certificates only work after restarting the phone.
Click to expand...
Click to collapse
Yep did that also. and not just once but multiple times.
Wonder why this is happening
redoxy said:
Yep did that also. and not just once but multiple times.
Wonder why this is happening
Click to expand...
Click to collapse
I've came across this error little while back as I tend flash back and forth, was at a loss until I did the following:
Navigate to c:\windows\system32\drivers\etc\ then open hosts with notepad and delete any references to windowsphone developer services
Note: as it's system file you may need to take ownership otherwise you will not be able to edit it!
hope this helps you!
gfreek said:
I've came across this error little while back as I tend flash back and forth, was at a loss until I did the following:
Navigate to c:\windows\system32\drivers\etc\ then open hosts with notepad and delete any references to windowsphone developer services
Note: as it's system file you may need to take ownership otherwise you will not be able to edit it!
hope this helps you!
Click to expand...
Click to collapse
Did Exactly as you instructed and it worked.
thanks
I have a message on my phone about a new firmware/software update ready to be installed.
Am on ATT LG E980.....Anybody else seeing this????
EDIT: It's only ~5MB so it cannot be a major update. It must be the previous update I never installed....and I am sure it will break my root and phone !!! But that was months ago ?
Why are they trying to push it again? Or is it a new one? Don't know...
But don't install any new update since it is not a major one. Quite sure it will soft brick the phone like the last one. ATT and their old tricks.
Last version was 20h..is this one the same or some different version number?
Sent from my LG-E980 using XDA Free mobile app
I dont know the version number because I did not download it yet. Will do and report.
What version is your G Pro right now? If its 20H then it looks like you have found a new update.
Mine is 20H on ATT and no updates are available.
.
Did it actually soft-brick you? My wife mentioned something about an update right before her phone soft bricked. And, what makes things even more fun, the last update soft bricked her AND screwed up things so that I can't even connect to USB to flash back to stock (Unknown device)
ixijimixi said:
Did it actually soft-brick you? My wife mentioned something about an update right before her phone soft bricked. And, what makes things even more fun, the last update soft bricked her AND screwed up things so that I can't even connect to USB to flash back to stock (Unknown device)
Click to expand...
Click to collapse
This should help
http://forum.xda-developers.com/showthread.php?t=2420219
Your usb will work with the right drivers. No update will hardbrick your usb
Thanks, but I've already those drivers up to the brand new ones on the LG website, no dice. If the update didn't cause it, it was sure the worst case of coincidence I've had in a long time
Didn't mean to highjack, was just wondering if anyone had that same extra symptom.
Anyone know how I can turn off the update notification?
channeledbymodem said:
Anyone know how I can turn off the update notification?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2394892
You need root.
Flaco05 said:
http://forum.xda-developers.com/showthread.php?t=2394892
You need root.
Click to expand...
Click to collapse
There's an easier way: just disable "Software Update" in Settings/Apps.
channeledbymodem said:
There's an easier way: just disable "Software Update" in Settings/Apps.
Click to expand...
Click to collapse
I spoke too soon Today the update was forced on me which since I am rooted soft bricked the phone. I guess when I finally get it back I'll follow the advice in the thread Flaco linked to. Thanks.
I got my phone around the begining of last month and decided the other night that it was time to root as I have rooted every android device I have owned since the wildfire s. I had previously taken the OTA so I was on vs98512b. I used LG flashtool to downgrade to vs98510b. The downgrade it's self went fine. I then rooted using stumproot again nothing out of the ordinary. I downloaded Supersu and enabled survival mode. I tried to check for New updates and it says "your phone is not registered" I found that to be strange so I checked some other settings and found that my imei was 000000000000000. I found that to be strange. I attempted to make a call and my phone switched to roaming and I lost all my signal bars. I performed a factory reset and after the reset I have all network function, I'm connected to Verizon 4g lte and can make calls, no more roaming. I checked the imei again at this point and it is still showing 000000000000000 and I was still unable to update. So I then reflashed the stock firmware for vs98510b. Again I had the roaming issue that went into being unable to connect to network. Again I performed a hard rest on my phone and got full network function back. I had a new micro SIM tucked away for a rainy day so I put the New SIM card in and activated it with no change to imei. What can I do from here? My phone is working fine with the imei being 000000000000000 it seems like the only issue is not being able to get an OTA, when I try using Verizon's upgrade assistant it won't even list my phone. If I check my Verizon it shows up as a non vow device. Thanks in advanced.
wcallah04 said:
I got my phone around the begining of last month and decided the other night that it was time to root as I have rooted every android device I have owned since the wildfire s. I had previously taken the OTA so I was on vs98512b. I used LG flashtool to downgrade to vs98510b. The downgrade it's self went fine. I then rooted using stumproot again nothing out of the ordinary. I downloaded Supersu and enabled survival mode. I tried to check for New updates and it says "your phone is not registered" I found that to be strange so I checked some other settings and found that my imei was 000000000000000. I found that to be strange. I attempted to make a call and my phone switched to roaming and I lost all my signal bars. I performed a factory reset and after the reset I have all network function, I'm connected to Verizon 4g lte and can make calls, no more roaming. I checked the imei again at this point and it is still showing 000000000000000 and I was still unable to update. So I then reflashed the stock firmware for vs98510b. Again I had the roaming issue that went into being unable to connect to network. Again I performed a hard rest on my phone and got full network function back. I had a new micro SIM tucked away for a rainy day so I put the New SIM card in and activated it with no change to imei. What can I do from here? My phone is working fine with the imei being 000000000000000 it seems like the only issue is not being able to get an OTA, when I try using Verizon's upgrade assistant it won't even list my phone. If I check my Verizon it shows up as a non vow device. Thanks in advanced.
Click to expand...
Click to collapse
have you backuped the efs partition like the rooting thread said
Of course not. That would have been to easy. If I had I would have been able to avoid making a new thread. I really do Google first. Except with the back up of the eds partition. I knew nothing about that until I searched imei problems.
wcallah04 said:
I got my phone around the begining of last month and decided the other night that it was time to root as I have rooted every android device I have owned since the wildfire s. I had previously taken the OTA so I was on vs98512b. I used LG flashtool to downgrade to vs98510b. The downgrade it's self went fine. I then rooted using stumproot again nothing out of the ordinary. I downloaded Supersu and enabled survival mode. I tried to check for New updates and it says "your phone is not registered" I found that to be strange so I checked some other settings and found that my imei was 000000000000000. I found that to be strange. I attempted to make a call and my phone switched to roaming and I lost all my signal bars. I performed a factory reset and after the reset I have all network function, I'm connected to Verizon 4g lte and can make calls, no more roaming. I checked the imei again at this point and it is still showing 000000000000000 and I was still unable to update. So I then reflashed the stock firmware for vs98510b. Again I had the roaming issue that went into being unable to connect to network. Again I performed a hard rest on my phone and got full network function back. I had a new micro SIM tucked away for a rainy day so I put the New SIM card in and activated it with no change to imei. What can I do from here? My phone is working fine with the imei being 000000000000000 it seems like the only issue is not being able to get an OTA, when I try using Verizon's upgrade assistant it won't even list my phone. If I check my Verizon it shows up as a non vow device. Thanks in advanced.
Click to expand...
Click to collapse
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
please note i did it a little different then the instructions...i didnt use a1 or b1 instruction bc it was different for my phone..
crazy4android said:
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
please note i did it a little different then the instructions...i didnt use a1 or b1 instruction bc it was different for my phone..
Click to expand...
Click to collapse
Did it put your imei back in? Or just made it so you can talk and text?
wcallah04 said:
Did it put your imei back in? Or just made it so you can talk and text?
Click to expand...
Click to collapse
i rewrote my orignal imei...u can change it if u want but its illeagal...but who cares...i just fixed mine...and data and everything works perfectly...even using at&t on a verizon phone and it humming like a humming bird... its not hard or complicated....very simple dont even have to get nervous...
That's all I need is to put my imei back in. Lol I'll try it as soon as I get home from work. Thanks.
crazy4android said:
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
please note i did it a little different then the instructions...i didnt use a1 or b1 instruction bc it was different for my phone..
Click to expand...
Click to collapse
No luck. I can't get my phone to diag mode.
suljo94 said:
have you backuped the efs partition like the rooting thread said
Click to expand...
Click to collapse
Is it possible to backup my efs prior to gaining root access?
wcallah04 said:
No luck. I can't get my phone to diag mode.
Click to expand...
Click to collapse
which service provider did u use...with verizon i used ##228378 in the dialer code nd i left it in the menu that pop up nd on my pc it showed up a a serial com port...make sure ur drivers are working properly...nd when connecting to cdma tool u pick serial port...
crazy4android said:
which service provider did u use...with verizon i used ##228378 in the dialer code nd i left it in the menu that pop up nd on my pc it showed up a a serial com port...make sure ur drivers are working properly...nd when connecting to cdma tool u pick serial port...
Click to expand...
Click to collapse
Hmmm... I have verizon. The only thing I can get the cdma tool to to connect to is the modem port. Nothing else replies...
wcallah04 said:
Hmmm... I have verizon. The only thing I can get the cdma tool to to connect to is the modem port. Nothing else replies...
Click to expand...
Click to collapse
hey check out this tool...i also used this once...it worked great..http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546 first open efs professional.exe./qualcomm nv tool/...connect to port for the drop down menu on top...i used serial since thats the only one that responded...then press connect...then try and read phone info to see if it sees ur phone...then go to the secure ops tab.....select the imei(dec) box and enter ur imei and then write it...then select meid(hex) box.....write ur meid...same as imei minus the last digit.... thats the best instruction i can give on the top of my head..i did it a while ago...so if confused feel free to ask questions...
VS985: Lost IMEI, Can't Make Phone Calls
I'm having problems with my VS985 after downgrading including losing the IMEI and especially the ability to make phone calls.
So I got a used VS985W that had 35B installed on it for one of my kids. Having put CyanogenMod on my LG G3 (VS985) successfully, I started down that path. I used the TOT method to flash back to 10B, then used KDZ to upgrade to 12B. Then I rooted, installed TWRP, and then CyanogenMod. But I couldn't make phone calls.
There are numerous things I've tried, but it's still unable to make phone calls, usually giving out of service area, but when trying to use the *#06# code, I get an error of "missing IMMI or such".
At one point I found the IMEI had gone to all zeros. I managed to find a method to fix that. I also switched out SIM cards between phones; same issue - it's the phone and firmware.
The only thing that seems to fix it is to go back to stock 35B. Then it makes phone calls. But then I can't root it and restore the apps/data we backed up from the previous phone (LG Spectrum running CM 11).
I have done hours of searching and reading these forums along with others. I've redone the downgrade and root and TWRP install and tried numerous things but still can't get phones calls in stock versions less than 35B or in CyanogenMod (12.1, not 13, which I did try to install but never could get it to reliably boot back up after an installation, so finally gave up and went back to 12.1).
Anyone heard of this before? I can't find it. I did see in this thread post #4:
Google~Android said:
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
Click to expand...
Click to collapse
Unfortunately this link doesn't work (moved or deleted). I'm continuing to search, but it almost seems like I managed to royally muck up some partition I didn't mean to? I've tried following the advice of a number of posts, too, on related, similar aspects, but I'm getting to a point of slight insanity. Along with a kid that wants their phone (and the old one has the older style SIM so not just that easy to deal with just switching unfortunately).
Any guidance or thoughts Much appreciated. Am going to continue to try the various things I'm reading about. Thanks, -Mark
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
JRSouth said:
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
Click to expand...
Click to collapse
i have the exact problem since saturday, you have to use the ATT firmware but i couldnt find it anywhere
also
please pm me if u fixed yours
Lactaid said:
please pm me if u fixed yours
Click to expand...
Click to collapse
Still no luck. I'm sure if we could find the AT&T firmware we would be able to recover. Unfortunately it appears it is not available on ASUS support and AT&T doesn't even provide firmware. Our only hope may be from a backup of another device that isn't bricked.
Does anybody know if we could possibly use the temporary CWM recovery used in the root method to flash to another ROM that is compatible with this device? Any input would be greatly appreciated.
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
JRSouth said:
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
Click to expand...
Click to collapse
ive literally tried everything, my device has been bricked for like 3 weeks now
Lactaid said:
ive literally tried everything, my device has been bricked for like 3 weeks now
Click to expand...
Click to collapse
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
JRSouth said:
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
Click to expand...
Click to collapse
i havent tried it yet, do you have a tutorial of it?
The truth hurts, your screwd. This is a budget phone. At&t will not support it. Throw away device my their standards.
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
http://forum.xda-developers.com/showpost.php?p=63323103&postcount=118
^^^This worked for me successfully!
Make sure to only restore system and disable MD5 Checksum Verification.
I have the same problem, what do I do with that file? How do I apply it through the SD, so I can apply update from SD? I forgot pin code to phone so i need to restore
need help
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
how do I flash this?
Hola, alguien lo consiguió hacer..???
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
Im getting an error that day footer is wrong :/
m1chb3ltr3 said:
Im getting an error that day footer is wrong :/
Click to expand...
Click to collapse
Wait, are you bricked and tried using that as the fix? I cant post links but Check out Asus, They have Firmware, Kernel (havent checked but read it earlier today), and Boot Unlock that you can get right from (assuming you have an account) My Products.
Also... Has anyone used that method recently?
Cathaterfish said:
Sorry I will give credit to DavePmer for his guide in minute, but qouting him for some reason wouldnt let me post, even when I removed the links? anyways I'll edit and give credit I promise
So my phone is stuck on the Asus Logo, I downloaded all of this and followed the instructions all the way up to:
11) now the fun part. open your microsd card and check the folder TWRP\BACKUPS see if it has a folder named
01234567890123456789 if it does great if not, not a problem just copy all the system files from the folder
you extracted TWRP-zf2e-ATT_12.16.10.7 to your microsd card TWRP\BACKUP\01234567890123456789\ whatever folder you have next\ in other words, replace your system.ext4.win000 files with my system.ext4.win000 file.
Replace your system.ext4.win001 with mine, and replace system.ext4.win00.md5 with mine as well as system.ext4.win001.md5 when done safely dismount the microsd card.
It then occurred to me that i should be more careful this time around... This was from October and although I ran across links saying for the most part that this was a good shot for fixing my ZE500CL, Z00D or whatever. But things have changed since then and I was wondering if this is still the best/easiest/safe route. I learned pretty quick that over looking things like OTA/Root or in my case Making assumptions is a fast path to really doing a number on your phone. (Honestly I just started even giving thought to rooting my phone, just considered them back ups I kept in a box). I now have the itch to do this right so hoping to fix this and go about this the right way.
Thanks for any input.
Currently DLing RussaiNBeaR, went and bought a card reader/writer. I was going to Download the firmware, kernel and boot unlock tool but currently staying at a place where im getting 160kbs on my DL's. So if I can get away with davepmer's guide that would be great, or something other or smaller than downloading 4gbs on this Internet Connection.
EDIT: Forgot to add that I haven't completed this step yet because the wording kind of tripped me up. And I want to do this right. When he says "in other words replace your system.ext4.win000 files with my system.ext4.win000 file." and then goes on and 3 more to the list. Does that mean only copy and replace those 4? or does that include all system.(whatever).(extension) files? Im sure it sounds really dumb or noobish but the fact that the next step is using twrp to restore using system only makes me afraid to do this part wrong.
Click to expand...
Click to collapse
ayuda
ATT ZE500CL/Z00D rom
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