General A WARNING TO ALL A32 4G/5G USERS (very important) - Samsung Galaxy A32 5G

As you have seen in the title, this is a warning. DON'T root your galaxy a32, as it can take some time but the phone will lose fingerprint unlock and sim card/internet functionality because of UNKNOWN BASEBAND and IMEI error.
You can't get it to work even reflashing stock firmware, and you can't downgrade because of Samsung bootloader lock. There's no TWRP for the 4g variant so you can't backup important partitions. Many people are having this problem with both 4g and 5g, as seen in the forums from those device.
If you don't want to turn ur galaxy into an AndroidPod with no sim, then don't root it, at least for now or until magisk people bug fix it.
Assine o Abaixo-assinado
Fix MAGISK and baseband in Samsung galaxy A32!
www.change.org
Lets try to talk to john wu on twitter guys

Magisk 23 very stable. No IMEI or baseband issues. Phone is A32 5G with TWRP.
Magisk 24+ too risky. Don't use it. Not ready for regular use.

scottyrick2 said:
Magisk 23 very stable. No IMEI or baseband issues. Phone is A32 5G with TWRP.
Magisk 24+ too risky. Don't use it. Not ready for regular use.
Click to expand...
Click to collapse
there were people before magisk 24 dropping out that complained about the issue... and my phone got bricked on 23

No, you dont root and then NOT make a TWRP backup immediately, that was the mistake by some here.
If your phone is rootable but no TWRP, THEN DONT ROOT!
*I got the IMEI error. Bootloop. Etc. Fixed in 240 seconds with TWRP. Obviously I had just made a backup before trying to update Magisk.

Good point, @TimmyP. I had forgot the exact process I followed to root in the first place. That must be why I have never had any of the imei problems.
I always rooted by flashing Magisk in TWRP. No other way. Never used the Magisk app to patch boot.img. AND always did a full backup before rebooting.

lucky you guys, a32 5g users, but we the 4g ppl don't have a custom recovery yet and it's soooo bad optimized

[SOLVED] suddenly unknown imei
ok so, i was using my phone normally yesterday, but out of nowhere, my SIM card stopped working and i couldn't use mobile internet/calls anymore. So i checked my settings and i saw my IMEI was marked as unknown, the same with baseband. The A32...
forum.xda-developers.com

Related

Galaxy S6 Edge SoftBrick (DRK)

Hi,
I've one (big) problem that I can't fix.
I've been using Android 5.0.1 for more than 1 year as I didn't want to upgrade (it worked pretty well) and because I had the S6 rooted with PingPong root.
However, one month ago it started to run slowly, crashing apps, ... so I decided that, as I wanted to wipe the device, why not upgrade to MM (6.0.1)??, so I did.
I did a backup of all my data and EFS folder and downloaded a 6.0.1 ROM to flash it with ODIN. Everything went OK and finished flashing the rom, but when the S6 restarted it showed this in the recovery:
'dm-verity verificztion failed...
Need to check DRK first...'
And I cant boot.
I've tried some tips that are here and in other websites:
- I've flashed stock rom again
- I've flashed a stock rom without cache.img file.
- I Can't flash some files as I've R/L ON. (I've been trying to disable it for many months but I couldn't).
But the S6 doesn't boot...
Thank you!
What worked for me.
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.
Critical_DoubleShot said:
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.
Click to expand...
Click to collapse
Thanks for your reply!
I tried to downgrade to 5.1.1 or 5.0.1 but I get an error.
(SW REV CHECK FAIL DEVICE 2 BINARY 1)
That happens when you don't have the right firmware you have.
You CANNOT downgrade to 5.1 or 5.0 since you are on 6.0. The bootloaders refuses to be overwritten.
Critical_DoubleShot said:
That happens when you don't have the right firmware you have.
Click to expand...
Click to collapse
I'm trying to flash another 6.0.1 ROM (a bit older), but I get 'CHECK FAIL. DEVICE: 4, BINARY:3'
I've read that DRK problems are related with EFS files, so... Can I restore EFS folder (I've a backup from Android 5.0.1) to solve?? I don't know how to restore it without booting into the sistem (and without custom recovery)
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thank you for your reply!!
I had the device rooted, but with PingPong root, so Knox is still 0. However it shows that the system is "custom".
I'll try the warranty, they may not notice the "custom", just the knox.
I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk
orbgel10 said:
I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
If you are talking about DRK, the only way to fix it that I know of, other than hw replacement, is via 3rd party professional repair tool. (Octopus/Octoplus box)
If DRK is ok, phone boots normaly, if it is messed up, the only way of booting is with custom kernel which bypass DRK check.
You can check it in recovery, if messed up it will say DM verity failed on bottom of the screen.
Ok, i send my phone to fix, i will tell you what happened.
Sent from my Redmi 3S using Tapatalk
brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thanks for your reply!!.
I took my S6 (925F) to a Samsung service center as you said. However, they told me that my S/N was incorrect (I bought a second-hand S6 edge, I think someone changed it) so they couldn't fix it.
Now I'm trying to use SmartSwitch to do a factory reset but it asks me for the S/N and I don't have the original one, just a S/N from a non edge S6 (920F). How can I do the factory reset without my S/N??? Can I use the serial number from another 925F??
Now I'm trying to find an engineering bootloader, to bypass the R/L and flash CF-AutoRoot, custom recovery.... but I only find it for 5.0.1 or... for galaxy S6 G925T, not F.
Finally, I managed to fix my S6 by myself!! (not really, but at least it boots...)
This is what I did:
- I found a factory binary for my S6 so I flashed it via ODIN
- I flashed a 6.0.1 ROM without hidden and without cache
Then it boots without any problems. However, now I can't get into recovery
I hope this will help someone

Battery drains extremely rapidly. Recommended firmware to flash?

So my sister gave me her S7 after my Sony Xperia XA2 refused to read my new Verizon service. So I flashed the Verizon firmware since it was on AT&T's firmware (which disables the bands for Verizon) and it's awesome. Super snappy, super quick, good 4K video camera, the works.
The only problem is that the battery is draining faster than my iPhone 6, and this is just with responding to texts while I'm at work. Like today, I worked 5 hours and it went from 100% to 32%.
I read that there is a firmware I can flash with Odin that will greatly help the battery, but I'm not sure what it is. I really dont want to brick this phone.
My S7 is not rooted btw.
SirShemp said:
So my sister gave me her S7 after my Sony Xperia XA2 refused to read my new Verizon service. So I flashed the Verizon firmware since it was on AT&T's firmware (which disables the bands for Verizon) and it's awesome. Super snappy, super quick, good 4K video camera, the works.
The only problem is that the battery is draining faster than my iPhone 6, and this is just with responding to texts while I'm at work. Like today, I worked 5 hours and it went from 100% to 32%.
I read that there is a firmware I can flash with Odin that will greatly help the battery, but I'm not sure what it is. I really dont want to brick this phone.
My S7 is not rooted btw.
Click to expand...
Click to collapse
First off you it's a US S7 which means the bootloader is locked which means you can't flash Twrp (Custom Recovery) which means you can't flash a custom rom or obtain root threw recovery what you could do is see about rooting it first i believe the root for the US S7 is threw a modified boot image that is patched threw Odin you would have to researcher that first after you obtained root then you have 2 options debloat the phone yourself which I wouldn't suggest cause if you remove something vital to the phone it will soft brick and you have no custom recovery to revert to a working image of your phone and you going to have to flash a stock firmware in Odin to fix it second whkch I do recommend is see if there are any roms for your model of phone that are flash fire flashable that you can flash again the process with this is one error and you will have to start the process all over again.... If you going to debloat after you obtain root just remove Samsung apps and Verizon bloatware and you should see a speed and battery increase just off of that alone... If your bold you flash xposed threw flashfire and open up your options even more.... Flash the wrong xposed and you Wil soft brick and have to start over again.... Some Samsung phones can take the official xposed for your sdk or need the alternative xposed for Samsung to work properly don't know which one yours fall under.... Good luck [emoji1696]
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]

Samsung Galaxy J3 Orbit (SM-S367VL) Looking for advice on how to root.

I've looked for quite a while on anything that could help me root the phone, and have had no success with anything. I'm worrying at this point that the bootloader is just locked and have to ask, is there anything else I can do to root this phone? Willing to try pretty much anything, even at risk of bricking it.
Lavitz324 said:
I've looked for quite a while on anything that could help me root the phone, and have had no success with anything. I'm worrying at this point that the bootloader is just locked and have to ask, is there anything else I can do to root this phone? Willing to try pretty much anything, even at risk of bricking it.
Click to expand...
Click to collapse
I'm interested in this too but in all likelihood nobody with the knowledge is even working on it because this is a niche phone.
Locked bootloader..
Well i have this fone now...i bought it because it was a good deal so it seemed..Less than 100$ for fone and service activation plan...I have rooted just about every Samsung i have ever owned...So heres what i have come up with..There is no OEM option in Developer options...On any other samsung fone i always go right into developer options and disable OEM by turning it off...Then i either have used Kingroot apk or Kingoroot apk in the past and they have worked...sometimes u have to find the perfect version to match your android software specifically...Now i have always had huge success with Odin and flashing TWRP via Laptop or Computer via USB connection, but thats something each individual should personally take the time and educate theirselves on just in case... Sorry to say that the Samsung J3 Orbit with Total Wireless and Oreo 8.0 needs a serious look at...
Lavitz324 said:
I've looked for quite a while on anything that could help me root the phone, and have had no success with anything. I'm worrying at this point that the bootloader is just locked and have to ask, is there anything else I can do to root this phone? Willing to try pretty much anything, even at risk of bricking it.
Click to expand...
Click to collapse
Your phone is a 2018 model of the j3. When xda finally makes a J3 (2018) thread i will request for this thread to be moved. Any root methods shown in J3 (2017) are likely not to work anymore since samsung patched the methods used. The only way to root phones now is by buying the U variants of samsung's phones which are only available from samsung's website under unlocked phones. Unlocked phones from samsung have an unlocked bootloader by default.
thepcwiz101 said:
Your phone is a 2018 model of the j3. When xda finally makes a J3 (2018) thread i will request for this thread to be moved. Any root methods shown in J3 (2017) are likely not to work anymore since samsung patched the methods used. The only way to root phones now is by buying the U variants of samsung's phones which are only available from samsung's website under unlocked phones. Unlocked phones from samsung have an unlocked bootloader by default.
Click to expand...
Click to collapse
incorrect statement.
My s9+ is a U varient with no OEM unlock option and did not come from samsung. And my s9+ is still not rootable.
OuijaElite said:
incorrect statement.
My s9+ is a U varient with no OEM unlock option and did not come from samsung. And my s9+ is still not rootable.
Click to expand...
Click to collapse
strange. what is the model number.
thepcwiz101 said:
Your phone is a 2018 model of the j3. When xda finally makes a J3 (2018) thread i will request for this thread to be moved. Any root methods shown in J3 (2017) are likely not to work anymore since samsung patched the methods used. The only way to root phones now is by buying the U variants of samsung's phones which are only available from samsung's website under unlocked phones. Unlocked phones from samsung have an unlocked bootloader by default.
Click to expand...
Click to collapse
U models are normally U.S. models which are locked tight. I run a s8 as my everyday driver which is rooted. The s9 s10 and most other us snapdragon and in this case exynos all are locked tight. And they cannot be rooted as of right now. The sampwn and other samfail do not work anymore. The U model you are referring to is the U.S. sim unlocked model not bootloader. With the S series F is the European bootloader unlocked model I don't know the European letter for J series.
Until some one finds a way to push a rooted system img on stock permissive combination kernel root will not come just like s9 and s10 us models
If these where us snapdragon we could push a rooted system combination file with safestrap just like we do on the newer bootloader on s8 using EDL and Qualcomm 9008
Just had an idea, another thread on this forum a guy says he made a modified version of Odin that can flash mix matched models. So just flash a model version of the j3 orbit that can be rooted or at least oem unlock capable to be able to flash twrp and then be able to root through twrp.
If flashing a j3 with a model number different than sm-367vl would brick it, just extract the .img partitions like boot.img or whatever the partition may be with ubuntu to restore one by one until you find which one makes the phone boot.
I don't know much about phones when it comes to this depth of modification. But I had a lg zone 3 that used this method to turn an unrootable model number version into a different model number that was rootable. Before I flashed the .img partitions of the stock software the screen had lines all over it, so using screen mirroring I was able to root the different model number software then download partition backup and restore app them restore the partitions that were for the original model number.
So basically it took both model numbers and combined some partitions of each to make it work properly.
In my head I can totally see this working. Just depends on how close to the same hardware each model number of the galaxy j3 has i guess.
I wish I would have noticed/seen this a bit sooner.. any progress or luck? I have the j337u ...
I know chimera tool is able to remove Knox kglock oemlock rmm mdm , of which mine shows kglock on, oemlock: on, frplock off. Trying to flash anything gives the error insufficient payment somethin. So there's got to be a way around it. ALSO I found interesting, the FCC id has J337t instead of U ...wonder why that is ...
(Anyone know where I can get stock j260AZ/AIO -notpaid- (cricket) firmware,I've literally checked every where )
We need someone to take that new 0day exploit rootPoC mod it however and release it
Found this [Have not tried it yet]
Came across an article on androidbiits. Not sure it's actually viable. Unfortunately I cant post the direct link until I have enough posts under my belt.
I'm willing to pitch in if someone can point me in the right direction.
Yhuda
How now????You are find How to root this phone????Please add Develop for find How to root Samsung J3 Orbit?!??
For my kglock on, oem lock on j337u, which also has some new mdm / rmm on it from consumer , I used chimera tool to set KGLock to Complete.
This also switched the oem lock to off and show the toggle in Dev ops....
1st flash of magical patched img worked. But after.connectinf.the Wi-Fi , knox enrollment and instantly a sec. Msg popped up and locked up the entire device. No usb connection or.anything.
factory reset
Same Issue,.then locks up
So for try 3, flash the patched boot, let boot.
AS SOON AS ITboots to android, hit the Airplane Mode toggle to activate it to stop Knox Enrollmnt
So er.gont get
was able to unlock the boatloader with comb file that was compatible, flashed stock track phone, updated to 9 pie...
used a gig pressed power button ???
9 pie trac phone j3 orbit
patched AP file with majisk, ran with Odin : says noway fail, I was able to reflash with stock firmware, so it doesn't work on mine...
any other luck
thanks
I would really like to know if anyone has succeeded either rooting or SIM unlocking or flashing with a different firmware on this model.
I was able to access the OEM unlock in my J3 Orbit (SM-S367VL) via factory binary after flashing combination firmware.
That is as far as Ive gotten. I am assuming you would want to run ADB download mode to flash anything as factory binary seems to have some security measures against full bootloader unlock built in

SM-G930V

Greetings My Brothers. I have a huge Problem. Sometimes ago I got a Samsung Galaxy S7 Verizon Model, thought it will be cool to have such a model, just come to think of it; Snapdragon 820 what else did I wanted again. And the phone started running Berserk. apps downloaded and installed from PlayStore don't work at all even WhatsApp does work properly. The phones freezes all the Time, it overheats all the time. So I made a decision. root, install custom recovery and install Custom Rom like lineage OS. I'm accustom to those stuffs like Odin, download mode, etc. I don't have any problem with a phone stock on boot loop, it's something I have been fixing, so I'm Used to It. My SM-G930V security level is High with its latest android version Oreo, the bootloader is locked. tried to unlock it with ADB and Command Prompt. It was a failure. tried to get some help On YouTube. Failed, all the videos I watched was about SM-G930F none of them talked about SM-G930V, I came across SM-G930V bootloader Unlocking, rooting and custom Rom but, it wasn't compatible with my SM-G930V. So let Me ask You Guys this question. Can I really unlock the bootloader, root the phone and Install a custom recovery, and A custom Rom??? If there is a slight chance or possibility of doing so, please Brothers help me out, because I am unable to use the phone to its full potential. Thanks. Michael.

Samsung Galaxy M23 Root

Somebody know how to root Galaxy M23? I can't find any solution on the internet.
How to Root Samsung Galaxy M23 5G using Magisk Without TWRP
Easy tutorial to Root Samsung Galaxy M23 5G SM-M236B/DS in easy steps using Magisk. For rooting, you we have described Magisk method, without installing TWRP.
www.androidweblog.com
We need a galaxy m23 forum!
mrsiri said:
We need a galaxy m23 forum!
Click to expand...
Click to collapse
*** New Device Forum Requests ***
Please post all your requests here. The forum admins choose new device forums carefully, based on several factors. There's no guarantee your device will have a forum created here, but feel free to posts your requests in this thread :) Please do...
forum.xda-developers.com
I recently bought an M23 5g, had a Moto g7 plus. I've never had a Samsung cell phone before. I don't know what happens to the phone after rooting. I saw that on other Samsung smartphones, because of the Knox protection, some apps and features stop working, so I was in doubt about the fingerprint, as it has the Knox logo when unlocking it. Can someone who rooted the M23 5g tell me if it continues to work normally the fingerprint? What other functions does it miss?
Marcus4agenT said:
I recently bought an M23 5g, had a Moto g7 plus. I've never had a Samsung cell phone before. I don't know what happens to the phone after rooting. I saw that on other Samsung smartphones, because of the Knox protection, some apps and features stop working, so I was in doubt about the fingerprint, as it has the Knox logo when unlocking it. Can someone who rooted the M23 5g tell me if it continues to work normally the fingerprint? What other functions does it miss?
Click to expand...
Click to collapse
i don't have M23 but i have another samsung, i can tell you my experience. After flashing Magisk, you'll need to wipe you data (knox **** will block your phone otherwise), i didn't lost any features, except Payment apps, and fingerprint work. Don't worry your phone will work normally if you root it
F-Google said:
i don't have M23 but i have another samsung, i can tell you my experience. After flashing Magisk, you'll need to wipe you data (knox **** will block your phone otherwise), i didn't lost any features, except Payment apps, and fingerprint work. Don't worry your phone will work normally if you root it
Click to expand...
Click to collapse
I came back here to tell my experience rooting the M23 5g. Yes, the fingerprint works great with the root and face unlock too, but some apps of Samsung dont work anymore like: Samsung pay/wallet, secure folder, health and all other's. So i find a module Lsposed called: Knox Patch. With this module, only samsung pass and pay dont became to work, other work great. The bank apps i recomend use magisk module call shamiko, all my bank apps work with this, but you will need put the apps on negation list of magisk before and resetart the smartphone. Puting google wallet on magisk negation list you can use this app and dont need anymore the samsung pay. So, the unic apps you realy lose with the root is the samsung pass.
OBS: For me, when i'm installing the root file on ODIN, the M23 dont boot without factory reset. I have a botloop and stuck at screen with factory reset option, after the reset magisk app apper for me normaly and work's great, so remember backup your files before rooting.
For all user's.
the price for this one is nice for its specs, considering to buy it and install TWRP and some custom rom like lineageos or something, can I pm anyone who did it?
simplydroiding said:
the price for this one is nice for its specs, considering to buy it and install TWRP and some custom rom like lineageos or something, can I pm anyone who did it?
Click to expand...
Click to collapse
There is no custom tom for this phone
Found some great tools for generating device trees, I want to make sure flashing TWRP, and/or Lineage OS is possible before buying this phone (In my case the SM-M236B/DS). Can someone please try it out for me? Luckily it's based of the Snapdragon 750G 5G, so it should be easier than making a device tree for an Exynos. (thanks Samsung).
Here are the things I found:
Firmware:
https://www.sammobile.com/samsung/galaxy-m23/firmware/#SM-M236B or
https://samfw.com/firmware/SM-M236B
There is a database of already dumped device trees but I doubt there is a device tree for SM-M236B/DS
https://dumps.tadiphone.dev/dumps
You could always try to download it straight from Samsung, but I don't know how to do that.
Tutorials:
Found this really easy to follow tutorial about using Dumpyara a device tree dumping tool.
https://baalajimaestro.me/posts/extract-vendor-2/
TWRP build guides, this is the best guide I found, kind of complicated but still realy useful
https://gist.github.com/rokibhasansagar/15c8e728d94a6bd35a687aac73ef79a5
Haven't found any Lineage OS build guides for unsupported devices but I've found a build guide for /e/ os, it should be similar (/e/ os is based of Lineage). (if you find one pleaaase tell me)
https://doc.e.foundation/support-topics/build-e
a question, is there a proper section of this phone?
haky 86 said:
a question, is there a proper section of this phone?
Click to expand...
Click to collapse
I don't think so.
Firmino Neto said:
I don't think so.
Click to expand...
Click to collapse
I was interested to get one for aosp developments, but idk if it has an active developments
I tried to install crDroid gsi with no luck. Bootloop on start
haky 86 said:
I was interested to get one for aosp developments, but idk if it has an active developments
Click to expand...
Click to collapse
I am developing LineageOS for the M23. If you have knowledge and are willing to help me out, send me a dm and I'll send you details
Isitiah said:
I tried to install crDroid gsi with no luck. Bootloop on start
Click to expand...
Click to collapse
make a patched magisk boot image and flash it. Then flash vbmeta_disabled. Lastly, go to lineage recovery and wipe data and fastboot flash the GSI.
{Mod edit: Drag to Telegram removed. Oswald Boelcke, Senior Moderator}
mrsiri said:
make a patched magisk boot image and flash it. Then flash vbmeta_disabled. Lastly, go to lineage recovery and wipe data and fastboot flash the GSI.
{Mod edit: Drag to Telegram removed. Oswald Boelcke, Senior Moderator}
Click to expand...
Click to collapse
Where i can get vbmeta disabler? And how I can flash this via fastboot? Through TWRP?
Okay so i succesfully flashed crDroid gsi. Here is a tutorial:
1. Unlock Bootloader
2. Using Odin flash a13_5g_fastbootd-recovery.tar
in AP slot in odin
3. After restart immediately go to recovery and you should see option "enter fastboot", select this and your phone should go into fastbootd mode
4. Now launch fastboot on your PC type fastboot devices if it shows your device that's good.
5. Copy your gsi to adb/fastboot directory and type: fastboot flash system <name of gsi>.IMG
Now flashing should start.
If flashing complete succesfully FIRST go to recovery and select FORMAT DATA. After data is formatted reboot your phone.
Now your phone should boot up with your gsi tom.
RECOVERY FILE (i cant attach it to post): https://t.me/SamsungGalaxyF23/49136

Categories

Resources