Related
I Unlocked the bootloader 3 days ago and flashed Cyanogenmod 12.1 with exact gapps and was able to use the phone perfectly ,today I searched for xposed and found that it could be only installed by manual flashing for android lollipop , so I downloaded the zip file and rebooted my phone in Recovery Mode [ TWRP ] and flashed the zip file just after that the phone stuck at bootloop. Restarted the phone 3 time's but no luck so finally I got into bootloader by pressing the volume down button and the power button and opened recovery mode to factory reset the phone and reflashed the CM 12.1 with gapps , now the problem begin's when I restarted the phone it is stuck at "Warning Bootloader Unlocked" and even the recovery mode is stuck at beginning screen of twrp , Im only able to use the bootloader . Even tried to reflash TWRP Recovery from computer but thier's no change it is still stuck at the recovery screen .
Any help would be really appreciated
try reflashing and then wiping cache's before rebooting ?
like the regular cache and dalvik cache.
also don't expect the first boot to work quick.. leave it for a long time...
good luck.
Actully the problem is , when i try to open recovery mode it stucks at teamwin logo (twrp)
"I searched for xposed and found that it could be only installed by manual flashing for android lollipop"
Click to expand...
Click to collapse
that quote is confusing.. what did you mean exactly.
What TWRP ? From Where + what version # ?
If i were you i would re-download it then MD5 hash it.. verify it !
I always check the md5 hashes on any phone roms or firmware etc.
I have had tons of incomplete downloads and there is nothing wrong with my internet connection either.
The more detailed you can be the more likely someone can help.
Once you are positive your TWRP is downloaded properly if i were you
i would re-flash it with fastboot. (if you can)
Can you power off the phone and put it in bootloader mode then connect to pc ?
power it off then hold volume down + power then plug in USB
then right click the empty space in the windows folder (assuming no Linux)
select open command prompt here then type:
adb devices
Is it listed ?
I also assumed you have "Minimal ADB and Fastboot" installed.
Sounds like you flashed a 5.1 firmware package ?
yes ? which one ?
And watch out many sites have cut off my download on me while downloading them.
and if you then flashed a half completed download you could prob damage the phone.
for checking hashes on windows i use HashSlash.. it's clean / free and has a GUI ..google it
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
sabungolfer0011 said:
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
Click to expand...
Click to collapse
https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
i used that.. but didn't flash my phone yet.
that is all firmware packages stock for Moto-2015
You still have not mentioned a lot like where did you get TWRP and what version ?
What carrier is your phone ?
I take it you unlocked the bootloader or did you get it like that ?
I'm guessing the bootloader loads TWRP
so either of those is probably damaged i bet.
I would try and get it stock then work from there getting TWRP back on and rooting etc.
What i was trying to ask you is..
Was your phone on 5.02 and you tried to update it to v5.1 ?
Because i have seen other people here who had problems with that.
Relocking the bootloader can cause problems and so can reverting to an old ver from 5.1 to 5.02
I used a custom kernel and TWRP from Squid here on the forum and rooted
and his kernel is only good for me up to version 5 but he has way newer versions out..
but they are only for users who updated to 5.1
So you have to be VERY careful what your doing.
I might have screwed up my phone if i didn't notice the fine print.
Also just search the forum for some guides on flashing firmware
and verify the downloads
My Bootloader is unlocked , TWRP Recovery Version 2.8.6.0 . My phone was on Android 5.0.2 [ Official Non Rooted ] , so I thought of updating it to 5.1.1 which was available as custom rom So I unlocked the bootloader flashed TWRP version 2.8.6.0 by copying Recovery.img in minimal adb folder and oped CMD and flashed the custom recory and it was no problem , then 2 days ago I flashed Cyanogenmod.12.1.Surnia.20150829.zip and it worked fine no issues then I flashed Xposed Modular in recovery mode , now when I tried to restart the system it stuck at bootloop so I entered Bootloader and again restarted 2, 3 times but no luck so I again entered bootloader and entered Recovery Mode ( TWRP 2.8.6.0) and wiped all my data , But unfortunately I was outside so I dint had the firmware and gapps so I switched the phone off in hope that ill flash the firmware and gapps when i reach back home . So when I vame back home and pasted the firmware and gapps in memory card and inserted it baxk in the phone and tried to enter recovery mode , that was the first time when I experied That teamwork logo stuck at recover mode and the further story you laready know
Hello,
I'm trying to install TWRP recovery mode on my Samsung Galaxy note 4 ( version N910FFXXU1DPE3) running under android 6.0.1 Marshmallow
I have rooted my phone (installed the CF_Autoroot stuff with Odin) , but it doesn't seem to be enough, because when i install TWRP and try to boot in recovery mode, my phone show a message "unable to do normal boot" and switch in "download mode" and get stuck in it.
I Fixed it to work normal again, and try to find what i did wrong :
And It seems I missed to "unlock" my "bootloader".
I try to find on internet how to do it, but i can't find anything
Either the file links are missing,
Either it's only for Android 5
Either its for another version of Galaxy note, and not for mine : N910F
I can't find any good tutorial to do it, can you help me with this ?
Thank you !
You're most likely using the wrong version of TWRP or the incorrect way to load it. Please link to which version you are trying to confirm.
es0tericcha0s said:
You're most likely using the wrong version of TWRP or the incorrect way to load it. Please link to which version you are trying to confirm.
Click to expand...
Click to collapse
Well i downloaded TWRP on android store.
Then he ask me the model of my phone, i choose Samsung galaxy s4 international
Then he hask me wich version of TWRP i want, I take the latest.
Then he ask me if it should install, and just before that it launch a popup saying "Warning : You have to be sure that your phone bootloader is unlocked, are you sure you want to proceed" ?
First time, i pressed Yes, and the phone was not starting anymore.
When starting normally or in recovery .it was saying "cannot boot normally" and it switch automatically in "download mode"
I understood after that it was because I only rooted my phone, but I never unlocked the bootloader in order to install a custom recovery.
Maybe it was a typo, but you said you choose S4 international, whereas in the title you mentioned having a Note 4. That would certainly cause this...
Other than that, just reflash the original firmware in Download Mode and then boot back to Download Mode and install TWRP that way.
Sorry I meant galaxy note 4 international. not s4.
You say its possible to install a TWRP with odin ? how ?
and without unlocking the bootloader ?
Because the bootloader is supposed to be here to prevent you from installing other Custommode, other OS... replacing the basic boot files..
That's what I don't understand.
I did it with odin.
Actually i kept reading that it wasnt possible to install TWRP on a locked bootloader...
But what i didn't know that was my bootloader wasn't lock in the first place!
sorry
Hello!
Thanks for reading this thread, there's a lot that I'm about to say based on what has happened for the past 8 hours of troubleshooting.
I hope you'll be able to help me regarding my issue.
Everything was going well as I on my way to unlock my bootloader (done) and root my device.
After rooting via TWRP, I'm stuck on the white XPERIA logo screen.
Proceeded to wipe my phone, and thanks to my stupidity, loss of OS.
Downloaded an GLOBAL OS online, tried to flash into my device with FlashTool.
Error came to me as I needed flash script.
Search online, to no avail, I went to my final option
I saw a tutorial of creating a pre-rooted ROM : https://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
I attached my OS I previously downloaded which i tried to flash with FlashTool, attached SuperSu into the application and a flashablezip (as instructed).
Flashed this pre-rooted ROM into my device using TWRP, rebooted.
New problem: Stuck at white Sony logo, couldn't enter TWRP.
Flashed in via cmd.exe a working boot.img & recovery.img.
TWRP now works, but I'm back to square one : stuck at the white XPERIA logo screen.
If you've read all of that, I thank you so much for doing so.
I hope that you'll be able to help me after these gruesome 8-hours of researching, trial & error session.
It's about time I requested help from professionals.
Thank you!
Edit : I can boot up my phone now, however that's achievable by removing SuperSu via TWRP.
This is no longer an urgent need for help, but it will be nice if I could get an idea why would I be stuck at the XPERIA logo screen when SuperSu is installed.
Mercuryus said:
Hello!
Thanks for reading this thread, there's a lot that I'm about to say based on what has happened for the past 8 hours of troubleshooting.
I hope you'll be able to help me regarding my issue.
Everything was going well as I on my way to unlock my bootloader (done) and root my device.
After rooting via TWRP, I'm stuck on the white XPERIA logo screen.
Proceeded to wipe my phone, and thanks to my stupidity, loss of OS.
Downloaded an GLOBAL OS online, tried to flash into my device with FlashTool.
Error came to me as I needed flash script.
Search online, to no avail, I went to my final option
I saw a tutorial of creating a pre-rooted ROM : https://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
I attached my OS I previously downloaded which i tried to flash with FlashTool, attached SuperSu into the application and a flashablezip (as instructed).
Flashed this pre-rooted ROM into my device using TWRP, rebooted.
New problem: Stuck at white Sony logo, couldn't enter TWRP.
Flashed in via cmd.exe a working boot.img & recovery.img.
TWRP now works, but I'm back to square one : stuck at the white XPERIA logo screen.
If you've read all of that, I thank you so much for doing so.
I hope that you'll be able to help me after these gruesome 8-hours of researching, trial & error session.
It's about time I requested help from professionals.
Thank you!
Edit : I can boot up my phone now, however that's achievable by removing SuperSu via TWRP.
This is no longer an urgent need for help, but it will be nice if I could get an idea why would I be stuck at the XPERIA logo screen when SuperSu is installed.
Click to expand...
Click to collapse
Hi, without any logcat it will be very hard to help you
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")
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