Is there any way to work root for galaxy a10s i tried all the methods and didn't work with me ... even the boot.img method via odin didn't work with me .... is there any other way ?????
Galaxy a10s Mediatek MT6762 Helio P22 (12 nm)
CPU Octa-core 2.0 GHz Cortex-A53
Any helps please
Good morming,
This link worked for me: https://www.full-repair-firmware.com/2019/10/how-to-root-a107m-9.0.html
Although I didn't use the BL from the (in my case TELCEL SM-A107M) firmware, I downloaded this Boot file (I don't remember from where ), it is for A107MUBU3ASI4:
https://mega.nz/#!tRgXgCTI!dHdQPB-MSQ7Znpm7d-Nme7lwwc_w2-im75putNHxgtM
SO I copied the boot file to the sdcard, ran magisk manager on the phone, selected patch boot image and selected the boot image on the sdcard for patching, after the patching is done, I copied the image back to the PC, started Odin, booted the phone to download mode (turn it off, connect the phone to the usb cable press power button to start the phone, then release the power button and press both volume buttons until it boots to download mode), then when Odin detected the phone I clicked the AP button on Odin, selected the patched boot file that I copied from the phone and then clicked on the Start button to flash the image, then when Odin finished, the phone booted automatically ... the tutorial says that the phone will ask for a factory reset and delete all the phone info, but in my case it didn't asked for nothing nor deleted my data, so I got root without losing information, as soon as the phone booted it was already rooted an root was working witout me having to do anything.
The first time I rooted my phone I installed xposed framework, then had some troubles with the beta version, got a bootloop and had to re-flash the original firmware, BUT when I tried to reflash the patched boot image I got the PreNormal message and had to wait a week to root again my phone .
So I googled and then found some info about the KG/RMM problem, but couldn't find a zip that worked for the SM-A107M, also since there is no TWRP available to this model, I wouldn't be able to flash the zip anyway, but I found that deleting this files:
libvkjni.so
libvkmanager.so
libvkservice.so
KnoxGuard.apk/Rlc.apk
will disable the service.
The first 3 are in the system/lib directory, the knoxGuard apk is in the priv-app/knoxGuard directory.
So I rooted the phone again (after waiting 7 day to prenormal to end) and in the first boot I
installed "Root Explorer" from the play store (Any file manager with root privileges will work) and deleted 4 of those files (the RLC.apk I couldn't find) and after 2 weeks of rebooting, reinstalling xposed, getting the bootloop problem again , re-flashing original firmware (without the KG/RMM prenormal state), re-rooting, and finally installing xposed without problems (in my phone the 4.6.0 beta version didn't work so I inistalled the 4.5.1 beta) I am happy with my rooted, xposed phone.
I would really like if somebody created/xported a TWRP for this model, but in the interim all is good the ends good.
Regards
:good: Thanks for the wonderful information .... But the problem I have is KGG / RM PRENORMAL STATE .... must do cancellation of the first ...
If you have already Prenormal state, then you have to wait 7 days, dont turn off your phone, don't restart and don't disconnect from the internet, then after the 7 days (168 hrs) the prenormal state should disappear!
Check this link:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Best Regards
I did not find prenormal state or normal.....
I found : KG status : checking
OEM unlock : off
Then, if not in prenormal, you should be able to flash and root your phone!
cheveguerra said:
Then, if not in prenormal, you should be able to flash and root your phone!
Click to expand...
Click to collapse
Good night
Unfortunately .... this root method did not work for me .... via Magisk ... I don't know what the problem is .... but this method did not work for me which is in many websites and it is the same way .... As follows my device info :
Ap: A107FXXU3ASJ5
CP: A107FXXU3ASJ1
CSC: A107FOJM3ASJ5
Model: sm- A107F / DS
The same method is used by everyone via Magisk ...
My device have no problem:
Unlocking the device bootloader
OEM unlock: off
Kg status: checking
I have no prenormal state
I followed all the steps on the sites
1- I downloaded Galaxy A10S Firmware
2- I downloaded and installed the latest Magisk Manager app.
3- Copied only the boot.img file from the extracted folder to a device storage.
4- opened the Magisk Manager app then clicked on on “Patch Boot Image File”.
5- when patched boot img finished from Magisk .... I renamed to boot.img and used 7zip and archived it to .tar format ....
6- I flashed via Odin in download mode but I got on fail .....
I don't know what problem ...
But this is what happened !!!!
Did you use the boot image (BL) I posted on the second post??
Download the file, copy it to your phone, use magisk manager to patch it, copy patched image to pc, flash via Odin to your phone.
Regards
No, I didn't use that boot img .... It the same : A107F .... A107M.. ???
I will try later.
I used that boot in your post .... for A107m.... l flashed via Odin in my A107F ... It's flashed in my device.... but when I boot to Magisk..... no root........ for that I think will wait someone to create twrp for galaxy A10s then I flash root.... Thanks for everything....
anybody with A107F firmware pls. i need to try to root mine.
raymihsenior said:
anybody with A107F firmware pls. i need to try to root mine.
Click to expand...
Click to collapse
You can go to sammobile there you can find it:good:
Try this for A107F
drive.google.com/file/d/1-5G6FDEzfT2oJ86aOneYGU1er7hbORIA/view?usp=drivesdk
DangVN said:
Try this for A107F
drive.google.com/file/d/1-5G6FDEzfT2oJ86aOneYGU1er7hbORIA/view?usp=drivesdk
Click to expand...
Click to collapse
....
This is TWRP 3.3.1.0 beta for galaxy A107F.... It's working????
.... Are you tested that ????
It is in img format and not in tar ... do we have to convert it to tar to flash it via odin?.
....
What do i need to do to make the oem unlock option appear again?
I've already tried the turning off updates and changing dates thing.
And I waited out the 7 days ( Which was difficult since my IP doesnt have a stable connection.)
I've started doubting if it even exists at all.
I only got my A10s for free from a carrier plan.
KG Status is Normal
OEM is still locked and nowhere to be seen
Helios007 said:
What do i need to do to make the oem unlock option appear again?
I've already tried the turning off updates and changing dates thing.
And I waited out the 7 days ( Which was difficult since my IP doesnt have a stable connection.)
I've started doubting if it even exists at all.
I only got my A10s for free from a carrier plan.
KG Status is Normal
OEM is still locked and nowhere to be seen
Click to expand...
Click to collapse
......
If you made all the attempts and didn't succeed with you ... Install the stock firmware for your country ... and you delay the date a few months earlier ... then go to update the program .... then you should have an OEM unlock
Hastoma said:
......
If you made all the attempts and didn't succeed with you ... Install the stock firmware for your country ... and you delay the date a few months earlier ... then go to update the program .... then you should have an OEM unlock
Click to expand...
Click to collapse
And how does one Install a "different/new" firmware?
I remember doing it once or twice with Odin with a firmware I got from sammobile SMA-107f.
Succeeded. Although I don't know if it actually worked, since it booted up just like the first time I got it, with the carriers default wallpaper and pre-loaded apps.
I've been trying to root the SM-A107F for weeks now but no luck.. Any help will be appreciated
cheveguerra said:
Good morming,
This link worked for me: https://www.full-repair-firmware.com/2019/10/how-to-root-a107m-9.0.html
Although I didn't use the BL from the (in my case TELCEL SM-A107M) firmware, I downloaded this Boot file (I don't remember from where ), it is for A107MUBU3ASI4:
https://mega.nz/#!tRgXgCTI!dHdQPB-MSQ7Znpm7d-Nme7lwwc_w2-im75putNHxgtM
SO I copied the boot file to the sdcard, ran magisk manager on the phone, selected patch boot image and selected the boot image on the sdcard for patching, after the patching is done, I copied the image back to the PC, started Odin, booted the phone to download mode (turn it off, connect the phone to the usb cable press power button to start the phone, then release the power button and press both volume buttons until it boots to download mode), then when Odin detected the phone I clicked the AP button on Odin, selected the patched boot file that I copied from the phone and then clicked on the Start button to flash the image, then when Odin finished, the phone booted automatically ... the tutorial says that the phone will ask for a factory reset and delete all the phone info, but in my case it didn't asked for nothing nor deleted my data, so I got root without losing information, as soon as the phone booted it was already rooted an root was working witout me having to do anything.
The first time I rooted my phone I installed xposed framework, then had some troubles with the beta version, got a bootloop and had to re-flash the original firmware, BUT when I tried to reflash the patched boot image I got the PreNormal message and had to wait a week to root again my phone .
So I googled and then found some info about the KG/RMM problem, but couldn't find a zip that worked for the SM-A107M, also since there is no TWRP available to this model, I wouldn't be able to flash the zip anyway, but I found that deleting this files:
libvkjni.so
libvkmanager.so
libvkservice.so
KnoxGuard.apk/Rlc.apk
will disable the service.
The first 3 are in the system/lib directory, the knoxGuard apk is in the priv-app/knoxGuard directory.
So I rooted the phone again (after waiting 7 day to prenormal to end) and in the first boot I
installed "Root Explorer" from the play store (Any file manager with root privileges will work) and deleted 4 of those files (the RLC.apk I couldn't find) and after 2 weeks of rebooting, reinstalling xposed, getting the bootloop problem again , re-flashing original firmware (without the KG/RMM prenormal state), re-rooting, and finally installing xposed without problems (in my phone the 4.6.0 beta version didn't work so I inistalled the 4.5.1 beta) I am happy with my rooted, xposed phone.
I would really like if somebody created/xported a TWRP for this model, but in the interim all is good the ends good.
Regards
Click to expand...
Click to collapse
This is very interesting. KG State has been non existent on my device, I can flash modified firmware since day 1. I'll try this, I tried patching the whole AP_ file and there are problems with the signal, I did not try only patching the boot.img
Thanks!
ShaDisNX255 said:
This is very interesting. KG State has been non existent on my device, I can flash modified firmware since day 1. I'll try this, I tried patching the whole AP_ file and there are problems with the signal, I did not try only patching the boot.img
Thanks!
Click to expand...
Click to collapse
when you flash the patched AP.tar you should also be flashing it with the rest of the firmware.. tjw even says somewhere on his github you shouldnt flash the patched AP by itself
Related
Hello XDA!
I am writing this thread to ask for help rooting my Samsung Galaxy J2 Pro.
I attempted to use apps such as: Framaroot, Kingroot, etc.. but so far none of them have worked and I have not been able to find a working guide on the internet of how to root my phone.
I also tried installing an unofficial version of TWRP for my phone but everytime I tried to boot into the recovery it would say "No Command" and then boot into the original recovery.
Is anyone able to help me root my phone? Can it even be done?
Any help is sincerely appreciated. Thanks!
Phone Specifications:
Samsung Galaxy J2 Pro.
SM-J250G
Android Version: 7.1.1
Bumpity Bump
Try this at your own risk
Make a backup before trying
I got root access with this method
Download stock Rom from sammobile extract and there should be 5 MD5 files extract the AP file with 7z and copied boot.img on to sdcard
Installed MagicalMmanager-7 used it to patch the boot.img to a tar file
Copied the boot image to my pc desktop then flashed the boot with odin
When I booted it back up magisk manager kept crashing so I uninstalled it and installed magiskmanager-5.23 rebooted it opened magisk and followed the prompts to update it
:good:
putzwon said:
Try this at your own risk
Make a backup before trying
I got root access with this method
Download stock Rom from sammobile extract and there should be 5 MD5 files extract the AP file with 7z and copied boot.img on to sdcard
Installed MagicalMmanager-7 used it to patch the boot.img to a tar file
Copied the boot image to my pc desktop then flashed the boot with odin
When I booted it back up magisk manager kept crashing so I uninstalled it and installed magiskmanager-5.23 rebooted it opened magisk and followed the prompts to update it
Click to expand...
Click to collapse
Hello there.
I have tried to patch my boot.img but when I put into a .tar and flash it, it doesn't flash, it's just stuck on file analysis despite being able to flash other files. Would you be able to send me a copy of your boot.img, thanks.
Kindest Regards
-Jayden
JaydenATC said:
Hello XDA!
I am writing this thread to ask for help rooting my Samsung Galaxy J2 Pro.
I attempted to use apps such as: Framaroot, Kingroot, etc.. but so far none of them have worked and I have not been able to find a working guide on the internet of how to root my phone.
I also tried installing an unofficial version of TWRP for my phone but everytime I tried to boot into the recovery it would say "No Command" and then boot into the original recovery.
Is anyone able to help me root my phone? Can it even be done?
Any help is sincerely appreciated. Thanks!
Phone Specifications:
Samsung Galaxy J2 Pro.
SM-J250G
Android Version: 7.1.1
Click to expand...
Click to collapse
Hi Jayden
I've got exactly the same problem. Have you worked this out eventually? Please help!
MC
qichen said:
Hi Jayden
I've got exactly the same problem. Have you worked this out eventually? Please help!
MC
Click to expand...
Click to collapse
Unfortunately I have not found a solution. Please notify me if you find one.
here is a copy of my boot.img after flashing this you will get a verification problem and you will have to reset your phone if it bootloops into recovery or starts to update and says no command take battery out put it back in and boot it again or boot in to odin mode and push down and boot it eventually it will boot in to recovery then factory reset it. first boot may take 5-10 minutes
my software version is J250GDXU2ARD3_J250GXSA2ARD3_XSA
putzwon said:
here is a copy of my boot.img after flashing this you will get a verification problem and you will have to reset your phone if it bootloops into recovery or starts to update and says no command take battery out put it back in and boot it again or boot in to odin mode and push down and boot it eventually it will boot in to recovery then factory reset it. first boot may take 5-10 minutes
my software version is J250GDXU2ARD3_J250GXSA2ARD3_XSA
Click to expand...
Click to collapse
Hello and thanks a lot! I flashed my boot image and now when it boots it says "Set Warranty Bit : Kernel" and an infinite booting screen.
What do I do from here? or do I need to flash the original rom?
don't worry about "Set Warranty Bit : Kernel" mine does it too here is another boot.img after i flashed this i got verification failed so i used 7z to tar userdata.img.ext4 i extracted from the AP image i got the boot.img from.
i put boot in BL and userdata in AP and flashed it. it fired up as normal and then i installed magisk apk
JaydenATC said:
Hello and thanks a lot! I flashed my boot image and now when it boots it says "Set Warranty Bit : Kernel" and an infinite booting screen.
What do I do from here? or do I need to flash the original rom?
Click to expand...
Click to collapse
Flash the original rom then flash boot and userdata as i explain in next post
Hey, sorry for the late response. Everything is working fine! I now have superuser abilities but everytime I try to flash my recovery with TWRP it just loads the stock recovery. I even tried removing certain files from the root folder to avoid the stock recovery being flashed but it hasn't worked.
Any idea? Ps. You are a life saver my man.
JaydenATC said:
Hey, sorry for the late response. Everything is working fine! I now have superuser abilities but everytime I try to flash my recovery with TWRP it just loads the stock recovery. I even tried removing certain files from the root folder to avoid the stock recovery being flashed but it hasn't worked.
Any idea? Ps. You are a life saver my man.
Click to expand...
Click to collapse
glad i could help and i don't think there is an official twrp for this device here is one i ported a couple things still don't work mtp and sideload but it's not really usable until someone ports a rom due to the data encryption which you have to format to be able to flash anything
putzwon said:
glad i could help and i don't think there is an official twrp for this device here is one i ported a couple things still don't work mtp and sideload but it's not really usable until someone ports a rom due to the data encryption which you have to format to be able to flash anything
Click to expand...
Click to collapse
Hello,
Sorry, I don't have the J250G anymore as I traded it for a J5.
Kindest Regards
Jayden
My internal storage showed I only have 8gb instead of 16gb. Is there a fix for this?
P.S. Wiping data fixes it
ok
You can extract it from the AP file from stock firmware using 7z
hey
hey everyone im just wondering but is there a kernel for this device yet or any rom ("J250G")
Hey
Yesterday I flashed a boot logo on my SM-G928F in TWRP. After that my phone doesn't boot into system or recovery anymore - there's always a blackscreen. I only can boot into download mode.
I tried to flash a stock-rom via Odin but that didn't helped - the same blackscreen, because a stock rom does not replace the boot logo.
I think I have to flash the stock boot logo ( https://drive.google.com/file/d/1378RQ5w_vAAmnQ3HB0FymZXWIm12T0Mg/view ) , but thats a zip which I can't flash via Odin.
There a two ways in my mind which could work:
1. Getting a tar.md5 file with the stock boot logo.
2. Getting a tool which allows to flash zips in download mode of the phone.
I really hope that someone could help me with my big problem.
Best regards
DGB
Hey there
I recommend to flash the firmware again but this time after flashing firmware flash the twrp and flash the zip via adb sideload ( a feature present in TWRP) as by adb sideload one is able to flash zip files as well
Or i recommend you to get to know the combination of keys that will help you to directly enter into recovery
Hope it will work
And if there is any problem let me know
As in the internet there are various ways by which a person can flash the custom rom and custom recovery via odin
Look at this link:-
http://www.lineageosrom.com/2017/07/how-to-flash-custom-rom-via-odin.html?m=1
nr10prashant said:
Hey there
I recommend to flash the firmware again but this time after flashing firmware flash the twrp and flash the zip via adb sideload ( a feature present in TWRP) as by adb sideload one is able to flash zip files as well
Or i recommend you to get to know the combination of keys that will help you to directly enter into recovery
Hope it will work
And if there is any problem let me know
As in the internet there are various ways by which a person can flash the custom rom and custom recovery via odin
Look at this link:-
http://www.lineageosrom.com/2017/07/how-to-flash-custom-rom-via-odin.html?m=1
Click to expand...
Click to collapse
Thank you for your answer but that didn't worked. The problem is that flashing the stock firmware doesn't replace or repair the boot image. So I've got a never ending blackscreen when I want to boot in system or TWRP/Recovery and that means that I'm not able to configure ADB Sideload.
I can only boot into download mode, nothing else.
I think the jpg of the boot logo I've installed was corrupted so it can't be loaded
You are in download mode so you have to press all the keys including the home button and once the download mode closes then press the "volume up key and power key and also the home button and then your phone will automatically reboot into recovery.
I know, I tried that multiple times but it doesn't work. Blackscreen... only a never ending blackscreen. The download mode is the only thing taht works. I have to flahs the old boot logo via download mode... but i don't know how
Wait for the battery to be drained out completely and then do what i said earlier
nr10prashant said:
Wait for the battery to be drained out completely and then do what i said earlier
Click to expand...
Click to collapse
I did. but it didn't work, too
I really need someone who is able to integrate the stock boot logo into a custom rom which can be flashed via Odin... Or I need a tool which allows to install zips in download mode. I tried adb sideload again but it didn't recognizes my phone when its not in recovery.
I really think that my S6 edge + is nearly died :crying:
Try to flash the firmware with the samsung smart swith.....
This will 100% works!!!!!4
Inderpreets said:
Try to flash the firmware with the samsung smart swith.....
This will 100% works!!!!!4
Click to expand...
Click to collapse
I know but Samsung removed this feature some months ago so I'm not able to do this
--- I know, it's from the German Samsung Support but it's a confirmation that Samsung removed this feature:
DGB100 said:
I know but Samsung removed this feature some months ago so I'm not able to do this
--- I know, it's from the German Samsung Support but it's a confirmation that Samsung removed this feature:
Click to expand...
Click to collapse
Not even flashing a factory firmware (4 files with pit) with repartition option selected?
What about a combination firmware and then a full stock FW?
яι¢αя∂σ said:
Not even flashing a factory firmware (4 files with pit) with repartition option selected?
What about a combination firmware and then a full stock FW?
Click to expand...
Click to collapse
I only tried to flash stock firmware with AP in Odin... and I tried stock rom with re-partition.
Where do I get those 4 files? I need XEU for my SM-G928F. It would be very nice if you could give me a more detailed instruction for this because I never worked with PIT...
get samfirm v0.3.6
On the model you put sm-g928f, region XEU, tick the binary nature box and press "check update". Download the resulting file, that is a factory firmware to do repairs in a 4 files format: bootloader, pda or ap, modem or cp and csc!
You will get this file:
SM-G928F_1_20180305151001_nsg8uwd0sh_fac.zip
Put each file in the correct field in odin!
About combination firmware, it needs to be same binary version as stock firmware already programed on phone! if first number on firmware version is a 3, combination FW need to be also bin 3!
G928FXXS4CRB4 if is 4, you need comb fw also in bin 4! if you downgrade you get odin error and a softbrick!
Was checking if any comb. fw is available, but i find only paid files for your phone model!
яι¢αя∂σ said:
get samfirm v0.3.6
On the model you put sm-g928f, region XEU, tick the binary nature box and press "check update". Download the resulting file, that is a factory firmware to do repairs in a 4 files format: bootloader, pda or ap, modem or cp and csc!
You will get this file:
SM-G928F_1_20180305151001_nsg8uwd0sh_fac.zip
Put each file in the correct field in odin!
About combination firmware, it needs to be same binary version as stock firmware already programed on phone! if first number on firmware version is a 3, combination FW need to be also bin 3!
G928FXXS4CRB4 if is 4, you need comb fw also in bin 4! if you downgrade you get odin error and a softbrick!
Was checking if any comb. fw is available, but i find only paid files for your phone model!
Click to expand...
Click to collapse
Thanks it worked for me but now I need a pit-file. Do you now where I get it?
EDIT: I found a pit-file for myself. Thank you very much for your help!
HTML:
https://drive.google.com/file/d/0BzyeAt2hy6XednpHZmhRUmtOMFk/view
DGB100 said:
Thanks it worked for me but now I need a pit-file. Do you now where I get it?
EDIT: I found a pit-file for myself. Thank you very much for your help!
HTML:
https://drive.google.com/file/d/0BzyeAt2hy6XednpHZmhRUmtOMFk/view
Click to expand...
Click to collapse
It worked means you got your phone back to normal or you could get the firmware using samfirm?
Pit file is always inside csc file on a 4 files fac firmware. Use the pit on firmware because the pit from your link can be from a early version of android and have different bits for partition sizes!
EDIT: Here, got the combination fw for the binary 4. IF your phone is already ok, don't use this!
DGB100 said:
I know but Samsung removed this feature some months ago so I'm not able to do this
--- I know, it's from the German Samsung Support but it's a confirmation that Samsung removed this feature:
Click to expand...
Click to collapse
SmartSwitch still works for my G925v.
яι¢αя∂σ said:
It worked means you got your phone back to normal or you could get the firmware using samfirm?
Pit file is always inside csc file on a 4 files fac firmware. Use the pit on firmware because the pit from your link can be from a early version of android and have different bits for partition sizes!
EDIT: Here, got the combination fw for the binary 4. IF your phone is already ok, don't use this!
Click to expand...
Click to collapse
I got my phone back to normal so thank you very much!
I have the same problem on my j2 prime I can only goto download mode and in odin tried to install stock firmware but got write fail..can you please help me with this error
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Why not compile a matching TWRP by yourself?
Look inside here.
@ jwoegerbauer i can give a try but have no experiences when it comes to makin a custom recovery.
ᐯerified Developer said:
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Click to expand...
Click to collapse
Yea, im also looking for a way to get some sort of custom recovery on the exact same device. My advice is (if you cant build your own version of twrp) to just wait for some devs to release something for it. The galaxy a11 is a very new device so we'll just have to wait it out.
Edit: So I followed a tutorial here (https://www.youtube.com/watch?time_continue=40&v=MyxGZbCuxDQ&feature=emb_logo) and i created this (https://filebin.net/u3yww2cyajktm043). IT MAY OR MAY NOT WORK!!! USE IT AT YOUR OWN RISK!!!!
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
ninjakira said:
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
Click to expand...
Click to collapse
You can put the device into download mode and unlock the bootloader from there...
I'm currently stuck on this device trying to get it to unlock the boot loader. I've ticked OEM unlock but when I get into download mode (adb reboot download) I'm not getting any option to unlock the boot loader there. I'm also not able to get into download mode with any key commands. Any ideas here?
I've heard you power off, then hold volume up and down when you plug in a data cable. Haven't tried it yet, I'm on the a115u t-mobile variant. I can get to what it calls download mode, which looks to be fastboot and NOT the standard samsung blue screen download mode. Just boot to recovery and select reboot to bootloader. I do not have oem unlock in my dev settings, but I'll see if I can fastboot oem unlock when I get back to my laptop.
flash sm-a115u1 version firmware first. gives you oem unlock option. obviously toggle on and adb debugging. power off the phone. hold both volume buttons and insert usb cable. it will look like the normal blue download warning screen but read it carefully. it says long press volume up to unlock bootloader. it works. it will go black. release volume up and next it will ask you to confirm. choose yes. it will reboot and erase. after skipping thru set up enable dev options again and you will see oem toggle greyed out with a caption "bootloader already unlocked". thats as far as ive gotten. because now im like "what now?" i need a custom recovery file to flash to the device. any help with that out there? so now that the bootloader is unlocked can i install magisk to root and if so after that how can i network unlock? any help would be greatly appreciated. also looking for any custom roms that are available for this a11(2020). seems like a decent phone.thanks.
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Is there any updates that can be flashed with stock recovery
griha41 said:
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Click to expand...
Click to collapse
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
sdell said:
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
Click to expand...
Click to collapse
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
griha41 said:
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
Click to expand...
Click to collapse
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
sdell said:
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
Click to expand...
Click to collapse
Ahh I see. Sorry then.
You shall do that way. Find current fiware for your device, download it through fine software.
A result you will get 5 files with .zip extension.
You need to unpack file with AP_ prefix, i suggest you to use 7zip for that stuff. From file you need took off the boot.img.
Then boot.img you shall pack into archive.tar,
When you've done, down load the Magisk apk from github and install on your phone. Move your jew archive to phone memory/diwnload folder and start the Magisk, make patching of kenel, as result you'll receive the magisk_patched.tar, copy that file to your pc and start the Odin, place that archive in AP slot and flash it.
PROFIT!
But I want to warn you in android 10 and up there root and kernel system are different, now system is booting from super.img, and partition /,/system and etc are RO, so through the root you'll not able to change anything in system it would be wiped on next system restart.
After a couple of months of deep research I have managed to find a solution to unlock bootloader and root our SMAO15F device.
1st step: If your on android 10 it's possible to unlock bootloader even if our device has that option by default.
Fortunately with the newly released of official android 11 we are able to do so all you gotta do is you have to jump to android 11 if you're still on android Q then proceed to the unlocking method.
2nd step: after bootloader unlock download this .tar file (patched boot image for android 11 samsung sma015f).
Final process: Go to download mode, open latest odin and import the attached file with the AP button, phone will automatically restart after the process or restart it manually if not,
voila our samsung a01 is now rooted without twrp. Now we just have to wait for someone to make a custom twrp for our device or wait for official twrp or kindly please let me know if there is.
Credits: to that russian guide for the patched boot file for android11 (sma015f)
Cool bro!, but, how i'm unlock the bootloader for A01?
ROOT WITH MAGISK 23 WORKING 100% ON ANDROID 11 JUST UPGRADE UNLOCK BOOTLOADER AND FOLLOW THE INSTALLATION GUIDE https://topjohnwu.github.io/Magisk/install.html
Kaik Ricardo said:
Cool bro!, but, how i'm unlock the bootloader for A01?
Click to expand...
Click to collapse
Vol+ and Vol - and plug the usb cable then long press vol+
Hello,
Finally, I can unlock the bootloader, flash twrp and root my Samsung Galaxy A01 (a01q) (SM-A015M).
All I need is just update to Android 11 and then I can unlock the bootloader and flash the magisk patched boot.img together the patched vbmeta.img.
I can flash TWRP using the image file "TWRP_3.5.2_A015F.img" sent by @tariqa
How To Root Samsung A01 (a015f/DS)
Hello, I want to ask how to root samsung galaxy a01 (a015f) , i want to instal f.lux for better blue light filter, Thanks!
forum.xda-developers.com
Thank you very much
1. Unlock your bootloader enter in download mode Vol+ + Vol- + USB conected to pc (Keep in mind that by doing this you will lose your files, it is advisable to make a backup of your photos, music, etc.)
2. Once you start your cell phone install magisk manager, Choosing the boot.img file of your rom into the app (Tip: Only!!! If your model is SM-A015M Android 11 I leave you my own modified boot.img to flash:
File on MEGA
mega.nz
Otherwise, you can download the firmware (3.79 gb) and extract the boot.img from the firmware of your model SM-A015 M / F ... Android 10, Android 11... etc. And No need for pc
https://samfrew.com/model/SM-A015M/
3. The image will begin to flash
4. When it restarts you will have Root on the cell phone!
------------------------------------------------------------------------------------------------------------------------------------------------
Extra: If you need the custom recovery I give you the link with my TWRP which is installed through the Odin program on a PC (this step does not delete your files)
File on MEGA
mega.nz
Keep in mind that to install TWRP you must deactivate the DM-VERITY & FORCEENCRYPT DISABLER I leave it in a link:
Zackptg5 - Android
zackptg5.com
This is a module that can be installed via magisk, which is necessary to decrypt the system ... so once TWRP is installed, it is advisable to uninstall it via Magisk to avoid R / W errors
Marti_Fajardo said:
After a couple of months of deep research I have managed to find a solution to unlock bootloader and root our SMAO15F device.
1st step: If your on android 10 it's possible to unlock bootloader even if our device has that option by default.
Fortunately with the newly released of official android 11 we are able to do so all you gotta do is you have to jump to android 11 if you're still on android Q then proceed to the unlocking method.
2nd step: after bootloader unlock download this .tar file (patched boot image for android 11 samsung sma015f).
Final process: Go to download mode, open latest odin and import the attached file with the AP button, phone will automatically restart after the process or restart it manually if not,
voila our samsung a01 is now rooted without twrp. Now we just have to wait for someone to make a custom twrp for our device or wait for official twrp or kindly please let me know if there is.
Credits: to that russian guide for the patched boot file for android11 (sma015f)
Click to expand...
Click to collapse
after flashing the AP, the phone won't boot and says can't load android system.
edit: i patched my own AP with Magisk and it worked.
So i managed to upgrade my samsung a01m/ds to android 11 & i had unlocked the bootloader. Afterwards i had use the magisk rooting process, then flashed a boot.img that i had extracted from firmware (if needed i will upload) then the phone restated and took like 7 minutes to start, having said that i setup my device but upon doing so i noticed i was not able to use wifi but i had mobile data , managed to get in and install root checker pro and i had root but there was root( will leave an image ) but i didn't enjoy the fact that the wifi was not working, my hotspot wasn't working. i never managed to install TWRP becuase i was tampering a little more and trip my knox. it's been like 2 months since it trip and the OEM UNLOCKING in developer options is yet to be visible so i can unlock the oem and start a fesh.
Marti_Fajardo said:
After a couple of months of deep research I have managed to find a solution to unlock bootloader and root our SMAO15F device.
1st step: If your on android 10 it's possible to unlock bootloader even if our device has that option by default.
Fortunately with the newly released of official android 11 we are able to do so all you gotta do is you have to jump to android 11 if you're still on android Q then proceed to the unlocking method.
2nd step: after bootloader unlock download this .tar file (patched boot image for android 11 samsung sma015f).
Final process: Go to download mode, open latest odin and import the attached file with the AP button, phone will automatically restart after the process or restart it manually if not,
voila our samsung a01 is now rooted without twrp. Now we just have to wait for someone to make a custom twrp for our device or wait for official twrp or kindly please let me know if there is.
Credits: to that russian guide for the patched boot file for android11 (sma015f)
Click to expand...
Click to collapse
I managed to root my phone using this method but after I rooted, my wifi was stuck at turning on. I would then restore it to its stock firmware to have the wifi back and it did, but then I rooted again and wifi got stuck again. How do I fix this problem?
Johnmarr said:
I managed to root my phone using this method but after I rooted, my wifi was stuck at turning on. I would then restore it to its stock firmware to have the wifi back and it did, but then I rooted again and wifi got stuck again. How do I fix this problem?
Click to expand...
Click to collapse
Did you try to enable or disable MAC randomizing?
how
VD171 said:
Did you try to enable or disable MAC randomizing?
Click to expand...
Click to collapse
How do I enable or disable mac randomizing?
Hello Everyone,
hopefully this is the right section for my question. If not please let me know.
I got a t865 with android 12 and want to root it. So i use the helping guide from Magisk (https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root).
What i did:
1) Unlocking the Bootloader (The OEM is grayed out) and i get a message every boot their is a open bootloader
2) Download with frijya the last stock image
3) Transfer it to the tablet
4) Download magisk and patching the file with recovery boot (no ramdisk)
5) Adb pull back to the laptop
6) Reboot to download mode and patch the magisk ap and the bl, cp and csc
And after the flashing, i cannot reboot to into the recovery. Everytime i get the info about the open bootloader and than the message: The tablet is not running samsung official software. ... (You can see the error on the image)
I can get back to the download mode and flashing the orignal stock image and be back were i started, but without rooting.
Can someone tell me how i can fix it?
Thx a lot in advanced
smartech0815
hi, don't worry about rebooting into recovery to wipe, if you did a clean install that's not the problem. i think the problem is the file patched with magisk. try to patch a new one leaving the flag on ramdisk and try the flash again
Thank you for your answer. You mean the check of the “Recovery Mode Option“ when I patch the file with magisk?
peppet said:
hi, don't worry about rebooting into recovery to wipe, if you did a clean install that's not the problem. i think the problem is the file patched with magisk. try to patch a new one leaving the flag on ramdisk and try the flash again
Click to expand...
Click to collapse
Thank you very much. It worked perfectly with leaving the flag on ramdisk. Just a little change, but it saved my day. Thanks.