i have flashed the offical stock firmware via odin, before data i wiped all the data via custom recovery.
then i also locked the bootloader again because it is was open by lock oem.
is that enough and means my phone is fully unrooted? i dont want that google will detected my device is rooted.
should i install stock recovery? or can i stay with the custom recovery ?
what custom rom i can use that there is anything about root ?
EREVtov said:
i have flashed the offical stock firmware via odin, before data i wiped all the data via custom recovery.
then i also locked the bootloader again because it is was open by lock oem.
is that enough and means my phone is fully unrooted? i dont want that google will detected my device is rooted.
should i install stock recovery? or can i stay with the custom recovery ?
what custom rom i can use that there is anything about root ?
Click to expand...
Click to collapse
Bootloader and root are 2 different things.
What method of root did you have installed?
SuperSU? Magisk? Something else?
magisk.
i flashed the offial firmware of 6.0, same bootloader and mm for it.
i earsed all the data and system before flashing the offical firmware, even the custom recovery has been removed while flashing that.
however i saw the the oem button at develpoers options was enbaled even after the flashing, so i turn it off.
anything else i need to do ?
and if i will custom recovery, would it detected as root? or it is fine ?
garylawwd said:
Bootloader and root are 2 different things.
What method of root did you have installed?
SuperSU? Magisk? Something else?
Click to expand...
Click to collapse
magisk.
i flashed the offial firmware of 6.0, same bootloader and mm for it.
i earsed all the data and system before flashing the offical firmware, even the custom recovery has been removed while flashing that.
however i saw the the oem button at develpoers options was enbaled even after the flashing, so i turn it off.
anything else i need to do ?
and if i will custom recovery, would it detected as root? or it is fine ?
i think its because you flagged knox counter:/
You can still install Magisk v12 with fake knox 0x0
Reply if it solved your problem, and "OEM" its just a FRP (factory reset protection). You can see if you have a custom rom and you disable ACCIDENTLY FRP your will stuck at boot "frp lock..."
sry for my bad english
---------- Post added at 09:32 PM ---------- Previous post was at 09:32 PM ----------
Sorry if you cant unroot without having problem, soo try hide root
BaconOFBurgerPS said:
i think its because you flagged knox counter:/
You can still install Magisk v12 with fake knox 0x0
Reply if it solved your problem, and "OEM" its just a FRP (factory reset protection). You can see if you have a custom rom and you disable ACCIDENTLY FRP your will stuck at boot "frp lock..."
sry for my bad english
---------- Post added at 09:32 PM ---------- Previous post was at 09:32 PM ----------
Sorry if you cant unroot without having problem, soo try hide root
Click to expand...
Click to collapse
what is it knox counter: ?
i flashed a firmware stock from sammobile.
so oem unlock is not root? or custom recovery ?
Related
Anyone know when will be released for lg h340n Marshmallow root
I wanna know too ??
i too
I think the only possible root method is Chainfire's systemless root.
But you need to unlock the bootloader (warranty void) and install TWRP. But as always read about it:
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
---------- Post added at 06:32 PM ---------- Previous post was at 06:32 PM ----------
I think the only possible root method is Chainfire's systemless root.
But you need to unlock the bootloader (warranty void) and install TWRP. But as always read about it:
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
The question is how do we unlock the bootloader( or we just tick OEM Unlock from Dev settings) and how do we enter in fastboot mode to install twrp?
I am trying since several days to somehow install TWRP. And nothing works so far for the H340N .
My next idea is to downgrade again to v10h, then try to root (via kingroot i guess?). Change from kingroot to SU, then install Flashfire. Through Flashfire you should be able to install a OTA Update, such as Android 6.0 without loosing root. And then when you have root and the option to OEM-Unlock you should be able to install TWRP through the TWRP-Manager app. Or am i wrong at some point?
Would be nice to just have access to fastboot mode in marshmallow though...
A new version of kingroot was released yesterday. Can someone check if this version can root our device on marshmallow?
LuciIT said:
A new version of kingroot was released yesterday. Can someone check if this version can root our device on marshmallow?
Click to expand...
Click to collapse
cant root h340
can we install twrp on h340n without root? with fastboot and OEM unlock?
leandresca said:
can we install twrp on h340n without root? with fastboot and OEM unlock?
Click to expand...
Click to collapse
No, because there is not a fastboot mode as far as i know
Sent from my C6903 using XDA-Developers mobile app
I've seen some people with LG g4 with the same problem on MM. They can't root withou tunlocking bootloader. That sucks balls. Seems to be that the root needs to be on the boot partition, which is inaccessible without unlocking bootloader. The thing is, will OEM UNLOCK unlock bootloader? That's it? :/
Normally you can do "adb reboot-bootloader" and then "fastboot boot twrp.img".
But "adb reboot-bootloader" does not work with V20a, it just starts a normal boot.
Any luck so far?
Any News???
I would greatly appreciate if someone got a solution to root the H340N with android 6.0. Kingroot doesn't seem to support Android 6.0... :/
Regarding the "systemless root", anyone tried it with this phone and Android version?
I want to know to, and doeas anyone know how to unlock he bootloader, i have allow oem nlock ticked, but how do i actually do it, it doesn;t help that lg blocked the bootloader and recovery
root marshmallow lg h340n
Any news for root lg leon h340n?
Up, any2?
Hi,
...any information on how to apply root on this model would be appreciated, thank you.
Hi,
I successful root my LG-H340n marshmallow a few month ago. It's a mix of several tips found on Internet.
Using USB download mode and "LG Root Script v1.3", it's possible to have an access to partitions and change recovery partition to TWRP. Using the same way I change also aboot partition (with one compatible with twrp).
After TWRP installed, I use it to install SuperSU systemless root.
And It's magic now I can use my SD card and Apps2SD to create symbolinc link to my apps and free internal memory !
I have some notes and links, if you want, I can write a tutorial.
CID is 15. I don't know if the bootloader is locked or not and couldn't get adb to recognize device to check it. Does that matter if already rooted on 4.4.4? Any help appreciated.
To check if boot loader is locked boot into download mode and check for a line that says developer mode if you don't see that you are on a locked boot loader
---------- Post added at 07:54 AM ---------- Previous post was at 07:51 AM ----------
It depends on what you want to do with your phone
Do you want stable secure official warranty stock
or crazy good performance and ability to personalize everything but bad battery life and somewhat less secure experience
Thanks, [email protected]. I don't have "developer mode" when booting into download mode but...I tried that on a G900P that has rooted 6.0.1 on it and I believe an unlocked bootloader and it doesn't say anything about "developer mode" either.
I just want to upgrade to rooted stock MM 6.0.1 but not if it's a real pain in the neck. Knox doesn't matter at this point.
Try flashing twrp in Odin that will tell you for certain if your boot loader is unlocked and developer mode is only for Verizon s5 bootloader unlock
Thanks again, [email protected]. I tried latest version of ODIN to install latest TWRP but it failed with S5 reading "secure magiccode check fail: recovery." I don't know if that means the bootloader is locked or some other problem. At this point I'll probably just forget it and stay on KK 4.4.4 hoping somebody comes up with an easy way to root MM 6.0.1 like Towelroot or CF-Auto-Root or something. Thanks for the help.
It means your bootloader is locked that was just to test your bootloader unlock status
---------- Post added at 01:58 AM ---------- Previous post was at 01:46 AM ----------
To get bootloader unlocked go to getex kk-mm bootloader unlock for s5 Verizon on XDA developers under s5 Verizon section
Then flash twrp in odin
Then flash your custom ROM in twrp In this order
Do a twrp full backup to SD card or USB otg drive
Then do a Full wipe except usb storage and external storage
mm kernel
Mm modem
ROM
Optional Extras
Su hide
Xposed
Custom kernel
SuperSU zip
That doesn't look too bad. Will have to wait until tomorrow to start it. Thanks!
I got the bootloader unlocked and installed TWRP and did a full backup but now stumped. Don't know what to flash next or where to find it.
Still on rooted KK 4.4.4 but now with unlocked bootloader. Will probably just stay here until there is an easier method. Thanks!
Hi xda!
I have rooted my J5 (2015 6.0.1 Stock) with SuperSU flashed with recovery (SU binary installed in /su/bin/su) and i want unroot
how i can do a unroot?
There are any problems if I already have installed busybox in /su/xbin/ (/su/xbin/busybox) ?
regards.
There's a "full unroot" option in supersu settings or you can just reflash the stock boot.img with twrp recovery
The only way you can remove root is by flashing stock firmware using odin, and it is the most easiest, note, you can not hide that you have rooted your phone since knox is e fused, which means once you root, no matter what you do, it will always stay 0x1
@jam66 you should install stock only if you care of stock and your warranty but if you don't mind about TouchWiz you're fine with SuperSu uninstall options.
Taivotat2 said:
@jam66 you should install stock only if you care of stock and your warranty but if you don't mind about TouchWiz you're fine with SuperSu uninstall options.
Click to expand...
Click to collapse
i really don't want flash stock rom.
i not want install and configure my apps again.
i only want know if there is not problem if i use supersu full unroot if i having installed su binary in /su/bin/su and busybox in /su/xbin/
thanks.
jam66 said:
i really don't want flash stock rom.
i not want install and configure my apps again.
i only want know if there is not problem if i use supersu full unroot if i having installed su binary in /su/bin/su and busybox in /su/xbin/
thanks.
Click to expand...
Click to collapse
First of all, what is the reason you want to unroot?
Most of the people that want to unroot is because they want to take phone to the service, and they need to have phone status 'official' and you can only achieve that by flashing stock rom..
Edit: YOU DON'T NEED TO RECONFIGURE YOUR APPS, YOU DON'T LOSE DATA WHEN FLASHING SAME ANDROID VERSION USING ODIN
rhadz19 said:
There's a "full unroot" option in supersu settings or you can just reflash the stock boot.img with twrp recovery
Click to expand...
Click to collapse
when you say "reflash the stock boot.img" you mean restore a nandroid backup from a backup made by twrp ??? or a boot.img downloaded from somewhere?
Ragazzza said:
First of all, what is the reason you want to unroot?
Most of the people that want to unroot is because they want to take phone to the service, and they need to have phone status 'official' and you can only achieve that by flashing stock rom..
Edit: YOU DON'T NEED TO RECONFIGURE YOUR APPS, YOU DON'T LOSE DATA WHEN FLASHING SAME ANDROID VERSION USING ODIN
Click to expand...
Click to collapse
I want install magisk.
jam66 said:
I want install magisk.
Click to expand...
Click to collapse
Flash stock rom, this way you will fully unroot your phone and you won't lose any data, after that just install magisk and done, easiest way
Ragazzza said:
Flash stock rom, this way you will fully unroot your phone and you won't lose any data, after that just install magisk and done, easiest way
Click to expand...
Click to collapse
mmm i don't know what is the correct firmware version for my phone. i have a J5 2015 Dual-Sim (SM-J500M) but it was imported from another country. i don't know what country and for my country/carrier there are not firmware version. in SamMobile or samsung-firmware
some data:
Android: 6.0.1 (Stock)
baseband version: J500MUBU1BPI1
Compilation Number: MMB29M.J500MUBU1BPI2
Android security revision: 1 september 2016.
Ragazzza said:
YOU DON'T NEED TO RECONFIGURE YOUR APPS, YOU DON'T LOSE DATA WHEN FLASHING SAME ANDROID VERSION USING ODIN
Click to expand...
Click to collapse
Let me see if i understand to you. that mean i can flash for example this 2Gb .tar.md5 file i will have the same stock rom without root and all my config and data intact?
I personally did this way:
Uninstall root totally from SuperSu app itself.
Let BusyBox as is.
Flash the original boot.img of the rom with TWRP.
And then you can flash Magisk or Phh SuperUser choose what you prefer.
You go to Play Store and install BusyBox Stericson app to manage BusyBox and you're done. It's unnecessary flash the rom , but you can choose if you still prefer.
---------- Post added at 07:45 PM ---------- Previous post was at 07:42 PM ----------
jam66 said:
when you say "reflash the stock boot.img" you mean restore a nandroid backup from a backup made by twrp ??? or a boot.img downloaded from somewhere?
Click to expand...
Click to collapse
When you're in TWRP there two options flash zip and flash image.
You choose image, so TWRP "ask" you if it will be for boot or recovery. You will choose boot and then swipe to flash and you're done . That's is all.
---------- Post added at 07:59 PM ---------- Previous post was at 07:45 PM ----------
@jam66 After you uninstall root completely from device you need boot.img because when installing SuperSu it patches the kernel. So to avoid problems with it, it's preferable to flash the "virgin" boot.img of the rom you're using. This way you will get a clean flash with the Superuser zip of your choice.
Taivotat2 said:
@jam66 After you uninstall root completely from device you need boot.img because when installing SuperSu it patches the kernel. So to avoid problems with it, it's preferable to flash the "virgin" boot.img of the rom you're using. This way you will get a clean flash with the Superuser zip of your choice.
Click to expand...
Click to collapse
mmm it make sense...
now i'm thinking, where i find a appropriate boot.img file for flash in my phone?
looking inside /data folder, i found a compressed backup of stock boot.img created the same day i rooted my phone with supersu using twrp. this file might work for flash with twrp as you suggest?
When I flashed TWRP on my J500m the first thing I did was a fresh backup of my system. So I would pick the boot.img of this backup. After that I proceed rooting my phone. SuperSu makes backup of img when getting systemless root. You can try with that img it's supposed to be backup of original personally I never have troubles dealing with it because of the first nandroid backup never need to pick that img.
Hi I use samsung j5 2017 i have used supersu root checker and others and my phone isn't rooted but my samsung health keep saying cos of a new security policy s health can't be opened on rooted device and my phone isn't rooted
Bishop esther said:
Hi I use samsung j5 2017 i have used supersu root checker and others and my phone isn't rooted but my samsung health keep saying cos of a new security policy s health can't be opened on rooted device and my phone isn't rooted
Click to expand...
Click to collapse
It's bc of knox
Search your problem on google there is a way to solve it
I screwed up and left the bootloader unlocked when I flashed the 7.0 OTA. So, SafetyNet test fails and Android Pay refuses to work. Based on what I have found and read, I believe it is impossible (currently) to simply relock the bootloader. I think I need to root with Magisk and then use the appropriate module to hide root and unlocked status from Android Pay. Is that the possible? Is that the correct approach? I have been searching and reading but my mind is swimming now. Must be getting too old for this stuff.
Thanks in advance.
Root with magisk - hide is inbuilt - don't need add. module.
How to:
Boot twrp - fastboot boot NameTwrp3xx.img
Backup all with twrp
Restore boot with twrp
Install Magisk14+.zip
Reboot.
If you need - you can flash twrp.
---------- Post added at 07:21 AM ---------- Previous post was at 07:21 AM ----------
@BigBadger
dzidexx said:
Root with magisk - hide is inbuilt - don't need add. module.
How to:
Boot twrp - fastboot boot NameTwrp3xx.img
Backup all with twrp
Restore boot with twrp
Install Magisk14+.zip
Reboot.
If you need - you can flash twrp.
---------- Post added at 07:21 AM ---------- Previous post was at 07:21 AM ----------
@BigBadger
Click to expand...
Click to collapse
So I did this, and Magisk is installed, set to hide for Android Pay, and it's still not working. It still recognizes the unlocked bootloader. Is there anything else I can do?
What is in magisk manager - safety net status?
Magisk 14? Stock Nougat? @yaoverstand
@dzidexx
ctsProfile: false
basicIntegrity: false
stock nougat
Magisk 14
Latest TWRP
Sorry, I don't know why.
Wipe all, restore boot + system, format data and try again.
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
@yaoverstand
yaoverstand said:
So I did this, and Magisk is installed, set to hide for Android Pay, and it's still not working. It still recognizes the unlocked bootloader. Is there anything else I can do?
Click to expand...
Click to collapse
Go into Settings in the Magisk app, scroll down about halfway, and make sure the Magisk hide slider is on.
If it shows on toggle it off then back on and again then reboot and try the safety net check again. I've had to do this once or twice right after flashing Magisk.
@jason2678
Tried this just now, and I'm still failing the safety net check in the same manner.
Could it have to do with the fact that I flashed a stock nougat image instead of taking the ota?
What did you flashed?
Give here link to thread.
Your model is...? Give full info. @yaoverstand
dzidexx said:
What did you flashed?
Give here link to thread.
Your model is...? Give full info. @yaoverstand
Click to expand...
Click to collapse
Just an update. I flashed the official image from the when the OTA came out.
I restarted Magisk with hide slider off, and then turned it on when the phone came back on. Then I restarted again, and all is well. Passed safetynet and everything. Thanks guys!
jason2678 said:
Go into Settings in the Magisk app, scroll down about halfway, and make sure the Magisk hide slider is on.
If it shows on toggle it off then back on and again then reboot and try the safety net check again. I've had to do this once or twice right after flashing Magisk.
Click to expand...
Click to collapse
I think in magisk 14.3 it's on by default now
Spencervb256 said:
I think in magisk 14.3 it's on by default now
Click to expand...
Click to collapse
I think so too, but I've had it happen a few times where hide wasn't really on until I turned it off, then back on again. That might have been pre 14 versions. I don't flash my phone too often.
Hello There,
I'm looking for a way to downgrade my Moto G4 Plus from Oreo (8.1.0) to Nougat, this device lost signal network after the OTA update, and I need to reflash the modem files (I tried flashing the Oreo rom via fastboot but it didn't change anything).
If I install twrp, root the device, can I flash the original nougat rom? Can it get bricked or anything like that? I dont know if bootloader is updated with the oreo or it can be downgraded?
Via fastboot it doesnt work because of the android oreo downgrade protection stuff.
The driver for the modem, it is inside rom package? I can try rooting and forcing only the oreo driver again, can't I?
if you downgrade to Android 7 and apply any OTA your phone will get a HARDBRICK.
---------- Post added at 03:05 PM ---------- Previous post was at 02:20 PM ----------
Takx said:
Hello There,
I'm looking for a way to downgrade my Moto G4 Plus from Oreo (8.1.0) to Nougat, this device lost signal network after the OTA update, and I need to reflash the modem files (I tried flashing the Oreo rom via fastboot but it didn't change anything).
If I install twrp, root the device, can I flash the original nougat rom? Can it get bricked or anything like that? I dont know if bootloader is updated with the oreo or it can be downgraded?
Via fastboot it doesnt work because of the android oreo downgrade protection stuff.
The driver for the modem, it is inside rom package? I can try rooting and forcing only the oreo driver again, can't I?
Click to expand...
Click to collapse
you can downgrade to any version via Fastboot or via twrp, but NEVER apply a ota update because your phone will get a hardbrick