Related
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
iBowToAndroid said:
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
Click to expand...
Click to collapse
I have a similar issue, could this be fixed with a Z3X Box?
you could try this method . . .
https://www.youtube.com/watch?v=ggRhkme9FC0
if for any reason didn't work try this one
https://www.youtube.com/watch?v=KRUp09bXnDA
JeffB81 said:
I have a similar issue, could this be fixed with a Z3X Box?
Click to expand...
Click to collapse
Yes it can be, do you have one?
discomaniac said:
Yes it can be, do you have one?
Click to expand...
Click to collapse
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
You took off FRP lock with software?
JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
Confirm?
vazersecurity said:
Confirm?
Click to expand...
Click to collapse
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
crazynapkinman said:
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
Click to expand...
Click to collapse
Incorrect. FRP is held in a partition that is not touched during a firmware flash
vazersecurity said:
Confirm?
Click to expand...
Click to collapse
iBowToAndroid said:
Incorrect. FRP is held in a partition that is not touched during a firmware flash
Click to expand...
Click to collapse
Then what about this Cl3? Are there steps after flashing the firmware?
crazynapkinman said:
Then what about this Cl3? Are there steps after flashing the firmware?
Click to expand...
Click to collapse
Flashing firmware can't fix an FRP lock - period.
If you want to know what that poster meant by his message, I suggest you ask him directly
Samsung phones can be frp unlocked by flashing firmware
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Bullshipcaptcha said:
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Click to expand...
Click to collapse
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
That doesn't matter when the phone no longer has a persistent partition.
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Bullshipcaptcha said:
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Click to expand...
Click to collapse
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like system, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Your going to need to go against the grain her a moment . Business or no business
iBowToAndroid said:
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like tem, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Click to expand...
Click to collapse
I'm telling you. I'm not debating the facts. Im telling you what I did. Kinda like I did today with a Moto e4 play. I bypassed frp with flashing stock rom through Odin and then custom rom on the Samsung J7. Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked . I don't have a business in the phones field but I am a business man and sittin on 12 frp locked phones gets tire some. Thant goodness for broken digitizers and displays or I'd still have a bunch more of them. I wont dipute that you know what your doing because likely you do more so than I; we can can probably be certain. I'm just going to tell you the 100 percent fact. Upset wife as my motivating factor I successfully unlocked and rooted a j7 by flashing stock rom into it with Odin then custom reccovery then root then custom rom. The custom recovery I used by accident was for a different brand Jay 7 so mysecond time around I tried the "right" recovery and bricked it. Then again and again and again until Knox was tripped and that's when finally I took bl,ap cp, csc and flashed them in dl mode successfully from there I had Rob from simple cell unlock ( Thanks Rob your the best) remotely unlock the jay7 from T-Mobile after which I flashed the "wrong" proper twrp file giving me the ability to install custom note 8 dna rom into the system. Took two tries, first try I flashed no encrypt no verity but it custom rom frp locked. So second time I made sure I install the developer tools package with OEM unlock switch not able to be turned off then no encrypt no verity. It was a very long process since especially since it was only my second successful full root. Then vallet. Man becomes praised by wife. Man feels empowered man tears apart more phones makes mess, MAN HAPPY! WIFE HAPPY! LOL okay sorry about that part.
---------- Post added at 04:18 PM ---------- Previous post was at 04:06 PM ----------
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
None the less each developer has a different approach that being said you frp unlocking phones? I have a Samsung s8 Moto e5 five LGs one zte n835 a couple of alcatels and a few more I couple reassemble real quick If I knew some one who had the abilitby to unlock especially if said amazing developer was teaching El padawan young Como. Yo tango mucho programs, apps and software. Just need the knowledge.
Bullshipcaptcha said:
Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked
Click to expand...
Click to collapse
Thinking you can flash TWRP on a locked bootloader device shows me exactly what your knowledge level is when it comes to all of this. Future discussion would be futile, and no more responses from me will be had. I do wish you luck with your devices though
How frustrating you are.
Your business need some schooling it sounds like. Your business can't be doing good. Go ahead and Google the Moto e4 unlock method. You will see. You have to try before you say it won't work.
discomaniac said:
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Click to expand...
Click to collapse
I just removed the frp lock on my s6 using a combination firmware (found here-https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=7410) which completely erased all partions and allowed me to access the settings menu to enable the OEM unlock setting. They are two different firmware there. I used the second one and it worked like a charm. Hope this helps
Edit: The Verizon repair assistant put my phone back to PHE build [100% battery].
Man I knew I shouldn't have tried to root after all this time. I'm not sure which firmware my phone was on [it was the 60% battery update], either PHE or PK1, as it displays in recovery right now. I tried to follow Lrileys modification of freeza's root guide, which neither of them specify a base firmware to go off of, lol.
Anyways, flashing the userdebug sprint firmware with ODIN 3.12.4 failed and my device softbricked. It boots into recovery and download mode.
I have tried factory reset, wiping cache partition, flashing an AP PH1 firmware, and repair through Verizon software/upgrade assistant.
The closest I've gotten to restoring it was with VUA, however when I go to the repair assistant page, it tells me to put phone in download mode [which I do] but the repair button stays greyed out.
Any help would be greatly appreciated.
Edit: The Verizon Upgrade Assistant wasn't starting, saying it was missing mfc90.dll. Well I downloaded the dll, dropped it in the folder, and was able to get UA to recognize phone. Repair assistant is downloading software right now, we'll see how it goes.
IF you would have read there is no root for the PHE.. you also could have checked this via phone settings before you rooted.
You can also use the verizon app to restore your firmware from even the most bricked of phones. Also in in this forum..(looks like you might have tried this?)
I wouldnt even bother at this point, go get your temp phone =]
ars0n said:
IF you would have read there is no root for the PHE.. you also could have checked this via phone settings before you rooted.
You can also use the verizon app to restore your firmware from even the most bricked of phones. Also in in this forum..(looks like you might have tried this?)
I wouldnt even bother at this point, go get your temp phone =]
Click to expand...
Click to collapse
Well the repair assistant seems to be working atm, so hopefully it goes through without any problems. Neither of these threads in the original post mentioned anything about incompatible firmware though [https://forum.xda-developers.com/verizon-note-7/how-to/root-vzw-note-7-t3448711 and https://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202]. I suppose I should have known trying to use a method that dated.
You shouldn't be messing with this stuff if you don't even know how to see what version your on and read.
very helpful
jjayzx said:
You shouldn't be messing with this stuff if you don't even know how to see what version your on and read.
Click to expand...
Click to collapse
Thank you for the gratuitous reply. Despite your sour attitude I was able to return to PHE through VUA. I was running PK1 firmware, however, again, neither root method specified/recommended/listed a base or stock firmware to flash from [or even posted what they were running]. This place used to be helpful.
I've got a SM9600, purchased in US from BH Photo Video but it appears to be Spanish model and hence Samsung Pay wouldn't work.
Per some advice from random threads on internet, I factory reset it last night but that didn't change anything.
I now want to flash a US firmware but thought of checking with you guys first.
Two questions,
1. I noticed someone adviced not to flash a G960F/FD. Is it okay for G9600 to be flashed?
2. My biggest concern is of any side effect. Does flashing stock firmware change anything at all from stock behavior? I use the phone for work and the enrollment process is security sensitive. If there is any change in Knox status, device unlock status, rooting etc, I'll be out of work email access. It needs to be in stock condition
Also, if someone can guide me to the right firmware and guides, I'll appreciate it.
I have a us model if you wanna trade
Good day to everyone, well i have the same model but mine is for a customer it has been hard reset by the owner, but she does forget the google account on da phone, I was trying to flash it with a combination, it has given me an error frp is enabled not allowed to download non frp boot binary, i don't have a clue how to get ride of it.
Please help
Fulgor_ki said:
Good day to everyone, well i have the same model but mine is for a customer it has been hard reset by the owner, but she does forget the google account on da phone, I was trying to flash it with a combination, it has given me an error frp is enabled not allowed to download non frp boot binary, i don't have a clue how to get ride of it.
Please help
Click to expand...
Click to collapse
It would be best to start a new post rather than tack this on to another.
Fulgor_ki said:
Good day to everyone, well i have the same model but mine is for a customer it has been hard reset by the owner, but she does forget the google account on da phone, I was trying to flash it with a combination, it has given me an error frp is enabled not allowed to download non frp boot binary, i don't have a clue how to get ride of it.
Please help
Click to expand...
Click to collapse
Did she really forget her Google account
hi,
A70 is now widely sold, i try to buy one soonest but just waiting for root and twrp. it is still empty here on xda...
i found a link show how to root and install
https://myphoneupdate.com/samsung-galaxy-a70-twrp-recovery/
can i ask if some one already tried as above? looks like a copy method for all kind of phones ...
tks.
Most likely fake, the article was published a month ago. A70 only got released on 26th March.
I would definitely wait until someone posts a technique here; I tend to trust the experts here, but not so much everywhere else on the internet. I would prefer to wait a few weeks and put with an unrooted device, rather than possibly end up with a bricked (or hijacked) device.
Andre
ok i will wait...
it was like this, waited for s10+, came twrp but didnot like camera hole and waiting for A70, then waiting for twrp, then oneplus7pro release, then wait a bit for its twrp, till then note 10 pro comes soon, then wait for twrp of it....
and after 2+ year still using note8 LOL
amk said:
hi,
A70 is now widely sold, i try to buy one soonest but just waiting for root and twrp. it is still empty here on xda...
i found a link show how to root and install
https://myphoneupdate.com/samsung-galaxy-a70-twrp-recovery/
can i ask if some one already tried as above? looks like a copy method for all kind of phones ...
tks.
Click to expand...
Click to collapse
First thing I tried ofcourse, rooting the A70, but... follow the steps in the manual yourself, and you'll see that you get stuck on step 3:
3.) After That Download TWRP Recovery https://twrp.me File On Your PC And Renamed The Downloaded Recovery File Name To twrp.img.
But there is no TWRP Recovery available for the A70
I also tried the A50 manual, but that also fails (stuck on OEM lock). I can install CROM Service, but it crashes.
Captain Beretta said:
First thing I tried ofcourse, rooting the A70, but... follow the steps in the manual yourself, and you'll see that you get stuck on step 3:
3.) After That Download TWRP Recovery https://twrp.me File On Your PC And Renamed The Downloaded Recovery File Name To twrp.img.
But there is no TWRP Recovery available for the A70
I also tried the A50 manual, but that also fails (stuck on OEM lock). I can install CROM Service, but it crashes.
Click to expand...
Click to collapse
don't follow some clickbait website's...
wait for a proper and trusted dev to release twrp. the phones has barely hit the market it will take a few weeks (if not months) at least till someone builds an twrp. one think you could provide us with would be some information. is the bootloader unlockable?
In devsettings is a possible to unlock oem. Try this before flashing twrp. If twrp flashed ok, I think need to wipe all data, include internal storage, then flash DM-VERITY, FORCE ENCRYPTION, AND DISC QUOTA DISABLER
zackptg5.com/android.php
I don't try it by myself. But you can try it, if you just buy the phone, and have not important data on it
What about this guide is it worth trying or not really possible? https://topjohnwu.github.io/Magisk/install.html
Avicohen21 said:
What about this guide is it worth trying or not really possible? https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
Need to try
hello everyone I find a good deal on galaxy a70 is anyone succeed in rooting?
celoxocis said:
... is the bootloader unlockable?
Click to expand...
Click to collapse
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode. then got another with tick to choose. baterry is so good but look like i have touch panel issue. waiting for update and then root, twrp...
amk said:
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode.
Click to expand...
Click to collapse
Mine (bought direct from Samsung UK) has the OEM Unlock option in the Developer Options menu. Not tried it yet, not really much point until there is a reliable and tested root out there.
Andre
Hey guys manegd to root with this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Seems to work good I'll notify if I'll notice any bugs. If you have twrp porting guide send me and I'll try to Port. If you want I can open a new thread with more details and upload the AP file I used. BTW I have the Israeli version SM-705FN
Avicohen21 said:
Hey guys manegd to root with this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Seems to work good I'll notify if I'll notice any bugs. If you have twrp porting guide send me and I'll try to Port. If you want I can open a new thread with more details and upload the AP file I used. BTW I have the Israeli version SM-705FN
Click to expand...
Click to collapse
make a topic please
sanakess said:
make a topic please
Click to expand...
Click to collapse
Ok when I get home I'll open a thread with detailed explanation of what I did
Samsung account
Hello. My dumbass bought used A70 with samsung account. I can't make a factory reset, because it needs password from old owner account which i don't know. But I have my Google account on that phone and Google find my device enabled. Will I need to enter samsung account information when I make a reset via Google find my device? So when reset is made, phone will be locked only by FRP? And then when I login in my old Google account can i create a new Samsung account or do I need to login in existing that was on that phone first? Sorry for offtopic.
Any news about TWRP? SuperSu or Magisk?
Hello All, still can't find TWRP for sm-a705fn
Can I flash TWRP for another Exynos phone, like Galaxy 9, to my A70 ?
Also, can I still use SuperSu with Pie/A70 ? I failed to root my previous Galaxy Tab8 with custom Pie using SuperSU, had to root with Magisk instead,
it worked just fine, but the link to topjohnwu mentioned in previous posts, tells scary things about Samsung/Pie/Magisk -
like, I have to switch between two recoveries... Is that really the case?
I haven't noticed any issue with Tab8/Pie/Magisk, but SuperSu would be still more familiar to me.
used2brick said:
Hello All, still can't find TWRP for sm-a705fn
Can I flash TWRP for another Exynos phone, like Galaxy 9, to my A70 ?
Also, can I still use SuperSu with Pie/A70 ? I failed to root my previous Galaxy Tab8 with custom Pie using SuperSU, had to root with Magisk instead,
it worked just fine, but the link to topjohnwu mentioned in previous posts, tells scary things about Samsung/Pie/Magisk -
like, I have to switch between two recoveries... Is that really the case?
I haven't noticed any issue with Tab8/Pie/Magisk, but SuperSu would be still more familiar to me.
Click to expand...
Click to collapse
No, you can't use twrp for a different device, and don't use SuperSU neither. It was sold by chainfire to a Chinese company years ago and have been basically abandoned since 2017. I'm pretty sure Magisk is the better choice on any device running android 5 - 9.
Sent from my motorola one vision
Hello,
The problem with the post you mentioned is that there is no valid twrp attached. And I noticed that only Odin detects the fastboot mode of this device. If you enable USB debugging let's say, the command "adb devices" will detect the device and list it; whereas, if you reboot it to bootloader mode(fastboot), the command fastboot devices doesn't detect the phone. So in fastboot mode, only Odin will detect the device. Meaning, that the post of fake and not tested.
Regards,
Wael
amk said:
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode. then got another with tick to choose. baterry is so good but look like i have touch panel issue. waiting for update and then root, twrp...
Click to expand...
Click to collapse
That's weird. I do have the Bootloader unlock option in the developer settings and can do/undo it just fine. Looks like Samsung is using different Firmware versions on the A70?
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