Cf-Auto Root Issue Soft or Hard brick ? - Galaxy S 4 Q&A, Help & Troubleshooting

Hi
If CF-Auto-root fail, its a hard or a soft brick ?
Thank for your answer

Neither of them. A brick is something completely different.
Just try to reflash cf auto-root or flash a stock rom.

Related

flash cf root g7102DXUANB1 soft risk :(

flash [CF-ROOT][SM-G7102] DXUANB1 soft risk , pleas update ...
forum.xda-developers.com/galaxy-grand-2/development/cf-root-root-galaxy-grand-2-t2698428

[Q] Can someone help me please

I purchased a note 3 model : N900 I have rooted the device with Kingo and now wish to install CWMR. I entered into download mode to install the recovery img file and was greeted with Chinese symbols! Anyway to chance this?
1. Kingo root is the worst root you can ever use.
2. Flash stock ROM via Odin. (It wipe kingo root and residues after kingo..)
3. Root again. (CF-auto-root or Use Philz touch recovery and flash superSU.zip)
verny94 said:
1. Kingo root is the worst root you can ever use.
2. Flash stock ROM via Odin. (It wipe kingo root and residues after kingo..)
3. Root again. (CF-auto-root or Use Philz touch recovery and flash superSU.zip)
Click to expand...
Click to collapse
Thanks for your advice, sadly after reading and reading I have seen more posts regarding this issue. The kingo software says your can click the unroot button but is malware still present on the device after the root removal? Also I can not flash stock rom via odin as I already stated its in bloody Chinese.
VonStarkeGSD said:
Thanks for your advice, sadly after reading and reading I have seen more posts regarding this issue. The kingo software says your can click the unroot button but is malware still present on the device after the root removal? Also I can not flash stock rom via odin as I already stated its in bloody Chinese.
Click to expand...
Click to collapse
Update: Managed to install CWM using MTK DROID instead all done

[Q] Restore factory image after tripping KNOX on 900t

Hey there, I'm an idiot... I tripped KNOX and now phone is stuck on Tmobile boot screen. With so many different ways to do things and so many variants of this frickin phone and Android it seems the rules are every changing.
So my questions:
1.) How can I get this thing back to working? Can I flash a factory image with ODIN? If so which factory image do I use and what version of ODIN and what boxes need to be ticked in ODIN?
2.) Will #1 reset KNOX? Can KNOX be reset?
3.) Whats the best method to get the thing rooted so I can put a ROM on it. I hate TouchWiz. I tried using this method but it landed me here... http://www.androidrootz.com/2014/04/how-to-root-galaxy-s5-recovery-root.html
Thanks in advance....
Can I just flash the corresponding firmware with ODIN? Is it that simple? Does the firmware version displayed in factory recovery always correspond to the firmware to flash with ODIN? Any insights would help!!!! Thanks for your time!
sammobile dot com, grab a stock ROM for your model S5 (G900T), flash with ODIN
KNOX is permanently tripped now, no way to reset
your knox is permanently tripped, so might as well do what you want with the phone.
if you can get into download mode, you should be able to flash a recovery through ODIN, and then flash the rom of your choice. if that doesn't work, follow Detection's post above and flash a factory Tmobile rom through ODIN and start again.
That's all great thanks all, but does the firmware have to match the version that corresponds to the recovery that is currently on it? For instance, if I flashed 5.1.1 me thinks I wouldn't be able to root it or downgrade it thereafter, correct?
[bor]Its the loosey goosey instructions for multiple methods of doing the same thing for various android versions that make this sketchy. I found it easier to flash my HTC magic with jesus freak and a gold card than it is to flash this thing...or maybe my brain is decaying. Anyway, not what I expected for a common android phone. [/eor]

Recovery booting... fails to boot to recovery - i9505

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)...

Stock ROM pre-rooted?

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

Categories

Resources