Morning everyone,
I have searched and searched, is it possible to root these A3's as yet?
I bought this s a replacement for my son as he broke his s5 mini sitting on it lol.
Best wishes
If tripping KNOX is not a worry, you can flash TWRP, and flash the SuperSU package. (Optionally, you can flash back the stock recovery, and retain the root.)
There is no solution without tripping KNOX yet, CF-AutoRoot has not been updated for A300FU Marshmallow yet.
PlutoDelic said:
If tripping KNOX is not a worry, you can flash TWRP, and flash the SuperSU package. (Optionally, you can flash back the stock recovery, and retain the root.)
There is no solution without tripping KNOX yet, CF-AutoRoot has not been updated for A300FU Marshmallow yet.
Click to expand...
Click to collapse
Hi,
I tried downgrading to lollipop without success, as it would stay on samsung logo.
So i had to use smart switch to re-install marshmellow.
Tripping knox is no issue, Therefore as supersu not been updated it would leave me with only option to go back to lollipop?
If so, is there a tut i could follow as doing usal way with odin etc did simply not work.
The A3 is on 02 network
Best wishes
Go for the 4 file package then, it is the only thing that keeps saving peoples phones around here.
Use SamFirm for to download them (make sure you tick binary update)
Related
I'm using their latest firmware and update. Is it possible to root? I just want to change the resolution of the screen -- everything is so damn huge.
Install a launcher. Also reduce text size.
Sent from my SM-N9005 using Tapatalk
An easy way to root would be to install TWRP and flash supersu from TWRP. This will also trip the knox counter and change it from 0x0 to 0x1. This is not an issue unless you still have warranty on the phone.
I also recommend updating to the latest doh1 ROM before installing TWRP.
audit13 said:
An easy way to root would be to install TWRP and flash supersu from TWRP. This will also trip the knox counter and change it from 0x0 to 0x1. This is not an issue unless you still have warranty on the phone.
I also recommend updating to the latest doh1 ROM before installing TWRP.
Click to expand...
Click to collapse
So you have successfully flashed N900W8VLU2DOH1 firmware and rooted it with the latest, which is for 5.0, cf-auto-root from chainfire.eu?
Nope, I used supersu.zip which was from from TWRP.
I've posted my solutions here
Hi
I have a new Samsung S4 (i9505) (yep - new with waranty, apparently). The phone came with Lollipop but I downgraded to Kitkat (4.4.2) to root without tripping Knox.
I have successfully rooted (after several soft bricks) and my Knox counter remains at 0x0 - but I cannot boot to recovery (the phone says "recovery booting..." in blue small text at the top but then goes to a normal boot with boot loop). I can boot in to the normal mode, and can boot to safe mode, and can boot to download mode - but not to recovery. And cannot factory reset the phone (from settings - the procedure just leaves the phone as it is). I have tried (successfully) to flash the Lollipop bootloader, and have tried (unsuccessfully) to flash the image file extracted from the stock lollipop ROM (extracted recovery.img, used 7zip to create a tar file, and tried flashing as AP with Odin 3.09 but it fails to write the file)... I also tried the OTA update back to Lollipop (using the settings, update option on the phone) but that too failed.
The phone seems to work but I just cannot get in to recovery mode (and cannot factory reset the phone). I am using the original usb cable and a usb port directly connected to the mother board (and have successfully flashed other components). Any suggestions as to how to re-enable or restore the recovery (without tripping Knox warranty counter)?
Many thanks for any help
Flash the whole firmware with Odin.
Custom recovery is a no-go as it will trip Knox.
GDReaper said:
Flash the whole firmware with Odin.
Custom recovery is a no-go as it will trip Knox.
Click to expand...
Click to collapse
Thanks for that.
I was leaving a complete reflash to Lollipop (with Odin) as a last resort - as this would cause me to lose root. However, yesterday I chose the backup function on FlashFire to backup (to the external SD card) the phone with Kitkat and root and... following the backup, all apps (system and user) fail on boot so I have no option but to reflash anyway (worked without issue). Not sure what happened with FireFlash - all I did was to select backup - but is must have affected the phone in some way... I guess it is incompatible with the S4 or Kitkat (or both).
I am still confused: what will have prevented the phone from booting to recovery with the Kitkat image (and prevented me from reflashing the stock Lollipop recovery via Odin)? And what is the issue with FireFlash (I can not understand why taking a backup should cause a problem when rebooting the phone).
I will start again trying to gain root without tripping Knox (downgrading to Kitkat, using TR to root, then, hopefully, upgrading via Mobile Odin with everroot)...
Thanks again for your help.
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
GDReaper said:
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
Click to expand...
Click to collapse
Thanks again for your response. When I tried removing Knox with the Knox removal script in Mobile Odin having downgraded my device to Kitkat, I got a soft brick which did take a while to fix (but did get fixed eventually). I had thought of perhaps trying to upgrade from rooted Kitkat to Lollipop using FireFlash but was a bit disconcerted at the way it crashed my device when I only tried backing up the phone (and not flashing anything at all) using it.
Do you know whether the issue I had with FireFlash is indicative of FireFlash being incompatible with my device or is the symptom I had just something that may randomly occur (ie is there any point trying to use FireFlash upgrade from rooted but not Knoz tripped 4.4.2 to rooted and not Knox tripped 5.01)?
Many thanks for all your help and best wishes, Boris.
bprtzel said:
Thanks again for your response. When I tried removing Knox with the Knox removal script in Mobile Odin having downgraded my device to Kitkat, I got a soft brick which did take a while to fix (but did get fixed eventually). I had thought of perhaps trying to upgrade from rooted Kitkat to Lollipop using FireFlash but was a bit disconcerted at the way it crashed my device when I only tried backing up the phone (and not flashing anything at all) using it.
Do you know whether the issue I had with FireFlash is indicative of FireFlash being incompatible with my device or is the symptom I had just something that may randomly occur (ie is there any point trying to use FireFlash upgrade from rooted but not Knoz tripped 4.4.2 to rooted and not Knox tripped 5.01)?
Many thanks for all your help and best wishes, Boris.
Click to expand...
Click to collapse
Sorry - FlashFire not FireFlash!
Mobile Odin and bricked phone?
GDReaper said:
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
Click to expand...
Click to collapse
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
bprtzel said:
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
Click to expand...
Click to collapse
I tried to update my modem and bootloader with it. I also was on a custom ROM.
bprtzel said:
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
Click to expand...
Click to collapse
Just to say I finally got my phone to Lollipop (5.01) rooted with Knox guarantee void remaining at 0x0.
I downgraded (again) to 4.4.2 with Odin, installed the GF1 kernel, used towel root (my wifi was still working though it would not remember the wifi passwords), the used FireFlash to upgrade back to stock 5.01 plus SU beta.zip as OTA/ZIP. All worked great - except I now cannot get the wifi to switch on. Used Odin to load the Lollipop BL and also Lollipop kernel, and did a factory reset for good measure too but still no wifi... (can't switch the switch to on). Guess I will try the GSM modem to just to see if that helps (unless anyone has other suggestions)...
Hi to everyone, I have a galaxy A5(2016) A510F and I want to root it but this will trip knox so I want to ask if we root a stock rom and flash it via odin does this detect root and trip knox ? (we will modify the system.img that we find in.tar file)
It probably won't trigger KNOX, but root access would be unstable, at best. Try using KingRoot instead - if it works on your device, it will root it and keep the KNOX counter the same, and if it doesn't, it'll just tell you that it can't root your phone.
I don't want try it because my phone it's new so can someone try it and post the result ? Maybe someone that have already trigger knox, this don't want to be a problem for him/her
EDIT: I think Kingroot don't work http://forum.xda-developers.com/sam...ment/galaxy-a5-2016-success-kingroot-t3400564
Up
I tried king root, but after reebooting my phone was unrooted. I suggest you to flash cf autoroot because, yes, it trips knox counter, but If u soft-brick your device in any way, you can always solve it using odin and flashing stock firmware/PIT...
They are two different things, maybe you are confused because it doesn't mean that if you flash cf autoroot and soft-brick your devices you can unbrick it just flashing stock rom, yes this is true but you can unbrick you phone in anytime without having cf autoroot!
I didn't mean that, i know odin doesn't request root permission, I said that if he flashes cf autoroot and he soft-bricks his device ( I know it's almost impossible ) he will resolve the problem by flashing stock formware (or a custom ROM after wiped cache, dalvik, data and system)
Unfortunately not possible to pre-root a stock Samsung 5.1.1 or 6.0 rom and preserve knox. It will boot loop your device. Selinux will block root and prevent the device from booting unless the boot.img is patched to remove the selinux root restriction.
However patching the boot.img trips knox, catch 22 situation.
Keep hoping for kingroot or Kingoroot if you want to preserve the knox counter.
Thanks for the reply
Can anyone try this http://www.samsungsfour.com/tutorials/how-to-root-all-samsung-galaxy-smartphones-without-pc.html ? I don't want to trip my knox!
If it works it wont trip knox as it doesn't touch the binaries.
Unfortunatelly, I can't try because i've already tripped the knox
so a family member asked me to downgrade his samsung galaxy s5 from android 6.0.1 to the previous version.
i've googled it a bit but only found ways where you either lose your data or need root and he won't let me root his phone.
is it still possible and could someone either explain or link me how to do this?
thnx
Backup photos and videos then downgrade via odin but i am not sure if knox will trip and make wipe to dont get bootloop
Backup using Smart Switch
Downgrade by flashing the ROM you want over the top with ODIN
Got a feeling you'll get a load of FCs / errors on boot with MM apps trying to run on LP, if yes, factory reset from recovery and restore with smart switch
It's won't trip KNOX, that's only tripped by flashing custom
*Detection* said:
Backup using Smart Switch
Downgrade by flashing the ROM you want over the top with ODIN
Got a feeling you'll get a load of FCs / errors on boot with MM apps trying to run on LP, if yes, factory reset from recovery and restore with smart switch
It's won't trip KNOX, that's only tripped by flashing custom
Click to expand...
Click to collapse
kool, i just got access to his phone and he told me he doesn't care about his warranty so i've just rooted it for him. is there a better way to do this and keep all data now that its rooted?
and are you sure this will save my app data too?
*Detection* said:
Backup using Smart Switch
Downgrade by flashing the ROM you want over the top with ODIN
Got a feeling you'll get a load of FCs / errors on boot with MM apps trying to run on LP, if yes, factory reset from recovery and restore with smart switch
It's won't trip KNOX, that's only tripped by flashing custom
Click to expand...
Click to collapse
Hi there! I just this post of your's that perfectly fits for my objective.
Is it really possible to downgrade From official stock Marshmallow 6.0.1 to official stock kitkat 4.4.2 without tripping knox? Also does the bootloader will allow you to downgrade?
Just saw this forum and he said that secure bootloader will block any downgrade
"If on Marshmallow 6.0.1 you will probably not be able to downgrade.
Odin will fail at s.boot - the secure bootloader that will block the downgrade."
Source of quote from greenman's post:
http://www.sammobile.com/forum/showthread.php?t=24635&page=2
[Sorted out] I did not root, however my s7 edge does not allow me to use s health claiming root after reinstalat stock via odin. Any solution for that?
Did you trip the Knox counter? If you did, there's no way back
The knox was changed, but I wonder how could that be that it was a stock rom?
Br9 said:
The knox was changed, but I wonder how could that be that it was a stock rom?
Click to expand...
Click to collapse
Did you install TWRP or made any changes in the bootloader.
Once the boot loader has been modified in any way. \it will trip knox.
No. I just reinstalled stock via odin, there was no twrp installation.
Br9 said:
No. I just reinstalled stock via odin, there was no twrp installation.
Click to expand...
Click to collapse
why did you have reinstall stock /
if you have reinstall stock that means something was done to your phone, which caused your phone to think knox is tripped.
So what happened that you ned to reflash your phone ?
System crashes with crashes
Are you the original owner of this phone?
If you try to root it or install anything non-Samsung, it will trip knox and there is no turning back.
Flashing Samsung ROMs via Odin won't trip knox....
I'm his first owner. I saw in a post that it is possible to continue using s health if dowgrade to marshmallow and then upgrade via OTA to 7.0. Do you know if it's possible?
Br9 said:
I'm his first owner. I saw in a post that it is possible to continue using s health if dowgrade to marshmallow and then upgrade via OTA to 7.0. Do you know if it's possible?
Click to expand...
Click to collapse
I think you just have to add or modify a line in system/build.prop and it will work. For that, you have to be rooted.
Take a look here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
Sorted out. I was able to reuse the app by going back to 6.0 via odin, configuring the app and upgrading via OTA to 7.0